Pre-pilot evidence roadmap
Research and design
Trackers, beacons, radio, gateways, event models and dashboard work.
Assets and equipment first
The initial scope excludes public person tracking and requires explicit consent for human-related visibility.
Evidence before coverage claims
No public coverage, event-delivery or uptime promise is currently made.
3ntTrackNET
Privacy-controlled tracking infrastructure for assets, equipment and approved mobile operational objects across logistics, facilities, infrastructure and field operations.
Target architecture
From a moving asset to a controlled operational event.
Identity, radio transport, event quality, observability, recovery and privacy are treated as one operational system.
Trackers and beaconsApproved vehicles, equipment and assets.
Local radioLoRa and site-local movement signals.
Site gatewaysReception, validation and offline buffering.
Event pipelinePresence, movement and zone transitions.
Regional serverPrivate storage, health and operational logic.
Approved viewsDashboards, alerts and sanitised export.
Development roadmap
Five phases, each with an evidence gate.
Target windows are planning ranges rather than launch commitments. Progress depends on measured technical and operational results.
In progress
35%
Foundation and decision package
- Approve the 3ntTrackNET product direction and first pilot boundary
- Select tracker, beacon, gateway, enclosure and power candidates
- Define asset identity, event, retention and dashboard models
- Document consent, privacy and human-location exclusions
- Map 3ntCommCore and Regional Server integration
- Write laboratory acceptance tests and rollback procedure
Decision gate: Approved laboratory architecture, hardware shortlist, privacy model, event schema and evidence plan.
Private asset-tracking laboratory
- Connect approved trackers, beacons and local gateways
- Generate presence, movement and zone-transition events
- Test local-radio transport, buffering and reconnect behaviour
- Build local dashboards, alerts and device-health views
- Measure event latency, battery life and missed observations
- Create backups, rebuild instructions and maintenance records
Decision gate: Repeatable asset events, predictable recovery, known battery behaviour and no public location leakage.
Controlled operational pilot
- Operate with known vehicles, equipment and approved assets
- Define zones, permissions and operational workflows
- Expose only sanitised summaries outside the local system
- Test lost-device, stale-data and gateway-failure procedures
- Measure radio reliability, support burden and pilot value
- Record limitations and a go/no-go decision for each use case
Decision gate: Representative field evidence, privacy approval and a recorded decision for each intended use case.
Regional resilient 3ntTrackNET
- Add gateways and coverage only where measurements justify them
- Provide redundant 3ntCommCore and backhaul paths
- Introduce fleet, yard and equipment-maintenance integrations
- Archive event-quality and incident evidence
- Integrate Regional Telemetry Node and controlled federation
- Define recovery exercises and service-level options
Decision gate: Evidenced operational area, funded ownership, tested recovery and approved production terms.
Productisation and federation
- Managed vehicle, equipment and asset visibility
- Private zone, presence and movement dashboards
- Standard tracker, beacon and gateway packages
- Regional event federation with local data ownership
- 3ntSensorNET, 3ntRTKNet and field-system integration
- Commercial packaging based on measured demand and support capacity
Decision gate: Expansion follows measured demand, event quality, privacy approval and support capacity.
Quality, resilience and privacy
Tracking must remain operationally useful and privacy-defensible.
Measure continuously
- Tracker, beacon and gateway uptime
- Event latency and missed observations
- Battery state and replacement history
- Radio quality and reconnect behaviour
- Zone-transition consistency
- Configuration and firmware changes
Protect people and assets
- Operational assets rather than public person tracking
- Explicit consent for any human-related visibility
- Private dashboards and least-privilege access
- No public raw coordinates or movement history
- Controlled retention and sanitised reporting
- Credential rotation and revocation
Engineer resilient tracking
- Suitable tracker and enclosure for each asset
- Battery, vehicle and fixed-power options
- Gateway placement based on measurements
- Offline buffering and delayed event delivery
- Lost-device and stale-data procedures
- Documented recovery and rollback
Candidate use cases
- Logistics yards and vehicle presence
- Farm and field equipment visibility
- Tools, trailers and mobile operational assets
- Facility zones and equipment movement
- Resilience pilots and controlled incident awareness
Current boundary
3ntTrackNET remains in staged development. This page does not advertise public person tracking, a defined coverage area, guaranteed event delivery or an SLA.
Pilot collaboration
Help test the right asset-visibility problem.
3nt is interested in technical and operational partners for controlled vehicle, equipment and asset-visibility validation.
Contact the team