Product Standards Committee(s)

Public Page


Membership

CIECA Product Standards Committee(s) participation is open to both members of CIECA and Non members of CIECA.

Membership within the CIECA Product Standards Committee(s) is granted after attending two consecutive meetings and 50% of the scheduled meetings after membership is established.

Membership is granted to the individual, not an organization.  

All approval decisions are made openly and on a consensus basis.  Consensus requires that all views and objections be openly and honestly considered, and that a concerted effort be made toward resolution.  The group will agree collectively on recognizing different positions.

 

Operating Guidelines

  • To incorporate all potential business entities in the business processes.

  • To work with the members to respond to committee goals and timelines.

  • To provide an open working relationship with the committee within the antitrust guidelines.

  • To coordinate all standards development with CIECA’s standards committees and SAB committee.

  • To coordinate all standards development and terminology with other industry entities.


Mission

CIECA’s Product Standard Committee(s) goal is to identify, prioritize, develop and maintain messaging, data sharing standards and codes to help all segments of the collision industry get access to and share data that enables commerce, communication and connectivity between segments.

The committee(s) responsibilities will include, but not be limited to, identifying new data sources, new data access and sharing requirements, new connectivity methodologies, new workflows, new terminology, and new data requirements to help drive the adoption and implementation of these new technologies into all collision industry segments.

Background

The Purpose of CIECA’s Product Standard Committee(s) is to define business information passing between parties as it relates to the collision repair and related industries. We are asking for responses and feedback from the industry at-large relative to the work the committee(s) has done to date, and to emphasize the importance of continued work in this area.

Each Product Standard Committee(s) will have a single focus for the CIECA Service they are representing and continue to develop standards for the product that enforce the CIECA mission.

It is evident that a framework has already begun that can drive future progress, and success will be dependent upon an expanded active participation.

Scope and Objectives

  • Provide industry definitions to new terminology to be documented and coordinated with the industry. We will work with other areas to get a consistent definition for this termination.

    • CIC

    • SAE

  • Provide accurate information to allow industry workflows to be documented.

  • Determine the data requirements to share this information electronically.

    • Identify any existing data fields or aggregates that may need to be included or modified.

    • Identify any existing code list that needs to be updated.

    • Identify new data fields or aggregates.

    • Identify new code list and values.

  • Develop new messages to share the required data.

  • Modify existing messages to share the required data.

  • Determine the benefits to all industry segments

  • Provide industry definitions (including questions and answers) and process flows

  • Develop a standard format for data communications

  • Establishing relationships to existing data elements

  • Developing a business workflow and providing industry definitions for all entities involved in this process

  • Developing new message types, code lists and/or fields (as needed) to facilitate vehicle scheduling.

  • Establishing Scheduling Implementation Guide(s)

 


 


CIECA Documents Location

All Standard documents (Use Cases, Workflows, Data Dictionary, Code List, Implementation Guides and Test Instances) can be found on the CIECA web site, www.cieca.com

Standards Documentation is specific to the CIECA Product. Please contact CIECA for access to the Product Standards documentation or sign into the CIECA web site.

 

Release, Version, and Syntax

CIECA has 2 Standard Releases a year (April and October).

 As all releases are backward compatible, use of the most current release is recommended to enable additional messages and message capabilities to be more easily implemented.  New releases include the newly created messages and recent changes to existing messages. 

 


Deliverables

CIECA Business Message Suite (BMS)/Data Dictionary

The BMS provides the foundation for implementing services related to the collision repair industry.  The document contains BMS Service Sections that define the messages.  This document provides the definitions, data types, building blocks, naming conventions, etc. to be followed when implementing a message(s). It also contains descriptions, definitions, and usage guidelines for the common aggregates and elements required when implementing a message(s).

CIECA XML Schema

The XML schema provides a technical interpretation of the BMS by defining the precise format for implementing the services illustrated therein. The schema is a faithful rendering of the message as described in the BMS, including exact replication of aggregate and element names, data types, tag structure, etc. There are no embedded attributes in the schema.

Beginning with 2012R1, there are two schemas in each release.  The only difference between two schemas is one contains all the codes embedded within it.

CIECA Master Code List

The CIECA Master Code List provides a comprehensive catalog of all code lists referenced in the BMS. The code lists contained within include both the codes and code descriptions required to implement services as defined by the BMS. This document contains code lists that have been developed by and are maintained by CIECA, as well as those that are sub-sets of code lists acquired by other sources; for code lists developed and maintained by organizations other than CIECA, the source of each list is identified.

 

Workflows

Industry Workflows are key to understanding the CIECA services and messages and how they are designed to work together.

Business Use Cases

The High-Level representation of the Services to provide a look at the services and what they do, without sharing the intellectual properties of CIECA Standards.

This will allow non CIECA members to get a glimpse at what CIECA offers.

Implementation Guides and Test Instances

The Implementation Guides are the How-To knowledge that the industry segments have shared as the best practices of the messages. Specific Data Requirements is shared as well as a test instance. The test instance is a schema filled in with the data as described in the implementation guide.