ASSOCIATION CONNECTING ELECTRONICS INDUSTRIES ® IPC-2577 Sectional Requirements for Supply Chain Communication of Manufacturing Quality Assessment - Product Data eXchange (PDX) Proposed Standard for Ballot IPC-2577 February 2005 A standard developed by IPC 2215 Sanders Road, Northbrook, IL 60062-6135 Tel 847.509.9700 Fax 847.509.9798 www.ipc.org The Principles of Standardization In May 1995 the IPC’s Technical Activities Executive Committee adopted Principles of Standardization as a guiding principle of IPC’s standardization efforts Standards Should: • Show relationship to Design for Manufacturability (DFM) and Design for the Environment (DFE) • Minimize time to market • Contain simple (simplified) language • Just include spec information • Focus on end product performance • Include a feedback system on use and problems for future improvement Notice Standards Should Not: • Inhibit innovation • Increase time-to-market • Keep people out • Increase cycle time • Tell you how to make something • Contain anything that cannot be defended with data IPC Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of IPC from manufacturing or selling products not conforming to such Standards and Publication, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than IPC members, whether the standard is to be used either domestically or internationally Recommended Standards and Publications are adopted by IPC without regard to whether their adoption may involve patents on articles, materials, or processes By such action, IPC does not assume any liability to any patent owner, nor they assume any obligation whatever to parties adopting the Recommended Standard or Publication Users are also wholly responsible for protecting themselves against all claims of liabilities for patent infringement IPC Position Statement on Specification Revision Change It is the position of IPC’s Technical Activities Executive Committee (TAEC) that the use and implementation of IPC publications is voluntary and is part of a relationship entered into by customer and supplier When an IPC publication is updated and a new revision is published, it is the opinion of the TAEC that the use of the new revision as part of an existing relationship is not automatic unless required by the contract The TAEC recommends the use of the latest revision Adopted October 1998 Why is there a charge for this document? Your purchase of this document contributes to the ongoing development of new and updated industry standards and publications Standards allow manufacturers, customers, and suppliers to understand one another better Standards allow manufacturers greater efficiencies when they can set up their processes to meet industry standards, allowing them to offer their customers lower costs IPC spends hundreds of thousands of dollars annually to support IPC’s volunteers in the standards and publications development process There are many rounds of drafts sent out for review and the committees spend hundreds of hours in review and development IPC’s staff attends and participates in committee activities, typesets and circulates document drafts, and follows all necessary procedures to qualify for ANSI approval IPC’s membership dues have been kept low to allow as many companies as possible to participate Therefore, the standards and publications revenue is necessary to complement dues revenue The price schedule offers a 50% discount to IPC members If your company buys IPC standards and publications, why not take advantage of this and the many other benefits of IPC membership as well? For more information on membership in IPC, please visit www.ipc.org or call 847/790-5372 Thank you for your continued support ©Copyright 2004 IPC, Northbrook, Illinois All rights reserved under both international and Pan-American copyright conventions Any copying, scanning or other reproduction of these materials without the prior written consent of the copyright holder is strictly prohibited and constitutes infringement under the Copyright Law of the United States IPC-2577 ASSOCIATION CONNECTING ELECTRONICS INDUSTRIES ® PDX – Quality Assessment Sectional Requirements for Supply Chain Communication of Manufacturing Quality Assessment – Product Data eXchange (PDX) A standard developed by the Product Manufacturing Quality Exchange Task Group (2-15d) of the Supply Chain Communication Subcommittee (2-15) of IPC The IPC-2577 standard defines an XML encoding scheme that captures the setting and updating of quality goals, communicating and responding to quality excursions and reporting actual data from manufacturing and repair operations Users of this standard are encouraged to participate in the development of future revisions Contact: IPC 2215 Sanders Road Northbrook, Illinois 60062-6135 Tel 847 509.9700 Fax 847 509.9798 IPC-2577 February 2004 Acknowledgment Any document involving a complex technology draws material from a vast number of sources While the principal members of the Product Manufacturing Quality Exchange Task Group (2-15d) of the Supply Chain Communication Subcommittee (2-15) are shown below, it is not possible to include all of those who assisted in the evolution of this standard To each of them, the members of the IPC extend their gratitude Supply Chain Communication Subcommittee Product Manufacturing Quality Exchange Task Group Technical Liaisons of the IPC Board of Directors Chair Barbara Goldstein NIST Co-Chairs Douglas Furbush Georgia Institute of Technology Nilesh S Naik Eagle Circuits Inc John Cartwright Intel Corporation Sammy Yi Flextronics International Product Manufacturing Quality Exchange Task Group Agile Software Corporation, Roy Stafford Hewlett-Packard Company, Stan Pluta Celestica Corporation, Robert Voitus Intel Corporation, Mike Alner E2open, Richard Kubin Intel Corporation, Mike Stankavich Georgia Institute of Technology, Andrew D Dugenske Lucent Technologies Inc., Bernard Morel Georgia Institute of Technology, Douglas A Furbush NIST Nat’l Institute of Stds & Technology, Barbara Goldstein Hewlett-Packard Company, David Lienhard NIST Nat’l Institute of Stds & Technology, John Messina ii Intel Corporation, John Cartwright Nortel Networks, Christopher Stranc Nortel Networks Limited, Richard Lee National Electronics Manufacturing Initiative, Inc., David Godlewski Siemens Dematic Corporation, Cord Burmeister Village Principle Partners, Jim Harrington IPC-2577 Draft document for consensus vote only February 2005 Contents Introduction 1 SCOPE 1.1 1.2 Focus and intent Business Objectives 1.2.1 Quality Metrics 1.2.2 Quality Issues 1.2.3 Corrective Actions 1.2.4 Repair/Failure Analysis APPLICABLE DOCUMENTS 2.1 Introduction 2.1.1 IPC 2500 CAMX Series 2.1.2 RosettaNet 2.2 Documentation conventions 2.3 Notation GRAPHICAL REPRESENTATION AND XML STRUCTURE 3.1 3.2 3.3 Quality – The Quality Tree 3.1.1 XML Glossary – Quality Tree 3.1.1.1 Element: Quality Quality – Quality Metrics 3.2.1 XML Glossary – Quality Metrics 3.2.1.1 Element: QualityMetrics 3.2.1.2 Element: QualityMetric 3.2.1.3 Element: DataMeasure 3.2.1.4 Element: Attachments 10 3.2.1.5 Element: TimePeriod 10 3.2.1.6 Element: EntityDefinition 10 3.2.1.7 Element: ProductReference 11 3.2.1.8 Element: ProductIdentification 11 3.2.1.9 Element: PartnerProductIdentification 12 3.2.1.10 Element: ProductIdentificationReferenceInformation 12 Quality – Quality Issues 13 3.3.1 XML Glossary –(Quality Issues - Exceptions/Incidents) 13 3.3.1.1 Element: QualityIssues 13 3.3.1.2 Element: QualityIssue 13 3.3.1.3 Element: AffectedItems 15 3.3.1.4 Element: Attachments 15 3.3.1.5 Element: Customer 15 3.3.1.6 Element: BusinessDescription 15 3.3.1.7 Element: PartnerBusinessIdentification 16 3.3.1.8 Element: RelatedIssues 16 3.3.1.9 Element: RelatedIssue 16 3.3.1.10 Element: Supplier 17 IPC-2577 3.4 Draft document for consensus vote only February 2005 Quality – Corrective Action 18 3.4.1 XML Glossary – (Corrective Action standard) 18 3.4.1.1 Element: QualityCorrectiveActions 18 3.4.1.2 Element: QualityCorrectiveAction 18 3.4.1.3 Element: AffectedItems 20 3.4.1.4 Element: Approvers 20 3.4.1.5 Element: History 20 3.4.1.6 Element: Attachments 20 3.5 Proactive Quality Repair Data exchange standard 21 3.5.1 XML Glossary – Quality Repair Data exchange standard 21 3.5.1.1 Element: QualityRepairs 21 3.5.1.2 Element: ProductRepairAndFailureData 21 3.5.1.3 Element: CustomerInformation 22 3.5.1.4 Element: GeographicRegion 22 3.5.1.5 Element: ReceivedProductReference 23 3.5.1.6 Element: DocumentReference 23 3.5.1.7 Element: FinalProductReference 24 3.5.1.8 Element: QualityIncidentInformation 24 3.5.1.9 Element: IncidentDetail 25 3.5.1.10 Element: FailureEvent (choice) 25 3.5.1.11 Element: RepairEvent (choice) 26 3.5.1.12 Element: TestInformation 26 3.5.1.13 Element: TestEnvironment 27 3.5.1.14 Element: TestLocation 27 3.5.1.15 Element: TestName 28 3.5.1.16 Element: TestResultInformation 28 3.5.1.17 Element: testResultDetail 28 3.5.1.18 Element: ComponentRepairData 29 3.5.1.19 Element: ComponentIncidentInformation 30 3.5.1.20 Element: ComponentLocationInformation 30 3.5.1.21 Element: RepairProvider 30 3.5.1.22 Element: RepairDataSupplier 31 Appendix A – Recommended Codes and Values IPC-2577 Draft document for consensus vote only February 2005 Sectional Requirements for Supply Chain Communication of Manufacturing Quality Assessment – Product Data eXchange (PDX) Introduction The IPC-2571 document provides introductory and explanatory information about this standard and includes other elements that are also required or available The IPC-2571 dictates the required package structure and XML format for information exchange using any of the subsequent IPC-257x standards such as this one (IPC-2577) In any such exchange, a Product Data eXchange package must be defined which contains at a minimum a single pdx.xml file This file in turn is required to contain a single ProductDataeXchangePackage element, and may contain any number of other elements from this specification The Product Data eXchange package may optionally contain or refer to related external files (see IPC-2571 documentation) This standard (IPC-2577) covers the sectional requirements for the exchange of Product Quality information resulting from manufacturing, assembly, test, repair and failure tracking Quality Metrics are also defined and the actual metric can be exchanged between parties SCOPE This standard (IPC-2577) defines an XML encoding scheme that allows business partners to set and update quality goals, communicate and respond to quality excursions, and report actual data from manufacturing and repair operations Information represented in this standard includes such things as: quality metrics and goals, manufacturing quality results and failure tracking data, parametric data, quality performance, repair detail and corrective actions 1.1 Focus and intent This standard facilitates the exchange of manufacturing & repair information between supply chain partners that supports warranty tracking, product excursion containment, and product quality functions The generic format requirements are provided in a series of standards focused on printed board manufacturing, assembly, and inspection testing This standard series consists of a generic standard (IPC-2571) that contains all the general requirements and this quality standard (IPC2577) as an element inside the IPC-2571 There are four sectional standards that are focused on the XML quality details used to define and report information in the area of quality performance and detailed process information 1.2 Business Objectives Any IPC-2577 quality file is composed of a high level element PDX structure (IPC-2571) that contains any of the following IPC-2577 subelements: QualityMetrics – Defines the different quality performance Metrics and actual measurements, QualityIssues – Defines the different quality Issues that arose during production, CorrectiveActions – Defines the different Corrective Actions that address the related issues, Repair/Failure Analysis – Defines the different instances where failures occurred and the repair steps to correct the issue and/or the disposition IPC-2577 Draft document for consensus vote only February 2005 Listed below are the Main Elements in the Quality Specification There are four use cases currently defined that address several Quality exchanges There must be at least one use case defined Multiple cases can be included in one file Each case has its unique role so it would be impractical to see all use cases included in one transmission 1.2.1 Quality Metrics In this use case scenario, information is exchanged between supply chain partners to set key parameters for the other data exchange scenarios It defines elements related to the data exchange of performance metrics, which could be collected by product, line, cell, workstation, etc This scenario allows for actual measurements to be reported against the goals This scenario is defined as a unidirectional exchange Use case: Establish parameters for capturing production volume metrics and communicating the quality codes, values & descriptions Update the parameters for capturing production volume metrics and quality codes, values & descriptions Business Objective: To understand the quality data being transferred between the contracting company and the contractee it is necessary to agree in advance on, the volume measurements will be taken, the level of data to be passed and the content (or values) within the data The “quality data exchange metrics set-up and actuals” definition allows a contractor to set the data criteria for the contractee Using this standard the contractor can: • Establish and update the data volume measurements used to support product production; • Define the values and description of the quality codes being exchanged from the contractee These quality codes can be used within any entity of the data being exchanged Examples of these quality codes would be failure/repair codes, test codes, cross-reference values etc These quality codes support both production processing and repair processing 1.2.2 Quality Issues In this use case scenario, information is exchanged between supply chain partners to communicate production issues It defines elements related to the data exchange of product nonconformance, or other issues that require resolution These quality issues could be collected by product, line, cell, workstation, etc This scenario allows for actual issues to be reported or product service requests (PSRs) to be initiated Use Case: Respond to Quality Issues – Symptoms and Problems Business Objective: To provide bilateral data exchange to communicate and provide feedback resolution for quality issues This data exchange can be initiated by either the contractor or the contractee and both can play either of the actor roles depending on who is responsible for the corrective action 1.2.3 Corrective Actions In this use case scenario, information is exchanged between supply chain partners to communicate a corrective action (or actions) to open issues It defines elements related to the data exchange of resolution of open quality issues The corrective action(s) can address the product, line, cell, workstation, employee training, etc This scenario allows for resolution to reference multiple actual issues that were reported or product service requests (PSRs) This scenario is defined as a unidirectional exchange IPC-2577 Draft document for consensus vote only February 2005 Use Case: Respond to Quality Issues by Correction Actions Business Objective: To monitor product health to proactively prevent product excursions and drive corrective actions, and to utilize the data to drive continuous improvement and next generation improvements The standard is setup to enable the exchange to support various levels of business and product maturity As an example, data exchange content could vary by production type The cross reference of related issues is available to enable a linkage between an issue and the corrective action data As an example: • This would permit the tracking of a failure in a manufacturing line to a corrective action / repair from another supplier i.e a hard drive reported as the failure cause on a systems integration line could be tracked back to the corrective action/repair record of the hard drive 1.2.4 Repair/Failure Analysis In this use case scenario (ProductRepairAndFailureData), repair and failure analysis information is exchanged between business partners The information may include product related repair and failure analysis details concerning individual product instances The standard supports test, failure and environmental data, which can be cross-referenced to other supply chain partners Use Case: To capture a final disposition, failure analysis, root cause and component usage data from repair providers Communicate repair and/or failure information about a product to support the control of the repair process and the lowering of the repair costs Business Objective: To provide a data exchange to communicate failure and repair data from repair providers In this standard the data receiver is expecting a data exchange for each repaired item or group of repaired items This data could include: • identification of the product (individual or quantity driven); • disposition of the product; • failure and repair codes associated with each incident for the product; • identification of sub-assemblies (or components) repaired or replaced; • failure and repair codes associated with the sub assemblies; • test data associated with the failure or repair of the product and/or sub-assembly; • Cross-reference data for the product (i.e RMA Number, PO, Master Event Number etc ) The Repair Quality Data exchange standard supports a flexible ongoing feed of repair and failure data in which the level of data being communicated is negotiated between the company (such as an EMS) requesting the data (contractor) and the repair provider(s) (contractee) performing the failure analysis and repair From a manufacturing standpoint this standard can support a production line in which finished products are being integrated to create a new product to be sent to an end customer (e.g Building a server) As testing is performed on the integrated products any failure data associated with the sub-assembly would be sent to a repair provider contracted to repair the sub-assembly Any failure or repair quality data captured by the repair provider would be sent to the EMS where aggregation and trend analysis could take place IPC-2577 Draft document for consensus vote only February 2005 This flexible standard can also be used for post customer support If a customer sends a defective product to a repair provider this standard would allow: • The customer to send failure or repair information found at the customer site to the repair provider This could lower cost of the repair to the contractor by providing the repair provider has an understanding of the failure that was found at the customer site • Once completing the repair, the repair provider could send quality data about the repair to the EMS • The EMS could use the data from the two repair providers to support failure/repair trend analysis They could also use the data to manage the business relationship with their contracted repair providers APPLICABLE DOCUMENTS 2.1 Introduction There are relationships to other standard initiatives The following documents contain provisions, which, through reference in this text, constitute provisions of this standard All documents are subject to revision Parties who make agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the documents These include the following: 2.1.1 IPC 2500 CAMX Series The CAMX Series standard (IPC 2500’s) describes printed boards and printed board assemblies in various definitions from a graphical representation (CAD), a manufacturing representation (CAM), machine recipes, machine messages, ERP and MES interfaces, Supply Chain communications (PDX) Please also refer to the IPC-2501 document for introductory and explanatory information about this standard IPC-2501 also includes other elements that are required or used by this standard which dictates the required package structure and xml format for information exchange using any of the subsequent IPC-25xx standards such as this one This standard describes message transport mechanisms that are based upon an architecture whereby a single logical middleware server (the Message Broker) exchanges messages among Clients in a Domain The Product Data eXchange (PDX) standard (IPC-257x series), is intended for high-level supply chain communication of product definition, product build, and production reporting data IPC-T-50 Terms and Definitions for Interconnecting and Packaging Electronic Circuits IPC-2501 Definition for Web-Based Exchange of XML Data IPC 2511 Generic Computer Aided Manufacturing Descriptions for Printed Boards and Printed Board Assembly IPC-2541 Generic Requirements for Electronics Manufacturing Shop-Floor Equipment Communication Messages (CAMX) IPC-2547 Sectional Requirements for Shop-Floor Equipment Communication Messages (CAMX) for Printed Circuit Board Test, Inspection and Rework IPC-2571 Generic Requirements for Electronics Manufacturing Supply Chain Communication – Product Data eXchange (PDX) IPC-2576 Sectional Requirements for Electronics Manufacturing Supply Chain Communication of As-Built Product Data - Product Data eXchange (PDX) IPC-2577 Draft document for consensus vote only February 2005 Appendix A – Recommended Codes and Values All - Recommend values and codes presented below are taken out of the RosettaNet PIP 7C6 Release 01 document See www.rosettanet.org GlobalPartnerRoleClassificationCode Entity Instances Account Supplier Account User Anonymous Buyer Appointment Provider Authorized Service Provider Authorizer Buyer Catalog Distributor Catalog Producer Change Requester Change Review Forum Claim Requester Consignee Credit Provider Credit Reference Requester Customer Customer Manager Decision Stakeholder Delivery Appointment Provider Delivery Appointment Requester Demand Creator Failure Report Administrator Financing Processor Forecast Owner Forecast Recipient Forecast Reply Recipient Description Any trading partner that buys or sells products/services from customers and/or vendors Any trading partner that requires an account to buy or sell products/services A requestor of information that chooses to remain anonymous The stakeholder(s) in the shipment delivery activity The Service Provider authorized by an OEM to perform service on a unit The partner role that provides product authorization, from a product owner or manufacturer, for a reselling organization to resell a product An employee or organization that buys products for a partner type in the supply chain The partner role that distributes catalog information to catalog producers and buyers The partner role that produces catalog information for a partner type in the supply chain A party who has an interest in requesting a review of a possible change to the component The requester may be any party including customers and suppliers A party who has responsibility for the review of Engineering Change Requests and the drafting and review of Engineering Change Orders The Change Review Forum is assumed to be at the company that has responsibility for the engineering aspects of the component affected by the change The owner of the shipments who is responsible for the intact delivery The receiver of the shipment This partner role is responsible for providing credit information about potential customers This partner role is responsible for requesting credit information about potential customers This partner role creates a demand for a product or service This partner role manages the relationship with the business customers The party (such as suppliers, customers and others) who is responsible for the review and approval of the Engineering Change Approval Request The stakeholders may be from multiple organizations A party that receives a request for a change to a previously scheduled delivery appointment A party that requests a change to a previously scheduled delivery appointment The partner role that identifies the opportunity, submits design registration, provides engineering support to advance the opportunity towards design win, and generates revenue by satisfying customer demand for a product An employee or organizational entity that receives and processes PIP Failure Notifications The organization that processes the request for financing The party that creates a sales or order forecast and is ultimately responsible for it The party that receives a sales or order forecast The party that receives a forecast reply The Recipient can be the original forecast owner or other forecast partner (Please refer to the GlobalPartnerClassificationCode) IPC-2577 Draft document for consensus vote only Implementation Plan Creator Initiator In-transit Information User Invoice Provider Invoice Receiver Invoice Reject Provider Invoice Reject Receiver Marketing Activity Information User Marketing Activity Initiator Payee Payer PIP Failure Notifier Product Distributor Product Information Distributor Product Information Subscriber Product Information User Product Provider Product Supplier Quality Data Provider Quality Data User Receiver Responder Return Provider Return Receiver Return Requester Sales Facilitator Sales Lead Originator Sales Lead Processor Sales Marketing Claim Processor Sales Marketing Claimant Sales Marketing Program Reimbursement Recipient Sales Marketing Program Reimburser Seller Shipment Information User Shipment Requester February 2005 The partner role that creates, maintains and manages an implementation plan associated with an Engineering Change Order The party that starts the data exchange The party who receives shipment status information The organization that generates the invoice The organization being invoiced The organization that rejects an invoice The organization being issued an Invoice Reject Notification The party who uses information about Marketing Activities This party might include distributors, and retail operations The partner role that distributes information about marketing activities being sponsored by the organization The party receiving a payment The party issuing a payment An organizational process that automatically notifies the appropriate Failure Report Administrator of a PIP process failure The party authorized by a Product Supplier to purchase goods and services from the Product Supplier and resell to customers The partner role that distributes new product information to product information users and buyers The business partner that subscribes to product information from other business partners The partner role that uses product information to create or update enterprise systems and online promotion systems such as electronic catalog systems The partner role that creates a differentiated product, owns the registration process and creates a list of eligible products for use in design registration This partner role supplies product to customers in the supply chain The party responsible for sending the Repair Quality Data The Provider, through various means, learns of product or product component defect(s) The party who receives the repair and/or test data The User analyzes the data and incorporates findings into its business model The intended recipient of products or business information The Receiver may verify receipt if prescribed The party that replies to the initiators message The party responsible for authorizing and/or processing the return A third-party or warehousing operation responsible for receiving returns, inspecting the package contents and comparing to the issued RMA to assure the contents are what was authorized on the RMA Any party wishing to return a product This role could be played by a large end-user such as the Government Services Administration (GSA), a distributor, or a reseller This partner role facilitates the sale of product between partners in the supply chain The party assigning a sales lead to another party The party who receives the sales lead This party is responsible for accepting or rejecting the lead, and if accepted, reports the status of the lead The partner role that processes the claim and/or remits compensation to the Sales Marketing Claimant The partner role that requests reimbursement from a Sales Marketing Claim Processor The partner role that receives status on a previously submitted sales marketing claim, or who receives reimbursement without submitting a claim The partner role that is currently processing a sales marketing claim, (or providing a payment without a claim submitted) and who provides information on the status of the claim processing An organization that sells products to partners in the supply chain The party who receives shipment status information The party requesting transportation services IPC-2577 Draft document for consensus vote only Shipment Controller The party who is authorized to make decisions regarding a shipment while in-transit The party who relinquishes (assigns) a shipment to a transport service provider The party that may architect, configure, engineer, sell, or determine the fulfillment of the configured solution to partners in the supply chain This party that creates a demand for a product or service, or has contracted with a Solution Provider for the manufacture or fulfillment of a product(s) The partner role that creates or passes on manufacturing specifications This may be a Solution Provider, an OEM who is sub-contracting manufacturing tasks like fabrication or assembly, or another party The partner role that uses a manufacturing specification This might be a sub-contract assembler or fabricator The party that is required to implement an Engineering Change Order The Stakeholder may include all levels of suppliers, customers or other parties The Stakeholder may represent multiple organizations The Stakeholder may draft and/or be responsible for completing tasks in an implementation plan The functional partner role, that could be a Product Provider, that creates a differentiated product, owns the registration process and creates a list of eligible products, or who is responsible for identifying the opportunity (that is, it could be a Demand Creator) The organizational partner role, that could be a Product Provider, that creates a differentiated product, owns the registration process and creates a list of eligible products, or who is responsible for identifying the opportunity (that is, it could be a Demand Creator) This partner role supplies product to customers in the supply chain The stakeholder(s) in the tendering activity The party that provides transportation services for a Shipment Requester The provider who honors the warranty terms and reimburses the Authorized Service Provider for a service event performed under the terms of the warranty Shipper Solution Provider Solution Requester Specification Provider Specification User Stakeholder Status Requester Status Responder Supplier Tender Information User Transport Service Provider Warranty Provider GlobalSupplyChainCode Entity Instances Electronic Components Information Technology Semiconductor Manufacturing GlobalPartnerClassificationCode Entity Instances Broker Carrier Contract Manufacturer Customs Broker Distribution Center Distributor End User End User Government Financier Freight Forwarder Manufacturer Original Equipment Manufacturer Reseller Retailer Service Provider Shopper Warehouser February 2005 Description The electronic components supply chain The information technology supply chain The semiconductor manufacturing supply chain Description Representative of a third party Product carrier for transporting goods in supply chain The party responsible for the services rendered Product customs broker in supply chain Product distributor in supply chain Product distributor in supply chain Product end user in supply chain End user government Financial service provider in supply chain Product freight forwarder for transporting goods in supply chain Product manufacturer in supply chain Product manufacturer of original equipment in the supply chain The party who buys goods from a manufacturer and resells them to customers unchanged Product retailer in supply chain A provider of services such as repair, diagnoses, maintenance, installation or removal of a unit Product shopper in supply chain Product warehouser in supply chain IPC-2577 GlobalDocumentFunctionCode Constraint Entity Instances Request Response Draft document for consensus vote only Description Only GlobalDocumentFunctionCode equal to "Request" is allowed The business document is a request for a business action to be performed by a partner The business document is a response to a requesting partner GlobalGeographicRegionCode Entity Instances Global GlobalDocumentReferenceTypeCode Entity Instances ASP Claim ASP Part Return ASP Part Order ASP Requisition Commercial Invoice Contract Delivery Note Drawing # Invoice Master Event Number OEM Claim OEM Part Order OEM Part Return Purchase Order Purchase Order IN Purchase Order OUT Quote Requisition RMA - Returned Material Authorization Sales Order Serial Number Spec # Warranty Claim Waybill Work Order GlobalProductUnitOfMeasureCode Entity Instances 10 Kilogram Drum 10,000 Gallon Tankcar 100 Board Feet 100 Pound Drum 1000-pack 100-Pack 10-pack 115 Kilogram Drum 15 Kilogram Drum 20 Foot Container 20,000 Gallon Tankcar 20-Pack 25 Kilogram Bulk Bag 300 Kilogram Bulk Bag 40 Foot Container 50 Pound Bag 500 Kilogram Bulk Bag 50-pack 55 Gallon Drum February 2005 Description All countries Description The unique identifier assigned by the ASP for a warranty claim The unique identifier assigned by the ASP for a part return The unique identifier assigned by the ASP for a part order The unique identifier assigned by the ASP to reference a work order The unique identifier assigned by the OEM for a warranty claim The unique identifier assigned by the OEM for a part order The unique identifier assigned by the OEM for a part return Denotes a warranty claim Description IPC-2577 Draft document for consensus vote only Acre Actual Pounds Aluminum Pounds Only Ampere Bag Bale Ball Band Bar Barrel Barrel, Imperial Barrels Per Day Barrels Per Minute Base Box Base Weight Basket Batch Batt Batting Pound Beam Becquerel/kilogram Belt Billet Bin Block Board Board Feet Bolt Bottle Box British Thermal Unit (BTU) British Thermal Units (BTUs) Per Cubic Foot British Thermal Units (BTUs) Per Pound Bucket Bulk Bulk Car Load Bulk Pack Bundle Bunks Bushel Bushel, Dry Imperial Calorie Can Candela Canister Car Carat Carboy Card Carload Carton Cartridge Case Cask Cassette Catchweight Cell Centiliter Centimeter Centipoise (CPS) Chains (Land Survey) Chest Coil Coil Group Composite Product Pounds (Total Weight) February 2005 IPC-2577 Draft document for consensus vote only Cone Connector Container Cover Crate Cubic centimeter Cubic centimeter/second Cubic Foot Cubic inch Cubic yard Cubicmeter Cup Cycles Cylinder Day Deal Decimeter Degree Celsius Degree Fahrenheit Dep Factor Die Disk (Disc) Dispenser Display Dozen Dram Drum Dry Pounds Each Electrical Capacitance Fluid Ounce Fluid Ounce (Imperial) Fluid Ounce US Foot Fuel Usage (Gallons) Gage Systems Gallon Gigajoules Gill (Imperial) Grain Gram Gram/Cubic Centimeter Gram/square meter Grams Per 100 Centimeters Grams Per 100 Grams Grams Per Cubic Centimeter Grams Per Kilogram Grams Per Liter Grams Per Milliliter Grams Per Square Centimeter Grams Per Square Meter Great Gross (Dozen Gross) Gross Gross Barrels Gross Gallons Gross Kilogram Gross Ton Gross Yard Group Half Gallon Half Hour Half Liter Hank Heat lots Hectare February 2005 IPC-2577 Draft document for consensus vote only Hectoliter Hectopascal Hertz Hour Hours Hundred Boxes Hundred Count Hundred Sheets Hundredth of a Carat Imperial Gallons Inch Jar Joint Joule Keg Kelvin Kiloampere Kilobecquerel/Kilogram Kilogram Kilogram per cubic meter Kilogram/Kilogram Kilogram/square meter Kilogramm pro Sekunde Kilohertz Kilojoule Kilometer Kilometer/hour Kiloohm Kilovolt Kilowatt Kilowatt-hour Kit Kubikdezimeter Kubikmeter pro Sekunde Lifts Link Liquid Pounds Liter Load Lot Lug Mat Megagram Megagrams Per Hour Megahertz Megapascal Megawatt Meter Meter pro Quadratsekunde Meters per second Micrograms Per Cubic Meter Micrometer Microsecond Mikrogram/cubic meter Mile Milliampere Millibar Milligram/cubic meter Milligram/kilogram Milligram/Liter Milligrams Per Cubic Meter Milligrams Per Square Meter Millijoule Milliliter Millimeter February 2005 IPC-2577 Millimeter H20 Millimol Millimol/kilogram Million BTU's Millipascal seconds Millisecond Millitesla Millivolt Milliwatt Minute Miter Mol Mol/kilogram Month Multichip Nanometer Nanosecond Net Barrels Net Gallons Net Imperial Gallons Net Liters Newton Ohm One One Thousand Pieces Ounce Pack (PAK) Package Packet Pad Pail Pair Pallet Pallet (Lift) Pallet/Unit Load Pallete Panel Parcel Parts per billion (US) Parts per million Pascal Pascal second Pennyweight Per Hundred Pieces Percent Percent Per 1000 Hours Percent Weight Percentage Piece Pint - US liquid Pint U.S Dry Plate Pound Pounds Per 1000 Square Feet Pounds Per Foot Pounds Per Gallon Pounds Per Piece of Product Pounds Per Pound of Product Pounds Per Thousand Quart - US liquid Rack Ream of 500 Sheets Reel Ring Rod Draft document for consensus vote only February 2005 When or more dies (chips) are merged into one package IPC-2577 Roll Sack Second Set SET Sheet Sheet-Metric measure Shipment Shot Skein Skid Sleeve Slip Sheet Spool Square Square foot Square inch Square kilometer Square meter Square meter/second Square mile Square millimeter Square Yard Statute Mile Stick Strip Super Bulk Bag Tablet Tank Tank Truck Tesla Thousand Ton Tonne Torr Tote Track Foot Trailer Train Tray Troy Troy OZ Truckload Tube Unitless Unit of Measure US gallon US pound US ton Vial Volt Wafer Watt Week WF Wrap Yard Year Draft document for consensus vote only Mask Set (SET) Wafer (WF) February 2005 IPC-2577 Draft document for consensus vote only GlobalQualityDispositionCode Entity Instances Finished Goods Inventory - New Finished Goods Inventory - Repaired/Updated Manufacturing Analysis NFF NTF Process Scrapped Received Receiving Scrapped Repair Analysis Repaired Return to Manufacturer Shipped February 2005 lines 46,121 Indicates that the quality data being communicated is associated with a product that has completed the manufacturing process and is ready to be shipped This disposition could also be used within the 7C6 PIP in conjunction with Product Quantity to communicate inventory levels of manufactured material in inventory Indicates that the quality data being communicated is associated with a product that has completed the repair process and is ready to be shipped This disposition could also be used within the 7C6 PIP in conjunction with Product Quantity to communicate inventory levels of material in inventory that is not “new” but is ready to be shipped Indicates that the quality data being communicated is associated with a product that has NOT completed the manufacturing process but data is being provided because of an engineering request or checkpoint No failure found No trouble found Indicates that the quality data being communicated is associated with a product that has NOT completed the Repair/Update process but data is being provided because of an engineering request or checkpoint Indicates that the quality data being communicated is associated with a product that has completed the manufacturing and/or repair/update process and has been shipped Updated GlobalFailureTypeCode Entity Instances Primary Failure Secondary Failure GlobalRepairTypeCode Entity Instances Primary Repair Secondary Repair GlobalAttachmentDescriptionCode Entity Instances Assembly drawings Assembly/fabrication instructions Block diagrams Blueprints BOM CAD information Logistics Quality data Sample plan Schematics Test instructions GlobalMimeTypeQualifierCode Entity Instances application/activemessage application/andrew-inset Description The failure deemed to be "most significant" by the determining source A failure mechanism that contributes to the failure analysis process but is not deemed to be the primary reason for failure Description The repair code related to the primary failure mechanism for the product or component The repair code related to the secondary failure mechanism for the product or component Description Bill of Material Computer Aided Design Information For example: packaging, carrier requirements, etc Yield data Quantity of samples in a sample plan Description 10 IPC-2577 Draft document for consensus vote only application/applefile application/atomicmail application/batch-SMTP application/cals-1840 application/commonground application/cybercash application/dca-rft application/dec-dx application/EDI-Consent application/EDIFACT application/EDI-X12 application/eshop application/http application/hyperstudio application/iges application/index application/index.cmd application/index.obj application/index.response application/index.vnd application/ipp application/mac-binhex40 application/macwriteii application/marc application/mathematica application/msword application/news-message-id application/news-transmission application/ocsp-request application/ocsp-response application/octet-stream application/oda application/pdf application/pgp-encrypted application/pgp-keys application/pgp-signature application/pkcs10 application/pkcs7-mime application/pkcs7-signature application/pkix-cert application/pkixcmp application/pkix-crl application/postscript application/prs.alvestrand.titrax-sheet application/prs.cww application/prs.nprend application/remote-printing application/riscos application/rtf application/sdp application/set-payment application/set-payment-initiation application/set-registration application/set-registration-initiation application/sgml application/sgml-open-catalog application/slate application/vemmi application/vnd.$commerce_battelle application/vnd.3M.Post-it-Notes application/vnd.accpac.simply.aso application/vnd.accpac.simply.imp application/vnd.acucobol application/vnd.anser-web-certificate-issue-initiation application/vnd.anser-web-funds-transfer-initiation 11 February 2005 IPC-2577 Draft document for consensus vote only application/vnd.audiograph application/vnd.businessobjects application/vnd.claymore application/vnd.commonspace application/vnd.comsocaller application/vnd.cups-postscript application/vnd.cups-raster application/vnd.cups-raw application/vnd.cybank application/vnd.dna application/vnd.dpgraph application/vnd.dxr application/vnd.ecdis-update application/vnd.ecowin.chart application/vnd.ecowin.filerequest application/vnd.ecowin.fileupdate application/vnd.ecowin.series application/vnd.ecowin.seriesrequest application/vnd.ecowin.seriesupdate application/vnd.enliven application/vnd.epson.msf application/vnd.epson.quickanime application/vnd.epson.salt application/vnd.epson.ssf application/vnd.fdf application/vnd.ffsns application/vnd.FloGraphIt application/vnd.framemaker application/vnd.fujitsu.oasys application/vnd.fujitsu.oasys2 application/vnd.fujitsu.oasys3 application/vnd.fujitsu.oasysgp application/vnd.fujitsu.oasysprs application/vnd.fujixerox.docuworks application/vnd.fut-misnet application/vnd.hp-HPGL application/vnd.hp-hpid application/vnd.hp-hps application/vnd.hp-PCL application/vnd.hp-PCLXL application/vnd.ibm.MiniPay application/vnd.ibm.modcap application/vnd.intercon.formnet application/vnd.intertrust.digibox application/vnd.intertrust.nncp application/vnd.intu.qbo application/vnd.intu.qfx application/vnd.is-xpr application/vnd.japannet-directory-service application/vnd.japannet-jpnstore-wakeup application/vnd.japannet-payment-wakeup application/vnd.japannet-registration application/vnd.japannet-registration-wakeup application/vnd.japannet-setstore-wakeup application/vnd.japannet-verification application/vnd.japannet-verification-wakeup application/vnd.koan application/vnd.lotus-1-2-3 application/vnd.lotus-approach application/vnd.lotus-freelance application/vnd.lotus-notes application/vnd.lotus-organizer application/vnd.lotus-screencam application/vnd.lotus-wordpro application/vnd.mediastation.cdkey 12 February 2005 IPC-2577 Draft document for consensus vote only application/vnd.meridian-slingshot application/vnd.mif application/vnd.minisoft-hp3000-save application/vnd.mitsubishi.misty-guard.trustweb application/vnd.Mobius.DAF application/vnd.Mobius.DIS application/vnd.Mobius.MSL application/vnd.Mobius.PLC application/vnd.Mobius.TXF application/vnd.motorola.flexsuite application/vnd.motorola.flexsuite.adsi application/vnd.motorola.flexsuite.fis application/vnd.motorola.flexsuite.gotap application/vnd.motorola.flexsuite.kmr application/vnd.motorola.flexsuite.ttc application/vnd.motorola.flexsuite.wem application/vnd.ms-artgalry application/vnd.ms-asf application/vnd.ms-excel application/vnd.ms-powerpoint application/vnd.ms-project application/vnd.ms-tnef application/vnd.ms-works application/vnd.musician application/vnd.music-niff application/vnd.netfpx application/vnd.noblenet-directory application/vnd.noblenet-sealer application/vnd.noblenet-web application/vnd.novadigm.EDM application/vnd.novadigm.EDX application/vnd.novadigm.EXT application/vnd.osa.netdeploy application/vnd.pg.format application/vnd.pg.osasli application/vnd.powerbuilder6 application/vnd.powerbuilder6-s application/vnd.powerbuilder7 application/vnd.powerbuilder75 application/vnd.powerbuilder75-s application/vnd.powerbuilder7-s application/vnd.previewsystems.box application/vnd.publishare-delta-tree application/vnd.rapid application/vnd.seemail application/vnd.shana.informed.formdata application/vnd.shana.informed.formtemplate application/vnd.shana.informed.interchange application/vnd.shana.informed.package application/vnd.street-stream application/vnd.svd application/vnd.swiftview-ics application/vnd.triscape.mxs application/vnd.truedoc application/vnd.ufdl application/vnd.uplanet.alert application/vnd.uplanet.alert-wbxml application/vnd.uplanet.bearer-choice application/vnd.uplanet.bearer-choice-wbxml application/vnd.uplanet.cacheop application/vnd.uplanet.cacheop-wbmxl application/vnd.uplanet.channel application/vnd.uplanet.channel-wbxml application/vnd.uplanet.list application/vnd.uplanet.listcmd 13 February 2005 IPC-2577 Draft document for consensus vote only application/vnd.uplanet.listcmd-wbxml application/vnd.uplanet.list-wbxml application/vnd.uplanet.signal application/vnd.vcx application/vnd.visio application/vnd.wap.wbxml application/vnd.wap.wmlc application/vnd.wap.wmlscriptc application/vnd.webturbo application/vnd.wrq-hp3000-labelled application/vnd.wt.stf application/vnd.xara application/vnd.xfdl application/vnd.yellowriver-custom-menu+A91 application/wita application/wordperfect5.1 application/x400-bp application/xml application/zip audio/32kadpcm audio/basic audio/L16 audio/vnd.cns.anp1 audio/vnd.cns.inf1 audio/vnd.digital-winds audio/vnd.lucent.voice audio/vnd.nortel.vbk audio/vnd.octel.sbc audio/vnd.qcelp audio/vnd.rhetorex.32kadpcm audio/vnd.vmx.cvsd image/cgm image/g3fax image/gif image/ief image/jpeg image/naplps image/png image/prs.btif image/prs.pti image/tiff image/vnd.cns.inf2 image/vnd.dwg image/vnd.dxf image/vnd.fastbidsheet image/vnd.fpx image/vnd.mix image/vnd.net-fpx image/vnd.svf image/vnd.wap.wbmp image/vnd.xiff message/delivery-status message/disposition-notification message/external-body message/http message/news message/partial message/rfc822 message/s-http model/iges model/mesh model/vnd.dwf model/vnd.flatland.3dml model/vnd.gtw model/vrml 14 February 2005 IPC-2577 Draft document for consensus vote only multipart/alternative multipart/appledouble multipart/byteranges multipart/digest multipart/encrypted multipart/form-data multipart/header-set multipart/mixed multipart/parallel multipart/related multipart/report multipart/signed multipart/voice-message text/calendar text/css text/directory text/enriched text/html text/plain text/prs.lines.tag text/rfc822-headers text/richtext text/rtf text/sgml text/tab-separated-values text/uri-list text/vnd.abc text/vnd.fly text/vnd.fmi.flexstor text/vnd.in3d.3dml text/vnd.in3d.spot text/vnd.latex-z text/vnd.motorola.reflex text/vnd.wap.wml text/vnd.wap.wmlscript text/xml video/mpeg video/quicktime video/vnd.motorola.video video/vnd.motorola.videop video/vnd.vivo GlobalComponentRepairCode Entity Instances Repaired Replaced Updated 15 February 2005