Forged Operations · Operating fleets
An operating fleet already has a quality program that works. What it does not have is one place to look: document control in one system, corrective actions in another, thirty years of records on a shared drive, and an evidence request that takes three weeks. Records are read where they already sit, so none of it has to move first.
18 questions, mapped to the NQA-1 requirements. Your score and gap list open as soon as you tell us where to send the report.
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. Records can be read where they already sit and brought in as they are used.
Files sync in from the shared drive or SharePoint you use now. Documents, forms and scanned PDFs are read and indexed as they arrive, so nothing has to be re-keyed and nothing has to move before you start.
Related: Records Management, Document Control
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.
Read first
Questions
No. That requirement is what stops most programs from moving at all. Records can be read where they already sit, on a shared drive or in SharePoint, and brought in as they are used rather than all at once. There is no parallel run to staff and no cut-over date to defend.
It reads from them. Files sync in from the storage you already use, and documents, forms and scanned PDFs are imported and indexed as they arrive. 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. Tell us where to send the report and your score, band and gap list open on screen.
Prefer email? [email protected]