Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
Reset the slide back to its
Change the slide layout
via menu bar:
Alternating between white and black
slide layouts via menu bar:
Introducing AutomationML in a heterogeneous software
tool landscape – a success storyJoachim Burlein, Matthias Rassl, Dr.-Ing. Nicole Schmidt
Tool chain
Benefits
Agenda
AGENDA
Motivation
Method
Who we are
Common model
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 2
Development cycle
Challenges of data exchange in a heterogeneous software tool landscape
MOTIVATION
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 3
Source: AutomationML in
a Nutshell – AutomationML.org
Mechanical
engineering
*.txt
*.*
*.doc
*.ppt
*.*
*.csv
*.xml
*.xps
System
engineering
Simulation
Layout
Planning
Control
engineering
Different interfaces
Common language is base for consistent data exchange
MOTIVATION
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 4
Mechanical
engineering
*.txt
*.*
*.doc
*.ppt
*.*
*.csv
*.xml
*.xps
AML
Standard
System
engineering
…
Mechanical
engineeringElectrical
engineering
Virtual
commissioning
*.aml *.aml
*.aml
System
engineering
Simulation
Layout
Planning
Control
engineering
Documentation
*.aml
Control
engineering
Layout
Planning
*.aml
*.aml *.aml
Source: AutomationML in
a Nutshell – AutomationML.org
Communication needs a common language
From a common language to a common and managed model
MOTIVATION
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 5
AML
Standard
System
engineering
…
Mechanical
engineeringElectrical
engineering
Virtual
commissioning
*.aml *.aml
*.aml
Documentation
*.aml
Control
engineering
Layout
Planning
*.aml
*.aml *.aml
Source: AutomationML in
a Nutshell – AutomationML.org
Common semantics
Neutral viewOption to specialize
Enable standardization
Option to extend
Communication needs a common language
Governance required
AutomationML needs a common and managed model, too
How to develop a common, company wide model?
METHOD
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 6
weekly
AML Governance
Board
AML association
representatives
Discipline
responsible IT
Global goals and
direction
Global
IT
Discipline specific input
Discipline specific
requirements
Disciplines
Permanent
attendance
Topic specific
invitation
AML Governance
Steering board
Common Model
Report
How to develop a common, company wide model?
METHOD
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 7
Analysis of software tools
Identification of data needed to be exchanged
Development of proposals for mapping data in a tool neutral and
standardized manner
Verification of the model by building up examplesVerification
Discussion
and
integration
Proposal
Discussion and validation of proposals
Assessment of suitability and conformity to the common, company
wide model
Integration into the model
Assessment of impact on software tools
Analysis
Common Model
All aspects of a production line needs to be covered by the model
COMMON MODEL
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 8
How to structure the data?
COMMON MODEL
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 9
Site
Area
Structure
Resource
Resource
Resource
Grouping
Mirror
Resource
Grouping
Mirror
Process
order
Link between branches
External Interface
Legend
Appropriate role classes,
interface classes, and
attributes are used
How to build up a common model in AutomationML
COMMON MODEL
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 10
External Interface
Legend
Enterprise
SiteAllProcessesAllParts
BoMContext
Spec. BoM
Mirror
Prod.Process 1
Prod.Process 2
ProcessStep
ProcessStep
Processes
Line 1
Mirror
Mirror
Area
ProductionLine
WorkCell
Robot
Worker
Station
Mirror
Mirror
Mirror
Assembled
Product
Purchased
Product
Purchased
Product
Instance P1
Instance P2
Standard
Product
Structure
Object
Grouping
Mirror
How to evolve the model?
DEVELOPMENT CYCLE
Model V1
Model V2
Analysis, proposal,
discussion and
integration, verification
Reali-
zation
Current
version nPhase
Out
Release
Steering Board
Release
Steering Board
+ new/more specific Role
classes/Interface classes
+ new Attributes
+ new Groups
New version released, both versions in
parallel until the last software tool has
changed
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 11
PhaseOut
Release
Steering Board
…
Version
n+1
Version
n+2 ...
Impact of a common model
BENEFITS
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 12
Data consistency Data exchange
Modularization Standardization
Application
Digitalization
Common Model
Application support for commissioning / documentation
TOOL CHAIN
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 13
generate PLC HMIAdding safety elements to a layout
Application support for planning / engineering
TOOL CHAIN
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 14
Automatic electrical dimensioning
integra Engineering Studio
Live Demo
TOOL CHAIN
Thank you
Who we are
Introducing AutomationML in a heterogeneous software tool landscape – a success story | 24.10.2018 17
Daimler AG
• Joachim Burlein (TF/VAS)
Daimler Protics
• Matthias Rassl (IT/PRO)
• Dr.-Ing. Nicole Schmidt (IT/PRO)