Skip to main content
Industries

Defence and commonwealth

Keep data items, approvals and security duties connected to delivery

A data item, approval or security duty can affect delivery even while technical work progresses. The record needs to show the source requirement, what is recorded and which decision path applies.

Operating contextASDEFCON Support, Commonwealth delegations and the Defence security framework

The Australian House of Representatives chamber in session
04Defence and Commonwealth controls are explicit.

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 specimen

Nebula workspace

NebulaDefence and commonwealth

Engagement

A performance-based Defence support engagement

ASDEFCON Support, Commonwealth delegations and the Defence security framework

1 delegate decision needs action.

Review

Where it stands

Support cycle is active

8 of 10 data items accepted

What needs you

1 decision

Support requirement change

Who is involved

Commonwealth programme officeCustomer
Orion Support ServicesSupplier

Engagement performance

Current delivery position
83/100

Delivery84

Response77

Evidence86

Delivery items

Recurring support outcomes and evidence
10 data items

Monthly support report

Verified

Support requirement change

Decision due

Security governance report

Active

The engagement lifecycle

How the engagement moves through delivery

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

  1. Connected record 01

    Delivery

    Data items, evidence, item status and recorded decisions.

  2. Connected record 02

    Authority

    Organisation approval levels, variation decisions, reasons and values.

  3. Connected record 03

    Commercial

    Pricing, invoices, approved changes and budget position.

  4. Connected record 04

    Security duties

    Delivery items, owners, dates, recorded actions and status.

Delivery trust

Keep verified delivery available for later review

For verified item outcomes, Nebula applies its eligibility rules before it can record a reputation event in an organisation's delivery history. 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 works

Start with the documents that define the work

Build the delivery plan and manage the work, or talk to us about a portfolio.

Get startedRead the security page