Q and A - Responses 2.xlsx.docx

1. What is the peak hourly transaction load that contractors should use for the design of the matching system software and hardware?

The maximum transaction capacity per hour is not predefined. The contractor must propose scalable architecture that complies with the requirements set forth in this RFP, considering design best practices, high availability, performance, and the future growth of the solution.

As a reference for sizing the proposal, the current volume averages 3,000 passport enrollments per 24-hour period—subject to the operational capacity of the enrollment centers—as well as an average of 270,000 daily migration records.

2. Does the customer require a perpetual license for biometric application software so that it will continue to operate after the three-year period of performance even if technical support and updates end after three years?

Yes. A perpetual license for the biometric application software is required so that the system continues to operate indefinitely after the specified period, regardless of whether technical support and updates end.

3. Does the customer require perpetual licenses for operating system software or security software?

Yes, include licensing for the operating system, perpetual licensing – Linux.

Regarding security software, it is not necessary to include it in the proposal, as the client will provide it.

4. Is open-source Linux operating system software acceptable?

Yes, as long as compatibility with the offered product is guaranteed.

5. Regarding disaster recovery:

1) Does the customer have a recovery time objective (RTO) resulting from system loss? Answer in next paragraph

2) Do you have a recovery point objective (RPO) that affects backup frequency? Answer in next paragraph

3) Do you have a requirement for a disaster recovery site? Answer in next paragraph

4) Do you have specific targets defined for RTO/RPO or needs for a disaster recovery site? Answer in next paragraph

Regarding disaster recovery, the client currently lacks formally established RTO and RPO objectives for the platform subject to this procurement.

Furthermore, a dedicated secondary site for disaster recovery (Disaster Recovery Site) is not currently available.

Consequently, vendors must propose the best practices, architectures, and mechanisms for backup, recovery, and operational continuity that they deem appropriate for the proposed solution. This includes recommendations regarding RTO, RPO, backup strategies, high availability, and disaster recovery, taking into account the criticality of the biometric services and information protection—provided that this does not result in any impact on the costs associated with the offered product.

6. The RFP has a training requirement for “Best practices for capturing high-quality fingerprints, facial and iris images compliant with the newly mandated MINEX III standard”. Biometric capture training can be capture device specific.

1) Is the provision of biometrics capture devices in the scope of this award?

2) If not, what devices are planned for capturing biometrics?

No provision of devices is required; fingerprint readers and a camera for facial capture are available, both of which comply with the standards requested by the ICAO/OACI

7. The RFP has a biometrics database technology transfer requirement for “1) An intensive hands-on workshop of at least 40 man-hours, focused specifically on the integration, development, and connectivity testing of the IGM's enrolment and verification systems with the ABIS engine; …”

1) Please clarify that this RFP is requesting a biometric matching engine, and is not requesting a full ABIS that includes a transaction manager (TM), examiner/user tools, and a matching engine, etc., Assuming that an “ABIS” contains a transaction manager that

i. Verifies and accepts enrollments from collection sources provided in ANSI NIST ITL “EFT” files.

ii. Routes and handles data according to transaction types defined in the EFT file (per an EBTS specification)

iii. Stores enrollment biographic data and images

iv. Submits biometric images to the matcher for templating and matching

v. Receives biometric matcher responses and routes them according to the transaction type Enrollment data storage – biographic data, transaction records, biometric images Examiner tools – tools used by biometric examiners to review submitted images and match results.

Matching engine – converts images to proprietary image templates, compares probe image templates to the gallery of image templates, and provides matching results User tools – transaction and workflow management, query and reporting tools, system health monitoring, user account administration

This RFP specifically requests a biometric matching engine for integration with the IGM’s existing systems. The vendor is not required to provide a complete ABIS, including a transaction manager, biographical data storage, examiner tools, or user administration modules, unless such components are necessary for the proper operation and integration of the proposed biometric engine.

The technology transfer workshop must focus on the integration, configuration, development, and connectivity testing between the IGM’s systems and the supplied biometric engine.

8. On page 16 of the solicitation, under 52.212-2(a), no evaluation criteria is provided. Please provide the evaluation criteria in this section.

Evaluation Criteria in section 3.10 on page 11 of the SOW

9. Would the government consider a 1-week extension to June 11, 2026 to enable solution design optimization according to the answers to these questions assuming the answers will be no later than June 4, 2026?

One week is acceptable.