ISO STEPAP233 Transition Development to Enablement

1
ISO STEP-AP233 Transition Development to
Enablement

• Harold P. Frisch NASA Emeritus, AP233 co-lead
• Charlie Stirk - CostVision Inc.
• With special thanks to
• David Price Phil Spiby
• at Eurostep

2
Agenda

• Development
• Background on AP233 and SE standards
• Relationship to other STEP standards
• AP233 detail _at_ executive level
• Enablement
• Implementation approaches
• UML/SysML based
• STEP/EXPRESS based
• New implementations possibilities

3
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

4
AP233 Users Content Picture
Analysis Tools
PDM Tools
Schedule Tools
Documentation Tools
V V Tools
Program Management Organizational
Structure Schedule Project Management Inf Work
Break Down Structure Project Breakdown Project
Mgmt Resource Inf Product Data Management
Configuration Management
Risk Issues
Authorization/Review
System Reqts/Design Requirements and
MOEs Allocation of Requirements to model
elements Trade Studies Function Based
Behavior State Based Behavior Interface to
Analysis Verification and Validation
Risk Issues Authorization/Revie
w
WBS Tools
Trade Tools
CM Tools
Reqt, MOE Mgmt Tools
Strategic Planning Tools
Risk Tools
Issue Tools
Modeling Tools
5
AP233 Participants

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

6
AP239 PLCS Relationship
They share a common core!
AP239
WBS
Classification
V V
Product Structure
State Machines
Change Management
Approvals, Security, Status
Function Diagrams
Requirements Management
Risk Management
Schedule
Activities
Link to Analysis
Organizations
Property
7
AP209 Engineering Analysis Relationship
AP209
V V
Classification
Schedule
Product Structure
Construction History
State Machines
Change Management
GDT Presentation
Function Diagrams
Approvals, Security, Status
Composite Structure
Risk Management
Analysis Management
GDT
Requirements Mgmt.
3D Models
Drawings
Property
8
AP210 Electromechanical Relationship
AP210
V V
Multi-level Tech
Classification
Constraints
Netlists
Schedule
Product Structure
Production Rule
Change Management
State Machines
Interfaces
Approvals, Security, Status
Function Diagrams
Evaluation Results
Requirements Management
Risk Management
Requirement Allocation
Link to Analysis
Component Models
Organizations
Simulation Models
Property
Activities
Design Models
9
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

10
AP233 - SysML - OWLLanguages with Common
Semantics
OWL Ontology Modeling Language
REPRESENTAT ION
PRESENTAT ION
SysML Graphical Modeling Language
STEP AP233 Information Modeling Language
11
DoD and ISO 10303 STEP

• Kenneth Krieg, US Under Secretary of Defense for
  Acquisition, Technology and Logistics (DoD USD
  ATL)
• Memorandum Standard for the Exchange of. Product
  Model Data (STEP) --- ISO 10303, June 23, 2005
• Recommends
• Implementing an approach for managing digital
  product/technical data across DOD
• Ensure product model data meets ISO STEP
  requirements
• Adoption of ISO 10303 to enhance interoperability
• Ensure procuring activities plan, purchase and
  accept delivery of product/technical data only in
  digital formats specified by the guidance on
  contracts awarded

12
STEP for DOD Acquisition Cycle (Dr. Raj Iyer)
13
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

Analysis
Requirements/Concept
Lifecycle Support
Manufacturing
Detailed Design/BoM

• 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

• Work activities and resources
• define
• justify
• approve
• schedule
• feedback

Components Assemblies

• 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
AP2122001, Electrotechnical design and
installation
AP2092001, Composite and metal structural
analysis and related design
AP233, Systems engineering data representation
AP239, Product lifecycle support
AP219, Dimensional inspection
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 Paramete
rs for parts and functional objects
Make or buy Macro process planning
Edition 3 in process to add gear features
AP2242001, Mechanical product definition data
for process planning using machining features
Edition 2 in process
AP2102001, 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
Related Standards
Cross Process Utility

• 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 Allwei
ler 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
AP2322002, Technical data packaging core
information and exchange
AP2322002, Technical data packaging core
information and exchange
AP238, Computer numerical controllers
Edition 2 Tolerances Construction
history Colors Layers
Geometry Dimensions Material
Components Assemblies
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
14
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/n
iddesc.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
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 Allwei
ler Marine Q 200 m3/h Ps bar 3
bar RPM 1750 Power 23 kw TMAX 250

• Connectivity
• assembly
• penetrations
• ports

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

AP2272001, Plant spatial configuration piping
systems
AP227 Edition 2draft, 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 2draft, Plant spatial
configuration - cable trays
AP227 Edition 2draft, Plant spatial
configuration - mechanical systems
ISO 15926 (Oil and Gas)
AP215IS, 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)

• 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

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
AP2122001, Electrotechnical design and
installation
Technical Description
AP218IS, Ship structures
15
PDES, Inc. Digital Enterprise Phase
Envisioned Tool Environment
Digital Enterprise
Model Based Enterprise
Systems Engineering
MBe
MBm
MBs
engineering
manufacturing
sustainability
Long Term Data Retention
Engineering Analysis

• Digital Manufacturing
• Product Modeling
• Process Modeling
• Information Modeling

• 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
16
AP233 Enablement PhaseNo open technical issues

• Development team transitioning to a support and
  maintenance role.

Enablement activities will test and validate
capabilities while AP233 is in the ballot
resolution and Draft International Standard
(DIS) preparation process.
17
What Does AP233 Enable?

• Program management
• Issue
• Activities
• Approvals
• Risk
• Probability Consequence
• Source Impact
• Contingency plans
• Project
• Organizational structure
• Project breakdown
• Schedule
• Work structure
• Management information resources

• System modeling
• Decision support
• Requirements management
• Measures of effectiveness
• Analysis interface
• Verification Analysis
• Justification
• System structure
• Product data management
• Breakdown
• Interface
• System behavior
• Function based behavior
• State based behavior

18
AP 233 Extendibility

• Through External_class references to
  External_class_library
• Adds semantics to basic schema concepts
• Can tailor to specific domain or business
• Can standardize the external libraries

19
Traceability enabled by Interfacing Core
Capabilities
20
Approaches to Implementation

• Representation AP233 in UML
• Generate XMI file from UML
• Transform XMI to STEP XML file (Part 28)
• Development of Data Exchange Sets (DEX)
• Like AP239 Product Life Cycle Support
• Standardization through OASIS
• Both use OWL for external classes

21
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

22
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
  www.ap233.org

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

24
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

25
Context Diagram for Systems Engineering Standards
DoDAF

• This shows only one thread through these
  standards, others are necessary as well.

CADM
26
DoDAF Views
27
Mapping Documentation

• Document as a Web site in the style of a
  programmers guide
• Audience
• Audience is software developers
• No previous knowledge of AP233 is required
• UML diagrams and XML Schemas used to explain how
  to write a converter
• Approach
• Develop standalone AP233 document that is
  independent of DoDAF/CADM mapping
• Develop document for each DoDAF View and link
  into the AP233 document
• Makes the AP233 documentation reusable for a
  similar project on SysML, MoDAF, etc.

28
Published Deliverable

• Web site documenting AP233 and CADM/AP233 mapping
  http//www.exff.org/ap233

29
Scripting API Implemented

• Application Programming Interface (API) in simple
  and accessible language
• Programmer must know concepts, attributes and
  relationships in AP233
• Ruby API code generated from AP233 EXPRESS ARM
• Available as open source from www.exff.org

30
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

31
AP 239 Product Life Cycle Support

• PLCS is STEP AP239
• PLCS became ISO standard 9/01/2005
• Funding and implementation led by NATO allies
• Many early AP233 models were incorporated into
  PLCS (e.g. Requirements)
• Extending through DEX
• Web Services Definition Language (WSDL) interface
  developed for PLCS
• (www.plcs-resources.org)

32
PLCS enables requirement management through life

• AP239 shares common modules with AP233 Systems
  Engineering
• Aim is to support requirements trace from
  pre-design through to maintenance and disposal
• UK MOD has funded demonstration project for this
  capability with BAE Systems

33
PLCS provides full history to support
optimization and change over time

• In the PLCS models it is assumed that any value
  supplied
• E.g. a property such as mean time to perform a
  task
• may have multiple values over time
• where each value could have been
• supplied at different times
• by different people
• subject to approval
• subject to security classification
• associated to a justification/probability/risk
• This requirement has been recognised from the
  start of modelling
• Improve CM of support information by use of
  single source Assured Product and Support
  Information (APSI)

34
PLCS - Life Cycle PDM Capability (1)

• PDM Schema already supports automated exchange of
• Part id and properties
• Associated documents and files (incl. CAx)
• Product structure
• Product (and document) approval status
• This is already in production use by
• US Aerospace and Defence prime contractors (via
  AP203)
• German/Swedish/French Automotive sector (via
  AP214 cc6)
• Eurofighter Typhoon PDM partners
• .. A powerful and proven capability for
  Configuration Management of a complex product
  design

35
PLCS - Life Cycle PDM Capability (2)

• AP239 has added
• Classification, supported by reference data
  libraries
• Product_as_individual (planned and realized) -
  UID
• Product breakdowns (system, physical, functional,
  zonal and hybrid)
• Text based requirements (from AP233)
• Extended property capability
• Interfaces
• Attachment_slot
• Message, Envelope (similar to ENGDAT)
• Information Rights
• A powerful capability for Life Cycle
  Configuration Management of Assured Product and
  Support Information

36
AP233 and PLCS support full life cycle processes
Request
Database
Database
Response
Taxonomy
233
PLCS
AP233 Data File
References for added semantics
Database
37
PLCS - Reference data

• What is it?
• Values for attributes that are agreed and defined
  in advance of use
• E.g types of task, grades of people, types of
  products, types of document
• E.g. NATO Stock Number classifications
• Why use it?
• Because it improves reliability and effectiveness
  of exchange
• Because it can be extended
• To add to the scope of the standard
• To provide project specific functions
• Because it supports re-use of values from
  existing standards
• Idea proven in Oil and Gas industry

38
PLCS Data Exchange Sets

• DEXs are
• Subsets of the AP239 Information model
• Selected to meet a specific data exchange need
• Built from relevant modules
• Supported by Usage Guidance, population rules and
  Reference data
• Can be refined from other DEXs
• DEXs may be standardized at any level (work
  group, company, project, organization, national,
  international)
• DEXs enable
• Consistent implementation of AP239
• Data consolidation through time

39
Current PLCS DEX developments

• Product as individual
• Product breakdown for support
• Maintenance plan
• Task set
• Operational feedback
• Fault states
• Work Package Definition
• Work Package Reporting
• Plus a range of developments which apply
  additional constraints and reference data based
  on generic DEX

40
(No Transcript)
41
Update Implementations

• Early pilots used AP 233 Working Draft 1 and
  Working Draft 2
• Found gaps and fixed AP233
• AP 233 now in Committee Draft (CD) on way to
  becoming Draft and then International Standard
  (IS)
• Prior mappings will need updating

42
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

43
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)

44
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

45
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

46
Backup Slides
47
(No Transcript)
48
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

49
Ap233 - Systems Engineering

• ISO 10303 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
  10303-433
• System behaviour
• System structure
• System modelling
• Decision support
• Requirements, analysis, trade studies
• Program and project management
• Verification and validation
• Risk management
• Issue management

50
Ap233 Enabling Capability Breakdown
51
AP 210 Requirements Traceability
Requirements Decomposition
Physical Assembly Decomposition
Physical Interconnect Decomposition
Requirement To Assembly
Requirement occurrence
Requirement To Interconnect
Functional Path Subset To Assembly
Physical Occurrence
Layout Occurrence
Layout Network Subset to Implement Node
Function to Layout
Physical Macro Component Definition
Layout Macro Template Definition
Note Details of Recursive Definition Omitted for
Clarity Pin Mapping in Library Omitted for
Clarity
52
DEX Architecture Overview
Business Dependant
Domain Independent
Concept driven PLCS Exchange Functionality
Business Driven PLCS Exchange Functionality
DEX
Business DEX
may be subset of
What to be exchanged defined by Business objects
collects 1?
collects 1?
Defined by
Capability
Business Object
Typical PLCS functional units
Business Specific Functional units
may refer to functionality defined in
Business Templates represent either the object or
one or more object attributes
Templates may be hierarchically defined through
the use of other templates
represented by 1?
represented_by 1?
may be represented_by 0?
Template
Business Template
Business Specialised Functional Unit
instantiation
Functional unit Instantiation
contains 0?
53
Business DEX Architecture
Business Dependant
Scope Introduction Terms Business
overview Information model Business
Objects Dependent templates1 Business Reference
Data2  Schema
Business DEX
Collects 1?
Business Templates represent either the object or
one or more object attributes
 1Note that the current DEXlib format states
dependent capabilities.  2Note that the
current DEXlib format states Model
reference data.
Introduction Scope Business requirements Informati
on model Business templates
Business Object
may be represented by 1?
Description Model Diagrams Input
parameters Reference parameters Instantiation
path Instance diagrams Characterizations
Business Template
Template
May refer to
54
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?
55
Current PLCS Implementations

• Visby Corvette
• Gripen pilot project
• Norwegian frigate
• Extending to other NDLO programmes
• Being promoted actively for JSF
• Eurostep Share-A-Space
• BAE Systems Land Systems Hagglunds
• UK MOD pilots for RAF LITS and Navy UMMS
• Logistics Coherence project
• US DoD ELITE project for UH-60 helicopter
• Extending to other service linked to UID
• Plans for HMMWV and Bradley

56
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)