Safety & Assurance Case · Energy edition
Make the argument.
Keep the evidence.
Review the change.
Bring operating context, safety claims, shared barriers and review decisions into a connected energy assurance case.
For competent teams preparing and reviewing cases. Software does not certify compliance or authorise operations.
From claim to substantiation
Transfer risks are controlled within the operating envelope
Prevention, detection and response depend on demonstrable control performance.
Proof tests · inspections · competence · change reviews
Fictional illustration · unapprovedA defensible process starts with traceability
Keep the reasoning close to the records.
Scope before conclusions
Record facility boundaries, lifecycle stage, operating limits, hazards, requirements, assumptions and risk-reduction reasoning.
Claims with evidence
Build linked claims, explain supporting arguments and retain contradictions, limitations and challenge dispositions.
Shared barriers
Maintain common barrier identities, owners, performance standards and verification dates. See the cases that depend on each barrier.
Independent decisions
Separate contributors from the assigned reviewer. Server checks protect the review sequence and reject conflicting revisions.
Controlled issues
Retain the reviewed case, dependency snapshots and evidence manifest separately from subsequent draft work. Export JSON and printable reports.
Changes remain visible
Changed source assessments, degraded barriers and overdue verification create review gaps. They do not silently rewrite an issued case.
Northbank Energy · fictional demonstration
What happens when the isolation barrier changes?
A fuel-transfer case relies on isolation, reviewed operating arrangements and competent people. Explore how the same case needs reassessment when its supporting evidence changes. All records below are fictional and no live workspace is modified.
Transfer isolation
Reference condition: available in this fictional scenario.
Isolation performs its safety function
Evidence must be current, applicable and sufficient for the defined operating envelope.
A retained reference
The reference issue remains unchanged. This illustration is not an approved engineering case.
One suite · a deliberate review process
Connect the case to the work that supports it.
Incident → Investigate → Pro
Use reviewed findings to challenge assumptions and identify failed barriers. Cite the specific source record and reviewed assessment revision.
Bowtie → shared barriers → Assure
Bring risk pathways, barrier standards and verification evidence into the argument. Shared barriers are explicitly registered and linked; existing bowtie records are not silently merged.
Change → Compliance → Audit
Reference the change decision, relevant requirements and audit findings. Any later update to a linked assessment prompts a review gap.
Observe → Competence
Use relevant observations and competence evidence to support or challenge claims. Upload authorised copies of standalone register evidence when required; permissions remain separate.
Designed for energy assurance. Introduced with care.
The energy edition provides an original, configurable case structure. Applicable obligations differ between offshore installations, onshore process facilities, renewables and other operations. Your competent team establishes the requirements and decides whether the evidence is sufficient.
Is this an automatic safety assessment?
No. Completeness checks identify missing fields and changed dependencies. They do not evaluate engineering adequacy, calculate accident probability or determine acceptable risk.
Does an issued case replace regulatory acceptance?
No. Issued means the assigned independent reviewer has recorded a decision for that revision. Dutyholder responsibilities and any required external acceptance remain separate.
Can I keep the original files?
Yes. Protected attachments retain their original bytes and a SHA-256 fingerprint. Download originals separately; reports and JSON exports include an evidence manifest. The module does not scan attachments for malware.
How is access licensed?
Safety & Assurance Case is a separately allocated extension to an active Sentinel annual company licence. Current authoring and review access is restricted to company managers. Pricing, training and implementation scope are agreed by quotation.
What is available for other sectors and desktop?
Energy, Rail, Cyber, Defence, Nuclear and Healthcare are available as separately allocated cloud evaluation editions. Each needs sector-specific operational validation. Desktop case synchronisation is not included in these new editions.