Supplier Implementation of RosettaNet

Intel's Expectations of a Supplier for a RosettaNet Implementation

1. Provide technical resources
   • A RosettaNet implementation requires a technical team, or individual, consisting of mainly software developers, but could also include technical support personnel and technical coordinators.  
   • These resources would be responsible for:
     • Mapping the data elements into and out of their ERP systems.
     • Establishing the connectivity between Intel® and the supplier for transferring the data between the two companies.
     • PIP testing between the two companies
2. Provide System Development
   • Acquire all the necessary hardware and software required to successfully implement a RosettaNet PIP.  See next section for these requirements.
3. Provide Project Management
   • A RosettaNet implementation requires a project manager to coordinate and facilitate the implementation.  This individual usually has the title of e-Business Manager or Project Manager.
   • These resources would be responsible for:
     • Coordinating the supplier's RosettaNet Team.
     • Creating the supplier's RosettaNet timelines and driving towards those milestones.
     • The main Intel® contact for this implementation.
4. Attend the Intel® /Supplier RosettaNet meetings 
   • A RosettaNet implementation consists of several meetings throughout the duration of the project to discuss progress, issues, and any other topics.  The majority off these meetings will be facilitated by Intel® personnel. 
     • The first meeting is a RosettaNet Kick-off meeting to go over introductions, plans, and next steps.
     • The following meetings usually occur once a month until PIP testing begins. 
     • When testing begins, meetings move to once a week until the implementation is complete and the PIP is in production.  
5. Track to proposed Implementation timelines
   • The supplier's project manager is responsible for creating and tracking towards an implementation timeline.  This timeline should be aggressive, but at the same time, realistic.

Intel's Best Known Methods (BKMs) of our RosettaNet implementations

Intel has learned the following from our RosettaNet implementations:

• A RosettaNet implementation usually takes 3 months.
  • The first month or two is dedicated to ISV selection, hardware/software installation, and data mapping.
  • The last month is dedicated to PIP testing.
• There are many factors that can delay a RosettaNet implementation.
  • RosettaNet delaying the validation of the PIPs.
  • RosettaNet changing the DTD.
  • ISV responsiveness to changes in the DTD or supplier requirements.
• Before you engage in a RosettaNet implementation.
  • Understand your business model .
  • Understand the scope of the project