Interoperable Enterprise Systems: Principles, Architectures, Standards and Metrics F.B. Vernadat LGIPM, University of Metz, France European Commission, DIGIT/B2
F.B. Vernadat
Contents • • • • • • •
Introduction Interoperable Enterprise Systems Enterprise Integration & Interoperability Enterprise Architectures Standards for EI Metrics for EI Conclusion
F.B. Vernadat
Current Business Trends • • • • • • •
Globalization of economies Focus on customer satisfaction Time-based & price-based competition Lean management / Autonomous units Total quality management / TPM Agility/Reactivity Networked (extended/virtual) enterprises
F.B. Vernadat
Introduction Globalization: • Implies tighter relationships – Competitive enterprise networks – Strong partnerships
• Concerns industry as well as administrations/gov’ts – Industrial supply chains – Trans-national networks (e-Goverment Portals)
From loose relationships to close cooperation: – shared skills/competence, capabilities, knowledge/know-how
Networked interoperable enterprise systems F.B. Vernadat
Interoperable Enterprise Systems From highly fragmented environments…
J2EE SAP
Unix/Oracle Windows F.B. Vernadat
Interoperable Enterprise Systems To more interoperability to remove barriers
F.B. Vernadat
Interoperable Enterprise Systems Common business needs: 1. Need for co-operation and a decision-making framework Data managed by # domains (ADMIN, BUDG, HRM, PROD…) Intra-domain vs. Inter-domain interoperability
2. Need for joined-up business and administrative processes Partial workflows and manual procedures Non-integration of basic IT systems
3. Need for accurate and up-to-date information Data often locked inside separate information systems
4. Need for coherent information systems BP rely on various legacy systems with redundant info/data
5. Need for single or unified entry point and single sign-on to multiple applications (Corporate Portals) F.B. Vernadat
Interoperable Enterprise Systems Networked organizations: A network, the nodes of which are business entities (suppliers, sub-contractors, mfg plants, assembly plants, storage areas, distributors/resalers) and the arcs are material and info. flows 1. 2. 3.
Supply Chain Extended Enterprise Virtual Enterprise
F.B. Vernadat
supplier manufacturing
stock area final assembly
customer
Networked Organizations • Supply Chain
• Extended Enterprise
• Virtual Enterprise Ent. A
Ent. B F.B. Vernadat Ent. C
EE Contract
2nd tier
1st tier
Enterprise Integration and Interoperability Enterprise Integration (EI): deals with increasing interoperability among people, machines, and applications to enhance synergy within an enterprise (or a network of enterprises) to better achieve business objectives (or mission) (Vernadat, 1996) is the coordination of all elements including business, processes, people, and technology of the enterprise working together in order to achieve the optimal fulfillment of the mission of that enterprise as defined by enterprise management (Williams and Li, 1999) Has 1st organisational dimension and 2nd technological dimension Keys to EI = business process communication, co-operation and co-ordination F.B. Vernadat
Integration Levels CIM Integration
BUSINESS INTEGRATION Knowledge-Based Decision Support Business Control * Automated Business Process Monitoring Production and * Process Simulation *
APPLICATION INTEGRATION Portable Applications * Distributed Processing Common Services/ * Execution Environment Common (Shared) * Data Resources PHYSICAL SYSTEM INTEGRATION Inter System Communication/ * Network Configuration & Management Data Exchange Rules * and Conventions Physical Systems * Interconnection CIM Evolution 1970
F.B. Vernadat
1980
1990
(AMICE, 93) 2000
Integration Levels CIM/EI Integration levels
BUSINESS INTEGRATION Extended Enterprise/Virtual Organisation
Coordination
CIMOSA
CALS/GERAM Enterprise Portals
Organisation and human aspects / BP coordination
APPLICATION INTEGRATION Co-operation
BP/workflow engines/CSCW EDM/WCM EDI/EDIFACT STEP/PDES HTML/XML/XSLT SQL/OQL/ODMG KQML/KIF PIF WPDL/BPML UDDI Integration/Web Services Application servers
PHYSICAL SYSTEM INTEGRATION OSF/DCEOMG/CORBA Internet/WWW J2EE SOAP
Communication ISO-OSI
TCP/IP
ASI
ATM
Fast Ethernet
CIM/EI Evolution F.B. Vernadat
Interoperability • What it is? – Webster: “ability of a system to use the parts of another system” – In business: “ability of a business entity to use functionality or information provided by another business entity”
• Traditional answers to interoperability needs – Traditional EAI (Enterprise Application Integration) • RPC, CORBA, XML, custom integration logic, etc.
– Standardization of e-commerce frameworks and their components • EDIFACT, X12, ebXML, RosettaNet …; CORBA, XML, SOAP …
• The Web Services promise: – “Plug & Play” use of services delivered by anyone, anywhere, with any underlying technology
F.B. Vernadat
Interoperability issues • The scenario – An enterprise wants to use services of another enterprise, delivered electronically
• Many complex differences to resolve – – – – – – – – –
Message formats, transport protocols Data models (semantics) Representation of concepts (ontologies) Business processes (orchestration) Economic aspects Security and identification issues Legal aspects Human languages (multiligualism) Etc.
• Are Web Services up to the task? F.B. Vernadat
WS?
Technologies for interoperability
- Object-oriented approach - CORBA/DCE/appl. servers - Java/J2EE - XML - Internet/Enterprise Portals
Interfaced data silos F.B. Vernadat
Interoperable projects
Levels of an Interoperability Architecture
F.B. Vernadat
Enterprise Architectures Architecture foundational for managing modern enterprise and planning Enterprise Integration Enterprise Architecture (EA): organized collection of ingredients (tools, methodologies, modeling languages, models, etc.) necessary to architect or rearchitect whole or part of an enterprise
F.B. Vernadat
Why Enterprise Architectures?
• Which of these answers (A or B) would you state to be correct if you want a new house: • •
A) You give a construction company a description and ask them to build the house. B) You ask an architect to create a blueprint showing what the house will look like. You expect the construction company to realise the blueprint and you use the blueprint to validate this.
• If a construction company is building a house: •
•
A) They start building the house using your verbal or written description, maybe asking you some additional questions as they go along. B) They use an architect's blueprint to construct the house.
F.B. Vernadat
EA Definition • An Enterprise Architecture describes the relationships among the – Work the enterprise does – Information the enterprise uses and – Information technology that the enterprise needs
• An Enterprise Architecture: – Is derived from business requirements – Guides the organization’s information systems and technology infrastructure across the various component architectures – Is understood and supported by the senior management and the business F.B. Vernadat
EA Benefits • Clear picture of mission, strategies, business process map, and supporting technology across the enterprise • Establishes a change control process over business, IT, or other projects • Enables reuse, reduces duplication of effort, leverages economies of scale • Promotes information and knowledge sharing • Communicates standards and guidance
F.B. Vernadat
EA Components • An Enterprise Architecture contains … – Architectural Principles – Standards Profile and Technical Reference Models – Architectural Views: • Functional, Information, Organizational, Infrastructure
– Baseline and TargetViews – Gap Analysis and Migration Plan – Strategic Plans
• … and the capability to access and utilize the information F.B. Vernadat
EA – What its’s not … • Enterprise Architecture is not Computer Architecture – Enterprise Architecture is NOT: • A platform/wiring diagram • A list of product standards, or • A static, sophisticated drawing
– Printouts and manuals are nice BUT: • Provide virtually no management capabilities • No model driven “what if’s” • No ability to define and evaluate the relationships between the architecture elements • Zero analytical tools for measuring progress or evaluating risk for a given scenario F.B. Vernadat
EA – BGL example (Functional architecture – AS-IS) Sends Info
Security Administrator
Seeks Assistance
Receives Info
Client
Support
Content Manager Product Folder
eDocs
Incoming Legacy
Description Tariff …
Operator
Records Manager
F.B. Vernadat
End User
Electronic Archiving
eMail Printers
Campaign
Bulk Loading Imaging
Fax
Web
Optifax
Content Delivery
eMail
Bulk Loading System
eForm
Access
Web
Client Info
Paper Archiving
Fax Custom Application
eDocs
EA – BGL example (Conceptual architecture – TO-BE) Security
Support Fax Incoming
eForm
Specific Content Management Storage Mgt
Web eMail Printers
Document Repository
Fax
eMail
eDocs
F.B. Vernadat
Users
Basic Document Management
Interfaces
Web
Output Manager
Content Manager
Interfaces
Legacy
Input Manager
IT Framework
Electronic Paper Archiving Archiving
External Applications
eDocs
External Storage
Metis
F.B. Vernadat
Metis
F.B. Vernadat
CIMOSA: CIM Open System Architecture Instantiation of Building Blocks
EU AMICE Project: - Three modeling levels - Four modeling views - Three instantiation levels
Generation of Views
Organisation View Resource View
Information View Function View
Requirements Definition Model
Reference Architecture Generic Constructs
Partial Models
Design Specification Model Particular Model Implementation Description Model
F.B. Vernadat
Derivation of Models
CIMOSA Language CIMOSA Event-driven process-based language - Process/Operation/Agent relationship - Task/Capability-Competency/Agent relationship Event Process
Ev = (Eid, source, P-list, Predicate, Date) P = (Pid, aP, bP, dP, ES) dP = {WHEN (condition) DO action} Activity A = (Aid, EC, EF, EC, ER, SF, SC, SR, dA, ES) EC= set of capabilities/competencies Resource R = (Rid, EC, FO-list, components) Object View OV = (Ovid, O-list, Properties) Enterprise Object EO = (Oid, Isa, Part-of, Properties) Organisation unit UO = (UOid, tasks, responsibilities, authorities) Organisation cell EO = (Eoid, manager, responsibilities, authorities, components)
F.B. Vernadat
ARIS Architecture Organisation enterprise plant area planning levels
organisationnal chart
AND Entity Relationship Model (ERM)
F2
F4
F3
F5
F1
F6
F AND
F1
Process
F2 F3
F4
Hierarchy
Data F.B. Vernadat
Control
Function
GRAI-GIM Fun ctio n al mod el o f th e en terp rise
Conceptual
Reference mod els (CP IRM) Co ncep tual D ata Mod el (CDM) en tity
en tity
relationsh ip ca rdinality
Organizational
en tity
Org an ization Data Mod el (OD M) rec ord ty p e (ow n er) set ty pe
Physical
G RA I grid
Co ncep tual O peratio n al Mod el (COM) co ntraints
H o r izo n / P erio d A ctiv ity
S u p p o r ts
ac tivity G RA I ne ts
P h ys ical Data Mod el (P P M) Datab ase and co mp uter to o l su p po rts
Data
co ntraints ac tivity
Org an ization P roces s Org an ization al Mod el (OP M) Op eration al Mod el (OO M) E ven t E ven t syn chronizatio n
ac tivity
op eration m e cha nism s
rec ord ty p e (m e m be r)
F.B. Vernadat
Reference mod els (CP DRM) Co ncep tual P ro cess Mod el (CP M) F u n ctio n s
E ven t
P h ys ical P ro ces s Mod el (P P M) Software an d co mp uter to o l su p po rts
P ro ces s
ac tivity m e cha nism s
P h ys ical Op eration al Mod el (P OM) Mach in es an d p h ys ical o rganizatio n o f p rod u ctio n sy stem Op eration al
PERA (Purdue Enterprise Ref. Architecture) An Enterprise Consists of 3 Major Concepts Enterprise Definition
Enterprise Physical Syst. & Facilities
People
Enterprise Logical Systems
Enterprise Dissolution F.B. Vernadat
The PERA Model Combines these 3 Concepts in a Systematic "Phased" Approach 1
Feasibility Study
2 3 5 7 9
F.B. Vernadat
4
Policies Req'ments Functions Flow Diags
Enterprise Definition
6 8
Conceptual Engineering
10
12
11
13
Prelim. Engineering
14
15
16
Detailed Engineering
17
18
19
Construction
20
21
22
Operations & Maintenance
23
24
25
Decomissioning
Facility & Enterprise Phys. Syst.
Human Roles
Enterprise Logical Systems
Enterprise Dissolution
PERA Designation of Enterprise Business Entity
IDENTIFICATION
Mission, Vision, and Values Business competitive environment information
Government laws and regulations
CONCEPT PHASE
Policies Information on requirements or other processes and plants
Further details of governement laws and regulatory requirements Requirements
Generic task lists, competitive information
Function and control task list from same or similar products Tasks, Functions, Modules
F.B. Vernadat
DEFINITION PHASE
IFAC/IFIP Task Force: GERAM Generic Partial
Views {
{
{
GERA
Particular
}
Subdivision according to genericity
Instantiation Identification
Customer service
Concept
Management and control
Requirements
}
Subdivision according to purpose of activity
}
Subdivision according to physical manifestation
}
Subdivision according to model content
}
Subdivision according to means of implementation
Software Hardware
Preliminary design Design
Resource Organisation Information Function
Detailed design Implementation Operation Decommission
Life-cycle phases
F.B. Vernadat
Machine Human Reference Architecture
Particular Architecture
Zachman Framework What
Principles
Business Layer
Functional Layer
Application Layer
Technology Layer
F.B. Vernadat
How
Where
Who
When
Why
Zachman Framework Principles What
How
Where
Who
When
Why
Scope = Planner’s view
Contextual
Enterprise Model = Owner’s view
Conceptual
System Model = Designer’s view
Logical
Technology Model = Builder’s view
Physical
Detailed representation = Subcontractor’s view
As Built
Functioning Enterprise = User's view
Functioning
F.B. Vernadat
Zachman Framework (Interpretation)
Row 1 – Scope = Planner’s view
External Requirements and Drivers
IIG activity layer: business domains
As Built, Deployment
Row 2 – Enterprise Model = Owner Business Process Models
Row 6 – Functioning Enterprise = User’s view Functioning Enterprise, Evaluation
IIG business process layer: processes
Row 5 – Detailed representation = subcontractor’s view
Row 3 – System Model = Designer Logical Models, Requirements Definition
IIG IT Systems layer: applications
What
How
Where
Who
When
Why
1
Scope = Planner’s view
Contextual
2
Enterprise Model = Owner’s view
Conceptual
Physical Models, Solution Definition and Development
3
System Model = Designer’s view
Logical
IIG infrastructure layer: building blocks
4
Technology Model = Builder’s view
Physical
5
Detailed representation = Subcontractor’s view
As Built
6
Functioning Enterprise = User's view
Functioning
Row 4 – Technology Model = Builder’s view
F.B. Vernadat
Zachman Framework (Rules)
Basic Model = Entities and Relationships
Rule 1 Columns have no order
Relationship Entity
Entity
Rule 2 Each column has a simple, basic model What
Rule 3 Basic model of each column is unique
Rule 4 Each row represents a distinct view
Rule 5 Each cell is unique
Rule 6 Combining the cells in one row forms a complete description from that view F.B. Vernadat
How
Where
Who
When
Why
Scope Planner’s view
Contextual
Enterprise Model Owner’s view
Conceptual
System Model Designer’s view
Logical
Technology Model Builder’s view
Physical
Detailed representation Subcontractor’s view
As Built
Functioning Enterprise User's view
Functioning
Zachman Framework at EC
F.B. Vernadat
Zachman Framework at EC Business-to-IT governance framework (B2I)
Business activities
ABM Activities
Processes, Business functions procedures, business rules
Applications
IT Systems
Infrastructure Hub
F.B. Vernadat
Building blocks
Zachman Framework at EC • Alignment of an element from a stakeholder's perspective to another stakeholder perspective, serving thus as a communication tool for all stakeholders involved • Blueprint describing the current situation (AS-IS) and the future one (TO-BE)
Ideal tool for planning an IT strategy that has business alignment incorporated from the start and responds to the political and administrative objectives
F.B. Vernadat
Service-Oriented Architectures (Technology layer) • Service definition: A function that is well-defined, self-contained, and does not depend on the context or state of another service Generally implemented as a coarse grained, discoverable software entity (that exists as a single instance and interacts with applications and other services through a loosely coupled message based communication model A simple service SessionFacade WSDL
Any language: C, PL/SQL… Java J2EE
Interface TransferObject XML schema
F.B. Vernadat
Service-Oriented Architectures (Technology layer) • To offer a service, you need to: – Describe your service (well-defined, coarse grain) in a technology independent way (WSDL) – Register the service (UDDI) – Minimize the dependencies on other services (selfcontained)
• To use a service, you need to: – Discover the right service (UDDI) – Communicate with it in a loosely coupled manner, minimizing your dependencies (SOAP/XML)
F.B. Vernadat
Service-Oriented Architectures (Technology layer) Intranet Client
Internet Client
Portal portlet
ESB Enterprise Service Bus Composite Service
Service 1 Service layer
App. 3
App. 2
App. 1
Service 2
Business Applications
Data
F.B. Vernadat
Service 3
Stores
Standards for EI • • • • •
OMG (Object Management Group) CEN (Comité Européen de Normalisation) TC 310 ISO (International Standards Organization) TC 184 IEC (International Electronics Committee) OAG (Open Applications Group)
F.B. Vernadat
Standards for Enterprise Modeling • ENV 40003 (1990) – EN ISO 19439 (2004) Framework for Enterprise Modeling
• ISO 14258 (1998) Concepts and Rules for Enterprise Models
• ISO 15704 (1998) Requirements for Enterprise Architectures and Methodologies
• ISO/IEC 15288 (1999) Life-Cycle Management System/Life Cycle Processes
F.B. Vernadat
Standards for Ent. Modeling Languages • ENV 12204 (1995) – EN ISO 19440 (2004) Constructs for Enterprise Modeling
• ISO 18629 (2001) Process Specification Language (PSL)
• ISO 10303/11 (1992) STEP/EXPRESS
• ISO/IEC 15414 (2000) Open Distributing Processing (ODP) – Enterprise Language
• ISO/IEC 15909 (1997) High Level Petri Nets
F.B. Vernadat
Enterprise Modeling CEN ENV 12204 between
ENTERPRISE OBJECT
state of view of
RELATION
OBJECT STATE
can play the role of
type of BUSINESS PROCESS
OBJECT VIEW involved in ORDER RESOURCE
used in
SEQUENCING RELATIONSHIP
employs combined by
PRODUCT ORGANISATION UNIT
provides CAPABILITY SET
F.B. Vernadat
ENTERPRISE ACTIVITY
required by
used in
EVENT
Standards for Software Interoperability • ENV 13350 (1995) Enterprise Model Execution and Integration Services (EMEIS)
• ISO 15414 (2000) Open Distributed Processing (ODP) – Reference Model
• TOGAF (Technical Open Group 2000) Technical Reference Model
• OMA (OMG, 2002) Open Management Architecture
• OAGIS (OAG, 2001) Open Applications Group Integration Specification
F.B. Vernadat
OMG-MDA
F.B. Vernadat
Metrics for EI • Objectives Measure and assess achievement of strategic objectives and alignment of business strategy with enterprise operations
• Performance indicators for EI/NE – Reactivity: measure of the speed and relevance of implementing change in reaction to a perturbation – Flexibility: ability to quickly switch from a situation to another – Robustness: ability of a system to absorb perturbations No more cost-oriented PIs but multi-criteria PIs based on measures of complex nature (numeric, symbolic, fuzzy) F.B. Vernadat
Performance evaluation Objectives
• Industrial performance – Effectiveness – Efficiency – Relevance
Relevance
Ind. Perf.
Resources
Effectiveness
Efficiency
• Performance indicators
Results
– PI= 3-tuple (objective, variable, measure) Objectives
P : OxM E ( o , m ) P( o , m ) P
Performance Indicators
• Performance measurement systems • Performance aggregation F.B. Vernadat
Decision variables
PIs in the control structure
Htactical Ptactical
Physical System/process
Hoperationa Poperational
F.B. Vernadat
DC
DC
TdB
DC
DC
TdB
DC
OU
OU
Inputs
OU
Feedback loop
Control system
Hstrategic Pstrategic DC
OU OU
End Product
OU UO : Operational unit TdB : Tableau de Bord DC : Decision center
Physical flow Action plan Feedback information
Performance aggregation • Information aggregation (Wald, 98): Phenomenon
Extraction
Representation
Combination
Interpretation
Decision making
• Physical measure aggregation:
Physical decomposition
F.B. Vernadat
Extraction of the analytic combination function
Extraction of the elementary physical measures and then combination of them
Interpretation of the aggregated physical measure
Decision making
Aggregation operator • 2-additive Choquet Integral (instead of weighted sum): n
CI g (P1, P2,...,Pn)
with
Pi(vi 1 Iij min(Pi, Pj )Iij max(Pi,Pj ) Iij 2 j i I ij 0 I ij 0 i 1
n 1 (vi I ij ) 0 and v 1 (Shapley parameters) 2 i j i 1 i
I ij
in [-1, 1]
F.B. Vernadat
(Berrah, Mauris, Vernadat, 2004)
Performance expression aggregation
Extraction of the weights and interactions Decisional decomposition
Commensurability
Combination of the elementary performances by 2-additive Choquet integral
Interpretation of the aggregated performance
Extraction of the elementary performances
Increase margins
F.B. Vernadat
= Agg
Control tardiness (w1=0.4) Control quality (w2=0.2) Reduce inventory levels (w3=0.2) Increase productivity (w4=0.2)
Decision making
CONCLUSION Interoperable enterprise systems in highly skilled, competitive, and reactive enterprise networks A holistic approach Alignment of IT infrastructure with business strategy: 1. Enterprise Architecture (mission, vision, values) set up 2. AS-IS, TO-BE and Gap analyses & migration path 3. Interoperable business process implementation (as well as support apps and IS) 4. Existing and emerging IT standards to be considered 5. Performance metrics definition
F.B. Vernadat
Thank you for your attention
[email protected]
F.B. Vernadat
