TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
01 / 12
Asset Recovery Proposal

Asset Recovery Proposal for Coca-Cola Global Equipment Platform

Device options, data architecture, and pilot path for global equipment recovery, presented with a transparent commercial and technical view for board-level evaluation.

Prepared By TrackGPS by AROBS
Format Technical + Commercial Proposal
Date June 2026
01
Recovery-First Scope
The proposal is centered on equipment recovery, location visibility, battery life, and low-touch field operations.
02
Transparent Option Comparison
Each solution will be presented on the same structure, with consistent pricing logic.
03
Pilot-to-Scale View
The presentation is designed to support a 100-unit pilot decision while showing clear indicative pricing at 1,000 and 10,000 units.
(c) 2026 TrackGPS by AROBS Board Proposal Draft
Coca-Cola Global Equipment Platform
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
02 / 12
Executive Summary

Recovery-first decision framework for Coca-Cola equipment visibility

The immediate objective is faster asset recovery with lower operational effort, using a solution path that can scale across bottlers.

The Business Problem

Equipment can move out of place without enough recovery visibility.

Assets can leave their expected location without enough recovery traceability, creating recovery delay, replacement risk, and unnecessary manual effort in the field.

Why It Matters

This is bottler capital with direct operational impact.

The first decision is not full telemetry. It is better recovery visibility and movement awareness with a deployment model that stays practical in day-to-day operations.

Operational Reality
Devices must be easy to install.
Battery service events must stay low.
Data must be usable across Coca-Cola and bottlers.
What Success Looks Like
Reliable visibility into where the equipment is.
Long battery life with low service burden.
Low-touch installation in the field.
Portable data for Coca-Cola and bottler systems.
Phase 1 focus: location visibility, movement awareness, battery endurance, scalable deployment
(c) 2026 TrackGPS by AROBS Executive Summary
Business problem, success criteria, and recovery-first scope
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
03 / 12
TrackGPS Footprint

Relevant scale, real deployments, and operational credibility

Before selecting a device path, the board should also see the operating base behind the proposal: active deployments, enterprise adoption, and a platform already used at scale.

20+
Years of industrial expertise
9,700+
Enterprise clients worldwide
150K+
Active assets tracked daily
99.9%
Mission-critical uptime SLA
Why This Matters

The proposal is backed by an existing operating platform, not a greenfield concept.

The value for Coca-Cola is not only the device selection itself, but the ability to connect that device into a proven asset-tracking environment with established service and support discipline.

Heat map and market footprint visual can be added in the next iteration
What This Demonstrates
TrackGPS already operates at enterprise scale with daily monitored assets.
The proposal is grounded in deployment experience, not only in hardware evaluation.
The same platform logic can support recovery-first rollouts and later expansion.
(c) 2026 TrackGPS by AROBS TrackGPS Footprint
Existing scale behind the proposed solution path
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
04 / 12
Heatmap & Country Activation

Existing GPS footprint with strong European density and visible global activation

View based on real-time location data flowing through the TrackGPS IoT Hub ecosystem, framed to keep the core European cluster visible while also showing activity in Indonesia and the United States.

Heatmap View
TrackGPS global heatmap with Europe, Indonesia, and United States activity
Static heatmap view based on the current GPS footprint, emphasizing the European core while keeping Indonesia and U.S. activity visible in the same frame.
Activation Focus

Europe is the operational core, with additional live signal visible in Indonesia and the U.S.

This helps the board see that the current footprint is not only local density around the core European base, but also includes visible international activity.

Current Dataset Signal
94% Europe traces
4% Indonesia traces
1% U.S. traces
What The Board Should Read
The dominant operational density is in Europe, supporting the primary business case discussion.
Indonesia appears as a meaningful secondary activity cluster outside the European core.
The U.S. signal is smaller, but it confirms broader global spread in the current dataset.
The same visual layer can later be connected to live production feeds if a client-facing footprint view is required.
(c) 2026 TrackGPS by AROBS Heatmap & Country Activation
Current GPS dataset footprint with Europe core and visible global spread
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
05 / 12
Processing Architecture

Existing IoT data processing backbone

High-level infrastructure view: ingest, route, process, and deliver asset data.

TrackGPS high-level IoT Hub processing diagram
(c) 2026 TrackGPS by AROBS Processing Architecture
Ingestion, ordering, event routing, and service distribution
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
06 / 12
Integration & Open Data

Existing IoT integration capabilities ready for enterprise delivery

Beyond device connectivity, TrackGPS already operates the ingestion, processing, normalization, and enterprise delivery layer required to turn field events into client-ready data.

Ordered Ingestion Receive, acknowledge, and control device event flow from the field layer.
Processing & Normalization Decode, enrich, route, and persist asset data into the existing platform backbone.
Enterprise Integration Deliver structured outputs through existing client-facing interfaces and service paths.
Portable Data Model Support reusable outputs across Coca-Cola and bottler-side environments.
What Already Exists Today

This is not a greenfield integration model.

TrackGPS already has the operational backend and service logic required to receive device-originated data, process it, and deliver it onward through enterprise integration paths.

.NET Full Framework ingestion and processing layer already used in production operations.
Hybrid infrastructure model using Azure Event Hub for scalable event routing and downstream distribution.
Existing HUB and IoT processing backbone for ordered message handling and downstream routing.
Established platform logic for normalization, persistence, mapping, and client-specific delivery.
Integrator model already positioned between device data capture and enterprise consumption systems.
Open Delivery Methods Already Supported

Client-facing integration interfaces are already part of the current operating model.

TrackGPS can adapt device and platform data into established enterprise delivery methods, making the output portable rather than locked into a single device ecosystem.

FTP File-based enterprise delivery for scheduled downstream consumption.
Kafka Streaming-oriented integration path for event-driven consumption models.
JSON APIs Structured service delivery for application-level integration and data exchange.
SOAP Connectivity Compatibility with enterprise systems still using service-based legacy interfaces.
TrackGPS Positioning TrackGPS acts as the orchestration layer between device-originated data and enterprise consumption systems, reducing integration risk while keeping the data model open and portable.
(c) 2026 TrackGPS by AROBS Integration & Open Data
Existing backend, enterprise interfaces, and portable client delivery model
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
07 / 12
Device Option 1
Recovery Tag Device
7-year battery Small tag form factor Fast implementation

Recovery Tag Device

A compact tag device, similar in concept to an AirTag, designed for recovery-oriented asset visibility with long battery life and rapid deployment potential.

Connectivity Type Uses nearby Android and iOS phones to capture location events, then data is made available through the platform layer.
Estimated Battery Life Estimated battery life: 7 years.
Installation Guide Mounted with double tape in a protected area of the refrigerator.
Dimensions 59 x 39 x 15 mm.
2.32 x 1.54 x 0.59 in.
Functionality Flow
Refrigerator + Tag Tag is attached in a protected mounting area
→
Nearby Phones Android and iOS devices detect the tag presence
→
Cloud Service Location data is collected through the ecosystem service layer
→
TrackGPS by AROBS Data is received, processed, and mapped inside the TrackGPS platform
→
Coca-Cola API Processed recovery data is sent onward via API
(c) 2026 TrackGPS by AROBS Device Option 1
Compact recovery-oriented tag device with ecosystem-assisted location flow
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
08 / 12
Device Option 1

Decision view for the Recovery Tag Device

Commercial and operational view of the compact tag option, including deployment strengths, adoption risks, rollout timing, and cost structure.

Strengths & Weaknesses

Strengths

Fast implementation path with ready-to-use tag form factor.
Small device dimensions simplify protected placement on the refrigerator.
Long estimated battery life supports low-touch field operations.

Weaknesses

No true real-time data flow in the same sense as a cellular GPS device.
Location visibility depends on mobile devices being near the asset.
No motion detection, which means no real-time movement alert unless a new nearby phone creates a new position update.
Implementation Timeline
10 Working Days

Order and testing

Initial order placement, sample handling, and internal testing after agreement.

15 Working Days

Development and integration

Platform-side development and integration toward the Coca-Cola system interface.

10 Working Days

Shipment and activation

Product delivery, real activation, and installation execution in the field.

Cost Structure

Estimated total implementation timeline: 35 Working Days from agreement to shipment, activation, and installation readiness.

The solution can be delivered either as a service model or as a client-owned platform model.

Hardware One-Time Fee Per-device acquisition cost for the recovery tag hardware.
Monthly Data / Platform Fee Recurring fee for the connected location data and platform access model.
100 Sample Devices Initial pilot batch structure for validation and first deployment wave.
1,000 and 10,000 Devices Volume-based commercial structure to be compared consistently against the other device option.
(c) 2026 TrackGPS by AROBS Device Option 1
Rollout considerations, delivery timing, and commercial structure
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
09 / 12
Device Option 2
Asset Tracker AT1 Device
MVNO SIM connectivity Up to 5-year battery Existing GPS platform Integrated in TrackGPS IoT

Asset Tracker AT1 Device

A compact existing GPS asset tracker designed for recovery-oriented deployments, with direct MVNO SIM connectivity and stronger control over data flow than phone-dependent tag solutions. eSIM-ready architecture can further reduce SIM-related physical failure points and improve long-term deployment flexibility. Indoor positioning can also fall back to LBS triangulation based on the available 4G or 2G GSM cell. This is an existing device integrated into the TrackGPS IoT system.

Connectivity Type MVNO SIM connectivity with direct GPS data transmission into the TrackGPS processing path.
Estimated Battery Life Up to 5 years, assuming GPS enabled and 1 coordinate per day.
Installation Guide Can be mounted with double tape in a protected area of the refrigerator, with optional magnet-based attachment.
Dimensions 64.6 x 51 x 28.3 mm.
2.54 x 2.01 x 1.11 in.
Functionality Flow
Refrigerator + GPS Tracker Tracker is installed on the refrigerator as the recovery device
→
MVNO Network Device sends data through the MVNO SIM connectivity path
→
TrackGPS by AROBS Data is received into the TrackGPS server and routed into the IoT pipeline
→
IoT Hub + Processing Data is processed, normalized, and mapped inside the existing platform backbone
→
Coca-Cola Systems Processed recovery data is sent onward to Coca-Cola servers
(c) 2026 TrackGPS by AROBS Device Option 2
Existing GPS tracker with direct MVNO-based recovery data flow
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
10 / 12
Device Option 2

Decision view for the Asset Tracker AT1 Device

Commercial and operational view of the existing GPS tracker option, including deployment strengths, practical trade-offs, rollout timing, and cost structure.

Strengths & Weaknesses

Strengths

Fast implementation using an existing device platform.
Direct MVNO SIM connectivity with no dependency on nearby mobile phones.
Indoor positioning can fall back to LBS triangulation based on available 4G or 2G GSM cell data.
Better control over data acquisition and delivery path.
Stronger fit for recovery use cases where asset movement needs more deterministic visibility.
Good battery management profile for a GPS tracker under low-frequency reporting logic.
Flexible mounting options with double tape and optional magnet attachment.
eSIM-ready architecture can further reduce SIM-related physical failure points and improve long-term deployment flexibility.

Weaknesses

Larger and more visible than a passive tag solution.
Battery autonomy depends on reporting profile, GPS fix quality, and field conditions.
Installation remains simple, but is more deliberate than a pure stick-on consumer-style tag.
Implementation Timeline
10 Working Days

Order and testing

Initial order placement, sample handling, and internal testing after agreement.

15 Working Days

Development and integration

Platform-side development and integration toward the Coca-Cola system interface.

10 Working Days

Shipment and activation

Product delivery, real activation, and installation execution in the field.

Cost Structure

Estimated total implementation timeline: 35 Working Days from agreement to shipment, activation, and installation readiness.

The solution can be delivered either as a service model or as a client-owned platform model.

Hardware One-Time Fee Per-device acquisition cost for the GPS tracker hardware.
Monthly Data Connectivity Fee Recurring fee for the MVNO SIM connectivity and connected data flow.
100 Sample Devices Initial pilot batch structure for validation and first deployment wave.
1,000 and 10,000 Devices Volume-based commercial structure to be compared consistently against the other device option.
(c) 2026 TrackGPS by AROBS Device Option 2
Rollout considerations, battery trade-offs, and commercial structure
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
11 / 12
Phase 1 - POC

Fixed-fee pilot package to validate the operating model before scale

Phase 1 is structured as a flat-fee POC package, independent of the selected device option, designed to validate field installation, data delivery, and operational readiness before wider deployment.

Why This Phase Matters

Low-risk commercial entry point with full operational validation.

The same commercial POC structure applies whether the pilot uses the Recovery Tag Device or the Asset Tracker AT1 Device.
The objective is to prove installation, recovery visibility, integration flow, and field support in a controlled first phase.
This creates a cleaner decision path for scale by validating operational reality before broader rollout.
Flat-Fee POC Structure

One managed pilot package, regardless of selected device path.

Commercial Model Fixed implementation fee for Phase 1 - POC, kept separate from later scale economics.
Device Independence The package structure remains the same even if the pilot is executed with either of the two device options.
Board-Level Advantage Allows Coca-Cola to validate the recovery approach first, then optimize the larger commercial rollout with better evidence.
Services Included in Phase 1
Hardware & Connectivity Hardware cost for selected pilot units, connectivity, and platform access required to run the POC.
Integration & Solution Setup Device onboarding and configuration, IoT data ingestion and platform integration, recovery event processing and business-rule mapping, and API delivery setup toward Coca-Cola systems.
Deployment & Field Readiness Deployment logistics, training and initial setup in 2 geographical zones, and field activation support.
Governance & Support Customer support, feedback sessions, and project management throughout the pilot execution window.
Phase 1 Flat Fee
One-Time Fee
USD 60,000

One-time POC fee, independent of the selected device option.

Covers the managed pilot package for setup, integration, field readiness, and pilot support required to validate Phase 1 before scale.

(c) 2026 TrackGPS by AROBS Phase 1 - POC
Fixed-fee pilot package to validate operations before scale
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
12 / 12
Phase 2 - Product Rollout

Products and services offered for large-scale rollout

After POC validation, the production model can be structured around either device path. The comparison below shows the same cost areas and operating trade-offs for both options.

Post-POC Productization Note

The initial productization fee after POC reflects the effort required to move from validated pilot to production rollout. Based on POC findings, this may include custom application development, workflow adjustments, API refinement, and required ecosystem modifications.

Cost & Operating Comparison

Direct comparison of fixed and recurring costs across both device paths.

Cost / Product Area
Asset Tracker AT1 Device
Recovery Tag Device
Productization Fee
Setup after POC
USD 500,000 - 600,000
Custom application development and production adjustments if needed.
USD 500,000 - 600,000
Custom application development and production adjustments if needed.
Training & Enablement
Distributor readiness
USD 12,000 - 15,000
Onboarding support for rollout teams.
USD 12,000 - 15,000
Partner-side onboarding and field readiness.
Activation Fee
Per-asset activation
USD 10 - 12
Direct tracker operating model with better cost efficiency.
USD 10 - 15
Variable depending on external ecosystem setup.
Monthly Service Fee
Device, connectivity, and platform
USD 3.29
Optimized recurring cost in production.
USD 6.67
Higher dependency on ecosystem-based location model licensing.
AT1 Production View
Direct real-time tracking with direct tracker-based recovery data flow.
Up to 5-year battery life, balancing endurance with stronger operational visibility.
Better GPS accuracy supports more deterministic recovery positioning.
Movement-triggered visibility and notifications support stronger live recovery operations.
Lower recurring cost per asset supports scaled rollout more efficiently.
Tag Production View
Ecosystem-dependent reporting relies on third-party location network detection.
Up to 7-year battery life offers longer endurance, but with visibility trade-offs.
Lower positioning accuracy depends on ecosystem detection and reporting conditions.
Lower real-time determinism means no guaranteed movement alerting.
Higher monthly recurring fee comes with lower operational certainty for recovery response.