PlatformsFaststream SiliconFaststream RadioFaststream VisionConnected EdgeFaststream SecureMobility & Rail
ProductsSemiconductor IPIP CoresWireless & RANEdge & GatewaysTracking & IdentificationSoftware & FrameworksConnected Systems
Technology5G protocol stackWireless and RF architectureBaseband and low PHYForward error correctionControl and data planeHigh-speed interfacesFirmware and bootSilicon root of trustSoftware-defined vehicleAutomotive OTAFunctional safety
AIAI Engineering ServicesEdge AI & Embedded MLComputer Vision EngineeringSensor Fusion & PerceptionAI Silicon & AccelerationMLOps for DevicesAI Visual InspectionPredictive MaintenanceDriver MonitoringVideo Analytics & Safety
SolutionsSemiconductorIndustrial AIConnected ProductsAsset TrackingMHE Tracking & UtilizationBluetooth AoA RTLSWearable TrackingAutomotive & MobilitySmart InfrastructureSecure IdentityWireless & SatelliteNTN Asset TrackingPrivate 5GSmart WashroomsFuel ManagementSmart BuildingsWorker SafetyEnergy MonitoringSmart AgricultureSmart CityAutonomous PlatformsAssembly AutomationLiDAR Rail SafetyHardware Wallet
IndustriesSemiconductorTelecommunicationsIndustrial & ManufacturingAutomotive & MobilityTransportation & RailAerospace & DefenceHealthcare & MedicalEnergy & UtilitiesOil & GasRetailConsumer ElectronicsMedia & EntertainmentSmart Infrastructure & IoT
ServicesSystem Integration overviewASIC & SoC DesignRTL to GDSIIVerification methodologyDFT and silicon testLow-power designMixed-signal integrationDesign enablementFPGA DesignFPGA-to-ASIC ConversionAnalog, Mixed-Signal & RFHardware & High-Speed PCBEmbedded SoftwareCloud, OTA & Device ManagementManufacturing TransitionHow we engage
CompanyAbout FaststreamEngineering ExcellenceLeadership & OrganisationHow We EngageQuality & ComplianceStandards & EcosystemPartners & EcosystemTrust CentreLocations & DeliveryNewsroom & MediaCareersCase StudiesKnowledge CenterWhite PapersGlossaryNewsletterResources & Support
ContactStart a projectHow we engage
Talk to us
SOLUTION · INDUSTRIAL IoT

MHE Tracking, Fleet Utilization & Equipment Health Monitoring

Knowing where every forklift, reach truck and tow tractor is — indoors and outdoors — and what it is doing, is one engineering problem, not a box you buy. Faststream designs the tag, the positioning, the edge intelligence, the wireless backhaul and the cloud analytics as one system, so a US plant gets continuous location, real utilization and equipment-health insight — not a GPS dot that disappears at the shutter door.

UWBBLEGNSSCellular / 5GEdge AICAN / J1939Cloud
ShareLinkedInEmail
THE REQUIREMENT

What a plant actually asked for.

A US manufacturer asked Faststream to make its material-handling fleet visible and measurable across indoor warehouses, loading docks and the outdoor yard. The requirement is specific: real-time location with indoor–outdoor continuity, movement and route history, distance travelled, runtime and idle time, equipment utilization, and equipment-health monitoring — as one system a supervisor can act on.

See every unit

Live location of each vehicle across warehouse, dock and yard on one map — no blind spots at the indoor/outdoor boundary.

Measure the work

Runtime, idle time, productive time, distance and utilization — defined consistently so the numbers mean the same thing on every shift.

Protect the asset

Battery and motor health, fault codes, impact events and service intervals — where the vehicle interface allows it to be read.

Indoor and outdoor are one tracking problem. UWB and BLE locate the vehicle inside, GNSS and cellular outside, and the system hands the tag off through the dock so each vehicle is one continuous track — not three partial records with gaps between them.
INDOOR + OUTDOOR · ONE RECORDWAREHOUSE · INDOORUWB anchorssub-metreBLE gatewayszone levelForklift / reach-truck tagUWB + BLE + IMULoading dockseamless hand-offOUTDOOR · YARDGNSSmetresCellularwide areaYard / tow-tractor tagGNSS + cellular + IMUWi-Fi · cellular · private 5GbackhaulLocation platformfuses + hands offOne continuoustrack + historyOne tag is seen indoors (UWB/BLE) and outdoors (GNSS), handed off through the dock, and fused into a single continuous track — not three partial records.
CONTINUITY

One continuous record, indoors to outdoors.

Indoors, GNSS does not work; outdoors, fixed anchors do not exist. The system uses the right technology in each zone — UWB or BLE inside, GNSS and cellular outside — and fuses them on the device and in the platform so a vehicle that leaves the warehouse, crosses the dock and drives into the yard produces a single track a supervisor can follow, rather than two systems a person has to reconcile.

The metrics are defined before they are reported, because a number no one can define is a number no one trusts:

Metric definitions
MetricDefinition
RuntimeTime the vehicle is powered and in motion or actively handling load.
Idle timeTime powered but stationary and not handling load, beyond a configurable threshold.
Productive timeRuntime attributed to value-adding movement or handling, per rules agreed with the site.
Distance travelledPath length from fused position over a shift or period.
UtilizationProductive time as a share of available/scheduled time, by vehicle and by shift.
EQUIPMENT HEALTH

What can be read, and what it depends on.

Health telemetry is only as available as the vehicle lets it be. Some signals come from sensors on the Faststream tracking module itself; others require access to the vehicle’s own bus or added instrumentation. We state the dependency plainly rather than imply every signal is free.

Health telemetry and its interface dependency
SignalSource / dependency
Motion, impact & shock eventsOn-module IMU — available without vehicle integration.
Runtime, idle, locationOn-module sensing and positioning — available without vehicle integration.
Battery voltage / current / temperature / SoC / SoH, charge cyclesBattery/BMS interface or added sensors — requires access or instrumentation.
Engine or motor hours, controller temperature, hydraulicsOEM vehicle bus (CAN / J1939) or added sensors — requires OEM interface or integration.
Fault codes & diagnostic eventsOEM telematics/diagnostic interface — brand-dependent, requires OEM access.
Abnormal idle / operating patternsDerived on the edge from the signals above.

For mixed-brand fleets this matters: what is natively readable differs by make and model. Faststream’s role is to engineer the interface — a harness, a CAN/J1939 reader, or supplementary sensors — so a consistent set of health signals reaches one platform regardless of vehicle brand.

The reason this is one coherent system and not integrated parts: Faststream engineers every layer — the silicon and analog IP, the sensor electronics and tracking module, the embedded firmware and on-device inference, the wireless and gateways, the cloud and APIs, and the enterprise integration.
SILICON TO SYSTEM · ONE PARTNERAPPLICATIONSFleet ops · utilization · ERP / WMS / MES / CMMSCLOUDIngest · analytics · APIs · dashboardsCONNECTIVITYGateways · Wi-Fi / cellular / private 5G / satelliteEMBEDDED + EDGEFirmware · sensor fusion · on-device inferenceDEVICESensors · tracking module · power · vehicle interfaceSILICONASIC / SoC · analog IP · FPGA · securityENGINEERED IN-HOUSEsiliconcloudFaststream engineers every layer from the transistor to the enterprise dashboard — not a reseller of one of them.
OPERATIONS DASHBOARD

What a supervisor sees.

The platform presents fleet overview, a live plant map, per-vehicle detail, route replay, shift-wise utilization, runtime versus idle, equipment health and alerts. The illustration below is a demonstration — a representative layout with sample data, not live customer telemetry.

Demonstration dashboard — representative layout and sample data, not live customer telemetry. Fleet utilization, runtime-versus-idle by shift, a live plant map and equipment-health alerts in one view.
OPERATIONS DASHBOARD · DEMONSTRATIONPLANT MAP · SAMPLEWarehouse AWarehouse BDockYard● running ● idle ● chargingFLEET UTILIZATION · SAMPLE54%productiveRunning 54%Idle 28%Charging 18%RUNTIME vs IDLE · BY SHIFT · SAMPLES1S2S3HEALTH ALERTS · SAMPLE▲ FL-07 battery SoH 71% · service due▲ RT-12 idle 2h10m in Dock
POSITIONING

Choosing the technology by the zone.

No single positioning technology covers an entire plant. The choice is made per zone against accuracy need, infrastructure, environment and power — and connectivity (how the data gets back) is a separate decision from positioning (how the vehicle is located). The ranges below are general engineering guidance, not guarantees; real accuracy depends on the site survey.

Positioning technology trade-offs
TechnologyTypical accuracyInfrastructureBest for
UWBSub-metreAnchor network indoorsPrecise indoor bay/aisle location
BLE / BLE AoAZone to a few metres (AoA tighter)Gateways indoorsCost-effective indoor zoning
RFID (UHF)Portal / choke-pointReaders at doorsEntry/exit and inventory events
GNSSMetres outdoorsSky visibilityOutdoor yard location
Wi-Fi positioningSeveral metresExisting APsCoarse location on existing networks
Hybrid / sensor fusionContinuous across zonesCombines the above + IMUSeamless indoor–outdoor continuity
COVERAGE

Equipment this covers.

Forklifts & reach trucks

Counterbalance and reach trucks in warehouse aisles and racking.

Pallet movers

Powered pallet trucks and stackers across pick and dispatch.

Tow tractors

Tuggers and trains moving material between zones.

AGVs

Automated guided vehicles alongside manned equipment on one map.

Yard vehicles

Yard trucks and terminal tractors in the outdoor yard.

Mixed-brand fleets

Multiple OEMs unified behind one tracking and health platform.

ENGINEERING EVIDENCE

Where the building blocks are proven.

These are delivered programmes that each prove a building block of an MHE system. They are component-level evidence from separate projects, not one integrated MHE deployment — shown so you can see the engineering behind each capability.

PILOT

A pilot before a rollout.

We prove the system on a defined slice of the fleet before scaling. The sequence — and the acceptance criteria that gate each pilot — are agreed up front rather than promised as performance.

  1. Site survey Walk the plant; map zones, materials, RF environment and the indoor/outdoor boundary.
  2. Technology selection Choose positioning per zone and the backhaul, against the survey.
  3. Integration Fit tracking modules and any vehicle-bus or sensor interfaces on the pilot fleet.
  4. Calibration Place and calibrate anchors/gateways; validate position in each zone.
  5. Dashboard setup Configure metrics, utilization rules and health alerts with the site.
  6. Pilot validation Run the pilot and test against agreed acceptance criteria.
  7. Rollout Scale to the full fleet with support.

Acceptance is defined by measurable criteria set with the customer — for example, position availability in each named zone, continuity of a track across the dock, and utilization reported per shift — not by unverified performance claims.

Typical pilot parameters — a starting point, tuned to your site at survey.

Typical pilot parameters
ParameterTypical starting point — tuned at survey
Pilot fleet size5–15 vehicles spanning the zones that matter — indoor aisles, yard and dock
Indoor positioning accuracySub-metre to ~1–3 m (UWB / BLE AoA), by zone and anchor density
Outdoor positioning accuracy~2–5 m (GNSS), held through gaps with dead-reckoning fusion
Position update rateSeconds-level live location; configurable per zone and power budget
Health & telemetry reportingMinutes-level by default; event-driven for impacts, alerts and fault codes
Site surveyOne site visit — zones, RF environment, materials and the indoor/outdoor boundary
Deployment timelineSurvey wk 1 · integration & calibration wks 2–3 · pilot run wks 4–8
Acceptance criteriaPosition availability per named zone · track continuity across the dock · utilization & idle per shift · health signals present per the interface matrix
ENGAGEMENT

How we engage.

Turnkey solution

The complete MHE system, engineered and delivered end to end.

Custom hardware & embedded

Tracking controller, sensors and firmware designed to the fleet.

Hardware & gateway integration

Tracking devices and gateways integrated into your site.

Cloud & analytics

Dashboards, reporting and APIs on your cloud or ours.

Pilot to production

A validated pilot scaled to a supported rollout.

Maintenance & support

Ongoing support, updates and fleet management.

COMMON QUESTIONS

What engineers ask before they call.

01

How do you keep tracking continuous from inside the warehouse to the outdoor yard?

Different technologies per zone — UWB/BLE indoors, GNSS/cellular outdoors — fused on the device and in the platform, with the dock handled as a hand-off so a vehicle stays one continuous track rather than two records.

02

Can you read battery and engine health on our existing forklifts?

Motion, impact, runtime and location need no vehicle integration. Battery SoC/SoH, motor hours, temperatures and fault codes require the vehicle’s BMS/CAN/J1939 interface or added sensors, and what is readable varies by brand — we engineer the interface to make it consistent.

03

Is the dashboard shown real data?

No. The dashboard illustration is a demonstration with representative sample data. A deployment reports your fleet’s own data against metrics defined with you.

04

Do we have to replace our mixed-brand fleet?

No. The platform unifies multiple OEMs; the integration depth per vehicle depends on each brand’s available interfaces.

RELATED CAPABILITIES

The engineering behind it.

KEEP READING

Related work.

BUILD WITH FASTSTREAM

Bring us the difficult part.

Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.