Authorisation deals with establishing whether work contemplated may in fact be authorised and to what extent. It does so by interrogating all previous history for the vehicle concerned and the costs and nature of all previous work are viewed and considered.

As a vehicle is identified an optional Button Click shows a complete job history for the vehicle, and where a Reason / Event code is entered again an optional button click shows a complete job history for this event on the nominated vehicle plus a total of costs to date for the event.
Average actual costs incurred historically for all vehicles of a similar Make /Model / Version, for the same Event or Reason, are given, enabling accurate estimating of the antipicated cost of the job in question.

The system automatically prompts if a vehicle replacement date or distance is close at hand and poses the question 'is the work justified' in view of pending replacement.

Individual items of work may be specified against a user-definable 'event' code together with the authorised cost for each item. Where it is inappropriate or undesirable to enter items against an established event code each line may be free-typed and may or may not contain an authorised amount per 'line item'.

Alternatively the system generated description for any defined event may be over-ridden by the user. Description of the authorised work if not completely covered by narrative entered against line items can be amplified by an optional entry of comments.

Each may be defined as one of four types :- Alphanumeric, Numeric (Integer); Numeric (Decimals); or Date. Data entry is validated according to the field type as described.

Where established these user-defined fields are prompted and available for all vehicles. ALL such fields may be used in the Vehicle Identification Enquiry to provide a very powerful retrieval and query system.

These fields need not be thought of ONLY as equipment items and can be employed for whatever purpose the user has in mind.

Other User-Defined Fields

Diary Dates / Titles
These set-up system standard diary (reminder) topics. Those items established appear on the basic details screen during Vehicle Maintenance. Each topic may or may not be indicated for automatic advancement following formal reporting. A non-zero entry in 'Advance By (Months)' implies automatic advancement.
Whereas similarly entitled prompts will appear for ALL vehicles at Vehicle Master Maintenance, entries always remain optional for individual vehicles. The Diary topics can be complemented and much enhaced by Reminders and Memos.

Organization Codes
(e.g Division/Region/Branch) may be defined. Where defined they wiil appear, as do alternative keys (see above), in vehicle basic details (Tab1) during maintenance activity. Prompted fields, whether alternative keys or Organization codes, are entered free-format with no validation during maintenance.

Annual Costs
Two additional Annual Costs topics may be defined, in addition to the fixed annual costs of Road Tax and Insurance. Where defined these wiil appear in Vehicle Master maintenance under 'Financial Details', and may be selectively used for nominated vehicles, as are Tax and Insurance. Values entered against a vehicle as annual costs are subject to Period and year end apportionment of costs.(Separate provision exists for handling Depreciation/Leasing charges as 'Annual' costs).

Enquiries do NOT affect any of the master files and may be freely employed by authorised users.

Enquiries fall into two main categories; ' Vehicle Specific' and 'General'.

'Vehicle Specific' is where the user has a particular vehicle in mind, and will select that vehicle deliberately. 'General' is where the entire file may be scanned with filtering mechanisms employed at the user's discretion to isolate and present vehicles satisfying the selection criteria. Qualifying Vehicles are presented in a scrollable ListBox. Selecting a vehicle by clicking a ListBox entry will present the 'Specific' type enquiry Menu for the selected vehicle.

The Enquiry system has been designed with total flexibility in mind. e.g. where the user orientates to a specific vehicle, then all enquiries are available for that specific vehicle from a pop-up menu and the user remains orientated to that vehicle, until a deliberate selection is made for another.

In the General approach having selected a vehicle from the ListBox (filtered according to optional General Selection Criteria), then the full range of Vehicle-specific enquiries for that vehicle is available, with return to the ListBox to select another, or to re-state the general selection criteria, for a different range of vehicles.

Where a vehicle is the subject of a specific enquiry the basic details of that vehicle; Registration No. and Date Registered; Make and Model; Current (and Previous Odo if any); Status; Driver; Usage; and Operating Location are displayed on an associated (but separate) window at the top of the screen, amplifying the particular enquiry details in the current main window.

Vehicle-Specific Enquiries

• Cost Code

For each selected Vehicle displays accumulated costs resulting from 'R & M' - Material, Labour & 'Other' transactions. Costs from these type of transactions are automatically associated with 'Cost Code' groupings according to the 'Events' nominated as they are entered to various jobs. Costs are detailed under the three headings as indicated and are always shown related to the 'standard' periods:- Current Period, Year to Date and Life to Date.
• Events

The Jobs DataBase is scanned, showing for each vehicle selected, in chronological order, events occurring on that vehicle. The date, event type, distance, and total cost are given, per event, together with the workshop and job number. Total number of occurrences and total costs are given. If a single event is nominated averages of 'Days and Distance' between events, and average Cost per event is given in addition. An effective range of dates may be given and only events occurring within the date range will be selected.
• Fuelling

Displays detailed fuelling history for selected vehicle(s), item by item for each fuelling & in reverse chronological order, (latest first).
Details shown are :- Date, Odometer Reading, & Volume of Fuel, Cost, Driver (if known) and the Operating Location (at the time of fuelling), if a Manual transaction, or the Retail outlet if a FuelCard transaction. Additionally the 'Source' of the transaction, i.e. whether a Fuel-Card transaction, (e.g. PHH, Tri), or a manually entered user (Usr) transaction.
Multiple 'pages' of fuelling details may exist and the user may freely scroll through the entire fuelling history for any vehicle. A special 'anomaly-check' is performed during the scrolling process where each fuelling is related to it's neighbouring fuelling (above and below) and if mileage, or cost is unusual the suspect item is highlighted in red.
• Jobs History

The Jobs DataBase is scanned selectively and for each selected job displays Job Header details of Job Number, Authorisation No. and Authorised By (if Authorisations required), the 'main' event for which the job was raised, Start Date, Odo. reading; Downtime (if available); Workshop, Id. and Registration No. of the Vehicle, the Status of the Job (whether 'Open' or 'Closed'), and an indication of warranty applying to the job. Detailed elements, Labour, Materials, 'Other' & Comments display item by item.
• Performance vs Budgets

Illustrates R & M expenditure Vs. Budget. Budget value, type, and duration are established in the Financial section of Vehicle Master maintenance. Budgets may be set to operate under Reverse Rule 78 over a given time scale, or merely to express an annual amount.
The Budget 'Rules' and parameters are displayed together with Year on Year comparison of spend vs. Budget, from Date in Service to the current date. R & M expenditure for each year is broken down to Labour, Materials, and Other, giving a total expenditure for each year.
• Performance /Statistics

Scans the Vehicles DataBase and for selected Vehicle(s) for a given period illustrates Costs aggregates for Annual, R&M, and Operational Costs. Distance Run and Fuel & Oil consumption is given, and, optionally if the System Control Parameter is set, a usage % figure expressing Hours Used vs. Available.
M.p.g. and Litres per 100Km. figures are given and costs broken down to a cost per mile and expressed as pounds and pence to three decimal places. Current Period , Y.t.d., or a Lifetime basis may be selected.
• Transfers

Provides a record of a vehicle's movements from / to various Operating Locations in its lifetime. Details include the Date and Odometer reading of each movement, the Operating Location, Usage and Driver at each movement, and the Days and Distance at each location, together with a description of the Vehicle's condition at the time of transfer.
• Vehicle Master

The Vehicle Master file holds a considerable amount of detail relevant to each vehicle on separate 'Tabs' for Basic, Equipment and Financial details. The Financial 'Tab' may appear in two variants depending whether a Leased or Owned vehicle.
The content of each Tab will largely depend upon the manner in which the 'General Parameters' and various user-defined fields are engineered on the system control file. General Parameters control the appearance and content of the topics under the 'Alternative File Keys' & 'Organization Structure' titles, whilst Diary Titles controls the 'Diary Dates' section. EXCEPTIONALLY there may indeed be NO entries under any of these section titles and they will appear as 'Disabled or Greyed-Out'.

General Enquiries

• AutoScan

This is a combinined scan involving three individual enquiries in ONE single pass of the file viz:- 'Diaries'; 'Reminders' and 'Replacements'. When used ALL Diary Topics are evaluated, as are ALL Reminder Topics, and ALL Date or Distance-related 'Vehicle Replacements', with an initial Default 'Effective Date' of Today's Date.
This feature may be set to run automatically at each System start-up ( Login), giving an 'Action List' at start-of-day. The enquiry may also be invoked ad-hoc from the Main System Menu.
• Diaries

Scans the Vehicle DataBase and will determine whether any reminder dates are due or up-coming by a user-defined effective date. The range of topics applying is user-defined on the System control file, as 'Diary Dates'. Up to four such topics may be defined as a system standard and will apply to ALL vehicles.
Default on the effective date is today's date which implies 'Due' or 'Overdue'. Normally a 'forward' date will be selected allowing timely action to be taken in advance.
• Excess Mileage (Actual or Predicted)

Only vehicles with a 'Leased' Ownership type are considered for these Enquiries. Vehicles with a Disposal Date recorded or lacking a Start Date, Start Mileage, Excess Mileage Distance or Excess Mileage Rate are excluded.
Any vehicle calibrated in Kilometres has the kilometre value converted to miles for consistent calculation purposes.
Actual Excess Incurred Only vehicles currently in an 'Excess Mileage' situation are reported. The present Excess mileage and Cost are given for each vehicle. A current daily mileage (to-date) is computed and is used to calculate the predicted mileage if this daily rate is maintained to the end of the Lease period, with a predicted total excess cost based on this predicted mileage.
Predicted Excess Only vehicles having travelled at least 500 miles are considered. (A lesser value inhibits the calculation of an accurate daily mileage rate). A current daily mileage (to-date) is computed and is used to calculate the predicted mileage if this daily rate is maintained to the end of the Lease period. A predicted date on which the Excess is calculated to begin is shown, together with a final predicted total excess cost based on this predicted mileage.
• Performance vs Standards

Compares for a given Make/Model, each vehicle of that type's performance vs. the manufacturer's stated performance figures. Comparison is made to the particular values set up for the type in Model Standards maintenance for Fuel m.p.g, Oil miles per litre, and R & M pence per mile. Each of these is set up with a tolerable variance %. The total number of vehicles and aggregates for the vehicle type are given.
Selection of Make/Model type is augmented by the capability to request exceptions only, i.e. only vehicles NOT meeting performance on any element will be displayed, and to nominate a particular period :- Current Period, Y.t.d., or a Lifetime basis.
• Reminders

Scans the Vehicle Master DataBase and will determine whether any reminder dates are due or up-coming by a user-defined effective date. The range of topics applying is user-defined on the special 'Reminders' file, maintained under Housekeeping as Reminders / Memos. This feature is an extension to the Diary Dates reminder system, and allows special topics to be user-defined and coded, and optionally, attached to selected vehicles.
• Replacement

Scans the Vehicle Master DataBase for Vehicles due for replacement in Date or Distance terms as indicated in the Vehicle Basic Details 'Tab'. Replacement Date is compared to a user-supplied 'Effective Date' and an 'Effective Distance' is computed by adding a user-supplied 'Odo Advance' value to the current Odometer reading. If the Effective Date is NOT LESS than the indicated Replacement Date, or the computed distance is NOT LESS than the indicated Replacement Distance then the vehicle is reported.
• Service Scheduling

Allows services due for vehicles to be predicted but only if Service Scheduling 'Patterns' have been established for the Vehicle type and defined in 'Make & Model Standards'.
Reference is made to the latest known odometer reading for the vehicle, and a distance run per day is calculated either from the odometer as at the last service or the vehicle entering system whichever is higher. Vehicles which have not run at least 500 miles in the intervening period are excluded since a 'distance per day' cannot be calculated accurately enough.
The next service distance is established as per Make / Model Standards, and a number of days to next service is estimated and added to today's date. If the result of the calculation is on or before the user-supplied 'effective' date then the service requirement is reported.
Where the 'Service Patterns' indicate that two different service types may be due at the same distance, then the 'more significant' of these will be indicated, i.e. more significant in the sense that it is due at a higher distance. e.g. a vehicle due REPEATED minor servicing at 5,000 miles intervals, and a major service at 20,000, would (apparently) have a 5,000 due at the same time as the major service.
An 'effective' date may be given. Only vehicles due for servicing on or before the effective date will be scheduled. Default is today's date.
• Vehicle Identification

Allows a vehicle to be located and identified by string-searching any or all of the target fields as indicated below:-
· Registration Number
· Comments
· The four User-Definable 'Alternative Keys'
· The four User-Definable 'Organization' fields
· The thirty User-Definable 'Equipment' fields
In all cases the 'target' field of the selection has the contents of its field matched to an enterable 'string' (NOT case-sensitive) and ALL vehicles satisfying the string are listed. The condition is satisfied if any part of the target field has successive characters matching the entered string. User-Definable 'Equipment' fields of a Numeric(N/V) or Date(D) type can be scanned to have values within a user-supplied From - To range.
The search can be further limited to vehicles of a selected Make/Model; Location; Workshop; Usage or Status by employing 'General Selection Criteria'. A 'Clear and Run' Button clears all 'locally-set' selection criteria, and ignores (but does not obliterate) General Selection Criteria for this run only.
• Vehicle Search

The enquiry provides information regarding the type and disposition of the fleet, in particular allowing a vehicle to be traced to a last known Operating Location or Driver. Selections allow ALL vehicles to be listed by Operating Location and by Make / Model etc. The search can be further limited to vehicles of a selected Make/Model; Location; Workshop; Usage or Status. General Selection Criteria applies if given. A 'Clear and Run' Button may be used, exceptionally, to quickly clear all General Selection Criteria for a complete file-scan.

The user may select :-

• a particular vehicle by its unique Registration Number
• a range of vehicles as a vehicle 'group' i.e a Make and Model combination. This may indeed be ALL vehicles of a particular Make regardless of Model. Up to 50 individual Makes may also be Tag-Selected.
• vehicles based at a selection of operating locations, Up to 50 individual Locations may be selected and combined in any single report invocation. The required range of Locations is Tag-Selected.
• A single workshop where maintenance or repair work may be carried out (Workshop is the general term used whether an internal workshop or external private garage and the user should interpret the terminology to suit his particular usage)

'Standard Selections' where offered will always operate as here described but will often have additional topic-specific selections or user parameters supplied at run-time. Date From and Date To, and other criteria may be offered but only if appropriate to the Report currently selected.
Running a report ORDINARILY does NOT affect master files, with rare exceptions clearly indicated where they may occur.
A Report Preview facility is generally available where the complete report may be previewed in an enquiry Window before a decision is taken to commit to hard-copy. Main Module Reports - (Currently available)
Unless otherwise indicated 'Standard Selection Criteria' applies

Vehicles are compared against stated Performance Objectives applicable to their Make and Model. These will ordinarily reflect the Manufacturers' published performance figures and will, in many cases already exist as part of the installation 'package' - an existing data-base of popular Make & Model standards is supplied as an intrinsic part of the software, However, the user must often create standards to suit his own fleet composition.

Make, Model, Vehicle Type, Fuel Type, Odometer Calibration, Staff Grade and Cubic Capacity are ALL required fields. Of these Fuel Type and Odoometer Calibration are selected from preset 'pop-up' windows. Others:- Make, Model, Vehicle Type, require General Descriptor records to exist on the System Control file, and cubic capacity must be entered specifically.

ALL other fields are optional, including Service Schedules, however if service schedule patterns are not, or cannot be, set then the system can not facilitate the important service scheduling reminder feature available both as enquiry and formal report Service Scheduling is distance related and when entering service types they must be entered in ascending order of distances due. They will also indicate if they are of a type to repeat at the stated distances. If a repeating service type happens to co-incide with a higher interval type then the higher interval will always be deemed to be the most significant.

It should always be set by the user following a year-end run to establish the new calendar for the incoming year. A 12 or 13 period accounting year may be set and each period given a designated period-end date. Each successive date must be greater than the preceding date.

The system does not insist that period ends must be run strictly according to the calendar, but if a period end is 'overdue' the user will be reminded of this each 'login' until such time as the period IS run, and until the NEXT period end falls due beyond today's date.

The user may 'skip' periods if so desired, but the next time a period end is run the system is aware of the date on which the LAST was run and will apportion any annual costs according to the elapsed days between.

Annual costs are apportioned according to the interval between the 'Current' and the 'Last' period end, or from the 'Date in System' for a particular vehicle, whichever is later.

Period End
This process is invoked at the user's discretion normally at intervals in line with the 'Periods Calendar' which will have been established and held on the System Control File.

ANNUAL costs are apportioned according to the interval between the 'Current' and the 'Last' period end, or from the 'Date in System' for any particular vehicle, whichever is the later. Depreciation and Leasing charges are calculated where applicable, again with reference to the current period end date.

If the Period End number now nominated is the LAST for the year BOTH period end AND Year End activity is indicated. Period End sets Current Period costing values to zero, Year End sets BOTH Current Period and Year to Date values to zero. Please be sure you have run any reports required before running this process.

The period end process requires that no other users are active. If other users ARE active then following an advisory message the user will be returned to the Menu.

A record of 'Disposed of' vehicles may be maintained in a DataBase dedicated to this purpose. The vehicle must first be selected from the Current vehicles DataBase and the 'Disposal' status confirmed. The original vehicle's status is flagged as 'set for disposal', but the vehicle remains on the current Vehicle DataBase until such time as it is specifically deleted.

A disposal record once created may be Changed or Deleted at any time. If a disposal record is Deleted and the 'original' vehicle (of same Regn.No), exists on the current vehicles DataBase, then the vehicle's status is reset to 'Normal'. If the original vehicle is deleted and a Disposal record has previously been created for that vehicle, the Disposal record remains unaffected and is accessible until it too is specifically (and deliberately) deleted.

Wheels and Tyres

Any individual vehicle may have its 'Wheels and Tyres' individually defined, not just the current configuration, but the whole history of tyre changes etc. may be recorded.
The position e.g. Nsf (near-side-front), Rim size, Type (e.g. Alloy or Steel), and Cost of each wheel may be given. For multi-axle vehicles any number of wheels may be declared.

On each defined wheel the fitted tyre(s) (current and previous) are defined with details of Serial Number, Manufacturer, Supplier, Distance fitted, and Cost, together with a generously sized comment and Warranty details. A 'distance since fitted' is calculated for each tyre.

Global RFl and Insurance Updates

This procedure scans ALL vehicles on the Vehicle Master file and changes the current value of the Road Fund licence or Insurance recorded against each vehicle from the current value to a 'New' value.

The current value given must precisely match the value on the Vehicle record otherwise no change is made. Changes made are immediately effective for costing purposes in the next Period or Year-End process.

Road Fund Licence - Refund Claims

This enquiry examines the status of all recorded Rfl refunds claimed, and displays the Date and Amount claimed together with the Date and Amount received. Options are given to scan all claims or outstanding claims only. The vehicle's Registration Number, Date Registered, Make, and Disposal Date are also given.

DataBase Statistics

In both cases 'Standard Topics' are established FIRST to apply system-wide, and thereafter these standards are referred to in creating a vehicle-specific 'attachment'. In attaching to selected vehicles the description of the standard topic always remains as the FIRST line of the text of the attached topic, but the user may enter considerable additional text specific to the vehicle / topic in question.

There may be any number of standard topics, all user-defined, and any topic may be attached to any number of vehicles.

The user may select either 'Reminder' or 'Memo' (these are Colour-Coded for ease of identification).

Standard Reminders
allow for pre-planned activity topics to be set-up, which may be to operate for Date or Distance. A full general description of the topic of the reminder is entered. A standard reminder may be set to be of a repeat type at stated intervals, (days, months, or years), or at distance increments.

Standard Memos (or Notes)
Allow a standard memo to be consistently set with a generous additional text capacity

Vehicle Attachment
The standard reminder is attached to the specific vehicle. For a 'new' attachment any text set up in the standard is automatically set into the attachment, and, with the exception of the FIRST line, all other text may be modified to requirements.

The reminder may be given a Due Date, Distance or both, and may be indicated as an incremental (repeating) type by entry of the days, months, years, or distance increment fields. If none of these are employed the reminder may be temporary only and the user may indicate that it should be 'Deleted once Reported'.

Reminders, once attached, may be freely enquired upon or reported under the Menu choice, 'Enquiry - Reminders', where the user gives a 'look-ahead' parameter,(a 'forward' date), at runtime.
Enquiries allow a view to be taken of up-coming reminders, whilst reporting gives a formal hard-copy of scheduled activity, and allows the user, optionally, to cause reminders to be automatically advanced to the next due date or distance, and to delete any reminders of a temporary nature.

Memos are attached to the specific vehicle. As for reminder attachment the text may be modified to suit requirements for a specific vehicle with the exception of the FIRST line. An expiry date for the memo may be given. Memos are automatically notified when the user accesses any vehicle which has non-expired memos attached. Virtually any enquiry or Vehicle-Related housekeeping activity will notify the existence of such a Memo.

Full Insert, Change, Delete, and Review, facilities are given.

A standard record whether of a Reminders or Memo type may not be deleted where it remains attached to any vehicle. Attachments of any type may however be deleted at any time.

All cosmetic features are set-up in the System Manager executable, and may be changed or disabled at any time.

Choice of Background Colour
Brighten up your windows with a selection of more than 40 backgrounds to choose from.

If you are running a multi-module system it is always a good idea to assign a different background to each discrete module, they stand out very well from one another. With the flexibility of the Windows operating system you could have a great number of screens (windows) in view at any given time from a variety of applications. Colour coded backgrounds are a great help to navigation.

Your own Logo
Put your own Logo on your system reports. (a '.gif' or '.jpg' image is preferable, a '.bmp' image is usually acceptable). Space is reserved on ALL reports for a reasonably-sized user Logo.

Millenium Compliance
Dates are maintained within the system as the number of days that have elapsed since December 28, 1800. The range of accessible dates is therefore from January 1, 1801 to December 31, 2099. The standard date calendar also adjusts for each leap year within the range of accessible dates.

List Boxes
The software makes extensive use of List Boxes. They provide a very efficient means of selectively interrogating and manipulating large files (or indeed files of any size).
'Locators' allow rapid access to specific records. As successive characters are keyed the List Box automatically positions to contain records whose keys match the characters contained in the Locator field. (A Locator of this type is referred to as an 'Incremental Locator'). The principle of incremental location is very similar to the 'Search' technique used within Windows 'Help'.
Different Tabs will have different associated Locators reflecting the key sequence for that Tab. ListBoxes generally have both VCR and ThumbNail Controls.
The ThumbNail types are both Vertical and Horizontal and will be familiar to Windows users.

The VCR buttons (where employed) simulate controls on a Video Cassette Recorder, and have facilities to move immediately to the BEGINNING of the file with the LeftMost Button (that depicted with the combination of a Vertical Bar and Left Arrow) or to the END of the the file with the RightMost button (RightArrow and VerticalBar combination). The other buttons mimic the functionality of the Vertical ThumbNail. The beginning of file may also be automatically located by space filling the associated Locator field (assuming the Locator is currently active).

Fields within a ListBox may be dynamically re-sized by Left-Clicking on the dividing (vertical) line between fields, holding the Mouse button down and dragging the line to right or left. If you do this then you need not bother to restore to the original field dimensions, the software automatically sets the fields to their original size on the next invocation of the program.

Hot Fields
Many ListBoxes may make use of associated 'HotFields'. This is computer-speak for what simply means certain designated fields which amplify in more detail the basic identifying data from the record currently HighLighted in Inverse Video in the ListBox itself. HotFields are normally shown in a panel to the right of (or below) the ListBox. Use the vertical ThumbNail control to move up and down the ListBox and observe the HotField data change to reflect the ListBox record currently in Focus !.

System Control File
Certain elements of the System Control file are mandatory such that the system cannot function without them. These mandatory elements will to a large extent have been set up (INSERTed) initially in consulation with, and normally by, the software supplier's installation personnel. From time to time it will be necessary for the user to AMEND such elements, but they may never be DELETED.

System SetUp and Management
A separate 'Executable' procedure is supplied giving a duly-appointed System Manager privileged access to certain system functions. Notably these are Password assignments, System Backups, UserCount Control, Apearance Options and other more sensitive areas of System Administration such as Event/Reason definitions etc.

'Reasons' and 'Events'
The main objective in having a Vehicle maintained or repaired is thought of as the 'Reason' for the Job, and is associated to the Job 'Header'. However co-incidental to the main job being carried out other work may have been done which cannot be adequately described within the overall reason. Hence the 'Event' is to describe elements of ancillary work. Hereafter all reference to Reasons or Events will be referred to as Events for convenience.

There will be multiple Event definition entries on the System Control file, and whilst not seen as essentially mandatory, the system will depend upon elements of work entered to the system as a Job 'Header' or Job 'Details' (R & M transactions) to be associated with pre-established event codes, to enable later analysis by type.

FleetFocus support staff can provide a starter 'data-base' of typical codes, but these will often need to be augmented or modified by users for their own purposes.

Thoughtful engineering of event definitions from the outset will enable powerful, and meaningful, interrogation potential in due course. Each event when defined will also be associated with a cost centre or cost grouping, again to enable subsequent analysis in this area.