How NIQS works

Evidence discipline before engineering action.

NuclearIQ Solutions is a founder-led specialist in nuclear mechanical integrity, plant reliability and modernization. Each mandate starts with the owner decision, makes uncertainty visible and connects the selected technical route to implementation and verification.

Operating model

Principal-led, bounded and decision-focused.

NIQS works alongside owner, operator, OEM and engineering teams. Project leadership is applied inside the technical mandate, not sold as generic capacity.

Diagnose and Decide

Bounded diagnostic package with decision charter, evidence register, causal model and closure plan.

Engineer and Close

Defined engineering package with checked assessment, specification, acceptance criteria and residual actions.

Lead and Implement

Assigned technical workstream with integrated plan, hold points, supplier interfaces and closure dossier.

Specialist Teaming

Additional competence and checking are matched to the work. Formal roles remain with the responsible organisations.

NIQS six-step controlled engineering process: Substantiate, Diagnose, Confirm diagnosis, Engineer, Validate solution and Verify implementation, from brownfield evidence to controlled deliverables.

Controlled method

Substantiate. Diagnose. Confirm diagnosis. Engineer. Validate solution. Verify implementation.

Evidence comes before diagnosis; diagnosis is confirmed before the solution is engineered. Validation then checks that the solution answers the intended need, while verification checks that it was implemented correctly. The chain may be compressed for a small review or expanded for a multi-party implementation programme.

  1. 01Substantiate

    Establish the controlled evidence basis, rank sources and expose material gaps or conflicts.

  2. 02Diagnose

    Develop the credible causal mechanism within the defined asset and decision boundary.

  3. 03Confirm diagnosis

    Use discriminating evidence, tests or calculations to confirm the controlling mechanism.

  4. 04Engineer

    Develop the assessment, specification, corrective action or deployment package.

  5. 05Validate solution

    Demonstrate that the engineered solution addresses the intended plant need and operating context.

  6. 06Verify implementation

    Check conformity with requirements and acceptance criteria, then retain residual actions.

Assurance controls

Make accountability, evidence and acceptance visible.

The control level is proportionate to the mandate. NIQS does not imply that every engagement requires the same governance, checking or independent-review structure.

ControlWhat is made explicitDecision value
Mandate boundaryScope, exclusions, interfaces, formal roles and required owner inputsPrevents assumed responsibility and uncontrolled scope
Source hierarchyAuthoritative documents, records, data quality and conflictsShows what each conclusion rests on
Assumptions and gapsUnverified inputs, conservative values, sensitivity and closure actionsPrevents unsupported certainty
Checking basisPreparer, checker, specialist input and required independenceMatches assurance to technical risk
Decision controlsHold points, acceptance criteria, decision owner and change basisKeeps analysis connected to action
ClosureImplementation evidence, residual actions and final dispositionSeparates completed work from verified outcome

Confidentiality and security boundary

Non-sensitive first contact. Controlled evidence exchange later.

The public website and ordinary email are not routes for plant-sensitive technical data.

  • The public form accepts a generic issue summary only and no file attachments.
  • Classified, export-controlled and plant-sensitive information is explicitly excluded.
  • A controlled exchange route is agreed before technical files are transferred.
  • Public claims, project details and results require evidence, confidentiality clearance and release approval.
  • Client, partner and formal authority roles remain separated from NIQS delivery.

Public form delivery

The issue screen sends server-side to a fixed NIQS mailbox. The browser cannot select a recipient, sender or email template, and no delivery secret is exposed in public code.

Start with the owner decision

Describe what is known, what remains uncertain and what decision is blocked.

NIQS will return a Fit / No-Fit view and the appropriate delivery mode.