Maintenance Verification Demo Script

Step-by-step validation click path for the live use case.
Maintenance Verification Demo Script
Refreshed: 2026-07-19 09:42:51 UTC
SOURCE
bp Sphere validation click path
Scope: Step-by-step presenter guidance
POLICY
Narrative first · proof second · action third
EVIDENCE
Work orders, engineering specs, maintenance procedures, waivers, supplier claims
RECORDS
6 guided steps
ACTION
Launch Maintenance Verification
Validation Click Script
Maintenance Verification
Prove that work happened, was compliant, improved asset condition, and is financially valid for payment.
Audience
Maintenance supervisor, reliability engineer, operations leader, AP reviewer
Duration
5 minutes
Default role
operator
Live launch
Launch Maintenance Verification
Back To Use Case Introduction Launch Maintenance Verification Open Evidence & Context Explorer

Step-By-Step Click Script

1
Open the launch page
Click/ui/use-case-launch?case=maintenance_verification
What to say
Frame this as operational assurance, not just a work-order lookup.
What proof to land on
Business Problem and operator questions.
2
Review the proof categories
ClickStay on the launch page and point to Maintenance Supervisor Dossier and Reliability Impact
What to say
Show that the model covers asset context, work evidence, compliance, cost, and reliability.
What proof to land on
Asset context, parts and materials, procedure compliance, predictive insights.
3
Launch the live workspace
ClickLaunch Maintenance Verification
What to say
Move from the narrative into the verification surface.
What proof to land on
Maintenance decision workspace opens.
4
Show work completion proof
ClickUse Physical Verification and Digital Verification
What to say
Answer the direct question: how do we know the work was actually performed?
What proof to land on
Photos, inspections, SCADA / historian readings, and asset-condition delta.
5
Show compliance and cost validation
ClickOpen Procedure Compliance and Cost Breakdown
What to say
Prove the work followed the right process and the bill aligns to the work performed.
What proof to land on
Permit / checklist posture, planned vs actual cost, and parts validation.
6
Close on reliability and payment decision
ClickReturn to Reliability Impact and Operational Command Center
What to say
Connect the maintenance action to asset outcome, risk, and payment approval.
What proof to land on
MTBF / failure posture, high-risk cases, and payment-hold logic.

How To Use This In The Room

  • Start on the introduction page, not the live workspace.
  • Use the script to control the order: business problem, trust model, live proof, then action.
  • Spend most of the time on source-backed evidence rather than UI chrome.
  • If the room asks a skeptical question early, jump directly to the step that answers it.
Presenter note:
The recommendation is not the product. The product is the governed combination of context, evidence, policy, impact, human judgment, and memory.