Attch_9_Task_Limited_Req.doc

Contract Number

Task Number – Limited Requirements Test Attachment 9

1. GENERAL TEST INFORMATION: Unless specifically changed by this task order, the contractor performance shall be in accordance with the terms and conditions of the contract. If there is a conflict, the terms and conditions of the task order shall take priority.

1.1. BACKGROUND

a. Full name of test:

b. Test Location/Dates: Fort Hood, Texas

Pilot Test: 30 April-3 May

Record Test: 7 May-8 June

Excursion 1: Fort Jackson, South Carolina, 8-15 May

Excursion 2: Reserve Component Unit, Atlanta, GA, 22-26 May

Excursion 3: New Orleans, Louisiana, 2-6 June

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

d. 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 and 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 were: AN/PRC 154 Rifleman Radio (RR), Wireless Network after Next (WNaN), and Man Atrix EUD and the production representative RR.

e. Safety/HUC: Documents are under development.

(1) Human Use Committee (HUC) constraints and requirements: None identified at this time. Late or subsequent publishing of HUC constraints and requirements will be forwarded by the TO through the TSO to the COR for inclusion in a follow-on point change or TIL.

(2) Safety issues and concerns. The risk at all levels in the performance of responsibilities pertaining to human subject participation in research and development activities must be considered IAW Section C, 1.4.3 (Safety Regulations) of the contract.

(3) Other safety issues and concerns IAW Section C, 1.3.5 (Hazardous Duty) of the contract. The following are elements of the test program which are anticipated to pose potential hazards in the course of test implementation activities. Actions should be considered to mitigate the risks associated with these hazards and should be considered in the development of the TIP.

· Radio Frequencies

f. Contracting Officer’s Representative:

g. Alternate Contracting Officer’s Representative:

1.2 SCOPE: The test participants shall be from xxxx. The Test will consist a four day pilot test, Mon-Thu; a thirty-three day record test encompassing weekends; but excluding the Memorial Day Holiday four-day holiday weekend. All test dates will be 24 hour operations. Testing shall take place in a Forward Operational Base (FOB) environment. Personnel are not expected to “chase” test players across the grid during operations; 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. Three excursions to other sites are planned during the record test per dates and locations shown in paragraph 1.1.b. above. These events are anticipated to be twelve hour missions, during weekdays only.

A total of 54 soldiers will be trained for the test at Fort Hood; of which 48 will be used for the conduct of the test. Six soldiers will be trained to serve as supernumeraries. 24 soldiers are expected to participate at each of the three excursion 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 repored by test incident report (TIR). The test team will mark the test items for eas of identification. The US Army Infantry School (USAIS) will conduct training 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 test team will conduct a 4-day pilot test to rehearse communication, control procedures, to validate data collection and reduction processes. The pilot test will consist of two 18-hour Field Training Exercises (FTX). The event will be conducted using the 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 test at Fort Hood, Texas, will consist of six 18-hour FTX scenarios with test players using blank ammunition. At the end of pilot and record tests, and upon last mission completion at each of the excursion 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.

1.3 TECHNICAL POINTS OF CONTACT:

Test Officer:

Technical Support Analyst:

Personnel identified herein are constrained by the Performance Based Work Statement (PBWS). All technical coordination shall be within the general scope of the contract and the work requirement. Technical coordination shall not result in any action that:

a. Constitutes an assignment of additional work outside Section C 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 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.

2. SPECIFIC TECHNICAL REQUIREMENT:

The contractor's TIP response shall describe the technical approach and methodology with associated labor and reimbursables for each of the below sub-paragraphs. Cost shall be separately identified by each month and segregated by fiscal years.

2.1 Instrumentation Engineering Development/Methodology Requirements

a. Point of Contact:

b. Period of Support: N/A

c. Requirements: None identified at this time.

2.2 Data Management Requirements.

a.

Point of Contact:

b.

Period of Support: 26 March-22 June c.

Requirements: There will be sixteen (16) each of three different End User Devices (EUD). Data harvesting will be consolidated at the test player FOBs.

(1) Provide weekly status reports. As a minimum, reports shall include activities accomplished during the reporting period, cost expended, balance of funds, and overtime expended by position.

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

(3) Be prepared to travel to remote test site during conduct of test as directed by the Test Officer.

(4) Modify/update OTE RAM database and forms that will be provided by the government ORSA.

(5) Develop training procedures and train data collectors on forms, collection procedures, safety measures, data accountability procedures and quality control.

(6) Conduct an “end-to-end” checkout for data collection during pilot test.

(7) Provide on-site data collection support during the pilot and record test events. Performance, Manpower and Personnel Integration (MANPRINT) and Reliability and Maintainability (RAM) data shall be collected. Data will be harvested at the Forward Operational Base (FOB) location as soldiers return from MEL scenarios.

(8) Ensure quality control and run edit checks of all data.

(9) Enter data into databases.

(10) Reduce data to level 3 within 24 hours of collection.

(11) The TSC is responsible for the completeness of all data collected in accordance with the approved test design.

(12) Provide technical input to the Capabilities and Limitations (C&L) Report.

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

(14) Maintain a data library for tracking of all data flowing into and out of the data management cell.

(15) Perform daily backups of all data.

(16) Provide data inputs to the Data Authentication Group (DAG) for authentication, and anomaly investigations and resolution to the scoring conference committee members. Provide reports modifications as needed for the DAG Scoring Conference as requested by the Test Analyst.

(17) Provide final database and data dictionary. Final database shall be submitted to the Government not later than five days after the final DAG meeting. Required media for deliverables is compact disk, to include jewel case and labels.

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

(a) Scan Raw Data Forms: Verify the scanned copy is readable and an exact copy of the original. Save the scanned forms and make them retrievable as if they were stored in paper form (manila folders). Once the verification process is completed and with approval from the Test Officer the paper forms are to be shredded.

(b) Electronic/Digital Records: If the document is received electronically or in digital format then keep it that way. No need to print the document for archiving - it can be archived in electronic format.

(c) When archiving data keep test planning files separate from raw data files, for example use separate disks.

a. Milestones/Deliverables:

DATE

EVENT/REQUIREMENT/DELIVERABLE

RESPONSIBILITY

26 Mar-15 Jun

Provide Teleconference Support

TSC

16 Apr

Provide updated database

16 Apr

Provide data training plan

30 Apr-

3 May

Pilot Test

Govt TT/TSC

2-3 May

Conduct end-to-end data run

7 May-8 Jun

Record Test

Govt TT/TSC

14 Jun

Provide technical input for C&L Report

15 Jun

Provide final data base w/ data dictionary

19 Jun

Provide input for AAR/lessons learned

22 Jun

Provide data for Archive

2.3 Instrumentation Requirements (other than engineering development).

a. Point of Contact:

b. Period of Support: N/A

c. Requirements: None identified at this time.

2.4. Logistics Requirements.

a. Point of Contact:

b.Period of Support: 26 March-22 June

c. Requirements:

(1) Design, create, and issue test team badges. Utilitize badges to ensure that only authorized personnel enter test operations areas. All logistics requirements and resources are allocated and issued based on availability.

(2) Provide the following Government Furnished Property (GFP). TSC must move items to and from the Fort Hood test site.

d. Milestones/Deliverables:

All items to be issued 18 March or as otherwise indicated below. All GFP items will be turned in NLT 17 June .

Item Description Date/Quantity

Unplanned Procurements ($400)

1 Ea HMMWV, 2 door

4 Ea Chair, Folding

12 Ea

First Aid Kit, Med

6 Ea

Flash light

8 Ea

Battery, BA-30

24 Ea

Power surge protector

5 Ea Goggles, safety

10 ea

e. Travel Requirements.

(1) Washington, DC, 5 days to attend coordination meetings

(2) Fort Jackson, SC, 3 days to attend coordination meeting

(3) New Orleans, LA, 5 days to attend coordination meetings

(4) Fort Jackson, SC, 10 days to collect data during excursion

(5) Atlanta, GA, 7 days to collect data during excursion

(6) New Orleans, LA, 7 days to collect data during excursion