14:00-15:40...concepts, usage of plcopen xml (iec 61131 -10), caex- interfaces to plcopen xml...

DIESAR Direction Internationale de l’Evaluation, de la Sécurité et des Affaires RéglementairesAFNeT Standardization Days 2019

June 5 & 6, 2019 (Paris) – [email protected] - http://standardizationday.afnet.fr/ - ‹1›

14:00-15:40


Presenter: Joseph BRIANT Company: Business Unit: Industrial Automation

Standardization:Committee "Devices and integration in enterprise systems" (TC 65/SC 65E) The chairman

"Smart Manufacturing Standards Map Task Force" (SM2TF) The IEC convenor

French mirror committee of IEC/TC 65 (UF 65)"Industrial-process measurement, control and automation" The chairman

French mirror committee of IEC/TC 3, SC 3C and SC 3D (UF 3)"Information structures, documentation and graphical symbols" The chairman

French mirror committee of ISO/TC 184 (CP IDMI)"Engineering of data and models for industry" Member



AutomationML by

Joseph BRIANT


AutomationML e.V. – the Association

ASD 2019

ASD 2019 2

The AutomationML e.V.

Association for development and standardisation

of the AutomationML data exchange format

Founded 2009

On June 2019, 56 members from industry, research and academia

Regular workshops (~ 2 months), working group meetings and events

ASD 2019 3

AutomationML e.V. Members

ASD 2019 4

AutomationML e.V. MembersEnd users

ASD 2019 5

AutomationML e.V. MembersComponent manufacturers

ASD 2019 6

AutomationML e.V. MembersSystem integrators

ASD 2019 7

AutomationML e.V. MembersSoftware editors

ASD 2019 8

AutomationML e.V. MembersOT and ICT solution providers

ASD 2019 9

AutomationML e.V. MembersTechnology providers

ASD 2019 10

AutomationML e.V. MembersAcademics

ASD 2019 11

Board ManagementBranch office Cash auditor

Working groupcommunication

Working grouplibraries

Working grouplogics

Working grouparchitecture

Working group application scenarios

Standardisation Best practiceactivities

Component classification DKE

IEC Organisation

Workgroups

Standardisation activities

Sub activities

Working grouprobotics

Abstract API

OPC UA

eCl@ss

Automation project

Materialhandling

FDT

Higher automation

levels

MTP

Fluidic plans

Containerformat

Organization

ASD 2019 12

Upcoming events

ASD 2019

Cooperations

The AutomationML e.V. cooperates for harmonization of standards and collaborative development of Best Practice

Liaisons exist with KHRONOS PLCopen OPC Foundation eCl@ss ProSTEP iViP FDT Group IEC CADENAS CPLA

Informal collaborations exist with VDMA and VDA Upcoming liaisons with ETG and IO Link

13

ASD 2019 14

Advantages for members

Knowledge advantage

Enhance AutomationML, keep updated to developments and

standardisation

Technical advantage

Access and influence AutomationML association's software

Business advantage

Do networking, collaborative appearance and marketing

ASD 2019 15

Membership in the AutomationML e.V.

Promoting member (9000 €/year) Contributing member (2500 €/year) Academic member (500 €/year)

Visit our webpage: www.automationml.orgor contact the AutomationML Office: [email protected]

Technology overview

ASD2019

ASD2019

Starting points

2

Preproduct (material, pieces)

Product line development

Product order generation

Production technology

development

Product discontinuation management

Product order maintenance

Production system removal

Product order shipment

Production system maintenance

Components

Products

Production system engineering

Production system installation &

ramp-up

Product

Production system

Product engineering

ProductionScope of

AutomationML

Engineering & use of production systems is a complex & interdisciplinary process Consideration of both products to be produced and their production systems

ASD2019

Production systems are complex For the different life cycle phases and system hierarchy levels, different information categories

are relevantScope of AutomationML

Starting points

3

9-Production network

8-Factory

7-Production line

6-Production line segment

5-Work unit

4-Work station

3-Function group

2-Component

1-Construction element

Blo

ck la

yout

2D la

yout

Bas

ic s

peci

ficat

ion

3D la

yout

Beh

avio

ur m

odel

s

Mec

hani

cal C

AD

Ele

ctric

al C

AD

Par

t lis

tFl

uidi

c pl

ans

Pow

er s

uppl

y

Saf

ety

conc

ept

Con

trol c

ode

Sim

ulat

ion

mod

els

Engineering Operation & maintenance Retirement

Supplier managementInvestment plan

Product mixCapacity plan

Material stockHuman labour plan

Product related process sequencingResource monitoring

Process supervisionProduction data acquisition

Quality control

Process control

Product identification

Sensor & actuator controlProduct data acquisition

Con

ditio

n m

onito

ring

& A

sset

man

agem

ent

Mat

eria

l flo

w c

ontro

l

HM

I

Com

pone

nt re

leva

nt in

form

atio

nG

ener

al

info

rmat

ion

Pro

duct

ion

syst

em re

leva

nt

info

rmat

ion

Mat

eria

l rel

evan

t in

form

atio

n

ASD2019

Issue statement and motivation

4

Motivation: In factory automation engineering is cost driver number one

In a heterogeneous tool landscape data exchange between the corresponding tools is an important factor

Data is stored in proprietary file formats, user has often no access to his own data.

Proprietary and numerous interfaces between tools lead to gaps in passing over information and thus result in an engineering process with poor efficiency.

Source: Cost structure analysis of robotics and controls, AIDA 2005

Analysis of factory automation costs

Precommissioning; 3%

Assembly; 11%

Engineering Commissioning; 50%

Bought-in Parts; 28%

Project Management; 3%

Robot Programming Offline/Online; 5%

ASD2019

Heterogeneous tool landscape

5

Product Design CATIA, Autocad, SolidWorks, 3ds Max

Layouting and Process planning CATIA, AutoCAD, Microstation, DELMIA Siemens PLM Software

Documentation MS Office, OpenOffice

Robot-Simulation and Offline Programming Cosimir, DELMIA Robotics, Robcad, vendor-tools

Controls Programming RSLogix 5000, STEP 7, CoDeSys, ABB PS500, MULTIPROG

Electrical Planning ePlan, PSPICE, Electronics Worrkbench, Multisim, IGE+XAO

Virtual Commisioning WinMOD TrySim, virtuos, SIMIT, DELMIA Automation, 3D Create

ASD2019

Scope of AutomationML

Starting points

Good news: Engineers are able to handle this problem since ages But the costs are high

Manual collection of necessary data Replication of (sometimes stupid) work Error prone manual actions Uncontrolled reuse leading to “strange” and sometime person depending solutions …

What can we do better?DATA Logistics

6

ASD2019

We accept that tools and data models are heterogeneous. We accept that an agreement of a common data model does not exist. We accept that development of common data models is a long term standardization activity. We accept that bidirectional data exchange across all thinkable domains does not reflect the needs of the

reality. Data integration requires in most cases only a subset of the theoretical interconnections

A pragmatic approach

7

n tools: n*(n-1) relations n tools: n relations

ASD2019

Requirements to the data exchange process

Data exchange process between two different tools requires two logical steps: Identification of data structure in accordance with the syntax of the data Identification of the meaning of the data according to the semantics

Both steps must be supported by the exporter as well as by the importer

8

Source tool

Project data

Data model Target tool

Projectdata

Data model

Exportdata

Iden

tific

atio

nof

the

data

stru

ctur

e

Iden

tific

atio

nof

the

mea

ning

ASD2019 9

Overview on AutomationML

AutomationML is …

… an object oriented data exchange format,

… based on XML,

… an IEC standard,

… free of charge, and

… open

ASD2019 10

The Architecture of AutomationML

Basic format is CAEX (IEC 62424) to…

… describe topology

… define the meaning of objects by role classes

… define reusable objects for the engineering

… model relations between objects and

… reference to external documents

ASD2019

AutomationML is …

11

A data format, that allows a vendor-independent data exchange of engineering data of production systems.

A storage format for information. Applicable within the entire engineering process by connecting different discipline

specific engineering tools. Object orientated and allows the modelling of production system components as data

objects aggregating different aspects. A combination and adaptation of already existing industry formats that were

developed for exchange and storage of different engineering aspects. A consistent and distributed document architecture, that enables the handling of large

data sets and the outsourcing of libraries to external documents.

ASD2019

AutomationML is NOT …

12

Tool functionality. Capable to review conditions, attribute values, relations, references, or semantic

correctness of data objects. Capable to check consistence or to review and match version of data objects. Capable of automatic standardization of user specific information. Capable of automatic creation of libraries. Capable of automatic management of versions and variants. A project management tool. A project management database. But it allows the storage of all data required for that.

ASD2019 13

General architecture of AutomationML

Essential features of AutomationML: Separation of syntax and semantics of data objects based on libraries of role classes and

SystemUnitClasses and referencing to library elements out of the instance hierarchy

Provision of identification capabilities for objects based on UUIDs

Provision of version information including version identification and version history information based on appropriate object attributes

Provision of data source identification information based on appropriate object attributes

Provision of data structuring capabilities beyond object hierarchies exploiting the facet and group concept

ASD2019

Objectives of AutomationML

Which data contents are covered by AutomationML?

14

Plant structure

• Component hierarchy• Topology

• Components relations

Plantdescription

Geometry and kinematics

• Mechanical construction• Motion planning

• Electrical construction

Behaviour

• Component behaviour• Control design

• Robotic process

Network

• Electrical construction• Communication systems

Plant components

• Mechatronical structures• Component attributes

• Parameters• Economical data

Semantics

• Clear meaning of the objectsabout classification systems

ASD2019

The AutomationML – architecture

15

ISO 17506

IEC 61131-10

ASD2019

The AutomationML – architecture

16

CAEX

COLLADA

COLLADA

COLLADA

PLCopen XML

PLCopen XML

PLCopen XML

ASD2019 17

The architecture of AutomationML

Using COLLADA to describe

Geometry,

Surfaces,

Kinematics, and

Kinematic scenes

ASD2019 18

The architecture of AutomationML

Using PLCopenXML for to model behaviour, e.g.

Gantt charts,

PERT charts,

Timing diagrams,

State charts,

...

ASD2019

Topology description with CAEX

Definition of meaning of objects by role classes

Definition of reusable objects for the engineering Components Interfaces Roles

Representation of project data as project tree

Integration of object descriptions as attributes

Relations between objects and references to external documents

19

Interface Class LibraryDefinition of interfaces

System Unit LibraryDefinition of reusable components

InstanceHierarchyDescription of project data

Role Class LibraryDefinition of object semantics

IH

IE

SUC LIB

SUC

LIB

RoleLIB

Role

IE

IE

IE

IE

SUC

Role

Role

*.dae

*.xml

SUC

Reference toexternal data

Linking ofobjects

Instantiation ofobjects

Nutzen von Bedeutungen

Use ofsemantics

Nutzen von Bedeutungen

Use ofinterfaces

ASD2019

InstanceHierarchyIH

InternalElementIE

1

1..*

1

0..*

Attribute

Role classRC

System unit classSUC

RoleRequirement

SupportedRoleClass

1

10..*

0..1

1 Interface10..*

0..*

1

1

RefB

aseS

yste

mU

nitP

ath

20

Topology description with CAEX

Simplified structure of an InstanceHierarchy

Reference to a defined

semantics

Reference to a copy template

Object Properties

Object RelationsObject Relations

ASD2019

Network modelling

21

Networks are the essential part of technical systems Combination of used elements Requirement: Representation of network structures

at various levels and technologies Example: Communication networks

RFC 470 PN 3TX PN BK DI8

Main controlapplication

Input function

Wire

1

Wire 2

Logical Connection A

PDU A

D1 D2 D3 D1 D2

AXL BK PN-ME

Output function

Logical Connection B

D3

PDU B

ASD2019 22

Network modelling

Communication system structure represented by AutomationML

PLC IO Device

Physicaldevice

Active infra-structure device

Main controlapplication IO function

Physicalend pointof device

Logical device

Logical end pointof device

Physicalconnection

with end point

Logical connection

with end points

Mapping oflogical tophysical

interfaces

Wire 1

Wire 2

Logical Connection A

AutomationML Communication

Variable / Signal

interface

Mapping ofVariable /

Signal interface todatagram

object

Datagramobject

PDU

PDU 1

ASD2019 23

AutomationML in Use

Examples of tools using AutomationML Coman Software Gmbh: COMAN EPLAN: Electric P8 EKS: RF::Suite logi.cals: AML.hub Mitsubishi Electric: MELSOFT iQ Works Software Suite Siemens: TIA Portal Tarakos: taraVRBuilder, taraVRControl …

ASD2019 24

AutomationML in standardization

AutomationML: IEC 62714

...

Part 1:

Part 4: Logics

Part 2: Semantics

Part 3: Geometry and kinematics

Part 5: Communication

...

Architecture and general requirements

Definitions, basic concepts, top level architecture, usage of CAEX (IEC 62424)Edition 2 (2018-04)

Role Library, industry specific librariesEdition 1 (2015-03), edition 2 in progress

Usage of COLLADA (ISO 17506), CAEX-interfaces to COLLADAEdition 1 (2017-01)

Concepts, usage of PLCopen XML (IEC 61131-10), CAEX-interfaces to PLCopen XMLEdition 1 in progress, CDV planned mi 2019, pub planned 2020

Description of communication networksLaunch of edition 1 planned in 2019, pub planned 2022


Administration Shell by

Joseph BRIANT


Administration Shell

Festo AG & Co. KG \ TD \Dr. Michael Hoffmeister - -

Asset Administration Shell

IoT shares the same principles on all verticals,Industrie 4.0 deepens the concepts for smart manufacturing

Smart ManufacturingIndustrie 4.0

Smart Grid

Smart HomeSmart Building

Smart Mobility

Healthcare

SmartDevices

Smartphone

Smart Meter

SmartFactory

Horizontal integration

Vertical integration

Integrated engineering

Human centricity

Source: Martin Hankel, Bosch Rexroth

2

Horizontal integration via value-added networks Vertical integration and networked production system

Digital consistency for the engineering throughout the whole value-added chain

The human being as a conductor for aded value

ProductionServices

Product design & development

Production engineeringProduction planning

Adapted from source: Siemens AG/Festo AG&Co KG

A flexible framework is needed to address 4 main aspects

Interoperability between different actors from different companies.> Life cycle costs, customized products ...

Interoperability between different software tools in the factory lifecycle.

Interoperability between different assets in the production system.> Reconfiguration, lot size one, constant change ...

Horizontal integration Vertical integration

Integrated engineering Human centricity

Orchestration, skills, knowledge management, training ...3

The main stakeholders in the product delivery chain

Systemintegrators

Componentsuppliers

Machinebuilders

Production operator

Applicationproviders

Service providers

4

Company B

Leading principle

Company A Company C Company Dproductdelivery

productdelivery

Systemintegrators

Componentsuppliers

Machinebuilders

Production operator

productdelivery Company E

Company F

5

Composite AAS can be used for the entire factory lifecycleand enables benefits for engineering, operation and maintenance

Componentsuppliers

Machinebuilders

System integrators

Productionoperator

composite component

component

component

component

machine / station line / plant

Models datasheetsTerms & conditions

Simulations

BOMDrawings

SchematicsSimulations

Floor planLogistic

SimulationsMaintenance plans

Procedures

Automatedengineering

Generation of HMI & documentation

Supportdata analytics

Diagnosticsystems

6

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&uact=8&docid=1X1a2Bdf6xVy7M&tbnid=AMeMNmZoB9vsQM:&ved=0CAUQjRw&url=http://www.elektronikpraxis.vogel.de/verbindungstechnik/articles/303736/&ei=KPvgU_ijOYrEPLysgIAJ&bvm=bv.72197243,d.bGE&psig=AFQjCNE61gn2BWP5XAojuUWkLpqYb1v8WA&ust=1407339641318092http://www.festo.com/cat/de_de/search?query=motorcontrol

Categaories of assets in the scope

The current AAS specifications cover the asset category "physical objects"

7

Cloud

ControlProductionprocesses

PartnersDataApps

Office Floor Network

Events

Businessprocesses

Sensors Data Machines

100101001101011101101

100101001101011101101

Services

Shop Floor Network

Connectivity to any endpoint

A core challenge: IT/OT interoperability1- Connectivity

Shared communication system

8

Cloud


PartnersDataApps


Events

Businessprocesses


100101001101011101101

100101001101011101101

Services

Shop Floor Network

Connectivity to any endpoint Common data model

Shared grammar

Je voudrais une pomme s’il vous plait

I would like an apple please

이해가안돼

A core challenge: IT/OT interoperability2- Data model

9

Cloud


PartnersDataApps


Events

Businessprocesses


100101001101011101101

100101001101011101101

Services

Shop Floor Network

Connectivity to any endpoint Common data model Common semantic

Shared vocabulary

Braeburn Cameo Cox

FujiGolden

DeliciousGrannySmith

Jazz

PinkCrisp

RedDelicious

RoyalGala

I would like a cox please

A core challenge: IT/OT interoperability3- Common semantic

10

I4.0 Component

Administration Shell (AAS)

Asset

I4.0 Communication

The Administration Shell:The solution from Industrie 4.0 as information provider of on assets

Connectivity

Data model&Semantic

The Administration Shell is the virtualization of the asset(characteristics and functions associated to the asset).

A common model of the variousassets is needed

"Asset Administration Shell (AAS)"in short "Administration Shell"

The Administration Shell provides information and added values

The digital worlds reflectsthe specific features of the asset

Connection is established via I4.0 / IoT communication

11

=Administration Shell


... is structured by functional domains

Specific functions (Motion, power protection, weighing, sensor, control ...)

Representation (3D, 2D, electrical ...)

Structuration of Administration Shell

Generic functions (Energy management, networking, safety, security ...)

=Administration Shell


... submodel describes a domain by properties, and additional info and

functions

Identification

Sub model 1: Energy

Asset IDAdministration Shell ID

Measure

Sub model 2: MotionVelocity

Positionning

Rotation speed

Rated voltage

Saving

Sub model 3: CADMounting

...

InformationInformationCAD information

InformationInformationCAD information

Exec

Axis

MOVE VEL

InVel

Vel

Actual power

Cumulative energy

CAPABILITIES PROPERTIES ADD INFORMATION + FUNCTIONS

...

...

...

InformationInformationAdd information

InformationInformationAdd information

STRICT (DICTIONARY) Customized (Manufacturer Def.)

The Administration Shell is structured by sub models

Other ID

The real innovation:We're giving each information an agreed meaning (semantics)!

I4.0 compliant communication

Submodel Positioning

Endpos. left [mm] 5Endpos. right [mm] 200Max. velocity [mm/s] 15Max. acceleration [mm/s2] 33

No of completed jobs [1] 4634Avg. pos. lag. [mm] 4.5

Submodels of the AAS

i

i

i

i

i

i

i

14

consortiumspecifications

Internationalstandards(ISO/IEC..)

proprietary properties, differentdata formats, company specs

Established standard properties

identification

safety (SIL)

energy efficiency

condition Monit.

positioning

3D model

purchasing

.. many further

iiii

iiii

Asset, e.g.electrical axis

AdminstrationShell (AAS)

i

i

= worldwide identification, if possible standardisedas well: secure identities

Identificator (1) IRDI (International Registration Data Identifier) in IEC 61360, ISO 13584

Identificator (2) URI / URL (as in web)

14

http://www.festo.com/cat/de_de/search?query=motorcontrol

Identification

15

The Administration Shell in product and production system life cycles

Adapted from source: The Structure of the Administration Shell:TRILATERAL PERSPECTIVES from France, Italy and Germany

16

Data modelSpecification series: "Details of the Administration Shell"

Part 1 - Information model for the AAS for the exchange of information between partners in the value chain

Part 2 - Interfaces and API for using a single AAS information model described in Part 1(access, modify, query and execute information and active functionality)

Part 3 - Infrastructure, which hosts and interconnects multiple AAS together (registry, discovery, endpoint handling)

18

https://www.google.de/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0ahUKEwjL0YzW7unZAhWHxxQKHY-VC0IQjRwIBg&url=https://bar.wikipedia.org/wiki/Datei:744px-Siemens-logo_svg.png&psig=AOvVaw2DPT7fjmAUa7oteHVCOpsm&ust=1521049921613925

Requirementsapproaches

Technology neutralUML model

XML, JSON OPC UA AutomationML RDF

Informationsecurity

Packageformat

19

Details of the Administration ShellPart 1: Methodology

Details of the Administration ShellPart 1: Data exchange between partners in the value chain

IntegratorSupplier

Internal

public

Operator

I4.0 Repository

DecentralRepositories

2Publish

A1

TB1

T

Receiv e Publish Receiv eCompositeTy pe machine

Internal

A4

TB4

T

C1

T

C4

T

D1

E1

CompositeInstance machineD4

E4 F1 (D4,E4) F4 (D4*,E4*)

productty pe

consolidate

consolidate

deliv ery

deliv ery

product

product

masterdata

Compositeproduction

line

I4.0-platform

Internal

deliv eryproduct

Picture Hoffmeister/ Jochem, according Epple, 2016

A2 A3

B2 B3 C2 C3

D2 D3

E2 E2 F2

(D4,E4)

F3

(D4*,E4*)

20

► Exemplary prototypes of Admin shells, e.g. for USB stick

► Exemplary browse applications ..

► Real applications need to come from 'real' software vendors

► Competition will drive innovation and will produce fitting solutions for different needs (e.g. SMEs vs global companies)

22

Details of the Administration ShellWe're currently building up SDKs, tools, more examples ...

July 2015 July 2017

Local Standardization

InternationalPAS

IEC/TC 65

Smart Manufacturing Reference Model(s)


ReferenceArchitectureModel forI 4.0

AssetAdministrationShell

CriteriaComponentI 4.0

Nov. 2016 Nov. 2017 Jan. 2019

ModularTypePackage

Mid. 2016

2015

April 2018

April 2018

Communication Data model Semantic

OPC UA, ….. AutomationML, ….. eCl@ss, IEC CDD, …..

Status of I4.0 concepts and associated standards

Associated standards

International?

International?

23

Administration Shell: Standardisation status and AIF


AssetAdministrationShell

April 2016 April 2018

Definition of concept

Application to dedicated segments

Involment

50% 0%100% 100% 50%

Document ready for

standardizationModel of

AASDefinition of Sub Models

0%

International?

April 2019 International?

Structureof AAS

AASin details

24

Part 1


Smart Manufacturing Standards Map by

Joseph BRIANT


SM2

Smart Manufacturing Standards Map (ISO-IEC-SM2)

ASD2019

Joseph BRIANT, France

Terms of reference1

Organization2

Members3

Reference documents4

Tasks and schedule5

To create and maintain a list of standards 6

To define a vocabulary7

To generate charts8

Agenda

Smart Manufacturing Standards Map (SM2)

1-Terms of reference

The terms of reference from ISO/TMB and IEC/SMB

Three phases• Phase 1: To publish a Technical Report including terms & definitions and a

standards list based on existing publications.• Phase 2: To publish a second edition of the Technical Report based on the Smart

Manufacturing Reference Model of ISO-IEC-JWG 21.• Phase 3: To draft a recommendation to ISO and IEC for the smart graphical

represention of the standards map

4

2-Organisation

JWG 21SM

Reference Model(s)

SM2TF in the Smart Manufacturing standards landscape

System Level

Technical Committee Level

SMCCSmart Manufacturing

Coordination Committee

Other TCsand SCs

Outside ISO and IEC

xxTFPossible new TF

for generic Smart SM Topic

TC 65TC 184

6

Other TCsand SCs

SEG 7disbanded

Smart ManufacturingSystem Evaluation Group

SyC SMxxSmart Manufacturing

System Committee

JTC 1Information technology

SM2Smart Manufacturing

Standards Map Task Force

IEEE

Standards bodies

Consortia

AutomationML

2019

SM2TF is hosted by IEC

https://www.iec.ch/dyn/www/f?p=103:14:1041771280186::::FSP_ORG_ID,FSP_LANG_ID:23177,25

3-Members

Mr Udo BAUSCH Germany [email protected] Mr Daehyun KWON Korea [email protected]

Mr Joseph BRIANT France [email protected] Mr Soonhung HAN Korea [email protected]

Mr Erwin SCHOITSCH Austria [email protected] Mr Klas BOIVIE Norway [email protected]

Mr George WEICHHART Austria [email protected] Mr Nils SANDSMARK Norway [email protected]

Mr Hongye SU China [email protected] Mr Tor Arne IRGENS Norway [email protected]

Mr LIU Yang China [email protected] Mr Miguel Ángel IÑIGO ULLOA Spain [email protected]

Mr Nan ZHENG China [email protected] Mr Xavier PI Spain [email protected]

Ms DING Lu China [email protected] Mrs Patricia TAMES Spain [email protected]

Ms DONG Xiao China [email protected] Mr Bengt OLSSON Sweden [email protected]

Ms WEI Sha China [email protected] Mr Gunnar BOLMSJO Sweden [email protected]

Mr Christophe MOUTON France [email protected] Mr Hikmet HUSSAIN Sweden [email protected]

Mr Philippe JUHEL France [email protected] Mr Mikael HEDLIND Sweden [email protected]

Mrs Anne-Francoise CUTTING-DECELLE France [email protected] Mr Sven RADHE Sweden [email protected]

Ms Valérie DEMASSIEUX France [email protected] Mr Thomas LUNDHOLM Sweden [email protected]

Mr Martin HANKEL Germany [email protected] Mr Torjörn HOLM Sweden [email protected]

Mr Michael HOFFMEISTER Germany [email protected] Ms Ann-Sofie SJÖBLOM Sweden [email protected]

Mr Yun Chao HU Germany [email protected] Ms Gunilla SIVARD Sweden [email protected]

Mrs Laura MATHEW ISO [email protected] Mr Aydin NASSEHI UK [email protected]

Ms Margherita DE MINICIS Italy [email protected] Mr Howard MASON UK [email protected]

Mr Fumihiko KIMURA Japan [email protected] Mr Maurice WILKINS UK [email protected] Hitoshi KOMOTO Japan [email protected] Mr Alexander MCMILLAN USA [email protected]

Mr Koji DEMACHI Japan [email protected] Mr Kenneth SWOPE USA [email protected]

Mr Takenori BABA Japan [email protected] Mr Lonnie MANDIGO USA [email protected]

Mr Tohru KANADA Japan [email protected] Mr Richard MARTIN USA [email protected]

Mr Daehyun KWON Korea [email protected] Mrs Allison BARNARD FEENEY USA [email protected]

Mr Soonhung HAN Korea [email protected] Ms Michelle PASTEL USA [email protected]

Mr Klas BOIVIE Norway [email protected] Ms Yan LU USA [email protected]

SM2TF members

9

4-Reference documents

The already existing material

China

GermanyISO/TC 184

France Japan Japan

SGAM USA

11

ISO/SAG I4.0-SM

5-Tasks and schedule

SM2 method

• To define a vocabulary limited to the criteria of classification• To create and manage a list of standards• To generate automatically diagrams (graphical representations for analysis)

14

Additionnal

BerlinMeetingMar 7~8(18 at.)

FrankfurtMeetingJul 12~13

(17 at.)

Prepararation of vocabulary and library

Approvalof

version 1

8WProcessing by committees

2018

Circulationto

committees

ChicagoMeeting

Nov 15~16(14 at.)

Mar 29Jan 30

ParisMeeting

May 20~21(23 at.)

Phase 1 schedule v2

15

49 ISO TCs/SCs35 IEC TCs/SCs15 JTC 1 SCs

ShanghaiMeeting

October 21~22

Consolidatethe inputs

2nd circulationto TCs/SCs

committees

Jun 30Jul 04

Jul 05

Circulationto NCs by IEC/CO

and ISO/CS

Jul 12

9W

Processing by TCs/SCs

& NCs

Draft amended documents and

consolidatethe inputs

Sep 13

Provide webmeetings

to TCs/SCs

Only 16 TCs answered 2019

Phase 2: Synchronisation with JWG 21 (current)

16

*viewpoint*perspective

*concern

SM2 targets and phases

Phase 1

Vocabulary

List

Diagrams

Publicationof "TR"

Publication of"TR" ed2

Maintained data base format

17

Phase 2

Phase 3

Recommendations toISO/TMB & IEC/SMB

Spread sheet

Applicationof

the unifiedreference model

Synthesysof

existingreference models

TC 184 TC 65 JWG 21

6-To create and maintain a list of standards

Current Excel file

19

Classification criteria

CN system hierarchy

SGAM layers

Functional hierarchy

Equipement hierarchyRAMI layers

RAMI life cycle

Product type life cycle

Product instance life cycle

Production system life cycle

Supply chain life cycle

Type of process

Industrial sector

International Codification of Standards

Interoperability approach

Interoperability barrier

Interoperability concern

CN life cycle

Intelligent characteristics

21

Grouping of classification criteria

22

V1 result: Hierarchy

23

V1 result: Life cycle

24

V1 result: Interoperability

25

V1 result: Process

26

8-To generate charts

28

RAMI model chart

OSI/RAMI model chart

29

Production system model chart

30

Intelligent Manufacturing System Architecture model chart

31

Smart Grid Standards Map

http://smartgridstandardsmap.com/?ref=extfooter

ASD2019_JB10_AutomationML_TitleSlide Number 1Presenter: Joseph BRIANTSlide Number 3

ASD2019_JB11_AutomationML_AssociationSlide Number 1The AutomationML e.V.AutomationML e.V. MembersAutomationML e.V. Members�End usersAutomationML e.V. Members�Component manufacturersAutomationML e.V. Members�System integratorsAutomationML e.V. Members�Software editorsAutomationML e.V. Members�OT and ICT solution providersAutomationML e.V. Members�Technology providersAutomationML e.V. Members�AcademicsSlide Number 11Slide Number 12CooperationsAdvantages for membersMembership in the AutomationML e.V.

ASD2019_JB12_AutomationML_Technical OverviewSlide Number 1Starting pointsStarting pointsIssue statement and motivationHeterogeneous tool landscapeStarting pointsA pragmatic approachRequirements to the data exchange processOverview on AutomationMLThe Architecture of AutomationMLAutomationML is …AutomationML is NOT …General architecture of AutomationMLObjectives of AutomationMLThe AutomationML – architectureThe AutomationML – architectureThe architecture of AutomationMLThe architecture of AutomationMLTopology description with CAEXTopology description �with CAEXNetwork modellingNetwork modellingAutomationML in UseSlide Number 24

ASD2019_JB20_Administration Shell_TitleSlide Number 1

ASD2019_JB21_Administration ShellSlide Number 1IoT shares the same principles on all verticals,�Industrie 4.0 deepens the concepts for smart manufacturingSlide Number 3Slide Number 4Slide Number 5Composite AAS can be used for the entire factory lifecycle�and enables benefits for engineering, operation and maintenanceSlide Number 7Slide Number 8Slide Number 9Slide Number 10Slide Number 11Slide Number 12Slide Number 13The real innovation:�We're giving each information an agreed meaning (semantics)!IdentificationThe Administration Shell in product and production system life cyclesData model�Specification series: "Details of the Administration Shell"Slide Number 19Details of the Administration Shell�Part 1: Data exchange between partners in the value chainDetails of the Administration Shell�We're currently building up SDKs, tools, more examples ...Slide Number 23Slide Number 24

ASD2019_JB30_ISO-IEC-SM2_TitleSlide Number 1

ASD2019_JB31_ISO-IEC-SM2Slide Number 1Slide Number 2Slide Number 3The terms of reference from ISO/TMB and IEC/SMBSlide Number 5SM2TF in the Smart Manufacturing standards landscapeSM2TF is hosted by IECSlide Number 8SM2TF membersSlide Number 10The already existing materialSlide Number 13SM2 methodPhase 1 schedule v2Phase 2: Synchronisation with JWG 21 (current)SM2 targets and phasesSlide Number 18Current Excel fileClassification criteriaGrouping of classification criteriaV1 result: HierarchyV1 result: Life cycleV1 result: InteroperabilityV1 result: ProcessSlide Number 27RAMI model chartOSI/RAMI model chartProduction system model chartIntelligent Manufacturing System Architecture model chartSmart Grid Standards Map

14:00-15:40...concepts, usage of plcopen xml (iec 61131 -10), caex- interfaces to plcopen xml...

Documents