1. D-8895-Ontology Enterprise Language standards
CCM00-00_01_INTRO_OVW_en
04/2009
D-8895-Ontology Enterprise Language standards
J. Vieille
04/2010
CCM (R) BOK

2. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

3. Background Interoperability is a key element for enabling interactions
Developing knowledge and systemic intelligence of the enterprise
This project aims at « conceptualizing » ISA88 and ISA95 standards
Express a canonical modelling
Defining data structures and terminologies valid for specific situations
Not exposing the underlying logic for constructing their models
Though these constructs appear to be somewhat consistent and implicit
Contrasting with more academic works developed in ISO standards
This project is placed in a wider perspective of the « Enterprise Language »,
Looking for a semantic convergence with existing standards
This presentation exposes a quick review of some relevant standards that could provide basic, alternative or extensions to the ISA88/95’s
Enterprise Language standards

4. Enterprise language (EL)
Language is the precondition for intelligence
Enables effective interactions and systemic optimization
Transforms interfaces in interactions
Enterprise languages address
people to people communications
machines to machines communications
people to machines communications
EL for machines
Machine, being notably stupid, need extended, precise simplistic formalism (symbols and rules)
To exchange meaningful, non ambiguous messages for knowledge exchange, storage, retrieval
Supporting the description of enterprise structural and behavioural aspects on the time scale
Enterprise Language standards

5. Elements of the enterprise language
Definition of a semantic tree of concepts
Associated with lexicon (translations, synonyms) relationships and value domains
Concepts are 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
Enterprise Language standards

6. Applicable standards This study present some relevant standards
To establish an enterprise language in the context of this project
Sometimes overlapping, More or less focused
Possible use of these standard in the context of this project :
To provide abstract meta-structures (or upper level ontologies) on which ISA88, ISA95 or other standards could be expressed
This means to identify the most abstract concepts in the standards
To substitute equivalent terminology to ISA88/ISA95 to fit enterprise specific context, while leveraging their smartest concepts
ISA88/95 can enrich a given indigenous enterprise language based on other standards instead of creating a foreign language island in manufacturing
A significant public knowledge is available
From ISO and other standardization bodies
Enterprise Language standards

7. Applicable standards Reference Title Domains ISO15000-5 UN/Cefact CC
ebXML - Core Componenet Technical Specification
ULO - Data structures for elementary concepts
OPC UA
OPC Unified Architecture
ULO - Neutral Upper level ontology
ISO15926
Industrial automation systems and integration – Integration of lifecycle data for process plants
ULO - Upper level ontology of enterprise concepts
ISO15414
Information Processing – Open Distributed Processing – Reference model – Enterprise language
ULO - Generic enterprise concepts
Upper level ontology
ISO19440
Constructs for enterprise modeling
Generic enteprise concepts
BPMN
Business Process Model and Notation
BP description, depiction, exchange and depiction
ISO IEC61512
Enterprise-control system integration
Batch Control
Manufacturing operations specific concepts
ISO15531
(not studied)
Industrial automation systems and integration – industrial manufacturing management data
Manufacturing specific concepts
ISO11179
Information Technology – Metadata registries
Semantic registry
Enterprise Language standards

8. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

9. CCM00-00_01_INTRO_OVW_en
04/2009
ISO UN/CEFACT CCTS
ISO15000 “Electronic business eXtensible Markup Language”
ebXML 
ISO ebXML - Core Componenet Technical Specification
CCTS
Developped by the United Nations Centre for Trade Facilitation and Electronic Business
Relevant work:
Core Components Data Type Catalogue
Core Components Technical Specification
XML Naming and Design Rules Technical Specification
Amount Ordinal
Binary Object Percent
Code Picture
Date Quantity
Date Time Rate
Duration Ratio
Graphic Sound
Identifier Text
Indicator Time
Measure Value
Name Video
Enterprise Language standards
CCM (R) BOK

10. Core Components Data Type Catalogue
Amount
Ordinal
Binary Object
Percent
Code
Picture
Date
Quantity
Date Time
Rate
Duration
Ratio
Graphic
Sound
Identifier
Text
Indicator
Time
Measure
Value
Name
Video
Enterprise Language standards

11. 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 machineprocessable 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.
Enterprise Language standards

12. UN/CEFACT CCTS Standards Stack
Core Components Technical Specification
Data Type Catalogue
Context Categories
Component Library ISO15000
Business Data Types
Message Assembly
XML NDR
Business Transactions
XML
XSD
XCDT
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
ISO 11179
SBDH
TMG (Techniques and Methodologies Group)
TBG (Trade Business Group)
ATG (Applied Technologies Group)
Implicit parts of UN/CEFACT Standards
Non UN/CEFACT Standards
UMM
UCM
UML Profile for CCTS
UML
EDIFACT
EDIFACT Syntax R e g i s t r y
ICG
Enterprise Language standards

13. Relationship between core abstract and business types
Enterprise Language standards

14. 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
Enterprise Language standards

15. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

16. OPC UA OPC “OLE for Process Control”
Legacy acronym, not much relevant today
“OPC Unified Architecture”
Totally re-engineered infrastructure
to facilitate information exchange between industrial applications
Field devices, Control systems, MES systems, ERP systems
OPC UA deliverables
Modeling language for describing structures, behaviour, semantics
Standard, extensible models
Messaging concepts to interact between applications
Communication concepts to handle data transfer
Enterprise Language standards

17. Elements of OPC UA (Node classes)
Main classes
subclasses
Defined by
Predefined
View
Object
ObjectType
Type
Definition
Folder type
DataTypeSystem
ModellingRule
EventType
Next slides
DataType
VariableType
Data Types
DataTypeDictionary,
Reference Type
Variable
Property
DataVariable
Methods
Enterprise Language standards

18. OPC UA standard Attributes
AccessLevel
IsAbstract
ArrayDimensions
MinimumSamplingInterval
BrowseName
NodeClass
ContainsNoLoops
NodeId
DataType
Symmetric
Description
UserAccessLevel
DisplayName
UserExecutable
EventNotifier
UserWriteMask
Executable
Value
Historizing
ValueRank
InverseName
WriteMask
Enterprise Language standards

19. OPC UA standard Services
Service set
Discovery
Discover Servers: FindServers, GetEndpoints, RegisterServer
SecureChannel
Open / close secure communication (lower level – protocol dependent)
Session
Open / close Session
Attribute
Read / write data (including history)
Subscription
Subscribe to data (receive data)
MonitoredItem
Subscribe to data (specifying which data to subscribe to)
View
Browsing
Query
Querying
NodeManagement
Add / delete Nodes and References
Method
Method calls
Enterprise Language standards

20. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

21. ISO15926
ISO “Industrial automation systems and integration—Integration of life-cycle data for process plants including oil and gas production facilities”
Developed in ISO TC184/SC4-Industrial Data by the EPISTLE consortium
Supported by POSC Caesar Association
Petrotechnical Open Software Corporation (Oil & Gas, Norway)
Modestly states a focus on reference data lifecycle and Oil & gas
But much wider applicability
Focuses on describing industrial facilities
Based on an upper level ontology of large expressiveness
OWL implementation available
Convoluted, restrictive, probably unfitted title…
Enterprise Language standards

22. ISO15926 in short
ISO specifies an ontology for long-term data integration, access and exchange
Contains about 200 classes and properties
Support the evolution of data through time
Includes
Upper ontology elements such as thing, class, possible_individual and relationship
Generic classes such as physical_object, activity, event and generic relationships such as participation and connection_of_individual
Can be extended by defining specific classes
such as pump, distillation_column
The Reference Data Library ISO standardizes many common real objects
Enterprise Language standards

23. ISO15926 - Upper level types Class Thing Possible Individual
Pump #1234
Abstract
object
Pump
Relationship
Pump #1234 is member of Pump
Composition of Individual
Connection of Individual
Multi-dimensional
List of « Things »
Enterprise Language standards

24. ISO15926 - examples Upper level types Physical object
Material organization
Enterprise Language standards

25. ISO15926 Example
Enterprise Language standards

26. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

27. ISO15414
ISA15414  "Information Technology – Open Distributed Processing Reference model – Enterprise Language "
Developed by ITU
International Telecommunication Union – ITU-T X.911
Proposed « Enterprise language » in the more global context of RM-ODP
Reference Model of Open Distributed Processing
ISO /2/3/4 - ITU-T X901/2/3/4
Enterprise Language standards

28. 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
Enterprise Language standards

29. ISO15414 Structuring rules Community rules Enterprise object rules
Common community types
Lifecycle of a community
Objective rules
Behaviour rules
Policy rules
Accountability rules
Enterprise Language standards

30. Example: System concepts
Enterprise Language standards

31. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

32. ISO19440 ISO19440 “Constructs for enterprise modelling”
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.
Enterprise Language standards

33. 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
Enterprise Language standards

34. Example of « Business Process » - Header
Construct label
[‘BP‘]
Identifier
[<model-unique 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 Authority
[<identifier> / <name> of Organisational Unit or Organisational Cell with the authority to design/maintain this particular instance]
Enterprise Language standards

35. Example of « Business Process » - Descriptives
DESCRIPTION
[textual description]
OBJECTIVES
[non-empty list of Objectives to be fulfilled by the Business Process instance
CONSTRAINTS
['NIL' or list of Constraints imposed on the BP instance]
PERFORMANCE
INDICATORS
['NIL' or list of the metrics or measures by which achievement of the objectives can be assessed]
DECLARATIVE
RULES
['NIL' or list of Declarative Rules applicable to this Business Process instance]
INPUTS
[non-empty list of <identifier> / <name> of all Object View instances, occurrences of which can be received by occurrences of the Business Process instance]
[non-empty list of <identifier> / <name> / <source domain> of all Events , instances of which can be received by occurrences of the Business Process instance]
Enterprise Language standards

36. Example of « Business Process » - Descriptives
OUTPUTS
[non-empty list of <identifier> / <name> of all Object View instances, occurrences of which can be sent by occurrences of the Business Process instance]
[non-empty list of <identifier> / <name> / <sink domain> of all Events, instances of which can be sent by occurrences of the Business Process instance]
PROCESS BEHAVIOUR
[non-empty set of Behavioural Rules expressed using the syntax defined for Process Behaviour as defined in 6.3.3]
PRIORITY
[Integer in a range <min, max> where min and max are integers representing the lowest and highest priorities respectively]
Enterprise Language standards

37. Example of « Business Process » - Relationships
WHERE USED
[<identifier> / <name> of the Domain employing this Business Process instance]
CONSISTSOF
[non-empty 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
Responsibility
[<identifier> / <name> of Organisational Unit or Organisational Cell with responsibility for operation of this instance
Authority
[<identifier> / <name> of Organisational Unit or Organisational Cell with authority for operation of this instance]
Enterprise Language standards

38. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

39. BPMN BPMN “Business Process Model and Notation”
Originally created by BPMI as a simple notation for describing processes from a business perspective
Since its move to OMG, it became “IT enabled” and much more expressive (and subsequently more difficult for non-it users)
The coming BPMN 2.0 is a widely encompassing specification for describing activities in many relationship situations
BPMN 2.0 is “interpretable”
Uses XML Schema, XPath, and WSDL,
Includes XSD / XMI serialization
Defines a formal mapping to BPEL4WS, though not all BPMN model can be translated to BPEL which focuses on Web service orchestration
Enterprise Language standards

40. A limited scope
In the context of an Enterprise Language, BPMN offers a lexical and graphical semantics for describing collaborative behavioral aspects
Does not address
Definition of organizational models and resources
Modeling of functional breakdowns
Data and information models
Modeling of strategy
Business rules models
Enterprise Language standards

41. BPMN interactions types
BPMN defines 2 types of interaction types
Process
Choreography
BPMN defines 2 types of interaction scenarios
Collaboration
Conversation
Enterprise Language standards

42. BPMN element types
BPMN defines a formal semantics for describing behavioral intaractions
Flow Objects
Events, Activities, Gateways
Data
Data Objects, Data Inputs, Data Outputs, Data Stores, Properties
Connecting Objects
Sequence Flow, Message Flow, Association, Data Association
Swimlanes
Pools, Lanes
Artifacts
Group, Text Annotation
Enterprise Language standards

43. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

44. ISA-88 and ISA-95 An XML schema specification B2MML
KP_T-8895_Overview_Modeling_v1_en.pptx
11/2009
ISA-88 and ISA-95
ISO/IEC62264 – ISA- 88 – Batch Control
Object Design of automation applications for flexible manufacturing
Manufacturing solutions Interoperability and information history
Product lifecyle from the definition of physico-chemical transformations to operating procedure for target facilities
Initially designed for Batch processes, but applicable to any type of process
ISO/IEC62264 – ISA-95 Enteprise – Control System Integration
Communication between business and manufacturing systems
Typically between ERPs and SCADA/MES
Extending to intra operations management level communications
Classification of manufacturing operations management
Typical MES systems functionalities
Not really a model, not exactly a thesaurus – almost an MES “tutorial”
An XML schema specification
B2MML
Enterprise Language standards
CCM (R) BOK

45. ISA-88/ISA-95 modeling framework
KP_T-8895_Overview_Modeling_v1_en.pptx
11/2009
ISA-88/ISA-95 modeling framework
ISA-95
Product Asset Management
Inventory Asset Management
Physical Asset Management
Human Asset Management
IT Asset Management
ISA-88
TOGAF
ITIL
ISA-88 + ISA-95
Enterprise Language standards
CCM (R) BOK

46. ISA95 extended physical model (Actual Facility layout)
KP_T-8895_Overview_Modeling_v1_en.pptx
11/2009
ISA95 extended physical model (Actual Facility layout)
ENTERPRISE
PROCESS
CELL
UNIT
BATCH
(ISA88)
PRODUCTION
UNIT
CONTINUOUS
PROCESS
PRODUCTION
LINE
WORK CELL
DISCRETE
PROCESS
STORAGE
ZONE
UNIT
WAREHOUSE
SITE
AREA
WORK
CENTER
WORK UNIT
Product Asset
Physical Asset
Human Asset
IT Asset
Inventory Asset
EQUIPMENT
MODULE
CONTROL
MODULE
Enterprise Language standards
CCM (R) BOK

47. ISA95 Operational Activity Model
KP_T-8895_Overview_Modeling_v1_en.pptx
11/2009
ISA95 Operational Activity Model
4. Data
collection
3. Execution
8. Resource
management
2. Dispatching
5. Tracking
1.Detailed
scheduling
7. Definition
6. Analysis
Product Asset
Physical Asset
Human Asset
IT Asset
Inventory Asset
Production
Other
Discuss why these are called core issues and explain the difference between this definition and the MESA model.
Quality Control
Inventory
Maintenance
Enterprise Language standards
CCM (R) BOK

48. ISA-88/95 Modeling elements
KP_T-8895_Overview_Modeling_v1_en.pptx
11/2009
ISA-88/95 Modeling elements
Domain
Model
Std
Information elements
Product Asset
Process
Product
ISA88
ISA95
Product Hierarchy
Product Definition
Inventory Asset
Material
Material Resources
Equipment Asset
Physical
Equipment
Equipment Hierarchy
Equipment Resources
Human Asset
Personnel -
Personnel Hierarchy
Personnel Resources
Equipment Control
Procedural
Functional Hierarchy
Equipment Procedural Elements
Physical Process Control
Physical Processes / Procedural Elements
Physical Process Transform Components
Physical Process Mngt
Segment
Segments
Operation Process Mngt
Operation Activity
Operation Processes
Activities / Tasks
Enterprise Language standards
CCM (R) BOK

49. Introduction ISO15000-5 UN/CEFACT CCTS OPC UA ISO15926 ISO15414
BPMN
ISO62264/ISA-95 + IEC61512/ISA-88
ISO11179
Enterprise Language standards

50. ISO11179 ISO11179 “Information Technology – Metadata registries”
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
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
Enterprise Language standards

51. 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
Enterprise Language standards

52. ISO11179 meta model « Value » « Measure » « PT104 » « Temperature »
Enterprise Language standards

53. ISO11179 data administration
Enterprise Language standards

54. Thank You ! Enterprise Language standards CCM00-00_01_INTRO_OVW_en
04/2009
Thank You !
Enterprise Language standards
CCM (R) BOK