Attachment 0001_BFC2 PWS_04-39-2025.docx

DRAFT

Product Manager Biometrics

Performance Work Statement for Biometrics and Forensics Collection Capability (BFC2)

Solicitation Number: TBD

Dated: 10 April 2025 DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense (DoD) and U.S. DoD contractors only by specific authority of AR 380-5. Date of determination is 02 February 2024. Other requests for this document shall be referred to the Product Manager (PM) DoD Biometrics, 10115 Gratiot Road, Building 363, Fort Belvoir, VA 22060; (703) 704-0336.

SOURCE SELECTION SENSITIVE

SOURCE SELECTION SENSITIVEDRAFT

Table of Contents

Product Manager Biometrics

16.0 Contractor Manpower and Reporting 32

ii

1.0 Scope

This Performance Work Statement (PWS) defines the requirements for Product Manager (PM) Biometrics’ procurement, fielding, and sustainment of products that fall under Biometrics and Forensics Collection Capability (BFC2) portfolios. It includes all efforts associated with a five (5)-year Indefinite Delivery/Indefinite Quantity (IDIQ) contract to include program management, system procurement (hardware (HW) and software (SW)) and fielding, system sustainment, software engineering services, cloud services, help desk services, and cybersecurity services.

1.1 bACKGROUND

PM Biometrics under Project Manager Terrestrial Sensors (PM TS), Program Executive Office for Intelligence, Electronic Warfare and Sensors (PEO IEW&S) designs, engineers, acquires, deploys, and sustains enterprise biometric and forensic solutions in multiple operating environments enabling identity dominance on the battlefield and across the Department of Defense (DoD). PM Biometrics’ information technology (IT) systems capture, transmit, store, manage, share, retrieve, and display biometric data for timely identification or identity verification. BM Biometrics’ Forensics IT systems assist with gathering and analyzing data specific to intelligence, detainee management, and forensics within Areas of Responsibility (AORs) to provide Near Real Time (NRT) information to Commanders and stakeholders. These systems are mission enablers for force protection, intelligence, physical and logical access control, identity management/credentialing, detention, and interception operations. PM Biometrics provides HW and SW support to various operations, including counterintelligence (CI), detainee operations, and post-Improvised Explosive Device (IED) incident exploitation, intelligence operations, presence operations, local population control, seizure operations, and base access control.

1.1.1 PL Biometrics Collection Capability

Product Lead (PL) Biometrics Collection Capability (BCC) provides the Army tactical biometric collection capability to capture biometric data of an adversary or neutral person and enroll them into DoD Automated Biometric Identification System (DoD ABIS). This enables the data capture and enrollment process for identity verification of actual or potential adversaries. Collection devices include the Biometrics Automated Toolset - Army (BAT-A), Near Real Time Identity Operations (NRTIO), and Next Generation Biometric Collection Capability (NXGBCC).

BAT-A System Overview The BAT-A Program of Record (PoR) has been supporting contingency operations for over twenty (20) years. BAT-A is a biometric system comprised of both hardware and software that is capable of capturing, storing, matching, and disseminating biometric and biographical data on non-U.S. personnel. BAT-A integrates Commercial Off-The-Shelf (COTS) biometrics subsystems and hardware components (fingerprint, iris, and facial capture) with special purpose Government Off-The-Shelf (GOTS) software for capabilities such as digital dossier creation, biometric searching of the database for matches to Known and Suspected Terrorists (KST) and supporting detainee management. In addition, BAT-A contains peer-to-peer network software that provides the capability of synchronizing databases throughout a network of BAT-A systems.

Currently supported components of the BAT-A system include the following:

· Biometrics Automated Toolset-Army Kit (BAT-A Kit)

· BAT-A Client (PC-based hardware)

· Peripheral devices for enrollment and associated functions

· Biometrics Automated Toolset-Army Handheld (BAT-A HH)

· It should be noted that the BAT-A HH is sometimes referred to as either BAT-HH or as the Secure Electronic Enrollment Kits II (SEEK II). However, the preferred current usage holds that the SEEK II refers to the previously available COTS hardware, wherein the BAT-A HH refers to the hardware/software combination that enables the device to perform the necessary mission functions.

· Biometrics Automated Toolset Web (BAT.Web)

· Provides 24X7 access to BAT-A data without the requirement to have BAT-A hardware.

NRTIO System Overview The NRTIO Quick Reaction Capability (QRC) has been supporting contingency operations since 2016. NRTIO is an identity information system intended to enhance the processing and sharing of biometric data within the United States Central Command (USCENTCOM) AOR. The system ingests biometric records collected by US forces and agencies, partner nations, and other coalition forces; compares them to active watch lists and previously collected biometric records; and provides rapid identity verification and alerts to support identity operations and inform Anti-Terrorism and Force Protection (AT/FP) decisions. To support in-theater operations, the NRTIO system returns biometric match responses in NRT, which is defined as less than 3-minutes.

NRTIO is based on an unclassified architecture to facilitate the sharing of identity information between US and coalition partners in the USCENTCOM AOR. Key components of the system include biometric collection devices (SEEK II and Jump Kit), data communications platforms, and an Amazon GovCloud with a web portal user interface. The handheld, man-portable biometric collection device support missions that involve security screening, vetting, or force protection, especially those requiring compact or mobile collection solutions. The Jump Kit is a ruggedized collection platform, optimized for fixed-site operations. Jump Kits are commonly used at checkpoint operations, entry control points, or other static locations where security screening, vetting, or force protection missions are conducted, and subjects are brought to the collector. A Jump Kit is comprised of a waterproof and airtight case, an iris scanner, a digital camera, a fingerprint scanner, a laptop computer, a card scanner, and cleaning and maintenance supplies.

Currently supported components of the NRTIO system include the following:

· NRTIO Static/Jump Kit

· Dell Latitude 5440

· IrisID iCAM R100 Dual Iris and Face Camera

· HID Guardian 200 Fingerprint Device

· USB-C to Ethernet Adapter

· Anker USB-C to 4-port USB Hub

· Pelcian Case, 6700 Series

· NRTIO Mobile Device

· IDS Hand-held Collection Device

· Sapre Visor Assembly (1)

· Lithium ion Battery (4)

· External Battery Charger (1)

· Modified Power Supply (1)

· External Battery Charger (1)

· Hardware Tool Kit (1)

· Spare Mounting Hardware (1)

· NRTIO Medium Maverick Terminal

· Case 1: Reflector

· Case 2: Azimuth Hub and Elevation Jack

· Case 3: Legs and Controller Feed

· Case 4: Indoor Unit (IDU)

· NRTIO Cellular Kit

· TBD

NXGBCC System Overview The NXGBCC PoR will replace the current BAT-A capability. NXGBCC will support Army force protection and identity dominance missions. It is designed to support access control, identify persons of interest, and provide biometric identities to detainee and intelligence systems through submission to DoD ABIS. NXGBCC collects, matches, stores, and shares biometric, biographical, and contextual data through fingerprint, iris, voice, and facial modalities. The capability will be used for both mobile and static operations in connected and disconnected, intermittent, and limited connectivity environments to inform the Warfighter of potential threats in NRT.

The NXGBCC system is comprised of collection devices and the Ares Gateway Transaction Manager (AGTM). The AGTM along with the mobile (JavelinXL) and static (Javelin Jump Kit Lite) devices and associated peripherals are commercial items. The collection devices will interface with the DoD ABIS via the AGTM. The AGTM will function as a transaction manager, receiving biometric submissions from the JavelinXL and Javelin Jump Kit Lite. Biometric matches will be returned from DoD ABIS to AGTM and automatically transmitted back to the collection device in NRT.

Components of the NXGBCC system include the following:

· Javelin Jump Kit Lite

· Nanuk 915 IP67 Kit Case (PARENT)

· Dell Latitude 5340

· IrisID iCAM R100 Dual Iris and Face Camera

· Integrated Biometrics Five-o Fingerprint Sensor

· USB-C to Ethernet Adapter

· Anker USB-C to 4-port USB Hub

· JavelinXL Mobile Biometric Collection Kit

· JavelinXL Pelican Case

· JavelinXL, Black, S23, Standard Label

· Integrated Biometrics Five-o Fingerprint Sensor

· Four Fingerprint Sensor

· Dual Iris Sensor

· Samsung Galaxy Smart Phone Galaxy S23-128GB

1.1.2 PL Forensics

PL Forensics is responsible for the delivery of several capabilities that support a range of military operations. PL Forensics actively engages with a wide range of stakeholders in executing its mission to deliver enhanced forensic and forensic-adjacent capabilities for improved intelligence collection and law enforcement. Capabilities include two new start programs, Counterintelligence (CI) Human Intelligence (HUMINT) Equipment Program - Army (CIHEP-A) and Detainee Management Accounting and Reporting (DMAR), as well as the Forensic Exploitation Laboratory (FXL). CIHEP-A and DMAR initial research and development efforts begun or will begin in Fiscal Year 2025 (FY25) and FY26 respectively, and FXL will begin in FY28.

CIHEP-A System Overview The CIHEP-A PoR will replace the Army’s current CI and HUMINT Automated Reporting and Collection System (CHARCS) PoR. CIHEP-A provides an integrated suite of capabilities to enable CI to identify, deter, neutralize, and exploit adversarial intelligence collection, and insider threats, and HUMINT to provide insight and information on enemy activities, capabilities, motivations, and objectives. Collection of this intelligence data contributes to situational awareness and understanding to increase lethality. HW includes integrated and advanced communication devices, and technically advanced solutions to enable collection, reporting, analysis and production of information and intelligence for battlefield preparation and Large-Scale Combat Operations (LSCO).

CIHEP-A consists of four (4) packages that are assembled based on mission requirements:

· CIHEP-A Basic Package – Provides foundational communication and analysis capabilities, to include a social network scraper and multi-language translator resident on the provided computer processing system. Docking stations and all peripherals will be required as well as another computing device capable of transmitting classified data. A COTS/GOTS satellite communication (SATCOM) device will be included to enable voice and data transmission up to the SECRET level. Cross domain solutions will be required as well as an application to support collection and organization of collected data (presumably the SW supporting the HW solution) so that information can be reviewed. The package will also provide the necessary HW and connectors to connect to a vehicle-based radio; the vehicle-based radio will be provided as Associated Support Items of Equipment (ASIOE).

· Team Support Package – A tactical equivalent to the Basic Package solution, the Team Support Package provides the same HW/SW for analysis, with a lighter, more portable Line of Sight (LOS) radio option instead of the SATCOM capability.

· Functional Support Package – Provides critical intelligence data collection capabilities, including a Beyond Line of Sight (BLOS) SATCOM capability, portable biometric collection device, an imagery/video collection kit, and a forward-looking infrared camera. A credibility assessment device and countersurveillance kit to detect radio frequencies (RF) in the area will also be included. Each of these components could be packaged for transport separately so that the operators only need to carry the equipment necessary for the mission at hand.

· Media Exploitation (MEDEX) Package – Provides a static processing device with the capacity and software necessary to capture, store, and analyze media including computer hard drives, cell phones, and secondary storage. Adaptors will be included to allow the exploitation of audio and video recorders and recordings.

DMAR System Overview The DMAR PoR will replace the legacy Detainee Reporting System (DRS). DMAR is a web-based software system that provides NRT tracking and accountability of Detainees and/or Enemy Prisoners of War (EPWs). The system provides Military Police Commands with the capability and capacity to operate an AOR registry to account for, manage/store detainee information including administrative, biometric, legal, medical, and intelligence data allowing for timely and efficient automated detainee management and tracking as well as generate reports on detainee operations to the Secretary of Defense and other organizations (national and international) as required by law. DMAR will serve as the primary means to maintain accountability and track all movement within and between Detainee Holding Areas (DHAs), Theater Detention Facilities (TDFs) and Strategic Detention Facility (SDFs) worldwide.

1.2 PERIOD OF PERFORMANCE

The IDIQ Period of Performance (PoP) shall be sixty (60) months; one (1) twelve (12)-month base period from the date of award with four (4) twelve (12)-month option periods.

1.3 PLACES OF PERFORMANCE

The Contractor shall provide support within the Continental United States (CONUS) at the Contractor’s facility and at various Outside of the Contiguous United States (OCONUS) locations. The Contractor shall have the facilities (i.e., office space, laboratory space, staging and storage areas) necessary to accomplish Contract/Task Order objectives. Travel will be required to various locations to service/update equipment. Table 1 below provides the anticipated Combatant Command (COCOM) locations.

Table 1: Places of Performance

2.0 APPLICABLE DOCUMENTS

The Contractor shall provide BCF2 services in accordance with the following regulations, directives, guidance, and documents. Where a policy is revised or updated, the most current version of the policy, directive, or document will apply.

DoD, Army, and Federal References:

· AR 25-1, Army Information Technology

· AR 25-2, Information Assurance

· AR 350-1, Army Training and Leader Development

· AR 380-5, Department of the Army Information Security Program

· AR 381-12, Threat Awareness and Reporting Program (TARP)

· AR 700-142, Type Classification, Materiel Release, Fielding, and Transfer

· AR 710-1, Centralized Inventory Management of the Army Supply System

· AR 710-2, Supply Policy Below the National Level

· AR 735-5, Property Accountability Policies

· DISA Security Technical Implementation Guides (STIGs)

· DoD Cloud Computing Security Requirements Guide (CC SRG) version 1, release 3,

· DoD Product Support Manager Guidebook

· DoDD 8570.01, Information Assurance (IA) Training, Certification, and Workforce Management

· DoDI 3020.41, Operational Contract Support (OCS)

· DoDI 5200.48, Controlled Unclassified Information (CUI)

· DoDI 8500.01, Cybersecurity

· DoDI 8510.01, Risk Management Framework RMF for DoD Information Technology

· DoDI 8530, Cybersecurity Activities Support to DoD Information Network Operations

· DoDM 8140.03, Cyberspace Workforce Qualification & Management Program

· Federal Information Processing Standard (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems

· National Institute of Standards and Technology (NIST) Special Publications (800 Series)

· MIL-STD-130N Change 1 dtd 16 NOV 2012, DoD Standard Practice Identification Marking of U.S. Military Property

· MIL-HBDK-61B, Configuration Management Guidance

· National Industrial Security Program Operating Manual (NISPOM)

3.0 PERFORMANCE REQUIREMENTS

The Contractor shall provide qualified personnel, supervision, and other items and services necessary to perform the non-personal services described in this PWS. The Contractor shall perform the following tasks:

· Task 1: Program Management

· Task 2: System Procurement and Fielding

· Task 3: System Sustainment

· Task 4: Software Engineering Services

· Task 5: Cloud Services

· Task 6: Help Desk Services

· Task 7: Cybersecurity Services

· Task 8: Surge Support

3.1 Task 1: Program Management

The Contractor shall provide qualified personnel, administrative, and financial resources necessary to successfully execute the requirements of this PWS. The Contractor shall provide a single point of contact through which tasks/requests from the Government are accepted and contractor performance is managed. The Contractor shall ensure all activities and deliverables are identified, documented, and tracked so that the Contractor’s performance can be continuously evaluated and monitored for timeliness and quality of services and deliverables (CDRL A001). The Contractor shall apprise the Contracting Officer Representative (COR) of any performance, staffing, or other PWS related issues.

The Contractor shall plan, estimate, budget, and manage costs in accordance with the Contractor’s proposed costs for each year of the base contract and subsequent awarded Task Orders. The Contractor shall deliver a monthly Cost Report with a comprehensive breakdown of costs (CDRL A001). The Contractor will be evaluated on their ability to control costs for each year. Any cost overrun above the Contractor’s proposed costs may result in a negative Contractor Performance Assessment Reporting System (CPARS) rating under “Cost Control”.

3.1.1 Post Award Conference

The Contractor shall coordinate and hold a contract Post Award Conference (PAC) within 15 calendar days of contract award. The Contractor shall present a briefing outlining their approach to meeting the contract requirements, the associated contractor organization, staffing, and execution of the Contractor’s proposed Transition-In Plan (CDRL A002). In addition, the post-award meeting shall include all corporate and working-level points of contact (POC).

3.1.2 Task Order Award Kick-Off

The Contractor shall coordinate and hold Task Order Kick-Off Meeting(s) no later than (NLT) seven (7) calendar days after each Task Order award to establish milestones and POCs. The Contractor shall schedule, coordinate with the COR and provide an agenda/briefing for the Kick-Off Meeting(s) (CDRL A002). The meeting(s) will provide the opportunity to discuss technical, management, security issues, travel authorization, and reporting procedures. At a minimum, the attendees shall include vital Contractor personnel and representatives from the Government.

3.1.2.1 The Contractor shall deliver a Task Order Status Report (TOSR) (CDRL A003) that includes all data collection, analysis, and reporting efforts. The TOSR shall contain at a minimum information on system functionality, known issues, resolutions, resolution actions, interfaces, and interoperability.

3.1.2.2 With each Task Order award, the Contractor shall deliver an Integrated Master Schedule (IMS) (CDRL A004).

3.1.3 Transition Planning

3.1.3.1 Transition-In Planning

The Contractor shall ensure a complete and successful transition not later than 45 calendar days after Task Order award(s). The Contractor shall execute all activities and milestones for the transition period by the timelines specified for meeting those milestones in its proposed Transition-In Plan. The Contractor shall provide their final proposed Transition-In Plan to PM Biometrics within five (5) days after contract award.

3.1.3.2 Transition-Out Planning

The Contractor shall perform services in accordance with the contract without reduction of manpower, quality of services, or interruption to customers. The Contractor shall prepare a Transition-Out Plan (CDRL A005), including all steps to handover responsibility and knowledge transfer to the follow-on Contractor, if applicable. The Transition-Out Plan shall address how the Contractor will implement adequate measures to coordinate communications with the follow-on contractor and their staff to ensure uninterrupted workflow and minimal mission impact during the transition process. The Contractor’s Transition-Out Plan shall include a comprehensive plan for the transfer of work control, addressing all security issues, the transfer and accountability of Government Furnished Property (GFP) (to include inspect and acceptance); transfer of training materials (e.g., job aids, operational procedures, knowledge documentation repository), job shadowing, observation/reverse shadowing; monitoring of current operations, delineating the method for processing and assigning tasks; and plan for demobilizing all OCONUS personnel.

3.1.4 Configuration Management

The Contractor shall develop a Configuration Management Plan (CMP) (CDRL A006) IAW industry configuration management standards and DoD standards, directives, and guidance. The CM Plan includes, but is not limited to, the Contractor supporting all change management, identifying, documenting, and verifying functional, performance, and physical characteristics of systems; tracking configurations of systems and platforms including equipment obsolescence; maintaining all hardware and software baselines and preparing configuration baseline documentation.

3.1.4.1 Configuration Management Processes and Procedures

a) The Contractor shall document the strategy in the CMP to establish and maintain hardware and software configuration management for all system environments; identify, track and control developmental and operational baselines; engineering work products and define and execute a program change management process.

b) The Contractor shall document software release processes in the CMP for sustainment and system engineering activities.

c) The Contractor shall execute release management procedures for all systems in accordance with the CMP.

d) The Contractor shall refine, document, and maintain the currency of its release management processes and procedures in the CMP.

e) The Contractor shall post all release documentation to the CM repository.

f) The Contractor shall provide administrative and technical support to weekly and off-schedule PM Biometrics-led change management forums (e.g., Configuration Control Board (CCB), Technical Review Board (TRB)).

g) The Contractor shall document, maintain and update changes to hardware and software in the Version Description Documents (VDDs) (CDRL A026).

h) The Contractor shall disseminate system change documentation among the members of the CCB and TRB.

i) The Contractor shall provide technical subject matter experts to assist the Government review of baseline documentation during System Verification Reviews (SVR) / Functional Configuration Audits (FCA) and Physical Configuration Audits (PCA). SVR/FCA and PCA will be conducted by the Government prior to major deployments or as required. SVR/FCA is conducted to verify the system performance meets the requirements in the functional specifications and is documented in the functional and allocated baselines. PCA is conducted to verify the systems as-built configuration against the technical documentation to verify the product baseline.

3.1.4.2 Configuration Management (CM) Repository

The Contractor shall implement and maintain a web-based Configuration Management (CM) system using MIL-HDBK-61A (System Engineering) as a guide; however, the CM repository must reside on Government servers and be remotely accessible by the Government. The CM system is intended to provide a collaborative CM environment for the Government and the Contractor and a historical repository of Engineering Change Proposals (ECPs). The Contractor shall notify the COR of all licenses required to operate the system and track software baselines to include licenses / license keys, proof of purchase and maintenance agreements / End User License Agreement (EULA) / Terms & Conditions (T&C).

The proposed CM Repository system shall be capable of performing the following:

a) Encompass all systems and versions baselines;

b) Identify the state of development efforts in addressing change requests, system issues, maintenance, management of environments, and release content;

c) Document all system baseline changes, problems and upgrades;

d) Maintain software licenses;

e) Employ automated processes to load and update the repository to reduce errors and cost; and

f) Leverage discovery tools, inventory and audit tools to maintain, enforce, and report near–real–time system configuration.

3.1.4.3 Configuration Items Control

a) The Contractor shall exercise control of the HW and SW Configuration Items ensuring that only authorized and identifiable Configuration Items are accepted and recorded from receipt to disposal under PM Biometrics direction. The Contractor shall add, modify, replace, and remove Configuration Items only through the processing of appropriate controlling documentation in accordance with the CMP.

b) The Contractor shall monitor all systems, capturing all current and historical lifecycle subsystems data, including tracking of subsystems status (ordered, received, under test, live, under repair, withdrawn or for disposal).

c) The Contractor shall conduct automated discovery and configuration audits of the Configuration Items monthly to ensure approved, standard patches, updates, and configurations are maintained within all systems and report any discrepancies to the Government.

3.2 Task 2: System Procurement and Fielding

The Contractor shall procure and field COTS/GOTS software and hardware in support of PM Biometrics’ collection capability missions.

3.2.1 System Procurement

The Contractor shall procure COTS/GOTS hardware and software including embedded software, software licenses, maintenance agreements, or any combination of these items. Final COR approval shall be obtained prior to the Contractor procuring equipment. The Contractor shall provide all records, to include invoices, receipts, license key notifications and proofs of purchase in association with the procured item(s).

The Contractor shall procure COTS hardware and software through the Army’s designated primary source for commercial IT, Army’s Computer Hardware, Enterprise Software and Solutions (CHESS) IT e-Mart. A statement of Non-availability (SoNA) is required if any HW or SW purchases are made outside of CHESS and the Contractor shall obtain an Information Technology Approval System (ITAS) waiver.

3.2.1.1 The Contractor shall execute Item Unique Identification (IUID) marking requirements for all operational equipment under this IDIQ (CDRL A007). The Contractor shall capture and enter all IUID required items into the IUID registry prior to shipment. The item marking criteria for development of specific marking requirements and methods for identification of items of military property produced, stocked, stored, and issued by or for the DoD is outlined by MIL-STD-130N Change 1 dtd 16 NOV 2012, DoD Standard Practice Identification Marking of U.S. Military Property. This standard addresses criteria and data content for both free text and machine-readable information (MRI) applications of item identification marking.

The required marking shall be applied to an identification plate, identification band, identification tag, or identification label securely fastened to the item, or shall be applied directly to the surface of the item and be compliant with the standards of location, size, content, permanency, legibility, deleterious effect and type of lettering. Marking materials that create a hazardous condition shall not be used.

3.2.1.2 All items (hardware and software) shall be kitted in accordance with the associated technical documentation (i.e., TDPs, drawings, Specification Sheets, etc.). All hardware associated with each kit shall be inventoried and documented using the as built inventory sheet (list of all serialized components) and placed in the kit along with the DD Form 250 prior to shipping. Any purchases shall be approved by the COR prior to purchase.

3.2.1.3 The Contractor shall certify that it purchases supplies from authorized resellers and/or distributers. The Contractor shall warrant that the products are new and in their original box. The Contractor shall procure products from authentic manufacturers or through legal distribution channels only, in accordance with all applicable laws and policies in effect at the time of purchase. The Contractor shall provide the Government with a copy of the EULA warranting that all manufacturer software is licensed to the Government as the original licensee authorized to use the software. The Contractor shall track and report all licensing information (CDRL A008).

3.2.1.4 The Contractor shall not release any equipment without proper authorization from the COR. The Contractor shall ensure security and 100% property accountability of equipment. The Contractor shall enter and track all equipment in the Defense Property Accountability System (DPAS) upon receipt of signed DD Form 250(s).

3.2.2 System Fielding

The Contractor shall provide system fielding services consistent with Total Package Fielding (TPF) IAW AR 700-142 Chapter 5. TPF is the Army’s standard materiel fielding process designed to provide Army materiel systems to the gaining units as a coordinated package of end items, support items, spares, and technical documentation. Materiel Fielding Services consists of New Equipment Fielding (NEF), New Equipment Training (NET), Platform Integration (PI), and Technical Field Support.

3.2.2.1 The Contractor shall serve as TPF Leads for fielding missions whose responsibilities include being the single point of contact between the gaining unit and the Product Office, as well as coordinating all logistic needs for the NET and PI teams. The Contractor shall conduct NEF in support of BFC2 systems in both CONUS and OCONUS locations and may be required in contingency theaters of operation.

3.2.2.2 The Contractor shall conduct NET as part of Materiel Fielding Services IAW AR 350-1 Chapter 6. NET provides the initial transfer of knowledge on the operation and maintenance of new equipment from the Government to the end user and field maintainer. NET assists Commanders with achieving operational capability in the shortest time practical by training soldiers how to operate and maintain the new equipment. The Contractor shall conduct NET in support of systems in both CONUS and OCONUS locations per the Government provided NET Plan.

3.3 Task 3: System Sustainment

The Contractor shall provide sustainment services for BFC2 systems in support of current military operations worldwide. This support includes ongoing and routine operational and field support, training support, product support, and shipping support. This support includes BFC2 equipment shared with allies and coalition partners.

3.3.1 Operational and Field Support

The Contractor shall provide continuous and routine operational and field level maintenance support. Such support shall include short or long-term deployment of personnel for at least one (1) year who work and live in hazardous areas in or near military combat zones as well as other OCONUS COCOMs referenced in Section 1.3, Places of Performance. For all contractor personnel hired for specified deployment locations, the Contractor shall schedule mandated CONUS Replacement Center (CRC) (or equivalent) attendance.

3.3.1.1 The Contractor shall provide Coordination, planning, and management oversight of the BFC2 systems field service support. The Contractor shall ensure that planning and resources allow for backfill of personnel who are on-leave or rotating out of their country of assignment, and for support of special missions.

3.3.1.2 The Contractor shall provide Database Administration (DBA) support for BFC2 systems to include database maintenance, tracking and monitoring of data flow, establishment and coordination of the replication schema, and server software upgrades. The Contractor shall perform daily tasks to include monitoring the replication schema, monitoring and optimizing network performance, providing network metrics, developing and implementing database monitoring tools, and serving as the resident database expert for system users.

3.3.1.3 The Contractor shall provide Multifunctional Field Technical Support (MFTS). The Contractor shall provide day-to-day maintenance and repair of tactical biometrics and forensics collection devices and peripherals. This includes preventative, controlled, emergency, and corrective maintenance.

a) MFTS shall provide system administration, troubleshooting, and configuration support for communications platforms, and networks. Support shall include field level maintenance, comprehensive and responsive network support services, database administration, security administration, and configuration management.

b) MFTS shall:

· Schedule, perform, document, and review system maintenance records

· Sanitize equipment prior to offsite maintenance

· Checks security controls following maintenance

· Ensure that personnel performing maintenance on the information system have required access authorizations

· Maintain a list of authorized maintenance personnel including third-party maintenance providers

· Inspect all maintenance tools brought into a facility by maintenance personnel for obvious improper modifications

· Check all diagnostic and test program media for malicious code before use

c) MFTS shall coordinate with vendors to install and configure software and hardware; monitor system performance; and provide recommendations for improvements to network/configuration security and efficiency.

d) MFTS shall respond to routine warfighter requests for support within 48 hours and to emergency inquiries within eight (8) hours as per the MFTS routine operating environment. These response times may vary depending on intra-theater transportation availability.

e) MFTS shall conduct Tier One (1) support and user training at the operator tier on BFC2 systems. MFTS shall coordinate with vendors for support above Tier One (1).

3.3.1.4 The Contractor shall ensure that their employees deploying to theater are supplied with the necessary equipment, such as workstations or tool/test kits to perform their duties.

3.3.1.5 The Contractor shall provide timely notification to direct support organizations regarding the operability and serviceability of assigned facilities and assets. IAW AR 710-1, AR 710-2, and AR 735-5, the Contractor shall maintain configuration management of all BFC2 systems’ hardware, software, and equipment and abide by all provisions outlined in Section 7.0, Government Furnished Property of this PWS.

3.3.2 Training Support

The Contractor shall provide Training support for BFC2 systems in operational use. Training shall be geared to cover all the tasks and associated skills required to execute the specific biometrics or forensics collections mission.

3.3.2.1 The Contractor shall develop targeted training materials for specific missions.

3.3.2.2 The Contractor shall accompany units on actual missions as required to ensure that personnel are satisfactorily trained to execute their system related tasks to standard in a live environment.

3.3.2.3 The Contractor shall provide training team support at Combat Training Centers (CTCs) during scheduled exercises. Support shall include, but is not limited to, training the staffs of rotating units regarding the technical and network support that is required in theater; providing field support to units during the exercise; provide lessons learned input for training material development as required; provide support to the CTC operations group staff section, as determined by the CTC leadership, in the development of scenarios incorporating and managing the use of biometrics and forensics data during rotation training.

3.3.2.4 The Contractor shall coordinate with the Directorate of Doctrine and Intelligence Systems Training (DDIST) team to provide the necessary new equipment training to support technical refreshes.

3.3.3 Product Support

Product Support spans the total scope and all aspects of life cycle sustainment. The Contractor shall provide product support guided by the 12 Integrated Product Support Elements in accordance with the DoD Product Support Manager Guidebook. Where it is in the best interest of the Government, the Contractor shall evaluate the use of public private partnerships with DoD agencies in support BFC2 systems.

3.3.3.1 The Contractor shall develop and implement an Integrated Logistics Support Plan (ILSP) (CDRL A024) to ensure supportability is considered throughout the system life cycle through the optimization of the key performance outcomes of reliability, availability, maintainability, and reduction of total ownership costs. Where applicable, the Contractor shall develop a Diminishing Manufacturing Sources and Material Shortages (DMSMS) Implementation Plan (CDRL A009). The DMSMS Implementation Plan will be used to assess how the Contractor plans to implement the requirements of the program’s DMSMS Plan for identifying and managing the loss, or impending loss, of manufacturers or suppliers of parts and/or material required for sustained operational availability of the program’s systems.

3.3.3.2 The Contractor shall develop required design changes and implement technical refreshes of the systems. These shall be documented via an ECP and annotated within the Configuration Management Plan (CDRL A006).

3.3.3.3 The Contractor shall establish procedures to support counterfeit prevention, detection, and reporting for BFC2 components and equipment (CDRL A010). These procedures include item verification, reporting timelines, and notification/reporting processes. Note: CHESS procurements do not require counterfeit prevention procedures as vendors were pre-vetted.

3.3.3.4 The Contractor shall track the levels of system spares and repair parts (CDRL A021) and ensure all classes of supplies meet a Supply Availability rate as directed by the Government. The Contractor shall be responsible for tracking and shipping of all equipment to original equipment manufacturer (OEM) repair facilities in accordance with the purchased warranty.

3.3.3.5 The Contractor shall provide maintenance planning and management. Maintenance planning and management is the development process that defines the repair and upkeep tasks, schedule, and resources required to care for and sustain BFC2 systems with the focus being to define the actions and support necessary to attain the system’s Operational Availability (Ao) objective. The Contractor shall report the status of system(s)’ Ao in the monthly TOSR (CDRL A003).

3.3.3.6 The Contractor shall identify facility needs in support of BFC2 systems. The Contractor shall ensure the optimal temperature is maintained in the facilities for the system(s) to transmit data within the allotted time. The Contractor shall maintain maintenance facilities/warehousing in support of the systems network equipment. Regardless of type of facility, the Contractor shall maintain a safe work environment and require all personnel to always wear appropriate protective equipment.

3.3.4 Packaging, Handling, Storage, and Transportation

The Government will provide a FedEx account and will bear all shipping costs, unless otherwise directed. The COR may specify or provide special packaging for select systems; all packaging materials not provided by the COR shall be charged to the Task Order.

3.3.4.1 The Contractor shall coordinate and execute the movement of items between the field support locations and OEM and Depot locations or other locations identified by the COR. This shall entail determining the most economical method of shipping within the constraints of DoD transport system and turn-around-times.

3.3.4.2 The Contractor shall ensure all customs documentation, declarations, verification necessary for these shipments are properly completed and submitted. The Contractor shall track shipments, receipts, and returns as applicable. The Contractor shall provide up-to-date status of all shipping / transportation actions to and from its facilities (CDRL A011).

3.3.4.3 The Contractor shall ensure all Contractor and subcontractor/vendor personnel understand the content of the applicable Security Classification Guide (SCG). The Contractor shall ensure that all personnel properly mark, store, handle, and ship all material they acquire, generate or create in accordance with AR 380-5, and the applicable SCG. The Contractor shall ensure all packaging is properly marked, and that all security classification guidance for marking and handling is followed.

3.3.4.4 The Contractor shall assist the Government as needed to demilitarize and dispose of assets no longer required. The Contractor shall track excess equipment and coordinate with the Government to determine equipment for DEMIL.

3.4 Task 4: Software Engineering Services [NRTIO, NXGBCC, CIHEP-A, DMAR]

The Contractor shall provide software engineering services for BFC2 systems including software development and maintaining existing software engineering environment(s) for enhancements, upgrades, modifications, and software maintenance and fixes.

3.4.1 The Contractor shall perform assessments/investigations resulting from reported problems or incidents, user requests, or changes to applicable biometric/forensics standards, processes and technologies, to determine whether event(s) results in an ECP.

3.4.1.1 The Contractor shall:

a. Resolve approved System software problems or changes.

b. Resolve approved System integration or interoperability problems with existing COTS or GOTS hardware and software products as documented.

c. Ensure all System deployments are fully interoperable with all other standards compliant systems.

d. Ensure Systems are upgraded as required to meet applicable biometric/forensics standards and Information Assurance (IA) findings.

e. Ensure Systems are compatible with the DoD Biometric Enterprise Information Technology infrastructure, and comply with DoD, Army and Local Command policies, processes, regulations, and certifications.

f. Deliver maintenance releases to fix approved problems and implement approved system changes as required.

3.4.2 The Contractor shall produce a Software Development Plan (SDP) (CDRL A012) for COR approval and execute to the SDP. The Contractor shall resolve all software issues approved by the Government via the CCB, using the processes defined in the SDP and CMP.

3.4.3 The Contractor shall develop, implement, and deliver Test Procedures (CDRL A013) to verify the new requirements and support regression testing to ensure original functionality has not been impacted.

3.4.3.1 The Contractor shall prepare and maintain a cross-reference of all requirements to the verification procedures that shall be used to determine successful compliance. The Contractor shall include the COR in the verification of the system, by conducting, and/or participating in software test phases and providing Test Reports (CDRL A014). The Contractor shall provide the COR the opportunity to witness all testing.

3.4.4 The Contactor shall produce and maintain Software Sustainability Packages (SSP) for applicable BFC2 systems (CDRL A015). The Contractor shall provide the means to construct a system image for biometric collection devices. The complete Configuration baseline is provided via the SSP and TDP. This shall include the following:

a. Identification of COTS application including version (for example, Windows 10 Enterprise with SPx, Microsoft Office 20xx with SPx).

b. Installation package which includes:

· Installer

· Drivers/libraries

· Executable code of developed applications

c. Determine and document through updating of the Version Description Document (VDD), any special installation/configuration requirements.

3.5 Task 5: Cloud Services [NRTIO, NXGBCC, CIHEP-A, DMAR]

3.5.1 The Contractor shall develop and sustain cloud infrastructure in accordance with the Enterprise Cloud Management Agency (ECMA) or Army Military Intelligence Cloud Computing Service Provider (AC2SP) processes. Prior to initiating the ECMA or AC2SP process, the Contractor shall present Cloud requirements, architecture, and design that identifies the most effective approach to implement/migrate the application to the cloud. Upon Government approval, the Contractor shall engage ECMA or AC2SP to complete the Cloud process.

3.5.2 The Contractor shall physically maintain all Cloud data solely on equipment located within the legal jurisdiction of the United States IAW DFARS 239.7602-2(b). All data, including but not limited to documents, administrative data, support data, and billing data, transmitted via the system or maintained in the system shall reside at all times in data processing and storage equipment located in the United States or in data processing and storage equipment of which the operation and maintenance are subject only to the laws of the United States. Cloud data transmitted must only be subject to disclosure pursuant to U.S. Federal law and not the laws of any other jurisdiction or foreign nation. All DoD information/data placed or created by DoD users in a Cloud Service Provider’s (CSP) Cloud Service Offering (CSO) is owned by the DoD, the Mission Owner, and/or their Information Owner. The CSP has no rights to the DoD’s information/data. For more information on data storage, data rights, and data ownership requirements refer to Section 5.2, Legal Considerations, in the DoD Cloud Computing Security Reference Guide (SRG) v1r3.

The Government will retain unlimited rights to all development and automation performed and all data, Infrastructure-as-Code (IaC) or Configuration as Code (CaC) or processes created under this Contract. This would not include code, processes, or automation that the Army might subscribe to that are commercially available under Commercial Use Rights and/or Government Purpose Rights.

The Government will retain unlimited rights of all user data/information/knowledge provided to, created/developed in, loaded/transitioned to, or hosted in/by the Contractor, CSP, tenant, multiple CSP, multiple tenant, CSO, vendor IT infrastructure, hosting environment, system(s).