(S.5) Exploratory Committee Advanced VMRS Coding for Predictive and Prognostic Maintenance

Please see the following Minutes of the VMRS Coding for Predictive and Prognostic Maintenance - we are submitting an update to RP 802F to add PM Codes to the VMRS System:

S.5 – Fleet Maintenance Management Task Force Meetings   |   Sept. 19^th 2023

Study Group Chair: Matt Farcosky, FleetPro, Inc.

Study Group Secretary: Bailey Stephenson, Alcoa Wheels

Minutes: S.5 VMRS Coding for Predictive and Prognostic Maintenance

Task Force Chair: Brian Mulshine, Navistar Inc.      Task Force Secretary: Robert Nordstrom, Decisiv Inc.

Agenda:

1. Call to Order / Opening Remarks / ATA Antitrust Guidelines
2. Review Prior Meeting Minutes and approval.
3. Old Business
4. Discuss updates that have been collaborated on to support the new VMRS code request.
5. Other / New Business
6. Request to move to Ballot.

Task Force Chair Brian Mulshine opened the meeting.

To start off the meeting Brian Mulshine discussed the Background:

This Task Force was stimulated from discussions that started in the 2022 Fall meeting as manufacturers discussed the need for integrating the predictive maintenance data and insights to a customer in their native maintenance tracking systems. A significant discussion with customers and fleet management system providers acknowledged the need to allow the maintenance information to be common across fleet management platforms. Since the fall meeting of 2022, we officially kicked off this Task Force at the 2023 Spring meeting in Orlando, Florida and there has been 3 additional open Web Based meetings with all green sheet attendees invited and expanded to over 30 people on each call. The attendance was well represented by customers, manufacturers, service providers and technology / fleet management system providers. Multiple manufacturers, technology providers and customers also worked closely together, shared thoughts and compromised to ensure the new potential VMRS code key could be adopted by all.

Although the Task Force name is VMRS Coding for Predictive and Prognostic Maintenance, it was recommended to call the new code key "Maintenance Labor Alerts".

Mulshine then went into the explanation of the Terminology for the Data from vehicles called "RUL Based" which indicates the remaining useful life for maintenance items like Oil & Filters, DPF filters and other components. He then showed that across manufacturers they have similar maintenance items that the difference is various terminology and varying intervals.

As we introduce the possibility of having this new Maintenance Labor Alert code key, to reduce confusion of other code keys, Maintenance Alerts are proposed to be 3 digits in length preceded by the ATA system code and then the maintenance alert code beginning with a letter to provide differentiation. The final characters after the maintenance labor alert code will be leveraging code key 16 (Repair Priority Class) to identify the alert status such as "Due Soon, Past Due or Request Performed".

The benefits were discussed on how the maintenance information can be automated from trucks to fleet systems and then with service providers in the future leveraging systems (API) integrations. The integrations can also contain additional payload (parts and other messages) information based on data provider.

This session then reviewed the proposed recommendations that supports the requirement of the additional code key. This would be supported by an update to RP 802F.

The primary additional paragraph:

Maintenance Labor Alerts "Code Key XX"

Code Key XX enables the creation of standard maintenance labor alert requirements. This will also enable the ability to be digitally communicated between integrated vehicle manufacturers and component suppliers, fleet management systems and service providers in a common identification format. This key can be leveraged to improve accuracy of work accomplishment by identifying each desired maintenance item that is required by each event.

During the Q& A session,

·         Robert Nordstrom – Decisiv, asked if the proposed changes would include the addition of an additional instruction set. Brian Mulshine – Navistar, answer yes.

·         Robert Sweany – Wooster, asked if he could receive a copy of the presentation.  Brian Mulshine – Navistar, agreed to share a copy with him.
 

After a brief Q&A /Discussion a motion was made by Robert Sweany - Wooster, to amend RFP802F. The motion was then seconded by Ken Culver – Volvo NA. Matt Farcosky – FleetPro – S. 5 Study Group Chair put the motion to a vote. The motion to amend passed unanimously.   

------------------------------
Matthew Farcosky
VP Operations
FleetPro, Inc.
Elkridge MD
------------------------------