Campaigns & Schedules > The VOSP Interface

The VOSP Interface

Why:

Within VOSP, a service schedule can be created for a vehicle that can then be deposited in VIDB and extracted into a schedule file (THF 492) within Fusion.

As VOSP does not require shift patterns the Fusion Parameter ‘Parameter SEC 003 determines the default shift code for schedules extracted from VOSP. That will update the file with a default shift. This can then be changed at a later date if required.

 

Where:

Schedules extracted from VOSP can be seen in the Scheduled Work screen accessed from the Vehicle View via the Actions > Schedules command.

Downloaded VOSP schedules are indicated with this icon .

 

How Data is Extracted During VOSP Schedule Downloads:

Certain rules have been applied when extracting the data from VIDB into Fusion. These are:

      If the Chassis number is blank then the schedule is not copied (as the key to the schedule file is the Chassis ID-number).

      If any TST Operation numbers used with the VOSP module are not found in Fusion, then again the schedule is not copied. This is to prevent certain operations being overlooked and not carried out.

      Providing that the chassis number is not blank and all TST Operations are found, the schedule will be copied into Fusion and a report generated. This report will indicate whether the vehicle is found within The Vehicle Master File. If the vehicle is not found within The Vehicle Master File then you must add the vehicle and assign the correct scheduled branch against it. All listing, letter and enquiry functions may then be used.

 

What else would you like to do?

Schedule Letters.

 

Related Topics:

Schedule Templates.