Service system for recording maintenance requirements and regular service events

For our partner we developed and implemented a service system module to record both planned and extraordinary service requirements. The system notifies the user of upcoming terms of scheduled maintenance. The system is capable of automatic generation of service events and item breakdown of invoices. Analytical part of the system records and stores information for analytical evaluation of vehicle’s technical state.

Digging Deeper

  • system module implementation to record service requirements for vehicles
  • recording both regular and extraordinary service and maintenance requirements
  • automatic generation of regular service events
  • notification of upcoming terms
  • advanced data processing of performed services
  • item breakdown of invoices
  • registration of related documents
  • flexible data outputs for an analytical evaluation of recorded information
  • user-defined service code dials, vehicle service profiles, tracked invoice items and service partners

Used Technologies

Number of Man Days we spent programming

Angular

5100 100% Complete

Javascript

2500 49% Complete

Typescript

2100 42% Complete

C#

1500 29% Complete

.NET

1200 23% Complete

Use Cases

Two types of user service requirements

Planned or extraordinary - based on actual user's needs

Planned – FLW2 system generates them based on user-defined criteria:

  • kilometers between service stations
  • time between services
  • a combination of both – in this case the priority has the requirement that occurs first
  • scheduled service requirements may have been set to follow a different requirement

Extraordinary – based on current user’s needs

  • accidents and a consequent need for repairs (tires, windshield…)
  • malfunctions and a consequent need for repairs (tires, transmission…)

Functional sections

Service requirements can be categorized into functional sections – subject to the user’s decision

Typical functional sections are:

  • administration
  • malfunctions
  • regular service
  • equipment purchase
  • accidents

Practical merging functions

Service requirements can be merged and executed at the service partner at the same time

Merged can be:

  • scheduled + extraordinary service
  • scheduled + scheduled service
  • extraordinary + extraordinary service
  • merged requirements must from the user's point of view also support a repeated redistribution of individual requirements and their subsequent processing

Comprehensive service records

Service records include comprehensive information for a better operational comfort

Service records include:

  • partner who performed the operation
  • date of a partner’s appointment
  • actual date of implementation
  • a description of the requested operation
  • a description of the performed operation

Detailed invoicing

There are very detailed information about every item stated in the invoice

Invoice include:

  • price per item of the invoice
  • time duration required for a service stated on the invoice
  • total price (the sum of prices per item)
  • total time required (the sum of the time required per item)

Every service is well-documented

Execution of the service is documented into more operational documents simultaneously

Documents related to the execution of the service:

  • order sheet
  • order
  • invoice
  • delivery protocol
  • typically jpg, pdf, potentially xlsx

More operational layouts

Service requirements can be displayed with vehicle overview and scheduled maintenance, or vehicle service card with an overview of all services

TOP PREV NEXT