All Project Committees will follow the Project Standard Committee Guidelines and Mission.
📈 Status: CIECA STAFF REVIEW
🗓 Dates
Project Proposed | Project Reviewed by CIECA Staff | Submitted to Committee(s) Review | Project Started | Rejected/Completed |
|---|---|---|---|---|
|
|
|
Background
Author of Project: Chuck Olsen, AirPro Diagnostics
Objective:
We need to share data beyond scanning to standardize messaging on specific procedures makes sense for CIECA and the industry.
AirPro Diagnostics has several shops participation in a pilot program to receive Itemized Services invoices and provide feedback to us in several categories to adjust and/or proceed on a larger scale. To Date over 2500 APD invoices with Itemized services have been issued to APD customers Shop feedback has been instrumental for evaluation of itemized work performed charges and/or description of the services performed that justify the individual procedures.
Risk/Challenges:
Insurer scrutiny of documented individual procedures being that historically, all procedures may have included and undocumented at a higher priced all-inclusive scan program without addressing specific procedures performed.
Several customers have reported certain insurers are dictating they will only pay a minimal fee for pre-and post-scanning and advocating shops acquire their own tools and perform pre-and post-scanning themselves without the technical expertise or tools capable of the additional more complex procedures required that are discovered beyond basic scanning during the processes.
The shops challenge is they are still reliant on sublet vendors unless the shop has multiple manufacturer diagnostic specialist and additional tools on sight or a service provider such as AirPro diagnostics to properly identify and execute all required procedures to bring a vehicle to a complete, safe road-worthy condition.
Expected Outcomes:
👥 Interested Industry Segments/Interested Party:
AirPro Diagnostics, CCC, Mitchell, and Solera
\uD83E\uDD14 Problem Statement
As a leader in the industry, we see the logical next move towards documenting work performed by individual procedures versus scans with average pricing. Each session (regardless of scan-type) has varying levels of complexity, technician skills, and time invested by both the shop and our diagnostic technicians and must be transparent, justified and thus compensated for accordingly.
🎯 Scope
Must have: |
|
|---|---|
Nice to have: | |
Not in scope: |
🛒 CIECA Products Impacted Estimate, Invoice, Parts and Material Procurement, Survey, and Valuation
Initial Analysis:
The <RepairTotalsInfo> Common Data Aggregate has the Optional/Repeating aggregate of <LaborTotalsInfo>
<LaborTotalsInfo> uses a Code List of Total Type to identify the estimate total category and the Code List of Total Sub Type to identify the Specific estimate total within the category.
<RepairTotalsInfo> aggregate is included in the VehicleDamageEstimateAddRq, PropertyDamageEstimateAddRq, VehicleDamagePhotoEstimateAddRq, VehicleDamageEstimateChgRq, RepairOrderFolderAddRq, CSIEstimateSurvey, CSIRepairOrderSurvey, CSIGlassSurvey, CSIPropertySurvey, ValuationAddRq, and ValuationReportAddRq messages.
<RepairTotalsInfo> aggregate is included in RepairOrderFolder, which is used in RepairOrderFoldersAddRq message.
The InvoiceAddRq Message uses <BatchInvoice> Aggregate, which uses <RepairInvoiceDetails> Data Aggregate along with <RentalInvoiceDetails>, <GlassInvoiceDetails>, <TowingInvoiceDetails> and <SalvageInvoiceDetails>.
<RentaIInvocieDetails> uses the <BillToPartyDetiails> <RentalInvoicedLineItemDetails to show the details of the invoice.
<GlassInvoiceDetails> uses the <GlassInvoiceLineItemDetails> to show the details of the invoice.
<TowingInvoiceDetails> and <SalvageInvoiceDetails> uses the Aggregate <InvoiceTotalsInfo> aggregate to show the details of the invoice, which is a duplicate of the above mentioned <LaborTotalsInfo>
<RepairInvoiceDetails> does not seem to have an aggregate that shares the details of the invoice. We could Add <RepairTotalsInfo> aggregate to share the same information that was on the Estimate.
The Test Instances and Implementation Guides we have today do not have a clear picture of a Repair Invoice, we should add a good example.
Benefits to Industry
🕰 Releases and Task
| Description | Due date | Assignee | Task appears on |
|---|---|---|---|
| Paul Barry | 2024-08-09 Meeting notes | ||
| 2024-04-11 Estimate (VDI) Committe Meeting notes | ||
| 2024-03-28 Estimate (VDI) Committe Meeting notes | ||
| 2024-03-28 Estimate (VDI) Committe Meeting notes | ||
| 2024-03-14 OEM Repair Procedures and Build Sheet Data Meeting Minutes | ||
| 2024-03-14 OEM Repair Procedures and Build Sheet Data Meeting Minutes | ||
| 2024-03-14 OEM Repair Procedures and Build Sheet Data Meeting Minutes | ||
| 2024-03-19 Architecture Meeting Minutes | ||
| 2024-03-14 OEM Repair Procedures and Build Sheet Data Meeting Minutes | ||
| 2024-02-07 EV Committee Meeting Minutes | ||
| 2024-02-07 EV Committee Meeting Minutes | ||
| 2024-02-07 EV Committee Meeting Minutes | ||
| 2024-02-07 EV Committee Meeting Minutes | ||
| 2024-02-07 EV Committee Meeting Minutes | ||
| 2024-02-07 EV Committee Meeting Minutes | ||
| 2024-01-03 EV Committee Meeting Minutes | ||
| 2024-01-03 EV Committee Meeting Minutes | ||
| 2024-01-03 EV Committee Meeting Minutes | ||
| 2024-01-03 EV Committee Meeting Minutes | ||
| 2024-01-03 EV Committee Meeting Minutes |