The purpose of this committee is to define and audit 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 has done so far, and to emphasize the importance of continued work in this area.
The first objective will be to develop a single focus of the committee’s scope, objectives and goals. It is evident that a framework has already begun that can drive future progress, and success will be dependent upon an expanded active participation.
The overseeing of standards and the proposed changes to them is needed to maintain quality and consistency. The placeholder for cooperation with other associations also needs to be centralized and changes to our co-developed products as a result. In addition to the outreach to other associations, there is a need to centralize new technology research and its integration into the standards.
CIECA’s Architecture Committee’s goal is to establish rules and take responsibility for development of technical and architectural aspects of CIECA standards. This committee is also responsible for researching and assessing new technologies and for acting as a liaison with other industry organizations/associations.
The chair(s) of the Architecture Committee participates on the Standards Advisory Board (SAB). The ideal candidate(s) will have both technical and business experience in business-to-business (B2B) data exchanges such as, but not limited to, X12/EDI, XML, and JSON syntax.
Scope & Objectives
The Architecture Committee will focus on the potential and process of:
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
Develop deliverables with industry participation to achieve widespread industry acceptance, functionality, and compatibility
Ensure new project proposals, releases, maintenance, and support guidelines for technical standards are being followed
Ensure Project work meets business case
Ensure deliverable(s) are within the scope of the business case
Develop project forms and templates
Develop and recommend new technical methods
Define release, maintenance, and support guidelines for technical standards
The goal is to focus our standards development on current technologies that have industry acceptance
The current focus is based upon the development of XML and JSON documents including but not limited to:
Schemas and/or example instances
Data element names and definitions
Code lists and code definitions
Incorporate security and other standards as required
Develop and coordinate work that spans multiple Standards Development Committees
Assist committees in their development efforts
Review developments for reuse opportunities
Responsible for training and education of technical and architectural aspects of CIECA standards
Other objectives as assigned by the Standards Advisory Board or the Board of Trustees
To incorporate all potential business entities in the business processes
To work with the group to respond to group goals and timelines
To provide an open working relationship with the Committee within the antitrust guidelines
To meet monthly or more frequently as needed
To maintain and make available Guides and other documents through the CIECA web site
To coordinate activities with other industry and standards setting organizations to gain greater acceptance and/or speed development
To incorporate other standards, including codes, as part of the development process
To coordinate with other industry standards organizations and other associations through appointed CIECA liaisons
Industry Segments Affected
Constraints and Assumptions
The Architecture Committee assumes the SAB will facilitate and coordinate the activities of the various CIECA Standards Development Committees (SDC). Refer to the SAB Charter for more detailed information.
Architecture Committee Membership
CIECA membership is required to be an Architecture voting member. Membership within Architecture is granted after attending two consecutive Architecture meetings. Attendance criteria includes full Architecture meetings as well as Architecture sub-committee meetings. After membership is established, a member must attend at least one meeting per quarter. A scheduled meeting is a meeting announced as both CIECA webinar meetings and face to face meetings. Membership is granted to an individual, not an organization.
Architecture participation is open to all individuals, however non-CIECA members do not have voting rights. An individual may participate within Architecture without being a member of Architecture.
Coordination within the collision industry, standards organizations, and industry groups is essential for this committee to meet its objectives. This list includes but is not limited to ASC X12, Aftermarket Council on Electronic Commerce (ACEC), ACORD, Universal Business Language (UBL), United Nations Center for Trade Facilitation and Electronic Business (UNCEFACT), Automotive Recyclers Association (ARA), Standards for Technology and Automotive Retail (STAR), Open Travel Alliance (OTA), and other CIECA SDC.