Attachment_6_-_Test_TAR_Recompete_Revised_Version_8_Mar_19.doc

Volume II, Factor I, Mission Capability (Technical) Task Authorization Request (TAR XXXX)-Test Support- Task Authorization Request (TAR) (Sample)–Attachment #6 Task Authorization Request (TAR) -Test Support (Sample)

1. GENERAL TEST INFORMATION. This TAR requirement is not part of the PWS, Section 5, Test Support Services.

1.1. Full name of test:

1.2. Test Location/Dates: Fort Hood, Texas

Pilot Test: 30 April - 1 May 20XX

Fort Jackson, South Carolina

Record Test: 8-14 May 20XX NOTE: Pilot and Record phase operations are 18 hours per/day (including weekends).

Other: New Equipment Training (NET) at Fort Hood, Texas, 2-5 April 20XX

1.3. Classification: UNCLASSIFIED

NOTE: The test operations officer will coordinate security requirements (including security training, information security, transportation security, physical security, personnel security, force protection, and foreign disclosure). Primary security requirements for safeguarding and managing all test information will be established In Accordance With (IAW) the appropriate classification guide(s) provided by the Program Manager.

1.4. System/Functional Description: The System is an integrated, dismounted, leader Situational Awareness (SA) system for use during combat operations. It is intended to provide SA, Command, and Control (C2) capability to dismounted leaders, Team Leaders (TL), and above. Three different configurations will be evaluated during this test. All three-network configurations use the Motorola Atrix End User Device (EUD); however, each configuration uses a different network transport layer to transmit and receive voice and digital message. These radio systems are AN/PRC 154 Rifleman Radio (RR), Wireless Network after Next (WNaN), and Man Atrix EUD.

2. Reserved

3. DESCRIPTION OF SERVICES.

3.1 SCOPE: This SenarioTest will consist a two (2) day pilot test (Mon and Tue); and the record test will consists of seven (7) days (Tues – Mon), weekends included. Testing shall take place in a Forward Operational Base (FOB) environment. The data will be harvested at the FOB. Personnel shall be performing duties in a tactical field environment during ambient weather conditions and may be required to traverse rough terrain on foot.

A total of 24 soldiers will be trained for the test at Fort Hood, of which 24 soldiers are expected to participate at each of the two locations and will be used for both the pilot and the record test.

Pre-test activities will begin at Fort Hood, Texas, with the test team conducting an inspection and inventory of the system support package using the system support package listing as a guide. Any damage or shortages noted during the inspection will be reported by Test Incident Report (TIR). The test team will mark the test items for ease of identification. The US Army Infantry School (USAIS) will conduct the New Equipment Training (NET) for the test soldiers on the operations and use of the systems. Upon completion of training, the USAIS will certify that the soldiers are trained and qualified to participate in the operational test. The pilot test will consist of one (1) 18-hour Field Training Exercises (FTX). The event will be conducted using the System Under Test (SUT) systems in multiple integrated laser engagement system (MILES) force-on-force exercise. The FTX will focus on the collective tasks derived from the test unit’s Mission Essential Task List (METL) and the Operation Mode Summary/Mission Profile (OMS/MP). Equipment will be provided/accounted for by the test unit at each of the excursion locations.

The record phases will consist of four (4) 18-hour FTX scenarios using blank ammunition. At the end of pilot and record phases, and upon last mission completion at each of the locations, the test team will administer questionnaires and conduct an After Action Review (AAR) during which the test soldiers will be led in a discussion of Human Factors Engineering (HFE) concerns, Tactics Techniques, and Procedures (TTP), and Safety.

3.2. Specific Technical Requirement. The contractor shall describe its technical methodology in Volume II of the solicitation and provide a staffing approach in Attachment 5 with associated labor hours and categories for the below paragraphs 3.3.-3.5. The contractor shall not submit a cost estimate.

3.3. Data Management Requirements.

a. Period of Support: 22 Jan - 22 June b.

Requirements:

NOTE: There will be sixteen (16) each of three different End User Devices (EUD). This equates to 24 soldiers used for pilot test and 24 soldiers for record test with two soliders per system. Data harvesting will be consolidated at the test player FOBs.

NOTE: Manual data collection forms and surveys will be provided by the Government test team ORSA.

(1)Explain the methodology:

[a] Data collection processes for quality control and accountability of human system integration (HSI), Reliability and Maintainability (RAM), Performance and Survey data for both pilot and record tests.

[b] Procedures for transferring, reducing, and reporting of all data collected.

[c] Applications that convert, merge, extract and create views of the data to assist in the data reduction and review processes.

[d] Procedures to provide quick review of RAM, Performance, HSI and survey data.

(2) Explain the procedures for maintaining all test data and manual documentation. Documentation shall include, but not be limited to, test reference documentation such as collection requirements, training plans, system description documentation, doctrine and organizational support packages, control plans, and other test related reference materials and items. Paper-based products received (surveys, questionnaires for example) shall be transferred to digital images for archival to electronic media.

(3) Explain how a forward data operations cell will be established to harvest and perform quality control of data prior to forwarding it to the data management cell.

(4) Explain the procedures to enter data into the databases in a Level III Data Collection format. RAM, Performance, HSI data shall be completed within 24 hours after data collection.

(5) Explain procedures to perform backups of all data twice each day.

(6) Explain how test data will be archived for delivery to the Government.

3.4. Data Collection Requirements

a. Period of Support: 7 Mar – 15 May b.

Requirements:

(1) Explain Methodology on:

[a] Program of Instruction (POI) for data collection training.

[b] Control plans for data collection procedures at the test site.

[c] Safety measures and operating procedures for data collection personnel as required.

[d] Training to data collectors on forms, data collection procedures, safety measures, control procedures and quality control of data.

(2) Explain data collection procedures during the pilot and record test phases.

3.5. Milestones/Deliverables:

Date

Event/Requirement/Deliverable

Responsibility

20 Feb

Opertaional Test Readiness Review (OTRR) Govt TT

6 Mar

Data Collector Handbook

TSC

Data collection training plan

19 – 23 Mar Data Collector Training TSC

2-5 Apr

NET (Fort Hood)

NOTE: Ten days prior to first day of record phase Advance Party from the GovernmentTest Team Deploys to remote test sites

30 Apr-

1 May

Pilot Test

Govt TT/TSC

8-14 May

Record Test

Govt TT/TSC

22 Jun

Data for Archive