Attachment 1 Sample Test Scenario TAR 20210329 16 Apr 21 .pdf
PDF 181 KB Posted
- Solicitation number
- W91151-21-R-0012
About this file
This solicitation seeks proposals for test technology support services. The U.S. Army Operational Test Command at Fort Hood, Texas requires systems engineering expertise, software support, operations and integration assistance, analytical studies, and instrumentation support for operational test events to be conducted at locations in the continental U.S. and overseas. The performance period is 60 months with a 30-day phase-in, and the contract type is cost-plus-fixed-fee. The North American Industry Classification System code is 541330. Responses are due by April 14, 2021 under the revised solicitation number W91151-21-R-0012. The federal agency is the U.S. Army Materiel Command Mission and Installation Contracting Command Fort Hood.
View the file
Other files
Show 40 more
Latest 50 of 66 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
NOTE: This Test Task Authorization Request (TAR) is forwarded for your action in accordance with the basic terms and conditions of the contract.
1. GENERAL INFORMATION.
1.1. FULL NAME OF EFFORT: Tank Destroyer, Follow-on Operational Test &Evaluation
(FOT&E).
1.2. TEST LOCATIONS/DATES: The pilot test will be conducted at Fort Hood (Continental United States (CONUS) and at JBLM, Joint Base Ft. Lewis, while record test will be conducted in Stuttgart, Germany, Outside CONUS (OCONUS).
1.2.1 Verification and Validation (V&V) event: 11 – 22 June XXXX
1.2.2 Pilot Test: 6 - 10 Sep XXXX
1.2.3 Record Test: 14 Sep – 14 Oct XXXX
1.3. SYSTEM/FUNCTIONAL DESCRIPTON:
Tank Destroyer provides new communication systems and weapon system upgrades.
The Tank Destroyer with a scout Mission Equipment Package (MEP) modification, provides infantry and Cavalry (CAV) scouts a unique based platform in lieu of the Reconnaissance Vehicle they would have used in FBH equipped SBCTs. To enable the accomplishment of unique mission capabilities, unique MEPs are integrated onto a common platform. Over the course of multiple deployments, kits were applied to the platform primarily to enhance force protection and survivability, as well as to enhance Command and Control (C2). The test team will conduct test events that will consist of a combination of Force on Force missions against a representative threat, which will stress the system in order to gather the necessary data using a combination of instrumentation and manual collection procedures.
1.4. CLASSIFICATION: This TAR is UNCLASSIFIED. Some work during test preparation will require personnel to have secret clearances.
1.4.1. The Live Virtual Constructive (LVC) networks are unclassified.
1.5. Safety/Human Research and Protection Plan (HRPP): 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 In Accordance With (IAW) Performance Work Statement (PWS) Section C.1.6.21 (Safety) of the contract.
1.5.1. HRPP constraints and requirements: None identified at this time. Late or subsequent publishing of HRPP constraints and requirements that affect Test Technology Support Service (TTSS) personnel and require additional actions by the TTSS shall be forwarded to Contracting Officer’s Representative (COR) for inclusion in a follow-on point change.
1.5.2. Other safety issues and concerns IAW PWS Section C.1.6.16.7 (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 consider to mitigate risks associated with these hazards and should be considered in the development of the TIP.
a. Radio Frequencies
b. Power Interfaces
1.6. TECHNICAL POINTS OF CONTACT
1.6.1. Contracting Officer’s Representative (COR): TBD, USAOTC G-4, 254-288-xxxx
1.6.2. Alternate COR: TBD, USAOTC G-4, 254-288-xxxx
1.6.3. Technical POC: TBD, USAOTC Test Technology Directorate (TTD), 254-288-xxxx
1.6.4. Test Officer: TBD, 254-288-xxxx
1.6.5. Assistant Test Officer: TBD, USAOTC Maneuver Test Directorate (MTD), 254- 288-xxxx
1.6.6. Operation Officer: TBD, USAOTC MTD, 254-288-xxxx
1.7. CONTRACT LIMITS: Personnel identified herein are constrained by the PWS. All technical coordination shall be within the general scope of the contract and the TAR.
1.7.1. Constitutes an assignment of additional work outside Section C or the Government requirement.
1.7.2. Constitutes a change as defined in the contract clause entitled "Changes -Cost- Reimbursement" (FAR 52.243-2 Alt I).
1.7.3. 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.
1.7.4. Changes in any of the expressed terms, conditions, or specifications of the contract.
1.7.5. Interferes with the Contractor's right to perform the terms and conditions of the contract.
2. SCOPE: To provide support as described in paragraph 3 below, “Specific Technical Requirements.”
3. SPECIFIC TECHNICAL REQUIREMENTS: The Contractor shall provide a technical methodology/approach/narrative to include labor categories and hours based on the requirements in this TAR using Contract Data Requirements List (CDRL) A003, Technical Exhibit (TE) F, TIP and Attachment 7, Sample Test TAR Position and Labor Proposal. The Contractor shall describe its technical methodology/approach/narrative in the TIP (TE F) as part of Volume II – Subfactor 4. The labor categories and hours shall be separately identified by each month and segregated by fiscal year and provide in Attachment 7. A cost is not required for this Subfactor.
3.1. Participate in test team weekly planning meetings and other weekly meetings.
3.2. Provide a plan to confirm Common Data Link (CDL)/ Real Time Casualty Assessment (RTCA) Instrumentation Training System interface during the Verification and Validation (V&V) test.
3.3. Support scenario development for the V&V event.
3.4. Support the V&V event at Joint Base Ft. Lewis McChord (JBLM) 11 - 22 June XXXX. V&V support shall include One Semi-automated Forces (OneSAF), Extensible Command, Control, Communications, Computers, Intelligence (C4I) Instrumentation Suite (ExCIS) and if these systems have been integrated into the CDL/RTCA Instrumentation interface.
3.5. Support the development of the V&V plan, report, and Accreditation Package.
3.6. Develop a Live Virtual Constructive (LVC) architecture to support indirect fires and Improvises Explosive Device (IED) missions using the CDL-RTCA Instrumentation interface. The LVC architecture shall also include OneSAF, ExCIS, and Mission Command systems.
3.7. The LVC architecture will be located in the Simulations facility at JBLM. Network connectivity at the facility will be provided.
3.8. Setup and operate the LVC architecture at the ATIC during the pilot and record test at Fort Hood.
3.9. Setup and operate a Blue Force Tracker (BFT) system in the test team operations cell at the ATIC during the Pilot and record test. The BFT roles and required graphics will be provided by the test team.
3.10. The workday will be 8 hours during planning and test site preparation. The workday will be 10 hours during V&V.
3.11 The workday will be 24-hours during pilot and record test. Weekend work will be required during the pilot and record test. The record test will be conducted at Stuttgart, Germany.
3.12. All platforms shall meet Risk Management Framework (RMF) cybersecurity requirements. The RMF requirement for an alternate work site will be the responsibility of the Government. Material purchase and systems designs presented shall comply with RMF rules and guidelines IAW PWS Section C.2.1.21.
3.13. Provide a lessons learned report that includes an assessment of the utility and appropriateness of test technologies, modeling, and simulation for test support at the conclusion of the test.
4. TRAVEL REQUIREMENTS:
4.1. One five-day trip (travel included) to JBLM and Yakima WA to attend the Final Planning Conference and to visit the JBLM RTCA Instrumentation team to prepare for the V&V event. No more than two (2) personnel shall travel to support this mission.
Scheduled for 21 - 25 May XXXX.
4.2. One fifteen-day trip (travel included) to Ft. Lewis/JBLM, WA, (11 – 25 June XXXX) for V&V event. Provide CDL, ExCIS, and OneSAF, support for indirect fires and RTCA data recording. No more than five personnel shall travel to support this mission.
4.3 One 32 day trip (travel included) to Stuttgart, Germany for set up record test (11 Sep to 14 Oct XXXX) will be required. No more than eight personnel shall travel to support this mission.
5. REPORTING REQUIREMENTS:
5.1. Delivery location for the above requirements (documentation) is USAOTC, G4, ATTN: Contracting Officer's Representative (COR), Fort Hood, Texas 76544-5068, with copy furnished to the Contracting Officer.
5.2. All documentation shall be in accordance with the CDRL A006, TE K, Test Technology Validation Reports unless otherwise directed by the Contracting Officer’s Representative Office, USAOTC, G4, Fort Hood, Texas 76544-5068.
5.3. Request all deliverable documents be delivered to USAOTC, ATTN: COR, Fort Hood, 76544-5068. Documents shall be delivered in electronic format unless otherwise specified by the COR or the KO. Delivery of documentation to personnel other than the COR will be coordinated with the COR/Contracting Officer.
5.4. Milestones: Milestone/Deliverable dates shall be listed in chronological order of required delivery.
DATE EVENT/REQUIREMENT/DELIVERABLE
4 May XXXX Start supporting planning efforts and meetings
21 – 25 May XXXX Site visit at Joint Base Lewis –McChord
(JBLM)
1 Jun XXXX Provide input to V&V Plan (CDL/RTCA
Instrumentation interface)
11 - 22 June XXXX Travel, setup and execute V&V event @ JBLM
29 June XXXX Submit V&V event CDL and RTCA data to TTD
13 July XXXX Input to V&V report
23 - 31Aug XXXX Setup CDL, ExCIS, OneSAF, BFT, and
Mission Command in the ATIC, Ft. Hood.
04 Sep XXXX LVC/BFT capability fully operational
06 – 10 Sep XXXX Pilot Test
14 Sep – 14 Oct XXXX Record Test
16 Oct XXXX Return to Fort Hood, TX
18 Oct XXXX Lessons Learned Report
19 Oct XXXX Equipment returned to pre-test configuration
File details come from the government source that posted it. Updated .