LuminaPlatform
Everything the plant knows, in one record.
Overview
Samples, lab results, issues, tasks, forms, readings and the documents that govern them have always lived apart. Lumina is the layer where they stop being separate: one record, written as the work happens.
- 1 Open issues, by owner
- 2 Exceptions, named
- 3 Areas ranked by risk
The plant, ranked by risk. What is online, where positivity is trending, which areas carry the most risk right now.
Nothing turns into an unread email. A finding becomes an issue with the evidence attached, an owner and a due date.
Screens on this page are the live product on seeded demo data. Counts and rates are illustrative, not performance figures.
One event, end to end
A positive lands at 09:12.
Here is everything that happens to it.
- Step 01
The report lands
The lab PDF is parsed into a structured result and matched to the sample. A person reviews it before it counts.
- Step 02
It appears on the map
Pinned to the drain it came from, beside that site's history: the same drain, three times in four months.
- Step 03
The issue files itself
Typed as a pathogen finding, with an owner, a severity and a due date, before anyone has forwarded the email.
- Step 04
The response is recorded
Immediate action, root cause and verification swabs, each with a name and a time. Ask answers from your own SSOP, with the citation.
- Step 05
Closed, with the clock
Observed to corrected, in hours, in the record. Exportable as one PDF the day an inspector asks.
Every step above is live on the platform today. When Detect is installed, a sensor flag will file an issue the same way: to a person, never to a hold.
Facility map
Know which surface is drifting, without walking the floor.
- 1 Floor plan and flow
- 2 Four systems need attention
- 3 Test positivity rate
Your actual floor plan. Drawn or uploaded in Admin, with material flow drawn over it, and every sensor, machine, sample site and issue where it sits.
On the web and on the floor. The same map runs in the mobile app, below. Insights roll up device status and test positivity for the plant.
What the record holds. The positive arrives on the map with that site's history beside it, so QA scopes the hold from evidence, not memory. Unit: pounds held, days to disposition.
Product on hold · Working capital
Laboratory
Years of swab results, and not one says where the problem lives.
- 1 Positive, pinned to its site
- 2 The issue it opened
- 3 Parsed from the PDF
Stop retyping PDFs. ATP, pathogen PCR, chemistry panels and genomic reports parsed into structured results, matched to the sample, pinned to where it was taken. A person reviews before it counts.
Positives on the map, over time. The same drain going positive three times in four months has always been in the data. Now it is visible.
The lab still rules. Lab results stay the record, and wherever your plan holds product for a test, the lab result decides release, not Lumina.
What the record holds. The drain that went positive three times shows up as one pattern, so the deep clean and the investigational swabs go there first. Unit: re-cleans per week, repeat positives per site.
Sanitation spend and re-cleans · Operating cost
Issues
They know the event happened, not how long they were exposed.
- 1 Opened by the system
- 2 Task Owner and Due Date
- 3 Actions, timestamped
- 4 Where it happened
An issue opens itself. Filed from the lab result, assigned before anyone opened the PDF. A failed check on a form raises an issue the same way.
Corrective action lives in the issue. Owner, due date, notes, linked tasks and files, and Ask answers from your own SOPs with the citation attached. Observation and correction both timestamped.
Where it happened, on the floor plan. The issue carries the spot it came from, so whoever responds walks to that drain instead of to the room it sits in.
What the record holds. Every hold, re-clean and stop carries who saw it, when, and who closed it: one clock for production, sanitation and QA. Unit: hours from observed to corrected.
Product on hold · Working capital
Tasks, forms and logs
The clipboard on Line 3 becomes a record you can search.
- 1 Out of range, flagged
Your paper checks, as forms. Line checks, floor checks, thermometer calibration logs: filled where the work happens, against a scheduled task or on their own, with a review step and a signature.
Readings with a range. Monitoring points carry the range each should stay in. A reading outside it is flagged, asks for the corrective action, and can raise an issue in one step.
Shifts and crews the plant defines. Recurring work assigned to people, shifts or roles, with checklists and a verifier's sign-off, and every run tracked.
Every filed form is findable. Thirty, sixty or ninety days of records, when an auditor asks for them on the spot.
What the record holds. Every late start logged from the floor with its cause, so the 07:00 meeting reads one record instead of three recollections. Unit: late-start minutes by cause, per line.
Line downtime · Variance
Live on the platform, on the web and in the mobile app.
Floor execution
The work happens where there is no signal. So does the record.
- 1 Ranked for you, not the site
- 2 Offline: the write waits
A person-ranked Today. Web answers how the plant is doing. The phone answers what you should do next: the issues, tasks and forms that need this person now.
Built for the rooms with no signal. Cached sign-in, lists served offline, forms and readings included, writes queued and replayed when the signal returns, with the time the work was actually done.
Ask, on the floor. The same cited answers from your own documents, on the phone. Photos never touch the camera roll.
What the record holds. The 04:30 call becomes an issue from sanitation with the time and the cause, and the late start is coded to what caused it. Unit: late-start minutes by cause.
Line downtime · Variance
Mobile app for iOS and Android. Not yet deployed at a plant. We're looking for the design partners who will run it first.
Library and Ask
If your QA manager leaves Friday, what can the new one read on Monday?
- 1 Only your documents
- 2 Cited to the page
- 3 Your manuals, indexed
Only your documents. CFRs, HACCP plans, SSOPs, manuals, training material. Never a general model's training data.
Every claim cited, reasoning shown. One click opens the source at the passage.
It says so when it cannot answer. No sources, conflicting sources, a citation that does not hold up: it tells you, instead of guessing.
What the record holds. When the senior mechanic's fix for the #3 sealer is written down, it is a cited page with a name and a date on it, not a story told at shift change.
Compliance labor · Labor and fees
How the assistant is allowed to answer
The model is never free to invent.
Grounded, cited, and it stops when the record stops.
- 01
Grounded only on your records
It answers from the documents and results you uploaded, and from nothing else.
- 02
Cited, with the reasoning shown
Every claim carries a citation to the passage, and the steps it took to get there.
- 03
It never says compliant
It reports gaps, or no gap found against the clauses it checked. A qualified person decides.
- 04
A person is in the loop
Anything that counts as a record is confirmed by a person before it does. That is today's ceiling, and we say so.
Where your data goes. Lumina runs in the cloud, with each customer's data isolated in its own tenant. Your data is used to answer your questions and build your record; it is not used to train third-party models, and the assistant is not a shared wrapper over a general chatbot. We intend to train Lumina's own models on de-identified data, under the terms of your agreement, and never anyone else's. The plant sets what is captured and how long it is kept. Where a customer needs it, we can run the models in our own cloud environment, so your documents don't go to an outside AI provider.
Compliance intelligence In development
Your SOPs, read against the regulation, and the gaps brought to you.
Regulation and your documents, together. 9 CFR 416 and 417 read against your SOPs and HACCP plans, section by section.
Edits proposed in your own document. Verbatim clause, confidence, reasoning. Your HACCP-trained individual or PCQI confirms or rejects.
Re-checked when anything moves. A regulation, directive or scheme update, or an SOP revision, re-flags the gaps.
It never says compliant. It reports gaps, or no gap found against the clauses it checked. A qualified person decides, every time.
What it is for. A $50,000 annual review and days of audit prep can become a continuous first pass your expert reviews.
Compliance labor · Labor and fees
In development: demonstrated on synthetic data, not yet running on a customer's document set. The $50,000 is one account's stated spend, not a market average; a dollar is displaced only when the plant cancels the engagement.
The record
The record writes itself, for everything that happens in Lumina.
Every change, attributed. Every entry time-stamped and attributed to the person who made it, signed where the form asks for a signature, with every change kept in the audit trail. Forms, readings and issues logged offline keep the time they were actually done.
Pull any issue as a complete record. Evidenced, time-ordered, exportable as one PDF. Every view, print and export is itself logged.
What the record holds. Evidence on the day it is asked for, not a search through binders and inboxes.
Audit exposure · Revenue deduction
Built to the expectations for electronic records. Time-stamped, attributed, exportable: the shape 9 CFR 417.5(d) and 21 CFR 117.305 ask for. Schemes and agencies certify plants, never software, so we do not claim a certification.
It sits over your systems, not in place of them. 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.
The technology
What the sensor reads, and how it decides.
Everything above is live today, except where it is marked. Where it goes next is a reading taken off a surface while the line runs, built to tell your program where the next swab should go.
The signal path from reflected light to a risk signature. The research the detection is built on, the accuracy it has shown in the lab, and the validation still outstanding.