PPC Architecture reviews

1
PPC Architecture reviews

• Outline of scope
• Presentations of architectural issues
• Issue capture
• Discussion
• Conclusions and actions

2
Challenges for the future

• Continued building on the foundation
• industry implementation
• new structures for sharing
• new areas of application
• new representation technologies
• extension to libraries and reference data
• convergence with other business areas
• EXPLOITING OUR INVESTMENT IN INFORMATION

3
Scope

• Exploitation of SC4 models in OWL, UML and other
  Semantic Web
• Use of reference data - simple, hierarchical,
  extending the data model
• Consistent definition and use of reference data
• Facilitating ARM level implementations while
  preserving AIM level integration

4
Views on the architecture

• David Price
• Nils Sandsmark
• Magne Valen-Senstad
• David Leal
• Wolfgang Wilkes
• Lothar Klein/Tom Thurman
• Gerry Radack
• Dave Loffredo
• Keith Hunten
• Nigel Shaw

5
Requirements (1)

• SC4 work fits in a much larger picture
• Need to support multiple information viewpoints
• Need to talk to users in ARM terminology
• Growing need for agile information sharing across
  enterprises, through life, with audit trail
• Implementation based on standard business objects
  - exchange, Semantic Web
• Single information model for implementation, XML
  schema, Web services, OMG PLM services,EDA
• Extensibility

6
Requirements (2)

• Need to have consistent reference data with
  consistent terminology across SC4 standards,
  which can also be used beyond SC4
• Inferencing based on available structures
• Need to simplify and promote industry
  implementation
• Align deliverables to stakeholders
• Use of mainstream technologies

7
Issues (1)

• Need to define how SC4 standards fit together and
  interoperate in common architecture
• ? integration model
• equivalence of approaches
• SC4 work does not meet full requirements for
  enterprise integration - neither does anything
  else!
• Need to cooperate with other groups
• Need to support business object implementation
• ARM access to AIM structures
• Precise mapping
• Simplified implementation of common structures
• Services

8
Issues (2)

• Making our models available on the Semantic Web
  in useful blocks
• Separating out reference data from models
• Reference data published in OWL -
• use by STEP - external reference
• link to PLIB?
• consistent terminology
• relationship to external dictionaries eg eOTD
• PLIB dictionaries in OWL and other representation
• How to implement knowledge based approaches
• precise reference data and relationships

9
Issues (3)

• Update strategic plan
• Appropriate tracking of technology
• Test changes to architecture before deployment
• Align deliverables to market stakeholders
• Separate components such as ARMs?
• Network of related models, precisely related
• Opportunities to clean up basic model - change
  management issue
• Exploit software development methodologies

10
Standards

• Zachman Framework
• ISO 10746
• ISO 11179
• OMG MDA
• UML
• Emerging knowledge standards