1 / 34

Enhancing System-of-Systems Engineering with AP233 Model System Response

AP233 is an ISO standard enabling communication between Systems Engineering tools. This robust model utilizes formal protocols to prevent data ambiguity and aids in system architecture design. Collaborative participants shape this standard for compatibility across domains.

edupont
Download Presentation

Enhancing System-of-Systems Engineering with AP233 Model System Response

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System-of-systems engineering requires • Greater collaboration and tool interoperability, and … • Using robust modeling techniques for describing systems architectures Request System Model Response 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

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

  3. AP233 - SysML - OWLLanguages with Common Semantics OWL Ontology Modeling Language REPRESENTAT ION PRESENTAT ION SysML Graphical Modeling Language STEP AP233 Information Modeling Language

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

  5. FW LT Pump FW LT Pump FW LT Pump (Spare) FW HT Pump FW HT Pump FW HT Pump (Spare) ISO 10303, STandard for the Exchange of Product model data (STEP) STEP - http://www.tc184-sc4.org USPRO – https://www.uspro.org Aircraft Product Model Data Exchange Standards Manufacturing Requirements/Concept Analysis Detailed Design/BoM Lifecycle Support • Equipment Coverage • Power-transmission • Power-distribution • Power-generation • Electric Machinery • Electric Light and Heat • Control Systems • Electrotechnical Systems • Buildings • Plants • Transportation Systems • Data Supporting • Terminals and Interfaces • Functional Decomposition of Product • 3D Cabling and Harnesses • Cable Tracks and Mounting Instructions Components Assemblies • Work activities and resources • define • justify • approve • schedule • feedback • Configuration • design requirements • design configuration • as-built • as-maintained Operating states Behavior Usage • Support • facilities • personnel • equipment • diagnostics • Electrotechnical Plant • Plant, e.g., Automobile • Unit, e.g., Engine Control System • Subunit, e.g., Ignition System Administration Planning Execution Archiving 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 Shape Associated Finite Element Analysis (FEA) Analysis results material properties Geometry Dimensions Tolerances Inspection processes AP209:2001, Composite and metal structural analysis and related design AP212:2001, Electrotechnical design and installation AP233, Systems engineering data representation AP219, Dimensional inspection AP239, Product lifecycle support Components Assemblies Machining features Assembly information Explicit geometry Tolerances 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 Make or buy Macro process planning Edition 3 in process to add gear features AP224:2001, Mechanical product definition data for process planning using machining features Edition 2 in process AP210:2001, Electronic assembly, interconnect, and packaging Configuration controlled exchanges between Product Data Management (PDM) systems Links multiple formats Geometry Dimensions Material Design Analysis Manufacturing Support Mirco process planning Automated NC generation Cross Process Utility Related Standards • Mechanical parts machining • milling • turning • electro discharge machining • Sheet metal bending • Pipe bending 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 Value Equipment: Pump Type: Vertical Centrifugal Casing: Cast Iron Impeller: Bronze Shaft: Stainless Mfg: Allweiler Marine Q: 200 m3/h Ps bar 3 bar RPM: 1750 Power: 23 kw TMAX 250 Configuration Management of Product Structure Versioning and Change Tracking Bill of Materials AP232:2002, Technical data packaging: core information and exchange AP232:2002, Technical data packaging: core information and exchange AP238, Computer numerical controllers Edition 2 Tolerances Construction history Colors Layers Components Assemblies Geometry Dimensions Material AP203, Configuration Controlled 3D designs of mechanical parts and assemblies • Maco process planning • machining • fabrication ISO 13584 (Parts Library Exchange) Mechanical parts Structural steel Sheet metal bending Pipe bending AP240, Process plans for machined products

  6. Weight Description FW LT Pump FW LT Pump FW LT Pump (Spare) FW HT Pump FW HT Pump FW HT Pump (Spare) Production Design Data 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 AP216:2003, Ship moulded forms 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 Request, define, justify, approve, schedule and capture feedback on work activities/resources. Product requirements and configuration as-designed, as-built, as-maintained Feedback on product properties, operating states, behaviour and usage Define support opportunity, facilities, personnel, equipment, diagnostics and organizations AP 233 Systems engineering data representation Navy/Industry Digital Data Exchange Standards Committee http://www.usashipbuilding.com/niddesc/niddesc.html AP 239 Product lifecycle support http://kstep.or.kr/ Marine e-business Standards Association http://www.emsa.org/ http://www.jmsa.or.jp Ship Structural Envelope Equipment/Subsystems Distributed Systems • Connectivity • assembly • penetrations • ports Pipe Flow Analysis and Sizing • 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 Value Equipment: Pump Type: Vertical Centrifugal Casing: Cast Iron Impeller: Bronze Shaft: Stainless Mfg: Allweiler Marine Q: 200 m3/h Ps bar 3 bar RPM: 1750 Power: 23 kw TMAX 250 Pipe Stress Analysis 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 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 AP227:2001, Plant spatial configuration – piping systems AP227 Edition 2:draft, Plant spatial configuration - HVAC systems ISO 13584 (Parts Library Exchange) • Connectivity • assembly • penetrations • ports • Connectivity • assembly • penetrations • ports Loading conditions • Compartments • types • properties • (shape, • coatings, • adjacency, • access….) • Zone Boundaries • Controlling Access • Design Authority • Cargo Stowage • Machinery Compartments • Crew Occupancy • Common Purpose Spaces 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 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 • Cargoes • assignment to compartments • weight, • centre of gravity • Stability • intact • damaged General Subdivision of a Ship into Spatially Bounded Regions AP227 Edition 2:draft, Plant spatial configuration - cable trays AP227 Edition 2:draft, Plant spatial configuration - mechanical systems ISO 15926 (Oil and Gas) AP215:IS, Ship arrangement • Ship Structural Envelope (hull forms, arrangement, structures) • Distributed Systems (electrical, piping, HVAC, cable ways, mechanical systems) • Mission Equipment/Subsystems (library and catalog parts) • Equipment Coverage • Power-transmission • Power-distribution • Power-generation • Electric Machinery • Electric Light and Heat • Control Systems • Electrotechnical Systems • Buildings • Plants • Transportation Systems • Data Supporting • Terminals and Interfaces • Functional Decomposition of Product • 3D Cabling and Harnesses • Cable Tracks and Mounting Instructions General Characteristics • Configuration Management • Class Approval • Approval Relationship • Change Administration • Promotion Status Production Engineering Data • Product Structure • Generic Product Structure • System • Space • Connectivity • Assembly • Electrotechnical Plant • Plant, e.g., Automobile • Unit, e.g., Engine Control System • Subunit, e.g., Ignition System • Structural Parts • Feature • Plate • Edge Content • Opening • Profile • Profile Endcut Hull Cross Section • Geometric Representations • Wireframe • Complex Wireframe • Surfaces • Solids Ship Product Model Data Exchange Information STEP - http://www.tc184-sc4.org USPRO – https://www.uspro.org Ship STEP - http://www.usashipbuilding.com/niddesc/t23.html Technical Description AP212:2001, Electrotechnical design and installation AP218:IS, Ship structures

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

  8. 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

  9. 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

  10. 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

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

  12. 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

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

  14. Ap233 Enabling Capability Breakdown

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

  16. 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)

  17. 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

  18. 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)

  19. 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

  20. 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

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

  22. 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 9th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2-4 May 2007-

  23. 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 9th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2-4 May 2007-

  24. "Classical" Engineering Data Standards andOntologies "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 9th NASA-ESA Workshop on Product Data Exchange, Santa Barbara, CA, USA, 2-4 May 2007-

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

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

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

  28. 3. Enterprise Collaboration - Portals and dashboards to Applications 2. Enterprise Process Management – Cross-application processes 1. Enterprise Integration - Management of PLM and Enterprise Information Servers Software Storage Integrated PLM SOA Environment Project/Business Management (OEM &/or Suppliers) Engineers(OEM &/or Suppliers) Quality Operations Sales Service 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 Enterprise Application Systems ERP Other Enterprise Applications EAM Requirements Management Data Management Data Management Data Management Data Management Program and Portfolio Management Enterprise PDM Software Authoring Analysis & Simulation Mechanical Authoring Electrical Authoring 32

  29. IBM: influencing and shaping open standards for PLM • 1980s -1990s • Java and ebXML • ISO STEP • OMG UML and XML • OpenGL • SQL • AIAG • IEEE • VRML • ANSI • RosettaNet • 2000 - 2005 • Web Services / Interoperability • Eclipse to Open • UDDI • SOAP • W3C XML • SOAP4J to Open • Open Systems • 2006 - 2007 • OMG PLM Services 1.0-3.0 • STEP AP 214, 210, 219, 233, 239.. • ProSTEP • PDES Inc • SASIG, AutoSAR, JAMA other industry groups • IBM Enterprise Interoperability Center • IBM Services Oriented Architecture • BPEL • WSBPEL • WS-TX • WS-TC • OASIS Over 160 business integration technology patents First integrated private UDDI directory First Web Services Gateway

  30. Standards across PLM Lifecycle (Ministry of Defense)

  31. Systems Engineering Standards Process Standards Ex: EAI 632, ISO 15288, CMMI,… Architecture Frameworks Ex: DoDAF, MoDAF, … Modeling Methods Ex: SADT, OOSE,… Implemented by tools Modeling & Simulation Standards Ex: UML/SysML (modeling), HLA (Simulation) Interchange Standards Ex: MOF/XMI , STEP/AP233, CADM,…

  32. Standards for Model-Based Systems Engineering Data and Model Interchange • AP233 - The ISO standard for exchanging systems engineering data DoDAF – DoD Architecture Framework • Defines standardized view of systems information • CADM = Core Architecture Data Model SysML – Systems Modeling Language • Standard modeling language and notation for systems engineers These standards are highly complementary.

  33. Data and Model Interchange – AP233 • 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 • Multi-company collaboration is increasing • Data exchange between systems engineering applications/organizations is not simple

  34. AP233 Concept Model

More Related