Ready No asset loaded
Read-only view — no edits or save
📚 Libraries
Locationnot loaded
Chemicalnot loaded
Toxicnot loaded
Acidnot loaded
Other fluidsnot loaded
Materialsnot loaded
Damagenot loaded
GFF (generic failure frequency)not loaded
PoF Mappingnot loaded
Half remaining lifenot loaded
Susceptibilitynot loaded
Management Scorenot loaded
CoF & PoF rulesnot loaded
Risk matrixnot loaded
Area Affectednot loaded
Planningnot loaded
Inspection Methodnot loaded
Ready

Data library
Data library is read-only — changed in Fulcrum

Change the data library in Fulcrum. This copy is read-only. RBI uses the library loaded with the vessel.

M0.2 — Chemical

API RP 581 Table 4.2M (metric). MolWt kg/kmol, LiquidDensity kg/m³, BoilPt_C and AIT in °C. Ideal-gas Cp notes 1–3 use T in K. Name is a typical example for the Fluid code (e.g. C6–C8 → Hexane). Used in M2 Chemistry and M3 release/consequence.

M0.3 — Toxic

Edit the table below. Properties are metric: MolWt kg/kmol, LiquidDensity kg/m³, BoilPt_C and AIT in °C. Once loaded in Engine 3 (Load Rules JSON or Toxic in Libraries), toxic fluid properties are used for Industry screening toxic release and consequence analysis.

M0.4 — Acid

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Acid in Libraries), acid fluid properties are used for Industry screening acid release and consequence analysis.

M0.5 — Materials

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Materials in Libraries), material specs and allowable stress are used in M5 Damage (min wall calculations) and material selection.

M0.6 — Damage

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Damage in Libraries), the mechanism library drives M5 Damage screening, cracking/other mechanism lists, and inspection/definition lookups.

M0.7 — Risk consequences

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Risk consequences in Libraries), consequence dimensions and score options are used in M6 Risk for CoF scoring and probability bands.

M0.8 — Risk Matrix

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Risk Matrix in Libraries), the matrix drives M6 Risk (PoF × CoF, risk level, planning). Cell highlight colors are applied in M6 when you leave M0 (switch to M1–M9) or use Save combined CSV (full export), which pushes this snapshot into REF so the live matrix can read cells and colors.

M0.9 — Area Affected

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Area Affected in Libraries), area bands are used in M6 Risk for consequence and release area mapping.

M0.10 — GFF (generic failure frequency)

Edit the table below. Once loaded in Engine 3, GFF (generic failure frequency) (Table 3.1, failures/yr) is used with calculated Df,thin in M3 min-wall GFF method and M6 PoF (GFF (generic failure frequency) × FMS (management systems factor) × Df,thin (damage factor)).

M0.11 — PoF Mapping

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or PoF Mapping in Libraries), numeric bands map working PoF (GFF (generic failure frequency) × FMS (management systems factor) × DF (damage factor)) to a 1–5 score in M6 Risk; the M6 PoF tab shows the GFF (generic failure frequency)/FMS (management systems factor)/DF (damage factor) breakdown and per-row mapped bands for min-wall calcs.

M0.12 — PoF Matrix score

Edit the table below. CoF matrix column letters (A–E) and the M6 Driving consequence dropdown labels (1–5 with comment text) are taken from this table once loaded in Engine 3 or from M0 RBI Data.

M0.13 — Half remaining life

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Half remaining life in Libraries), numeric bands use the same columns as PoF Mapping — min, max, score, and label. Enter min / max as half-life in years (same units as the M3 min-wall 1/2 life (yrs) result). Shorter half-life → higher PoF score (5 = most urgent). Default bands match built-in M3 tiers: <2 yr→5, 2–6→4, 6–10→3, >10–16→2, >16 yr→1.

M0.14 — Cracking
Susceptibility (1–5)

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Susceptibility in Libraries), these options appear in M5 Damage → Cracking → Susceptibility (1–5).

M0.15 — Management Questionnaire

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Management Score in Libraries), the questionnaire and FMS (management systems factor) are used with M3 GFF (generic failure frequency) and in M6 PoF (GFF (generic failure frequency) × FMS (management systems factor) × DF (damage factor)).

M0.16 — Planning

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Planning in Libraries), risk-cell-to-frequency mapping is used in M7 Planning to suggest inspection intervals from risk score.

M0.17 — Inspection Method

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Inspection Method in Libraries), inspection methods are used in M7 Planning for method selection and inspection plan details.

Module 1 — Asset register
How to use Module 1 — click to open

Record the vessel identity, location, design and operating data used by later modules (M2–M7). Complete the sections in order. Save with the global save control when you finish.

  1. M1.1 Location — Choose Site, Unit / Area, and Chemistry system. Set whether the item is in a bunded area.
  2. M1.2 Basic Info — Enter tag, name, description, date vessel new, insulation, and heat treatment. Tag and name appear in the header and report.
  3. M1.3 Design Conditions — Enter design temperature, design pressure (gauge), shell nominal thickness, and corrosion allowance (from the vessel design / nameplate data).
  4. M1.4 Operating Conditions — Enter typical operating temperature and pressure (gauge), liquid level (%), and total vessel volume (L). Volume and level feed release / inventory calculations in M3.
  5. M1.5 Component design — Add shell, heads, nozzles, and other components. Materials come from the M0 Materials library. These rows feed M5 min-wall and damage calculations.

Use the refresh icon on the module title to re-apply M0 libraries after Location or Materials changes in M0. Pressures in M1 are gauge; later release maths convert to absolute where required.

M1.1 — Location Choose Site first, then Unit / Area, then Chemistry system. A value with no match is left blank.
M1.2 — Basic Info

Identify the vessel. Date vessel new is used as the age start date in damage calculations (M5). Insulation and heat treatment support damage screening.

M1.3 — Design Conditions

Enter values from the design code / nameplate (e.g. ASME VIII). Pressure is gauge (MPa). These values are shown or inherited in M2–M7.

M1.4 — Operating Conditions

Typical operating values for release scenarios. Pressure is gauge. Vessel % liquid level and Total volume support inventory and time-to-empty in M3.

M1.5 — Component design

Register vessel components. Material options come from the M0 Materials library. Length (m) is the component length in metres (for example shell cylinder length). Use the delete icon to remove a row, + on a row to insert below it, or + Add row at the end.

Open Volume calculator — estimate vessel volume from shell, heads, and nozzles (opens in a new tab).

Module 2 — Level 1 CoF analysis

How to use Module 2 — click to open

Build the Level 1 consequence-of-failure analysis: chemistry mixtures, release source terms, detection/isolation, screening areas, aggregation, and owner CoF.

  1. M2.1 Chemistry — Composition and representative fluid come from the chemistry system. Class and mixture properties are filled from the M0 library row for each chemical.
  2. M2.2 Fluid & conditions — Choose representative fluid (M0) and phase at release here. MW, density, and AIT come from the M0 chemical row.
  3. M2.3 Holes & inventory — Review hole sizes and Wₙ from M3; set available inventory mass.
  4. M2.4 Detection / isolation — Choose detection and isolation classes; calculate source term (rateₙ / massₙ).
  5. M2.5–M2.8 Areas, aggregation, CoF, driving — Enter or pull consequence areas, aggregate models, set owner CoF ratings (Financial from your external calculator) and driving consequence.
  6. M2.9 Notes — Optional analysis notes.

Complete M1 first and run M3 Calculate All Holes so release rates and inventory can flow into M2.2–M2.4. Fields under M2.4 are numbered M2.41, M2.42…

⚠ Module 1 not completed — design data will not flow through.
M2.1 — Process chemistry and representative fluid

Composition

Chemistry system

Composition and representative fluid come from the chemistry system. Class is filled from which library the chemical belongs to.

# Chemical Class Mole % BoilPtmix (BoilPt_C) MolWtmix ρmix (LiquidDensity)
Average Mol % total: — — — —

Mixture properties & library

Mixture properties
BoilPtmix (BoilPt_C)
Primary — CSV column
—
MolWtmix
Secondary — CSV column
—
ρmix (LiquidDensity)
Tertiary — CSV column
—
Name: —
— MW
— NBP
— ρ
Load library…
Representative fluid properties (M0 table)
Fluid
Selected row
—
BoilPt_C
M0 chemical table
—
MolWt
M0 chemical table
—
LiquidDensity
M0 chemical table
—
AmbientState
M0 chemical table
—
M2.2 — Fluid & conditions (phase chosen here)
Level 1 uses representative-fluid properties — not process-simulator flash / EOS. AIT is blank when Table 4.2M lists N/A (water, steam, acids).
M2.3 — Holes, theoretical rate Wn, inventory
Hole d (mm) A (m²) Wn (kg/s) GFFn
Load vessel / calculate M3 to populate holes.
M2.4 — Detection / isolation → raten & massn (Tables 4.5–4.7)
Hole ldmax (min) raten (kg/s) massn (kg) Type
Click Calculate source term.
M2.5 — Level 1 consequence areas (representative fluid / screening)

Enter Level 1 screening areas (m²) per hole from representative-fluid tables / M4 Build Consequence Models. Leave blank = 0.

M4 Level 1 Eq 1.4 (flammable)
Cfflam
—
Hole CAflam,cmd CAflam,inj CAtox,inj CAnfnt,cmd CAnfnt,inj
M2.6 — Consequence Aggregation

https://cdxapps.epa.gov/olem-rmp-maintain/action/rmp-comp

https://www.epa.gov/cameo/aloha-software

https://www.arl.noaa.gov/hysplit/

https://www.epa.gov/scram/air-quality-dispersion-modeling-alternative-models

⚠ Module 3 (Release) not completed — release rates not available.
Release Data (read-only)

Consequence Type Selection

API 581 Fig. 4.3 Level 1 COF event tree — first branch
No ignition → Safe Dispersion; Ignition + liquid → Pool/Jet Fire; Ignition + gas → Jet Fire / Flash / VCE (AIT & early/late not auto-selected yet)

Maximum Consequence Areas

Area Affected (CSV) provides screening bands aligned with screening-style modelling; owner CoF ratings come from your owner criteria in Libraries. Columns: Type, Hole, Rate (kg/s), Area (m²), Distance (m), Continuous or Instant, Area band. All four hole sizes are shown: Small → Medium → Large → Rupture.
Select consequence type(s) above — areas calculate automatically (or click Build Consequence Models).
M2.7 — Consequence of Failure (CoF)
Loading consequence dimensions…
M2.8 — Driving consequence
Select the Owner consequence rating (labels from M0 PoF Matrix score; stored as ranks 1–5) and driving dimension (from CoF dimensions in Libraries). Used with PoF for the risk cell.
M2.9 — Notes

Module 3 — Release Rate Estimation

Inherited from M2 — Chemistry Name —
How to use Module 3 — click to open

Estimate release rates for the four standard hole sizes. Results feed M2 Level 1 CoF and downstream consequence work.

  1. M2.1 Representative fluid — Selected in Module 2, M2.1 (Process chemistry and representative fluid). Used by Calculate All Holes.
  2. M3.1 Release inputs — Set phase, pressure (from M1 gauge options), back pressure, temperature, Cd, and gas k if needed. Vessel volume comes from M1.
  3. M3.2 Results — Click Calculate All Holes to get Wₙ, mass, and continuous/instant classification.

M1 pressures are gauge; release maths use absolute where required. Save M3 after calculating so M2 can refresh rates.

⚠ Module 2 not completed — representative fluid not available.

Representative fluid is selected in Module 2, section M2.1 (Process chemistry and representative fluid).

M3.1 — Release Inputs
Orifice flow release model
M1 values are gauge. Release rates use absolute pressure: Ps = gauge + 0.101325 MPa (ref. atm). Operating is typical for scenarios.
Downstream / ambient absolute pressure (default 1 atm). §4.3 Patm.
Set in Module 1 (Asset register). Used here for full contents mass and time-to-empty.
M3.2 — Results — 4 Hole Sizes
Dispersion:
PCC-3: time-to-empty (<2 min=Inst, 2–10 min=Trans, ≥10 min=Cont). Continuous / Instant (API 581 Fig. 4.2 style): hole ≤6.25 mm=Continuous; else 4536 kg in ≤180 s OR mass>4536 kg emptied in ≤180 s=Instant.
Enter inputs and click Calculate

Module 4 — Historic Review
How to use Module 4 — click to open

Record historic review reports and free-form vessel history for this asset.

  1. M4.1 Historic review reports — Add rows (date, tag, description, URL). Use Open to launch links. Save M4 when done.
  2. M4.2 Notes — Short historic-review notes.
  3. M4.3 History — Rich-text history log (font, links, images).

This module does not replace M2 consequence aggregation; it stores inspection / review history for the report.

Register historic review reports and link each row to an external URL (inspection report, PDF, sharepoint link, etc.). Columns: Date, Tag, Description, and URL.

M4.1 — Historic review reports
Date Tag Description URL (link) Open

Use a full URL (https://…). The Open column launches the link in a new tab. Drag the right edge of a column header to adjust width.

M4.2 — Notes
M4.3 — History
Ready
Choose font and size like Word; use Link and Image, or drag an image onto the field; double-click an image to resize.
Notes

Module 5 — Damage mechanism

from M1 Shell Nominal Thickness (mm) — from M1 Design Pressure (MPa) GAUGE — from M1 Shell Corrosion Allowance (mm) —
How to use Module 5 — click to open

Screen and analyse damage mechanisms: equipment GFF baseline, thinning (min wall), cracking, other damage, and related notes.

  1. M5.1 Equipment GFF — Select the M0 GFF row and confirm management / FMS baseline.
  2. M5.2 Thinning — Component min-wall and thinning DF steps (materials and sizes from M1).
  3. Further M5 sections — Complete cracking, other mechanisms, inspections, and notes as applicable.
  4. Consequence models — Build / refresh consequence models where prompted so M6 can read areas.

Design pressure, nominal thickness, corrosion allowance, and date vessel new come from M1. Refresh after M0/M1 changes.

Module 6 — Risk Analysis
How to use Module 6 — click to open

Combine consequence and probability to place the asset on the risk matrix and support planning.

  1. M6.2 Maximum consequence areas — Review areas from M5 / Level 1 models.
  2. M6.3 CoF — Owner CoF is entered in Module 2; use the link to jump there if needed.
  3. M6.4 PoF — Confirm probability factors from damage / mapping libraries.
  4. M6.5 Risk position & matrix — Read the risk cell and recommended planning cues from the M0 risk matrix.

Complete M2 CoF and M5 damage first. Matrix colours and planning intervals come from M0.

M6.1 — Recorded ranking

Same record as Fulcrum. Last assessment date, recorded ranking, next review date, and assessment method stay here when the risk matrix is calculated.

M6.2 — Maximum Consequence Areas (from M5)
Complete M5 and Build Consequence Models to see areas here
M6.3 — Consequence of Failure (CoF)

Owner CoF dimension ratings and driving consequence are entered in Module 2 — Level 1 CoF analysis (M2.7 and M2.8). Risk position below still uses those values.

M6.4 — Probability of Failure (PoF)
Loading probability factors…
M6.5 — 🎯 Risk Position · 📊 Risk matrix

🎯 Risk Position

📊 Risk matrix

Owner matrix: CoF (A = low … E = high) × PoF (1 = lowest frequency … 5 = highest). Rows run 5 at top to 1 at bottom. Load via Libraries (Risk matrix).

📅 Risk Planning

—
—
—
—
—
—

Module 7 — Planning
How to use Module 7 — click to open

Turn risk results into an inspection plan and recommended interval.

  1. M7.1–M7.2 — Confirm basic info and design conditions inherited from M1 (read-only).
  2. M7.3 Inspection frequency — Review risk score and recommended interval from M6 / M0 planning.
  3. M7.4 Inspection plan — Rows from M5 appear automatically. Every cell is editable. Calculated figures are suggestions only until you enter or accept them — the plan is your data.

Use Print plan for the inspection test plan, or Print for the full module.

M7.1 — 📝 Basic Info
—
—
—
—
—
—
M7.2 — 🔧 Design Conditions
—
—
—
—
M7.3 — 📅 Inspection Frequency
Risk Planning
—
—
M7.4 — 📋 Inspection plan
Rows from M5 Damage appear automatically. Every cell is editable. Calculated figures (from M5, last + freq, M7.3 interval, recommended method) are suggestions only — grey placeholder text is not the plan until you type a value, double-click a cell, or click Use suggestions. Use Add row for a manual entry, or duplicate a row with the replicate icon. Drag column edges to resize. Dates are yyyy/mm/dd. freq (years) is interval in years, not days.
ID ⇅ Source ⇅ Calculation title ⇅ Component type ⇅ Damage Mechanism ⇅ Mode ⇅ PoF ⇅ Material ⇅ last inspected ⇅ next inspected ⇅ freq (years) ⇅ comment ⇅ Type ⇅ Inspection ⇅
Complete M5 Damage (Min wall, Cracking, Other) to see calculations

Module 8 — Report

How to use Module 8 — click to open

Produce the assessment as a technical paper. The paper includes every saved RBI item.

  1. Produce report — Click to write the paper from the saved modules: introduction, background, asset, chemistry, release, consequence, damage, risk, inspection plan, history, conclusions and the data library appendix.
  2. Review — Scroll the report content; use Print on the module title to print.
  3. Refresh — Re-apply M0 and reload after upstream edits, then Produce report again.

The report stays blank until you click Produce report. Ensure modules are saved first.

Click Produce report. The paper includes every saved RBI item.
Important Notice and Conditions of Use

1. Demonstration and Proof-of-Concept Website

OpenRBI is a free, user-operated demonstration and proof-of-concept website, including for training purposes. It has been developed to illustrate a transparent, traceable, and reviewable approach to Risk-Based Inspection (RBI) calculations and documentation.

OpenRBI provides a calculation and record-management workspace for screening, training, education, calculation support, evaluation, discussion, and the preparation of user-controlled RBI calculation records.

OpenRBI is not a production engineering system. It must not be used as the sole basis for engineering decisions, inspection planning, inspection interval extension, inspection deferral, fitness-for-service assessment, regulatory compliance decisions, maintenance deferral, risk acceptance, safety-critical decisions, plant operation, regulatory submissions, or authorisation for continued operation.

A complete, deployable RBI system would require extensive customisation to national, local, and customer requirements — including codes, standards, data libraries, workflows, approvals, and record-keeping — before it could be considered fit for operational or decision-making use in any practical sense.

2. No Engineering Approval or Certification

OpenRBI exports user-generated RBI calculation records only. It does not issue approved, certified, or regulator-accepted RBI assessments.

OpenRBI does not provide engineering certification, regulatory approval, statutory inspection approval, fitness-for-service approval, inspection interval approval, inspection deferral approval, plant safety assurance, or any other formal engineering approval.

Engineering approval by OpenRBI is not provided. Regulatory approval is not provided. No certification status is conferred by OpenRBI.

Access to or use of the website does not create a contract for professional engineering services, an engineer-client relationship, or any obligation to provide engineering advice, verification, certification, approval, maintenance, or ongoing support.

Any professional engineering service provided separately by an RPEQ engineer is a separate engagement and must be governed by its own written scope of services and formally issued deliverables.

3. User Responsibility and Competent Review

OpenRBI is intended for use only by suitably qualified and experienced personnel.

All calculations, inputs, assumptions, reference data, damage mechanisms, consequence assumptions, inspection history, inspection intervals, outputs, and conclusions must be independently checked by the user before use.

Any output must be reviewed by a competent engineer, Registered Professional Engineer of Queensland (RPEQ), certified inspector, owner-user representative, statutory authority, or other appropriately qualified person where required by applicable law, site rules, codes, standards, and jurisdictional requirements.

The user remains responsible for the final interpretation, acceptance, use, and implementation of any OpenRBI output.

4. Demonstration Data and Examples

Any pre-filled data, default values, sample records, demonstration examples, reference examples, and illustrative calculations are provided for demonstration purposes only.

They must not be treated as recommended values, site-specific values, approved values, or suitable values for any actual plant, equipment, facility, or inspection programme.

The user is responsible for replacing all example data with independently verified, site-specific information before any output is considered for further review.

5. Local Browser Processing and Data Control

OpenRBI operates within the user’s web browser. It does not require a login, user account, or registration.

User-selected files, equipment data, inspection data, calculation records, and exported reports are processed locally within the browser. The OpenRBI application does not upload, transmit, receive, store, or retain the contents of user-selected files or user-generated RBI calculation records.

OpenRBI does not use server-side storage, databases, external application programming interfaces, analytics scripts, third-party trackers, or data-upload services.

The website is not an archival storage service. Users remain responsible for retaining their own master copies of all source files, exported files, PDF reports, calculation records, and supporting documents.

6. Website Updates, Version Control and Compatibility

OpenRBI may be updated periodically. Updates may change the website layout, features, calculation methods, assumptions, default values, examples, documentation, file formats, or outputs.

Users are responsible for recording the OpenRBI version and date used for any retained calculation record. Users must independently verify outputs following any update.

No representation is made that files or outputs created using one version of OpenRBI will remain identical to, or fully compatible with, a later version.

7. Website Availability and Downtime

The OpenRBI website may be unavailable from time to time due to maintenance, updates, technical issues, or other downtime.

Continuous access is not guaranteed. The website, any feature, and the service itself may be changed, suspended, or discontinued at any time without notice.

Users must not rely on the website as the sole repository for any file, calculation record, or supporting document.

8. Exported PDF Reports and Calculation Records

Any PDF report or calculation record exported from OpenRBI is a user-generated calculation record.

It is not an engineering certificate, statutory inspection certificate, fitness-for-service approval, inspection deferral approval, regulatory compliance certificate, or plant safety assurance document.

Review status: requires competent review before use.

9. Standards, Codes and Recommended Practices

OpenRBI supports API 580 and industry screening-style RBI workflows but does not claim to replace competent engineering review, statutory inspection, professional judgement, site procedures, owner-user responsibility, or regulatory approval.

Any reference to standards, codes, or recommended practices is provided for calculation support and workflow alignment only. It is not a statement of compliance, certification, or approval.

10. Limitations of Responsibility

To the maximum extent permitted by law, no responsibility is accepted for loss arising from reliance on the website, its calculations, its outputs, user-generated files, inaccurate or incomplete input data, unverified assumptions, changes to calculations or file formats, incompatibility between versions, modification by others, loss of access, interruption of service, or discontinuation of the website.

Users are responsible for satisfying themselves that any calculation record, output, or file is suitable for their intended purpose and for obtaining any required independent professional review, statutory approval, or authorisation before use.

11. Acceptance

By accessing or using OpenRBI, the user acknowledges that the website is a free demonstration and proof-of-concept workspace only and accepts responsibility for independently reviewing and verifying any information, calculation, output, or file generated through its use.

Information — drag to move