Rollout planning · Free planner

OTA Rollout and Data Planner

How long will a firmware update take, how much SIM data will it use, and on which dates should each wave go? Enter your package, fleet and link, then read the schedule, the data per month and a go or no-go checklist.

Runs in your browserYour own link ratesA plan, not an approval
MB

The size of the image that devices download. Use the real file size.

KB

Settings sent with the update. Enter 0 if there is none.

%

Extra bytes for headers, acknowledgements and encryption.

kbps

Download rate of the link. Cat-1 10,000, Cat-M1 300, NB-IoT 26 (GSMA peak figures), 2G about 40 (typical).

%

Share of the link rate you really get after signal, protocol and server limits.

Verify against the current official text

The link rates are published planning figures, not guarantees. Measure your own network. The download peaks for Cat-1 (10 Mbps), Cat-M1 (about 300 kbps in half duplex) and NB-IoT (26 kbps) are from GSMA: data throughput of LTE-M, NB-IoT, 3G and 4G. The 2G figure is a typical value with no official source here.

Source and date checked: 3 November 2026.

devices

Devices that will receive the update, one SIM each.

devices

The most downloads your platform runs at the same time.

hours

Hours each day when updates may run.

%

Share of devices that fail once and download again.

Download timePer device

Attach the plan to your change record

A report with the download time, the wave schedule, the data per month and the checklist.

Rollout report

Take the rollout plan to your change meeting

  • Download time per device on your link
  • Waves with dates, soak days and failure limits
  • SIM data per month and the rollback reserve
  • The go / no-go checklist with the checks still to confirm
  • Every assumption you entered

How long does one device take to download an update?

Time is the size in bits divided by the speed you really get. The speed you really get is the link rate times an efficiency.

time (s) = size (MB) × 8,000,000 ÷ (rate (kbps) × 1,000 × efficiency)1 MB = 1,000,000 bytes. Efficiency 60% = 0.6.

Example: a 1.5 MB image on a 300 kbps link at 60% efficiency is 12,000,000 bits ÷ 180,000 bit/s = 66.7 s. The same image at 26 kbps and 100% efficiency takes 461.5 s.

A 1.5 MB image at 60% efficiency
LinkRate (kbps) typicalTime per device
LTE Cat-110,0002.0 s
LTE Cat-M13001 min 7 s
NB-IoT2612 min 49 s
2G (GPRS/EDGE)408 min 20 s

The Cat-1, Cat-M1 and NB-IoT rates are GSMA peak figures, and the 2G rate is typical. Your operator, signal and server decide the real number, so measure one device first and enter the result.

What is a staged rollout?

Update a few canary devices first, watch them, then widen the group: 5%, 25%, 50%, 100%. If devices fail more than your threshold, stop and roll back before the next wave.

Example schedule for 500 devices
StageDevicesTotal so farDate (2026)Soak days after
Canary group101015 Nov2
Wave 1 (5%)152518 Nov2
Wave 2 (25%)10012521 Nov2
Wave 3 (50%)12525024 Nov2
Wave 4 (100%)25050027 Nov0

The schedule assumes 100 devices update at once, 8 hours a day, each in about 1 minute, with 2 soak days after every step except the last, and no weekend rule. A slower link or a lower concurrency lengthens the waves.

How much SIM data does a rollout use?

Each device downloads the firmware and the config file, plus protocol overhead. Add the devices that retry, and keep a reserve for rollbacks.

Data for the example fleet
ItemHow it is calculatedResult
One device(1.5 MB + 20 KB) × 1.10 overhead1.67 MB
Fleet, no retries500 devices × one device836 MB
Fleet with 8% retriesFleet × 1.08903 MB
Rollback reserve10% of 500 devices × one device83.6 MB

On a plan of 5 MB with 3 MB of normal use, a SIM has 2 MB spare. One download of 1.67 MB fits. A download plus a retry (3.34 MB) does not, so spread the waves over two months or raise the plan before you start.

What goes on a go / no-go checklist?

The planner calculates the first six checks from your inputs. A person must confirm the rest.

  • Spare data on every SIM covers one download, and the pooled data covers every month.
  • Wave percentages increase and the dates avoid your weekend days.
  • A stop threshold is written down before wave 1.
  • The previous firmware is stored and was installed on a bench device.
  • A bench device survived a power cut during an update.
  • Your platform shows the firmware version of every device after the update.
  • One named person can stop the rollout and start a rollback.

What usually goes wrong?

  • Slow devices stall the wave. A few devices in weak signal can take far longer than the average. Do not size the window on the average alone.
  • Data runs out on small plans. A retry doubles the download for that SIM. Check one SIM, not only the pool.
  • Devices are off when the wave runs. Vehicles that are parked for days miss a wave. Plan a catch-up pass for them.
  • No way back. If the previous image is missing, a bad update cannot be undone. Store it and test it first.

Assumptions and limits

  • Link rates, efficiency, overhead and the retry share are typical planning values. Replace them with your own measurements.
  • The planner does not know the firmware size, delta-update support or resume behavior of any Tracom model. Enter the figures your device and platform really use.
  • Every device is assumed to have its own SIM and to download the full package. A resumed or partial download uses less data.
  • Waves run one after another. Your platform may start several at the same time or limit the hours per day.
  • The checklist is a planning aid. It is not an approval, and the decision to go stays with your team.
  • The calculations run in your browser. Your inputs are sent to our server, and kept for up to 45 days, only if you ask for the emailed report.

Sources

Last checked 3 November 2026. The 2G rate and the staged-wave practice have no official text here: measure your own network and verify before you rely on a figure.

Related Tracom solution

Roll out updates without a technician on every vehicle

Tracom devices support over-the-air updates, and the SCMS portal manages device settings and configuration files. Use this planner to agree the waves, the dates and the data before you start.

  • Over-the-air updates. Bring new firmware to devices in the field.
  • SCMS portal. Manage device settings and configuration files in one place.
  • Second-by-second data. Records how the vehicle moves in fine detail.
  • No internet? No problem. The device keeps deciding on the vehicle without a connection.
Questions

Questions about OTA rollouts

Planning a large update? Contact Tracom.

Why start with a canary group?

A few devices show a bad image or a bad setting before it reaches the whole fleet. You pay the data cost of a handful of devices, not of all of them.

What efficiency should I enter?

Start with 60% and replace it with a measurement. Download one image to a test device on your SIM and divide the speed you saw by the link rate.

How big should the rollback reserve be?

The planner starts at 10% of the fleet as a typical value. A rollback sends the previous image again, so each rolled-back device costs one more download. Raise it for a risky update.

Does the planner know the size of my firmware?

No. Enter the real file size. The planner does not hold the firmware size, delta-update support or resume behavior of any Tracom model.

Is my data sent anywhere?

Only if you ask for the emailed report. The plan is calculated in your browser. If you request the report or the CSV, your inputs are sent to our server with your name and email, and kept for up to 45 days.

What is Tracom's role here?

Tracom makes tracking and video hardware. The planner helps you prepare a rollout. It does not approve an update, and it does not replace your own testing or your platform's limits.

Related tools and templates

Keep planning the rollout

Get the report

Enter your details and we will email you the file.

Use your real name so the file arrives addressed to you. Don't worry, we won't flood you with emails or calls.

Scroll to Top