Two types of user service requirements
Planned or extraordinary – based on actual user’s needs
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.
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
Technologies
used
Selected
Use cases
Functional sections
Service requirements can be categorized into functional sections – subject to the user’s decision
Practical merging functions
Service requirements can be merged and executed at the service partner at the same time
Comprehensive service records
Service records include comprehensive information for a better operational comfort
Detailed invoicing
There are very detailed information about every item stated in the invoice
Every service is well-documented
Execution of the service is documented into more operational documents simultaneously
More operational layouts
Service requirements can be displayed with vehicle overview and scheduled maintenance, or vehicle service card with an overview of all services
Interested in a similar solution?
Tell us about your project and we will put the right team on it.
Are you interested?