ISO/TC 184/SC 5/WG 1: 2000-May-15/17

ISO/TC 184/SC 5: 2000-May-18/19

Kyoto International Conference Hall, Kyoto, Japan

Jim Nell, WG 1 Convenor, opened the meeting at 0900 on 2000-May-15.

Attending were:

Yoshiro Fukuda Japan, host

Michael Gruninger Canada

Hao Shufen China (Tuesday Wednesday)

Jinyou Wang China (Tuesday Wednesday)

Wang Qian China (Wednesday)

Jean-Jacques Michel France, and Convenor TC184 SC4 WG8

Roland Jochem Germany

David Shorter UK

Shaw Feng US (Tuesday Wednesday)

Em dela Hostria US, Convenor WG4 pro tem, SC5 Chair

Jim Nell TC 184 SC 5 WG 1 Convenor

Greg Winchester TC 184 SC 5 WG 1 Secretary (part time)

Wednesday, 17 May TC 184 SC 5 WG1 met jointly with TC 184 SC 5 WG 4 to discuss WG1 requirements for standard software-capability profiles, and with ISO TC 184 SC4 WG8 to discuss how to standardize aspects of the Process Specification Language.

The minutes of the La Defense meeting (WG1 N436) were approved as written.

The group approved the agenda (WG1 N437) with the following changes:

• Item 6: Change order of discussion in item 4 to accommodate the joint sessions
• Item 6e: Move the IFAC/IFIP UEML discussion to item 4, Related Activities, because it requires development before it is ready for standardization by WG1.

Greg Winchester reported that the ISA (the US-based Instrument Society of Measurement and Control) SP 95 committee has completed a final draft of Enterprise-Control System Integration, Part 1 terminology and models, a candidate standard. ISA has decided to fast track the draft in IEC SC65a for approval as an IEC standard. They have no intention of standardizing in ISO, where TC 184 SC 5 would be the logical place for industrial enterprise-control-system standardization. WG1 is interested in the standard because the topic is defining interfaces between enterprise-resource systems, manufacturing-execution systems, and factory-floor processes. WG1 needs to know more about this environment to define requirements for our series of standards on improving manufacturing-process interoperability. WG1 instructed its convenor to introduce the topic to the SC 5 plenary session later in the week.

ACTION: Jim Nell to raise this issue as part of his WG 1 convenor's report to SC5 and recommend that SC5 consider that the work should logically be done in the TC184 SC5 venue and advise IEC SC65a of the WG1 position on this matter.

At the SC5 meeting SC5 noted the WG1 concern and agreed to obtain copies of the document and forward them for WG1 review and recommendation of further action.

WG1 discussed several concepts to better understand manufacturing-process interoperability. We assumed that the necessary infrastructure would be in place and that there would be two players involved in transactions, a customer and a supplier. Customers and suppliers have applications, software, each of which has its own ontology inside that conforms to international standards, hopefully those being planned by the new PSL-ontology project. When a manufacturing enterprise engages in these transactions there are several actors whose role need to be defined and understood. There would be enterprises, applications, processes, and systems. In addition, there is information representing the information aspects of those actors.

For this standard WG1 considers the following to define the actors and the transactions:

Interoperability. Sharing necessary information among the information aspects

Application. Software system or tool

Process. Collection of software, information models, and physical systems that perform a function

System. Collection of real-world items organized for a purpose

Enterprise. Collection of processes that share common goals regarding its product or service output

WG1 feels that although one can envision exchanges such as process-to-process, system-to-system, and enterprise-to-enterprise, none of those will be meaningful to us because of imprecision. The standard is to enable more effective exchange signals between modeled business processes. Therefore, we will consider the only meaningful transaction to be information aspect-to-information aspect, and this most often will occur between customer and supplier applications.

Following is an initial attempt at an outline for the new standard:

Title: Requirements for manufacturing-process interoperability

4.1 Capability (Invitation to dance: things to do to capabilities)

4.1.1 Identify capability (methodology, declare context (usage and applicability, and regime of interoperability))

4.1.2 Extract

4.1.3 Extend

4.1.4 Register, publish

4.1.5 Compare

4.1.6 Constrain

4.1.7 Organization of capabilities

4.1.8 Represent (shall include pre and post conditions)

4.1.9 Quality of service

4.2 Protocols (The dance: Things to do with capabilities)

4.2.1 publish (supplier)

4.2.2 Browse (customer)

4.2.3 Interrogate

4.2.4 Invite

4.2.5 Offer

4.2.6 Assess match

4.2.7 Do match

Complete

Partial (extend or redefine)

None

Qualified (match if)

4.2.8 Establish communication (closure)

4.2.9 Quality of service management

4.2.10 Exit (Reset)

Annexes for scenario, use cases, and collaboration diagrams for protocols (for example, swim lanes)

In writing the standard we need to:

• Define the use cases and scenarios
• Hang some meat on each of the outline elements
• Identify what parts of this standard can be provided by other working groups

The figure above was prepared by Yoshiro Fukuda to help the working group sort out the various concepts of process interoperability and to allow us to focus on the parts that would be standardized by this working group. The Convenor has added some features that will be discussed further at the next meeting.

Because WG4 had insufficient resources to accomplish meaningful work, the task to begin to define the nature of the profiles was deferred. Instead, WG1 discussed with WG4 its need to have the capability of software applications to be defined in standards such that one process application can evaluate the capability, applicability, and quality of another in a pre-defined way.

The CEN TC310 WG1, the CEN group paralleling ISO TC184 SC5 WG1 for European standardization, has received approval to update and extend ENV 40 003, Framework for enterprise modeling and ENV 12 204, Enterprise-modeling constructs. The first meeting to update these standards is in Berlin 2000-May 23/26 in conjunction with a European workshop to further work in this area. Updating the ENVs 12 204 and 40 003 are to be done jointly with TC184 SC5 WG1. To this end, several ISO TC184 SC5 WG1 experts will be in Berlin. David Shorter will be there as convenor of CEN TC310 WG1, and Jean-Jacques Michel will attend part time. Kurt Kosanke will be there as conference chairman. Francois Vernadat and Peter Bernus will be there as participants in the IFAC/IFIP Task Force. Roland Jochem, the host of the workshop, will represent ISO TC184 SC5 WG1 officially in Berlin and will report results to ISO TC184 SC5 WG1.

David Shorter reported that the 00-05-23/26 workshop in Berlin has thirty experts registered. This workshop is combining three activities: the workshop, a CEN TC310 WG1 meeting, and an IFAC/IFIP task force on enterprise integration. The purpose of the workshop is to develop a European plan to support the new CEN work item to update the CEN ENVs 12 204 and 40 003, pre-normative standards that cover enterprise-modeling constructs and enterprise-modeling architecture, respectively. The workshop also plans to consider how CEN ENV 13 550, EMEIS, is supported commercially, whether there are infrastructure capabilities that EMEIS does not address, and to solicit from industry how EMEIS could be made more useful and usable.

Updating the ENVs will consist of the following:

ENV 40 003: The ENV 40 003, based largely on CIMOSA, will be updated to include Generalized Enterprise Reference Architecture concepts from the ISO 15704, Requirements for enterprise reference architectures and methodologies. The project will:

• Address shortcomings with respect to newer modeling approaches
• Expand enterprise life-cycle coverage
• Provide a more rigorous conceptual founding, perhaps using UML the model concepts and relationships
• Improve the representation of generic partial and particular modeling concepts
• Include a description that positions the 40 003 framework within ISO 15704, Requirements for Enterprise Reference Architectures and Methodologies
• Provide a position statement for model-based enterprise engineering.

ENV 12 204: The ENV will be extended to define more clearly the relationships of Product and Order with other constructs, make serial rules normative, accommodate different planning horizons as per the GRAI-grid, consider the issue and feasibility of graphical representation of constructs, and consider human issues and capability.

The theme of the work will be to provide a much sounder base for the constructs in logic. The team will use UML, TogetherJ and NoMagic tools. They will be looking for a canonical form for constructs so users can compare models. The results will be similar to the ontology part of PSL.

There was concern that the ballot soliciting support for the ENV updates received disappointing amount of support both in and outside of Europe; in fact, while there was enough countries approving the work, there was insufficient support to participate in the new activity. The US voted to abstain on both the approval and participation aspects of the ballot because of the ballot make-up and because we felt our support would be insufficient. Other key countries not voting or abstaining were Italy, Belgium, and Australia. ISO TC184 SC5 WG1 feels that this work is important to its standardization plans and that it should proceed on a joint basis. At the meeting, we all reminded ourselves that support can consist of reviewing and commenting to documents in a timely manner. The US can certainly do this.

ACTION: Jim Nell to notify Greg Winchester, SC5 Secretary, that the US would participate in the work by reviewing documents that are generated. Jean-Jacques Michel will notify contacts in Italy regarding their support. David Shorter will contact Australia and Belgium regarding their support.

Jean-Jacques Michel reported that PLS is needed by different working groups of TC184 SC4 and SC5. One of the first project tasks will be to identify the needs of the working groups SC5 WG1, SC5 WG4, and the MANDATE project currently in SC4 WG8. The PSL project will consolidate needs where practical, and meet jointly when the needs are similar, and separately when needs are individual. Meetings will occur at both SC4 and SC5 working-group venues. As regards the joint project between CEN and SC5 WG1, the requirement for PSL will come from formalizing the modelling constructs of CEN 12 204. These constructs could become pieces of PSL because the constructs will be formalized.

Formation of the joint working group must be endorsed by SC4 (hopefully 00-June) and by SC5 (done: SC5 resolution 346, 00-May-19) and by the TC184 Advisory Group.

ISO TC184 SC5 WG1 needs an ontology to do or contain the following:

• Have negotiated or mediated capability
• A standard way of creating a new ontology from customer and supplier local ontologies
• Consensus on semantics of the ontology
• Consensus on the methodology of representing of the ontology
• Tools to support and extend the ontology
• Concepts such as qualities, properties, and characteristics
• Language with formal syntax and has notion of consistency and equivalence
• A way to ascertain completeness

The following are ontologically necessary to achieve self-integrating system

• Flexibility, extendibility, capability to mediate to create needed characteristics
• Method to create the temporal ontology
• Way to agree on semantics between two systems
• Standard way for applications to represent their own ontology
• Terms in the ontology: qualities, properties, characteristics, for example timed or located
• Language with formal syntax and has notion of consistency, equivalence, and completeness
• Ways to assure compliance and conformance
• Characteristics or negotiation acts increasing levels of commitment
• Static--Is a meaningful exchange possible? (Use IDEF, PSL, KIF to give model information)
• Dynamic--Is exchange sufficient to achieve behavior desired?

• Quality of performance--Can we resolve the differences?

• Fault-recovery capability
• Behavior capability to fulfil objective

5e UEML
The IFAC/IFIP Task Force on Enterprise Integration project is preparing a questionnaire to gather requirements for the Universal Enterprise Modeling Language. A European project, called Framework 5, has been formed to research and develop UEML concepts.

2000-September-11/13 NIST, Gaithersburg USA

2000-October-16/18 Charleston SC USA, SC 4/JWG 8. Note: SC5 WG1 experts will be invited to help develop the PSL standards: (Parts 1, 11, and 12 Mon. 00-10-16, 1300-1700 hours, Parts 4x Tue. 00-10-17, 0800-1530 hours, and PSL tutorial 1530-1700 hours)

Upon thanking Dr Yoshiro Fukuda for the excellent arrangements and hosting, the convenor adjourned the meeting on Wednesday, 2000-May-17, at 1600.

PREPARED BY: Jim Nell, WG 1 Convenor

EDITED BY: Greg Winchester, WG 1 Secretary