FAQ - Contents
Filter Title 
Filter Content 
 
AutomationML - Technical questions top
Does AutomationML support exchange of libraries?

Yes, the support of object oriented library concepts is a core feature of AutomationML and its related standards CAEX, COLLADA and PLCopen XML.

Does AutomationML support versions, encryption, access rights and data protection?

AutomationML is able to store version and history information. Tools are able to use standard XML methods for encryption, e.g. XML encryption or XML signatures.

Management of access rights is a tool functionality, while AutomationML is a data exchange format.

How do you manage bulk data?
AutomationML supports distribution of data in separate XML files through reference mechanisms, e.g. geometry of objects can be stored in different XML files.
How is data stored?

Data is stored in any storage system that supports XML documents.

How is the architecture of AutomationML designed?

AutomationML combines well accepted standards for certain aspects of automation engineering under an own top-level format.

What are the parts of AutomationML?
Parts of AutomationML are:
  • CAEX as top-level format and for plant topology,
  • COLLADA 1.5 (Khronos Group) for geometry, kinematics and motion planning
  • PLCopen XML SFCs for behavior and sequence descriptions
  • MathML 2.0 for formulas
What is your technical approach?
  • We define a free and open, XML-based data format.
  • We do not want to reinvent the wheel, thus use and enrich already existing, free and open, well established standards.
  • One core effort is the development of a single roof format that incorporates well accepted standards for important engineering aspects.
What use cases do you implement?

In general we cover the whole engineering process, such as simulation or coordination of mechanical, electrical and logics design.

However we start with those use cases most important for the AutomationML members, e.g.:

·         Transition from robot simulation system to robot specific programming system
·         Transition from mechanical design engineer to functional (electrical and PLC) engineering
·         Data exchange between CAD systems
·         Transition from CAD system to documentation system

Why do you use an XML-based format?

We use XML as a base format because:

·         XML is a globally highly accepted data format,

·         it is very easy to provide connectors to XML,

·         a variety of stable and reliable XML parsers are available for low cost,

·         XML solves the syntax problem.

Content top
What changes does AutomationML require in our engineering workflow?

AutomationML does not require changes in your workflow. AutomationML supports today’s workflows. Furthermore it simplifies regular synchronizations of parallel engineering steps.

Motivation and Scope top
Does AutomationML enable automatic data synchronization in a heterogeneous tool landscape?

AutomationML is a good basis for automatic data synchronization, as it provides all necessary engineering information. But remember, AutomationML is a data format; data synchronization is a tool functionality.

Does AutomationML require changes in our engineering workflow?
No, AutomationML does not require changes in your workflow.
AutomationML supports today’s workflows. Furthermore it simplifies regular synchronizations of parallel engineering steps.
How will AutomationML influence engineering in general?
AutomationML accepts a heterogeneous tool landscape per definition. There will not be the one solution for single problems and there will not be one tool to solve all problems. Thus AutomationML:
  • supports usage of best tools in class,
  • closes gaps in the engineering process,
  • reduces complexity by providing a common intermediate format,
  • empowers innovative companies to bring in their solutions without being forced to connect to numerous major tools,
  • helps tool vendors to focus on their core competences instead of spending high efforts on developing and maintaining
    interfaces.
Is AutomationML restricted to the automotive industry?

No. AutomationML addresses data exchange for any plant information and is thus not restricted to specific industries.

What are the goals of AutomationML?

Goals of AutomationML are:

·         Reduction of engineering costs and acceleration of engineering

·         Protect investment by enabling openness of engineering data

·         Lower market entry barriers for innovative niche product vendors and service providers

·         Seamless data transport

·         Make it easier to keep data consistency

What artifacts will AutomationML deliver?

AutomationML comprises:

  • a specification document,
  • XML schemas,
  • supporting software tools with example files and implementation recommendations.
What is AutomationML about?

With AutomationML we jointly define and validate the Automation Markup Language (AutomationML) as an intermediate XML based data format for all phases of plant engineering along the business cases of our members.

What is the core motivation for the AutomationML group members to spend that effort?

We reduce engineering efforts and improve quality by interconnecting a heterogeneous tool landscape.

What is the main difference between AutomationML and all other free formats?

Main innovation is the incorporation of well accepted standards for important engineering aspects under a single roof format, e.g. plant topology, geometry, kinematics and logics.
As such it is the only freely available, open XML-based standard.
It is not dominated by a single vendor but driven by leading automation players

 

Will AutomationML be free of charge/freely available?
Yes. AutomationML will be an open standard available through the IEC.
The schema and further documents are available for free.
Will you develop new engineering software tools?

No, the AutomationML group only defines the data format. However the group provides exemplary reference implementations as freeware. Please see our download site.

Organization top
Can everybody join the working group?

Yes, AutomationML is an open standard. Thus principally everybody can join the organization as member.

What do I need to implement AutomationML in my application?
Please see the “Getting started” posting in the AutomationML forum at http://www.automationml.org/forum.
What is the schedule of AutomationML?

AutomationML is ready for use. Further topics are under work, however are under NDA of our members. For your topics that you might miss in AutomationML, just join AutomationML.

What is the standardization body for AutomationML?

The standardization body of AutomationML is the Deutsche Kommission für Elektrotechnik Elektronik Informationstechnik (DKE), we intend to submit it to the IEC as a Publicly Available Specification (PAS).

Additionally the AutomationML group contributes to other standardization organizations with own proposals, namely the Khronos Group and PLCopen.

Where can I get the schema?
http://www.automationml.org, please see the download page.
Who are the members of the AutomationML group?

Daimler as manufacturer together with ABB, KUKA and Siemens Industry Automation as strong industry partners, NetAllied Systems, Zühlke and Fraunhofer IITB as software and service providers as well as the Universities of Karlsruhe and Magdeburg as research partners.

The AutomationML community is open for new members.

Who has the lead in the AutomationML group?

The AutomationML organization has promoting members, contributing members and academic members. Although the promoting members have some more rights according to their higher fees, the major work happens in working groups with the same voting power for every participant.

Why not CAD tool providers?
We wanted to identify the requirements for this standard from the viewpoint of industrial automation players first.
Why not other companies?
In the first step we wanted to keep the group small to be more effective.
Why this choice of members?
In the first step we wanted to keep the group small to be more effective. However the group will be opened after the Hannover Messe 2008.