1. AP233 Systems Engineering
System-of-systems engineering requires
Greater collaboration and tool interoperability, and …
Using robust modeling techniques for describing systems architectures
Request
Response
System
Model
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. Standards and SE data
INCOSE - International Council on Systems Engineering
Model-Based Systems Engineering Working Group
Model-Based SE Semantic Dictionary and Concept Model
Group work results in SysML/AP233 and alignment activity
DoDAF - DoD Architecture Framework
Defines standardized views of systems information
CADM = Core Architecture Data Model
Underlying data element model in XML
SysML - from Object Management Group
Provide a standard modeling language and notation for systems engineers
AP233 Systems Engineering and Design Representation
Defines a neutral information model for complex systems engineering structures

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

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

6. ISO 10303, STandard for the Exchange of Product model data (STEP)
USPRO –
Aircraft Product Model Data Exchange Standards
Requirements/Concept
Analysis
Detailed Design/BoM
Manufacturing
Lifecycle Support
Equipment Coverage
Power-transmission
Electric Machinery
Power-generation
Power-distribution
Control Systems
Electric Light and Heat
Electrotechnical Systems
Plants
Buildings
Transportation Systems
Data Supporting
Functional Decomposition of Product
Terminals and Interfaces
Cable Tracks and Mounting Instructions
3D Cabling and Harnesses
Assemblies
Components
Work activities and resources
approve
justify
define
feedback
schedule
Configuration
as-built
design configuration
design requirements
as-maintained
Operating states
Usage
Behavior
Support
equipment
personnel
facilities
diagnostics
Electrotechnical Plant
Unit, e.g., Engine Control System
Plant, e.g., Automobile
Subunit, e.g., Ignition System
Administration
Planning
Archiving
Execution
System definition data and configuration control
Conformity to the concept of a system
Requirements, requirement analysis, and functional allocation
Functional, functional analysis, and functional behaviour
Trade studies for decision support
Physical architecture and synthesis
Shape
Associated Finite Element Analysis (FEA)
Analysis results
material properties
Tolerances
Dimensions
Geometry
Inspection processes
AP233, Systems engineering data representation
AP209:2001, Composite and metal structural analysis and related design
AP212:2001, Electrotechnical design and installation
AP219, Dimensional inspection
AP239, Product lifecycle support
Assemblies
Components
Machining features
Assembly information
Explicit geometry
Tolerances
Physical layout of the circuit card assembly
Description of logical connections among the functional objects
Physical interconnections
Packaged parts
Configuration management
Parameters for parts and functional objects
Edition 3 in process to add gear features
Macro process planning
Make or buy
Edition 2 in process
AP224:2001, Mechanical product definition data for process planning using machining features
AP210:2001, Electronic assembly, interconnect, and packaging
Configuration controlled exchanges between Product Data Management (PDM) systems
Links multiple formats
Geometry
Dimensions
Material
Manufacturing
Analysis
Design
Support
Cross Process Utility
Related Standards
Mirco process planning
Automated NC generation
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
Mfg: Allweiler Marine
Shaft: Stainless
Impeller: Bronze
RPM: 1750
Ps bar 3 bar
Q: 200 m3/h
TMAX 250
Power: 23 kw
FW LT Pump
FW LT Pump (Spare)
FW HT Pump
FW HT Pump (Spare)
Mechanical parts machining
electro discharge machining
turning
milling
Pipe bending
Sheet metal bending
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
Construction history
Tolerances
Layers
Colors
Assemblies
Components
Material
Dimensions
Geometry
AP203, Configuration Controlled 3D designs of mechanical parts and assemblies
Maco process planning
machining
fabrication
ISO (Parts Library Exchange)
Mechanical parts
Structural steel
Sheet metal bending
Pipe bending
AP240, Process plans for machined products

7. ISO 10303, STandard for the Exchange of Product model data (STEP)
TC 184/SC 4/WG 3/T 23 Ship Team Standards
System definition data and configuration control
Conformity to the concept of a system
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
AP 239 Product lifecycle support
Navy/Industry Digital Data Exchange Standards Committee
Marine e-business Standards Association
Ship Structural Envelope
Distributed Systems
Equipment/Subsystems
Surface, wireframe and offset point representations
Design, Production and Operations lifecycles
Hull form geometry
Main dimensions
General characteristics
Hydrostatics
Major internal surfaces
Intact Stability tables
AP216:2003, Ship moulded forms
Connectivity
penetrations
assembly
ports
Pipe Flow Analysis and Sizing
Pipe Stress Analysis
Connectivity
penetrations
assembly
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
Mfg: Allweiler Marine
Shaft: Stainless
Impeller: Bronze
RPM: 1750
Ps bar 3 bar
Q: 200 m3/h
TMAX 250
Power: 23 kw
FW LT Pump
FW LT Pump (Spare)
FW HT Pump
FW HT Pump (Spare)
Configuration Management of Product Structure
Versioning and Change Tracking
Bill of Materials
Configuration Management of Product Structure
Versioning and Change Tracking
Bill of Materials
2-D and 3_-D Shape Representation
Solid Model Presentation
Diagrammatic Presentation
Interference Analysis
2-D and 3_-D Shape Representation
Diagrammatic Presentation
Interference Analysis
Solid Model Presentation
AP227:2001, Plant spatial configuration – piping systems
AP227 Edition 2:draft, Plant spatial configuration - HVAC systems
ISO (Parts Library Exchange)
Loading conditions
Connectivity
assembly
ports
penetrations
Connectivity
assembly
ports
penetrations
Compartments
properties
types
coatings,
(shape,
access….)
adjacency,
Zone Boundaries
Controlling Access
Machinery Compartments
Cargo Stowage
Design Authority
Common Purpose Spaces
Crew Occupancy
Configuration Management of Product Structure
Versioning and Change Tracking
Bill of Materials
2-D and 3_-D Shape Representation
Solid Model Presentation
Diagrammatic Presentation
Interference Analysis
Configuration Management of Product Structure
Versioning and Change Tracking
Bill of Materials
2-D and 3_-D Shape Representation
Diagrammatic Presentation
Interference Analysis
Solid Model Presentation
Cargoes
weight,
assignment to compartments
centre of gravity
Stability
damaged
intact
into Spatially Bounded Regions
General Subdivision of a Ship
AP227 Edition 2:draft, Plant spatial configuration - cable trays
AP227 Edition 2:draft, Plant spatial configuration - mechanical systems
AP215:IS, Ship arrangement
ISO (Oil and Gas)
Ship Structural Envelope (hull forms, arrangement, structures)
Distributed Systems (electrical, piping, HVAC, cable ways, mechanical systems)
Mission Equipment/Subsystems (library and catalog parts)
Production Design Data
Equipment Coverage
Power-transmission
Electric Machinery
Power-generation
Power-distribution
Control Systems
Electric Light and Heat
Electrotechnical Systems
Plants
Buildings
Transportation Systems
Data Supporting
Functional Decomposition of Product
Terminals and Interfaces
Cable Tracks and Mounting Instructions
3D Cabling and Harnesses
Configuration Management
Approval Relationship
Class Approval
Change Administration
Promotion Status
General Characteristics
Production Engineering Data
Product Structure
Space
System
Generic Product Structure
Assembly
Connectivity
Electrotechnical Plant
Unit, e.g., Engine Control System
Plant, e.g., Automobile
Subunit, e.g., Ignition System
Weight Description
Structural Parts
Feature
Opening
Edge Content
Plate
Profile Endcut
Profile
Hull Cross Section
Geometric Representations
Surfaces
Complex Wireframe
Wireframe
Solids
Technical Description
AP212:2001, Electrotechnical design and installation
Ship Product Model Data Exchange Information
STEP -
USPRO –
Ship STEP -
AP218:IS, Ship structures

8. PDES, Inc. Digital Enterprise Phase
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

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

10. SysML-AP233 Converter SysML concept scope
Requirement-derivation, -decomposition
System-decomposition, -satisfies requirement
Defined AP233 in terms of widely used UML and XML representation rather than niche STEP/EXPRESS
Implementation flow
SysML tool exports XMI file
XSLT translates XMI to AP233 XML file
AP233 XML file import into Demonstrator application
Demonstrator application available on

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

12. DoDAF CADM/AP233 Project Purpose Deliverables
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

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

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

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

16. SysML - Systems Modelling Language
The SysML Partners collaborated to define a modeling language for systems engineering applications, called Systems Modeling Language™ (SysML™). SysML customized UML 2.0 in order to support the specification, analysis, design, verification and validation of complex systems that include hardware and software components.
The following are within the scope of SysML:
Structure
e.g., system hierarchies, interconnections
Behavior
e.g., function-based behaviors, state-based behaviors
Properties
e.g., parametric models, time variable attributes
Requirements
e.g., requirements hierarchies, traceability
Verification
e.g., test cases, verification results

17. Ap233 - Systems Engineering
ISO is an International Standard for the computer-interpretable representation of product information and for the exchange of product data. The objective is to provide a neutral mechanism capable of describing products throughout their life cycle. This mechanism is suitable not only for neutral file exchange, but also as a basis for implementing and sharing product databases, and as a basis for archiving.
The following are within the scope of ISO/CD-TS :
System behaviour
System structure
System modelling
Decision support
Requirements, analysis, trade studies
Program and project management
Verification and validation
Risk management
Issue management

18. Ap233 Enabling Capability Breakdown

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

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

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

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

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

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

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

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

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

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

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

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

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

32. Integrated PLM SOA Environment
3. Enterprise Collaboration - Portals and dashboards to Applications
2. Enterprise Process Management – Cross-application processes
1. Enterprise Integration - Management of PLM and Enterprise Information
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
Program and Portfolio Management
Requirements
Management
Data Management
Data Management
Data Management
Data Management
Enterprise PDM
ERP
EAM
Other Enterprise Applications
Mechanical Authoring
Electrical Authoring
Software Authoring
Analysis & Simulation
Storage
Servers
Software 32

33. 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
Web Services / Interoperability
Eclipse to Open
UDDI
SOAP
W3C XML
SOAP4J to Open
Open Systems
OMG PLM Services
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
For over 20 years, IBM has worked with our customers, industrial consortia, standards development organizations, technology services teams and our software partners, such as Dassault Systemes to develop and implement open CAD/CAM/PDM standards in our PLM product portfolio (CATIA, ENOVIA and SmartTeam).
Over these years, IBM PLM has collaboratively influenced and shaped the industry, engineering and IT standards for PLM. IBM has had either leadership or key participation in over 30 standards related organizations and committees since the 1980‘s. On behalf of IBM‘s customers, partners and IBM as a manufacturer, IBM influences the direction and decisions of these organizations with the clear goal of developing standards to benefit the industry. IBM invests directly via membership fees, special projects, technology and has over 20 senior professionals who continue to play a significant role in many open, PLM related standards bodies.
Recently IBM has been involved with defining 11 published standards and are colloborating on 7 other standards under development. These include:
PLM Services 1.0 (published) Scope: PDM based on ISO STEP AP 214 Conformance Class 6 & 8.
PLM Services 2.0 (under development) Scope: Engineering change management
STEP AP 214 Conformance Class 1, 2, 6 & 8 (published) Scope: Geometry & PDM, implemented in CATIA, ENOVIA and by other ISVs.
STEP AP 214 Conformance Class 21 (under development) Input from ProSTEP Engineering Change Management project
STEP AP 203 E2 (published) Scope: Geometry & PDM, Implemented in CATIA, ENOVIA and by other ISVs.
STEP AP 219 (under development) Scope: Dimensional Inspection, Impacts CATIA and DELMIA
STEP AP 233 (under development) Scope: Systems Engineering, based on SysML & PDES Inc project.
SysML (published) Provides input to ISO STEP AP 233
STEP AP 239 (published) Scope: Product Life Cycle Support, now under OASIS
STEP Parts 108, 1050, 1051 (published) Scope: Dimensioning, Tolerancing, Parametrics & Constraints, Impacts CATIA and DELMIA
PDF/A (published) Scope: PDF for archival, for 2D documentation
PDF/E (under development) Scope: Adobe 3D, for 3D documentation
3D Presentation of product specification (published) Scope: 3D presentation of STEP data
Long term data retention (LTDR, LOTAR) Scope: Long term data retention, product data archival
STEP AP 209 (published) Scope: Analysis of metallic & composite structures.
STEP AP 210 (published) Scope: Electronic assembly, interconnect & packaging
STEP AP 212 (published) Scope: Electotechnical design and installation
IBM has also invested in a european based interoperablity center and recently announced it‘s commitment to an open, services oriented architecture IBM plans to leverage this architecture to integrate the various disparate PLM tools, technologies and components to enable a collaborative product development and support ecosystem.
IBM understands the need for standards.
The market place doesn’t want to be locked up in proprietary systems; standards protect their investment.
The market wants operate in heterogeneous environment and they need integration based on standards.
Global supplier network, and mergers & acquisitions have made their environment even more heterogeneous.
Standards avoid point-to-point, custom integrations that need continual maintenance and support.
In the end, IBM understands that companies (IBM customers) drive open standards in PLM. IBM’s role and investment is as a participant in these standards consortia and IBM will continue to support these founded and managed bodies (e.g, PDES Inc, ProSTEP iViP, …).
Dr. Vijay Srinivasan Vice chair of US delegation to ASME ISO standards committee (TC 213), IBM representative at ISO STEP (ISO TC 184/SC 4) committee. Participate and influence in open PLM standards on behalf of IBM.
PDES Inc, Board member: Jim Denzak, Technical Advisory Committee member: Vijay Srinivasan
Enterprise Interoperability Center (Vice-chair: Jochen Friedrich)
ProSTEP iViP, IBM on Technical Steering Committee membership
Other IBM Industry and PLM related standards leaders include Buddy Raines/Poughkeepsie/IBM, Chae H An/Watson/IBM, Fatema Maher-Khorshed/Germany/IBM, Frank Hendricks/UK/IBM, Jens Erb/Germany/IBM, Jim Denzak/Rochester/IBM, Jochen Novaes/Watson/IBM, Mark Holt/Charlotte/IBM, Mezjan J Dallas/India/IBM, Naguib Attia/Charlotte/IBM, Peter Kluge/Germany/IBM, Peter Robison/UK/IBM, Robert L Norton/Westford/IBM, Vijay Srinivasan, Laurent Balmelli
Friedrich/Germany/IBM, Jonathon Siudut/Endicott/IBM, Karen Newman/Southfield/IBM, Larry Liu/Baltimore/IBM, Marcos
Over 160 business integration technology patents
First integrated private UDDI directory
First Web Services Gateway

34. Standards across PLM Lifecycle (Ministry of Defense)

35. 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,…

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

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

38. AP233 Concept Model