Strategic Workshop on Enterprise Integration and Enterprise Computing
(Systems and Software Engineering Standards in the Context of Enterprise Integration)

19-20 November 1998, Sanctuary Cove
(Brisbane's Gold Coast, Queensland Australia)

Position Statement (David Shorter, 6th November 1998)

This statement is in three parts, the first being a general concern about how to get enterprise modelling recognised and used, the second a statement from a European workshop, and the third a personal response from me as CEN TC310 WG1 convenor to Jim Nell’s ‘dialogue’ questions.

1. General

Problems for standards-makers concerned with Enterprise Modelling (EM) in support of Enterprise Integration are that:

Proposal:

Focus on the business drivers that senior management in industry will respond to, and explain and demonstrate how EM technology will help. We tend to be mired in discussions of technical issues to be resolved and the impact of ‘new’ technology. Let’s put that on one side, document the achievable business benefits, agree what EM capabilities vendors need to be able to deliver to achieve those, who the stake-holders will be and only then move to define what technical problems still need to be solved and where standards should be part of that solution. Then promote these messages to management.

2 CEN STAR workshop recommendations

The following is the final report of a CEN STAR working group (A) produced during a two day meeting in Senlis in June 1998. Members of the working group were: K. Kosanke, CIMOSA Association, Germany, J-J Michel, CETIM, France, M. Petit, University of Namur, Belgium, D. Shorter, IT Focus, UK, R. Weston, Loughborough University, UK. (A previously duplicated paragraph in 2.1 has been moved to 2.3.)

2. Technology Trends

The move in industry is towards autonomous enterprise units (extended and virtual enterprises with agile behaviour) with a significant need for decision support based on real time information. Such information can be identified by and represented in enterprise models and with sufficient ICT support the models can be used to evaluate strategic, tactical and operational alternatives through simulation of business process/enterprise models. Because these models represent both business and technology components, they can be used to maintain the coupling between the business requirements and the technological solutions.

Enterprise models have to coexist and interwork with product models and new models of electronic interworking (EDI, CALS). At present these different kinds of models have different semantic underpinnings (the same word means different things) and it is difficult to relate concepts precisely (say in a form allowing computer support for visualisation of relationships and even assistance with translation). This also makes it difficult to present and assess which standard is addressing what, how they are intended to interwork and what standards should be specified to meet a particular business need at a particular time.

Therefore representation and handling of enterprise models have to be adapted to the needs and capabilities of business people to allow for modifications and their evaluation and verification to be carried by those people themselves.

2.2 Serious Drawbacks

However, we are in a real vicious circle: proactive standardisation has per definition a long pay back period and is a high risk investments, but with a high ROI - if successful. Therefore industry will try to avoid this and will invest in reactive standardisation type activities with low risk and relatively low ROI. The result is a loss in use of leading edge technology, due to not being aware of capabilities and therefore not being able to use more efficient and effective methods, tools and technologies in the enterprise operation.

On the other hand we are supporting technology development with rather large amounts of tax payers money, but we forget about the needs for technology transfer to the user. With the complexity of current technologies the demonstration of applicability and benefits of new solutions is a prerequisite for awareness and acceptance in the user community. However, it is not sufficient to convince a few people in an organisation, but to create a critical mass in the enterprise which is willing and prepared to invest in the new technology.

2.3 Approach for Improvements

We think that new ways and methods have to be explored to create the critical mass of knowledgeable people in the enterprises and thereby achieve the technology transfer on a much broader scale and with an significantly increased speed. At the same time the barriers to take-up need to be lowered by developing and releasing model fragments which are easily accessible at low cost, so allowing industry to make incremental investments within a holistic framework. This will benefit both our industry, which will be again on the leading edge of technology, and the tax payer, who will benefit from his investment in a much shorter time frame with an improved standard of living.

Such an awareness campaign should focus on a selected set of regional enterprises doing some pilot work for demonstrating applicability and potential benefits. These enterprises would then act as show cases for the community.

2.4 Present Requirements

Enhance current standards or pre-standards and ongoing work:

New work items:

2.5 Existing Deficiencies

Overlapping and conflicting standards

Limited industry involvement in standardisation and use of standards. Need to improve transfer to industry and increase involvement:

2.6 Future Requirements

C CEN TC310 WG1 convenor’s response to Jim Nell’s ‘dialogue questions’

 



1. Process Representation
1.1 Define requirements for process models (WG1 La Defense) ISO, IFAC/IFIP
1.2 Extend CEN 12 204

(ICEIMT ws4)
Definitely a CEN intention/activity
1.3 Enterprise-component patterns (Weston) ISO, IFAC/IFIP. How useful will this be (because can standardize only at generic level and needs to be an open set)?
1.4 Specifications of modelling constructs (Weston) CEN, combine with 1.5
1.5 Formal & simple UEML

(XML?, PSL?) (ICEIMT ws4)
CEN, combine with 1.4
1.6 Model components for transfer over Web (Shorter) A possible CEN activity. Should be based on what we’ve already done, if done at all. Include AIT's XML pilot. Maybe combine with 2.1?


2. Terminology Facility
(WG1 La Defense)
2.1 Requirements for on-line, ontology-based, computer-processable, meaning mediation (WG1 La Defense) Possibly a CEN activity? Combine maybe with 1.6?


3. Integrating infrastructure
3.1 Requirements for next-generation integrating infrastructure.

(ICEIMT ws3, Kosanke)
We can distinguish between standards which define requirements and standards which deliver properties such as interworking and reuse. Where to pitch this item to be really useful?


4. Standards landscape for modelling and architecture standards.

(ICEIMT ws2)
4.1 Manage, update, and combine CEN M-IT-04 and ISO TR10314 (WG1 La Defense) A common concern for those of us concerned with ISO's and CEN's strategies. Not a standards-making issue though.
4.2 Priority list: modelling human aspects, integration platforms, model execution (ICEIMT ws2) A common concern for those of us concerned with ISO's and CEN's strategies. Not a standards-making issue though.


5. Human representation
5.1 Rules and guidelines for representing human roles, skills, and behaviour

(Kosanke)
In view of problems in getting a European consensus on a NWI in a related area (CEN TC310 WG4), maybe best treated as an IFAC/IFIP issue? Or possibly a CEN Workshop involving the active players, including the unions? Also R&D issues here.
5.2 Requirements for relating humans & supporting IT components (Weston) Similar comment to 5.1.

 

 

David Shorter, david@itfocus.demon.co.uk, 6/11/98