Defence and Commonwealth
Keep the data, the approvals and the security duties attached to the delivery they affect
A data item, an approval or a security duty can still hold up delivery while the technical work moves. The record has to show the source requirement, what is recorded, and which decision path applies.
The agreement and rules behind the work
ASDEFCON Support, Commonwealth delegations and the Defence security framework
Illustrative engagement
A performance-based Defence support engagement
A supplier delivers recurring support outcomes, data items, reports and priced changes under an ASDEFCON Support style agreement.
- Delivery
- Statement of work, performance measures and recurring data requirements
- Authority
- Acceptance roles, Commonwealth delegation records and commitment approvals
- Money
- Pricing, invoices, performance consequences and approved changes
- Security
- DISP obligations and customer-approved handling environments
Product example
Nebula workspace
Project
A performance-based Defence support engagement
ASDEFCON Support, Commonwealth delegations and the Defence security framework1 delegate decision needs action.
ReviewWhere it stands
Support cycle is active
8 of 10 data items acceptedWhat needs you
Your decision1 decision
Support requirement changeWho is involved
Delivery position
Current delivery positionDelivery items
Recurring support outcomes and evidenceMonthly support report
VerifiedSupport requirement change
Decision dueSecurity governance report
ActiveThe engagement lifecycle
How Nebula carries this work through delivery
01
Form
Read the delivery and authority model together
The defining materials produce proposed requirements for the work, data, performance, pricing and decision roles. Project parties review the responsibilities attributed to them before the delivery plan is accepted.
What stays connected
Requirement, source, deliverer, accepter, reporting cycle and recorded decision.
02
Mobilise
Establish every recurring cycle
Data items, reviews, reports, invoices and option dates become owned delivery items. Dependencies keep each recorded Commonwealth input or acceptance decision connected to the supplier work that depends on it.
What stays connected
Cycle, prerequisite, deliverer, reviewer, deadline and dependency.
03
Deliver
Keep performance with its evidence
Each data item stays connected to its source requirement, current item status and supporting evidence. Questions and recorded decisions remain in the engagement history.
What stays connected
Data item, evidence, item status, response and recorded assessment.
04
Change
Keep the proposed change with its authority
A proposed change records scope, cost, time, clause reference and reason. For members, Nebula applies the organisation's recorded permission and value limit when approving a variation; the Commonwealth entity determines the applicable PGPA delegate and value-for-money position.
What stays connected
Proposal, reason, clause, cost, time, responder and decision.
05
Secure
Keep protected material in authorised systems
Annual reporting, training, incident-register and security-governance duties can be scheduled as delivery items. For material kept outside Nebula, the team can create the required delivery action without adding the protected material itself.
What stays connected
Security duty, owner, due date, recorded action and item status.
06
Close
Resolve options, handback and final performance
Outstanding data, asset handback, final invoices, performance assessments, records and option decisions remain visible when the authorised parties decide whether the support period closes or an option is exercised.
What stays connected
Open deliverables, money position, handback, assessments and option decision.
One connected engagement
What Nebula keeps connected as work changes
Delivery
Data items, evidence, item status and recorded decisions.
Authority
Organisation approval levels, variation decisions, reasons and values.
Commercial
Pricing, invoices, approved changes and budget position, with each variation's response deadline held against the counterparty.
Security duties
Delivery items, owners, dates, recorded actions and status.
Delivery trust
Keep verified delivery available for later review
Verified work counts in an organisation's delivery history only when two separate organisations are party to it. Authorised teams can prepare a project report from the current delivery record; Commonwealth supplier assessment, DISP membership and security accreditation remain separate decisions.
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.