2012 Multifora Handbook - The Five Eyes Data-Sharing Communities

UNCLASSIFIED
WASHINGTON-BASED MILITARY MULTIFORA
STAFF HANDBOOK 2012
UNCLASSIFIED
UNCLASSIFIED
INTENTIONALLY BLANK
ii
UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP
UNCLASSIFIED Record of Changes
Original Updated Updated Updated Updated Updated Updated Updated Updated Updated Updated Updated Updated
September 2002. 4 February 2003, Electronic Edition 1. 03 December 2003, Electronic Edition 2. 11 August 2004, Edition 2. 2 February 2005, Electronic Edition 3. 19 March 2005, Edition 3. January 2006, Edition 4. June 2007, Edition 5. July 2007, Edition 5 - Amendment 1. October 2008, Edition 6. May 2009, Edition 7. ICCWG included. August 2010, Edition 8 includes revised Multifora SOC document July 2012, Edition 9
iii
UNCLASSIFIED
INTENTIONALLY BLANK
iv
UNCLASSIFIED TABLE OF CONTENTS INTRODUCTION..........................................................................................................................................IX MULTIFORA STATEMENT OF COOPERATION - 2012 ............................................................................XI MIC CCEB STATEMENT OF COOPERATION ................................................................................... XVII ARTICLE I: ROLE OF PARTICIPANTS ............................................................................................ xvii ARTICLE II: AIM ............................................................................................................................... xviii ARTICLE III: STATEMENT OF COOPERATION ............................................................................. xviii CHAPTER 1 ................................................................................................................................................ 21 AMERICAN, BRITISH, CANADIAN AUSTRALIAN AND NEW ZEALAND ARMIES PROGRAM ........ 21 History Of The Program ...................................................................................................................... 21 Mission................................................................................................................................................ 21 Organization of the Program .............................................................................................................. 21 Program Planning System (PPS) ....................................................................................................... 23 Figure 3 ABCA Annual planning cycle ............................................................................................ 24 Program Elements .............................................................................................................................. 25 CHAPTER 2 ................................................................................................................................................ 27 AIR AND SPACE INTEROPERABILITY COUNCIL ............................................................................... 27 Introduction.......................................................................................................................................... 27 Mission ................................................................................................................................................ 27 Vision .................................................................................................................................................. 27 Capstone Concept............................................................................................................................... 27 ASIC Interoperability Framework ......................................................................................................... 27 Warfighting Functions and Capability Elements ................................................................................... 28 The Time Element ............................................................................................................................... 28 ORGANIZATION ................................................................................................................................. 28 Management ....................................................................................................................................... 28 National Directors ................................................................................................................................ 28 Management Committee ..................................................................................................................... 28 National Program Managers ................................................................................................................ 28 Steering Group .................................................................................................................................... 29 Working Groups .................................................................................................................................. 29 Working Groups .................................................................................................................................. 29 Project Groups .................................................................................................................................... 30 National Head of Delegation Meetings (HoD) ...................................................................................... 30 Project Development ........................................................................................................................... 30 ASIC Task List..................................................................................................................................... 30 ASIC Document Management Plan ..................................................................................................... 30 Test Project Agreement ....................................................................................................................... 30 ASIC WEBSITES ................................................................................................................................ 31 CHAPTER 3 ................................................................................................................................................ 33 AUSCANNZUKUS MARITIME INFORMATION WARFARE ORGANISATION ..................................... 33 Introduction ......................................................................................................................................... 33 Vision .................................................................................................................................................. 33 Strategies............................................................................................................................................ 33 Guiding Principles ............................................................................................................................... 33 Purpose .............................................................................................................................................. 33 Mission................................................................................................................................................ 34 Organisation ....................................................................................................................................... 34 Publications/Correspondence ............................................................................................................ 36
v
UNCLASSIFIED Liaison ................................................................................................................................................ 36 CHAPTER 4 ................................................................................................................................................ 39 COMBINED COMMUNICATIONS-ELECTRONICS BOARD ................................................................. 39 Background and History ..................................................................................................................... 39 CCEB Mission Statement ................................................................................................................... 39 Strategy for Achieving the Purpose .................................................................................................... 39 Resources........................................................................................................................................... 40 Organization ....................................................................................................................................... 40 CHAPTER 5 ................................................................................................................................................ 43 INTERNATIONAL COMPUTER NETWORK DEFENSE (CND) COORDINATION ............................... 43 WORKING GROUP ................................................................................................................................ 43 Background ........................................................................................................................................ 43 Role .................................................................................................................................................... 43 Introduction ......................................................................................................................................... 43
Scope............................................................................................................................................................. 43
Goals .................................................................................................................................................. 44 Implementation Plan ........................................................................................................................... 44 Collaboration ...................................................................................................................................... 44 Organization ....................................................................................................................................... 44 CHAPTER 6 ................................................................................................................................................ 45 MULTINATIONAL INTEROPERABILITY COUNCIL .............................................................................. 45 Background ........................................................................................................................................ 45 Purpose .............................................................................................................................................. 45 Membership ........................................................................................................................................ 45 Vision Statement ................................................................................................................................ 45 Mission Statement .............................................................................................................................. 45 Objectives ........................................................................................................................................... 45 Areas of Interest and Scope ............................................................................................................... 46 Organization ....................................................................................................................................... 47 Meeting Schedule ............................................................................................................................... 48 MIC Contacts ...................................................................................................................................... 48 CHAPTER 7 ................................................................................................................................................ 49 THE TECHNICAL CO-OPERATION PROGRAM .................................................................................. 49 Introduction ......................................................................................................................................... 49 Objectives & Scope ............................................................................................................................ 49 Structure ............................................................................................................................................. 49 Management ....................................................................................................................................... 52 Meeting Cycle ..................................................................................................................................... 53 Websites and Communication Tools .................................................................................................. 53 CHAPTER 8 ................................................................................................................................................ 55 THE QUADRILATERAL LOGISITICS FORUM ......................................................................................... 55 Background ........................................................................................................................................ 55 Purpose .............................................................................................................................................. 55 Goal .................................................................................................................................................... 55 Scope.................................................................................................................................................. 55 Authority.............................................................................................................................................. 55 Participants ......................................................................................................................................... 55
vi
UNCLASSIFIED Frequency and Duration ..................................................................................................................... 56 CHAPTER 9 ................................................................................................................................................ 57 WASHINGTON-BASED STAFF CONTACT DETAILS ............................................................................. 57 ABCA Armies Program Office............................................................................................................ 57 ASIC Management Committee ........................................................................................................... 58 AUSCANNZUKUS Permanent Support & Coordination Group ......................................................... 59 ICCWG ............................................................................................................................................... 60 MIC ..................................................................................................................................................... 61 TTCP .................................................................................................................................................. 61 QLF ..................................................................................................................................................... 61 CHAPTER 10 .............................................................................................................................................. 63 MULTIFORA MEETING SCHEDULE ..................................................................................................... 63 ABCA 24-Month Meeting Schedule .................................................................................................... 63 ASIC 24-Month Meeting Schedule ..................................................................................................... 64 AUSCANNZUKUS 24-Month Meeting Schedule ............................................................................... 65 CCEB 24 Month Meeting Schedule .................................................................................................... 66 ICCWG 24-Month Meeting Schedule ................................................................................................. 66 MIC 24-Month Meeting Schedule ....................................................................................................... 67 TTCP 24-Month Meeting Schedule .................................................................................................... 68 QLF 24-Month Meeting Schedule ...................................................................................................... 69 WASHINGTON BASED MULTIFORA MEETING SCHEDULE ......................................................... 70
vii
UNCLASSIFIED
INTENTIONALLY BLANK
viii
UNCLASSIFIED
INTRODUCTION
This handbook is published on behalf of the Washington-based Staffs of the multinational (MN) military interoperability and standardization fora that are currently operating under separate agreements. The membership of these fora varies, but include some combination of the following countries: Australia, Canada, France, Germany, Italy, New Zealand, the United Kingdom, and the United States. It should be noted that the Multinational Interoperability Council (MIC) and The Technical Co-operation Program (TTCP) are not military standardization forums, however; the MIC and TTCP maintain close relationships with the MN military standardization fora and are therefore included in this handbook. The multinational military interoperability and standardization fora is known locally in Washington as the Multifora. The original Statement of Cooperation (SOC) was signed in July 1996 and was amended in May 2003 and again in August 2010. A copy of the SOC is included in this handbook. The Multifora first met in December 1996 to gain an understanding of the interoperability issues, and work ongoing, within the other member organizations. The Multifora meets tri-annually to exchange information and be briefed on interoperability matters at the working level. The Multifora meetings are hosted in rotation by the member organizations. The Multifora produce a Handbook each year, the purpose of this handbook is to provide a basic overview of the organizations in order to maximize mutual knowledge and co-ordination and to help minimize duplication of effort. It also provides a ready reference of Washington-based staff contact details so that individuals can brief their parent organizations on the capabilities and functions of the fora and to network as required. Production of the handbook is coordinated in rotation by the member fora.
2010 Handbook 2011 Handbook 2012 Handbook 2013 Handbook 2014 Handbook 2015 Handbook 2016 Handbook 2017 Handbook MIC QLF ABCA ASIC AUSCANNZUKUS CCEB ICCWG TTCP
This 2012 handbook covers the following multifora: American, British, Canadian, Australian and New Zealand Armies Program (ABCA), Air and Space Interoperability Council (ASIC), AUSCANNZUKUS Naval C4 Organization (AUSCANNZUKUS), Combined Communications-Electronics Board (CCEB), International Computer Network Defense (CND) Coordination Working Group (ICCWG), Multinational Interoperability Council (MIC). The Technical Co-operation Program (TTCP), and the
ix
UNCLASSIFIED Quadrilateral Logistics Forum (QLF).
Each of the fora has separate web sites on the Internet and additional information is available from those sources. The following is a list of web sites: http://www.abca-armies.org/ http://airstandards.com http://www.auscannzukus.org/ https://community.apan.org/international/cceb/combined_commuicationselectronics_board/default.aspx http://www.acq.osd.mil/ttcp/index.html https://community.apan.org/mic
UNCLASSIFIED
MULTIFORA STATEMENT OF COOPERATION - 2012

Preamble The following statement of cooperation (SOC) between the America, Britain, Canada, Australia and New Zealand Armies Program (ABCA); the Air and Space Interoperability Council (ASIC); the Australian, Canadian, New Zealand, United Kingdom and United States Naval Command, Control, Communications and Computers Organization (AUSCANNZUKUS), the Combined Communications- Electronics Board (CCEB), the International Computer Network Defense (CND) Coordination Working Group (ICCWG), the Multinational Interoperability Council (MIC), The Technical Cooperation Program (TTCP), and the Quadrilateral Logistics Forum (QLF) has been agreed between all participants. STATEMENT OF COOPERATION BETWEEN THE ABCA ARMIES PROGRAM, THE AIR AND SPACE INTEROPERABILITY COUNCIL, THE AUSCANNZUKUS NAVAL C4 ORGANISATION, THE COMBINED COMMUNICATIONS-ELECTRONICS BOARD, THE INTERNATIONAL COMPUTER NETWORK DEFENCE COORDINATION WORKING GROUP, THE MULTINATIONAL INTEROPERABILITY COUNCIL, THE TECHNICAL COOPERATION PROGRAM, AND THE QUADRILATERAL LOGISTICS FORUM Cooperation embodies the coordination of all activities so as to achieve the maximum combined effort from the whole. Goodwill and the desire to cooperate are necessary at all levels within the Services, between the Services and the Government, and between Allies. Cooperation is as essential in planning and preparation in peacetime as it is in conflict, and is greatly enhanced through the maintenance of joint and combined interoperability. It is a means of attaining concentration of combat power with prudent expenditure of effort
An ADF Principle of War, ADFP1 The ABCA, ASIC, AUSCANNZUKUS, CCEB, ICCWG, MIC, TTCP, and QLF (the Participants): - RECOGNISING that military operations increasingly involve joint and combined application of the national forces and that interoperability between Allied nations is essential for the successful conduct of joint and combined military operations; - RECOGNISING that Command, Control, Communications, and Computer systems (C4) are a vital element of military operations; - NOTING that there are C4 issues of mutual interest and concern to the Participants (all or severally), which are often addressed concurrently but in isolation; - NOTING that, in response to an initiative of the US Vice Chief of the Joint Chiefs of Staff, the Vice/Deputy Chiefs of the CCEB nations agreed in early 2001 that the CCEB should take a leading role in facilitating coordination on C4 matters between the CCEB nations and the various single Service groups. - RECOGNISING that sufficient commitment and resources must be applied by nations to resolve C4 issues of concern while being cognizant that resources available to the Participants at both the national and international level are limited; - RECOGNISING that closer coordination of efforts and increased cooperation between the Participants in areas of mutual concern may lead to enhanced operational effectiveness during joint and combined operations and more effective use of limited resources;
xi
UNCLASSIFIED - DESIRING TO RECORD ARRANGEMENTS to establish procedures and agreements for further cooperation and coordination of effort to resolve C4 issues of mutual concern to the Participants;
HAVE AGREED AS FOLLOWS:
ARTICLE I: ROLE OF PARTICIPANTS
1.
The role or principal objective of each Participant is as follows: a. The mission of ABCA is to optimize interoperability through cooperation and collaboration in the pursuit of standardization and mutual understanding in order to integrate the capabilities of the ABCA Armies. Its member nations are: Australia, Canada, the United Kingdom and the United States. b. The principal objective of the ASIC is to ensure member nations are able to fight side-byside as airmen in joint and combined operations. Its member nations are: Australia, Canada, New Zealand, the United Kingdom and the United States. c. The AUSCANNZUKUS mission is to foster knowledge sharing that enables Warfighters to successfully complete missions across the spectrum of joint and combined operations. Its member nations are: Australia, Canada, New Zealand, the United Kingdom and the United States. d. The CCEB purpose is to enable interoperable C4 capabilities that make Warfighters more effective in coalition operations by influencing capabilities, policies, procedures and radio spectrum that optimize information and knowledge sharing. Its member nations are: Australia, Canada, New Zealand, the United Kingdom, and the United States. e. The role of the ICCWG is to facilitate the conduct of MN Information Assurance/Computer Network Defense (IA/CND) operations and information sharing to achieve mutually assured national defense information networks. Its member nations are: Australia, Canada, New Zealand, the United Kingdom, and the United States. f. The MIC provides an operator-led MN forum for identifying interoperability issues and articulating actions, which will contribute to more effective coalition operations. It is the senior body for coordinating and facilitating resolution of those issues. Initially, its work is focused on identifying and resolving information interoperability issues, which are considered to be key to effective coalition operations. Its member nations are: Australia, Canada, France, Germany, Italy, the United Kingdom and the United States. g. The aim of TTCP is to foster cooperation in the science and technology needed for defense. Cooperation includes collaborative research, sharing of data and facilities, joint trials and experiments, and advanced concept technology demonstrations. TTCP also provides a means of acquainting participating nations with each other's defense R&D programs so that each national program may be adjusted and planned in cognizance of the efforts of the other nations. Its member nations are: Australia, Canada, New Zealand, the United Kingdom and the United States. h. The purpose of the QLF is to provide a forum for the joint logistics principals of Australia, Canada, the United Kingdom and the United States to identify and prioritize logistics interoperability issues and provide strategic direction for their resolution.
xii
UNCLASSIFIED ARTICLE II: AIM 2. The Aim of this SOC is to articulate for all participants in the joint combined and single service organizations the desire and direction of the leadership of the organizations for a coordinated and cooperative approach to issues of mutual interest and concern to two or more of the organizations.
ARTICLE III: STATEMENT OF COOPERATION 3. We ENDORSE this Statement of Cooperation as an enduring symbol of our common desire to develop, maintain and enhance cooperation at all levels between the staffs of each Participant on issues of mutual interest or concern. 4. ABCA, ASIC, AUSCANNZUKUS, CCEB, ICCWG, TTCP and QLF SUPPORT the MIC position as a leader for coordinating and facilitating strategic-level courses of action to address interoperability issues, which will contribute to more effective coalition operations. 5. The MIC, ABCA, ASIC, AUSCANNZUKUS, ICCWG, TTCP and QLF SUPPORT the CCEB position as a leader in developing multinational C4 systems interoperability. 6. We ENDORSE the conduct of joint activities of mutual benefit to two or more organizations. To this end, we NOTE and ENDORSE the establishment of joint and combined working parties where this is practical and cost effective. 7. We ENCOURAGE coordination of effort to enhance allied interoperability which may reduce unnecessary duplication or nugatory effort on issues of common interest. To this end we encourage the exchange of details of meeting schedules and agendas and encourage representation by other fora when possible. 8. We NOTE and SUPPORT the establishment of regular Multifora Meetings of the Washingtonbased representatives of the Participants to further coordination efforts and to develop and agree an equitable sharing of effort and resources on cooperative activities. These Multifora coordination meetings are to occur at least twice annually and will be chaired in rotation amongst the Participants. Meeting reports are to be distributed by the members to their respective national representatives. 9. We AGREE that participation in joint activities is voluntary and that recommendations from joint activities will be available for consideration and implementation if appropriate within the individual organizations. 10. We SUPPORT the exchange of information on ongoing or proposed tasks and AGREE that the outcomes and recommendations from joint cooperative activities will be freely available for consideration, and implementation if appropriate, by all organizations, whether or not they were active participants in the activity. 11. We AGREE that this Statement of Cooperation is non-binding in law.
12. We AGREE that this Statement of Cooperation will enter into effect following endorsement of and signature by the designated Representative of each of the Participants. It will remain in effect with the mutual agreement of the Participants. 13. We AGREE that the criteria for organizations to be members of the Multifora are as follows: a. An element of the organizations governance structure and/or staff is based in the 1 Washington DC metropolitan area.
Washington metropolitan area is defined as Washington DC and its surrounding Virginia and Maryland suburbs.
xiii
UNCLASSIFIED b. To be a member of the Multifora, the role or principal objective of the organization is to be related to achieving multinational (MN) military interoperability and/or standardization or multinational cooperation and collaboration for defense purposes. c. A Multifora member must sponsor a MN organization seeking membership in the Multifora.
d. A member of the Multifora sponsoring a MN organization for membership is responsible for circulating organizational and functional details of the organization to other Multifora members. These materials should justify the organization's request for membership. The Multifora member sponsoring an organization must recommend the organization for membership and is responsible for advising the organization seeking membership of the decision of the Multifora on their membership request. e. Membership is subject to unanimous agreement of all members of the Multifora. f. This Statement of Cooperation will be amended when an organization is approved for membership in the Multifora.
xiv
UNCLASSIFIED
MIC CCEB STATEMENT OF COOPERATION
STATEMENT OF COOPERATION BETWEEN THE COMBINED COMMUNICATIONS ELECTRONICS BOARD AND THE MULTINATIONAL INTEROPERABILITY COUNCIL
Cooperation embodies the coordination of all activities so as to achieve the maximum combined effort from the whole. Goodwill and the desire to cooperate are necessary at all levels within the Services, between the Services and the Government, and between Allies. Cooperation is as essential in planning and preparation in peacetime as it is in conflict, and is greatly enhanced through the maintenance of joint and combined interoperability. It is a means of attaining concentration of combat power with prudent expenditure of effort An ADF Principle of War, ADFP1
The Combined Communications Electronics Board (CCEB) and the Multinational Interoperability Council (MIC) (the Participants):
RECOGNIZING that military operations will increasingly involve joint and combined application of the national forces and that interoperability between Allied nations is essential for the successful conduct of joint and combined military operations; RECOGNIZING that Command, Control, and Communications and Computer Systems (C4) are a vital element of military operations; RECOGNIZING that sufficient commitment and resources must be applied by nations to resolve C4 issues of concern while being cognizant that resources available to the Participants at both the national and international level are limited; RECOGNIZING that closer coordination of efforts and increased cooperation between the Participants in areas of mutual concern may lead to enhanced operational effectiveness during joint and combined operations and more effective use of limited resources; DESIRING TO RECORD ARRANGEMENTS to establish procedures and agreements for further cooperation and coordination of effort to resolve C4 issues of mutual concern to the Participants;
ARTICLE I: ROLE OF PARTICIPANTS
1. The role or principal objective of each Participant is as follows: a. The Combined Communications Electronics Boards (CCEB) role is to enable interoperable C4 capabilities that make coalitions more effective in operations. Member nations are: Australia, Canada, New Zealand, the United Kingdom, and the United States. b. The Multinational Interoperability Councils (MIC) role is to identify interoperability issues and articulate actions, which will contribute to more effective coalition operations. It is a senior operator-led body for coordinating and facilitating resolution of those issues. The scope of the MIC covers a wide range of strategic and operational interoperability issues, including non-military actors, considered to be key to coalition operations. Comprising the small group of nations that have the potential to assume
xvii
UNCLASSIFIED the role of lead nation in a coalition operation, the MIC member nations are Australia, Canada, France, Germany, Italy, the United Kingdom, and the United States.
ARTICLE II: AIM
2. The aim of this Statement of Cooperation is to articulate for all participants the desire and direction of the CCEB and MIC leadership for a coordinated and cooperative approach to issues of mutual interest and concern.
ARTICLE III: STATEMENT OF COOPERATION
3. We ENDORSE the Statement of Cooperation as an enduring symbol of our common desire to develop, maintain, and enhance cooperation at all levels between staff of each Participant on issues of mutual interest or concern.
4. The MIC SUPPORTS the CCEB position as a leader in developing multinational C4 systems interoperability.
5. The CCEB SUPPORTS the MIC position as a leader for coordinating and facilitating courses of action to address interoperability issues, which will contribute to more effective coalition operations
6. We INTEND that the CCEB will fully support the activities of the Operations Support MIWG.
7. The CCEB INTENDS that non-CCEB members of the MIC will be invited to participate in those CCEB groups directly involved in MIC directed activities.
8. We INTEND that New Zealand is granted observer status at MIC meetings.
9. We INTEND that the CCEB will be represented and provide status updates at the MIC, MIWG, and Steering Group meetings as required.
10. We INTEND that the MIC will be represented and provide status updates at CCEB Board, Executive Group, and Working Group meetings as required.
11. We SUPPORT the exchange of information on ongoing or proposed tasks and INTEND that the outcomes and recommendations from the joint cooperative activities will be freely available for consideration and implementation, if appropriate, by both Participants, whether or not they were active participants in the activity.
12. We INTEND that this Statement of Cooperation is non-binding in law.
13. We INTEND that this Statement of Cooperation will enter into effect following endorsement of and signature by the Chair or Senior Principal on behalf of each of the Participants.
xviii
UNCLASSIFIED
xix
UNCLASSIFIED
INTENTIONALLY BLANK
20
UNCLASSIFIED
CHAPTER 1
AMERICAN, BRITISH, CANADIAN AUSTRALIAN AND NEW ZEALAND ARMIES PROGRAM History Of The Program 101. The American, British, Canadian, Australian and New Zealand Armies' Program (ABCA Program) originated as a result of the close cooperation that developed between the Allied Armies during World War II. This relationship was formalized in 1947 when the Plan to Effect Standardization was initiated between the Armies of the United States, United Kingdom and Canada. The ABCA Program was formally established on 12 December 1949, and in 1954, the plan was progressed into the Basic Standardization Concept. In 1963, Australia joined the organization, and in 1964, the Basic Standardization Agreement (BSA 64) was ratified by the four participating Armies. BSA 64 serves as the current legal foundation for the ABCA Program. New Zealand gained observer status in 1965 and was admitted as a full program member in 2006. The USMC became associate members within the US delegation in 2004. Mission 102. The ABCA Mission is: To optimize ABCA Armies interoperability in order to deliver success on coalition operations. This mission is achieved through cooperation and collaboration in the continuous pursuit of standardization and mutual understanding Organization of the Program 103. The governance of the ABCA Armies Program is depicted at figure 1.
Figure 1 Governance Structure of ABCA
104. Executive Council (EC). The EC, typically at the Vice/Deputy Chief of Staff of the Army level, governs the Program. Informed by national perspectives, operational experience, Program reports, coalition lessons and joint/interagency/multinational (JIM) considerations, the EC provides strategic guidance, endorses Program activities, ensures commitment of the related national resources, and guides the work of the National Directors.
21
UNCLASSIFIED 105. National Directors (NDs). NDs, typically at the one or two-star level, are responsible to the EC for providing direction and operational oversight of the Program by determining, shaping and monitoring Program activities, including prioritization of effort, authorization of tasks and commitment of resources required to achieve the intent of the ECs strategic guidance. At the Programs Annual Meeting, the NDs assign Interoperability Objectives (IOs) to the Capability Groups and then make approval decisions on the tasks proposed by the Groups to address those IOs. 106. Program Office. The Program Office is responsible to the NDs for the management of the Program through coordination of Program activities and groups, publication and dissemination of ABCA products, collection and dissemination of coalition lessons, liaison with JIM agencies/fora, and provision of Program secretariat support. 107. Capability Groups (CGs). CGs comprise national representatives who are knowledgeable in their specific capability area. CG leadership is allocated to a Colonel from one of the Armies on a standing basis. They seek to optimize coalition interoperability within their capability area in accordance with the interoperability objectives assigned by the National directors. They conduct interoperability gap analysis, propose tasks to mitigate identified gaps, establish Project Teams to conduct approved tasks and manage the Program products that belong to the CG. Below is a description of the interoperability aspects of the CGs. a. CG Command. All aspects of the command and control of coalition forces within an operational battlespace, including all of the related processes, systems and tools ( including communication and information systems), such as planning, decision-making, information exchange, battlespace management and situational awareness. b. CG Sense. All aspects of the provision of knowledge and understanding of the coalition operational battlespace, especially of adversaries, neutrals, non-combatants, weather and terrain. It includes all of the related processes, systems and tools (including electronic warfare) that manage and integrate coalition data collection assets and that fuse and analyze the respective output. c. CG Act. All aspects of the employment of coalition forces and the exercise of coalition combat power, especially through the synchronization of manoeuvre, firepower and information, within a tactical or operational battlespace to achieve desired effects.
d. CG Shield. All aspects of the protection of coalition forces, resources and facilities in order to ensure the forces survivability, conserve its fighting potential, facilitate its freedom of action and degrade the adversaries ability to carry out hostile actions. e. CG Sustain. All aspects of the provision, distribution and management of the logistics, personnel and other support required to maintain and prolong the operations of a coalition force within an operational battlespace. 108. Support Groups (SGs). SGs comprise national representatives who are knowledgeable in the Groups support area. SG leadership is allocated to one of the Armies on a standing basis and typically assigned to a Colonel by that Army. SGs are primarily focused on providing advice and support to the Program, especially to the CGs, in relation to their support area. SGs also propose tasks, establish Project Teams and manage their Program products. a. SG Futures. SG Futures is responsible to the NDs to advise the Program on the likely nature of coalition operations and security environment in which the ABCA Armies can expect to operate, out to twenty years, in order to provide a framework for the analysis and development of coalition interoperability. b. SG Science and Technology (S&T). SG S&T is responsible to the NDs to advise the Program from and research and development perspective on scientific, technological and materiel issues. The group will inform the National Research and Development communities of ABCAs areas of interest. c. SG Exercise and Experimentation (E2). SG E2 is responsible to the NDs to provide advice and support to the Program concerning the planning and coordination of ABCA exercise and experimentation activities, for the collection, analysis and sharing of
22
UNCLASSIFIED coalition lessons for operations, exercises and experiments and to provide operational analysis and research support as required. 109. Project Teams (PTs). PTs are established by the NDs and are each responsible to an applicable CG for the development and delivery of an ABCA product (e.g., Standard, publication, report, database and architecture) intended to mitigate an identified interoperability gap. Once the assigned deliverable has been achieved, the PT is disbanded, transformed into an Information Team or assigned a new task, as appropriate. 110. Figure 2 depicts the structure of Capability Groups (CGs) and Support Groups (SGs) who report to the National Directors. Project and Information teams are the final level of the ABCA structure.
Figure 2 Capability and Support Groups 111. Information Teams (ITs). ITs are established by the NDs and overseen by a Program Office SO1 for the exchange information intended to optimize ABCA interoperability as well as support Army force development in a specified subject area. ITs are not resourced by the Program to conduct physical meetings or carry out other related activities. 112. National Coordinators (Coords). National Coords are the single point of staff contact for the ABCA Program in the Armies. They are responsible to their own Army's ND for overseeing, coordinating and facilitating that Army's participation in the Program. 113. Standardization Representatives (STANREPs). STANREPs are officers appointed by an Army to be based and accredited in one of the other ABCA nations, under the authority of BSA 64, for the purpose of facilitating information exchange, materiel transactions and standardization activities. Program Planning System (PPS) 114. The ABCA PPS is an annually recurring planning cycle that assesses the Armies' interoperability status, receives Strategic Guidance, identifies interoperability gaps, determines gap mitigation tasks, prioritizes these tasks, implements the tasks that can be resourced, and assesses the interoperability status again for the start of the next cycle. Figure 3 provides a graphical depiction of the ABCA annual cycle. This system comprises the following elements: a. Program Assessment. From the end of the previous years Annual Meeting until the start of the next one, the Armies consider the coalition interoperability issues that need to be addressed. To assist, the Program Office collates relevant information (e.g., lessons collected from operations, exercises and experiments; outputs from other JIM interoperability fora) into Program inputs, which are distributed prior to the EC/ND meetings in Oct/Nov. Subsequently, the Armies submit and exchange their national inputs prior to the NDs Video teleconference (VTC) in Jan/Feb.
23
UNCLASSIFIED b. Strategic Guidance. The NDs issue revised Strategic Guidance for the next Program Year prior to the start of the Annual Meeting. c. Interoperability Objectives (IOs). The NDs consider the Program and National Inputs and then translate the Strategic Guidance into a set of more specific IOs, which they issue to the CGs and SGs prior to the Annual Meeting.
d. Task Proposals. During the Annual Meeting, the CGs/SGs conduct interoperability gap analysis relevant to the IOs in order to determine possible tasks that will mitigate the gaps they identify. To conduct the gap analysis, CGs/SGs rely on their expertise in their capability/support area, participate in cross-walks with the other CGs/SGs and are mentored by the NDs. e. Program Plan. At the end of the Annual Meeting, the CG/SG leaders present their groups task proposals to the NDs, who approve, adjust, defer or disapprove them based on resources and priorities. The Program Office collates the Strategic Guidance, IOs and approved tasks into that years Program Plan, which is signed off by the NDs and serves to authorize the Programs work for the year. f. Project Teams (PTs). For each task that is approved, a PT is established by the tasks respective CG/SG. Each PT is issued terms of reference (TOR) by the CG/SG Leader and populated, with the assistance of the National Coords, with national representatives. If authorized, PTs meet physically in the nation that has been authorized to host their meeting(s) during the year.
g. Progress Monitoring. Throughout the year, PT Leaders apprise their CG/SG Leader of the PTs progress on the conduct of the task. In turn, CG/SG Leaders advise the NDs of the progress of their PTs in Jun/Jul (NDs VTC), in Oct/Nov (EC and NDs meeting) and in Jan/Feb (NDs VTC). At any of these opportunities or secretarially otherwise, a task can be adjusted or cancelled based on the recommendation of the CG/SG Leader and the approval of the NDs. Additionally, new tasks can be proposed and approved along the same lines. h. Task Completion. Upon completion of their task and in line with the deadline stated in their TOR, PTs submit their final product to the Program Office for dissemination, review, approval and/or ratification, depending on the requirements of the product. The PT is then disbanded.
Figure 3 ABCA Annual planning cycle
24
UNCLASSIFIED Program Elements 115. Program Products. ABCA products are formal outputs of data or documentation from the Program that are intended to enhance interoperability amongst the ABCA Armies. ABCA products are owned by respective CGs/ SGs, who are responsible for their products accuracy, currency, quality and relevance. The CGs/SGs are assisted by the Program Office, who acts as the configuration manager of the products. Types of ABCA products include: a. ABCA Standard. An ABCA Standard is a formal agreement that has been ratified by three or more of the ABCA Armies and that defines the levels of standardization or interoperability to be achieved and maintained in a specified materiel, procedural or technical area. b. ABCA Publication. An ABCA Publication is a document intended to inform ABCA Armies about materiel, procedural and/or technical interoperability matters. It does not require ratification by or compliance from the ABCA Armies. Examples of ABCA Publications are handbooks, guides and planning checklists. c. ABCA Architecture. An ABCA Architecture is a detailed, hierarchical description of a system that identifies the systems overall structure, the interaction and interconnection of its sub-components, and its operational processes.
d. ABCA Database. An ABCA Database is a multi-use aggregation of data, relevant to enhancing the interoperability of the ABCA Armies and organized so that its contents can be readily accessed, managed and updated. e. ABCA Report. An ABCA Report is a formal paper that provides an account of an event, the analysis of data or a problem, or the discussion of a position or an issue.
116. Biennial ABCA Activity. An ABCA Activity can range from a field exercise (FTX), command post exercise (CPX), experiment, seminar wargame, seminar workshop, through to a technical demonstration. A major ABCA activity is held every two years, hosted by each Army in turn. The primary purpose of these biennial activities is to identify interoperability gaps and potential solutions, inform the development of ABCA products and foster understanding, cohesion and collaboration between ABCA Armies through collaboration and participation in the activity. 117. Leveraged Exercises and Experiments (E2). In addition to the ABCA activities described above, the ABCA Armies may take advantage of other existing bilateral/multilateral exercises/experiments or agree to participate in remotely conducted experiments that can be used to achieve ABCA Program objectives. The E2SG maintains a database of national and multinational exercises and experiments in which one or more of the ABCA Armies is a participant. This database provides the Program and Armies with an awareness of activities that are potentially available to be leveraged. Such leveraging ranges from reviewing post-activity reports, through insertion of objectives, to direct participation in the activity. Of course, any leveraging intended by the Program and/or nonparticipating Armies is not guaranteed and must be requested from the host Army in accordance with the protocol required. 118. Coalition Interoperability Lessons. The Program exploits coalition lessons from operations, exercises and experiments, focusing on lessons related to interoperability between ABCA Armies. These lessons are processed as follows: a. Collection. The Program seeks to collect coalition lessons actively through the deployment of lesson collection teams and passively through the review of published reports. The Lessons National Points of Contact (NPOCs) and the SO1 COps are the key conduits for the collection of coalition lessons for the Program. The E2SG maintains a Lessons Critical Topic List (CTL) to help focus collection efforts. b. Analysis. Although the Program benefits from the collection and dissemination of raw data and observations, it is best served when analysis is conducted to process those data and observations into insights (i.e., trends) and lessons (i.e., proposed solutions). When appropriate, PTs are established or conferences are convened to conduct this analysis. The
25
UNCLASSIFIED Program conducts a large Coalition Lessons Analysis Workshop in odd-years and a smaller Interoperability Lessons Review Board in even years. c. Dissemination. Coalition lessons are collated by the Lessons NPOCs and passed to the SO1 COps and/or downloaded on the Coalition Operations Lessons Learned (COLL) website run by the US Center for Army Lessons Learned (CALL). Analyzed coalition lessons are provided where possible in the Program Inputs and at the Annual Meeting.
119. ABCA Information Exchange List. The ABCA Information Exchange List comprises information items (e.g., reports, documents) identified and cleared by the source Army for free access by the other ABCA Armies. 120. Reciprocal Use of Materiel (RUM) Loans. BSA 64 makes provision for the loaning of equipment between ABCA Armies for use in test, evaluation, research, development or standardization activities that promote coalition interoperability. Although facilitated by BSA 64, RUM Loans are bilateral in nature. In the US, RUM Loans are carried out using Section 65 of the US Arms Control Export Act. 121. ABCA Web site. www.abca-armies.org ABCA maintains both a public and a private web site. The Private site is password protected and registration is conducted on-line. This site provides extensive information about ABCA such as key source documents, information exchange list, calendar of events, whats new section and an extensive repository of downloadable reports, standards, databases, publications and handbooks. It also provides easy access to ABCA contact information, detailed project team information, documents and joining instructions as well as detailed information about Exercise and Experimentations. Questions/comments about the ABCA web sites can be directed to the ABCA Chief Clerk or the Executive Officer.
26
UNCLASSIFIED
CHAPTER 2
AIR AND SPACE INTEROPERABILITY COUNCIL
Introduction 201. The Air and Space Interoperability Council (ASIC) is an active and productive international organization which was established in 1948 with the original objective of ensuring that in any future conflict
there will be no material or technical obstacles to full cooperation for mutual defence between the contributing countries and to obtain the greatest possible economy in the use of their combined resources and effort. Today, the air forces of the 5 member nations of Australia, Canada, New Zealand, the United Kingdom and the United
States strive to improve interoperability between coalition expeditionary forces in both peace and war. 202. The formal construct and governing principles are outlined in the ASIC Master Agreement document. Each member nation supports ASIC with a small group of people from the National Directors (flag rank), through staff and project officers at appropriate levels. The Management Committee in Washington DC is permanently manned and provides the central coordinating function. All participants provide expertise to the organization and the Working Groups, and benefit through extensive information exchanges that can only be achieved through international exposure. Many of the ASIC interoperability efforts, specifically the internationally adopted Air Standards (AIR STDs), are incorporated into respective national documents. Mission 203. To enhance current and future Air and Space warfighting capabilities through joint and coalition interoperability. Vision 204. Allies striving towards fully interoperable and integrated Air and Space forces.
Capstone Concept 205. The ASIC Capstone Concept is the strategic document out of which all underpinning ASIC documents, activities and products are developed. It is reviewed annually at the National Director level to ensure continuing relevance, and provides the way ahead for interoperability development. The document touches on where the organization has been (the past), what has changed (transformation), where it is going (the future), and how ASIC will perform its mission (the present). ASIC Interoperability Framework 206. The ASIC Framework recognizes that Air and Space Power is applied across the full spectrum of warfare. The following are incorporated into the framework construct: a. b. c. d. e. f. Measuring degrees of interoperability (required and achieved), Identifying interoperability gaps/shortfalls, Clearly identifying priority areas for interoperability development, Harmonizing tasks with the work being performed by other interoperability fora, including regular liaison with NATO, ABCA, AUSCANNZUKUS, EAG and JAPCC. Allocating appropriate resources to agreed tasks, and Employing feedback mechanisms to ensure that published products meet the coalition warfighters needs.
The United States Navy is also a full member of ASIC

27
UNCLASSIFIED Warfighting Functions and Capability Elements 207. The fundamental building block for this Interoperability Framework is an agreed set of Warfighting Functions. Taking an Effects Based approach as well as acknowledging each member nations requirements, these warfighting functions are: a. b. c. d. e. Force Application (FA) Force Protection (FP) Air Mobility (AM) C2 & ISR Agile Combat Support (ACS) Air and Space Medicine (ASMG) Fuels
3
208. Interoperability must also be considered from a whole -of-capability perspective. ASIC employs Concepts/Doctrine/Experimentation, Organization, Training and Education, Personnel, Equipment Information, and Facilities capability elements to ensure that any analysis of interoperability considers all contributing components. The Time Element 209. The focus of ASIC interoperability covers the full time spectrum including Forces in Being, Developing Forces (out to five years), and Future Forces (six to 11 years). The latter two time periods enable the potential to build in interoperability from the ground floor. ORGANIZATION Management 210. The ASIC nations have interoperability representatives at three levels: National Directors flag rank; the Management Committee Lieutenant Colonel/Wing Commanders; and the National Program Managers - Lieutenant Colonel/Wing Commander or Major/Squadron Leaders. Chairmanship of the ASIC and the Management Committee rotates annually after the National Directors meeting. National Directors 211. ASIC Air Forces' Chiefs of Staffs have each appointed a flag rank officer to oversee national interoperability matters; their post title is ASIC National Director. The National Directors meet annually to formulate policy and direct activities of the ASIC organization. They direct the mission, goals, and tasks of ASIC through the biennial Task List. Management Committee 212. The National Directors' policies are implemented by the Management Committee (MC). The MC Members function collectively as an international secretariat and individually as Chairmen for the Working Groups and the Steering Group. The MC is permanently based in Washington, DC. National Program Managers 213. The National Program Managers (NPMs) are the coordinators of the national ASIC program and advisors and executive assistants on ASIC matters to their National Directors.
The Air and Space Medicine Group and Fuels Group are independent single focus groups administered as WGs.
28
UNCLASSIFIED
Figure 2.1: ASIC International Organization
Steering Group 214. The ASIC Steering Group (SG) provides oversight and management of ASIC and is comprised of the MC and national representatives from the warfighting functional areas. To assist the SG with Project Directive development, the SG may request additional US SMEs or other fora involvement if there are likely to be Joint Projects. The SG meets in Washington DC, yearly to prepare / review the prioritized Task List which, when endorsed by the National Directors, provides the tasking direction for the Working Groups and Project Groups. Working Groups 215. The ASIC Steering Group (SG) provides oversight and management of ASIC and comprises the MC and NPMs. To assist the SG with Project Directive development, the SG may request additional SMEs or other fora involvement if there are likely to be Joint Projects. The SG meets yearly, prior to the National Directors Meeting, to prepare and review the prioritized Task List which, when endorsed by the National Directors, provides the tasking direction for the Working Groups (WG) and Project Groups. Working Groups 215. The tasks of ASIC are carried out by seven permanent functional area WGs. A listing of each WGs current projects, information exchanges and documents, are published in the ASIC Task List. Working Group Management Plans, detailed Project Directives, and a record of WG activity, are recorded in the Working Group Meeting Reports. Individual WGs provide management oversight of Project Groups that are stood up as required. The Working Groups are: a. b. c. d. e. f. g. Force Application (FA) Air Mobility (AM) C2 & ISR Force Protection (FP) Agile Combat Support (ACS) Air and Space Medicine Group (ASMG) Fuels Group (FG)
29
UNCLASSIFIED 216. At the national level, each Working Group has one Head of Delegation (HoD) who is responsible to the National Program Manager for national issues and to the WG Chairman for actions arising from Working Group meetings. The MC may request additional Subject Matter Experts (SMEs) to meet specific WG tasking. Nations may appoint SMEs to assist with specific project action and development. ASIC tasks may be addressed at either the Working Group level or by a specific Project Group. Working groups meet annually. A meeting schedule is available on the ASIC public website Project Groups 217. Project Groups (PGs) are subordinate to the Working Groups and differ in that they are established temporarily for the purpose of progressing specifically approved tasks over a defined period. PGs are normally made up of SMEs, and can include membership from other Interoperability Fora, should a given project so require. The PG executive document will be the specific Project Directive that is published in the Task List. 218. As a rule, the Project Group members will meet for three days following the aligned Working Group Meeting. Project Groups may also meet at stipulated times outside of the WG meeting or may conduct meetings virtually on the ASIC private website. Some PGs may only be stood up virtually to address relatively minor interoperability issues. While the objective of any PG meeting is to resolve an interoperability problem, the actual product may be an international agreement in the form of an Air Standard, Advisory Publication, Information Publication, or a scoping paper for a proposed larger interoperability task. ASIC WORK CYCLE National Head of Delegation Meetings (HoD) 219. Individual nations host their own annual Heads of Delegation meetings where nations discuss and forward their Top 5 interoperability concerns, independent of and in addition to the survey process. The ASIC Interoperability Survey is administered biennially at the HoD meetings. The HoDs are the representatives to the ASIC WGs. Project Development 220. ASIC uses lessons learned to determine interoperability gaps and shortfalls. Projects are proposed nationally and developed by the Steering Group into prioritised ASIC interoperability tasks. The tasks are scoped and described in Project Directives. The Steering Group recommendations are reviewed and approved by the National Directors and incorporated into the Task List. ASIC Task List 221. The ASIC Task List is published every year. It includes strategic direction and the work plan, consisting of face-to-face projects, virtual projects and the document management plan. A project is used by WGs to organize tasking needed to address identified interoperability gaps. The project provides the means by which inputs from all interested agencies may be collated and developed into usable products such as Air Standards, Advisory Publications, Information Publications and Handbooks. Projects are normally established for the development of ASIC documents but may include other activities such as participation in exercises. These activities or products must be achievable within a reasonable timeframe (nominally one meeting cycle) to render a project active. They may be used also as a means for information exchange to scope an interoperability gap. Each Project has its own statement of deficiency, action to address the deficiency, resource requirements, milestones and tasks, metrics, validation and feedback procedures. ASIC Document Management Plan 222. ASIC maintains an extensive library of current Air Standards (AIR STDs), Advisory Publications (ADV PUBs), and Information Publications (INFO PUBs). All documents fall into a structured five year plan, with review cycles of individual publications ranging from annually to once every five years. Most document reviews are conducted virtually through relevant WGs. This formal process ensures that ASIC products remain both current and valid. All ASIC documents are available on the ASIC Private Website. Test Project Agreement
30
UNCLASSIFIED 223. The ASIC Test Project Agreement is a formal addendum to the ASIC Master Agreement that allows for the free exchange/loan of military equipment between ASIC nations for the purpose of testing and evaluation. It has proven to be an effective vehicle for the rapid introduction of new equipment/technologies.
Figure 2.2: ASIC Work Cycle
ASIC WEBSITES 224. ASIC is currently transitioning to new websites. The new Private Website is a password protected Sharepoint service hosted by the NZDF. It provides a publications library, details of projects and collaborative working areas. It is the primary vehicle for the management of projects and development of publications. Access may be requested through asicad01@pentagon.af.mil. A Classified Website is being developed, to be hosted on SIPRNET, and a Public Website designed to educate and raise awareness is also planned.
31
UNCLASSIFIED
INTENTIONALLY BLANK
32
UNCLASSIFIED
CHAPTER 3
AUSCANNZUKUS MARITIME INFORMATION WARFARE ORGANISATION Introduction 301. Early in World War II the lack of communications interoperability between Allied Forces became a matter of concern for all nations. During March 1941 the first high-level proposals to formally structure combined operations between the United States and the United Kingdom were considered. These discussions were the genesis of the current Combined Communications Electronics Board (CCEB). The origins of the AUSCANNZUKUS organisation arose from dialogue between Admiral Arleigh BURKE, USN, and Admiral Lord Louis MOUNTBATTEN, in 1960. Their intention was to align naval communications policies, and prevent, or at least limit any barriers to interoperability with the imminent introduction of sophisticated new communications equipment. AUSCANNZUKUS matured to the current five-nation organisation in 1980 when New Zealand became a full member. This organisation is firmly established and liaises closely with Washington based management groups of the Combined Communication Electronics Board (CCEB), American, British, Canadian & Australian (ABCA) Armies Program, Air & Space Interoperability Council (ASIC), The Technical Co-operation Program (TTCP) and the Quadrilateral Logistics Forum (QLF). 302. During a strategic review in 2011, AUSCANNZUKUS expanded its remit from Command and Control, Communications and Computers (C4) to Information Warfare (IW), the AUSCANNZUKUS definition of which is: The provision, assured use and protection of information, processes, systems, and networks, and the limiting, degrading and denying of that of our adversaries, to achieve operational advantage in the battlespace as applied to the fields of Command & Control, Communications, Computers, Intelligence, Surveillance & Reconnaissance (C4ISR) and Electronic Warfare (EW) Vision 303. The Organisations vision is: To deliver battle winning maritime IW Interoperability. Strategies 304. AUSCANNZUKUS strategies are to: a. Establish IW policy and standards. b. Identify IW interoperability requirements and risks. c. Identify, develop and utilize new technologies.
d. Exchange information on national IW capabilities, plans, and projects. e. Leverage exercises, experiments and demonstrations to deliver capability. f. Inform and influence multi national defense fora.
Guiding Principles 305. The Guiding Principles developed by the Supervisory Board are designed to provide focus and definition to the Visions and Strategies. a. The focus of all activities is to be on the requirements of the naval warfighter. b. All knowledge-sharing initiatives are to aim at providing innovative options, which are affordable to all AUSCANNZUKUS navies. c. Purpose 306. The purpose of AUSCANNZUKUS is to: a. Promote interoperability between member nations by formulating policy on agreed standards and minimum operational capabilities;
33
All relevant information is to be shared with appropriate joint and combined organisations.
UNCLASSIFIED b. Exchange information on issues of interoperability and information management; c. Mission 307. The AUSCANNZUKUS organisations mission is: To foster knowledge sharing that enables the warfighter to successfully complete missions across the spectrum of joint and combined operations. Organisation 308. AUSCANNZUKUS is a consensus-based body with no authority to impose decisions on member nations. The authority to exchange operational and research information within the organisation was established under the auspices of the ABCANZ-5 Information Exchange Project. Currently, there are two mechanisms for information sharing: a. The first, which primarily covers operational information, is the Combined Joint Multilateral Master Military Information Exchange Memorandum of Understanding (CJM3IEM), which came into effect on 29 June 2004. The specifics of information sharing are detailed in an Information Exchange Annex, the most recent of which is Combined Joint Military Information Exchange Annex (CJMIEA) O-AUSCANNZUKUS-061, which was signed in June 2006, and extended for one year in 2011 pending the outcomes of the strategic review; and b. The second, which deals primarily with Research and Development, is the ABCANZ Multilateral Master Information Exchange MOU (MMIEM), which came into effect on 12 February 1996. The Information Exchange Annex for this agreement is R-ABCANZ-07-1, which was signed in May 2007. 309. The current AUSCANNZUKUS Maritime IW Organisation consists of the Supervisory Board (SB), the Executive Steering Committee (ESC), the Operations Working Group (OWG), the Technical Working Group (TWG), the Permanent Support Coordination Group (PSCG), and the Experimentation Working Group (EWG). Ad Hoc Working Groups (AHWG) may be formed as required to progress specific tasks. The current organisation is at Figure 3.1. 310. A Flag Officer level Supervisory Board drawn from national policy or operational requirements authorities heads the organisation. The Supervisory Board meets as required to endorse policy and resource allocation proposed by the ESC, and to provide strategic guidance to the organisation. 311. The ESC (Navy Captain (O6) level) is subordinate to the SB and meets biannually to address and resolve technical and operational interoperability issues in response to SB tasking. The ESC is responsible for establishing priorities and making recommendations to the SB to ensure essential elements for AUSCANNZUKUS interoperability are identified, addressed and resolved. 312. The Maritime Cryptologic Committee (MCC) is a Five Eyes signals intelligence (SIGINT) organisation which comes under the sponsorship of the SB, with representation through the ESC. This arrangement assures 5-Eyes Intelligence interoperability, promotes improved network coherence and will lead to enhanced operational effectiveness. 313. The TWG (O4/O5 level) is responsible for providing technical support on operational interoperability issues to the SB, ESC and OWG. Technical support to the Working Groups is provided on an as required basis. Formal TWG meetings are held prior to the ESC meetings and are normally co located. TWG representatives provide the technical composition of the ESC. 314. The OWG (O4/O5 level) is responsible for representing identified Warfighter requirements to the SB and ESC. It identifies potential interoperability shortfalls between A-Z Nations and provides feedback on current operational IW matters. The OWG also assists in implementing A-Z policy for maritime operations. 315. The PSCG (consisting of representatives from Washington Embassies and OPNAV N2N6 staff, and permanently chaired by OPNAV N2N6F423, a UK PEP position) is responsible for supporting and maintaining AUSCANNZUKUS between meetings and coordinating the SB and ESC agendas. Directed by the ESC, the PSCG are required to ensure the completion of all tasking in timely manner. Though liaison is encouraged at all levels of the organisation, the PSCG is responsible for maintaining a close
34
Provide a forum to highlight maritime IW issues to national authorities.
UNCLASSIFIED liaison with other Washington-based interoperability fora with the aim of achieving enhanced operational effectiveness during joint and combined operations and the efficient use of limited resources. PSCG meetings are held in the Washington DC area as required, but normally every four to six weeks. Liaison Officers from other interoperability fora have a standing invitation to attend these meetings. 316. The EWG is tasked with advancing the A-Z vision through investigating solutions to interoperability risks, and presenting them as options for adoption by the five navies. Guidance is given to the EWG from the SB and ESC through an Experimentation Plan in order to align the desired outcomes with the overall direction of the organisation. The EWG meets as required by its experimentation schedule, which is currently primarily based on the US Fleet Forces Command Trident Warrior activity. The EWG is chaired by the incumbent of OPNAV N2N6F4231, a Canadian liaison position, and is composed of representatives from nations actively participating in the experimentation for that period. 317. Ad Hoc Working Groups may be formed to address specific interoperability issues in detail, and will be issued Terms of Reference detailing the required output. Only the SB and ESC have the authority to convene AHWGs 318. The Staff Officer AUSCANNZUKUS is the only permanently assigned staff member of the organisation, and is based in OPNAV N2N6. The position is filled on a rotational basis by AUS, CAN, NZ and UK.
Figure 3.1: AUSCANNZUKUS Maritime IW Organisational Structure 319.

GROUP Supervisory Board (SB) Executive Steering Committee (ESC) Maritime Cryptologic Committee (MCC) Technical Working Group (TWG) Operations Working Group (OWG)
A summary of the AUSCANNZUKUS organisation schedule is shown at Figure 3.2.

TIMING Normally annual, after Apr/May ESC Biannual meetings: 5 days in Mar/Apr 5 days in Oct As required, normally for 5 days prior to ESC As required, normally for 3-4 days prior to ESC As required, normally for 3-4 days prior to ESC LOCATION Host nation CHAIRMAN U.S. member MINIMUM REPRESENTATION Principals from Five Nations ESC Chairman Five nations WG Chairmen Five nations Determined annually Host nation
Host nation (Mar/Apr) Host nation in Washington DC (Oct) Host Nation
Host Nation (changes o/c Apr/May meeting)
Dependent on tasking and support required, normally in ESC location Dependant on tasking and support required, but normally in ESC location
35
Four nations
Host nation
Four nations
UNCLASSIFIED
GROUP Permanent Support and Coordination Group (PSCG) Experimentation Working Group (EWG) Ad Hoc Working Groups (AHWG) TIMING Monthly or as required LOCATION Washington DC CHAIRMAN Incumbent of the OPNAV N2N6F423 position Incumbent of the OPNAV N2N6F4231 As directed by parent body MINIMUM REPRESENTATION Four nations
As required by experimentation activities As directed by parent body
Figure 3.2: The AUSCANNZUKUS Organisation Schedule
320. The SB, ESC, TWG, and OWG meetings are hosted on an annual rotation basis. A list of upcoming meetings, including location, can be found on the AUSCANNZUKUS website (https://community.apan.org/international/auscannzukus). 321. The management of work undertaken by organisation is coordinated using the AUSCANNZUKUS Interoperability Reporting System (AIRS), the One Page Plan (OPP) and the A-Z Action Matrix. AIRS provides the organisation with an overview of its ability to meet agreed Information Exchange Requirements (IERs) (or risks to A-Z achieving its vision of delivering battle winning maritime IW interoperability), and prioritises them for consideration by the PSCG for inclusion in meeting agendas. AIRS is updated annually by member nations. The OPP details the Supervisory Board overarching objectives, ESC priorities based upon national and organisational IW risks, and ESC tasks to subordinate working groups that support the organisations mission. The OPP is reviewed biannually by the ESC and endorsed annually by the SB. To support the OPP, action items assigned by the SB, ESC or WG Chairmen are tracked within an action matrix maintained by the Staff Officer A-Z. 322. A-Z aims to identify interoperability issues well in advance, and seek solutions. To this end, nations are responsible for identifying and bringing to the attention of the ESC key issues where interoperability could be compromised by the implementation of new technology or the removal of an old technology. Publications/Correspondence 323. The Staff Officer A-Z is responsible for the distribution, tracking and recording of A-Z publications and correspondence. Correspondence and dissemination of organisational information is conducted primarily through the restricted-access AUSCANNZUKUS homepage (https://community.apan.org/international/auscannzukus) and unclassified email. Classified information is disseminated via normal security procedures. 324. The address for the Staff Officer AUSCANNZUKUS is: Staff Officer AUSCANNZUKUS OPNAV N2/N6F4233 Room 1E275 Pentagon Washington, DC 20350-2000 Liaison 325. AUSCANNZUKUS recognizes the importance of liaison and actively encourages participation by other interoperability fora (e.g. ABCA, ASIC, CCEB, ICCWG, MIC, and TTCP) at AUSCANNZUKUS Working Group meetings (e.g. PSCG, AHWGs). Briefings by other interoperability fora occur annually at the Oct ESC meeting, with the PSCG Chairman providing an update at the Mar/Apr meeting. Flag level interaction is also considered important; therefore all fora are invited to brief at the SB. The SB encourages AUSCANNZUKUS attendance at all levels of other interoperability fora meetings, including the respective Principals meetings. 326. In December 1996 the first combined meeting of the Washington-based interoperability fora (ABCA, ASIC, AUSCANNZUKUS, CCEB, and TTCP) was convened. This meeting resulted in the
36
UNCLASSIFIED initiation of the Multifora meetings now held tri-annually. The purpose of these meetings is to maintain an understanding at the working level of the efforts and issues being addressed by each of the organisations. In addition to attending the Multifora meetings, the PSCG has Liaison Officers to other interoperability bodies as detailed in this Handbook, with the aim of improving information flow throughout the Washington based multifora. 327. In an effort to encourage a coordinated and co-operative approach to issues of mutual interest and concern, a non-binding Statement of Co-operation (SOC) was drafted and signed by the multifora. The SOC acts purely as a symbol of our common desire to develop, maintain, and enhance co-operation between the different organisations.
37
UNCLASSIFIED
INTENTIONALLY BLANK
38
UNCLASSIFIED
CHAPTER 4
COMBINED COMMUNICATIONS-ELECTRONICS BOARD Background and History 401. The Combined Communications-Electronics Board (CCEB) is a five-nation joint military communications-electronics (C-E) organization whose mission is the co-ordination of any military C-E matter that is referred to it by a member nation. The member nations of the CCEB are Australia, Canada, New Zealand, the United Kingdom and the United States of America. The CCEB Board consists of a senior Command, Control, Communications and Computer (C4) representative from each of the member nations. The members of the board are known as the CCEB Principals. 402. The first high-level proposals for a structure to formulate combined communications-electronics policy were exchanged between the UK and US in March 1941. These proposals led to the development of the Combined Communications Board (CCB) that held its first meeting under Lord Mountbatten in Washington, D.C. on 24 July 1942. CCB membership consisted of two representatives from the United States Army, two representatives from the United States Navy, three UK representatives and one representative each from Australia, New Zealand and Canada. The CCB grew to 33 sub-committees established to consider all communication specialist areas. 403. The CCB produced all combined communications-electronics publications used by the member nations. It also produced at that time more than two million additional copies, in 12 languages, for use by CCB allies. The work of the CCB continued after the war until 14 October 1949 when it was reduced in size and commitment with the formation of NATO and dissolution of the Combined Chiefs of Staff Organization. The United Kingdom Joint Communications Staff, Washington and the United States Joint Communications-Electronics Committee continued to meet on regular basis as the US-UK Joint Communications-Electronics Committee with representatives of Australia, Canada and New Zealand attending as appropriate. 404. Canada became a full member of the organization in 1951, Australia in 1969 and New Zealand in 1972 when the organization was renamed the Combined Communications-Electronics Board. In 1986 the CCEB broadened its TOR to include communication and information systems in support of command and control. 405. CCEB interoperability activities have always been coordinated with those of the North Atlantic Treaty Organization (NATO) and the US Military Communications Electronics Board (MCEB). Recently, increased attention is given to coalition C4 interoperability and provision of tangible deliverables intended to maximize coalition Warfighter effectiveness. This has led to a close relationship with the seven-nation Multinational Interoperability Council (MIC). 406. In 2001, the Vice/Deputy Chiefs of the CCEB nations agreed that the CCEB should take a leading role in facilitating coordination on C4 matters between the nations and their various single Service groups, clearly showing the high-level support that continues to be given to the CCEB in C4 interoperability coordination. CCEB Mission Statement To enhance C4 interoperability and capability for the defence forces of its member nations and to provide leadership and influence across the wider C4 community. Strategy for Achieving the Purpose 407. The CCEB enhances C4 interoperability and capabilities for its member nations and aims to influence the broader coalition community, at the strategic, operational and tactical levels. Key to success is the sharing of information for the benefit of the CCEB nations. Work is coordinated with the single Service fora, TTCP, MIC and NATO. The CCEB may take the lead on issues, or provide expert technical support to single Service organizations. Where appropriate and when agreed, an individual CCEB
39
UNCLASSIFIED
country may be designated as lead nation on a particular issue. This may occur when a nation has the greatest or most pressing need to set a standard that is needed for a national project. 408. Interoperability within the NATO alliance is an essential operational issue for three of CCE Bs member nations. CCEB has had a major positive impact on NATOs wider coalition C4 (technical) interoperability through the generation and distribution of procedural documents titled Allied Communications Publications (ACPs). NATO and many other nations have come to depend upon ACPs for their communications operations. The CCEB has thus become a respected communications standards organization. Continued maintenance and generation of new ACPs in response to adoption of newer technologies by nations militaries is a fundamental objective and core competency of CCEB, and vital to its relevancy in coalition operations. Resources 409. The CCEB has a permanent full-time staff of one officer - the Permanent Secretary (PermSec). All other personnel, including the Principals, members of the Executive Group (EG), the Washington Staff (WS), and all of the international members who work on issues of mutual concern, are drawn from national organizations on a part time basis. 410. The CCEB Annual Strategy, Roadmap and Management Plan provide details of specific tasks to be achieved, but the actual resource implications and their allocation must be planned for and provided by the participating nations. Organization 411. The nominated senior C4 Representatives of the individual national joint military C-E organizations are known as Principals. The term Board is used to describe the collective Principals. The term CCEB is used to describe the organiza tion as a whole, which consists of component groupings: Principals; Executive Group (EG); Washington Staff (WS); National Staff (NS); Working Groups (WGs); Task Forces (TF) and Tiger Teams (TT). 412. The component groupings of the CCEB are as follows: a. Principals. The Principals influence their respective nations to further the goal of C4 interoperability and are responsible for providing the necessary national resources. The Board meets annually to review the past year and to give direction for future activities. Video teleconferences (VTC) are programmed twice a year and as required to exchange information on specific issues. The Chair changes after each annual meeting in the order of Australia, Canada, the United Kingdom, New Zealand and the United States of America. b. Executive Group (EG). The EG co-ordinates the development of the policy and planning, progresses combined C-E interoperability, and prioritizes and recommends allocation of resources. The EG meets formally twice per a year. The EG Chair is linked to the Board Chair in that the Chair of both groups are provided by the same nation. Under the Statement of Cooperation between the Multinational Interoperability Council (MIC) and the CCEB, the EG forms the nucleus of the MIC Operations Support Multinational Interoperability Working Group (MIWG). c. Washington Staff (WS). The WS act for the Principals and the EG on matters not requiring Board or EG approval. The WS are the Washington DC based national representatives who are tasked individually in a manner determined by each nation and, to an extent determined within each nation, have national responsibility to their respective EG representative and Principal. The WS Chair is agreed by the EG with the provision that the WS Chair is not from the nation that is the current Chairman of Principals.
40
UNCLASSIFIED
d. National Staff (NS). The NS is a generic term to describe those staff members in national headquarters whose function is, to an extent determined within each nation, to support the Principal and national EG member on CCEB business. The NS do not meet as a formed body. e. Permanent Secretary (PermSec). The PermSec is the full-time CCEB staff member who co-ordinates the day to day business of the CCEB. The PermSec acts on behalf of and is tasked by the chairmen of the EG and the WS. The PermSec works from the Pentagon, where he is collocated with the Joint Staff J6 staff.
f.
Working Groups (WGs). A WG is established as a standing body to consider specific ongoing areas of interest. The current WGs are the: (1) (2) (3) (4) (5) Allied Communications Publications Working Group (ACPWG); Architecture Working Group (AWG); Messaging Working Group (MWG); Pegasus Operational Management Working Group; and Spectrum Working Group (SWG).
g. Tiger Teams (TT). TT s are established to address a specific issue that demands a greater depth of expertise but will be non-enduring. Currently, the CCEB has three TTs. (1) (2) (3) (4) Information Assurance Tiger Team (IA TT) Data Tagging and Labelling TT (DATAL TT); Pegasus Program Delivery Team (PPDT); and Public Key Infrastructure TT (PKI TT).
Liaison with other International Bodies 413. As the CCEB is the organization responsible for enhancing joint interoperability of allied C4, an important role for the CCEB is to interact closely on C4 matters with the Multinational Interoperability Council (MIC), NATO and other single Service and research organizations. To this end, the CCEB strongly promotes and encourages both formal and informal co-operative efforts with other joint and combined organizations. Wherever possible and when invited, the CCEB will be appropriately represented and will provide presentations at other groups' plenary meetings and subordinate group meetings (e.g. Multifora meetings). CCEB Organizational Diagram 414. The CCEB organizational diagram is shown in Figure 4.1 below.
41
UNCLASSIFIED
Principals
Executive Group (EG) Washington Staff (WS) National Staff (NS) Permanent Secretary (PS) Note 1: Program Delivery Team (PDT) Tiger Team (TT)
Working Groups (WG)
__Teams
see Note 1
F i Architecture (AWG) g u
Allied Communications Publications (ACPWG) Spectrum (SWG) Data Tagging and Labelling TT Pegasus Operational Management (POMWG) Messaging (MWG) Pegasus PDT
Public Key Infrastructure TT
Information Assurance TT
Figure 4.1: CCEB Organization CCEB Web Sites 415. The CCEB manages two unclassified web-sites. The Allied Communications Publications (ACP) web-site is accessible from the internet and provides access to all unclassified ACP publications. A members-only web site is hosted on the US DoD Intelpedia (wiki) web -site and provides CCEB members with a collaborative information sharing capability, at the unclassified level. Multifora members are able to access this Wiki site through sponsorship of a US Joint Staff representative. 416. The URL for the above web-sites are:
Public ACP Web-Site: http://jcs.dtic.mil/j6/cceb/acps CCEB Members Wiki-Site: www.intelink.gov/wiki/Combined_Communications_Electronics_Board_(CCEB)
42
UNCLASSIFIED
CHAPTER 5
INTERNATIONAL COMPUTER NETWORK DEFENSE (CND) COORDINATION WORKING GROUP Background 501. The ICCWG is composed of Information Assurance/Computer Network Defense (IA/CND) military representatives from Australian, Canadian, New Zealand, United Kingdom, and United States (AUSCANNZUKUS). The ICCWG is convened under the authority of the AUSCANNZUKUS IA/CND MOU. Subject to the disclosure policies of each Nation, classified information exchanged pursuant to the MOU may be classified as high as TOP SECRET. Role 502. The role of the ICCWG is to facilitate the conduct of multilateral cybersecurity operations and information sharing to ensure mutually assured national and combined defence information networks. Introduction 503. Each country's Defense Department appoints a National Lead to represent their nation in the ICCWG. The five National Leads and the ICCWG Secretariat are known as the Executive Committee. Each nation can also appoint military and/or civilian representatives to serve on the ICCWG's Working Groups (WG). 504. The WGs are tasked with operationalizing the goals and objectives set forth by the Executive Committee. Each SWG has a Lead. 505. Key to the operational success of the ICCWG is the establishment of relationships between the national military organizations responsible for the day-to-day defense of their respective nation's military computers and systems. 506. These organizations routinely communicate via secure and non secure means.
507. The ICCWG has made substantial strides in meeting the original intent of the MOU. Examples of these efforts include: Routine communication among CND watch officers at the operations level; Intelligence briefings to the ICCWG National Leads on the threats to national IT systems and infrastructures; Sharing of IA/CND policies and procedures; Exchange of technical vulnerability information; Opportunities to join in IA/CND training; Coordination and execution of multi-national exercises; Participation and contribution to the development of the annual International Computer Defense Workshop. Scope 508. The ICCWG develops and maintains multilateral cybersecurity protocols and procedures, including: coordination of any multilateral cybersecurity incidents (including such things as cyber intrusions, data spills, and unauthorized disclosure of information); exchange of technical vulnerability assessment information; sharing of cybersecurity data to assist participants to enhance protective measures against cyber threats; and, sharing information to improve overall situation awareness of cyber space. The ICCWG also coordinates and execute multinational cybersecurity exercises to develop and
43
UNCLASSIFIED
test combined cybersecurity tactics, techniques and procedures; provides cyber technical security input and guidance on network architectures; develops cyber security system standards; and, provides combined cybersecurity advice and guidance. Goals 509. The goals of the ICCWG are to: improve situational awareness that enables near real-time analysis of cyber attacks and intrusions as well as the development of successful mitigation strategies; enhance preparedness in order to address emerging cyber threats; improve network security incident management that will work to interface national processes and procedures for collaborating on network security incidents in order to provide for coordinated CND response; leverage expertise and experience of each nation (including sharing IA/CND training, processes, procedures, IA/CND publications and policies, sharing of R&D, IA/CND tools & products, and the understanding of law enforcement/counter intelligence legal requirements); and, exercise operational IA/CND processes and procedures. Implementation Plan 510. The Implementation Plan provides specific objectives to the Working Groups to meet the Goals of the ICCWG. The Plan is a living document that will be modified by the Executive Committee as required. The Implementation Plan will guide and synchronize the implementation efforts necessary to achieve the Goals. Working Groups, for their part, raise to the Executive Committee potential risks and constraints as well as recommended options and solutions. Collaboration 511. The Executive Committee (EC) meets at least quarterly, once as an organized face-to-face EC meeting, and other times via teleconference or secure VTC. The ICCWG utilizes GRIFFIN (Pegasus) for secure email (w/ attachments) communication and information sharing. The primary collaboration method, aside from unclassified e-mail, is a restricted access, PKI enabled, unclassified collaboration website where each of the Working Groups maintains a presence in addition to the general ICCWG and EC information. Organization
44
UNCLASSIFIED
CHAPTER 6
MULTINATIONAL INTEROPERABILITY COUNCIL Background 601. The MIC (previously referred to as the Six-Nation Council) was first proposed during a symposium entitled C3I for the Coalition Task Force held in October 1996. Participating countries were Australia, Canada, France, Germany, the United Kingdom, and the United States. One of the major recommendations of the October 1996 symposium was to establish a Six-Nation Council to provide oversight of coalition interoperability and assist the implementation of approved actions. A second recommendation was the formation of Multinational Working Groups to generate issues and recommendations for the Six-Nation Council. 602. At the inaugural meeting in October 1999, the Council members agreed to change the name from the Six-Nation Council to the MIC, establish a charter, and begin working issues in a more formalized fashion. It was also agreed that flag/general officers from the J3/Operations Branch of each nations national defense headquarters should lead the MIC efforts for each member nation, and that the name of the Multinational Working Groups be changed to Multinational Interoperability Working Groups (MIWGs). In May 2005, Italy became the seventh member nation of the MIC. Purpose 603. The MIC provides a joint, multinational forum for identifying interoperability issues and articulating actions at the strategic and high operational level that, if nationally implemented by MIC member nations, will contribute to more effective coalition operations. The MIC is led by the senior operations officers of the member nations. The MIC focuses on identifying and addressing interoperability issues across the contemporary operating environment. The MIC addresses interagency and comprehensive approach activities that are key to planning and executing coalition operations. MIC has developed a formal Charter, a Strategic Guidance Document and Membership Policies and Procedures document to govern MIC activities. Membership 604. Each of the member nations is considered to be a potential Lead Nation of a future coalition or MN operation. It is desired that the MIC Principal be a flag/general officer from the operations branch of the MIC member nations national defense staff. Each member nation provides senior staff officers and officials to the MIWGs. Other nations and organizations (affiliate or observer category) participate, by invitation, in MIC/MIWG meetings to address common issues of mutual interest and/or to support a specific event to address interoperability challenges and/or leverage on-going MIC activities. Vision Statement 605. For the MIC to become a premier operator-led MN forum to promote interoperability among lead nation militaries, supported by interfaces to government and relevant non-government entities, to enable more effective and successful MN/coalition operations. Mission Statement 606. Provide an adaptive and agile framework to enable potential lead nations the opportunity to identify interoperability issues and articulate courses of action to set the strategic and operational level conditions for more effective coalition operations within and outside extant political alliances. Objectives 607. The MICs objectives are as follows: Develop, lead, communicate and assess interoperability from a Lead Nation perspective at the strategic and high operational level across all lines of development.
45
UNCLASSIFIED
Enhance coalition preparation by addressing all relevant MN interoperability issues from across the full spectrum of operations through the medium of coalition preparation, i.e., MIC input and influence on education, training and exercise programs at the appropriate level. Establish principles for effective coalitions by levering ongoing work within nations, alliances and international organizations to establish the foundation for coalition operations. Advance the Comprehensive Approach by acknowledging the increasing reliance on interagency cooperation involving militaries, other government departments (OGDs), international aid agencies, and non-government organizations (NGOs). Promote internal information sharing between member nations is key to the success and relevancy of the MIC. Promote external information sharing that allows the MIC to communicate its message and share its products with all potential coalition partners including militaries, OGDs, international aid agencies, and NGOs.
Areas of Interest and Scope 608. A main focus of the MIC is for the MIC Principals, in their role as senior operators, to address the multitude of interoperability challenges facing member nations individually and collectively in order to advance coalition building and operations. The MIC perspective is intended to represent that of the operational war fighter. Sustained areas of interest include: current and future coalition operations from a cross-functional perspective across all lines of development and employment.
609.
The MIC Scope diagram is shown in Fig 6.1.
46
UNCLASSIFIED
Figure 6.1 MIC Scope Organization 610. The MIC organization diagram is shown in Fig 6.2.
Figure 6.2 MIC Organization
611. Multinational Interoperability Working Groups (MIWGs). The purpose of each functional MIWG is to explore problems in coalition interoperability, identify and clarify impediments, and prepare prioritized recommendations for approval by the MIC Principals, for implementation by the MIC member nations. There may be multiple MIWGs working various coalition interoperability issues. Each MIWG is taskoriented in its approach to achieve a seven nation agreed position on the identified coalition interoperability challenge. MIWGs are comprised of representatives at the US O-5/O-6 level and NATO OF-4/OF-5 level from the member nations who present their national position in addressing the business of the MIC. Each member nation has at least one representative per MIWG. Other staff members from agencies within their national defense staffs may attend to support their countrys official representative. The MIC consists of two Standing MIWGs with different scopes, the Operations (Ops) and the Operations Support (Ops Sup) MIWG. Additionally, a Directed MIWG(s) is established on the direction of the Principals in order to address a specific or a group of specific tasks.
47
UNCLASSIFIED
612. MIC Executive Secretariat (MIC ES) staff. The MIC ES staff is a full-time permanent staff of five personnel who coordinate the day-to-day business activities of the MIC, MIC SG and the functional MIWGs. The MIC ES staff serves as the forums central point of contact and coordination and supporting body. Additionally, the MIC ES staff is responsible for the MICs strategic communication. Liaison officers (LNOs) from MIC member nation (other than the USA) are assigned to the MIC ES staff and perform duties and responsibilities outlined in the MIC ES Terms of Reference (TOR) document. The Chairman of the MIC SG is the senior member of the MIC ES staff and is responsible for the day-to-day activities of the staff. The MIC ES staff also works closely with the Chairmen and Secretaries of the functional MIWGs in completing their assigned tasks and projects. Meeting Schedule 613. The MIC Principals will meet twice a year, or more frequently as needed, to provide executive oversight and direction to the activities of the MIWGs and to respond to actions and recommendations from the MIWGs. Ad Hoc meetings will normally be via teleconference or VTC. The MIWGs normally meet twice a year, the MIC SG meets quarterly in parallel to the MIC Principals and MIWG meetings. MIC Contacts 614. MIC Website: https://community.apan.org/mic/
48
UNCLASSIFIED
CHAPTER 7
THE TECHNICAL CO-OPERATION PROGRAM Introduction 701. The Technical Cooperation Program (TTCP) is a forum for Defense Science and Technology (S&T) collaboration between Australia (AUS), Canada (CA), New Zealand (NZ), the United Kingdom (UK) and the United States (US) that dates back to 1957. It is governed by its own Memorandum of Understanding (MOU) and is probably the largest collaborative S&T organization in the world. The numbers below give some idea of the scale of TTCP: 5 11 84 170 300 450 1,200 6,000+ 500,000,000 nations involved technology and systems Groups Technical Panels and Action Groups organisations involved active work strands sites involved scientists and engineers directly accessed scientists and engineers accessed in total $s approximately of programs shared through TTCP per annum
702. This is a short guide to TTCP and its objectives, organization, management and operation. It is designed for newcomers to TTCP who will be working with or within the organisation. Objectives & Scope 703. The aim of TTCP is to foster cooperation within the S&T areas needed for conventional (i.e. nonatomic) national defense. The purpose is to enhance national defense and reduce costs. To do this, it provides a formal framework which scientists and technologists can use to share information amongst one another in a quick and easy way. Collaboration within TTCP provides a means of acquainting the participating nations with each others defense research and development programs so that each national program may be adjusted and planned in cognizance of the efforts of the other nations. This process avoids unnecessary duplication among the national programs, promotes concerted action and joint research to identify and close important gaps in the collective technology base, and provides nations with the best technical information available. Structure 704. TTCP is a hierarchical structure with three basic levels:
a. Level 1 is the strategic policy level and comprises three groups of personnel: Principals; Deputies; and Secretariat. Each nation has one representative to each of these groups, with the exception that the Australian Deputy also acts as the New Zealand Deputy. The Deputies and Secretariat are all based in Washington, DC, and collectively form the Washington Staff. Some nations also nominate one or more Executive Support staff to assist the Principals. b. Level 2 is the program planning and oversight level and currently contains eleven Groups, each focused on a particular technology or systems area. The Groups, which have a three-letter designator, contain an Executive Chair (EC) appointed from any one of the nations, up to five National Representatives (NRs), with one from each nation, although the EC may also act as a NR) and a number of Technical Advisors (TAs, if required by the NRs). Each Group has one Deputy assigned to act as its Group Counselor (GC) who works with the Group to help communicate the Principals strategic direction. c. Level 3 contains the bodies that sit under each Group and actually perform the collaborations. There are three types: semi-permanent Technical Panels (TPs); temporary Action Groups (AGs); and
49
UNCLASSIFIED
project-specific Project Arrangements (PAs). Technical Panels are designed to manage a continuing program of work and will generally oversee a number of subordinate activities. Each Group uses different terminology for such tasks. Action Groups are initiated to investigate a specific issue and on completion will recommend if and how any further work on the subject should be undertaken on a more permanent basis. Project Arrangements are a more binding form of cooperation used to support a specific project or a collaboration. Technical Panels and Action Groups have one formal Chair, drawn from one of the nations, plus one National Leader (NL, the Chair may double as a NL) and a number of Team Members from each participating nation. 705. Current Groups, Technical Panels and Action Groups are: AER TP-1: Aerospace Simulation and Operational Analysis AER TP-2: Rotorcraft Technologies and Operations AER TP-3: Propulsion and Power Systems AER TP-4: Structures and Dynamics of Aerospace Vehicles AER TP-5: Fixed Wing Systems Aerodynamics AER TP-6: Uninhabited Air Vehicle Systems AER TP-7: Airborne Mission Systems AER TP-8: Aerospace Capability Readiness and Sustainment
C3I TP-1: Information Fusion C3I TP-2: Command Information Interfaces C3I TP-3: Information Management C3I TP-4: Dynamic Planning and Scheduling C3I TP-6: RF Communications C3I TP-8: Communications Networks C3I TP-11: Information Assurance and Defensive Information Warfare
CBD TP-4: Medical Countermeasures against Biological Agents CBD TP-9: Hazard Modeling CBD TP-11: Low Burden CB Individual Protective Equipment CBD TP-14: Rapid Diagnostics CBD TP-15: Hazard Management CBD TP-16: Synthetic Environments for CB Risk Reduction CBD AG-55: Biological Hazard Assessment AG-56: Innovative Concepts for Biodetection
EWS TP-2: Communications Electronic Warfare

50
UNCLASSIFIED
EWS TP-3: Radar Electronic Attack EWS TP-4: Radar Electronic Surveillance EWS TP-5: EO and IR Warning and Countermeasures EWS AG-1: Service Action Group - Land/ISTAR Electronic Warfare EWS AG-2: Service Action Group - Naval Electronic Warfare EWS AG-3: Service Action Group - Air Electronic Warfare
HUM TP-2: Training Technology HUM TP-3: Military Human Resources HUM TP-7: Human Systems Integration - Air HUM TP-9: Human Systems Integration - Maritime HUM TP-10: Survival Psychology HUM TP-12: Combat Casualty Care HUM TP-13: Psychological Health and Operational Effectiveness HUM TP-14: Protection & Sustainment of Physical & Cognitive Performance HUM TP-15: Human Systems Integration - Land HUM TP-16: Workforce Modelling and Analysis HUM AG-26: Comprehensive Approach
JSA TP-2: Modelling and Simulation JSA TP-3: Joint and Combined Analysis JSA TP-4: Systems Engineering for Defence Modernisation JSA TP-6: Effects Based Analysis of Systems JSA TP-7: CD&E Sciences JSA AG-16: Power and Energy for Military Operations JSA AG-17: Emerging and Disruptive Technology
LND TP-1: Dismounted Combatant Operations LND TP-2: Land Systems Integration LND TP-3: Manned and Unmanned Ground Vehicle Systems LND TP-4: Land Operations Research LND AG-3: Mitigation of Battlefield Trauma LND AG-4: Current and emerging S&T Requirements that Support to Operations
51
UNCLASSIFIED
MAR TP-1: Maritime Command & Control and Information Management MAR TP-4: Maritime Platform Technologies MAR TP-9: ASW Systems and Technology MAR TP-13: Maritime Mine Warfare MAR AG-8: Maritime Domain Awareness MAR AG-14: Maritime Security Operations
MAT TP-1: Metals and Ceramics Technology and Performance MAT TP-5: Non-Destructive Evaluation for Asset Life Extension and Integrity MAT TP-6: Polymers, Adhesives and Coatings MAT TP-7: Composites, Technology and Performance MAT TP-8: Power and Energy, Materials and Systems MAT TP-9: Biotechnological Advances to Materials and Sensing Systems
SEN TP-1: Multi-Sensor Integration SEN TP-2: Signal / Image Processing SEN TP-3: Radar Systems and Technology SEN TP-4: EO Sensor Systems SEN TP-5: Laser Technology for Military EO Systems SEN TP-6: Radar Detection of Small Targets in Clutter SEN TP-7: Acoustic Signal Processing for Impulsive Events and UGS SEN AG-10: Persistent Surveillance and Tracking for Urban Environments
WPN TP-1: Terminal Effects WPN TP-2: Weapon Launch and Flight Dynamics WPN TP-4: Energetic Materials and Propulsion Technologies WPN TP-7: Guidance, Control and Fusing Technologies WPN TP-8: Network Enabled Weapon Systems WPN AG-25: Novel Weapons Management 706. TTCP operates by sharing the output from national S&T programs for the greater benefit of the participating nations. It is therefore fundamentally a bottom-up organization with collaborations only occurring where national programs and a willingness to cooperate already exist. The role of the Principals and NRs in managing TTCP therefore takes two forms: directing collaborations within areas where
52
UNCLASSIFIED
suitable national programs already exist; and directing their own national programs in order to provide the basis for future TTCP collaborations. TTCP is thus a best endeavours organization and can only be as good as the underpinning national programs. If you think that TTCP might be a useful vehicle for a collaboration that you wish to start, you should contact the Secretariat or the relevant NR / NL for advice. They will be able to suggest how best to incorporate the work into an existing or new TTCP activity, if appropriate. Meeting Cycle 707. TTCP operates on an annual cycle, anchored by the yearly meeting of the Principals, typically held around October. This is the point at which the Principals provide strategic direction to TTCP, reviewing the Groups programs, issuing guidance on their fu ture direction and addressing overall TTCP management issues. In advance of the Principals meeting, each Group will hold its own annual meeting generally between April and June, whilst Level 3 bodies meet as required throughout the year. The Principals meeting is hosted by each nation on a five-yearly cycle. Group Annual Meetings generally also rotate through different nations, but there is no formal requirement for this and the choice of venue is left to the discretion of the participants. Websites and Communication Tools 708. The majority of TTCPs work is at low levels of classification but information up to Secret is routinely exchanged and this can be extended to Top Secret under certain circumstances. TTCP currently uses three internet-based systems and one classified system to assist trans-national communication. As much TTCP work does have some level of sensitivity attached, even if it is nominally unclassified, the secure systems should be used in preference to unprotected email where appropriate. A short explanation of each system follows. 709. A publicly accessible website at http://www.acq.osd.mil/ttcp/index.html provides an unclassified overview of TTCP, its roles and its management, along with introductory guides for participants and TTCP templates. 710. A password-controlled system is available at https://www.ttcp.drdc-rddc.gc.ca. The website contains working areas for each body and activity. It is intended to be the definitive TTCP reference site. In due course, this system will also incorporate the TTCP Webmail function. 711. The Griffin network connects the Secret-level email systems of the five nations and thereby allows the transmission of information classified at up to Secret between group members. Accounts need to be applied for through national channels. National Secretariat members can assist.
53
UNCLASSIFIED
INTENTIONALLY BLANK
54
UNCLASSIFIED
CHAPTER 8
THE QUADRILATERAL LOGISITICS FORUM
Background 801. The Quadrilateral Logistics Forum (QLF) was established in May 2004 to accelerate resolution of key logistics issues. The senior logisticians of AUS, CAN, GBR and the USA agreed that better harmonization of national activities was needed to produce effective solutions to multinational logistics problems. Given the range of logistics issues requiring attention, it was recognized that efforts could be marginalized if resolution was attempted on too many topics at once. Therefore it was agreed that the QLF would focus on a small number of high-priority areas. In addition, the QLF Principals agreed that the QLF members should undertake a more proactive stance to identify important logistics issues and provide effective options for resolution of problems. 802. It was also accepted that solutions adopted by the QLF might have applicability on other fora. Indeed it would most likely be counterproductive to adopt one solution within the QLF whilst accepting another elsewhere. Thus, it was agreed that the QLF priorities should drive not only internal actions, but also national priorities in other fora. 803. To help carry out direction from the QLF principals, it was agreed that the officers of the Multinational Office (MNO) of the US Joint Chiefs of Staff Director for Logistics would be used as the coordinating agency - communicating the intentions of the QLF, coordinating the management of issues, and monitoring and reporting progress. These Terms of Reference describe how the QLF, supported by the MNO will operate. Purpose 804. The purpose of the QLF is to provide a forum for the joint logistics principals of AUS, CAN, GBR, and the USA to identify and prioritize interoperability issues and provide strategic direction for their resolution. Goal 805. The goal of the QLF is to harmonize the logistics efforts of its members to ensure the effectiveness and improve the efficiency of coalition operations through logistics interoperability, reduced duplication, shared priorities and a common focus. Scope 806. The QLF will consider joint and combined logistics issues known to be adversely affecting or expected to adversely affect interoperability during coalition operations involving two or more of the member countries. Authority 807. The QLF will provide direction through consensus and authority of its principal members.
Participants 808. Principals. The QLF comprises the Australian Commander Joint Logistics Command (CJLOG), the Canadian Operational Support Commander (CANOSCOM), The UKs Assist ant Chief Defence Staff Log Ops (ACDS Log Ops) and the US Joint Staff Director for Logistics (DJ4). 809. Multinational Office (MNO) The Joint Staff J4 MNO will provide working level support to coordinate the execution of the QLFs strategic/steering level dir ection. It will answer directly to the QLF principals.
55
UNCLASSIFIED
810. Working Group Chairs The QLF may from time to time stand up work groups to address specific Logistics issues that may arise. A work group chair will be assigned who will be responsible for the conduct of the work, be responsive to the MNO and report directly to the Principals. 811. The current Work Groups are: a. b. c. d. Supply Chain WG (SCWG); Movement WG (MWG); Energy WG (EWG); and Coalition Logistics Planning WG.
Frequency and Duration 812. The full QLF including principals, MNO and working group chairs will meet annually, each nation hosting the gathering in turn. QLF Principals will also meet to review and discuss issues at the annual US Council of Logistics Directors meeting and the Senior NATO Logisticians Conference held twice per annum.
56
UNCLASSIFIED
CHAPTER 9
WASHINGTON-BASED STAFF CONTACT DETAILS ABCA Armies Program Office Suite 1080 2521 South Clark Street ARLINGTON, VA, USA 22202-3926 fax: +1 703 601 0116 abca.programoffice@us.army.mil http://www.abca-armies.org/
Nation ABCA Appointment Title Chief of Staff (COS) Rank/Ti tle First Name Last Name Work Phone/Fax E-mail
NZ
Col
David
Hingston
703-601-0108
david.hingston.fm@mail.mil
US
Executive Officer
Mr.
James
Contreras
703-601-0110
james.p.contreras.civ@mail.mil
US
SO1 Combat (SO1 Cbt) SO1 Combat Support (SO1 Cbt Sp) SO1 Command, Control, Communications, Computing & Information (SO C4I) SO1 Combat Service Support (SO1 CSS) SO1 Coalition Operations (SO1 C Ops) Staff Officer 2 Coordination (SO2 Coord) Staff Officer 2 Products (SO2 Prod)
UK
Lt Col
Mike
Onslow
703-601-0113
michael.p.onslow2.fm@mail.mil
CA
LCol
Lorne
Leveck
703-601-0105
lorne.leveck.fm@mail.mil
AS
LTCOL
Scott
Hill
703-601-0115
scott.s.hill7.fm@mail.mil matthew.j.boggs2.fm@mail.mil
NZ
Lt Col
Matt
Boggs
703-601-0114
AS
MAJ
Kurt
Rezek
703-601-0109
kurt.a.rezek.fm@mail.mil
UK
Mrs
Heather
Royall
703-601-0101
heather.s.royall.civ@mail.mil
CA
Chief Clerk
PO
Robert
Doyle
703-601-0104
robert.j.doyle77.fm@mail.mil
57
UNCLASSIFIED
ASIC Management Committee 1500 W Perimiter Rd, Suite 3790 Joint Base Andrews, MD 20762-6604 Reception +1 240 612 4231/2 Facsimile +1 240 612 2002 (DSN 612) https://community.apan.org/air__space_interoperability_council_asic/
COUNTRY/ SERVICE INCUMBENT POSITION/ LIAISON EMAIL PHONE (Facsimile)
Australia
WGCDR Dave Bishop
Ch C2 ISTAR, Sec FP, Sec ROVER, AUSCANNZUKUS, CCEB, ICCWG
asicmcau@pentagon.af.mil 240 612 4233
Canada
LCol Vaughn Cosman
Ch FP, Sec ACS, ASMG Advisor, ABCA, JAPCC Ch FA, Sec C2 & ISR, Advisor ALSA, NATO Ch ACS, Sec AM, QLF, TTCP, Advisor Fuels Group MC Ch, Ch AM, Sec FA, EAG/MIC/Multifora NPM and MC Representative
asicmcca@pentagon.af.mil 240 612 4234 asicmcus@pentagon.af.mil 240 612 4237 asicmcnz@pentagon.af.mil 240 612 4235 asicmcuk@pentagon.af.mil 240 612 2436
USAF
Maj Mike Cancellare
New Zealand
WGCDR Nigel Cooper
UK
Wg Cdr Chris Thorpe
US Navy
LCDR
703-695-2630 DSN 225
Mrs Yvonne Cartwright
Administration and Webmaster Private Website Administration and Webmaster Public Website
asicad01@pentagon.af.mil 240 612 4231 asicad02@pentagon.af.mil 240 612 4232
Mrs Lesley Onslow
58
UNCLASSIFIED
AUSCANNZUKUS Permanent Support & Coordination Group https://community.apan.org/international/auscannzukus

COUNTRY INCUMBENT (as of Nov 11) POSITION/ LIAISON PSCG Chairman, OPNAV Allied Interoperability, CNO N2/N6F423 Multifora Staff Officer A-Z CNO N2/N6F4233 ICCWG LCDR Catherine Gordon, RAN tbrb LCDR Kathryn MCabe, RAN WEF 27 Sep 12 PHONE (Facsimile) EMAIL
UK
Cdr Rupert Irons, RN
703 695 7891 (703 695 7772)
rupert.irons.uk@navy.mil
NZ
Lt Cdr Alan Parker, RNZN
703 695 7879 (703 695 7772)
alan.parker.nz@navy.mil
Staff Officer C4IW CCEB
AUS
202 797 3251 (202 797 3328)
catherine.gordon@defence.gov.au kathryn.mccabe@defence.gov.au
CAN
LCdr Paul Collier, RCN CDR Andrew Brown, RNZN tbrb CDR Mathew Williams, RNZN WEF 13 Aug 12 Cdr Gavin Edward, RN LT Jonathan Parker, USN tbrb Mr David Zatt WEF 1 June 12 LCDR Donald Allan, RCN
Assistant Attach, Naval Engineering TTCP Assistant Naval Attach ABCA SO1 C4ISR Maritime ASIC Allied Interoperability CNO N2/N6F4232 MIC Experimentation Working Group Chairman
202 682 7630 (202 682 7643)
John.Collier@forces.gc.ca
NZ
202 328 4807 (202 265 9238)
andrew.brown@nzdf.mil.nz Mathew.Williams@nzdf.mil.nz
UK
202 588 6805 (202 588 7871)
BDSUS-DAT-C4ISR-MAR@mod.uk
US
703 695 7880 (703 695 7772)
jonathan.s.parker@navy.mil David.Zatt.ctr@navy.mil
CAN
703 695 7865 (703 695 7772)
Donald.allan.ca@navy.mil
59
UNCLASSIFIED CCEB Permanent Secretary 6000, The Joint Staff, The Pentagon Washington, DC 20318-6000
COUNTRY/ SERVICE AS INCUMBENT POSITION/ LIAISON PHONE (Facsimile) LCDR Catherine Gordon Washington Staff AUSCANNZUKUS Navies 202 797 3251 (202 797 3200) 202 682 7640 (202 682 7643) EMAIL
catherine.gordon@defence.gov.au
CA
LCol Yannick Lemieux
Washington Staff, ABCA, TTCP
yannick.lemieux@forces.gc.ca
NZ UK
Gapped Wg Cdr Richard Elder
Washington Staff Washington Staff ASIC, ICCWG 202 588 6827 (202 588 7871) 703 695 8408 (703 614 7814)
BDSUS-DAT-C4ISR-AIR@mod.uk
US
COL Brian Foley
Washington Staff
brian.p.foley.mil@mail.mil
AS
LCDR Paul Graham
Permanent Secretary CFBLNet, MIC: Ops Spt MIWG Secretary, NATO ACP
703 614 4684 (703 614 7814)
james.p.graham53.fm@mail.mil
ICCWG
COUNTRY/ SERVICE AU CA
INCUMBENT
POSITION/ LIAISON
PHONE (Facsimile)
EMAIL
LTCOL Adrian Pang Col Robert Mazzolin
SO1 CND, ICTCC Commander, Canadian Forces Information Operations Group Strategic Information Assurance Manager (SIAM), CIS Branch CIO J6 Deputy Head Ops Director, International Cyber Security Program, DoD CIO
+61-2-61444604 +1-613-9453104 +64-4-2371 890 +44-20-72186307 +1-703-5715890
adrian.pang@defence.gov.au ROBERT.MAZZOLIN@forces.gc.ca
NZ
Mr. Chris Ward
christopher.ward@nzdf.mil.nz
UK
Capt Mike Dyer, RN Mr. Mike Coomes
CIO-J6-OpsDepHead@mod.uk Michael.Coomes@osd.mil
US
60
UNCLASSIFIED MIC https://community.apan.org/mic/
COUNTRY/ SERVICE
J3 DDGO/MOD
INCUMBENT MIC ES staff Col Mike Brantley
POSITION/ LIAISON MIC ES staff Chairman MIC Steering Group (SG)/MIC ES staff Ops MIWG Chairman/ MIC ES staff MIC ES staff MIC ES staff MIC ES staff
US JS J3
PHONE (Facsimile) 703 692-0175 (703 614-9347) 703 614-9348 (703 614-9347) 703 614-5662 (703 614-9347) 703 614-9349 (703 614-9347) 703 614 6039 (703 614-9347) 703 693-7053 (703 614 9347)
EMAIL
US JS J3 US JS J3 ITA LNO DEU LNO
vacant Mr. Charles Pattillo Lt Col Lanfranco Amicarelli Lt Col Andreas Noeske
TTCP http://www.acq.osd.mil/ttcp/index.html COUNTRY/ SERVICE AUS INCUMBENT POSITION/ LIAISON AUS Secretariat PHONE (Facsimile) 202 797 3380 (202 797 1838) 202 682 7651 (202-6827643) ph. 240 - 612 4235 FAX: 240 - 612 4229 202 588 6728 (202 588 7873) 703 - 696 2472 wendy.steele@defence.gov.au EMAIL
Ms. Wendy Steele
CA
Keith Niall, Ph.D.
CA Secretariat
Keith.Niall@forces.gc.ca
NZ
WGCDR Nigel Cooper
NZ Secretariat
nigel.cooper@pentagon.af.mil
UK
Dr Michael Frame
UK Secretariat
BDSUS-DAT-DST-AE@mod.uk
US
Daly Young
US Secretariat QLF
http://www.jsj4.com
COUNTRY/ SERVICE AUS CAN UK US INCUMBENT CAPT Michael Miko, RAN LTCOL Robert Chaloux GPCAPT Russ Huxtable CAPT Michael Thomas POSITION/ LIAISON JS J4AUS LNO JS J4 CAN LNO JS J4 UK LNO JS J4 MN Log Division Chief PHONE 703-571-0217 703-571-9815 703-571-9814 703-571-9796 EMAIL
michael.miko@js.pentagon.mil
robert.chaloux@js.pentagon.mil
russell.huxtable@js.pentagon.mil michael.thomas@js.pentagon.mil
61
UNCLASSIFIED
INTENTIONALLY BLANK
62
UNCLASSIFIED
CHAPTER 10
MULTIFORA MEETING SCHEDULE 1001. This chapter provides details of the meeting schedule for each of the multifora organizations represented in this handbook. The dates presented are correct at time of publishing, but are subject to change. Please check with the sponsoring organization if you are intending to attend one of the listed meetings.
ABCA 24-Month Meeting Schedule
2012
Group Executive Council 1 Qtr
st
2013
4 Qtr Executive Council Meeting
th
nd
Qtr
3 Qtr
rd
1 Qtr
st
nd
Qtr
3 Qtr
rd
4 Qtr Executive Council Meeting
th
National Directors & Capability Groups Support Groups
VTC
Annual Meeting Mar 12 Ottawa CA
VTC
ABCA Board Meeting 7-9 Nov 12 (Wellington, NZ)
VTC
Annual Meeting 8-12 Apr 13 (Melbourne, AS)
VTC
ABCA Board Meeting 30 Oct 1 Nov 13 (CA)
Project Teams
20-30 Project team meetings throughout each year. Please contact the ABCA Program Office staff or download the ABCA Calendar www.abca-armies.org Lessons Collection Deployment (LCD)
Interoperability Lessons Review Board (ILRB)
Other Significant Events
Lessons Collection Deployment (LCD)
Coalition Lessons Analysis Workshop (CLAW)
63
UNCLASSIFIED ASIC 24-Month Meeting Schedule
Meeting Schedule National HoD Meeting

Chair: NPM
1st Qtr 2012 Jan-Mar Jan/Feb All
2nd Qtr 2012 April- Jun
3rd Qtr 2012 Jul-Sep
4th Qtr 2012 Oct-Dec
1 Qtr 2013 Jan-Mar Jan/Feb All
st
2 Qtr 2013 April- Jun
nd
3 Qtr 2013 Jul - Sept
rd
4 Qtr 2013Oct Dec
th
Steering Group (SG)

Chair & Sec rotate
Apr US Oct/Nov
Apr US Oct/Nov CA
Agile Combat Support (ACS)

Chair: NZ MC, Sec: CA MC
NZ
May NZ Oct/Nov US Oct/Nov AU Oct/Nov CA Oct/Nov US Oct/Nov UK May/Jun CA 1 Day each in Jan/Feb/Mar 1 Day each in Apr/May/Jun 1 Day each in Jul/Aug/Sep 1 Day each in Oct/Nov/Dec 1 Day each in Jan/Feb/Mar May-June AU 1 Day each in Apr/May/Jun 1 Day each in Jul/Aug/Sep 1 Day each in Oct/Nov/Dec
Fuels Group (FG)

NZ Advisor
May
UK Oct/Nov UK Oct/Nov NZ Oct/Nov
Air Mobility (AM)

Chair: AU MC, Sec: NZ MC
Force Protection (FP)

Chair: CA MC, Sec: AU MC
Air and Space Medicine Group (ASMG)

CA Advisor
NZ
Oct/Nov CA Oct/Nov AU
Force Application (FA)

Chair: US MC, Sec: UK MC
C2&ISR
Chair: UK MC, Sec: US MC
NDM
Chair: outgoing MC Chair
MC Meetings
Chair: UK after NDM NZ
64
UNCLASSIFIED
AUSCANNZUKUS 24-Month Meeting Schedule
Board/Committee/ Working Group meeting Supervisory Board
1st Qtr 2012 Jan-Mar SB 28 26-28 Mar 12 Auckland, NZ ESC 12-1 19-23 Mar Auckland, NZ 5 9 Mar Wellington, NZ
2nd Qtr 2012 Apr-Jun
1st Qtr 2013 Jan-Mar
2nd Qtr 2013 Apr-Jun SB 29, TBC UK
Executive Steering Committee (ESC) Maritime Cryptologic Committee (MCC)
ESC 12-2 TBC Oct Washington, DC (UK host)
ESC 13-1 TBC, UK
ESC 13-2 Oct Washington, DC (US host)
TBC, UK
TWG 12-1 Technical Working Group 12-16 Mar (TWG) Auckland, NZ Permanent Support and Coordination Group (PSCG) (Washington, DC) Operations Working Group (OWG) Jan Apr Jul, Sep
TWG 12-2 TBC Oct Washington, DC (UK host) Nov Feb
TWG 13-1 TBC, UK
TWG 13-2 Oct Washington, DC (US host) Jul, Sep Nov
Apr
OWG 12-1 12-16 Mar Auckland, NZ EWG 12-3 TW12 Final Rpt Writing 16 21 Apr San Diego, CA 13 17 Aug EWG 13-1 20 24 Aug
OWG 12-2 TBC Oct Washington, DC (UK host) EWG 13-2 TBC
OWG 13-1 TBC, UK
OWG 13-2 Oct Washington, DC (US host) TW13 Final Rpt EWG 14-2 TBC TBC EWG 14-1 TBC
Experimentation Working TW 12 Group RRLOE 23 Jan 4 Feb
EWG 13-3 TBC
65
CCEB 24 Month Meeting Schedule
Title of Panel, WG or WP meeting
1st Qtr 2012
2 Qtr 2012
nd
3 Qtr 2012
rd
4 Qtr 2012
th
1 Qtr 2013
st
nd
Qtr
3 Qtr 2013
rd
4 Qtr 2013
th
2013
Principals Meetings
Principals VTC 28 March
P43M 18-22 June Canberra EG43 11-15 June Canberra Monthly Telecons
VTC Nov
VTC Feb
P44M May CAN
VTC Oct
Executive Group (EG) Meetings
Monthly Telecons
EG44 Oct/Nov London
Monthly Telecons
EG45 May CAN
EG46 Oct AUS Monthly Telecons JM 4 Oct AUS
Joint WG/TT Meetings
PPDT Mtg 5-9 March Monthly Telecons
Monthly Telecons
PPDT/ POMWG Mtg 13-17 Aug Monthly Telecons
JM 3 Oct/Nov London
Monthly Telecons
Monthly Telecons
Washington Staff
Monthly
Monthly
Monthly
Monthly
Monthly
Monthly
Monthly
Monthly
ICCWG 24-Month Meeting Schedule
Title of Panel, WG or WP meeting Executive Group (EG) Meetings Sub WG Meetings
1st Qtr 2010 VTC 1 Mar
2 Qtr 2010 VTC 7 Jun
nd
3 Qtr 2010 VTC 23 Aug
rd
4 Qtr 2010 MtgOct NZL
th
1 Qtr 2011 VTC
st
2 Qtr 2011 VTC
nd
3 Qtr 2011 VTC
rd
4 Qtr 2011
th
Annual Conf Oct - UK
66
MIC 24-Month Meeting Schedule
Title of Panel, WG or WP meeting Principals
1st Qtr 2012 Mar
2nd Qtr 2012 May/Jun MIC 2012 14-18 May 2012 London, GBR
3rd Qtr 2012 Sep
4th Qtr 2012 Nov Principals meeting 5 9 Nov 2012 Washington, DC
MIC SG
Mar 12 MIWG 19-23 March 2012 Canberra, AUS Mar 12 MIWG 19-23 March 2012 Canberra, AUS
MIC 2012 14-18 May 2012 London, GBR
Sep 12 MIWG 17-21 Sep 2012 Miami, FL Sep 12 MIWG 17-21 Sep 2012 Miami, FL
MIC SG SPS 5-9 Nov 2012 Washington, DC
MIWGs
Title of Panel, WG or WP meeting Principals
1st Qtr 2013 Mar
2nd Qtr 2013 May/Jun MIC 2013 17-21 Jun 2013 Roem, ITA
3rd Qtr 2013 Sep
4th Qtr 2013 Nov Principals meeting 4-8 Nov 2013 Washington, DC
MIC SG
Mar 13 MIWG 18-22 March 2011 Paris, FRA Mar 13 MIWG 18-22 March 2011 Paris, FRA
MIC 2013 17-21 Jun 2013 Rome, ITA
Sep 13 MIWG 9-13 Sep 2013 Stuttgart, DEU Sep 13 MIWG 9-13 Sep 2013 Stuttgart, DEU
MIC SG SPS 4-8 Nov 2013 Washington, DC
MIWGs
67
TTCP 24-Month Meeting Schedule Group Meeting 1st Qtr 2012 2nd Qtr 2012 7-8 June; Brisbane AUS 14-18 May; VA USA 30 Apr-1 May MD USA 28-31 May; Ottawa CA 3-8 June; Calgary CA 6-8 June; Melbourne AUS 21-25 May; L.A. USA 7-11 May; DC, USA 11-15 June; Victoria CA 28-31 May; Porton Down UK 21-15 May; Portsdown West UK 2-4 Oct; Dayton OH, USA 3rd Qtr 2012 4th Qtr 2012 1st Qtr 2013 2nd Qtr 20 2013 t.b.c. 3rd Qtr 2013 4th Qtr 2013
AER C3I CBD EWS HUM JSA LND MAR MAT SEN
t.b.c. t.b.c. t.b.c. t.b.c. t.b.c.
t.b.c. t.b.c. t.b.c. t.b.c.
t.b.c.
WPN
Principals Meetings
Oct. 2013 UK
68
QLF 24-Month Meeting Schedule
1 Qtr 10 Jan - Mar QLF 22-26 Feb
st
2nd Qtr 10 Apr-Jun
3 Qtr 10 Jul-Sep
rd
4 Qtr 10 Oct-Dec 4 Oct
th
1 Qtr 11 Jan - Mar 21-25 Feb
st
2 Qtr 11 Apr-Jun
nd
3 Qtr 11 Jul-Sep
rd
4 Qtr 11 Oct-Dec Oct (details TBC) TBA Oct (details tbc)
th
SNLC COLD QLF Training WG
24-25 Apr
20-21 Oct 4-7 Oct tbc
23-24 Mar
N/A Monitor Mode -----------------------------------------------------------------
QLF Contracting WG QLF MN Information Integration WG Log MWIG 15-18 Mar tbc
tbc
tbc
tbc
tbc
tbc
tbc
tbc
tbc
tbc
tbc
tbc
tbc
27-30 Sep
TBA
TBA
69
WASHINGTON BASED MULTIFORA MEETING SCHEDULE
MEETING
2009 - 01 2009 - 02 2009 - 03 2010- 01 2010- 02 2010- 03 2011 01 2011 02 2011 - 03 2012 - 01 2012 - 02 2012 - 03 2013 - 01 2013 - 02
HOST
MIC QLF ABCA CCEB ASIC A-Z NAVIES TTCP MIC QLF ABCA CCEB ASIC A-Z NAVIES TTCP
70
DATE
Q1-09 Q2-09 Q3-09 Q1-10 Q2-10 Q3-10 Q1 11 Q2 11 Q3 11 Q1 - 12 Q2 - 12 Q3 12 Q1 - 13 Q2 - 13
UNCLASSIFIED
INTENTIONALLY BLANK
71
ABCA
ASCC
UNCLASSIFIED AUSCANNZUKUS TTCP
CCEB
ICCWG
MIC
QLF
UNCLASSIFIED
WASHINGTON-BASED MILITARY MULTIFORA
UNCLASSIFIED

2012 Multifora Handbook - The Five Eyes Data-Sharing Communities

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2012 Multifora Handbook - The Five Eyes Data-Sharing Communities

Uploaded by

Copyright:

Available Formats

UNCLASSIFIED

WASHINGTON-BASED MILITARY MULTIFORA

STAFF HANDBOOK 2012

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED Record of Changes

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED Quadrilateral Logistics Forum (QLF).

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

MULTIFORA STATEMENT OF COOPERATION - 2012

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

HAVE AGREED AS FOLLOWS:

ARTICLE I: ROLE OF PARTICIPANTS

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

MIC CCEB STATEMENT OF COOPERATION

ARTICLE I: ROLE OF PARTICIPANTS

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

ARTICLE II: AIM

ARTICLE III: STATEMENT OF COOPERATION

8. We INTEND that New Zealand is granted observer status at MIC meetings.

12. We INTEND that this Statement of Cooperation is non-binding in law.

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

Figure 1 Governance Structure of ABCA

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

Figure 3 ABCA Annual planning cycle

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

The United States Navy is also a full member of ASIC

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

Figure 2.1: ASIC International Organization

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

Figure 2.2: ASIC Work Cycle

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

Provide a forum to highlight maritime IW issues to national authorities.

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

Figure 3.1: AUSCANNZUKUS Maritime IW Organisational Structure 319.

A summary of the AUSCANNZUKUS organisation schedule is shown at Figure 3.2.

Host nation (Mar/Apr) Host nation in Washington DC (Oct) Host Nation

Host Nation (changes o/c Apr/May meeting)

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

As required by experimentation activities As directed by parent body

As required by experimentation activities As directed by parent body

As required by experimentation activities As directed by parent body

Figure 3.2: The AUSCANNZUKUS Organisation Schedule

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP

UNCLASSIFIED ABCA ASIC AUSCANNZUKUS CCEB ICCWG MIC QLF TTCP