Risk and reliability

Built on it

• Biomedical and medical device engineering — Device sheets for PartCraft: risk score before and after a control, design-history completeness and accelerated ageing time.
• Data center and mission-critical facilities — HVAC, energy and risk items for BimCraft with four calculation sheets: PUE, rack airflow and cooling units, UPS battery energy and redundancy availability.
• Facilities and maintenance engineering — Life-cycle, carbon, risk and live-data items for BimCraft with three calculation sheets: life-cycle cost, equipment availability and space planning.
• HAZOP and What-If — HAZOP on P&ID nodes, with the copilot.
• LOPA and SIL — Protection layers and SIL verification.
• Process safety engineering — Process-safety sheets for CadCraft, MarkupCraft, CivilCraft and BimCraft: LOPA arithmetic, safety-function PFDavg and band, release rates, relief area and plume concentration.
• Quality and metrology (inspection, CMM, GD&T) — Quality sheets for PartCraft, DetailCraft and CadCraft: process capability, control limits, positional tolerance with bonus, and a measurement uncertainty budget.
• Reliability — FMEA, fault trees, Weibull.
• Reliability and safety engineering — Reliability sheets for PartCraft, BimCraft and CadCraft: Weibull life, fault-tree and block-diagram probabilities and an FMEA risk priority number.
• Systems engineering (requirements, traceability) — Requirements bookkeeping sheets for PartCraft, BimCraft and CadCraft: verification coverage, a mass budget with margin and trace-link coverage.

Use it in your add-on

Name it in your manifest's needs. When someone adds your add-on, their account brings this engine too, and every edition loads it the first time your add-on needs it. Version ranges arrive with AL.13.

{
  "id": "com.example.my-addon",
  "apps": ["partcraft", "bimcraft"],
  "needs": ["engine.risk"]
}

Methods and standards

Fault trees are solved exactly by factoring, with minimal cut sets found by the MOCUS method; the failure mode table follows the IEC 60812 practice and MIL-STD-1629A criticality; Weibull fitting is by maximum likelihood and median rank regression; Markov models use uniformisation for the transient. Every result carries the name of its method, a reference and its limits. The risk matrix policy is the maker's, not the engine's.

Limits

Not mounted in any app, so nothing is reachable from a menu; the roadmap row (XE.8) is partial for that reason. Fault trees are coherent only: no NOT or XOR gates and no dynamic or sequence-dependent events; exact factoring is used up to 22 repeated events, then bounds only. Weibull is two-parameter with right-censored data only. Markov models are exponential only and dense, fine to a few hundred states. The default flag for severity 9 or higher is a house choice, not from a standard. Results are not a safety case or a regulatory file.