AP 233 Systems Engineering System-of-systems engineering requires

AP 233 Systems Engineering • System-of-systems engineering requires Request System • Greater collaboration and tool interoperability, and … Model Response • Using robust modeling techniques for describing systems architectures • AP 233 = ISO standard specifying communications pipeline between Systems Engineering tools and databases • Designed to be neutral vs DODAF, MODAF, Sys. ML, UML, IDEF, other SE tools, … which are more specific • As part of ISO STEP series, AP 233 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 – AP 233, like all new modular APs, is built from reusable information model “modules” for compatibility across application domains – AP 233 re-uses 70% of its data models from AP 239 PLCS • Associated module test & validation work is inherited • AP 233 module networks, test & validation work TBD

AP 233 Participants • Over the course of the project, numerous organizations have helped with AP 233

AP 233 - Sys. ML - OWL Languages with Common Semantics P R E S E N T A T I O N OWL Ontology Modeling Language Sys. ML Graphical Modeling Language STEP AP 233 Information Modeling Language R E P R E S E N T A T I O N

Context Diagram for Systems Engineering Standards Process Standards Architecture Frameworks Modeling Methods Modeling & Simulation Standards Interchange Standards EIA 632 ISO 15288 Do. DAF FEAF HP Zachman FW SADT UML/Sys. ML IEEE 1220 Modeling MOF/XMI Mo. DAF OOSE IDEF 0 CMMI * Other HLA Other Simulation STEP/AP-233 Other CADM This shows only one thread through these standards, others are necessary as well. Implemented by Tools

ISO 10303, STandard for the Exchange of Product model data (STEP) STEP - http: //www. tc 184 -sc 4. org USPRO – https: //www. uspro. org Aircraft Product Model Data Exchange Standards Requirements/Concept Analysis Equipment Coverage • Power-transmission • Power-distribution • Power-generation • Electric Machinery • Electric Light and Heat • Control Systems Electrotechnica l Systems • Buildings • Plants • Transportatio n Systems Data Supporting • Terminals and Interfaces • Functional Decomposition AP 233, Systems engineering data representation Shape Associated Finite Element Analysis (FEA) Analysis results material properties AP 209: 2001, Composite and metal structural analysis and related design Lifecycle Support Components Assemblies Work activities and resources • define • justify • approve • schedule • feedback of Product • 3 D Cabling and Harnesses • Cable Tracks and Mounting Instructions Electrotechnical Plant • Plant, e. g. , Automobile • Unit, e. g. , Engine Control System • Subunit, e. g. , Ignition System Conformity to the concept of a system System definition data and configuration control Requirements, requirement analysis, and functional allocation Functional, functional analysis, and functional behaviour Physical architecture and synthesis Trade studies for decision support Manufacturing Detailed Design/Bo. M Geometry Dimensions Tolerances Inspection processes AP 212: 2001, Electrotechnical design and installation Physical layout of the circuit card assembly Description of logical connections among the functional objects Packaged parts Physical interconnections Configuration management Parameters for parts and functional objects AP 219, Dimensional inspection Machining features Assembly informatio n Explicit geometry Tolerances Edition 3 in process to add gear features Edition 2 in process AP 210: 2001, Electronic assembly, interconnect, and packaging Design Analysis Manufacturing Support Related Standards All six pumps are the identical component in the library. When they are placed in the product model additional information is provided about the specific instance. Attribute Edition 2 Tolerances Construction history Colors Layers AP 203, Configuration Controlled 3 D designs of mechanical parts and assemblies FW LT Pump (Spare) FW HT Pump (Spare) Value Equipment: Pump Type: Vertical Centrifugal Casing: Cast Iron Impeller: Bronze Shaft: Stainless Mfg: Allweiler Marine Q: 200 m 3/h Ps bar 3 bar RPM: 1750 Power: 23 kw TMAX 250 ISO 13584 (Parts Library Exchange) AP 232: 2002, Technical data packaging: core information and exchange Make or buy Macro process planning AP 224: 2001, Mechanical product definition data for process planning using machining features Configuration controlled exchanges between Product Data Management (PDM) systems Links multiple formats Configuration Management of Product Structure Versioning and Change Tracking Bill of Materials Support • facilities • personnel • equipment • diagnostic s Administration Planning Execution Archiving Components Assemblies Cross Process Utility Configuration Operating • design requirements states • design configuration Behavior • as-built Usage • as-maintained Geometry Dimensions Material Mirco process planning Automated NC generation Mechanical parts machining • milling • turning • electro discharge machining Sheet metal bending Pipe bending AP 238, Computer numerical controllers Components Assemblies Geometry Dimensions Material Maco process planning • machinin g • fabricatio n Mechanical parts Structural steel Sheet metal bending Pipe bending AP 240, Process plans for machined products AP 239, Product lifecycle support

ISO 10303, STandard for the Exchange of Product model data (STEP) TC 184/SC 4/WG 3/T 23 Ship Team Standards Conformity to the concept of a system System definition data and configuration control Requirements, requirement analysis, and functional allocation Functional, functional analysis, and functional behaviour Physical architecture and synthesis AP 233 Systems engineering data representation Marine e-business Standards Association http: //www. emsa. org/ Request, define, justify, approve, schedule and capture feedback on work activities/resources. Product requirements and configuration asdesigned, as-built, as-maintained Feedback on product properties, operating states, behaviour and usage Define support opportunity, facilities, personnel, equipment, diagnostics and organizations AP 239 Product lifecycle support Ship Structural Envelope Surface, wireframe and offset point representations Design, Production and Operations lifecycles General characteristics Main dimensions Hull form geometry Major internal surfaces Hydrostatics Intact Stability tables Equipment/Subsystems Distributed Systems Connectivity • assembly • penetrations • ports Pipe Flow Analysis and Sizing Pipe Stress Analysis Connectivity • assembly • penetrations • ports All six pumps are the identical component in the library. When they are placed in the product model additional information is provided about the specific instance. Attribute Configuration Management of Product Structure Versioning and Change Tracking Bill of Materials AP 216: 2003, Ship moulded forms Stability • intact • damaged 2 -D and 3_-D Shape Representation • Diagrammatic Presentation • Solid Model Presentation • Interference Analysis AP 227: 2001, Plant spatial configuration – piping systems Connectivity • assembly • penetrations • ports Loading conditions Compartments • types • properties (shape, coatings, adjacency, access…. ) Navy/Industry Digital Data Exchange Standards Committee http: //www. usashipbuilding. com/niddesc. html http: //kstep. or. kr/ http: //www. jmsa. or. jp Configuration Management of Product Structure Versioning and Change Tracking Bill of Materials 2 -D and 3_-D Shape Representation • Diagrammatic Presentation • Solid Model Presentation • Interference Analysis AP 227 Edition 2: draft, Plant spatial configuration - HVAC systems FW LT Pump (Spare) FW HT Pump (Spare) Value Equipment: Pump Type: Vertical Centrifugal Casing: Cast Iron Impeller: Bronze Shaft: Stainless Mfg: Allweiler Marine Q: 200 m 3/h Ps bar 3 bar RPM: 1750 Power: 23 kw TMAX 250 ISO 13584 (Parts Library Exchange) Connectivity • assembly • penetrations • ports Zone Boundaries • Controlling Access • Design Authority • Cargo Stowage • Machinery Compartments • Crew Occupancy • Common Purpose Spaces Cargoes • assignment to compartments General Subdivision of a Ship • weight, into Spatially Bounded Regions • centre of gravity AP 215: IS, Ship arrangement Configuration Management of Product Structure Versioning and Change Tracking Bill of Materials 2 -D and 3_-D Shape Representation • Diagrammatic Presentation • Solid Model Presentation • Interference Analysis AP 227 Edition 2: draft, Plant spatial configuration - cable trays Configuration Management of Product Structure Versioning and Change Tracking Bill of Materials 2 -D and 3_-D Shape Representation • Diagrammatic Presentation • Solid Model Presentation • Interference Analysis AP 227 Edition 2: draft, Plant spatial configuration - mechanical systems ISO 15926 (Oil and Gas) • Ship Structural Envelope (hull forms, arrangement, structures) • Distributed Systems (electrical, piping, HVAC, cable ways, Production Design Data Configuration Management • Class Approval • Approval Relationship • Change Administration • Promotion Status Weight Description Structural Parts • Feature • Plate • Edge Content • Opening • Profile Endcut Technical Description General Characteristics Production Engineering Data Product Structure • Generic Product Structure • System • Space • Connectivity • Assembly Equipment Coverage • Power-transmission • Power-distribution • Power-generation • Electric Machinery • Electric Light and Heat • Control Systems Electrotechnica l Systems • Buildings • Plants • Transportatio n Systems Data Supporting • Terminals and Interfaces • Functional Decomposition of Product • 3 D Cabling and Harnesses • Cable Tracks and Mounting Instructions Electrotechnical Plant • Plant, e. g. , Automobile • Unit, e. g. , Engine Control System • Subunit, e. g. , Ignition System mechanical systems) • Mission Equipment/Subsystems (library and catalog parts) Hull Cross Section Geometric Representations • Wireframe • Complex Wireframe • Surfaces • Solids AP 218: IS, Ship structures AP 212: 2001, Electrotechnical design and installation Ship Product Model Data Exchange Information STEP - http: //www. tc 184 -sc 4. org USPRO – https: //www. uspro. org Ship STEP - http: //www. usashipbuilding. com/niddesc/t 23. html

PDES, Inc. Digital Enterprise Phase Envisioned Tool Environment Digital Enterprise Model Based Enterprise Systems Engineering MBe engineering Engineering Analysis Electromechanical • DFx • Printed Circuit Board Warpage • EDA-AP 210 Converters MBm manufacturing Digital Manufacturing MBs sustainability • Product Modeling • Process Modeling • Information Modeling Long Term Data Retention System Life Cycle Support Product Lifecycle Management Integration & Data Exchange Testing Information Standards: Infrastructure & Maintenance AP 203, AP 209, AP 210, AP 233, AP 239

Representation Using UML Pilots • Sys. ML-AP 233 Converter Demo – Eurostep: David Price & Phil Spiby – Artisan: Alan Moore – Presented at INCOSE July 2005 • Do. DAF/CADM-AP 233 Mapping – Eurostep: David Price – Presented at OSJTF So. S Architecture Modeling Meeting in 2006

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

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

Do. DAF Views B C System Functionality Description (SV-4) Systems Functionality Sequence and Timing Description (SV-10 a/b/c) Y X Systems Interface Description (SV-1) Activity to System Function (SV-5) Physical Schema SV-11 tem s Systems Evolution Description (SV-8) Standards Technology Forecast (TV-2) l ica Systems Communications Description (SV-2) Technical Architecture Profile (TV-1) chn Te System - System Matrix (SV-3) XY Z X Y Sys NODES TIME A T 1 T 2 T 3 Operational Systems Data Exchange Matrix (SV-6) Systems Performance Parameters Matrix (SV-7) Operational Concept Description (OV-1) Systems Technology Forecast (SV-9) Operational Activity Model (OV-5) • . . . Organizational Relationships Chart (OV-4) Node Connectivity Description (OV-2) • - Logical Data Model (OV-7) Information Exchange Matrix (OV-3) NODES TIME A T 1 T 2 T 3 B C Operational Activity Sequence and Timing Description (OV-6 a/b/c)

CADM-AP 233 Conclusions • Proved that AP 233 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 AP 233 itself by filling gaps identified during the project • Open source documentation, methods, tools, API

AP 233 and PLCS support full life cycle processes Request Database Response Database Taxonomy 233 PLCS AP 233 Data File References for added semantics Database

Ap 233 Enabling Capability Breakdown

DEX Architecture Business Dependant Domain Independent DEX may be subset of Business DEX collects 1: ? Capability Business process level may refer to functionality defined in Business Object represented by 1: ? Business information level represented_by 1: ? may be represented_by 0: ? Template contains 0: ? Business Template Implementation Level

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)

Future AP 233 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 IDEF 0 to Sys. ML activity diagram for UML • Do. DAF 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

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

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

Summary • AP 233 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 Sys. ML – enable INCOSE vision of Model-Based Systems Engineering

Ontology’s and Data Exchange 9 th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2 -4 May 2007 -

Holy grail of exchanging & sharing data (1) • Seamless and total interoperability – Across disciplines, organizations, system levels, modeling methodologies, tools • Flexible and precise formal open standards • Reliable and affordable • Affordable timely implementation and rigorously verified interfaces – Requires high quality public test suites with adequate coverage • Future proof and stable for long term archiving – May include open source middleware 9 th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2 -4 May 2007 -

Holy grail of exchanging & sharing data (2) • Scalability from small messages to full design/analysis/test/operation datasets • Pervasive and standardized configuration control / versioning • Minimal loss of information and common denominator between different (classes of) tools • Easy-to-use/easy-to-implement and spanning many disciplines • Support for white-box and black-box (degenerated/encrypted) data -Coming from genuine business needs and IPR protection 9 th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2 -4 May 2007 -

"Classical" Engineering Data Standards and Ontologies "Classical" engineering data exchange/sharing standards • Scope is usually a relatively specific and confined end-user problem • Terminology from software engineering (OO and/or ER) • Explicit, often detailed formal data model or just a file format • Reflection capabilities depend on implementation programming language Ontology's • Scope is often a "grand" data sharing problem for a complete industrial/scientific sector • Terminology shows scientific background, coming from philosophy, linguistics, artificial intelligence • Simple core data model allowing to state a large number of 'facts' • Built-in extensibility • Allows automated reasoning (inferencing) and has built-in reflection 9 th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2 -4 May 2007 -

Ontology spectrum -Source: Ph. D thesis Andries van Renssen- 9 th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2 -4 May 2007 -

Terminology 9 th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2 -4 May 2007 -

Layers in different standard families -9 th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2 -4 May 2007 -

IBM Software Group PLM Integrated PLM SOA Environment Project/Business Management (OEM &/or Suppliers) Engineers (OEM &/or Suppliers) Operations Quality Sales Service 3. Enterprise Collaboration - Portals and dashboards to Applications 2. Enterprise Process Management – Cross-application processes 1. Enterprise Integration - Management of PLM and Enterprise Information 32 Product Development Integration Framework IBM SOA Foundation Decision point—mandate system commonality (“rip & replace”) or integrated existing systems (“best of breed”) through SOA! PLM Application Systems Program and Portfolio Management Data Management Requirements Management Servers 32 Data Management Enterprise Application Systems Data Management Enterpris e PDM Mechanical Authoring Electrical Authoring Software ERP Analysis & Simulation EAM Other Enterprise Applications Storage 32

IBM Software Group PLM IBM: influencing and shaping open standards for PLM 1980 s -1990 s • Java and eb. XML • ISO STEP • OMG UML and XML • Open. GL • SQL • AIAG • IEEE • VRML • ANSI • Rosetta. Net 2000 - 2005 • Web Services / Interoperability • Eclipse to Open • BPEL • UDDI • WSBPEL • SOAP 33 • WS-TX • W 3 C XML • WS-TC • SOAP 4 J to Open • OASIS • Open Systems Over 160 business integration technology patents 2006 - 2007 • OMG PLM Services 1. 0 -3. 0 • STEP AP 214, 210, 219, 233, 239. . • Pro. STEP • PDES Inc • SASIG, Auto. SAR, JAMA other industry groups • IBM Enterprise Interoperability Center • IBM Services Oriented Architecture First Web Services Gateway First integrated private UDDI directory 33

IBM Software Group PLM Standards across PLM Lifecycle (Ministry of Defense) 34 34

IBM Software Group PLM Systems Engineering Standards Process Standards Ex: EAI 632, ISO 15288, CMMI, … Architecture Frameworks Ex: Do. DAF, Mo. DAF, … 35 Modeling Methods Ex: SADT, OOSE, … Implemented by tools Modeling & Simulation Standards Ex: UML/Sys. ML (modeling), HLA (Simulation) Interchange Standards Ex: MOF/XMI , STEP/AP 233, CADM, … 35

IBM Software Group PLM Standards for Model-Based Systems Engineering Data and Model Interchange AP 233 - The ISO standard for exchanging systems engineering data Do. DAF – Do. D Architecture Framework Defines standardized view of systems information CADM = Core Architecture Data Model 36 Sys. ML – Systems Modeling Language Standard modeling language and notation for systems engineers These standards are highly complementary. 36

IBM Software Group PLM Data and Model Interchange – AP 233 The industry is pursuing a neutral exchange format for systems engineering data because: • Systems are more complex (nr of interfaces and multi-discipline) • Tools are proliferating and they are more complex 37 • Multi-company collaboration is increasing • Data exchange between systems engineering applications/organizations is not simple 37

IBM Software Group PLM AP 233 Concept Model 38 38