> 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/fsms-starter-packages/6.-cook-chill-set.md). # 6. Cook Chill Set Precision Control for the CookChill Process *** The CookChill Set is a specialised solution designed for professional kitchens that perform CookChill operations as part of their food production workflow
Built on the MFC Didge Platform and integrated with Ridgy Vision AI, this set introduces a purpose-built CookChill probe and connected gateway to deliver continuous, automated temperature monitoring throughout both the cooking and chilling cycles — bringing precision, efficiency, and compliance into one streamlined process.
*** #### What’s Included * One CookChill Probe — durable, high-heat sensor designed for full cooking and chilling cycles * One Gateway — ensures seamless connectivity and live data transmission to the Didge Platform * Access to the CookChill Module within the Didge system, including: * Customisable temperature-time templates * Automatic monitoring and data logging * Alerts and corrective actions for non-compliant cooling curves
*** #### Hardware Details The CookChill Probe is engineered for the most demanding kitchen environments. It is built to withstand both high-temperature cooking and rapid cooling processes while maintaining precise accuracy throughout. Device Highlights: * Heat-resistant probe capable of remaining inserted in product during the entire cook and chill process * Fully submersible and designed for use in commercial-grade cooking and chilling equipment * Continuous data capture — transmits live readings to the Didge Platform via the included gateway * “Set-and-forget” functionality — no manual intervention or repeated temperature checks required This unique design allows operators to monitor temperature trends remotely, with data automatically logged and stored for audit-ready reporting. *** #### Software & Data Integration The CookChill Module within the Didge Platform provides an intelligent framework to manage and verify your CookChill operations: * Supports standard and custom CookChill templates, including: * Heat to cook to 75°C * Cool from 60°C to 21°C within 2 hours * Cool from 21°C to below 5°C within 4 hours * Automatically tracks each stage of the process * Generates real-time alerts if parameters fall outside compliance thresholds * Integrates seamlessly with Ridgy Vision AI and other Didge modules for a complete digital FSMS view This enables full traceability from cooking to storage, ensuring every batch meets food safety standards such as Food Standards Australia New Zealand (FSANZ) or equivalent regional requirements. *** #### Who It’s For The CookChill Set is ideal for: * Large hotel and institutional kitchens performing daily CookChill operations * Central production kitchens and commissaries * Food manufacturers producing chilled ready-meal products * High-volume caterers or food service providers managing batch production Whether you’re operating a large-scale CookChill system or simply need tighter control over your cooling cycles, this set delivers the automation and precision you need. *** #### Benefits at a Glance * Fully automated CookChill monitoring — from start to finish * “Set-and-forget” functionality — significantly reduces manual labour and temperature logging * Increased accuracy and consistency — eliminates human error in temperature recording * Continuous compliance — meets FSANZ and international cooling requirements * Live visibility — monitor progress remotely via the Didge dashboard * Digital records — every CookChill cycle stored securely and ready for audit * Enhanced food safety assurance — reduces risk of pathogen growth during critical cooling phases * Seamless integration — works alongside all other Didge modules and Ridgy AI processes *** #### Purpose The CookChill Set was developed to solve one of the most complex challenges in food safety: accurate, verifiable monitoring of the CookChill process. By combining high-heat probe technology, IoT connectivity, and automated data management, this solution: * Streamlines compliance verification * Reduces manpower requirements * Improves consistency and traceability * Delivers defensible, data-driven food safety assurance This technology empowers kitchens to focus on production quality while the system handles compliance automatically in the background. *** #### Getting Started 1. Receive your configured CookChill probe and gateway from MFC Safe. 2. Install and connect your devices to the Didge Platform. 3. Select or customise your CookChill template within the Didge module. 4. Insert the probe into the product, begin the process, and let the system handle the rest. 5. Monitor progress and review temperature curves directly through your digital dashboard. *** #### Set. Monitor. Chill. Simplify. The CookChill Set brings unmatched efficiency, control, and compliance to one of the most demanding areas of food safety. With continuous monitoring, automated alerts, and complete digital traceability, your team gains the tools to manage CookChill operations with confidence and precision — every time. Experience the future of food safety automation with MFC Safe, powered by Didge and Ridgy Vision AI. *** --- # 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/fsms-starter-packages/6.-cook-chill-set.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.