PIP 4B3 Version 01.00: Notify Consumption
PIP 4B3 Version 01.00: Notify of Consumption
Release 1.02
Intended for Intel Supplier Trading Partners
Intel Corporation
https://eroom3.intel.com/eRoom/bet/2001Deployment
Revision Date: 11 November 2003
CopyrightÓ 2003 Intel Corporation
Intel Confidential
This document is valid 30 days from the latest revision.
Table of Contents
Introduction 3
Purpose 3
Audience 3
benefits 3
intel key contacts 3
technical requirements 3
processing requirements 5
Supplier Managed Inventory/Consignment 5
service level agreement (performance time requirements) 5
related documents 5
Implementation 6
where to find PIPs 6
message guidelines 6
TOTAL SUPPLIER MANAGED INVENTORY EXAMPLE 10
Receipt acknowledgement 24
Testing 27
Purpose 27
Production 27
Readiness 27
Support 28
Frequently Asked Questions 29
Glossary of Terms 30
Introduction
Purpose
This document is intended to provide to Intel Suppliers (Trading Partners) the information necessary to begin implementing RosettaNet PIP 4B3 (Notify of Consumption) with Intel. The topics covered are:
Introduction provides the reader with a basic understanding of the PIP implementation
Implementation is a complete outline of the process to be followed to put the document in production
Testing describes testing procedures and scenarios specific to this PIP
Production describes how to migrate from a test to a production environment and the support to follow
FREQUENTLY ASKED QUESTIONS provides answers to some common questions regarding this PIP
Glossary of Terms defines terms that are specific to this PIP
Audience
This document is intended for suppliers and Rosettanet provisioners. It contains many hyperlinks, data mappings with required fields and is best viewed in soft form. If you are reading a hard copy of this document, then please print this document on a color printer to better view the message guideline section.
benefits
Some specific benefits of implementing PIP 4B3 for Intel and the Trading Partner include:
· Provides trading partner visibility into Intel’s product consumption
· Provides data to enable trading partner to more efficiently manage its downstream supply chain
§ Improves efficiency, increases data integrity and provides better visibility for tracking purposes
intel key contacts
For each implementation, Intel assigns the following roles to participate in the engagement:
Trading Partner Provisioners – They assist the technical part of the implementation where they manage the implementation process between the supplier and Intel.
PIP Development Team – The Intel technical developers responsible for the developing the PIP for Intel. They provide answers regarding PIP specifics and facilitate testing and migration to production.
Business Advocate/Buyer/Commodity Manager – To represent the business processes involved in this PIP and to provide user acceptance to data sent and received.
It is highly recommended that the trading partner have complimentary representatives available to support this implementation, as well.
technical requirements
The following RosettaNet Infrastructure for transaction processing will be used for this PIP:
RNIF / Version 1.1 / Version 2.0Service Header / Version 1.1, build #22 / Version 2.0
Preamble / Version 1.1, build #22 / Version 2.0
PIP0A1 / Version 1.0 / Version 2.0
General Exception / Version 1.1, build #22 / Version 2.0
processing requirements
Supplier Managed Inventory/Consignment
The Consignment and Supplier Managed Inventory processes use consumption notices instead of purchase orders for invoicingrs but the monthly reconciliation process does have a purchase order involved. It is the equivalent of a blanket purchase order the site creates After the monthly reconciliation of the consumption report takes place the supplier invoices against the agreed upon consumption datathat purchase order.
service level agreement (performance time requirements)
This transaction is sent daily around midnight Pacific Time. One transaction will be sent for each site (i.e. one for New Mexico, one for Arizona, etc.). The transactions will reflect the previous day’s activity.
It should be noted that this transaction could be over 1MB in size. The trading partner should test that they can receive a file of this size.
The DTDs for the Receipt Acknowledgment and PIP 0A1 (Notification of Failure) can be found at www.rosettanet.org.
related documents
Intel provides documents to assist trading partners in establishing connectivity with Intel. For trading partners who prefer not to use the connectivity package provided free of charge by Intel, they should reference the following (most are available on supplier.intel.com or through your Trading Partner Provisioner):
Name / Document Description /Core Handbook / This guide is meant for first time RosettaNet implementation partners who need some background on RosettaNet prior to engaging.
Connectivity Guide / Basic Guide To Understanding Available Connectivity Options with Intel.
HTTPS Trading Partner Guidelines Revision / HTTPS Implementation Guide
HTTPS Trading Partner Information Sheet (it is also embedded with the HTTPS Implementation Guide) / HTTPS Data Exchange Sheet with specific information the Trading Partner needs from Intel and the information Intel needs from its Trading Partners to establish connectivity
RAPID Carrier Code to SCAC.xls / List of current RosettaNet accepted SCAC codes.
Implementation
where to find PIPs
For a list of PIPs by cluster and segment and/or to download a copy of PIP 3B2, please access the RosettaNet web site at www.rosettanet.org. Users are not required to be a member of RosettaNet or have an ID/password to download the PIPs.
message guidelines
Intel is currently implementing 4B3_MG_V01_00_00_NotifyOfConsumption.
Intel Required Data in PIPIntel Optional
Not required by Intel
Line# / Card / SIMI Line Item / Intel Description / Values
1 / 1 / ConsumptionNotice / Header
2 / 1 / |--consumptionGenerationDateTime.DateTimeStamp / Date timestamp when report was generated / DateTimeStamp
3 / 1..n / |--ConsumptionIdentifierReference / Header - This sectoin can repeat for different document types.
4 / 1 / ||--GlobalDocumentReferenceTypeCode / This defines the type of transaction that is being reported. / I.e."ASP PartOrder"
5 / 1 / ||--ProprietaryDocumentIdentifier / "Not Available"
6 / 1..n / |--PartnerProductConsumption / Header
7 / 1..n / ||--ConsumptionPartner / Header
8 / 1 / |||--GlobalPartnerReferenceTypeCode / "Used by"
9 / 1 / |||--PartnerDescription / Header
10 / 1 / ||||--BusinessDescription / Header
11 / 0..1 / |||||--businessName.FreeFormText
12 / 0..1 / |||||--businessWebSite.UniformResourceLocator
13 / 1 / |||||--GlobalBusinessIdentifier / Intel's DUNS / "047897855"
14 / 0..n / |||||--PartnerBusinessIdentification / Header - This node will repeat once for each node (24, 24A, 24B, 28) below if information comes in from SIMI backend in that node. If there is no/blank data coming in, corrosponding node will not be created in outbound PIP.
15 / 1 / ||||||--ProprietaryBusinessIdentifier / Value of TransactionId, TransactionLineId, WIINGsIssueId, BaseCode if coming in from SIMI
16 / 1 / ||||||--ProprietaryDomainIdentifier / This field will contain the values of SIMI TransactionId representing a WIINGs id (ie item adjustment id, or transfer id, customer return id, etc.) where several transactions can relate to the same id, TransactionLineId used only for issues, returns and adjustments, WIINGsIssueId which is autogenerated by WIINGs at the transaction level if available; it will also be used to indicate the Intel "Vendor Id" assigned to the supplier / "Transaction ID" for node 24
"Transaction Line ID" for node 24A
"WIINGs Issue ID" for node 24B
"Vendor ID" for node 28
17 / 0..1 / ||||||--ProprietaryIdentifierAuthority / "Intel"
18 / 0..1 / ||||--ContactInformation / Header
19 / 1 / |||||--contactName.FreeFormText / This will be the requestor's name. If the requestor's name (the Intel employee who requested the item from the stock room) is not available, then the creator name (the Intel employee who created the transation) will be seen here. / Free Form Text
20 / 0..1 / |||||--EmailAddress
21 / 0..1 / |||||--facsimileNumber.CommunicationsNumber
22 / 0..1 / |||||--telephoneNumber.CommunicationsNumber
23 / 1 / ||||--GlobalPartnerClassificationCode / "End User"
24 / 0..1 / ||||--PhysicalLocation / Header / Header Tags
25 / 0..1 / |||||--GlobalLocationIdentifier
26 / 0..n / |||||--PartnerLocationIdentification / Header - This node will repeat once for each node (17,18,27) below if information comes in from SIMI backend in that node. If there is no/blank data coming in, corrosponding node will not be created in outbound PIP.
27 / 1 / ||||||--ProprietaryDomainIdentifier / This field will be used to indicate the name of the machine where the part is used, the name of the manufacturing unit where the machine is using the part and the name of the stock room containing the part involved in the transaction. / "Machine Name" for node 17
"Factory Name" for node 18
"Stock Room" for node 27
28 / 0..1 / ||||||--ProprietaryIdentifierAuthority / "Intel"
29 / 1 / ||||||--ProprietaryLocationIdentifier / Value of MachineName, FactoryName, StockRoomName coming in from SIMI
30 / 0..1 / |||||--PhysicalAddress / Header
31 / 0..1 / ||||||--addressLine1.FreeFormText
32 / 0..1 / ||||||--addressLine2.FreeFormText
33 / 0..1 / ||||||--addressLine3.FreeFormText
34 / 0..1 / ||||||--cityName.FreeFormText
35 / 0..1 / ||||||--GlobalCountryCode
36 / 0..1 / ||||||--GlobalLocationIdentifier
37 / 0..1 / ||||||--NationalPostalCode
38 / 0..1 / ||||||--postOfficeBoxIdentifier.FreeFormText
39 / 0..1 / ||||||--regionName.FreeFormText
40 / 1..n / ||--ConsumptionProduct / Header
41 / 1 / |||--GlobalProductUnitOfMeasureCode / Stock room UOM code value (NOT purchasing UOM) / Code identifying a product unit of measure.
42 / 0..n / |||--InventoryProductQuantity / Header
43 / 1 / ||||--GlobalInventoryCode
44 / 1 / ||||--ProductQuantity
45 / 0..1 / |||--LineNumber
46 / 1 / |||--ProductIdentification / Header
47 / 0..1 / ||||--GlobalProductIdentifier
48 / 0..n / ||||--PartnerProductIdentification / Header - This node will repeate twice once for supplier part number and one for Intel part number if that information is available from SIMI
49 / 1 / |||||--GlobalPartnerClassificationCode / "End User" /"Manufacturer"/ "Original Equipment Manufacturer"
50 / 1 / |||||--ProprietaryProductIdentifier / Value of Intel part number when element 49 = "End User", supplier part number when element 49 = "Manufacturer" coming in from SIMI and for the serial number 49 = "Original Equipment Manufacturer"
51 / 0..1 / |||||--revisionIdentifier.FreeFormText / This element will contain the item description concatenated with the SIMI transaction type and the SIMI reason code, separated by a semicolon; Data available only if 49 is "End User" / "DESC:<IntelItemDescription>;<TransactionType>;<Reason Code>"
52 / 1..n / ||||--ProductConsumptionConfirmation / Header
53 / 1 / |||||--ConsumptionNoticeNumber / "Not Available"
54 / 1 / |||||--materialConsumptionDate.DateTimeStamp / Consumption date value / Date Time Stamp
55 / 1 / |||||--ProductQuantity / Product quantity value / A quantity specifying the number of product units.
56 / 0..1 / |||--unitPrice.FinancialAmount
57 / 1 / ||||--GlobalCurrencyCode / "USD"
58 / 1 / ||||--MonetaryAmount / Unit Price value
59 / 1 / fromRole.PartnerRoleDescription / Header
60 / 1 / |--ContactInformation / Header
61 / 1 / ||--contactName.FreeFormText / "Intel Corporation"
62 / 1 / ||--EmailAddress / If no available coming in from SIMI hardcode to "Not Available"
63 / 0..1 / ||--facsimileNumber.CommunicationsNumber
64 / 1 / ||--telephoneNumber.CommunicationsNumber / If no available coming in from SIMI hardcode to "999-999-9999" / Telephone Number
65 / 1 / |--GlobalPartnerRoleClassificationCode / "Consumption Notification Provider"
66 / 1 / |--PartnerDescription / Header
67 / 1 / ||--BusinessDescription / Header
68 / 1 / |||--GlobalBusinessIdentifier / "047897855"
69 / 1 / |||--GlobalSupplyChainCode / "Electronic Components"
70 / 1 / ||--GlobalPartnerClassificationCode / "End User"
71 / 1 / GlobalDocumentFunctionCode / "Request"
72 / 1 / thisDocumentGenerationDateTime.DateTimeStamp / document generation datetime value / Date Time Stamp
73 / 1 / thisDocumentIdentifier.ProprietaryDocumentIdentifier / document ID value / Unique identifier, i.e. a numeric value or alphanumeric value, for a business document.
74 / 1 / toRole.PartnerRoleDescription / Header - Supplier information
75 / 0..1 / |--ContactInformation / Header
76 / 1 / ||--contactName.FreeFormText
77 / 1 / ||--EmailAddress
78 / 0..1 / ||--facsimileNumber.CommunicationsNumber
79 / 1 / ||--telephoneNumber.CommunicationsNumber
80 / 1 / |--GlobalPartnerRoleClassificationCode / "Consumption Notification User"
81 / 1 / |--PartnerDescription / Header
82 / 1 / ||--BusinessDescription / Header
83 / 1 / |||--GlobalBusinessIdentifier / Supplier's DUNS number / Supplier to provide
84 / 1 / |||--GlobalSupplyChainCode / Supplier's Supply Chain Code / "Electronic Components"
85 / 1 / ||--GlobalPartnerClassificationCode / Supplier's Classification Code / "Manufacturer"
The following elements are required for Total Supplier Managed business model:
· This node will repeat once for each node (24, 24A, 24B, 28) below if information comes in from SIMI backend in that node. If there is no/blank data coming in, corrosponding node will not be created in outbound PIP.
14 0..n | | | | |-- PartnerBusinessIdentification
15 1 | | | | | |-- ProprietaryBusinessIdentifier = Value of TransactionId, TransactionLineId, WIINGsIssueId, BaseCode if coming in from SIMI
16 1 | | | | | |-- ProprietaryDomainIdentifier = This field will contain the values of SIMI TransactionId representing a WIINGs id (ie item adjustment id, or transfer id, customer return id, etc.) where several transactions can relate to the same id, TransactionLineId used only for issues, returns and adjustments, WIINGsIssueId which is autogenerated by WIINGs at the transaction level if available; it will also be used to indicate the Intel "Vendor Id" assigned to the supplier "Transaction ID" for node 24"Transaction Line ID" for node 24A"WIINGs Issue ID" for node 24B"Vendor ID" for node 28
17 0..1 | | | | | |-- ProprietaryIdentifierAuthority = "Intel"
· This node will repeat once for each node (17,18,27) below if information comes in from SIMI backend in that node. If there is no/blank data coming in, corrosponding node will not be created in outbound PIP.
26 0..n | | | | |-- PartnerLocationIdentification
27 1 | | | | | |-- ProprietaryDomainIdentifier This field will be used to indicate the name of the machine where the part is used, the name of the manufacturing unit where the machine is using the part and the name of the stock room containing the part involved in the transaction. "Machine Name" for node 17"Factory Name" for node 18"Stock Room" for node 27
28 0..1 | | | | | |-- ProprietaryIdentifierAuthority "Intel"
· This node will repeate twice once for supplier part number and one for Intel part number if that information is available from SIMI
48 0..n | | | |-- PartnerProductIdentification-
49 1 | | | | |-- GlobalPartnerClassificationCode = "End User","Manufacturer","Original Equipment Manufacturer"
50 1 | | | | |-- ProprietaryProductIdentifier = Value of Intel part number when element 49 = "End User", supplier part number when element 49 = "Manufacturer" coming in from SIMI and for the serial number 49 = "Original Equipment Manufacturer"
51 0..1 | | | | |-- revisionIdentifier.FreeFormText = This element will contain the item description concatenated with the SIMI transaction type and the SIMI reason code, separated by a semicolon; Data available only if 49 is "End User" "DESC:<IntelItemDescription>;<TransactionType>;<Reason Code>"