XML

Starting points
Project management (3%)
 A significant cost factor Pre-commissioning (2%)
Assembly (11%)
of industrial production Bought-in parts (28%)
systems is the Geometry simulation (1%)
Robot programming offline/online

engineering process. (5%)
Engineering [incl. Commissioning]
(50%)
 A survey revealed: Source: AIDA 2005
 That 82% of the interviewed Do redundancies exist in the engineering process?
experts say that redundancy Yes (41%)
on planning steps exits. Depending on application (41%)
 That the pdf/paper interface No (18%)
is the most widespread

interface with 31%. Which interfaces are currently used ?
 That only 12% of the

Paper/PDF (31%)
Proprietary interfaces (26%)
interviewed experts use Generic exchange formats

(12%)
standardized interfaces. Consistent project database

(20%)
Other (11%)
08.03.2018 CADENAS Industry Forum 2

Data exchange problem
Prerequisite: Knowledge about the

Prerequisite: Definition of data elements,
contained data elements, their
that needs to be exported, their
representation (syntax), and their meaning
representation (syntax), and their meaning
(semantics) as well as the knowledge about
(semantics)
their relationship to the own data elements
Sending Receiving
tool tool
Data in Data
Data in
Project
Data
transformation exchange
exchange transformation
Project
format
data fromat data
Write data Exported Read data Objekt
Objekt
-attribut
-attribut
Data data
-attribut
-attribut
Data
1
1
1
model
Objekt
1
1
Objekt -attribut
model
-attribut
-attribut
-attribut
Objekt
1
Objekt -attribut
-attribut
-attribut Relation
-attribut
Mapping
Objekt
Objekt
-attribut
-attribut -attribut
-attribut
Relation

Objectives of AutomationML
Engineering
Project management
Discipline 1
Engineering Installation &

Discipline 2 Ramp UP
Engineering
Use & Maintenance
Discipline x
Component supplier Virtual commissioning
Use of unified
libraries

 Ensure a common understanding of exchanged

data
 Explicit common semantics for all data to be exchanged
Represented by role
class and interface Requires a common
class systems Common data exchange language information
structuring
Identification of common concepts
Domain specific
language discipline A
Domain specific
language discipline B
… Domain specific
language discipline X
Library specific
language
Discipline A Discipline B … Discipline X Component Provider

What about semantics?
6
08.03.2018 CADENAS Industry Forum
 AutomationML allows a
consistent data exchange
among and across different tool
chains.
 AutomationML is an XML based
human readable data format.
 It is an international standard
and free of charge.
Topology
 It allows the integration of the
Mechanic
information information
world of tools into the digital
Function
factory of the future. Further
Information
Mechatronic unit describing
information
 Covers the information sets:
Network Control
Ranging from simple objects to information information
complex ones storable in libraries

 Which data contents are covered by AutomationML?

Plant structure Plant components
• Component hierarchy • Mechatronical structures
• Topology • Component attributes / parameters
• Components relations • Economical data
Geometry and kinematics Network
• Mechanical construction
Plant • Electrical construction
• Communication systems
• Motion planning
• Electrical construction
description
Behaviour Semantics
• Component behaviour • Clear meaning of the objects
• Control design about classification systems
• Robotic process

 Which component related data contents are covered?

Plant structure Component
Geometry and kinematics Network
Component • Electrical conections
• Communication connections
• Motion planning description
Behaviour Semantics
• Robotic process

 Where can AutomationML be used?
Product Functional
Plant Planning Commissioning
Design Engineering

The AutomationML – architecture
 AutomationML combines Topology

information
the data formats
 CAEX (IEC 62424) to describe Network
information
system hierarchies as well as
attributes for system elements Further
and devices Information
 COLLADA (Standard of
KHRONOS Group) to describe
Mechanic
geometry und kinematic information
information
 PLCopen XML (Standard of
PLCopen for modelling of IEC
61131 projects) for behavior Function
information modelling describing
information
Control
information

Anlagenplanung und
IEC 62714 Inbetriebnahme Geometrie
und
Kinematik
Toplevel-Format
Format
CAEX IEC 62424 COLLADA
Anlagen-
struktur-
information
Komponenten Logik
Format
Komponenten- PLCopen
hierarchien XML
Mechatronik
Netzwerke
Geräte
Attribute Komponenten-
/Gerätebeschreibung mit
eCl@ss Attributen
12
D1 D2
Weitere Aspekte
zung
Nut-
in weiteren XML
Formaten Dn
AutomationML übertragen mittels OPC UA Technologie

COLLADA
CAEX
COLLADA
PLCopen XML
PLCopen XML
PLCopen XML
COLLADA

Topology description with CAEX
 Definition of meaning of
objects by role classes
 Definition of reusable
objects for the engineering
 Components
 Interfaces Reuseable
 Roles
system
 Representation of project components
data as project tree
 Integration of object
descriptions as attributes
 Relations between objects
and references to external
documents Semantics definition

Geometry and kinematics
description with COLLADA
 OpenXML – based 3D graphics format including geometry AND

kinematics (sinceV1.5) as only file format that enables that
 Also used by Google Earth/Sketch Up, Game Engines
 COLLADA is standardized as ISO/PAS 17506 by KHRONOS
 Originally developed for gaming industry. CAEX
 Main driver: Sony

AutomationML AutomationML
InternalElement COLLADA data
Geometry
Kinematics
COLLADA
Robot

Application examples
 Exchange of plant structures Plant structure Plant components

 CAD structures of transport • Topology

• Components relations
• Component attributes / parameters
• Economical data
systems
Network
 Example tool chain: Geometry and kinematics
AutoCAD (Autodesk) 
• Motion planning
description
taraVRbuilder (tarakos) 
PlantSimulation (Siemens) Behaviour Semantics
 Precondition: transport system role

• Robotic process
library

Application examples
 Exchange of network structures Plant structure Plant components
 Device and wiring structure within

automation systems
 Example tool chain: Geometry and kinematics
Plant
Network
EPlan Electric (Eplan) TIA Portal • Motion planning
description
(Siemens)/ logi.CAD (logi.cals)

 Precondition: Automation system Behaviour Semantics
hardware configuration role class • Component behaviour

• Control design
• Robotic process
• Clear meaning of the objects
about classification systems
system

Application example
 Exchange of kinematics
 Structure, geometry und Network

kinematics data for virtual • Mechanical construction
• Motion planning
Plant
description
commissioning • Electrical construction
 Example tool chain: Process Behaviour Semantics
simulate (Siemens), Delmia • Component behaviour

• Control design
(Dassault), NX MCD (Siemens)  • Robotic process
RF::Suite (EKS Intec)

 Preconditions: virtual
commissioning related role class
systems, COLLADA

Application example
 Setup of control projects

 Model based engineering of

Network
positive behavior within control Geometry and kinematics
description
application
• Motion planning
 Example tool chain: logi.CAD Behaviour Semantics

(logi.cals) • Component behaviour
• Control design
 Proconditions: control • Robotic process
related role class systems,

PLCopen XML
Velocity 6000

Application example
 Support of automation and process engineering • Component hierarchy
• Topology
• Mechatronical structures
• Component attributes / parameters
with intelligent parts from component libraries • Components relations • Economical data
 CENIT FASTSUITE Edition 2

Network
 Scalable solution with respect to level of Geometry and kinematics
information from component manufacturer • Motion planning
description
 Already available is download of Collada files from
CADENAS with geometry and kinematics import Behaviour Semantics
 Will be extended after release of BPR - AML Component • Component behaviour

• Control design
covering mechanical and electrical adapter, I/O signals • Robotic process
and behavior
 Components can directly be used to setup a mechatro-
nical simulation model for OLP and PLC validation
purpose in Fastsuite E2
CADENAS https://b2b.partcommunity.com CENIT Fastsuite Edition 2

Important support structure
 An very important building

block for the extensive use
of AutomationML are
component libraries
 Example OPAC Project
 How can a plant component

be modelled by
AutomationML?

 Development of component
modelling approach
 Defines Role Class Lib for
AutomationML Component
 Basic Role Class AutomationComponent
– Defines basic attributes
– Identification of elements as
„AutomationML automation component“
 Further Role Classes (examples)
– AutomationComponentDocumentation –
integration of external documentations in
different file formats, e.g. PDF
– AutomationModelElement – integration
of addition models like simulation, 3D or
kinematic models
– AutomationComponentConnector –
definition of different connector, e.g.
electric, pneumatic … are possible

 Development of component
modelling approach
 SUC as Template for 100%
Component
 Components are defined by the
Supported / RequieredRole
Class AutomationComponent
 Internal Elements with defined
Role Classes for all information
classes, including the necessary
interfaces

example
 Forerunner within the implemen-

tation of the component concept is
Festo
 At the moment Festo is able to provide
Collada 1.4.0 representations for
nearly all catalogue products (Collada
1.5.0 will be availabe soon)
 Provides ColladaWebViewer and
AutomationMLEditor Plugin
 Intention: Provide a stable tool kit for
evaluation of geometry and kinematic
behavior of components BEFORE
purchasing
 Enables a first step towards
integrated component libraries and
their use

example
 First CADENAS based solutions

available

State of applicability of
AutomationML
 Frequently addressed issue: Is AutomationML mature

enough to be applicable ?
 Simple answer: YES!
 More complex answer: There is a possible migration path from
existing stable engineering chains towards AutomationML based
ones!
 Problems to be tackled: Convince the user to NOT change their
known habit but improving their work.
Disziplin C: Datensenke
Disziplin A: Datenquelle
*.xml *.xml
*.aml *.aml
Transformer Transformer
*.aml *.aml
Transformer
*.csv *.aml *.aml Transformer

*.aml *.csv
*.aml
Disziplin B: Datenquelle Disziplin D: Datensenke

Cooperations
 The AutomationML e.V. cooperates

with different organizations for the
purpose of harmonization of standards
and the collaborative development of
Best Practice
 Liaisons exist with
 PLCopen
 KHRONOS (COLLADA)
 eCl@ss
 ProSTEP iViP
 OPC Foundation
 IEC
 FDT
 VDMA
 CADENAS

Cooperation with CADENAS
 Status: Liaison
 Technical objective:
 Development of a production system component
modelling methodology
 Integration of engineering and purchase relevant
information
 Application of this methodology as export function
from CADENAS product catalogs
 Enhancement of CADENAS PARTsolution product
line with AutomationML export
 Non-technical objectives:
 Collaborative promotion / marketing
 Affected parts of AutomationML
 Best Practice Recommendations Description of Automation
Components (currently in development)

AutomationML information
 What else can be found about

AutomationML?
 AutomationML web page on
www.automationml.org
Download area with all whitepapers,
software, development examples, …
Research projects, tools, publications, …
 AutomationML newsletter
Subscription possible on the web page
www.automationml.org
 AutomationML in a Nutshell
 Downloadable on the web page as well

Join AutomationML!
Eine wirklich gute Idee

erkennt man daran, dass
ihre Verwirklichung von
vorne herein
ausgeschlossen erscheint.
Albert Einstein
08.03.2018Messe, 20-24 April 2009

Hannover CADENAS Industry Forum 30
Topology description with CAEX
example
Project
Defined roles as sematic Component library

representation

example
CAEX
Quelle: www.arburg.com
CAEX
COLLADA

XML

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

XML

Загружено:

Авторское право:

Доступные форматы

Starting points

Project management (3%)

 A significant cost factor Pre-commissioning (2%)

systems is the Geometry simulation (1%)

Robot programming offline/online

 A survey revealed: Source: AIDA 2005

 That 82% of the interviewed Do redundancies exist in the engineering process?

experts say that redundancy Yes (41%)

on planning steps exits. Depending on application (41%)

 That the pdf/paper interface No (18%)

is the most widespread

 That only 12% of the

Proprietary interfaces (26%)

interviewed experts use Generic exchange formats

standardized interfaces. Consistent project database

08.03.2018 CADENAS Industry Forum 2

Prerequisite: Knowledge about the

Write data Exported Read data Objekt

08.03.2018 CADENAS Industry Forum 3

Engineering Installation &

Component supplier Virtual commissioning

08.03.2018 CADENAS Industry Forum 4

 Ensure a common understanding of exchanged

Identification of common concepts

Discipline A Discipline B … Discipline X Component Provider

08.03.2018 CADENAS Industry Forum 5

What about semantics?

08.03.2018 CADENAS Industry Forum 7

 Which data contents are covered by AutomationML?

Geometry and kinematics Network

08.03.2018 CADENAS Industry Forum 8

 Which component related data contents are covered?

Geometry and kinematics Network

08.03.2018 CADENAS Industry Forum 9

 Where can AutomationML be used?

08.03.2018 CADENAS Industry Forum 10

 AutomationML combines Topology

08.03.2018 CADENAS Industry Forum

AutomationML übertragen mittels OPC UA Technologie

08.03.2018 CADENAS Industry Forum 12

08.03.2018 CADENAS Industry Forum 13

08.03.2018 CADENAS Industry Forum 14

 OpenXML – based 3D graphics format including geometry AND

 Main driver: Sony

08.03.2018 CADENAS Industry Forum 15

 Exchange of plant structures Plant structure Plant components

 CAD structures of transport • Topology

 Precondition: transport system role

08.03.2018 CADENAS Industry Forum 16

 Exchange of network structures Plant structure Plant components

 Device and wiring structure within

(Siemens)/ logi.CAD (logi.cals)

hardware configuration role class • Component behaviour

08.03.2018 CADENAS Industry Forum 17

 Structure, geometry und Network

commissioning • Electrical construction

 Example tool chain: Process Behaviour Semantics

simulate (Siemens), Delmia • Component behaviour

(Dassault), NX MCD (Siemens)  • Robotic process

RF::Suite (EKS Intec)

08.03.2018 CADENAS Industry Forum 18

 Setup of control projects

 Model based engineering of

 Example tool chain: logi.CAD Behaviour Semantics

.csv .aml *.aml Transformer