Reefer Container Monitoring
Reefer monitoring connects readings, alarms, unit status and carriage instructions. Local checks and telematics help reconstruct deviations: distinguish the set point from measured temperature and retain checks, actions and authorisations for changes.
Operational Explanation
The set point is the system’s target, not a direct measurement of every part of the cargo. Identify the sensor and recorded parameter, agreed limits and unit status before interpreting a deviation.
Local recording, transmission and remote display are different functions. Loggers and telematics have their own intervals, retrieval methods and coverage: missing or delayed data require investigation and alone prove neither refrigeration failure nor compliant temperature. Carrier/SMS checks remain applicable.
Regulatory Reference
Identify cargo instructions, the contract, carrier/SMS procedures and rules applicable to the product and voyage. SOLAS addresses ship safety; it does not prescribe one set point or universal monitoring frequency for all reefers. Relevant IMDG requirements also apply to dangerous goods.
Maersk — pharma monitoring; Maersk — remote monitoring services; WHO — storage and distribution guidance. Commercial service features are not a universal standard. Read WHO guidance alongside applicable legislation and product requirements.
Scope of Application
Ships carrying energized reefer containers or otherwise responsible under the contract and SMS for monitoring temperature-controlled container cargo; duties follow the actual carriage, equipment and agreed service.
Procedure / How to Complete It
- At loading check connection, settings and shipper instructions.
- Monitor and record at the frequency prescribed by contract, carrier procedure and SMS; daily is only an example.
- Investigate alarms and restore power or technical functionality under authorised procedures.
- Do not change set point, ventilation, humidity or atmosphere settings without documented instruction from the authorised party, except under an already approved emergency procedure.
- For every authorised change record request, authorisation, time, old/new setting and confirmation.
Practical Example
The portal stops receiving new data. The crew checks power, the unit and local records under the procedure, compares the last timestamp and reports the transmission problem. It does not change the set point to try to restore telemetry; local readings and the action history are retained.
What Typically Goes Wrong
Confusing technical remote-adjustment capability with contractual authority to change settings, or imposing a daily check where a continuous system or contract prescribes another frequency.
Common Mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Confusing set point, air temperature and product temperature | The deviation is interpreted using the wrong quantity | Identify the parameter, sensor and units and compare them with the relevant instructions |
| Treating absence of alarms as proof of complete data | Missing data or a loss of power or transmission may go unnoticed | Check the last timestamp, power and coverage; perform the prescribed local checks |
| Changing settings to clear an alarm without authority | Carriage conditions may depart from the agreed instructions | Investigate and report under the procedure; obtain documented authority before changing values |
| Losing logs | The history of readings, alarms and actions cannot be reconstructed | Retain logs with timestamps and authorisations under the contract and prescribed custody arrangements |
What the PSCO Checks
Operational Tips
- Treat telematics primarily as monitoring and alerting.
- Separate technical restoration of power from changing cargo settings.
- Retain logs, request and authorisation with the alarm history.
Preparation checklist
- Shipper instructions and contract available
- Monitoring frequency defined by carrier/SMS
- Alarms investigated under procedure
- No cargo setting changed without documented authority
- Old/new setting, time and authorisation recorded
FAQ
Related Topics
Certified substantive revision: 15 October 2026 · page fingerprint 666ae36cfbf5