ISO STEP-AP233 Transition Development to Enablement

1. ISO STEP-AP233 Transition Development to Enablement Harold P. Frisch – NASA Emeritus, AP233 co-lead Charlie Stirk - CostVision Inc. With special thanks to David Price & Phil Spiby at Eurostep

3. AP233 Systems Engineering AP233 = ISO standard specifying communications pipeline between Systems Engineering tools and databases Designed to be neutral vs DODAF, MODAF, SysML, UML, IDEF, other SE tools, … which are more specific As part of ISO STEP series, AP233 links to standards with a vast scope AP stands for “Application Protocol” APs are very formal and strict – intended to prevent ambiguity in data exchange APs define the types of data to be exchanged and the structure of that data There are 40+ STEP Application Protocols AP233, like all new modular APs, is built from reusable information model “modules” for compatibility across application domains AP233 re-uses 70% of its data models from AP 239 PLCS Associated module test & validation work is inherited AP233 module networks, test & validation work TBD

4. AP233 Users Content Picture This is a representative picture of the contents of AP233 It is not the actual complex EXPRESS structure It shows a representative set of kinds of tools that can share data Among tools of the same type Between tools of different types where they store the same concepts Risk, Issues. And Authorization/Review tend to bridge between Project Management and Systems Requirements And Design This is a representative picture of the contents of AP233 It is not the actual complex EXPRESS structure It shows a representative set of kinds of tools that can share data Among tools of the same type Between tools of different types where they store the same concepts Risk, Issues. And Authorization/Review tend to bridge between Project Management and Systems Requirements And Design

5. AP233 Participants Over the course of the project, numerous organizations have helped with AP233

6. AP239 PLCS Relationship

7. AP209 Engineering Analysis Relationship

8. AP210 Electromechanical Relationship

9. Standards and SE data INCOSE - International Council on Systems Engineering Model-Based Systems Engineering Working Group Model-Based SE Semantic Dictionary and Concept Model Group work results in SysML/AP233 and alignment activity DoDAF - DoD Architecture Framework Defines standardized views of systems information CADM = Core Architecture Data Model Underlying data element model in XML SysML - from Object Management Group Provide a standard modeling language and notation for systems engineers AP233 Systems Engineering and Design Representation Defines a neutral information model for complex systems engineering structures

10. AP233 - SysML - OWLLanguages with Common Semantics

11. DoD and ISO 10303 STEP Kenneth Krieg, US Under Secretary of Defense for Acquisition, Technology and Logistics (DoD USD ATL) Memorandum “Standard for the Exchange of. Product Model Data (STEP) --- ISO 10303”, June 23, 2005 Recommends: Implementing an approach for managing digital product/technical data across DOD Ensure product model data meets ISO STEP requirements Adoption of ISO 10303 to enhance interoperability Ensure procuring activities plan, purchase and accept delivery of product/technical data only in digital formats specified by the guidance on contracts awarded

12. STEP for DOD Acquisition Cycle (Dr. Raj Iyer)

15. PDES, Inc. Digital Enterprise Phase

16. AP233 Enablement PhaseNo open technical issues Development team transitioning to a support and maintenance role.

17. What Does AP233 Enable? Program management Issue Activities Approvals Risk Probability & Consequence Source & Impact Contingency plans Project Organizational structure Project breakdown Schedule Work structure Management information resources

18. AP 233 Extendibility Through External_class references to External_class_library Adds semantics to basic schema concepts Can tailor to specific domain or business Can standardize the external libraries

20. Approaches to Implementation Representation AP233 in UML Generate XMI file from UML Transform XMI to STEP XML file (Part 28) Development of Data Exchange Sets (DEX) Like AP239 Product Life Cycle Support Standardization through OASIS Both use OWL for external classes

21. Representation Using UML Pilots SysML-AP233 Converter Demo Eurostep: David Price & Phil Spiby Artisan: Alan Moore Presented at INCOSE July 2005 DoDAF/CADM-AP233 Mapping Eurostep: David Price Presented at OSJTF SoS Architecture Modeling Meeting in 2006

22. SysML-AP233 Converter SysML concept scope Requirement-derivation, -decomposition System-decomposition, -satisfies requirement Defined AP233 in terms of widely used UML and XML representation rather than niche STEP/EXPRESS Implementation flow SysML tool exports XMI file XSLT translates XMI to AP233 XML file AP233 XML file import into Demonstrator application Demonstrator application available on www.ap233.org

23. SysML–AP233 Conclusions AP233 supports Core SysML Requirements concepts Core SysML System concepts AP233-specific extensions should broaden SysML coverage SysML/AP233 translator implementation can support industry needs, yet be simple and inexpensive if we: “stay out of the weeds” in STEP-land use widespread technology

24. DoDAF CADM/AP233 Project Purpose Evaluate feasibility of system architecture data exchange using emerging ISO AP233 Systems Engineering standard Deliverables Documented CADM View-AP233 mapping AP233 External Classes as OWL Classes Upgrades to AP233 itself to fill gaps found in mappings Proof-of-concept AP233-CADM converters for demos

25. Context Diagram for Systems Engineering Standards This shows only one thread through these standards, others are necessary as well.

27. Mapping Documentation Document as a Web site in the style of a programmers guide Audience Audience is software developers No previous knowledge of AP233 is required UML diagrams and XML Schemas used to explain how to write a converter Approach Develop standalone AP233 document that is independent of DoDAF/CADM mapping Develop document for each DoDAF View and “link” into the AP233 document Makes the AP233 documentation reusable for a similar project on SysML, MoDAF, etc.

28. Published Deliverable Web site documenting AP233 and CADM/AP233 mapping http://www.exff.org/ap233

29. Scripting API Implemented Application Programming Interface (API) in simple and accessible language Programmer must know concepts, attributes and relationships in AP233 Ruby API code generated from AP233 EXPRESS ARM Available as open source from www.exff.org

30. CADM-AP233 Conclusions Proved that AP233 can support Architecture Framework tool integration All DODAF views supported Mappings based on CADM Version 1.02 and AP 233 Working Draft 2 (with fixes) Improved AP233 itself by filling gaps identified during the project Open source documentation, methods, tools, API

31. AP 239 Product Life Cycle Support PLCS is STEP AP239 PLCS became ISO standard 9/01/2005 Funding and implementation led by NATO allies Many early AP233 models were incorporated into PLCS (e.g. Requirements) Extending through DEX Web Services Definition Language (WSDL) interface developed for PLCS (www.plcs-resources.org)

32. PLCS enables requirement management through life AP239 shares common modules with AP233 – Systems Engineering Aim is to support requirements trace from pre-design through to maintenance and disposal UK MOD has funded demonstration project for this capability with BAE Systems

33. PLCS provides full history to support optimization and change over time In the PLCS models it is assumed that any value supplied E.g. a property such as mean time to perform a task may have multiple values over time where each value could have been: supplied at different times by different people subject to approval subject to security classification associated to a justification/probability/risk This requirement has been recognised from the start of modelling Improve CM of support information by use of “single source” Assured Product and Support Information (APSI)

34. PLCS - Life Cycle PDM Capability (1) PDM Schema already supports automated exchange of Part id and properties Associated documents and files (incl. CAx) Product structure Product (and document) approval status This is already in production use by US Aerospace and Defence prime contractors (via AP203) German/Swedish/French Automotive sector (via AP214 cc6) Eurofighter Typhoon PDM partners .. A powerful and proven capability for Configuration Management of a complex product design

35. AP239 has added: Classification, supported by reference data libraries Product_as_individual (planned and realized) - UID Product breakdowns (system, physical, functional, zonal and hybrid) Text based requirements (from AP233) Extended property capability Interfaces Attachment_slot Message, Envelope (similar to ENGDAT) Information Rights … A powerful capability for Life Cycle Configuration Management of Assured Product and Support Information PLCS - Life Cycle PDM Capability (2)

36. AP233 and PLCS support full life cycle processes

37. PLCS - Reference data What is it? Values for attributes that are agreed and defined in advance of use E.g types of task, grades of people, types of products, types of document E.g. NATO Stock Number – classifications Why use it? Because it improves reliability and effectiveness of exchange Because it can be extended: To add to the scope of the standard To provide project specific functions Because it supports re-use of values from existing standards Idea proven in Oil and Gas industry

38. PLCS – Data Exchange Sets DEXs are: Subsets of the AP239 Information model Selected to meet a specific data exchange need Built from relevant modules Supported by Usage Guidance, population rules and Reference data Can be refined from other DEXs DEXs may be standardized at any level (work group, company, project, organization, national, international) DEXs enable Consistent implementation of AP239 Data consolidation through time

39. Current PLCS DEX developments Product as individual Product breakdown for support Maintenance plan Task set Operational feedback Fault states Work Package Definition Work Package Reporting Plus a range of developments which apply additional constraints and reference data based on generic DEX

41. Update Implementations Early pilots used AP 233 Working Draft 1 and Working Draft 2 Found gaps and fixed AP233 AP 233 now in Committee Draft (CD) on way to becoming Draft and then International Standard (IS) Prior mappings will need updating

42. Future AP233 Implementations Neutral format between tools of Same type e.g. Requirements Management UGS, Vitech, Rational, Telelogic, Cradle, etc. Different type e.g. Activity Modeling to SE Migrate IDEF0 to SysML activity diagram for UML DoDAF view independent of modeling approach Other SE domains Schedule, Program/Project, Risk, Issue, State Diagrams and Machines, Functional Flow Block Diagrams Link to downstream STEP design, analysis, manufacturing and PLCS domains

43. Vendor Support Early draft (2003) Vendor developed interfaces UGS Slate, 3SL Cradle User and independent consultant interfaces Telelogic DOORS, Rational Requisite Pro Current support SE Plug-fest (next talk)

44. Proposed High Level API Efficient Access: classes group objects that are create or destroyed simultaneously Business Objects: at level of SE domain concepts for mapping to software tools Web Services: functions of SE domain separate from data structures for integration

45. Summary AP233 is designed to support integration of Systems Engineering tools provide a “front end” to PLCS-based Support Engineering tools link with detailed design, PDM, analysis, etc. through other STEP protocols align with OMG SysML enable INCOSE vision of Model-Based Systems Engineering

46. Backup Slides

48. SysML - Systems Modelling Language The SysML Partners collaborated to define a modeling language for systems engineering applications, called Systems Modeling Language™ (SysML™). SysML customized UML 2.0 in order to support the specification, analysis, design, verification and validation of complex systems that include hardware and software components. The following are within the scope of SysML: Structure e.g., system hierarchies, interconnections Behavior e.g., function-based behaviors, state-based behaviors Properties e.g., parametric models, time variable attributes Requirements e.g., requirements hierarchies, traceability Verification e.g., test cases, verification results

49. Ap233 - Systems Engineering ISO 10303 is an International Standard for the computer-interpretable representation of product information and for the exchange of product data. The objective is to provide a neutral mechanism capable of describing products throughout their life cycle. This mechanism is suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases, and as a basis for archiving. The following are within the scope of ISO/CD-TS 10303-433: System behaviour System structure System modelling Decision support Requirements, analysis, trade studies Program and project management Verification and validation Risk management Issue management

51. AP 210 Requirements Traceability Color Key: Light Pink: Requirement decomposition Violet: Product decompositions Yellow: Requirement allocations Green: Network subsets in the scope of the referenced decomposition Dark Pink: Simulation model Library References to Simulation models from Design/Decomposition levels and from components omitted for clarity. Inclusion of decomposition relationships in library omitted for clarity. Some details of relationships omitted for clarity. Requirements may be allocated to a total design or to a component or between network subsets. Functional Decomposition forms a requirement for Assembly. Assembly forms a requirement for Interconnect. (these two are for the case where not all requirements are explicitly detailed using other mechanisms. AP 210 for instance does not fully map all the assembly details into a separate requirements tree to avoid data explosion.Color Key: Light Pink: Requirement decomposition Violet: Product decompositions Yellow: Requirement allocations Green: Network subsets in the scope of the referenced decomposition Dark Pink: Simulation model Library References to Simulation models from Design/Decomposition levels and from components omitted for clarity. Inclusion of decomposition relationships in library omitted for clarity. Some details of relationships omitted for clarity. Requirements may be allocated to a total design or to a component or between network subsets. Functional Decomposition forms a requirement for Assembly. Assembly forms a requirement for Interconnect. (these two are for the case where not all requirements are explicitly detailed using other mechanisms. AP 210 for instance does not fully map all the assembly details into a separate requirements tree to avoid data explosion.

52. DEX Architecture Overview

53. Business DEX Architecture

54. DEX Architecture

55. Current PLCS Implementations Visby Corvette Gripen pilot project Norwegian frigate Extending to other NDLO programmes Being promoted actively for JSF Eurostep Share-A-Space BAE Systems Land Systems Hagglunds UK MOD pilots for RAF LITS and Navy UMMS Logistics Coherence project US DoD ELITE project for UH-60 helicopter Extending to other service linked to UID Plans for HMMWV and Bradley

56. Deployments of Web Services Eurostep PLCS-PLM services implemented on top of Share-A-space SDK/JDKs provided for implementing clients Eurostep / Acando develop a SAP-adapter wrapping up SAP as PLCS web services and deployed inside the SAP-XI environment FMV PLCS-PLM services used with Share-A-space and Opus for spare optimization BAE Systems Hägglunds PLCS-PLM services implemented on top of in house PDM system Ericsson PLCS-PLM services + Share-A-space being used to integrate PDM systems. E.g. In house systems + multiple Windchill installations Motorola PLCS-PLM services + Share-A-space used to integrate DOORS / Requisite Pro requirements management systems Volvo Penta PLCS-PLM services used with Share-A-space and in house systems for producing spare parts lists VIVACE PLCS-PLM services used to integrate PDM data (Share-A-space ), engineering analysis and process flow software (Fiper)