Quality Inn & Suites Golf Resort, Naples, Florida, USA

1. The UEML project is in its startup phase, which will complete in 2003-June, they the project hopes to be part of the European 6th Framework initiative. The objective is to use prEN ISO 19440, Constructs for enterprise models, as a basis for exchange of enterprise models. So far, there has been an information-dissemination meeting and more are planned. Kurt Kosanke will act as a liaison with ISO and CEN for any needed standardization. David Shorter and Kosanke are project members and active members of TC 184 SC 5 WG 1 and CEN TC 210 WG 1. Currently, a consortium of participants is being solidified.
2. Kurt Kosanke provided status of the prEN ISO 19440, Constructs for enterprise models. The last meeting was in Paris in 2002-December, where a new draft was prepared. The current document is N200, which will be submitted for a joint ISO and CEN DIS ballot after behavior rules are complete.
3. The CIMOSA report is what Kurt reported about UEML above.
4. ISA SP 95, JWG 15. IEC 62264 consists of three documents, For Part 1, the FDIS ballot was approved by 100% of those voting. Part 2 was submitted for DIS CDV fast track: ballots close 03-01-10 for the IEC and 03-03-10 for ISO. Part 3 is still under development. Seven meetings of JWG 15 are scheduled for 62264 in 2003. Richard Martin and Ted Williams discussed need to call attention to technical issues identified in Part 1 so that Part 2 can be correctly specified. The resolution requires clear statement of issues so that JWG 15 members are fully informed concerning discontinuity between text and UML models in those two documents.
   
   It may be possible to use the amendment process to correct errors after publishing; Greg Winchester informed that IEC will need to administer any "maintenance team", probably through JWG 15, to do a revision project leading to amendment.
   
   Discussion between Richard Martin and Ted Williams resulted in agreement for Richard Martin to attempt prepare a document explaining the difficulty. Ted will distribute this explanatory document to the JWG 15 members before the North Carolina meeting in mid February to resolve issues before publication. (This explanatory document may not get done in time depending upon Richard Martin's client schedule.)
5. Vocabulary Consistency: Kurt Kosanke is leading an SC5-requested activity, resolution 418, to investigate the degree of consistency in SC5 standards. Kurt prepared a summary document of various definitions clauses, and compared that with Collins dictionary entries for defined terms. Kurt suggests using a key word with a qualifier of at least one word to distinguish what are now conflicting definitions rather than creating more definitions for the same word. Em dela Hostria asked about including in the definition a note regarding the origin of each term to aid in distinguishing terms. EM requested coverage of all section 3 terms for SC5 as target of activity. Jim Nell related experience at NIST with a project looking at computer-based means to determine when definitions are close enough to be considered equivalent. A general discussion of the vocabulary issue as it relates to interoperability versus integration since requirements may be different. Richard Martin related IEEE – SUO experience and agreed to contact Adam Pease of Teknowledge about possible effort to articulate a formal ontology of SC 5 vocabulary, or give us some guidance regarding how to proceed. There also was discussion about concern for aspects of defining terms and possible missing-term properties. The discussion concluded with the recommendation to identify the need to provide guidance in making new clause 3 definitions.
6. Informed group of N743 Diagnostic and Maintenance application document effort. Identified MIMOSA relationship with scheme for machine diagnostics. TAG response to N743 NWIP is due 02/24/2003. Discussed possible SP-99 effort for elaboration of ISA Security effort. How to make an enterprise secure; do IT security standards fit with needs of manufacturing control domain?
7. Other: Kurt Kosanke mentioned the Object Management Group's request for proposal on Profile for Business Process Definition and its possible relevance to SC5 and WG1. Em dela Hostria identified liaison with the OMG Manufacturing Task Force and the need to verify that this is in scope of TC 184. Discussion centered on need to be sure current SC5 efforts were understood by and accommodated by the OMG effort. Em dela Hostria or Greg Winchester will contact the OMG Manufacturing Task Force to determine extent of their involvement in the business-process activity.
   
   Other: Michiko Matsuda reported on the status of the WG4 current work item. 16100 –1 is now published, 16100 –2 is in final preparation for publishing, 16100 –3 (Interface Protocols and Templates) is in draft, and 16100 –4 (Conformance and Testing Methods) is only identified by scope. There is currently a "call for editor" issued for part 4.

At the Valencia meeting WG1 prepared an initial response to SC5 resolution SC5 resolution 396 and 407 relating to an economic view for ISO 15704. WG1 will consider any input received with respect to making an economic view a requirement of the ISO 14258 and ISO 15704 standards, and initiate the process to amend the standards accordingly. To date, no written contribution has been received regarding the economic-view issue. This topic arises from resolution 396 of Beijing in 2001. Action: Since no documentation has been received, WG1 will ask China for a few examples of what they mean by an economic view. Then, China should project the examples onto explanations an economic view; such as, a cash-flow model using activity-based costing.

At Naples, Professor Yuliu Chen, China, presented slides and discussed issues relevant to the economic view. Entrepreneurs are not attracted to CIM architecture because they need information on economic elements of enterprise operation and re-engineering. Economic factors play a key role in enterprise analysis but these factors are not articulated. Therefore, enterprises should tie their enterprise-reference architecture to economic benefit of operating and changing the enterprise. The number of views the enterprise uses depends upon the number and nature of questions to answer. In addition, the major modeling methods in general use; for example, IDEF-0; are driven by architectures that do not provide for economic content. Attempting to answer questions beyond the scope of a methodology increases model complexity.

Enterprise analyses seek measurements of enterprise performance in the following categories: financial quantitative, non-financial quantitative, and qualitative. Economic analysis is more important at the beginning of the life cycle to evaluate alternative improvement projects, after detail design, and during operation. However, the information to support adequate analyses is often elusive or not directly generated by the enterprise. Therefore, if economic view is mandatory, then some enterprises never can comply because required content is not available. It is also clear that we are seeking full economic views of the enterprise and its environment, such as the market, rather than the financial view or cost view of the enterprise alone.

The system architecture should answer most questions on system integration. Now, we can use it to describe, analyze, and design such enterprise features as organizational structure, resource configuration, decision process, information relationship, and function. However they cannot describe economic information yet. For example, they cannot point out the direct and indirect benefit ensuing from an advanced-technology implementation. Managers need this information to make informed decisions about improving enterprise operation.

In a resource view, there is information on economic elements; for example, physical and human resource cost can be obtained. Sometimes, knowledge cost can be derived as well. But this kind of information cannot cover all economic elements. To answer these questions, it is necessary to provide for an explicit economic view in the architecture.

An economic view will answer different questions at different stages of life cycle of a system-integration-improvement project. Before the implementation, it should present how much money an enterprise should spend when the designed system is implemented. Especially, its analysis should explain if the return is worth the cost. Direct benefit can be derived easily. Here, those indirect benefits should be transferred into calculable indices so that manager can balance between cost and technology. Furthermore, economic view should uncouple benefits of different investments. Thus we can know how every introduction of new technologies affects the enterprise. While implementation, economic view should present methods to trace cost, workload, and return, etc. and presents method to analyze and control these factors. There are justification issues that the economic view should consider. These include: methodologies for determining:

• Direct and indirect cost of the introduction of new technology
• Cost and risk of integration
• Direct and indirect benefits of integration
• How to de-couple the benefits among different investments
• How to balance between cost and new technology
• How to trace the change of economic elements and how to control them

The group consensus was that an economic view is, in the end, the final justification to decide how to best improve enterprise operation. In fact, given requirements for the other enterprise views, the information presented by those views probably should be organized to feed into an overarching view--the economic view. To handle the discussion of the economic view in ISO 15704, the group decided to use the following approach.

• Prepare an annex amendment that Professor Chen originates to elaborate 4.2 and 4.3 as model-based economic view. Add economic view projected from the four mandatory views as benefit (see clauses 4.2.10 and 0.4 of 15704).
• Issue an NP for a new document to address benefits of ISO 15704 and 19439 as regards life-cycle, model-based architecture including economic view, process view, decision view, function view, information view, resource view, organization view, and others the enterprise deeds useful. Professor Chen suggested a need for a rigorous definition of view for the NP. The amendment also needs to state benefits and risks of integration and a means to assess effectiveness of integration.
• Add to 19440 the constructs for economic view.

WG1 N433, rev 4, dated 03-01-15, is an NP Entitled: Requirements for establishing information interoperability in manufacturing-enterprise processes. This was updated as a result of discussion at the Valencia meeting. After a WG1 review, the current draft was deemed ready to be sent through the ballot process for SC5 P-member approval.

7. prEN ISO 19439, Framework for enterprise modelling

prEN ISO 19439, Framework for enterprise modelling, a DIS, has been circulated for ballot and several comments from China, France and the US have been received. WG1 addressed these comments, and offered the resolutions to David Shorter, CEN TC310 WG1 convenor, to prepare the document for the FDIS review.

Next meeting: not arranged, although WG1 acknowledges encouragement from SC5 for WG1 to meet in Korea. WG1 had planned to meet in Cheju, however, upon the resignation of the convenor, the group decided to withdraw their request for meeting space for that meeting.

Jim Nell adjourned the meeting at 1700 on 2003-January-23.