Nevertheless, it can be argued that JP2090 is working to improve fixed infrastructure capabilitiesand has not adequately addressed the immediate interoperability needs of deployed forcesthrough a common coalition system. ‘Gateway’ development is effective but it is not theanswer to the information exchange limitations of the operational commander.Current national and coalition architecturesNational systems provide national services; this is fundamental and will not change. The keyaspect of network-centric coalition operations is interoperability through commonality. At thelower tactical levels, this is achieved through direct liaison and (somewhat) automated sensorfusion. At the strategic level, there is any number of methods to facilitate interoperabilityacross the tenets of national power. These are concerned with diplomacy, intelligence activities,military and economic cooperation, and engagement. What is missing is interoperability inthe operational space. In an effort to achieve interoperability, a number of coalition systemshave been developed, including the ISAF ‘mission secret’ network (IMS), the common SIPR 3domain (CSD) and CENTRIX in its multitude of releasable formats. What is lacking is networksimplicity, which could be achieved through a single common system.The CENTRIX network was ‘designed to one day form a single, common, global, multinationaldata network’. 4 However, it remains a loose collection of multiple, separate networks that cannotbe interconnected because the necessary security technology is not commonly employed byall nations. Further, the system is also limited by over-exposure and a lack of hardware andnetwork commonality. It is, therefore, considered unsuitable for further development as it willnot evolve suitably to meet the needs of the operational commander in accordance with thenetwork concept proposed in this article.The established coalition systems commonly deployed have varying levels of effectiveness.For example, they are employed by <strong>Australian</strong> forces in the Middle East area of operations asthe primary means of coalition interoperability. But, despite connectivity, there is no reliablemethod (architecturally or technically) to exchange data between these systems and <strong>Australian</strong>national systems. The common practice is to ‘air gap’ the necessary data. This method hasinherent risk, as it contravenes information exchange principles and also relies on mass storagedevices to conduct the information exchange. This leads to an increased risk of computer virusinfection and may provide an easy target for clandestine intelligence collection.Additionally, accounts are often shared and passed between personnel because the processesassociated with ‘request’ and ‘creation’ vary significantly between systems. They are also oftencomplex and not timely. In some cases, the process to gain access to databases and accountsis measured in weeks and months, rather than days. Some stipulated aspects are difficult tomeet because <strong>Australian</strong> requirements are managed differently to the methods employed bycoalition partners. Recent experience has also highlighted further issues once members aregranted accounts. In particular, the gamut of applications and variations in standard operatingenvironments is problematic.82
Moreover, while often intuitive, users are forced to learn and navigate a range of foreignapplications and tools such as email, office programs, web-based tools and IP chat services.Technical awareness is not common across the range of service providers and response timesare generally not prioritised. As it stands, administrator rights also vary considerably. Forexample, Australia’s largest footprint in Afghanistan is in Tarin Kowt. While Australia considersthis site a key node for communications services, coalition service providers do not and notone of the three coalition information systems available in Tarin Kowt is currently administeredlocally.As a result, <strong>Australian</strong> forces employing these systems for coalition ISTAR (intelligence,surveillance, targeting acquisition and reconnaissance), situational awareness and mandatoryreporting rely on these services remaining serviceable. From an <strong>Australian</strong> perspective, theseservices should be considered critical capabilities. However, Australia is not represented inmaintenance schedules, outage reporting or network architecture change management. Thisoften results in service outages without warning. When this occurs, <strong>Australian</strong> personnelhave limited ability to contact the service providers to rectify services because the technicalcontrolling authorities are not in location.The coalition community uses multiple means to communicate operational information andintelligence product, including direct secure communications. When direct interoperabilitycannot be achieved because of security caveats, commanders rely heavily on the placement ofliaison officers. These personnel are invariably granted limited access to the respective nationalnetworks within the headquarters where they are working. Connectivity is maintained withparent <strong>Australian</strong> units through tactical radio or, more commonly in established headquarters,tactically deployable systems such as the ‘liaison officer’s briefcase’ system.These arrangements are also replicated by other government agencies. They maintain theirown independent systems but also have a requirement to share information in various forms.It is therefore reasonable to assert that the theme of commonality should be considered forreplication across the range of government agency systems. System commonality at this levelwould provide response forces with multiple options and a level of integration that has so fareluded the ADF. It is conceded that considerable planning and liaison would be required toachieve integration across the government spectrum. However, emphasis should be placed onthe strengths of ‘synchronisation’ and the benefits this system would generate, rather than thework required to implement it.For fixed infrastructure liaison, the GRIFFIN gateway was established to provide a rudimentarynetwork gateway bridging some national networks in the coalition community. 5 This network iseffective but, given the associated security procedures, it is not a timely or responsive system.Intelligence/SIGINT communities have developed strong coalition networks that are leveragedby coalition units. The ADF employs these strategic information networks to communicateoperational information and intelligence but they rely on ‘reach back’ to Australia to facilitateliaison and the official transfer of data. When considered holistically, there are a number ofcapability gaps evident.83
- Page 3 and 4:
Australian Defence ForceCONTENTSISS
- Page 5 and 6:
asics of the ADF’s approach to wa
- Page 7 and 8:
Oceanography and Force 2030: harnes
- Page 9 and 10:
The warm, relatively fresh waters o
- Page 11 and 12:
In a further example, the Australia
- Page 13 and 14:
Direct threats include maritime ter
- Page 15 and 16:
Commodore Rod Nairn is a career hyd
- Page 17 and 18:
Institute of Marine Science, $80m i
- Page 19 and 20:
The nature of casualties presenting
- Page 21 and 22:
Contracted solutions in less hostil
- Page 23 and 24:
Planning implications of increased
- Page 25 and 26:
When a nation is at war, it is acce
- Page 27 and 28:
NOTES1. Doug Brooks, ‘Role of pri
- Page 29 and 30:
the further from Stanley the landin
- Page 34 and 35: 20. Comisión de Análisis y Evalua
- Page 36 and 37: Coral Sea neighbours - then and now
- Page 38 and 39: sources. In contrast, such trade be
- Page 40 and 41: New Caledonia’s significance toda
- Page 42 and 43: years, it was often perceived—by
- Page 44 and 45: NOTES1. K. Mushakoji quoted in R. A
- Page 46 and 47: Lasers or Longbows? A Paradox of Mi
- Page 48 and 49: Military complexityAs military capa
- Page 50 and 51: accounts for 93 per cent of the pro
- Page 52 and 53: The paradox of military technology
- Page 54 and 55: fleet is massive, with sustainment
- Page 56 and 57: NOTES1. Benjamin Franklin, Poor Ric
- Page 58 and 59: 30. D. Korowicz, ‘Things Fall Apa
- Page 60 and 61: This new capability provides techni
- Page 62 and 63: ‘Reaching back’ for information
- Page 64 and 65: Figure 2. Chart summarising an exam
- Page 66 and 67: Fast OR typically uses established
- Page 68 and 69: the results produced. For example,
- Page 70 and 71: of findings if very short time-scal
- Page 72 and 73: Dr Tim McKay is Head of the DSTO Op
- Page 74 and 75: strategic documents signed by the U
- Page 76 and 77: • Strategic Command (STRATCOM), t
- Page 78 and 79: Geographic Combatant Commands in th
- Page 80 and 81: 8. This evolution and expansion can
- Page 82 and 83: 27. In particular, in contrast to t
- Page 86 and 87: Proposed conceptThe proposed networ
- Page 88 and 89: organisations could deploy at short
- Page 91 and 92: The PacificHugh AmbroseText Publish
- Page 93 and 94: Bloody Victory: the sacrifice on th
- Page 95 and 96: Somme as critical to the forging of
- Page 97 and 98: Command and Control: the sociotechn
- Page 99 and 100: Human Factors Issues in Combat Iden
- Page 101 and 102: The Canadian paper on CAS (Chapter
- Page 103 and 104: The Ashgate Research Companion to M
- Page 105 and 106: There is also a chapter on early vo
- Page 107 and 108: The authors’ chief vulnerability
- Page 109 and 110: Books of this genre are intended to
- Page 111 and 112: The ninth chapter is entitled ‘To
- Page 113 and 114: Many members of the ADF may honestl
- Page 115: GUIDANCE FOR AUTHORSThe Australian