Mazda Star Barcelona

STAR/XML

An OAGI Industry Initiative

Open Applications Group, Inc.

OAG Inc.

Anthony [Tony] BlazejDirector of Industry Programs,

Open Applications Group, [email protected]

Copyright © 2002 Open Applications Group, Inc. All rights reserved

Standards for Technology in Automotive Retail (STAR)

• Project Goal: Secure, automated interchange of auto retail business data over a TCP/IP-based infrastructure using industry consensus protocols

DEALERSDMS OEM

SYSTEMS

Customer Data

Vehicle Data

Service Data

Parts Data

Other Data

Financial Data

Auto Retail Infrastructure: transport, trading partner & business process interaction protocols

Dealers: NADA (National Auto Dealer Association)

Dealer System Providers:

ADP

Arkona

Auto/Mate, Inc.

EDS Automotive Retail Group

PBS Financial Systems Inc.

Reynolds & Reynolds

Sun Microsystems

UCS

Manufacturers:American Honda Motor Co., Inc.

American Isuzu Motors, Inc.

American Suzuki Motor Corp.

BMW of North America, Inc.

DaimlerChrysler

Ford Motor Company

General Motors Corp.

Jaguar Cars

Kia Motors America, Inc.

Mazda North American OperationsMitsubishi Motor Sales of America, Inc.

Nissan North America, Inc

Porsche Cars North America, Inc.

Saab Cars USA

Toyota Motor Sales, USA

Volkswagen of America

Volvo Cars of North America


Dealer Computing Environment

B2B Processor

Parts Order

Current Dealer System Current Dealer System EnvironmentEnvironment

OEM IT Infrastructure

OEM Mainframes

DMSSystem

3

DMSSystem

3

Ajax Ford, Mazda & Lexus

DMSSystem 2

DMSSystem 2

DMSSystem 1

DMSSystem 1

Ford

Mazda

LexusBi-Synch, Leased Line

FTP over Satellite Link

SDLC, Leased Line

22,000 auto dealers in USA


STAR/XML Objectives and Goals

1. Create open, non-proprietary, standard XML messages that are implementation independent

2. Create a common auto industry-wide infrastructure to support these messages

3. Build a near-real time, Internet-based solution to standardize business transactions between dealers and OEMs

4. Reduce the costs of interface development

5. Shorten the interface development and implementation times

6. Simplify the complexity of the dealership IT environment

7. Facilitate interoperability among disparate enterprise systems


Proof Phase Parts Order

Phase One Vehicle Service History Credit Evaluation Customer/Prospect

Information Repair Order Parts Order Status Warranty Labor Operation Parts SalesPhase Two [List in proposal]

Messaging Infrastructure Recommended transport /

messaging framework characteristics

Security framework for messaging and documents

Recommended Collaboration Protocol Profiles [CPP] templates

Recommended name services, registries & repositories

Produce profiles to facilitate transport interoperability

Scope of Work


STAR/XMLSTAR/XMLInitiativeInitiative

Collaborative Project

Auto BODsAuto BODsMessagingMessaging Frame- Frame- work workTPAsTPAs


Industry Consortium working to achieve dramatically easier business software integration for:

Open Applications Group

• Business to Business• Application to Application

– Legacy– Packaged

• Across the Enterprise • Down the Value Chain• From Factory Floor to Customer

Door


STAR/XML Architecture

• Message architecture - OAGIS ver. 8 [XSD]• Message Transport Method

– ebXML Messaging Services 1.0 – permanent high speed Internet link

[DSL equivalent or better]

• Message Security Method– Digital Signature– Digital Certificate

• Transport Security Method– Secure Socket Layer (SSL)– Digital Certificate

• BPSS schema express collaborations• CPP/A define OEM & Dealer system configurations


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 Architecture, Core Components & Data Dictionary

HRXML Finance ERP eMFG SCECRM TRANxml

Industry Extensions [automotive, aerospace, metals….]

Company extensions

------- OAGIS -------


Publish SpecificationsSTAR/XMLSTAR/XML

Work Work Group(s)Group(s)

Draft SpecificationsDraft Specifications - Auto BODs- Auto BODs - Messaging framework- Messaging framework - TPAs- TPAs

ReviewApprove

Final Final OAGIS/STAROAGIS/STARSpecificationSpecification

Perspective:Perspective:- Architectural integrity- Architectural integrity- Core component reuse- Core component reuse- Technical accuracy- Technical accuracy- Horizontal leverage- Horizontal leverage

Perspective:Perspective:- Industry/Bus.Process fit- Industry/Bus.Process fit- Data dictionary integrity- Data dictionary integrity- Technical accuracy- Technical accuracy


Success

Success

Dealer OEM

Parts OrderFailure

Parts OrderSuccess

XOR

AnyFailure

AnyFailure

AnyFailure Success

Success

Modify PO DealerCancel POChange PO

End Collaboration

Modify PO OEMCancel POChange PO

Process PO

AnyFailure

<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"/>

Deliverable #1: Collaboration (BPSS)

Initiator Responder

? Change PO

= Accept PO

x Reject PO

= Back Order

Transaction view: Change Parts Order

Parts Order Collaboration

BPSS


Deliverable #2: BOD - XML and Schema

<?xml version="1.0"?><!DOCTYPE ProcessPurchaseOrder007 SYSTEM

"StarProcessPO007.dtd"><ProcessPurchaseOrder007> <ControlArea>

<BusinessServiceRequest><Verb>Process</Verb><Noun>PO</Noun><Revision>007</Revision>

</BusinessServiceRequest> <Sender>

<LogicalIdentifier>CPAG</LogicalIdentifier>

<Component>PURCHASING</Component><Task>POISSUE</Task><ReferenceIdentifier>CPAGPOBERLIN02</

ReferenceIdentifier><Confirmation>0</Confirmation><Language>ENG</Language><CodePage>CP000111</CodePage><AuthorizationIdentifier>RSCHULTE</

AuthorizationIdentifier><UnitIdentifier>124</UnitIdentifier><GeographyIdentifier>014</

GeographyIdentifier <DestinationNameCode>HO</DestinationNameCode> <DestinationComponent>DCS</DestinationComponent

</Sender>

<xsd:schema targetNamespace="http://www.ebxml.org/BusinessProcess" xmlns="http://www.ebxml.org/BusinessProcess" xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" elementFormDefault="qualified">

<xsd:element name="Attachment">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

<xsd:attribute name="name" type="xsd:string" use="required"/>

<xsd:attribute name="nameID" type="xsd:ID"/>

<xsd:attribute name="businessDocument" type="xsd:string"/>

<xsd:attribute name="businessDocumentIDRef" type="xsd:IDREF"/>

<xsd:attribute name="specification" type="xsd:uriReference"/>

<xsd:attribute name="mimeType" type="xsd:string" use="required"/>

<xsd:attribute name="version" type="xsd:string"/>

<xsd:attribute name="isAuthenticated" type="xsd:boolean" value="false"/>

<xsd:attribute name="isConfidential" type="xsd:boolean"

XML Schema - validates the Parts Order

XML - the actual Parts Order


Deliverable #3: Implementation Guide

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 AddressPartner(BillTo) segment occurs once.BillTo AddressPartner(Supplier) segment occurs once.Partner(Carrier) segment optionally occurs once.Partner(AlternateCarrier) segment optionally occurs once.Partner(AlternateShipTo) segment optionally occurs once.AlternateShipTo AddressCharge 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.

Relationship Diagram - Hierarchy of data elements

Data element definitions - Indicates required or optional, data dictionary reference


STAR/XML Benefits

Who Benefits? OEMs

– Save time and $$$ in redundant interface development & expensive legacy support of proprietary interfaces

DSPs – Build one interface per business area (vs. one per OEM)

Dealers– More timely, reliable, accurate information– Only need one DMS system for multi-franchised dealers – New interfaces can be delivered faster

OEM Supply Chain – Re-use STAR standards (A part order is a part order...)


STAR/XML Benefits

How? Standardization

– Build it once; build it right; use standard technologies; reuse components

Lower Barriers to Entry for DSPs

– Increased competition; improved application quality; lower prices; gives dealers a choice for a DSP

Design an open, scalable, modular infrastructure Make it available to everyone Specifications become the intellectual capital of all STAR

members [OEMs/DSPs]


Call to Action...

• Companies with auto industry know-how and solutions relevant to auto retail that want to get involved should contact Tony Blazej

• Related Follow-on Work:– AMDX [Auto Manufacturing Data eXchange] project

being formed with European/NorthAmerican industry sponsorship to address supply-side transactions

– TRANxml - initiative to define a cross-industry, cross-modal set of logistics transactions

• Both will be ebXML framework projects http://www.openapplications.org

[email protected]


For more information...

WWW.StarStandard.org WWW.ebXML.org

B2B Framework/Infrastructure (messaging, business process schema, transport, routing, security, etc)

WWW.OpenApplications.org Message architecture and development methodology

Mazda Star Barcelona

Automotive

oagis data dictionary

oagis oagis

exchange of data

business application

enterprise business

auto dealers

business transactions

starxml objectives