Atch 2 - DRAFT PWS JIATF-S RDDS 17 Nov 25.pdf

Performance Work Statement

For

FA4890-26-R-CN14

Radar Data Distribution System (RDDS)

17 NOV 2025

Prepared by:

Acquisition Management & Integration Center (ACC/AMIC) Langley Air Force Base

Distribution Statement D: Distribution authorized to the Department of Defense and U.S. DOD Contractors only; administrative/operational use. Other requests for this document shall be referred to ACC AMIC/PKDA

Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

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 the provisions of DoD Directive 5230.25

TABLE OF CONTENTS

1. Scope of Work

1.1. Mission

1.2. Objective

1.3. Location

1.4. Work Hours

2. Document Overview

2.1. Applicable Documents

2.2. Non-Government Documents

3. Performance Requirements

3.1. System Description

3.2. Flexible Modular Open System Architecture

3.3. Power Requirements

3.4. Environmental Performance

3.5. Electromagnetic Interference (EMI)/Electromagnetic Compatibility (EMC)

3.6. Reliability

3.7. Maintainability

3.8. Physical Characteristics

3.9. Laboratory Test Bed

3.10 Safety

3.11 Security

3.12 Documentation

3.13 Assessment and Authorization

4. Quality Control

4.1. Quality Assurance Terms and Definitions

4.2. Verification

4.3. Acceptance

5. Logistics Management

5.1. Delivery Location

5.2. Information Technology Asset Management

5.3. Contractor Logistics Support System

6. Program Management

6.1. U.S. Government Functions

6.2. Contractor Functions

6.3. Meetings

6.4. Compliance Requirements

6.5. Management Information System (MIS)

6.6. Human Resources

6.7. Operating Instructions (OIs)

6.8. Project Completion Report

7. Government Furnished Services

7.1. Base Support

7.2. CACs and Access Badges

8. Security Requirements

8.1. Clearance Requirements

8.2. Pass and Identification Items

8.3. Retrieving Identification Media

8.4. Traffic Laws

8.5. Weapons, Firearms, and Ammunition

8.6. Reporting Requirements

8.7. Controlled Unclassified Information

8.8. Access Control of Contractor Personnel

9. Deliverables Table

9.1. Kick Off Meeting Agenda

9.2. Integrated master Schedule

9.3. Software/hardware License and Certifications

9.4. Weekly Status Report

9.5. Inventory List

9.6. Technical Data and Documentation

9.7. Warranty Plan

9.8. Quality Plan

9.9. ATO Artifacts

9.10 Project Completion Meeting Agenda

10. Equipment Inventory and Warranty Listing Examples

11. Shelf-Life Item Listing Example

SECTION A

DESCRIPTION OF SERVICES

1.0 SCOPE OF WORK

1.1 MISSION

Reference 10 U.S. Code § 124, the United States (U.S.) Department of Defense (DoD), as the single lead agency of the Federal Government for Detection and Monitoring (D&M) of aerial and maritime transit of illicit drugs into the U.S. The DoD supports U.S. Government (USG) Agencies and Departments, and Partner Nations’ anti-trafficking and counter-threat finance efforts worldwide. The DoD uses Combatant Commands (CCMD), Military Departments, and Defense Agencies to provide a unique mix of military capabilities, platforms, Command, Control, and Communication (C3) systems, and personnel to support foreign and domestic law enforcement agencies and Governments, with mission partner Counter Narcotics (CN) assistance. The Joint Interagency Task Force South (JIATF-S) headquarters, located in Key West, Florida, executes detection and monitoring of illicit trafficking across all domains, and facilitates international and interagency interdiction to enable the disruption and dismantlement of illicit and converging threat networks in support of national and hemispheric security. This is accomplished through combined systems that create a single Common Operating Picture (COP) supporting air sovereignty, search and rescue, and regional cooperation mission sets. With the COP in place, the U.S. along with Partner Nations work in unison to provide air and maritime surveillance, communications, and command and control support to meet the mission objectives.

1.2 OBJECTIVE

The Contractor shall provide personnel, equipment, supervision, training, and materials as necessary to accomplish modernization and acceptance of the existing Radar Data Distribution System (RDDS). The current infrastructure needs to be upgraded to support new data formats, increased data volumes, and evolving security requirements. The current system is made up of a series of Sunhillo Longports, and Juniper 2056 Circuit to Packet (CTP) devices that enable receiving of RADAR and sensor data, protocol conversion, and distributing that data to various stakeholders, including JIATF-S mission processing systems, customers, participating government agencies, and Partner Nations. The Contractor shall ensure the RDDS networks meet or exceed equipment reliability (defined in Para 3.6), and operational availability standards, be scalable up to 320 bi-directional serial ports and 512 virtual ports and include documentation to support Authorization to Operate (ATO)accreditation for the host network IAW applicable USG guidance. A flexible, modular, and reliable system for managing and distributing radar and sensor data is required for implementation. This RDDS will replace or augment existing systems, providing enhanced capabilities and improved data sharing.

1.2.1 RDDS Network

The RDDS shall be a Commercial-Off-The-Shelf (COTS) flexible, modular open system architecture hybrid radar data distribution system for receiving remote radar and sensor data feeds in serial or Internet Protocol (IP) data format, and provide the distribution of the radar and sensor data in raw or processed serial and IP data format to data tracking and correlation processing systems, customers, and participating government agencies and Partner Nations.

The vendor will be responsible for the following:

System Design and Engineering: Design a robust and scalable RDDS architecture based on a Commercial-Off-The-Shelf (COTS) solution, maximizing reuse of existing JIATF-S RDDS components where feasible.

Software Development and Programming: Develop and configure the necessary software to receive, process, and distribute radar and sensor data in various formats.

Hardware Procurement and Integration: Procure and integrate all necessary hardware components, including servers, network equipment, and interface cards, to meet the system requirements.

Installation and Configuration: Install and configure the RDDS system at the designated JIATF-S facility, ensuring seamless integration with existing infrastructure.

Testing and Validation: Conduct thorough testing and validation of the RDDS system to ensure compliance with all performance specifications and security requirements.

Documentation and Training: Provide comprehensive documentation, including system specifications, technical manuals, and training materials for operators, administrators, and maintainers to support DAF MAN 8140 and DFMAN 17-1303, and DAFMAN 17-1305 requirements.

Ongoing Support and Maintenance: Provide ongoing support and maintenance services to ensure the continued reliable operation of the upgraded RDDS system.

Laboratory Test Bed (Optional): Provide, install, and checkout a laboratory test bed for testing repairs, modifications, and general engineering support of the fielded system (if the Government exercises this option).

1.3 LOCATION

The RDDS Network is located at JIATF-S headquarters, in Key West, Florida

1.4 WORK HOURS

JIATF-S normal business hours are between the hours of 0730-1600, except for the following Federal Holidays.

New Year’s Day Martin Luther King Day President’s Day Memorial Day Independence Day Juneteenth Columbus Day Labor Day Thanksgiving Day Veteran’s Day Christmas Day

2.0 DOCUMENT OVERVIEW

This document specifies the required RDDS essential operational functions and technical parameters. The requirements stated herein shall be utilized as a basis for providing the hardware and software of the radar data distribution system necessary to achieve the performance and capability requirements of the system.

2.1 APPLICABLE DOCUMENTS

These documents shall be applicable to the RDDS hardware and software/firmware as produced, modified, or developed. Any additional documents (i.e., second tier) listed in the Reference/Applicable Documents section of an invoked document shall be used for guidance and information purposes only, unless it is specifically called out in a referenced section of the invoked document.

2.1.1 Government Documents

The following Government documents form a part of the requirements to the extent specified herein.

STANDARDS

MIL-STD-130N Identification Marking of US Military

Property MIL-STD-461E Requirements for the Control of

Electromagnetic Interference Emissions and Susceptibility

MIL-STD-464 Electromagnetic Environmental Effects Requirements for Systems

MIL-STD-882D System Safety MIL-STD-1472G Design Criteria Standard; Human

Engineering

HANDBOOKS

MIL-HDBK-419A Grounding, Bonding, and Shielding for

Electronic Equipment and Facilities, Volumes I and II

MIL-HDBK-454A General Guidelines for Electronic Equipment

MIL-HDBK-470A Designing and Developing Maintainable Products and Systems, Volumes I and II

MIL-HDBK-46855A Human Engineering Requirements for

Military Systems, Equipment and Facilities

2.1.1.1 Other Government Documents

The following other Government documents form a part of this specification to the extent specified herein.

Unless otherwise specified, the issues are those cited in the solicitation or contract.

Department of Defense (D0D)

CJCSI 6510.01F Information Assurance (IA) and Support to Computer Network Defense (CND) DAFI 23-101 Management of Discrepant, Counterfeit and Suspect Counterfeit Materiel DOD 5200.28-STD Trusted Computer System Evaluation

Criteria

DODI 5000.64 Accountability and Management of DOD Equipment and Other Accountable Property

DODI 5000.76 Accountability and Management of Internal Use Software

DoDM 5400.07_AFMAN 33-302 Freedom of Information Act DODM 8140 Cyberspace Workforce Qualification and

Management Program

2.2 NON-GOVERNMENT DOCUMENTS

The following documents form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

National Fire Protection Association (NFPA)

NFPA 70 National Electrical Code 29CFR1910 Occupational Safety and Health Standards American National Standard

ANSI/ISO/ASQC Q9000-2005 Quality Management Systems –

Fundamentals and Vocabulary ANSI/ISO/ASQC Q9000 series Quality Management Standards ISO 9001/2000 Quality Management Systems

3.0 PERFORMANCE REQUIREMENTS

3.1 SYSTEM DESCRIPTION

The RDDS shall be a flexible, modular open system architecture hybrid radar data distribution system for:

• Receiving remote radar and sensor serial or IP data feeds

• Radar and sensor data multi-cast distribution, in serial and IP required-formats, to the JIATF-S mission processing systems, customers, and participating government agencies and Partner Nations.

The RDDS shall be a programmable-controlled radar data matrix switching and distribution system. The RDDS will consist of multiple bi-directional serial and Internet Protocol data ports, switch and module controllers, power supplies, and administrator, maintainer and operator interactive system management control workstation(s). The RDDS shall be programmable and easily reconfigurable to provide flexible mission operational adaptation to meet fixed site and tactical radar/sensor data sharing requirements. The RDDS shall be compatible with and interface to several input feeds and data distribution ports. The system shall have low latency (i.e., less than 100 nanoseconds) for data distribution applications.

The switching matrix architecture shall have no crosstalk.

3.1.1 System Specifications

The RDDS system must meet or exceed the following technical requirements:

• Data Format Support: Capable of receiving serial radar/sensor data in the following formats, but not limited to: CD-2, ARSR-4, TPS-70, and FPS-117, OTH Gold, ASTERIX 38. The RDDS shall also support IP data formats.

• Architecture: Flexible, modular open system architecture with bi-directional interfaces.

• Scalability: Scalable up to 320 bi-directional serial ports and 512 virtual ports. Also capable of IP radar/sensor data distribution to 6 IP clients with scalability up to 20 IP clients.

• Performance: Low latency (less than 100 nano-seconds) for data distribution applications. Switching matrix architecture shall have no cross-talk.

• Reliability: Mission MTBCF of 226,000 hours and a series configuration MTBF of no less than 300 hours.

• Maintainability: MTTR not to exceed 0.5 hours.

• Environmental: Meet specified environmental conditions for temperature and humidity.

3.1.1.1 Current RDDS Environment

The current system is made up of a series of Sunhillo Longports, and Juniper 2056 Circuit to Packet (CTP) devices that enable receiving of RADAR and sensor data, protocol conversion, and distributing that data to various stakeholders, including JIATFS mission processing systems, customers, participating government agencies, and Partner Nations.

3.2 FLEXIBLE, MODULAR OPEN SYSTEM ARCHITECTURE

The flexible, redundant, modular open system architecture shall include, but is not limited to, the following aspects: interoperability, scalability, upgradeability, reconfigurability, software standards, interface standards, lifecycle support, and sources of supply and/or repair.

The flexible, modular open system architecture shall allow the addition and/or integration of specialized radar and sensor data feeds, data distribution requirements, and software to adapt to changing data distribution and sharing requirements.

The flexible, modular open system architecture shall provide a clear path for the insertion of technical insertion capabilities into the system baseline configuration, as they reach appropriate maturity.

The system modular open architecture shall support the integration and interoperability of third-party COTS products with minimal changes to the system.

The system architecture shall have a modular architecture with redundancy and hot-swappable, field replaceable parts for 99.99 percent availability. There shall be no loss of system control as the result of failure of any system component or subassembly. There shall be no loss of any operating system capability during switchover from a primary to a secondary unit or component.

3.2.1 Bi-Directional Interfaces

The RDDS shall be scalable up to 128 bi-directional serial ports.

The RDDS shall be capable of IP radar/sensor data distribution to 6 IP clients with scalability up to 20 IP clients.

3.2.1.1 Radar and Sensor Data Feeds

The RDDS shall be capable of receiving serial or IP data from remote radar and sensor feeds.

The RDDS shall be capable of receiving serial radar/sensor data in the following formats, but not limited to:

CD-2, ARSR-4, TPS-70, TPS-75, FPS-117, OTH Gold, ASTERIX 38.

The system shall be capable of receiving IP data from those serial data feeds migrating from serial to IP data.

3.2.1.2 Data Distribution

The RDDS shall be capable of radar/sensor data distribution, in serial or IP format, to the JIATF-S data processing, fusion and correlation systems, customers, and participating government agencies and Partner Nations.

The RDDS shall be capable of multi-cast radar/sensor data distribution in the same format from which it was received.

The RDDS shall be capable of migrating from serial to IP data distribution as customers and participating government agencies and Partner Nations migrate from serial to IP data sharing.

3.2.2 System Management Control

The RDDS shall provide operator, administrator, and maintainer system management control workstations that provide interactive point-and-click control in path configuration, routing, monitoring, and troubleshooting. The control workstations shall include a graphical topology dashboard, providing users with easy navigation between systems, clear presentation of system configuration and capacity, simple drill-down from the system to the port level, and alarm tracking, reporting, troubleshooting and activity scheduling.

3.2.2.1 Maintenance and Diagnostics

The RDDS System Management Control workstations shall provide system diagnostics, including data generation/checking, protocol tracing, and error detection/injection. The system diagnostics shall efficiently track port-to-port path connectivity and equipment usage while linking resources in real-time, providing the ability to test and monitor without physically moving equipment or cables.

System management control shall notify the operator of internal rerouting if a path is deemed degraded or bad by continuous internal diagnostics and analysis, full path redundancy through diagnostic tools, and generates, stores/saves, displays and prints comprehensive system logs to help analyze and track all data sharing events that pertain to system and user intervention.

3.2.2.2 Log Files

The system shall maintain and provide printed output log information concerning system status, unit failures, reconfiguration messages, diagnostic messages, and data sharing events pertaining to system and user intervention and reboots. The log shall contain error messages, circuit confirmations, alarms, and fault detection and isolation information. The log shall be stored in non-volatile memory by the system processors.

A status summary dump of the system activity shall be archived in the log and available for print on demand.

3.2.2.3 Alarms

The equipment shall provide audible and visual alarms indicating false operation or other malfunctions resulting from component failure, crossed or open wiring, or other conditions affecting service which can be detected automatically. System alarms and fault detection error messages shall be routed to a terminal where the system status can be visually displayed on the screen.

Alarms shall be classified as catastrophic, major, or minor according to their effect on the distribution system.

The classification definitions are:

a. Catastrophic – Such as loss of mission availability or service. Demands immediate attention.

b. Major – Such as loss from radar feed or distribution port. Demands rapid action.

c. Minor – Non-emergency conditions that may cause degraded service or a fault condition that makes the system perform at a level less than for which it is designed. A condition found in switching and data distribution, which had not shown in operation of the system but requires attention.

The system shall provide alarms to indicate system faults. The audible signal shall have the capability of being silenced by operator action.

3.2.2.4 Error Messages

Error messages for failures, including power supply, low voltage alarms, and failure switchovers shall be archived into the log files, and displayed on the operator’s workstation. These messages shall be plain language format (vice alphanumeric codes), and shall include the date and time of failure, unit name, and type of failure.

Once corrected or rebooted, a report shall be log-archived showing the date and time of system recovery and action taken to correct the failure.

3.3 POWER REQUIREMENTS

The RDDS shall consist of redundant DC power supplies. This power equipment shall provide all required power to the RDDS. Its output capacity shall be such that it can accommodate a fully expanded RDDS, without exceeding 75 percent of the power equipment subsystem’s rated load. The power equipment subsystem and RDDS shall be designed such that there is not a loss of RDDS control as the result of failure of any power equipment subsystem component or subassembly. There shall not be a loss of any RDDS operating capability during switchover from a primary to a secondary power equipment subsystem device. A chassis lug shall be provided to enable installation personnel the ability of terminating the interconnecting cabling to a common ground potential.

3.3.1 Primary Input Power

The power subsystem shall be able to operate from a critical power source, be 120 VAC, single phase, 60 Hz for the switch and control modules and external devices.

3.3.2 Power Fault Indications, Fusing, and Wiring

The equipment shall be completely wired and equipped with fuses and/or circuit breakers, monitored and arranged for printout and display of fault conditions. All associated power and protection equipment shall be provided for the wired capacity of the frames or cabinets provided.

3.3.3 Fuse and Circuit Breaker Types

Fuses and circuit breakers shall be of a visual indicator type, except where an alarm printout and display indicates in plain text the location of a blown fuse or open circuit breaker. Fuse and circuit breaker ratings shall be designated by numerals or color code on the fuses, circuit breakers, or panels.

3.3.4 Power Distribution and Protection

The RDDS shall provide necessary facilities for primary/secondary power distribution and fuse protection.

3.3.5 Secondary Power Protection

Fused circuit protection with blown fuse indicating circuitry shall be provided for all switching and position equipment. Switching equipment shall be fused on an individual channel basis. Each position’s electronic and illumination circuits shall be fused separately. Blown fuse indications (faults) shall be reported through the maintenance diagnostic equipment subsystem. However, visual indication of which fuse has blown shall be provided on the associated fuse panel.

3.4 ENVIRONMENTAL PERFORMANCE

The system shall meet the following environmental conditions.

3.4.1 Temperature Requirements

3.4.1.1 System Components

System components, not specified to the operating and non-operating temperature requirements, may require warm-up and cooling procedures to be employed for start-up operations and/ or to avoid damage to the equipment.

3.4.1.2 Operating

All system equipment shall maintain the specified performance when exposed to the interior operating environmental conditions below:

a. Temperature range from +5 degrees C (41 degrees F) to +71 degrees C (+160 degrees F)

b. Relative humidity of 15 to 90 percent for both continuous and intermittent periods.

3.5 ELECTROMAGNETIC INTERFERENCE (EMI)/ELECTROMAGNETIC COMPATIBILITY

(EMC)

The system shall comply with the radiated and susceptibility requirements of MIL-STD-464 and MIL-STD- 461E: CE-102, CS-101, CS-114, CS-115, CS-116, RE-102, and RS-103.

3.6 RELIABILITY

The system reliability shall be stated in terms of specified Mean-Time-Between-Critical-Failure (MTBCF) (Mission Reliability) and Mean-Time-Between-Failure (MTBF) (Basic Reliability) in hours. The equipment configuration, reliability models, and reliability requirements for individual equipment or groups of equipment shall be determined and apportioned so that the reliability requirements specified below are satisfied.

a. The failure of any Line Replaceable Unit (LRU) shall not affect the performance of any other LRU.

b. Provision of power to LRUs or removal of power from LRUs shall not affect the performance of other LRUs.

c. The subsystem equipment shall be selected so that it meets the specified and apportioned reliability requirements while also meeting the specified performance requirements at minimum life cycle costs.

3.6.1 Mission Reliability

The complete RDDS system, consisting of all contractor-furnished equipment installed, shall achieve a mission MTBCF of 226,000 hours. MTBCF is defined as the total RDDS system uptime divided by the number of critical hardware, software, and firmware failures that degrade Full Mission Capability (FMC). Failures due to incorrect instructions in the system technical documentation shall also be counted as relevant failures. FMC is that level of performance, which allows the RDDS system to perform its mission within all the requirements of this specification. The MTBCF requirement shall be met under the maintainability requirements specified in paragraph 3.7.1.

3.6.1.2 Basic Reliability

The RDDS system shall achieve a series configuration MTBF as determined by reliability modeling, allocation and prediction within the specified allowable maintenance actions (see paragraph 3.7.1). However, in no case shall the series configuration MTBF be less than 300 hours. The series configuration MTBF is defined as the total system uptime divided by the total number of hardware, software, and firmware failures that require corrective maintenance action. Failures due to incorrect instructions in the system technical documentation shall be counted as relevant failures.

3.7 MAINTAINABILITY

3.7.1 Mean Time to Repair (MTTR)

The system shall have an MTTR not to exceed 0.5 hours when defined as the sum of active corrective maintenance times divided by the total number of failures within a given period of time. The maximum-corrective-maintenance-time (Mmaxct) (95th percentile) shall not exceed 1.0 hour when corrective maintenance is accomplished at the organizational level by the replacement of components. Corrective maintenance is unscheduled on-line and off-line actions accomplished, as a result of failure, to restore the system to full operational capability. The corrective maintenance time includes localization, isolation, disassembly, interchange, reassemble, alignment, and checkout for all corrective maintenance times. The equipment is considered to be in a corrective maintenance mode whenever a failure or malfunction (including a malfunction that allows degraded operation) is detected.

3.7.2 Special Tools/Test Equipment

No special tools or test equipment shall be utilized unless approved by the Government.

3.7.3 Preventive Mx Inspections (PMIs)

Provide a comprehensive, site-specific, preventive Mx program to identify all preventive Mx required to safeguard and extend the efficient and effective lifespan of the RDDS system. This program shall derive and cite guidance for applied preventive Mx tasks, inspections, frequencies, standard hours, and material requirements from Technical Order(s) (TO), Government regulation(s), directive(s), Unified Facilities Criteria (UFC) or Industry Standards, manufacturers recommended Mx procedure(s), or commercial manual(s) or as local conditions dictate for each item. Revise the Preventive Mx Inspection (PMI) program when changes occur to the RDDS. Maintain completion dates IAW submitted schedules. Unless the manufacturer or other governing regulation specifies a more stringent standard, a ten percent (10%) deviation will be allowed from each scheduled PMI date. The number of days will be rounded up so that, for example, a weekly PMI will have a one-day variance or a monthly would have three days.

3.7.4 Personnel

The system shall be capable of operations and maintenance by operators and maintainers, respectively.

3.7.5 Interchangeability

Interchangeable items shall be as specified using MIL-HDBK-454A, Guideline 7 as guidance. All parts having the same manufacturer’s part number shall be functionally and physically interchangeable. Interchangeability of assemblies shall be accomplished without the necessity for realignment of electrical circuits contained in the interchanged assembly. Readjustment is allowed for interchangeability of subassemblies and lower item levels.

3.8 PHYSICAL CHARACTERISTICS

The system shall have the following physical characteristics.

3.8.1 Cabling

The contractor shall provide all necessary interconnecting cables and connectors for the RDDS, serial ports, data distribution ports, and system management control workstations.

3.8.2 Equipment Cabinets/Enclosures

The contractor shall use JIATF-S 19-inch equipment cabinets/enclosures for the installation of their system.

3.8.3 Modularity

The RDDS shall be modular in construction so that radar/sensor data feeds, data distribution ports, and matured technology insertions may be added or removed incrementally without disruption to system operation.

Equipment cabinets shall incorporate connectorized wiring to facilitate initial installation and future expansion.

Card/module cages shall be populated (as required) with connectorized printed circuit boards/modules to establish the system configuration/capabilities and facilitate both maintenance and expansion. Expansion shall be accomplished by the addition of printed circuit cards, plug-in modules, cabinet subassemblies and cabinets.

3.8.4 Nameplates and Product Marking

Markings and/or nameplates shall identify all contractor-manufactured and assembled items that remain legible for the life of the item, remain attached for the life of the item and are visible during operational use. MIL-STD- 130N (including requirement for UID) shall be used for marking guidance.

3.8.5 Human Engineering

The system shall meet the human engineering requirements for both male and female personnel of MIL-STD- 1472G. MIL-HDBK-46855A shall be used as a guide for process and procedures.

3.9 LABORATORY TEST BED (optional)

The contractor shall provide, install, and check out, if and to the extent the Government exercises the option for the Laboratory Test Bed. The hardware, software, emulation equipment, and hardware support test bed instructions required to maintain an identically configured RDDS system for testing repaired cards, hardware, firmware, and software modifications, and general engineering support of the fielded system.

This hardware shall be identically configured to the hardware that is provided for the operational system, less radar/sensor data feeds. This hardware shall consist of a RDDS, one operator station, printer, all special test equipment required to support the operational system, and other interfaces, as well as any other peculiar support equipment necessary for maintenance and checkout of system modification developments, interface testing, and material to support operators. The laboratory test bed shall be located at JIATF-S.

3.10 SAFETY

3.10.1 Electric Shock

The equipment design shall protect against the risk of electric shock and other hazards during normal use and under any likely fault condition. Normal use shall be considered the worst-case operating condition and environment, and shall include setup, operation, maintenance, teardown, transport, and disposal.

3.10.2 Equipment Certification

The system shall maximize use of equipment Listed or certified using an appropriate industry safety standard by a Nationally Recognized Test Laboratory, such as Underwriters Laboratories. The Listing or Certification must cover the intended equipment usage and operating environment. Where equipment or systems are not listed or certified, they shall comply with the design requirements of NFPA 70 (National Electrical Code), and the appropriate UL or other industry safety standard.

3.10.3 Voltage

Personnel shall not be exposed to voltages greater than 30V. System integration and power distribution shall comply with the National Electrical Code. An Army approved grounding system shall be provided with the system, and a grounding stud shall be provided to permit bonding of equipment. Equipment leakage current to ground shall not exceed 3.5 Meter Interface Unit (MIU), when tested IAW ANSI C101.

3.10.4 Safe Maintenance

Equipment shall be designed so that maintenance can be conducted safely by designated maintenance personnel in accordance with NFPA 70B (Recommended Practice for Electrical Equipment Maintenance), and Title 29 Code of Federal Regulations, part 1910.

3.11 SECURITY

The RDDS shall be in compliance with the National Information Assurance Partnership (NIAP) National Security Telecommunications and Information Systems Security Policy (NSTISSP) Number 11. This compliance shall include having an NIAP Common Criteria Certificate.

3.12 DOCUMENTATION

System documentation such as system specifications, drawings, technical manuals (operator/user, administrator, and maintenance), system acceptance test plans and procedures, installation instruction data, spare and critical spare parts list, security accreditation, and training material shall be delivered.

3.13 ACCREDITATION AND AUTHORIZATION

The Contractor shall support efforts required to maintain the RDDS network accreditation and authorization.

The Contractor shall integrate, and develop procedures to maintain, operate, administer, troubleshoot, secure, and perform PMIs on the RDDS network and periphery equipment. The Contractor shall install, configure, remove/replace RDDS hardware components, peripheral equipment and perform SW Mx and upgrades as required. The Contractor shall maintain an event report log of all activities and provide to the AMIC PM upon request.

3.13.1 Authorization to Operate (ATO) Artifacts

The Contractor is responsible to provide artifacts that will be used to sustain the network ATO that the RDDS equipment resides on, IAW Chairman Joint Chiefs of Staff Instruction 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND). The Contractor shall write, and update technical documents, network requirements, equipment upgrades, and all required artifacts to include topology, Ports, Protocols, and Services (PPS) matrix, HW/SW list, STIG list, STIG and system safeguards within the RDDS equipment demarcations. As applicable; but not all inclusive, the Contractor shall use DoD Directives, Security Technical Implementation Guides (STIGs), DoD RMF Knowledge Service. The Contractor shall ensure all managed RDDS equipment meets DOD Risk Management Framework (RMF) requirements. The Contractor shall review and submit all required documents via to the ISSM for approval/disapproval prior to implementing network systems modifications. Report STIGS completion and submit results according the ATO Configuration Management Plan Policy.

3.13.2 System Topology

The contractor shall establish a system topology diagram to include all network devices with a clearly defined demarcation point. This system topology shall also include IP addresses for all IT devices. This topology shall be updated to reflect changes within 7 days and be hosted inside the MIS.

3.13.3 Vulnerability Management

The contractor shall develop a vulnerability management SOP that will establish a vulnerability management system IAW DoDI 8531.01. The vulnerability management system shall be setup to scan all devices with full credentialed access.

3.13.3 Security Updates

The Contractor shall develop and implement a SOP that addresses security updates and maintains all network SW, firmware, and security updates for IT equipment within assigned demarcation points to ensure networking systems conform to DoD, and industry safeguards.

3.13.4 Controls

The Contractor shall implement and maintain network system controls SOP that will prevent unauthorized access to all Government-owned devices and assets within the RDDS system IAW Chairman Joint Chiefs of Staff Instruction 6510.01F, Information Assurance (IA) and Support to Computer Network Defense (CND) and applicable COTS publications, directives, OIs, and service manuals.

4.0 QUALITY CONTROL

The contractor shall implement a Quality Assurance Program shall be established, documented, controlled, auditable, consistent with the ANSI/ISO/ASQC Q9000 series and based on ISO 9001/2000, or equivalent to ensure the reliability of the RDDS system. The quality assurance process shall be coordinated with the related verification, validation, joint review, and audit processes. System verification shall include the complete RDDS, including all functional areas, and all internal and external interfaces. All verifications shall be performed by the contractor, as specified herein. All non-developmental items (NDI) procured shall be tested in accordance with standard vendor practices. Certificates of conformance and/or test data shall be available for Government review. Unless otherwise specified in the contract, the contractor shall be responsible for performing all testing necessary to demonstrate compliance with this performance specification. The Defense Contract Management Area Contract Management Office’s (DCMA, CMO) shall not be responsible for performing any testing, although the Government reserves the right to witness, perform, or assist in performing any of the tests set forth in this specification where such testing is deemed necessary by the Government to assure that supplies and services conform to prescribed requirements. When Government participation is deemed necessary, the Government will be notified ten (10) working days prior to testing and will provide written notice three (3) days prior to the scheduled test.

4.1 QUALITY ASSURANCE TERMS AND DEFINITIONS

Quality assurance terms used in this specification shall be as defined in ANSI/ISO/ASQC Q9000-2005.

4.2 VERIFICATION

Verification shall include inspection, analysis, demonstration and tests.

4.2.1 Inspection

Inspection shall consist of visual examinations, reviewing documentation, and comparing characteristics with specified system requirements. Inspections shall verify characteristics such as construction features, document and drawing compliance, workmanship, and physical condition.

4.2.2 Analysis

Analysis shall consist of theoretical analysis of system operation or computer simulations to determine conformance to specified system requirements. Analysis shall verify characteristics such as concealed design, performance, construction features, processes of manufacturing, and system operation through study, calculations, and modeling.

4.2.3 Demonstration

Demonstration shall consist of functional verifications by operation, movement, and/or adjustment of an item under test to determine conformance to specified system requirements. Demonstrations shall verify characteristics such as operational performance, human engineering features, service, access features, and transportability.

4.2.4 Tests

Test shall consist of measuring or recording system parameters and performance during or after the controlled application of operational, functional, and/or environmental stimuli. Test shall verify characteristics such as capacity, throughput, detection, and tracking.

The following tests and evaluations shall be accomplished in accordance with approved test plans and procedures prepared by the contractor and approved by the government. The tests and examinations include:

• Screening

• Acceptance System Test

4.2.4.1 Screening

Prior to any tests or examinations, the equipment shall be screened to detect workmanship defects.

4.2.4.2 System Acceptance Test

Following system equipment installation at JIATF-S, the complete system shall be tested in accordance with test plans and procedures provided by the contractor and approved by the Government. As part of the ongoing testing, the system shall be tested for specified operations. The contractor shall develop the test plans and procedures for the system acceptance testing.

The contractor shall verify all requirements of the RDDS system and its interfaces with the JIATF-S facilities during the system acceptance testing. Electromagnetic Interference (EMI) control and Electromagnetic Compatibility (EMC) for the system shall be approved and tested in accordance with the guidelines of MIL- STD-461E and all system equipment shall be subjected to leakage current testing in accordance with the guidelines of paragraph 5.1.3.10.1 of MIL-HDBK-2036A. All system acceptance testing shall be successfully completed prior to the start of the reliability demonstration.

All software delivered with the system shall be patch-free. Any patches, resulting from faults detected during the system acceptance test, shall be the responsibility of the contractor. When the software problem is rectified, all software in the equipment shall be reloaded and retested before the conclusion of the system acceptance test.

All firmware delivered with the system shall be error free. When firmware faults are detected during the system acceptance tests, the contractor shall insure the vendor fixes the problem. The contractor shall be responsible for ensuring the vendor regenerates the firmware, provides new modules, and retests prior to the conclusion of system acceptance testing. All software/firmware changes shall be under configuration control.

All test apparatus used in conducting the system acceptance test shall be provided by the contractor. Any unique test fixture or test jigs developed under this contract shall be delivered to the Government.

4.3 ACCEPTANCE

System Acceptance shall be predicated upon successful completion of the contractor conducted System Acceptance tests, as documented in the System Acceptance test report.

5.0 LOGISTICS MANAGEMENT

Provide and manage a cost-effective logistics program that includes all supply, transportation, equipment Mx, and property control functions necessary to support the operating locations. Government- furnished equipment (GFE) shall be managed IAW DODI 5000.64, Accountability and Management of DOD Equipment and Other Accountable Property, DODI 5000.76, Accountability and Management of Internal Use Software, DOD FMR, 7000.14-R, Volume 4, Chapter 25, General Equipment, and DOD FMR, 7000.14-R, Volume 4, Chapter 27, Internal Use Software.

5.1 DELIVERY LOCATION

The Point (s) of Delivery (POD) for IT assets will be Key West, Florida, Joint Interagency Task Force South (JIATF-S) with primary point of contact (POC), for the end user (EU) as JIATF-S/J6. The contractor shall structure delivery events to minimize cost and United States Government (USG) delivery assurance travel and maximize available Original Equipment Manufacturer (OEM) warranty. If the contractor subsequently becomes aware of any circumstances that may delay delivery/installation, the contractor is required to immediately notify the USG, explain the circumstances, and provide recommendations for mitigating any delays both in informal and formal communications.

The contractor shall notify the AMIC Multi-functional Team (MFT) [Program Manager (PM), Contracting Officer (CO), Contract Manager (CM), Contracting Officer’s Representative (COR) (names and email address provided at kick-off) of any long lead items, items that are unavailable/obsolete.

5.1.1 Holidays. To avoid delay, the contractor shall coordinate required documentation and delivery events around US federal holidays. See the Multiple Award (MA) Indefinite Delivery Indefinite Quantity (ID/IQ) Performance Work Statement (PWS) paragraph 2.6.2 for US legal holidays. In accordance with (IAW) US Law, American holidays falling on Saturday will be observed on the preceding Friday, and those falling on Sunday will be observed on the subsequent Monday.

5.2. INFORMATION TECHNOLOGY ASSET MANAGEMENT

The Contractor shall create technical solutions to purchase, as Government Furnished Equipment (GFE), all required computer hardware and SW equipment to support the RDDS mission. Hardware or SW requirements must be approved by the Government prior to purchase. IT assets paid for by the Government will be considered GFE and shall be added to the GFE listing CDRL A004. The purchase or replacement of contractor owned computer hardware and SW providing administrative functions supporting the RDDS Mission are at the contractor’s expense. IT assets used to connect or configure DoD networks or weapon systems shall be GFE.

5.2.1 Supply Chain Risk Management

The Contractor shall mitigate supply chain risks to include: counterfeit equipment, malicious introduction of unwanted function(s), and sabotage, in the procurement of all supplies and services to the Government.

- Do not purchase counterfeit or substandard assets.

- Information Technology/Telecommunications equipment produced by manufacturers identified within Section 889 of the NDAA of 2019 or any subsidiary or affiliate of such entities is strictly prohibited. Requesters must review current list located at www.sam.gov for excluded parties prior to requesting authorization to purchase and within 24 hours prior to any purchase of information technology and/or telecommunications equipment.

Purchase assets from the DoD-approved sources only, such as: Client Computing Solutions (CCS-3), Global Enterprise Modernization SW & Support (GEMSS), or other approved DoD approved Information Technology Acquisition programs.

5.3 CONTRACTOR LOGISTIC SUPPORT SYSTEM

To the maximum extent possible, utilize commercial sources for obtaining parts and supplies for repairs that meet TO and manufacturer's data as applicable to meet the objectives of DODI 5000.64, Accountability and Management of DOD Equipment and Other Accountable Property, DODI 5000.76, Accountability and Management of Internal Use Software, DOD FMR, 7000.14-R, Volume 4, Chapter 25, General Equipment, and DOD FMR, 7000.14-R, Volume 4, Chapter 27, Internal Use Software. Mandatory sources must be used/eliminated as the first source for all commercial procurements.

5.3.1 Authorizations

The Contractor shall reimburse all costs associated with purchase(s) not authorized if already billed and paid by the Government.

5.3.2 Management of Discrepant, Counterfeit and Suspect Counterfeit Materiel/Property

Manage IAW DAFI 23-101, Paragraph 5.10 Management of Discrepant, Counterfeit and Suspect Counterfeit Materiel. Prepare and submit a detailed report to the AMIC PM and appropriate functional branch as determined by AMIC PM whenever Discrepant, Counterfeit and Suspect Counterfeit Materiel is/are procured; report shall be submitted within 24 hours of discovery and shall include all pertinent acquisition data to include identification data, PO#, source, date of procurement/receipt, cost data and reason for believing the property is suspect.

5.3.3 Information Assurance (IA)/Computer Security Requirements

The contractor shall ensure that all products recommended and/or procured that impact IA shall be selected from the National Information Assurance Partnership Validated Products List. The products chosen shall be based on the appropriate Evaluated Assurance Level (EAL) for the network involved and utilized IAW the latest Defense Information Systems Agency (DISA) policy at time of order. This information shall be tracked and available for COR review as requested.

5.3.4 Supply Chain Procedures

See PWS paragraph 2.12.12.

5.3.5 Receipts

Process receipt of property within 24 hours and maintain receipt documentation. Inspect all property to ensure it meets the criteria prescribed in DODI 5000.64, Accountability and Management of DOD Equipment and Other Accountable Property, DODI 5000.76, Accountability and Management of Internal Use Software, DOD FMR, 7000.14-R, Volume 4, Chapter 25, General Equipment, and DOD FMR, 7000.14-R, Volume 4, Chapter 27, Internal Use Software.

5.3.6 Deficiency Report

The Contractor shall prepare a Deficiency Report (DR) when an item is received with quality deficiencies or installed with material deficiencies. In addition, the Contractor shall identify all re-engineered assets and provide DRs when performance is deficient. Items received from all sources shall adhere to the guidance of TO 00-35D- 54D-WA-1. Deficiency Report shall be IAW CDRL A019.

5.3.7 Physical Asset Management

Implement and manage a uniform storage and material handling system that meets the objectives of DODI 5000.64, Accountability and Management of DOD Equipment and Other Accountable Property, DODI 5000.76, Accountability and Management of Internal Use Software, DOD FMR, 7000.14-R, Volume 4, Chapter 25, General Equipment, and DOD FMR, 7000.14-R, Volume 4, Chapter 27, Internal Use Software, for all on- hand in-warehouse property. Requisition consumables to meet customer requirements and stockage objectives.

5.3.8 Property Control/Administration

Identify and code all GFP according to their property functional application and class to include, consumable, plant equipment, repairable and electronic serial number (ESN).

5.3.9 Life Cycle Logistics System

Manage all Government furnished Plant Equipment by utilizing a life cycle approach. Use the logistics data fields (as applicable) identified in Appendix K. This life cycle approach shall be maintained on the contractor’s MIS in a real-time state current to 24-hours and used to program all replacement assets and budget preparation. The life cycle approach shall be provided to the Government in conjunction with CDRL A004. The life cycle approach should be based on Fiscal Year reporting requirements.

5.3.10 Safeguarding Government Property

Provide applicable safeguards, protection, and control for Government property stored or being processed for shipment that meets the objectives of DODI 5000.64, Accountability and Management of DOD Equipment and Other Accountable Property, DODI 5000.76, Accountability and Management of Internal Use Software, DOD FMR, 7000.14-R, Volume 4, Chapter 25, General Equipment, and DOD FMR, 7000.14-R, Volume 4, Chapter 27, Internal Use Software.

5.3.11 Property Disposal Procedures

The contractor shall implement property disposition/disposal procedures for assets associated with the outgoing RDDS system that will not be incorporated into the modernized system IAW DODI 5000.64, Accountability and Management of DOD Equipment and Other Accountable Property, DODI 5000.76, Accountability and Management of Internal Use Software, DOD FMR, 7000.14-R, Volume 4, Chapter 25, General Equipment, and DOD FMR, 7000.14-R, Volume 4, Chapter 27, Internal Use Software with the exception of Defense Property Account System (DPAS) and Information Technology items. Information Technology items managed IAW DODI 5000.64, Accountability and Management of DOD Equipment and Other Accountable Property, DODI

5000.76, Accountability and Management of Internal Use Software, DOD FMR, 7000.14-R, Volume 4, Chapter 25, General Equipment, and DOD FMR, 7000.14-R, Volume 4, Chapter 27, Internal Use Software. For all IT assets contact ACC AMIC/PCYM accamic.pcy.pcym@us.af.mil for guidance.

5.3.12 Material Management System Managed Items

Items managed in Material Management Systems (MMS). For Materiel Management System (MMS) managed items, report excess, lost, damaged,…