Unit A
Rank 1
- Weighted score
- 95%
- Passed
- 19 / 20
- Mandatory failed
- 0
Bidders sent you sample units. Put them on the same bench, on the same day, and measure them against your own tender values: time to first fix, supply current, CAN read, network loss, tamper alarm, night image, OTA. Mandatory failures rule a unit out before any pilot.
Seven sheets for up to four units. Set the plan once and every result, score and rank follows.
01
Sample unitsUnits A to D with model, serial or IMEI, firmware, accessories and bid reference, plus the test site, dates, SIM, server and witnesses.
02
Test planTwenty example tests in eight areas, each with the method, unit, rule, your threshold, weight and a mandatory flag.
03
ResultsMeasured values per unit. Each result shows Pass, Fail or Not tested against the threshold and the rule.
04
ScorecardTests run, passed and failed, mandatory failures, weighted score, coverage, verdict and rank, and the score by area.
05
Evidence logOne row per photo, clip, screenshot or file, linked to a test ID and a unit.
06
Start here and ListsHow to run a fair bench test, the color legend and the drop-down lists.
Unit C scores higher than Unit B, but both fail a mandatory test, so only Unit A goes to the pilot. All values are examples.
Rank 1
Mandatory failure
Mandatory failures
Copy your thresholds from the tender, set the weights and mark the mandatory tests before any unit is switched on.
Keep model names on the Sample units sheet. Testers work with letters only.
Same place, same SIM network, same server. Enter each value and log the evidence.
Only qualified units go to a pilot in real vehicles. Use the rank to choose the order.
A datasheet says what a unit should do. A bench test shows what it does, next to the other bids, under your conditions. A few hours in the yard often settle what weeks of paper comparison cannot: which unit gets a fix fast, keeps its data through a network loss, and raises the alarms your tender asks for.
They cover what buyers usually ask of a tracker or recorder: GNSS fix and accuracy, supply current and restart, ignition and CAN data, delivery after a network loss, tamper and panic alarms, night image and DSM alarms, remote configuration and OTA, and the label and mounting. The thresholds are examples, not the values of any device. Replace them with the numbers in your own specification.
A bench test is quick and fair, but it is not the road. Heat, vibration, real wiring and real drivers come in the pilot. Use this scorecard to choose which units go to the pilot, then use a pilot test plan with acceptance criteria in real vehicles.
The scorecard compares the units you test, on the tests you choose. It does not rate a supplier, a contract or a price, and it does not state any device specification. A unit that passes here still needs a pilot and your acceptance test.
Tracom can send evaluation units for your bench test. Tell us which tests you plan, and we will tell you how to configure the unit for each one.
The file takes up to four, one per bid or model. Testing two units of the same model shows whether a result was a one-off.
From your tender or specification. The values in the file are examples so the formulas work. They are not the values of any device or standard.
Yes. A mandatory failure rules a unit out whatever its score. Rank is only among qualified units.
Leave the value empty. It shows Not tested, it is left out of the score, and the verdict shows Incomplete until every planned test is run.
No. It scores sample devices on a bench. Questions about contracts, support and data terms belong in your supplier questionnaire.
Tracom makes trackers and recorders and can supply evaluation units. The scorecard is neutral and works for any device. It does not certify a result and it does not choose a winner for you.
Get the scorecard, write your thresholds, and book a day in the yard.