Introducing FACILEX® ATOMIC nuclear quality assurance software for small modular reactors, fusion and advanced fission. 

FACILEX® ATOMIC
Nuclear Quality Assurance Software

Small Modular Reactors, Fusion, Advanced Fission - Quality Assurance & Compliance

FACILEX® ATOMIC connects 21 configurable software applications through the Plan-Do-Check-Act cycle so requirements, work, evidence, learning and corrective action never become disconnected.

ADVANCED NUCLEAR QUALITY ASSURANCE & OPERATIONAL GOVERNANCE

Advanced reactor organizations rarely lack documents.

They lack a reliable way to connect them.

Requirements, technical decisions, assigned work, supporting evidence and management approval must remain connected across the full lifecycle.

FACILEX® ATOMIC provides that connective tissue through an integrated nuclear quality assurance and operational governance platform.  Each application supports a defined nuclear or fusion business process, while the suite preserves the relationships among changes, conditions, SSCs, documents, qualifications, suppliers, readiness gates and operating experience.

The result is a defensible management system that shows not only what was decided, but why it was decided, who authorized it, what evidence supported it and whether the outcome was effective.

What changes when the loop is connected?

  • Fewer process gaps – Every action has a governed destination instead of disappearing into an informal tracker.
  • Faster readiness decisions – Leaders see prerequisites, open conditions and evidence in one current view.
  • Stronger configuration control – Physical changes, documents software, procedures and training converge on the same approved end state.
  • More credible oversight – Auditors, regulators, owners and customers can trace decisions from requirement to implementation and verification.

Integrated Nuclear Quality Assurance Across the Plan-Do-Check-Act Lifecycle

FACILEX® ATOMIC integrates 21 configurable nuclear quality assurance, regulatory compliance and operational governance applications within a Plan-Do-Check-Act (PDCA) lifecycle. From requirements, design basis and change control through controlled work, audits, operating experience and corrective action, FACILEX® ATOMIC preserves the relationships among processes, records, decisions and evidence throughout the nuclear lifecycle.

PLAN
Define requirements, risk, design basis and work
Change Control Project Delivery Assurance Hazard & Safety Case Integrated Risk Register Design Basis Information Procedure Management Job Hazard Analysis
DO
Execute controlled work, deployment and operations
Supplier & Contractor Assurance SSC Data Integration Credited Controls & Safety Functions Training & Qualification Transmittals & Vendor Data Licensing & Regulatory
CHECK
Verify performance, assess conditions and learn
Audits and Assessments Event Reporting Operating Experience Operational Readiness Reviews Bypass & Impairment Control
ACT
Correct, improve and institutionalize change
Corrective Action Program Action Item Management Organizational Change Control

START WHERE THE BUSINESS PAIN IS GREATEST

Change Control, Corrective Action & Action Item Management

The Big 3 create the backbone of closed-loop governance

FACILEX® ATOMIC Change Control, Corrective Action Program and Action Item Management can be deployed independently, but together they create a closed-loop governance system that ensures technical changes, adverse conditions and routine follow-up items receive the appropriate level of control, accountability and verification.

1. Change Control

Control technical and configuration changes across nuclear structures, systems and components (SSCs), documents, software, procedures and training.

  • Risk-based reviews and authorizations
  • Emergency changes and controlled documentation
  • Version control, traceability, audit trail and change history

2. Corrective Action Program

Turn adverse conditions into controlled corrective actions with defined accountability, follow-up, progress tracking and closure.

  • Integrated condition reporting and corrective actions
  • Defined workflows, ownership and accountability
  • Effectiveness reviews and recurring condition tracking

3. Action Item Management

Capture, assign and manage commitments and follow-up actions while maintaining visibility across projects, corrective actions and nuclear business processes.

  • Ownership and timely completion
  • Escalation and reporting on critical items
  • Integration with CAP, projects and related processes

THE FACILEX® ATOMIC ADVANTAGE

More Than Workflow: A Configurable Operational Assurance Platform

FACILEX® ATOMIC combines governed business processes, controlled information and enterprise integration in a configurable nuclear operational assurance platform that works with specialized enterprise and engineering systems rather than attempting to replace them.

Configurable lifecycle automation

States, actions, approvals, risk tools, checklists and business rules are configured through the user interface by trained end users.

Governed data and document vaults

Preserve revisions, approvals, relationships, applicability and audit history while giving authorized users fast access to the correct information.

Enterprise integration

Connect FACILEX® processes to SAP, Maximo, Microsoft platforms, engineering tools, document systems and analytics without duplicating their core functions.

Your Nuclear Compliance Program Should Operate as a System
Not a Collection of Folders, Spreadsheets and Inboxes.

When critical information is spread across email, spreadsheets, shared drives and disconnected applications, every audit, readiness review and management decision becomes a data-reconciliation exercise. 

FACILEX® ATOMIC creates a connected nuclear compliance environment where the evidence trail is created as the work is performed.

In one connected nuclear compliance environment, leaders can see:

  • What requires attention now
  • Which SSCs, documents and requirements are affected
  • Who owns each decision commitment and action
  • What evidence supports completion
  • Whether actions were verified and demonstrated to be  effective

Book a Working Session - See Your Own Process in FACILEX® ATOMIC

Bring one current process, procedure or pain point. Gateway will map it to the FACILEX® ATOMIC lifecycle, show how the applications connect and identify a practical first deployment that can provide value quickly.

Your highest priority use case

Change Control, CAP, readiness, design basis, supplier assurance or another urgent need.

Your current systems

Where FACILEX® should integrate – and where SAP, Maximo or specialized tools remain authoritative.

A credible first deployment

A focused path that solves a recognizable problem and demonstrates suite-wide potential. 

Why FACILEX® ATOMIC is the Right Software for the Job

FACILEX® ATOMIC is the nuclear and fusion edition of the FACILEX® suite: twenty-one configurable applications, built on the Microsoft platform, that govern the lifecycles, approvals, evidence and configuration context a nuclear organization is required to control.

Every application has been configured to address the regulatory frameworks that actually apply:

  • 10 CFR 50 Appendix B and NQA-1,
  • 10 CFR 50.59 and NEI 96-07,
  • 10 CFR Part 52 ITAAC closure,
  • 10 CFR 70 Subpart H Integrated Safety Analysis,
  • NEI 18-04 Licensing Basis Events,

For fusion and DOE-affiliated facilities:

  • 10 CFR 830, 10 CFR 851
  • DOE Order series

The vocabulary, the classifications and the determination records are the ones that regulators, auditors and new nuclear-experienced hires already expect.

Three markets, one platform:

  • Small modular reactors and advanced fission. Part 50 and Part 52 licensees, fleets of identical modules, and the ITAAC closure that legally precedes fuel load.
  • Fuel cycle. HALEU and TRISO enrichment and fabrication facilities under 10 CFR 70 Subpart H, where HAZOP, What-If, FMEA and checklist analysis with IROFS designation is the specified methodology — not a translation.
  • Fusion. Agreement State byproduct licensees and DOE-affiliated facilities, where hazard analysis, readiness reviews, procedure programs and configuration management are required by the DOE framework and, in most organizations, do not yet exist.

What FACILEX® ATOMIC Does Not Do

This matters as much as what it does. Your systems of record stay where they are. SAP and Maximo keep your equipment master. Your EDMS keeps your controlled documents. Your LMS keeps course delivery. Your work management system keeps clearances and schedules. CAFTA, SAPHIRE and RiskSpectrum keep your probabilistic risk assessment, and your I&C vendors keep their design tooling.

FACILEX® ATOMIC integrates with your systems of record and owns the compliance layer above them. That is a shorter procurement conversation and a much shorter argument with your IT organization.

Why a Suite, Not Twenty-One Tools

Point tools fail in nuclear for a specific and repeatable reason: the regulations do not treat programs as independent. They require that decisions made in one program propagate into every other program that carries their consequences. Three structural patterns run through the entire portfolio.

  1. The Corrective Action Program is the hub

Audit findings, event reportability determinations, inbound operating experience, promoted action items, degraded conditions requiring operability determination, supplier corrective actions and design basis discrepancies all funnel into one Corrective Action Program with traceable closure and verified effectiveness. Auditors and inspectors check that integration specifically. In a collection of point tools it does not exist.

  1. Safety analysis has to reach the implementing programs

The chain runs: a hazard is identified, a control is credited, the control is specified and classified, the classification generates required treatment, and that treatment propagates into equipment data, procurement, surveillance, procedures, training, qualification, change screening and readiness verification. Both frameworks name this explicitly — “special treatment” under NEI 18-04 and 10 CFR 50.69, “management measures” under 10 CFR 70 Subpart H. When the chain breaks it breaks silently, and the finding arrives years later.

  1. Readiness is a query, not a binder

Startup, restart, mode change and return to service all ask the same question: given everything that has been done, is it safe and compliant to operate? Every input to that answer — condition reports, surveillance currency, impairments and compensatory measures, procedure approvals, training currency, permits, test results, open items — already lives in the portfolio. Computing readiness instead of assembling it is the single largest recurring saving in the suite, and it is the one capability no point tool can offer at any price.

The change lifecycle, in three applications

  • Change Control decides whether you are permitted to make the change, and whether the regulator must approve it first.
  • Project Delivery Assurance executes it — scope, design, testing and turnover.
  • Operational Readiness Reviews authorizes operation once it is done.

Permitted, executed, authorized to run. One change object, three sequential decisions, three auditable records.

FACILEX® ATOMIC TWENTY-ONE APPLICATIONS

Change Control, the Corrective Action Program and Action Item Management appear first: they carry the highest regulatory weight and the highest transaction volume in any nuclear organization, and they are where every implementation should begin. The remaining eighteen follow alphabetically.

Configured, not customized. Each FACILEX® ATOMIC application is delivered configured to your requirements. Lifecycles, classifications, forms, checklists and screening rules are configuration — which is why a FACILEX® ATOMIC deployment is measured in weeks rather than in development cycles.

Platform, Connect and Deployment

Built on Microsoft 365 Ecosystem

FACILEX® ATOMIC runs on the platform your organization already licenses, governs and audits. Word and Excel for protocols, checklists and analysis worksheets. SharePoint Subscription Edition for controlled content. Power BI and Excel for reporting. Teams and Outlook for notification and approval. Full mobile access on tablets and phones for field execution — pre-job briefs, readiness walkdowns, audits, surveillances and impairment verification performed where the work is.

FACILEX® Connect

  • UDR — links FACILEX® business objects to external platforms such as SAP, Maximo and PLM systems including Windchill and Teamcenter.
  • Aggregation — one “my responsibilities” view across every application, facility and unit in the fleet.
  • Vault — links business processes to controlled document libraries in SharePoint or your existing EDMS.
  • Navigator — graphical asset structure navigation across site, unit, system and component.
  • DataMart — SQL Server staging for reporting and analytics.
  • Mobile — initiates any FACILEX® business process from a mobile interface.
  • Visualization — Excel and Power BI integration for specific and aggregated reporting.

Deployment options

Subscription Software as a Service on Microsoft Azure, client-dedicated Azure hosting, or on-premises deployment under a prepaid licensing model. Subscription delivers the fastest route to production and removes on-premises software, hardware and support cost. Comprehensive user training is included with every deployment; administrator training with a dedicated training site is available on subscription.

FACILEX® solutions are available on multiple platforms and in all Microsoft-supported languages.

 

CHANGE CONTROL [CC]

Screening, evaluation and authorization for every change — 50.59, 50.54, USQ and standard-design departures in one governed pipeline.

THE CHALLENGE

In nuclear the question is never only “is this change safe?” It is “may we make this change at all without asking the regulator first?” A single modification can require a 50.59 evaluation, a 50.54(q) emergency plan screen, a 50.54(p) security screen, a 50.54(a)(3) QA program screen and fire protection change control — simultaneously. Most organizations run those gates as separate, disconnected processes. “We screened it under 50.59 but nobody caught the emergency plan impact” is one of the most familiar findings in the industry.

WHY IT MATTERS NOW

  • One change in, every required screen out. A proposed change is routed automatically through 50.59 applicability, screening and evaluation and through every parallel gate it touches, with an auditable determination record for each. Nothing falls between programs.
  • The eight criteria, enforced rather than remembered. NEI 96-07 evaluation logic is built in, so a “yes” on any criterion stops the change and opens a License Amendment Request under 50.90 before work is authorized — not after it is installed.
  • Part 50 and Part 52 in one engine. Certified-design changes follow the Tier 1 / Tier 2 / Tier 2-Star departure processes under 52.63 and 52.98; operating-plant changes follow 50.59. You do not need two systems and two sets of training.
  • Fleet propagation, finally controllable. Change the standard design once and see every module it lands on, which units have taken it, and which hold approved deviations. Tools built for single-unit plants were never designed for twelve identical modules.
  • USQ determinations for DOE-authorization-basis and fusion facilities. The same configurable screening engine performs 10 CFR 830.203 Unreviewed Safety Question evaluations against the Documented Safety Analysis.
  • Digital I&C given its own path. The hardest evaluations in the industry — NEI 96-07 Appendix D — get guided treatment instead of a blank form and an optimistic reviewer.

 

LIFECYCLE

Initiation  ▸  Applicability  ▸  Screening  ▸  Evaluation  ▸  Approval / LAR  ▸  Implementation  ▸  Closure

CAPABILITIES  Configurable screening gates by jurisdiction, license type and facility · temporary modifications, equivalency and like-for-like determinations · setpoint and method-of-evaluation change tracking · automatic 50.71(e) UFSAR update queue · qualification-gated preparer and reviewer assignment · complete determination history retained as a QA record

REGULATORY ANCHORS  10 CFR 50.59 · NEI 96-07 (RG 1.187) · 10 CFR 50.90 · 50.54(a)(3), (p), (q) · 10 CFR 50.48 · 10 CFR 52.63 / 52.98 · 10 CFR 50.71(e) · 10 CFR 830.203 (USQ)

CONNECTS WITH  Hands executed work to Project Delivery Assurance, document consequences to Design Basis Information, affected procedures to Procedure Management, retraining to Training & Qualification, and authorization to operate to Operational Readiness Reviews.

If your change process cannot prove which screens were performed and why, you are one inspection away from finding out.

CORRECTIVE ACTION PROGRAM [CAP]

Condition reporting, graded cause analysis, extent of condition and verified effectiveness — the program a regulator samples first.

THE CHALLENGE

The Corrective Action Program is not a quality back office. It is the plant’s central nervous system and the front door to regulatory oversight. Inspectors sample condition reports continuously, and Problem Identification & Resolution is a standing inspection area. A low condition report volume is not evidence of a clean plant — it is read as a weak safety culture. Your CAP has to make low-threshold reporting cheap, and it has to survive the volume that follows.

WHY IT MATTERS NOW

  • Built for thousands of reports a year, not dozens. Screening in minutes rather than triage in weekly meetings. If reporting a condition is expensive, people stop reporting conditions — and that is the failure the NRC is looking for.
  • Graded analysis, routed automatically. Significance screening sends each condition to root cause, apparent cause or correction-only, with operability and reportability determinations captured on the record where an inspector will look for them.
  • Extent of condition that actually extends. Search the same condition across systems, units, sites and — for SMR fleets — every identical module, with documented extent-of-cause reasoning rather than an assertion.
  • Effectiveness reviews that cannot be skipped. Closure requires verified effectiveness, not a completed task. Repeat conditions are the finding; trending catches them before the regulator does.
  • Every other program funnels here by design. Audit findings, reportability determinations, inbound operating experience, supplier corrective actions and design basis discrepancies all land in one program with traceable closure. That integration is specifically what auditors check.
  • Fusion-ready without waiting for a mandate. First-of-a-kind machines generate anomalies faster than any spreadsheet survives. The same discipline, graded so a research-to-operations organization is not buried by its own low-significance findings.

 

LIFECYCLE

Identification  ▸  Immediate action  ▸  Screening  ▸  Cause analysis  ▸  Corrective action  ▸  Effectiveness review  ▸  Closure

CAPABILITIES  CAQ / SCAQ classification · trend coding and recurring-condition analytics · operability and reportability capture · extent of condition and extent of cause · action to preclude recurrence · due-date governance and escalation · supplier corrective action requests · fleet-wide search

REGULATORY ANCHORS  10 CFR 50 Appendix B Criterion XVI · NQA-1 Requirement 16 · NRC Reactor Oversight Process (PI&R) · NRC Inspection Manual 9900 (operability)

CONNECTS WITH  Receives from Audits and Assessments, Event Reporting, Operating Experience, Action Item Management, Design Basis Information and Supplier & Contractor Assurance. Escalates to Change Control when the fix is a modification.

Every regulator conversation you will ever have begins in your corrective action program. Make it the strongest thing you own.

ACTION ITEM MANAGEMENT [AIM]

The disciplined, auditable home for everything below the CAP threshold — with a documented path into it.

THE CHALLENGE

Not every issue belongs in the corrective action program, and no plant wants a condition report for a slow printer. But an off-CAP tracker that quietly holds conditions which should have been screened is one of the more serious findings a licensee can collect, and there is enforcement history to prove it. The answer is not to ban the bucket — every organization needs one. The answer is to make the bucket defensible.

WHY IT MATTERS NOW

  • A CAP screening gate on intake. Every item is screened against corrective action program thresholds on entry and the determination is recorded. You can show an inspector exactly why each item is where it is, in seconds.
  • One-click promotion with full lineage preserved. When an item turns out to be adverse to quality it becomes a condition report without losing a word of its origin, ownership or age.
  • Nothing is invisible. The entire register is reportable, searchable and ageable — the precise opposite of the spreadsheets, mailbox folders and personal notebooks it replaces.
  • Cross-functional action in one place at last. Design review actions, walkdown punch items, self-assessment improvements, meeting commitments, enhancement requests and suggestions with real owners and real dates.
  • Aging analytics that argue for themselves. Overdue low-level items are exactly where accumulated risk begins. The pile becomes visible to you before it becomes visible to someone else.
  • For fusion, the fastest win in the portfolio. Test campaigns and commissioning walkdowns generate action items faster than any team tracks by hand, and there is no threshold doctrine to navigate first.

 

LIFECYCLE

Creation  ▸  CAP screening  ▸  Assignment  ▸  Active  ▸  Verification  ▸  Closure

 

 

CAPABILITIES  Configurable threshold screening rules · promotion to CAP with retained lineage · classification by department, facility, owner and urgency · resolution depth from a single step to dozens · recurring and scheduled actions · aggregated “my responsibilities” view spanning every application in the suite

REGULATORY ANCHORS  CAP threshold discipline (PI&R inspection area) · 10 CFR 50 Appendix B Criterion XVI interface

CONNECTS WITH  Promotes into the Corrective Action Program and receives follow-up items from every other application in the portfolio.

A low-level action register is either your best evidence of a questioning organization or your worst inspection finding. The only difference is whether the screening was written down.

AUDITS & ASSESSMENTS [AA]

Audits, surveillances, self-assessments and supplier audits — planned, staffed, evidenced and closed.

THE CHALLENGE

Nuclear is the most audit-intensive industry there is. Appendix B Criterion XVIII and NQA-1 Requirement 18 require planned, scheduled audits of the entire quality assurance program with documented findings, management review and verified corrective action closure. That is before NUPIC supplier audits, independent assessments, self-assessments, readiness assessments and preparation for the inspections you do not schedule yourself.

WHY IT MATTERS NOW

  • Audits and surveillances, treated as different instruments. Comprehensive programmatic audits and narrow activity-focused surveillances carry different scopes, intervals and evidence expectations. Software that only understands “audit” fails its first NQA-1 review.
  • Schedule coverage you can prove on demand. Every required audit, its interval, its last performance and its next due date in one view. It is the question every quality assurance manager is asked and very few can answer instantly.
  • Auditor qualification and independence enforced at assignment. Lead auditor certification, team independence and conflict declarations are checked when the team is formed, not discovered during report review.
  • Findings that reach the CAP by design. Condition adverse to quality and significant condition adverse to quality classifications with automatic transfer into the corrective action program and verified effectiveness closure — the integration auditors look for first.
  • Protocols in whatever technology fits the task. Master protocols and checklists as Word or Excel documents or configurable forms, executed in the field on a tablet, with evidence attached line by line.
  • Graded for fusion without a rewrite. ISO 9001 foundations with NQA-1 applied selectively to safety-significant scope: the same engine, different criteria libraries, no second product to buy.

 

LIFECYCLE

Plan  ▸  Team & independence  ▸  Prepare  ▸  Execute  ▸  Classify findings  ▸  Report  ▸  CAP transfer  ▸  Effectiveness

 

CAPABILITIES  Master protocol and template library · risk-based supplier audit frequency and scorecards · sampling plans and evidence requests · factual accuracy review · recurring-finding trending · multi-site aggregated reporting

REGULATORY ANCHORS  10 CFR 50 Appendix B Criterion XVIII · NQA-1 Requirement 18 · NUPIC joint audits · 10 CFR Part 21 interface · ISO 9001 (graded programs)

CONNECTS WITH  Sends findings to the Corrective Action Program, draws qualification context from Supplier & Contractor Assurance, supplies evidence to Licensing & Regulatory, and feeds Operational Readiness Reviews.

An audit program you cannot schedule, staff and close on demand is not a program. It is a stack of reports.

BYPASS & IMPAIRMENT CONTROL [BIC]

What is defeated right now, what compensates for it, who verified it this shift, and how much time is left.

THE CHALLENGE

Your corrective action program tracks a condition toward resolution. Your change process authorizes a temporary modification once. Neither answers the question a shift supervisor asks every twelve hours: what is impaired at this moment, and what is holding the plant safe while it is? Today that answer lives in four or five disconnected logs owned by four or five different departments.

WHY IT MATTERS NOW

  • Clocks that cannot be missed. Technical Specification LCO Action Statement completion times are the highest-consequence clocks in the plant. Exceed one and you are shutting down or explaining yourself. Every clock, visible, escalating, in a single register.
  • Compensatory measures with per-shift verification. Fire watches under NFPA 805, security compensatory measures under 73.55, emergency plan equipment degradations under 50.54(q) — each logged, each verified every shift, each provable months later.
  • The jumper and lifted-lead log becomes a live control. Defeated annunciators, bypassed interlocks and temporary modifications, aged and reviewable, instead of a binder nobody has audited since the last outage.
  • Twelve modules, one site picture. Multi-module plants with independent LCO clocks, shared systems and reduced control-room staffing need a site-level impairment view that no existing tool provides.
  • Shift turnover in one screen. Impairment state, compensating actions, expiring clocks and verification status handed over cleanly rather than recited from memory at the end of a twelve-hour shift.
  • Fusion interlock bypass permits — an unserved need. Every major device runs a formal interlock defeat process during commissioning and nobody sells software for it. Magnet, RF, laser, vacuum, tritium and oxygen-deficiency interlocks under one controlled bypass regime.

 

LIFECYCLE

Request  ▸  Authorization  ▸  Compensatory measures  ▸  Shift verification  ▸  Restoration  ▸  Closure

CAPABILITIES  LCO completion time tracking with escalation · fire protection impairment register · temporary modification and bypass log · per-shift verification records · expiring-clock dashboard · aggregate exposure by system, unit and site

REGULATORY ANCHORS  Technical Specification LCO 3.0.4 and Action Statements · 10 CFR 50.48 / NFPA 805 · 10 CFR 73.55 · 10 CFR 50.54(q) · 10 CFR 830 Subpart B (Technical Safety Requirements)

CONNECTS WITH  Change Control authorizes the bypass; the Corrective Action Program documents the condition; Licensing & Regulatory issues permits that create compensatory measures; Operational Readiness Reviews requires the register clear before startup.

Nobody plans to run out of completion time. They run out of visibility first.

CREDITED CONTROLS & SAFETY FUNCTIONS [CSF]

Every control the safety case relies on — specified, classified, and carrying its obligations downstream.

THE CHALLENGE

Your hazard analysis credits a safety function in a sentence. Turning that sentence into a specified, classified, obligation-bearing object is where safety cases quietly fail. The analysis says the trip protects the plant. Nobody can produce the setpoint basis, the margin that remains after twenty years of small changes, or the list of programs now required to treat that component differently from every other component.

WHY IT MATTERS NOW

  • Classification that propagates by itself. Classify a function once — Safety-Related, NSRST, IROFS — and the required treatment appears automatically in equipment data, procurement, surveillance, procedures, training and change screening. Both frameworks demand exactly this: “special treatment” under NEI 18-04 and 50.69, “management measures” under 10 CFR 70.
  • Setpoint margin you can actually see. The full chain from Analytical Limit through Safety Limit, Limiting Safety System Setting and trip setpoint to as-found and as-left tolerances, with instrument uncertainty and drift documented — and a live view of how much margin is left.
  • IROFS management for the fuel cycle. The exact regulatory object under 10 CFR 70 Subpart H, with availability and reliability evaluation and full management-measures traceability. HALEU and TRISO facilities need this now.
  • SIL determination where SIL genuinely belongs. PFD calculation for fusion machine protection and personnel safety systems, balance-of-plant instrumented functions, and IEC 61513 / 61226 Category A, B and C classification for internationally licensed projects.
  • The change impact question nobody can currently answer. Reclassify a function and immediately see which procedures, surveillances, procurement controls and qualifications are now non-compliant — before the audit finds them.
  • Specification records that survive scrutiny. Redundancy, channel independence and separation, diversity, testability and fail-safe behaviour specified per function under IEEE 603 and IEEE 7-4.3.2 and held as controlled artifacts.

 

LIFECYCLE

Credit from analysis  ▸  Specify  ▸  Classify  ▸  Generate treatment  ▸  Verify  ▸  Maintain through change

CAPABILITIES  Credited function register · setpoint methodology and uncertainty records · safety classification schemes by regulatory framework · special treatment and management measures generation · SIL and PFD calculation · downstream obligation propagation with live compliance gap view

REGULATORY ANCHORS  10 CFR 70 Subpart H (IROFS) · NEI 18-04 / RG 1.233 · 10 CFR 50.69 · RG 1.105 · ANSI/ISA-67.04.01 · TSTF-493 · IEEE 603 / IEEE 7-4.3.2 · IEC 61508 / 61511 / 61513 / 61226

CONNECTS WITH  Hazard & Safety Case credits the function; SSC Data Integration carries the classification; Procedure Management, Training & Qualification, Supplier & Contractor Assurance and Change Control inherit the obligations. Your I&C vendors keep the design tooling.

A credited control with no specification, no margin record and no downstream obligations is not a control. It is an assumption.

DESIGN BASIS INFORMATION [DBI]

The controlled register of what your design basis is, whether it is complete, and whether it still matches the plant.

THE CHALLENGE

Configuration management is the discipline of keeping three things consistent: what the plant must do, what the documents say it is, and what it actually is. They drift. The industry has already run this experiment — the design basis crisis of the late 1990s, the 50.54(f) letters that followed, and a decade of design basis reconstitution at extraordinary cost. Nobody who lived through it wants to price the sequel.

WHY IT MATTERS NOW

  • Answers the one question a document system cannot. An EDMS knows what it has. Only a register knows what is missing — which required documents do not exist, which are overdue for review, and which cannot be located at all.
  • The document update backlog, closed. When a modification is implemented, dozens of artifacts must be revised: drawings, calculations, design basis documents, the master equipment list, setpoint lists, procedures, training material and eventually the UFSAR under 50.71(e). Tracked to closure instead of discovered three years later.
  • Discrepancies become condition reports, not notes. Drawing does not match the plant? Calculation cannot be found? That is a CAP entry with an owner and a due date, which is exactly how the regulator expects it to be handled.
  • Integrates rather than replaces. Your controlled documents stay in your EDMS, SharePoint or vault. This is the index, the currency status, the retention classification and the linkage to requirements and SSCs — the layer no repository provides.
  • Qualification files that are genuinely auditable. 10 CFR 50.49 requires an auditable environmental qualification file; 50.71(c) and 50.75(g) require retention. Completeness becomes a status you report rather than a project you commission.
  • For fusion: capture it now, or reconstitute it later. The plasma operating envelope, tritium inventory limits and confinement barriers, magnet quench basis, neutronics and activation assumptions and materials irradiation limits are being generated this year — on a design that changes weekly, scattered across PLM systems, CAD, wikis and notebooks. The fission industry has already published the price of the alternative.

 

LIFECYCLE

Requirement  ▸  Required-document register  ▸  Currency & review  ▸  Change-driven update  ▸  Discrepancy resolution  ▸  Retention

CAPABILITIES  Required-document register with currency status · design basis to SSC and requirement linkage · review clocks and obsolete-version control · update-to-closure tracking driven by approved changes · lifetime and non-permanent retention classification · discrepancy workflow into the CAP

REGULATORY ANCHORS  10 CFR 50.2 (design bases) · Appendix B Criteria III, VI and XVII · NQA-1 Requirements 3, 6 and 17 · 10 CFR 50.49 · 50.71(c) and (e) · 50.75(g) · DOE-STD-1073

CONNECTS WITH  Change Control authorizes the change; this application tracks its document consequences. Feeds Credited Controls & Safety Functions, Procedure Management and Operational Readiness Reviews.

Design basis reconstitution is the most expensive project you will ever run — and the most avoidable.

EVENT REPORTING [ER]

Reportability screening, notification clocks and event investigation — with the determination record that proves the call.

THE CHALLENGE

When something happens, the clock starts before the investigation does. 10 CFR 50.72 notifications run on 1-, 4- and 8-hour clocks. Licensee Event Reports are due in sixty days. Part 21 evaluations carry their own screening and timing. Missed notification timeliness is a recurring violation category — not because licensees do not care, but because the clock started while people were still deciding whether it had.

WHY IT MATTERS NOW

  • Clocks start automatically, from the first entry. Event classification drives the notification clock, the escalation path and the on-call notification the moment the record is created — not when the first meeting convenes.
  • Prove why you did not report. Non-reportable determinations require an auditable basis just as much as filings do. Every screening decision is recorded with its rationale and its reviewer, which is precisely what an inspector samples.
  • LER content assembled, not reconstructed. Prescribed 50.73 content — cause, corrective action, safety significance — built from the record you already have rather than assembled under pressure on day fifty-five.
  • Part 21 in both directions. Evaluate potential defects and noncompliances that could create a substantial safety hazard, and screen inbound vendor notifications straight into the corrective action program.
  • Multi-jurisdiction reportability for fusion. Agreement State requirements vary by jurisdiction and 20.2202 / 20.2203 obligations differ from federal reactor rules. Configurable rule sets rather than a hardcoded assumption about who regulates you.
  • One event, every obligation screened. Radiological reporting under Part 20, industrial recordables, security events and INPO or WANO submissions all screened from a single record instead of five parallel conversations.

 

LIFECYCLE

Notification  ▸  Classification & clock  ▸  Reportability screening  ▸  Investigation  ▸  Regulatory submission  ▸  CAP transfer  ▸  Closure

 

CAPABILITIES  Configurable event taxonomies and clock rules · on-call escalation · reportability determination records · LER and submittal assembly · actual versus potential severity assessment · operating experience export · extensive trending and graphical reporting

REGULATORY ANCHORS  10 CFR 50.72 · 10 CFR 50.73 · 10 CFR Part 21 · 10 CFR 20.2202 / 20.2203 · 10 CFR 50.9 · INPO / WANO event reporting

CONNECTS WITH  Cause analysis lives in the Corrective Action Program; transferable lessons flow to Operating Experience; supplier-origin defects route to Supplier & Contractor Assurance.

The hour you spend deciding whether the clock has started is an hour off the clock.

HAZARD & SAFETY CASE [HSC]

HAZOP, What-If, FMEA, FFMEA and checklist analysis — with every credited assumption traceable to the program that implements it.

THE CHALLENGE

Both nuclear and fusion have sophisticated safety analysis and chronically weak linkage between that analysis and the programs carrying its assumptions. The analysis is rarely wrong. What fails is the chain: the hazard was identified, the control was credited, and then nobody propagated the obligation into procurement, procedures, surveillance and training. That break is silent, and it is the finding.

WHY IT MATTERS NOW

  • The methods your analysts already use, where they are actually required. 10 CFR 70 Subpart H Integrated Safety Analysis explicitly calls for process hazard analysis techniques — HAZOP, What-If, FMEA and checklists — with IROFS designation and management measures. So does the DOE hazard analysis framework behind every Documented Safety Analysis. This is not a translation; it is the specified method.
  • IROFS to management measures, traced end to end. The regulation states that once you rely on an item, specific programs must apply to it. This is the tool that makes that statement true, current and provable.
  • Licensing Basis Event management for advanced reactors. AOOs, DBEs, BDBEs and derived DBAs under NEI 18-04, plotted against the Frequency–Consequence Target, with SSC classification, Required Functional Design Criteria and defense-in-depth evaluation. Because LBEs are co-developed with the design, version control and impact assessment across hundreds of events is the entire job.
  • FFMEA for fusion — not a fission framework in disguise. Functional Failure Modes and Effects Analysis is the recognized method. Tritium, activated tungsten dust, beryllium, loss of vacuum, coolant ingress, beryllium- and tungsten-steam reactions, stored magnetic and capacitive energy, cryogens and oxygen deficiency, analysed on their own terms.
  • Fire, criticality, internal hazards and human factors in one register. Fire Hazards Analysis under Appendix R or NFPA 805, Nuclear Criticality Safety Analysis under the ANSI/ANS-8 series, high energy line break, pipe whip, internal flooding and missile analysis, and NUREG-0711 human factors — each a named analysis with an owner and revision control.
  • It does not compete with your PRA, and says so plainly. CAFTA, SAPHIRE and RiskSpectrum keep the quantitative work. This consumes their insights and owns the traceability they were never built to hold.

 

LIFECYCLE

Scope & nodes  ▸  Hazard identification  ▸  Consequence & likelihood  ▸  Credit controls  ▸  Classify  ▸  Propagate obligations  ▸  Revalidate

CAPABILITIES  Multi-method analysis: HAZOP, What-If, checklist, FMEA, FFMEA and LOPA · project, drawing and node hierarchy · IROFS and credited control designation · LBE register with Frequency–Consequence plotting · recommendation and follow-up tracking · assumption register with validation status · equipment-to-analysis coverage search

REGULATORY ANCHORS  10 CFR 70 Subpart H / NUREG-1520 · NEI 18-04 / RG 1.233 · 10 CFR 50.69 · DOE-STD-3009 and DOE-STD-1027 · Appendix R / NFPA 805 · ANSI/ANS-8 series · NUREG-0711

CONNECTS WITH  Credited Controls & Safety Functions specifies what this application credits. Feeds Design Basis Information, Integrated Risk Register and Operational Readiness Reviews.

The safety case is not the document. It is the chain from hazard to control to program — and it breaks without a sound.

INTEGRATED RISK REGISTER [IRR]

Every risk you are monitoring, every risk you have accepted, and what the accumulation looks like in aggregate.

THE CHALLENGE

Individually justified acceptances are how facilities get hurt. A corrective action deferred to the next outage. A temporary modification that has been in place three years. A startup punch item accepted with justification. A design basis discrepancy pending resolution. A degraded-but-operable condition. Each one is defensible on its own. Davis-Besse was the sum of them, and the accumulation was visible to nobody because it lived in six different systems.

WHY IT MATTERS NOW

  • Aggregate accepted risk, visible for the first time. The acceptances already exist inside your programs. This assembles them into one view with owners, age, revalidation dates and system-level totals — the question no plant can currently answer and every board eventually asks.
  • Revalidation clocks on every acceptance. An acceptance is a decision with a shelf life. When its basis expires the item reappears for judgement rather than quietly settling into permanence.
  • Single Point Vulnerabilities and equipment reliability as living records. SPV registers, AP-913 critical and important classifications and 50.69 RISC-1 through RISC-4 categorization, maintained rather than studied once and filed.
  • Aging management across a multi-decade horizon. Part 54 aging management programs, time-limited aging analyses and GALL-derived commitments are textbook monitor-indefinitely items. They need a register with clocks, not a report with a date on it.
  • Project and first-of-a-kind risk in the same system. Licensing schedule risk, supply chain single-sourcing, financing milestones and — for DOE-funded work — formal risk management under DOE O 413.3B, in the ISO 31000 and PMI vocabulary your project team already speaks.
  • For fusion, the assumption register is the risk register. Tritium breeding ratio margin, first-wall survivability under fluence, disruption mitigation reliability, remote handling dependability, magnet quench consequence and tritium accountancy margin — tracked as assumptions awaiting validation, each with a defined closure path.

 

LIFECYCLE

Identification  ▸  Evaluation  ▸  Treat or accept  ▸  Monitor  ▸  Revalidate  ▸  Close or escalate

 

CAPABILITIES  Risk and vulnerability register with configurable ranking · accepted-risk tracking with revalidation clocks · aggregation by system, unit, site and fleet · parent-child risk relationships · aging analytics · tight integration with Power BI and Excel for executive reporting

REGULATORY ANCHORS  10 CFR 50.69 (RISC categorization) · 10 CFR Part 54 (aging management) · INPO AP-913 · 10 CFR 73.54 (critical digital assets) · ISO 31000 · DOE O 413.3B

CONNECTS WITH  Draws accepted positions from the Corrective Action Program, Bypass & Impairment Control, Operational Readiness Reviews, Design Basis Information and Supplier & Contractor Assurance. Feeds your enterprise risk function rather than replacing it, and does not perform probabilistic risk assessment.

Nobody decides to accept too much risk. They accept it one defensible item at a time.

JOB HAZARD ANALYSIS [JHA]

Radiological, industrial and plant-risk hazards in one analysis — and one pre-job brief the crew actually uses.

THE CHALLENGE

Work hazard analysis in nuclear runs on three axes and usually three systems. Radiation protection owns ALARA planning and the Radiation Work Permit. Safety owns the industrial hazards. Operations owns the online risk assessment. The crew gets briefed from three documents and everyone hopes nothing fell between them.

WHY IT MATTERS NOW

  • One analysis, all three hazard axes. Radiological dose estimates and stay times, conventional industrial hazards, and the configuration-risk consequence of removing equipment from service, assembled into a single pre-job product instead of three.
  • Online risk assessment at the point of planning. 10 CFR 50.65(a)(4) requires assessing and managing the risk increase before maintenance on risk-significant equipment. Risk-aware work screening while the schedule can still change, not after it is locked.
  • The pre-job brief, not the paperwork. Critical steps, error precursors, contingencies and STAR expectations captured in the form the crew uses at the job site — on a tablet, in the field, with the hazards in front of them.
  • FME and clearance context attached where it belongs. Foreign material exclusion zones and tagout boundaries travel with the hazard analysis rather than living in a system the crew will not open.
  • Fusion hazards no JSA template has ever contained. High magnetic fields and implant screening, cryogens and oxygen deficiency, stored magnetic and capacitive energy at lethal scale, high vacuum, Class 4 lasers, RF, beryllium and tritium. For DOE-affiliated facilities this is 10 CFR 851 and Integrated Safety Management work planning and control — and most fusion organizations have no framework for it yet.
  • Hazard libraries so the tenth job is not the first. Job-step and hazard libraries by discipline and work type mean the tenth valve replacement does not start from a blank page and a tired planner.

 

LIFECYCLE

Work scoping  ▸  Hazard identification  ▸  Radiological & risk screening  ▸  Controls & permits  ▸  Pre-job brief  ▸  Post-job feedback

CAPABILITIES  Job step and hazard libraries · dose and stay-time estimation · risk-significance flags drawn from SSC data · control and PPE selection · permit linkage · mobile field execution on tablets and phones · post-job lessons capture

REGULATORY ANCHORS  10 CFR 20.1101(b) (ALARA) · 10 CFR 50.65(a)(4) · OSHA 1910 / 1926 · 10 CFR 851 · DOE Integrated Safety Management · ANSI Z136 (laser safety)

CONNECTS WITH  Permits issue from Licensing & Regulatory and your radiation protection system; credited hazards inform Credited Controls & Safety Functions; post-job findings feed Operating Experience and the CAP.

Three hazard analyses in three systems is not defense in depth. It is three chances to miss something.

LICENSING & REGULATORY [LR]

Licenses, permits, commitments and conditions — decomposed into obligations with owners, clocks and evidence.

THE CHALLENGE

A license is not a document. It is several hundred individual obligations, each with an owner, a monitoring requirement, a reporting frequency and a renewal date. A commitment made in an RAI response twenty years ago is still binding. Reorganizations orphan them. Environmental permit conditions sit in a different department entirely. Almost nobody holds the consolidated list, which is why licensing basis reviews keep finding surprises.

WHY IT MATTERS NOW

  • One register for everything externally imposed. License conditions, permit conditions, NRC commitments, exemptions and regulatory requirements are the same object: an auditable obligation with an owner and a clock. Managing them in four systems is precisely why they get lost.
  • Commitment extraction at the moment of creation. RAI responses and submittals are where commitments are made. Capture them as they are written rather than rediscovering them during a licensing basis review two decades later.
  • Reorganization-proof ownership. Every obligation is held by a position, not a person. When the organization changes, obligations about to go unowned surface immediately instead of silently.
  • Renewal and reporting clocks that escalate. NPDES and thermal discharge, Title V air including EDG hour limits, NESHAP radionuclide emissions, effluent limits, water withdrawal, transport authorizations and ISFSI obligations — with forward visibility into what is due and who owes it.
  • The internal permits nobody else covers. Fire barrier breach and transient combustible permits, heavy load paths under NUREG-0612, scaffold seismic evaluation, excavation over buried safety-related cable, radiography and confined space — consolidated so one containment entry does not need five disconnected approvals from five departments.
  • For fusion, the license conditions that actually bite. Agreement State byproduct licenses carry tritium possession limits and named-individual conditions. You cannot change your Radiation Safety Officer quietly. Multi-jurisdiction rule sets rather than an assumption of NRC jurisdiction.

 

LIFECYCLE

Obligation capture  ▸  Decomposition  ▸  Ownership  ▸  Monitoring & evidence  ▸  Reporting  ▸  Renewal or amendment

CAPABILITIES  Condition-level obligation register · commitment extraction and traceability · permit issuance with multi-hazard consolidation · automatic compensatory measure generation · renewal and reporting calendars · evidence collection scheduling · regulator correspondence linkage

REGULATORY ANCHORS  10 CFR 50.4 · 10 CFR 50.54(f) commitments · 10 CFR 20 Appendix B / 50.36a · 40 CFR 61 Subpart H · CWA §316(a) and (b) · 10 CFR Part 71 / 49 CFR · 10 CFR Part 72 · Agreement State byproduct licenses · NUREG-0612 · NFPA 805

CONNECTS WITH  Change Control tests every change against license conditions; Bypass & Impairment Control receives the compensatory measures permits create; Audits and Assessments supplies evidence; Transmittals & Vendor Data delivers correspondence and returns extracted commitments.

Every commitment you cannot find is still binding. That is the entire problem.

OPERATING EXPERIENCE [OE]

Inbound screening with documented applicability determinations, and outbound lessons that genuinely transfer.

THE CHALLENGE

In process safety, lessons learned is what you publish after your own incident. In nuclear, operating experience is a two-way program and the inbound half is the larger obligation — SOERs, SERs, NRC Information Notices, Bulletins, Generic Letters and Regulatory Issue Summaries, Part 21 vendor notifications and other licensees’ event reports, every one requiring screening for applicability to your facility with a documented determination. Backlogged screening and thin applicability determinations are recurring findings.

WHY IT MATTERS NOW

  • The inbound stream under control. Every external item registered, screened, dispositioned with a written applicability basis and, where applicable, converted into corrective actions. Backlog becomes a number you manage rather than a surprise you inherit.
  • Determinations that survive scrutiny. “Not applicable” requires a reviewed rationale. This is exactly what inspectors sample and exactly what most organizations cannot produce quickly.
  • Response obligations tracked as the commitments they are. Some generic communications require a written response, and a Generic Letter may carry a 50.54(f) request with legal force. Those route into the licensing register automatically rather than sitting in an inbox.
  • Fleet and cross-module transfer. For an SMR fleet, an issue found on module 3 is operating experience for the other eleven. Applicability screening across identical designs is a first-order requirement, not a refinement.
  • Outbound without the manual assembly. Internal events become transferable lessons and INPO or WANO submissions from records you already hold, delivered to the point of use rather than to a shared drive.
  • For fusion, build the muscle before the mandate. There is no INPO for fusion and no required program — which is precisely why the organizations building one now will be the ones with a credible history when regulators, insurers and customers start asking for it.

 

LIFECYCLE

Receive  ▸  Register  ▸  Applicability screening  ▸  Determination  ▸  CAP actions  ▸  Communicate  ▸  Trend & close

CAPABILITIES  Inbound registry with source taxonomy · applicability determination records · response obligation tracking · cross-unit and cross-fleet screening · searchable lessons library with point-of-use delivery · outbound submission assembly · import from Office, third-party and ERP sources

REGULATORY ANCHORS  INPO / WANO SOER and SER · NRC generic communications (IN, Bulletin, GL, RIS) · 10 CFR 50.54(f) · 10 CFR Part 21 · 10 CFR 851 (DOE lessons learned)

CONNECTS WITH  Feeds the Corrective Action Program; response obligations become entries in Licensing & Regulatory; internal events arrive from Event Reporting.

Somebody has already had your next event. The only question is whether you read about it in time.

OPERATIONAL READINESS REVIEWS [ORR]

Readiness as a computed answer rather than a binder — for every startup, restart, mode change and return to service.

THE CHALLENGE

Readiness reviews are evidence-gathering exercises. Someone spends weeks assembling proof: open significant condition reports, surveillance currency, cleared impairments, approved procedures, trained operators, closed permits, accepted test results, justified punch-list deferrals. The evidence already exists inside your systems. Assembling it by hand is the entire cost — and it recurs every single time.

WHY IT MATTERS NOW

  • Readiness becomes computable. Every prerequisite is a live query against the portfolio: CAP status, surveillance currency, the impairment register, procedure approvals, training currency, permits and test records. A readiness dashboard instead of a document assembly project. No point tool can do this, because no point tool holds the other twenty data sets.
  • It is not a one-time event. Initial startup, return to service after modification, outage-to-online, mode change under LCO 3.0.4 and restart after forced shutdown are the same gate fired dozens of times a year, with graded depth for each.
  • ITAAC closure for Part 52 licensees. Hundreds of Inspections, Tests, Analyses and Acceptance Criteria, each requiring independent evidence, approval and closure before fuel load, rolling up to closure notifications under 52.99 and the §103(g) finding that legally permits operation. This is schedule risk at board level, and nobody else is selling to it.
  • Conditional authorization, actually tracked. Plants start up with documented restrictions and compensatory measures constantly, and almost never track them properly afterwards. Here every condition has an owner and an expiry.
  • Punch-list deferrals that cannot quietly accumulate. Each deferral carries a justification, an owner and a revalidation date, and rolls into the risk register where the accumulation is visible before it becomes an event.
  • DOE readiness reviews by the book. Order 425.1 with DOE-STD-3006 defines both the Operational Readiness Review and the lighter Readiness Assessment, each with a Plan of Action, Implementation Plan, criteria and review approach documents, findings closure and an authorization decision. For fusion, first plasma, tritium introduction, staged commissioning and post-vessel-entry return to service are exactly this process.

 

LIFECYCLE

Scope & grading  ▸  Prerequisites  ▸  Evidence collection  ▸  Independent verification  ▸  Open item disposition  ▸  Authorization  ▸  Post-startup closure

 

CAPABILITIES  Graded readiness templates from short-form to full ORR · prerequisite checklists with live status · evidence attachment and linkage · multi-signature and independent verification · open item and punch-list management with deferral control · ITAAC hierarchy and closure tracking · conditional authorization with expiry · field execution on tablets

REGULATORY ANCHORS  Appendix B Criterion XI · NQA-1 Requirement 11 · RG 1.68 · 10 CFR 52.99 and §103(g) · Technical Specification LCO 3.0.4 · DOE O 425.1 / DOE-STD-3006

CONNECTS WITH  Project Delivery Assurance executes the work; Change Control authorizes the change; this application authorizes operation. It consumes state from nearly every other application in the portfolio.

You already have the evidence. What you do not have is the three weeks it takes to find it.

ORGANIZATIONAL CHANGE CONTORL [OCC]

Reorganizations, staffing changes and departures — screened as safety questions, because that is what they are.

THE CHALLENGE

In nuclear, your organization is partly described in your licensing basis. Technical Specification Section 5.0 names positions and shift staffing. UFSAR Chapter 13 describes conduct of operations. Your quality assurance program description defines structure and independence. Changing any of it can require a 50.59 screen, a 50.54(a)(3) submittal or a license amendment — and almost no software treats an organization chart as a controlled object.

WHY IT MATTERS NOW

  • Screening, not just announcing. Proposed structural and staffing changes are evaluated for licensing basis impact before implementation, using the same determination engine as design change control.
  • Which license-required positions just went vacant? The question you need answered within the hour a resignation lands. Position-to-qualification mapping covers RO and SRO licenses, NQA-1 lead auditor, NDE Level II and III, the Technical-Specification-named Radiation Protection Manager and 50.59 preparer and reviewer qualifications.
  • Orphaned commitments caught at the source. Reorganizations are the single most common way NRC commitments lose their owner. Because obligations are held by position, a restructure surfaces every commitment about to go unowned.
  • Quality assurance independence preserved and provable. Appendix B Criterion I requires documented authority and independence for the QA organization. A restructure that erodes it should be flagged during review, not discovered during an audit.
  • Novel SMR staffing models defended. Fewer operators per module, one control room supervising multiple units, remote monitoring and 50.54(m) exemptions make staffing a licensing centerpiece. Every subsequent change has to be defended against the approved model — with a record.
  • For fusion, hypergrowth is the risk. Scaling from fifty to five hundred people creates acute key-person dependency and no framework to see it coming. Named-individual license conditions, such as the Radiation Safety Officer on an Agreement State license, cannot be changed silently.

 

LIFECYCLE

Proposal  ▸  Licensing basis screening  ▸  Qualification gap analysis  ▸  Transition plan  ▸  Communication  ▸  Implementation  ▸  Closure

CAPABILITIES  Position-centric organization model · position-to-credential matrix · vacancy and qualification gap alerts · obligation ownership by position · transitional condition management · temporary assignment and acting-role controls · screening determination records

REGULATORY ANCHORS  Appendix B Criterion I · NQA-1 Requirement 1 · 10 CFR 50.54(a)(3) and (m) · 10 CFR 50.74 · Technical Specification Section 5.0 · UFSAR Chapter 13 / 50.59 · 10 CFR Part 26 · IAEA GSR Part 2 · DOE O 426.2

CONNECTS WITH  Shares the screening engine with Change Control, the credential matrix with Training & Qualification, and obligation ownership with Licensing & Regulatory. Your HR system keeps the employee record.

Every reorganization is a change to something described in your license. Very few are screened like one.

PROCEDURE MANAGEMENT [PM]

The master list, the review clocks, the change screening and the traceability from requirement to procedure step.

THE CHALLENGE

Appendix B Criterion V requires that activities affecting quality be prescribed by procedures and accomplished in accordance with them. Technical Specification 5.4 and RG 1.33 Appendix A effectively hand the regulator a master list of procedures you must maintain. And in nuclear a procedure is not merely a work instruction — it is the implementing artifact for a commitment you made in writing.

WHY IT MATTERS NOW

  • Reverse impact analysis. When a Technical Specification, a design or the licensing basis changes, which procedures are affected? Almost nobody can answer this quickly, and it is the question that precedes most procedure-related findings.
  • Requirement-to-procedure traceability. Every Surveillance Requirement to the procedure that satisfies it. Every commitment to the procedure that implements it. Every PRA-credited operator action, with its assumed time window, to the step and the training objective.
  • Revisions screened rather than assumed. Procedure revisions are among the most common 50.59 inputs. A revision altering a method of evaluation or a UFSAR-described design function routes through the same screening engine as a hardware modification.
  • Review clocks and master list completeness. Periodic review obligations, controlled distribution, obsolete removal and a live view of which required procedures are missing, expired or overdue.
  • Training impact raised automatically. Modifications and procedure revisions get implemented before affected personnel are retrained. That is the recognized failure mode, and it closes with a flag on every revision.
  • The full hierarchy, including tiers process safety has never had. Emergency Operating Procedures with validation records including simulator walkthroughs, SAMGs and EDMGs, FLEX Support Guidelines under 50.155, abnormal and alarm response procedures, and surveillance test procedures each implementing a specific Technical Specification requirement.
  • For fusion, the run-sheet-to-procedure transition. Growing headcount, insurers, regulators and newly hired nuclear-experienced operations leaders all arrive expecting a procedure program. DOE Order 422.1 requires one; DOE-STD-1029 explains how to write it.

 

LIFECYCLE

Initiation  ▸  Draft / revise  ▸  Review  ▸  Change screening  ▸  Approve  ▸  Validate  ▸  Release  ▸  Periodic review

CAPABILITIES  Master required-procedure register · requirement and commitment linkage · continuous-use versus reference-use designation · review clock management · validation records · full revision and version audit trail · training impact flags · integration with your document vault and Office tools

REGULATORY ANCHORS  Appendix B Criteria V and VI · NQA-1 Requirements 5 and 6 · Technical Specification 5.4 · RG 1.33 Appendix A (ANSI N18.7) · 10 CFR 50.155 · 10 CFR 50.59 · DOE O 422.1 / DOE-STD-1029

CONNECTS WITH  Change Control screens the revision; Design Basis Information holds the governing requirement; Training & Qualification receives the impact; Operational Readiness Reviews verifies approval before startup.

Procedure adherence findings do not start with the crew. They start with a procedure nobody realised had to change.

PROJECT DELIVERY ASSURANCE [PDA]

Design control, ITAAC evidence, commissioning and turnover — the execution layer for new build and modifications.

THE CHALLENGE

Every SMR and fusion company is a construction project wearing a company’s clothing. Design control under Appendix B Criterion III has to hold across thousands of design inputs, reviews and verifications on a design that is still maturing. For Part 52 licensees, hundreds of ITAAC each need documented, independently verifiable evidence before fuel load. Schedule is the dominant commercial risk, and evidence assembly is the hidden cost buried inside it.

WHY IT MATTERS NOW

  • ITAAC as a managed hierarchy, not a spreadsheet. Hundreds of acceptance criteria with independent evidence, approval and closure states, rolling up to closure notifications under 52.99 and the §103(g) finding that legally permits operation. This is a traceability problem software should own, and today almost nobody does.
  • Design control that holds under first-of-a-kind pressure. Design inputs, design review gates, verification records and interface control across a maturing design, with change traceability instead of a document set that quietly diverges from what is being built.
  • Turnover packages complete when you need them. System turnover from construction to startup to operations, with certified records, test results and open items assembled continuously rather than in a panic at the deadline.
  • Operating-plant modifications use the same engine. Engineering change packages, post-modification and post-maintenance testing and configuration updates, with 50.59 screening handled by Change Control and execution handled here.
  • Commissioning connects directly to authorization. Test performance and results feed Operational Readiness Reviews, so “are we ready to start” stops being a separate three-week exercise every time.
  • For fusion, the schedule argument wins the room. No ITAAC and no 50.59, but a first-of-a-kind machine with novel systems, aggressive milestones and no precedent to copy. Design review gate discipline and action traceability from design through first plasma is the difference between a slip you saw coming and one you did not.

 

LIFECYCLE

Initiation  ▸  Scoping  ▸  Design & review  ▸  Approval  ▸  Implementation  ▸  Testing  ▸  Turnover  ▸  Close-out

CAPABILITIES  Project and modification hierarchy · design input and verification records · ITAAC register with evidence and closure states · design review gate management · punch list and open item tracking · turnover package assembly · integration with Microsoft Project and your scheduling tools · contractor and supplier linkage

REGULATORY ANCHORS  Appendix B Criteria III and XI · NQA-1 Requirements 3 and 11 · 10 CFR 52.99 and §103(g) · 10 CFR 50.59 interface · RG 1.68

CONNECTS WITH  Change Control grants permission to change; Operational Readiness Reviews grants authorization to operate; Supplier & Contractor Assurance and Transmittals & Vendor Data supply the certified records that make closure possible.

On a first-of-a-kind build, evidence you cannot produce is indistinguishable from work you did not do.

SSC DATA INTEGRATION [SDI]

Your equipment master, enriched with the safety classification that should travel with every record.

THE CHALLENGE

Your equipment data lives in SAP or Maximo and it should stay there. But in nuclear an asset is not a tag number and a description — it is a set of classification attributes that determine how every program must treat it. When that context does not travel, a condition report on a Q-List component gets handled the same way as one on a parking lot light.

WHY IT MATTERS NOW

  • Safety classification travels with every record. Q-List membership, safety-related versus augmented quality versus balance of plant, Maintenance Rule scope under 50.65, risk significance from the PRA, environmental qualification status under 50.49 and seismic category — surfaced into every application in the portfolio.
  • The Master Equipment List as a live configuration baseline. In most fleets the MEL is the authoritative baseline, and keeping it aligned with the licensing basis and the as-built plant is a permanent struggle. Reconciliation belongs in a tool, not in an annual spreadsheet exercise.
  • Automatic rigour instead of remembered rigour. A condition report, hazard analysis or modification package raised against a safety-related component inherits the correct classification, approvals and treatment at the moment it is created.
  • We do not replace your CMMS, and we do not want to. SAP and Maximo remain the systems of record. This consumes and enriches — which is also the reason your IT organization will approve it.
  • Coverage questions answered instantly. Which hazard analyses cover this equipment item? Which credited functions depend on it? Which procedures reference it? Which impairments have affected it this year? Each is one query rather than one project.
  • For fusion, the same job against different systems. Controlled equipment and BOM data usually lives in PLM — Windchill, Teamcenter, Arena — or a lighter CMMS. The integration pattern is identical; only the connector changes.

 

LIFECYCLE

Extract  ▸  Map  ▸  Classify & enrich  ▸  Publish  ▸  Reconcile  ▸  Maintain

CAPABILITIES  Connectors to SAP, Maximo and PLM platforms · classification attribute model · facility, system and unit hierarchy navigation · equipment-to-object linkage across every application · reconciliation and discrepancy reporting · graphical asset structure navigator

REGULATORY ANCHORS  Q-List and Appendix B scope · 10 CFR 50.65 (Maintenance Rule) · 10 CFR 50.49 (EQ) · 10 CFR 50.69 (RISC) · seismic category · Master Equipment List convention

CONNECTS WITH  Supplies classification to every application in the portfolio and receives classification decisions from Credited Controls & Safety Functions.

Safety classification is the most important attribute your equipment record carries. It should never be the one nobody can see.

SUPPLIER & CONTRACTOR ASSURANCE [SCA]

Approved Suppliers List, qualification scope, audit currency and Commercial Grade Dedication — the industry’s tightest bottleneck.

THE CHALLENGE

There are not enough NQA-1 suppliers to build the SMR fleet. Everyone is qualifying commercial vendors and dedicating their output, and Appendix B Criteria IV and VII require documented evaluation, qualification and periodic re-audit for every one of them. Supply chain quality is not a procurement inconvenience. It is the choke point of the entire industry, and it is where first-of-a-kind schedules go to die.

WHY IT MATTERS NOW

  • The Approved Suppliers List as a live control. Qualification scope, audit currency, expiry dates, conditional approvals and restrictions — with procurement blocked when the approved scope does not cover the item being bought.
  • Commercial Grade Dedication that holds up. Critical characteristics, verification method, acceptance records and dedication basis linked to the credited function the item actually supports. Dedication validity is documentation completeness, and this is where it is proved.
  • Part 21 flowdown in both directions. Defect reporting obligations flowed down through procurement documents, and inbound vendor notifications screened directly into your corrective action program.
  • Audit due dates that escalate before they lapse. Supplier audit frequency driven by risk and performance, NUPIC joint audit participation tracked, and scorecards that make renewal and removal decisions defensible rather than personal.
  • Counterfeit, fraudulent and suspect item defense. Documentation authenticity and traceability to the actual manufacturer, held as a provenance record at receipt — a sustained NRC and industry concern with very little tooling behind it.
  • Supplemental workforce oversight for outages. Hundreds or thousands of contractor personnel arriving at once, with training and qualification verification complete before anyone touches a job.
  • For fusion, the same problem without the infrastructure. Exotic magnets, large vacuum components and tritium-compatible systems from a supply base with no NUPIC, no ASL convention and no qualified pool. A ready-made qualification framework is the fastest maturity step available.

 

LIFECYCLE

Prequalification  ▸  Evaluation & audit  ▸  Approval & scope  ▸  Procurement control  ▸  Receipt & dedication  ▸  Performance  ▸  Re-audit

CAPABILITIES  ASL with scope and expiry control · risk-based audit scheduling and supplier scorecards · CGD workflow with critical characteristics · supplier corrective action requests · Part 21 flowdown and notification screening · contractor qualification verification · links to projects, changes and corrective actions

REGULATORY ANCHORS  Appendix B Criteria IV and VII · NQA-1 Requirements 4 and 7 · 10 CFR Part 21 · NUPIC · 10 CFR Part 26 interface · industry CFSI guidance

CONNECTS WITH  Audits and Assessments performs the supplier audits; Transmittals & Vendor Data collects the required documentation; Credited Controls & Safety Functions defines what dedication has to protect.

You cannot buy your way out of a supply chain that has not been qualified. You can only document your way through it.

TRAINING & QUALIFICATION [TQ]

Not whether they took the course. Whether they are qualified, right now, to be assigned this work.

THE CHALLENGE

Your learning management system knows who completed what. Every other program in your organization needs a different answer at the moment of assignment: is this person currently qualified to lead this audit, perform this cause analysis, enter this confined space, prepare this 50.59 evaluation or stand this watch? That is a qualification register question, and an LMS was never built to answer it.

WHY IT MATTERS NOW

  • Qualification as an authorization gate. Assignment is blocked or flagged when a required credential is missing, expired or out of scope — across audits, permits, cause analysis, 50.59 preparation and readiness reviews.
  • Currency clocks with forward visibility. Requalification cycles, continuing training, medical qualification, proficiency hours, drill participation and certification renewals, with a view of what expires during the next outage window — when discovering a gap is most expensive.
  • Training impact screening on every change. Modifications and procedure revisions routinely get implemented before affected personnel are retrained. This is a recognized weakness and a simple one to close.
  • The hard credentials nuclear actually runs on. RO and SRO licenses under Part 55 with 55.59 requalification, NQA-1 certified lead auditors, NDE Level I, II and III per SNT-TC-1A, ASME Section IX welder qualification, root cause analyst certification, fire brigade and emergency response organization position qualification.
  • One credential matrix, shared with organizational change. The same position-to-qualification model answers “who is allowed to do this job” and “which license-required positions just went vacant.” Built once, used by both.
  • It sits above your LMS, not in place of it. Course delivery, content, SCORM and exams stay where they are. This holds qualification state and answers the assignment question your LMS cannot.
  • For fusion, an entire qualification tier that does not exist yet. Magnetic field and implant screening, cryogen and oxygen deficiency, laser safety, RF, tritium worker, beryllium worker under 10 CFR 850, capacitor bank and stored energy, and vessel entry and remote handling operators. Build it before tritium introduction, not after.

 

LIFECYCLE

Requirement  ▸  Assignment  ▸  Delivery (your LMS)  ▸  Verification  ▸  Qualification granted  ▸  Currency  ▸  Requalification

CAPABILITIES  Position-to-credential matrix · qualification register with scope and expiry · LMS completion ingestion · currency dashboards and expiry forecasting · training plan creation and progress tracking · follow-up action items · specific and aggregated reporting

REGULATORY ANCHORS  Appendix B Criterion II · NQA-1 Requirement 2 · 10 CFR 50.120 (SAT) · 10 CFR Part 55 and 55.59 · 10 CFR 19.12 · 10 CFR Part 26 · Part 73 Appendix B · INPO accreditation · DOE O 426.2 · 10 CFR 850

CONNECTS WITH  Shares the credential matrix with Organizational Change Control and gates assignment in Audits and Assessments, Licensing & Regulatory, the Corrective Action Program and Operational Readiness Reviews.

A completed course is a record. A current qualification is a control.

TRANSMITTALS & VENDOR DATA [TX]

What you owed, what arrived, what went out — and who was authorized to receive it.

THE CHALLENGE

Every purchase order carries a list of documents the supplier owes: drawings, calculations, Certificates of Conformance, Certified Material Test Reports, weld and NDE records, test reports and vendor manuals. Those are quality assurance records under Criterion XVII, many with lifetime retention, and they are the evidence base for your environmental qualification and seismic files. Items arrive and get installed. The records show up months later, or never.

WHY IT MATTERS NOW

  • Supplier Document Requirements List, tracked to completeness. Every deliverable owed against every purchase order, with a hold on acceptance until the package is complete. “Can we accept this item without its documentation?” becomes a controlled decision rather than a judgement call on the loading dock.
  • Outbound screening nobody else provides. Transferring nuclear technology is regulated under 10 CFR Part 810 and Part 110, plus EAR and potentially ITAR. Your SMR programme is courting international customers; your fusion supply chain is internationally distributed by necessity. The control point is the moment technical data leaves the building — which is exactly where this sits.
  • Information protection enforced at the gate. Safeguards Information under 73.21 and 73.22, proprietary information withheld under 2.390, and sensitive unclassified information each constrain who may receive what. Classification, recipient authorization and transmission method recorded on every transmittal — the record an inspector or auditor will ask for.
  • Document currency checked on the way out. Sending a vendor a superseded drawing is how configuration errors get manufactured into hardware, at cost, on the critical path.
  • Counterfeit and suspect item provenance. Authenticity verification and traceability to the actual manufacturer, held with the receipt record rather than reconstructed after a recall notice.
  • Turnover packages already assembled. The construction-to-operations handoff is a mass transmittal of certified records. If the register is complete, the package is complete — and readiness is not waiting on a filing cabinet.
  • For fusion, the records are the qualification. First-of-a-kind components from an unqualified supply base often cannot be inspected to confidence. Documentation completeness is the primary quality control you have.

 

LIFECYCLE

Requirement (SDRL)  ▸  Outbound screening  ▸  Transmit  ▸  Receive  ▸  Completeness & authenticity  ▸  Acceptance  ▸  Retention

CAPABILITIES  SDRL register per purchase order · inbound and outbound transmittal records with full provenance · export control and information classification screening gates · recipient authorization checks · CMTR and Certificate of Conformance tracking · retention classification · turnover package assembly · EPC platform integration

REGULATORY ANCHORS  Appendix B Criteria IV, VII and XVII · NQA-1 Requirements 4, 7 and 17 · 10 CFR Part 21 · 10 CFR Part 810 / Part 110 · 10 CFR 73.21 and 73.22 · 10 CFR 2.390 · 10 CFR 50.49

CONNECTS WITH  Supplier & Contractor Assurance defines who may supply; Project Delivery Assurance consumes the turnover records; Licensing & Regulatory receives regulator correspondence and the commitments extracted from it.

An unqualified supplier and a supplier whose paperwork never arrived look identical in an audit.

WHERE ORGANIZATIONS START

Nobody deploys twenty-one applications at once. Three adoption paths account for almost every FACILEX® ATOMIC programme, and each one delivers a defensible capability inside a single quarter.

Operating plant

Start with the Corrective Action Program and Action Item Management, then Change Control. Those three carry the highest transaction volume and the greatest inspection exposure in the plant. Audits and Assessments and Operating Experience follow naturally, because both feed the CAP you have just strengthened. Bypass & Impairment Control is usually the first capability that operations staff ask for once they see the register.

New build and pre-operational

Start with Project Delivery Assurance and Operational Readiness Reviews — ITAAC evidence and closure is the schedule risk that dominates every Part 52 programme, and readiness authorization is what it feeds. Design Basis Information and Transmittals & Vendor Data follow immediately, because the certified records arriving from your supply chain this year are the evidence base for everything afterwards. Supplier & Contractor Assurance is often first in practice, since qualification is the constraint.

Fusion and DOE-affiliated facilities

Start with Hazard & Safety Case and Operational Readiness Reviews. The DOE framework already specifies both — HAZOP, What-If and FMEA methods behind the Documented Safety Analysis, and Order 425.1 with DOE-STD-3006 for readiness verification — so you are implementing a required process rather than importing a foreign one. Procedure Management and Training & Qualification follow as the organization crosses from research practice into controlled operations, which is the transition every fusion company is making right now. Build them before tritium introduction, not after.

Whichever path you take, the applications you deploy later inherit the classifications, obligations and evidence the earlier ones already hold. The suite gets more valuable with each addition — which is the opposite of how a shelf of point tools behaves.

Questions? We have answers.