Energy and utilities
Keep the planned outage, the notices and the restore evidence in one place
A planned interruption puts the operating decision, the customer notices, life-support records, the field work and the restore evidence into one work window.
The agreement and rules behind the work
Network operating approvals, National Energy Retail Rules and the field service agreement
Illustrative engagement
Planned network works involving life support customers
A Queensland distributor appoints a field services provider for regional works while remaining responsible for the customer notice, life support and restoration duties the Rules assign to it.
- Planning
- Work window, operating decision, delivery items and field prerequisites
- Notice
- Applicable life support records, required dates and evidence
- Delivery
- Mobilisation, work milestones, restoration and incident records
- Commercial
- Provider milestones, payment claims, variations and close-out
Product example
Nebula workspace
Project
Planned network works involving life support customers
Network operating approvals, National Energy Retail Rules and the field service agreement1 outage approval needs action.
ReviewWhere it stands
Outage plan is ready
4 of 5 readiness gates clearedWhat needs you
Your decision1 approval
Final switching authorityWho is involved
Delivery position
Current delivery positionDelivery items
Notice, field work and restorationLife support register check
VerifiedCustomer notices
VerifiedFinal switching approval
Decision dueThe engagement lifecycle
How Nebula carries this work through delivery
01
Form
Record the duties and delivery work
The team can record duties from the field service agreement, outage window, evidence requirements and applicable notice rules as delivery items. The distributor remains responsible for duties the Rules assign to it when a provider performs the field work.
What stays connected
Duty, source reference, responsible organisation, deliverer, due date and evidence.
02
Plan
Connect prerequisites to the work
Operating approvals, applicable life support checks, customer-notice duties and field prerequisites become linked delivery items. Nebula shows each item state and dependency for the authorised operating team. From resolved electrical requirements, Nebula produces a source-traced DXF proposal; anything it cannot place stays marked for that team to decide.
What stays connected
Approval item, life support check, notice duty, dependency and recorded item state.
03
Notify
Keep notice duties with the work
Customer-notice duties can be recorded as delivery items with required dates and evidence. If the work window changes, the earlier date and proposed date can be recorded for the other project party to respond. The distributor's authorised team determines any fresh customer notice or consent required by the Rules.
What stays connected
Notice item, required date, evidence, earlier date, proposed date and recorded response.
04
Deliver
Connect field records to restoration
The team can record mobilisation, a provider-reported blocker, completion and restoration evidence in the item workspace. Authorised operational systems and procedures govern switching, safety and field control.
What stays connected
Field milestone, provider-reported blocker, restoration evidence, incident and responsible party.
05
Respond
Record a proposed change and its decision
The deadline-change path retains the earlier date, proposed date, reason and responding party's recorded decision. A variation can separately record its description, reason, cost impact, time impact, clause reference and authorised response.
What stays connected
Earlier date, proposed date, reason, responder, variation and recorded decision.
06
Close
Record restoration and close-out work
Restoration evidence, project communications, incidents, provider reports, payment claims and remaining work can stay connected as delivery items and records. Authorised project members can generate a current engagement report from the records Nebula holds.
What stays connected
Restoration evidence, project communication, incident, payment claim, recorded state and close-out item.
One connected engagement
What Nebula keeps connected as work changes
Prerequisites
Approval items, life support checks, notice duties, dependencies and recorded item states.
Operations
Provider milestones, provider-reported blockers, restoration evidence and incident records.
Commercial
Payment claims, variations, suspension and defect notices, recorded decisions and stated service terms.
Performance
Verified work and its recorded delivery context.
Delivery trust
Keep service history available for review
Verified work counts in a provider organisation's service history only when two separate organisations are party to it. The distributor decides how that record informs provider selection.
See how record verification worksUse Nebula to carry this work through close-out
Nebula reads the documents that define the work into a delivery plan, carries approved changes and evidence forward, and prepares reports and handovers. Your people decide what is accepted and what happens next.
Nebula's assistant. Questions about Nebula.