Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Location in Libraries), sites and systems appear in M1 Asset Register for location selection.

Choose which pipe fields appear in positions 1–8 for Module 1 and future exports (customer-specific layouts can replace defaults later). Use — blank — to skip a position. Alignment with M0 → Pipe spec: line list DN ↔ Pipe spec DN; line list Spec (class) ↔ Pipe spec Spec (class); line list Service ↔ Pipe spec Service (same fluid / service text). Schedule / wall ↔ Schedule; Material / spec ↔ Material lookup; Design P / Design T / Notes ↔ the same headings on Pipe spec; Line # is often mirrored as Pipe spec Title. Defaults: columns 1–4 = DN, Service, Spec (class), Line #; columns 5–8 blank.

One row per piping specification: Spec (class) matches line list Spec (class); DN matches line list DN (metric nominal for schedule lookup). The Service column matches line list Service (stored as tag in the saved JSON). Then schedule and nominal thickness (mm) from M0 → Pipe schedule; Title, piping code (piping code B31), material lookup (M0 → Materials), description, corrosion allowance (mm), design pressure (MPa), design temperature (°C), and notes.

Nominal wall thickness (mm) from sched.csv (embedded). DN and NPS are the left columns; null matches an empty cell in the CSV. Edit or import CSV to replace.

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Chemical in Libraries), fluid data is used in M2 Chemistry and release/consequence calculations.

Edit the table below. 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.

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.

Edit the table below. The first column, Show in app, controls which rows appear in material dropdowns (M3 Damage, Pipe spec material lookup, and related selectors): checked includes the row; unchecked hides it from new selections. Rows without show_in_app in saved data default to shown. Once loaded in Engine 3 (Load Rules JSON or Materials in Libraries), material specs and allowable stress are used in M3 Damage (min wall calculations) and material selection.

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

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or Risk Matrix in Libraries), the matrix is used in M6 Risk to map PoF and CoF to risk level and inspection planning.

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.

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.

Edit the table below. The first column, M3 Damage, controls which rows appear in Engine 3 → Damage → Generic failure: checked always includes the row; unchecked always excludes it. Rows without m3_damage in saved data keep the previous behavior (when any Pipe equipment row exists, only Pipe rows are listed; otherwise all rows). Once loaded in Engine 3 (Load Rules JSON or GFF in Libraries), generic failure frequencies are used in M3 Damage (Generic failure) and M6 PoF calculation (GFF × FMS × DF).

Edit the table below. Once loaded in Engine 3 (Load Rules JSON or PoF Mapping in Libraries), numeric bands map working PoF (GFF × FMS × DF) to a 1–5 score in M6 Risk and in the M6 PoF-calculated column.

Same band style as CoF / PoF scoring: 1 = Low (longest half-life) through 5 = High (shortest half-life). Enter Min and Max half-life in years for each PoF row (min inclusive, max exclusive; leave max blank for open-ended). M3 Damage → PoF score (from ½ life) uses this table after M0 is saved.

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

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

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.

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.