What does the IVMS kit designer do?
A fleet quote goes wrong at the parts list. Miss the fuse for one class and the installer stops on site. Forget the tags and the driver ID reader does nothing. Count a recorder for a vehicle with no cameras and you pay for it twice.
This tool builds the kit for each vehicle class first, then adds up the fleet. It gives three results:
- Fleet and kit per class: the devices to supply and the kit for one vehicle of each class.
- Storage and mobile data: the storage size per recorder and the monthly data of a tracker and of live view.
- Bill of materials: generic lines with base quantity, spares and quantity to order.
The list carries no prices and no part numbers. Tracom adds the model, the specification and the code to every line from the datasheet before you quote.
What do you enter?
| Input | Where to find it | Tip |
|---|---|---|
| Vehicle classes | Your fleet register or the tender schedule | Group vehicles that need the same kit. Up to 12 classes. |
| Video, extra cameras, tanks, compartments | A survey of one vehicle per class | Counts are per vehicle. Enter 0 where they do not apply. |
| What to monitor | The project scope or the tender | Each need you tick adds its own lines. |
| Drivers and spares | Your HR list and your supply rule | One ID tag per driver, not per vehicle. Spares are a planning choice. |
| Bit rate, usable share, message size | The device datasheet | The defaults are typical values. Replace them with the datasheet figures. |
How is the list built?
Every class gets a base kit: tracker, power harness, fuse, SIM card and a fitting kit. A class with video adds a recorder, its harness, the DSM and ADAS cameras you ticked, extra cameras, one cable per camera and storage media. Each other need adds sensors by the counts you give per vehicle.
Fleet quantities are the per-vehicle counts times the vehicles in each class. Spares are added to each line and rounded up, so 84.0 stays 84 and 84.2 becomes 85. Storage media are listed once per size, because two classes may need different sizes.
Units are decimal, as printed on a card: 1 GB is 1,000,000,000 bytes. Bit rate, usable share, message size and storage sizes are typical values until Tracom confirms them from the datasheet.
Typical value. Replace with your device datasheet value.
What does each need add to the list?
Each need you tick adds its own lines. Some lines depend on a number in the class table, and some do not apply to every vehicle type.
| Need | Lines added | Quantity rule |
|---|---|---|
| Driver monitoring camera (DSM) | DSM camera and its cable | One per vehicle with video |
| Road-ahead camera (ADAS) | ADAS camera and its cable | One per vehicle with video |
| Fuel level sensor | Fuel level sensor | The tanks you enter per vehicle |
| Temperature sensor | Temperature sensor | The compartments you enter per vehicle |
| Load weight | Load weight sensor set (confirm availability with the Tracom team) | One per truck or tanker, none for other types |
| Driver identification | Driver ID reader and tags | One reader per vehicle, one tag per driver |
| Panic button | Panic button | One per vehicle |
| Engine cut-off relay | Relay for engine cut-off | One per vehicle |
| Live view over mobile data | SIM card in each recorder and a data estimate | One per recorder, when the recorder has its own SIM |
| Installation visits | Installation visit | One per vehicle, no spares |
What does the kit look like by class?
The matrix shows the example classes below. A 0 means the line is not in that class.
- In the kit
- Not in this class
| Line (per vehicle) | Pickups | Buses | Tankers |
|---|---|---|---|
| GPS tracker | 1 | 1 | 1 |
| Tracker power harness | 1 | 1 | 1 |
| Fuse holder and fuse | 1 | 1 | 1 |
| SIM card for the tracker | 1 | 1 | 1 |
| MDVR (mobile video recorder) | 0 | 1 | 1 |
| MDVR power harness | 0 | 1 | 1 |
| DSM camera | 0 | 1 | 1 |
| ADAS camera | 0 | 1 | 1 |
| Extra camera | 0 | 3 | 2 |
| Camera cable | 0 | 5 | 4 |
| Storage media (1 TB) | 0 | 1 | 1 |
| SIM card for the recorder | 0 | 1 | 1 |
| Fuel level sensor | 1 | 1 | 1 |
| Driver ID reader | 1 | 1 | 1 |
| Panic button | 1 | 1 | 1 |
| Fitting kit | 1 | 1 | 1 |
| Installation visit | 1 | 1 | 1 |
Worked example: 80 vehicles in three classes
The default values are an example: 40 pickups without video, 25 buses with video and 3 extra cameras, and 15 tankers with video and 2 extra cameras. Each vehicle has one fuel tank. The project needs DSM, ADAS, fuel, driver ID, panic button, live view and installation, for 90 drivers, with 5 percent spares.
- Devices: 80 trackers and 40 recorders, so 120 devices.
- Cameras: 40 DSM, 40 ADAS and 105 extra, with 185 camera cables.
- Storage: a bus with 5 channels writes 22.5 GB a day. A tanker with 4 channels writes 18 GB a day. Both need 1 TB for 30 days at a 90% usable share.
- List: 18 lines and 1,260 pieces before spares, 1,325 with spares, plus 80 installation visits.
- Data: a tracker moving 8 hours a day uses about 8.6 MB a month, and one hour of live view at 512 kbps uses about 230 MB.
How do you read the results?
- Devices are trackers plus recorders. They are the units that need a SIM card and an installation.
- Pieces count the lines before spares. Installation visits are a service, so they are not pieces.
- Quantity to order includes spares, rounded up for each line.
- A warning appears when a need has nothing to attach to, for example fuel sensors with no fuel tank in any class.
- The specification column says "To be confirmed by Tracom" until staff fill it from the datasheet.
Assumptions and limits
The list uses generic lines. It has no prices and no part numbers, and it does not state that any kit meets a client or authority list. Bit rate, usable share, message size, live view rate and storage sizes are typical values, not Tracom model data. Cable lengths, brackets and extra fittings depend on the vehicle: survey one vehicle of each class before you order. Check the list your client or authority publishes, and ask Tracom to confirm every line.