STEP, XML, and UML: Complementary Technologies ASME 2004 Design Engineering Technical Conferences (DETC) and Computers and Information in Engineering (CIE) Conference Sept 28 - Oct 2, 2004 • Salt Lake City, Utah Paper No. DETC2004-57743 http://eislab.gatech.edu/pubs/conferences/2004-asme-detc-lubell/ Extended version in JCISE December 2004 issue: http://eislab.gatech.edu/pubs/journals/2004-jcise-peak/ STEP, XML, and UML: Complementary Technologies J. Lubell - NIST R. Peak - Georgia Tech V. Srinivasan - IBM S. Waterbury - NASA Copyright © 1992-2004 by Georgia Tech Research Corporation, Atlanta, Georgia 30332-0415 USA. All Rights Reserved. Permission to reproduce and distribute for non-commercial purposes (including internal corporate usage) is hereby granted provided this notice and a proper citation are included.

STEP, XML, and UML: Complementary Technologies Abstract STEP, XML, and UML: Complementary Technologies One important aspect of product lifecycle management (PLM) is the computer-sensible representation of product information. Over the past fifteen years or so, several languages and technologies have emerged that vary in their emphasis and applicability for such usage. ISO 10303, informally known as the Standard for the Exchange of Product Model Data (STEP), contains the high-quality product information models needed for electronic business solutions based on the Extensible Markup Language (XML). However, traditional STEP-based model information is represented using languages that are unfamiliar to most application developers. This paper discusses efforts underway to make STEP information models available in universal formats familiar to most business application developers: specifically XML and the Unified Modeling Language™ (UML®). We also present a vision and roadmap for future STEP integration with XML and UML to enable enhanced PLM interoperability. http://eislab.gatech.edu/pubs/conferences/2004-asme-detc-lubell/ Extended version in JCISE December 2004 issue: http://eislab.gatech.edu/pubs/journals/2004-jcise-peak/ Notice: Commercial equipment and materials are identified in order to describe certain procedures. Some slides include product names for example purposes only (i.e., to help clarify the concepts presented via specific instances). In no case does such identification imply recommendation or endorsement by the authors or their organizations, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. Unified Modeling Language, UML, Object Management Group, OMG, and XMI are trademarks or registered trademarks of the Object Management Group, Inc. in the U.S. and other countries. Java is a trademark or registered trademark of Sun Microsystems, Inc. Other company, product, and service names may be trademarks or service marks of others.

Contents Context: Standards-based PLM Frameworks Model-centric thinking vs. tool-centric thinking Current Status of STEP, XML, UML High-level comparison Information/knowledge representation methods Modeling languages (schemas and instances) Standardized content models (schemas) Proposed Roadmap and Further Work

Model-Centric Standards-based Spacecraft Development Electrical Engineering Standard: AP210 Software Mentor Graphics Status: Prototyped Rockwell, Boeing Cabling Standard: AP212 Software MentorGraphics Status: Prototyped Daimler-Chrysler, ProSTEP Propulsion Standard: STEP-PRP Software:- Status: In Development ESA, EADS Fluid Dynamics Standard: CFD Software - Status: In Development Boeing, Software Engineering Standard::UML - (AP233 interface In Development) Software:Rational Rose, Argo, All-Together Status: In Production Industry-wide Optics Standard: NODIF Software - TBD Minolta, Olympus Mechanical Engineering Standard: AP203, AP214 Software Pro-E, Cadds, SolidWorks, AutoCad, SDRC IDEAS, Unigraphics, others Status: In Production Aerospace Industry Wide, Automotive Industry Structural Analysis Standard: AP209 Software: MSC Patran, Thermal Desktop Status: In Production Lockheed Martin, Electric Boat Systems Engineering Standard: AP233 Software: Statemate, Doors, Matrix-X, Slate, Core, RTM Status: In development / Prototyped BAE SYSTEMS, EADS, NASA PDM Standard: STEP PDM Schema/AP232 Software: MetaPhase, Windchill, Insync Status: In Production Lockheed Martin, EADS, BAE SYSTEMS, Raytheon Thermal Radiation Analysis Standard: STEP-TAS Software: Thermal Desktop, TRASYS Status: In Production ESA/ESTEC, NASA/JPL & Langely Machining Standard:: STEP-NC/AP224 Software:: Gibbs, Status:: In Development / Prototyped STEP-Tools, Boeing Inspection Standard: AP219 Software: Technomatics, Brown, eSharp Status: In Development NIST, CATIA, Boeing, Chrysler, AIAG Life-Cycle Management Standard: PLCS Software: SAP Status: In Development BAE SYSTEMS, Boeing, Eurostep 2001-12-16 - Jim U’Ren, NASA-JPL File: SLIDE_STEP-in-Spacecraft-Development-Ver4.ppt

Instance Browser/Editor Towards Standards-based PLM Frameworks Model-centric view (vs. Tool-centric view) Electrical CAD Tools Mechanical CAD Tools Systems Engineering Tools Eagle Pro/E Doors Traditional Tools Mentor Graphics CATIA Slate … AP210 AP203, AP214 AP233, SysML Collective Product Model Building Blocks: Information models & meta-models International standards Industry specs Corporate standards Local customizations Modeling technologies: Express, XML, UML, OWL, COBs, … XaiTools PWA-B LKSoft, … Gap-Filling Tools EPM, LKSoft, STI, … STEP-Book AP210, SDAI-Edit, STI AP210 Viewer, ... Instance Browser/Editor PWB Stackup Tool, … pgef Engineering Framework Tool AP210 AP2xx Standards-based Submodels

Contents Context: Standards-based PLM Frameworks Model-centric thinking vs. tool-centric thinking Current Status of STEP, XML, UML High-level comparison Information/knowledge representation methods Modeling languages (schemas and instances) Standardized content models (schemas) Proposed Roadmap and Further Work

Implementation Methods Primary Information Representation Technologies for Standards-based PLM Frameworks Information Modeling Implementation Methods Standardized Content (STEP Part 11)

STEP, XML, UML Capabilities regarding Engineering/Technical Domains Characteristic Aspect Classical STEP XML UML Information Modeling Capability: Popularity: High (+) Narrow High (-) High Implementation Methods Narrow: pre-web Standardized Content Breadth: Depth/Richness: Coordination: Usage: Broad (MCAD), plus Limited / Emerging (others) Medium Medium+ Low (islands) Broad (some), plus Emerging Medium (s/w+) Complementary Strengths Note: “Next-wave STEP” is adding XML and UML implementation methods (a.k.a. Parts 28 and 25)

Contents Context: Standards-based PLM Frameworks Model-centric thinking vs. tool-centric thinking Current Status of STEP, XML, UML High-level comparison Information/knowledge representation methods Modeling languages (schemas and instances) Standardized content models (schemas) Proposed Roadmap and Further Work

Information Model: simple_drawings Express lexical and graphical schema formats Express-G SCHEMA simple_drawings; ENTITY drawing; name : STRING; elements : SET [1:?] OF shape; END_ENTITY; ENTITY shape; label : STRING; ENTITY point SUBTYPE OF (shape); x : REAL; y : REAL; ENTITY line SUBTYPE OF (shape); end1 : point; end2 : point; END_SCHEMA; end1 end2 1 x y label name elements S[1:?] shape line point drawing STRING REAL Note: Another way for handling part-of relationships rather than SET as above is to use INVERSE as introduced earlier.

Information Model: simple_drawings XML format <xs:complexType name="Shape"> <xs:sequence> <xs:element name="label" type="xs:string"/> </xs:sequence> <xs:attributeGroup ref="OID"/> </xs:complexType> <xs:complexType name="Point"> <xs:complexContent> <xs:extension base="Shape"> <xs:element name="x" type="xs:decimal"/> <xs:element name="y" type="xs:decimal"/> </xs:extension> </xs:complexContent> <xs:complexType name="Point-ref"> <xs:attribute name="ref" type="xs:IDREF"/> <xs:complexType name="Line"> <xs:element name="end1" type="Point-ref"/> <xs:element name="end2" type="Point-ref"/> <xs:complexType name="Line-ref"> </xs:schema> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:attributeGroup name="OID"> <xs:attribute name="id" type="xs:ID" use="optional"/> </xs:attributeGroup> <xs:element name="p28data"> <xs:complexType> <xs:choice minOccurs="1" maxOccurs="unbounded"> <xs:element name="drawing" type="Drawing"/> <xs:element name="point" type="Point"/> <xs:element name="line" type="Line"/> </xs:choice> </xs:complexType> </xs:element> <xs:complexType name="Drawing"> <xs:sequence> <xs:element name="name" type="xs:string"/> <xs:element name="elements"> <xs:choice maxOccurs="unbounded"> <xs:element name="line" type="Line-ref"/> <xs:element name="point" type="Point-ref"/> </xs:sequence> <xs:attributeGroup ref="OID"/> Express  XML schema mapping done via STEP Part 28

Information Model: simple_drawings UML class diagram Express  UML mapping done via STEP Part 25

Example Drawing Instance: ‘Design 2L3P’ STEP Part 21 Format Instance Model Fragment (Part 21 format) Design 2L3P Reference to another instance Inherited attribute #10 = point ('P01', 2.0, 2.0); #20 = point ('P02', 5.0, 2.0); #30 = point ('P03', 5.0, 4.0); #110 = line ('L01', #10, #20); #150 = line ('L02', #10, #30); #200 = drawing ('Design 2L3P', (#10, #20, #30, #110, #150)); Members of aggregate attribute

Example Drawing Instance: ‘Design 2L3P’ XML Format (Part 28 mapping) Instance Model Fragment (Part 28 format) Design 2L3P <p28data> <point id="_10"> <label>P1</label> <x>2.0</x> <y>2.0</y> </point> <point id="_20"> <label>P2</label> <x>5.0</x> <point id="_30"> <label>P3</label> <y>4.0</y> <line id="_110"> <label>L1</label> <end1 ref="_10"/> <end2 ref="_20"/> </line> <line id="_150"> <label>L2</label> <end1 ref="_10"/> <end2 ref="_30"/> </line> <drawing id="_200"> <name>Design 2L3P</name> <elements> <point ref="_10"/> <point ref="_20"/> <point ref="_30"/> <line ref="_110"/> <line ref="_150"/> </elements> </drawing> </p28data>

Contents Context: Standards-based PLM Frameworks Model-centric thinking vs. tool-centric thinking Current Status of STEP, XML, UML High-level comparison Information/knowledge representation methods Modeling languages (schemas and instances) Standardized content models (schemas) Proposed Roadmap and Further Work

“STEP on a Page” Application Protocols (APs) p. 1 of 3  Source: “STEP on a Page” by Jim Nell. 2003-April-07 version. http://www.mel.nist.gov/sc5/soap/

STEP on a Page - IRs, etc.

STEP on a Page - App. Modules (AMs)

Contents Context: Standards-based PLM Frameworks Model-centric thinking vs. tool-centric thinking Current Status of STEP, XML, UML High-level comparison Information/knowledge representation methods Standardized content models (schemas) Example next-wave of STEP: Rich product models and tools (AP210, AP212, AP214) Proposed Roadmap and Further Work

STEP AP210 (ISO 10303-210) Domain: Electronics Design ~950 standardized concepts (many applicable to other domains) Development investment: O(100 man-years) over ~10 years Product Enclosure External Interfaces Printed Circuit Assemblies (PCAs/PWAs) Die/Chip Package Packaged Part Interconnect Assembly Printed Circuit Substrate (PCBs/PWBs) Configuration Controlled Design of Electronic Assemblies, their Interconnection and Packaging 2003-04 - Adapted from 2002-04 version by Tom Thurman, Rockwell-Collins

STEP AP210 Scope R Scope is “As-Required” & “As-Designed” Product Information Design “In Process” & “Release” Design views (white boxes) & usage views (black boxes) Design at individual or multiple levels: microsystems, packages, PCAs, units, … Sharing Partners: Engineering Domains Design / Analysis Manufacturing / Analysis Sharing Across Several Levels of Supply Base 3

STEP AP210 Models Requirements Models Component / Part Models Functional Models Design Constraints Interface Allocation Analysis Support Package Material Product Properties “White Box”/ “Black Box” Pin Mapping Functional Unit Interface Declaration Network Listing Simulation Models Signals Assembly Models Interconnect Models User View Design View Component Placement Material product Complex Assemblies with Multiple Interconnect User View Design View Bare Board Design Layout templates Layers planar non-planar conductive non-conductive Configuration Mgmt Identification Authority Effectivity Control Net Change GD & T Model Datum Reference Frame Tolerances 5

Rich Features in AP210: PWB traces AP210 STEP-Book Viewer - www.lksoft.com

Rich Features in AP210: Via/Plated Through Hole Z-dimension details …

Rich Features in AP210: PCB Assembly: 3D & 2D STEP-Book AP210 Browser - www.lksoft.com PDES Inc. EM Pilot Test Case: Cable Order Wire (COW) Board

Rich Features in AP210: Electrical Component The 3D shape is generated from these “smart features” which have electrical functional knowledge. Thus, the AP210-based model is much richer than a typical 3D MCAD package model. 210 can also support the detailed design of a package itself (its insides, including electrical functions and physical behaviors).

3D Mechatronics via AP210 JMID-210

Using Rich Product Models to Drive Analysis Complex Idealizations via AP210 for Circuit Board Warpage Analysis AP210 Design Model Idealizations Analysis Model (Analytical Level) Single Layer View width length … Top view of “effective” grid elements in top layer of the PCB Effective Material Property Computation … Side view of the PCB with “effective” grid elements across the stratums thickness Given: Thermal loading profile Boundary Conditions (mostly displacement) Idealize PWB stackup as a layered shell Grid (Sieve) Size Analysis template attributes Thermal loading profile Boundary Conditions (mostly displacement) Idealize PWB stackup as a layered shell

Example Warpage Results - ECAD to FEA via AP210 Experimental Results 0 C

AP 212: Electrotechnical Design and Installation Data Supporting Terminals and Interfaces Functional Decomposition of Product 3D Cabling and Harnesses Cable Tracks and Mounting Instructions Electrotechnical Systems Buildings Plants Transportation Systems Electrotechnical Equipment in Industry Electrotechnical Plant Plant, e.g., Automobile Unit, e.g., Engine Control System Subunit, e.g., Ignition System Equipment Coverage Power-transmission Power-distribution Power-generation Electric Machinery Electric Light and Heat Control Systems 2

AP 214: Core Data for Automotive Mechanical Design Processes ProSTEP Geometry Solids Data Surface Data Wireframe Measured Data Presentation Drawing Visualization Manufacturing NC-Data Process Plans Analysis Simulation Technology Data Material Data Form Features Tolerance Data Surface Conditions Specification/Configuration Product Structure Data Management Data 4

IDA-STEP Overview IDA-STEP Viewer (v1.2 - May, 2004 - free download) Example end-user tool for viewing and editing rich product models in an open standards-based PLM environment IDA-STEP Viewer (v1.2 - May, 2004 - free download) Supports AP203, AP212, AP214 Downloadable from www.ida-step.net IDA-STEP Center version Adds editing and transformation/export capabilities Supports repository interfaces

Linking Intelligent 3D with Product Structure Selecting and highlightig of components (single_instances) in both directions: Tree <-> Graphic

Process Plan - Tree Read Only, data generated in eM-PlannerTM / Tecnomatix

Linking Intelligent 2D (e.g. Factory Layout) with Product Structure

The Adobe Acrobat / pdf equivalent for rich product models Example Features and Usage of Standards-based Tools for Rich Product Models (IDA-STEP v1.2) AP203, AP212, AP214 and PDM-Schema support Viewing 2D & 3D geometry and intelligent schematics Creation and editing of rich PLM information Single user versions (PC, Workstation) Multi-user environments: STEP database using MySQL and Oracle Target Usage Standards-based PLM for SMEs Prime-SME collaboration via rich product models The Adobe Acrobat / pdf equivalent for rich product models

Contents Context: Standards-based PLM Frameworks Model-centric thinking vs. tool-centric thinking Current Status of STEP, XML, UML Proposed Roadmap and Further Work Complementary technologies working together

Complementary Usage of STEP, UML, and XML for Systems Engineering: Envisioned AP233-SysML Relationship Source: www.SysML.org 2003-12

Summary STEP, XML, UML are complementary technologies STEP provides standardized rich content models Next-wave capabilities are also emerging XML and UML provide ubiquitous implementation methods Further needed work: More detailed comparison methods and metrics for: Information modeling capabilities Content models Investigations & comparisons with other techniques: OWL (ontologies/semantic web) Schematron (XML-based schema rules/constraints)

Backup Slides

Next-Generation PLM Framework with Fine-Grained Interoperability … Customer/Acquisitions … … Abstraction Level Systems Engineering … Legend Rich models: Information objects Parametric relations Model interfaces: Fine-grained associativity relations among domain-specific models and system-level models … … Development Process … … … Requirements Software Electronics Structures Human Interfaces … Domain 2004-09 Models of varying abstractions and domains After Bajaj, Peak, & Waterbury 2003-09

Current Typical Levels of PDM System Deployment and Limitations Level 1: Domain-Level PDM Interactive WIP design collaboration: main tools Tight integration w/ major domain-specific CAD tools Level 2: Workgroup-Level PDM Interactive WIP design collaboration Focus on inter-tool information interoperability Limitations: Content coverage and semantics gaps Fine-grained associativity gaps Even within a native file Esp. between attributes in monolithic native files Dynamic interactivity lacking vs. batch releases Custom software and person-ware (manual) glue Basic Objects & Relations (Macro-level associativity) Oracle MGC DMS ____________ Native Files DBMS MGC BoardStation ECAD- Oriented PDM ECAD Bound Design Enterprise PDM EDS Metaphase Level 3: Enterprise-Level PDM Major releases (to manufacturer, to supplier, …) Long term archiving Plus other enterprise resources: Document Mgt. Systems (e.g., DocuShare), … ____________ Native Files DBMS Oracle … Oracle PTC ProjectLink ____________ Native Files DBMS PTC Pro/Engineer 2001 MCAD- Oriented PDM MCAD Bound Design

Knowledge Representation Elements Structure/Content Definition Languages Graphical Representations Knowledge Representation Meta-Model Protocol Operations/Methods

Coordinated Suite of Modeling Languages Lexical and Graphical Formulations Structure Level (Template) Instance Level OWL, XML, and UML formulations are envisioned extensions

STEP on a Page - Explanation

STEP-Book AP210 v2.x Major variants: STEP-Book AP210 Viewer STEP-Book AP210 Pro with integrated translators Server based AP210 translators Supports new Minor Revision of AP210 Interface on normative AIM level Internally working with an extended ARM schema

STEP-Book AP210 Pro v2.1 ECAD Interfaces Import Export Mentor / Boardstation PCB & PCA Zuken / Visula-CADIF CadSoft / EAGLE Mentor / PADS GERBER PCB only Valor / ODB++ AP203 / 214 PCA (& PCB) AP210 All Cadence / OrCAD translator under development Ongoing round robbin tests

Schematron Diagnostics for “Design 2L3P” XML Instance Example