Hide Notes 

Slide 1: Open Applications Group, Inc. OAGI Industry Initiatives - STAR/XML - AMDX - TRANxml Anthony [Tony] Blazej Director of Industry Programs, Industry Schemas OAGIS Cross -Industry Schemas Open Applications Group, Inc. ablazej@openapplications.org
Slide 2: Open Applications Group Industry Consortium working to achieve dramatically easier business software integration for: • Business to Business • Application to Application – Legacy – Packaged • Across the Enterprise • Down the Value Chain • From Factory Floor to Customer Door Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 3: OAGIS • OAGIS is a cross-industry XML document framework for exchange of data between enterprise business systems both within a company and across a value chain • OAGIS is architected for extensibility into industry specific domains • OAGIS is designed for implementation as the XML data interchange technology of COTS application offerings ------- OAGIS ------Industry Extensions [automotive, aerospace, metals….] Company extensions CRM HRXML Finance ERP eMFG SCE TRANxml OAGIS Architecture, Core Components & Data Dictionary Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 4: OAGIS “Industry Value Chain” Approach • Work with established industry organizations to gain commitment of major industry players • Identify all business-to-business touch points between trading partners in the value chain • Gain executive sponsorship of an industry B2B/XML initiative to build consensus for normalize business processes, related messages and “trading partner agreements” • Develop XML-based specifications to support those processes using open standards and production ready technologies • Work with key software vendors to get XML messages incorporated in their COTS offerings • Drive adoption and implementation of XML standards within and between member companies Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 5: Collaborative Project Industry Initiative Auto BODs Messaging Framework TPAs Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 6: Development Process Domain Experts define problem and build scenarios STAR/XML Work Group • Integration scenarios • Business process normalization • Identify messages • Work flow • Infrastructure definition • User / Solution Provider consensus building Asset Owners build messages, documentation & XML schemas STAR/XML Work Group • Modeling • Message choreography • Data Dictionary • BOD development • XML schema & samples • Documentation • Validation Specification Owners Review & Approve OAGIS Management Board • Architecture • Reuse review • Consistency • Methodology • Cross-domain coordination STAR Management Board • Industry applicability • Data dictionary consistency Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 7: Publish Specifications Project Work Group(s) Draft Specifications - Auto BODs - Messaging framework - TPAs Perspective: - Architectural integrity - Core component reuse - Technical accuracy - Horizontal leverage Perspective: - Industry/Bus.Process fit - Data dictionary integrity - Technical accuracy Review Approve Final OAGIS/ STAR Specification Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 8: Standards for Technology in Automotive Retail (STAR) Focus: Secure, automated interchange of auto retail business data over a TCP/IP-based infrastructure using industry consensus protocols on res ay P L D 0pm Vehicle Data bXM 3:2 e to Service Data DEALERS e ay @ DMS Parts com hursd Data e T Financial Data eas l P Customer Data Other Data tati en OEM SYSTEMS Auto Retail Infrastructure: transport, trading partner & business process interaction protocols Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 9: Auto Manufacturing DataeXchange (AMDX) Focus: Secure, automated interchange of auto supply chain business data over a TCP/IP-based infrastructure using industry consensus protocols Inventory Levels Forecasts SUPPLIER SYSTEMS Shipping Information Traceability Data Lead-times and Capacity Data Other Data OEM SYSTEMS Auto Industry Infrastructure: transport, trading partner & business process interaction protocols Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 10: What is the AMDX initiative? • A proposal for AIAG, Odette and JAMA to jointly participate in a project with the Open Applications Group to create a defined set of automotive industry transactions expressed in XML schemas and business process models. – Most automotive industry OEMs, suppliers, solution providers, B2B trade exchanges are eagerly waiting for someone to develop of a set of standardized XML documents so they can begin embracing this new technology and take advantage of the benefits it promises – This initiative will complement the “retail facing” work already underway in the STAR/XML project • The proposed new auto industry XML standards will leverage cross-industry XML documents developed by a recognized XML content standards organization backed by software industry Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 11: Major Players Deliverables focused on Automotive Industry needs AMDX Project Currently provides horizontal schemas XML Schemas Business Models Message Framework Funding Sponsors Solution Providers • 12-15 members • Provides $ • Software companies • Commited to implement • People resources • Provide subject matter experts Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 12: Proposed Deliverables AMDX project will deliver “enhanced” set of automotive XML documents based on X12/EDIFACT transactions as well as creating new standardized transactions for critical business processes not being addressed today. • Material Release • Ship Notice • Ship Schedule • Application Advice • Receiving advice • Production Sequence • Inventory Report • Purchase Order • Request for Quote • Response to RFQ • PO Change • PO Acknowledgement • PO Change Acknowledgement • Invoice • Payment order/remittance • Text message • Critical response scenario • Inventory consumption • Engineering changes • Warranty • eAPQP Legacy X12 and EDIFACT transactions Standardized set of: •content for transactions •business processes collaborations •messaging framework. NEW business processes “AMDX scope will be sized to produce deliverables within project schedule and budget” Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 13: Partnership in Action AMDX initiative establishes a forum promoting collaboration between “users” and their key “supply chain enablement” vendors • Users are expected to invite their key vendor[s] to work with them on this project • Sponsors will agree upon scope of work and schedule so they can interlock deployment initiatives with availability of deliverables • Participation by spectrum of users [OEM, Tier 1-2] validates the solution to be broadly applicable • OAGIS methodology ensures rapid progress, consensus building among users and solution providers, and deployable results • Documented “messages” and process models support future growth Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 14: AMDX Project Overview AMDX Board Odette Technology Committee AMDX Management Team AIAG EC Steering Committee AMDX Project Office OAGI Technical Support Office Domain groups Material Management Work Group Procurement Work Group Finance Work Group ebXML Messaging Work Group Legacy X12 and EDIFACT • Material Release • Ship Notice • Ship Schedule • Application Advice • Receiving advice • Production Sequence • Inventory Report • Purchase Order • Request for Quote • Response to RFQ • PO Change • PO Acknowledgement • PO Change Acknowledgement • Invoice • Payment order/remittance • Text message • TRP • Security • Digital certificates New processes • Critical response scenario • Inventory consumption • Engineering changes • Warranty • eAPQP Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 15: OAGIS based AMDX Solution will: • Define process & data requirements to streamline automotive supply chain business interactions • Enhance & advance current AIAG initiatives • Avoid “reinventing the wheel” – Save time – Streamline/focus partner XML development efforts • Use of OAGIS provides – Re-used of proven methodology – Vocabulary to support B2B messaging – Infrastructure based on existing/emerging implementation frameworks (RN, ebXML, BizTalk) – Experienced OAGIS solution providers Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 16: TRANxml Schema for Logistics Focus: Secure, system-to-system interchange of logistics business data over a TCP/IP-based infrastructure using industry consensus protocols Forecasts Tenders/Bills of Lading SHIPPER SYSTEMS [OEMs & Suppliers] Shipping Information Tracing/Tracking/ETA Freight Billing Metrics/Reports CARRIER SYSTEMS Messaging Infrastructure: transport, trading partner & business process interaction protocols Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 17: Logistics Process Core business function of all enterprises consuming raw materials or distributing products • The logistics process depends on data generated within the enterprise, by suppliers and distributors, and by carriers at different points along the transportation route • There are core transactions, documents and data items that can be standardized across industries and transport modes, plus… • Industry practices and mode specific data requirements drive a need for domain specific extensions Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 18: What is the TRANxml initiative? • A work effort extending the Open Applications Group’s Business Object Document library into the “logistics” domain • A set of transportation focused transactions and B2B process collaborations, expressed in XML schemas, serving as the horizontal [cross industry] platform for logistics data exchange – The schemas become core components for messages needed by the various transportation modes – The schemas are the “data source” for higher level B2B processes such as Supply Chain Execution and Materials Management • TRANxml BODs become the platform for industry specific extensions supporting the needs of shippers in auto, aerospace, metals, chemicals, electronics... Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 19: Interested Parties Industry Associations Standards Bodies Carriers & Shippers Logistics providers Application SW vendors “Logistics Domain” focused deliverables XML Schemas Business Models Messaging Framework TRANxml Project develops Funding cross-industry Sponsors [horizontal] schemas • 15-20 members • Provide $$$ Solution Providers • Software companies • Committed to implement • People resources • Provide subject matter experts Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 20: Proposed Deliverables TRANxml project will deliver “enhanced” set of logistics XML documents based on X12/EDIFACT transactions as well as creating new standard messages for critical business processes not being addressed today. • Rail Bill Of Lading • Car Location Message • Motor Carrier Bill Of Lading • Motor Carrier Load Tender • Shipment Status Message • Shipment Weights • Simple Rail Bill Of Lading • Terminal Operations and Intermodal Ramp • Simple Rail Carrier Waybill Interchange • Advance Car Disposition • Car Handling Information • Shippers Car Order • Rail Industrial Switch List • Ship Notice Manifest • Warehouse Stock Transfer Shipment Adv • Warehouse Shipping Advice • Warehouse Inventory Adjustment • Confirmation Ocean • Rail Carrier Freight Details and Invoice • Shipment Information • TranXML Acknowledgment • Vessel Schedule and Itinerary Ocean • Inventory Consumption • Product Update • Multi-modal Bill of Lading Legacy X12/EDIFACT transactions Standardized set of: •content for transactions •business processes collaborations •messaging framework. NEW business processes “TRANxml scope will be sized to produce deliverables within project schedule and budget” Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 21: OAGI EECF Architecture Extended Enterprise Collaborative Framework • Message architecture - OAGIS ver. 8 [XSD] • Message Transport Method – ebXML Messaging Services 2.0 • Message Security Method – Digital Signature • Transport Security Method – Secure Socket Layer (SSL) – Digital Certificate • BPSS schema express collaborations • CPP/A define OEM & supplier system configurations Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 22: Business Object Documents (BODs) • BODs are the XML messages that business partners exchange between each other • Examples: – – – – “Process Purchase Order” “Acknowledge Repair Order” “Submit Credit Application” “Return Credit Decision” • BODs have a formal architecture, re-use the OAGIS data dictionary and are expressed in XSD Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 23: Deliverable #1: Collaboration (BPSS) Initiator Responder Transaction view: Change Parts Order ? Change PO = Accept PO = Back Order x Reject PO Dealer Process PO Success XOR OEM AnyFailure Success Success AnyFailure Modify PO Dealer BPSS <BusinessTransactionActivity name="Process PO" nameID="F28FF3663B5E042F" businessTransactionname="Process PO" businessTransactionIDRef="F28FF36 B5E" fromAuthorizedRole="Dealer" fromAuthorizedRoleIDRef="F28FF33A3 B5E0" toAuthorizedRole="OEM" toAuthorizedRoleIDRef="F28FF33F3B5E0 405" isConcurrent = "true" isLegallyBinding = "false" timeToPerform="30s" /> Cancel PO Change PO Modify PO OEM AnyFailure Cancel PO Change PO End Collaboration Success Parts Order Failure AnyFailure Parts Order Success Parts Order Collaboration Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 24: Deliverable #2: BOD - XML and Schema <?xml version="1.0"?> XML - the actual Parts Order <!DOCTYPE ProcessPurchaseOrder007 SYSTEM "StarProcessPO007.dtd"> <ProcessPurchaseOrder007> XML Schema - validates the Parts Order <ControlArea> <BusinessServiceRequest> <Verb>Process</Verb> <Noun>PO</Noun> <xsd:schema targetNamespace="http://www.ebxml.org/BusinessProcess" <Revision>007</Revision> xmlns="http://www.ebxml.org/BusinessProcess" xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" </BusinessServiceRequest> elementFormDefault="qualified"> <Sender> <LogicalIdentifier>CPAG</LogicalIdentifier> <xsd:element name="Attachment"> <xsd:complexType> <Component>PURCHASING</Component> <xsd:sequence> <Task>POISSUE</Task> <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/> <ReferenceIdentifier>CPAGPOBERLIN02</ReferenceIdentifie </xsd:sequence> r> <xsd:attribute name="name" type="xsd:string" <Confirmation>0</Confirmation> use="required"/> <Language>ENG</Language> <xsd:attribute name="nameID" type="xsd:ID"/> <CodePage>CP000111</CodePage> <xsd:attribute name="businessDocument" type="xsd:string"/> <AuthorizationIdentifier>RSCHULTE</AuthorizationIdentif <xsd:attribute name="businessDocumentIDRef" ier> type="xsd:IDREF"/> <UnitIdentifier>124</UnitIdentifier> <xsd:attribute name="specification" <GeographyIdentifier>014</GeographyIdentifier type="xsd:uriReference"/> <DestinationNameCode>HO</DestinationNameCode> <xsd:attribute name="mimeType" <DestinationComponent>DCS</DestinationComponent type="xsd:string" use="required"/> </Sender> <xsd:attribute name="version" type="xsd:string"/> <xsd:attribute name="isAuthenticated" type="xsd:boolean" value="false"/> <xsd:attribute name="isConfidential" type="xsd:boolean" Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 25: Deliverable #3: Implementation Guide Relationship Diagram Hierarchy of data elements ProcessPurchaseOrder007 occurs once for the entire file. ControlArea segment occurs once for the entire file. BusinessServiceRequest segment occurs once for the entire file. Sender segment occurs once for the entire file. DateTime(Creation) segment with Creation qualifier occurs once for the entire file. DataArea segment with sub-elements may occur multiple times. ProcessPurchaseOrder segment occurs once. PurchaseOrderHeader segment occurs once. DateTime(Document) segment optionally occurs once. Partner(ShipTo) segment occurs once. ShipTo Address Partner(BillTo) segment occurs once. BillTo Address Partner(Supplier) segment occurs once. Partner(Carrier) segment optionally occurs once. Partner(AlternateCarrier) segment optionally occurs once. Partner(AlternateShipTo) segment optionally occurs once. AlternateShipTo Address Charge segment optionally occurs once. PurchaseOrderTerms segment optionally occurs once. OperationAmount segment occurs once. PurchaseOrderLine segment occurs once. Quantity(Ordered) segment occurs once. Quantity(Length) segment optionally occurs once. Quantity(Width) segment optionally occurs once. SerialNumber(VIN) optionally occurs once. SerialNumber(KeyCode) optionally occurs once. Partner(LineCarrier) segment optionally occurs once. Data element definitions Indicates required or optional, data dictionary reference Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 26: OAGI B2B Interoperability TestBed at NIST The B2B TestBed is a funded, collaborative initiative designed to facilitate on-demand testing and demonstration of enterprise application interoperability in a B2B setting, for use by: – – – – software vendors user project teams standards organizations and other stake holding parties Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 27: OAGI and the “B2B Challenge” Challenge - 1 Show that application suites from different vendors can “talk to” one another when OAG BODs package the “content” Challenge - 2 Show how process control, workflow, security and other aspects of robust B2B capabilities can be easily addedon by “integration vendors” Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 28: B2B TestBed Focus • Business Aspects of interoperability – the ability of business partners to move information between applications that make up their company’s IT backbones (e.g. ERP, Scheduling, CRM) • Business Aspects include – business information being exchanged [BODs], and – the processes of conducting the interaction and information exchange [collaboration], using – industrial strength, open B2B messaging infrastructure [ebXML] Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 29: NIST MONITORING SYSTEM Process_PO Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 30: ebXML Infrastructure Participant A TestBed Node • Routing ebXML Messages non-ebXML Messages Participant D Participant B • Reflection ? ? Notification / API Call ProxyComponent (e.g. “Vitiris”?) monitoring Center-components Participant E Participant C Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 31: B2B TestBed Value • User and vendor testing capability enhances development and deployment of new technologies • Market-driven, Real-world Demos & Proof-of-Concept – OAG Vendor Challenge showed people that OAGIS-based solutions existed and worked as advertised [Nov 2000] – Need to bring this message to local level by demonstrating realistic interoperability solutions through many, customer focused demos, and presentations – Infrastructure, demo code re-use • Minimize errors and “throw-away” code • Availability and low cost makes maximum exposure of “interoperability” possible • Quick feedback to standards bodies Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 32: Main Benefits Expected from OAGIS/ebXML • More information (orders, inventory status...) in a timely fashion [transaction based vs. batch] • A common infrastructure lowers the cost of doing business – For OEM, SW vendors and Suppliers – Provide room for extensions at marginal cost – Enable new services (financial, insurance, …) • A well defined interface (document formats and processes) against which internal processes can be engineered and optimized – The differentiation between OEMs will come from a better use of the new information, more efficient processes and innovative services which leverage the platform Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 33: Who Benefits? • OEMs – Save time and $$$ in redundant interface development & expensive legacy support of proprietary interfaces • Application Software Vendors – Build one interface per business area (vs. one per OEM) • Suppliers – More timely, reliable, accurate information – Single application interface to service multiple OEMs – New interfaces delivered via SW Vendor products • Automotive Supply Chain – Re-use of OAGIS standards (a part order is a part order...) – Compatibility with other industries [aerospace, metals..] Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 34: How? • Standardization – Build it once; build it right; use standard technologies; re-use components • Lower Barriers to Entry for Solution Providers – Increased competition; improved application quality; lower prices; gives suppliers a choice • Design an open, scalable, modular infrastructure • Make it available to everyone • Specifications become the intellectual capital of all industry association members Copyright © 2002 Open Applications Group, Inc. All rights reserved
Slide 35: Call to Action... • Companies with auto industry and logistics know-how and solutions that want to get involved should contact Tony Blazej • We invite “middle ware” providers with ebXML focus to work on the infrastructure portion of these projects and participate in our B2B TestBed • Both initiatives will be ebXML framework projects – Suggestions for improving, expanding, leveraging these projects are welcome http://www.openapplications.org ablazej@openapplications.org Copyright © 2002 Open Applications Group, Inc. All rights reserved