Diagnose and Decide
Bounded diagnostic package with decision charter, evidence register, causal model and closure plan.
How NIQS works
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
NIQS works alongside owner, operator, OEM and engineering teams. Project leadership is applied inside the technical mandate, not sold as generic capacity.
Bounded diagnostic package with decision charter, evidence register, causal model and closure plan.
Defined engineering package with checked assessment, specification, acceptance criteria and residual actions.
Assigned technical workstream with integrated plan, hold points, supplier interfaces and closure dossier.
Additional competence and checking are matched to the work. Formal roles remain with the responsible organisations.
Controlled method
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.
Establish the controlled evidence basis, rank sources and expose material gaps or conflicts.
Develop the credible causal mechanism within the defined asset and decision boundary.
Use discriminating evidence, tests or calculations to confirm the controlling mechanism.
Develop the assessment, specification, corrective action or deployment package.
Demonstrate that the engineered solution addresses the intended plant need and operating context.
Check conformity with requirements and acceptance criteria, then retain residual actions.
Assurance controls
The control level is proportionate to the mandate. NIQS does not imply that every engagement requires the same governance, checking or independent-review structure.
| Control | What is made explicit | Decision value |
|---|---|---|
| Mandate boundary | Scope, exclusions, interfaces, formal roles and required owner inputs | Prevents assumed responsibility and uncontrolled scope |
| Source hierarchy | Authoritative documents, records, data quality and conflicts | Shows what each conclusion rests on |
| Assumptions and gaps | Unverified inputs, conservative values, sensitivity and closure actions | Prevents unsupported certainty |
| Checking basis | Preparer, checker, specialist input and required independence | Matches assurance to technical risk |
| Decision controls | Hold points, acceptance criteria, decision owner and change basis | Keeps analysis connected to action |
| Closure | Implementation evidence, residual actions and final disposition | Separates completed work from verified outcome |
Confidentiality and security boundary
The public website and ordinary email are not routes for plant-sensitive technical data.
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
NIQS will return a Fit / No-Fit view and the appropriate delivery mode.