© 2009 IBM Corporation
Holistic PLM for the development of mechatronic systems
Proof of concept:
Synchronized Mechatronics Engineering enabled by SOA
Dr. Gerd Oelerich IBM SWG, PLM Solutions Bernd Sartor IBM SWG ,PLM Solutions Hubert Aunkofer IBM SWG, Rational
Ines Merk IBM SWG, WebShpere
Michael Buchholz PROSTEP
IBM Software Group | Lotus software
Challenges in development of mechatronics systems
and how to deal with
Challenges
–
Handle complexity
–
Ensure ability to innovate
–
Increase quality
–
Improve efficiency of development
processes
–
Synchronize different lifecycles
–
Integrate different disciplines,
cultures and organizations
Product
B1 B2 B3 … F1 F2 … Aggregates F u n c ti o n s Module HW | SW | EEIBM Software Group | Lotus software
Systems Engineering for development of mechatronic
systems compliant to requirements
Benefits through Systems Engineering:
– From vertical towers to one system level
– Synchronize communication, processes, methods and tools
– Integration and reuse of deliverables
Systems Engineering principles:
– Respects relations
and dependencies between elements
– Integrates work products of different development domains
to the synthesis of the whole system
– Verification and validation of the system to ensure that all requirements are met
Requirements Functions System Architecture Software Software Electronics Electronics Mechanics Mechanics
Test & Validation Integration Product/System
IBM Software Group | Lotus software
Iterative
Process V Process V Process
MCAD E/E HW Assets SW Development Assets EE Assets SW Mgmt ???
The Solution Approach: Synchronized Change Process
Consistent rules and
processes applied by all
stakeholders
Overall status and process
information available
Collaboration and sharing of
results
Traceability of artifacts and
business objects
Reuse of artifacts
Continuous validation against
requirements on all system
levels
Change Request ECO SW ECO EE ECO HW ECO ECR Approval ProcessIBM Software Group | Lotus software
The concept to integrative change within different development domains
The concept for developing on a domain-comprehensive basis intends that the change request
on the system level is being broken down into requests for the particular domains
After the execution: the new baselines of the single domains are being aggregated to a new
overall baseline and the change request is being closed
Stakeholder Change Request Master Order System Baseline 1 System Baseline 2 HWOrder E/EOrder SWOrder Baseline 1 HWRequirements Baseline 1 E/ERequirements Baseline 1 SWRequirements Baseline 2 HWRequirements Baseline 2 E/ERequirements Baseline 2 SWRequirements Requirement-Baseline 2 Requirement-Baseline 1 SW Baseline 1 E/E Baseline 1 HW Baseline 1 SW Baseline 2 E/E Baseline 2 HW Baseline 2
IBM Software Group | Lotus software
Advantages of the integration concept
The state conditions within the domains facilitate synchronizing
the different development disciplines – ongoing visibility for easy monitoring
– control on Gates or Milestones of the development process
Easy navigation into the processes and their work products at domain level end-to-end traceability
Within the domains the, development follows specific procedure models and is being executed with
specific tools and data managers
– The EC-interface delivers specific requirements and receives the work result that is relevant for the synthesis of the complete system; sub-components and processes can be managed “freely” within the domains
– Developers use solely or predominately their standard tools
Master Order HWOrder E/EOrder SWOrder Relational Design, CAD and VPLM Design/Layout - Loops
Rational Unified Process, Activity Mgr and CM Tool
IBM Software Group | Lotus software
Synchronizing Engineering Changes in Mechatronics
Integration Architecture Overview
Team Data SmarTeam Mechanical Authoring ERP Team Data MatrixOne ClearCase ClearQuest Master Order HW Change Order
E/E Change Order SW Change Order WAS/WID/WPS ECR Process ECO Management Build Forge E-CAD
System Level Integration Level
Application Level
BOM Software Authoring Electrical Authoring Mechanical Authoring
Federated BOM SW BOM E/E BOM Mech. BOM
IBM Software Group | Lotus software
System Level - ENOVIA Reference architecture
Bidirectional PROSTEP
Adaplet (Web Services)
ENOVIA PROSTEP Adaplet for OpenPDM
IBM Software Group | Lotus software
Using modular Web Services for the
integration of the SW domain
Modular Web Services have been developed which are
hosted by MatrixOne and ClearQuest resp. and are used in
different phases of the scenario
check out and download files related to File service, check out
Upload and check in files, connect to object
File service, Check in
Receives a new identification number from the MOne numbering generator Receive number
Connects objects through spec. relationship
Connect objects
Updates attributes of an existing object Update Object
Creates an object in MOne Create Object
MatrixOne
Update meta data of a record Update record
Set the state of a record Set record state
Link to records Link records
Provide state of a record Provide record state
Create record of given type Submit record
ClearQuest
Description
Method Name
IBM Software Group | Lotus software
Integrating the mechanics domain
We operate a Team Data Manager – which is
ENOVIA SmarTeam – for organizing the engineering procedures in
the mechanical domain.
The information flow towards SmarTeam goes through the IBM
WebSphere Process Server and the ProSTEP OpenPDM gateway.
IBM Software Group | Lotus software
Scenario Overview
Analyse Requirements Set up ECO structure Promote Master ECO
Perform transfer of ECO and affected part
OpenPDM
Navigate to affected CAD models, perform
change,
Promote ECO, update ECO in ENOVIA
provide new BOM
Set up SW project, assign team, Rational ClearQuest Perform change Build SW Rational ClearCase Build Forge Promote ECO, update ECO in ENOVIA,
provide new SW part
Rational ClearQuest
Check out schematics, Perform change, generate el. BOM
ECAD
Import el. BOM
Aggregate system BOM, transfer BOM to SAP,
complete ECOs
Incorporate material masters and BOM SW ECO
EE ECO
Mech. ECO, Part
IBM Software Group | Lotus software
State display on system level
ECO state on domain level
ECO state on domain level
IBM Software Group | Lotus software
ECO in the mechanical domain system
A new ECO is created in the domain data manager and
related information is attached.
A new ECO is created in the domain data manager and
related information is attached.
A team leader can use the hyperlink to switch to the
system context. .
A team leader can use the hyperlink to switch to the
system context. .
IBM Software Group | Lotus software
ECO in the SW domain system
Again, a local ECO is initiated from the system level and related information is
forwarded to the SW configuration management tool.
Again, a local ECO is initiated from the system level and related information is
forwarded to the SW configuration management tool.
Requirements that were assigned to the SW Change Order are forwarded to the domain system for validating the
deliverables.
Requirements that were assigned to the SW Change Order are forwarded to the domain system for validating the
IBM Software Group | Lotus software
The federated BOM
Root node Root node Electrical parts Electrical parts Mechanical parts Mechanical parts SW part SW part
IBM Software Group | Lotus software
Values of a holistic Product Lifecycle Management in the
mechatronics engineering
Reduce development costs through process automation, flexibility and
inter-domain collaboration
Accelerate development cycles through synchronization, faster feedback
and increased reuse of existing solutions
Increase product quality through
–
standardized development processes that ensure consistent results
–
improved reuse of approved assets
–
check and test results on all levels against initial requirements
Manage complexity through traceability and a single federated system
BOM
Protect and capitalize investments through leveraging of existing domain
specific knowledge and methodologies
© 2009 IBM Corporation
