Skip to main content
Compliance

Compliance Management

Reliatic builds compliance into the asset integrity workflow—not on top of it. Every risk assessment, inspection, mitigation, and decision generates an immutable compliance record with full audit trail. Regulatory review packages are generated from live platform data, not manually assembled.

Supported Standards

Platform workflows are aligned with the following regulatory and industry standards. Compliance tracking is standards-aware—due dates, documentation requirements, and risk thresholds are configurable per standard.

API 581

Risk-Based Inspection Methodology

Quantitative RBI methodology for pressure-containing equipment. Reliatic implements the Annex 2A thinning damage factor model and generates inspection plans with traceable PoF × CoF calculations.

API 580

RBI Base Resource Document

Foundational principles for RBI program development including program scope, data requirements, and risk tolerance criteria. Used to validate program completeness.

API 510

Pressure Vessel Inspection Code

In-service inspection, rating, repair, and alteration of pressure vessels. Reliatic tracks inspection intervals, wall thickness measurements, and remaining life calculations per API 510.

API 570

Piping Inspection Code

In-service inspection, repair, alteration, and rerating of in-service piping systems. CML (Corrosion Monitoring Location) management and corrosion rate trending.

ASME B31.3

Process Piping

Design, materials, fabrication, assembly, erection, examination, and testing of process piping. Minimum required wall thickness (t_min) calculations and fitness-for-service assessments.

ISO 31000

Risk Management Framework

Principles and guidelines on risk management. Provides the governance framework that Reliatic's Reliability-to-Action Loop is built around. See ISO 31000 documentation for integration details.

OSHA PSM

Process Safety Management

29 CFR 1910.119 compliance. Reliatic supports PHA/HazOp action tracking, mechanical integrity documentation, and incident investigation records required under PSM.

The Compliance Evidence Chain

Each asset maintains a complete, ordered evidence chain from initial risk assessment through verified resolution. This chain is the compliance record—it can be exported as an audit package at any time without manual preparation.

01
Risk Assessment

Quantitative or qualitative risk assessment on the asset. Records: methodology, inputs, calculated score, date, responsible engineer.

02
Inspection Planning

Inspection plan generated from risk score. Records: recommended interval, inspection type, NDE method, coverage percentage.

03
Inspection Execution

Field inspection with NDE measurements. Records: inspector name, date, findings, thickness measurements, test reports, photo attachments.

04
Finding Classification

Each finding classified by severity. Records: finding type, severity, location, recommended action, review deadline.

05
Mitigation / Acceptance

Either a Mitigation Action (with owner, deadline, verification criteria) or a Risk Acceptance (with executive justification, approver, expiry). Both are immutable records.

06
Verification

Confirmation that the mitigation was effective. Records: verification method, result, re-assessed risk score, sign-off by qualified engineer.

Chain immutability: All records in the evidence chain are written to a cryptographically chained audit log. Records cannot be edited or deleted after creation. Corrections must be made via new records with explicit amendment justification.

Overdue & Deviation Tracking

Compliance status is calculated continuously, not at month-end. Every asset and inspection has a compliance state that changes in real time as deadlines approach and pass.

Compliant

All inspections are current, all risk assessments are within the review window, and no open risk events exist above threshold.

Due Soon

An inspection or review is within the configurable advance-warning window (default: 30 days). Notification sent to responsible engineer.

Overdue

An inspection or review has passed its due date without completion. A compliance deviation is automatically recorded. Escalation begins.

Locked

An unresolved risk event above the governance threshold. Operational workflows blocked until a governed artifact is created.

Audit Package Generation

Generate a structured audit package for any asset or facility at any point in time. The package pulls live data from the platform—no manual document assembly required.

Audit package contents
audit_package/
├── 01_asset_register.pdf
│   └── All assets with criticality, last inspection date, risk score
├── 02_risk_assessments.pdf
│   └── RBI calculations with input data and methodology reference
├── 03_inspection_history.pdf
│   └── All inspection records with NDE results and inspector sign-off
├── 04_risk_events.pdf
│   └── Open and closed risk events with resolution records
├── 05_mitigation_log.pdf
│   └── All mitigation actions with owner, deadline, and verification
├── 06_acceptance_register.pdf
│   └── Risk acceptances with justification, approver, and expiry
└── 07_audit_log_extract.pdf
    └── Cryptographically verified event chain for selected period

Navigate to Reports → Audit Package to configure the scope (date range, asset set, standard) and generate. Packages are available as PDF or structured JSON.

Deviation Management

When a compliance requirement cannot be met on time, the platform creates a formal deviation record. Deviations are not the same as overdue items—they are governed exceptions with formal approval and time limits.

Condition
Inspection past due date
Record
Deviation automatically created with timestamp and reason code
Approval
Named approver must accept the deviation with written justification
Limit
Maximum deviation extension period is configurable per standard (default: 90 days)
Expiry
If deviation expires without resolution, escalation fires and compliance state moves to LOCKED
Compliance Management — Reliatic Documentation — Reliatic