Construction Equipment & Plant Tracking

Two different problems, usually bought as one

Heavy plant and small tools are entirely different tracking problems and are routinely specified as a single requirement. Heavy plant means a small number of expensive machines that mostly already report engine hours, fuel and location through their manufacturer's own telematics — a Caterpillar machine to one portal, a Komatsu to another, a Volvo to a third, and a hired machine to whichever the supplier uses. The plant manager therefore has excellent data in five places and no fleet view anywhere.

Small tools are the opposite: thousands of low-value items that disappear steadily, where a tracking device costing more than a fraction of the tool's value cannot be justified. Meanwhile the cost that dwarfs both sits quietly in the hire ledger — machines on rate, standing idle for weeks because nobody demobilised them, discovered at final account. Theft is the risk everyone talks about; idle hire is the one that is actually being paid.

• Manufacturer telematics are excellent and fragmented across separate portals.
• Hired plant reports to the supplier's system, not to the project's.
• Idle machines stay on hire because nobody sees they stopped being used.
• Small tools cannot economically carry the same devices as heavy plant.
• Maintenance is scheduled by calendar while wear happens by engine hour.

Solution overview

Swedish Technology treats the fleet view as an aggregation problem first. Most modern heavy plant already reports what matters, and the industry has an interchange standard for exactly this situation — the AEMP telematics standard, published as ISO 15143-3 — which lets engine hours, location, fuel and idle data be pulled from different manufacturers into one view without fitting a second tracker to a machine that already has one. Where a machine is older or a supplier exposes nothing, an aftermarket unit fills the gap rather than being the default answer.

Small tools are handled with economics that fit them: low-cost tags read at store issue, gate and container choke points, so the system knows what was issued to whom and what came back, rather than attempting continuous location on a two-hundred-dirham item. And the reporting is built around the decision that saves money — utilisation and idle time per machine against its hire rate, so off-hire happens when use stops rather than when the final account reveals it.

How the solution works

1. 1
   Separate the fleet by economics Heavy plant, light plant, and small tools each get an approach that suits their value and behaviour. Applying one method to all three is the most common way these projects waste money.
2. 2
   Aggregate existing telematics first Pull engine hours, location, idle and fuel from manufacturer systems using the AEMP / ISO 15143-3 interchange standard, so machines that already report are not fitted with a second device.
3. 3
   Fill the gaps with aftermarket units Older machines, non-reporting plant and equipment whose supplier exposes no data receive a tracker — as an exception rather than as the standard approach.
4. 4
   Tag tools at choke points Low-cost tags read at store issue, gates and containers, recording issue and return rather than attempting continuous location on low-value items.
5. 5
   Report against hire rate Utilisation and idle hours per machine set against its daily rate, so the off-hire decision is made from data while the cost is still avoidable.
6. 6
   Schedule on hours, alert on movement Maintenance triggered by engine hours rather than by calendar, and geofences flagging movement off site or outside working hours.

Key capabilities

Reference architecture

An integration layer more than a tracking layer. The data mostly exists; the problem is that it exists in other people's systems.

Deployment options: Cloud, since telematics providers are cloud services. Site-level tag readers buffer locally and reconcile, because store and gate operations continue whether or not the connection does.

Hardware options

The first question is what can be avoided, since a large share of a modern fleet already reports.

Swedish Technology supplies and integrates telematics and tagging hardware from established manufacturers, after establishing what the existing fleet already reports.

AI capabilities

Applied to the patterns in machine data that a plant manager has no time to read.

• Idle and under-use detection — Separates genuine working hours from idling and standing time, then ranks machines by cost of non-use against hire rate — which is the report that changes decisions.
• Maintenance prediction — Uses engine hours, fault codes and usage intensity to forecast service needs earlier than a fixed interval, which matters most for plant on critical path.
• Fuel anomaly detection — Identifies consumption inconsistent with recorded work, which is how fuel loss is distinguished from heavy operation rather than assumed either way.
• Demand forecasting — Predicts plant requirements from programme and historical usage, so hire is booked and released on data rather than on a call from a foreman.

Integrations

The integrations are the product here. These can be designed within project scope.

The integrations above are designed and implemented within project scope using vendor APIs, webhooks or standard connectors. They do not imply partnership, certification or endorsement by the system owner unless stated on that vendor's official pages.

Dashboards & analytics

• Utilisation and idle cost — Working versus idle hours per machine, priced at its hire rate and ranked by avoidable cost.
• Fleet location — Where every machine is, by site and zone, including plant that has moved without a movement order.
• Maintenance due — Hour-based service requirements with location, so the fitter is not sent to look for the machine.
• Tool issue and loss — Issued, returned and outstanding tools by store, trade and subcontractor over a period.

Security & deployment

Geofencing and movement alerting are genuinely useful and should be described accurately: they detect that a machine has moved, which supports recovery and deters opportunistic removal, but a determined thief locates and removes a tracker. Presenting geofencing as theft prevention rather than as movement detection sets an expectation that will fail at the worst moment. On hired plant, fitting anything is subject to the supplier's written agreement, and an unauthorised installation is a commercial problem for the project rather than a technical one. Aggregated telematics data is commercially sensitive — utilisation figures feed hire negotiations — so access should be scoped as deliberately as any other commercial data.

Data privacy

Machine tracking becomes staff tracking as soon as a machine is assigned to a named operator, and on a construction site that is normal. Operator assignment is legitimate — it supports competency verification and incident investigation — but it should be limited to that purpose rather than becoming a movement record of an individual's working day.

The practical distinction we apply is between machine data and operator data. Utilisation, idle time, fuel and maintenance are properties of the equipment and are reported freely. Data that describes how a named person spent their shift is workforce monitoring and needs the same justification, notification and proportionality as any other. Under UAE Federal Decree-Law No. 45 of 2021 the purpose should be stated to the people concerned, and on hired plant the supplier's telematics may already be collecting operator-related data under arrangements the project has not seen — which is worth establishing at contract stage.

Industry use cases

Implementation approach

1. 1
   Fleet audit Establish what each machine already reports and through which platform. This routinely finds that most of the required data exists and simply is not being collected.
2. 2
   Supplier data access Negotiate telematics access for hired plant, ideally as a standard hire term. This is commercial work and it is the usual critical path.
3. 3
   Aggregation setup Connect manufacturer and supplier feeds into one view, then fit aftermarket units only where a genuine gap remains.
4. 4
   Tool store process Tagging and choke-point readers at stores and gates, with the issue and return process agreed with storekeepers before hardware arrives.
5. 5
   Commercial reporting Utilisation against hire rate, built with the commercial team so the report supports the decision it exists to inform.
6. 6
   Maintenance transition Move from calendar to hour-based servicing for the plant where it matters most, with the maintenance team involved from the start.

Why Swedish Technology

• We aggregate the telematics your fleet already has before selling you trackers — most modern plant already reports everything you need.
• We use the AEMP / ISO 15143-3 interchange standard, which is the actual answer to a mixed-manufacturer fleet.
• Small tools get economics that suit them: choke-point issue and return, not continuous tracking of a low-value item.
• The headline report is idle cost against hire rate, because that is where the money is — not theft alerts.
• We describe geofencing as movement detection rather than theft prevention, because a determined thief removes the tracker.

Limitations & prerequisites

• Telematics access on hired plant depends on supplier agreement. Without it the project sees only what an aftermarket unit can gather, and fitting one requires the supplier's consent.
• GPS is unreliable inside steel containers, basements and deep excavations, so a machine can appear stationary or absent when it is simply out of view.
• Geofencing detects movement; it does not prevent theft. Trackers are found and removed, and recovery depends on response speed rather than on the alert alone.
• Small tool tracking below a certain value does not pay back. Choke-point issue and return is the economic answer, and continuous location on cheap tools is not.
• Aftermarket installation on heavy plant requires downtime and competent fitting; poor installation produces unreliable engine-hour data, which is worse than none.
• Utilisation data supports commercial decisions but does not make them. Programme, availability and mobilisation cost remain judgement calls.

FAQ

Related solutions

• Interactive Experiences & Smart Visitor Solutions
• Construction Workforce Tracking
• Construction Site Visitor Management
• Digital Permit to Work
• Hospital Asset Tracking
• Smart Inventory Cycle Count
• RFID Asset Management & Tracking
• Oracle E-Business Suite