1 / 23

Model Based Systems Engineering (MBSE) and Related Interoperability Standards

Model Based Systems Engineering (MBSE) and Related Interoperability Standards. Charlie Stirk stirk@costvision.com 303-539-9312 May 22, 2012. Systems Engineering and 3D Interoperability. Models are Used in both domains Inter-dependent Models need to be .. between MBSE and 3D Exchanged

erwin
Download Presentation

Model Based Systems Engineering (MBSE) and Related Interoperability Standards

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. Model Based Systems Engineering (MBSE) and Related Interoperability Standards Charlie Stirk stirk@costvision.com 303-539-9312 May 22, 2012

  2. Systems Engineering and 3D Interoperability • Models are • Used in both domains • Inter-dependent • Models need to be .. between MBSE and 3D • Exchanged • Shared • Traced • Transformed • Validated • Configuration & Change Managed • STEP MBSE and 3D model interoperability standards

  3. Use of AP233/239 in Systems Engineering • Early versions of STEP AP233 SE used for • Data Migration between Slate and TeamCenter SE • Mapping of CADM 1.5 format for DoDAF • Mapping of SysML • AP239 Product Life Cycle Support (PLCS) • Extendable and Tailorable • Basis for Integrated Logistics Support (ILS) standards • AP233 and AP239 Convergence • AP239ed2 contains all but 233’s Issue and Behavior Models (State Machines and Enhanced Functional Flow Block Diagrams) • Roll them into STEP modules and/or reference data

  4. Requirements Interchange Format (ReqIF) • From German auto mfg consortium HIS • Standardized through OMG • Several earlier versions in use as RIF (1.0, 1.0a, 1.1, 1.1a, 1.2) • Current ReqIF 1.0.1 from April 2011 • Metamodel with rules for creating XML schema • XML documents for exchange • Representation • spec hierarchy, formatted text, UID, attributes, relations, relation groups, editable or read-only • Can add company/project specific attributes • Attributes are strictly typed and values are validated by the XML schema (e.g. String, Integer, Enumerations ….) • Supports tool-specific extensions

  5. ReqIF Status • Tool implementations not interoperable • ProSTEPiViPrunning an implementers forum • Defined conventions for • Attribute naming & lifecycle • DOORS table handling • File extensions (.reqif, .reqifz) • Referencing external files (e.g. images) • First test round mid 2013 (DOORS, Integrity, requisis_REX) • Drive new release of implementation guide • Drive editorial changes to ReqIF 1.1 • Open source Eclipse RMF, ProR, TopCased-Req, Rodin • Early mapping with AP233 needs updating/validation • Use case 1: model configuration management • Use case 2: cross-domain interoperability (architecture, V&V)

  6. Systems Modeling Language (SysML) • Diagram language based on UML/OMG MOF • XMI = XML Model Interchange format • Written specification for OMG MOF (interpreted!) • Canonical XMI is restricted specification (NIST Validator) • OMG MIWG testing conformance, but not interchange yet • Need UID for diagram/data management • Without diagram exchange, limited to libraries, black-box, or manual model re-building • SysML and Modelica Integration • Through a model transformation specification • Partial mapping with AP233 needs completion

  7. SysML/AP233 Data Overlaps Issue Management AP233 SysML Classification Lifecycle Stages Diagrams System Structures/Blocks Eng Config Mgmt V & V Activities Organizations Allocations Parametrics Schedule Text-based Requirements Change Management FunctionModels Views and Viewpoints Approvals, Security, Status StateMachines RequirementsManagement Model Organization Property& Units Property-based Requirements Interfaces/Ports & Flows Risk Management

  8. Functional Mockup Interface (FMI) • For model exchange and co-simulation of dynamic models • Import/Export and Master/Slave • Contains • Description of interface data (XML file) • Functionality (C code or compiled binary) • FMI 1.0 published in 2010 • Over 35 tools support FMI (CATIA, MATLAB, LabVIEW, …) • FMI 2.0 in development • Unification and harmonization of exchange and co-simulation • Improved handling of time events • Clean handling of changeable parameters • Efficient interface to Jacobian matrices • ProSTEPiViP organizing implementers forum

  9. Open Services for Lifecycle Collaboration (OSLC) • Started by IBM for SE products (DOORS & Rational) • Supported by many software ALM tool vendors • Scope • Change, Requirements, Quality, Asset and Automation • Integrated ALM-PLM • Linked data using semantic web standards • RDF, SPARQL, HTTP, URI, REST • OAuth for authentication • Based partially on concepts from STEP AP233 SE • Standardizing through W3C and OASIS • Open source reference implementation • Eclipse Lyo: Tests, Libraries, Samples, Examples • E.g. Bugzilla, Mantis adaptors • OSLC4Net for .NET development

  10. Program and Project Management • Earned Value Management (EVM) • UNCEFACT based XML Schemas for Cost and Schedule • Cost classification by Work Breakdown Structure • MIL-STD-881 for systems (but hybrid breakdown) • Operations & Support WBS (functional breakdown) • DoD requiring on all large programs for EVM baseline and reporting to Central Repository • NATO Guidance on Life Cycle Costing (ALCCP-1) • Recommends use of PLCS for data collection • Recommends standard Cost Breakdown Structure • Recommends standard activity and resource classification • Collaborative Project Management (CPM) • Usage Guide, Data Exchange Model, Implementation Guide • By ProSTEPiViP with German auto industry • XML schemas and WSDL transport

  11. Model Transformation Technologies • XSLT (Extensible Stylesheet Language Transformations) • Between XML documents, HTML, PDF, relational databases, … • Many proprietary and open source implementations • E.g. STEPmod publishing system for STEP AP’s • EXPRESS-X (ISO 10303-14) • Data between EXPRESS schemas • NIST Expresso open source and commercial tools • E.g. implement STEP ARM to MIM/AIM mapping • Meta Object Facility (OMG MOF) • Typically between UML derived languages and models • Ecore variant in Eclipse Modeling Framework commonly used • Transformation languages: QVT, ATL, VIATRA • E.g. ReqIF to SysML Requirements

  12. PDES Systems Engineering Projects • Requirements Traceability • Decomposition from Capabilities to Specifications • Across supply chain • Across tools (DOORS, ReqIF, SysML, etc.) • To verification & validation artifacts • Engineering change processes • Systems Model Interoperability • Architecture, Behavior, … • Across lifecycle (Architecture, Systems, Design, Test, etc.) • Across languages (UPDM, SysML, UML, AADL, domain specific, …)

  13. Simulation Data Management (SDM) • SimPDM project of ProSTEPiViP • Business process diagrams • Business process between SDM, Multi-Body, FEM, CFD, PDM • Not an interchange data format, it is a metadata model • CAE Services project of ProSTEPiViP • Successor to Collaborative CAD/CAE Integration (C3I) • Successor to SimPDM • XML schemas and WSDL • Mapping to AP209 entities • SimDM project of PDES Inc. • Uses AP209ed2 and 242-style Business Object Model • CRESCENDO project of EU • Based on EU VIVACE, AP233/239 and PLCSlib • Behavioural Digital Aircraft (BDA) Model …

  14. Behavioural Digital Aircraft (BDA) Model • BDA Business Object Model defines common language exposed as web services based on 233/239 • BDA PLCSlib DEX’s to be publicly released soon • Many base PLCS templates already available as OASIS templates • Not specific to aircraft, can be used for other types of products • Web services to create, update, read and search data • WSDL interfaces implemented against • Share-a-space collaboration hub • Clients: MSC SimManager/SimXpert, Siemens TeamCenter/NX, Scilab, Proosis, Dassault CATIA/Enovia/iSight/Dymola, Altair/Optistruct

  15. Benefits of PLCSlib • New DEX development environment • Recommended by OASIS PLCS Technical Committee on all new DEX development • Replaces DEXlib and based on AP239ed2 International Standard (IS) • Generate DEX XML schema from SysML model • Reference data in semantic web technology (OWL2 DL, SKOS, RDF) • Uses new templates (due to AP239ed2 and other lessons learned) • Benefits • Can transform data for legacy DEX to new DEX’s (no DEX transform) • Re-use DEXlib business information requirements/entity mapping • Faster DEX development (SysML IDE & encapsulation/abstraction) • SysML integration to Enterprise Architecture and Systems Engineering • Smaller file sizes and XML schemas • Better re-use and fewer base templates • Better quality due to built-in object and type checking • Software code and web service generation

  16. Business Object Model : BDA Dataset coverage Rich model designed to enable traceability from customer expectations through to certification

  17. AP239 ed2 PLCS Concept Model

  18. Organization A Organization B Data Exchange Specification (DEX) Exchange process specifies Business Objects Model maps Ref. Data Templates uses maps specializes PLCS PSM maps maps Transformed System model System model PLCS PSM XSD References Translator Translator System A System B

  19. SysML Block Definition Diagram of PLCS Requirements

  20. PLCS and Logistics • ASD/AIA Integrated Logistics Support (ILS) S-series • SX000i Guide for Use of S-series • S2000M Material Management • S3000L Logistics Support Analysis • S4000M Scheduled Maintenance • S5000F Operational & Maintenance Feedback • S6000T Training Needs Analysis • S9000D Dictionary • GEIA-0007 Logistics Product Data • Based on MIL-STD-1388-2B • Participation in ILS S-series • Other MODs developing PLCS DEXs • France, Norway, Sweden, UK, USMC/NATO

  21. Role of STEP in Systems Engineering • AP233/239 used to manage mapped objects • Supports relationships & configuration management • Like earlier work with CADM, IFC, SysML • Add ReqIF, UPDM, EVM, CPM, etc. • STEP provides links to other domains • CAD, CAE, PDM, LSA, provisioning, scheduled maintenance, tech pubs, field data …

  22. Conclusions • Both SE and 3D have overlapping standards • 3D: BREP, PMI, tessellation, assembly structure • SE: Requirements, architecture, activity, project • Use different standards for different purposes • Map and manage the overlaps • Translate or transform between different implementations • Keys to success • Standards development infrastructure (eg. STEPmod, MOF) • Implementer forums (conformance & exchange) • Open source reference implementations • Best practices (Validation, UIDs, Testing …)

  23. Questions? Charlie Stirk CostVision Inc. stirk@costvision.com 303-539-9312

More Related