multilateral interoperability programme … document library/99_archives... · multilateral...

MIP Operational Level Test Directive 12 February 2009 Version 2.0 TUR

R. Ali Tütüncüo� lu MOLT Block III Test Controller 10-11-2009 - 1 -

MULTILATERAL INTEROPERABILITY PROGRAMME

OPERATIONAL LEVEL TEST DIRECTIVE

Block 3 MOLT

02 - 20 March 2009 12 February 2009, Greding/Germany Release of this document to nations or agencies who are not participants in the Multilateral Interoperability Programme, including the media and general public, requires approval of the MIP Steering Group (MSG) in accordance with the policy stated in the MIP Communications Plan (MCP). This document is the property of the MIP Participants, and the information contained in this document shall not be communicated, either directly or indirectly, to any person or agency not authorised to receive it.

UNCLASSFIED MIP Operational Level Test Directive 12 February 2009

Version 2.0 TUR

UNCLASSFIED - 2 -

1.1 INTRODUCTION This document describes the objectives, prerequisites and procedures for MIP Block 3 Operational Level Test (MOLT). The MIP Operational Level Test is carried out in accordance with the MIP Test and Evaluation Master Plan (MTEMP) and is conducted under TEWG control. The MOLT should demonstrate the operational readiness of the MIP Block 3 solution in a multi-national scenario representative of potential deployment. This scenario will require participating nations to exchange / share data between their respective national Command and Control Information Systems (C2IS). The MOLT shall also provide operational feedback to the Multilateral Interoperability Programme for future iteration / development of the MIP solution. 1.2 MOLT AIM The MIP Operational Level Test aim is to determine the fieldability and stability of the MIP Block 3 solution for deployment in operational theatres. 1.3 MOLT OBJECTIVES In order to achieve the aim, the MOLT must assess and validate the following objectives:

• Validate the MIP Operational Procedures (MOP); • Validate the MIP Operational Handbook (MOH); • Characterize the robustness of the Block 3 solution; • Validate the MIP Tactical C2IS Interoperability Requirements(MTIR);

1.4 ENTRY CRITERION Nations shall provide the following information NLT than the end of the WG 29 to the MOLT deputy test controller ( [email protected] ):

a. Naming and describing role of all participants at OLT ( Annex I ) b. To fill MTIR Implementation Matrix (Annex B) (to group nations) c. National Base line (Annex C)

2 MOLT – Testing Organisation 2.1 MIP Test Director and MIP OLT Test Director The MIP Test Director is responsible for managing and coordinating all levels of testing. Multiple levels of testing can occur simultaneously and the MIP Test Director (TEWG Chair-Mr. Garry ANNETTS from UK [email protected] or [email protected]) and MIP OLT Test Director Lt.Col Jeremy METCALFE [email protected] from UK are responsible for de-conflicting all issues which may arise during testing and will provide guidance on the execution of the tests.1 2.2 Test Organisation

1 See MIP MTEMP document.


Version 2.0 TUR

UNCLASSFIED - 3 -

The organisation will be established as described in Figure 1. Figure 1 – Test Organisation MIP Roles

# Role WG / Nation to

provide Appointed

1 MIP Test Director TEWG / GBR Mr Garry ANNETTS 2 MIP OLT(Tactical) Test Director TEWG / GBR Lt. Col Jeremy METCALFE

3 Test Controller TEWG / TUR Maj.R. Ali TÜTÜNCÜO� LU [email protected]

4 Deputy TC / Chief Data Collector TEWG / ITA Capt. Sergio MINGIONE [email protected]; [email protected]

5 G3 Controller OWG / ITA OWG / FRA OWG/ FIN

Maj. Giuseppe CALANDRINI [email protected] Capt. Mickaöl PIERRIN [email protected] Capt. Jarkko TURUNEN [email protected]

6 OLT Data & Eval Controller TEWG / LTU Vilius KAZLAUSKAS

7 Technical Coordinator SEAWG / NLD TEWG / FIN

Ton AMBAGTSHEER SrLt. Mika RAJALA [email protected]

Table 1: MIP MOLT team. 2.2.1 MIP OLT Test Controller and Deputy Test Controller (TC and DTC) The OLT Test Controller is responsible for the conduct of the OLT. The OLT TC shall ensure all participants are aware of OLT test procedures.

Test Controller Maj. Ali TÜTÜNCÜO� LU(TUR)

Deputy Test Controller (Chief Data Controller) Capt. Sergio MINGIONE (ITA)

Scenario / G3 Controller Cell •Maj. Giuseppe CALANDRINI (ITA)

•Capt. Michael PIERRIN (FRA)

•Capt. Jarkko TURUNEN (FIN)

Data Collection and Technical Cell

• Data Collector: Vilius Kazlauskas (LTU)

• Technical Controllers: Ton Ambagtsheer (NLD)

SrLt Mika RAJALA (FIN)

• National team * • National team *

Data Collector G3 Scenario Controller


Version 2.0 TUR

UNCLASSFIED - 4 -

The MIP OLT Test Controller and Deputy Test Controller are responsible to the TEWG for the preparation of the MOLT and for managing and coordinating the test activities. They will also produce the test report to the PMG after completion of the MOLT.2 The Deputy Test Controller also serves as the Chief Data Collector. 2.2.2 MOLT G3 / Scenario Controller Cell3 The G3 / Scenario Controller Cell reports to the MOLT Test Controller and Deputy Test Controller and is responsible for the conduct and monitoring of the MOLT. This cell will closely cooperate with national G3 participants to ensure that the testing is conducted as in accordance with the MTEMP. Additionally, this cell will also assist the TC and DTC in the conduct of the daily coordination meeting and discussion with national team members. Finally, this cell will also contribute to the production and review of the OLT final report. 2.2.3 MOLT Data Evaluation Controller Cell The Data Evaluation Cell ensures that information is collected during the MOLT to support the test objectives and that it will be sufficient for post MOLT analysis. This cell will also assist and direct the National data collectors during the conduct of the OLT. The Deputy Test Controller leads this cell. 2.2.4 MOLT Technical Controller Cell This cell is responsible for giving assistance to Nations during the conduct of any technical investigations and also ensures that problem reports are also generated in the MIP Problem Reporting Tracker (MPRT) to support further analysis by the appropriate MIP working groups. Finally, this cell assists and directs the national data collectors during the OLT. 2.2.5 Data Collector The Data Collector reports to the OLT DTC in order to ensure that all data collection activities are completed as per the MOLT directives. They shall also notify the OLT Data Evaluation and Technical Controller cell about any issues that occur during OLT. They are responsible to the OLT TC for the data collection to support the post-OLT analysis. Data Collectors will collect data at a different system from their own nation. For this reason, the National Data Collector shall not have “other roles” 4 See ANNEX L - OLT DATA COLLECTION Plan

2 See MIP MTEMP document. 3 In MIP MTEMP document, it is eepressed as “Operational Coordinator” 4 e.g. unlike the National G3 Controller


Version 2.0 TUR

UNCLASSFIED - 5 -

2.2.6 National G3 / Scenario Controller and other National roles Each Nation is responsible for providing a national G3 controller/coordinator, while MIP will provide a G3 Scenario controller. The national G3 staffs cooperate with the G3/ Scenario controller cell to ensure the proper conduct of the OLT activities. It is strongly recommended that the person assigned to this post has had previous experience in the MIP OWG or MOLT WP. The national G3 / G3 scenario controller will also be required to participate in the OLT discussion and coordination meetings. Finally, the national G3 /G3 Scenario controller will provide their own report and/or assessment on the OLT conduct to the OLT Test Controller. Other National roles as required (e.g. Chief of Staff, Coffeemakers’) are left to the Nations own discretion. See ANNEX M - OLT NATIONAL G3 Plan 2.2.7 MIP Test Management Toolset Instructions: System Operator The System Operator, after the login procedure, has to select his role into MTMT system. He/she will be able to update the iteration when his events are complete but he will not be able to input any data collector answers. See ANNEX N - OLT NATIONAL C2IS SYSTEM OPERATOR Plan Data Collector The Data Collector, after the login procedure, has to select his role in MTMT system. He/she is able to answer questions for the C2 system that is responsible. Data collectors will not conduct self evaluations of their national C2IS. The test organization will 'assign' data collectors to different C2ISs. View Iteration Answers This puts into a 'read-only' mode to allow viewing answers submitted for any particular organization / system. Conduct Test Before the first test event is displayed, it is mandatory to select a role. System Operator The System Operator will be able to select the "Click Complete" or "Click Skipped" link when his/her organization / system is the Source. "Click Complete" is to be selected only when ready with the test serial. The target systems will see that the event is complete (green dot) and data can be collected. "Click Skipped" is to be selected if the C2IS system doesn't have the capability to do the test serial. The target systems will see that the event is skipped (yellow dot) and will not search for data related to that system (they will have to answer the data collection question with SKIP). Data Collector The Data Collector will be able to answer questions when his/her organization / system is the Target. The comment, in the MTMT system, should be complete and understandable for someone that was not participating in the test! The status of event could be, for example: Go : "OK" Skip : "Div N (WHICH SYSTEM or COUNTRY!) does not have MEM capability";


Version 2.0 TUR

UNCLASSFIED - 6 -

N.I. : "The system does not implement holdings"; K.O. : "Mapping to (WHO!!) C2IS didn't work.” If an event asks to attach a file (for example, a jpg to display the "operational situation he must follow these operations in the MTMT System: A) Click the "attach file" command; B) Go to the folder where you have saved the file and select it (remember the naming conventions); C) Click the "Upload" command; D) Click the "Submit answer". 3 MOLT Testing Procedures The test has been designed for the requirements of MTIR. There will be nations/systems that have not implemented all requirements. In this situation to decrease the effect of daily rhythm, grouping will be done to incorporate nations who do not have MEM or who have not implemented P&O into the grouping by OLT Team. 3.1 General The OLT-Test Period is divided into two parts, the Triad and the Continuous Vignette and overall will last three weeks. The “Main Event List” will be used which is enclosed as Annex H. 3.2 The Triad 3.2.1 The system The Triad-Phase will last five and half days (please note: Saturday is scheduled as working day, Sunday if required). In each group, three systems act in three different roles, which are rotated after each session is completed among the group members. The three different Roles are Corps, Division North and Brigade A. Each role has to be performed in the Triad-Phase. Note: If there are insufficient systems to make up groups of three, the TC Cell will make an arrangement to accommodate this; for example, by making up a group of four nations. 3.2.2 The schedule

A B C Time Role A 1 A 2 A 3 B 4 B 5 B 6 C 7 C 8 C 9

Corps 1 4 7 10 13 16 19 22 25

Division 2 5 8 11 14 17 20 23 26 Day (Sequence) 1

Brigade 3 6 9 12 15 18 21 24 27

Corps 2 5 8 11 14 17 20 23 26

Division 3 6 9 12 15 18 21 24 27 Day (Sequence) 2

Brigade 1 4 7 10 13 16 19 22 25

Corps 3 6 9 12 15 18 21 24 27 Division 1 4 7 10 13 16 19 22 25 Day (Sequence) 3

Brigade 2 5 8 11 14 17 20 23 26

Place 1 Canteen 2 Testhall


Version 2.0 TUR

UNCLASSFIED - 7 -

Table 2: Example for 27 Systems, those are ready. 3.3 The Continuous Vignette 3.3.1 The plan The target is to test all national C2ISs. The continuous vignette will last for 10 days (please note: Saturday is scheduled as working day, Sunday if required). During the ten days, there will be three groups (with same event list, with up to nine systems in each group) that will take part in testing, depending on the national systems (C2IS) that are ready for testing. The assigned roles will not be changed during this period. The roles will be assigned by the TC Cell who will take note of the SLT 3 capability matrix and Annex B. National MTIR Implementation Matrix by TEWG. There are three possible hierarchies, these are: 1. One Corps with

One Divs with set with three nations One Bde

2. One Corps with Two Divs’ with set with five nations Two Bdes

3. One Corps with Two Divs’ with each set with nine nations Three Bdes 3.3.2 The schedule

Time Role Group 1 Group 2 Group 3 Corps 1 10 19

Division N 2 11 20 Division S 3 12 21 Brigade A 4 13 22 Brigade B 5 14 23 Brigade C 6 15 24 Brigade D 7 16 25 Brigade E 8 17 26

10 Day

Brigade F 9 18 27

Testhall 1 (Canteen)

Testhall 2 (Canteen)

Testhall 3 (Test Hall)

Table 3: Example for 27 Systems, those are ready. The set of hierarchies depends on the number of “available systems”. Groupings will be issued prior to the OLT by the OLT TC. (Note: nations may be asked to volunteer for specific roles.) Also for C2IS software developers there will be an extra room (TEWG) for support their system.


Version 2.0 TUR

UNCLASSFIED - 8 -

3.4 MOLT SCENARIO CONTROL PROCEDURES The MOLT scenario control will be executed by the G3 Controller Cell. Only through their directions will nations will be authorized to proceed to the next test case/event. This will ensure that all data collection activities are completed and that some quality checks are performed to ensure that the collected reports are sufficient and adequate for MOLT post-analysis and for the MOLT report. 3.5 MOLT Data Collection Procedures Data collection will be done in the MIP Test Management Tool (MTMT). Training for the use of this tool is planned, see Annex A. During OLT, it will also be necessary to capture screen shots of the C2IS to enable graphical comparison between the various systems and to also provide the OLT team with a means to conduct quick validation of the scenario conduct and progress. 3.6 Troubleshooting Procedures The MIP Problem Reporting Tool (MPRT) shall be used to capture any problems that occur during the OLT. The OLT Technical Controller will be responsible for the assignment of problems reported to the appropriate MIP WG for resolution. 3.7 MIP Common Data Fill No test data is required ahead of OLT. 3.8 National Data Fill Nations participating in OLT have to prepare their (unclassified) operational database ahead of the MOLT. Every nation will operate as either a (Mechanised Infantry or Armoured) Division and a (Mechanised Infantry or Armoured) Brigade level. One nation will operate as CORPS. In Annex F, information can be found regarding Battlefield Geometry and STARTEX Positions. 4 OLT Briefing and Visitors 4.1 OLT Coordination / Briefing facility The OLT battle rhythm (including coordination meetings) is at Annex A. A room is required to conduct the daily coordination meeting. It shall be equipped with Internet and LAN connection and a projector (beamer). A conference room is also required for the initial briefing/training (half a day) on day one of OLT. This conference room shall be large enough to accommodate the entire OLT team and all participants. 5 OLT Briefing and Visitors 4.2 OLT Coordination / Briefing facility The OLT battle rhythm (including coordination meetings) is in Annex A. A room is required to conduct the daily coordination meeting. It shall be equipped with Internet and LAN connection and a projector (beamer). A conference room is also required for the initial briefing/training (half a day) on day one of OLT. This conference room shall be big enough to accommodate the entire OLT team and all participants. 4.3 Distinguished Visitors Day – 17 March 2009. PMG have approved the following visitors’ policy for the OLT3:

• No Visitors in Week 1: 02 – 07 March 2009


Version 2.0 TUR

UNCLASSFIED - 9 -

• Minimal visitors as arranged by each Nation during Week 2: 09 – 14 March 2009 • A “Distinguished Visitors” day in Week 3 on Tuesday 17 March 2009.

o The OLT Test Director will organise this event. o Each Nation may bring a maximum of 5 guests. This is in order to control numbers

to about 130. o The visit is not to interrupt the main testing. o Briefings will take place in a separate Hall at WTD 81, and then visitors will be able

to visit National test nodes. o Each Nation is responsible for all the arrangements concerning their guests travel

and hotel arrangements. o Further details will be briefed to PMG at WG29 in Feb 09. o Nations shall fill in Annex O by 4 Feb 09 if at all possible. Names or the number of

guests should be completed. 6 OLT Support Requirements / Documents 5.1 MIP Configuration / documents The following reference documents, files and or standards shall be used by all participating nations during (preparation of) OLT:

− JC3IEDM 3.1d − AdatP3 baseline 13.1 (not a MIP document,) − MIR 3.7 − MTIR 3.8 − MOP 3.6 − MOH 2.3A − MTIDP 3.9 − MIP_Common_DataFill − (The “REPL_NODE” Table fill shall be:

o dems_version_descr_txt: JC3IEDM 3.1d o prot_version_descr_txt: MTIDP_3.9)

− MSLT3 test data for Symbology test Set 1 − MSLT3 test data for Data model coverage test Set 1 − MIP glossary 3.4 − MSRS 3.6

5.2 National Configuration Each system will provide the configuration or architecture of the systems they are bringing to MOLT. Annex D shows the test architecture. 5.3 MIP Host Nation Support Host Nation Support Roles

# Nation / from WG Appointed 1 Host Nation Technical Support DEU / TEWG Wilfried STAUTNER Nations shall inform the Host Nation about who will participate during the test period (using the normal MIP procedure via the PMG HoD’s). The IP address schema to be used during tests is at Annex G.


Version 2.0 TUR

UNCLASSFIED - 10 -

5.4 MOLT Physical layout The MOLT team shall coordinate with the Host Nation Support the physical layout required for the conduct of MOLT for all participants including the MOLT Exercise Control Room (HICON). An example layout of the Test Hall Layout can be found at Annex E. 5.5 MIP Local Area Network The network configuration will be based on the number of systems present at the specific MOLT test period. There will be two physically separated networks: 1. MIP Test LAN 2. MIP Service LAN All testing nations will have two Twisted Pair cables with RJ-45 plugs available, one for each of the networks. It is a national responsibility to connect additional hubs/switches to these cables if more than one machine per nation/system is to be hooked on a network. The host organisation cannot provide additional network components to nations. “Each participating nation/system must ensure that all their network and system equipments are operational before commencing the MOLT session” (please inform the OLT Team that the equipments are ready for test) The MIP Test LAN is a single LAN connecting national systems via a hub/switch. There will be no additional servers, routers, etc. on this network except for those belonging to national test systems. The 'MIP Test LAN' is not connected to the Internet. The 'MIP Service LAN' will provide the following services: File Sharing Chat

Internet Access Dhcp

The MIP Test Controller and the Host Nation Technical Support will decide the specific configuration when the number of nations and systems for the specific test period is known. Sergio MINGIONE R. Ali TÜTÜNCÜO� LU Capt. (ITA ARMY) Maj. (TUR ARMY) MIP OLT 3 Deputy Test Controller MIP OLT 3 Test Controller


Version 2.0 TUR

UNCLASSFIED - 11 -

ANNEXES: ANNEX A – MOLT 3 Schedule, ANNEX B – National MTIR Implementation Matrix, ANNEX C – National Baseline, ANNEX D – Test Architecture, ANNEX E – Test Hall Layout, ANNEX F – APPENDIX 1 - Corps Battlefield Geom., ANNEX F – APPENDIX 2 - Div South Battlefield Geom., ANNEX F – APPENDIX 3 - Div North Battlefield Geom., ANNEX F – APPENDIX 4 - Unit STARTEX Positions., ANNEX G – IPs for Tests, ANNEX H – Main Event List, ANNEX I - National G3 Scenario and Data Collectors Personnel, ANNEX L - OLT 3 Data Collection Plan, ANNEX M - OLT 3 National G3 Plan, ANNEX N - OLT 3 National C2IS System Operator Plan, ANNEX O - Distinguished Visitors Day – 17 March 2009.