Integrating Performance Modeling in Industrial Automation through AutomationML and PMIF
Download as PPTX, PDF3 likes411 views
The document discusses the integration of performance modeling in cyber-physical production systems (CPPS) using AutomationML (AML) and Performance Model Interchange Format (PMIF). It outlines three integration mechanisms to facilitate model-driven performance engineering, emphasizing the need for harmonizing data exchange across different engineering disciplines. The conclusion highlights the ongoing efforts to enhance integration and the potential for adopting these mechanisms in various methodologies.
Integrating Performance Modeling in Industrial Automation through AutomationML and PMIF
- 1. Business Informatics Group Institute of Software Technology and Interactive Systems Vienna University of Technology Favoritenstraße 9-11/188-3, 1040 Vienna, Austria phone: +43 (1) 58801-18804 (secretary), fax: +43 (1) 58801-18896 office@big.tuwien.ac.at, www.big.tuwien.ac.at Integrating Performance Modeling in Industrial Automation through AutomationML and PMIF Luca Berardinelli, Emanuel Maetzler, Tanja Mayerhofer, Manuel Wimmer INDIN 2016 July, 18-22, Poitiers, France
- 2. = discipline/domain Context: Need for integration in CPPS engineering process 2= documents = tool • Cyber Physical Production System (CPPS) Engineering is a multidisciplinary engineering process • Different stackeholders bring their own methodologies, tools and docs to carry out different activities during the process • Data exchange is a critical issue within the multidisciplinary CPPS engineering Mechanical Engineer Electronic Engineer Software Engineer … tools docs methodologies discipline Requirements Specification Production System Commitment stakeholders Process
- 3. = discipline/domain Context: Cross-cutting Model-Driven Engineering perspective 3= documents = tool Requirements Specification Production System Commitment • Stakeholders also model engineers: • Documents are models • Tools become model-driven, capable to process models • Discipline-specific methodologies become model-driven MDE Tools model methodologies discipline: MDEMechanical Engineer Electronic Engineer Software Engineer … + stakeholders Process technology
- 4. Goal: Integrating Model-Driven Performance Modeling in CPPS 4 Production SystemRequirements software engineering electronics mechanics integration integration Model Engineer you are here early stages of CPPS design&validation for MDPE Model-Driven Performance Engineering (MDPE) via Queuing Network
- 5. Goal: Integrating Model-Driven Performance Modeling in CPPS 5 MDPE via Queuing Network, do I need it? https://www.arenasimulation.com/industry-solutions/manufacturing-simulation-software http://jmt.sourceforge.net/ a “generic” QN Solver integration PM IF
- 6. Production SystemRequirements software engineering electronics mechanics integration Model Engineer Goal: Integrating Model-Driven Performance Modeling in CPPS you are here integration Both common representations for data exchange in two different domains. AML is a standard PMIF is an academic initiative Why AML and PMIF? PM IF Three possible Integration Mechanisms 6
- 7. Models: AutomationML 7 model PM IF Emerging standard (IEC 62714) for tool data exchange in CPPS Engineering Foundation for harmonizing engineering data coming from a heterogeneous tool network by means of a unified format and data model XML based document (CAEX.xsd) .XSD integration tech. Schema
- 8. Models: AutomationML 8 model PM IF • We provided also a complementary XML-based serialization format for AML top level format (CAEX) based on Ecore • Metamodeling is a key MDE enabling activity • Metamodels are language specification • Ecore is a metamodeling technology integration tech. .ecore metamodel .XSD Schema
- 9. technology Models: AutomationML 9 …or in Ecore, new enabling technology for MDE https://eclipse.org/modeling/emf/ Model Engineer AML in 10 secs slide? AML.xsd XSD cpps_example.aml XML «conforms to» Model (hierarchical graph based structure) a b c d c1 c2 c2.1 … Hierachy prototypes «cloned» c1 c2 roles blue semantics orange semantics interfaces «typing»
- 10. technology Models: AutomationML 10 …or in Ecore, new enabling technology for MDE https://eclipse.org/modeling/emf/ Model Engineer CAEX in 10 secs slide? Model (hierarchical graph based structure) a b c d c1 c2 c2.1 … Hierachy prototypes «cloned» interfaces c1 c2 roles blue semantics orange semantics«assign semantics to» AML.xsd XSD cpps_example.aml XML «conforms to» «typing»
- 11. Models: AutomationML 11 AML Language Specification in Ecore Eclipse Modeling Framework https://eclipse.org/modeling/emf/ IH IE RC concepts for structure modelingconcepts for semantics modeling Model Engineer AML.ecore ECORE cpps_example.aml XML «conforms to»
- 12. Representing a Production System in AutomationML 12 Pick and Place Unit Case Study • The PPU Production System produces different types of tanks • PPU resources are its stations • Tank products are processed by resources in accordance with production processes
- 13. Models: PMIF 13 • common representation for system performance model data to move QN models between analysis and simulation tools • PMIF documents are serialized in XML • PMIF is specified both as XML Schema (.XSD) and as Ecore Metamodel integration tech. model PM IF PM IF .ecore metamodel .XSD Schema workload(s) =jobs queuing network Arrival Rate Service Time Rate
- 14. 14 STACK CRANE STAMP CONVEYOR RAMP 1 2 3 4 5 6 7 2 3 2 4 3 2 4 5 4 6 4 7 Models: AutomationML and PMIF Pick and Place Unit Case Study 2 1 ResourcesProcess Products RAMP RAMP • The PPU Production System produces different types of tanks • PPU resources are its stations • Tank products are processed by resources in accordance with production processes
- 15. Models: Performance Model Interchange Format (PMIF) 15 PMIF.ecore metamodel .XSD Schema PMIF Language Specification in Ecore Eclipse Modeling Framework https://eclipse.org/modeling/emf/ integration tech. model PM IF
- 16. Models: Performance Model Interchange Format (PMIF) 16 STACK CRANE STAMP CONVEYOR RAMP Pick and Place Unit Case Study RAMP RAMP • The PPU Production System produces different types of tanks • PPU resources are its stations • Tank products are processed by resources in accordance with production processes PPU QueuingNetworkModel Two models representing the same PPU system. How can I generate them?
- 17. Integration: conceptual mappings between AML and PMIF 17 CPPS : {{Product}, {Process}, {Resource}} PM IF CPPSs can be described as PPR systems… AML language concepts PMIF language concepts IE STACK RC Resource (from AutomationML standard library) SRC Server «modeled in AML» «modeled in PMIF»
- 18. Integration: conceptual mappings between AML and PMIF 18 with service rate forIE STACK RC (from AutomationML standard library) SRC Process Service Request ч Server PM IF CPPSs can be described as PPR systems… AML language concepts PMIF language concepts «modeled in AML» «modeled in PMIF» CPPS : {{Product}, {Process}, {Resource}}
- 19. Integration: conceptual mappings between AML and PMIF 19 on Shown in the case study IE STACK RC (from AutomationML standard library) SRC Product Workload and arrival rate ч λ PM IF CPPSs can be described as PPR systems… AML language concepts PMIF language concepts «modeled in AML» «modeled in PMIF» CPPS : {{Product}, {Process}, {Resource}}
- 20. Integration: Overview of the PPU Case Study 20 integration PM IF Linking Model AML Native Model Transformation How to implement the conceptual integration?
- 21. Production SystemRequirements software engineering electronics mechanics integration Model Engineer Goal: Integrating Model-Driven Performance Modeling in CPPS 21 MDE Tools model 3 integration mechanisms PM IF integration tech. discipline: MDPE methodologies QN you are here Model-Driven Performance Engineering (MDPE) integration AML Native PM IF integration Linking Model PM IF integration Model Transformation PM IF .link .transf. integration integration
- 22. Integration: PPU - Native AML Integration 22 integration AML Native PM IF XML ID AML.xsd PMIF.xsd XML IDrefURI XSD XSD PPU.xml PPU_QN.xml XML XML languages • Default integration choice when the integration should be carried out through XSD-based tech. • AML ExternalDataConnector XML with refURI xs::anyURI models JAXP Xerces Integration coupled with AML docs. Not a MDE approach. IE
- 23. Integration: PPU - Linking Model 23 integration PM IF AML.ecore PMIF.ecore Ecore PPU.xml PPU_QN.xml XML XML languages models Linking.ecore Ecore Ecore XML LinkModel.xml Linking Model Linking language to create Link Models Links are explicit and static. Manual approach that can be automated by identifing source and target patterns in AML and PMIF models. API IE
- 24. Integration: PPU – Model Transformation 24 integration PM IF AML.ecore PMIF.ecore Ecore PPU.xml PPU_QN.xml XML XML languages models Ecoretxt AML2PMIF.atl Model Transformation Mappings defined among language concepts (not their instances!) Links between models are dynamic, i.e., generated when ATL file is executed. ATL is a transformation language available in Eclipse. The integration is realized with rules with «from» and «to» patterns.ie.hasRole(‘Product’) PMIF!Workload ( IEProduct2Workload( «from» «to»
- 25. Conclusions 1. We presented three different integration mechanisms to support Model-Driven Peformance Engineering (PE) with Queuing Networks in early System Design phases of CPPS 2. We choose two languages, AutomationML (AML) and Performance Interchange File Format (PMIF), devised to ease the integration of heterogeneous tools (and then methodologies adopting these tools) in CPPS and PE domains 3. The integration mechanisms are tool-independent and independent from each other. However, each mechanism imposes some technological requirements on tools (e.g., Java-based libraries). 4. Each integration mechanism has pros and cons. Their adoption is left to the end user. 25
- 26. Future Work 1. Completing the AutomationML and PMIF Integration (PMIF2AML is still missing, can be implemented as Model Transformatiom) 2. Adopting Linking and/or Model Transformation intergration mechanisms in different model-driven methodologies (e.g., reliability analysis) 26