.
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Industrial Operations / Information Processing Convergence Control Chain Management Body Of Knowledge
MI Enterprise Language Standards
04/2011
Jean Vieille
www.syntropicfactory.com j.vieille@syntropicfactory.com
Research community www.controlchainmanagement.org Consulting group: www.controlchaingroup.com
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
2
Introduction
The Enterprise organism keeps morphing itself Ø Achieving the Darwinian process of its existence by developing objective knowledge to its advantage Ø Fighting entropy, securing survival, enabling progress Ø Ensuring that thinking people and machines understand each other and the system they live in Hypercritical complexity Ø quantity and quality of interactions Ø spouts "emerging properties", Culture, Intelligence, Auto-organization Ø Developing new, higher ranking behavior Ø Not deductible from their individual components The Syntropic Factory focuses on becoming a smarter organism Ø Developing its "intelligence"
MI - Enterprise Language Standards
3
Conditions of intelligence
A product of complexity, Intelligence raises from Ø Ability to develop knowledge § Enabling cycling between subjective experience and objective knowledge Ø Ability to share knowledge § Enabling seamless storage and access to relevant knowledge Ø Ability to interact § Enabling understandable communications between components Ø Individual intelligence § Sophisticated components performing locally § At the advantage of the whole system Secondary level behavior Ø Creativity Ø Risk assessment and management § Securing actions against uncertainty
MI - Enterprise Language Standards 4
Language
Objective knowledge is out of reach Ø It exists independently of its actual understanding by human, machines Language is the means for handling knowledge Ø Language defines basic concepts (vocabulary) and rules (grammar) for expressing knowledge Existence of a language is a pre-condition for intelligence
MI - Enterprise Language Standards
5
Enterprise knowledge
Covers many domains Addresses tangible and intangible information. For Industrial facilities operations Ø Tangible knowledge § Resources and capabilities (equipment, people, material, energy...) Ø Intangible knowledge § Know-how not formalized Enterprise knowledge covers Ø Public knowledge § Readily available Ø Private knowledge § Represents the enterprise essence § Might need to be protected from competitors' eyes
MI - Enterprise Language Standards
6
Enterprise language
Tangible outcome of the language: Ø meaningful, non ambiguous messages for knowledge exchange, storage, retrieval Ø Support the description of enterprise structural and behavioral aspects on the time scale Must serve both Human and IT relationship Ø Understandable by people and machines Ø Machine, being notably stupid, need extended, precise formalism to understand
MI - Enterprise Language Standards
7
Elements of the enterprise language
Natural language accommodate most of human interactions Machines need more formalism The enterprise language is a formal ontology Ø A semantic tree Ø Defining concepts associated with lexicon (translations, synonyms,) Ø Structured successively in § simple abstract concepts i.e. « Identifier » « Description » § General concepts i.e. « « activity », « Resource » § business concepts as references for actual business entities mentioned in messages Ø Describing relationships and value domains
MI - Enterprise Language Standards
8
Public knowledge and standards
Standards expose public knowledge Ø Enterprise generic concepts (public knowledge) is well covered by available standards Acquiring appropriate public knowledge is part of the enterprise knowledge / intelligence development Ø Ignoring public knowledge forces to reinvent the wheel Ø Leveraging public knowledge § Saves effort and time, § Catalyze private knowledge development, § Accelerates intelligence development Many overlapping standards, more or less focused This study present some relevant standards to establish an enterprise language
MI - Enterprise Language Standards
9
Applicable standards
Reference Title Domains ULO - Data structures for elementary concepts ULO - Neutral Upper level ontology ULO - Upper level ontology of enterprise concepts ULO - Generic enterprise concepts Upper level ontology Generic enteprise concepts Manufacturing operations specific concepts Manufacturing specific concepts Semantic registry ISO15000-5 ebXML - Core Componenet Technical UN/Cefact CC Specification OPC UA ISO15926 ISO15414 OPC Unified Architecture Industrial automation systems and integration Integration of lifecycle data for process plants Information Processing Open Distributed Processing Reference model Enterprise language Contructs for enterprise modelling Enterprise-control system integration Batch Control Industrial automation systems and integration industrial manufacturing management data Information Technology Metadata registries
ISO19440 ISO62264 IEC61512 ISO15531 (not studied) ISO11179
MI - Enterprise Language Standards
10
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
11
ISO150005 UN/CEFACT CCTS
ISO 15000 : Electronic business eXtensible Markup Language (ebXML) Ø Part 5 is the UN/CEFACT Core Components Technical Specification (CCTS) UN Cefact relevant work: Ø Core Components Data Type Catalogue Ø Core Components Technical Specification Ø XML Naming and Design Rules Technical Specification
MI - Enterprise Language Standards
12
Core Components Data Type Catalogue
Amount Binary Object Code Date Date Time Duration Graphic Identifier Indicator Measure Name Ordinal Percent Picture Quantity Rate Ratio Sound Text Time Value Video
13
MI - Enterprise Language Standards
Core Components Technical Specification
Provides a way to identify, capture and maximize the re-use of business information to support and enhance information interoperability. Focuses both on human-readable and machine processable representations of this information. Semantic standardization is done in a syntax-neutral fashion. Ø allows for the richness inherent in natural language to be used to create data and information exchange models that are devoid of computer-driven syntax limitations and requirements. Captures a wealth of information about the business reasons for variation in data model and message semantics and structure. Ø In the past, these variations have led to incompatible models and a subsequent lack of interoperability. The core components mechanism will allow identification of similarities and differences between these models.
MI - Enterprise Language Standards 14
UN/CEFACT CCTS Standards Stack
Business Transactions
UMM
EDIFACT
EDIFACT Syntax
XML NDR
XSD XCDT XML
UML Profile for CCTS
UML
Message Assembly
SBDH
R e g i s t r y
Component Library ISO15000 UCM
Business Data Types
Core Components Technical Specification
Data Type Catalogue
TMG (Techniques and Methodologies Group) TBG (Trade Business Group) ATG (Applied Technologies Group) ICG Implicit parts of UN/CEFACT Standards Non UN/CEFACT Standards
ISO 11179
Context Categories
MI - Enterprise Language Standards
Note: UML = Unified Modeling Language UMM = UN/CEFACT Modelling Methodology XSD = XML Schema Definition Language XML = Extensible Markup Language XMI = XML Metadata Interchange XCDT = XML Expressed Core Data Types BCSS = Business Collaboration Specification Schema UCM = Unified Context Methodology SBDH = Standard Business Document Header
15
Relationship between core abstract and business types
MI - Enterprise Language Standards
16
XML Naming and Design Rules Technical Specification
Good Design Practices for XML Schemas Ø XML Schemas architecture principles Ø Recommended usage of XSD primitives Ø XML Schema files handling Ø XML instances handling
MI - Enterprise Language Standards
17
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
18
OPC UA main modelling concepts
OPC UA offers an infrastructure to facilitate information exchange Ø In industrial application areas § Field devices, Control systems, MES systems, ERP systems Ø Addressing § Modeling language for describing structures, behaviour, semantics Standard, extensible models § Messaging concepts to interact between applications § Communication concepts to handle data transfer OPC UA provides Ø Data modelling framework Ø Service set for accessing data
MI - Enterprise Language Standards
19
Elements of OPC UA (Node classes)
Main classes View Object Type Definition subclasses subclasses Defined by ObjectType ObjectType Folder type ModellingRule Type EventType DataType VariableType Reference Type Property DataVariable Data Types Data Types Data Types DataTypeSystem Predefined
Next slides Next slides DataTypeDictionary, Next slides
Variable Methods
MI - Enterprise Language Standards
20
OPC UA standard Attributes
AccessLevel ArrayDimensions BrowseName ContainsNoLoops DataType Description DisplayName EventNotifier Executable Historizing InverseName IsAbstract MinimumSamplingInterval NodeClass NodeId Symmetric UserAccessLevel UserExecutable UserWriteMask Value ValueRank WriteMask
MI - Enterprise Language Standards
21
OPC UA Standard Reference types
MI - Enterprise Language Standards
22
OPC UA standard event types
MI - Enterprise Language Standards
23
OPC UA standard Services
Service set Discovery SecureChannel Session Attribute Subscription MonitoredItem View Query NodeManagement Method Discover Servers: FindServers, GetEndpoints, RegisterServer Open / close secure communication (lower level protocol dependent) Open / close Session Read / write data (including history) Subscribe to data (receive data) Subscribe to data (specifying which data to subscribe to) Browsing Querying Add / delete Nodes and References Method calls
MI - Enterprise Language Standards
24
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
25
ISO15926 background
ISO 15926 "Industrial automation systems and integration-- Integration of life-cycle data for process plants including oil and gas production facilities" Ø Part of the European community program « ESPRIT » Ø EPISTLE consortium Ø Supported by POSC Caesar Association § Petrotechnical Open Software Corporation § Oil & Gas, Norway Ø OWL implementation Focused on reference data lifecycle Wide applicability Ø Focuses on describing industrial facilities Ø Based on an upper level ontology of large expressiveness
MI - Enterprise Language Standards
26
ISO15926 Upper level types
Class Thing Possible Individual Abstract object Class Relationship Composition of Individual Connection of Individual Multi-dimensional object MI - Enterprise Language Standards List of « Things » Pump Pump #1234 is member of Pump Pump #1234
27
ISO15926 examples
Upper level types Physical object Material organization
MI - Enterprise Language Standards
28
ISO15926 Example
MI - Enterprise Language Standards
29
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
30
ISO15414
« Information Technology Open Distributed Processing Reference model Enteprise Language » Developed by ITU Ø International Telecommunication Union ITU-T X.911 Proposed « Enterprise language » in the more global context of RMODP Ø Reference Model of Open Distributed Processing Ø ISO10746-1/2/3/4 - ITU-T X901/2/3/4
MI - Enterprise Language Standards
31
ISO15414 concepts
System concepts Ø Scope, Field of Application Community concepts Ø Onjective, Community object Behaviour concepts Ø Actor, Artefact, Resource, Interface Role, Process, Step Policy concepts Ø Policy, Authorization, Violation Accountability concepts. Ø Party, Commitment, Declaration, Delegation, Evaluation, Prescription, Agent, Principal
MI - Enterprise Language Standards
32
ISO15414 Structuring rules
Community rules Enterprise object rules Common community types Lifecycle of a community Objective rules Behaviour rules Policy rules Accountability rules
MI - Enterprise Language Standards
33
System concepts
MI - Enterprise Language Standards
34
ISO15414 Community and Behaviour concepts
MI - Enterprise Language Standards
35
Policy concepts
MI - Enterprise Language Standards
36
Accountability concepts
MI - Enterprise Language Standards
37
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
38
ISO19440
Defines the generic concepts for enterprise models Ø provides common semantics Ø enables the unification of models developed by different stakeholders These concepts can be Ø specialized / organized for specific purposes, Ø used for developing particular models for a particular enterprise. General requirements computer supported enterprise modeling Ø Business Processes model (dynamics, functions, information, resources, organization and responsibilities) Ø Detailing and qualification of enterprise components for a specific enterprise, Ø Support for management of change, Ø end-user-oriented representation to enable operational use.
MI - Enterprise Language Standards
39
ISO19440 « constructs »
The standard describes in detail the following concepts Ø Function- and process-related: § Domain, Business Process, Enterprise Activity, Event Ø Information-related: § Enterprise Object, Enterprise Object View, Order, Product Ø Resource-related: § Capability, Operational Role, Resource, Functional Entity Ø Organization-related: § Person Profile, Organizational Role, Organization Unit, and Decision Centre. These concepts can be specialized Ø Any enterprise concept shall be derivable from this list
MI - Enterprise Language Standards
40
Example of « Business Process » Header
Construc [`BP`] t label Identifier [<modelunique string>] Name [name of Business Process instance in the form: <adjective> <noun>, where <noun> relates to the scope of the Business Process, <adjective> qualifies the business Process instance]] Design [<identifier> / <name> of Organisational Unit or Authority Organisational Cell with the authority to design/maintain this particular instance]
MI - Enterprise Language Standards
41
Example of « Business Process » Descriptives
DESCRIPTIO [textual description] N OBJECTIVES [nonempty list of Objectives to be fulfilled by the Business Process instance CONSTRAINT ['NIL' or list of Constraints imposed on the BP instance] S PERFORMAN ['NIL' or list of the metrics or measures by which CE achievement of the objectives can be assessed] INDICATORS DECLARATIV ['NIL' or list of Declarative Rules applicable to this Business E Process instance] RULES INPUTS [nonempty list of <identifier> / <name> of all Object View instances, occurrences of which can be received by occurrences of the Business Process instance] MI - [nonempty list of <identifier> / <name> / <source domain> Enterprise Language Standards 42
Example of « Business Process » Descriptives
OUTPUT [nonempty list of <identifier> / <name> of all Object View S instances, occurrences of which can be sent by occurrences of the Business Process instance] [nonempty list of <identifier> / <name> / <sink domain> of all Events, instances of which can be sent by occurrences of the Business Process instance] PROCES [nonempty set of Behavioural Rules expressed using the syntax S defined for Process Behaviour as defined in 6.3.3] BEHAVIO UR PRIORIT [Integer in a range <min, max> where min and max are integers Y representing the lowest and highest priorities respectively]
MI - Enterprise Language Standards
43
Example of « Business Process » Relationships
WHERE USED CONSISTS OF [<identifier> / <name> of the Domain employing this Business Process instance] [nonempty list of <identifier> / <name> of all Business Process and Enterprise Activity instances that are employed directly (i.e. at the next level of decomposition) by this Business Process instance] Operation [<identifier> / <name> of Organisational Unit or Responsibilit Organisational Cell with responsibility for operation of this y instance Operation [<identifier> / <name> of Organisational Unit or Authority Organisational Cell with authority for operation of this instance]
MI - Enterprise Language Standards
44
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
45
ISA88/ISA95 set of standards
US standard ANSI/ISA-88.00.01: 1995 ANSI/ISA-88.00.02: 2001 ANSI/ISA-88.00.03: 2003 ANSI/ISA-88.00.04: 2006 ISA Draft88.00.05 ANSI/ISA-95.00.01: 2000 ANSI/ISA-95.00.02: 2001 ANSI/ISA-95.00.03: 2005 ISA draft 95.00.04 ASNI/ISA-95.00.05: 2007 INTL Standard IEC61512-1: 1997 IEC61512-2: 2001 IEC61512-3: 2008 IEC61512-4: 2009 IEC/ISO62264-1: 2003 IEC/ISO62264-2: 2004 IEC/ISO62264-3: 2006 IEC/ISO62264-5: 2009 Sub Title Models and Terminology" Data structures and guidelines for languages General and Site Recipe - Models and Representation Batch Production Records Implementation Models & Terminology for Modular Equipment Control Models and Terminology" Data Structures and Attributes" Activity Models of Manufacturing Operations Management Object Models and Attributes of Manufacturing Operations Management) Business to Manufacturing Transactions
MI - Enterprise Language Standards
46
ISA88 snapshot
Object Design of automation applications Ø Reuse, Knowledge Management, Robustness Flexible Design of automation applications - No programming required for Ø Modification of recipes, making different products with the same facility Ø Using alternate equipment for the same production step Ø Sequencing production runs for different products Interoperability Ø Assembling software components from different origins Product Industrialization Ø Neutral specification of product physico-chemical transformations Ø Conversion of this specification into operating procedure for target facilities Production Information Ø Data structures for production information history Ø Includes several ISA95 models Applications Ø Initially designed for Batch processes, but applicable to any type of process Ø Functional specification, batch managers, historians, PDM/PLM
MI - Enterprise Language Standards
47
ISA95 snapshot
B2M: Collaboration Business / Execution Ø Communication between execution systems (MES/MOM, DCS, MMS, LIMS, WES, SCADA,...) and business systems (ERP, SCM) Ø Master data management MES/MOM : Functional definition Data and Activity models Ø Description of resources, capability, products, work order requests and reports Ø Definition of operation management activities (MES) Applications: Ø User requirements and functional specification of MES and B2M interfaces Ø Native B2M connectors - MES/ERP (B2MML) Ø Possible basis for developing MES applications and software...
MI - Enterprise Language Standards
48
ISA88 ISA95
ISA88/ISA95 modelling overview
MI - Enterprise Language Standards
Product Asset Management Inventory Asset Management Physical Asset Management Human Asset Management
TOGAF ITIL ISA88 + ISA95
49
IT Asset Management
ISA88 Product model* (Processing Requirement)
Process
A Process is made up of an ordered set of one or more Process Stages
Process Stage
A Process Stage is made up of an ordered set of one or more Process Operations
Process Operation *Nota : called "Process Model" in ISA88
A Process Operation is made up of an ordered set of one or more Process Actions
Process Action
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
50
Resource models (Structural description)
The resource asset models (Personnel, Equipment, and Material) are based on the ISA95 breakdown. All these resources share a similar pattern. Equipment and Material are indeed the same entity: A "machine" can be: Ø A "Physical Asset" for the company that makes products with it, Ø An "Inventory Asset" for the company that makes them (finish product) or sell / distributes it
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
51
ISA95 Material Model
Is assembled from Is assembled from Is assembled from Is assembled from
0..n
0..n Defines a grouping 0..n
0..n 0..n 1..1 Defined by
0..n Made up of
0..n
0..n
Material Class
Has properties of
0..n
Material Definition
Has properties of
Material Lot
0..n
Material Sublot
0..n
Is tested by a >
Is tested by a > 0..n 0..n 0..n
Is tested by a > 0..n
Has values for
Has values for
May be made up of sublots
Material Test Specification
Defines a procedure for obtaining a 0..n Records the execution of
Is tested by a > 0..n
0..n Is tested by a > 0..n
QA Test Result
0..n
0..n
0..n < may contain nested
0..n < may contain nested
0..n < may contain nested
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
Material Class Property
May map to
Material Definition Property
0..n Maps to
0..n
Material Lot Property
0..n
52
ISA95 extended physical model (Actual Facility layout)
ENTERPRISE SITE AREA WORK CENTER PROCESS CELL PRODUCTION UNIT PRODUCTION LINE STORAGE ZONE BATCH PROCESS (ISA88) CONTINUOUS PROCESS DISCRETE PROCESS WAREHOUSE
WORK UNIT
UNIT
UNIT
WORK CELL
STORAGE UNIT
CONTROL MODULE
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
EQUIPMENT MODULE
53
ISA95 Equipment Model
< May be made up of 0..n 0..n 0..n 0..n Is tested by an > 0..n < Defined by 0..n Is tested by an > 0..n
Equipment Class
Has properties of >
Equipment
Has values for >
Equipment Capability Test Specification
0..n Is tested by an > Defines a procedure for obtaining an > 0..n Maps to 0..n 0..n < Records the execution of
Equipment Capability Test Result
0..n < may contain nested
0..n < may contain nested
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
Equipment Class Property
0..n
0..n
Equipment Property
54
ISA95 Personnel Model
Personnel Class
Has properties of > 0..n 0..n Is tested by a > 0..n < Defined by 0..n Is tested by a > 0..n Has values for >
Person
0..n
Qualification Test Specification
0..n Is tested by a > 0..n Defines a procedure for obtaining a > 0..n < Maps to 0..n
< Records the execution of
Qualification Test Result
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
0..n
0..n
Personnel Class Property
Person Property
MI - Enterprise Language Standards
55
ISA88 Procedural model (Equipment/Product Interactions)
Procedure
A Procedure is made up of an ordered set of one or more Unit Procedures
Unit Procedure
A Unit Procedure is made up of an ordered set of one or more Operations
Operation
An Operation is made up of an ordered set of one or more Phases
Phase
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
56
ISA95 Segment Model
0..n has an execution dependency on
Process Segment
is a collection of
0..n
0..n May be made up of
Process Segment Dependency
0..n
0..n
0..n
0..n
0..n
Process Segment Parameter
0..n May be made up of
Personnel Segment Specification
Has properties of 0..n
Equipment Segment Specification
Has properties of 0..n
Physical Asset Segment Specification
Has properties of 0..n
Material Segment Specification
Has properties of 0..n
0..n Is assembled from
Personnel Segment Specification Property
0..n Corresponds to element in 1..1
Equipment Segment Specification Property
0..n Corresponds to element in 1..1
Physical Asset Segment Specification Property
0..n Corresponds to element in 1..1
Material Segment Specification Property
0..n Corresponds to element in 1..1
Personnel Model
Equipment Model
Physical Asset Model
Material Model
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
57
ISA95 Operational Activity Model
1.Detailed scheduling 8. Resource management 2. Dispatching 7. Definition management 3. Execution 4. Data collection
5. Tracking
6. Analysis
Production Quality Control Inventory Maintenance
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
Other
58
ISA88 & ISA95 Objects in Production Lifecycles
Schedule Batch list 3. Operations Requests / Control Recipes Segments / RPE
Product Definition Recipe 1. Product Dévelopment
Segments PE/RPE
Segments EPE
Capability
Resources Personnel/Equipment/Material Equipment entity / Formula
2. Engineering
MI - Enterprise Language Standards
59
Continuous modeling workflow
P&ID R&D
1b. Physical Modelling
CCM Rules & Tools Use Build Improve
1a. Product Modelling 3. Process Procedural Modelling 4. Segments Modelling 5. Operation Process Modelling
1a. Inventory 1c. Human Modelling Modelling
Object classes and models repository Use Build Improve
2. Equipment Control Modelling
IT modelling
MI - Enterprise Language Standards
60
Continuous modeling workflow
P&ID R&D
Goveranc e Enabling CCM Rules & Tools Use Build Improve
/9 5 88 ISA 3. Process 2. Equipment Control Procedural 8 Modelling A8 Modelling IS
1b. Physical Modelling
1a. Product Modelling
1a. Inventory 1c. Human Modelling Modelling
I
95 SA
Persisten ce Object classes and models repository
4. Segments Modelling
95 5. Operation SA IProcess
Modelling
IT modelling
Use Build Improve
MI - Enterprise Language Standards
61
Interactions Hierarchy
Business Business Processes
Business Activities
Exécution
(ISA-95, MES)
Operations Processes
Operations Activities
(ISA-88, Equipment Control)
Operating Instructions Procedural Elements
Physical Processes
Recipes, routing 62
MI - Enterprise Language Standards
Examples of Description standards
Business / Operation process Description: BPMN, OSSAD, UML Schedule Requests / Recipes Segments / RPE Product Definition Segments PE/RPE
Product Definition: PPC
Physical Process Description : PFC Capability
Segments EPE
Resources Personnel / Equipment / Material MI - Enterprise Language Standards 63
ISA88/95 Modeling elements
Cliquez Domain sur l'icône pour ajouter un tableau Model Std Product Asset Inventory Asset Equipment Asset Human Asset Equipment Control Physical Process Control Process Product Material Physical Equipment Personnel Procedural Procedural ISA88 ISA95 ISA95 ISA88 ISA95 ISA95 ISA88 ISA88 Information elements Product Hierarchy Product Definition Material Resources Equipment Hierarchy Equipment Resources Personnel Hierarchy Personnel Resources Functional Hierarchy Equipment Procedural Elements Physical Processes / Procedural Elements Physical Process Transform Components Segments Operation Processes Activities / Tasks 64
Physical Process Mngt Operation Process Mngt
Segment Operation Activity
ISA95 ISA95
MI - Enterprise Language Standards
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
65
ISO11179
A semantic registry records all concepts as lexicon of unique terms They can be categorized i.e. Ø Basic vocabulary Ø Abstract concepts (not specific to a particular business context) § Simple, Enumerated or Non enumerated § Complex Ø Business concepts (meaningful in specific situations) ISO11179 Ø Supports semantic definition Ø Also register data representation § occurrences of concepts in actual situations IT solution, local terminologies Ø Handles reference data management Ø Define principles for consistent naming and clear descriptions
MI - Enterprise Language Standards 66
ISO 11179
Titre: Information technology -- Metadata registries (MDR) Ø Part 1: Framework § Vue d'ensemble Ø Part 2: Classification § Extrait du méta-modèle partie 3 concernant la classification Ø Part 3: Registry metamodel and basic attributes § Définit le meta-modèle pour gérer les données de référence Ø Part 4: Formulation of data definitions § Définit des principe pour exprimer clairement les définitions Ø Part 5: Naming and identification principles § Définit des principes d'identification et de nommage Ø Part 6: Registration § Définit le processus d'enregistrement des méta-données
MI - Enterprise Language Standards
67
ISO11179 meta model
« Value »
« Measure »
« PT104 » « Temperature »
MI - Enterprise Language Standards
68
ISO11179 data administration
MI - Enterprise Language Standards
69
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179 Next steps
MI - Enterprise Language Standards
70
Interoperability is a key element for enabling interactions Ø Developing knowledge and systemic intelligence of the enterprise Language Ø Is the precondition for intelligence Ø Transform interfaces in intereactions A significant public knowledge is available Ø From ISO and other standardization bodies Ø Helping to set a consistent basis for an Enterprise language Enterprise language Ø Allows to manage and leverage enterprise knowledge § Including Master Data Ø Provides global semantic reference refered to in collaboration Ø Provides formal concepts for interoperability § Meaningful messages between actors People and IT
MI - Enterprise Language Standards 71
Thank You !
MI - Enterprise Language Standards
72
Industrial Operations / Information Processing Convergence Control Chain Management Body Of Knowledge
MI Enterprise Language Standards
04/2011
Jean Vieille
www.syntropicfactory.com j.vieille@syntropicfactory.com
Research community www.controlchainmanagement.org Consulting group: www.controlchaingroup.com
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
2
Introduction
The Enterprise organism keeps morphing itself Ø Achieving the Darwinian process of its existence by developing objective knowledge to its advantage Ø Fighting entropy, securing survival, enabling progress Ø Ensuring that thinking people and machines understand each other and the system they live in Hypercritical complexity Ø quantity and quality of interactions Ø spouts "emerging properties", Culture, Intelligence, Auto-organization Ø Developing new, higher ranking behavior Ø Not deductible from their individual components The Syntropic Factory focuses on becoming a smarter organism Ø Developing its "intelligence"
MI - Enterprise Language Standards
3
Conditions of intelligence
A product of complexity, Intelligence raises from Ø Ability to develop knowledge § Enabling cycling between subjective experience and objective knowledge Ø Ability to share knowledge § Enabling seamless storage and access to relevant knowledge Ø Ability to interact § Enabling understandable communications between components Ø Individual intelligence § Sophisticated components performing locally § At the advantage of the whole system Secondary level behavior Ø Creativity Ø Risk assessment and management § Securing actions against uncertainty
MI - Enterprise Language Standards 4
Language
Objective knowledge is out of reach Ø It exists independently of its actual understanding by human, machines Language is the means for handling knowledge Ø Language defines basic concepts (vocabulary) and rules (grammar) for expressing knowledge Existence of a language is a pre-condition for intelligence
MI - Enterprise Language Standards
5
Enterprise knowledge
Covers many domains Addresses tangible and intangible information. For Industrial facilities operations Ø Tangible knowledge § Resources and capabilities (equipment, people, material, energy...) Ø Intangible knowledge § Know-how not formalized Enterprise knowledge covers Ø Public knowledge § Readily available Ø Private knowledge § Represents the enterprise essence § Might need to be protected from competitors' eyes
MI - Enterprise Language Standards
6
Enterprise language
Tangible outcome of the language: Ø meaningful, non ambiguous messages for knowledge exchange, storage, retrieval Ø Support the description of enterprise structural and behavioral aspects on the time scale Must serve both Human and IT relationship Ø Understandable by people and machines Ø Machine, being notably stupid, need extended, precise formalism to understand
MI - Enterprise Language Standards
7
Elements of the enterprise language
Natural language accommodate most of human interactions Machines need more formalism The enterprise language is a formal ontology Ø A semantic tree Ø Defining concepts associated with lexicon (translations, synonyms,) Ø Structured successively in § simple abstract concepts i.e. « Identifier » « Description » § General concepts i.e. « « activity », « Resource » § business concepts as references for actual business entities mentioned in messages Ø Describing relationships and value domains
MI - Enterprise Language Standards
8
Public knowledge and standards
Standards expose public knowledge Ø Enterprise generic concepts (public knowledge) is well covered by available standards Acquiring appropriate public knowledge is part of the enterprise knowledge / intelligence development Ø Ignoring public knowledge forces to reinvent the wheel Ø Leveraging public knowledge § Saves effort and time, § Catalyze private knowledge development, § Accelerates intelligence development Many overlapping standards, more or less focused This study present some relevant standards to establish an enterprise language
MI - Enterprise Language Standards
9
Applicable standards
Reference Title Domains ULO - Data structures for elementary concepts ULO - Neutral Upper level ontology ULO - Upper level ontology of enterprise concepts ULO - Generic enterprise concepts Upper level ontology Generic enteprise concepts Manufacturing operations specific concepts Manufacturing specific concepts Semantic registry ISO15000-5 ebXML - Core Componenet Technical UN/Cefact CC Specification OPC UA ISO15926 ISO15414 OPC Unified Architecture Industrial automation systems and integration Integration of lifecycle data for process plants Information Processing Open Distributed Processing Reference model Enterprise language Contructs for enterprise modelling Enterprise-control system integration Batch Control Industrial automation systems and integration industrial manufacturing management data Information Technology Metadata registries
ISO19440 ISO62264 IEC61512 ISO15531 (not studied) ISO11179
MI - Enterprise Language Standards
10
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
11
ISO150005 UN/CEFACT CCTS
ISO 15000 : Electronic business eXtensible Markup Language (ebXML) Ø Part 5 is the UN/CEFACT Core Components Technical Specification (CCTS) UN Cefact relevant work: Ø Core Components Data Type Catalogue Ø Core Components Technical Specification Ø XML Naming and Design Rules Technical Specification
MI - Enterprise Language Standards
12
Core Components Data Type Catalogue
Amount Binary Object Code Date Date Time Duration Graphic Identifier Indicator Measure Name Ordinal Percent Picture Quantity Rate Ratio Sound Text Time Value Video
13
MI - Enterprise Language Standards
Core Components Technical Specification
Provides a way to identify, capture and maximize the re-use of business information to support and enhance information interoperability. Focuses both on human-readable and machine processable representations of this information. Semantic standardization is done in a syntax-neutral fashion. Ø allows for the richness inherent in natural language to be used to create data and information exchange models that are devoid of computer-driven syntax limitations and requirements. Captures a wealth of information about the business reasons for variation in data model and message semantics and structure. Ø In the past, these variations have led to incompatible models and a subsequent lack of interoperability. The core components mechanism will allow identification of similarities and differences between these models.
MI - Enterprise Language Standards 14
UN/CEFACT CCTS Standards Stack
Business Transactions
UMM
EDIFACT
EDIFACT Syntax
XML NDR
XSD XCDT XML
UML Profile for CCTS
UML
Message Assembly
SBDH
R e g i s t r y
Component Library ISO15000 UCM
Business Data Types
Core Components Technical Specification
Data Type Catalogue
TMG (Techniques and Methodologies Group) TBG (Trade Business Group) ATG (Applied Technologies Group) ICG Implicit parts of UN/CEFACT Standards Non UN/CEFACT Standards
ISO 11179
Context Categories
MI - Enterprise Language Standards
Note: UML = Unified Modeling Language UMM = UN/CEFACT Modelling Methodology XSD = XML Schema Definition Language XML = Extensible Markup Language XMI = XML Metadata Interchange XCDT = XML Expressed Core Data Types BCSS = Business Collaboration Specification Schema UCM = Unified Context Methodology SBDH = Standard Business Document Header
15
Relationship between core abstract and business types
MI - Enterprise Language Standards
16
XML Naming and Design Rules Technical Specification
Good Design Practices for XML Schemas Ø XML Schemas architecture principles Ø Recommended usage of XSD primitives Ø XML Schema files handling Ø XML instances handling
MI - Enterprise Language Standards
17
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
18
OPC UA main modelling concepts
OPC UA offers an infrastructure to facilitate information exchange Ø In industrial application areas § Field devices, Control systems, MES systems, ERP systems Ø Addressing § Modeling language for describing structures, behaviour, semantics Standard, extensible models § Messaging concepts to interact between applications § Communication concepts to handle data transfer OPC UA provides Ø Data modelling framework Ø Service set for accessing data
MI - Enterprise Language Standards
19
Elements of OPC UA (Node classes)
Main classes View Object Type Definition subclasses subclasses Defined by ObjectType ObjectType Folder type ModellingRule Type EventType DataType VariableType Reference Type Property DataVariable Data Types Data Types Data Types DataTypeSystem Predefined
Next slides Next slides DataTypeDictionary, Next slides
Variable Methods
MI - Enterprise Language Standards
20
OPC UA standard Attributes
AccessLevel ArrayDimensions BrowseName ContainsNoLoops DataType Description DisplayName EventNotifier Executable Historizing InverseName IsAbstract MinimumSamplingInterval NodeClass NodeId Symmetric UserAccessLevel UserExecutable UserWriteMask Value ValueRank WriteMask
MI - Enterprise Language Standards
21
OPC UA Standard Reference types
MI - Enterprise Language Standards
22
OPC UA standard event types
MI - Enterprise Language Standards
23
OPC UA standard Services
Service set Discovery SecureChannel Session Attribute Subscription MonitoredItem View Query NodeManagement Method Discover Servers: FindServers, GetEndpoints, RegisterServer Open / close secure communication (lower level protocol dependent) Open / close Session Read / write data (including history) Subscribe to data (receive data) Subscribe to data (specifying which data to subscribe to) Browsing Querying Add / delete Nodes and References Method calls
MI - Enterprise Language Standards
24
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
25
ISO15926 background
ISO 15926 "Industrial automation systems and integration-- Integration of life-cycle data for process plants including oil and gas production facilities" Ø Part of the European community program « ESPRIT » Ø EPISTLE consortium Ø Supported by POSC Caesar Association § Petrotechnical Open Software Corporation § Oil & Gas, Norway Ø OWL implementation Focused on reference data lifecycle Wide applicability Ø Focuses on describing industrial facilities Ø Based on an upper level ontology of large expressiveness
MI - Enterprise Language Standards
26
ISO15926 Upper level types
Class Thing Possible Individual Abstract object Class Relationship Composition of Individual Connection of Individual Multi-dimensional object MI - Enterprise Language Standards List of « Things » Pump Pump #1234 is member of Pump Pump #1234
27
ISO15926 examples
Upper level types Physical object Material organization
MI - Enterprise Language Standards
28
ISO15926 Example
MI - Enterprise Language Standards
29
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
30
ISO15414
« Information Technology Open Distributed Processing Reference model Enteprise Language » Developed by ITU Ø International Telecommunication Union ITU-T X.911 Proposed « Enterprise language » in the more global context of RMODP Ø Reference Model of Open Distributed Processing Ø ISO10746-1/2/3/4 - ITU-T X901/2/3/4
MI - Enterprise Language Standards
31
ISO15414 concepts
System concepts Ø Scope, Field of Application Community concepts Ø Onjective, Community object Behaviour concepts Ø Actor, Artefact, Resource, Interface Role, Process, Step Policy concepts Ø Policy, Authorization, Violation Accountability concepts. Ø Party, Commitment, Declaration, Delegation, Evaluation, Prescription, Agent, Principal
MI - Enterprise Language Standards
32
ISO15414 Structuring rules
Community rules Enterprise object rules Common community types Lifecycle of a community Objective rules Behaviour rules Policy rules Accountability rules
MI - Enterprise Language Standards
33
System concepts
MI - Enterprise Language Standards
34
ISO15414 Community and Behaviour concepts
MI - Enterprise Language Standards
35
Policy concepts
MI - Enterprise Language Standards
36
Accountability concepts
MI - Enterprise Language Standards
37
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
38
ISO19440
Defines the generic concepts for enterprise models Ø provides common semantics Ø enables the unification of models developed by different stakeholders These concepts can be Ø specialized / organized for specific purposes, Ø used for developing particular models for a particular enterprise. General requirements computer supported enterprise modeling Ø Business Processes model (dynamics, functions, information, resources, organization and responsibilities) Ø Detailing and qualification of enterprise components for a specific enterprise, Ø Support for management of change, Ø end-user-oriented representation to enable operational use.
MI - Enterprise Language Standards
39
ISO19440 « constructs »
The standard describes in detail the following concepts Ø Function- and process-related: § Domain, Business Process, Enterprise Activity, Event Ø Information-related: § Enterprise Object, Enterprise Object View, Order, Product Ø Resource-related: § Capability, Operational Role, Resource, Functional Entity Ø Organization-related: § Person Profile, Organizational Role, Organization Unit, and Decision Centre. These concepts can be specialized Ø Any enterprise concept shall be derivable from this list
MI - Enterprise Language Standards
40
Example of « Business Process » Header
Construc [`BP`] t label Identifier [<modelunique string>] Name [name of Business Process instance in the form: <adjective> <noun>, where <noun> relates to the scope of the Business Process, <adjective> qualifies the business Process instance]] Design [<identifier> / <name> of Organisational Unit or Authority Organisational Cell with the authority to design/maintain this particular instance]
MI - Enterprise Language Standards
41
Example of « Business Process » Descriptives
DESCRIPTIO [textual description] N OBJECTIVES [nonempty list of Objectives to be fulfilled by the Business Process instance CONSTRAINT ['NIL' or list of Constraints imposed on the BP instance] S PERFORMAN ['NIL' or list of the metrics or measures by which CE achievement of the objectives can be assessed] INDICATORS DECLARATIV ['NIL' or list of Declarative Rules applicable to this Business E Process instance] RULES INPUTS [nonempty list of <identifier> / <name> of all Object View instances, occurrences of which can be received by occurrences of the Business Process instance] MI - [nonempty list of <identifier> / <name> / <source domain> Enterprise Language Standards 42
Example of « Business Process » Descriptives
OUTPUT [nonempty list of <identifier> / <name> of all Object View S instances, occurrences of which can be sent by occurrences of the Business Process instance] [nonempty list of <identifier> / <name> / <sink domain> of all Events, instances of which can be sent by occurrences of the Business Process instance] PROCES [nonempty set of Behavioural Rules expressed using the syntax S defined for Process Behaviour as defined in 6.3.3] BEHAVIO UR PRIORIT [Integer in a range <min, max> where min and max are integers Y representing the lowest and highest priorities respectively]
MI - Enterprise Language Standards
43
Example of « Business Process » Relationships
WHERE USED CONSISTS OF [<identifier> / <name> of the Domain employing this Business Process instance] [nonempty list of <identifier> / <name> of all Business Process and Enterprise Activity instances that are employed directly (i.e. at the next level of decomposition) by this Business Process instance] Operation [<identifier> / <name> of Organisational Unit or Responsibilit Organisational Cell with responsibility for operation of this y instance Operation [<identifier> / <name> of Organisational Unit or Authority Organisational Cell with authority for operation of this instance]
MI - Enterprise Language Standards
44
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
45
ISA88/ISA95 set of standards
US standard ANSI/ISA-88.00.01: 1995 ANSI/ISA-88.00.02: 2001 ANSI/ISA-88.00.03: 2003 ANSI/ISA-88.00.04: 2006 ISA Draft88.00.05 ANSI/ISA-95.00.01: 2000 ANSI/ISA-95.00.02: 2001 ANSI/ISA-95.00.03: 2005 ISA draft 95.00.04 ASNI/ISA-95.00.05: 2007 INTL Standard IEC61512-1: 1997 IEC61512-2: 2001 IEC61512-3: 2008 IEC61512-4: 2009 IEC/ISO62264-1: 2003 IEC/ISO62264-2: 2004 IEC/ISO62264-3: 2006 IEC/ISO62264-5: 2009 Sub Title Models and Terminology" Data structures and guidelines for languages General and Site Recipe - Models and Representation Batch Production Records Implementation Models & Terminology for Modular Equipment Control Models and Terminology" Data Structures and Attributes" Activity Models of Manufacturing Operations Management Object Models and Attributes of Manufacturing Operations Management) Business to Manufacturing Transactions
MI - Enterprise Language Standards
46
ISA88 snapshot
Object Design of automation applications Ø Reuse, Knowledge Management, Robustness Flexible Design of automation applications - No programming required for Ø Modification of recipes, making different products with the same facility Ø Using alternate equipment for the same production step Ø Sequencing production runs for different products Interoperability Ø Assembling software components from different origins Product Industrialization Ø Neutral specification of product physico-chemical transformations Ø Conversion of this specification into operating procedure for target facilities Production Information Ø Data structures for production information history Ø Includes several ISA95 models Applications Ø Initially designed for Batch processes, but applicable to any type of process Ø Functional specification, batch managers, historians, PDM/PLM
MI - Enterprise Language Standards
47
ISA95 snapshot
B2M: Collaboration Business / Execution Ø Communication between execution systems (MES/MOM, DCS, MMS, LIMS, WES, SCADA,...) and business systems (ERP, SCM) Ø Master data management MES/MOM : Functional definition Data and Activity models Ø Description of resources, capability, products, work order requests and reports Ø Definition of operation management activities (MES) Applications: Ø User requirements and functional specification of MES and B2M interfaces Ø Native B2M connectors - MES/ERP (B2MML) Ø Possible basis for developing MES applications and software...
MI - Enterprise Language Standards
48
ISA88 ISA95
ISA88/ISA95 modelling overview
MI - Enterprise Language Standards
Product Asset Management Inventory Asset Management Physical Asset Management Human Asset Management
TOGAF ITIL ISA88 + ISA95
49
IT Asset Management
ISA88 Product model* (Processing Requirement)
Process
A Process is made up of an ordered set of one or more Process Stages
Process Stage
A Process Stage is made up of an ordered set of one or more Process Operations
Process Operation *Nota : called "Process Model" in ISA88
A Process Operation is made up of an ordered set of one or more Process Actions
Process Action
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
50
Resource models (Structural description)
The resource asset models (Personnel, Equipment, and Material) are based on the ISA95 breakdown. All these resources share a similar pattern. Equipment and Material are indeed the same entity: A "machine" can be: Ø A "Physical Asset" for the company that makes products with it, Ø An "Inventory Asset" for the company that makes them (finish product) or sell / distributes it
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
51
ISA95 Material Model
Is assembled from Is assembled from Is assembled from Is assembled from
0..n
0..n Defines a grouping 0..n
0..n 0..n 1..1 Defined by
0..n Made up of
0..n
0..n
Material Class
Has properties of
0..n
Material Definition
Has properties of
Material Lot
0..n
Material Sublot
0..n
Is tested by a >
Is tested by a > 0..n 0..n 0..n
Is tested by a > 0..n
Has values for
Has values for
May be made up of sublots
Material Test Specification
Defines a procedure for obtaining a 0..n Records the execution of
Is tested by a > 0..n
0..n Is tested by a > 0..n
QA Test Result
0..n
0..n
0..n < may contain nested
0..n < may contain nested
0..n < may contain nested
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
Material Class Property
May map to
Material Definition Property
0..n Maps to
0..n
Material Lot Property
0..n
52
ISA95 extended physical model (Actual Facility layout)
ENTERPRISE SITE AREA WORK CENTER PROCESS CELL PRODUCTION UNIT PRODUCTION LINE STORAGE ZONE BATCH PROCESS (ISA88) CONTINUOUS PROCESS DISCRETE PROCESS WAREHOUSE
WORK UNIT
UNIT
UNIT
WORK CELL
STORAGE UNIT
CONTROL MODULE
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
EQUIPMENT MODULE
53
ISA95 Equipment Model
< May be made up of 0..n 0..n 0..n 0..n Is tested by an > 0..n < Defined by 0..n Is tested by an > 0..n
Equipment Class
Has properties of >
Equipment
Has values for >
Equipment Capability Test Specification
0..n Is tested by an > Defines a procedure for obtaining an > 0..n Maps to 0..n 0..n < Records the execution of
Equipment Capability Test Result
0..n < may contain nested
0..n < may contain nested
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
Equipment Class Property
0..n
0..n
Equipment Property
54
ISA95 Personnel Model
Personnel Class
Has properties of > 0..n 0..n Is tested by a > 0..n < Defined by 0..n Is tested by a > 0..n Has values for >
Person
0..n
Qualification Test Specification
0..n Is tested by a > 0..n Defines a procedure for obtaining a > 0..n < Maps to 0..n
< Records the execution of
Qualification Test Result
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
0..n
0..n
Personnel Class Property
Person Property
MI - Enterprise Language Standards
55
ISA88 Procedural model (Equipment/Product Interactions)
Procedure
A Procedure is made up of an ordered set of one or more Unit Procedures
Unit Procedure
A Unit Procedure is made up of an ordered set of one or more Operations
Operation
An Operation is made up of an ordered set of one or more Phases
Phase
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
56
ISA95 Segment Model
0..n has an execution dependency on
Process Segment
is a collection of
0..n
0..n May be made up of
Process Segment Dependency
0..n
0..n
0..n
0..n
0..n
Process Segment Parameter
0..n May be made up of
Personnel Segment Specification
Has properties of 0..n
Equipment Segment Specification
Has properties of 0..n
Physical Asset Segment Specification
Has properties of 0..n
Material Segment Specification
Has properties of 0..n
0..n Is assembled from
Personnel Segment Specification Property
0..n Corresponds to element in 1..1
Equipment Segment Specification Property
0..n Corresponds to element in 1..1
Physical Asset Segment Specification Property
0..n Corresponds to element in 1..1
Material Segment Specification Property
0..n Corresponds to element in 1..1
Personnel Model
Equipment Model
Physical Asset Model
Material Model
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
57
ISA95 Operational Activity Model
1.Detailed scheduling 8. Resource management 2. Dispatching 7. Definition management 3. Execution 4. Data collection
5. Tracking
6. Analysis
Production Quality Control Inventory Maintenance
MI - Enterprise Language Standards
Product Inventory Asset Physical Asset Human Asset Asset IT Asset
Other
58
ISA88 & ISA95 Objects in Production Lifecycles
Schedule Batch list 3. Operations Requests / Control Recipes Segments / RPE
Product Definition Recipe 1. Product Dévelopment
Segments PE/RPE
Segments EPE
Capability
Resources Personnel/Equipment/Material Equipment entity / Formula
2. Engineering
MI - Enterprise Language Standards
59
Continuous modeling workflow
P&ID R&D
1b. Physical Modelling
CCM Rules & Tools Use Build Improve
1a. Product Modelling 3. Process Procedural Modelling 4. Segments Modelling 5. Operation Process Modelling
1a. Inventory 1c. Human Modelling Modelling
Object classes and models repository Use Build Improve
2. Equipment Control Modelling
IT modelling
MI - Enterprise Language Standards
60
Continuous modeling workflow
P&ID R&D
Goveranc e Enabling CCM Rules & Tools Use Build Improve
/9 5 88 ISA 3. Process 2. Equipment Control Procedural 8 Modelling A8 Modelling IS
1b. Physical Modelling
1a. Product Modelling
1a. Inventory 1c. Human Modelling Modelling
I
95 SA
Persisten ce Object classes and models repository
4. Segments Modelling
95 5. Operation SA IProcess
Modelling
IT modelling
Use Build Improve
MI - Enterprise Language Standards
61
Interactions Hierarchy
Business Business Processes
Business Activities
Exécution
(ISA-95, MES)
Operations Processes
Operations Activities
(ISA-88, Equipment Control)
Operating Instructions Procedural Elements
Physical Processes
Recipes, routing 62
MI - Enterprise Language Standards
Examples of Description standards
Business / Operation process Description: BPMN, OSSAD, UML Schedule Requests / Recipes Segments / RPE Product Definition Segments PE/RPE
Product Definition: PPC
Physical Process Description : PFC Capability
Segments EPE
Resources Personnel / Equipment / Material MI - Enterprise Language Standards 63
ISA88/95 Modeling elements
Cliquez Domain sur l'icône pour ajouter un tableau Model Std Product Asset Inventory Asset Equipment Asset Human Asset Equipment Control Physical Process Control Process Product Material Physical Equipment Personnel Procedural Procedural ISA88 ISA95 ISA95 ISA88 ISA95 ISA95 ISA88 ISA88 Information elements Product Hierarchy Product Definition Material Resources Equipment Hierarchy Equipment Resources Personnel Hierarchy Personnel Resources Functional Hierarchy Equipment Procedural Elements Physical Processes / Procedural Elements Physical Process Transform Components Segments Operation Processes Activities / Tasks 64
Physical Process Mngt Operation Process Mngt
Segment Operation Activity
ISA95 ISA95
MI - Enterprise Language Standards
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179
MI - Enterprise Language Standards
65
ISO11179
A semantic registry records all concepts as lexicon of unique terms They can be categorized i.e. Ø Basic vocabulary Ø Abstract concepts (not specific to a particular business context) § Simple, Enumerated or Non enumerated § Complex Ø Business concepts (meaningful in specific situations) ISO11179 Ø Supports semantic definition Ø Also register data representation § occurrences of concepts in actual situations IT solution, local terminologies Ø Handles reference data management Ø Define principles for consistent naming and clear descriptions
MI - Enterprise Language Standards 66
ISO 11179
Titre: Information technology -- Metadata registries (MDR) Ø Part 1: Framework § Vue d'ensemble Ø Part 2: Classification § Extrait du méta-modèle partie 3 concernant la classification Ø Part 3: Registry metamodel and basic attributes § Définit le meta-modèle pour gérer les données de référence Ø Part 4: Formulation of data definitions § Définit des principe pour exprimer clairement les définitions Ø Part 5: Naming and identification principles § Définit des principes d'identification et de nommage Ø Part 6: Registration § Définit le processus d'enregistrement des méta-données
MI - Enterprise Language Standards
67
ISO11179 meta model
« Value »
« Measure »
« PT104 » « Temperature »
MI - Enterprise Language Standards
68
ISO11179 data administration
MI - Enterprise Language Standards
69
Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414 ISO19440 ISO62264/ISA-95 + IEC61512/ISA-88 ISO11179 Next steps
MI - Enterprise Language Standards
70
Interoperability is a key element for enabling interactions Ø Developing knowledge and systemic intelligence of the enterprise Language Ø Is the precondition for intelligence Ø Transform interfaces in intereactions A significant public knowledge is available Ø From ISO and other standardization bodies Ø Helping to set a consistent basis for an Enterprise language Enterprise language Ø Allows to manage and leverage enterprise knowledge § Including Master Data Ø Provides global semantic reference refered to in collaboration Ø Provides formal concepts for interoperability § Meaningful messages between actors People and IT
MI - Enterprise Language Standards 71
Thank You !
MI - Enterprise Language Standards
72
Johann Sebastian Bach. the music closest to silence, closest, in spite of its being so highly organized, to pure, one-hundred-degree proof Spirit" (Aldous Huxley, Island)