PWS EX24026 DT-B-WAZ Georgia IFATDS.docx

Advanced Field Artillery Tactical Data System (AFATDS) For Export to Georgian Defense Forces (GE DF)

Performance Work Statement

Ver 2

International Field Artillery Tactical Data System-Georgia (IFATDS_GE) Project

PWS EX24026 DT-B-WAZ

Prepared by the United States Army Communications-Electronics Command (CECOM) Security Assistance Management Directorate (SAMD) Aberdeen Proving Ground, Maryland

20 December 2023

Contractor - Unrestricted Content

This document does not contain technology or technical data controlled under either the U.S. International Traffic in Arms Regulations or the U.S. Export Administration Regulations.

Non-Export Controlled – See Sheet 1 Non-Export Controlled – See Sheet 1

TABLE OF CONTENTS

SCOPE

Introduction and Background This Performance Work Statement (PWS) defines the work to be performed and the associated requirements to be met by the Contractor for the U.S. Government (USG; hereinafter also referred to as “the Buyer” and the “Government”), for the design, development, installation, integration, test, training, delivery, and field support of the Georgian Defense Forces (GE DF) Artillery Command and Control portion of the PWS EX24026 DT-B-WAZ Program. This PWS also refers to the GE DF as the “End User” and “the Foreign Military Sales (FMS) Customer,” where appropriate.

The US Army Communications-Electronics Command (CECOM) is directed to procure for the GE DF, exportable hardware, software, and support services for this program, under the FMS case PWS EX24026 DT-B-WAZ, implemented in 2023. Most software, equipment and services for this program mainly consisting of Command and Control (C2) software and hardware elements and most training, logistics and in-country C2 installation, integration support services are to be procured through the Contractor. The Tactical Communications (TC) radios and communications hardware, installation, programming and associated radio training and maintenance support for this program are being procured through a separate government acquisition. This PWS for the C2 and associated program requirements, calls for the Contractor to provide an overall, integrated solution, which incorporates the radios and TC systems provided as Customer Provided Equipment (CPE, defined in Appendix F of this PWS) into the overall program effort.

The End User has previously acquired and fielded NATO sourced, modified M109A2+ series howitzers. This PWS for the C2 and associated program requirements, calls for the Contractor to provide an overall, integrated solution, which incorporates the radios and TC systems provided as Customer Provided Equipment (CPE, defined in Appendix F of this PWS) into the overall program effort. The Radio/TC supplier will provide programing of the radios as necessary, IAW the Contractor network designs, along with associated Radio/TC training and fielding support services in conjunction with the collective IMP.

The core system element selected to meet the GE DF’s requirements for this automated support system for field artillery C3, is IFATDS. IFATDS and select RTX peripheral systems (MobileC2: AOS, WCS, MMS) are the systems of record for the purposes of FMS.

IFATDS is a networked C3 system, built on a foundation of domestic origin AFATDS, upgraded by RTX to incorporate software and capabilities, specifically designed by RTX for the international market which may be combined with a number of other RTX software applications and utilities and networked C3 architectures, primarily connected via radios. The RTX product baseline is then tailored to meet US export and End User needs specific to each country. This PWS calls for an overall system of systems, tailored for GE DF mission requirements, designated as the International Field Artillery Tactical Data System-Georgia (or IFATDS_GE).

As used in this PWS, the definitions for the following terms apply:

· Government – U.S. Government (USG) on behalf of Georgia

· End User – Georgian Defense Forces (GE DF)

· Program/Project – International Field Artillery Tactical Data System-Georgia (IFATDS_GE)

· Contractor – RTX Scope of Work

End User’s Organization and Mission This PWS establishes and describes the Contractor’s requirements for IFATDS_GE system software and hardware, support equipment, data, and services to be provided. The required services include program integration and management, engineering, installation, logistics, maintenance, training, and field service representative (FSR) support. The PWS calls for IFATDS_GE systems and services to provide C2 for multiple Field Artillery Brigades and Battalions, each with unique organizations, along with equipment and materials supporting a training classroom.

Hardware and Software Overview This PWS defines select aspects of requirements resulting in software tailored to the operational needs of this End User, provision of hardware to host and run the software, and services supporting these efforts. The tailored systems to be delivered in this PWS include IFATDS_GE, the Advanced Observer System (AOS), the Weapons Control System (WCS) and the Meteorological Messaging System (MMS) with associated computer hardware. Additionally, IFATDS_GE includes the Digital Fire Support Training System (DFSTS) to support sustainment training. Integration includes ruggedized laptop computers for fire direction centers (FDC), Forward Observers, other sensors, MET stations, Weapon Platforms, and classroom training facilities. Finally, IFATDS-Georgia also requires various software utilities such as Munitions SDK and, if applicable, Language Software Development Kit (SDK) and Communications Wizard. Artillery Systems Cooperation Activities (ASCA) Interoperability Program Common Technical Interface Design Plan (CTIDP) will be in IFATDS_GE, and a Government Furnished Information (GFI) AFATDS/ASCA training support package will be in training package.

In accordance with the paragraph above regarding country unique software requirements, the US Government (USG) will provide the Contractor with the Artillery Systems Cooperation Activities (ASCA) Interoperability Program, ASCA 012 - Common Technical Interface Design Plan (CTIDP) Version 7.02 as Government Furnished Information (GFI). The Contractor will incorporate ASCA v7.02 into the final IFATDS_GE product deliverable and ensure the minimum required message sets are operational. The USG will provide the currently fielded USG AFATDS/ASCA Training Support Package (TSP) as Government Furnished Information (GFI). The GFI TSP will be updated to ASCA version 7.02 by the Contractor and incorporated into their final training package deliverable(s) and classes.

Systems Integration Overview The program requires integration, for mission processing, with the Kearfott Fire Control System (FCS) onboard the M109A2+ howitzers. WCS software integration with the M109 crew simulation systems is not a part of this case but can be considered for a future phase. Software (AOS) integration with Forward Observer Laser Range Finders (LRF) is included, only if GE DF devices have the necessary data connection cables. LRF connection hardware is not a part of this case. Since GE DF LRF devices are not available, FAT testing is via UI inspection, not demonstration. Software integration with the MSTAR radar system is not a part of this case, therefor a swivel-chair approach with AOS will be employed. Software integration with the UAV/ground station system is not a part of this case, therefor a swivel-chair approach with AOS will be employed. Software integration between the Vaisala MW32 MET Station and MMS is included. Installation of one small classroom is included to support training.

Since non-standard C2 command post vehicles are involved along with positioning of equipment in howitzers, up to three (3) site surveys (2 persons, three days in-country) are necessary to support the USG Lead System Integrator efforts and hardware installation responsibilities. Finally, the program requires integrated management of these systems, support for installation of the C2 elements and integration, along with verification and acceptance testing, operations training, technical manuals and data, spare parts, and support services for both hardware and software.

Period and Place of Performance The Contractor shall perform the required work at multiple site locations, both in CONUS and OCONUS. These include software development, testing, installation, and meetings in CONUS, as well as support for USG installation activities, testing, training, meetings, maintenance and support at facilities OCONUS, which likely include one or more cities inside Georgia. The GE DF facilities include the respective Artillery Brigade and Battalion locations, as well as the GE DF Artillery Institute (classrooms) facility.

The Contractor shall complete all the requirements defined herein no later than (NLT) thirty-six (36) months after contract award (ACA). Within this timeframe, the Contractor shall meet the following required timelines:

· The Contractor shall complete pre-fielding design, development, installation, testing, and acceptance activities NLT twenty-four (24) months ACA, assuming USG delivery and installation activities are completed within that timeframe.

· The Contractor shall perform required software warranty activities upon successful System Acceptance Test (SAT) for each Battalion slice, which will include associated Brigade and/or Fire Support elements and continuing for twelve (12) months.

· The Contractor shall perform Field Service Representative (FSR) support for twelve (12) months commencing immediately upon the first successful Battalion SAT.

APPLICABLE DOCUMENTS

· International Standards for Phytosanitary Measures (ISPM) 15 – Guidelines for Regulating Wood Packaging Materials in International Trade

· MIL-STD-129R – Military Marking for Shipment and Storage

· American Society for Testing and Materials (ASTM) D 3951-98 – Standard Practice for Commercial Packaging Requirements IFATDS_GE System Hardware Requirements The Contractor shall deliver and install computers and hardware, in the quantities defined in Appendix C. The planning location for in-country installation is Tbilisi, Georgia. The Contractor-provided operator stations shall all be commercially ruggedized to ensure reliable operation in harsh environments and tactical, mobile, combat conditions. MIL-STD certification is not a requirement. GETAC computers are environmentally tested by the manufacturer and will not be environmentally retested by the Contractor on this contract, nor will testing documentation be required. USG will identify the conditions for each node: dismounted, vehicle type, tent or building; and 24VDC or 220VAC. The computers installed in tactical vehicles shall be installed with ruggedized shock mountings and with vehicle 24VDC DC power adapters. Computers operating continually in dismounted all-weather conditions shall be further adapted for these demanding conditions. All hardware shall be supplied from new production.

Classroom student computers can vary in form factor from the field computers, i.e., are not required to be rugged.

The Contractor will also procure and provide platform software, defined herein, to run on the required computer hardware.

The Contractor shall prepare all hardware and materials required for international shipping in accordance with the requirements defined herein. Transportation of all equipment and material will be the responsibility of the Government.

The Contractor shall design, develop, install, integrate, and configure IFATDS_GE to operate on networks connected primarily by radio communications equipment. The Contractor shall integrate the IFATDS_GE solution with CPE-provided radio equipment consisting of Harris RF-7850M 50W (MTNW and TNW-75 waveforms) and RF-7800H-V001 (HF).

Materials are listed at Appendix C. In addition to the listed items, Contractor may provide miscellaneous consumables and/or expendable items.

Laptop Computers for Hosting AFATDS and DFSTS The Contractor shall supply laptop computers equipped to run the AFATDS 6.8 based International Version and other associated software. Equipment for field stations (vs classrooms) shall include vehicle mounts and other items to facilitate field operations. See Appendix C. The laptop computers shall meet or exceed the following specifications:

· Processor: i7

· Storage: 500GB, minimum

· RAM: 32GB, minimum

· Display: 15 inch or larger Laptop Computers for Hosting MobileC2 (AOS, MMS, WCS) The Contractor shall supply computers equipped to run the MobileC2 applications and other associated software, with associated vehicle mounts and/or configured as necessary according to the supported role. The computers shall all be identical except where a continuous all-weather role is defined, in that role the computers shall additionally have special militarized connectors. See Appendix C for quantities per role. The computers shall meet or exceed the following specifications:

· Processor: i5 or better

· Storage: 256GB, minimum

· RAM: 4GB, minimum

· Display: 11 inch, approximate Classroom Computers for Students and Instructors The Contractor shall supply ruggedized computers for use by students and instructors, equipped to run IFATDS_GE, DFSTS and the MobileC2 applications – along with supporting software. Will not include installation kits. Note: All the above applications can be installed on every classroom computer, but only one application can be run at once, guided by the training objectives. The computers shall all be identical. See Appendix C for quantities per role. The computers shall meet or exceed the following specifications:

· Processor: i5 or better

· Storage: 256GB, minimum

· RAM: 32GB, minimum

· Display: 15 inch, or better Contractor Facility Computers The Contractor shall procure one (1) workstation of each type and configuration as the deliverable computers, including classroom, to host IFATDS_GE and related SW, total four (4). The Contractor shall procure one (1) workstation suitable for hosting the Fire Control Panel Trainer (FCPT) SW. These five workstations, for use in the Contractor’s facility supporting software development, integration, test, and warranty activities, are to be retained by the Contractor in support of future potential phases or eventually for disposal, i.e., these workstations are not deliverable to USG or GE DF. Note: shipping and handling of these items to Georgia costs far more than the value of the items after the PoP.

Miscellaneous Equipment The Contractor shall also provide and install equipment to support OCONUS classroom instruction. See Appendix C. This equipment is intended to be installed in a GE DF provided training facility, used during train-the-trainer training of GE DF students in furtherance of both unit sustainment training and GE DF ongoing training of additional system operators. Note: Each Battalion size unit is typically provided a training sustainment set of equipment used in conjunction with other USG provided items, e.g., Fire Control Panel Trainer HW/SW, whereas an Artillery Institute would typically be provided additional classroom items plus be equipped with representative vehicles to conduct field training exercises (FTX). This contract provides a limited initial capability for the GE DF Artillery Institute and no training support resources for field units.

IFATDS_GE System Software Requirements Software Licensing, Export and Documentation The Contractor shall identify, procure, and deliver all required licenses. The Contractor is responsible for ensuring that all commercial products embedded within the delivered software are properly licensed. The Contractor shall be responsible for ensuring all software provided on this task executes and functions properly on the required hardware platforms.

Preparation for International Export The Contractor shall modify the IFATDS_GE software baseline to meet the PWS requirements and comply with the AFATDS Releasability Matrix to be provided by USG. The Releasability Matrix category guidelines are listed below.

· Basic Export – Functionalities that are part of the basic C2 features of IFATDS 6.8.x International Version such as startup and run features, communications, situational awareness, planning, engagement analysis, mission execution, etc. Retain all functionality.

· Export If Required – Retain, with approval of PEO C3T via the Releasability Matrix, the functionality necessary to support tasks necessary per this PWS.

· US Only – Functionalities that are unique either to U.S. select weapon / munition Systems, U.S. Fire Support TTP (Techniques, Tactics and Procedures) or U.S. System Interfaces. These functions shall be disabled (which includes, appropriate to the topic: removed, non-selectable option, or replaced with an international similar feature).

Commercial Software Licenses for IFATDS_GE Products The Contractor shall be responsible for ensuring that all commercial products embedded within the delivered systems are properly licensed for use by the End User. The Contractor shall procure, as a minimum, the following commercial software licenses required for the development, distribution, and operation of the IFATDS_GE.

Commercial Software License

Postgres Database Software

Open Map / World Wind

Multilingual Methods (RTX Proprietary)

AimPoint Algorithm Suite

SQ Lite (DFSTS only)

The Contractor shall also procure and provide the following platform software for the laptop computers:

HW Platform Licenses

Open Office (IFATDS only)

Adobe Acrobat Reader

Microsoft Windows 10

Recovery Software

IFATDS_GE Specific Software Licenses The Contractor shall provide licenses for the IFATDS_GE software in the required quantities and allocations defined below, which includes: Field systems, students and instructors. It does not include licenses for spare HW, as these are swapped with the outgoing HW. Note: The Munitions SDK (Entity Manager) is a powerful but complex utility and thus is not a deliverable item. It is available for use by the FSR to facilitate (create, update, delete) weapons/ammo for use in Tactical Fire Control and/or for sensors such as radars and observers.

IFATDS_GE Software The Contractor shall test and provide IFATDS_GE executable software with English capable Graphical User Interface (GUI) and messaging. User interface and all documents are to be delivered in English only. Note: MIL-STD 6017 variants only support ASCII characters, i.e., legacy systems are not multilingual capable, e.g., US radars.

The open-source map engines and map content are not required to be multilingual. Map content is not a required deliverable item and is typically provided by either the USG or End User.

The Contractor shall provide the capability for IFATDS_GE to interface with the GE DF’s M109 howitzer NAPS/FCS (Kearfott Navigation-Aiming-Pointing-System / Fire Control System) and. Weapons are normally paired with WCS. The IFATDS_GE software shall contain Technical Fire Direction capability for the M109 series munitions as defined in Appendix C: Weapons, Munitions and Sensor Descriptions.

The Contractor shall provide the capability for IFATDS_GE to interface with the GE DF’s various targeting sensors to the extent possible (See Appendix C: Weapons, Munitions and Sensor Descriptions). Sensors are normally paired with AOS. No cables or interface devices, accessories or equipment are provided in the current case. Some sensors do not have a viable interface and/or GE DF may not have the required cables or accessories, in which circumstance a manual data entry TTP may be employed.

The Contractor shall provide the capability for IFATDS_GE to interface with GE DF’s meteorological stations (Vaisala MW32) to the extent possible (See Appendix C: Weapons, Munitions and Sensor Descriptions). MET stations are weather sensors normally paired with MMS.

Counterfire Radars IAW and to reinforce the Releasability Matrix, Contractor shall retain the existing radar interfaces, including those for the, AN/TPQ-36, Q37, Q49 & Q50 (LCMR) and Q53 employing VMF 6017A, B and C (as applicable per radar). DFSTS may be used for verifying these interface requirements.

Nonstandard Sensors (no automated interface) Georgia units include two sensors for which an automated interface is not provided in the FMS case, but which can be explored for future phases. However, these sensors can be provided with a capability to employ a manual data transfer TTP, also referred to as a “swivel chair” interface.

The TACP performs a specialty function of managing allocated air sorties and directly controlling air/aviation strikes. IFATDS has the necessary air management features. AOS does not have air attack features, especially not specific to NATO aircraft digital messages and media support. The TACP may also perform regular surface to ground tasks for which AOS is well capable of supporting. Appendix C: Weapons, Munitions and Sensor Descriptions provides a more detailed description of the TACP.

The MSTAR (man portable surveillance and target acquisition radar) is a ground surveillance radar. Appendix C: Weapons, Munitions and Sensor Descriptions provides a more detailed description of the MSTAR.

Advance Observer System (AOS) The Contractor shall provide AOS executable software with multilingual capable Graphical User Interface (GUI) and messaging. The AOS shall provide self-location, situational awareness and messaging, target location, target lists, and Call for Fire capabilities. Target location is provided either by manual entry or imported from a targeting system such as a laser range finder (provided the LRF is supported and has the appropriate interface cable). AOS also supports a radar mode, which employs an “unobserved” Call for Fire (fire and forget, not adjusted). A detailed description of sensors is provided in Appendix C: Weapons, Munitions and Sensor Descriptions.

Weapon Control System (WCS) The Contractor shall provide WCS software, with multilingual capable Graphical User Interface (GUI) and messaging, supporting the GE DF M109 howitzer and an interface to the Kearfott NAPS/FCS. A detailed description of this weapon is provided in Appendix C: Weapons, Munitions and Sensor Descriptions. The WCS shall provide self-location, situational awareness and messaging, priority missions (pre-planned targets) and fire mission logic tied to IFATDS-L. For self-location, WCS is capable of selecting the NAPS/FCS.

Meteorological Messaging System (MMS) The Contractor shall provide MMS software with multilingual capable Graphical User Interface (GUI) and messaging. The MMS software shall have an interface to the Vaisala MW32 MET Station for MET-CM. A detailed description of this MET station is provided in Appendix C: Weapons, Munitions and Sensor Descriptions. The MMS shall provide self-location, situational awareness, and messaging, plus editing of MET-CM data.

Digital Fire Support Training Software (DFSTS) The Contractor shall provide Digital Fire Support Training Software (DFSTS) executable software with training support capability. The Contractor shall provide DFSTS software with an English language GUI. The Contractor shall develop and provide training in the use of DFSTS for the End User, to be combined with AFATDS training (as further detailed in the Training Section of this PWS). The DFSTS message simulation and stimulation solution shall be capable of supporting testing and training for fire support systems. The DFSTS solution shall be capable of transmitting and receiving messages using multiple communications protocols and performing simple but highly intelligent message response generation to mimic a number of common sensor, shooter, and command and control systems. The DFSTS solution shall include a Time-Ordered-Event List (TOEL) generation and execution capability, providing a means of creating and playing back a sequence of actions. The DFSTS solution will be used to stimulate the system in order to train operators. These active simulation capabilities will provide for a virtual substitution of non-AFATDS systems, permitting training using fewer live resources.

Multilingual Graphical User Interface (GUI) Framework The Contractor solution shall include the capability to display menu items and help menu items in English only.

Multilingual Messaging Mechanism The Contractor shall provide a plain text Multilingual Message Tool. The plain text Multilingual Message Tool shall support multilingual plain text between IFATDS_GE stations.

Supporting Utility Applications If applicable, The Contractor shall provide and integrate the following supporting utilities to support the End User’s utilization of IFATDS_GE (and MobileC2): Language Software Development Kit (SDK) and Communications Wizard, both of which are multilingual capable. The FSR will have access to the Munitions SDK, which is not deliverable.

Windows Operating Environment The Contractor shall provide the capability for AFATDS and IFATDS_GE components, including DFSTS, to operate on workstations using Microsoft Windows 10 as the operating system. Modifications to IFATDS_GE to meet GE DF cyber policy are not a part of this case.

Recovery Software The Contractor shall provide the capability to capture an image of each computer for recovery purposes. The FSR will train GE DF in the use of image recovery software. The image recovery SW is English only.

Artillery Systems Cooperation Activities (ASCA) Interoperability The USG will provide the Prime Contractor the Artillery Systems Cooperation Activities (ASCA) Interoperability Program Common Technical Interface Design Plan (CTIDP) Version 7.02, 18 messages listed below, to be incorporated into the final IFATDS deliverable. The USG will provide the Government Furnished Information (GFI) AFATDS/ASCA training support package to be incorporated into the Prime Contractor’s final training package deliverable.

Program Management and Engineering Requirements IFATDS Program Management and Systems Integration Overview The Contractor shall ensure IFATDS_GE computer hardware and software are integrated and are functionally interoperable with the applicable radios and communications systems and networks as required by this PWS. The Contractor shall perform design, installation, testing and all other tasks needed to ensure viable, functional interoperability with the associated IFATDS computers, radios, vehicles, communications, weapons, and other systems. Actions as the Lead System Integrator (LSI) are not a part of this contract.

Note: The Radio supplier is responsible for programming radios to reflect the network designs provided by Contractor. The radio supplier is responsible for supplying all HW, waveforms and firmware related to the digital capabilities required of this program. The radio supplier is responsible for training GE DF in the end user programming, operation, and maintenance of the radios. USG is responsible for facilitating these activities.

Furthermore, the Contractor shall perform administrative and technical management, and shall maintain a status reporting system monitoring multiple efforts to achieve the PWS objectives, including technical activities, problems or deficiencies, impacts, and recommended solutions.

The contractor shall continuously monitor the technical performance of this contract, and all subcontracts, and deliver to the Government a monthly assessment report in accordance with CDRL, DD Form 1423, Data Item A003, DI-MGMT-80368A, Status Report. This report shall convey the status of contractor activity during the previous month as well as cumulative contract performance. Technical reviews shall address all areas concerning technical status/progress, testing/plan/procedures, architecture, training, technical documentation, reliability and all else relating to technical performance. The performance report as a minimum shall discuss:

· Significant accomplishments and issues that arose during the reporting period

· Projected activities for the following and subsequent periods

· Subcontractor performance when applicable

· Program risks and mitigation efforts (technical and schedule)

· Status of milestone payments, as applicable

· Status of any material/software deliveries

· Dates and quantities of any material deliveries

· Any general meetings that occurred with the Government or End User representatives during the reporting period Program Management Plan (PMP) The Contractor shall develop and implement a Management Program that clearly defines how the effort shall be managed and shall have overall responsibility for the control, execution, management, and coordination of all contractor work performed. The Contractor’s designated Program Manager (PM) shall ensure, using a standard management system, that all functions necessary for all programmatic, technical, and other special requirements, are performed and accomplished in a timely and compliant manner, i.e., in compliance with all applicable laws, regulations, policies and contractual guidance. The Program Management Plan (PMP) shall be developed in accordance with CDRL, DD Form 1423, Data Item A001, DI-MGMT-81117, Program Management Plan. The PMP shall be developed to address all aspects of the program work, to include integration, installation, training, and maintenance support, and to incorporate and implement deliverables.

The PM shall act as the single point of contact within the Contractor’s activity for all required program status information, to include administrative and managerial aspects, through the complete PoP.

As a part of its overall quality assurance effort, the Contractor shall develop a risk management program. The Contractor shall document the details of the Risk Management Program in the Program Management Plan. The plan shall be used to monitor management and schedule of the contract efforts relative to the overall AFATDS program and is intended to provide the Government with data for all risks associated with the program.

The Contractor shall implement a process to control the configuration management of the program deliverables (e.g., documentation, software versions, system design aspects, etc.). The Contractor shall document the details of the Configuration Management process in the Program Management Plan.

The Contractor shall implement a process to monitor the quality assurance of the Contractor’s efforts. The Contractor shall document the details of the Quality Assurance Program Plan in the Program Management Plan.

Integrated Master Schedule (IMS) The Contractor shall develop an Integrated Master Schedule (IMS), which shall include scheduling details for material delivery, installation, testing and training in accordance with CDRL, DD Form 1423, Data Item A002, DI-MGMT-81650, Integrated Master Schedule. The Contractor shall maintain the IMS for currency and accuracy, adjusting it for developments and changes in order to maintain accurate scheduling forecasts throughout the contract’s Period of Performance (PoP).

The IMS shall incorporate scheduled events and milestones for all IFATDS subsystems, to include shipments and deliveries, installation, training, design reviews, program reviews, technical interchange meetings, and other formal stakeholder meetings. The USG will coordinate with the End User for vehicle and facility preparation and availability, for surveys, installation, testing and training, based on the Contractor-developed and USG-approved IMS.

Management Meetings and Reviews The Contractor shall be responsible for conducting a meeting with USG every other week to discuss status and next steps of the program.

Post-Award Conference (PAC) The Contractor shall host USG representatives for a Post-Award Conference within thirty (30) days of contract award to review program plans and contractual requirements.

Technical Interchange Meetings (TIMs) The Contractor shall attend three (3) Technical Interchange Meetings CONUS and three (3) TIMs OCONUS. Each TIM shall be no more than five (5) days in duration. For each TIM, the Contractor shall prepare presentation and supporting documentation and provide them to the USG at least twenty-one (21) days in advance of the meeting.

The timing of these meetings shall be coordinated to optimally support meeting objectives, including ensuring availability of necessary data to appropriately review, examine and address all program execution activities. TIMs shall be scheduled when there is need for substantial technical interchange between the government, End User, and the Contractor.

Meeting content for the TIMs may include discussion of any information that has impact upon the task activities, including documentation contents or format.

Weekly Program Status Update Meetings The Contractor shall support weekly teleconferences with the USG stakeholders to discuss program status/progress. The Contractor shall normally use these meetings to provide a brief progress brief, and to address with U.S. Government representatives’ relevant issues or problems. The Contractor shall schedule and coordinate each meeting with Contractor’s PM acting as the chair/host. The Contractor shall provide meeting materials for participants’ preparation and reference during the meeting no later than noon the day prior to each meeting. The update and materials shall address the following issues, as a minimum:

Progress and Milestone Update;

Action Item Status and Progress;

Scheduled Travel;

Schedule Changes;

Significant or Notable Program Changes;

Program Actions (Contractor, USG, and End User).

Site Survey The Contractor shall plan, schedule, coordinate, and execute a Site Survey of IFATDS_GE locations, facilities, and vehicles, and shall publish and provide a Site Survey Report (SSR) in accordance with CDRL DD Form 1423, Data Item G001, DID DI-MISC-80508B, Technical Reports-Studies/Services. The vehicle Site Survey will be performed at the USG designated OCONUS facility, for planning purposes in Georgia. The vehicles are GE DF provided with 24VDC power capability. The classroom Site Survey will be performed at USG coordinated facilities, for planning purposes in Georgia. The main purpose of the Site Survey is to validate the Contractor’s knowledge and assumptions for IFATDS design and program management, and to identify issues with existing facilities and vehicles as they relate to the IFATDS_GE design, installation, operation, and management. The Contractor shall collect, consolidate, and incorporate all relevant observations for documenting in the SSR.

Version Description Document The Contractor shall provide a Version Description Document (VDD) in accordance with CDRL, DD Form 1423, Data Item B003, DI-IPSC-81442A, Version Description Document (VDD). This document will be the primary configuration control document used to track and control versions of the software to be released to the operational environment. The VDD will summarize the features and contents for the software build. For any applicable commercial software, as part of the VDD deliverable, the Contractor shall provide any necessary license key(s), expiration date(s), activation process(es), and/or ownership registration for the End User Customer as available.

Deliverable Media Markings Upon successful completion of Factory Acceptance Test (FAT), the Contractor shall provide a total of four (4) media copies for all IFATDS_GE configurations to USG (two for USG and two for GE DF). Note: GE DF copies to be delivered by USG. Note: GE DF are provided the media and training to self-manage recovery images, which are created following installation activities. The Contractor shall mark the deliverable media IAW the following:

CUI//SP-CTI/SP-EXPT//REL TO USA, GE (To be added to top and bottom of every label or document) Controlled by: US Army, PEO C3T Controlled by: PM Mission Command, PdM Fire Support C2 CUI Categories: CTI, EXPT Distribution Statement E POC: Jonathan Ochs, jonathan.ochs.civ@army.mil

DISTRIBUTION STATEMENT E. Distribution authorized to DoD Components only; Administrative or Operational Use; Export Control; (DATE mm/dd/yyyy). Other requests for this document shall be referred to CECOM ILSC SAMD, FMS Case Manager, AFRICOM/EUCOM Division, 6590 Reconnaissance St., Bldg 6010, Aberdeen Proving Ground, MD 21005.21005.

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

System Fielding and Verification Requirements Installation and Integration Requirements The Contractor shall install, integrate, and configure the IFATDS_GE hardware in Government-provided (or coordinated) vehicles and facilities. USG is responsible for vehicle installation kits (hole drilling, securing mounts, electrical connections) USG will mount the computer installation kits prior to the in-country integration efforts performed by Contractor . The USG will be responsible for all vehicle modifications including appropriate horizontal mounting locations, cable routing paths, mounting hole preparations and access to vehicle power. The Contractor shall ensure that all like vehicles have common installations and configurations. For planning purposes, the in-country vehicle installations will not exceed sixty (60) calendar days. For planning purposes, the classroom setup period will not exceed five (5) days.

The Contractor shall develop a detailed installation and fielding plan in accordance with CDRL DD Form 1423, Data Item G001, DID DI-MISC-80508B, Technical Reports-Studies/Services. The I&FP shall describe the installation and fielding process, utilizing a top-down approach, and including the validation and verification for each installation. The overall I&FP shall be discussed as part of the TIM process. The Contractor shall ensure submission of the I&FP in enough time for government reviews and approval, and no less than ninety (90) days prior to the beginning of the installation efforts. A technical data package (assembly drawings & interconnection drawings) is not required as part of this contract.

The Contractor shall perform the IFATDS_GE installation and checkout (I&CO) activities per the Contractor-developed installation and fielding plan (I&FP), and in accordance with CDRL, DD Form 1423, Data Item A002, DI-MGMT-81650, Integrated Master Schedule. This includes installing SW, placing computers in mounts, final connections, and test. GE DF will be responsible for any necessary classroom modifications and preparation of the classroom (furniture, electrical outlets, cleaning) to receive materials.

The Government will provide secure warehouse (or storage container) space at each installation site. The Government will be responsible for logistics and transportation of equipment during the installation process. The USG is responsible for coordinating installation facilities which include weather protection, HVAC, or other environmental control, 220VAC power, lighting, office space/furniture and latrine facilities.

Work for each facility/vehicle’s installation shall be considered complete when the respective Certificate of Completion (CoC) is completed per the process described herein.

System Verification Requirements Testing and Acceptance Overview The Contractor shall plan and perform a coordinated series of tests, at several levels and stages of execution in developing, installing, and supporting the IFATDS_GE. These testing functions shall apply to the deliverable software described in section 3.2.1.3, and as possible incorporate the radios, modems, vehicles provided and integrated through this PWS.

Testing is conducted in four phases.

Phase 1 is hardware. The Contractor shall establish and maintain a system for the final inspection and test of all purchased items to comply with contract requirements. The Government has the right to review the Contractor’s quality system and require correction whenever it, or any portion thereof, fails to meet the requirements set forth in the contract. The Contractor shall deliver hardware for the Government’s acceptance, after which the Government will transport the hardware to the CONUS and/or OCONUS installation location. Acceptance shall be by DCMA via Wide Area Work Flow (WAWF). Upon acceptance, the Contractor shall plan on ninety (90) calendar days for the USG to deliver the equipment at the OCONUS installation location or 30 days for the CONUS installation location. The Contractor shall perform Quality Assurance inspection procedures on deliverable hardware, prior to the Government’s acceptance. Additionally, the Contractor shall consolidate hardware deliveries to enable the Government to ship all the deliverable hardware in up to two (2) separate shipments. The Contractor may request USG approval to utilize an additional, third shipment for long lead items or for the benefit of program dependencies.

Phase 2 is an in-depth operational thread testing of the BMS software which will culminate in an operational thread demonstration of the BMS Software as part of the Software Factory Acceptance Test (FAT) at RTX’s facility in Ft Wayne, Indiana. This test is performed prior to shipment of software. Hardware used during the performance of this test is representative of deliverable hardware. The contractor may use similar RTX hardware assets if sufficient Customer Provided Equipment (CPE) are not available. A separate hardware FAT will be performed.

Phase 3 BMS Vehicle Certificate of Completion (CoC) is conducted to verify that all assigned equipment has been installed in deliverable vehicles. This test is run at the Buyer’s facility in-country (TBD, Poland).

Phase 4 is a Battalion System Acceptance Test (SAT) which is a representative selection event demonstrating that the system is functional as installed in deliverable vehicles. This event is run at the Buyer’s facility in-country (TBD, Poland).

RTX shall determine the priority of any software anomalies (Priority 1 to 5) according to the following criteria:

Priority 1 Defect An error shall be designated as a priority 1 error if any of the below are true:

a. It prevents the accomplishment of an operational or mission essential function in accordance with official requirements (e.g., causing a program stop)

b. It prevents the operator’s accomplishment of an operational or mission essential function.

c. It jeopardizes personnel safety.

Priority 2 Defect An error shall be designated as a priority 2 error if it has no alternative workaround solution and any of the below are true:

a. It adversely affects the accomplishment of an operational or mission essential function in accordance with official requirements.

b. It adversely affects the operator’s accomplishment of an operational or mission essential function.

Priority 3 Defect An error shall be designated as Priority 3 error if it has a reasonable alternative work around solution, and

a. Degrades performance, or

b. Adversely affects the accomplishment of an operational or mission essential function in accordance with official requirements, or

c. Adversely affects the operator’s ability to accomplish an operational or mission essential function.

Priority 4 Defect An error shall be designated as Priority 4 error if it is an operator inconvenience or annoyance and does not affect a required operational or mission essential function.

Priority 5 Defect All other errors shall be designated Priority 5 errors. Priority 5 issues are considered as potential future enhancements.

The Contractor shall perform testing at the Contractor’s Fort Wayne facilities, as well as at Government-provided sites and facilities in Georgia. The Contractor shall develop a schedule and procedures to validate system functionality, interoperability, and reliability, and perform these series of tests in accordance with CDRL, DD Form 1423, Data Item A002, DI-MGMT-81650, Integrated Master Schedule. System Acceptance will occur upon IFATDS_GE’s successful completion of all required verification events (i.e., System Acceptance Test (SAT) and approved CoC for each facility and vehicle).

Test Plan and Procedures (TPP) The Contractor shall develop a Test Plan describing the overall approach of the verification events throughout the program in accordance with CDRLs, DD Form 1423, Data Item D001, DI-NDTI-80566A, Program Test Plan. The Contractor shall develop a separate Acceptance Test Plan and Procedures (TPP) specific to each verification event in accordance with CDRLs, DD Form 1423, Data Item D002, DI-NDTI-80603A, Test Plan & Procedures. The TPP shall address all key parameters specified in this PWS and define all relevant acceptance criteria. Upon Government approval, the Acceptance Test Plan shall be the basis for approving all work accomplished under this contract. The Contractor shall develop a detailed Test/Inspection Report for each verification event in accordance with CDRL, DD Form 1423, Data Item D003, DI-NDTI-80809B, Test/Inspection Reports. All requirements will be verified per the Contractor-developed, Government-approved TPPs.

The Contractor is not required to procure radars, meteorological systems, sensors, or other materiel merely for test and verification purposes, beyond the deliverable hardware and software already stipulated in this PWS for the End User’s operational employment. For interoperability and interface requirements, the Contractor shall verify those requirements for which systems are available for testing, or for which the systems can be emulated (e.g., with DFSTS, or with an interface identical to other equipment that is available). Simulated fire support inputs are acceptable substitutes for equipment not available.

In the event a requirement is not fully verified at the specified verification event (i.e., solution does not comply with the requirement), the Contractor shall include appropriate remediation steps within the Test Report, including regression procedures necessary to fully verify requirements met.

Final Integration Testing (FIT) The Contractor shall perform systems and software verification at the Contractor’s CONUS facilities. The intent of the testing is to verify export compliance and verify specific functionality capabilities detailed in the Requirements Section of this PWS. The Contractor may utilize the DFSTS as simulation-stimulation. The USG may elect to observe and provide comments to each test.

The Contractor shall demonstrate IFATDS_GE capability via system level test cases per approved Releasability Matrix and the clarifications and specific capabilities indicated in the Requirements Section of this PWS. The Contractor shall prepare and provide test materials. At the conclusion of the Test for Record event, the Contractor shall prepare and provide a Software Test Report in accordance with CDRL, DD Form 1423, Data Item D003, DI-NDTI-80809B, Test/Inspection Reports.

Factory Acceptance Test (FAT) The Contractor…