26OIPL-RFI-26-17_QUESTIONSFORINTERESTEDPARTIES.xlsx
XLSX spreadsheet 21 KB Posted
- Solicitation number
- 26OIPL-RFI-26-17
About this file
This file is a questionnaire template designed to gather information from interested vendors regarding their capabilities to provide iOS-compatible biometric devices for the U.S. Coast Guard's Biometrics at Sea System. The RFI (Request for Information) numbered 26OIPL-RFI-26-17 seeks to identify potential contractors who can supply devices meeting specific technical and operational requirements before a formal solicitation is issued.
The questionnaire addresses multiple dimensions of vendor capability and product specifications. Business qualification questions ask whether companies would submit a quote if formally solicited, whether they currently offer the product or service commercially, their relevant experience, applicable contract vehicles, NAICS codes, business size, and socioeconomic status. The template also requests lead time requirements, feedback, capabilities statements with project references, and response timelines for RFQ preparation. Technical specifications covered include OEM support dates (End of Life, End of Sales, End of Support, End of Extended Support), deployment history within DoD and federal civilian agencies, and on-site test support capabilities. Device-specific questions address iOS compatibility, connectivity to InCadence Ares Gateway and Microsoft Intune, power interfaces, WiFi and cellular connectivity, data export capabilities via multiple methods, physical characteristics (hand-carry capability and weight), battery life exceeding five hours, anti-tamper mechanisms, biometric compliance standards (FBI NGI, OBIM IDENT, HART, FIPS 140-2), ANSI/NIST-ITL record generation, FBI EBTS and DHS IXM message transmission, and specific biometric capture capabilities including fingerprints (slap 4-finger), iris images, and facial images in compliance with DoD EBTS 4.1 standards.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 26OIPL-RFI-26-17 CAPABILITY STATEMENT.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
Sheet1
| Question | Question Type | Answer |
| Based on the provided information, would your company submit a quote if this requirement was issued on SAM.gov? | Yes/ No | |
| Does your company provide this service or product commercially? | Yes/ No | |
| Does your company have the capability to perform all required services in the capability needs statement? | Yes/ No | |
| Does your company have similar or previous experience with the type of work outlined in the capability needs statement? | Yes/ No | |
| Please identify all contract vehicles that your company is on and are applicable to this requirement. | Open Ended | |
| Please list the NAICS code(s) you determine are appropriate for this requirement. | Open Ended | |
| Business Size. | Open Ended | |
| Please listall socio-economic categories that apply. | Open Ended | |
| In your estimation how much of this potential requirement would your company need to subcontract to other companies? | Open Ended | |
| How much lead time would your company need from notification of award to start of contract performance for this type of requirement? | Open Ended | |
| Optional Feedback: Please provide any feedback or questions you may have related to this capability needs statement. | Open Ended | |
| Capability Website: Please provide a URL to a capability website for your company. | Open Ended | Please Upload |
| Capabilities Statement: to include up to 3 relevant projects and provide the following information for each: Customer Name, Customer/Client POC Email, Total Contract Value, Period of Performance, Brief Description of Services Provided, Indicate if there is a CPARS Available | Open Ended | Please Upload |
| What is a realistic response time for RFQ preparation on this type of solicitation? | Open Ended | |
| What is the Original Equipment Manufacturer (OEM) listed End of Extended Support date for the product(s)? | Open Ended | |
| What is the Original Equipment Manufacturer (OEM) listed End of Life date for the product(s)? | Open Ended | |
| What is the Original Equipment Manufacturer (OEM) listed End of Sales date for the product(s)? | Open Ended | |
| What is the Original Equipment Manufacturer (OEM) listed End of Support date for the product(s)? | Open Ended | |
| Has the product been deployed within a Department of Defense (DoD) Organization (.mil domain)? | Yes/No | |
| Has the product been deployed within a Federal Civilian Agency (.gov domain)? | Yes/No | |
| Do you provide on-site test support to include planning, execution, and analysis of live test events? | Yes/No | |
| Does your company provide configuration, customization, and enhancement services for the product? | Yes/No | |
| How do users access the software product(s)? | Open Ended | |
| How are the software product(s) installed / deployed? | Open Ended | |
| Are there any hardware-infrastructure dependencies for the software product(s) solution (e.g., Server, CPU, RAM)? | Open Ended | |
| Are there any software-infrastructure dependencies or specialized integration software required for the installation / deployment of the software product(s) (e.g., Operating System)? | Open Ended | |
| Is the device/application iOS compatible? | Yes/No | |
| Can the device connect to the InCadence Ares Gateway? | Open Ended | |
| Can the device be managed via Microsoft Intune? | Open Ended | |
| What power and peripheral interfaces are utilized (e.g., USB-C Power Delivery, inductive charging)? | Yes/No | |
| Can the device connect to available WiFi? | Yes/No | |
| Can the device connect to available Cellular service? | Yes/No | |
| Can the data be exported via WiFi? | Yes/No | |
| Can the data be exported via Cellular? | Yes/No | |
| Can the data be exported via thumb drive (or external media)? | Yes/No | |
| Can the device be carried in one hand? | Yes/No | |
| How heavy is the device? | Open Ended | |
| Can the device stay charged for more than 5 hours while in use? | Yes/No | |
| How long can the device stay charged while in use? | Yes/No | |
| Does the hardware incorporate physical anti-tamper mechanisms or zeroization capabilities? | Open Ended | |
| Does the device comply with FBI’s Next Generation Identification (NGI), Office of Biometric Identity Management’s (OBIM) Automated Biometric Identification System (IDENT) and upcoming replacement system, Homeland Advanced Recognition Technology (HART) standards? | Open Ended | |
| Does the device have GPS? | Yes/No | |
| Is the device ruggedized (MIL-STD-810G (6-foot drop test))? | Open Ended | |
| Can the device be audited? | Yes/No | |
| Is the device Federal Information Processing Standard 140-2 compliant (FIPS-140-2)? | Open Ended | |
| Does the system natively generate ANSI/NIST-ITL compliant records (e.g., Type 4/14, Type 10, Type 17) at the point of capture? | Yes/No | |
| Is the device software capable of building and transmitting FBI EBTS and DHS IXM formatted messages? | Open Ended | |
| Are the biometric sensors certified to FBI Appendix F (or Mobile ID) standards? | Open Ended | |
| How does your software handle and evaluate ISO/IEC 19795-1 and 29794 quality scores in real-time? | Open Ended | |
| Does the device collect biometric data in accordance with DoD EBTS 4.1? | Yes/No | |
| Does the device collect Iris images? | Yes/No | |
| Does the device collect slap fingerprints 4 fingers at a time? | Yes/No | |
| Does the device collect facial images? | Yes/No |
File details come from the government source that posted it. Updated .