TE K - AMDTD Base TAR Final Revision 20220105 Clean.docx

AIR AND MISSILE DEFENSE TEST DIRECTORATE (AMDTD)

TASK AUTHORIZATION REQUIREMENT (TAR) BASE SUPPORT SERVICES

FORT BLISS, TX

1. GENERAL INFORMATION: This TAR is forwarded for your action in accordance with the basic terms and conditions of the contract.

1.1. PERFORMANCE REQUIREMENTS:

1.1.1. Hours of Work. The contractor shall provide coverage at the specified government site from 7:30 a.m. to 4:30 p.m. During test periods, the contractor shall be required to provide coverage as necessary to support planning and testing objectives. Such work often extends beyond the period of coverage described above with possible 24-hour operations. Government-furnished resources will be made available to the contractor when overtime is required.

1.1.2. During performance of the individual task order, contractor must work the required regular hours (80 hours within two-week pay period under the overall project) before overtime hours are justified and approved. During the course of all events, extended hours of work may be required.

1.1.3. Place of Performance:

Operational Test Command (OTC) Air and Missile Defense Test Directorate (AMDTD) 1660 Bradley Road Fort Bliss, Texas 79916-6816

Fort Bliss, TX and White Sands Test Center (WSTC), NM ranges or remote locations as specified by the test requirements (transportation will be provided by the government).

1.1.4. Period of Performance: 20 April 20XX – 19 April 20XX.

1.2. Task Implementation Plan (TIP): The contractor shall develop the Task Implementation Plan (TIP) in support of the AMDTD mission within five (5) working days. The contractor shall provide a breakdown of skills, hours, and funds in their proposal or for any subsequent proposal changes but funding and hours will be as shown in the progress reports with the remaining availability of funds. Task Implementation Plan shall include methodology and mitigation strategies to adapt to schedule changes, system under test (SUT) equipment quantity variations, additional test events that require simultaneous execution.

1.3. Funding: This task is subject to incremental funding and availability of funds.

1.4. Contractor Officer’s Representative (COR) and Technical Point of Contact: TBD

1.5. Contract Limits: 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 work requirement. The Contractor is prohibited from performing an action which:

1.5.1. Constitutes an assignment of additional work outside of the Government requirement.

1.5.2. 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.5.3. Changes in any of the expressed terms, conditions, or specifications of the contract.

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

2. BASE OPERATIONS SUPPORT: Services specified below are core support requirements to OTC AMDTD’s base support mission to the Army Test and Evaluation Command (ATEC) units operating at Fort Bliss, Texas. Base services are required during test periods as well as during non-test periods. During test periods – test/projects will fund test support task. The Base Support Task Order funds the network support, Automatic Data Processing (ADP) inventory clerical support, data management services, and security clerical functions supporting ATEC operations at Fort Bliss. The following task list specifies the required level of support:

2.1. Information Technology Support (Test Support Networks): AMDTD Information Technology (IT) Department manages Closed Restricted Network’s (CRN).

2.1.1. Tier III or Tier III-R LAN Access Requirement. All Contractor personnel requiring access to the OTC LAN and other Information Technology (IT) systems involving sensitive information with higher-level access shall be required to have a Tier III. Contractor employees performing on this contract in positions designated ADP I, ADP II, and ADP III sensitive positions, per AR 380-67 paragraph 3-54, 3-67, and Appendix K will have appropriate investigations. Document current clearance in Defense Information System for Security (DISS) for verification.

2.1.2. Obtain and maintain certifications at Information Assurance Certification Training (IAT) II level listed in the current version of DoD 8570.01-M for IAT II.

2.1.3. Provide CRN user level support to approximately 120 OTC / AEC / WSMR / EPG users operating on Fort Bliss. During test operations, additional IT requirements beyond the core support requirements will be documented in a test task order.

2.1.4. Create, maintain, and delete user’s accounts both local and in Active Directory supporting Closed Restricted Networks.

2.1.5. Maintain CRN Active Directory users and group’s compliancy checks, Group Policy objects, and Organizational Units (OU’s).

2.1.6. Maintain logs in support of CRN help desk functions and changes including daily logs of system status, issues, and resolutions and will generate a report to information system owner.

2.1.7. Works closely with CRN Information System Owner Government POC on all software and hardware upgrades. Installs computer software, hardware, networking switches and components, and system updates.

2.1.8. Creates and performs computer imaging for lifecycle replacement for CRN’s equipment while upholding the system accreditation baseline support. (OTC and AMDTD Department of the Army (DAC) manage lifecycle replacement program).

2.1.9. Identify, fabricate as needed, and perform cable and wiring connections when installing, testing, computer, and office equipment in support of test network CRN’s.

2.1.10. Proficient in performing Administration on CRN of virtual machines in a hosted VMware environment, while maintaining system availability and ability to install, setup, deploy and decommission virtual machines. System Administrator will also maintain systems snapshots, maintain network attached storage including storage pools, network files services (NFS), storage volumes, network shares, and security groups.

2.1.11. Performs server, computer and office machine preventive maintenance and repairs for example, component replacement as required to keep CRN IT systems operational.

2.1.12. Provide maintenance to CRN network switches, routers, disk arrays, and back-ups as coordinated with Government POC Information System Owner or Information System Security Manager.

2.1.13. Conducts daily and weekly network maintenance tasks to include compliance scans, Risk Management Framework (RMF) control tasks, and weekly system back-ups of CRN networks. Provides artifacts to support the system records for System Accreditation Purposes in eMASS based on the continuous monitoring schedule of the CRN.

2.1.14. Provides network extension support from AMDTD to remote ranges in support of test operations. Network extensions may include configuring network switches and routers (coordinated through AMDTD configuration management board), and hardware installation (to include user level cabling) at remote range facilities. Proficient in routing, layer 3 networking, tunneling protocols, and layer 2 networking.

2.1.15. Provide CRN network switch maintenance and user support, to include printers, port security, Security Technical Implementation Guides (STIG’s), and General-Purpose Operating System Security Requirements Guide (SRG).

2.1.16. Provide support with RMF documents for accreditation and perform task that meet network (RMF) controls (National Institute of Standards and Technology ((NIST) 800-54A)) in support of AMDTD Closed Restricted Network’s (CRN).

2.1.17. Obtains unclassified and classified Enterprise Mission Assurance Support Service (eMASS) and Army knowledge On-line (AKO) accounts (AMDTD will sponsor contractor accounts to meet RMF mission).

2.1.18. Trained and certified on RMF accreditation process and RMF Control assessment. Plan of Action and Milestones (POA&M’s), system security plan submission requirements, and artifact collection and maintenance in eMASS and submission of eMASS control updates as defined by the system categorization.

2.1.19. Establishes and maintain accurate notes, network drawings, and manuals describing all aspects of required equipment and facilities in regards to network systems and deployed networks in a disconnected environment. Will review and upload audit logs, event logs daily, and perform transfers of data and accountability of removable media as a trusted agent as required.

2.1.20. Provide CRN system owner recommended updates to Standard Operating Procedures (SOP) documentation of RMF controls in eMASS employed on each CRN. Updates are due as new STIG/SRG’s are released and/or during time of accreditation or system validation.

2.1.21. Provides support to handle both Controlled Cryptographic Item (CCI) and Communications Security (COMSEC) material (AMDTD DA Civilians or Soldiers manage the COMSEC hand receipt account). Contract personnel will perform COMSEC loading and destruction tasks to include associated COMSEC record keeping documentation.

2.1.22. Requires valid state driver's license and must be able to obtain a Government vehicle license.

2.1.23. Maintain records and documents in support of individual tasks.

2.1.24. Performs system Life Cycle Replacement (LCR) of systems, servers, network hardware, and components as it pertains to the vendor published End of Life (EOL) documentation and will keep records of the hardware and software for tracking purposes to aid in the procurement of replacement hardware and software to maintain the security requirements and availability of the overall systems.

2.2. Automatic Data Processing (ADP) Logistical Support:

2.2.1. Provides Incidental Government Property inventory documentation support.

2.1.27. Provide support with Incidental Government Property (TE M) Inventory Support to support issuing, repairing, and/or turn-in of office and AMDTD equipment and software.

2.2.2. Maintains records on the destination, warranty program, classification, of all ADP equipment, to include hardware and software.

2.2.3. The Contractor shall provide support to updates to GCSS-Army by scanning, or manual entry into the database, all pertinent information including but not limited to: serial numbers, item type, ownership, and equipment incident reports, for all ADP equipment provided under TE M.

2.2.4. Maintains and ensures the disposition of ADP submitted for repair for warranty return and other outside agencies.

2.2.5. Prepares reports encompassing the different types of ADP equipment to include, hard-drive, computer processing units (CPUs), displays/monitors, accessories, memories, speed and any other pertinent information as requested by AMDTD.

2.2.6. Maintains and coordinates with the government for re-supply of ADP supplies to eliminate/reduce shortages to ensure the ADP section, mission, and test support are successful.

2.2.7. Maintain records and documents in support individual tasks

2.2.8. Requires state driver’s license.

2.3. Test System Programmers:

2.3.1. Support all phases of the test, development, planning, execution, and reporting. When test funds become available this task will be funded by test funds. AMDTD DA Civilians provide project management guidance to programmers coding software in support of notebook/table based data collections tools.

2.3.2. Provides Computer Sciences and Programming services to build integrated database support to ATEC, OTC and Training and Doctrine Command (TRADOC) Cross Functional Team (CFT) events, Joint Warfighting Assessments (JWAs) and other ATEC test missions as required. AMDTD DACs provide project management and Structured Query Language (SQL) server administrator for integrated database operations. If programmers are assigned to support OTC test operations outside of aforementioned events/activities, programmers will be listed and funded through the test task order.

2.3.3. The contractor shall not disclose any information or any information derived there from to any third person, including but not limited to information related to: software development and design, business or software architecture, software not yet known to the public, clients or prospective clients, internal communications, events, or meetings, or any other research, development, operations, marketing, transactions, regulatory affairs, discoveries, inventions, methods, processes, articles, materials, algorithms, formulas, specifications, designs, drawings, data, strategies, plans, prospects, know-how and ideas, whether tangible or intangible, and including all copies, analyses and other derivatives thereof

2.3.4. Contractor shall provide database management coding and debugging service using Statistical Analysis Software (SaS), SQL, MySQL, Microsoft Access, and Excel programs to provide notebook or tablet based data entry capability to data collectors using windows based operating systems.

2.3.5. Contractor shall include coding support documentation (embedded comments) within Government owned database design, graphical user interface and databases using SAS, SQL, MySQL, Microsoft (MS) Access or MS Excel spreadsheets. Documents and maintains accurate notes, plans, diagrams, drawings, schematics, and forms to enable a clear understanding of database historical records. The contractor shall participate in reviewing test plans and data point requirements

2.3.6. Support beta testing and customer tests on prototype data collection graphic user interfaces and databases supported by the test support network to provide end-user and analyst required data inputs and outputs prior to the pilot test.

2.3.7. During coding and beta testing, provide troubleshooting support to AMDTD project manager and Computer Scientist to resolve interface, data collection, reduction, and analysis programming issues within 72 hours.

2.3.8. During test operations, provide troubleshooting support to AMDTD project manager and Computer Scientist to resolve interface, data collection, reduction and analysis programming issues within 24 hours.

2.3.9. Provides software data reduction support during test operations.

2.3.10. Maintain records and documents in support individual tasks.

2.3.11. Provide input to reports on data collection inputs and database performance statistics.

2.3.12. Provides to Government for approval, recommended changes to data collection procedures to improve existing functions.

2.3.13. Requires valid state driver's license.

2.4. Security Support PWS 5.6:

2.4.1. Carries out the duties of the designated key custodian IAW standing instructions (SOP provided by the Government), required training, or accepted practices in accordance with AR 190-51. Reviewing prescribed procedures to enhance key control for the test directorate. Issues, rotates, and accounts for keys, locks, and locking devices assigned to test directorate.

2.4.2. Serves as the initial point of contact for all visitors requiring access to the facilities. Maintains databases as required to enable tracking of items of interest. Maintains a daily journal of all incoming and outgoing visitors.

2.4.3. Maintains access rosters and procedures documents to be used to grant personnel to classified material and areas. Maintains a document file that supports entries to property accountability records.

2.4.4. Performs a variety of security duties by providing briefings, process inbound and outbound forms, issuing and retrieving badges, submitting outbound visit request, receiving inbound visit request, and verify security clearances for all new personnel and visitors.

2.4.5. Monitor video surveillance to ensure that only authorized personnel access the test command in support of maintaining the physical security of the test directorate facilities.

2.4.6. Maintain records and documents in support of individual tasks.

2.4.7. Requires valid state driver’s license.

2.4.8. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Secret” and requires contractors to comply with the Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DOD 5220.22-M); any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

2.4.9. All contractor employees shall process through the security office of the requiring activity. and issued a badge that fully identifies that contractor employee.

2.4.10. Collection of unclassified data using manual data collection methods is required. Data associated with this task will be covered by the Privacy Act of 1974; therefore, all contractor personnel assigned will be required to take appropriate actions to prevent disclosure of this information.

2.4.11. Access and General Protection/Security Policy and Procedures. Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

2.5. Technical Data Collection and Support Equipment:

2.5.1. Provide detailed methodologies and processes to show an understanding of required operational test support. The contractor shall provide systems hardware and software development, operations, and maintenance for business and scientific/engineering applications. The contractor shall support technical operations in the areas of test planning and coordination: test resources, data collection (automated/manual), data processing/reduction, data management, and report generation for SUTs. The following areas are examples (referenced to paragraphs in PWS section 5) of support requirements associated with sustainment operations:

2.5.1.1. Review data collection/instrumentation system performance for planning, data collection, reduction and reporting (Ref. 5.2.1.5)

2.5.1.2. Conduct interoperability tests of instrumentation to verify non-interference among different pieces of instrumentation and tactical systems (Ref. 5.4.1.2)

2.5.1.3. Perform instrumentation requirements analysis including design, integration, and consolidation as required by SUT data collection requirements (Ref. 5.2.1.2, 5.3.3)

2.5.1.4. Provide software scripts and documentation for new and existing test technology systems, communication systems, network systems, data collection systems, and engineering support systems.

2.5.1.5. Provide software to merge data, assure data quality, reduce data, and produce data products for test data authentication. Data products shall be in formats required by customers. Data visualization, selection, and manipulation tools shall be developed and used to help the customer better use the data IAW PWS 5.4.

2.5.1.6. Access the capability of existing software to meet test requirements. Recommend upgrades, provide programming and design of software.

2.5.1.7. Provide technical capabilities in the following systems: mechanical, electronic, electrical, digital design, radio frequency, electrical magnetic interference (EMI), computer network, computer, software, embedded software, project, systems integration, communications, GPS tracking, and electro-optical (Ref.5.4.1.2)

2.5.1.8. Software development, enhancements, or scripts i.e. to automate the extraction, movement, and storage of data from SUT (Ref. 5.4.3)

2.5.1.9. Provide support in managing property actions, ensure equipment location is documented, ensure that all supplies and equipment received are documented and coordinated with equipment owners responsible for accountability (Ref. 5.2.1.4).

Note: There is no GFP on this contract. Contractor shall utilize Incidental Government Property, TE M. identified as incidental property to the place of performance.

2.5.1.9.1. Contractor shall be required to access share drive to provide inventory-tracking support for data collection/instrumentation equipment.

2.5.1.9.2. Contractor shall maintain records on the destination, warranty program, classification, of data collection equipment, to include hard-drive, computer-processing units (CPUs), displays/monitors, peripherals and software.

2.5.1.9.3. Contractor maintains, updates, and correlates provided issue and receiving documents by either scanning, or manual entry into a database (typically spreadsheet) pertinent information as to serial numbers, item type, location, and equipment incident reports.

2.5.1.9.4. Maintains, updates, and correlates by either scanning, or manual entry into a database all pertinent information as to serial numbers, item type, ownership, and equipment incident reports, for all data collection equipment.

2.5.1.9.5. Records the disposition of equipment submitted for repair or warranty return. Tracks and identifies items requiring re-supply of data collection equipment supplies to eliminate/reduce shortages ensure the test data collection mission, and support functions are successful.

2.5.1.9.6. Prepares reports encompassing the different types of data collection equipment to include, hard-drive, computer processing units (CPUs), displays/monitors, accessories, memories, speed and any other pertinent information as requested by TSD.

2.5.1.9.7. Maintains and coordinates with the government for re-supply of instrumentation supplies and equipment to eliminate/reduce shortages to ensure the branch mission and test support are successful.

2.5.1.9.8.. Maintain records and documents in support individual tasks.

2.5.1.10. Support personnel shall attend meetings, conferences, training, and integration working groups as needed to support test event planning and execution.

2.5.1.11. Operate equipment to concurrently interface with modeling and simulation devices and network (Ref. PWS Section 5)

2.5.1.12. Provide Instrumentation Description Documentation (Ref. PWS Section 5).

2.5.1.13. Provide technical information and data to support instrumentation certification/accreditation report for Mission SUT accreditation (Ref. PWS Section 5).

2.5.1.14. Demonstrate instrumentation performance to selected integrated product team members when required by test agencies (Ref. PWS Section 5).

2.5.1.15. Provide technical support for collection of instrumentation and/or SUT data for ATEC instrumentation certification/accreditation/verification and validation (V&V). Contractor shall collect test data, deliver test data, and support certification/accreditation/V&V test report. Instrumentation systems and SUT shall be in the configuration planned for the test event. Software and hardware versions used in the test shall be reported in the certification/accreditation/V&V report; test shall show that the instrumentation meets the following requirements (Ref. PWS Section 5). :

2.5.1.15.1. The Contractor shall ensure the Instrumentation is not intrusive, produces the required test data, and the data meets the evaluator’s requirements.

2.5.1.15.2. The Contractors shall ensure the instrumentation performs the required tasks

2.5.1.16. The Contractor shall conduct periodic maintenance checks and services on applicable instrumentation support equipment/vehicles.

2.5.1.17. The Contractor shall conduct and document maintenance/repair actions using automated maintenance tracking system (GCSS-Army) on support equipment and vehicles.

2.5.1.18. Provide recommendations to determine hardware mounting solutions for test instrumentation on SUT/SUE node/vehicles. Description of mounting bracket requirements will be coordinated with TSD machine shop for fabrication.

2.5.2. Provide detailed methodologies and processes to show an understanding of required operational test support. Provide personnel to support technical operations. Maintain, monitor, retrieve data, and appropriately configure test data collection devices for all assigned test events. Provide technical development and research expertise to support test instrumentation enhancements, design, and configuration per data, data collection, and data reduction requirements. Provide technical skills to install, remove, and operate data collection equipment; collect and retrieve SUT data using data collection systems on various military weapon and/or communication systems. Provide technical knowledge and skills to perform computer, network, audio/video, integrated system operations on equipment/systems within boundaries of the accredited networks. Operate and control computer systems using a variety of operating systems/data collection applications and possess a thorough understanding of the open systems interconnection (OSI) model.

2.5.2.1 Provide software development and documentation for new and existing test technology systems, data processing systems, data visualization systems, network systems, and engineering support systems.

2.5.2.2. Provide software to merge data, assure data quality, reduce data, and produce data products. Data products shall be in formats required by customers. Data visualization, selection, and manipulation tools shall be developed and used to help the customer better use the data IAW PWS 5.4.

2.5.2.3. Access the capability of existing software to meet test requirements. Recommend upgrades, provide programming and design of software.

2.5.3. Reduce and/or process automated/manual/video data products to information level (level III) format; generate required routines, data bases and reports. Provide appropriate products and support for test data analysis as events of interest are correlated by time. This data will be used to evaluate the effectiveness and suitability of the SUT (Ref. PWS Section 5.2).

2.5.4. Establish and maintain network paths and RF communications supportive of digital and analog data collection. Operate and maintain associated test support equipment: satellite communications, simulators, digital video recording, technical vehicles, mobile laboratories, mobile antenna towers, power generation equipment, lighting units, oscilloscopes, amplifiers, radios, antennas, network switches/routers, Tactical Local Area Network Encryption (TACLANE), cabling, automated data processing computers, and office computers (Ref. PWS Section 5).

2.5.5. Support Accredited Information System Owners with execution of Risk Management Framework (RMF) accreditation of data collection systems, perform tasks that meet network RMF controls (National Institute of Standards and Technology ((NIST) 800-54A), and prepare documents in support of information systems. Personnel shall be trained and certified on RMF accreditation process, RMF Control assessment, and use of enterprise Mission Assurance Support Service (eMASS) application. eMASS is used for the automated RMF process and required documentation actions to support the Information System Owners Authorization to Operate (ATO) accreditation. Contractor shall use Security Technical Implementation Guide, a cybersecurity methodology for standardizing security protocols within networks, servers, computers, and logical designs to enhance overall security.

2.5.5.1. Provide approved system administration responsibility for the information system in support of instrumentation/data collection and operating systems in alignment with the accredited systems authorized baseline.

2.5.5.2. Provide Accredited Information System Owners with updates to the Plan of Action and Milestones (POAM) no later than the 23th day of each month IAW CDRL A010, TE N. Other document input required to the Information System Owner for RMF document updates include but not limited to document reviews; change logs, audit reviews pulled from systems; administrative updates; and integration to other systems (e.g. MOAs with other system owners). Management of POA&Ms is performed in eMASS.

2.5.5.3. Provide Accredited Information System Owners support to maintain RMF system administration support for Authorization to Operate (ATO) of one (1) information system network and one (1) software ATO.

2.5.5.4. Support the Government ISSO requirements with sustaining system and network security.

2.5.5.5. Support Accredited Information System Owners with analysis of all new Security Technical Implementation Guide (STIG)s which are published quarterly by the Defense Information Systems Agency (DISA) and provide updates as required by Government policy/ guidance.

2.5.5.6. Support Accredited Information System Owners with executing STIG weekly/monthly network scans for vulnerabilities; conduct and document continuous security risk assessments including monitoring, investigation and reporting of security risk as required by government policy/guidance

2.5.5.7. Support Accredited Information System Owners to identify and document network weaknesses using DoD defined tool set and report to cyber-security personnel and propose courses of action to resolve system weaknesses

2.5.5.8. Assist Government Accredited Information System Owners with maintaining the Information Assurance Vulnerability Management (IAVM) Program; deploy software patches and support measures to prevent intrusion and other security problems associated with SYSTEM HIGH operations.

2.5.5.9. Provide Accredited Information System Owners with System Administrators in support of test events to support the maintenance and configuration management of information systems; provide field level support as required to sustain ATOs; adjustment of configurations within the boundaries of the ATO or proposed changes by approved Configuration Control Review Board (CCRB) in alignment with current standards as mandated by the Information system owner and approved by the authorizing official.

2.5.5.10. Provide Accredited Information System Owners with System Administrators to support verification and validation (V&V) of all test support automated information technology (AIT). Ensure data collection network diagrams are developed for all SUT integrations, verified, and validated on test site.

2.5.5.11. Verify on-site security guidelines are within ATO requirements.

2.5.5.12. Support instrumentation/data collection equipment certification and accreditation activities for each test.

2.5.6. As applicable to contractor skill sets, personnel shall be required to use one or more of the following:

2.5.6.1. Hardware: Laser printers, PC computers (various brands), compact commercial and ATEC instrumentation/data collection systems, voice/land communication interface devices, RF network, government computer system applications, and associated support equipment and vehicles.

2.5.6.2. Government Provided Software: Variety of LINUX versions and Visual StudioClient/Server applications and CISCO IOS, Windows OS, Visual Basic, Python, Anaconda, a variety of Databases, HEX Editing software, data collection/reduction routines/scripts/applications developed per SUT data requirements.

2.5.6.3. Office administrative computers and a variety of LINUX versions Add Visual Studio, Client/Server applications and CISCO IOS as stated in 2.5.6.2.

2.5.7. All technical information developed for technical operations and/or test events (software applications, programs, scripts) by contract personnel is the property of the Government. The Government will have unlimited access to this technical information. The Contractor shall provide technical information to the Government, to include but not be limited to, photocopies, drawings, software, and data on electronic media (Ref. PWS Section 5).

2.5.8. The contractor shall provide instrumentation technical support for all data collection and support equipment.

2.5.9. The contractor shall provide instrumentation technical support for each assigned test event:

2.5.9.1. Train qualified technical personnel on instrumentation equipment and technical operations to execute data collection (Ref. PWS Section 5).

2.5.9.2. Conduct instrumentation/data collection and support equipment functional checks (Ref. PWS Section 5).

2.5.9.2. Prepare and account for instrumentation/data collection and support equipment in preparation for movement to test site(s) (Ref. PWS Section 5).

2.5.9.3. Develop test event scenario scripts and operate Next-Generation Command Control Communication & Intelligent Engineering and Evaluation System (NGCEES) (e.g. Link 16 configurations MIL-STD 3011A/B/C, MILD-STD 6016) to support surrogate interoperability tactical communication requirements and test operations based on test design and architecture.

2.5.9.4. Execute movement and transport of instrumentation/data collection and support equipment (transport generators, power distribution boxes, SATCOM vehicles, trailers, and other test support equipment) to test site(s) (Ref. PWS Section 5).

2.5.9.5. Prepare and install instrumentation equipment in mobile support trailers (Ref. PWS Section 5)

2.5.9.6. Prepare test site for instrumentation/data collection operations.

2.5.9.7. Configure, functional check and operate Satellite Communications (SATCOM) system based on test design and architecture (Ref. PWS Section 5).

2.5.9.8. Installation/emplacement of SUT instrumentation and data collection equipment along with all associated interconnection cabling required and the performance of post functional tests (Ref. PWS Section 5).

2.5.9.9. Execute data collection operations during preliminary events (Flight Readiness Check/Dry Runs/Dress Rehearsal/COMMEX/FACEX), pilot, and record test operations based on test design and architecture (Ref. PWS Section 5).

2.5.9.10. Document instrumentation status on instrumentation operator log sheets, annotating equipment status and any associated issues and/or malfunctions during test/data collection operations.

2.5.9.11. Harvest required data from instrumentation systems and conduct quality control checks during preliminary events (Flight Readiness Check/Dry Runs/Dress Rehearsal/Collective Training/COMMEX/FACEX), pilot, and record test operations (Ref. PWS Section 5).

2.5.9.12. Consolidate and prepare harvested data for processing during preliminary events (Flight Readiness Check/ Dry Runs/Dress Rehearsal/COMMEX/FACEX), pilot, and record test operations (data management) (Ref. PWS Section 5)

2.5.9.13. Account for and track all data storage media using appropriate forms and logs (Ref. PWS Section 5).

2.5.9.14. Conduct daily inventory of all unclassified and classified data media to verify accountability (Ref. PWS 5.6).

2.5.9.15. Transfer consolidated data to the data authentication team via network transmission and/or physical delivery (data management).

2.5.9.16. Respond to data information requests from data processing/reduction team

2.5.9.17. Consolidate all test data for archival on instrumentation data storage media/devices and provide to Data Management Storage Facility (DMSF) for reference and long-term storage.

2.5.9.18. De-install SUT instrumentation/data collection, support equipment, and associated interconnection cabling.

2.5.9.19. Execute test site recovery of instrumentation/data collection equipment and support equipment.

2.5.9.20. De-install instrumentation equipment in mobile support trailers and prepare for movement.

2.5.9.21. Prepare and account for all instrumentation/data collection and support equipment in preparation for movement to AMDTD work site (Ref. PWS Section 5).

2.5.9.22. Execute movement and transport of instrumentation/data collection and support equipment to AMDTD work site (Ref. PWS Section 5).

2.5.9.23. Configure operate, and repair instrumentation network equipment to maintain all test event data collection operations.

2.5.9.24. Execute movement and transport of instrumentation/data collection and support equipment (transport generators, power distribution boxes, SATCOM vehicles, trailers to AMDTD work site) (Ref. PWS Section 5).

2.5.9.25. Perform equipment recovery: operational checks on all data collection/support equipment and support vehicles, document malfunctioning/broken items, and repair equipment as needed (Ref. PWS Section 5).

2.5.9.26. Clean all data collection/support equipment and return to storage locations (Ref. PWS Section 5).

3. PROGRAM MANAGEMENT OFFICE (PMO): The Program Manager (PM) is fully responsible for all contract support. To fulfill this responsibility, the PM is supported by a Site Lead at Fort Sill. The PM is designated to facilitate management, supervision, and reporting responsibilities among all TETSS personnel. The PM supervises employees at the Fort Bliss worksite and provides oversight of employees at the Fort Sill worksite. In addition, the PM provides guidance to all Team members and provides a direct interface to the Government and direct accountability to the Contracting Officer (KO) and the Contracting Officer Representative (COR) for schedule, budget, performance and quality of all contract efforts.

4. ITR ENVIRONMENT: As a minimum, contractor personnel shall be required to use the following:

4.1. Hardware: Laser printers, scanners, and PC computers. LAN communication interfaces devices, wireless systems, trunking radio system, data encryption devices (tactical and commercial), and ancillary components for these systems, commercial voice communication interfaces devices.

4.2. Software: UNIX, Windows 7 & 10 Enterprise, a variety of database management systems to include, but not limited to Oracle, Excel, and SAS, SQL, My SQL, MS Office Products, and in-house developed data collection and reduction routines.

4.3. COMSEC: Both CCI and COMSEC shall be handled by the IT operators in the form of classified encryption tapes, key generators and data transfer devices.

5. TRAVEL. For proposal purposes only, a plug number will be incorporated.

For informational Purposes Only:

Contractor personnel shall be required to travel as necessary to support sustainment objectives. Details shall be provided at the time of travel if required in the form of a Task Instruction Letter (TIL) or in the Task Implementation Plan (TIP). Contractor shall submit a Request for Travel Authorization to COR and Test Officer (TO) for concurrence or travel should be included it in the TIP that is associated with the Task Authorization Request (TAR). Concurrence will be forwarded to the Contracting Officer (KO) for approval. Details shall include task number, dates, and personnel for travel, and an estimate of costs.

5.1. Per Diem shall be in accordance with the Federal Travel Regulation for the locations visited. U.S. Per Diem rates for the continental U. S. are located at the following website: https://www.defensetravel.dod.mil. Costs for travel, subsistence, and lodging shall be reimbursed to the contractor only to the extent that it is necessary and authorized for performance of the services under this task order. Reimbursement for the costs of subsistence and lodging shall be considered to be reasonable and allowable daily charges as compared to the maximum rates set forth in the following:

5.1.1. Joint Travel Regulations, which is used as a guide for the contractor. Reimbursement to the contractor for per diem shall be limited to payments to employees for authorized per diem, as described above, not to exceed the authorized per diem. If mission requirements exceed the JTR lodging rates, the Contracting Officer (KO) is the approving authority. The contractor shall retain supporting documentation for per diem paid to employees as evidence of actual payments, and this documentation shall be submitted with the applicable vouchers, which includes travel expenses.

5.1.2. The contractor shall use the lowest cost travel mode commensurate with the requirements of the mission. When it is necessary to use air or rail travel, the contractor agrees to use coach, tourist class, or similar accommodations to the extent consistent with the successful and economical accomplishment of the mission for which the travel is being performed.

5.1.3. Before undertaking any travel in performance of this Contract, the Contractor shall have the travel coordinated by the TO/COR and approved by the KO. Notification shall include, the number of people, traveler(s) name, and destination, number of day, purpose, and estimated cost in accordance with the paragraph.

5.1.4. Once travel has been performed contractor shall submit a Travel Expense Report with name, date, destinations and detailed expenses of travel. Receipts shall be included with submission of each voucher in Wide Area Work Flow (WAWF).

6. SPECIAL INSTRUCTION/REQUIREMENTS.

6.1. The contractor shall participate in technical meetings, bidder’s conferences, and program review as required, in addition to having technical personnel available to answer questions. The Government will make subject matter experts available to the contractor to answer specific, military oriented questions about procedures.

6.2. Training Requirements: The contractor shall maintain completed training certificates/records on file and submit an electronic copy of all training certificates to the COR as per required in the PWS Section 1.6.9.1, 5.2.2.2.1, 5.5.1.3.and 5.6., IAW CDRL A008, TE I to include the following:

6.2.1. Security Education Training Awareness (SETA)Training. Per AR 530-1 all new contractor employees must complete SETA training within 30 calendar days of their reporting for duty. The contractor shall abide by the OPSEC Plan and or Standard Operating Procedures of the requiring activity.

6.2.2. Threat Awareness and Reporting Program (TARP). Per AR 381–12, Army contracting officers or contracting officer representatives will ensure that threat awareness and reporting requirements are included in future classified contracts or on DD Form 254 (Department of Defense Contract Security Classification Specification), as appropriate. The Program/Site Manager (PM) will ensure contractor personnel with security clearances comply with threat awareness and reporting requirements specified by this regulation. Training is a Face-to-Face instruction requirement. Contractor personnel will provide training certificates at completion, to the COR through the PM. Persons employed by Army contractors will report threat-related incidents, behavioral indicators, and other matters of Counterintelligence (CI) interest to the facility security officer, the nearest military CI office, the Federal Bureau of Investigation, or the Defense Security Service.

6.2.3. AT Level I Training. All Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, and controlled-access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee, to the COR or to the KO, if a COR is not assigned, within 15 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website: https://atlevel1.dtic.mil/at.

6.2.4. AT Awareness Training for Contractor Personnel Traveling Overseas. U.S. based Contractor employees and associated subcontractor employees to make available and to receive Government-provided area of responsibility (AOR) specific AT awareness training as directed by AR 525–13. The combatant commander directs specific AOR training content with the unit anti-terrorism officer (ATO) being the local point of contact.

6.2.5. iWATCH Training. The Contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local-developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR no later than 45 calendar days after contract award.

6.2.6. IA/IT Training. All Contractor employees and associated subcontractor employees must complete the DOD IA awareness training before issuance of network access and annually thereafter. All Contractor employees working in IA/IT functions must comply with DOD and Army training requirements in DOD Directive 8570.01, DOD 8570.01–M, and AR 25–2 within 6 months of employment.

6.2.7. OPSEC Training. Per AR 530–1, new Contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty. All Contractor employees must complete annual OPSEC awareness training.

6.2.8. Annual Security Refresher Training. This training is hosted on ALMS and accessible through AKO/My Training and Army Training Network (ATN). Contractor personnel will provide training certificates at completion, to the COR through the PM. Users must be logged into AKO to access the ALMS site where the courses are listed. From the AKO homepage, the ALMS portal can be accessed by clicking through “Self Service”, “My Training” and “ALMS”. After accessing the ALMS site, users should click on the “browser setting” to make sure their computer is compliant with ALMS requirements. Users then type: security training in the “advanced catalog search” function to find the above named training products. In “offerings”, users can register and “launch content” to begin the training. If you experience a problem with the web-based training program, submit a trouble ticket to the army training help desk: athd@mailds01.csd.disa.mil. Additional security education, training and awareness resources and information can be found at http://www.dami.army.pentagon.mil/site/seta.

6.3. Incidental Government Property: AMDTD will provide contractor personnel incidental Government property, TE M, IAW PWS 3.4., such as computers, monitors, printers, and peripherals in support of daily operations and test support operations that is incidental to place of performance.

6.4. Security: The contractor shall abide by the Department of Defense Contract Security Classification Specification; (DD Form 254, TE L). Contractor personnel supporting the tests must possess a SECRET security clearance.

6.5. The Contractor shall be trained to use, operate, and maintain the latest version of software for Standard Army Management Information Systems (STAMIS) (GCSS-Army). The GCSS-Army training consists of web-based and formal courses. Web-based and Formal Net training shall be completed within thirty (30) calendar days after contract start date and the certificates of completion submitted to the COR through e-mail within fifteen (15) calendar days after completion. A personnel list of whom shall be using GCSS-Army shall be provided to the Government prior to start of training. Personnel using GCSS-Army shall only complete the training associated with their duty position. New employees shall complete training and submit results to the COR before commencing work under the contract. Web Based Training is available at http://www.gcss.army.mil/GTRAC/Account/Login.aspx.

7. REPORTING REQUIREMENTS:

7.1. All documentation shall be in accordance with the Contract Data Requirement List (CDRL).

7.2. Request all deliverable documents be delivered to is USAOTC, AMDTD, ATTN: Contracting Officer's Representative (COR), Fort Bliss, Texas 79916-6816. Documents shall be delivered in electronic format unless otherwise specified by the COR or the Contracting Officer (KO). Delivery of documentation to personnel other than the COR will be coordinated with the COR/KO.

8. DELIVERABLES: Travel dates and specifics will be provided with Task Instruction Letters (TIL)(s).

Date Event

Monthly Monthly Progress and Financial Report

Monthly Personnel Status and Training Report

Monthly/Quarterly Plan of Action and Milestones (POAM) Updates

Quarterly Sensitive Item Report

Annually Service Contract Reporting (SCR)