STAR XML BODs
BODs (XML Schemas)
STAR has worked with its membership to develop over 200 XML message formats covering over 35 business areas from from customer relationship management to fixed and variable operations. These specifications have been designed to leverage the globally-recognized UN/CEFACT Core Component Technical Specification (CCTS) and the Open Application Group Integration Specification (OAGIS) Business Object Document (BOD) Methodology. In addition, the STAR XML Schema Repository is written using the W3C XML Schema Language.
Cross-Industry
Solution
Solution
STAR’s original charter was to support the retail automotive industry, however in recent years it has expanded its support effectively demonstrating value in related industries including:
• Marine
• Medium & Heavy-duty Trucks
• Powersports
• Construction Equipment
• Marine
• Medium & Heavy-duty Trucks
• Powersports
• Construction Equipment
Global
Solution
Solution
In addition to expanding related- industry support, STAR has also grown from a US-centric organization to a global solution supporting:
• Asia-Pacific
• Canada
• Central America
• South America
• Europe
As STAR's community continues to expand and evolve so does its requirements base. With a strong commitment to community and to agility, STAR will continue to adapt and advance to meet the changing needs of its users.
For more information, view our XML Schema FAQs
• Asia-Pacific
• Canada
• Central America
• South America
• Europe
As STAR's community continues to expand and evolve so does its requirements base. With a strong commitment to community and to agility, STAR will continue to adapt and advance to meet the changing needs of its users.
For more information, view our XML Schema FAQs
Specification
Support
Support
STAR provides support for the most current version of its XML Schema Repositories which can be found in the XML Schemas page.
In addition to supporting the current version of the XML Schema Repositories, STAR also supports the N-1 versions, i.e., the prior year's releases, which can be found in the N-1 XML Schemas page.
Specifications older than N-1 are not supported and therefore are not provided either on the STAR website or by request.
In addition to supporting the current version of the XML Schema Repositories, STAR also supports the N-1 versions, i.e., the prior year's releases, which can be found in the N-1 XML Schemas page.
Specifications older than N-1 are not supported and therefore are not provided either on the STAR website or by request.
- General
- Customer
- Dealer
- Parts Management
- Vehicle Management & Sales
- Vehicle Repair & Service
| Specification | Description | Sequence Diagram |
|---|---|---|
| Confirm BOD | The Confirm BOD reports on the outcome of processing a BOD. | n/a |
| Standard Codes | The scope of this BOD is to transmit Standard Codes information to/from the dealership. Standard Codes is the task of sending the Standards Codes information electronically between Dealer and OEM systems. | X |
| Specification | Description | Sequence Diagram |
|---|---|---|
| Credit Application | The scope of this BOD is to define the Credit Application process for individual consumers apply for vehicle financing through their Dealer. | X |
| Credit Contract | The scope of this BOD is to define the Credit Contract process for individual dealers to submit credit contracts to lenders. | X |
| Credit Contract Response | The scope of this BOD is to define the Credit Contract Response process for lenders responding to individual dealers that have submitted credit contracts. | X |
| Credit Decision | The scope of this BOD is to define the Credit Decision process for Lenders to provide decision information to Dealers for individual consumers applying for vehicle financing. | X |
| Customer Information | The Customer Information BOD is utilized to communicate the changes performed on the DMS customer database back to the OEM’s customer database to maintain accuracy and synchronicity. | X |
| Sales Lead | The scope of this BOD is to define the Sales Lead for individual consumers who purchase/lease automobiles through dealers for vehicle products only. | X |
| Service Appointment | The scope of this BOD is to define the Service Appointment for individual consumers who schedule service appointments with their local dealership via the Internet. |
X |
| Specification | Description | Sequence Diagram |
|---|---|---|
| Financial Metrics | FinancialMetrics is used to transmit dealer Financial Metrics information. | Coming Soon |
| Financial Statement | The scope of this BOD is to transmit dealer Financial Statement information. This may include Balance Sheet, Profit and Loss, and any other Financial Statement related information. | X |
| Specification | Description | Sequence Diagram |
|---|---|---|
| Parts Inventory | The scope of this BOD is to define the Credit Application process for individual consumers apply for vehicle financing through their Dealer. | X |
| Credit Contract | The scope of this BOD is to define the Credit Contract process for individual dealers to submit credit contracts to lenders. | X |
| Credit Contract Response | The scope of this BOD is to define the Credit Contract Response process for lenders responding to individual dealers that have submitted credit contracts. | X |
| Credit Decision | The scope of this BOD is to define the Credit Decision process for Lenders to provide decision information to Dealers for individual consumers applying for vehicle financing. | X |
| Customer Information | The Customer Information BOD is utilized to communicate the changes performed on the DMS customer database back to the OEM’s customer database to maintain accuracy and synchronicity. | X |
| Sales Lead | The scope of this BOD is to define the Sales Lead for individual consumers who purchase/lease automobiles through dealers for vehicle products only. | X |
| Service Appointment | The scope of this BOD is to define the Service Appointment for individual consumers who schedule service appointments with their local dealership via the Internet. |
X |
| Specification | Description | Sequence Diagram |
|---|---|---|
| Initiative Download | The scope of the Initiative Download BOD is to support the daily transmission of up-to-date vehicle initiative information from the OEM to the Dealer. | X |
| Retail Delivery Reporting | The scope of this BOD is to report the "sale" of a vehicle at the dealership. Retail Delivery Reporting is the task of sending the Retail Delivery Reporting information electronically between Dealer and OEM systems. | X |
| Validate Initiative | The scope of the Validate Initiative BOD is to is to support the validation of initiatives to be used during the creation or “desking” of a deal when a vehicle is being purchased. This information is sent from the Dealer to the OEM for validation. The OEM will then respond by acknowledging if the initiatives selected are valid and have not expired. | X |
| Vehicle Initiative Payment Invoice | VehicleInitiativePaymentInvoice supports the transmission of Variable Marketing Dealer Rebate Payment Data to the dealership. NOTE: Although this is the traditional use of the Vehicle Initiative Payment Invoice, it could be used to send Vehicle Initiative Payment Invoice information between any two business parties. | X |
| Vehicle Data Availability | The Vehicle Data Availability BOD allows the DMS to submit a single inquiry to determine what information is available for retrieval. The DMS could then submit individual BOD request only for the data that is available. This will conserve bandwidth and system resources. | X |
| Vehicle Inventory | The scope of this BOD is to transmit Vehicle Inventory information to the dealership. Vehicle Inventory is the task of sending the Vehicle Inventory information electronically between Dealer and OEM systems. | X |
| Vehicle Invoice | . The scope of this BOD is to transmit Vehicle Invoice information to the dealership. NOTE: Although this is the traditional use of the Vehicle Invoice, this BOD could be used to send Vehicle Invoice information between any two business parties. | X |
| Vehicle Order | The scope of this BOD is to support the placement of Vehicle Orders. The BOD supports placing orders to the manufacturer by a dealer, leasing company or other entity and reporting order status to the ordering entity. A Vehicle Order is defined as an order for one or more vehicles including specifications of Model, Color and Options. The order may, or may not, include incentives. NOTE: Although this is the traditional use of the Vehicle Order BODs, this BOD could be used to send Vehicle Order information between any two business parties. | X |
| Vehicle Remarketing | The scope of this BOD will be to transmit vehicle and advertising data between the remarketing organizations, such as newspapers, used vehicle publications and the internet advertisers. NOTE: Although this is the traditional use of the Vehicle Remarketing, this BOD could be used to send Vehicle Remarketing information between any two business parties. | X |
| Vehicle Specifications | The scope of these BODs will be to provide specifications of what options, colors are available for a given model and what options are required. Additionally, option dependencies, conflicts and inclusives could be provided. NOTE: Although this is the traditional use of the Vehicle Specifications, this BOD could be used to send Vehicle Specifications information between any two business parties. | X |
| Specification | Description | Sequence Diagram |
|---|---|---|
| Labor Operations |
The scope of this BOD is to provide real-time access to labor operation data through inquiries and searches. Labor Operations is the task of sending the labor operation information electronically between Dealer and OEM systems. | X |
| Model Codes | The scope of this BOD is to provide real-time access to vehicle model code data through inquiries and searches. Model Codes is the task of sending the vehicle model code information electronically between Dealer and OEM systems. | X |
| Repair Order | The scope of this BOD is to define the Repair Order process for individual consumers who service their automobiles through their OEM’s authorized Dealers. The focus is on Dealer and OEM interactions, not third party repair organizations. | X |
| Service Plan | The scope of this BOD is to define the Service Plan process of communicating vehicle service plan and maintenance plan, pricing and availability information to the dealer. NOTE: Although this is the traditional use of the Service Plan BOD, this BOD could be used to send Service Plan information between any two business parties. | X |
| Service Processing Advisory & Receipt Acknowledgment |
The scope of the Service Processing Advisory BOD is to send an advisory to a Dealer from an OEM on the status of a Warranty Claim submitted to the OEM by the Dealer. Service Processing Advisory is the task of sending the advisory information electronically between OEM and Dealer systems. The scope of the Service Advisory Receipt Acknowledgment BOD is to send a confirmation to a Dealer from an OEM acknowledging receipt of request for payment for a Warranty Claim. Service Advisory Receipt Acknowledgment is the task of sending the confirmation information electronically between OEM systems and Dealer systems. |
X |
| Vehicle Service History |
The scope of this BOD is to transmit Vehicle Service History information to the dealership. Vehicle Invoice is the task of sending the Vehicle Service History information electronically between Dealer and OEM systems. | X |