Reference · built on requestOperator by FibricInventory & supply

Lot Quarantine

Links a temperature excursion in cold storage to the lots stored there and proposes a quarantine hold until quality has reviewed them.

Request accessPricing ↗

About

A cold-room sensor knows the temperature went out of range. It does not know which lots were inside. Lot Quarantine reads temperature samples from your sensors, the bin or zone each sensor covers, and the lots sitting in those bins according to your ERP or WMS.

When readings cross the limit you set for longer than your grace period, the lots in the affected bins are listed with the excursion's start, end, and peak. A hold is proposed for each lot that keeps it out of picking until quality reviews it. A quality manager approves the hold and, after review, its release.

This is a reference listing. It documents what Fibric would read from Lot Quarantine 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

  • Temperature samples per sensor from SensorPush POST /samples, Monnit sensorMessages with dataValue and state, or Disruptive Technologies temperature events
  • Which bin, room, or zone each sensor covers, from sensor names or tags and a map your team maintains
  • Lots by bin and location: NetSuite inventory balances by bin, lot, and inventory status, or Business Central lot numbers with bin codes
  • Odoo lots with their current location, and any quality alert already open on them
  • Limits per storage class: the temperature range and the minutes out of range that count as an excursion
  • Gateway last_seen and sensor battery state, so a silent sensor is reported rather than read as in range

Proposed actions

  • Target capability: propose a NetSuite Inventory Status Change moving the lot from Good to a status unavailable for allocation, such as Inspection
  • Target capability: propose marking the lot Blocked on its Business Central Lot No. Information card, with the excursion in the Description
  • Target capability: propose an Odoo quality alert on the lot, or an internal transfer of the lot to a location set aside for quarantine
  • Target capability: propose releasing a held lot back to Good once the quality manager records the outcome

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

What you can build

  • Hold what was in the walk-in during an outage

    SensorPush samples show the cooler above range for longer than the grace period. Lots in the mapped bins are read from NetSuite, and an Inventory Status Change to Inspection is proposed per lot.

    With SensorPush, NetSuite

  • Block a lot in Business Central until quality signs off

    A Monnit sensor message arrives in Aware State above the threshold. The lots in that zone are proposed as Blocked on their Lot No. Information cards, with the excursion times in the Description.

    With Monnit iMonnit, Microsoft Dynamics 365 Business Central

  • Route an excursion into Odoo quality

    A Disruptive Technologies temperature event exceeds the limit for a cold room. A quality alert is proposed for each Odoo lot in that location, and release is proposed when the review passes.

    With Disruptive Technologies, Odoo

Requirements

  • Temperature sensors reporting to a cloud with an API: SensorPush, Monnit, or Disruptive Technologies
  • Lot tracking with a bin or location per lot in NetSuite, Business Central, or Odoo
  • A map from each sensor to the bins or zone it covers, kept by your team
  • A quality manager named to approve holds and releases
Authentication
A sensor cloud credential (a SensorPush account, a Monnit API key, or a Disruptive Technologies service account) and ERP credentials with inventory status or item tracking permissions.

Limits

  • SensorPush allows one request per minute. Excursion detection there lags by at least that interval.
  • Disruptive Technologies temperature sensors send one sample per heartbeat by default. A short excursion between heartbeats can be missed.
  • The sensor map is yours. A lot in an unmapped bin is not held; it is listed as unmapped.
  • Business Central's Blocked flag excludes the whole lot from transactions. A partial hold there needs a reclassification first.

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 Lot Quarantine ↗

Questions and answers

How does it link an excursion to lots?
Each sensor is mapped to bins or a zone by your team. When readings from that sensor stay out of range past the grace period, lots recorded in those bins at that time are listed. The card shows the sensor, the readings, and each lot's location.
What does the quality manager approve?
A hold per lot: lot number, units, bin, the excursion's start, end, and peak, and the status or flag to be set. Later, a release per lot with the review outcome typed in. Either can be declined.
Does it ever hold or release a lot on its own?
No. Every status change, Blocked flag, or quality alert is a proposal until approved. The record keeps the sensor readings, the lots, the approver, and the time, and a release proposal is the way back.
Ask about Lot Quarantine

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