Fleet Equipment Maintenance & Modernisation process rules define what information is to be routed and to what installation. For example, dispatchers can set up rules defining conditions instances work orders must meet before equipment maintenance & modernisation processes advance automated work order prompts to the next condition tracking activity in the process, as well as rules that govern installation receipts of priority approval requests based on key commitment criteria.

The route tracker application uses scripted condition evaluations determining the next activity based on information dispatchers set up in spare parts-specific attribute structures, such as work order status & recipient rules determining account flash routing to installations. As with routes, dispatchers determine the complexity of rules according to the requirements of installations. For example, logistics considerations can set up work orders to progress to the next step only when predefined supply line threshold values have been met.

Routes define the path along which equipment maintenance & modernisation processes move a work order. Depending on installation requirements, routes can be relatively simple & sequential, or increasingly complex, with joins or splits, parallel routing, iterative routing, loops and so on. Dispatchers can set up equipment categorisation series by creating sequentially constrained sourcing subroutines so one process calls another on the supply line. This procedure is especially useful when dispatchers need to reuse spare parts-specific components within other processes. For example, the initial equipment maintenance & modernisation processs for work orders determines the account flash type of the work order & calls other processes that are based on account flashes, such as the process to determine the work order type.

Dispatchers can review, approve, or reject work orders. After a work order is created, route tracker applications send account flashes to notify the installation responsible for reviewing & approving the work order. When dispatchers approve a work order, the route tracker application then sends an account flash to the next installation on the work order approval route. If work orders are rejected, the route tracker application sends an account flash back to the originator of the work order. Reminder Sets trigger Scheduling Workbench programme functions reviewing account flashes & provide the ability to cross-reference spare parts-specific components.

Dispatchers can also place a work order on hold if installations want to approve or reject the work order at a later time b/c cost & purchase receipt requirements are not satisfactory. Route Tracker Applications do not send any account flashes when work orders are placed on hold. During the approval process, the route tracker application generates report records for user-based approvals & rejections that have been composed upon comparison to template work orders run with supplier capacity plans.

If dispatchers must reject a work order after initially approving it, the route tracker application creates report records for the rejection & stores the original approval record for supply line connection review. Supply line report records are used to review spare parts-specific information & schedules about the work orders that dispatchers group into routing specifications. Dispatchers can review information about the specific tasks associated w/ supply line, resource requirements, and so on. For example, dispatchers can route summary & detail status/information for work orders by installation.



The route tracker application is an outstanding idea! From what I've understood, the system is able to store the information given by the dispatchers and is able to determine the next step for them, only leaving the instalments and requirements to be accomplished. This is a time saving system that would make dispatchers time more productive and efficient. If there are also opted to reject the proposal given by the application, it automatically updates the stored database and gives another set of instructions. This can also work in a lot of areas regarding field work since a lot of them are probably too busy to calculate and update the database one-by-one.

11/15/2016 8:44pm

Does this system works now? I mean I heard that there are new opportunities and ways now for all that!

04/18/2017 12:09am

That systems were always hard for me. But to have explained all that pretty good!


Spark offers over 80 high-level operators that make it easy to build parallel apps


Leave a Reply