Public Page

Architecture Committee

8 Public Page



As participants in this meeting, we need to be mindful of the constraints of antitrust laws. There shall be no discussions of agreements or concerted actions that may restrain competition. This prohibition includes the exchange of information concerning individual prices, rates, coverages, market practices, claims settlement practices, or any other competitive aspect of an individual company’s operation. Each participant is obligated to speak up immediately for the purpose of preventing any discussion falling outside these bounds.


Architecture Membership
Architecture participation is open to all individuals who qualify as members of CIECA.

An individual may participate within Architecture without being a member of Architecture.

Membership within Architecture is granted after attending two consecutive Architecture meetings and 50% of the scheduled meetings after membership is established. Attendance criteria includes full Architecture meetings as well as Architecture sub-committee meetings.

 A scheduled meeting is a meeting announced as both CIECA webinar meetings and face to face meetings.  

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.

Architecture Scope and Objectives

  • Develop deliverables with industry participation to achieve widespread industry acceptance, functionality, and compatibility.

  • Enforce Quality assurance

    • Project Documentation meets CIECA approved standards 

    • Updates schemas for two releases per year

    • Reviews BMS and code list changes

  • Enforce Compliance with CIECA Procedures

    • 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 the required project forms and templates

  • New technology awareness and assessment

    • 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 will be upon the development documents including but not limited to:

    • Data structures

    • Schemas

    • Tag names and definitions

    • Naming conventions

  • Incorporate security and other standards as required

  • Develop and coordinate work that spans multiple Systems Development Committees

    • Assist committees in their development efforts

    • Review 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

Operating Guidelines

  • The Architecture Committee will meet monthly or more frequently as needed

  • Guides and other documents will be maintained and made available through the CIECA web site

  • There will be a commitment to coordinate XML activities with other industry and standards setting organizations to gain greater acceptance and/or speed development

  • Coordinate with other industry standards organizations and other associations  through appointed CIECA liaisons

  • Constraints and Assumptions

The Architecture Committee assumes the SAB will facilitate and coordinate the activities of the various CIECA Standards Development Committees (SDC) and action teams.  Refer to the SAB Charter for more detailed information.   

The Collision Industry Electronic Commerce Association (CIECA) Board of Trustees established an Architecture Committee empowered to establish rules and take responsibility for development of technical and architectural aspects of CIECA standards.  The Architecture Committee will report to the Standards Advisory Board (SAB).  This committee will be comprised of Business and Technical people from CIECA member companies.  This committee will also be responsible for researching and assessing new technologies and for acting as a liaison with other industry standards organizations and other associations.

The chair(s) of the Architecture Committee will be selected by the SAB and participate on the 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 and XML syntax.

Industry Coordination
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, ACORD, Universal Business Language (UBL), OT(A) (Open Travel), United Nations Center for Trade Facilitation and Electronic Business (UNCEFACT), Automotive Recyclers Association (ARA), STAR, and other CIECA subcommittees.

Meet the team

If you have questions on the committee’s activities, please contact a recent attendee.  If there is no date in column 1, they have not participated.

Chair(s):      Dan Webster



Industry Segment

Andy Bober



Aaron Daniele


Becky Kimmick

State Farm


Brad Broerman


Chris Poulos



Chrisa Hickey



Dan Webster


Information Technology

Jeff Mueller


Jeff Schroeder


Mike Hastings

Part and Material

Paul Barry


Data Standards

Paulette Reed


Data Standards

Phil Martinez


Information Technology

Stacey Phillips


Data Standards

Jira Report

key summary type created updated due assignee reporter priority status resolution