Video summary

Webinar Series Inspector - Risk Based Inspection (RBI) Analysis : Introduction

Main summary

Key takeaways

Business

Business-focused summary (RBI / Risk-Based Inspection webinar)

The webinar explains how companies should plan and execute Risk-Based Inspection (RBI) using standards such as API 580/581 (RBI methodology) and the newer API 580 (2016) updates. It emphasizes how to:

  • Prioritize inspection scope
  • Reduce risk
  • Improve decision quality using better inputs (e.g., data quality, corrosion/defect assessment, consequence modeling, and inspection effectiveness)

Core ideas / logic used in RBI

  • Risk = Probability of failure (PoF) × Consequence of failure (CoF)
    • The speaker frames risk as consequence + probability, where consequences depend on what can happen to people/environment/assets and operations.

RBI improves inspection planning by:

  • Focusing on high-risk equipment/components
  • Choosing inspection type/method and intervals based on risk
  • Reducing unnecessary inspections (cost) while targeting meaningful risk reduction

Frameworks, processes, and “playbooks” mentioned

API 580 / API 581 RBI (probability & consequence approach)

  • PoF assessment
    • Uses corrosion/defect-related probability methods.
  • Consequence assessment
    • Uses scenario outcomes (e.g., equipment rupture/leak/explosion impacts).

API 580 (2016) updates (key fundamental change)

  • A major update described as enabling determination of an “accepted risk level”
    • This relates to risk acceptance/risk criteria selection via a curve/table concept.

Assessment tiers / approaches (qualitative vs semiquantitative vs quantitative)

The webinar discusses tiered approaches:

  • Qualitative
    • Used when data is limited; relies more on judgment.
  • Semi-quantitative
    • A middle tier using structured scoring/levels.
  • Quantitative
    • Uses more exact modeling calculations, but requires better data.

Guidance implied: move up tiers as data quality improves so results align better with actual risk.

Inspection plan development

A typical flow described:

  • Inputs → screening/sizing of risk → inspection plan → actions
  • Actions include communication/operations/maintenance changes to reduce risk.

Concrete execution steps / actionable recommendations

  • Start with correct data collection, then build PoF/CoF:

    • Collect manufacturing/asset design information (equipment specifications)
    • Use inspection history
    • Use BPJS/accident records / incident evidence (as an example source of consequences/impact)
    • Include operational/environmental context (location, usage, operating conditions)

  • Corrosion assessment must be done before concluding failure drivers

    • The speaker warns against jumping directly to a “cause” without associating it to corrosion/defects.

  • Use tiered methods intentionally

    • If quantitative inputs are weak, use semi-quantitative/qualitative first, then refine with better data.

  • Tie RBI outputs to management action

    • After risk ranking/assessment, define actions such as:
      • Inspection strategy changes
      • Asset modifications / operational restrictions
      • Maintenance planning updates

  • Treat software as an enabler, not a substitute for data quality

    • Outputs depend heavily on inputs; software cannot compensate for poor data.

Key metrics / KPIs / targets (as stated or implied)

The subtitles provide limited clean numerical KPI targets, but the webinar includes the following themes and cost/risk indicators:

  • Risk reduction / inspection effectiveness (qualitative)

    • Goal is to reduce risk levels through appropriate tools/approaches and improved data for better accuracy and risk targeting.

  • Cost / margin framing

    • Claim: RBI can reduce inspection cost while ensuring risk control.
    • Subtitles mention potential cost reduction up to ~20% for certain cost elements.
    • For some “architecture/equipment,” inspection cost shares are mentioned as ~50–60% (wording is noisy, but presented as cost-impact ranges).

  • Data-driven frequency change

    • A key implied KPI is inspection scope optimized to risk:
      • increase coverage for high-risk items
      • decrease coverage where risk is lower

  • Certification/training costs (compliance-related)

    • Brief mention of certification fee ranges (e.g., ~5–6 million and up to ~35 million in some contexts).
    • Exact mapping is unclear due to subtitle noise.

Example / case elements discussed

  • 2016 vs older editions

    • Contrasts older RBI calculation approaches with API 580 (2016) improvements, especially usability around risk acceptance and updated tables/curves.

  • Industry context examples

    • Equipment categories referenced include items like compressors and other process equipment.
    • Corrosion/defect mechanisms are treated as equipment-specific.

  • Data availability determines output

    • When data are missing/outdated, results can diverge from expectations—so the plan must adjust (e.g., tier selection and data refinement).

Question/answer topics (execution-relevant clarifications)

  • How to choose qualitative vs quantitative

    • Quantitative is preferred when data quality supports it; otherwise start with semi/qualitative and refine.

  • Where RBI tools/software help

    • Software can integrate PoF/CoF calculations, but results still depend on correct input data and correct defect/corrosion association.

  • How to use operational history

    • Past inspection history and field evidence should influence the assessment; don’t rely only on software defaults/specs.

Presenters / sources (as mentioned)

People

  • Ice Farid Adi Prasetyo (main speaker)
  • Mas Faris, Mas Indra Bagas, Dian Mayasari (participants/questions)
  • Mas Heri, Mak (mentioned around certification discussion)
  • Mas Wisnu (participant mentioning finding verification/contact)
  • Other referenced participants in fragments/closing lines: Yudistira, Rizki, Amin, Hasyim, Rudi, Faisal Ardi, Engking Asben, Asen, Haryoso, Rian

Standards/sources cited

  • API 580 (RBI methodology) including API 580 (2016) updates
  • API 581 (probability/consequence-related methodology mentioned)
  • GPS appears (likely for location-related inputs), though details are unclear due to subtitle quality.

Original video