Skip to main content
Founding places are open. Claim yours
Industries

Defence and commonwealth

Deliver against the data list, delegation and security obligations.

Delivery can fail through a missed data item, unsupported delegate decision or broken security process even when the underlying technical work is progressing.

Operating contextASDEFCON Support, PGPA 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, financial delegations and commitment approvals
Money
Pricing, invoices, performance consequences and approved changes
Security
DISP governance duties and approved handling environments

Product proof

Nebula workspace

NebulaDefence and commonwealth

Engagement

A performance-based Defence support engagement

ASDEFCON Support, PGPA 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 work statement, data requirements, performance framework, pricing and decision authorities are proposed from the defining materials. Authorised participants review the responsibilities attributed to them, and decisions are recorded for the scope they govern.

    What stays connected

    Requirement, source, deliverer, accepter, authority and reporting cycle.

  2. 02

    Mobilise

    Establish every recurring cycle

    Data items, reviews, reports, invoices and option dates become an owned programme. Dependencies show when a Commonwealth input or acceptance decision is blocking supplier delivery.

    What stays connected

    Cycle, prerequisite, deliverer, reviewer, deadline and dependency.

  3. 03

    Deliver

    Keep performance with its evidence

    Each data item is submitted, accepted, rejected or disputed against its source requirement. Supporting files, questions and decision history remain connected to the performance assessment.

    What stays connected

    Data item, evidence, acceptance state, response and performance effect.

  4. 04

    Change

    Keep the proposed change with its authority

    A changed support requirement records scope, price, schedule and value-for-money reasoning. The delivery plan changes only after the authorised delegate decision is recorded.

    What stays connected

    Proposal, reasons, delegate, approval, revised value and revised dates.

  5. 05

    Secure

    Keep protected material in authorised systems

    Annual reporting, training, incident-register and security-governance duties can be scheduled. Sensitive or classified material remains in its authorised environment, with Nebula recording only appropriate references and actions.

    What stays connected

    Security duty, owner, due date, appropriate evidence reference and status.

  6. 06

    Close

    Resolve options, handback and final performance

    Outstanding data, asset handback, final invoices, performance assessment, records and option decisions are resolved before the support period closes or extends.

    What stays connected

    Open deliverables, final money, handback, assessment and option decision.

One connected engagement

What Nebula keeps connected.

  1. Connected record 01

    Delivery

    Data items, performance measures, evidence and acceptance decisions.

  2. Connected record 02

    Authority

    Delegates, approvals, reasons and revised commitments.

  3. Connected record 03

    Commercial

    Pricing, invoices, accepted change and budget position.

  4. Connected record 04

    Security duties

    Appropriate obligation references preserve classified-system authority.

Delivery trust

Make verified supplier performance portable

Verified delivery, documentation and response history strengthens future supplier assessment. The record gives Commonwealth rating, assurance and security-accreditation processes source-linked evidence of execution.

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.