DRAFT_Attachment 7 - Technical Specifications_DO1_C2PL-25-3.docx

DRAFT RFP: 70Z04426RC2PL2503

DRAFT ATTACHMENT 7

TECHNICAL SPECIFICATIONS

NEXT GENERATION SURFACE SEARCH RADAR (NXR) FOR THE UNITED STATES COAST GUARD (USCG) COMMAND, CONTROL, COMMUNICATIONS, COMPUTERS, CYBER, AND INTELLIGENCE SERVICE CENTER (C5ISC)

1 GENERAL

BACKGROUND

The Coast Guard (CG) uses Surface Search Radar (SSR) to provide operators with an advanced system for collision avoidance, safe navigation and enhanced situational awareness of the maritime environment. There are currently five separate radars in use on multiple ashore and afloat platforms. The current SSRs, which include the AN/SPS-50, AN/SPS-78, AN/SPS-79, AN/SPS-73, and Terma Scanter 2001 radars, installed across 14 cutter platforms and 113 Vessel Traffic Service (VTS) remote sites. In May 2019, Furuno USA notified the Coast Guard the FAR 2XXX series (which includes the AN/SPS-50 radar) was in final production and end-of-support. The AN/SPS-78 and AN/SPS-79 radars precede the AN/SPS-50, are significantly degraded, and overdue for recapitalization. Ashore, the VTS Terma Scanter 2001 Radars are end-of-support and require replacement. The AN/SPS-73 radar is beyond its service life and needs replacement.

The AN/SPS-50 and AN/SPS-78 are advanced SSRs used by the CG for navigational and surveillance purposes. The AN/SPS-50 provides target detection with a 25kW X-Band and a 30kW S-band transmitter/receiver (TR) up, turning unit, and a high-resolution LCD monitor. It displays up to 1,000 AIS-equipped contacts and acquires a maximum of 100 radar targets, complying with the latest IMO (International Maritime Organization) and IEC (International Electrotechnical Commission) standards. The AN/SPS-78 is designed for multiple cutter platforms and includes a radar and Stand-Alone Operator Position (SAOP) that enhances situational awareness of the maritime environment.

The AN/SPS-79 radar set is a short-range, two-dimensional radar system designed for use aboard the 418’ Maritime Security Cutter - Large (WMSL) National Security Cutter (NSC) vessels. It provides target detection with a 25kW X-Band and a 30kW S-band transmitter/receiver (TR) up, turning unit, and integrated with the C2 system as part of the multi-mission console. The AN/SPS-79 provides primary navigation and SSR (SSR) functionality using Commercial Off-The-Shelf (COTS) equipment.

The Terma Scanter 2001 radar series offer detection, monitoring, and management of vessel traffic movement in confined and busy waterways with small targets. It is an X-band, 2D, fully coherent pulse compression radar based on solid state transmitter technology with digital software-defined functionality. This radar is not IMO compliant and is utilized for shore-based applications only.

AN/SPS-73 SSR was designed for both large and small cutter applications but has been altered to be utilized for VTS sites with the assistance of a Personal Computer Based Radar Processor unit (PCRP). The SSR provides operators with an advanced navigation and surveillance system that enhances situational awareness of the maritime environment. The AN/SPS-73 system is comprised of a Furuno radar and includes the antenna, pedestal, receiver/transmitter, and performance monitor and is available in 25kW X-Band.

SCOPE

The Coast Guard (CG) seeks to procure a scalable, IMO-certified Surface Search Radar (SSR) system to serve as the primary collision avoidance system, enhancing navigation and surveillance for cutters and shore units. The system must ensure interoperability between core hardware components used both afloat and ashore, and ancillary devices receiving input from various navigation sensors, facilitating seamless integration with existing navigation systems and shore-based Vessel Traffic Services (VTS). This modernization effort aims to replace outdated AN/SPS-50, AN/SPS-78, AN/SPS-79, AN/SPS-73, and Terma radars across 13 cutter platforms, 113 VTS remote sites, and Coastal Sentinel improving sensor performance and standardizing system support.

1.3 APPLICABLE DOCUMENTS

1.3.1 Compliance Documents. The radar, associated accessories and documentation must conform to applicable standards identified in this section. The Contractor must adhere to all policies and procedures established by the Government, Safety Code, or Industry Standard. This is not a complete list of all references; therefore, the Contractor is required to meet all standard requirements /specifications, whether the reference document is listed or not. The documents listed below provide specifications, standards, or guidelines that must be complied with to meet established requirements:

a) Coast Guard Navigation Standards Manual, COMDTINST M3530.2 (series)

b) NMEA Standard 0183 Version 4.30 or greater

c) NMEA Standard 2000 Edition 3.000 or greater

d) NMEA Standard OneNet Version 1.001 or greater

e) MIL-STD-810H: Environmental Engineering Considerations and Laboratory Tests

f) MIL-STD- 167-1A: Mechanical Vibrations of Shipboard Equipment (Type I - Environmental and Type II - Internally Excited)

g) MIL-DTL-5015H: General Specification for Circular Threaded Connectors

h) ASTM Designation: F 1337-10 (2010): Standard Practice for Human Engineering Program Requirements for Ships and Marine Systems, Equipment, and Facilities

i) IEC 60945: International Standard on Maritime Navigation and Radio Communication Equipment and Systems

j) IEC 61108-1: International Standard on Maritime Navigation and Radio Communication Equipment and Systems – Global Navigation Satellite System (GNSS)

k) IEC 61162-1: Maritime navigation and radio communication equipment and systems – Digital interfaces - Part 1: Single talker and multiple listeners

l) IEC 61162-3: Maritime navigation and radio communication equipment and systems-Digital interfaces - Part 3 Serial data instrument network

m) IEC 61924-2: Maritime navigation and radio communication equipment and systems – Integrated navigation systems – Part 2: Modular structure for INS - Operational and performance requirements, methods of testing and required test results

n) IEC 61993-2: Maritime navigation and radio communication equipment and systems – Automatic identification systems (AIS) – Part 2: Class A shipborne equipment of the automatic identification system (AIS) – Operational and performance requirements, methods of test and required test results

o) IEC 62288: Maritime navigation and radio communication equipment and systems – Presentation of navigation-related information on shipborne navigational displays - General requirements, methods of testing and required test results

p) IEC 62388: Maritime navigation and radio communication equipment and systems - Shipborne radar - Performance requirements, methods of testing and required test results

q) NAVSO P-3641: Navy Power Supply Reliability Design & Manufacturing Guidelines

r) Human Factors Design Standard (DOT/FAA/HF-STD-001B), Federal Aviation Administration William J. Hughes Technical Center, December 2016.

s) Federal Radio Navigation Plan (2019)

t) Adoption Of The Revised Performance Standards For Radar Equipment (Resolution MSC.192(79) adopted on 6 December 2004)

u) Coast Guard Next Generation Surface Search Radar (NXR) System Requirement Document (SRD)

v) RTM Standard 13700.0 (2022) for Electromagnetic compatibility requirements for light emitting diode (LED) devices and other electrical and electronic equipment in vicinity of shipboard antennas for the protection of onboard receivers

As the references above are updated and revised, the most current versions of these documents replace the versions identified above and will be the required standards regardless of whether the list above is updated.

Note: If a notated FOUO (For Official Use Only) or NOFORN (Not Releasable to Foreign Nationals) reference document is requested, the requester must provide the Government with proof of eligibility from the Defense Information Security System (DISS) (formerly Joint Personnel Adjudication System (JPAS)) prior to obtaining access to the documents.

1.4 GOVERNMENT TERMS AND DEFINITIONS

AC – Alternating Current ACP – Azimuth Change Pulse AIS – Automatic Identification System API – Application Programming Interface ARP – Azimuth Reference Pulse BIT – Built-In Test Cat5- Category 5 Cat6- Category 6 CBRNE – Chemical, Biological, Radiological, Nuclear, Explosive CG – Coast Guard COTS – Commercial Off the Shelf DC – Direct Current DISS - Defense Information Security System DVI - Digital Visual Interface ECDIS- Electronic Chart Display Information System EMI- Electromagnetic Interference FAR – Federal Acquisition Regulation FCC – Federal Communications Commission FOUO – For Official Use Only GNSS – Global Navigation Satellite System GPS – Global Positioning System HDMI- High-Definition Multimedia Interface (HDMI) Hz- Hertz IAW – In Accordance With IEC - International Electrotechnical Commission IMO- International Maritime Organization IP – Internet Protocol JPAS - Joint Personnel Adjudication System KVM- Keyboard Video Mouse LAN – Local Area Network LCD – Liquid Crystal Display LED – Light-Emitting Diode MTBF – Mean Time Between Failure NAVSO – U.S. Naval Forces Southern Command NDI- Non-Developmental Items NEMA – National Electrical Manufacturers Association NM – Nautical Mile NMEA - National Marine Electronics Association NOFORN – Not Releasable to Foreign Nationals NSC – National Security Cutter NTIA – National Telecommunications and Information Administration NXR – Next Generation Radar OEM – Original Equipment Manufacturer PCRP – Personal Computer Based Radar Processor PPI – Plan Position Indicator RF – Radio Frequency RFI - Radio Frequency Interference RU- Rack Units SAOP – Stand Alone Operator Position SDK – Software Development Kit SRD – System Requirement Document SSR- Surface Search Radar TR – Transmitter/receiver USB- Universal Serial Bus VAC- Volts Alternating Current VDC – Volts Direct Current VTS – Vessel Traffic Service WMSL – Maritime Security Cutter, Large uS – micro seconds uV – micro volts

REQUIREMENTS

Reference Attachment 6 – NXSSR Compliance Crosswalk.

3 DHS-USCG ENTERPRISE ARCHITECTURE COMPLIANCE

All solutions and services shall meet DHS and USCG Enterprise Architecture policies, standards, and procedures. Specifically, the contractor shall comply with the following Homeland Security Enterprise Architecture (HLS EA) and USCG EA requirements:

All developed solutions and requirements shall be compliant with the HLS and USCG EAs.

All IT hardware and software shall be compliant with the HLS EA Technical Reference Model (TRM) Standards and Products Profile and with the USCG IT Products and Standards Inventory.

Description information for all data assets, information exchanges and data standards, whether adopted or developed, shall be submitted to USCG Enterprise Architecture Division (EAD) and DHS Enterprise Architecture Division (EAD) for review, approval and insertion into the USCG and DHS Data Reference Model and Mobius.

Software development must demonstrate measurable improvements in radar system integration, including greater than or equal to 20 percent reduction in data processing time or greater than or equal to 15 percent improvement in situational awareness accuracy compared to baseline. Compliance with DHS Data Management Policy MD 103-01 is required only if it directly supports these outcomes.

Applicability of Internet Protocol Version 6 (IPv6) to DHS-related components (networks, infrastructure, and applications) specific to individual acquisitions shall be in accordance with the DHS Enterprise Architecture (per OMB Memorandum M-05-22, August 2, 2005) regardless of whether the acquisition is for modification, upgrade, or replacement. All EA-related component acquisitions shall be IPv6 compliant as defined in the U.S. Government Version 6 (USGv6) Profile (National Institute of Standards and Technology (NIST) Special Publication 500-267) and the corresponding declarations of conformance defined in the USGv6 Test Program.

4 SECTION 508 COMPLIANCE

4.1 Section 508 Requirements (include in the SOW, PWS, or SOO) Section 508 of the Rehabilitation Act (classified to 29 U.S.C. § 794d) requires that when Federal agencies develop, procure, maintain, or use information and communications technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public with disabilities must be afforded access to and use of information and data comparable to that of Federal employees and members of the public without disabilities.

All products, platforms and services delivered as part of this work statement that, by definition, are deemed ICT shall conform to the revised regulatory implementation of Section 508 Standards, which are located at 36 C.F.R. § 1194.1 & Appendixes A, C & D, and available at https://www.ecfr.gov/cgi-bin/text-idx?SID=e1c6735e25593339a9db63534259d8ec&mc=true&node=pt36.3.1194&rgn=div5. In the revised regulation, ICT replaced the term electronic and information technology (EIT) used in the original 508 standards. ICT includes IT and other equipment.

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the Contracting Officer and a determination will be made according to DHS Directive 139-05, Office of Accessible Systems and Technology, dated November 12, 2018 and DHS Instruction 139-05-001, Managing the Accessible Systems and Technology Program, dated November 20, 2018, or any successor publication.

4.2 Section 508 Requirements for Technology Products (include in the SOW, PWS, or SOO) Section 508 applicability to Information and Communications Technology (ICT): Next Generation Shipborne Surveillance Radar System Applicable Exception: National Security Authorization #: EXC0001554 Applicable Functional Performance Criteria: Does not apply Applicable 508 requirements for electronic content features and components: Does not apply Applicable 508 requirements for software features and components: Does not apply Applicable 508 requirements for hardware features and components: Does not apply Applicable 508 requirements for support services and documentation requirements: Does not apply

4.3 Section 508 Requirements for Technology Products (include in the SOW, PWS, or SOO) Section 508 applicability to Information and Communications Technology (ICT): Training Documentation and Reports Applicable Exception: N/A Authorization #: N/A Applicable Functional Performance Criteria: All functional performance criteria in Chapter 3 apply to when using an alternative design or technology that results substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 508 Standards, or when Chapters 4 or 5 do not address one or more functions of ICT.

Applicable 508 requirements for electronic content features and components (including but not limited to Electronic documents; Electronic training materials): All requirements in E205 apply, including all WCAG 2.0 Level A and AA Success Criteria apply as specified in E205, except 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent Identification Applicable 508 requirements for software features and components (including but not limited to Electronic content and software authoring tools and platforms): All requirements in Chapter 5 apply, including all WCAG 2.0 Level A and AA Success Criteria Apply except 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, 3.2.4 Consistent Identification, 502 Interoperability with Assistive Technology, 503 Application, 504 Authoring Tools Applicable 508 requirements for hardware features and components (including but not limited to Peripheral Equipment (ex. keyboards); Video Displays and Monitors): All requirements in Chapter 4 apply Applicable 508 requirements for support services and documentation: All requirements in Chapter 6 apply

4.4 Section 508 Requirements for Technology Services (include in the SOW, PWS, or SOO)

4.4.1 When providing installation, configuration or integration services for ICT, the Contractor shall not reduce the original ICT item's level of Section 508 conformance prior to the services being performed.

4.4.2 When providing maintenance upgrades, substitutions, and replacements to ICT, the contractor shall not reduce the original ICT’s level of Section 508 conformance prior to upgrade, substitution or replacement. The agency reserves the right to request an Accessibility Conformance Report (ACR) for proposed upgrades, substitutions and replacements prior to acceptance. The ACR should be created using the on the Voluntary Product Accessibility Template Version 2.2 508 (or successor versions). The template can be located at https://www.itic.org/policy/accessibility/vpat

4.4.3 When developing or modifying ICT, the Contractor is required to validate ICT deliverables for conformance to the applicable Section 508 requirements. Validation shall occur on a frequency that ensures Section 508 requirements is evaluated within each iteration and release that contains user interface functionality.

4.4.4 When modifying, installing, configuring or integrating commercially available or government-owned ICT, the Contractor shall not reduce the original ICT Item’s level of Section 508 conformance.

4.4.5 When developing or modifying electronic documents and forms provided in a Microsoft Office or Adobe PDF format, the Contractor shall demonstrate conformance to the applicable to the applicable Section 508 standards (including WCAG Level A and AA Level 2.0 Success Criteria) by conducting testing using the test methods published under “Accessibility Tests for Documents” at https://www.dhs.gov/compliance-test-processes.

4.4.6 When developing or modifying ICT deliverables that contain the ability to automatically generate electronic documents and forms in Microsoft Office and Adobe formats, or when the capability is provided to enable end users to design and author web based electronic content (i.e. surveys, dashboards, charts, data visualizations, etc.), the Contractor shall demonstrate the ability to ensure these outputs conform to the applicable Section 508 standards (including WCAG 2.0 Level A and AA Success Criteria). The Contractor shall demonstrate conformance by conducting testing and reporting test results based on representative sample outputs. For outputs produced as Microsoft Office and Adobe PDF file formats, the Contractor shall use the test methods published under “Accessibility Tests for Documents”, which are published at https://www.dhs.gov/compliance-test-processes. For outputs produced as web based electronic content, the Contractor shall use the DHS Trusted Tester for Web Methodology Version 5.0, or successor versions. This methodology is published at https://www.dhs.gov/trusted-tester

4.4.7 Contractor personnel shall possess the knowledge, skills and abilities necessary to address the accessibility requirements in this work statement.

4.5 Section 508 Deliverables (include in the SOW, PWS, or SOO) Section 508 Test Plans: When developing or modifying ICT pursuant to this contract, the Contractor shall provide a detailed Section 508 Conformance Test Plan. The Test Plan shall describe the scope of components that will be tested, an explanation of the test process that will be used, when testing will be conducted during the project development life cycle, who will conduct the testing, how test results will be reported, and any key assumptions.

4.5.1 Section 508 Test Results: When developing or modifying ICT pursuant to this contract, the Contractor shall provide test results in accordance with the Section 508 Requirements for Technology Services provided in this solicitation.

4.5.2 Section 508 Accessibility Conformance Reports: For each ICT item offered through this contract (including commercially available products, and solutions consisting of ICT that are developed or modified pursuant to this contract), the Offeror shall provide an Accessibility Conformance Report (ACR) to document conformance claims against the applicable Section 508 standards. The ACR shall be based on the Voluntary Product Accessibility Template Version 2.0 508 (or successor versions). The template can be found at https://www.itic.org/policy/accessibility/vpat. Each ACR shall be completed by following all of the instructions provided in the template, including an explanation of the validation method used as a basis for the conformance claims in the report.

4.6 Other Section 508 Documentation: The following documentation shall be provided upon request for ICT items offered through this contract:

· Documentation of features provided to help achieve accessibility and usability for people with disabilities.

· Documentation on how to configure and install the ICT Item to support accessibility.

· Documentation of core functions that cannot be accessed by persons with disabilities.

· Documentation of remediation plans to address non-conformance to the Section 508 standards

5.0 TERMS AND CONDITIONS

5.1 ITAR SME Cybersecurity Policy

All hardware, software, and services provided must be compliant with DHS Security Policy. The 4300 handbook is no longer in use. Reference Information Security Systems Program 4300A version 13.3, Feb 13, 2023.

5.2 ISO Terms and Conditions for Sensitive but Unclassified Requests

5.2.1 DHS Security Policy Requirement

The following terms and conditions should be included in all acquisition documents. All hardware, software, and services provided under this task order must be compliant with DHS Information Security System Program 4300A version 13.3 Feb, 13 2023 and attachments.

5.2.2 Encryption Compliance Requirement

The following terms and conditions should be included in all IT procurement documents.

1. FIPS 197 (Advanced Encryption Standard (AES)) 256 algorithm and cryptographic modules that have been validated under FIPS 140-2 and / or FIPS 140-3.

2. National Security Agency (NSA) Type 2 or Type 1 encryption.

3. Public Key Infrastructure (PKI), key cards, biometrics, or in the case of multi-factor authentication, some combination therein (See Attachment U) Information Security Sensitive Systems Program Directive 4300A version 13.3, Feb 2023.

Security Review Requirement The following requirements should be included in all acquisition documents.

Security Review The Government may elect to conduct periodic reviews to ensure that the security requirements contained in the contract are being implemented and enforced. The Government, at its sole discretion, may obtain assistance from other Federal agencies and/or third-party firms to aid in security review activities. The Contractor shall afford DHS, the Office of the Inspector General, other government organizations, and Contractors working in support of the Government access to the Contractor’s facilities, installations, operations, documentation, databases, networks, systems, and personnel used in the performance of this contract. The Contractor shall, through the Contracting Officer and Contracting Officer's Representative (COR), contact the Component or Headquarters CIO, or designee, to coordinate and participate in review and inspection activity by government organizations external to DHS. Access shall be provided, to the extent necessary as determined by the Government (including providing all requested images), for the Government to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability, and confidentiality of government data or the function of computer systems used in performance of this contract and to preserve evidence of computer crime.

Interconnection Security Agreement (ISA) The following requirements should be included if the service being supplied requires a connection to a non-DHS, contractor system, or DHS system of different sensitivity.

Interconnection Security Agreement Requirements Interconnections between DHS and non-DHS IT systems shall be established only through controlled interfaces and via approved service providers. Connections with other federal agencies shall be documented based on interagency agreements, memoranda of understanding, service level agreements or interconnect service agreements. The applicable network connectivity policy is located in the Access Control Section, for “Interconnection Security Agreements,” of the DHS 4300A, Attachment N.

Required Protections for DHS Systems Hosted in Non-DHS Data Centers The following requirements should be included when information systems are hosted, operated, maintained, and used on behalf of DHS at non-DHS facilities. Contractors are fully responsible and accountable for ensuring compliance with all Federal Information Security Management Act (FISMA), National Institute of Standards and Technology (NIST), Special Publication SP-800-47, DHS Management Directive 140-01, “Information Technology Security Program,” Revision 2, May 5, 2017, Federal Information Processing Standard (FIPS) and related DHS security control requirements (to include configuration guides, hardening guidance, DHS Security Policy, Procedures, and Architectural guidance). The contractor security procedures shall be the same or greater than those that are provided by DHS Enterprise Data Center(s). Please note that all the subsections from Security Authorization to Log Retention must be included in this requirement to comply with 4300A Information Security Systems Program version 13.3, Feb 13, 2023, Attachment N.

Security Authorization A Security Authorization of any infrastructure directly in support of the DHS information system shall be performed as a general support system (GSS) prior to DHS occupancy to characterize the network, identify threats, identify vulnerabilities, analyze existing and planned security controls, determine likelihood of threat, analyze impact, determine risk, recommend controls, perform remediation on identified deficiencies, and document the results. The Security Authorization shall be performed in accordance with the DHS Security Policy and the controls provided by the hosting provider shall be equal to or stronger than the FIPS 199 security categorization of the DHS information system.

At the beginning of the contract, and annually thereafter, the contractor shall provide the results of an independent assessment and verification of security controls. The independent assessment and verification shall apply the same standards that DHS applies in the Security Authorization Process of its information systems. Any deficiencies noted during this assessment shall be provided to the COR for entry into the DHS’ Plan of Action and Milestone (POA&M) Management Process. The contractor shall use the DHS’ POA&M process to document planned remedial actions to address any deficiencies in information security policies, procedures, and practices, and the completion of those activities. Security deficiencies shall be corrected within the timeframes dictated by the DHS POA&M Management Process. Contractor procedures shall be subject to periodic, unannounced assessments by DHS officials. The physical aspects associated with contractor activities shall also be subject to such assessments.

The Government may elect to conduct periodic reviews to ensure that the security requirements contained in this contract are being implemented and enforced. The Government, at its sole discretion, may obtain assistance from other Federal agencies and/or third-party firms to aid in security review activities. Within ten working days’ notice, the Contractor shall afford DHS, the Office of the Inspector General, other government organizations, and Contractors working in support of the Government access to the Contractor’s facilities, installations, operations, documentation, databases, networks, systems, and personnel used in the performance of this contract. The Contractor shall, through the Contracting Officer and Contracting Officer’s Representative (COR), contact the Component or Headquarters Chief Information Officer, or designee, to coordinate and participate in the review and inspection activity of government organizations external to the DHS. Access shall be provided, to the extent necessary as determined by the Government (including providing all requested images), for the government to carry out a program of inspection, investigation, and audit to safeguard against threats and hazards to the integrity, availability and confidentiality of government data or the function of computer systems used in performance of this contract to preserve evidence of computer crime.

1.2 ITAR SME Cybersecurity Supply Chain Risk Management (C-SCRM)

Cybersecurity C-SCRM language is applicable for requirements for the use of supplies and services to include the following:

a. Definitions:

i. Component: a unit defined by the supplier that connects to and functions as part of the product. For software products, a component is a unit of software defined by a supplier at the time the component is built, packaged, or delivered. For hardware, a component is one hardware unit designed to connect to and function as part of a larger product.

ii. End-of-Life (EOL): means that an ICT product has reached the final stage of the product life cycle in which that version of the ICT product will no longer be supported nor manufactured (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iii. End-of-Support (EOS): means that an ICT product will no longer be supported (e.g., no patches will be developed, no security improvements will be made, and, sometimes, no troubleshooting technical assistance will be offered).

iv. Information and Communications Technology (ICT): encompasses the capture, storage, retrieval, processing, display, representation, presentation, organization, management, security, transfer, and interchange of data and information; includes all categories of ubiquitous technology used for the gathering, storing, transmitting, retrieving, or processing of information (e.g., microelectronics, printed circuit boards, computing systems, software, signal processors, mobile telephony, satellite communications, and networks).

v. Product: part of the equipment (hardware, software and materials) for which usability is to be specified or evaluated.

b. Original Equipment Manufacturer (OEM) End-use Information and Communications Technology (ICT) Product:

i. The contractor shall provide new equipment unless otherwise formally approved by the Government, in writing. The contractor shall provide only Original Manufacturer (OEM) end-use products to the Government. In the event that a shipped OEM product, or part or component of that product, fails, all replacements must be new (i.e., non-refurbished, not previously used) OEM.

ii. The contractor may provide previously used OEM products only with written Government approval. Such parts shall be procured from their original source and shipped only from the manufacturer's authorized shipment points.

c. Accounting of Components in ICT Products:

i. The contractor shall provide and maintain a list of components for each product used in performance of the contract, including through subcontracts or other arrangements. This list for each product shall provide the component manufacturer's name, address, state, and/or domain of registration, and, where applicable, the Unique Entity Identifier (UEI) number, for all components comprising the ICT products.

ii. The contractor shall notify the Government when a new contractor/subcontractor/service provider is introduced to the ICT provided on this contract, or when suppliers of components or products are changed. If a software component used in the performance of the contract is updated with a new build or release, the contractor must update the list provided in accordance with (i) above to reflect the new version of the software. This includes software builds to integrate an updated component or dependency.

iii. For software products, the contractor shall provide all OEM software updates, and patches to correct defects, for the life of the product [i.e., until the "End of Life" (EoL) or "End of Support" (EoS)]. Software updates and patches shall be made available to the government for all products procured under this Contract and replaced when End of Support (EoS) is reached.

iv. A contractor using team members in performance of the contract (e.g., subcontractors or other service providers) shall ensure that the standards for the accounting of components in this subsection are met by team members.

d. Supply-Chain Transport:

i. The contractor shall use formal, documented, and accountable transit, storage, and delivery procedures (i.e., the possession of the end-use product to be delivered is documented at all times from initial shipping point to final destination, and every transfer of the product from one custodian to another is fully documented and accountable) for all information and communication technology (ICT) shipments to fulfill this contract.

ii. The contractor shall maintain all records pertaining to the transit, storage, and delivery of ICT deliverables under this contract through at least 6 months after acceptance and make available for inspection upon request of the Government.

iii. The contractor shall make use of tamper-proof or tamper-evident packaging for all shipments.

iv. The contractor shall provide a packing slip for each container or package with the information identifying the contract or order number, a description of the hardware/software enclosed (Manufacturer name, model number, serial number), and the customer point of contact.

v. The contractor shall provide a shipping notification to the intended government recipient; with a copy transmitted to the Contracting Officer, or other designated representative. This shipping notification shall be provided electronically and identify the contract or order number, a description of the hardware/software being shipped (manufacturer name, model number, serial number), initial shipper, shipping date and identifying (tracking) number.

e. Changes to Ownership and Control:

The Contractor shall immediately notify the Contracting Officer and Contracting Officer's Representative regarding any significant changes to corporate ownership or control from contract award through final delivery or the end of the period of performance. A significant change would be one in which a change occurs in the individuals or entities who, directly or indirectly, either (1) exercises substantial control over an entity, or (2) owns or controls at least 25 percent of the ownership interests of an entity.