IBS PWS-11.20.26.pdf

PDF 1 MB Posted

Attached to
Integrated Biometrics System/Facial Recognition
Solicitation number
101926A0595
Issued by

About this file

This is a Performance Work Statement (PWS) for the Integrated Biometric System (IBS) procurement by the U.S. Department of State, Bureau of Diplomatic Technology, issued in November 2026.

The PWS defines requirements for licensing, maintenance, operational support, and sustainment of the Department of State's facial recognition (FR) system and associated software components over a 12-month base period with four 12-month option periods (04/01/2027 through 03/31/2032). The contractor must maintain Multi-Biometric Search Services (MBSS) 7.7 or higher and proprietary IDEMIA software including Quality Over the Web (QotW) and Quality Assessment (QA) SDK 6.3 or higher, as the sole source justification cites CEAC's legacy dependencies on these tools until transition to the Consular System Modernization platform. The contract is Firm Fixed Price for services with cost-reimbursable travel not-to-exceed amounts per FAR 31.205-46. Performance shall occur primarily within the National Capital Region or 50-mile radius from State Annex 17, with authorized work at specified government locations (SA-9, SA-17, and Alexandria, VA facility). Core business hours are 7:00 a.m. to 6:00 p.m. EST, Monday through Friday.

The four task areas include: (1) FR Software and Licenses providing enterprise licensing for identification, verification, and enrollment supporting exponential capacity scaling; (2) FR System Installation, Maintenance and Support Services including system installation at two geographically distinct data centers, operational monitoring, preventive maintenance, metrics collection and reporting, emergency support, re-enrollment capabilities, training, and technology refresh; (3) FR System Integration Services encompassing image review software development, image repository management, API-based interface evolution, and system integration planning; and (4) Program and Project Management requiring a Program Management Plan, weekly activity reports, monthly Contract Status Reports, monthly Project Status Reports, Quality Control Plan, Standard Operating Procedures, and transition-in/transition-out plans. Security requirements include SECRET facility and personnel clearances, HSPD-12 credentials, compliance with FISMA and NIST standards, Plan of Action and Milestones maintenance, cybersecurity protocols, information security planning, and disaster recovery contingency planning. Key personnel must include a Program Manager with 10 years experience and PMP certification, Project Manager with Agile Product Owner certification and 5 years biometric/FR experience, Lead Software Developer, and Lead Systems Architect, all with specified education and experience requirements. The contractor must maintain certifications including CMMI Level 3, ISO/IEC 27001:2022, and ISO 9001:2015 throughout contract performance and comply with all applicable DOS policies, enterprise architecture standards, and federal regulations.

View the file

Other files

File Type Posted
IBS SSN-11.20.26.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

United States Department of State Bureau of Diplomatic Technology, Washington, DC 20520

U.S. Department of State

Bureau of Diplomatic Technology

Integrated Biometric System (IBS) Performance Work Statement (PWS)

November 2026

SBU - CONTRACTING AND ACQUISITIONS 2

TABLE OF CONTENTS

I INTRODUCTION

1 SCOPE

2 OBJECTIVES

3 BACKGROUND

II TASK AREAS

1 SPECIFIC TASKS OR REQUIREMENTS

1.1 Task Area 1: FR SOFTWARE AND LICENSES

1.2 Task Area 2: FR SYSTEM INSTALLATION, MAINTENANCE AND

SUPPORT SERVICES

1.3 Task Area 3: FR SYSTEM INTEGRATION SERVICES

1.4 Task Area 4: PROGRAM and PROJECT MANAGEMENT

1.5 SECURITY REQUIREMENTS

1.5.1 Plan of Action and Milestones (POA&M)

1.5.2 Security Operations Guides

1.5.3 Cybersecurity

1.5.4 Information Technology Security Plan

1.5.5 Disaster Recovery and Contingency Planning

1.5.5.1 Plan Development and Maintenance

1.5.5.2 Testing, Updates, and Coordination

1.5.5.3 Technical Support and Implementation

1.5.6 DELIVERABLES & SCHEDULE

III GENERAL REQUIREMENTS

1 STATUTORY, REGULATORY, AND POLICY REQUIREMENTS

2 TYPE OF CONTRACT

3 PERIOD OF PERFORMANCE

4 PLACE(S) OF PERFORMANCE

5 DAYS AND HOURS OF PERFORMANCE

6 KICKOFF MEETING

7 TRAVEL

8 IDENTIFICATION OF CONTRACTOR EMPLOYEES

9 NON-DISCLOSURE AND CONFIDENTIALITY

10 PROPRIETARY INFORMATION

SBU - CONTRACTING AND ACQUISITIONS 3

11 HOMELAND SECURITY PRESIDENTIAL DIRECTIVE 12 (HSPD-12)

CREDENTIALS………………………………………………………………………46

12 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

12.1 Information Technology Systems Requirements

12.2 Access Requirements

12.3 Information Assurance

13 ONBOARDING PROCESS

14 GOVERNMENT-FURNISHED PROPERTY, EQUIPMENT, AND/OR

INFORMATION

15 CONTRACTOR PERSONNEL STAFFING ASSIGNMENT

15.1 Key Personnel

15.1.1 Program Manager

15.1.2 Project Manager

15.1.3 Lead Software Developer

15.1.4 Lead Systems Architect

15.1.5 Other-Than Key Personnel Qualifications

16 ORGANIZATIONAL CONFLICT OF INTEREST (OCI)

17 DATA RIGHTS

18 ORDER OF PRECEDENCE

19 SERVICE CONTRACT LABOR STANDARDS (SCLS) APPLICABILITY

20 INVOICING AND PAYMENT

21 QUALITY ASSURANCE

22 CONSTRAINTS AND ASSUMPTIONS

IV ATTACHMENTS

SBU - CONTRACTING AND ACQUISITIONS 4

I INTRODUCTION

The purpose of this Performance Work Statement (PWS) is to define the requirements for the procurement, licensing, maintenance, and support of facial recognition software capabilities to support identity verification, identity assurance, fraud prevention, and adjudication support operations. The COTS (Commercial Off-The-Shelf) solution shall provide secure, scalable, and high performing facial recognition capabilities that integrate with existing enterprise systems and workflows while supporting operational efficiency, mission effectiveness, and evolving security requirements.

The Contractor shall provide commercial facial recognition software licenses, associated technical support, maintenance, updates, and related services necessary to enable facial comparison, identity matching, and image analysis functions across designated operational environments. The solution shall support high-volume processing, interoperability with existing infrastructure, compliance with Federal Information Security Management Act (FISMA), National Institute of Standards and Technology (NIST) standards, and applicable federal privacy requirements, and shall support configurable operational thresholds and workflows.

1 SCOPE

This PWS covers the licensing, maintenance, operational support, and sustainment of the Department of State's (DOS) facial recognition system and associated software components. The Contractor shall maintain Multi-Biometric Search Services (MBSS) 7.7 or higher, the current CST-approved software baseline, which the Government is implementing for full domestic deployment within a redundant architecture designed to ensure continuous service availability.

The Contractor shall also maintain the following mission-critical software tools that the Department of State currently uses:

• Quality Over the Web (QotW)

• Quality Assessment (QA) Software Development Kit (SDK) 6.3 or higher

• Re-enrollment software for failed-to-enroll images

The Consular Electronic Application Center (CEAC) depends on IDEMIA's proprietary QotW and QA SDK software. The Government plans to replace the CEAC application with the Consular System Modernization (CSM) platform; however, this transition is currently on hold due to upcoming Online Passport Renewal (OPR) modernization upgrades. Because no other contractor can license IDEMIA's proprietary QotW and QA SDK, CEAC's legacy dependencies on these tools must remain in place until CA transitions to CSM. This proprietary dependency constitutes the primary justification for sole source award to IDEMIA or an authorized IDEMIA reseller.

The Contractor shall provide periodic technology refreshes and capability upgrades on an annual basis, or as otherwise directed by the Government, throughout the contract period to enhance performance and mitigate security vulnerabilities. The Contractor shall also provide all required software licenses, technical support, maintenance services, patches, updates, and operational

Santhumayor, Ashrita Rewrote this language- need review

SBU - CONTRACTING AND ACQUISITIONS 5

assistance necessary to maintain uninterrupted availability and functionality of the facial recognition environment housing millions of facial images.

The Contractor shall support the existing operational architecture, interfaces, workflows, and configurations deployed by the DOS. In addition to sustaining current operations, the Contractor shall provide technical support and assistance for authorized government applications or systems that may require access to or utilization of the existing facial recognition software capability during the period of performance. The government shall authorize all new system integrations. Support may include onboarding assistance, interface configuration support, operational guidance, account provisioning, Application Programming Interface (API) service enablement, troubleshooting, and coordination activities necessary to facilitate approved use of the existing capability by additional government systems or programs.

The Contractor shall ensure that all support activities maintain compatibility with applicable government security, privacy, and operational requirements.

The areas of work to be performed are as follows:

Task Area 1 – Facial Recognition (FR) Software and Licenses Task Area 2 – FR System Installation and Support Services Task Area 3 – FR System Integration Services Task Area 4 – Program and Product Management

2 OBJECTIVES

The primary objective of this effort is to ensure the continued availability, reliability, and operational support of the Government’s existing facial recognition capability through the provision of software licenses, maintenance, and technical support services.

Specific objectives include:

a. Maintain operational continuity: Ensure uninterrupted operation and sustainment of the existing facial recognition environment in support of ongoing government mission and adjudication activities.

b. Provide software licensing and maintenance: Maintain valid software licensing, vendor support software updates, security patches, and defect remediation necessary to support the current operational environment.

c. Support existing system functionality: Preserve and support the current facial recognition capabilities, interfaces, workflows, configurations, and service integrations without requiring redesign or modernization activities.

d. Enable enterprise service utilization: Provide technical and operational support necessary to allow authorized government applications and systems to utilize the existing facial recognition capability as approved by the government

e. Ensure system stability and performance: Support reliable system performance, operational availability, and issue resolution to minimize service disruptions and maintain mission effectiveness

SBU - CONTRACTING AND ACQUISITIONS 6

f. Support security and compliance requirements: Ensure all support activities are performed in accordance with applicable government security, privacy, and operational policies, standards, and procedures

g. Provide technical assistance and troubleshooting: Deliver responsive Technical Support incident resolution and operational guidance for government stakeholders utilizing the existing facial recognition capability

h. Maintain compatibility with existing infrastructure: Ensure continued interoperability and compatibility with the government's current infrastructure, connected applications and operational environment throughout the period of performance

i. Support integration of new government applications: Provide technical support and coordination necessary to enable authorized new or enhanced government applications, systems, or workflows to connect to and utilize the existing facial recognition capability.

Support activities may include interface configuration, service enablement, connectivity support, API integration assistance, testing coordination, troubleshooting, and operational guidance required to facilitate successful integration with the existing facial recognition environment. Such integration support shall not require redesigning the core facial recognition system.

The Government may also require optional services:

Enhancements (Optional): The contractor shall provide enhancement services that improve the functionality, performance and usability of existing Department of State (DOS) systems and applications to meet current operational needs. Enhancement services may include:

1. Adding or changing features and functions in existing applications.

2. Improving system performance, efficiency and reliability.

3. Upgrading existing algorithms, business logic and workflows.

4. Improving user interfaces and the user experience.

5. Expanding the reporting, data and integration capabilities of existing systems.

6. Updating system configurations to meet changed business requirements.

Enhancement services do not include acquiring or developing new technologies, incubating new products, or modernizing or migrating infrastructure or applications. The Government shall issue task orders that define the scope, deliverables and acceptance criteria for each enhancement activity.

Example Enhancement: Morph Attack Detection (MAD) The following example shows the type of enhancement the Government may request under this section.

MAD API Access: The contractor shall provide access to Morph Attack Detection (MAD) features through an Application Programming Interface (API), based on mission needs as the Government determines them. The contractor provides MAD to DOS as part of its technology refresh offerings.

The API shall let the Government use MAD on demand in its product development work and integrate morph attack detection into existing fraud

Cambi, Blanca J @Santhumayor, Ashrita/@Virgin, George C - Please review this section. As per the CO, within a Sole Source-PWS contract, “modernization” can be included, however “enhancements” that are part of the product itself can be provided to the government. Such as morph detection that is currently within MBSS 7.7.

Virgin, George C Hi Blanca, all references to modernization were removed, and now the section only applies to enhancements. This seems to conform with the preferred re-award format. I can't think of additional changes to this section.

SBU - CONTRACTING AND ACQUISITIONS 7

prevention workflows and applications.

Implementation Support: The contractor shall provide the customization and integration support needed to implement MAD, including:

1. API access and complete technical documentation.

2. Integration assistance and technical support.

3. Customization services that adapt MAD to DOS workflows.

4. Coordination of testing and troubleshooting.

5. Performance tuning and optimization.

6. Training on API use and integration best practices.

Government Responsibilities: The Government will retain responsibility for the following activities related to the MAD API implementation:

1. Concept of Operations (CONOPS) development.

2. Workflow integration design.

3. User interface design.

4. Threshold configuration.

5. Evaluation protocols.

6. Analytics.

Contractor Support to Government-Led Activities: At the Government's request, the contractor shall provide technical consultation, API configuration support and integration guidance for the activities listed under Government Responsibilities.

3 BACKGROUND

The U.S Department of State (DoS or State Department) / Bureau of Diplomatic Technology (DT) empowers the DoS to achieve its foreign policy mission by providing modern, secure, and resilient information technology and services. DT’s foremost objective is to foster innovative, effective, and interconnected diplomacy by constantly improving, modernizing, and refreshing its tools and services.

The Office of Consular Systems and Technology (CST) within DT delivers secure, reliable, and accessible technology solutions for consular services that enable the Department of State to safeguard our borders, facilitate legitimate travel, and protect U.S. citizens. CST supports the Bureau of Consular Affairs (CA), which issues visas to foreign nationals and passports to U.S.

citizens. Inherent in these responsibilities is the obligation to verify applicant identities, to prevent the issuance of travel documents to those who pose national security threats, and to prevent the issuance of travel documents to applicants using fraudulent aliases. These tasks may require the comparison of some identifying features of applicants against large databases from multiple agencies, such as DoS, the Federal Bureau of Investigation (FBI), and the Department of Homeland Security (DHS). DoS checks textual biographic information (e.g., name and date of birth) of applicants and collects biometrics information from non-exempt groups of visa applicants at consular posts. DoS’s responsibility for preventing multiple-application fraud requires searching large databases of previous visa/passport applications.

SBU - CONTRACTING AND ACQUISITIONS 8

The Facial Recognition system integrates with several CA travel document processing systems.

The vendor library document "VL1 – Systems Requirements Documentation" (included in the solicitation package) provides a brief description of the processes that the facial recognition system supports. The Contractor shall work seamlessly with several DOS groups, as directed by the Contracting Officer (CO) or Contracting Officer's Representative (COR). These groups represent government stakeholders, end users, and existing DOS support contractors. CA represents the core DOS end users of the facial recognition technology and includes DOS employees and contractors in Passport Services and Visa Services. CST provides technical direction for the systems acquired through this contract.

Other government agencies, such as the Department of Homeland Security (DHS), are provided with limited access to DoS’s FR system to conduct FR searches against DoS’s visa gallery in support of their investigations.

II TASK AREAS

1 SPECIFIC TASKS OR REQUIREMENTS

1.1 Task Area 1: FR SOFTWARE AND LICENSES

The Contractor shall provide an enterprise software license model to the Department of State for use in identification (1:N), verification (1:1), and enrollment of biometric face images. The license model should support both on-premises deployment and cloud deployment configurations.

The Contractor shall enroll images from current and future government image repositories and other sources into the COTS solution. The Vendor Library document “VL1 – Systems Requirement Document (SRD), Section 4.1. Sizing Requirements” specifies the number of images and the estimated annual growth in enrollments and searches. However, the enterprise software license model shall allow for scaling in searching and enrollments beyond what Section 4.1. Sizing Requirements specifies without requiring additional license procurement or renegotiation for increases up to exponential increases of the baseline capacity.

In addition to the operations specified in the Systems Requirement Document, the Contractor shall provide additional licenses to CST’s support contractors and Independent Verification and Validation (IV&V) teams for integration testing, performance benchmarking, and algorithm tuning. Typically, these operations require galleries sized at greater than or equal to 2,000,000 images.

Prices and terms of use for the enterprise software license model for identification, verification, and enrollments shall be independent of future implementation of additional watch lists or other image repository sources when used to meet the mission of the Department of State. The Contractor shall identify all software comprising the FR system. The Contractor shall include the cost of the software in the Pricing Sheet. Costs related to the maintenance of the software shall be included in FR System Installation and Support Services.

Goudy, Felicia D How is the contractor supposed to price this as a FFP if some of the work is at the discretion of the Government? They are going to price high to cover this optional request. This work should probably be an optional CLIN.

Cassady, Ty M Removed at the discretion of the Government. The license model should support both on-premises deployment and cloud deployment configurations.

Goudy, Felicia D Why wouldn’t IV&V be done by a separate vendor?

Cassady, Ty M Given that IDEMIA has sole ownership of their product, they need to provide licenses for their system design lifecycle processes. IV&V is currently being done by a separate vendor, and IDEMIA is providing licenses in support.

SBU - CONTRACTING AND ACQUISITIONS 9

1.2 Task Area 2: FR SYSTEM INSTALLATION, MAINTENANCE AND

SUPPORT SERVICES

The Contractor shall install and maintain FR systems at two geographically distinct DoS computer operation centers. Except during scheduled outages, each system shall provide active search capabilities. Each system shall be capable of meeting workload and performance requirements if one system is interrupted, as described in the vendor library document VL1 - System Requirements Document (SRD).

The Contractor shall configure the FR system to accommodate the workloads and database sizes as specified in Appendix A of VL1 - System Requirements Document (SRD). The Contractor shall install all FR software on the system as specified in the Software Installation Plan. The Contractor shall conduct a Service Operations Readiness Test (SORT) in accordance with the Government-provided Service Operational Readiness Framework (SORF) to demonstrate that the system is ready to accept operational data and be integrated with the Government’s Visa and Passport Systems.

The SORT plan shall include:

• Database backup

• Database Recovery

• Software Installation and Configuration

• Rollback

• Failover

• Reliability

• Performance

• Regression testing

• Security

1.2.1 System Installation and Support Plan

The Contractor shall develop and maintain a comprehensive FR System Installation and Support Plan (SISP) describing the technical approach for installation of the FR software at two geographically distinct DoS computer operation centers. The SISP shall include the Contractor’s approach to enrolling images, resolution of data conversion problems, testing, and configuration of the FR system to accommodate the workloads and database sizes. SISP shall provide a detailed narrative defining ongoing services to be provided in quantitative and qualitative terms while at the same time providing descriptive instructions on how to achieve/complete specific operational functions.

SISP is a living document and may be changed in response to innovative performance improvements. SISP should utilize a combination of text and diagrams to clearly illustrate processes. The Contractor shall submit the SISP within fourteen (14) business after task order, at the kickoff meeting, for Government review and approval by the COR. The Contractor shall

SBU - CONTRACTING AND ACQUISITIONS 10

submit a revised SISP to Government ten (10) business days after an innovative performance improvement.

At a minimum, the SISP shall address the following:

a) Software Installation Plan

b) Technology Refreshment Plan

c) System Training Plan

d) System and IV&V Test Plan

e) Service Operational Readiness Test (SORT) Plan

f) Software Maintenance Plan

g) Disaster Recovery Plan

Revisions to the SISP after innovative performance improvements shall include, but are not limited to:

a) All sections of the SISP, as necessary

b) System Test Execution Reports

c) End User Assessment Reports

1.2.2 Support for Operations

The Contractor shall provide operational support for FR systems throughout the period of performance, including real-time performance monitoring with automated alerting, workload monitoring with predictive capacity planning, system growth and technology refreshment support, system health diagnostics, troubleshooting, and interoperability with the Government's Visa and Passport Systems.

At the Government's discretion, the Contractor shall support independent performance testing on operational and laboratory systems as directed by the Government. Testing shall assess accuracy, ensure equitable performance across demographic groups, prevent susceptibility to presentation attacks, and maintain compliance with legal, privacy, and operational requirements following software updates and as database sizes increase. Testing results shall support Government system configuration decisions.

The Contractor shall provide periodic preventive and adaptive maintenance on Contractor-installed software. The Contractor shall notify the Government thirty (30) calendar days in advance of all software updates with rationale. Updates require Government approval prior to integration and shall be installed with no disruption to operations. The Contractor shall maintain rollback capability in the event of performance degradation.

The Contractor shall provide non-emergency technical support for non-mission critical problems during business hours via email and Contractor-provided hotline. Technical support shall meet the requirement outlined in the Technical Performance Standards section of this document.

When a new version of the FR software is available for public release, the Contractor shall notify DoS within thirty (30) calendar days of the public release date and shall install it within thirty (30)

Santhumayor, Ashrita Should we specify what the business hours are?

Salama, Shery S No need to specifiy

SBU - CONTRACTING AND ACQUISITIONS 11

calendar days of written (including email) DoS approval. The Contractor shall provide at least one facial recognition system software release upgrade per contract year at no additional cost to the Government (cost shall be included in the software lease cost at time of contract award). With Government approval, the Contractor may deploy minor software updates to the facial recognition system to continue to meet or exceed requirements.

Planned upgrades shall not cause any facial recognition service downtime nor compromise current facial recognition operations. Image enrollments required by facial recognition system upgrades must not interfere with current facial recognition operations.

1.2.3 System Performance Monitoring

CST has standardized the following application and system monitoring tools to enhance operations support, including but not limited to:

Zabbix: Operating System monitoring AppDynamics: End-to-end business transaction monitoring Splunk: Event log monitoring

The Contractor shall demonstrate knowledge of and experience with these monitoring tools or equivalent systems capable of performing the same functions. The Contractor shall integrate the facial recognition system with these monitoring tools or provide equivalent monitoring capabilities that meet or exceed the functionality of the Government's standardized tools.

1.2.4 Metrics Collection and Reporting

The Contractor shall collect, maintain, calculate, and report operational metrics associated with the facial recognition environment and in support of government oversight, and operational monitoring requirements. The contractor shall submit the first metrics report 14 days after DOA;

monthly reports shall be submitted NLT 20 days after the end of a month.

1.2.4.1 Metrics Repository

The Contractor shall establish and maintain a centralized metrics repository to store, track, and update approved operational, system, and performance metrics in accordance with Government-defined reporting intervals, including daily, weekly, monthly, quarterly, and annual requirements, as applicable. The Contractor shall ensure all collected metrics are accurate, complete, and timely, and shall maintain documentation demonstrating the provenance and validation of all reported data.

The Contractor shall provide the Government with access to the centralized metrics repository upon request and generate reports in Government-specified formats within established timeframes. All metric data and associated documentation shall be retained in accordance with applicable Federal records management requirements and shall remain Government property.

1.2.4.2 Operational Metrics

Cambi, Blanca J @Santhumayor, Ashrita

SBU - CONTRACTING AND ACQUISITIONS 12

Operational metrics track day-to-day system activities and business processes, including but not limited to:

• Transaction volumes

• Facial recognition processing statistics

• Search and enrollment of images

• Operational throughput

• Incident and trouble ticket statistics

• Integration and service utilization metrics

• Error rates and exception reporting

1.2.4.3 Performance Metrics

Performance metrics measure system health, reliability, and responsiveness, including but not limited to:

• System availability and uptime

• Performance and response time measurements

• Service level achievement

• System capacity utilization

1.2.4.4 Gallery Statistics Metrics

The Contractor shall submit a Gallery Statistics Report based on the specifications outline in VL1

- System Requirements Document (SRD)

1.2.4.5 Reporting Requirements

The Contractor shall provide metrics reports, summaries, data extracts, and supporting documentation in Government-specified formats. Generally, the Contractor shall generate reports monthly, but the DOS Contracting Officer Representative (COR) may request reports as needed to answer management inquiries. The Contractor shall maintain reports in a centralized location accessible to authorized Government personnel. The Contractor shall support ad hoc reporting, data analysis, operational trend identification, audit support, and metric validation activities as required throughout the period of performance.

Quality Assurance The Contractor shall maintain documented procedures for metric collection, calculation methodologies, data handling, quality assurance, and reporting processes to ensure consistency and repeatability across reporting periods.

1.2.5 Emergency Support

The Contractor shall provide emergency support upon request from the Government. An "emergency" is defined as a technical failure of the FR system that is mission-critical and/or renders the FR system non-functional – see Technical Performance Standards

1.2.6 Image Re-enrollment

SBU - CONTRACTING AND ACQUISITIONS 13

The Contractor shall provide an Enterprise license for a software application that facilitates re-enrollment of images that failed to automatically enroll into a gallery. The re-enrollment software and license shall be available at the time images are initially loaded and shall remain available throughout the life of the contract.

1.2.7 Capacity Upgrades

In accordance with the Capacity Management Plan contained in the contractor developed PMP, when a capacity upgrade is required to meet projected growth requirements or other operational needs, the Contractor shall perform the upgrade during a normally scheduled maintenance period. Upgrades shall not adversely impact the required service availability levels.

1.2.8 Technology Refresh

The Contractor shall monitor and maintain awareness of updates, enhancements, algorithm improvements, software releases, and technical capabilities associated with the facial recognition solution throughout the period of performance.

Technology Refresh Notifications

When applicable, the Contractor shall notify the Government of available technology refresh opportunities, including:

• Algorithm updates

• Software improvements

• Replacement components

• Technical enhancements that may improve operational effectiveness, security, supportability, or system performance

Technology Refresh Proposals The contractor shall provide a technology refresh proposal to the government for review and consideration when recommending new or replacement products, services, software versions, algorithms, or technical capabilities. At a minimum, the proposal shall include:

• Description of the proposed product, service, update, or replacement capability

• Identification of products or services to be added, modified, replaced, or removed

• Justification for the proposed addition, replacement, or update

• Operational, technical, security, and performance impacts

• Compatibility considerations with the existing environment

• Technical literature, vendor documentation, release notes, and supporting materials

• Licensing implications, dependencies, and support requirements

• Risks, assumptions, limitations, and implementation considerations

Government Evaluation Support

@Chapman, William J /@Hall, Nathaniel A - What is this speaking to? Is this already in the SRD? If yes, which section for refence.

Hall, Nathaniel A This is in the SRD section 5.1 and also discussed in SRD sections 2.1 and 4.1.1

Santhumayor, Ashrita What is a normal period?

Cambi, Blanca J @Chapman, William J /@Hall, Nathaniel A - Please clarify how is this under this section?

Hall, Nathaniel A retitled this section

Hall, Nathaniel A Separated into spearate sections by adding a section here.

SBU - CONTRACTING AND ACQUISITIONS 14

The Contractor shall support Government-directed independent validation, testing, assessment, audit, and evaluation activities associated with proposed technology refresh efforts. Support may include:

• Coordination with designated Government personnel

• Provision of technical documentation

• Troubleshooting assistance

• Test environment support

• Participation in technical reviews as requested by the Government

1.2.9 Training and Materials Services

Training Requirements The Contractor shall provide training on the use of the FR system to designated DoS staff. The training program shall be approved by the Government and conducted within 30 days of commencement of parallel operations.

Training Schedule and Location

• Initial Training: Within thirty (30) days of commencement of parallel operations.

• Update Training: Following each system upgrade, but no more frequently than once every six (6) months.

• Location: Classroom training shall be provided at Department offices in Washington, DC, or other Department-designated training locations.

• Annual Training: The Contractor shall provide annual in-person training classes for

Department operations personnel.

Training Content:

The focus of training for Government-designated system personnel shall include, but not be limited to:

• Adjusting per-search FR customizable settings and parameters

• Interpreting daily operations reports

• Executing diagnostic tests to determine system performance

• Modifying FR system parameters to identify and address abnormal conditions found in daily operations reports

• Interpreting daily operations reports to determine if parameter changes successfully addressed abnormal conditions

• Determining when changes to FR system parameters did not resolve abnormal conditions identified in daily operations reports

Training Materials and Documentation

SBU - CONTRACTING AND ACQUISITIONS 15

The Contractor shall develop and deliver comprehensive training materials and documentation as deliverables to support all training activities.

• Initial Delivery: Updated training materials shall be delivered to the COR/Government

Technical Monitor (GTM) within fourteen (14) calendar days of contract award.

• Updates: Training materials shall be updated within thirty (30) calendar days following each system upgrade or modification that affects training content.

Training The Contractor shall be required to provide periodic training on the basics of facial recognition to Foreign Service employees and others as designated by the Department.

1.2.10 Independent Biometrics Tuning, Biometric Accuracy Measurement, and Stability Testing

The Contractor shall coordinate with the Government and other contractor teams to facilitate independent review and verification of:

• Biometrics tuning

• Biometrics accuracy measurement

• Operational match result stability testing

Test System for Tuning and Accuracy Measurement For biometrics tuning and accuracy measurements, the Contractor shall provide a non-production FR system license and technical support for a Test System to facilitate search results threshold tuning and match accuracy testing for both the current production system and any future proposed products.

Test System Requirements:

• Algorithm Parity: The biometric algorithms must be identical to those used in the production environment, although the Test System is not subject to operational performance workload, throughput, or response time requirements

• Capacity: The Test System shall support a test gallery of greater than or equal to 2,000,000 images

• Gallery Content: The test gallery contents shall be a Department-designated subset of the operational repositories

Stability Testing Support The Contractor shall support periodic (monthly) stability tests of the operational biometrics system. The Contractor shall:

• Batch enrolls and search designated images from a test gallery and search probe images

• Mark all test images as "test" to ensure they are not included among operational returns

Goudy, Felicia D Should not be part of the FFP pricing - separate CLIN.

Cassady, Ty M The Contractor shall be required to provide periodic training.

Goudy, Felicia D Should be done by another vendor?

Cassady, Ty M IV&V is currently being done by a separate vendor, and IDEMIA is providing licenses in support.

SBU - CONTRACTING AND ACQUISITIONS 16

• Provide image identifications with returned biometric scores from probes searched against operational system galleries, including the test gallery, to the Government and other contractor teams

• Support investigations of all unexpected anomalies the Government may discover in test results

Analysis and Investigation:

Image identifications and scores shall be analyzed for stability of image returns and score consistency between periodic tests. The Contractor shall support Government investigations of any unexpected anomalies discovered in these results.

1.2.11 Independent Verification and Validation Support

The Contractor shall provide products to the CST Independent Verification and Validation (IV&V) Support Team through the CST Configuration Management (CM) upon completion of product development. The Contractor shall factor IV&V testing time into the development and installation schedule. During IV&V testing, the Contractor shall cooperate with CST CM, CST Data Engineering group, and other relevant parties as necessary.

Capabilities developed by the Contractor shall be subject to IV&V as detailed in the CST IV&V Standard Operating Procedures (SOP). Business and system requirements shall be reviewed and validated by the IV&V group as complete and testable. Design and implementation artifacts may also be reviewed and validated by the IV&V group. Applications shall be subject to a combination of functional, performance, and reliability testing during the IV&V test process as recommended by the IV&V agent and deemed appropriate by government.

The Contractor shall provide a non-production FR system (Test System) for tuning and IV&V testing. The Test System shall be integrated with Government IV&V systems for testing and development purposes and deployed on Government Furnished Equipment (GFE). The Test System shall support the same functionality as the operational system; however, it is not subject to operational workload, throughput, or response time requirements. The Test System shall have capacity to support all operational galleries and include greater than or equal to 2,000,000 test gallery images for tuning and testing, the contents of which shall be a Department-designated subset of the operational repositories.

The Contractor shall provide plans for the installation and testing of the software comprising the new FR system (referred to as the Software Installation Plan). All hardware will be defined in VL4

– Preferred GFE [Government Furnished Equipment] Specs [Attachment E] in the vendor library.

All additional support requirements to be provided by the Government shall be identified.

The Contractor shall perform Quality Assurance (QA) testing to systematically examine and exercise the system during installation to validate that the software is production-ready before delivering it to IV&V. QA testing shall include assessment and evaluation of system functionality, Salama, Shery S Confirm info

Forst, Brendan P Consider removing the reference to "re-train". Training of a vendor algorithm is usually handled in house by vendors as it is a proprietary process. IV&V would likely be able to fine tune the algorithm with adjustments to vendor thresholds.

SBU - CONTRACTING AND ACQUISITIONS 17

integration testing with other affected systems, and performance testing conducted internally throughout system development.

1.2.12 Operations Manual

The Contractor shall develop, provide, and maintain an Operations Manual for the FR system. The content of the Operations Manual shall be agreed upon by the Contractor and the Government within thirty (30) days of contract award. The completed Operations Manual shall be delivered to the Department within thirty (30) days of FR system installation.

At a minimum, the Operations Manual shall contain:

• Summary of all adjustable operational settings and parameters (e.g., normalization, enrollment leniency)

• Definitions of parameters and their value ranges, including recommended values

• Procedures for setting Department customizable settings and parameters (e.g., score threshold, maximum rank)

• Instructions for interpreting daily operations reports

• Procedures for executing diagnostic tests to determine system performance

• Guidance for modifying FR system parameters to address abnormal conditions identified in daily operations reports

• Methods for interpreting daily operations reports to determine if parameter changes successfully addressed abnormal conditions

• Procedures for determining when changes to FR system parameters did not resolve abnormal conditions identified in daily operations reports

• System architecture overview and component descriptions

• Troubleshooting procedures and common error resolution steps

• Contact information for technical support escalation

Manual Maintenance and Updates

The Contractor shall update the Operations Manual within thirty (30) days following any system upgrade, modification, or change that affects operational procedures or system parameters. The Contractor shall submit updated versions to the COR for review and approval. The Contractor shall maintain version control and change tracking for all manual revisions. The Contractor shall maintain the Operations Manual in a centralized location accessible to authorized Government personnel and provided in both electronic searchable format and printed format as specified by the Government.

1.3 Task Area 3: FR SYSTEM INTEGRATION SERVICES

The Contractor shall integrate the FR system with the Government’s systems in a manner that does not compromise the performance of the operational systems. The integration effort shall address all databases and all transaction types as specified in VL1 - System Requirements Document (SRD).

The integrated components will be subjected to a SORT, which will demonstrate that the FR system has the required functionality, that the performance levels are compliant with the specifications, and that the database is synchronized with the system. The Government shall

SBU - CONTRACTING AND ACQUISITIONS 18

conduct acceptance testing for the FR matcher in accordance with clause 52.212-4(a) Inspection of Supplies - Commercial Items.

The Contractor shall be required to provide the capability to deliver and integrate matching software for additional biometric modalities as requested (e.g., iris). The Contractor may be required to support the capability to fuse biometric information from multiple sources into a single matching decision with weights adjustable by DoS.

1.3.1 Image Review Software

The Contractor shall develop, integrate, and maintain software that facilitates human verification of FR results by biometric examiners. The image review software shall be tailored for high-volume review processes and support multiple user types with varying workload volumes. Staff at the Kentucky Consular Center (KCC) and National Visa Center (NVC) are the primary examiners responsible for reviewing FR candidate lists. The image review software shall enable KCC/NVC staff to review candidates quickly and efficiently in a high-volume environment. At lower volumes, travel document adjudicators, fraud investigators, and FR specialists shall also use the image review software.

At a minimum, the image review software shall provide side-by-side image comparison capabilities, display of biometric match scores and ranking information, image zoom, pan, and enhancement tools, clear presentation of candidate biographical data, intuitive navigation through candidate lists, decision recording and annotation capabilities, queue management for pending reviews, and search and retrieval of previous examiner decisions. The user interface shall be intuitive, require minimal training, and optimize examiner productivity. The software shall provide role-based access controls appropriate to each user type.

The image review software shall integrate with the FR system, operational galleries, and relevant Department systems to retrieve candidate images, biometric scores, biographical data, and case information as required for examiner review. The system shall maintain audit trails of all examiner decisions, including examiner identity, timestamp, decision rendered, and any annotations or comments. The system shall support reporting on examiner activity, decision statistics, and workflow metrics as specified by the Government.

The Contractor shall provide user documentation, quick reference guides, and training materials for the image review software. Documentation shall be tailored to each user type and updated within thirty (30) days of any software modification that affects user procedures or functionality.

1.3.2 Support for Image Repositories

The Contractor shall operate, manage, and maintain the existing facial recognition template repository / galleries in support of DT’s operations and associated services.

The repository shall store and manage facial image templates and associated metadata required to support authorized CA business processes and operational workflows. The contractor shall ensure continued availability, integrity, and accessibility of repository data within the existing operational environment.

Salama, Shery S Is the Acceptance testing part of the SORT? Does the contractor perform the acceptance testing or CST?

Santhumayor, Ashrita Updated

Santhumayor, Ashrita What is the scope here?

Goudy, Felicia D Again, FFP is based on definite requirements, this section does not lend to a FFP.

Cassady, Ty M The Contractor shall be required.

Salama, Shery S Review for accuracy and updates

Chapman, William J @Santhumayor, Ashrita Do we expect the vendor to provide this? It may not make sense for the team to develop a different interface if Occam will be the new system.

Santhumayor, Ashrita Occam is a replacement for TDIS to perform adjudication for OPR applications. Manual review of the FR results will still be around for a bit until the decision to bypass KCC review is fully implemented.

Santhumayor, Ashrita MBSS only provides results to be viewed via the CCD. So, can we check this again, please? @Virgin, George C @Chapman, William J

Chapman, William J Revised to remove the aspect of retrieval from the repository and focus on retention and management of image identification and metadata

Leave it as future enhancement

SBU - CONTRACTING AND ACQUISITIONS 19

The repository shall remain accessible through existing web services and interfaces and show support capabilities including but not limited to:

• Image enrollment, image edition and updates

• Template management

• Retention and management of image identification and metadata provided during enrollment

• Record deletion

• Associated metadata management

The Contractor shall maintain interoperability and compatibility with existing applications, connected systems, and operational workflows currently utilizing the repository. In addition, the contractor shall provide technical support and integration assistance necessary to enable authorized new government applications additional services to interface with then utilized existing repository capabilities, as approved by the government.

The Contractor shall provide one-to-many FR matching support for additional watch-list galleries or other image repository sources when used to meet the mission of the Department of State. Prices and terms of use for watch-list support shall remain independent of the number of watch lists or repository sources, consistent with Task Area 1 licensing provisions.

The Contractor shall provide operational, technical, and troubleshooting support necessary to sustain repository functionality, connectivity, and performance throughout the period of performance.

1.3.3 Support for Evolving Enterprise Architecture

As the infrastructure evolves, the Contractor shall evolve and/or support the development of new interfaces to the FR system to meet approved requirements issued by the Government. This may include updating system-of-systems architecture to a more robust Enterprise Solution.

The Contractor shall design and implement modern, API-based interfaces that support scalability, interoperability, and integration with contemporary Department systems and cloud-based services.

All interfaces shall adhere to industry-standard API design principles, including RESTful architecture, secure authentication and authorization mechanisms, and comprehensive API documentation.

API documentation shall include:

• Endpoint descriptions and specifications

• Request and response formats and examples

• Authentication and authorization requirements

• Error codes and handling procedures

• Rate limiting and throttling policies

• Sample code and integration examples

• Testing and sandbox environment access

Chapman, William J @Virgin, George C - are images being retained for retrieval? Is this accurate?

Chapman, William J This appears to have been updated such that image retention has been removed and instead refers to image identification and metadata (rather than images themselves)

Chapman, William J @Virgin, George C - are images being retained for retrieval? Is this accurate?

Chapman, William J This appears to have been updated such that image retention has been removed and instead refers to image identification and metadata (rather than images themselves)

Salama, Shery S Review

Question for Santi - How does CCD integrate with MBSS? Via ESB?

SBU - CONTRACTING AND ACQUISITIONS 20

All API interfaces shall implement:

• Secure authentication mechanisms (e.g., OAuth 2.0, API keys, mutual TLS)

• Role-based access control (RBAC)

• Encryption in transit (TLS 1.3 or higher)

• Input validation and sanitization

• Audit logging of all API transactions

• Compliance with Department security policies and NIST standards

The Contractor shall ensure that API implementations support versioning, backward compatibility, and graceful deprecation of legacy interfaces to minimize disruption to existing integrations. API interfaces shall be designed to facilitate microservices architecture, containerization, and cloud-native deployment models as the Department's infrastructure modernization efforts progress. The Contractor shall provide API specifications, developer documentation, and testing tools to support Government and third-party integration efforts.

1.3.4 System Integration Plan

The Contractor shall develop a System Integration Plan (SIP) as directed by the Government. The SIP shall include the Detailed Design and Interface Control Document (ICD) describing how they will accomplish the transition to Enterprise Solution. The Contractor shall include Image Review Software & System Documentation as part of the SIP.

The contractor shall provide a SIP to the COR within 30 days of the start of the performance of this vehicle. The Contractor shall update the SIP regularly and as integration work progresses and shall submit revised versions for Government approval following any significant changes to the integration approach, architecture, or requirements.

1.4 Task Area 4: PROGRAM and PROJECT MANAGEMENT

The Contractor shall be responsible for the effective management and administration of all efforts performed under this task order. The Contractor shall ensure that all work activities are performed in a timely, efficient, and cost-effective manner while maintaining the highest quality of performance. The Contractor shall institute and maintain an effective, efficient, and responsive management organization that provides administrative support for all tasks under this contract.

The Contractor shall oversee all contracted personnel and subcontracted resources used in the performance of this contract, including while on-site at Department offices.

The Contractor shall be responsible for program control and management for this effort and shall execute…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .