Specification Development Effort Purpose

·     Companies are not able to utilize their RosettaNet infrastructure investments across all tiers of their trading partner base.  Maximum ROI is driven by broad utilization.

·     Length of time to bring up a trading partner on current RosettaNet gateway solutions is too extended.

·     Existing solutions have a high cost of entry and require significant IT resources to implement.

·     Small sized companies must deal with multiple applications and data formats from their trading partners and have to date, been unable to take advantage of RosettaNet standards.

·     As a result of these business issues, companies have to develop redundant B2B solutions for connecting to their trading partners.

Specification Development Effort Scope

The business focus of this program will be to convert some of the commonly used Forecast to Cash business process scenarios to XML Schema; validate and implement Trading Partner Implementation Requirements (TPIR) – PIP and TPIR – Presentation Format (PF).   The exact PIPs to be converted will be decided on by the committed Supply Chain implementers.

The program scope DOES NOT include plans to:

• Develop new Forecast to Cash standards
• Gather new requirements for existing standards (Note: Other working groups may affect the same PIPs).

Specification Development Expected Output

FOUN DATIONAL OUTPUT   

• Define  a structure, format and method for describing Trading Partner Implementation Requirements (TPIR-PIP) in a machine-readable standard ,    supported by the RosettaNet Integration Architecture, allowing multiple scenarios per PIP.
• Define   a  structure, format and method for creating a default Presentation Format (TPIR-PF) that reflects the TPIR-PIP constraints in a machine-readable standard that is supported by the RosettaNet Integration Architecture  

MILESTONE OUTPUT  

• Develop & Validate XML Schema PIPs (target ing roughly  7 Forecast To Cash PIPs)
• Validating Partners  will  utilize TPIR-PIP format/methods to create Trading Partner Implementation Requirements (TPIRs) for their target ed  PIPs/scenarios
• Specifications Requirement Document (SRD).
• Validate TPIR-PIP and TPIR-PF standards and prove interoperability with XML Schemas

Documentation and Implementation Support Expected Output

The supporting business and technical documentation to be developed by the program include:

            DOCUMENTATION

·          White Paper based on the business and technical investigation findings

·          TPIR-PIP specification and template  

·          TPIR-PF specification and template  

·          TPIR-PIP for each PIP and company  

·          TPIR-PF for each PIP and company

IMPLEMENTATION SUPPORT

·          Solution Providers  will integrate XML Schema  and  TPIR -PIP support into their solutions

·          Optionally, SP Validation Partners will utilize the TPIR-PF formats and methods to create presentation views for the trading partner specific implementation scenarios

Include any known relationships or dependencies to other working groups or RosettaNet specifications:

·         Multiple Messaging Services (MMS)

·         Messaging Control & Choreography

·         RosettaNet Connectivity Profile Service

·         Shipment Notification Management

·         Service Contract Management