TE AA Fort Hood Base TAR Re-compete 20200603.pdf

W91151-TBD Date:

Task Order (XXXX, Fort Hood Test Technology Base)

NOTE: This Task Authorization Request (TAR) is forwarded for your action in and your respond back to the Government for approval in accordance with the basic terms and conditions of the contract.

1. GENERAL INFORMATION.

1.1. FULL NAME OF EFFORT: Test Technology Support Services (TTSS) Base – Fort Hood, TX

1.2. BACKGROUND. The TTSS-Fort Hood provides technology support to US Army Operational Test Command (USAOTC) at Fort Hood and other locations as required.

Additional Task Orders will cover specific test requirements.

1.3. PRIMARY LOCATION/DATES: Fort Hood, Texas

1.4. CLASSIFICATION AND NEED-TO-KNOW: Specific tasks performed under this TAR may require personnel and facilities cleared for access at the Secret, Top Secret (TS), or Sensitive Compartment Information (SCI) levels of classification and need-to-know.

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) C.1.6.21, Safety.

1.5.1. HRPP constraints and requirements: None identified at this time. Late or subsequent publishing of HRPP constraints and requirements that affect TTSS personnel and require additional actions by the contractor shall be forwarded to the Contracting Officer Representative (COR) for inclusion in a follow-on point change.

1.5.2 Inform all personnel who enter facilities under its control, participate in, or observe Contractor-conducted activities of precautions that must be taken to mitigate safety concerns whenever a risk to personnel exist that has been assessed as negligible.

1.5.3. 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 risks associated with these hazards and should be considered in the development of the Task Implementation Plan (TIP) IAW Performance Work Statement (PWS) paragraph C.1.6.16.7 (Hazardous Duty).

1.6. CONTRACT LIMITS: Personnel identified herein are constrained by the PWS. All technical coordination shall be within the general scope of the contract and the work requirement.

1.7. POINTS OF CONTACTS:

1.7.1. COR - TBD.

1.7.2. Alternate COR (ACOR) - TBD.

1.7.3. TAR Initiators – TBD

2. SCOPE: This TAR Includes support to OTC for Fort Hood base technology support, technology developments, and technology verifications and validations. Specific test supports will be defined in separate TARs.

3. CONTRACTOR RESPONSE REQUIREMENT: The Contractor shall provide a technical methodology/approach/narrative and cost based on the requirements in this TAR as part of its proposal. The Contractor shall submit the cost (labor and reimbursable) for this base TAR in a separate tab under Attachment 5, Proposal Template as part of Volume IV, Cost. Test specific work shall not be charged to base task order.

4. COMMON CONTRACT REQUIREMENTS.

4.1. Test Support. Requirements will be defined by specific Test TAR. The Government will provide the contractor separate TARs for supporting each specific test. The contractor shall reply to the KO with a TIP IAW Performance Work Statement (PWS) Paragraph C.5.1.1. The KO funds and authorizes the TIP with a task order (TO). The Contractor shall designate a Project Leader, single Point of Contact (POC), for each test event TARs. The Contractor shall provide the following services and support in diverse environments and circumstances, ranging from Government furnished facilities, such as the permanent facilities at Fort Hood, Texas, to field test sites located at various CONUS and OCONUS locations and installations. Test support shall be provided with the full extent of base labor force approved in the Base TAR. The Contracting Officer will approve any additional labor category (ies) or hours required under specific Test TIP prior to being hired. Test support may encompass pre-test, test execution, and post-test services.

4.2. Future Test Support and Development. The contractor shall research future technical capabilities required to support testing, conduct feasibility studies, and recommended courses of action. The contractor shall analyze current and (potential) future requirements to assess the possibility of integrating increased/additional capability into the current system(s). IAW PWS paragraph C.5.1.2,Future Test Support and Development.

4.2.1. The Contractor shall collaborate with other DoD organization, such as the Army Futures Command (AFC) and ATEC Test Centers, to recommend the development, integration, and/or utilization test technologies to support future tests.

4.2.2. The Contractor shall support demonstrations and capability briefing to USAOTC and other DoD organization and dignitaries IAW PWS paragraph C.5.1.1.1.3.

4.3. Systems Engineering, Software Development, Knowledge Management, and Configuration Management Support Tasks. The Contractor shall use a common pool of personnel to the extent possible to support these tasks IAW PWS paragraphs C.5.1.3 through 16. Using this methodology, the Contractor shall develop efficiencies supporting common systems & software development incorporated throughout the PWS paragraph C.5. IAW PWS paragraphs C.5.1.3 to C.5.1.5.

4.3.1. Provide software documentation and reusable procedures for the development, integration, testing, and validation of simulation-based test architectures IAW PWS paragraph C.5.1.14, Documentation.

4.3.2. Provide software /technical support. Assess the capabilities of existing training and testing systems to determine integration requirements and to ensure systems meet test requirements. Recommend upgrades to existing training and testing systems to meet test-specific gaps IAW PWS paragraph C.5.1.13, Software Support Programs.

4.3.3. Ensure software meets test requirements to validate system-level functionality.

Provide test/accreditation plans, execute tests, analyze test results, and report findings in accreditation reports. Testing may include integration testing, load testing, systems-of-systems integration testing, and pilot end-to-end testing with focus on data usability, data correctness, and interoperability.

4.3.4. Design software and support hardware to comply with Army Cyber-security/Information Assurance (IA) policies and standards. Support reviews, tests, and demonstrations to ensure computer system security IAW PWS paragraph C.5.1.5.

4.3.5. User Acceptance Test Support. Conduct user acceptance tests to ensure developed/modified software meets tester requirements while operating in a near “real world” test environment using test scenario data IAW PWS paragraph C.5.1.3.3.

4.3.6. Verification, and Validation, and Accreditation (VV&A) (V&V) support. Support VV&A of hardware/software systems. Ensure the software and systems meet tester requirements and fulfill the intended purpose. Develop and execute V&V tests against the system and analyze the results. Develop a V&V plan to describe how the software/system will be tested. Develop a V&V report documenting the V&V activities and results IAW PWS paragraph C.5.1.13.3. The Government will use V&V results provided the Government to secure Accreditation of the system to be used for the System Under Test (SUT).

4.4. Cybersecurity Support IAW PWS paragraph C.5.1.5:

4.4.1. The Contractor shall perform requirements related to the Risk Management Framework (RMF) process to improve information security. Ensure compliance with the National Institute of Standards and Technology (NIST) 800-37 guideline. NIST 800-37 is the primary reference document for applying RMF. Support implementation of cybersecurity daily/weekly monthly/annual requirements for all OTC test technologies located at the ATIC, and OTC identified test sites. For OTC owned systems (e.g. CDL, ILTE, and two network enclaves), the contractor shall provide the Government RMF support for USAOTC’s test technologies for systems operating at Unclassified, Secret, and Top Secret/Sensitive Compartmented Information level. Support includes, but is not limited to, providing Information System Security Officer (ISSO), Information System Security Manager (ISSM), System Administrator (SA), Network Administrator (NA), and Auditor functions. The Contractor shall also provide functions such as preparing documentation, security plans, and verification procedures in accordance with certification and accreditation requirements.

4.4.2. Maintain the Enterprise Mission Assurance Support Service (eMASS) database for each system and update required documentation

4.4.3. Perform auditing functions as required. Download and review system logs to identify suspicious activities and system issues and document findings.

4.4.4. Perform continuous monitoring functions as required.

4.4.5. Track and report all USAOTC owned test technology networks/equipment.

Document the results in the weekly Cybersecurity Information System Status Tracking Report under A008, TE M, Technical Reports. Notify the Government when a tracked IT system is not expected to be certified in time for a test event.

4.4.6. Provide a life-cycle replacement plan as part of your Property Management System (PMS) to ensure test technology remains compliant with Cybersecurity and RMF requirements IAW PWS Paragraph C.5.1.5. Contractor shall recommend disposal of obsolete systems, recommend, and develop system upgrades and modifications, prepare system requirements, prepare system specifications, and conduct market research. Information shall be provided in A001 and A008, TE D and TE M, Monthly Progress Report and Technical Reports. Guidelines are listed in Accountability of ITR, OTC Memorandum 710-5.

4.4.7. Configuration Management (CM). Using configuration management software, manage and control software development, applications and documentation for multiple networks operating at different classification levels. Configuration manager is responsible for software revision control and the establishment of baselines. The CM oversees the Configuration Management Plan (CMP) and the system RMF Plan of Action and Milestones (POA&M) providing input to corrective measures IAW PWS paragraph C.5.1.15/C.5.1.16 (Configuration Management for Contract Managed System).

4.4.7.1. The contractor shall maintain the CM repository.

4.4.7.2. Media Control. The CM shall maintain strict accountability of all media (classified and unclassified) entering and leaving OTC controlled areas.

4.4.8. System Administration (SA). The system administrator shall perform system administration and security functions for multiple computer systems (servers, workstations).

Responsibilities include:

4.4.8.1. Operation and support of computer systems in a multi-server environment

4.4.8.2. Installation/configuration/operation & maintenance of system hardware and software

4.4.8.3. Database maintenance

4.4.8.4. Maintenance of Microsoft Active Directory if required

4.4.8.5. Analyzing and resolving software/hardware problems

4.4.8.6. Applying OS upgrades/patches/configuration changes

4.4.8.7. Adding/removing/updating user accounts

4.4.8.8. Management of work groups and domains

4.4.8.9. Creating backup and recovery procedures

4.4.8.10. Monitoring system performance

4.4.8.11. Implementing the DoD Security Technical Implementation Guides (STIGs) and Information Assurance Vulnerability Alerts (IAVAs).

4.5. Test Measurement Diagnostic Equipment (TMDE). Track and report TMDE calibration status and maintenance actions in a manner that captures the average cost of repairs (labor and parts) and reports equipment requiring maintenance/calibration.

Ensure TMDE systems are calibrated on schedule IAW PWS paragraph IAW PWS Section C.5.1.25.1.

4.6. Transportation Services. Provide packaging, shipping, and receiving services utilizing the most efficient and economical modes of transportation. The Installation Transportation Office (ITO) is the preferred means of transportation IAW PWS paragraph C.5.1.20 (Transportation Services).

4.7. Supply Services. Provide hardware, software, and material needed to support tests and technology upgrades. Prepare procurement packages and obtain government purchase approval. Provide repair parts, spares, equipment, software, and raw materials to meet contract requirements. The contractor shall be responsible for the storage of equipment at USAOTC designated storage facilities.

4.8. Property Control and Maintenance IAW PWS paragraphs C.5.1.22 through C.5.1.25.

4.8.1. Maintain and account for property provided by the Government under TE H, GFP Listing, IAW PWS paragraph C.3.1.2. for performance on this contract.

4.8.2. Identify obsolete and unused material for both GFP and Incidental Property IAW PWS paragraphs C.5.1.22.7 and PWS C.5.1.23. Request approval to dispose of obsolete, excess and non-reparable material. Upon approval dispose of the material.

4.8.3. Initiate actions through the COR and the Government Property Administrator to replace lost, damaged, or destroyed GFP in accordance with the contractor's approved property control plan.

4.8.4. Conduct inventories and report the results to the Government IAW PWS paragraph C.5.1.24.

4.9. Reports. Contractor shall submit all reports and deliverables IAW contract CDRLS and DIDs.

4.10. Training/Certifications. Meet Government required training and certification requirements. Personnel shall complete Government required training and certifications prior to the dates outlined in the Performance Work Statement (PWS). Training status shall be reported monthly IAW PWS paragraph C.1.6.9.

4.11. Security. Request and maintain contractor security clearance. Provide a contractor security officer and program. Submit visit request needed to support the contract IAW PWS paragraph C.1.6.7.

4.12. Contractor Personnel IAW PWS paragraph C.1.6.16.

4.12.1. Common Access Card (CAC). Request and maintain contractor CAC cards.

Ensure background checks and fingerprinting actions are completed. Submit contractor reverification request every six months. Turn in CAC with the CAC retrieval documentation when an employee employment is terminated IAW PWS Section1.6.7.5.

4.12.2. Identification Badges. Provide contractor identification badges to all employees

IAW C.1.6.7.7.

4.13. Provide contract management. Provide contract status. Submit invoices and track contract-funding status. Communicate issues, incidents, and concerns to the COR and KO, contract status IAW PWS paragraph C.5.3.2.1.6.1.

5. Specific Tasks.

5.1. Maintain and renew the required licenses for software and technology support for each technology IAW PWS paragraph C.5.1.1.1.6.3.

5.2. Support facility visits, technology demonstrations, and briefings IAW PWS paragraph C.5.1.1.3.

5.3. Test support IAW PWS paragraph C.5.1.1.

5.3.1. Support technology meetings.

5.3.2. Provide program management.

5.3.3. Provide analytical studies.

5.3.4. Support the analysis of technologies needed in future testing.

5.3.5. Perform data analysis.

5.3.6. Support quality control and assurance activities of collected and reduced data.

5.3.7. Provide configuration management for software and hardware.

5.3.8. Provide systems engineering support IAW PWS section C.5.1.3.

5.3.9. Perform requirement analysis including design, integration, and consolidation.

Provide software development, systems engineering services and integration support for modeling simulation and integration (MS&I), data collection, reduction, and analysis, and technology tool enhancement.

5.3.10. Conduct acceptance testing of technology tools provided by the Government, commercial technology, and interface equipment. Test, assess, and demonstrate technical systems and software operational capabilities. Provide evaluations, feasibility assessments, and trade-off analysis of products, concepts, and methodologies.

Provide reports of acceptance test results with recommendations.

5.3.11. In coordination with the Army Test and Evaluation Command (ATEC) Government Technology Support Team support technology V&V&A plans, reports, and requests required for operational test systems.

5.3.11.1. Support, observe, and document onsite and offsite technology V&V&A events.

5.3.11.2. Support and provide input to and record test case procedures/steps/results in support of V&V&A plan and report developments.

5.3.11.3. Create staffing comment matrices and record/track all comments and adjudications made during the plan and report staffing process.

5.3.11.4. Support and provide a lead for test case execution to control/synchronize the execution of the technology V&V&A plan.

5.3.11.5. Conduct specified test cases at the ATEC Technology Integration Center (ATIC) and other test sites.

5.3.11.6. Provide data collection support to ensure test case documentation is properly recorded, reviewed, and stored.

5.3.11.7. Provide daily test case execution summaries.

5.3.11.8. Support the conduct of technology V&V&A data reduction verification reviews.

Provide analysis of collected data as input to the Accreditation Event Report.

5.3.11.9. Provide live, virtual, constructive (LVC) simulations and Mission Command System support for technology V&V&A event(s).

5.3.11.10. Support Real Time Casualty Assessment (RTCA) and CDL integration.

5.3.11.11. Create simulation scenarios to populate Mission Command environments supporting networks with a specified amount of network traffic data over a designated period. The data to be produced by and the duration of the traffic generation shall be specified during the planning process by the TTD lead technology project officer.

5.3.12. Be capable of providing instrumentation and stimulation test support after action reports (AAR) within seven (7) days after test completion. AARs shall cover all test activities/events supported by the contractor. The AAR shall be prepared using format provided by the OTC.

5.3.13. Assess technologies needed to meet OTC requirements and provide systems architecture diagrams.

5.3.14. Based on completed test event results, identify and recommend efficiencies in OTC system development improvements and existing technologies required for a future test.

5.3.15. Identify existing technology capability gaps and recommend solutions to support future tests. Recommended solution shall consider leveraging existing technology IAW PWS paragraph C.5.1.17.1.

5.3.16. Provide support for LVC, RTCA simulation, and Mission Command Systems.

Specific test requirements will be provided during the test task order IAW PWS paragraph C.5.1.10.

5.3.17. Data Collection/Reduction/Analysis (DCRA). Provide a DCRA capability.

Contactor shall be capable of operating and integrating DCRA to meet test requirements IAW PWS paragraph C.5.1.8.

5.3.18. Integrate Cyber Electromagnetic Activities (CEMA) effects with existing RTCA functionality to increase realism in the operational testing environment IAW PWS paragraph C.5.1.12.

5.4. Be capable of supporting and operating RTCA training systems during integration events IAW PWS paragraph C.5.1.12.

5.5. Support Improved Multiple Integrated Laser Engagement System (I-MILES) and any other variants IAW PWS paragraph C.5.1.1.7.

5.5.1. As part of OTC’s Core Capabilities improvement and life cycle maintenance, the contractor shall:

5.5.2. Operate I-MILES in order to test and integrate with other OTC test technologies in order to accredit OTC’ Core Capabilities.

5.5.3. Identify I-MILES findings and recommended corrective actions and provide to Government.

5.5.4. Incorporate PM TRADE or PM ILTE I-MILES updates into OTC’s Core Capabilities.

5.6. As part of pre-test execution and daily checks, the contractor shall be capable of:

5.6.1 Verifying and validating that the unit’s MILES is properly installed and operational on the unit’s vehicle.

5.6.2. Verifying the boresight/zero of each weapon is correct.

5.6.3. Identifying MILES issues and work with the Test Team and Unit to resolve the issues. Working with the unit, actions may include but not limited to: troubleshooting, reconnect/replace cables, or exchange the components.

5.7. Systems Engineering Annual Travel Requirements:

5.7.1. Fourteen 5-day trips (travel included), specific date, and location to-be-determined to support technology process update events. No more than two (2) personnel shall support these missions. For planning purposes, use four trips to Yuma, AZ, two (2) trips to Aberdeen, MD, five (5) trips to Orlando, FL, and three (3) to Las Cruces, NM.

5.7.2. Eight (8), five (5)-day trips (travel included) to locations to be determined to technology planning meetings and technology events. No more than one (1) personnel shall support these missions. For planning purposes, use two (2) trips to Ft. Huachuca, AZ, two (2) trips to Aberdeen, MD, and four (4) trips to Orlando, FL.

6. FORT HOOD EXECUTION CENTERS SUPPORT FOR BASE SUSTAINMENT

REQUIREMENTS (IAW PWS C.5.2.1).

6.1. Provide technology support during planning, preparation, integration, and execution of USAOTC operational test events. Maintain and operate technology capabilities.

Specific operational test support missions will be provided in separate test TOs.

6.2. Integrate LVC/RTCA/Instrumentation/Mission Command technology capabilities needed to support operational test events. Provide detailed LVC/RTCA/Instrumentation/Mission Command architectures to include test control systems for each event supported IAW PWS paragraph C.5.1.10 and C.5.1.12.

6.3. Maintain the required license for each OTC technology capability.

6.4. Attend technical and test support meetings as required IAW PWS paragraph C.1.6.25.

6.5. Operate and utilize facilities and equipment to maximize its capability and readiness for support of USAOTC operational tests. Provide instrumentation system characterizations reports, studies, and demonstrations. Make acquisition recommendation to keep current with new technology.

6.6. Collaborate with other organizations to include Electronic Proving Ground, Aberdeen Test Center, Redstone Test Center, Program Executive Office for Simulation Training and Instrumentation, and laboratories such as Army Research Laboratory and Naval Research Laboratory to leverage utilization of existing technologies IAW PWS paragraph C.5.2.1.1.

6.7. LVC Simulations Support. Support operational testing by analyzing test requirements and plans and recommending LVC capability to support test planning and preparation, integration, rehearsal, simulations data collection and reduction, test control, accreditation, and execution IAW PWS section C.5.1.10.

6.7.1. Develop detailed test scenario products to support daily test activities. The Government will provide all supporting documentation associated with the test scenario products. Test specific work shall be charged to test TOs.

6.7.2. Be capable of providing information required to build the combat simulation databases necessary to support daily test activities. This information shall include, but is not limited to, unit hierarchies, unique identifiers, force dispositions, percent of strengths, table of organizations, and simulation workstation assignments.

6.7.3. Develop scripted simulation/stimulation products to support scenario flow and continuity; master events list events related to simulation/stimulation products, and incidents. This includes, but is not limited to, messages to simulate/stimulate intelligence reporting, to cue units to specific actions, and to provide continuous operations in the event of simulation system failure.

6.8. Mission Command Systems IAW PWS paragraph C.5.1.3.13.

6.8.1. Maintain Mission Command systems with the latest software releases. Maintain an in-depth knowledge of the operations of the Mission Command systems within the ATIC facility.

6.8.2. Update systems with current patches and Cybersecurity updates as they are published.

6.8.3. Provide recommendations for Mission Command and network integration hardware required to stay compatible with fielded systems and provide appropriate System of Systems (SoS) environments.

6.8.4. Setup and operate Mission Command systems/networks to support operational test events. Test specific work shall be charged to test TOs.

6.9. One Semi-Automated Forces (OneSAF) development IAW PWS paragraph C.5.1.13.

6.9.1. Provide support to the One Semi-Automated Forces (OneSAF) Test and Evaluation Community to identify shortfalls in capabilities to support OTC test requirements. Provide recommendations for added capabilities for software updates.

6.9.2. Support OneSAF software development by participation in teleconferences, Early-User Assessments (EUAs), TRADOC Project Officer (TPO) Acceptance Test, Thread Testing, and Advanced User’s Familiarization Events.

6.10. Integrated Live Virtual Constructive Test Environment (ILTE) IAW PWS paragraph C.5.1.2.1.

6.10.1. Provide support to the ILTE Test and Evaluation Community to identify shortfalls in capabilities in support of test requirements and provide recommendations for added capabilities for software updates.

6.10.2. Support technology accreditation of Integrated Live Virtual Constructive Test Environment (ILTE), Cross Domain Solution (CDS), and future technology acquisitions

6.11. Common Data Link (CDL) AW Develop detailed test scenario products to support daily test activities. The Government will provide all supporting documentation associated with the test scenario products. IAW PWS paragraph C.5.1.13 (Software Support Programs).

6.11.1. Maintain CDL interfaces such as Test and Training Enabling Architecture (TENA), Distributed Interactive Simulation (DIS), and High Level Architecture (HLA) to provide a capability to integrate dissimilar systems.

6.11.2. Provide recommendations for upgrades and solutions to support interfaces with evolving capability of instrumentation systems, simulation systems, and other devices such as Network Time Protocol Server; in support of USAOTC operational test requirements.

6.12. ATIC Travel Annual Requirements:

6.12.1. Six, six (6)-day trips (travel included) to Orlando, Florida, specific dates to be determined, to support participation in OneSAF activities. No more than two (2) person shall support these missions.

6.12.2. Four (four), five (5)-day trips (travel included) to locations to be determined to support a site survey in support of test planning. No more than two (2) personnel shall support these missions. For planning purposes, use Ft. Lewis, WA.

6.12.3. Three (3), five (5)-day trips (travel included), specific date and location to-be-determined to support RMF process update events. No more than two (2) personnel shall support these missions. For planning purpose, use Ft. Huachuca, AZ.

6.12.4. Four (4), five (5)-day trips (travel included) to locations to be determined to support test-planning meetings. No more than one (1) personnel shall support these missions. For planning purpose, use Aberdeen Proving Ground, MD.

6.12.5. Two (2), five (5)-day trip (travel included), specific date, and location to-be-determined to support WireShark familiarization. No more than two (2) personnel shall support these missions. For planning purpose, use Los Angeles, CA.

7. REPORTING REQUIREMENTS:

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

7.2. Documents shall be delivered in electronic format unless otherwise specified by the COR or the KO. All documentation shall be in accordance with the Contract Data Requirement List (CDRL), unless otherwise directed by the Contracting Officer’s Representative Office, USAOTC, G4, Fort Hood, Texas 76544-5068.

7.3. Request all deliverables documents be delivered to USAOTC, ATTN: COR, Fort Hood, 76544-5068. Delivery of documentation to personnel other than the COR will be coordinated with the COR/Contracting Officer.

7.4. Milestones: Milestone/Deliverable dates shall be listed in chronological order of required delivery. Travel dates and specifics will be provided with Task Instruction Letters (TIL) s. The base TO and milestones will be updated quarterly.

Date Event/Deliverables Year 2021 Start Work Weekly Task Order Cost Report Weekly Cyber-security Information System Tracking Report Weekly Information Assurance Status Tracking Report Monthly Progress Report Monthly Personnel Status Monthly CIMS Report Monthly Sensitive Item Inventory Quarterly Progress Briefing Quarterly Non-Tactical Vehicle Utilization Report Annually Incidental Property Inventory Annually GFP Master Report

4.8. Property Control and Maintenance IAW PWS paragraphs C.5.1.22 through C.5.1.25.