Selected experience / Claim-controlled

Experience shown with its role and boundary intact.

NIQS is a young company. The evidence below is Benjamin Regener's professional experience before NIQS, not NIQS corporate project history. Each example states the owner situation, technical contribution and result enabled without disclosing protected details.

Evidence policy

Specific enough to test. Bounded enough to trust.

Client identities, plant identifiers, protected drawings and unreleased metrics are omitted. NIQS will not imply corporate delivery, formal authority or regulatory approval that belongs to another organisation.

Evidence class	How it is labelled	What it may support	What it does not imply
Founder experience	Founder experience before NIQS	Relevant technical judgment, leadership and problem-solving experience	NIQS corporate project history
NIQS mandate	NIQS delivery with stated scope and status	Company work inside the contracted boundary	Work outside that boundary or unreleased client outcomes
Partner input	Named specialist or partner role	Capability available under the stated teaming arrangement	NIQS ownership of the partner's accreditation or authority

Representative founder experience

Three problem patterns relevant to NIQS mandates.

These examples are deliberately anonymised and contain no client testimonial, confidential metric or unsupported attribution.

Founder experience before NIQS

First-of-a-kind repair route for BWR jet-pump riser damage

Owner situation: Damage required an unprecedented repair route inside restricted geometry.
Technical complication: Nuclear quality requirements, difficult interfaces and no established precedent.
Benjamin's contribution: Mechanical lead coordinating assessment, repair concept, suppliers and interfaces; engineered an extensive test programme incorporating first-of-a-kind sensing systems.

Enabled an engineered repair basis and executable closure route.

Founder experience before NIQS

Fracture-mechanics finding affecting restart readiness

Owner situation: An integrity finding had to be resolved against a restart decision.
Technical complication: Time-critical decision with incomplete and cross-disciplinary evidence.
Benjamin's contribution: Technical lead integrating inspection evidence, loads, fracture assessment and reviewer interfaces.

Enabled a defensible restart decision basis and defined follow-up actions.

Founder experience before NIQS

Nuclear deployment routes for robotics and advanced manufacturing

Owner situation: Promising technologies needed a credible nuclear use case and acceptance path.
Technical complication: Capability claims had to be translated into bounded requirements, tests and evidence.
Benjamin's contribution: Programme and innovation lead defining use cases, requirements, tests and decision gates.

Enabled staged trials, qualification pathways and owner decision gates.

What NIQS makes visible

The decision chain, not a logo wall.

When a mandate can be discussed publicly, NIQS structures evidence around the actual owner question and work product.

Owner situationSymptom, consequence and blocked decision.

Technical mechanismWhat was known, inferred, tested and verified.

ContributionExact NIQS, founder, client and specialist roles.

Work productDecision basis, calculation, specification, test, implementation or verification record.

BoundaryAssumptions, uncertainties, formal roles and residual actions.

Discuss the fit

Have a similar problem pattern?

Use the confidential issue screen to describe the asset, symptom, decision and timing without sending sensitive technical data.

Detailed evidence can be disclosed later through a contractually controlled route.

Discuss a critical challenge Review services