The vendor is required to provide that data records linkage tool requirements:
1. Functional requirements
• Data validation and standardization processes.
o Feature scaling to standardize and normalize data across a variety of datasets from various sources (range of values, gender, age groups, etc.) (l)
• Record matching algorithms and accuracy expectations.
o Algorithm must evaluate datasets and match records based on probabilistic methods.
o Algorithm must learn and predict based on supervised, unsupervised learning models.
o Algorithm must provide means to measure accuracy of output such as precision, recall metrics. need a mechanism to determine the accuracy of the match, statistical methods used (example: precision, recall, confusion matrix) (h)
• Integration capabilities with existing systems.
o Ability to ingest data from across a variety of data sources (json, csv, tab delimited, and pipe delimited).
o Ability to address different file encodings: utf-8, utf-16, and latin-1 (m)
o Need a configuration driven approach that can adjust and manage acceptable probability match % and filter records that match the criteria. must support data siphoned to different queues such as manual review, pass, fail, etc. (h)
o Generate and maintain a unique id that
a. Is internal to the matching process and is refreshed every time an individual match is identified (h)
b. Ability to store the unique id and reference ids for tactical operational purposes including investigational, debugging, optimization, etc.(h)
c. Is truly unique so there is no scope for duplication (h)
o Action on non-matched records
a. Store non matched records for operational optimization (l)
2. Non-functional requirements
• Performance benchmarks (e.g., data processing speed, latency)
o Must be able to process match algorithm and generate unique ids in within operational SLAss (h)
• Scalability to handle increasing data volume
o The algorithm must be able to evaluate and process complex datasets typically 50 – 100 features and millions of records (h)
• Security measures, controls (e.g., data encryption, access controls)
o Ability to encrypt sensitive information in compliance with data privacy and security requirements (h)
3. Compliance, privacy requirements
• Must address DULA privacy and security requirements addressed in section vi part a (h)
• Must be in compliance with state and federal regulations listed in section v part a (h)
4. Technical/architectural requirements: (h)
• Compatibility with existing it infrastructure.
• APIs and data exchange protocols.
• Support for cloud-based or on-premises deployment including initial setup and configuration.
- Contract Period/Term: 3 years
- Questions/Inquires Deadline: April 07, 2025