CIECA Products

CIECA Standards Development Process

Procedures for the proposal, development, and continuing maintenance of industry standards and guides by the Collision Industry Electronic Commerce Association (CIECA).  The development of such documents is within CIECA's Mission, which is to facilitate the implementation of Electronic Commerce within the Collision Repair Industry.  Through the cooperation and energy of industry volunteers, CIECA strives to develop standards whereby industry trading-partners can better utilize information technology.  All such agreements are purely voluntary, bit itis through the use of them that the Collision Repair Industry becomes decidedly more efficient and cost effective.

New Project Proposal and Maintenance Request

All new standards and guide development begins with the Project Proposal.  Any CIECA member or industry party is invited to submit a project Proposal request by emailing projects@cieca.com or using the CONTACT - CIECA form on HOME - CIECA

Staff Review
New Project Process
Maintenance Request Process
Recourse
Staff Review

Upon receipt of a Project Proposal, the CIECA staff will review it for completeness and clarity and then present the Project Proposal to the Architecture Committee followed by the Standards Advisory Board (SAB).  


CIECA staff will process all Project Proposals within three weeks of receipt.  The SAB must receive all new Project Proposals one week prior to any meeting in order to be considered for that meeting's agenda.



New Project Process
Project Workflow

The Architecture Committee and SAB will accept or reject the proposal based on its merits.

The Requestor will be notified as soon as practical of the decision of the standards review process.


If request is approved by the Architecture Committee and the SAB Committee:

  • New Project Request: 
    • Project will be added to the JIRA Board
    • Assigned to a Committee
      • New Project Standards Committee will be created if there is not an existing Product Standards Commitee that has the capability or expertise to complete the project or if the request requires joint effort with existing Product Standards Committees. The Architecture Committee and SAB will assist in finding chairs and membership with new Project Standards Committees.
        • A Project Plan will be created to highlight the objectives, expected outcome, problem statement, scope and milestones of the project.
        • When Milestones have been accomplished, the changes will be presented to the appropriate Product Committees, Architecture Committee and SAB Committee for review and approval.
        • If a New Product is needed at this time, CIECA Staff will create the necessary web pages and Committee will become a Product Standards Committee.
        • If all requirements are rolled up into other Product Standards Committees, the Project Standard Committee will be closed.
      • Assign to existing Product Standards Committee if only one CIECA Product will be impacted, and the existing committee has the expertise and capability to complete the request.
        • The Product Standards Committee will collaborate in meetings to discuss the changes to the CIECA Product.
        • All changes will be presented to the Architecture Committee and/or SAB Committee for review and approval.
  • The Product/Project Committee accepting the request will be responsible for completing the work.  They will report their progress on a regular basis to the SAB with the assistance of CIECA Staff.
  • The CIECA staff will assist in all projects
Maintenance Request Process
Maintenance Workflow

When a Maintenance Request is submitted for purposes of changing a CIECA standard or adopted standard, it will be reviewed by the Architecture Committee.  If it is approved, the maintenance request will be presented to the Product Standards Committee responsible for that CIECA Product standard or implementation guide.  The Product Standards Committee Chair will place the item on its agenda for approval.  Any request that is not approved, must have a reason stated.


The Maintenance Request enables all parties the ability to submit changes to the CIECA Product Standards.  The most common process, however, is to have the change brought to the committee via an e-mail or as an ongoing part of the Product Standards Committee's meeting process, without requiring completion of a form.  The request, once received are handled in the same manner, described below.

  • Maintenance Request/Documentation Updates/Code Addition:
    • Project will be added to the JIRA Board
    • Assigned to the Product Standards Committee that has the expertise with the CIECA Product.
    • Product Standards Committee will collaborate in meetings to discuss the changes to the CIECA Product.
    • All changes will be presented to the Architecture Committee and/or SAB Committee for review and approval.


 The Product/Project Committee accepting the request will be responsible for completing the work.  They will report their progress on a regular basis to the SAB with the assistance of CIECA Staff.


The CIECA staff will assist in all projects.

Recourse
If a requester is at any time dissatisfied with the progress made on a Project or Maintenance Request, their first recourse is to petition the SAB through the Executive 
Director or the Chair of the SAB. The SAB will investigate and report. The requestor’s second recourse is to petition the Board of Trustees through the Executive Director or the Chairman of the Board.