Reference · built on requestOperator by FibricProduction & maintenance

Food Safety Log

Fills HACCP monitoring records from sensor readings and proposes the corrective action record when a check is missed or out of range.

Request accessPricing ↗

About

Food Safety Log is an operator for the monitoring and corrective action records in a HACCP plan. The FDA's HACCP guidelines say monitoring should be continuous where physical measurements allow it, and that monitoring records are dated and signed or initialed by the person doing the monitoring. This operator reads the temperature sensors mapped to each critical control point, compares each reading with the critical limit in your plan, and proposes the record.

When a reading breaks a limit, it proposes a corrective action record for the person to complete. When no reading arrives in a check window, it proposes a missed-check record. It writes nothing until you approve, and it never decides what happens to the product.

This is a reference listing. It documents what Fibric would read from Food Safety Log 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 readings per critical control point: Monnit sensor messages with sensorID, messageDate, and dataValue, SensorPush samples, or Disruptive Technologies temperature events
  • The HACCP plan's critical limits and check schedule per control point, kept in a Google Sheets range or a Microsoft Excel table
  • Sensor health that would void a check: Monnit batteryLevel and signalStrength, SensorPush gateway last_seen, Disruptive Technologies batteryStatus and networkStatus
  • Threshold crossings the sensor platform raises itself, such as a Monnit sensor entering its Aware State
  • Corrective action issues already open in Jira, Asana, or monday.com for the same control point

Proposed actions

  • Target capability: propose each scheduled check's monitoring record, with reading, time, sensor, and pass or fail against the limit, as a log sheet row
  • Target capability: propose a corrective action record in Jira, Asana, or monday.com when a reading breaks a critical limit; a person fills cause and disposition
  • Target capability: propose a missed-check record when no reading arrives inside the check window, naming the sensor and its last message
  • Target capability: propose a threshold or heartbeat change on a Monnit sensor through SensorSetThreshold or SensorSetHeartbeat, so it alerts at the critical limit

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

What you can build

  • Log cold-room checks from Monnit sensors

    Each control point maps to a Monnit sensor. At every scheduled check the latest sensor message becomes a proposed row in the Google Sheets log, and a reading past the critical limit opens a proposed Jira issue.

    With Monnit iMonnit, Google Sheets, Jira

  • Fill a walk-in cooler log from SensorPush

    SensorPush samples arrive about once a minute. The operator proposes the check row in a Microsoft Excel table on the schedule you set, and a monday.com item when the limit is crossed or the gateway goes quiet.

    With SensorPush, Microsoft Excel, monday.com

  • Catch a check that never happened

    When no Disruptive Technologies temperature event lands inside a check window, the operator proposes a missed-check record and an Asana task for the person on shift, with the sensor's last event time.

    With Disruptive Technologies, Asana

Requirements

  • A sensor connector with a reading per control point: Monnit iMonnit, SensorPush, Disruptive Technologies, or Milesight Development Platform
  • A sheet or table that holds the HACCP plan: control point, critical limit, check frequency, and the sensor mapped to it
  • A work-management connector for corrective actions: Jira, Asana, or monday.com
  • A named person who signs each proposed record, since the FDA guidelines expect monitoring records to be dated and signed or initialed
Authentication
Sensor readings, sheet rows, and tickets flow through the connectors you bind and the access each one holds; the operator has no credentials of its own.

Limits

  • It records what the sensor reports. A probe away from the product, or a stale reading, gives a wrong check; health fields are the guard
  • SensorPush answers at most once a minute and Monnit heartbeats cannot go below ten minutes, so a check window shorter than that cannot be filled
  • It never decides product disposition. A corrective action record is proposed with the disposition left blank for the person to fill in
  • Verification and validation of the HACCP plan stay with your food safety team; the operator fills monitoring and corrective action records only

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 Food Safety Log ↗

Questions and answers

What does the HACCP monitor approve?
Every record. A monitoring record shows the reading, the time, the sensor, and the critical limit it was judged against; you approve it as written or correct it. A corrective action record shows the deviation and asks you to determine the cause and decide the disposition. Nothing is written to the log or the tracker until then.
What record does it leave?
The log row or ticket as your system created it, plus a receipt: the sensor message the reading came from, who approved it and when, and how to reverse the write. Dismissed proposals are kept, so an auditor can see which readings were judged and why.
Does it change sensor settings on its own?
No. A threshold or heartbeat change on a Monnit sensor is proposed with the old and new values, applied once after approval, and reversible from the receipt. It never silences an alert, deletes a reading, or writes to the HACCP plan sheet.
Ask about Food Safety Log

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