Professional Documents
Culture Documents
Key c ustomers
3 6/23/16
Sodius’ Layered Technology
Get Your Data to Where it is Needed
Data Integration
RLIA Windchill®
Integrates Windchill PLM with CCM ALM via OSLC
SE-Collab®
Share and annotate complex systems engineering artifacts
Engineering Knowledge Integration
Store and spread systems engineering artifacts securely
4 6/23/16
Example Information Exchanges
Requirement Negotiation
between an OEM and Supplier
Requirement Synchronization
• Automotive OEMs, Tier 1s and suppliers are continuously exchanging requirements/stakeholder
requests.
• Requirements Management Tools and processes vary considerably from BU to BU (internally) and
between organizations. It requires support teams in each BU (5 peoples min.) to import and check
requirements exchanges.
• A harmonized automated tooling & method is significantly help to remove this drawback and
enable sync with the corporate RM/CM system
DOORS
BU
1
BU
2
…
BU
OEMs n
Stakeholder Request Supplier
Round Trip Process
…
RM Data Mapping
• Typically, the exchange is based on custom attributes that have to be fed
(create and update) from both parts to feasibility/maturity/acceptance of
items
Mapping Rules
DOORS
Reuse Your Data in the Format You Need
Get Your Data No Matter Where it was Authored Get Your Data No Matter Where it was Authored
Data Access Data Transformation Data Access
Example of Automated Collaboration Service
DOORS to Integrity Synchronization
MDWorkbench
DOORS
Service Launcher
Server side
MDWorkbench Web Services Layer
DOORS
CLIENT
Run
Mapping
DOORS
SERVER Rules Integrity
Doors2Integrity SERVER
Mapping between APIs
SODIUS
DOORS Structure
Mapping Integrity Structure
Formal Module Processor
Requirements Document
Object executes Requirement
System Attributes Category
Object Heading Title
Mapping
Object Text Content.fva
profile
… Safety
Custom Attributes …
ObjClass
Stakeholder Request Document
Safety Level
… Stakeholder Request
Exchange Scenario
1
6
DOORS Module DOORS Module Updated
3 4
Integrity Requirements Integrity Requirements
Document Document Editing
DOORS to Integrity Exchange Platform
1
3
2
Mapping features
MERGING
PTC
Windchill
System Architect / Mega
SA
UML Base Classes NOV-2 Stereotypes
«extends»
«metaclass»
ArchitecturalDescription
Package
owningArchitecture
1
1
ownedMember products
*
«metaclass»
ArchitecturalProduct
PackageableElement
«extends» CompositeStructureModel
1
«metaclass»
StructuredClassifier
NodeRelationshipDescription
«extends»
«metaclass»
Node
1
Class
conductedAt
whole
1
part
1
class
type
1
1
*
*
*
«extends»
role
«metaclass»
NodeAssemblyUsage
Property
connectionContext
1
source
1
target
1
source
1
target
*
*
«extends»
«metaclass»
InformationExchange
InformationFlow
«extends»
«metaclass»
NestedConnectorEnd
ConnectorEnd
supportingNeedlines
*
end
NodeConnectorEnd
realizingConnector
2
ownedConnector
Needline
1
«extends»
«metaclass»
1
NodeConnector
*
Connector
«extends» activityConducted
«metaclass»
OperationalActivity
1
Activity
«extends»
«metaclass»
NodeHasBehavior
*
Dependency
*
«metaclass»
NamedElement
*
*
client
1..*
supplier
1..*
NAF Metamodel
MEGA
Defect
Tracking
(Shared)
Tasktop Sync
Defect gives instant Defect
Tracking visibility Tracking
(Supplier) (OEM)
Intelligent queries only update defects when appropriate,
and only publish allowed information
Exchange Maturity Level
3. Model Exchange
0. No Exchanges
The Future of Exchanges
OEM Supplier
Present
OEM Supplier
Future
Owner A
Owner B
Owner C
Strategies For Model Exchange
• Expose as little as possible
– Each owner should
explicitly expose elements
for others to use
Private Elements
Public Elements
Strategies For Model Exchange
• Control dependencies
– Two-way bad, one-way good
Collaborative Model Sharing
My Virtual Catalog of
• Heterogeneous engineering toolset « engineering » data
(tools, version of tools and their
customizations) exists inside
organization and their partners
• We work on capabilities to
simplify/enhance collaboration in this
context
Authors
CM
Associate Publish Create Feedback linked
Requirements
CM Project Data Review to CM system
Architectures
Stakeholders/Reviewers
Review and provide
comments
Web-based publish/feedback collaboration platform
for the French Ministry of Defense (DGA)
• Proving access to model information across organizational boundaries allows
managers to gather efficient stakeholder feedback
Requirements
SE-Collab
Classification &
Transformation
Architectures
Design Data
publish review
review
publish
PROVIDE CONTENTS
SE Authors Reviewers
(Desktop Tools) (Web)
PROVIDE FEEDBACK
HTTPS
Archive Archive
Connected or disconnected
mode allow different mode REVIEW
according network
continuity configurations AREA
Web Portal Content (1/6)
• A main dashboard per project Data are stored into
container Projects
We contribute to
We share Designs Reviews
A Review
defines
Contributors
and
Resources
Reviews can be
exported as Reports
Architecture Overview
• Full HTTPS/REST, RDF + OSLC Implementation (Open-Services for Life Cycle
Collaboration)
• Connector Extensibility / Web UI Navigation Customization
• Repositories
• RTC Repository (at DGA)
• Standalone Apache Jena Repository
• Add Links between artifacts by content analysis (e.g DOORS/MEGA/SA Links)
Extensibility
New
connector RDF/Sparql
Manager
Apache
Jena Repository
XML and SysML Sync
• During design, the data exchanged between partners
throughout external interfaces of a system are described by a
set of XML files
– They have to be integrated in the SysML models manually.
– Impact Analysis for each iteration step is complex to handle.
Model
Complexity
Integrator Time
Partner 1 Libraries of Consuming
“technical” types
Manual
Errors
Partner 2
N+1
versions
SysML & XML-Based
Tooling Interoperability
• Integration of XML data and Impact analysis when
importing a new version
assistance to iterations of datatypes libraries
Libraries of types
«Block» «Block»
Demande_Prise_Vue Demande_Image
Parts Parts
Angle_Prise_Vue:AngleType
Client:ClientType Direct Suspected Angle_Image:AngleType
ID:Int
ID:Int
Impact Impact Position_Image:PositionType
Position_Prise_Vue:AngleType
OEM 1 1
1 itsCatalogue:Catalogue
itsRechercheImgExistante:RechercheImgExistante
Operations Operations
1 Consultation_Catalogue():void Reception():void
itsClient:Client Demande_Image:Deman
de_Image_Type
Operations
Demande_Image:Demande_Image Demande_Image:Demande_Image
Elaborer_Demande_Prise_Vue():void
Demande_Prise_Vue «flow»
Demande_Prise_Vue:Demande_Prise_Vue Demande_Prise_Vue:Demande_Prise_Vue
«flow» Image
Image:Image_Type Image:Image_Type
«flow»
v1 v2
Manage Iterations
Conclusion
• Process drives everything
• Exchanges will increase in complexity
• Exchanges will increase in frequency
• Models will rule the world