EIC and OAGi Addressing the Challenges of Cross- Industry Interoperability.
-
Upload
buck-miles -
Category
Documents
-
view
215 -
download
0
Transcript of EIC and OAGi Addressing the Challenges of Cross- Industry Interoperability.
EIC and OAGi
Addressing the Challenges of Cross-Industry Interoperability
eic Enterprise Interoperability Centre / 2
Agenda
EIC and OAGi
Introduction to EIC
OAGi and EIC – a win win scenario
Share experiences: Business profiles
Outlook EIC testbed activities
Future collaboration
eic Enterprise Interoperability Centre / 3
Interoperability is complex
LogisticsLogisticsProviderProviderLogisticsLogisticsProviderProvider
DistributorDistributorDistributorDistributor
Sub-AssemblySub-AssemblyManufacturerManufacturerSub-AssemblySub-AssemblyManufacturerManufacturer
ASICASICManufacturerManufacturer
ASICASICManufacturerManufacturer
Indirect Indirect SupplierSupplierIndirect Indirect SupplierSupplier
Technology Technology ResellerReseller
Technology Technology ResellerReseller
ContractContractManufacturerManufacturer
ContractContractManufacturerManufacturer
Chemical Chemical SupplierSupplierChemical Chemical SupplierSupplier
System OEMSystem OEMSystem OEMSystem OEM
Retail
Electronics Value ChainService
Provider
FoundryAssembly
& TestBanking
System Design House
Inter-company processes include those that exist between multiple trading partner tiers, required to create a competitive supply chain
CIDX
RosettaNet
SWIFT
Aerospace
EDIFACT
Spec2000
Automotive
OAGi
IPC
RosettaNet
ISA-95
EDI
WS-I
Paper
Fax
EmailPortal
Portal
eic Enterprise Interoperability Centre / 4
Interoperability Trends and Challenges
Competition of value chains (instead of companies) and increasing process
integration within value chains
Business partners use different process and product models Increase in the number and complexity of electronic business relationships
Lack of commonly accepted inter-company processes missing process standards - public processes are vague or missing altogether
Low penetration of existing standards Lack of m:n connectivity Time and effort for setting up electronic collaboration with a larger number of partners inconsistent implementation of standards
Dominance of human-human interface (phone, fax, e-mail) or human-machine-interface
(portals) in B2B relationships Bilateral agreements on electronic collaboration prevail
eic Enterprise Interoperability Centre / 5
Collaboration Challenges in the Future
eic Enterprise Interoperability Centre / 6
Framing the Problem
Sta
ndar
d
Custom Standard
Cus
tom
Mes
sag
e
Business Process
Magic Quadrant
Point-to-point
Industry Standard
1. Vertical standards organizations only move companies so far along this line
3. The proliferation of vertical standards has made even this movement difficult
Within and across industries2. Other companies must follow the same path for this to work
• The reference model aligns the critical factors of integration on two axis – messages (semantics) and business processes
• To simultaneously address cost and complexity, both messages and processes must be standardized
The format of the message is standardized by Industry standards organizations
Legacy installations of custom work processes and message structures
Aligned business processes, standardized messages and connectivity automation
Vertical standards
eic Enterprise Interoperability Centre / 7
Standards and the EIC
Sta
ndar
d
Custom Standard
Cus
tom
Mes
sag
e
Business Process
Magic Quadrant
Point-to-point
Industry Standard
The EIC defines a standardized business process and also selects the best vertical industry standards by defining a profile
Standards Reference Model
Within and across industries
Vertical standards
eic Enterprise Interoperability Centre / 8
Objective of the EIC
The EIC defines and applies integration methodology and tools leveraging existing standards where possible to define common public business processes for achieving interoperability of networked organizations across multiple industries.
The EIC approach Addresses the business and technical aspects of a common public process
Leverages existing technology, applications, research and standards
Defines architectures, methodologies, guidelines, best practices, semantics and interfaces
Validates an Interoperability Profile by building prototype implementations of real-world business scenarios defined by precise requirements
Delivers tools, conformance testing, analysis, training and other services to facilitate broad adoption in the community
eic Enterprise Interoperability Centre / 9
Deliverables
Interoperability Profiles A common definition of a public process that is consensus-driven An executable business process with defined interfaces A concise definition of required business semantics Guidelines, conventions and best practices for using the interoperability profile in ways
that ensure low-friction integration across multiple networks
Reference implementations Demonstrate profile-based interoperability in a production implementation Use cases and usage scenarios based on customer requirements Sample code and applications built in multiple environments
Methodology, Test tools and supporting materials Tools that test profile implementations for conformance with the profiles Supporting documentation and white papers
eic Enterprise Interoperability Centre / 10
Agenda
EIC and OAGi
Introduction to EIC
OAGi and EIC – a win win scenario
Share experiences: Business profiles
Outlook EIC testbed activities
Future collaboration
eic Enterprise Interoperability Centre / 11
Process Abstraction Concept – Carrier-Shipper Scenario
SalesOrder
Rate&Service
SelectionLabel
Generation
Delivery PickingPrivateProcess
CarrierViewProcess
Packing ShipmentAfter Sales
Track &Trace
WebServices
WebServices
SalesOrder
PackingViewProcess
Shipment
SalesOrder
Rate&Service
SelectionPacking Label
GenerationCross-org.BP
Track &TraceShipment
Shipper
eic Enterprise Interoperability Centre / 12
Value Proposition: End Users
Without standards, each information system would require point-to-point integration which requires a significant investment in time and capital
Reduce complexity Define a common business process with broad acceptance in an industry or across industries
Select the best message standard necessary to support the business process from the hundreds of standards specifications
Reduce total cost of ownership Leverage the analysis and design efforts embodied in the EIC deliverables
Broad adoption allows for the work to be reused in the next integration effort
Increase Flexibility Faster configuration of new partners and change to business processes with better, faster and
more complete information flow
eic Enterprise Interoperability Centre / 13
Business Forum Community Processes
ValidationAnalysisScoping
- Identify pain points and requirements
- Prioritize requirements and select target scenario
Identify As – Is Interoperability Situation
- Identify To-Be Scenario-Define solution to resolve interoperabilitychallenges
- Create a reference implementation of the Interoperability Profile
Definition
Forum CharterContaining: - scenario process description, - goal of forum-Alternative funding- Standards involved
Capability tables describing provided interfaces of participating companiesGap tables to cover the interoperability issues of all partners in forum
Interoperability Profile - describes how the problem can be solved Technical recommendation for research or standards development orgs
guidelines training toolstest tools / test suites
eic Enterprise Interoperability Centre / 14
Profiling Process Life Cycle
Initial Detailed
Forum Operations
Use Case Business Process
IntOp Profile
Use Case Business Process
IntOp Profile
Member Commitment
IP Policy
Planning for Detailed Scoping
Value Prop
Business Process
St-o-t-Art
Best practices
Detailed work plan
Charter
scoping
Interest Group
InteroperabilityProfile
eic Enterprise Interoperability Centre / 15
Analyst Consultations:
Profiles: •“Reference Model” for Business Profiles•When addressing an interoperability profile, the EIC needs to focus on business requirements down to technology not vice versa for identifying “optimal” (not “best”) solutions. •Beware that “Standards” have been used as a marketing and commercial weapon and have frequently been manipulated so the press and analysts to a certain extent have “Standards Fatigue”.•Need to clearly articulate and reiterate that it is about business integration.•Recommended using an eclipse like iterative model of freezing a base set of processes for contributors to build off of, then rejoin to review best set of changes to enhance the next level base.
Target Members•Need to differentiate what type of CIO we are addressing—those that are technology v. business oriented.•Value proposition for solution providers needed to be right sized for small, medium and large businesses stressing the strength and advantages of an ecosystem
Long term Value.•The greatest value of profiling workgroups will be at the intersection of where different forums meet.
?Are the challenges real? Are other organizations addressing the challenges? ?Does the forum process sound reasonable? ?Is the approach feasible? ?Is the business model reasonable?
eic Enterprise Interoperability Centre / 16
EIC Pilot - Background
In order to define the methodology and organization of EIC Business Forums, the initiative “SOA For Automotive”, started by University of St. Gallen (HSG) in October 2005, has been attributed the status of EIC Pilot in Q2/2006.
“SOA For Automotive” involves 6 Automotive companies, andaims at improving interoperability in OEM - supplier relationships by Creating a common understanding of the cross-organizational
engineering change management process; establishing a clear semantic for Engineering change documents; leveraging Web Services and SOA concepts for implementation.
Initiated by University of St. Gallen, adopted by the ATHENA research project, representing as a pilot the EIC concept
Targets of the EIC Pilot are to define a methodology for Business ProcessForums To serve as proof of concept for future business process forums
System
eic Enterprise Interoperability Centre / 17
(SOA based) integration architecture(SOA based) integration architecture
application architecture application architecture
process architectureprocess architecture
servicerepository
servicerepository
privateprivate
Publicprivate private
applicationservice
businessservice
workflow
desktopintegration
applicationservice
businessservice
workflow
desktopintegration
info
rmat
ion
sys
tem
in
form
atio
n s
yste
mb
usi
nes
s p
roce
ss
bu
sin
ess
pro
cess
Send Request_Details
Receive Respond_details
ReceiveRequest Details
Analyse Affected
Objects
SendRespond_details
ConsolidateTechnical Analysis
service description
WSDL
Semantics
message
DistributeAnalysis Task
ConductAnalysis Task
CheckAnalysis Task
ReviewDetails
EliminateRedundancy
CheckConistency
Automotive manufacturer (OEM) supplier
EIC Profile: the ECM scenario
2
3
4
5 5
3
2
Map the public process to private
processes
Specify artefacts of the service-oriented target architecture
Map public process interfaces onto
business services
Map service-oriented target architecture to
enterprises’ architectures
1
Derive the public process
eic Enterprise Interoperability Centre / 18
C.f. Roland Merrick (IBM): Interoperability Profiles for Collaborative Business Processes
eic Enterprise Interoperability Centre / 19
EIC Profile Templatehttp://www.eic-community.org/Templates/InteroperabilityProfile.html
eic Enterprise Interoperability Centre / 20
Example: EIC Profile for Engineering Change Management available as EIC Profile document
EIC Profile Engineering Change Management in the Automotive Industry
Relationships to other Standards / Profiles
VDA Recommendation 4965 (ECR/ECM)OAGIS 9.0WS-I Profiles
Use case(motivation, actors, scenarios)
Interaction scenarios in engineering change management (reflecting different cooperation models between OEM and supplier)
Business Process “Public” view of engineering change management process as ARIS EPC (BPMN used as shadow documentation)
Role model • organizational level: 2 roles (coordinator and participant)• functional level: 9 roles (Engineering Change manager, comment performer, approver, …)
Service Definition:- messages (information model)- web services (functional model)
11 messages (OAGIS BODs) ECR Business Service with 11 operations (WSDL)
Platform WS-I Basic Profile; Security (Two-way SSL + WS-Security); in future: WS-I Reliable Secure Profile (WS-I RSP)
Profile conformance (Not yet defined Test cases)
eic Enterprise Interoperability Centre / 21
Agenda
EIC and OAGi
Introduction to EIC
OAGi and EIC – a win win scenario
Share experiences: Business profiles
Outlook EIC testbed activities
Future collaboration
eic Enterprise Interoperability Centre / 22
Motivation for a Global Testbed Initiative(Initiators: CEN, EIC, ETSI, NIST, KorBIT, AIAG, IAI)
e-Business interoperability typically requires that a full set of standards are implemented
from open internet and Web Services standards to industry-level specifications and e-business frameworks
There are only limited and scattered testing facilities. As testing facilities are typically provided by one of the standard
developing organizations, they have a rather narrow focus on a particular standard.
eic Enterprise Interoperability Centre / 23
Overall Objectives of the Global Testbed Initiative(Initiators: CEN, EIC, ETSI, NIST, KorBIT, AIAG, IAI)
Concept for a global e-business interoperability test bed Definition key components of a global e-business interoperability test
bed
Outline of a testing methodology
Development of a roadmap for deploying a global e-business interoperability test bed
Available test expertise and facilities world wide
Worldwide requirements and global collaboration model
eic Enterprise Interoperability Centre / 24
Global eBusiness Interoperability Test Bed Methodologies – Scope
Phase 1: Concept and roadmap
An analysis of the benefits, risks, tasks, requirements, required resources of a global e-Business interoperability test bed based on business cases;
Development of alternative approaches to architecting and implementing global e-Business interoperability test bed;
A recommended architecture and process to develop the test bed that follows from the requirements analysis and with clear rationale;
An assessment of requirements from key international stakeholders, including of the resource commitment needed to complete the test bed development tasks.
Phase 2: Realization• implementation of the
test-bed as shared testing facility based on the suggested collaboration model
• provisioning of testing services to industry users, software vendors and SDOs
eic Enterprise Interoperability Centre / 25
Global eBusiness Interoperability Test Bed Methodologies Project Organization
Project team
Project convenor
Industry require-ments / Use cases:
AutomotiveConstruction
Furniture (Experts 5-7)
Test bed architecture(Experts 1-4)
Automotive
Bu
siness team
s
IT Vendors / Integrators
SDOs
Users
Construction
IT Vendors / Integrators
SDOs
Users
Furniture
IT Vendors / Integrators
SDOs
Users
Expert & Stakeholdercommunity
eBIF
CEN/ISSS
EIC
ETSI
NIST
Test bed architect. & collab. model
Review &Validation ofdeliverables
Test bed architect. & collab. model
Test bed architect. & collab. model
Requirements
Requirements
Requirements
Overall concept, methodology and
collaboration model(Experts 8-9)
Project secreteriat
AIAG
IAI
OtherSDOs:ISO, UN/CEFACT, …
Application vendors
Industry users
Pro
ject
init
iato
rs
Projectsteering
eic Enterprise Interoperability Centre / 26
Agenda
EIC and OAGi
Introduction to EIC
OAGi and EIC – a win win scenario
Share experiences: Business profiles
Outlook EIC testbed activities
Future collaboration
eic Enterprise Interoperability Centre / 27
EIC – Collaboration with OAGi
EIC members to join OAGi
Key objective: Jointly collaborate within OAGi and contribute to process orchestration activitiesComplement standardisation with process profiles as future delivery model
Collaborate in Process Workgroups
Key objective: Share experiences and best business practises, Introduce templates
Interlink between industry and research
Key objective: bring research activities closer to the industry alliances
Automotive Pilot: Engineering change management profile
Key objective: provide meta models and methodologies for business documents that are exchanged between cooperating business partners. The documents are the external representation of internal Business Objects Business Protocols define the interaction between partners and specify which documents are exchanged in which order.