IDEAS roadmap for eBusiness Interoperability - Google Sites

eGovernment Interoperability Workshop Brussels, 18 March 2003

IDEAS roadmap for eBusiness Interoperability

Interoperability Development for Enterprise Application and Software – Roadmaps IST-2001-37368 01.06.2002 – 31.05.2003 http://www.ideas-roadmap.net/ Arian Zwegers Baan [email protected]

IDEAS

eGovernment Interoperability Workshop

18 March 2003

1

Overview Definitions Rationale IDEAS Some results Interoperability Framework State-of-the-art User requirements Vision Roadmap

Conclusions

IDEAS


18 March 2003

2

Definitions “The ability of a system (as a weapons system) to use the parts or equipment of another system” (source: Merriam Webster’s) “The ability of a system or a product to work with other systems or products without special effort on the part of the customer” (source: whatis.com) A product is compatible with a standard but interoperable with other products that meet the same standard

IDEAS


18 March 2003

3

Rationale More internal sources of information Quality Data Product Database Usage Timing Cost Weight Investment UPG/VSC Material Specs Torque

SST Database

Quality Planning

Vehicle Input Data & Model Output for

CAE

Impact Analysis Perf/Fuel Economy/Emissions Ride & Handling NVH - FEA Aero/Climate Control Electrical/Electronics Ergonomics

DFMA DFMEA's PFMEA's DVP&R's AVA/GD&T QED,SPC Error Proofing

PAP Tools

Model Assemblies

Warranty (WIS) Plant Audits (VQA) Customer Survey (OTS) Open Issue Summary BITS DDRC

Competitive Teardown Cost Weight Features Process

EBOM/CN P & S System BOM Usage ...

Sourcing I.D. Supplier Cost Transportation Materials Labor (Fab & Ass'y) Quality Rating

"Engineer's Desktop" CATIA CDM Models MDM Models GD&T Welding CMM N/C Cutter Paths

Manufacturing (Legacy)

Serviceability Fastener/Torque Packaging Data KBS Tools Features

Tooling Cost –Dies/Molds –Assembly Tools –Guauges Facility Cost PP&L Cost Process (OGS) "The Wall" Process Simulation (Auto XXX)

Technical Computer Center CDV

AMPS (Standard)

DMA

Assembly Line Process Descriptions

Books of Knowledge Intranet Netscape Browser Mail for Unix

Electronic Mail Notes Mail (STANDARD)

Body Interior Chassis Electrical P/T Vehicle Development Sci Labs

Vehicle Test Data D.D.E. STF P.G. Lease/PE Fleet Rental Car Fleet Duty Cycle Info

MEDDS (Standard) Vehicle Program Investment

(source: Gus Olling, DaimlerChrysler) IDEAS


18 March 2003

4

Rationale More interactions with external parties

(source: Gartner) IDEAS


18 March 2003

5

Rationale Integration throughout the decades Paradigm: ’70s

Islands of Automation a. Legacy applications

2. ’80s

Integrated ERP applications (ERP-I) a. Monolithic b. Passive & inward looking c. Proprietary tools

’90s 3.

Statically integrated applications a. Tight coupling (synchronous communication) b. Request-reply based (RPC) c. Point-to-point d. Shared tools platform

4. ’00s

ERP Tools

EAI Tools

Dynamically integrated applications (ERP-IIa) a. Loosely coupled (a-synchronous) b. Event driven c. Peer-to-peer (common message definition)

’05s 5.

Business process-driven integration (ERP-IIb) a. Dynamic routing (message content-based) b. Business Process-aware applications & integrations c. Process control component (initiation, control & monitoring

IDEAS


Process Control Component

18 March 2003

6

Rationale Enterprise priorities 61%

Integrating systems and processes External customer service / relationship management

49%

39%

Enabling / enhancing e-commerce Knowledge management / leveraging intellectual assets

35%

33%

Implementating data security and privacy measures Automating / optimizing the supply chain

32%

26%

Implementing new technologies, such as wireless 21%

Extending systems globally

Other

8%

(Source: CIO Magazine, Sept 2002) IDEAS


18 March 2003

7

Rationale Increasing integration budgets

Application integration license revenue

System implementation budget Misc. 20%

B$

Integration 40%

Hardware 10% Imp. Services 20%

Software 10%

(source: the Yankee Group 2001)

IDEAS


18 March 2003

8

Rationale Standardisation vs individualisation Collaborating enterprises want local solutions that better suit their unique local conditions. Every enterprise insists on: preserving its rights to local choices and solutions protecting its proprietary information, which includes part of its information that it will not share, and provision of special access rights to a part of its information only to those other enterprises that either it can trust or it is obliged to by contract

Tension between needs for cooperation among organisations (standardisation) and the suitability of proprietary solutions that can more readily meet local conditions (individualisation)

IDEAS


18 March 2003

9

Rationale The result Purchased Packages

Legacy Applications

E-marketplaces

HTTP/ XML Message queue FTP Download file

Autonomous Divisions

Download file Screen scrape

CICS gateway Gateway

Transaction Sockets file

RPC

Transaction file

Screen scrape ORB

E-mail

Applications in Trading Partners

Message queue

Transaction file

SMTP

CICS gateway Browser

End-User Development

Message

Download file

Applications From Mergers and Acquisitions (source: Gartner) IDEAS

Transaction file


APPC

Message queue

XML/ HTTP

Outsourced and ASP Applications

18 March 2003

10

IDEAS In a nutshell IDEAS is a strategic RTD roadmap project Impacts on interoperability of enterprise applications. It will suggest and prepare large scale Actions in FP6 actions for the forthcoming European (European 6 Framework Program for R&D) 6th Framework Programme (FP6). It aims at achieving major impacts Management tools in sectors that use enterprise Roadmap applications and software. State of th

the art

Vision

Challenges

Goals

IDEAS


18 March 2003

11

IDEAS Expected results State of the art reports, User requirements, Visions including industrial business scenarios and identification of challenges and risks, Definition of roadmaps based on gap analyses, An implementation plan: IP Framework, Terminology and Taxonomy, An intensive dissemination programme to collect information and to create consensus

IDEAS


18 March 2003

12

IDEAS Focus Ontology •

Models

Enterprise Modelling

HIGH LEVEL ABSTRACTION OF MAIN DECISION FLOWS BET. THE PARTNERS, THE NETWORK AND THE PROJECT ENTERPRISE

PARTNERS H/P

External Info Manage Products market situation opportunity 1.2 identification risk response development scope adjustment

To Plan / Coordinate realignment of mission ,objectives

Orders

client request handling procurement planning

1.6

1.5

budget allocation

individual budget planning

1.9

Manage Products strategic product decisions scope planning

proactive resource deployment

strategic direction planning

1.4

External Info. industry data customer data

master plan for network operations

2..4

2.6

2.8

Manage

plan process 3.2 3.3

control quality, control incoming and outgoing goods and services 3.4

assignment of authorities development of IT tools

2.9.1

To Plan / Coordinate

plan activities components procurement activity duration estimating quality planning

combined network resource capability management budget allocation

2.7

Manage Products

Manage Resources overall network resource planning 2..3

2..1

project plan development (creation of project enterprise) project plan evaluation and adjustments in budget

orders

Enterprise objectives

Level Strategic

3.1

Customer request

Level Strategic

network operational data

Tactical

Experience

Operate Operate enterprise A1

Network initialisation Networking strategy VE ICT modules

Operate Operate enterprise enterprise network network

Shared business info

Resources

workload

payments & balancing team devt. -day to day control of projectl

Internal Info Available network IT tools/processes network project plan financial records operational data

A2

Network mgt tools

Shared project info

Level Strategic Tactical

VE experience Product LC experience Inter-enterprise coordination A3

VE ICT system VE mgt tools

Operate Product Product collaboration

Network partners OKP enterprise

VE initialisation VE procedures

Operate Virtual Virtual Enterprise Enterprise

Shared product info

Production resources

Operational

Models

Networking experience

Tactical

2.9.2

develop project resource needs (mgt.,info., human, tools) project budgeting distr.

schedule process monitor progress

Internal Info network ref.models network core competencies resource info frm network partners

Standards

VE membership requirements

ICT tools

Tactical Operational

1.1

2..5

client request details and information

financial records hrm records

staff allocation

1.8

To Plan / Coordinate

2..2

VIRTUAL ENTERPRISE H/P External Info.

Internal Info feasibility results

1.3

risk control procurement of add’l.tools 1.7

NETWORK H/P

Manage resources capability assessment & adjustment

A4

Product / service Order

VE partners

Enterprise mgt tools

3.5

Architecture

CAD

CIM Database GT CAM

IDEAS


18 March 2003

13

IDEAS Topics & scope Human/social Human/social aspects aspects Collaborative Collaborative Business Business

e/m-Business e/m-Business

Workflow Workflow mgt mgt

ICT ICT standards standards Architecture Architecture

Open Open systems systems

Configurable Configurable interfaces interfaces

Semantic Semantic Web Web

Trust Trust

Interoperability Core Plug-and-do-business Interoperability Plug-and-do-business Topics for topics potential Enterprise Enterprise applications applications collaboration with other Related Ontologies Intelligent Intelligent Infrastructures Infrastructures Ontologies topics to be initiatives Security Security adressed Enterprise Enterprise modelling modelling mainly by other Product Product development development Platforms Business Platforms Business Models Models initiatives Related Knowledge Knowledge mgt mgt topics that Scalability are out of Scalability the scope Sector-specific Sector-specific issues issues Legal Legal issues issues

IDEAS


18 March 2003

14

IDEAS Consortium

BAAN BAAN

ICFOCUS FOCUS Université IC Université Bordeaux I Bordeaux I SAP AIDIMA AIDIMA

GRAISOFT GRAISOFT

Natexis

IDEAS IDEAS Core Core Members Members

EADS-CCR EADS-CCR

LEKS FORMULA

INTRACOM CEN/ISSS CEN-ISS

COMPUTAS COMPUTAS ITIN FZI Versailles

CR-FIAT CR-FIAT UNINOVA

TXT

ANTARA

PRIMEUR

SINTEF

Free TIGA Univ. Amsterdam Technologie

IDEAS Network

IDEAS


18 March 2003

15

Overview Definitions Rationale IDEAS Some results Interoperability Framework State of the Art User requirements Vision Roadmap

Conclusions

IDEAS


18 March 2003

16

Interoperability Framework General objectives to determine the universe of discourse (“things that matter”) to identify aspects/levels/dimensions of interoperability to act as a project management tool (basis for WBS) to act as a communication tool (common view) to give a high-level overview independent of actual content

IDEAS-related objectives to identify research themes to focus on specific interoperability aspects/levels to structure, scope, and rationalise the work (esp. aligning WP1-3) to get a common view on terminology, positioning, focus, …

IDEAS


18 March 2003

17

Interoperability Framework Simplified

Business

Applications

Semantics

Knowledge

Data Communication

IDEAS


18 March 2003

18

Interoperability Framework Extended Framework 1st Level

Framework 2nd Level

ONTOLOGY Semantics

E N T E R P R I S E A R C H I T E C T U R E

QUALITY ATTRIBUTES Security

Scalability

Evolution

Decisional Model Business Model Business Processes Knowledge Organisation Roles Skills Competencies Knowledge Assets Application Solution Management Workplace Interaction Application Logic Process Logic Product Data Data Process Data Knowledge Data Commerce Data

Business

QUALITY ATTRIBUTES Performance

Availability

Portability

Communic. IDEAS


18 March 2003

19

State of the Art Enterprise Modelling “The art of externalising enterprise knowledge” To support the analysis and design of (parts of) an enterprise To simulate the behaviour of an enterprise To control, coordinate and monitor some parts of the enterprise

EM and interoperability EM content interoperability • Interoperability among enterprise modelling languages

EM-based application interoperability • Interoperability among applications supported by EM • Analysis of the interoperability of a set of applications and processes towards each other

Main source UEML project, www.ueml.org

IDEAS


18 March 2003

20

State of the Art Enterprise Modelling Enterprise Modelling Languages Many but overlapping Tendency to combine languages

Enterprise Modelling Software Environments Tendency to support several languages and views No interoperability between tools Few tools allow definition of new languages

Standards related to EM Most standards are not widely used due to lack of convergence

IDEAS


18 March 2003

21

State of the Art Ontology “Formal, explicit specification of a shared conceptualisation” Ontology and interoperability Ontology content interoperability • Interoperability among ontologies

Ontology-based application system interoperability • Interoperability among applications supported by ontologies

Main source Ontoweb project, www.ontoweb.org

IDEAS


18 March 2003

22

State of the Art Ontology Ontology Representation Languages Most current languages are adequate to model static aspects of reality Functions and processes are much more difficult to be ontologically defined Need to enhance ontology languages in the direction of semantic adequacy

Ontology Tools Existing ontology tools show similar limitations Commercial offering is very limited

Standards IEEE: upper ontology W3C: OWL

IDEAS


18 March 2003

23

State of the Art Architectures & Platforms A broad, diverse area Standards and standardization projects eBusiness Frameworks Web Services Development standards and environments Research efforts towards intelligent infrastructures

Main source CEN/ISSS, www.cenorm.be/isss

IDEAS


18 March 2003

24

State of the Art Architectures & Platforms General conclusions Many Architectures and Platforms exist and even more are emerging Lack of interoperability between them Same architecture / platform can lead to divergent implementations

IDEAS


18 March 2003

25

User Requirements Generalised in a number of classes ‘functional requirements’ • e.g. GR5 Application layer shall be decoupled from technical layer

A&P requirements • e.g. GR10 The user shall be able to interact with the applications from different devices in different situations • e.g. GR17 Development and/or use of generic standards for process data management is required

EM requirements • e.g. GR21 EM tools shall enable the enterprise to manage EISs and their evolution

ON requirements • e.g. GR29-32 Semantic concepts and relationships defined by the calling function shall be recognised and managed by the called functions, in order to properly allow interoperability among them

Quality attribute related requirements • e.g. GR39 Scalability: A large number of users should be served

IDEAS


18 March 2003

26

Vision Based on industrial goals and challenges “Organisations will be able to seamlessly interoperate with others (personal statement) (plug and do-business)” Results Execution of intra- and inter-enterprise business processes New ways of working and collaborating Seamless integration of software architectures, components and services, in a dynamic, unpredictable environment

Business benefits Reduced time to market for product or service delivery Reduced risks and costs of systems development, delivery, integration and management

IDEAS


18 March 2003

27

Roadmap Purpose Roadmap: Identification of elements, issues, and paths towards a defined goal

Purpose: coordination prioritization sequencing, giving sense of timeline persuasion, marketing identification of the context/relationships identification of gaps, risks, factors speeding up/slowing down wanted/unwanted development

IDEAS


18 March 2003

28

Roadmap Process

State of the Art

User Requirements

Have

Visions

Want

Compare & Contrast

Roadmapping

IDEAS


18 March 2003

29

Roadmap Gap Analysis Process of identifying delta between existing situation future or desired situation

Research Gap Fundamental absence of knowledge

Technology Gap Absence of technology or the integration of technologies

Standards Gap Insufficient specification or absence of • • • • •

a commonly agreed format of data, or a commonly agreed protocol or process in which to exchange data implementation guidelines best practices Technical specifications

De-jure standards, de-facto standards Harmonisation of standards themselves IDEAS


18 March 2003

30

Roadmap Identified gaps EM • • • • • • • •

Cross-Organisational Workflow Business Processes (any process) Business Models and Modelling Knowledge Assets – models, templates, and language services Model-Driven Enterprise Software Generation Visually Modelled Enterprise Knowledge Architecture EM Interoperability Approach Business Decisional Model (BDM) - Governance

• • • • • • • • • •

Networked Organizational structures and roles Competencies and Skills (methods for POPS) Customer Solutions Delivery and Support Continuous Business Solutions Management Intelligent Infrastructures Model-generated Workplaces and Environments Enhanced ICT Architectures Identification of objects Service description Registries

A&P

IDEAS


18 March 2003

31

Roadmap Gap: cross-organisational workflows Is-situation Desired Situation

Problem Space Existing Research Existing Technology Existing Standards Research Gap Technology Gap

Standard Gap

IDEAS

Business Processes operate efficiently inside the boundaries of individual organizations Business Processes operate across company boundaries and therefore facilitate, coordinate, and automate the exchange of business data Workflows that operate across company boundaries without exposing company-sensitive process information. ~10 year research in workflow management system, workflow models and architectures Workflow Management systems that run efficiently company-internal workflows Workflow Management Coalition (WfMC), OMG, ebXML, BPML, WSCI, WSFL Cross-organisational workflow models. Ontologies to interpret different workflow standards. Workflow Systems that implement cross-organisational workflow models and support their execution and eventcorrelation A single workflow standard, instead of the several available ones, or a proposal how the existing standards interact. eGovernment Interoperability Workshop

18 March 2003

32

Roadmap Gap: business processes (any) Is-situation Desired Situation Problem Space

Existing Research Existing Technology Existing Standards Research Gap

Technology Gap

Standard Gap

IDEAS

Business process descriptions are abstract, static, and detached from the execution platform. Richer and active models that reflect what is performed, and can be supported by an intelligent infrastructure. Process and Task Modelling (PTM), Work Management (WM), and Work Execution Monitoring (WEM) methodology and visual languages. Some 300 tools offer proprietary template based modelling of one or more aspects of logical process description. Some de facto standards are emerging: BPML, BPEL4WS and PSL Defining core Visual Languages, and services as editable PTM modelled tasks, supported by Intelligent Infrastructures. Services to visually declare tasks, to categorise and store tasks and the processes they are included in, supported by a Process and task repository. The PTM, WM and WEM methodologies are all candidates for standardisation. eGovernment Interoperability Workshop

18 March 2003

33

Roadmap Gap: EM interoperability Is-situation Desired Situation Problem Space Existing Research Existing Technology

Existing Standards

Research Gap Technology Gap Standard Gap

IDEAS

No interoperability between EM models Two different EM models can be exchanged independent of used formalism (modelling language) and tool Interoperability between EM models UEML, TOVE, PSL, BPML, MDA Limited model translation tools such as XMI /MOF, STEP EXPRESS X/SDAI, BNF/Compilers Non interoperable EM software tools ISO/EN 19400 constructs for EM, ODP Enterprise Language, ISO/EN 19439 framework for EM, ISO 10303 Part 41 Enterprise Modelling ontology; EM mappings; EM methodologies Tools and services for translating models; configurable interfaces for EM software Harmonisation of terms and concepts of existing and future standards; interface standards for EM software interoperation


18 March 2003

34

Roadmap Gap: enhanced ICT architectures Is-situation Desired Situation Problem Space Existing Research

Existing Technology Existing Standards Research Gap

Technology Gap Standard Gap

IDEAS

Web services as software and tasks depend on repository services for persistency, security and availability More powerful scalable web, application and database servers, and additional adaptation and extension services IST architectures, servers and services as adaptable work process tasks Work is ongoing to develop standardised ICT architectures, but with manual mappings between generic models and specific models. SAP NetWeaver, IBM WebSphere, Microsoft BizTalk WSCI, BPEL4WS, BPML, SOAP, WSDL Understand the impacts and contributions from the EKA to ICT architectures, and avoid manual mappings and transformations of disjoint meta-models Integrating the portals, process engines, modelling and application execution architectures and platforms Standard tasks and repository services for model interpretation, adaptation and transformation


18 March 2003

35

Roadmap Gap: service description Is-situation Desired Situation Problem Space Existing Research Existing Technology Existing Standards Research Gap Technology Gap Standard Gap

IDEAS

Common way of describing services Catalogue exposing details about supplier DAML-S Web Services WSDL, BPEL4WS, WSCI, BPML, BPQL Persistent Service / Transient Service


18 March 2003

36

Conclusions eBusiness interoperability is a relevant problem and top priority for industry Interoperability is most relevant on business process level and application level (both semantic and syntactic) IDEAS will identify key research challenges in interoperability of enterprise applications Enterprise modelling, Architectures & Platforms, and Ontology are three domains that address interoperability problems Current “solutions” address limited part of the problem Current “solutions” lack sufficient supporters which leads to defragmentation Addressing interoperability requires the support of a large community Much to do ahead of us... IDEAS


18 March 2003

37

Thank you! For more information: Please visit http://www.ideas-roadmap.net/ Check the web site for public meetings Dissemination event in May/June Concurrent Engineering conference CE2003

IDEAS


18 March 2003

38