mTracker
The miniature GSM/GPS device that puts utilization and OEE inputs on the assets that don't report them today — fixed or mobile. It reads equipment-level signals, tracks location, and publishes over cellular, on a retrofit attachment with battery backup.
4G / LTE cellular · GPS / GNSS · equipment-level digital inputs · geo-fence alerts · battery backup · retrofit attachment · IP65 / IP67-compatible (BOM-scoped).
Utilization and OEE inputs on assets that never reported them.
mTracker is a miniature GSM/GPS asset-tracking and telemetry device. It reads equipment-level digital signals — run / stop, cycle, output counts — and reports OEE inputs (production time, downtime, idle time, output quantity) along with location, over cellular, with battery backup. It is designed for retrofit attachment to fixed or mobile assets.
It is the Asset Intelligence pillar — see the capability story → /capabilities/asset-intelligence. mTracker provides the inputs; EREMOS V2 computes the OEE and the utilization analytics. (For direct analog sensor acquisition — pressure, flow, temperature — see mDAQ; mTracker is asset tracking + digital-signal telemetry, not an analog DAQ.)
What it does — and what it removes from your BOM.
Reads equipment-level signals
Digital inputs capture run / stop, cycle, and output-count signals straight from the asset — no manual logs.
Tracks location + utilization
GSM/GPS reports where an asset is and whether it's running, idle, or stopped — fixed plants or mobile fleets.
Geo-fence alerts
Boundary entry/exit alerts for location and compliance.
Retrofit + remote
A miniature attachment with battery backup and cellular publish — fits assets that ship without telemetry.
One mTracker removes from the customer BOM:
- manual production-hour spreadsheets;
- a separate GPS / geo-fence tracker;
- a service-hours odometer for warranty triggers;
- asset-presence audits.
The device, in numbers.
| Connectivity | Cellular publish — 4G / LTE class (SIM / carrier / region / bands confirmed during BOM scope) — plus GPS / GNSS positioning |
| Inputs | Equipment-level digital inputs for run / stop, cycle, and output-count signals. Channel count, voltage / contact type, counter rate, debounce, sink / source behavior, and input protection confirmed during BOM scope. |
| Location | GPS / GNSS positioning + geo-fence entry / exit alerts |
| Power + battery | Battery backup for assets without continuous power. Supply range, backup-vs-primary role, charging / replacement, runtime by reporting interval, and low-power behavior confirmed during BOM scope. |
| Form factor | Miniature, designed for retrofit attachment (fixed or mobile assets) |
| Environmental | Operating temperature, humidity / condensation, shock / vibration (mobile assets), and UV / outdoor exposure confirmed during BOM scope |
| Mechanical | Dimensions, weight, enclosure material, connector / harness, and cable ingress confirmed during BOM scope |
| Ingress protection | IP65 / IP67-compatible configurations can be scoped where a site requires it; final protection level, enclosure approach, and any certification requirements confirmed during BOM scope. (Compatibility, not a certified rating — no formal IP certification is currently claimed.) |
| Mounting | Retrofit attachment; mounting method, exposure, and antenna placement confirmed during BOM scope |
| Item | Confirmed during BOM scope |
|---|---|
| Digital inputs | Channel count, voltage/threshold, dry/wet contact, debounce, sink/source behavior, protection |
| OEE-input mapping | Which equipment signals map to run / stop / cycle / output-count; how output quantity is counted |
| Reporting | Report interval, timestamping, buffering / offline retention, publish path (to EREMOS V2) |
| Power + battery | Supply, current draw, battery runtime, charging / replacement, low-power mode |
| Mechanical + mounting | Mounting method (screw / adhesive / magnetic / bracket), tamper resistance, antenna placement, cable ingress for mobile assets |
| Geo-fence behavior | Boundary source, update interval, alert latency, indoor / poor-signal behavior, and device-side vs platform-side evaluation |
| Data handling | Offline buffer capacity, timestamp source, store-and-forward + duplicate handling, event-triggered vs periodic publish |
| Device management | Device identity / TLS, provisioning, remote config, OTA firmware, geo-fence config management |
How it retrofits.
| Retrofit attachment | Designed to attach to fixed or mobile assets without a redesign. Mounting method, location, and antenna placement confirmed during BOM scope. |
| Equipment-signal wiring | Digital inputs wire to existing run / stop / cycle / output signals. Signal voltage/threshold, contact type, and OEE-input mapping confirmed during BOM scope. |
| Power | Battery backup for assets without continuous power; supply + runtime confirmed during BOM scope. |
| Connectivity | GSM / GPS / 4G cellular publish. SIM / carrier / antenna and network assumptions confirmed during BOM scope. |
| Geo-fence | Boundary entry/exit alerts configured per deployment. |
| Offline | Buffers locally and publishes when connectivity returns. |
| Environment | Exposure, humidity, and enclosure approach confirmed during BOM scope; IP65 / IP67-compatible configurations can be scoped where the placement (incl. mobile/outdoor assets) requires it (no certified rating claimed). |
The device in the stack.
ArchitecturePanel.interactive variant.
For direct analog sensor acquisition, see mDAQ; for service-hours / warranty / fleet outcomes on shipped equipment, see /solutions/oem-machine-monitoring. The full stack → /architecture.
One device, plus the utilization picture.
Packaging labels are illustrative until commercial packaging is approved; this section describes how the unit is bought + what it pairs with, not pricing.
mTracker is a hardware unit, scoped against the assets to instrument, the equipment signals available, connectivity, power/battery, and the mounting environment. It feeds utilization + OEE inputs to EREMOS V2. For OEM machine builders, the same equipment-level run-hours drive service-hours billing, warranty triggers, and fleet visibility on shipped equipment — see /solutions/oem-machine-monitoring. Bring the asset list, the signals available on each, the connectivity, and the mounting; we'll scope the BOM. Contact Elpis for unit availability and BOM scoping; detailed pricing follows the BOM review. No pricing tables, SKU grids, or per-unit pricing on this page.
Built to retrofit, fixed or mobile.
Built to retrofit, fixed or mobile.
A miniature attachment with battery backup, designed to go onto assets that ship without telemetry — including mobile equipment in the field.
Remote-ready, offline-capable.
GSM / GPS / 4G publishes from anywhere with cellular; buffers locally and publishes on reconnect. Geo-fence alerts for location and compliance.
Formal third-party certifications are not currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope; IP65 / IP67-compatible configurations can be scoped where required, but certified/rated claims are published only when formal evidence exists for the specific product/configuration.
What plant engineers ask.
What does it actually track?
Asset utilization and location: it reads equipment-level digital signals (run / stop, cycle, output count) and reports the OEE inputs — production time, downtime, idle time, output quantity — plus GPS location, over cellular. Which signals are available and how they map are confirmed during BOM scope.
How is mTracker different from mDAQ?
mDAQ is the field sensor DAQ: analog 4–20 mA / 0–10 V sensor acquisition plus I/O. mTracker is the asset telemetry tracker: equipment-state / count inputs plus GPS, geo-fence, cellular, battery, and retrofit attachment — no analog channels. (Both touch digital signals, so the real split is by purpose:) mDAQ is for sensor values; mTracker is for run-state, counts, utilization inputs, and location.
Does mTracker compute OEE?
No — mTracker provides the equipment-side OEE inputs from digital signals: run / stop, cycle / output count, and time-state signals. EREMOS V2 computes OEE and utilization analytics, combining those inputs with the configured production context — planned time, ideal cycle, product / SKU, and quality data where required. The device captures and reports the signals; the platform does the math.
Can it track mobile equipment, not just fixed machines?
Yes. GSM/GPS + battery backup are designed for fixed plants and mobile assets alike; geo-fence alerts cover location and compliance. Mounting and antenna placement for mobile assets are confirmed during BOM scope.
What does it need from the equipment to read run-hours?
Access to equipment-level digital signals (run / stop, cycle, or output-count). The available signals, their voltage/contact type, and the OEE-input mapping are confirmed during BOM scope; where a signal isn't exposed, we scope how to derive it.
Is it certified? What about IP65 / IP67?
No formal third-party certifications are currently claimed. Certification, ingress-protection, and site-compliance requirements are handled case-by-case during BOM scope. Where an asset (including mobile/outdoor) requires IP65 / IP67-compatible protection, Elpis can scope a compatible configuration or enclosure approach; formal certification or rating claims are published only when the specific product/configuration has the required certification or test evidence.
For OEMs — can it drive service-hours billing and warranty?
Yes — that's a core use. Equipment-level run-hours and utilization feed service-hours billing, warranty triggers, and fleet visibility on shipped equipment. See the OEM outcome → /solutions/oem-machine-monitoring.
How long does the battery last, and how is it powered?
Battery backup covers assets without continuous power; supply, current draw, runtime, and charging/replacement are confirmed during BOM scope against the duty cycle and reporting interval.
Bring us the assets you can't see.
A list of the assets to instrument, the signals available on each, and where they sit (fixed or mobile) — that's what we scope a BOM against. We confirm the inputs, power, and mounting for your assets, not for a brochure.