A useful refrigeration monitoring procurement worksheet begins with a decision, not a list of sensors. For each measurement, it should state what must be known, where and under which operating conditions it must be known, what the system should do with the result, and what evidence a supplier must provide. A compressor pressure transmitter, cold-room temperature probe and fixed refrigerant gas detector may all feed one controller, but they measure different media and have different failure consequences. Buying them as an undifferentiated “monitoring package” makes proposals hard to compare and gaps easy to miss.
This guide is for facility owners, refrigeration engineers and purchasing teams preparing a request for proposal or comparing quotations. It offers an adaptable worksheet and review method, not a legal tender form or a claim that every site needs every device. The equipment manufacturer's instructions, site risk assessment, applicable standards and jurisdiction determine safety-related requirements. Product pages below are examples of what a data sheet can substantiate, not endorsements or evidence that one supplier can serve every use case.
Define the procurement boundary before counting channels
First name the facility and the actual system boundary. Is the work a single cold room, a supermarket rack, an industrial ammonia plant, a heat-pump fleet or an HVAC appliance design? Is the purchase for permanent sensors only, a complete controller and alarm system, remote monitoring service, installation, commissioning or all of these? Who owns the existing control system and who will accept the final data? Without these answers, two quotations may describe different systems while appearing to have the same number of “points.”
List the refrigerant or refrigerants used by each equipment group. A site can have R-744 CO₂ process circuits, an R-290 appliance and a separate A2L HVAC unit; a generic gas detector line item cannot be assumed to cover all three. The Refrigerants.net directory is a useful way to organize the refrigerant identities and applications. Final sensor and safety requirements must come from the actual equipment and authoritative product documents. A fluid's safety class, operating pressure and monitoring objective can materially change the procurement route.
Record the project deliverables alongside the hardware: drawings, installation instructions, data sheets, gas-response evidence, controller point list, alarm logic, test plan, training, spares and service arrangements. A lower hardware price may come with a larger integration burden if the purchaser must build the interface, documentation and acceptance tests separately. Conversely, a complete monitoring system may include devices the site already owns. The worksheet should make those boundaries explicit so comparison is fair.
Separate three measurement layers
Refrigerant process measurements observe pressure, temperature, valve state and sometimes flow within the working circuit. They help control and diagnose the refrigeration process. A pressure transmitter must be appropriate for its location, pressure range, refrigerant/oil compatibility and electrical input. It is not an ambient gas detector.
Space and product measurements observe cold-room air, product or return-air conditions, doors and defrost operation. They help protect stored goods and assess the control sequence. A room-air probe can be correctly calibrated yet poorly positioned beside a door, fan discharge or defrost heater. State which quantity and location a decision actually depends on.
Ambient gas-safety measurements look for refrigerant in occupied or equipment spaces when required by the design. The target refrigerant, detector technology, location, alarm/fault behavior and mitigation chain matter. A room detector cannot infer the detailed health of a compressor from its low gas reading, and a process pressure trend does not prove the room air is safe. Our refrigeration plant-room monitoring log guide shows the event and response records that a permanent gas system should be able to support.
| Layer | Example channel | Decision supported | Evidence or boundary to specify |
|---|---|---|---|
| Process | Suction pressure and matched tube temperature | Control or diagnose a defined circuit condition | Refrigerant, tap location, reference, range and paired probe position |
| Process | Discharge pressure | Equipment protection or capacity control | Maximum conditions, transmitter range and controller action |
| Space | Cold-room air temperature | Room control and alarm | Sensor position, accuracy conditions, delay and defrost handling |
| Space | Door or defrost status | Explain a temperature event | Contact logic, timestamp and historian availability |
| Gas safety | Fixed refrigerant detector | Alarm and defined mitigation response | Exact gas/profile, inlet location, fault state and system evaluation |
| Monitoring platform | Gateway or controller | Trend, alert and record all relevant states | Point list, units, time base, access and data export |
The worksheet should include only channels justified by the site. Some simple equipment already provides adequate protected process signals; another site may need additional installed sensors for trend quality. Avoid paying twice for the same measurement while overlooking a missing response signal, such as fan-run feedback after a gas alarm.
The core worksheet: one decision per row
The table below is a copyable starting structure for a buyer. Put one specific measurement or system response in each row. “Supplier response” is a field for a quotation; it is intentionally blank here. A response such as “compliant” should point to the exact page and product revision that demonstrates it.
| Field | What the buyer should define | Supplier response or evidence to request |
|---|---|---|
| Function and consequence | Control, trend, product protection, gas alarm or safety mitigation | Functional description and complete system boundary |
| Medium and target | Refrigerant, air, water/glycol, product or specific ambient gas | Approved media and gas/profile list |
| Measurement point | Tap, pipe, room zone, cabinet, inlet or product location | Installation drawing and location conditions |
| Operating envelope | Normal and extreme pressure, temperature, humidity, vibration and cleaning exposure | Model-specific environmental and pressure limits |
| Range, reference and units | Gauge/absolute/differential, ppm/%LFL, °C/°F, etc. | Data sheet, accuracy conditions and resolution |
| Output and interface | Analog, relay, digital protocol, supply and controller ownership | Wiring, protocol, message map and fault behavior |
| Required action | Display, trend, alarm, stop, fan or notification | Logic diagram and response acceptance test |
| Reliability and service | Failure detection, calibration or verification, replacement, spare parts | Maintenance instructions and service availability |
| Evidence scope | Exact model, firmware, gas, test conditions, standard edition | Test report or certificate with matching scope |
| Handover | Drawings, configuration backup, training and data access | Deliverable list, ownership and export format |
This format stops an attractive headline specification from hiding a different measurement basis. An accuracy value may be stated at one temperature and part of the range; a temperature probe in a freezing, wet room must be evaluated at its installed conditions. A gas module may list a target gas yet omit the host controller's reaction to sensor fault. A digital interface may be supported by the sensor but not by the existing building-management system without a gateway.
What to write in the “required action” column
The action should say what the system must do when a valid state occurs, not merely that it should “send an alarm.” For a cold-room temperature excursion, the site may need a local notification, remote alert, acknowledgement, escalation and trend record. For a gas detector connected to safety-related equipment, the applicable design may require automatic mitigation. For a pressure signal, the action may be a controller adjustment or protective trip. These are different levels of responsibility and must be evaluated separately.
Where an actuator matters, ask how its operation is confirmed. A controller's fan-start command and a fan-run contact are not equivalent evidence. If there is no feedback, record that fact in the worksheet. Procurement is the right time to decide whether that limitation is acceptable; discovering it after an incident is too late. A complete point list should distinguish command, feedback, measured value, alarm, fault and communication status.
Compare device specifications under the conditions of use
Pressure transmitters. Define pressure reference, normal and maximum pressure, transient tolerance, refrigerant and oil exposure, connection, supply, output and accuracy over the relevant temperature range. The Danfoss AKS 3000 data sheet illustrates how a refrigeration-specific transmitter documents its pressure reference, wetted materials and output. A range or approval from that model cannot be assigned to another model by analogy. Our HVAC pressure-diagnostics guide explains why the position and reference of an installed pressure channel matter once data are used for troubleshooting.
Temperature probes. State whether the decision concerns air, liquid, pipe surface or product temperature. Require the range, accuracy at relevant temperatures, response time, mounting and cleaning/condensation conditions. Specify who supplies the probe and who is responsible for its calibration or replacement. A contractor cannot price a meaningful channel from the phrase “one temperature sensor per room” if the required locations and data uses are undefined.
Gas detectors. Identify the exact refrigerant or gas profile, expected concentration unit, intended alarm function, inlet/placement constraints and environmental exposure. Ask how the device distinguishes normal, alarm, fault and lost communication. A device that can detect several gases may report different performance for each. The Danfoss gas-detection product information illustrates distinct models, integrations and service accessories. Its catalog scope is not a universal placement rule or an assurance that one product covers all site refrigerants. For an embedded module, our HVAC module-integration guide details the host-controller questions.
Controller and communications. Specify point capacity, sampling interval, retained event history, unit handling, time synchronization, alarm transmission, loss-of-network behavior, access roles, configuration backup and export. The supplier should explain whether a point is a raw sensor value, an engineering-unit value calculated by the controller, or a simple state. It should also explain what happens when a device goes offline. “Cloud ready” is not an answer to a question about local alarm behavior during an internet outage.
Demand evidence that matches the offered configuration
The most important line in a comparison sheet may be “document ID, revision and exact model covered.” A certificate or test report for a sensor element does not necessarily cover the packaged detector, its controller or the installed refrigeration appliance. A brochure statement about one refrigerant may not cover another profile. A product drawing for one cabinet orientation may not justify a different orientation. Ask suppliers to mark the exact evidence for each proposed line item and configuration.
UL Solutions' discussion of integral HVAC refrigerant detection explains that, where required, the RDS may be evaluated as part of the equipment and installed to the equipment manufacturer's instructions. This is a reminder to define the system being bought and the scope of the claimed evaluation. The applicable product standard edition and local adoption require project-specific verification; do not buy on the strength of a generic “UL compliant” label without the actual listing and instructions.
Ask for evidence in four groups:
- Product identity: part number, option code, sensor module, firmware, refrigerant profile and serial-number traceability.
- Performance: target-gas or media response, range, error conditions, timing, interference, environmental exposure and applicable test conditions.
- Integration: wiring and protocol, input scaling, alarm/fault states, location and complete equipment response.
- Lifecycle: installation, commissioning, maintenance, replacement, spare parts, training and end-of-life information.
A missing document is not automatically a failed product, but the buyer should mark it unresolved, assign an owner and decide whether that gap prevents comparison or acceptance. Avoid filling missing values from another vendor's data sheet. If a proposal uses a substitute part, recheck the fields affected by the substitution instead of assuming functional equivalence from a similar housing.
Evaluate commissioning and lifetime cost
Hardware is only one part of the purchase. A sensor may need a protective accessory, a calibration kit, periodic field verification or a replacement head. A controller may require a gateway, license, custom mapping or service contract. A detector may be inexpensive to buy but difficult to reach after installation. Ask bidders to describe a realistic maintenance workflow and identify who supplies consumables, qualified service and replacement modules over the intended life of the system.
For commissioning, require a test plan that follows the measurement path. A process transducer should be checked for correct point, scaling and controller value. A room temperature probe should be checked in its intended location and control state. A gas detector should be checked through its applicable sensor, host and notification/mitigation chain by qualified personnel using approved methods. A simulated controller input and a physical gas challenge test different layers. The record should say which was done. Danfoss's application guide distinguishes function checks from calibration and emphasizes product-dependent maintenance.
The handover package should include as-built point locations, installed model and serial numbers, current firmware and gas profiles, configuration backup, test records, spare-part list and the contact responsible for future changes. A controller trend has limited value if nobody knows which replaced sensor supplied a past reading. Define a retention and export format that the facility can use independent of one contractor's login. The purchaser should be able to reconstruct the state of the system at the time of an alarm.
Compare offers by gaps as well as features
Use the same worksheet rows for every bidder and permit three clear response states: meets with cited evidence, proposed alternative with stated differences, or unresolved. Do not treat a blank as a pass. If a proposed alternative changes the gas profile, pressure reference, interface or maintenance method, ask for a revised diagram and acceptance test. If suppliers disagree about whether a particular detector is required, resolve that project requirement with the responsible engineer and applicable authority before scoring products against different assumptions.
Separate mandatory project requirements from desirable features. A colorful dashboard, longer trend retention or easier reporting can be useful, but it should not compensate for an unproven sensor fault response where the design requires one. Similarly, a product with more channels is not necessarily better if the channels cannot be located or maintained correctly. A concise evidence-backed comparison is more useful than a weighted score that hides a critical missing document.
A qualitative worked example
Consider a hypothetical cold room with a compressor package and a fixed gas detector required by its approved design. The buyer first lists a suction pressure channel for process diagnosis, with refrigerant identity, tap location, pressure reference and controller scaling. The second row is cold-room air temperature, with an agreed sensor location and defrost interpretation. The third row is ambient refrigerant detection, with target gas, detector location, alarm and fault paths, and evidence that the complete response is tested. The fourth row is remote notification, including who receives an alarm and how loss of network is handled.
No vendor number, test result or legal threshold has been invented in this example. Its purpose is to show that four rows can have four different acceptance methods. A quotation that provides a pressure transmitter and a cloud dashboard but omits gas-detector fault handling is not equivalent to one that addresses the complete gas response. A quotation that includes a fixed gas detector but no pressure data may meet a safety requirement while leaving a process diagnostic goal unanswered. The buyer needs both the function and its evidence in each row.
The same method scales to a larger rack. Group points by equipment and measurement purpose, then add shared controller and network requirements. Keep an identifier for every channel so future logs can be tied to the device installed at a particular location. This is especially valuable after refrigerant conversion, sensor replacement or a control-software update.
Frequently asked questions
Can one refrigerant detector cover every gas at a mixed site?
Do not assume so. Request model-specific performance for each target gas or approved profile, including units, response and maintenance. R-744 CO₂ and R-717 ammonia require different measurement routes from many halocarbon or hydrocarbon applications.
Should a buyer specify a sensor brand in the worksheet?
Specify the function, interface, environmental boundary and evidence first unless the installed equipment or approval requires a particular part. If an exact approved part is required, state that dependency and the revision. This prevents both unnecessary sole sourcing and unsafe substitution.
What is the difference between a module and a complete monitoring system?
A module may deliver a conditioned gas or pressure signal. A complete system includes placement, power, controller interpretation, alarms, fault handling, action, recordkeeping and maintenance. Determine which layers the supplier is actually offering and which remain the integrator's responsibility.
Can the same acceptance test cover pressure, temperature and gas detection?
No. The media, measurement methods and consequences differ. A common commissioning plan can organize the work, but each channel needs a test appropriate to its function, and safety-related gas response needs the approved complete-system method.
How should missing supplier evidence be handled?
Mark the requirement unresolved, request the exact document or test, and record the responsible reviewer. Do not substitute a similar model's data or turn an uncited “yes” into a verified pass. Critical gaps should be closed before acceptance.
A good procurement worksheet makes the required measurement, decision and proof visible on the same line. That structure lets a buyer compare suppliers fairly, identify integration responsibility early and hand over a monitoring system that can still be understood and maintained years later.
Leave a Reply