Reference · built on requestOperator by FibricProduction & maintenance

Cold Room Watch

Reads walk-in and case temperatures, door state, and compressor runtime. Proposes a service call or product move before the limit.

Request accessPricing ↗

About

A walk-in fails slowly: the compressor runs longer each day to hold the same temperature. Cold Room Watch reads air temperature in each walk-in and display case from LoRaWAN sensors, door contact state from door sensors, and compressor run state and runtime from the refrigeration controller's registers over Modbus TCP. It also reads the sensor network's own status, so a silent sensor is not mistaken for a steady room.

From the rate of rise and the limit you set per room, it projects when the limit will be crossed. When runtime climbs while the room holds, or the temperature climbs with the door shut, it proposes a service call in your CMMS with the trace. When the projection is shorter than a technician's response, it proposes moving product to a named backup unit.

This is a reference listing. It documents what Fibric would read from Cold Room Watch and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Air temperature per walk-in and case from LoRaWAN sensors, through your network connector, Milesight DEVICE_DATA events, or Monnit readings
  • Door contact state, open or closed, from LoRaWAN door sensors or Disruptive Technologies contact events
  • Compressor run state and runtime from the refrigeration controller's holding registers, read on a schedule over Modbus TCP
  • Defrost state where the controller exposes it as a register, so a rise during defrost is not read as a fault
  • Sensor and gateway status: Disruptive Technologies networkStatus heartbeats and Monnit gateway status, so a silent sensor is flagged
  • Open work orders on the same unit in Fiix, MaintainX, UpKeep, or Limble CMMS

Proposed actions

  • Target capability: propose a service work order in your CMMS when compressor runtime rises while the room holds temperature, with the runtime trend
  • Target capability: propose a service call when the temperature climbs with the door shut and no defrost under way
  • Target capability: propose a product move to a named backup unit when the projected time to the limit is shorter than your service response
  • Target capability: propose a door notice to the shift's Slack or Microsoft Teams channel when a door has stayed open past the minutes you set
  • Target capability: propose a sensor check when a sensor goes silent or reads flat while the compressor cycles

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Runtime tells first

    A walk-in holds temperature, but the compressor's runtime register climbs week over week. Cold Room Watch proposes a MaintainX work order on the unit with the runtime trend before the room warms.

    With LoRaWAN Network, Modbus TCP, MaintainX

  • Move the product

    Temperature rises with the door shut and no defrost. The projection reaches the limit before a technician could arrive; the operator proposes moving product to the named backup case and a Fiix service call.

    With Milesight Development Platform, Fiix

  • Door, not compressor

    A Disruptive Technologies contact sensor shows the door open through a delivery. The proposal is a door notice to the shift channel, not a service call, and an UpKeep work order only if the rise continues after it closes.

    With Disruptive Technologies, UpKeep

  • Silent sensor

    A Monnit sensor stops reporting while its case keeps cycling. Rather than read the last value as steady, the operator proposes a sensor check as a Limble task and a Slack note.

    With Monnit iMonnit, Limble CMMS, Slack

Requirements

  • A LoRaWAN, Milesight, Disruptive Technologies, or Monnit connector, with a temperature sensor per room or case and a door sensor per door
  • A Modbus TCP connector with the refrigeration controller's run state and runtime registers on its allow-list
  • A CMMS connector with the units as assets: Fiix, MaintainX, UpKeep, or Limble CMMS
  • A temperature limit per room or case, and a named backup unit for product moves
Authentication
Cold Room Watch carries no credentials. Readings come through your LoRaWAN, Milesight, Disruptive Technologies, or Monnit connector and the Modbus TCP connector; work orders go through the CMMS connector's scopes.

Limits

  • The limit per room is yours, taken from your food safety plan or local code. The operator does not set it.
  • Projection uses the recent rate of rise. An open door makes it steep; the operator says so rather than calling the compressor faulty.
  • It reads registers. It never writes to a refrigeration controller, changes a setpoint, or alters a defrost schedule.
  • LoRaWAN sensors report on their own interval. A fast rise is seen one interval late.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Cold Room Watch ↗

Questions and answers

What does a person approve?
Each service call, product move, door notice, and sensor check. The proposal shows the room, the temperature trace, the door events, the compressor runtime, the projected time to the limit, and any open work order. Approve, change the unit, or dismiss. A dismissed projection returns when the rate of rise worsens.
What record is left?
A trace per room: temperature, door state, compressor runtime, and defrost state over time. A receipt per proposal: the limit applied, the projection, who approved, what was written to the CMMS or posted, and how to close it.
What will it never touch on its own?
It never files a work order, moves product, or posts a notice without approval. It never writes a register, changes a setpoint, or silences an alarm on the controller.
Ask about Cold Room Watch

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy