Joint C2 Focus Group – 23rd July

Dear ADIESA Member,
The second Joint Command and Control Focus Group (JC2-FG) was held at ADFA on 23 July. The event was well received with almost 80 attendees; half of whom were Defence members, a big ‘thank you’ to those who participated. I know Defence are especially grateful as they noted who from industry are involved.
The agenda included:

  • updates on the three major projects, including scope, intended dates to approach the market, and Government decision timeframes;
  • update from Director C4ISR Design, Dr Gina Kingston;
  • CASG and CIOG perspectives, delivered by and on-behalf of the respective Branch heads;
  • fruitful break-out sessions on the four industry questions around commercial strategy and technology futures.

The slides are being finalised now, including the notes from the breakout sessions. They will be posted to the ADIESA website within the next few business days.

Please provide any feedback or other ideas to help us improve the FG in the future.

Our next JC2-FG meeting is expected to be held around November this year.

I encourage everyone to make the effort to join us.

Regards,
David Horton
ADIESA JC2-FG Facilitator
0410 814 619
David.horton@systematic.com

Joint C2 Focus Group Report – 9th May, 2018

Report by Mr David Horton (ADIESA) and Mr John Gray (Defence)

Copy of the PowerPoint Presentations from the Day

JC2 FG PPT
Click to open the JC2 FG presentation

Summary of Workgroup Discussions

Workgroup 1 – How does Defence and Industry harness Innovation?

  • Acknowledged the loss of RPDE.
  • Pre-qualified tender panels risk not including the best elements, especially from Australian small business.
  • Consortium approach – workgroup provided examples of success from Europe.
  • Innovation Hub – some have found cumbersome and time consuming for no value.

Workgroup 2 –How do we achieve a more agile, faster approach to capability delivery?

  • What does ‘Agile’ mean?
  • Need to have relationship between Defence and industry assessed and approved so the process can continue quickly.
  • Risk sharing – Defence taking some.
  • Length of sprint directly related to the amount of risk i.e. the longer the acquisition, development and support, the higher the risk.
  • Industry has resources to fund R&D but needs to collaborate with Defence to meet capability needs together.
  • Security accreditation. The process of acceptance should not stop delivery.

Workgroup 3 – Innovations points to 2025

  • Looked at key disruption points e.g. Uber or AirBnB – doesn’t own the assets (e.g. car, driver) but owns the experience. HQ doesn’t own the asset but owns the information. Both working in a contested environment.
  • Where does disruption happen? Where there are deficiencies, or where innovation is heading in a certain direction that provides benefit. Often need an imperative or catalyst to move, though.
  • One requirement where innovation required is Multi-Level Security (MLS). Currently a singular approach to Identity Management.
    • Needs to encompass Whole of Government, and even five-eyes (FVEY), and others(?)
    • Establish trust. All about the individual, so that we trust that they can gain access to the information they need.
    • Virtualisation and IP encryption allows new approach.
    • See Innovation Hub and Data61 submission to overlay information at one classification over another, but preserving labels.
  • Lack of direction from Government to Defence.
  • Interoperability:
    • NATO C2 Simulation and Modelling Language.
    • How do we work with interoperability specifications that haven’t been updated since 2003, for example.
    • Need for a Joint Network Interoperability Centre (JNIC).
  • Australian mining operations share a similar environment to Defence. What can we learn from them?
  • Technology change is just one aspect. Also cultural, organisational and system change.

Workgroup 4 – Australian Industry Capability

This group was not run due to lack of numbers.

Workgroup 5 – Open Architectures in next 10 years

  • Both Commonwealth and Industry must take ownership of the problem if there is to be success / progress toward achieving open architecture framework.
  • Industry tends to place a premium on open architectures, which will need to be addressed to take the problem correctly.
  • Must define rules “open architecture is just quality attribute of the system” – Boeing.

Workgroup 6 – Defence Do Better to Serve Industry as a FIC

  • Mapping Defence capability gaps and commercial deficiencies (within security boundaries).
  • Other FIC have 3-star capability managers. What about Industry?
  • Scheduling.
  • Dual employment.
  • Australian industry is fragmented and small. CEA may be the biggest left with 400 employees.  How do we bring together?

Closing Remarks

  • Please provide feedback on the value you gained from the day:
    • As an industry representative?
    • Do you think Defence was receptive to the message?
    • Were the questions right?
    • Please email your responses to:
  • More successful than expected.
  • Must maintain communication and explore how we can continue to collaborate better.

Next Steps

  • C4ISREW Environmental Working Group (EWG) is pencilled in for end May or early June. This would contain a JC2 breakout session.
  • JC2 Concepts Paper due for release in July. ADIESA will look to having a JC2-FG meeting after that.