> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/pricing/archive-product-simulant.md).
# \[Archive] Product Simulant
Product Simulant Probe Add-On – Accurate Temperature Monitoring Without Compromising Product Integrity
> $25 per unit (exclusive of sensor, in USD)
The **Product Simulant Probe Add-On** is an advanced accessory for MFC Safe’s temperature monitoring system. When used in conjunction with the Dragino LHT65S LoRaWAN temperature and humidity sensor, this add-on delivers real-time, **simulated product core temperature readings**—ideal for refrigerated displays, cold rooms, and HACCP-critical environments.
***
{% tabs %}
{% tab title="Chillers" %}
{% endtab %}
{% tab title="Freezers" %}
{% endtab %}
{% tab title="Service Fridges" %}
{% endtab %}
{% tab title="Under Bench Units" %}
{% endtab %}
{% tab title="Dashboard " %}
{% endtab %}
{% endtabs %}
#### Why Ambient Alone Isn’t Enough
Ambient sensors provide valuable data on the surrounding environment, but **they do not represent the thermal behavior of actual food products**. Food items, especially those with high water activity or density (e.g. meats, dairy, prepared meals), do not change temperature as quickly as air. Monitoring only ambient conditions risks underestimating thermal exposure, potentially allowing microbial growth before a breach is noticed.
***
#### Avoid Invasive Core Temperature Checks
Traditionally, operators must physically probe food items to measure core temperature. This process is:
* **Invasive**: Can damage or devalue the product
* **Potentially unsafe**: Risk of introducing contamination
* **Intermittent**: Offers no continuous temperature record
The product simulant eliminates the need for manual checks while improving both hygiene and data integrity.
***
#### How the Simulant Works
The simulant consists of a calibrated **external temperature probe**, fully submerged in a **thermal medium** that mimics food's thermal inertia. Available media include:
* **Glycerol**: High thermal mass, ideal for meat and dairy simulation
* **Water**: General-purpose food simulating fluid
* **Food-grade oils**: Suitable for high-fat content food simulation
* **Glass beads**: Non-fluid alternative for dry or packaged foods
The probe transmits data through the LHT65S sensor at configurable intervals, providing a true reflection of what the *product temperature* would be under current ambient conditions.
***
#### HACCP & Microbiological Safety Rationale
The **Codex Alimentarius HACCP framework** mandates that food be kept at safe temperatures to prevent microbial proliferation. Many critical pathogens, such as *Listeria monocytogenes* and *Salmonella spp.*, begin multiplying rapidly above 5 °C.
Product simulants:
* Enable **non-invasive, continuous verification** of temperature control
* Are **essential for passive display cabinets, cold rooms, and self-service fridges**
* Support **evidence-based corrective action** and temperature mapping during audits
***
#### Ideal Use Cases
* Supermarket refrigerated displays
* Commercial cold rooms
* Retail deli counters
* Food transportation and logistics
* Temperature mapping studies
***
Benefits
* Accurate product-equivalent temperature data
* Continuous monitoring (not spot-checking)
* No contamination risk or product damage
* Supports HACCP validation and compliance
* Easy to retrofit into existing MFC Didge dashboards
***
**Add the Product Simulant Probe Add-On** to your MFC temperature monitoring system and elevate your food safety visibility to real product conditions—without ever touching the product.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.didge.io/home/pricing/archive-product-simulant.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=12e7d222-4d70-4511-8490-adc54c715ca0)
