Attch J2 Currencyreader.gov Site Defined.pdf
PDF 162 KB Posted
- Attached to
- RFQ: Currency Reader Information Management System (CRIMS) Support, Enhancements, and Upgrades
- Solicitation number
- 030ADV26Q0024
- Issued by
-
Library of Congress
About this file
Attachment J2 details technical requirements for the Currencyreader.gov website, a web-based platform for requesting free currency reader devices for the National Library Service (NLS). The webform must be bilingual (English and Spanish), include specific required fields such as applicant and certifier information, and incorporate digital signature functionality. The system will generate submission confirmations, validate entered information, and provide error prompts for incomplete submissions.
The solution requires integration with the existing CRIMS (Customer Records and Information Management System) database, with capabilities for NLS staff to review, edit, and validate applications before import. Key technical specifications include: maintaining all application records permanently, supporting data export to CSV, creating analytics dashboards, updating the CRIMS database every 10 minutes, and processing approximately 200 entries per week (10,000 shipments annually). The new Microsoft Azure user interface must maintain legacy system workflows, permit manual record editing, and support role-based access controls with least privilege principles.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFQ 030ADV26Q0024 - Amend 0002.pdf | ||
| QandA Release 1 - 030ADV25Q0024 - CRIMS - Final.xlsx | XLSX spreadsheet | |
| Attch J5 Price Quote Tmpl - Amend 0002.xlsx | XLSX spreadsheet | |
| RFQ 030ADV26Q0024 - Amend 0001.pdf | ||
| Attch J6 Sol Q A Matrix.xlsx | XLSX spreadsheet | |
| RFQ 030ADV26Q0024.pdf | ||
| Attch J5 Price Quote Tmpl.xlsx | XLSX spreadsheet | |
| Attch J7 - Agile Methodology.pdf | ||
| Attch J4 LOC OCIO IT Sec Dir 5-410.1.pdf | ||
| Attch J3 LOC CRIMS CMP v1.2.pdf | ||
| Attch J1 CRIMS SLA Draft.docx | DOCX document |
Show all 11
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
Attachment J2
Currencyreader.gov Site Defined
Page | 1
1. MAINTAIN WEBFORM (CURRENCYREADER.GOV)
Webform (Currencyreader.gov) shall be maintained in English and Spanish.
Submitted webform shall generate a confirmation to the applicant upon successful submission and contain a unique identifier for tracking.
Webform shall provide prompts for improperly completed forms or unsuccessful submission attempts back to sender for remedy or escalation for help support. Prompts shall state specific field error or diagnostic statement to assist with troubleshooting.
Webform shall incorporate digital signature via a notice that clicking "Submit" acknowledges that the user agrees to the terms and conditions of the website/webform and includes a link to those terms and conditions.
Digitally signed forms shall be stored by the system and include retrieval capacity for certifying history for a particular certifier.
Webform shall validate information entered as the applicant certifier initiates the form to request a free currency reader device.
Form includes following required fields for successful request submission – o Applicant Name o Applicant Street address, city, state and zip code, o Phone (included but not a required field) o Email address as a required field for applications submitted via the webform only for use with communication with the applicant. Certifier email may be substituted as necessary.
o Radio button(s) to select Yes/No certification of prior and/or current NLS membership to activate Certification requirements.
o Radio button for self-certification of US citizenship.
o Certifier Name o Certifier Organization o Certifying Organization Street Address, email, and phone number o Certifying Organization City, State and Zip Code o Digital Signature capability -- implemented as a notice that clicking "Submit" acknowledges that the user agrees to the terms and conditions of the website/webform, and includes a link to those terms and conditions o Radio Button for Certifier to confirm a hand-delivered transaction for a currency reader device for NLS review and validation in CRIMS.
2. NLS REVIEW AND VALIDATION
Webform solution shall permit NLS staff or other reviewers to review all forms submitted by applicants and certifiers for batch processing for the purposes of validating if the application meets eligibility requirements. This step shall occur prior to the record being imported into CRIMS. The review and approval workflow shall allow for the review, editing, updating, or deleting of all patron data in the application by NLS staff. The system shall allow for the viewing by NLS staff of all pending, approved, and denied applications in a sortable, filterable, and searchable manner.
11/26/2025
Attachment J2
2026-NLS-0076 Currencyreader.gov Site Defined
Page | 2
3. DATA AND ANALYTICS
Solution shall include capabilities for user to perform data analysis and reporting activities on a common web interface. This includes the ability to export all data in the system into a Comma Separated Value (CSV) file and dashboards to track metrics. The system shall maintain all applications as records and shall not delete legacy records regardless of if they were approved, denied, or no action was taken.
4. INTEGRATION WITH CRIMS USER EXPERIENCE
The new MS Azure UI shall integrate with the legacy CRIMS system operations to permit users of the existing CRIMS system to edit and accrete records to the existing CRIMS patron record database based on the approved data in the application form. The update shall update the CRIMS database no less than once every 10 minutes. Average accretion rate to patron record database is approximately 200 entries per week resulting in approximately 10,000 shipments per year. New and existing patron records shall be tied to a unique patron ID in the same manner as the legacy workflows. Solution shall be compatible and interoperable with CRIMS legacy database and system architecture to maximize efficiencies at the patron record level and in the cloud including by:
Permitting CRIMS users to manually edit, manage duplicate/multiple patron entries, issue replacement devices to legacy patron applicants.
Maintaining legacy records and history for all device transactions.
Maintaining Service Level Agreement and Service Availability with parity to CRIMS
Maintain role-based reporting capability for both front end and backend CRIMS users according to least privilege.
File details come from the government source that posted it. Updated .