InTouch platform and product benchmark
Reviewed on 10 November 2026. This is a feature and architecture comparison of published first-party documentation. The shortlist covers managed infrastructure, self-hostable device management, operational SaaS, consumer sharing and industrial historians. The right comparator depends on the buyer and workload. Vendor latency, accuracy, battery, reliability and cost have not been tested here.
Platform engineering
| Reference | Documented capability | InTouch product requirement inferred from it | Pilot test |
|---|---|---|---|
| AWS IoT Core + Greengrass | An application can change a shadow while the device is offline. Greengrass Stream Manager exposes storage, retention, export priorities and bandwidth policies per stream. Device shadows · Stream Manager | Keep desired and applied revisions, policy owner and rejection reason. Give incident metadata, routine telemetry and video independent queues and budgets. | Change policy twice while a gateway is offline. On reconnect it applies the current valid revision, publishes its effective limits and sends an incident before bulk video. |
| Microsoft Azure IoT Edge | After first synchronization, a gateway can authenticate provisioned downstream modules/devices and buffer upstream traffic. Capacity and message lifetime bound how much can survive an outage. Extended offline operations | Track parent gateway, child identity, clock quality, queue watermark, dropped range and expiry. Make disconnected commissioning a separate enrollment capability. | Disconnect a provisioned parent, reboot it, collect child measurements, then reconnect. Reconcile counts with the configured TTL and disk cap. |
| ThingsBoard CE | Dashboard operations use server-side RPC. Persistent requests can wait through disconnects and expose queued, sent, delivered, result and expiry states. Command and control | Use commands with deadlines and result reporting for discrete actions. Use versioned policy for continuous configuration. Scope each operation by device capability. | Expire a command offline and confirm that reconnecting cannot cause execution. Redeliver an acknowledged command and inspect its one business effect. |
| AWS IoT SiteWise | Asset models contain measurements and hierarchies. Transforms derive values and metrics aggregate properties within time windows or across assets. Asset models | Give sensors versioned unit, axis and quality definitions. Bind sensor/channel identities to an asset over time and persist the formula version on a derived KPI. | Move a vibration probe between motors. An earlier shift's report still attributes its data to the original motor. |
| Inductive Automation Ignition | The historian records tag value, timestamp and quality. Deadbands and sampling modes determine what goes into history. Store and Forward provides memory and disk buffering on the path to a database. Tag history · Store and Forward | Preserve quality through historian views. Set channel-specific deadband, max silence and raw incident windows. Plot missing periods as gaps. | Replay stable temperature, a transient spike, bad quality and a disconnect. Verify trend fidelity, maintenance alert context and storage growth. |
Products and operational workflows
| Reference | Documented capability | InTouch design decision | Evaluation case |
|---|---|---|---|
| Mappls InTouch | The existing product advertises live tracking, trip assignment, configurable dashboards, geofences, driver behaviour, vehicle diagnostics and APIs for devices, events and drives. Existing InTouch platform | Preserve existing customer concepts. Inventory the existing schema and contracts with their owners before defining ID mappings, coexistence and a tenant-by-tenant migration. | Dual-read an opt-in test fleet. Compare device assignments, trip endpoints, geofence transitions and event counts before moving readers. |
| Samsara | Its vehicle gateway uses accelerometer data for driving events. Its safety API relates events to dashcam footage, and it exposes driver and vehicle aggregates. Driver behavior | Put event evidence and review decisions on one timeline. Identify the detector version, physical mount and confidence. Media may arrive later than the event. | A rough-road event arrives over cellular. An authorized reviewer sees its trace immediately and can review the later Wi-Fi clip. An overturned event is excluded from reviewed totals. |
| Geotab MyGeotab | An integration supplies a persisted version token to fetch changes incrementally. Consumers can resume from a prior cursor. Data feed | Offer resource-scoped change feeds for ERP, TMS and reporting. Cursors advance on ingestion order so a late device observation remains discoverable. | Stop a connector during a page, replay from its last committed cursor and reconcile one downstream record per source revision. |
| project44 | The truckload API exposes shipment milestones, positions, route sections and stops, through queries or webhook updates. The carrier API accepts temperature, position, status and ETA observations. Shipment visibility · Carrier updates | Treat a shipment and its legs as business objects independent of the assigned equipment. Qualify each ETA by source and age. | Transfer a refrigerated shipment to a new trailer. The customer sees a continuous shipment timeline while the new carrier sees only its leg. |
| Google Maps Platform Fleet Engine | It models on-demand trips separately from scheduled delivery tasks. A delivery stop can include several tasks. Driver and consumer SDKs serve different journey views. Overview · Scheduled tasks | Separate fleet-wide dispatch, rider work orders and trip-scoped customer reads. A stop can succeed physically while one parcel fails verification. | At one apartment complex, complete two parcels and mark a third undeliverable. Only the affected recipient sees the failure. |
| Uber Direct | Deliveries can require picture, signature or barcode verification. Result details appear in the delivery response and status webhooks. Proof of delivery | Model verification requirements and outcomes per task. Keep proof objects behind separately authorized, expiring retrieval. | A courier scans the wrong parcel offline. Reconnect, surface the mismatch and keep the task open until a valid outcome is recorded. |
| Life360 | Sharing can be paused per Circle. Members can configure place arrival and departure notifications. Location sharing · Places | Make consent specific to group, precision, purpose and expiry. Separate personal sharing from work-shift telemetry even when both originate on one phone. | Pause a family audience while a shift remains active. Replaying a delayed batch cannot reveal the paused period to family viewers. |
Build, integrate and verify
- Build the common capture path. A phone, browser and board need the same sample identity, observed time, event lineage and replay contract. They need different clock, storage and scheduling adapters. Android hardware batching and the selected iOS location accuracy materially affect energy use. Android sensor guidance · Apple location efficiency
- Integrate existing Mappls routing. Query a bounded shortlist of vehicles against a versioned, licensed route provider. Cache results for a defined freshness window. Distinguish provider failure, an unreachable route and stale input in the dispatcher UI. The published distance-matrix service accepts source and destination coordinates and returns route distances and durations. Mappls Distance Matrix
- Stage industrial integration. Begin with read-only gateways, timestamp/quality propagation and a historian. Validate site-specific write paths with operations staff and certified local controls. Launch consumer sharing only after grant expiry, revocation and delayed upload tests pass.
Comparative performance trial
Use the same vehicle route, payload schema, requested sample rates, capture permission state and device hardware when the comparison permits. Record unsupported scenarios as such. Publish OS version, build, radio, signal level, ambient temperature, duty cycle, broker region, quotas, cache policy and payload sizes with each result. Run at least three repetitions per profile and report median plus range. Use emulators to check protocol behavior and physical devices for power readings.
| Workload | Collect | Pilot decision |
|---|---|---|
| One-hour stationary and moving phone, screen off | Incremental mWh against same-device idle, fix accuracy/age, delivered observations, process wakes and bytes including transport overhead | Reduce requested accuracy or increase batch age until energy and freshness meet the agreed field profile. Report Wh/hour alongside percentage of the tested battery. |
| Thirty minutes disconnected, 25 Hz three-axis motion and 1 Hz position | Expected/received sample IDs, duplicates, oldest pending age, queue bytes, drain time, drop reasons and live-event delay during drain | Accept within-capacity replay only when the manifest reconciles fully after a client restart and lost ACK. |
| Two incident clips per hour under a metered link | Encode duty cycle, metadata latency, clip size, media retries, dropped frames, peak RAM, display-ready delay and per-device daily bytes | Keep urgent metadata flowing under a full media queue. Compare clip-only and opt-in live video as separate workloads. |
| Fleet ingest and tenant read contention | Acknowledgement and query p50/p95/p99, devices/s, samples/s, worker CPU, durable-write IOPS, active sockets and per-tenant throttles | Raise concurrency to saturation and repeat with one noisy tenant. Record throughput at the agreed latency, retention and durability level. |
| Thirty-day normalized cost | Device hours, messages after provider rounding, rules, stored GiB-days, video transfer, reads, cross-zone traffic and operator time | Quote an identical bill of materials in the same region and currency. Show separate costs per device-month and per retrieved clip. Use dated provider price quotes during procurement. |
A 20-second clip at 1 Mbit/s represents roughly 2.5 MB of encoded media. Two clips per hour over an eight-hour shift generate roughly 40 MB before headers or retries. This sizing example motivates the media budget and remains independent of vendor performance claims.