Att P – Requirements Matrix.xlsx
XLSX spreadsheet 94 KB Posted
- Attached to
- Automated Fingerprint Identification SystemBid Documents State and local contract opportunity
- Solicitation number
- 27-85295
- Issued by
- Marion County, Indiana
About this file
Attachment P – Requirements Matrix for Indiana State Police AFIS Modernization
This document is a requirements matrix for the State of Indiana, Indiana State Police (ISP), RFP #27-85295 for an Automated Fingerprinting Identification System (AFIS) Modernization project. The matrix serves as the evaluation tool for vendor responses and outlines functional, technical, and administrative requirements across multiple categories. Respondents must indicate whether their proposed solutions meet each requirement as an existing component, through configuration only, via customization, as a planned upgrade within 12 months, or not at all. The matrix encompasses over 80 distinct functional and technical requirements spanning general administration, biometric modalities, data intake, FBI interfaces, field operations, security, reporting, training, and system architecture. Key functional areas include support for multiple biometric modalities (fingerprints, palm prints, latent impressions, facial recognition), integration with existing state systems (MBIS, CCH), mobile identification capabilities, multi-level verification workflows, disaster recovery with specific RPO/RTO objectives (5-second RPO, 30-second RTO), and CJIS-compliant cloud hosting operated by U.S. persons.
Vendors must provide detailed descriptions, expected level of effort, risk assessments, and implementation timelines for any requirements marked as "Customization Required," "Planned," or "Not Applicable." The requirements include mandatory deliverables such as design documents, interface control documents, Factory and Site Acceptance Tests, role-based training programs, and formal change control procedures. The system must maintain compliance with ANSI/NIST standards, FBI requirements, U.S. export controls, and state-specific regulations under Indiana Code. Additional optional capabilities include facial recognition with deep-learning algorithms, state SSO integration, and a modular architecture enabling independent scaling. Respondents must complete the matrix by entering their company name and marking each requirement with a single response option; multiple responses per requirement render the submission invalid.
View the file
Other files for this state and local contract opportunity
Show all 29
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| State of Indiana |
| Indiana State Police (ISP) |
| RFP # 27-85295: Automated Fingerprinting Identification System (AFIS) Modernization |
| Attachment P: Requirements Matrix |
Respondent Name:
| Steps | Details |
| 1 | Enter your company name in the yellow box provided on the top of this tab. |
| 2 | Please respond to all of the functions in the Requirements tab. Descriptions of the available responses are provided below. For each function enter an "X" under the response column that best describes your solution's ability to meet that functionality or an equivalent requiring customization. |
Existing: The Respondent's solution meets the function as an existing component of its offered product without any effort or customization.
Configuration Only Required: The Respondent's solution will meet the function with configuration of existing components.
Customization Required: The Respondent's solution will meet the function with customization.
Planned: The Respondent's solution does not presently meet the function (with or without customization), but an upgrade to the base product that will meet this function is planned within the next 12 months.
Not Addressed (NA): The Respondent's solution does not and will not address the function.
3 Use the Comments column to respond to every functionality for which you have selected the "Planned" or "Not Applicable" option, and please describe when your solution will meet the functional requirement or why it will not. Additional comments in the COmments column are not required for functional requirements with "Existing" or "Configuration Only Required" responses.
Please provide only one response per function. Multiple responses will be regarded as invalid. If you select "Planned" for any functionality, you must enter the date of the planned release in the comments column.
Requirements Requirement Type Category Requirement Description Required / Optional Existing Configuration Only Required Customization Required Planned Not Applicable Comments The Respondent must provide a detailed description of each functionality with a "Customization Required", "Planned", or "NA" response, including expected level of effort and risk to any customizations and timing if not currently available with your proposed solution.
| General | Administration | Provide administrative access for designated state employees. | Required |
| General | Biometrics | Support facial recognition. | Optional |
| General | Biometrics | Support two‑finger mobile ID. | Required |
| General | Identity & Access Management | Provide self‑service password reset. | Required |
| General | Identity & Access Management | Provide account unlock functionality. | Required |
| General | Records Restrictions | Support sealing of juvenile or restricted records. | Required |
| General | Reporting | Provide customizable reporting for user statistics, workflow totals, database size, and other ISP‑designated metrics. | Required |
| General | Training | Provide full system training with online and printable user manuals for all aspects of the system. | Required |
| General | User Interface | Provide customizable user interface (adjustable font type, size, and coloration). | Required |
| Functional | Administration | Provide an administrative dashboard with access to reports, system settings, and user permissions. | Required |
| Functional | Administrative Tools & Operations | Allow configuration of transaction priorities and per-search candidate count/image return settings. | Required |
| Functional | Administrative Tools & Operations | Provide centralized time synchronization and automated alerting with email/SMS integration. | Required |
| Functional | Biometric Modalities & Matching | Support multi‑incident record fusion to leverage highest‑quality prints per subject during matching. | Required |
| Functional | Biometric Modalities & Matching | Use matching algorithms with demonstrable performance in independent benchmarks; provide evidence during validation. | Required |
| Functional | Biometrics | Search and retain tenprint records. | Required |
| Functional | Biometrics | Search and retain palm prints. | Required |
| Functional | Biometrics | Search and retain latent impressions (fingers and palms). | Required |
| Functional | Biometrics | Retain mugshots and other person images. | Required |
| Functional | Data Intake | Receive fingerprints and data from remote livescans. | Required |
| Functional | Data Intake | Receive fingerprints and data from MBIS. | Required |
| Functional | Data Intake | Receive fingerprints and data from other related systems. | Required |
| Functional | Error Handling | Collect designated FBI errors for potential resolution and retransmission; support editing of all NIST fields for reprocessing (ERT). | Required |
| Functional | Error Handling | Provide error handling workflow for malformed or invalid data received from livescan sites. | Required |
| Functional | Face (Optional) | Support acquisition from images and short videos (common formats), automatic cropping, pose correction, and eye detection. | Optional |
| Functional | Face (Optional) | Use deep‑learning–based face matching with multi‑stage filtering and support periodic algorithm updates. | Optional |
| Functional | Face (Optional) | Provide descriptor‑only searches, lineup creation (exportable), and workflows supporting witness interviews. | Optional |
| Functional | Face (Optional) | Support tattoo image matching and descriptor‑filtered searches within the face subsystem. | Optional |
| Functional | FBI Requests | Ability to request and receive fingerprints from FBI (IRQ). | Required |
| Functional | FBI Responses | Receive FBI III records, errors, and receipts in response to tenprint, latent, and data transmissions. | Required |
| Functional | Field Operations & Mobile ID | Provide client software for mobile and fixed devices supporting 1:1 and 1:N fingerprint identification with configurable image‑quality thresholds and capture guidance. | Required |
| Functional | Field Operations & Mobile ID | Integrate mobile/fixed device workflows into central AFIS with automated routing, search, and results return. | Required |
| Functional | Identity & Access Management | Support integration with state SSO. | Optional |
| Functional | Identity & Access Management | Support MFA login. | Required |
| Functional | Image Data | Receive, process, and store Type 4 fingerprint images. | Required |
| Functional | Image Data | Receive, process, and store Type 10 images. | Required |
| Functional | Image Data | Receive, process, and store Type 15 images. | Required |
| Functional | Image Data | Receive, process, and store Type 16 images. | Required |
| Functional | Interfaces & Interoperability | Maintain ANSI/NIST EBTS compliance for interagency exchange. | Required |
| Functional | Interfaces & Interoperability | Support transport protocols SFTP, SMTP, HTTPS, XML, SOAP, REST, JMS for interface traffic. | Required |
| Functional | Interfaces & Interoperability | Provide interoperability from examiner workstations to FBI NGI and local MBIS systems (IMPD/Marion, Fort Wayne/Allen, South Bend/St. Joseph). | Required |
| Functional | Interfaces & Interoperability | Support ULW (Universal Latent Workstation) gateway for latent submissions from field devices. | Required |
| Functional | Interfaces & Interoperability | Implement interface isolation per inbound/outbound endpoint to enable independent scaling and change management. | Required |
| Functional | Manual Data Intake | Manually import fingerprints from NIST EFT files. | Required |
| Functional | Manual Data Intake | Edit or add all necessary NIST fields upon manual import. | Required |
| Functional | Manual Data Intake | Manually import fingerprint images from JPG, TIFF, PNG, PDF. | Required |
| Functional | Manual Data Intake | Add Type 1 & 2 NIST fields upon manual image import. | Required |
| Functional | Matching | Provide high‑accuracy fingerprint matching algorithms. | Required |
| Functional | NIST Data | Receive, process, and store all Type 1 & 2 NIST data fields (FBI-required and optional; custom ISP fields). | Required |
| Functional | Policy & Contractual Controls | Provide Disaster Recovery (DR) and Business Continuity (BC) for hosted services with equitable resource allocation across customers during multi‑tenant incidents, defined clearly in SLAs. | Required |
| Functional | Policy & Contractual Controls | Comply with U.S. export controls (EAR) for software, services, and related technical data. | Required |
| Functional | Project Management & Implementation | Use an industry-recognized project management framework with phase gates, status reporting, and action-item tracking. | Required |
| Functional | Project Management & Implementation | Provide design documents (RDD), interface control documents (ICDs), data dictionary, acceptance test plan, training plan, and installation/transition plan. | Required |
| Functional | Project Management & Implementation | Conduct Factory Acceptance Test (FAT) and Site Acceptance Test (SAT) with punch list tracking. | Required |
| Functional | Project Management & Implementation | Execute cutover including residual migration, stabilization period, and issuance of final acceptance certificate. | Required |
| Functional | Project Management & Implementation | Maintain formal change control for scope changes/enhancements; document approved changes via change orders. | Required |
| Functional | Project Management & Implementation | Define customer milestones such as site/network readiness, document approvals, and resource availability for FAT/SAT/training/cutover. | Required |
| Functional | Records Management | Retain criminal and applicant prints separately (per Indiana Code). | Required |
| Functional | Records Management | Edit all NIST fields within archived TCN event records for correction, update, or removal. | Required |
| Functional | Records Management | Consolidate state records within MBIS and archival systems (manual and automated). | Required |
| Functional | Records Reproduction | Reproduce full-quality fingerprints, palm prints, and mugshots from stored records. | Required |
| Functional | Records Reproduction | Support export to State of Indiana and FBI template fingerprint cards or PDF/digital formats. | Required |
| Functional | Remote Access | Support secure remote access for designated users. | Required |
| Functional | Reporting & Auditing | Provide standard administrative reports (user activity, login/logoff, stuck jobs), database counts/quality, and system statistics. | Required |
| Functional | Reporting & Auditing | Provide FBI reports (send/response statistics, response time, differential reports). | Required |
| Functional | Reporting & Auditing | Provide Enrollment reports (summary/detail, livescan quality). | Required |
| Functional | Reporting & Auditing | Provide Tenprint reports (hit/no‑hit, hit distribution, consolidation, search response times). | Required |
| Functional | Reporting & Auditing | Provide Latent reports (hit/no‑hit, case statistics, candidate position distribution). | Required |
| Functional | Reporting & Auditing | Provide Archive reports (activity, statistics, audit, user access). | Required |
| Functional | Reporting & Auditing | Support ad‑hoc/custom reporting with downloadable tooling; centralize audit trails for administrator access. | Required |
| Functional | Security | Meet or exceed latest FBI CJIS security requirements. | Required |
| Functional | Security | Enforce password complexity, expiration, and login attempt limits. | Required |
| Functional | State Responses | Transmit state responses, III records, errors, and other necessary files to remote livescans, MBIS, CCH, and related systems. | Required |
| Functional | System Integration | Provide interface connectivity with external providers. | Required |
| Functional | System Integration | Provide interface connectivity with external vendors. | Required |
| Functional | System Integration | Maintain compliance with all functions of current interface with state CCH system. | Required |
| Functional | Training & Documentation | Deliver role-based training for administrators, tenprint operators, latent operators, and archive users, including curriculum outlines and competency objectives. | Required |
| Functional | Training & Documentation | Provide face subsystem training (if acquired), including optional policy/governance modules. | Required |
| Functional | User Management & Administration | Provide a central administrative console to manage licensing, users & groups, decision-logic thresholds, and reporting. | Required |
| Functional | User Management & Administration | Provide an administration console with dashboards, user management, auditing, configuration settings, and job/service control. | Required |
| Functional | Verification | Provide multi-level verification capability (e.g., double blind, supervisor review, consolidation verification). | Required |
| Functional | Workflow & Transaction Processing | Support criminal arrest event workflow (search local and FBI; retain per policy). | Required |
| Functional | Workflow & Transaction Processing | Support applicant background workflows (NFUF, MAP, SMAP) with retention rules (local-only or local+FBI). | Required |
| Functional | Workflow & Transaction Processing | Support mobile identification workflows for fixed/mobile devices enabling both 1:1 and 1:N searches. | Required |
| Technical | Card Scanning | Scan fingerprint hard cards into NIST format at 500 or 1000 ppi; acquire Type 1 & 2 data from CCH-generated text files using barcode reference. | Required |
| Technical | Image Specifications | Receive and transmit fingerprints at 500 or 1000 ppi in accordance with FBI requirements. | Required |
| Technical | Maintenance & Support | Provide 24×7×365 backend support with diagnostics, case tracking, escalation processes; deliver preventive maintenance, algorithm updates, and corrective patches. | Required |
| Technical | Monitoring, Storage & DR Objectives | Maintain centralized logging, messaging, and monitoring services; support threshold-based health monitoring with email/SMS alerts. | Required |
| Technical | Monitoring, Storage & DR Objectives | Database failover objectives must meet RPO not greater than 5 seconds and RTO not greater than 30 seconds. | Required |
| Technical | Network & Infrastructure | Provide central-site WAN and remote-site bandwidth sized to operational workload; support site-to-site VPN; optional private connectivity as needed. | Required |
| Technical | Network & Infrastructure | Provide DNS-based failover/rerouting during disaster recovery events. | Required |
| Technical | Network & Infrastructure | Maintain automated backups with point-in-time recovery and geo-redundant storage. | Required |
| Technical | Performance & Sizing | Meet or exceed baseline capacity and throughput targets derived from projected workloads; provide capacity planning documentation and performance testing results. | Required |
| Technical | Performance & Sizing | Support real-time or near real-time identification/matching per operational requirements. | Required |
| Technical | System Architecture & Hosting | Provide CJIS-compliant cloud hosting operated by U.S. persons. | Required |
| Technical | System Architecture & Hosting | Implement geo-redundant disaster recovery with automated failover (active-active or active-passive acceptable). | Required |
| Technical | System Architecture & Hosting | Participate in an evergreen program including periodic OS/DB/app updates and hardware refreshes. | Required |
| Technical | System Architecture & Hosting | Provide a modular, scalable architecture enabling independent scaling of biometric and non-biometric services. | Optional |
| Technical | System Architecture & Hosting | Employ managed database services with built-in high availability and disaster recovery. | Required |
File details come from the government source that posted it. Updated .