Cold-Chain Thermal Management Platform
Commercial Temperature-Sensitive Asset Tracking & Alerts
1. SYSTEM OVERVIEW
A thermal tracking platform deployed on harizeon.com that captures IoT sensor streams, plots container temperature metrics, and triggers instant alerts for cold-chain compliance.
Perishable goods spoil in transit when container cooling fails, but operators only found out at delivery, leading to massive inventory losses and liability claims.
Zero inventory spoilage over a 90-day pilot run, providing certified audit logs to temperature-sensitive pharmaceutical and food cargo insurers.
- Ingest continuous telemetry updates from multiple container GPS sensors
- Instantly trigger alarms when temperature drifts outside the strict 2°C - 8°C boundary
- Provide interactive simulation preview for cargo planning verification
- Built backend log receivers and configured data ingestion streams
- Designed React state machine mapping temperature telemetry into alert models
- Implemented dashboard map grids and route visualization charts
2. SYSTEM FEATURES
Interactive slider widget replicating live container temperature fluctuations and alarm states.
Visual map system rendering route legs, current GPS positions, and thermal markers.
Granular workspace views giving clients, drivers, and safety auditors distinct data visibility.
3. SYSTEM ARCHITECTURE
Connected tracking system monitoring cold-chain containers. IoT streams route to Express backends, caching data in DynamoDB and sharing real-time states with clients via secure sockets.
IoT Temperature Sensors ──> AWS IoT Core ──> Node.js Express Receiver
│
┌──────────────────────────────────────────────┘
▼
DynamoDB (History) ──> React Client (WebSockets) ──> Dynamic Warning Banners
│
└─[Drift Detected < 2°C or > 8°C]─> AWS SNS SMS Alertcold-chain/
├── src/
│ ├── components/
│ │ ├── TempControl.tsx # Slider control
│ │ └── MapTracker.tsx # Route rendering
│ ├── server/
│ │ ├── index.js # Express configuration
│ │ └── routes.js # Telemetry APIs
└── public/
└── assets/ # Assets and route vectors4. INTERACTIVE SIMULATOR WIDGET
Run active operations audits utilizing the custom sandbox telemetry receiver widget below.
Adjust the thermostat slider below to simulate container cooling state changes. Audits expect temperature to persist strictly between 2°C and 8°C.
5. ENGINEERING ARCHITECTURE DECISIONS (ADRs)
Vehicle hardware runs on low-power cell chips with volatile connection dropouts on rural highways.
- HTTP/2 JSON Polling
- gRPC streams
- MQTT via AWS IoT Core
MQTT via AWS IoT Core
- Minimal packet overhead, conserving mobile data costs
- Automatic re-connection and state-caching (Device Shadows)
- Highly secure, requiring client certificate authentication
- Requires setting up and managing TLS client certificates on hardware
- Slightly higher setup complexity
Accepted client-certificate setup complexity in return for rock-solid connection persistence and 70% lower data payload costs.
Integrate cellular cell-tower triangulation fallbacks for times when GPS modules lose direct line-of-sight to satellites.
6. DETAILED TECHNOLOGY STACK
7. SECURITY REVIEW & POSTURE
Spoofed sensor telemetry could mask thermal failures or inject fake routes.
Inspecting route records exposes valuable corporate transport pathways to competitors.
8. PERFORMANCE METRICS TELEMETRY
Optim:Websockets link between Node server and React client, bypasses standard database polling.
Optim:MQTT deep sleep mode optimization, sending events only on temperature delta or 5-min intervals.
9. ENGINEERING CHALLENGES & RESOLUTIONS
Under extreme cold climates, containers naturally drop below 2°C, causing false alerts even when cargo remains safe.
Root Cause:Alert thresholds were static and did not consider product-specific thermal inertia or packaging buffers.
Correlated physical cargo inspections with sensor histories, noting that internal packaging insulated the actual products from short external chills.
Configured a 15-minute integration window where temperature must remain outside boundary limits before triggering critical alerts.
Delayed alert dispatch by up to 15 minutes, but eliminated 98% of cold-weather false warnings.
Telemetry triggers must align with physical material buffer properties rather than raw sensor limits.
10. SYSTEM LESSONS LEARNED
Always code sensor data processing handlers defensively; corrupted packets are common over cellular streams.
Using AWS Device Shadow patterns ensures that offline vehicles automatically update their state upon reconnecting.
Audited log certification is highly valued by clients; providing exportable PDF certificates builds customer trust.
I would swap our Express socket server with Socket.io clusters to scale vehicle connections to thousands.
11. ROADMAP & TECHNICAL DEBT
- Integrate machine-learning prediction for container cooling failure times
- Support bluetooth temperature sensor aggregators
- Add geofencing warnings for high-risk route stops
12. GITHUB SOURCE EXPLORER
Audit raw repository script configurations directly inside the active terminal workspace.