Forged Operations · Operating fleets
An operating fleet already has a quality program that works. What it does not have is the hours: thousands of condition reports a year, screened on judgment that shifts with whoever is on shift, and the people who knew why the threshold sat where it did have retired. Every record is reviewed the day it lands, against the same threshold every time, with the reasoning written down beside it.
18 questions, mapped to the NQA-1 requirements. Your score and band appear on screen without an email. Request the written report for a detailed gap list.
Illustration of a nonconformance report moving through its lifecycle: Identification, Screen and Grade and Disposition are complete, Root Cause is the current step, and Extent of Condition and Tasks and Actions come next — step 4 of 11. It was screened against the same threshold as every other record, on significance, recurrence, reportability and grade, with the reasoning recorded beside the grade.
Start here
Every nuclear quality tool arrives as a rip-and-replace: map the old data, run both systems side by side, wait a year. That cost is the reason most programs never move at all. Document control, corrective action, records — each area stands up on its own, so the program moves one area at a time rather than all at once.
Every condition report is reviewed the day it lands, against the same threshold every time, and the reasoning is written down beside it. Nothing waits for the next screening meeting to be looked at, and nobody has to remember why the last one was graded the way it was.
Related: Corrective Action Program, Records Management
Which revision was in force when the work was done, who approved it, and who held it. Procedures and forms written, reviewed, approved and issued in one place, with the signature part of the record.
Related: Document Control, Configuration Management
A condition reported, dispositioned, given a cause, and closed against evidence that the action worked. One process from the first report to the close, so the backlog is a queue rather than an archaeology exercise.
Related: Corrective Action Program, Nonconformance Management, Operating Experience
Records are connected as they are made, so an evidence package assembles on request. Every action anyone takes is recorded as it happens and cannot be edited after, and every AI answer points back to the record it came from.
Related: Auditing & Assessment, Records Management
The gap, concretely
Seven requests that come up in almost every internal audit, self-assessment and regulatory review.
| The request | What it takes today | What should carry it |
|---|---|---|
| The revision in force when the work was done | Check the controlled copy, then check whether the shop copy matched. | The revision at that date, with the record of who held it. |
| Whether the person who signed was qualified to | Training records, cross-referenced by hand against the signature. | Qualification checked against the sign-off at the moment it happened. |
| Calibration status when the measurement was taken | Certificates in a folder, matched to dates manually. | Calibration status on the measurement date, and what was affected if it lapsed. |
| Every condition report on a system, and its closure | Two logs and the ones handled informally. | One list, each with disposition, cause, and the action that closed it. |
| Whether a corrective action actually worked | A closure date, and a hope. | Effectiveness recorded against the action that claimed it. |
| Records for a job from a decade ago | Days of assembly, if the people involved are still here. | An evidence package assembled on request, traceable to source records. |
| What everyone did, and when | Reconstructed from memory and email. | Recorded automatically on every action, and never edited after. |
The process exists in every row. Having to reconstruct the evidence under review is where findings come from.
lewis · the AI quality manager for nuclear
An operating fleet makes more records in a week than any team can read. lewis reads all of them, so the ones that need a person get to a person.
The request that took three weeks comes back assembled, traceable to the source records.
Writes the cause analysis and the response from the condition report and the evidence attached to it.
Every record checked as it lands, so a gap surfaces years before someone goes looking for it.
Built by operators, in production with
Founded by engineers out of Ontario Power Generation, and in production with operating nuclear organizations. Each customer runs its own isolated instance, in our cloud, in yours, or on-premise and air-gapped. SOC 2 Type II certified — request the report.
Read first
Questions
Not all of it, and not first. Each area stands up on its own: document control, corrective action, records. Start with the one that hurts most and add the next when you are ready. There is no parallel run to staff and no cut-over date to defend.
One area at a time. Documents, forms and scanned PDFs are imported and indexed when you bring an area across, and the areas you are not ready to move stay where they are until you are.
A management system covering the whole organization, not a quality manual sitting beside it: defined processes, controls graded to safety significance, people qualified for the work they do, and records that show all of it happened. The CNSC assesses the system as it is run, not as it is written.
Eighteen questions against the NQA-1 requirements. See your score and band without an email, then request the written report for a detailed gap list.
Prefer email? [email protected]