Fleet and refrigeration units2 / 7

Apply EU Regulation 2024/573 only to covered gases and equipment. Do not automatically class a passive plate container as F-gas equipment.

Record energy use, refrigerant inventory and calculation boundaries separately; compare reductions with measurements.

Track vehicle availability, service downtime and actual route duration, verifying product transport plans against current rules.

The three letters of an ATP mark give, in order, the equipment type, the insulation level and the temperature class it can hold. What each letter means, the K-coefficient limits and the difference between FRC and FNA.

Use actual trips to assess load volume, route duration, stops and power access. Validate each option with measurements against product instructions.

Measure traction and refrigeration separately; document charging electricity and the factor boundary.

Keep traction and refrigeration energy separate. Compare them through tank stock, operating mode, electricity and passive preparation records.

Measure rounds, load, usable space and delivery windows to test whether another vehicle is needed.

For the same route capacity, compare purchase, operating, maintenance, finance and idle costs.

Cooling during charging depends on the vehicle and unit. Track interruptions, power source and product temperature on one timeline.

Define the failure report, load details, logger and alternate delivery decision with named owners in advance.

Track actual stop time, load and plate conditions together; validate any delay allowance with product records.

Do not decide to switch a unit off by guesswork. Check vehicle and unit guidance alongside real load, route duration and product-temperature records.

Assess more than body and unit price: weigh payload, axle limits, usable dimensions, wiring, testing, downtime and the fallback plan together.

Use utilisation, ready containers, route delays, and dated quotes to find which investment addresses the bottleneck.

Link route, stops, load and refrigeration runtime, then compare active and passive options at similar workloads.