Mazda Star Barcelona
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Mazda Star Barcelona

Uploaded on

Experience Mazda Zoom Zoom Lifestyle and Culture by Visiting and joining the Official Mazda Community at for additional insight into the Zoom Zoom Lifestyle and......

Experience Mazda Zoom Zoom Lifestyle and Culture by Visiting and joining the Official Mazda Community at for additional insight into the Zoom Zoom Lifestyle and special offers for Mazda Community Members. If you live in Arizona, check out CardinaleWay Mazda's eCommerce website at

More in: Automotive , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. STAR/XML An OAGI Industry Initiative Open Applications Group, Inc. OAG Inc. Anthony [Tony] Blazej Director of Industry Programs, Open Applications Group, Inc. [email_address]
  • 2. 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
    DEALERS DMS OEM SYSTEMS Customer Data Vehicle Data Service Data Parts Data Other Data Financial Data Auto Retail Infrastructure: transport, trading partner & business process interaction protocols
  • 3.
    • 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 Operations Mitsubishi 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
  • 4. Dealer Computing Environment B2B Processor Parts Order Current Dealer System Environment OEM IT Infrastructure DMS System 3 Ajax Ford, Mazda & Lexus DMS System 2 DMS System 1 Ford Mazda Lexus Bi-Synch, Leased Line FTP over Satellite Link SDLC, Leased Line 22,000 auto dealers in USA OEM Mainframes
  • 5. 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
  • 6.
    • 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]
    • 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
  • 7. Collaborative Project STAR/XML Initiative Auto BODs Messaging Frame- work TPAs
  • 8. 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
  • 9. 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
  • 10. 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 SCE CRM TRANxml Industry Extensions [automotive, aerospace, metals….] Company extensions ------- OAGIS -------
  • 11. Business Object Documents (BODs)
    • BODs are the XML messages that dealers and OEMs transact with one another.
    • Examples:
      • “ Process Repair 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
  • 12. STAR/XML Development Team
    • OAGI Provided Resources
      • Project Manager
      • Architect
      • Business Analyst
    • STAR Provided Resources
      • Data Dictionary Maintenance
    • STAR Member Resources [per Company]
      • Project Team Member [Coordinator]
      • Application Domain Expert(s)
      • IT Department Specialists
      • Access to "Users" and their Management
  • 13. STAR/XML Development Process Specification Owners Review & Approve Asset Owners build messages, documentation & XML schemas 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
    • STAR/XML Work Group
    • Modeling
    • Message choreography
    • Data Dictionary
    • BOD development
    • XML schema & samples
    • Documentation
    • Validation
    • OAGIS Management Board
    • Architecture
    • Reuse review
    • Consistency
    • Methodology
    • Cross-domain coordination
    • STAR Management Board
    • Industry applicability
    • Data dictionary consistency
  • 14. Publish Specifications STAR/XML Work Group(s) Draft Specifications - Auto BODs - Messaging framework - TPAs Review Approve Final OAGIS/STAR Specification Perspective: - Architectural integrity - Core component reuse - Technical accuracy - Horizontal leverage Perspective: - Industry/Bus.Process fit - Data dictionary integrity - Technical accuracy
  • 15. Project time line
    • FOCUS:
    • 1Q2001: Project organization, staffing & launch
    • Proof: produce useable results quickly
    • Phase 1: deliverables & infrastructure architecture
    • Phase 2: build STAR team skills, finish work scope
    • Deployment: support [work not part of project scope]
  • 16. Deliverables *
    • Normalized business collaborations
      • identify/document current process
      • define normalized business collaborations
      • document via "model"
    • BODs [messages] for each business collaboration
      • message content
      • normalized data elements
      • mappings to existing data dictionaries
    • Business Transaction Set choreography
    • XML rendition of BODs
    • PLUS - Messaging Infrastructure deliverables
    * per application domain
  • 17. Deliverable #1: Collaboration (BPSS) <BusinessTransactionActivity name=&quot;Process PO&quot; nameID=&quot;F28FF3663B5E042F&quot; businessTransactionname=&quot;Process PO&quot; businessTransactionIDRef=&quot;F28FF36 B5E&quot; fromAuthorizedRole=&quot;Dealer&quot; fromAuthorizedRoleIDRef=&quot;F28FF33A3 B5E0&quot; toAuthorizedRole=&quot;OEM&quot; toAuthorizedRoleIDRef=&quot;F28FF33F3B5E0 405&quot; isConcurrent = &quot;true&quot; isLegallyBinding = &quot;false&quot; timeToPerform=&quot;30s&quot; /> Transaction view: Change Parts Order Parts Order Collaboration BPSS
  • 18. Deliverable #2: BOD - XML and Schema
    • <?xml version=&quot;1.0&quot;?>
    • <!DOCTYPE ProcessPurchaseOrder007 SYSTEM &quot;StarProcessPO007.dtd&quot;>
    • <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=&quot;; xmlns=&quot;; xmlns:xsd=&quot;; elementFormDefault=&quot;qualified&quot;> <xsd:element name=&quot;Attachment&quot;> <xsd:complexType> <xsd:sequence> <xsd:element ref=&quot;Documentation&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;unbounded&quot;/> </xsd:sequence> <xsd:attribute name=&quot;name&quot; type=&quot;xsd:string&quot; use=&quot;required&quot;/> <xsd:attribute name=&quot;nameID&quot; type=&quot;xsd:ID&quot;/> <xsd:attribute name=&quot;businessDocument&quot; type=&quot;xsd:string&quot;/> <xsd:attribute name=&quot;businessDocumentIDRef&quot; type=&quot;xsd:IDREF&quot;/> <xsd:attribute name=&quot;specification&quot; type=&quot;xsd:uriReference&quot;/> <xsd:attribute name=&quot;mimeType&quot; type=&quot;xsd:string&quot; use=&quot;required&quot;/> <xsd:attribute name=&quot;version&quot; type=&quot;xsd:string&quot;/> <xsd:attribute name=&quot;isAuthenticated&quot; type=&quot;xsd:boolean&quot; value=&quot;false&quot;/> <xsd:attribute name=&quot;isConfidential&quot; type=&quot;xsd:boolean&quot; XML Schema - validates the Parts Order XML - the actual Parts Order
  • 19. 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 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.
    Relationship Diagram - Hierarchy of data elements Data element definitions - Indicates required or optional, data dictionary reference
  • 20. 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...)
  • 21. 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]
  • 22. 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 [email_address]
  • 23. For more information...
    • B2B Framework/Infrastructure (messaging, business process schema, transport, routing, security, etc)
    • Message architecture and development methodology