DOCSLIB.ORG

Interoperation in Industrial Automation: an ISO Viewpoint

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Interoperation in Industrial Automation: an ISO Viewpoint Tinwisle Corporation Interoperation in Industrial Automation: an ISO viewpoint Richard A. Martin Convener ISO TC 184/SC 5/WG 1 Interoperation in Industrial Automation: an ISO viewpoint • Context of interoperation • Integration standards • Architecture standards • Interoperability standards • Future Efforts © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 1 Context Integrate Who’s standards Architect Interop. Future ISO/TC 184 Industrial Automation Systems & Integration CEN TC310/WG1 SC 1 SC 2 SC 4 SC 5 Physical Robots and Industrial Architecture, Advisory Device robotic devices Data Communications & Group Control Integration Frameworks PPC Policy & planning committee WG1 WG7 Modeling & Architecture Data modeling for PT1 QC - Quality Committee MT1 Revision of integration of physical Communications & Interconnections ISO 10218 WG2 devices Standard parts library WG4 Manufacturing Software & Environment WG8 WG3 Product Modeling WG5 Distributed installation Application Integration Frameworks in industrial JWG8** applications Manufacturing process and WG6 management information Application Service Interface WG11 WG7 Express language, Diagnostics/Maintenance/Control implementation methods Integration SC5 Chair: Emanuel delaHostria (USA) JWG8** WG12 Manufacturing process and Contact: ISO/TC 184/SC 5 Secretariat Common resources management information [email protected] WG13 JWG15 Industrial data quality Enterprise-Control System Integration SG1 ISA SP95/IEC SC65A Vocabulary and terminology © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 2 Context Integrate NACFAM E-Manufacturing Architect Interop. Future • Interoperability problem is more complex because it requires agreement on certain common principles and features before truly interoperable solutions can emerge. • Solutions must…have the trust and acceptance of the industrial and software communities. • Requires a mechanism to convene the right decision makers to produce the necessary agreement. © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 3 Context Integrate The supply chain effect Architect Interop. • High costs of interoperability Future particularly impact small and medium sized suppliers • They often have to maintain redundant and costly software packages in order to communicate with their large EOM customers. • Large manufacturing companies have pushed costs onto SME’s by requiring “standardization” around their preferred systems. Source: Exploiting E-Manufacturing: Interoperability of Software Systems Used by U.S. Manufactures, NACFAM, Feb. 2001 © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 4 Context Integrate SC5 Working Groups Architect Interop. Future • WG1 – Richard Martin (USA) • WG4 – Michiko Matsuda (Japan) • WG5 – Graeme Meyer (New Zealand) • WG6 - Robert Patzke (Germany) • WG7 – Charles Hoover (USA) • JWG8 – Jean-Jacques Michel (France) •JWG15– Dennis Brandl (USA) © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 5 Context Integrate Interoperability approaches Architect Interop. Future • Integrated – common format for all models agreed by all parties necessary • Unified – common format at a meta- level to enable mapping between models using semantic equivalence • Federated –no common format requires accommodation through a shared ontology © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 6 Context Integrate SC5/WG6 Architect Interop. Future • ISO 20242 a series of 6 parts: –Overview of Service Interface for Testing Applications – Resource Management Service Interface – Virtual Device Service Interface – Device Capability Profile Template – Application Program Service Interface – Conformance test methods • First is published, 2nd in CD • Strong link to ASAM GDI specifications © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 7 Context Integrate SC5/WG 5 Architect Interop. Future • ISO 15745 series of 5 parts: Generic description and 4 specific to shop floor communication protocols • Uses a framework and profiles approach • Work now complete with last amendment approved recently • Systematic reviews will begin 2009 © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 8 Context Integrate Application integration Architect Interop. ISO 15745 – Industrial AutomationFuture system and integration - Open systems application integration framework • Framework identifies: – Elements and rules for integration requirements using integration models – Application interoperability profiles as interface specifications • UML based integration models • XML schemas for profile templates © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 9 Context Integrate SC5/WG4 Architect Interop. Future ISO 16100 Manufacturing software capability profiling for interoperability series of 5 parts: – Framework description (ISO 15745 kind) – Profiling Methodology – Interface protocols – Conformance testing – Profile matching methodology • First 4 published © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 10 Context Integrate Software capability Architect Interop. Future ISO 16100 – • Characterization of software interface requirements • Software unit capability elements & rules • IDEF0 process descriptions, UML models and XML profile schemas “Manufacturing software units shall interoperate with one another, in support of a manufacturing activity, when the services requested by the former can be provided by the latter, using the same operating environment.” © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 11 Context Integrate Capability classes Architect Interop. Future • Manufacturing Capability classes – Domain, Application, Information, Process, Resources, Activity, Function, Software Unit • Software Capability classes – Computing system, Environment, Architecture, Design Pattern, Datatype, Interface/Protocol • Role Capability class © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 12 Context Integrate SC5/JWG15 Architect Interop. Future ISO/IEC 62264 Enterprise-control system integration series of 5 parts: – Models and terminology – Object models and attributes – Activity models of manufacturing operations management – Object models and attributes of manufacturing operations management activities – Business to manufacturing transactions • First 3 parts published © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 13 Context Integrate A boundary standard Architect Interop. Future ISO/IEC 62264 Enterprise-control system integration – Object models for interfaces between enterprise business systems and manufacturing control systems Functions outside the control domain Information flows of interest (for example, (for example, production scheduling) production schedule and production results Enterprise-control system boundary Functions within the control domain (for example, equipment monitoring) © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 14 Context Integrate Product definition model Architect Interop. Future In this part of IEC 62264, the word “Class” used as part of an object definition name is to be considered as a category, not as a “Class” in the object- oriented sense. IS 62264 Figure 8. © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 15 Context Integrate MES & ERP integration Architect Interop. Future • IS 62264 is better known as ISA95 • Selected by SAP and others as basis for MES to ERP information integration • Part 4 and 5 are slower to emerge • Diversity in implementation results in incompatibility among vendor solutions • A middle-ware market will evolve © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 16 Context Integrate SC5/WG7 Architect Interop. Future • ISO 18435 a series of 3 parts for diagnostic and maintenance of manufacturing assets: – Overview and general requirements – Descriptions and definitions of application domain matrix elements – Application integration description methods • First is in CD stage • Strong link to MIMOSA OSA © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 17 Context Integrate Domains & Operation levels Architect Interop. Future A4.1 – Intra-enterprise activities: Business A4.2 – Inter-enterprise activities: Supply Chain Level R4 Planning, Orders & Production, and Planning, Logistics Strategy Enterprise / Maintenance Site A3.2 – Capability A3.1 - Operations Assessment & A3.3 - Maintenance Level R3 Planning & Scheduling Order Fulfillment Planning & Scheduling Area A2.2 - Asset Prognostics A2.1 - Supervisory Control and Health, Quality, A2.3 - Maintenance & Human-Machine Safety, & Environmental Execution & Tracking Level R2 Interface Management Work Center A1.1- Control, I/O,Data Acquisition, A1.2 - Asset Condition A1.3 - Asset Data Historian, Asset Monitoring & Sample / Configuration, Level R1 Utilization, Test / Diagnostic Calibration & Repair / Work Unit & Displays & Quality Monitoring Replace A0.1 - Resource A0.2 - Asset Level R0 Identification and Location Identification and Location Asset Assets Resources (Equipment / Facilities / Serialized Components / ( Material / Personnel ) Sensors / Transducers / Software / Documents) © Copyright 2006 by Richard Martin Prepared for OMG-ManTIS & SE DSIG Dec. 2006 18 Context Integrate SC5/JWG8 Architect
Load more

Recommended publications
  • IFIP Advances in Information and Communication Technology 326
    IFIP Advances in Information and Communication Technology 326 Editor-in-Chief A. Joe Turner, Seneca, SC, USA Editorial Board Foundations of Computer Science Mike Hinchey, Lero, Limerick, Ireland Software: Theory and Practice Bertrand Meyer, ETH Zurich, Switzerland Education Bernard Cornu, CNED-EIFAD, Poitiers, France Information Technology Applications Ronald Waxman, EDA Standards Consulting, Beachwood, OH, USA Communication Systems Guy Leduc, Université de Liège, Belgium System Modeling and Optimization Jacques Henry, Université de Bordeaux, France Information Systems Barbara Pernici, Politecnico di Milano, Italy Relationship between Computers and Society Chrisanthi Avgerou, London School of Economics, UK Computer Systems Technology Paolo Prinetto, Politecnico di Torino, Italy Security and Privacy Protection in Information Processing Systems Kai Rannenberg, Goethe University Frankfurt, Germany Artificial Intelligence Max A. Bramer, University of Portsmouth, UK Human-Computer Interaction Annelise Mark Pejtersen, Center of Cognitive Systems Engineering, Denmark Entertainment Computing Ryohei Nakatsu, National University of Singapore IFIP – The International Federation for Information Processing IFIP was founded in 1960 under the auspices of UNESCO, following the First World Computer Congress held in Paris the previous year. An umbrella organi- zation for societies working in information processing, IFIP’s aim is two-fold: to support information processing within its member countries and to encourage technology transfer to developing nations. As its mission statement clearly states, IFIP’s mission is to be the leading, truly international, apolitical organization which encourages and assists in the development, ex- ploitation and application of information technology for the benefit of all people. IFIP is a non-profitmaking organization, run almost solely by 2500 volunteers. It operates through a number of technical committees, which organize events and publications.
    [Show full text]
  • A Modelling Language for User Oriented Enterprise Modelling
    3e Conférence Francophone de Modélisation et SIMulation "Conception, Analyse et Gestion des Systèmes Industriels" MOSIM'01 - du 25 au 27 avril 2001 - Troyes(France) A MODELLING LANGUAGE FOR USER ORIENTED ENTERPRISE MODELLING Martin ZELM Kurt KOSANKE CIMOSA Association e.V. CIMOSA Association e.V. Gehenbühlstr. 18 A, D-70499 Stuttgart Stockholmer Str. 7, D-71034 Böblingen Mél . [email protected] Mél . [email protected] Abstract: Enterprise modelling provides the means to structure and decompose the enterprise system into less complex parts and to describe functionality and behaviour of the operation or any part thereof. The relevant enterprise knowl- edge can be captured, shared and managed through process models. Process models describe both the functionality and the flow of control in the enterprise and identify all the needed and produced information. However, the user should employ a modelling language consisting of modelling constructs relevant for the representa- tion of his business. Constructs, which provide means for easy information capturing and are represented by easy to understand graphical symbols or icons. Both, common modelling construct types and their representation by icons will make the modelling process more effective and efficient and also improve the human understanding of enterprise mod- els. The latter is especially important for the upcoming e-business to business and virtual enterprise type operations. Only with increased efforts in harmonisation and standardisation, will the envisaged improvements be realised. Starting from the CIMOSA reference architecture the paper proposes structuring of user oriented modelling construct types and type hierarchies and presents an overview of construct icon types for graphical representation used in differ- ent modelling tools.
    [Show full text]
  • Cimosa CSE Kosanke
    Enterprise Modelling - from CIMOSA to CSE-OSA (Computer Integrated Manufacturing to Computer Supported Enterprise) By Kurt Kosanke, former CIMOSA Association Abstract: CIMOSA (Computer Integrated Manufacturing Open System Architecture) has been developed during a time where the focus was on Manufacturing. However it was clear from the very beginning that its process-oriented concepts can be applied to any en- terprise. This paper presents a summary of the CIMOSA concepts starting with some general remarks on enterprise modelling and a short review of the CIMOSA history. Since the emphasis in most enterprises has shifted towards heavy collaboration between individual organisations, this paper also addresses the capabilities of CIMOSA in this in- ter-organisational field of enterprise modelling. Details of the extension of the CIMOSA specification are briefly discussed and presented in a separate paper (to be published) that describes the capabilities for both intra and inter-organisational communications in- cluding the proposed extension of the CIMOSA templates. Introduction Enterprise modelling has been a subject of trial and error throughout human history. Even early civilisations identified organisational models by assigning responsibilities and authorisation to hierar- chies of people. Such position assignments have been made public by titles, uniforms and status sym- bols like castles, palaces, etc. and a clear assignment of numbers of subordinates. But with the increase of enterprise complexity in the military and even more in the commercial area the need for a common understanding among participants about their common enterprise lead soon to the widely used form of organisation chart to document the organisational model of the enterprise. However any enterprise requires also some more or less rigor thinking about the possible thread of actions to take place during the undertaking as well as of needed supply and resources.
    [Show full text]
  • 2. Standards in Enterprise Inter- and Intra-Qrganisational Integration Kurt Kosanke CIMOSA Association Kosanke(A).T-Online
    2. Standards in Enterprise Inter- and Intra-Qrganisational Integration Kurt Kosanke CIMOSA Association kosanke(a).t-online. de World-wide collaboration and co-operation of enterprises of all sizes increases the need for standards supporting operational interoperability in the global environment. Such standards are concerned with the communication aspects of information and communication technology (ICT), like communication proto­ cols as well as the syntax and semantics of the communication content. Communicating parties have to have the same understanding of the meaning of the exchanged information and trust both the communication itself and the validity^ of its content. Focus of the paper is on business process modelling and its standardisation in the area of enterprise inter- and intra-organisational integration. Relations to the subject of interoperability are discussed. Keywords: business process modelling, enterprise integration, enterprise engineering, standardisation. 1. INTRODUCTION Business in today's global environment requires the exchange of physical products and parts and even more importantly the exchange of the related business information between co-operating organisations. The latter is true for such an operation itself, but to an even larger extent for the decision making processes during the establishment of the cooperating enterprise with market opportunity exploration and co-operation planning and implementation. The need for a knowledge base to be used for organisational interoperation and decision support on all levels of the enterprise operation is recognised as an urgent need in both business and academia (Kosanke et al 2002). Building and maintaining the enterprise knowledge base and enabling its efficient exploitation for decision support are major tasks of enterprise engineering.
    [Show full text]
  • KNOWLEDGE SHARING in the INTEGRATED ENTERPRISE IFIP - the International Federation for Information Processing
    KNOWLEDGE SHARING IN THE INTEGRATED ENTERPRISE IFIP - The International Federation for Information Processing IFIP was founded in 1960 under the auspices of UNESCO, following the First World Computer Congress held in Paris the previous year. An umbrella organization for societies working in information processing, IFIP's aim is two-fold: to support information processing within its member countries and to encourage technology transfer to developing nations. As its mission statement clearly states, IFIP's mission is to be the leading, truly international, apolitical organization which encourages and assists in the development, exploitation and application of information technology for the benefit of all people. IFIP is a non-profitmaking organization, run almost solely by 2500 volunteers. It operates through a number of technical committees, which organize events and publications. IFIP's events range from an international congress to local seminars, but the most important are: • The IFIP World Computer Congress, held every second year; • Open conferences; • Working conferences. The flagship event is the IFIP World Computer Congress, at which both invited and contributed papers are presented. Contributed papers are rigorously refereed and the rejection rate is high. As with the Congress, participation in the open conferences is open to all and papers may be invited or submitted. Again, submitted papers are stringently refereed. The working conferences are structured differently. They are usually run by a working group and attendance is small and by invitation only. Their purpose is to create an atmosphere conducive to innovation and development. Refereeing is less rigorous and papers are subjected to extensive group discussion. Publications arising from IFIP events vary.
    [Show full text]
  • Modelling and Methodologies for Enterprise Integration IFIP - the International Federation for Information Processing
    Modelling and Methodologies for Enterprise Integration IFIP - The International Federation for Information Processing IFIP was founded in 1960 under the auspices of UNESCO, following the First World Computer Congress held in Paris the previous year. An umbrella organization for societies working in information processing, IFIP's aim is two-fold: to support information processing within its member countries and to encourage technology transfer to developing nations. As its mission statement clearly states, IFIP's mission is to be the leading, truly international, apolitical organization which encourages and assists in the development, exploitation and application of information technology for the benefit of all people. IFIP is a non-profitmaking organization, run almost solely by 2500 volunteers. It operates through a number of technical committees, which organize events and publications. IFIP's events range from an international congress to local seminars, but the most important are: • the IFIP World Computer Congress, held every second year; • open conferences; • working conferences. The flagship event is the IFIP World Computer Congress, at which both invited and contributed papers are presented. Contributed papers are rigorously refereed and the rejection rate is high. As with the Congress, participation in the open conferences is open to all and papers may be invited or submitted. Again, submitted papers are stringently refereed. The working conferences are structured differently. They are usually run by a working group and attendance is small and by invitation only. Their purpose is to create an atmosphere conducive to innovation and development. Refereeing is less rigorous and papers are subjected to extensive group discussion. Publications arising from IFIP events vary.
    [Show full text]
  • CIMOSA Association Ev
    CIMOSA Association e.V. CIM c/o K. Kosanke Tel: (49) 7031 27 76 65 Stockholmer Str. 7 FAX: (49) 7031 27 66 98 OSA D-71034 Böblingen e-mail: [email protected] Böblingen, 2010-03-01 CIMOSA History 1984 – 2009 by Kurt Kosanke and Martin Zelm, CIMOSA Association e.V. Part 1 ESPRIT Project AMICE developed in 4 consecutive projects by consortia with up to 33 participating organisations 1984 – 1994 Date Work Items Main results 1984 ESPRIT (European Strategic Programme for proposals submitted by 4 consortia, Research in Information Technology), European Commission recommendation: resubmit 1st Call for Proposals on CIM Architectures joined proposal 1984 AMICE (European CIM Architecture) Techn. Report: Project organisation, CIM Archi- - ESPRIT Project 688; tecture basic concepts, Standardisation 1985 Project definition phase 1985 AMICE - ESPRIT Project 688: Project Deliverables: Architecture Description 1.0 - Project development Phase I 1989 Publication CIMOSA AMICE (Eds.), “Open Systems Architec- ture for CIM”, Springer-Verlag, 1989 (Japanese translation 1993) 1989 AMICE - ESPRIT Project 2422: Project Deliverables: Architecture Description 1.1 - Project development Phase II 1990 Standardisation CEN ENV 40003:1990 “Framework for Enterprise Modelling” 1990 AMICE - ESPRIT Project 5288: Project Deliverables: Architecture Description 1.1 - Project development Phase III 1991 Publication AMICE (Eds.) “Open Systems Architecture for CIM”, 2nd Edition, Springer-Verlag; 1991 1991 AMICE - ESPRIT Project 7710: Project Deliverables: Project final report, CIMOSA - Project development Phase III/P Technical Baseline 3.0, 1994, 1994 Pilot implementation and demonstration of CIMOSA at WZL, Aachen/Germany, 1994 Cooperations SIG-CCVP (Special Interest Group - Cooperation for CIMOSA Validation and Promotion) with ESPRIT Projects AMICE, CIMPRES, CODE and VOICE Europe – USA cooperation with 4 Workshops: Europe 2, USA 2 and International Conference ICEIMT’92 (Intern.
    [Show full text]
  • CIMOSA Process Model for Enterprise Modelling
    6 CIMOSA process model for enterprise modelling Kurt Kosanke(1), Fram;ois B. Vernadat(2), M Zelm(1) (1) ClMOSA Association e. v., Stockholmerstr. 7, D-71034 B6blingen, Germany (2) Universite de Metz, LGlPM, lie du Saulcy, F-57045 Metz Cedex 1, France Abstract CIMOSA is an open systems architecture for CIM developed by the ESPRIT Consortium AMICE. It structures a CIM system as a set of concurrent communicating processes executed by a finite set of functional entities. Modelling is based on a three-stage, process-based enterprise modelling approach (for business requirements definition, system design specification and implementation description). This paper presents the CIMOSA process model. It covers functionallbehavioural, information, resource and organisation aspects of an integrated enterprise at each modelling level. The approach enforces the genericity and reusability principles by the use of generic building blocks to build partial models and particular models. Keywords CIMOSA, Enterprise Integration, Enterprise Modelling, Business Process Modelling, Workflow 1 INTRODUCTION Enterprise modelling is a prerequisite to enterprise integration (Vernadat, 1996). Enterprise integration (EI) is concerned with breaking down organisational barriers and harmonising business process execution within an enterprise or the extended enterprise to improve efficiency by creating a synergistic whole. Enterprise modelling is also a central activity in Business Process Reengineering (BPR). BPR consists of simplifying enterprise processes to reduce excessive delays or costs in the enterprise operations. Various approaches have been proposed for enterprise modelling. Among these, we can mention the IDEF suite of models (ICAM, 1981) or the GRAI-GIM method (Doumeingts et al., 1992) as early methods which were strongly activity-based.
    [Show full text]
  • CIMOSA - Overview and Status
    ELSEVIER Computers in Industry 27 (1995) 101-109 CIMOSA - Overview and status Kurt Kosanke * CIMOSA Association (e.V.), Stockholmer Str. 7, D-71034 Btiblingen, Germany Abstract Starting from the identification of the increased need for enterprise integration and real-time and up-to-date information, the paper briefly describes the CIMOSA concept, the enterprise modelling solution for identification of available information and its use in the ope.rational processes of the manufacturing enterprise. CIMOSA has been developed by the ESPRl’I‘ Consortium AMICE and has been validated together with the ESPRIT projects CIMPRES, CODE and VOICE in multiple case studies and pilot implementations. Validation results have been used to improve the technical specifications of CIMOSA. Exploitation of CIIMOSA has been started in the area of enterprise modelling, modelling tool developments and further enhancement of industrial pilot implementations of the Integrating Infrastructure. These efforts are being complemented by promotional activities aimed at increasing enterprise integration awareness and acceptance and support of standard&&ion activities on national, European and international level. Enterprise integration has not yet become the common industrial goal, nor the specific day-to-day operational tool in the manufacturing community that it should be. Lean enterprises, business re-engineering, concurrent engineering, management of change - identified as current management concerns - should be viewed as subsets of enterprise integration. The engineering of the enterprise has to be become an engineering discipline in its own right in order to solve the many problems in the operation of enterprises of the future. Keywords: Enterprise integration; Enterprise modelling; CIMOSA, CIM; Open System Architecture 1.
    [Show full text]