The DECNET directory is moving to Helyx.

Sign In Become a Member

CollabX 2026: What actually matters (and what to extract)

ACT Base Services Transformation Business news Consultant Opportunities Contractor Opportunity Estate Works Hot Buttons Industry Briefs Procurement Policy Stakeholder Engagement Tips & Tricks

By Darian Macey, March 24 2026

The 30-second airport read

CollabX is industry’s annual signal check on how Defence will actually deliver the estate.

This is what matters:

  • The next Integrated Investment Program (IIP) shape will be hinted at, not published
  • Pipeline visibility is still the biggest friction point
  • Base Services Transformation is really about data and accountability
  • Indigenous participation is shifting from narrative to enforcement (but still weak in planning)
  • There is still no standard for project scheduling across Defence
  • AI is coming fast, but governance is ahead of practical direction

If you attend, your job is simple:
extract clarity on those six points.


Why this CollabX matters now

The Defence estate is entering a different phase.

Not growth.
Execution.

The signals are clear:

  • More money committed
  • Less tolerance for delay
  • Higher expectations on industry performance
  • Increasing pressure on productivity

At the same time:

  • Data is now treated as a capability input
  • AI is being actively explored across logistics, planning and decision-making

But the system is still fragmented.

That gap – between ambition and execution – is where the opportunity sits.


1. Strategy & Pipeline (Perkins, Sowry, Quinn)

What youโ€™ll hear

Strategic intent, priorities, constraints, confidence language

What actually matters

  • Direction of the next IIP update
  • Near-term pipeline (next 6โ€“18 months)
  • Where Defence lacks delivery confidence

Questions that matter

  • What is actually funded vs โ€œdirectionalโ€?
  • What will be released in the next two quarters?
  • Where are projects failing before contract?

Watch for

  • Any move toward clearer pipeline communication
  • Language around โ€œconfidenceโ€ and โ€œcertaintyโ€

Red flags

  • Long-term vision with no near-term detail
  • Continued opacity on sequencing and timing

2. Delivery & Performance (Follett, McLeod)

What youโ€™ll hear

Service delivery, base services reform, estate outcomes

What actually matters

  • How Defence will measure performance
  • What behaviours will be rewarded or penalised
  • How base services contracts will evolve

Questions that matter

  • What metrics actually drive payment and penalties?
  • What does โ€œgood performanceโ€ look like in practice?
  • What data will industry be required to provide?

Watch for

  • Shift from reporting โ†’ accountability
  • Increased reliance on data systems

Red flags

  • More reporting without consequences
  • No clarity on performance enforcement

3. Major Programs (Submarines, NT, WA)

What youโ€™ll hear

Program updates, regional opportunities, constraints

What actually matters

  • Which packages are real vs speculative
  • Where industry can invest with confidence
  • Constraints (workforce, approvals, security)

Questions that matter

  • What is locked vs still shaping?
  • What will be tendered in the next 12 months?
  • What are the gating constraints?

Watch for

  • Clear sequencing of packages
  • Signals on procurement timing

Red flags

  • โ€œOpportunitiesโ€ without timelines
  • No clarity on how work will be packaged

4. Reform Themes (Productivity, Collaboration, MVP)

What youโ€™ll hear

Innovation, collaboration, risk-sharing, productivity

What actually matters

  • How Defence will actually reduce delivery time
  • Whether requirements will stabilise earlier
  • Whether industry risk will reduce or just shift

Questions that matter

  • What is the minimum viable requirements baseline?
  • How do we stop rework loops?
  • What will be standardised across projects?

Watch for

  • Any mention of standardisation
  • Early contractor involvement models

Red flags

  • โ€œCollaborationโ€ without structural change
  • No movement on requirements certainty

5. Policy Direction (Indigenous, Sustainability, Data)

What youโ€™ll hear

Indigenous participation, net zero, governance

What actually matters

Indigenous participation

  • Shift from commitments โ†’ enforcement
  • Integration into planning phase (not delivery phase)

Questions

  • How is participation verified?
  • What happens when targets arenโ€™t met?
  • Why is planning-phase participation still weak?

Sustainability

  • What is mandatory vs optional
  • Who owns trade-offs (cost vs compliance)

Questions

  • What standards will be enforced?
  • Who arbitrates cost vs sustainability?

The unresolved issues (this is where the value sits)

If CollabX delivers real value, it will address these directly:

1. IIP visibility

Not headlines โ€” actual pipeline clarity

2. Contract award transparency

Who won what, why, and what it means for the market

3. Indigenous accountability

Particularly in planning and design, not just delivery

4. Project scheduling standard

Defence still lacks a consistent approach
This is a major inefficiency across the estate

5. Data as a capability input

Now formalised, but not operationalised consistently


The big one: AI in Defence estate delivery

Defence has already set the policy direction.

From the Responsible AI policy:

  • AI must be lawful, accountable and explainable
  • Humans remain responsible for outcomes
  • Risk-based controls apply across the lifecycle

From the Data Strategy:

  • Data is a fundamental input to capability
  • Decision advantage = faster, better decisions
  • AI will be enabled through platforms like OneDefence Data Platform

But the practical gap is obvious.

What industry needs clarity on:

  • Can contractors use AI in delivery workflows?
  • What documentation is required if they do?
  • Where is AI prohibited vs encouraged?
  • How will Defence audit AI-assisted outputs?

If this isnโ€™t answered at CollabX, the gap remains.


If you only do three things

  1. Ask one hard question on pipeline – get a date, not a narrative
  2. Validate one opportunity with two independent sources
  3. Leave with one agreed next step – not โ€œletโ€™s stay in touchโ€

Final word

Most people will attend CollabX and take notes.

A few will extract signals.

Very few will convert those signals into action.

Thatโ€™s the difference.

Donโ€™t go to learn.
Go to test assumptions.
Go to force clarity.
Go to position.

If you leave with:

  • One clearer pursuit
  • One stronger relationship
  • One sharper narrative

Then it was worth it.

If not, it was just another conference.

Darian Macey
Author: Darian Macey

Darian is a former Engineering Officer with the RAE with tertiary qualifications in Engineering and Project Management. He is a leading practitioner within Australia's NSI sector with previous employment in Government, project management and building contractor organisations.

chatsimple