Power
Plant engineers and outage managers keep boiler, HRSG, and high energy piping condition on one record, so the run or repair call gets made before the window opens.
Where it runs
A unit's UT grids, its fitness-for-service verdict, and its outage closeout stay in custody together.
Boilers · HRSG · headers · drums · high energy piping
Between outages
Every reading, verdict, and signature lands on the same unit and component identity, so nothing waits for the next binder review.
02 layers · scroll to stack
intelliINSPECT runs in-service inspections on drums, headers, and casings to National Board Inspection Code scope, captured offline in the boiler house and signed at the point of work.
intelliNDT holds UT grids on waterwalls, hot reheat welds, and Grade 91 seams, computing corrosion rate and remaining life for ASME B31.1 covered piping programs.
intelliINTEGRITY screens headers and drums to API 579 fitness for service, so every component decision carries its inputs, its math, and its approver.
intelliPROJECTS carries planned outages from readiness through scope freeze, execution, and closeout, with every gate decision logged against the unit.
One panel, one thread
A waterwall panel carries its history from the penthouse to the audit.
One panel, one thread
An inspector shoots a UT grid across the panel inside the boiler enclosure, no signal, and the readings sync with photos, location, and signature when the crew surfaces.
intelliNDT recomputes wall loss against prior outages, intelliINTEGRITY flags the panel for API 579 screening, and the repair lands in intelliPROJECTS scope before the freeze, not in extra days after it.
When the authorized inspector asks, the panel history exports as one query, every reading, decision, and sign-off in place, the same record a NERC reliability review draws from.
How it runs
Runs NBIC and ASME boiler and pressure part inspections with user, timestamp, and signature on every entry.
intelliNDTTies UT grids on waterwalls, headers, and Grade 91 welds to ASME B31.1 covered piping programs.
intelliINTEGRITYScreens headers and drums to API 579 fitness for service with inputs, math, and approver on the record.
intelliPROJTURNHolds outage scope from readiness gates to closeout on the same record the inspection data lives on.
Evaluation path
Power · next step
Bring one unit and one outage scope and we will walk the record from readiness to closeout.
Answers
Yes. Drum, header, tube, and casing inspections are captured as structured records with user, timestamp, and signature against the National Board Inspection Code and the ASME Boiler and Pressure Vessel Code. intelliSPEC organizes the workflow and audit trail rather than certifying compliance on your behalf.
HRSG modules are mapped as inspectable components, so tube panel UT readings, FAC susceptible circuits, and attemperator checks accumulate on each harp and header across combined cycle outages. Corrosion rates and remaining life recompute through intelliNDT as each new grid lands.
Yes. Main steam, hot reheat, and feedwater lines run as ASME B31.1 covered piping programs, with hanger walkdowns, weld examinations, and creep damage findings held to each specific weld through intelliNDT and intelliINTEGRITY.
Plants run planned outages in intelliPROJECTS, which holds scope, readiness gates, daily execution, and closeout evidence on the same record the inspection data lives on. Discovered work flows straight into scope instead of into a spreadsheet.
Yes. Water tube boiler inspections map to EN 12952 and shell boiler work to EN 12953 alongside NBIC and ASME, so a fleet with units on both sides of the Atlantic runs one standard and one audit trail.
Inspection, NDE, corrective action, and outage closeout records are held per unit with user, timestamp, and signature, and export as one query when a jurisdictional inspector or NERC reliability review asks. intelliSPEC organizes the evidence rather than certifying compliance on your behalf.
Yes. Inspectors capture forms, UT readings, photos, and signatures with no signal in the penthouse, drum, or enclosure, and everything syncs when the crew is back in coverage. Offline capture is core platform behavior, not a degraded mode.
