Transcript 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.
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.
2
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
3
Model-Centric Standards-based Spacecraft Development
Propulsion
Fluid Dynamics
• Standard:
• Standard: CFD
• Software • Status: In Development
• Boeing,
STEP-PRP
• Software:• Status: In Development
• ESA, EADS
Electrical Engineering
Cabling
• Standard: AP210
• Standard: AP212
• Software Mentor Graphics
• Status: Prototyped
• Rockwell, Boeing
• Software MentorGraphics
• Status: Prototyped
• Daimler-Chrysler, ProSTEP
Software Engineering
Optics
Mechanical Engineering
• Standard: NODIF
• Standard: AP203, AP214
• Software - TBD
• Minolta, Olympus
• Software Pro-E, Cadds, SolidWorks,
AutoCad, SDRC IDEAS, Unigraphics,
others
• Status: In Production
• Aerospace Industry Wide, Automotive
Industry
Structural Analysis
• Standard: AP209
•STEP-Tools, Boeing
2001-12-16 - Jim U’Ren, NASA-JPL
• Standard: AP233
• Software: MetaPhase, Windchill, Insync
• Status: In Production
• Lockheed Martin, EADS, BAE SYSTEMS,
Raytheon
• Software: Thermal Desktop, TRASYS
• Status: In Production
• ESA/ESTEC, NASA/JPL & Langely
•Software:: Gibbs,
•Status:: In Development / Prototyped
Systems Engineering
• Standard: STEP PDM Schema/AP232
• Standard: STEP-TAS
STEP-NC/AP224
• Software:Rational Rose, Argo, All-Together
• Status: In Production
• Industry-wide
PDM
Thermal Radiation Analysis
• Standard::
Development)
• Software: Statemate, Doors, Matrix-X,
Slate, Core, RTM
• Status: In development / Prototyped
• BAE SYSTEMS, EADS, NASA
• Software: MSC Patran, Thermal
Desktop
• Status: In Production
• Lockheed Martin, Electric Boat
Machining
• Standard::UML - (AP233 interface In
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
File: SLIDE_STEP-in-Spacecraft-Development-Ver4.ppt
4
Towards Standards-based PLM Frameworks
Model-centric view (vs. Tool-centric view)
Traditional
Tools
Electrical
CAD Tools
Mechanical
CAD Tools
Systems Engineering
Tools
Eagle
Pro/E
Doors
Mentor
Graphics
CATIA
AP210
…
Slate
AP203, AP214
AP233, SysML
Collective Product Model
Standards-based
Submodels
AP210
Gap-Filling
Tools
XaiTools
XaiTools
PWA-B
PWA-B
AP2xx
pgef
PWB Stackup Tool, Engineering
…
Framework Tool
Building Blocks:
• Information models & meta-models
• International standards
• Industry specs
• Corporate standards
• Local customizations
• Modeling technologies:
• Express, XML, UML,
OWL, COBs, …
EPM,
LKSoft,
LKSoft,
…
STI, …
STEP-Book AP210,
SDAI-Edit,
STI AP210 Viewer, ...
Instance Browser/Editor
5
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
6
Primary Information Representation Technologies
for Standards-based PLM Frameworks
Information Modeling
Implementation Methods
Standardized Content
(STEP Part 11)
7
STEP, XML, UML Capabilities
regarding Engineering/Technical Domains
Characteristic
Aspect Classical STEP
XML
UML
Information
Modeling
Capability:
Popularity:

High (+)
 Narrow

High (-)
 High

Implementation
Methods
Capability:
Popularity:

High (-)
 Narrow: pre-web

High
 High

Standardized
Breadth:
Content Depth/Richness:
Coordination:
Usage:

High
 High
 High
 Broad (MCAD),
plus Limited /
Emerging (others)

Medium
 Medium+
 Low (islands)
 Broad (some),
plus Emerging

Note: “Next-wave STEP” is adding
XML and UML implementation methods
(a.k.a. Parts 28 and 25)
High (-)
 High
High
 High
Medium (s/w+)
 Medium+
 Medium
 Broad (some),
plus Emerging
Complementary
Strengths
8
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
9
Information Model: simple_drawings
Express lexical and graphical schema formats
Express
Express-G
SCHEMA simple_drawings;
ENTITY drawing;
name : STRING;
elements : SET [1:?] OF shape;
END_ENTITY;
ENTITY shape;
label : STRING;
END_ENTITY;
ENTITY point SUBTYPE OF (shape);
x : REAL;
y : REAL;
END_ENTITY;
ENTITY line SUBTYPE OF (shape);
end1 : point;
end2 : point;
END_ENTITY;
name
STRING
drawing
REAL
label
elements
S[1:?]
shape
1
x
y
end1
point
end2
line
END_SCHEMA;
Note: Another way for handling part-of relationships rather than SET as above is to use INVERSE as introduced earlier.
10
Information Model: simple_drawings
XML format
<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:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="line" type="Line-ref"/>
<xs:element name="point" type="Point-ref"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attributeGroup ref="OID"/>
</xs:complexType>
Express  XML schema mapping
done via STEP Part 28
<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:sequence>
<xs:element name="x" type="xs:decimal"/>
<xs:element name="y" type="xs:decimal"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Point-ref">
<xs:attribute name="ref" type="xs:IDREF"/>
</xs:complexType>
<xs:complexType name="Line">
<xs:complexContent>
<xs:extension base="Shape">
<xs:sequence>
<xs:element name="end1" type="Point-ref"/>
<xs:element name="end2" type="Point-ref"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Line-ref">
<xs:attribute name="ref" type="xs:IDREF"/>
</xs:complexType>
</xs:schema>
11
Information Model: simple_drawings
UML class diagram
Express  UML mapping done via STEP Part 25
12
Example Drawing Instance: ‘Design 2L3P’
STEP Part 21 Format
y
Instance Model Fragment
(Part 21 format)
Design 2L3P
6
Reference to
another instance
Inherited attribute
5
P03
4
L03
3
2
P01
L01
P02
1
x
1
2
3
4
5
6
7
#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));
name
STRING
drawing
elements
S[1:?]
Members of
aggregate attribute
REAL
label
shape
1
x
y
end1
point
end2
line
13
Example Drawing Instance: ‘Design 2L3P’
XML Format (Part 28 mapping)
y
Instance Model Fragment (Part 28 format)
Design 2L3P
6
5
P03
4
L03
3
2
P01
L01
P02
1
x
1
2
3
4
5
6
7
<p28data>
<line id="_150">
<point id="_10">
<label>L2</label>
<label>P1</label>
<end1 ref="_10"/>
<x>2.0</x>
<end2 ref="_30"/>
<y>2.0</y>
</line>
</point>
<drawing id="_200">
<point id="_20">
<name>Design 2L3P</name>
<label>P2</label>
<elements>
<x>5.0</x>
<point ref="_10"/>
<y>2.0</y>
<point ref="_20"/>
</point>
<point ref="_30"/>
<point id="_30">
<line ref="_110"/>
<label>P3</label>
<line ref="_150"/>
<x>5.0</x>
</elements>
<y>4.0</y>
</drawing>
</point>
</p28data>
<line id="_110">
<label>L1</label>
<end1 ref="_10"/>
<end2 ref="_20"/>
</line>
14
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
15
“STEP on a Page”
Application Protocols (APs)
Source: “STEP on a Page” by Jim Nell. 2003-April-07 version. http://www.mel.nist.gov/sc5/soap/
p. 1 of 3

16
STEP on a Page - IRs, etc.
17
STEP on a Page - App. Modules (AMs)
18
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
19
R
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
Configuration Controlled Design of Electronic Assemblies,
their Interconnection and Packaging
Interconnect
Assembly
Printed Circuit Assemblies
(PCAs/PWAs)
Product Enclosure
Die/Chip
Packaged Part
Printed Circuit
Substrate (PCBs/PWBs)
Die/Chip
2003-04 - Adapted from 2002-04 version by Tom Thurman, Rockwell-Collins
Package
External Interfaces
20
R


STEP AP210 Scope
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
21
R
STEP AP210 Models
Requirements Models
• Design
• Constraints
• Interface
• Allocation
Functional Models
•
•
•
•
•
Functional Unit
Interface Declaration
Network Listing
Simulation Models
Signals
Component / Part Models
•
•
•
•
•
•
Analysis Support
Package
Material Product
Properties
“White Box”/ “Black Box”
Pin Mapping
Assembly Models
Interconnect Models
• User View
• Design View
• Component Placement
• Material product
• Complex Assemblies with
Multiple Interconnect
GD & T Model
• Datum Reference Frame
• Tolerances
•
•
•
•
•
Configuration Mgmt
Identification
Authority
Effectivity
Control
Net Change
•
•
•
•
•
User View
Design View
Bare Board Design
Layout templates
Layers
planar
non-planar
conductive
non-conductive
Rich Features in AP210: PWB traces
AP210 STEP-Book Viewer - www.lksoft.com
23
Rich Features in AP210: Via/Plated Through Hole
Z-dimension details
…
24
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
25
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).
26
27
3D Mechatronics
via AP210
JMID-210
28
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
…
thickness
Side view of the PCB with
“effective” grid elements across
the stratums
Given:
Grid (Sieve) Analysis template attributes
Size
• Thermal loading profile
• Boundary Conditions (mostly displacement)
• Idealize PWB stackup as a layered shell
• Thermal loading profile
• Boundary Conditions (mostly displacement)
• Idealize PWB stackup as a layered shell
29
Example Warpage Results - ECAD to FEA via AP210
Experimental Results
Scale (mils)
25
0C
20
15
10
5
0
Model
Exp't
200
Temperature (C)
150
100
50
0
-50
-100
30
AP 212: Electrotechnical
Design and Installation
Electrotechnical Systems
• Buildings
• Plants
• Transportation Systems
Equipment Coverage
• Power-transmission
• Power-distribution
• Power-generation
• Electric Machinery
• Electric Light and Heat
• Control Systems
Data Supporting
• Terminals and Interfaces
• Functional Decomposition of Product
• 3D 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
Electrotechnical Equipment in Industry
31
AP 214: Core Data for Automotive
Mechanical Design Processes
Geometry
• Solids Data
• Surface Data
• Wireframe
• Measured Data
ProSTEP
Presentation
• Drawing
• Visualization
Manufacturing
Analysis
• NC-Data
• Process Plans
• Simulation
Technology Data
Specification/Configuration
• Product Structure Data
• Management Data
• Material Data
• Form Features
• Tolerance Data
• Surface Conditions
IDA-STEP Overview
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
33
Linking Intelligent 3D with Product Structure
34
Process Plan - Tree
Read Only, data generated in eM-PlannerTM / Tecnomatix
35
Linking Intelligent 2D (e.g. Factory Layout)
with Product Structure
36
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
37
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
38
Complementary Usage of STEP, UML, and XML
for Systems Engineering: Envisioned AP233-SysML Relationship
Electrical
CAE
SysML
Tools
Systems
Engineering
XMI
(XML Metamodel
Interchange for UML)
AP-233 Neutral
Info Exchange
Format
Algorithm
Design
Mechanical
CAD
SW Dev
Environment
Source: www.SysML.org 2003-12
Testing
Tools
Planning
Tools
39
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)
40
Backup Slides
Abstraction Level
Next-Generation PLM Framework with Fine-Grained Interoperability
…
Customer/Acquisitions
…
Systems Engineering
…
…
Legend
Electronics
Human Interfaces
Software
Structures
…
Requirements
Model interfaces:
Fine-grained associativity
relations among
domain-specific models
and system-level models
…
…
…
…
Development Process
Rich models:
Information objects
Parametric relations
…
Domain
2004-09
Models of varying abstractions and domains
After Bajaj, Peak, & Waterbury
2003-09
42
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
Oracle
MGC DMS
MGC BoardStation
ECAD Bound Design
ECADOriented
PDM
Level 2: Workgroup-Level PDM
• Interactive WIP design collaboration
• Focus on inter-tool information interoperability
Basic Objects
& Relations
(Macro-level associativity)
DBMS
Custom software and
person-ware (manual) glue
____________
Native Files
…
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
Oracle
PTC ProjectLink
PTC Pro/Engineer 2001
MCAD Bound Design
MCADOriented
PDM
DBMS
____________
Native Files
Oracle
EDS Metaphase
Level 3: Enterprise-Level PDM
• Major releases (to manufacturer, to supplier, …)
• Long term archiving
Enterprise
PDM
____________
Native Files
DBMS
Plus other enterprise resources:
Document Mgt. Systems
(e.g., DocuShare), …
43
Knowledge Representation Elements
Structure/Content
Definition
Languages
Graphical
Representations
Knowledge
Representation
Meta-Model
Protocol
Operations/Methods
44
Coordinated Suite of Modeling Languages
Lexical and Graphical Formulations
Constraint Schematic-S
Lexical Formulations
Subsystem-S
COB Structure
Definition Language
(COS)
Structure
Level
(Template)
I/O Table-S
Object Relationship Diagram-S
Constraint Graph-S
Express-G
OWL XML UML
STEP
Express
Constraint Schematic-I
Instance
Level
100 lbs
20.2 in
R101
Lexical Formulations
COB Instance
Definition Language
(COI)
30e6 psi
200 lbs
Constraint Graph-I
R101
OWL XML UML
20.2 in
100 lbs
OWL, XML, and UML formulations
are envisioned extensions
30e6 psi
200 lbs
STEP
Part 21
45
STEP on a Page - Explanation
46
47
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
48
STEP-Book AP210 Pro v2.1
ECAD Interfaces
Import
Export
Mentor / Boardstation
PCB & PCA
PCB & PCA
Zuken / Visula-CADIF
PCB & PCA
PCB & PCA
CadSoft / EAGLE
PCB & PCA
PCB & PCA
Mentor / PADS
PCB & PCA
GERBER
PCB only
Valor / ODB++
PCB only
AP203 / 214
PCA (& PCB)
AP210
All
All
Cadence / OrCAD translator under development
Ongoing round robbin tests
49
Schematron Diagnostics for
“Design 2L3P” XML Instance Example
50