ASSUREIQ · TURNAROUND ASSURANCE & CREDIBILITY
An independent verdict on whether a shutdown programme is credible, before the tools come out and again once the plant restarts.
Download the product overview (PDF)A major turnaround concentrates a year of cost, safety exposure and production risk into a fixed window, and it's planned by parties who each keep their own version of the plan. The contractor has a programme. The EPCM has a programme. The owner has a summary of both. Each is internally consistent, and none can be checked independently. By the time the gap between the plan and the plant is obvious, the scaffolding is up and the critical path is already moving.
A programme can be fully logic-linked and fully dated with no crew, no long-lead item and no confirmed access behind a single activity in it.
Where contractor and client numbers differ, reconciliation usually produces one blended figure, and the disagreement, which was the useful signal, disappears into it.
Post-turnaround analysis gets reconstructed from memory and spreadsheets weeks later, when nobody's account can be checked against anyone else's.
A deterministic CPM forward and backward pass with assumption-matched comparisons, so "is this network sound, and is it comparable to last run?" has a reproducible answer rather than an opinion.
Monte Carlo modelling of finish-date risk, with the seed, configuration and engine version logged against every run. The same inputs give the same distribution, and the run can be defended months later.
Crew, equipment and long-lead checks made against confirmed supply only. A plan resourced from optimistic availability is reported as unresourced rather than scored as ready.
CPI is produced only where real actual cost exists. Hours-based approximations are suppressed rather than dressed up as cost performance, because a number you can't trust shouldn't look like one you can.
Baseline, contractor-reported, engineer-validated and client-confirmed figures are held apart rather than merged. Where they disagree, "disputed" is a valid and visible end state.
Engineer and client sign off together in the field with evidence attached to the finding, so the verdict is agreed where the work is rather than asserted from a spreadsheet afterwards.
Any recommendation can be bypassed by an authorised user, and every bypass stores the original value, the replacement, the reason, the evidence and the forecast impact. Nothing changes silently.
Sites, plants and units are data rather than code, so a new plant or a multi-site operation is configuration rather than a rebuild.
Asset Management
Risk Management
Compliance Management
Governance & Assurance
Information Security Management
Isolation enforced at the database
AssureIQ runs standalone from imported schedule files, so a site can start with it alone and federate later. It deliberately doesn't run the shutdown: execution stays with the execution team and TurnSure. It also never certifies payment, quality release or restart authorisation.
TurnSure runs the turnaround. AssureIQ judges whether the programme behind it is credible. Keeping execution and verification separate is the point.
Confirmed crew availability and competency turn resource feasibility from a planning assumption into something checkable.
Plant hierarchy, asset criticality and equipment history ground the scope in the register rather than in the programme's own labels.
Readiness findings and post-turnaround variances join the operating picture, so a slipping shutdown is a signal rather than a surprise at restart.
Blocking findings appear ahead of any score, so what must be fixed before start is visible rather than buried inside an overall percentage.
An independent verdict on a programme prepared by other people, and a review afterwards that reconciles plan against what actually happened.
One shared record where their position is held distinctly rather than absorbed. A good programme can be demonstrated instead of asserted.
Reproducible runs with logged seeds and versions, evidence on every finding, and a complete override trail.
Bring your existing programme files. The schedule gets audited for network integrity, simulated for finish-date risk, and checked for resourcing against confirmed supply. You get a blocking-findings list and a verdict before committing to anything.
Warned, scored and recommended. Never blocked.
Your schedule files ingested and audited for logic integrity, compared against the prior baseline on matched assumptions.
Monte Carlo risk and resource feasibility run against confirmed crew, equipment and long-lead supply.
A joint engineer-and-client walkdown on a representative scope, with evidence captured against findings in the field.
ASSUREIQ · TURNAROUND ASSURANCE & CREDIBILITY