copyright © 1995-2003 open applications group, inc. all rights reserved 1 open applications group...
TRANSCRIPT
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 1
Open Applications Group Briefing
January, 2004http://www.openapplications.org
Open Applications Group
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 2
Not-For-Profit Industry Consortium to:
Promote interoperability among Business Software Applications and
To create and/or endorse one or more standards for easier business software interoperability
Open Applications GroupWho we are
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 3
The Open Applications Group
• OAGi is . . . The Open Applications Group, Incorporated
• OAGIS is . . . The Open Applications Group Integration Specification
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 4
OAGi is not Just B2B
E2E = B2B + A2A + A2ETMEverywhere to Everywhere Integration
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 5
Open Applications Group
• This E2E goal is unique to OAGi• All other SDO’s focus on B2B exclusively• OAGi only does business languages• OAGi does this for:
– Outside the Enterprise (B2B)– Inside the Enterprise (A2A)– Down the Enterprise (A2E)
• A2E is Application to Execution and Engineering Systems
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 6
OAGi Genesis
• Founded in November, 1994• Originally by ERP Vendors• Focused on how they can
integrate together better• Identified common content as
biggest missing piece
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 7
Umbrella
• OAGi is an umbrella organization for building business languages for interoperability
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 8
By the Membership andfor the Membership
• OAGi is owned by it’s members• Open membership• Anyone can join• Must be a member to join or form
a Workgroup• OAGIS work is supported by
membership fees
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 9
Business Languages for Interoperability
• OAGi focuses on business languages only
• All work is based on OAGIS• No Duplicate efforts• Message architecture is consistent• Development Methodology is
consistent• This eliminates the 2 to 3 year
start-up and duplication of efforts
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 10
Forming Work Groups
• Any three members may form a Workgroup• May be Domain Based• May be Industry Based• Work Group Types
– OAGi Internal– External and Collaborative
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 11
OAGi Internal Work Groups
• Core Components• CRM XML• Logistics XML• Location Services• RiskML (ICXML)• VisionML• Semantic Integration• OAGi/NIST Test Bed• Web Services
– WS-I Member– WSDL for BODs
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 12
OAGi External Collaborative Workgroups
• AIAG• Odette• STAR• Automotive Aftermarket (AAIA)• Heavy Truck• ITA (German Technology Providers)• OSCRE (Facilities Management)• SWIFT/IFX/TWIST Payment Workgroup• Korbitt - Korean B2B Test Bed
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 13
Workgroups Accessible on OAGi Web Site
http://www.openapplications.org
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 14
• Tens of thousands of OAGIS Library Downloads since 1996
• Each Download contains all OAGIS Schemas
• Use includes– B2B, 80%– A2A, 64%– C2B, 15%
• Representing over 60 countries• 5 Continents
OAGIS Adoption
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 15
OAGIS in over 38 Industries
• Aerospace• Agri-Business• Automotive Manufacturing• Automotive Retail• Automotive Aftermarket• Banking• Brewing• CPG • Chemical• Computer Hardware• Computer Software• Consumer Goods – Electronics• Defense• Distributors• Federal Government• Food Manufacturing• Furniture Manufacturing• Pharmaceutical• Insurance
• Industrial Goods Manufacturing• Logistics• Medical Device Manufacturing• Mining• Oil • Natural Gas• Paint• Paper• Publishing• Retail• Shipping• Software• State and Local Government• Telecommunications• Tire Manufacturing• Tobacco• Trucking• Universities• Electric Utilities
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 16
OAGIS Live in 40 Known Countries
• Australia• Austria• Bahrain• Belgium• Canada• Chile• China• Croatia• Czech Republic• Denmark• Ireland• Finland• France• Germany
• Holland• Hungary• India• Israel• Italy• Japan• Korea (South)• Lithuania• Mexico• Netherlands (Holland)• Norway• Papua New Guinea• Poland
• Russia• Saudi Arabia• Singapore• Slovenia• Solvakia• South Africa• Spain• Sweden• Switzerland• Turkey• United Arab Emirates• United Kingdom• United States
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 17
• ADC Broadband• Agilent• Atofina Chemical• ATT Wireless• Bank of America• B.Braun McGaw• BE Aerospace• Black & Decker• Boeing• CD Net• Chicago Tribune• Champion Paper• Chesapeake• Covisint• Corio• EUROFLUX• DuPont• Falconbridge• Ford Motor Company• Franklin Covey• General Motors
• Gilroy Foods• GoldKist • IBM• ICI Paints• IDS Scheer• Labatt• Ingersol Rand• Johnson Controls• Lockheed Martin• Lucent• Mrs. Smiths• Pioneer• Play by Play• Qualcomm• Quebec Government• Random House• Sasol• Shell• Steelcase• US Air Force• US DOD• Xerox
OAGi Example XML Implementations
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 18
OAGi Organization, Workgroups, and OAGIS as the Unifier
PartsOrdering
Logistics XML
Risk Markup
Language
CRM XML
Inventory Visibility
OAGIS Canonical Business Language
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 19
Benefits of OAGIS-based Work
• Fast start up– Rich body of work gives an excellent
starting point– Technical Architecture in place– Development Methodology in place– IP Policy in place– Eliminates the 2 year start up– Can begin content work immediately
• Common Architecture– Technical Architecture - BOD– Application Architecture– Framework Independence– No competing standards under the
umbrella
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 20
What is OAGIS?
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 21
OAGIS is Process Definitions and Payloads
• Scenario is process definition
• Business Object Documents (BODs) are messages within the Collaboration
• Freely downloadable at:
http://www.openapplications.org
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 22
OAGIS Scenarios are Processes
• Scenarios may be large or small– Processes, Activities, Tasks, etc.
• Scenarios are expressed in UML• Scenarios serve as a library of
re-useable processes• Organizations are welcome to
modify to fit their requirements
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 23
OAGIS Scenarios
• 1.0 General Ledger to Sub-Ledger Scenario Description.. • 2.0 General Ledger to Budget.• 3.0 Order Management to Accounts Receivable• 4.0 Order Management to Accounts Receivable• 5.0 Order Management to Accounts Receivable• 6.0 Order Management to Accounts Receivable• 7.0 Purchasing to Accounts Payable• 8.0 Purchasing to Accounts Payable• 9.0 Project Accounting Synchronization• 10.0 Feeder Applications to Project Accounting• 11.0 Human Resources Integration• 12.0 Purchase Order Process• 13.0 Plant data Collection – Warehouse Management (Cycle Counts)• 14.0 Plant Data Collection – Warehouse Management (Issues)• 15.0 Plant Data Collection – Warehouse Management (Transfers)• 16.0 Plant Data Collection – Warehouse Management (Receipts)• 17.0 Plant Data Collection – Warehouse Management (Production Orders)• 18.0 Plant Data Collection – Warehouse Management (Work in Process)• 19.0 Plant Data Collection – Warehouse Management (Shipping)• 20.0 Plant Data Collection – Warehouse Management (Time and Attendance)
Page one of three
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 24
OAGIS Scenarios
• 21.0 Manufacturing to Purchasing – Receiving and Inspection in Manufacturing (Publish/Subscribe Model)• 22.0 Manufacturing to Purchasing – Receiving and Inspection in Manufacturing (Request/Replay and Publish/Subscribe)• 23.0 Manufacturing to Purchasing – Receiving and Inspection in Purchasing (Publish/Subscribe)• 24.0 Manufacturing to Purchasing – Receiving and Inspection in Purchasing (Request/Reply and Publish/Subscribe)• 25.0 Manufacturing to Order Management – Financials with Logistics, (Make to Order, Build to order)• 26.0 Manufacturing to Order Management – Financials with Logistics, (Engineer to Order, Configure to order)• 27.0 Manufacturing to Order Management – Financials with Logistics, (Mixed Mode Manufacturing)• 28.0 Manufacturing to Order Management – Financials with Manufacturing, (Make to Order, Build to Order)• 29.0 Manufacturing to Order Management – Financials with Manufacturing, (Engineer to Order, Configure to Order)• 30.0 Manufacturing to Order Management – Financials with Manufacturing, (Mixed Mode Manufacturing)• 31.0 Invoice Matching, Matching in Purchasing, Invoices entered in Purchasing• 32.0 Invoice Matching, Matching in Purchasing, Invoices entered in Accounts Payable (Publish/Subscribe)• 33.0 Invoice Matching, Matching in Purchasing, Invoices entered in Accounts Payable (Request/Reply)• 34.0 Invoice Matching, Matching in Accounts Payable, Invoices entered in Accounts Payable (Publish/Subscribe)• 35.0 Invoice Matching, Matching in Accounts Payable, (Request/Reply)• 36.0 Synchronize Sales Orders for Shipping• 37.0 Sales Force Automation to Order Management, Updating orders in Order Management• 38.0 Sales Force Automation to Order Management, Inquiring on orders in Order Management• 39.0 Sales Force Automation to Order Management and Shipping• 40.0 Supply Chain Integration, Manufacturing to Purchasing, Order Management, Billing, Shipping, and Financials
Page two of three
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 25
OAGIS Scenarios
• 41.0 Customer Service Integration, Field Service, No Returns• 42.0 Manufacturing to Order Management, Financials with Manufacturing, Make to Order with Credit Checking• 43.0 Manufacturing to Purchasing, Receiving and Inspection in Manufacturing, Request/reply Model• 44.0 Production Synchronization• 45.0 Purchase Order Integration• 46.0 Production Routing synchronization• 47.0 Human Resources Integration• 48.0 Hr to Time Data Collection• 49.0 Engineering Changes Scenario Description• 50.0 ERP to Finite Scheduling and Manufacturing Execution Scenario Description• 51.0 Computerized Maintenance Management System (CMMS) to Field Devices• 52.0 Catalog Exchange Scenario Description• 53.0 PriceList Exchange Scenario Description• 54.0 Item Unit-Of-Measure (UOM) Integration Scenario• 55.0 Buyer and Supplier RFQ - Quote Scenario Description• 56.0 Forecast Exchange Scenario Description - Revision 001• 57.0 Production to Manufacturing Execution Scenario Description• 58.0 Supply Chain Execution Scenario Description• 59.0 Ledger Actuals Scenario Description• 60.0 Vendor Managed Inventory (Consumption) Scenario Description• 61.0 Full Cycle Purchasing (non-production)
Page three of three
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 26
OAGIS BODs are a Language
• OAGIS BODs use XML to define a common business language for businesses to use.
• This language is used to exchange information between business applications and businesses.
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 27
OAGIS BOD Definition
• The OAGIS Business Object Document (BOD) Architecture defines the common XML structure and behavior definition for all OAGIS Messages.
• The OAGIS BOD Definition defines the layout or structure of a specific message to be used.
• The OAGIS BOD Instance is an occurrence of a live message that contains real data in the format defined in the schema above.
• The term BOD is often used as a generic term used to describe either BOD Definitions or BOD Instances.
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 28
Core Components
(each box is a component)
OAGIS BOD – (Payload is entire
structure)
Business View of BOD
POORDERHDR
POTERM
ADDRESS
CONTACT
PARTNER
CHARGE
DISTRIBUTN
Diagram Note: - Required = Solid boxes - Optional = Dashed boxes
POORDERLIN
POSUBLINE
POLINESCHD
PARTNER
ADDRESS
CONTACT
POTERM
DISTRIBUTN
CHARGE
DISTRIBUTN
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 29
OAGIS Core Components
• OAGi has been building these “core components” building blocks since 1995
• OAGIS Nouns are comprised of these Core Components
• Used to “Assemble” the BODs• Usually only 50% or less of a new BOD
has to be built.• Most new BODs re-use at least 50% of
existing work.
POORDERHDR
POTERM
ADDRESS
CONTACT
PARTNER
CHARGE
DISTRIBUTN
Diagram Note:- Required = Solid boxes- Optional = Dashed boxes
POORDERLIN
POSUBLINE
POLINESCHD
PARTNER
ADDRESS
CONTACT
POTERM
DISTRIBUTN
CHARGE
DISTRIBUTN
POORDERHDR
POTERM
ADDRESS
CONTACT
PARTNER
CHARGE
DISTRIBUTN
Diagram Note:- Required = Solid boxes- Optional = Dashed boxes
Diagram Note:- Required = Solid boxes- Optional = Dashed boxes
POORDERLIN
POSUBLINE
POLINESCHD
PARTNER
ADDRESS
CONTACT
POTERM
DISTRIBUTN
CHARGE
DISTRIBUTN
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 30
OAGIS Core Components
• OAGi is committed to supporting the UN/CEFACT TBG 17 CC Harmonization Process
• OAGi members are actively engaged with the UN/CEFACT efforts
POORDERHDR
POTERM
ADDRESS
CONTACT
PARTNER
CHARGE
DISTRIBUTN
Diagram Note:- Required = Solid boxes- Optional = Dashed boxes
POORDERLIN
POSUBLINE
POLINESCHD
PARTNER
ADDRESS
CONTACT
POTERM
DISTRIBUTN
CHARGE
DISTRIBUTN
POORDERHDR
POTERM
ADDRESS
CONTACT
PARTNER
CHARGE
DISTRIBUTN
Diagram Note:- Required = Solid boxes- Optional = Dashed boxes
Diagram Note:- Required = Solid boxes- Optional = Dashed boxes
POORDERLIN
POSUBLINE
POLINESCHD
PARTNER
ADDRESS
CONTACT
POTERM
DISTRIBUTN
CHARGE
DISTRIBUTN
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 31
The BOD Architecture
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 32
BOD Application Area
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 33
BOD Architecture
Noun
Verb
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 34
OAGIS Architecture
Resources
Which Content
Includes
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 35
BOD Assembly Example
F ie ld F ie ld
C o m p ou nd
F ie ld F ie ld
C o m p ou nd F ie ld
C o m p o ne nt
F ie ld F ie ld F ie ld
C o m p ou nd F ie ld
N o un
F ie ld C o m p ou nd F ie ld
C o m p o ne nt F ie ld
C o m p o ne nt F ie ld C o m p ou nd
N o un
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 36
OAGIS Nouns
• Nouns are consistent like Common Objects• 62 in OAGIS 8 (70 in 9.0)• Can be Documents• Can be Control Data• Can be any content needed in a message• Behavior is affected by Verbs• Verbs are described in next section
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 37
OAGIS 8.0 Nouns
• BOD• BillOfMaterial• Catalog• ChartOfAccounts• Consumption• CostingActivity• Credit• CreditStatus• DeliveryReceipt• DispatchList• ElectronicCatalog• EmployeeTime• EmployeeWorkSchedule• EngineeringChangeDocument
• ExchangeRate• Field• FinancialDocument• Inspection• InventoryBalance• InventoryCount• InventoryIssue• InventoryMovement• InventoryReceipt• Invoice• ItemCrossReference• ItemMaster• JournalEntry• Ledger
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 38
OAGIS 8.0 Nouns
• ItemCrossReference• ItemMaster• JournalEntry• Ledger• LedgerActual• LedgerBudget• LedgerTransactionDocument• Location• MaintenanceOrder• MatchDocument• MatchFailure• MatchOk• Party• Payable
• Personnel• PickList• PlanningSchedule• PriceList• ProductAvailability• ProductionOrder• ProductRequirement• ProjectAccounting• PurchaseLedgerInvoice• PurchaseOrder• Quote• Receivable• RequestForQuote• Requisition
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 39
OAGIS 8.0 Nouns
• Resource• ResourceAllocation• Routing• SalesOrder• SequenceSchedule• Shipment• ShipmentPlanningSchedule• ShipmentSchedule• SupplyChainExecution• TimeReporting• UnitOfMeasureGroup• WIPConfirm
• WIPMerge• WIPMove• WIPRecover• WIPSplit• WIPStatus
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 40
OAGIS Verbs
• Approach derived from Object Orientation• Nouns may need different attributes at
execution time• OAGi invented the Verb to provide this
capability.• OAGIS constrains the Nouns using XPath
portion of XSL (Not XSLT portion)• Example
– SyncPurchaseOrder– CancelPurchaseOrder
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 41
Verbs Constrain the Nouns
• Nouns are Consistent as Common Objects• Nouns may need to be different at execution• OAGIS constrains the Nouns with XPath
portion of XSL (Not XSLT portion)• The Verbs drive these constraints• Example
– SyncPurchaseOrder– CancelPurchaseOrder
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 42
OAGIS Verbs
• Acknowledge• Cancel• Change• Confirm• Get• Show• GetList• List
• Load• Notify• Post• Process• Respond• Show• Sync
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 43
OAGIS Verb Rules
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 44
OAGIS Verb XSL
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 45
BOD InstanceBOD XML Instance
Verb Constraining the Noun
Application
Validating P
arser
BOD XML Schema
XS
L Processor
BOD Constraints
Validated against OAGIS Schema
Using a standard schema-validating parser
Checked for adherence to BOD Constraints
Using a standard XSL Processor
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 46
Overlay Extensibility
• Unique to OAGIS• Non-invasive extensibility• Use two new XML Schema features
– Name Space– Substitution Group
• Uses OAGIS as base• Enables the Workgroup to build only
new or unique content• Finished schema is customized for
End-User
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 47
Overlay Example
OAGIS
Overlay
Your BOD
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 48
Extensibility Benefits
• Non-intrusive to the standard• Leverages work of OAGIS base• More customized approach for user• Less re-work for re-application at next
release• Easier to manage
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 49
Value Chain CollaborationApplications
EnterpriseManagement Applications
EnterpriseExecution
Applications
Current Scope of OAGIS Content
• eCommerce– e-Catalog– Price Lists– RFQ and Quote – Order Management– Purchasing– Invoice
• Manufacturing– Plant Data Collection – Engineering– Warehouse Management– Enterprise Asset Mgmt.
• Logistics– Shipments
• CRM– Customer– Sales Force Automation
• ERP– Financials– Human Resources– Manufacturing– Credit Management
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 50
Current OAGIS Release
• OAGIS 8.0– Full XML Schema, 4th Generation for OAGIS– Approx 60 Scenario Definitions– Approx 200 Messages– Approx 62 nouns– Approx 19 Verbs– Approx 190 Core Components– Actually the 18th Release
• 8+ years in maturing
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 51
Framework Independence
• OAGIS is framework independent• The separation of the message
architecture from the framework is critical to enable cross environment deployment
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 52
OAGIS fits with ebXML
• Communication Layer (T&R) ebXML Transport
• Partner Agreements (CPP, CPA) Format - ebXML
• Process Definitions (BPSS) Format – ebXML Content - OAGIS
• Syntax OAGIS Tags
• Meaning of Information OAGIS Dictionary
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 53
OAGIS and SOAP
• SOAP Overlaps with BOD Application Area– Sender, DateTime, Digital Signature– BOD does not assume SOAP– BOD has to remain neutral– BOD may be used without SOAP
• Strategies for Use– Use Application Area for business applications– Don’t use Application Area as an envelope– Make sure you use DateTime and BODId at least
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 54
OAGIS and Web Services
• Web Services standardizes– Shape of the plugs (SOAP)– Shape of the outlet (WSDL)– Current over the wire (OAGIS XML)– WS-Security will be the ground
WSDL
SOAP
OAGIS XML
WS -Security
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 55
OAGIS is Framework Independent
OAGIS is the payload
ebXML is the envelope
Web Services is the envelope
Your Envelope is the envelope
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 56
Using OAGIS XML as a Canonical Model
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 57
Business Environment
Integration Back Bone
Business
Unit n
Su
pp
lier
Cu
stom
er
Business
Unit 1
Business
Unit 2
Enterprise
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 58
A Case for a Canonical Model
From <many to many> to <many to one>
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 59
The mathematics of scaling up
For traditional point to point or<many to many> integration:
The number of possible connectionsamong any number of items is n(n-1)for two way connections.
n = 5 5(4) = 20
n = 10 10(9) = 90
n = 15 15(14) = 210
n = 20 20(19) = 380
Number ofcomponentsto integrate
Apply traditionalformula
Cost of traditionalintegration @ 0.1 FTE
2 FTEs
9 FTEs
21 FTEs
38 FTEs
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 60
The mathematics of scaling up
For best practices integration:
The number of possible connections among any number is n * 2.0
Number ofcomponentsto integrate
Best practicesformula
n = 5 5 * 2.0 = 10
n = 10 10 * 2.0 = 20
n = 15 15 * 2.0 = 30
n = 20 20 * 2.0 = 40
1 FTE
2 FTEs
3 FTEs
4 FTEs
Cost of best practicesintegration @ 0.1 FTE
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 61
Side by side comparison
<many to many> growth <many to one> growth
4 FTEs38 FTEs
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 62
Lucent SOA with OAGIS Canonical Model
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 63
Agilent Enterprise Integration Model
Service & SupportService
& Support
eBusinesseBusinessOrder
GenerationOrder
Generation
Order Fulfillment
Order Fulfillment
Information Management
Legacy Systems
Broadvision
enCommerce
BladeRunner Oracle Apps
HRFinanceReference Systems
Product
Customer
Supplier
Price
Company Information
PeopleSoftSAP/Oracle
Data Warehousing
Reporting
Intranet ContentXpedio/
BladeRunner/
Filenet
FunctionalApplications
Legal, GTT, WPS ...
Merging Companies’ Applications
Merging Companies’ Applications
Packaged, Legacy
OAGi Canonical ModelTIBCO Bus (RVRD)
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 64
• Agilent• Amersham Health• Emerson Motors• Ford• General Electric Power• Goodyear• IBM• Lucent• US Air Force• Weyerhauser
Sample of Customers using the OAGIS Canonical Model
OAGIS Canonical Business Language
CRMERP CustomerSupplier
ERP CustomerSupplier CRM
OAGIS Canonical Business Language
CRMERP CustomerSupplier
OAGIS Canonical Business Language
CRMERP CustomerSupplier CRMERP CustomerSupplier
ERP CustomerSupplier CRMERP CustomerSupplier CRM
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 65
Development Methodology
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 66
• Demand driven• Projects led by members• Virtual teams• Work done by email and
teleconference between meetings
• Repeatable process
Development Methodology
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 67
Project Definition
Construction PublicationReview & Approval
Activities- Propose Project- Build Project Definition- Choose Team- Get CTO Approval- Set up Yahoo Group
Activities- OAGi Architectural review for consistency, etc.- Editing by OAGi architect- Final testing of XML deliverables- Combine all project content together- Complete any defect removal necessary- Complete any requested enhancements not in a specific project- Publish to OAGi web site.
Activities- Review deliverables with OAGi Architect- Review final deliverables with working team and ask for vote.- Present to OAGi Technical team and ask for vote- Finalize changes based on voting results- Turn deliverables over to OAGI architect- CTO presents to OAGi Board for final approval
Activities- Business process modeling- BOD message development- Dictionary development- XML Schema development- XML message examples development- Teleconferences with
project team- Construction Phase review
to OAGi technical meeting- OAGi architectural review
OAGi Open Development Methodology
Deliverables (PL)- Project Definition- Project Team- Yahoo Group
Deliverables (PL, TM)- Integration Scenario(s)- BOD documentation- Dictionary updates- XML Schemas (DTDs)- XML message examples
Deliverables (PL, TM)- Approved versions of the following:- Integration Scenario(s)- BOD documentation- Dictionary updates- XML Schemas (DTDs)- XML message examples
Deliverables (OA, CTO)- Final versions of the following:- Integration Scenario(s)
-UML Sequence Diagram-UML Collaboration Diagram
- BOD documentation- Dictionary updates- XML Schemas (XSD)- XML message examples
Roles:PL - Member Project
LeaderTM - Team membersOA - OAGi ArchitectCTO - OAGi CTO
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 68
OAGIS Construction Workflow
Copyright © 1995-2003 Open Applications Group, Inc. All rights reserved 69
Questionshttp://www.openapplications.org