MitsiTrack — Telematics Product Function Description
1. Purpose and scope
This document defines what MitsiTrack does: an STW TCG4 gateway fitted to Mitsubishi refrigerated units, reporting to a Cumulocity IoT tenant. It is the reference for sales, customer onboarding, firmware and platform configuration.
In scope: device functions, platform functions, data, alarms, alerts, reports and security. Out of scope: commercial pricing, installation procedures and the Mitsubishi reefer controller's own internal logic.
2. Product overview
MitsiTrack gives fleet and cold-chain operators live and historical visibility of where each Mitsubishi reefer is and how it is performing. The device reads the reefer and vehicle data locally and sends it over encrypted 4G; the platform stores, displays, alarms on and reports it.
| Component | Role |
|---|---|
| STW TCG4 telematics gateway | In-vehicle hardware: reads reefer and CAN data, GPS position, sends data over 4G |
| MitsiTrack firmware | Custom application on the TCG4: reefer protocol, sampling, buffering, event logic |
| Cumulocity IoT | Cloud platform: device management, data storage, dashboards, alarms, rules, exports |
| MitsiTrack web application | Customer-facing views built on Cumulocity: map, reefer status, graphs, reports |
Target users are transport operators, cold-chain logistics managers, dispatchers and service technicians.
3. System architecture
Data flows one way from reefer to user, with configuration and firmware flowing back from the platform to the device.
The TCG4 buffers data when coverage is lost and uploads it on reconnection, so history has no gaps. Wi-Fi is a secondary path for depot upload, diagnostics and firmware updates.
4. Device functions (STW TCG4)
The TCG4 provides six functions. Hardware figures should be confirmed against the current STW TCG4 datasheet before release.
| ID | Function | Description | Key behaviour |
|---|---|---|---|
| D1 | 4G cellular M2M, encrypted | LTE M2M SIM connection to the Cumulocity tenant | TLS-encrypted MQTT/HTTPS; per-device credentials; auto-reconnect; store-and-forward buffer during coverage loss |
| D2 | CAN bus | Reads vehicle and equipment CAN messages | Configurable message/signal decoding (e.g. ignition, engine hours, battery voltage); bit rate set per install |
| D3 | Wi-Fi | Local wireless connectivity | Depot data offload, technician diagnostics, local firmware and configuration updates |
| D4 | Mitsubishi reefer interface | Reads the Mitsubishi reefer controller | Setpoint, return/supply air temperature, operating mode, unit on/off, defrost state, alarm codes, run hours |
| D5 | GPS | Satellite positioning | Latitude, longitude, speed, heading, fix quality; position attached to every data record |
| D6 | Customisable firmware | MitsiTrack application on the TCG4 | Configurable sample and send intervals, on-device event logic, remote configuration and over-the-air updates |
Default behaviour: the device samples reefer data continuously and sends a full record every 10 minutes. Reefer alarms, power-on/off and ignition changes are sent immediately, outside the interval.
5. Platform functions (Cumulocity IoT)
The platform delivers seven user-facing functions, each built on standard Cumulocity capabilities plus MitsiTrack configuration.
P1. Location tracking and history
- Live map of all units with status colour (running, off, in alarm).
- Trip history replay for any unit and date range, with speed and stop markers.
- Last known position and time shown when a unit is offline.
P2. Reefer monitoring, live and historical
- Live view per unit: setpoint, return and supply air temperature, mode, defrost, active alarms.
- Default update every 10 minutes; interval configurable per customer or per unit.
- Full history retained for trend and compliance review.
P3. Data visualisation
- Time-series graphs of temperatures against setpoint, with alarm and event markers.
- Tables of readings, events and alarms, filterable by unit, fleet group and date.
- Configurable dashboards per customer or user role.
P4. Reefer alarms
- Mitsubishi controller alarm codes shown with a plain-language description.
- Severity levels (critical, major, minor, warning) mapped from the reefer code.
- Alarm lifecycle: active, acknowledged, cleared, with timestamps and user.
P5. Customisable user alerts (email)
- Users choose which alarms or events trigger an email, and for which units.
- Recipient lists per customer, fleet group or unit.
- Example rules: temperature outside setpoint ±X °C for more than Y minutes; unit powered off; no data for Z hours.
P6. Customised event programming
- Rule-based logic on the platform (Cumulocity smart rules and streaming analytics) or on the device firmware.
- Example — preload timer trial: when a unit reaches setpoint before loading, start a timer; raise an event if temperature holds for the required time, or an alarm if it fails.
- Other examples: door-open duration, pull-down time, defrost frequency.
P7. Historical data download reports
- Export selected units, fields and date range to CSV or Excel.
- Standard reports: temperature log, alarm history, trip and location history.
- Scheduled reports delivered by email (daily, weekly or per trip).
6. Data model and reporting intervals
Each data point maps to a standard Cumulocity object type, so it works with built-in dashboards, alarms and exports.
| Data point | Source | Cumulocity type | Default interval | Configurable |
|---|---|---|---|---|
| Reefer alarm code | Reefer | Alarm | Immediate | No |
| Unit on/off | Reefer | Event | Immediate | No |
| Return air temperature (°C) | Reefer | Measurement | 10 min | Yes |
| Supply air temperature (°C) | Reefer | Measurement | 10 min | Yes |
| Setpoint (°C) | Reefer | Measurement | 10 min, and on change | Yes |
| Operating mode, defrost state | Reefer | Measurement / event | 10 min, and on change | Yes |
| GPS position, speed, heading | GPS | Location event | 10 min moving | Yes |
| Reefer run hours (h) | Reefer | Measurement | 60 min | Yes |
| Signal strength, device health | TCG4 | Measurement | 60 min | Yes |
| Custom events (e.g. preload trial) | Firmware / rules | Event or alarm | On trigger | Yes |
7. Security, users and permissions
Data is encrypted in transit end to end, and each customer sees only its own units.
- Device to cloud: TLS encryption over a private M2M APN; unique credentials per device; devices registered before they can send data.
- Customer separation: one Cumulocity tenant or sub-tenant per customer; no cross-customer visibility.
- User access: named logins with optional two-factor authentication; role-based permissions.
- Audit: alarm acknowledgements, configuration changes and firmware updates logged with user and time.