LuminaPlatform

A modern operating system for the plant floor.

Overview

Monitoring, lab results, corrective action, and the documents that govern all of it have always lived in separate systems. That separation is why a problem found on a surface takes days to become a decision. Lumina is the layer where it stops being separate.

The plant, ranked by risk. It opens as one picture: what is online, where positivity is trending, which areas carry the most risk right now. Not a report someone assembles on Monday from four exports.

A continuous intelligence layer. Plant monitoring stops being a periodic check. See the exception, open the issue, close the loop, while production runs.

Every class of issue, one pipeline. A pathogen signature, a drifting temperature, wash water failing spec, a machine that drops offline. Each new sensor type inherits the alerting, the issues, and the records the moment it comes online.

Nothing turns into an email. A detection becomes an issue with the evidence already attached, routed by the SOP your team wrote.

It opens with an owner. Assignment is not a triage step someone gets to later. The issue is created against the person accountable for that zone, chosen from its classification and location, with a due date already on it, so nobody has to find it in a queue and work out whose problem it is.

01 · Live monitoring

Know which surface is drifting, without walking the floor.

The Lumina floor map: a plant laid out over satellite imagery with color-coded risk zones, sensors and equipment placed where they sit, an open device card reporting a burner fault in exception state, and an Insights panel showing 92% of devices operational, four exceptions, test positivity and health by Zone 1 to Zone 4 — Status the moment it changes: no walk, no clipboard.

Sites, buildings, floors, and zones. Your actual floor plan, with every sensor and machine placed on it. Food-safety zoning is built in: Zone 1 through Zone 4, each with its own risk rank.

Every site, from anywhere, on any device. It runs in any browser, desktop or mobile, with no app to download. A corporate quality lead can move between plants without standing on any of their floors. Insights roll up per site as well as per zone, which makes it obvious where risk is concentrating across the network, not just inside one building.

Site health at a glance. Per-area rollups of what is online, what is in exception, and where positivity is trending, all computed from live data, not estimated.

02 · Laboratory

Stop retyping lab PDFs into a spreadsheet.

The Lumina laboratory view: samples with test positivity and counts of Listeria monocytogenes and Salmonella positives, beside a surface-sample detail panel showing a PCR result sourced from Report Extraction, its zone location, and a test breakdown confirming the positive — A positive opens an issue before anyone has read the PDF.

Automate your lab process. Uploaded lab reports become structured samples and issue tickets are created automatically when positive tests are detected. Samples are mapped to the exact location where they were created. Extraction runs on a deterministic parser, not by asking a language model to read a regulated record.

Positive to issue, automatically. An out-of-spec result files an issue with the report attached and the sample linked. Unmatched samples get flagged for a human to resolve rather than silently dropped.

The lab still rules. Continuous sensing directs where your program looks next; confirmatory laboratory results remain the release criterion and remain the record.

03 · Issues

Every exception opens its own investigation.

A Lumina issue for a detected Listeria monocytogenes sample, auto-generated from a lab result and created by the system, showing its pathogen classification, Listeria tag, assignee, due date, location on the floor plan, and a draft CAPA with numbered immediate actions and a root-cause analysis — Sensors and lab imports file the issue, attach the evidence, and route it.

An issue opens itself. The issue shown was auto-generated from that lab result: source recorded as report extraction, created by the system, assigned before anyone opened the PDF. Device alerts, lab imports, email, mobile and the web portal are all tracked the same way, so you always know what raised it. A cooler drifting out of range or a sensor gone dark files exactly the same way a positive does.

Corrective action, in the issue. Immediate actions, root-cause analysis, and verification live on the issue itself rather than in a separate document, with the specs, programs and CFR references your team cites written into the steps.

Custody and change history. Every assignment, severity or priority change, state change, file, and sign-off is recorded against the issue. Pull it as a complete evidenced record, with no reconstruction after the fact.

04 · Grounded answers

Answers cited to your own records, with the exact paragraphs highlighted.

The Lumina document library beside an equipment assistant answering how to calibrate a checkweigher, with every step carrying a numbered citation back to the source manual — Ask a question, get an answer drawn only from your own documents.

Grounded in your records. Answers come only from documents you uploaded: CFRs, HACCP plans, SSOPs, equipment manuals, training material, detection logs. Never from a general model's training data.

Every claim cited. Each statement links to the exact document and page it was drawn from. One click opens the source at the passage.

Answers you can defend. Every response traces back to a source, so it can go straight into a record or in front of an inspector. Where your documents do not cover a question, the system shows you the gap and logs the reason (no sources found, conflicting sources, citation validation failed), which points you at the documentation worth writing next.

05 · The record

Compliance that documents itself.

The audit trail writes itself. Every detection, hold, and action is logged with its evidence and time-stamped as it happens, across issues, documents, assets, and lab samples. Timestamped, attributed, and ready for regulatory reporting, so when an inspector asks for the record it already exists.

Pull any issue as a complete record. Evidenced, time-ordered, and exportable: the same trail a human liability decision would be audited by.

Roles and access. Users, roles, and per-client classifications are administered in the platform, with access changes captured in the audit log.

Your library, indexed. SOPs, SSOPs, HACCP plans, cleaning protocols, FSIS directives, equipment manuals, specification sheets, centerlines, and training material, all ingested, chunked, and searchable by meaning and exact wording.

It sits over your systems, not in place of them. In: lab report PDFs parsed into structured results, device and sensor telemetry, and issues raised from email, mobile, or the web portal. Out: any issue or audit trail as a complete evidenced record. Lumina is the layer over monitoring, lab results, and corrective action, it is not a replacement for your LIMS of record or your document system of record, and it does not ask you to migrate them.

06 · The technology

What the sensor sees, and how it decides.

Everything above runs on a reading taken off a surface. A hyperspectral camera samples hundreds of narrow bands of reflected light, and at that resolution the pattern is specific enough to name what is on the surface rather than only flag that something is there.

The signal path from reflected light to a named organism. How a sample is identified by the company it keeps rather than by a single reference match. The research the detection is built on, the accuracy it has shown, and the validation still outstanding.

See the technology Or see it on your line