PIP 4C1 VERSION 02.01: INVENTORY REPORT NOTIFICATION

PIP 4C1 Version 02.01: Inventory Report Notification

Release 1.01

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 4

Total Supplier Managed Inventory Transactions 4

service level agreement (performance time requirements) 4

related documents 4

Implementation 5

where to find PIPs 5

message guidelines 5

Total Supplier Managed Inventory Example 10

Receipt acknowledgement 14

Testing 15

Purpose 15

Production 15

Readiness 15

Support 15

Frequently Asked Questions 16

Glossary of Terms 17

Introduction

Purpose

This document is intended to provide to Intel Suppliers (Trading Partners) the information necessary to begin implementing RosettaNet PIP 4C1 VERSION 02.01: INVENTORY REPORT NOTIFICATION 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 4C1 for Intel and the Trading Partner include:

§  Reduces time spent calling and sending emails to determine inventory levels

§  Improves efficiency, increases data integrity and provides better visibility

§  Provide a standard means for communicating inventory levels between all trading partners

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.0
Service 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

Total Supplier Managed Inventory Transactions

The basic SIMI process uses shipment notices instead of purchase orders 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 takes place the supplier invoices against that purchase order.

This transaction is not a snapshot of all inventories available in Intel’s warehouse. This document notes the transactions, which occurred against the warehouse inventory for the previous day. Currently Intel has no intentions of sending a snapshot view of the warehouses because of the size and processing time required to generate this type of information.

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 4C1_MG_V02_01_00_InventoryReportNotification.htm (12-Nov-2001 00:00:00).

Intel Required Data in PIP
Intel Optional
Not required by Intel
Line# / Card / SIMI Line Item / Intel Description / Values
1 / 1 / fromRole.PartnerRoleDescription / Header
2 / 1 / |-- ContactInformation / Header
3 / 1 / | |-- contactName.FreeFormText / "Intel Corporation"
4 / 1 / | |-- EmailAddress / If this information is not available, it will appear as "Not Available". / If no available coming in from SIMI hardcode to "Not Available"
5 / 0..1 / | |-- facsimileNumber.CommunicationsNumber
6 / 1 / | |-- telephoneNumber.CommunicationsNumber / If no available coming in from SIMI hardcode to "999-999-9999"
7 / 1 / |-- GlobalPartnerRoleClassificationCode / "Inventory Information Provider"
8 / 1 / |-- PartnerDescription / Header
9 / 1 / | |-- BusinessDescription / Header
10 / 1 / | | |-- GlobalBusinessIdentifier / "047897855"
11 / 1 / | | |-- GlobalSupplyChainCode / "Electronic Components"
12 / 1 / | |-- GlobalPartnerClassificationCode / "End User"
13 / 1 / GlobalDocumentFunctionCode / "Request"
14 / 1 / InventoryReport / Header
15 / 1 / |-- inventoryReportDateTime.DateTimeStamp / The date when the transaction occurred. / DateTimeStamp
16 / 1..n / |-- InventoryReportLineItem / Header
17 / 0..n / | |-- DocumentReference / Header
18 / 0..1 / | | |-- DateTimeStamp / DateTimeStamp
19 / 1 / | | |-- GlobalDocumentReferenceTypeCode / "Contract"
20 / 0..1 / | | |-- LineItemNumber
21 / 1 / | | |-- ProprietaryDocumentIdentifier / "Not Available"
22 / 1 / | |-- GlobalProductUnitOfMeasureCode / Stock room UOM code value (NOT purchasing UOM) / Code identifying a product unit of measure
23 / 0..n / | |-- IntraCompanyTransfer / Header
24 / 0..1 / | | |-- inTransitFrom.PartnerDescription / Header
25 / 1 / | | | |-- BusinessDescription / Header
26 / 0..1 / | | | | |-- businessName.FreeFormText
27 / 0..1 / | | | | |-- GlobalBusinessIdentifier
28 / 0..n / | | | | |-- PartnerBusinessIdentification / Header
29 / 1 / | | | | | |-- ProprietaryBusinessIdentifier
30 / 1 / | | | | | |-- ProprietaryDomainIdentifier
31 / 0..1 / | | | | | |-- ProprietaryIdentifierAuthority
32 / 0..1 / | | | |-- ContactInformation / Header
33 / 1 / | | | | |-- contactName.FreeFormText
34 / 1 / | | | | |-- EmailAddress
35 / 0..1 / | | | | |-- facsimileNumber.CommunicationsNumber
36 / 1 / | | | | |-- telephoneNumber.CommunicationsNumber
37 / 1 / | | | |-- GlobalPartnerClassificationCode
38 / 1 / | | | |-- PhysicalLocation / Header
39 / 0..1 / | | | | |-- GlobalLocationIdentifier
40 / 0..n / | | | | |-- PartnerLocationIdentification / Header
41 / 1 / | | | | | |-- ProprietaryDomainIdentifier
42 / 0..1 / | | | | | |-- ProprietaryIdentifierAuthority
43 / 1 / | | | | | |-- ProprietaryLocationIdentifier
44 / 0..1 / | | | | |-- PhysicalAddress / Header
45 / 0..1 / | | | | | |-- addressLine1.FreeFormText
46 / 0..1 / | | | | | |-- addressLine2.FreeFormText
47 / 0..1 / | | | | | |-- addressLine3.FreeFormText
48 / 0..1 / | | | | | |-- cityName.FreeFormText
49 / 0..1 / | | | | | |-- GlobalCountryCode
50 / 0..1 / | | | | | |-- NationalPostalCode
51 / 0..1 / | | | | | |-- postOfficeBoxIdentifier.FreeFormText
52 / 0..1 / | | | | | |-- regionName.FreeFormText
53 / 1 / | | |-- inTransitQuantity.ProductQuantity
54 / 0..1 / | | |-- inTransitTo.PartnerDescription
55 / 1 / | | | |-- BusinessDescription / Header
56 / 0..1 / | | | | |-- businessName.FreeFormText
57 / 0..1 / | | | | |-- GlobalBusinessIdentifier
58 / 0..n / | | | | |-- PartnerBusinessIdentification / Header
59 / 1 / | | | | | |-- ProprietaryBusinessIdentifier
60 / 1 / | | | | | |-- ProprietaryDomainIdentifier
61 / 0..1 / | | | | | |-- ProprietaryIdentifierAuthority
62 / 0..1 / | | | | |-- businessName.FreeFormText
63 / 0..1 / | | | |-- ContactInformation / Header
64 / 1 / | | | | |-- contactName.FreeFormText
65 / 0..1 / | | | | |-- EmailAddress
66 / 0..1 / | | | | |-- facsimileNumber.CommunicationsNumber
67 / 1 / | | | | |-- telephoneNumber.CommunicationsNumber
68 / 1 / | | | |-- GlobalPartnerClassificationCode
69 / 1 / | | | |-- PhysicalLocation / Header
70 / 0..1 / | | | | |-- GlobalLocationIdentifier
71 / 0..n / | | | | |-- PartnerLocationIdentification
72 / 1 / | | | | | |-- ProprietaryDomainIdentifier
73 / 0..1 / | | | | | |-- ProprietaryIdentifierAuthority
74 / 1 / | | | | | |-- ProprietaryLocationIdentifier
75 / 0..1 / | | | | |-- PhysicalAddress / Header
76 / 0..1 / | | | | | |-- addressLine1.FreeFormText
77 / 0..1 / | | | | | |-- addressLine2.FreeFormText
78 / 0..1 / | | | | | |-- addressLine3.FreeFormText
79 / 0..1 / | | | | | |-- cityName.FreeFormText
80 / 0..1 / | | | | | |-- GlobalCountryCode
81 / 0..1 / | | | | | |-- NationalPostalCode
82 / 0..1 / | | | | | |-- postOfficeBoxIdentifier.FreeFormText
83 / 0..1 / | | | | | |-- regionName.FreeFormText
84 / 1 / | |-- inventoryLocation.PartnerDescription / Header - Intel Information
85 / 1 / | | |-- BusinessDescription / Header
86 / 0..1 / | | | |-- businessName.FreeFormText
87 / 0..1 / | | | |-- GlobalBusinessIdentifier
88 / 0..n / | | | |-- PartnerBusinessIdentification / This node will repeat once for the Vendor Id information if it is available form SIMI
89 / 1 / | | | | |-- ProprietaryBusinessIdentifier / 6 digit vendor ID value
90 / 1 / | | | | |-- ProprietaryDomainIdentifier / "Vendor ID"
91 / 0..1 / | | | | |-- ProprietaryIdentifierAuthority / "Intel"
92 / 0..1 / | | |-- ContactInformation / Header
93 / 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
94 / 1 / | | | |-- EmailAddress / If this information is not available, it will appear as "Not Available". / If this information is not available, it will appear as "Not Available".
95 / 0..1 / | | | |-- facsimileNumber.CommunicationsNumber
96 / 1 / | | | |-- telephoneNumber.CommunicationsNumber / If no available coming in from SIMI hardcode to "999-999-9999" / If no available coming in from SIMI hardcode to "999-999-9999"
97 / 1 / | | |-- GlobalPartnerClassificationCode / "End User"
98 / 1 / | | |-- PhysicalLocation / Header
99 / 0..1 / | | | |-- GlobalLocationIdentifier
100 / 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.
101 / 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