Overcome the current problems in creating PIP business documents by creating a RosettaNet domain model (and sub- models) that will facilitate flexibility within governed boundaries. The domain model (and sub- models) should be architected for future extensibility (e.g., additional supply chains).

Problem symptoms this effort is attempting to solve:

• Inconsistencies affecting quality and potential interoperability across PIPs due to similar business concepts being defined and/or used differently.
• Inefficiencies in developing business documents due to re-invention of similar constructs.

Benefits sought:

• Ability to ascertain the validity (i.e., exist for valid business reasons) of variations (current and future)
• Establish the boundaries of acceptable variation.
• Ability to speed up map/gap for applicability of new supply chains.
• Increased clarity and awareness with respect to how PIP data content is used across a much wider variety of content domains (Supply Chain, Product, Business Process, Geography, B2B Business Model, etc.).