All Project Committees will follow the Project Standard Committee Guidelines and Mission.
Project Proposed | Project Reviewed by CIECA Staff | Submitted to Committee(s) Review | Project Started | Rejected/Completed |
---|---|---|---|---|
|
| Use /Date Function |
Author of Project Request: Emerging Technologies Committee
Objective: It was decided by the Emerging Technologies Committee that we needed a CIECA Committee to look at the OEM Repair Procedures and Build Sheet Data to determine a better way to communicate the data for accessing Build Sheet and OEM Repair Procedures.
Expected Outcome(s): The users of this data will be critical in this committee to develop the data standards and relieve pain points the industry is experiencing. The vehicle is becoming more complex, and the complexity of repairs are growing. The end result of this committee is to provide data standards that promote quality and safe repairs of the vehicle and have mutual accountability through the industry that if a repair procedure says to execute a step that everyone agrees this step has to be done. This can be accomplished by having easy open access to repair procedures anytime, anywhere, any place by anyone, data categorized for use in a search engine, pictogram can find the data for a repair, unified terminology, and standardized build sheet best definition of standard.
OEM / Repair Facilities / Insurance / Estimating Platforms / Information Providers
The OEM repair procedures are different based on each manufacturer (parts may be included or excluded or not give MPA), names of similar or same parts being called different things, difference in specifications of material considerations, categorizing repair procedures under different categories and the procedures are written from a service perspective instead of a collision perspective. This is causing technicians many hours to find the correct information to provide into the information provider software programs. The procedures are written from a service perspective instead of a collision perspective. This is causing technicians many hours to find the correct information to provide into the information provider software programs. The procedures leave for questions and negotiate repair plans and multiple supplements and end up causing delays and impact the customer.
Must have: Way to cross reference all part names |
|
Must have: Message parameters to search for repair procedures |
|
Must have: Sending procedures back into the estimating system |
|
Nice to have: Repair Categories standardized |
|
Nice to have: Repair Procedures that can be used for Repair and Insurance |
|
Nice to have: Repair Procedures by Collision and not Service |
|
Nice to have: Photo validation of repair |
|
Not in scope: Training technicians |
|
Risk to scope: | Add Bulleted List |
Initial list of CIECA Products impacted needs to be filled out by the Requestor; the list may change as the Project processes.
Initial Benefits to Industry needs to be filled out by the Requestor to help gain Industry participation, the list may change as the Project progresses.
Scheduled Release: The Release and Version of Project
Insert /Jira Function after the Filter has been created for Project
Add links to all Reference Material for the Project