Case Study: Project delivery, uplift and AI tooling for Defence simulation and training

Client: Department of Defence, Joint Collective Training Branch (JCTB)

Project: ICT Futures Program, DTEN modernisation

How Profectus took over project management and delivery of the Defence Training and Experimentation Network (DTEN) modernisation for the Joint Collective Training Branch, running a seven-line-of-effort program to a hard end date under an engineering and architecture-led Delivery Lead, while designing, building and sustaining its two products: the uplifted DTEN platform and a locally hosted AI tooling suite for exercise planning and federation builds.

Client and context

The Joint Collective Training Branch (JCTB), within Headquarters Joint Operations Command (HQJOC J7), is responsible for delivering high quality, timely and realistic joint collective training to prepare Australian Defence Force elements for operational success. To meet the increasing complexity of Defence training environments, JCTB initiated a multi-year ICT Futures Program to refresh, remediate and modernise the branch’s simulation and network infrastructure.

The program covers network and server upgrades, system transitions and architectural improvements to support live, virtual and constructive training environments across Australia, with the aim of delivering secure, resilient and scalable infrastructure that underpins the ADF’s joint and combined exercise capability.

At the centre of the program is the modernisation of the Defence Training and Experimentation Network (DTEN), the federated simulation environment JCTB uses to deliver joint collective training. The modernisation is an uplift of DTEN rather than a new capability: new hardware and platforms, upgraded and migrated workloads, and stronger identity, security, network and monitoring integration, delivered while the network continues to support live training.

The engagement

Profectus provides specialist personnel across multiple technical streams including Networks, Transition, Project Coordination and Solution Architecture. Working within the CENGR directorate under JCTB, the team supports the design, remediation and delivery of the Futures Program infrastructure upgrades, collaborating with Defence engineers, the Chief Architect and other technical stakeholders. Personnel work from JCTB facilities at Fyshwick and HMAS Harman, supporting both local and distributed Defence sites, with work often extending beyond standard hours during training cycles and travel undertaken to support system upgrades and validation activities.

As the program matured, Profectus took over project management and delivery of the DTEN modernisation, and is running it through to completion. The whole Profectus team at JCTB is now responsible for the modernisation end to end: providing design feedback, implementing the uplift and sustaining the environment once delivered. Work is resourced from both the modernisation team and J76 operations, with Profectus coordinating effort across the two so the uplift keeps moving without compromising training. Project management sits with Profectus’ Delivery Lead, whose strong background in engineering and architecture means the modernisation is run by someone who understands the technology as deeply as the plan. Critically, Profectus is not handing the modernised DTEN over to someone else: the same Profectus team of system administrators, engineers and technical specialists that supports DTEN day to day is there to catch each element of the modernised environment as it lands, and to sustain it from then on.

The engagement has two parts. The first, and the core of this case study, is project delivery: Profectus runs the modernisation program end to end, from lines of effort and critical path to reporting, risk and transition. The second is product: the program delivers two products that the Profectus team designs into, builds and sustains, the uplifted DTEN platform and a locally hosted AI tooling suite that brings AI into exercise planning and federation builds.

The challenge

JCTB’s simulation and training systems had evolved through years of incremental upgrades, requiring a coordinated remediation, transition and modernisation effort:

  • Fragmented infrastructure: inconsistent configurations, legacy technical debt and integration challenges across multiple Defence networks, with limited visibility of system dependencies
  • Operational continuity: maintaining readiness while systems were transitioned or upgraded, often supporting live training events concurrently under high operational tempo
  • Architecture and security alignment: aligning new and legacy network components to Defence enterprise standards, security frameworks and future-state architectures
  • Coordination: integrating multiple technical disciplines, contractors and Defence stakeholders under a unified project structure and strict timelines
  • No documentation baseline: DTEN had never had a proper baseline of technical documentation, yet the uplift had to preserve the network’s existing ICT Security Authorisation
  • Complex migration decisions: every legacy application and capability, from Active Directory and Exchange to common services and Mercury, needed a deliberate decision to upgrade in place, migrate as is or replace
  • Integration-heavy risk: identity and security integration, network cutovers, coalition interoperability and operations readiness all had to come together as the program moved from build into integration, migration and test
  • External lead times: licensing and procurement activities, some in train for more than nine months, sat outside the program’s direct control
  • A hard end date: DTEN must be modernised, documented, authorised, migrated and handed over into sustainment by 30 April 2027

Project delivery

Project delivery sits at the core of the engagement. Profectus runs the DTEN modernisation as a structured program with a single accountable Delivery Lead, seven resourced lines of effort, an actively managed critical path, documentation that keeps pace with the build, open status reporting and disciplined risk management, all working back from a fixed end date.

Engineer-led project management

The modernisation is project managed by Profectus’ Delivery Lead, and his strong background in engineering and architecture shapes how the program is run. He engages directly with designs, challenges technical assumptions and reads dependencies at the engineering level, so risks surface earlier, upgrade, migrate or replace decisions are grounded in what is technically achievable, and the schedule reflects how the work will actually be built. He is the single point of coordination between Profectus engineers and architects, J76 operations, the Chief Architect and JCTB leadership, translating technical detail into clear delivery status and decisions, and keeping design feedback from implementation and sustainment flowing back into the designs.

Seven lines of effort and the critical path

Profectus structured the modernisation into seven lines of effort (LOEs), each with a defined scope, resourcing drawn from the modernisation team and J76 operations, and target dates worked back from the 30 April 2027 end state. LOE4, migration planning, is managed as the critical path because it unlocks all downstream build, test and migration work. Progress at November 2026:

  • LOE1 Design and procurement: finalising designs and completing procurement; around 85 per cent complete, target November 2026
  • LOE2 Infrastructure: racking, stacking and networking the new hardware; essentially complete at 99 per cent
  • LOE3 Platform: configuring the platform and establishing connectivity; around 90 per cent complete
  • LOE4 Migration planning: deciding for every legacy application and capability, including Active Directory, Exchange, common services and Mercury, whether to upgrade in place, migrate as is or replace, then documenting each decision and breaking it into resourced work packages; around 70 per cent complete, target December 2026, and the program’s critical path
  • LOE5 Build and test: testing the new infrastructure and building the applications, including the Joint Live Virtual Constructive (JLVC) environment; target February 2027
  • LOE6 CFBL: relocation and management uplift; target December 2026
  • LOE7 Closeout and transition: running alongside the other lines of effort, moving each element into sustainment as it finishes
Resourcing and coordination

Every line of effort draws on people from both the modernisation team and J76 operations. Profectus plans and coordinates that shared resourcing so modernisation work is sequenced around training cycles and operational commitments, and the uplift progresses without compromising readiness. The Delivery Lead brings Profectus engineers and architects, J76 operations, Defence engineers, the Chief Architect and other technical stakeholders together under one project structure, so decisions are made once, dependencies are visible and work is not duplicated.

Documentation-led delivery

Because the modernisation is an uplift of DTEN rather than a new capability, Profectus made documentation lead and keep pace with the build. This retains DTEN’s existing ICT Security Authorisation rather than triggering a fresh authorisation, and gives JCTB a proper baseline of DTEN technical documentation for the first time.

Status reporting and risk management

Profectus reports the program openly. Overall status is Amber-Green: not because the program is off track, but because it is moving out of build and into integration, migration and test, where risk naturally rises. The main pressure has come from outside the program, chiefly licensing and procurement lead times, some in train for more than nine months. These have absorbed contingency without moving the timeline. Key risks are actively managed across five areas:

  • Identity and security integration: PKI, Active Directory, APAM and MAMO
  • Network cutovers: DTCN to DEF2300, and HAIGS to Indigo
  • Coalition and cross domain interoperability: JTEN and USG
  • Operations and monitoring readiness: DNOC, DSOC and ITSM
  • People availability: securing the right people across the modernisation team and J76 operations at the right time
Closeout, transition and sustainment

A Transition Manager managed the transition of systems into maintenance and support phases, developing service design and support documentation. The team developed technical control documentation, ensured configurations complied with Defence security requirements, ITSM policy and Authority to Operate conditions, applied ITIL service management principles and participated in Change Advisory Boards. Under the modernisation, closeout and transition run in parallel with delivery, so each element moves into sustainment as soon as it is complete rather than waiting for a single cutover at the end.

Profectus is also the team that receives what the program delivers. Its system administrators, network and systems engineers and technical specialists already run and support DTEN, so as each element of the uplift completes, it is caught and sustained by people who helped design and build it. That removes the usual gap between a delivery team and a separate sustainment team: there is no cold handover, knowledge stays in place, issues found in early operation feed straight back into the remaining lines of effort, and JCTB has continuity of support from build into steady state.

The product

The program delivers two products. The Profectus team feeds design into both, builds them and sustains them once delivered, so the people accountable for running each product are the same people who shaped and built it.

Product one: the uplifted DTEN platform

The first product is DTEN itself, uplifted onto new hardware and platforms. New kit is racked, stacked and networked, the platform is configured with connectivity established, and every legacy application and capability, including Active Directory, Exchange, common services and Mercury, is being upgraded in place, migrated as is or replaced, then built and tested, including the JLVC environment. The finished product is a modernised, documented and authorised DTEN: integrated with Defence identity and security services, cut over to current Defence networks, interoperable with coalition and cross domain environments, monitored and supported through Defence operations and ITSM, and handed over into sustainment by 30 April 2027.

A Solution Architect designed and documented network, server and system architecture components to support current and future training requirements, delivering architectural artefacts, designs and implementation roadmaps aligned with Defence standards and the HQJOC enterprise architecture under the direction of the Chief Architect. Through the modernisation, the wider team feeds design feedback from implementation and sustainment back into the designs, so what is built is what can be supported.

Network Engineers provided hands-on remediation and transition support for simulation network environments, deploying and configuring infrastructure including routing, switching and firewall management across JCTB-managed systems. Engineers remediated networks, virtualisation, compute and storage, applied automation and scripting for repeatable builds and configuration consistency, and normalised operating system and software baselines to reduce recurring faults.

Specialists undertook deep fault diagnosis across operating systems, hypervisors, middleware and simulation application stacks, performing controlled rebuilds of virtual machines and simulation hosts, correcting configuration drift and restoring known-good states, then conducting post-remediation validation before returning environments to service.

Product two: AI tooling for exercise planning and federation builds

The second product brings AI into how JCTB plans and builds exercises. AI is being applied to exercise planning, and to federation builds and deployment, to speed up planning processes, align more closely with real-world operational tools and data, and remove human error from repetitive build and configuration steps.

This builds on AI work the same Profectus team has already delivered on DTEN. An early, locally hosted LLM orchestration tool used retrieval-augmented generation (RAG) to turn natural language exercise descriptions into build proposals that, once approved, trigger the infrastructure pipeline. The team has since matured that prototype into Augmented Automation: four modular tools (AA01 to AA04) on a common, locally hosted LLM foundation, developed and tested on JLVC infrastructure and ready for production deployment. The guiding principle is that automation should make JCTB’s people more capable, not replace them.

  • AA01 Private chat for local LLMs: a web chat for Ollama-hosted models, packaged as a single Docker container that moves to offline hosts, with a model selector to match model size to the available hardware
  • AA02 Answers from JCTB’s own documents: indexes the in-house document repository and answers with sources cited under every reply, saying so when nothing relevant is found rather than guessing; it re-indexes automatically, supports a shared team memory and holds secrets in an encrypted vault away from chat
  • AA03 Logs and alerts in plain English: queries error-level logs in Loki and alert history from Prometheus and Alertmanager, answering only from JLVC’s own data, filtering by host or time window and charting CPU, memory, disk and network against thresholds for hosts and individual applications
  • AA04 Run and manage JLVC builds from chat: connects to Jenkins to list, run and monitor build, install, uninstall and security check pipelines, explains failed builds in plain English, and adds hosts singly, by CSV or Excel upload or as predefined groups, auto-filling hostnames, IPs, MACs and VLANs and checking every value against an editable JLVC rules file and existing systems before anything is committed to the version-controlled build repository

Responsible AI is built in. Every component runs offline on Defence hardware with no data leaving the environment, there is no LLM in any write path, jobs and files are allowlisted, every change is previewed and confirmed by a person before it runs, and a separate audit log records what was done. Because build standards live in one editable rules file, every federation build adheres to the JLVC standard and the standard can change without code changes. The product is designed to remove manual entry errors such as address and VLAN clashes, speed the preparation of JLVC federations and reduce reliance on specialist knowledge, with automated application configuration to standards and per-application tracking and execution identified as next steps.

What we delivered

  • Project management and delivery: engineering and architecture-led project management of the DTEN modernisation by Profectus’ Delivery Lead, across seven lines of effort, with the critical path actively managed to a fixed end date
  • Critical path control: LOE4 migration planning managed as the critical path, unlocking all downstream build, test and migration work
  • Coordinated resourcing: work resourced and sequenced across the modernisation team and J76 operations around training cycles and operational commitments
  • Documentation baseline: a proper baseline of DTEN technical documentation, developed in step with the build to retain ICT Security Authorisation
  • Transparent reporting and risk control: clear Amber-Green reporting and active management of identity, network cutover, interoperability, operations readiness and people risks, with external procurement delays absorbed in contingency rather than the timeline
  • Parallel closeout and transition: each element moved into sustainment as it finishes, supported by service design, support and technical control documentation
  • Catch and sustain: a Profectus team of system administrators, engineers and technical specialists in place to receive each element of the modernised DTEN and sustain it, with no cold handover between delivery and support
  • Product one, new infrastructure in place: new hardware racked, stacked and networked (99 per cent complete), with platform configuration and connectivity around 90 per cent complete
  • Product one, migration decisions and work packages: an upgrade, migrate or replace decision for each legacy application and capability, documented and broken into resourced work packages
  • Product two, AI tooling: Augmented Automation, four locally hosted, offline AI tools developed and tested on JLVC infrastructure and ready for production, bringing AI into exercise planning and federation build and deployment with a person confirming every change
  • Infrastructure remediation: remediation of key network and server infrastructure components supporting simulation environments, with improved stability, predictability and maintainability
  • Updated architecture: delivery of updated architectural artefacts, designs and standards documentation under the direction of the Chief Architect
  • Configuration and ITSM uplift: uplift in configuration control, ITSM compliance and integration across simulation and production systems, supported by CMDB and risk assessment contributions
  • Enterprise alignment: improved alignment between JCTB systems and Defence enterprise network architecture, with quality management and reporting maintained throughout

Systems and methods

Project delivery: Seven lines of effort · Critical path management · Shared resourcing across the modernisation team and J76 operations · Documentation-led delivery · ICT Security Authorisation · RAG status reporting and risk management · ITIL and Change Advisory Boards · Parallel closeout and transition · Catch and sustain by the delivery team

Product: PKI, AD, APAM and MAMO integration · JLVC · Routing, switching and firewall management · Virtualisation, compute and storage remediation · Automation for build consistency · CMDB · Authority to Operate conditions · Defence enterprise architecture alignment · Augmented Automation (AA01 to AA04) · Locally hosted LLM (Ollama) with RAG · Docker · Jenkins · Loki, Prometheus and Alertmanager

The result

By embedding cleared personnel across project management, project coordination, solution architecture, transition and engineering roles, Profectus is strengthening Defence’s ability to modernise and sustain its simulation infrastructure while maintaining operational continuity.

Having taken over project management and delivery, and led by a Delivery Lead who combines project management with deep engineering and architecture experience, Profectus is running the DTEN modernisation to completion. The new infrastructure is essentially in place, platform configuration is well advanced, and the program is moving through migration planning into integration, migration and test. The end state is fixed: DTEN modernised, documented and authorised, with workloads migrated and handed over into sustainment by 30 April 2027, with continued focus on interoperability, cyber resilience and readiness assurance. Because the same Profectus system administrators and engineers who help build the new DTEN are there to catch and sustain it, JCTB gets continuity from delivery straight into steady-state support.

Alongside the platform, the AI tooling product is bringing AI into exercise planning and federation builds so JCTB can plan faster, align more closely with real-world operational tools and data, and remove human error from the build process.

The engagement demonstrates Profectus’ capacity to deliver cleared, technically proficient professionals who design, remediate and transition complex ICT environments under active operational conditions, and to take ownership of delivering a major modernisation and its products to a hard deadline, contributing to Defence’s objective of secure, modern and flexible ICT foundations for joint training and operational preparedness.