Open Applications Group, Inc.
STAR/XML
An OAGI Industry
Initiative
OAG Inc.
Anthony [Tony] Blazej
Director of Industry Programs,
Open Applications Group, Inc.
ablazej@openapplications.org
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
Customer Data
Vehicle Data
DEALERS
DMS
Service Data
Parts Data
Financial Data
OEM
SYSTEMS
Other Data
Auto Retail Infrastructure: transport, trading partner &
business process interaction protocols
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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
Mazda North American
Operations
Mitsubishi Motor Sales
of America, Inc.
Nissan North America,
Inc
Porsche Cars North
America, Inc.
Saab Cars USA
Ford Motor Company
Toyota Motor Sales,
USA
General Motors Corp.
Volkswagen of America
Jaguar Cars
Volvo Cars of North
America
Kia Motors America,
Inc.
Current Dealer System
Environment
Ajax Ford, Mazda & Lexus
Ford
OEM IT Infrastructure
B2B Processor
Mazda
DMS
System 1
DMS
System 2
Parts
Order
OEM Mainframes
Lexus
DMS
System
3
Dealer Computing
Environment
22,000 auto dealers in USA
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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
Copyright © 2002 Open Applications Group, Inc. All rights reserved
Scope of Work
Proof Phase
 Parts Order
Phase One
 Vehicle Service History
 Credit Evaluation
 Customer/Prospect
Information
 Repair Order
 Parts Order Status
 Warranty Labor Operation
 Parts Sales
Phase Two
 [List in proposal]
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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
Collaborative Project
STAR/XML
Initiative
Auto BODs
Messaging
Framework
TPAs
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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
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
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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
Publish Specifications
Perspective:
- Architectural integrity
- Core component reuse
- Technical accuracy
- Horizontal leverage
STAR/XML
Work
Group(s)
Draft Specifications
- Auto BODs
- Messaging framework
- TPAs
Review
Approve
Final
OAGIS/STAR
Specification
Copyright © 2002 Open Applications Group, Inc. All rights reserved
Perspective:
- Industry/Bus.Process fit
- Data dictionary integrity
- Technical accuracy
Deliverable #1: Collaboration
(BPSS)
Initiator
Responder
Transaction view: Change Parts Order
? Change PO
= Accept PO
Dealer
OEM
Process PO
= Back Order
Success
x Reject PO
XOR
AnyFailure
Success
Success
AnyFailure
Modify PO Dealer
BPSS
Cancel PO
Change PO
<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"
/>
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
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</ReferenceI
</xsd:sequence>
dentifier>
<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</Authorizatio
<xsd:attribute name="businessDocumentIDRef"
nIdentifier>
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
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.
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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...)
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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]
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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
ablazej@openapplications.org
Copyright © 2002 Open Applications Group, Inc. All rights reserved
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
Copyright © 2002 Open Applications Group, Inc. All rights reserved