Vehicle Databases – Rationalisation
Proposed changes to systems
August 2009
Introduction
Brenton Eden, Manager Training, co-ordinated a meeting to discuss the rationalisation of Vehicle databases and interfaces. There are current links from TAS to IRIS and Masterpiece. There is a separate Vehicles.mdb database and the new Appliance Delivery System application.
Resolved
a) The Appliance Delivery System replaces all uses of the Vehicles.mdb
b) The Appliance Delivery System will be the Master list of vehicles.
c) Data will be shared by replicating data using database triggers to avoid programming, and to make the transfer visible and auditable by SAFECOM IT staff
d) The existing links between TAS and IRIS and Masterpiece will remain, with some additional information being passed
My thanks go to Andre Fürstenrecht of Prodata Solutions for his co-operation in this.
Recommended
These changes be implemented as soon as possible.
Ian Fry
Fry Systems Pty Ltd
5th August 2009
TAS Changes
a) Disable Appliance Type Maintenance (with the exception of the Is SFEC flag below).
b) Brenton Eden and Sandy Paterson to agree on the titles for each type and complete a comprehensive list in Appliance Delivery System.
c) Include a new field in Appliance Type (via Code Tables screen in ESOTAS)
- IS SFEC – Yes or No This controls whether or not the vehicle type requires SFEC planning or not. Trailers, Command Vehicles etc will now be in the list, and will be shown in a separate group
d) Disable UnitsAppliance Maintenance (from the Brigade Details screen, Requirements tab) except for the ability to redeploy an existing vehicle to/from another Unit and re-allocate its call sign. Create Database trigger to update ADS when a redeployment is done. In ESOTAS, effectively only editing Callsign, plus an option ‘Move Appliance’ which would allow moving appliance. As per point c) above the Brigade Appliances grid on the Requirements tab of the Brigade details screen would be grouped by SFEC Appliance (Yes/No), then the current Appliance type / callsign as the detail, as per current display).
e) UnitsAppliance table to include Rego Number. Mobile Phone number. In ESOTAS to be available as customisable fields (but not visible by default)
f) Disable Units Maintenance (unsure what this means?)
g) One time exercise to recode the current data to the new equivalent codes where necessary
h) Clarification from Brenton required about the Appliance Summary tab (and consequently reports) – would this include only SFEC appliances, or all appliances? Or do similarly to how the Requirements tab will be and group?
i) Additional change for ESOTAS is the SFEC calculation routines to be modified to only use the number of SFEC appliances a brigade has, not the total number of appliances.
j) The IRIS export to be modified to export the registration number and vehicle mobile number for the vehicles file.
ADS Changes
a) Include Mobile Phone against vehicles
b) Create external keys where necessary for TAS interface.
c) Create database triggers to maintain Appliance Type , Units and UnitsAppliance in TAS
Vehicles.mdb
Delete the database and all users to use Appliance Delivery System.
Unresolved Issue – possible later version
Within ADS we track the deployment of new vehicles on the build program, and the downstream re-deployments resulting from that. Theoretically, if a new type of equipment was coming to a unit, it needs training.
However, there is some flexibility on when that move may happen and it seems safest not to insert that “notional” vehicle (plus possibly a “notional outward movement”) into TAS, at this time
Brenton Eden and Sandy Paterson to monitor this item.