centurio.work - Modular Secure Manufacturing Orchestration

Transcription

1 centurio.work - Modular Secure Manufacturing Orchetration Florian Pauker, Juergen Mangler, Stefanie Rinderle-Ma, Chritoph Pollak Autrian Comptetence Center for Digital Production, Vienna, Autria, {juergen.mangler, florian.pauker, chritoph.pollak}@acdp.at Univerity of Vienna, Faculty of Computer Science, Reearch Group Workflow Sytem and Technology, Vienna, Autria, tefanie.rinderle-ma@univie.ac.at Abtract. Organiational and technical procee of manufacturing companie are becoming more and more complex while the preure for flexibility increae. The bigget challenge here i till the integration of different ytem in a coherent tranparent way. In order to further vertical integration in the automation pyramid, thi paper preent a olution baed on ue BPM technology, more pecifically proce modelling and execution baed on BPMN to integrate hopfloor with top level planning. Our full-tack olution i currently in active development with our cutomer. One main advantage i that through coherent uage of BPMN procee from top to bottom, all monitored data during execution can alway be tored in the right context, which ave a lot of effort compared to the tate of the art in manufacturing ytem. 1 Introduction In today global competition, manufacturing companie mut adapt their technical procee and reource to contantly changing condition. Additionally the demand to maller lot ize i increaing and o higher flexibility i needed. In thi high mix low volume environment, the ue of digital tool i becoming increaingly important. Data management in the factory relie on information flow that acce different ytem. The problem in many manufacturing companie i that mot oftware tool are hard-coded tand-alone olution with no or proprietary oftware interface. Thi poe a huge interoperability challenge. The lack of oftware interface compatibility make data exchange between individual application difficult and increae the effort of integrating new ytem. Tailor-made oftware olution are often ued for coupling the individual oftware olution. Thi kind of hard-coded integration can uually only be maintained, changed and expanded by oftware developer. Thi lead to high maintenance cot due to the complexity. What intead i required i an infratructure that enable efficient adaptation of ytem orchetration. Current initiative like Indutry 4.0 (I4.0), Indutrial Internet of Thing (IIoT) demand a fully connected environment coniting of o called Cyberphyical Sytem (CPS). CPS are object coniting of a phyical part with an F. Caati et al. (Ed.): Proceeding of the Diertation Award and Demontration, Indutrial Track at BPM 2018, CEUR-WS.org, Copyright c 2018 for thi paper by it author. Copying permitted for private and academic purpoe. Thi volume i publihed and copyrighted by it editor.

2 Florian Pauker, Juergen Mangler, Stefanie Rinderle-Ma, Chritoph Pollak virtual repreentation which can communicate with other CPS over a partially global network [4]. Thi technology approach lead to new infratructure in companie. The well known automation pyramid [10], decompoe to looely coupled ervice that interact with each other and the hardware and enor on the field level (ee Fig. 1). Enterprie reource planning level {..} Plant management level Proce control level Control (PLC) level Field level BPMN/Proce-baed Automation Automation Hierarchy CPS-baed Automation Fig. 1: Decompoition of the Automation Pyramid [10] The contribution of thi paper i the centurio.work approach for implifying the integration of heterogeneou ytem throughout the whole automation pyramid, by utilizing a true ervice-oriented oriented approach and advance like the BPMN [7] modelling language, and flexible execution [1,5]. A een in Fig. 1 In Sect. 2 we tart out by decribing currently exiting tandard and requirement on the hopfloor (lower level of the automation pyramid). In Sect. 3 we then decribe the overall architecture of the ytem in relation to the hopfloor requirement. In Sect. 4 when then decribe how the architecture i adapted by our cutomer. 2 Modelling of Shopfloor Procee For orchetration of manufacturing different olution are available. Thee olution typically depend on the hierarchy level in the automation pyramid [10]. For orchetration of procee on Control level graphical language are ued a a bai. Graphchart [11] i one example for a graphical language for equential uperviory control of ytem. It i baed on Sequential Function Chart (SFC), one of the programming language for PLC decribed in IEC [2]. On higher organization level other language like BPMN or BPEL are ued. For lower level traditional programming i prevalent. One requirement of Cyber-phyical Sytem (CPS) baed automation i the need of orchetrating different ervice, which i implemented e.g. by the Manufacturing Service Bu (MSB) [6], an pecialization of the Enterprie Service Bu. The main integration ervice of an ESB are: (i) tranformation ervice that bridge difference in data format and data model; (ii) a routing ervice

3 centurio.work - Modular Secure Manufacturing Orchetration that handle meage and end them to deignated recipient; and (iii) an orchetration ervice which ue predefined proce model and control the flow of meage between ervice conumer and ervice provider. For different artefact, uch a orchetration and integration ervice, different language are ued e.g BPEL and XSLT, which lead to rather unneceary complexity. In other word: the MSB i truggling to gain traction with companie becaue it i a medley of technologie and component with high configuration and maintenance complexity. To the bet of our knowledge only one implementation [9] exit. The motivation for the centurio.work framework i to bring down the complexity of introducing an MSB (or ESB) by configuring the bag of adapter and tranlation, and meage exchange component through BPMN procee, thu uing a ingle concept of configuring, uing and maintaining infratructure. 3 Modular Secure Manufacturing Orchetration centurio.work wa deigned a an interoperability and integration framework for manufacturing companie. The motivation i bringing the flexibility of Buine Proce Management Sytem from the management level to the hopfloor. Fig. 2 how the architecture of the framework. Deign Reaon Feedback Prepare Proce Deign Reource / IEC Data Aggregation Utility App Plan M Reource Deigner Procee Machine NC/Robot Program Tranformation and Filtering Data Analyi Cloud Service Tool Data Orchetration Tranformation and Filtering Buine Intelligence Tranportation Uer / Operator Robot Shopfloor Machine OPC-UA MQTT HTTPS Execution Control Proce Execution Data Proviioner Buine MRP Intelligence Connector Fig. 2: centurio.work Architecture The centurio.work framework wa deigned from the ground up with ecurity in mind. It group application into four context that are trictly eparated and are allowed to either puh or read data. The arrow repreent the data flow between thee context. While every component inide a context i intended to be replaceable, the arrow repreent trictly defined protocol, data format and ecurity mechanim. Context which are not connected by arrow do not interact. Orchetration component are allowed to acce Reource and can puh information to Data Aggregation component. Data Aggregation component provide Data to Utility App but data change i not allowed.

4 Florian Pauker, Juergen Mangler, Stefanie Rinderle-Ma, Chritoph Pollak The centurio.work framework tore tatic (deign-time) information in the reource context. Thi information tem from variou company ytem and i fingerprinted upon inertion to be able to detect corruption and tampering. For interacting with the hopfloor (run-time) centurio.work upport different interface. For orchetration of hop floor equipment OPC-UA i preferred olution. OPC-UA ha trong modelling capabilitie and i an agreed-upon tandard for European companie. So the hopfloor equipment can offer their abilitie a OPC-UA method and tatic information a variable and propertie. Therefore, we can utilize the client erver paradigm and the built in ecurity mechanim of OPC-UA e.g. uer authentication and certificate. Additionally MQTT upport i built in becaue of it light-weight publih/- ubcribe mechanim and the poibility to run on embedded ytem. Thi i epecially ueful for high-performance data gathering. The centurio.work Execution Engine itelf i configured to puh data for certain topic to Data Aggregation component. In other word: it communicate with Data Aggregation App through a ecure publih/ubcribe mechanim. 3.1 Reource There exit ome baic type of reource, which may be utilized by the Orchetration component. The Procee which provide a logic for coordinating the interaction between different machine. They define equence of interaction with deciion and parallel execution. Procee typically refer to other information Reource, uch a pecific Machine, NC/Robot Program, and Tool-Data. Proce of coure may alo acce thi information a run-time, e.g. to decide which machine to utilize for a certain job. The tructure of the Reource container i baed on the IEC [3]. The Reource context may acceed from the outide to add or modify procee and other tatic data. 3.2 Orchetration Component Thi context i the ole context that i allowed to interact with the hopfloor. It doe o by utilizing procee, which in turn contain all information how to interact with machine for the purpoe of production and for the purpoe of monitoring. Currently three type of app can exit in thi context: (i) An Execution Control App which allow to tart and modify procee at runtime in the cae of error (ii), an Execution Engine which enact the procee and (iii) a Data Proviioner which act a an efficient gateway for machine that have the capability to puh enor data to ubcriber. The Execution Engine in turn i the ole ource of data that i available to Data Aggregation. It puhe all apect of interaction with machine to thee Data Aggregation component, which may (or may not) filter, tranform or otherwie proce and tore thi data. Data may be duplicated, a each Data Aggregation App erve one pecific purpoe, and i to tructure data for optimum performance and uability.

5 centurio.work - Modular Secure Manufacturing Orchetration 3.3 Data Aggregation App Data Aggregation App, may (or may not) filter, tranform or otherwie proce and tore data. Each app i intended to implement it torage and an interface how to acce thi torage. Data Aggregation App may: (i) log the execution (ii) log / monitor the execution for poible ecurity violation (Secure Logging), and (iii) calculate Key Performance Indicator (like Overall Equipment Efficiency) of the equipment or the proce. They may alo (iv) aggregate data o that Utility App can efficiently perform their tak. We ue tandard uch a IEEE XES 1 and tool uch a InfluxDB to allow for optimized acce by Utility App implementing dah-boarding and data- and proce analytic. 3.4 Utility App All other app/function are intended to run in thi context. The baic function of Utility App are to read data tored in Data Aggregation context. The App alo can interact with each other and can additionally implement their own torage. A containerization alutation e.g. Docker i ued to fulfil thee requirement and to increae the uability for cutomer. Thee App are alo the bai for improvement recommendation, which in ome cae (e.g. optimization for the invocation of machine) automatically flow back into to the Reource context, or be paed on a document to human which may decide how the proce tructure or it parameter can be changed. 4 Example Scenario From Our Cutomer centurio.work wa created a the reult of feedback from our cutomer. In order to evaluate it applicability in an iterative manner, it i deployed in an increaing number of mall and medium Autrian enterprie. Some ue cae which have been developed and teted are decribed in the following. 4.1 Orchetration of a Manufacturing Proce A propoed in [8] for orchetration of a flexible manufacturing cell, on a hardware level, we need ome atomic operation. Current retriction for thee are the real time capabilitie of interface and network infratructure. Some tak have to be performed on the real time controller of the machine. Typically we have different granularity on different level in a manufacturing company (cmp. Fig. 3). Thi i repreented in the automation pyramid a different level which have different requirement on information, communication and data granularity. Approache like the MSB ue different modelling language for the different level. centurio.work ue BPMN for all level, o we have a eamle modelling and proce execution from buine to hopfloor. Fig. 3 how a common proce in a company with different information granularity in each level. On the top level (ERP) the proce owner only ee a proce coniting of three tak, order, produce and deliver. 1 [Lat acceed: ]

6 Florian Pauker, Juergen Mangler, Stefanie Rinderle-Ma, Chritoph Pollak ERP Order Produc on Background Ditribu on to oh igh MES Logi c Produce Part QA vib ra {..} on == Set-Up Fetch Data Check Statu SCADA Statu Bad Saw Part Saw Part Turn Part Mill Part Statu Good Aembly Fig. 3: Example Proce with Hierarchy The production planning need more information of the Production proce. Thu the ub proce i more detailed with additional information on how to get the raw material and how to et up the machine. A worker on the hopfloor i involved in a ubproce with all tak to produce individual part. Additionally there are ome background procee which for example gather enor data from machine or calculate KPI (cmp. Sect. 4.3). 4.2 Worker Machine Interaction Currently on the hopfloor, human involvement i bound to hard-coded oftware on the machine. The big advantage of centurio.work i the independent coordination of human tak with tak from oftware ytem or machine. A implified proce for etting up a machine (equip the machine with cutting tool) i diplayed in Fig. 4. In the firt tak the proce interact uing a UI with the worker. After finihing the tak the next proce tep i executed. All information which are diplayed on the UI are defined in the proce tak. Setup Machine excluive {..} data.etup == 'ok' Produce Part Fig. 4: Setup and Produce

7 centurio.work - Modular Secure Manufacturing Orchetration 4.3 Data Collection for Traceability While traditionally data i collected individually for each machine, and i contextualized a part of a data analyi, in the centurio.work framework all data i collected from a ingle ource, the Proce Execution component. There i alway an explicit connection between all monitored data artefact. Thi hold true even when only oft integration i required: i.e. when machine are not actively triggered, but jut paively monitored without any change to hopfloor at all. Fig. 5 how a implified verion of the procee at our cutomer plant. One background proce monitor the NC machine and if a NC Program i tarted it pawn a new intance of the machining proce. The generated data i buffered in the Data Aggregation context. Correct Queue Liten to NC tart true () excluive data.let_continue () Fetch Statu excluive {..} data.intance.empty? Sleep {..} data.tep < 35 Statu Bad Spawn Machining Subproce Statu Good (a) Spawn Machining Proce (b) Machining Proce Fig. 5: Procee for data collection of a NC-machine 5 Concluion and Outlook On the hopfloor ome of the challenge hindering tight IT integration are: Enterprie ervice bu (ESB) baed ytem provide the neceary ingredient, but require a lot of time and know-how to introduce, to configure and to maintain and are thu are typically employed only by big companie. Smaller companie typically have home-grown olution that work. The hop floor i heterogeneou and machine manufacturer often till focu on building upport for actively communicating with other machine into their proprietary oftware (reulting in a Meh-Topology). Open, well documented interface for their own feature are adly till rare.

8 Florian Pauker, Juergen Mangler, Stefanie Rinderle-Ma, Chritoph Pollak Although OPC-UA gain traction, it focu i on tandardizing the metamodel how to interact with machine. While taking away ome communication iue, all the emantic iue remain. centurio.work focue on olving the above challenge by (1) providing a et of tandardized component which can be deployed without any configuration. All configuration i handled through modelling BPMN procee for improved uability. (2) Experience value and improvement can eaily flow back into the tored procee, intead of flowing back into configuration of individual component, or flowing back into tatic code. Thi again i a main uability improvement for our cutomer. (3) The bu topology with a centralized Orchetration Engine, allow for all the uual advantage like tandardized monitoring and ecurity auditing. centurio.work focue on a plug&play infratructure, while moving all complexity into eay to interact with BPMN procee. Acknowledgement: Thi work ha been partially upported and funded by the Autrian Reearch Promotion Agency (FFG) via the Autrian Competence Center for Digital Production (CDP) under the contract number Reference 1. Dadam, P., Reichert, M., Rinderle, S., Jurich, M., Acker, H., Göer, K., Kreher, U., Lauer, M.: Toward Truly Flexible and Adaptive Proce-Aware Information Sytem. In: Int l Conference UNISCON. pp (2008) 2. DIN Deutche Intitut für Normung e. V.: IEC : Speicherprogrammierbare Steuerungen-Teil 3: Programmierprachen. Berlin: Beuth (2003) 3. DIN Deutche Intitut für Normung e. V.: IEC Enterprie control ytem integration (2016) 4. Geiberger, E., Broy, M.: agendacps: Integrierte Forchungagenda Cyber- Phyical Sytem, vol. 1. Springer-Verlag (2012) 5. Mangler, J., Rinderle-Ma, S.: CPEE - Cloud Proce Exection Engine. Eindhoven (Sep 2014), 6. Minguez, J., Lucke, D., Jakob, M., Contantinecu, C., Mitchang, B., Wetkämper, E.: Introducing SOA into production environment the manufacturing ervice bu. 43rd. CIRP International Conference on Manufacturing Sytem, Vienna (2010) 7. OMG: Buine Proce Model and Notation (BPMN) Verion 2.0. OMG Document formal/ (Jan 2011), 8. Pauker, F., Ayatollahi, I., Kittl, B.: Service Orchetration for Flexible Manufacturing Sytem uing Sequential Functional Chart and OPC UA. IN-TECH - International Conference on Innovative Technologie 9, (2015) 9. Schel, D., Henkel, C., Stock, D., Meyer, O., Rauhöft, G., Einberger, P., Stöhr, M., Daxer, M.A., Seidelmann, J.: Manufacturing ervice bu: an implementation. In: 11th CIRP Conf. Intell. Comput. Manuf. Eng. (2017) 10. VDI/VDE-Geellchaft Me-und Automatiierungtechnik, Kowalewki, S.: Cyber-phyical ytem: Chancen und Nutzen au Sicht der Automation. VDI/VDE-Geellchaft Me-und Automatiierungtechnik (2013) 11. Årzén, K.E.: Grafchart: A graphical language for equential uperviory control application. IFAC Proceeding Volume 29(1), (1996)