Mixed Fleet Tracking: Trucks, Trailers, and Equipment on One Account

One account, several asset types

Four VITALGLOW formats can sit inside the same account: the wired tracker at $119.99, the magnetic tracker at $99.99, the OBD plug-in at $99.99, and the mini tracker at $59.99. All of them ship with the 4G SIM and data included and are sold with no monthly fee and no subscription, so a tenth asset costs the same as the first. What separates them is how they take power, and that question decides which unit goes on which asset.

Plan the mix by counting power situations rather than vehicle names: machines with a live 12V system, light vehicles with an open OBD port, and assets with no electrics at all. Note which assets sit idle for weeks. A mixed asset tracker setup usually ends up with two or three formats, which is normal rather than a compromise.

Fix the naming convention before the second asset is added. Use a stable asset number with a class prefix and the format, as in VAN-03 OBD, TRK-14 WIRED, or TRL-07 MAG, and keep driver names, customer names, and street addresses out of every label. A number that never changes means a reassignment is an edit to your operational record instead of a rename in the tracker list.

What changes when assets move between sites

Reassignment changes who is responsible for an asset; it does not change the asset record. In a mixed fleet the durable row is the asset, whether that is trailer TRL-07 or bucket unit 22, and the driver, the site, and the job are attributes you update. One asset per record survives turnover, resale, and seasonal storage, because a new driver inherits an existing history. A record per driver does the opposite: the day that driver leaves, the history leaves too.

Take a trailer dropped at Site A on Monday and collected by a different truck on Thursday. Because the magnetic unit travels with the trailer, the trailer record shows one continuous history with a parked stretch in the middle, which is the question a utility fleet tracking review asks about a trailer sitting in a lot. Had you tracked only the tractor, the drop is invisible and the trailer's location between loads is unknown. Bucket truck tracking carries the inverse risk: the unit belongs to the truck, so a trailer it pulls needs its own record.

Treat reassignment as a recorded change rather than a rename: note the date, the new responsible driver or crew, the neutral site label where the asset was left, and the format in use. Seasonal and stored assets need a decision per asset, either leaving a self-powered unit on the asset with a review date for the season, or taking it off and logging the removal date and storage location.

Keep customer addresses out of the fleet record

A mixed fleet record should be a list of assets, not a list of customers. The work-order system needs the customer's name, service address, and appointment window; the tracking account needs far less: an asset ID, a neutral site reference, a timestamp, and an exception status. Connect the two with a code like WO-1842 or Site A instead of copying customer fields into tracker labels.

Avoid labels that reveal a person's name, a health condition, an access code, or the type of valuable equipment on site. A dispatcher with authorized access can look up the work order when the business need requires it.

Site labels and zones for assets, not households

Permanent geofences make sense for stable company locations: the yard, approved parking, the warehouse, a regular supplier, or a job site the crew returns to for weeks. A permanent named zone for every home the fleet visits adds maintenance work and can expose appointment patterns long after the job ends. For customer work, ask first whether a zone changes a decision; a neutral work-order reference plus route context is often enough. If a temporary zone helps, name it neutrally, restrict access, and give it a review or deletion date.

Do not treat a zone event as doorway precision. A zone event represents a tested boundary and reported movement; parking position, road layout, buildings, lot size, and signal conditions all affect what it shows.

Screenshots and exports from an account that holds everything

One screen in a mixed fleet account can show every asset, every site label, route history, and alert settings. Crop a screenshot to the asset, timestamp, and map area the question needs, and redact unrelated stops, site names, and identifiers. Do not send a full day of fleet routes when a fifteen-minute segment answers the question, and do not attach a fleet-wide export to one customer ticket. Approved records belong in the business system with an access rule and a review date.

Who gets access when one login covers every asset type

A dispatcher usually needs the whole asset list. A driver needs one assignment, or none. Customer service needs an approved arrival range rather than route history, and an installer needs power and device details without customer records. Write those tasks down first, then check what the account can actually enforce. If roles cannot be separated, do not hand the main login around; run a controlled request process and answer each role with the minimum it needs. Remove temporary access when an assignment ends and review authorized users on a schedule.

The FTC and NIST references below are business-data principles, not legal advice for a specific business or state.

Customer updates that do not expose the rest of the fleet

A useful update says that the service vehicle was reported in your area at the displayed time and that dispatch is confirming the technician's status. Do not say the technician is at the door, has entered the property, or will arrive in a specific number of minutes based on a map. Do not send customers raw tracker links or screenshots from a fleet account, because one screenshot can show other stops, other assets, and site labels. Customer communication belongs to the work-order and dispatch process, with GPS as one source of route context.

Deleting customer detail without losing asset history

When a work order closes, review temporary zones, screenshots, exports, support attachments, and route notes. Delete the company-controlled copies that no longer serve an approved purpose, and keep the asset history the fleet still needs. If a complaint, insurance claim, or contract creates a hold, record the scope, the owner, the access rule, and a review date. Deleting a local copy does not remove provider-side records or backups; confirm current service behavior separately.

Choosing a format for each asset without breaking the privacy rule

The VITALGLOW wired GPS tracker at $119.99 is the default for trucks and bucket units that run daily: it wires into vehicle power, is waterproof, includes the 4G SIM and data with no monthly fee, and supports location history, geofence context, and selected driving alerts. Those records answer dispatch and utilization questions; they do not create customer consent, identify the driver, or promise an arrival time. Compare formats in the VITALGLOW tracker collection before ordering, and keep customer detail out of the tracker list.

Run a mixed-fleet acceptance test

Test with the yard and one other authorized business location, never a customer address. Add one asset per format, create a neutral reference for each, run a short route, review the event, and remove the temporary local copy under the test procedure. Confirm that a dispatcher, a driver, and a manager each see only what the team intended. The test passes when the team can answer an operational question, such as where TRL-07 is or whether the truck reached the site, without exposing a customer's identity or an unrelated asset's history.

Frequently asked questions

Final Recommendation

Plan the account before the hardware: one record per asset, a format chosen by power source, a naming convention that survives reassignment, and customer detail that stays in the work-order system. Use the Business GPS Tracking page for deployment planning, the VITALGLOW FAQ for product questions, or contact VITALGLOW with the device details needed to confirm current product behavior.

Where a yard holds bucket trucks, service vans and pickups side by side, gps tracking for electric and utility companies is mostly a question of who answers for each vehicle.

Sources and Further Reading

• FTC: Protecting Personal Information on data minimization and secure disposal.
• NIST Privacy Framework for voluntary privacy-risk guidance.