Towards a Support Framework for Enterprise Integration

Transcription

1 EI2N 2010: 5 th International Workshop on Enterprise Integration, Interoperability and Networking Towards a Support Framework for Enterprise Integration Ovidiu Noran 27/10/2010

2 The Enterprise Engineering (EE) tasks involved in obtaining / maintaining Enterprise Integration (EI) are on-going, complex, lengthy and are often ill-defined. To make it worse, Enterprises are moving targets Major needs: a) common understanding of the present (AS-IS) b) choosing the future (TO-BE) c) defining how to reach the future state (actions / schedules) d) communicate this vision to the rest of organisation(s) Many frameworks aiming to support EE exist. We propose a novel approach based on analysing the interactions of all relevant EI project participants in a lifecycle context.

3 Framework component 1: a method to construct methods How to? Domain Knowledge Structured Repository Entity E1: the large Farmer / association Entity E2: the small / medium Carrier Entity E3: the large Wholesaler Entity E4: the small / medium Retailer Entity E5: the Food Plant / Processor Entity E5: the Commodity Handler Entity List Business Model Activity model Meta-methodology Specific method

4 Framework component 1 (refined): a set of steps / sub-steps Environment Factors Project Scope Best Practice Reassess Domain knowledge Build Entity List Build Business Model Build Activity Model New Knowledge (tacit, reasoning, explicit,..) (expressed in Models) Aspects (Views) AS-IS, TO-BE Language, Tools Legend: (NIST, 1993) Architecture Framework Elements Enterprise Architect, CIO, Tools input control Activity output resource

5 Framework component 2: A repository of Architecture Framework elements AF Element type family integration tools Prerequisites (,..., ) Outcomes (,, ) Knowledge Base AF Elements AF Elements: Modelling Fwks, Languages, Methods, Reference Models Rule Find AF Elements w. Outcomes matching Prerequisites Rule Order AF Elements: - least prerequisites - multiple use - integrated set - aspect coverage Rules

6 Human Manuf. & Info Ctrl Org M H & O I / C M H & O I / C ARIS FEAF TOGAF GRAI Zachman CIM-OSA GERA EEM EML Generalised Enterprise 1..* 1..* Enterprise Engineering 0..* 1..* Enterprise Modelling Language Reference Architecture Methodology employs utilises Identifies concepts of Describes process of Provides modelling constructs for Enterprise Integration enterprise engineering processes, technologies and human role 0 * 1..* implemented in 0..* implemented in 0..* GEMC EET Generic Enterprise 0..* Enterprise Engineering Modelling Concept supports 0..* Tool Defines the meaning of Supports Enterprise enterprise modelling constructs Engineering PEM 0..* supports Partial Enterprise Model Provides reusable reference is a kind of models and designs of processes, technologies and human roles EMO Enterprise Module 0..* 1..* Provides implementable modules of operational processes, technologies and human professions used to implement 0..* used to build 1..* EM Enterprise Model Supports Enterprise Engineering 1..* used to implement 1..* EOS Enterprise Operational System Supports the operation of the particular Enterprise M M PERA H & O I / C H & O I / C Processing Processing Requirements Operational View Systems Assoc to Requirements Requirements Specific Capabilities Systems Technical View View Technical Criteria Technology Capabilities Processing & Info Requirements C4ISR / DoDAF FEAF Other AFs ( = imminent) Reference AF: ISO15704 Annex A Add Generic Elements Tools Modelling Formalisms Partial Models Modelling Fwks Supports Family Framework component 2 obtained by mapping main AFs to a neutral reference Modules AF + generic Elements

7 GERA Generalised Reference Architecture EEM Engineering Methodology utilised in EML Modelling Language GEMC Generic Modelling Concept PEM Partial Model EMO used in MOdule supports define meaning of Reference used: GERAM (ISO15704:2005 Annex A) implemented in EET Engineering Tool used to build EM Model used to implement EOS Operational System

8 Sample Additional Rules Should the present state (AS-IS) be modelled? IF ((TO-BE_obtained_from_AS-IS) OR (AS-IS_not_understood)) THEN (model_as-is) Thus, model present state will fire if user asserts the fact that the future state (TO-BE) will be largely based on the present, i.e. no radical changes mandated

9 Sample Additional Rules (cont.) Should several TO-BE states be modelled? Should the TO- BE be represented separately from AS-IS? IF (undecided_to-be) THEN (several_to-be) and (as a likely consequence): IF (SEVERAL TO-BE) THEN (separate AS-IS_TO-BE) So, if the stakeholders do not have a clear, common view of the future state, represent several scenarios in separate models

10 Framework component 2: Evolved format (added additional best practice, steps / substeps rules) AF Elements Rules Steps & Substeps

11 Possible Implementation: A Decision Support System AF Elements Inference Engine AS-IS, TO-BE(s) Aspects to model Suitable Tools, Languages Change Management Activities G u i d a n c e Rules Knowledge Base Steps & Substeps User Interface AF Elements Stages, sub-steps

12 How would the system work? The user is prompted to perform actions according to the main stages and sub-steps. Advice is provided according to best-practice; The system interactively creates ranked lists of elements suitable for modelling the aspects necessary for the task at hand. Dependencies are automatically resolved. The user makes selections that confirm or override the system, returns to saved bookmarks, etc

13 Conclusions EI can benefit substantially from a support framework. This approach is based on the analysis of project participants interactions in the context of their lifecycle phases. Distinctive features: based on an original, tested theoretical concept; uses a life cycle paradigm, appropriate for dynamic organisations; uses mainstream AF elements (while AF-neutral); suggests areas that need to be represented in the change process, suitable models and tools

14 Future Work complete the AF element repository (map other AFs) refine meta-methodology rule logic through more field tests implement the system using a suitable suite / shell. The system components must be continuously updated to reflect latest AF developments and best practice.

15 THANK YOU