Attachment_6_-_Test_TAR_.doc.pdf

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.

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 and the production representative RR.

2. CONTRACT INFORMATION.

2.1. Personnel identified herein are constrained by the Performance Work Statement

(PWS): All technical coordination shall be within the general scope of the contract and the Task Authorization Request. Technical coordination shall not result in any action that:

a. Constitutes an assignment of additional work outside of the contract

Performance Work Statement (PWS) or the Government requirement.

b. Constitutes a change as defined in the contract clause entitled "Changes -

Cost-Reimbursement" (FAR 52.243-2 Alt I).

c. Causes an increase in the total cost, the resource limits approved by the Contracting Officer (KO) in the approved performance estimate, or the time required for contract performance.

d. Changes in any of the expressed terms, conditions, or specifications of the contract.

e. Interferes with the Contractor's right to perform the terms and conditions of the contract.

3. DESCRIPTION OF SERVICES.

3.1 SCOPE: The Test will consist a two (2) day pilot test (Mon and Tue); and the record test 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 102 soldiers will be trained for the test at Fort Hood, of which 24 soldiers are expected to participate at each of the two locations.

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's TIP response shall describe the technical approach and methodology with associated labor for each of the below sub-paragraphs.

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).

Data harvesting will be consolidated at the test player FOBs.

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

ORSA.

(1) Attend planning meetings, providing technical input to briefing slides and discussions.

(2) Provide:

[a] Data collection 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.

(3) Establish and maintain an on-site data library(government approved share drive) for tracking of all data flowing into and out of the data management cell. Develop 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.

(4) Establish a forward data operations cell to harvest and perform quality control of data prior to forwarding it to the data management cell.

(5) Enter data into the databases in a Level III format. Data shall be completed within 24 hours after data collection. After data entry and final quality control check, all data shall be made available on automated systems to allow the Test Team ORSA and other personnel to perform essential data review.

(6) Perform backups of all data twice each day.

(7) Provide final authenticated level III test databases and data dictionaries formatted for distribution.

(8) Provide input to lessons learned during test planning and execution; present them to the test officer using the issue, discussion, and recommendation bullet format.

(9) Archive test data for delivery to the Government.

3.4. Data Collection Requirements

a. Period of Support: 7 Mar – 15 May

b. Requirements:

(1) Provide

[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) During the pilot and record test phases; collect Performance, HSI, and Reliability and Maintainability (RAM) data; SYSTEM subsystem electronic data files. Ensure quality of these files. Data will be collected on each EUD, as well as in the Green, Red, and White cells. Subsystem data files will be harvested at the end of each test scenario and provided to the data center. Data will be harvested at the Forward Operational Base (FOB) location as soldiers return from MEL scenarios.

3.5. Milestones/Deliverables:

Date Event/Requirement/Deliverable Responsibility

20 Feb OTRR 2 Govt TT

6 Mar Data Collector Handbook TSC Provide data collection training plan

19 – 23 Mar Data Collector Training TSC

2-5 Apr NET (Fort Hood) TSC

NOTE: Three weeks prior to first day of record phase Test Team Deploys to remote test sites

30 Apr- 1 May Pilot Test Govt TT/TSC

8-14 May Record Test Govt TT/TSC

15 Jun Provide final data base w/ data dictionary TSC

19 Jun Provide input for AAR/lessons learned TSC

22 Jun Provide data for Archive TSC