Senate Document Management System

Amendment / Modification

This document is Amendment 002 to Solicitation 2025-R-060, dated April 3, 2026. It acknowledges receipt of Amendment 001 dated July 30, 2025.

• Section A – Solicitation/Contract Form: Block 10, "ACKNOWLEDGEMENT OF AMENDMENTS", has been updated to reflect the issuance of Amendment 002.

No changes to proposal deadlines, requirements, or evaluation factors are indicated by this amendment. It serves as an administrative update to the solicitation record.

Amendment / Modification

This amendment modifies the solicitation "2025-R-060" and introduces changes related to proposal preparation and evaluation, specifically concerning a Product Demonstration requirement.

Key changes include:

• Revising Section L.6 (Proposal Preparation) to inform Offerors of potential participation in a Product Demonstration.

• Adding Section L.7.1.5 to provide instructions for the Product Demonstration requirement.

• Revising Section M.3 (Acceptable Procedures) to address unacceptable ratings.

• Revising Section M.4 (Evaluation Procedures) to incorporate the evaluation of the Product Demonstration.

• Modifying Section M.5.1 (Technical and Cost Evaluation Areas/Factors) to add "Product Demonstration" as Factor 4 and renumber "Price" as Factor 5.

• Adding Section M.5.1.5 specifically for the "Product Demonstration - Factor 4".

• Renumbering the Price factor to Section M.5.1.6, "Price - Factor 5", and including the right to reject proposals.

• All changes are indicated in red text and highlighted in yellow.

• Section L.6 (Proposal Preparation)

• Section L.7.1.5 (Product Demonstration)

• Section M.3 (Acceptable Procedures)

• Section M.4 (Evaluation Procedures)

• Section M.5.1 (Technical and Cost Evaluation Areas/Factors)

• Section M.5.1.5 (Product Demonstration - Factor 4)

• Section M.5.1.6 (Price - Factor 5)

Offerors should note the inclusion of a Product Demonstration requirement and its impact on proposal evaluation. The deadline for receipt of offers is not extended by this amendment. All other terms and conditions remain unchanged.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the "2025-R-060 Bidders Questions and Answers" solicitation for a Document Management System (DMS) for the Senate.

• Migration Scope: The legacy repository contains 1.8 TB across 2 million objects. Migration includes documents, metadata, user/role mapping, and workflows.
• User Licensing: The government requires pricing for 100 concurrent users (CLIN 001) and expects offerors to state any underlying named user or tier assumptions. Current production supports 42 active users.
• System Preference: There is no preference for cloud-based or on-premises solutions; hybrid or modular approaches are acceptable.
• Go-Live Timeline: A go-live of four months post-award is ideal, but offerors should propose a realistic timeline.
• Data Sources: The primary migration source is Hyland OnBase. Other data sources like SharePoint or shared drives are not part of this migration.
• OCR Requirements: Approximately 10% of documents are handwritten, and 90% are scanned. The system must support advanced OCR capabilities.
• Past Performance: References should be for projects performed within the last 3 years, but contracts within the last 5 years are acceptable.
• Cloud/FedRAMP: While FedRAMP certification may be favorably evaluated, the solution must meet all mandatory requirements and comply with Senate cybersecurity SOPs. A hybrid (on-prem/cloud) architecture is permitted.
• Scanning: Scanning is to be done on-site at Senate offices. Offerors can propose their own scanning solution or one that integrates with existing scanners.

These clarifications provide essential details for offerors to refine their proposals regarding data migration, user licensing, technical requirements, and submission guidelines. Key deadlines and evaluation factors remain as outlined in the original solicitation.

Solicitation / RFP / RFQ

This solicitation is for a comprehensive solution to modernize the United States Senate's document management capabilities. The Senate is seeking to replace its current on-premises Hyland OnBase system with a new solution that addresses unique workflows, business needs, and technical requirements across diverse operational units. The proposed solution should support document management, workflows, and operational needs.

• Scope of Work: Includes providing software licenses, tools, and components; implementing and configuring the proposed solution; establishing workflow replacements and improvements; migrating all content, metadata, users, roles, and permissions from the legacy system; executing a tailored training program; establishing reporting and analytics; providing ongoing technical support and maintenance; and supporting the legacy OnBase system during transition.

• Technical Requirements: Detailed in Attachment J-02, Requirements Matrix, which must be completed by the offeror. Requirements are designated as Mandatory (M) or Optional (O).

• Performance Standards: Must meet or exceed Service Level Agreement (SLA) requirements specified in Attachment J-03.

• Contract Tasks: Include Assessment, Discovery and Gap Analysis; Solution Implementation; Data Migration; Testing; Training Program; Documentation; Acceptance Period Support; and Technical Support and Maintenance.

• Contract Type: Firm Fixed Price (FFP) and Labor Hour (LH).

• Term: Base period plus five (5) one-year option periods.

• Estimated Value: Not explicitly stated, but pricing is detailed in Section B.

• Proposal Submission: Technical, Price, and Administrative Proposals are due via email by August 1, 2025, at 12:00 pm EST.

• Technical Proposal: Must include Technical Approach, Management Approach, Key Personnel Resumes, and Past Performance. No pricing information is allowed.

• Price & Administrative Proposal: Must include pricing details and administrative information.

• Evaluation Criteria: Best value, competitive source selection based on Technical Approach (most important), Management Approach, Past Performance, and Price. Technical factors combined are more important than price.

• Key Deadlines: Technical and Administrative Questions due July 16, 2025. Proposals due August 1, 2025.

• No specific set-aside is mentioned.

• Attachments include: J-01 U.S. Sergeant at Arms Standard Operating Procedures (SOPS) for Cybersecurity, J-02 Requirements Matrix, and J-03 Service Level Agreement with Incentives and Penalties.

• Offerors must acknowledge all solicitation amendments.

• Proposals must allow for a minimum of ninety (90) calendar days for acceptance.

Form / Attachment / Pricing Sheet

This document, "Attachment J-01 U.S. Sergeant at Arms Standard Operating Procedures (SOPS) for Cybersecurity," outlines the comprehensive cybersecurity policies and procedures for the U.S. Senate Sergeant at Arms (SAA) and its contractors. It details the requirements for protecting Senate information systems and data.

• Senate Information Systems Security Policy: Covers general security goals, scope, and responsibilities for Senate unclassified systems and networks.
• SAA Cybersecurity Policy: Details the protection of information throughout its lifecycle and the responsibilities of SAA departments.
• Office of the Chief Information Officer (CIO) Cybersecurity Policy: Outlines objectives for security, integrity, and accountability of Senate IT resources.
• Non-Disclosure of Sensitive Information: Defines sensitive information and prohibits its disclosure.
• Access to Senate Office Information: Governs how SAA support staff and contractors access Senate office systems.
• Project Management: Requirements for integrating security into projects.
• System Administration: Security measures expected from System Administrators.
• Computer User Guidelines: Responsibilities for all users accessing Senate computers and networks, including basic computer care and securing work areas.
• Contractor Responsibilities for Cybersecurity: Extensive requirements for contractors, including adherence to NIST standards, developing cybersecurity plans, implementing security measures, incident response, training, and remote access procedures.
• Senate System Remote Access Authorization Form: A form to authorize contractor remote access to CPS servers.
• Cybersecurity Responsibilities Acknowledgement: A form for users to acknowledge their understanding of responsibilities.

This document is critical for any bidder or contractor involved with the U.S. Senate Sergeant at Arms, particularly those dealing with information technology systems, data, or services. It establishes the cybersecurity standards, policies, and procedures that must be adhered to, including specific requirements for contractors regarding risk assessment, data protection, incident response, and software updates. Bidders must understand and plan to comply with these extensive cybersecurity mandates as part of their proposal and contract execution.

Form / Attachment / Pricing Sheet

This document, "Attachment J-02 - Requirements Matrix.xlsx", outlines the technical, functional, and operational requirements for the Senate Document Management System (SDMS). It serves as a detailed checklist for offerors to indicate how their proposed solutions meet or exceed each specified requirement.

The matrix is organized into several sections, detailing requirements for:

• General Requirements: Availability, scalability, user portals, browser/mobile compatibility.
• Analytics and Reporting: Logging, usage reports, custom reporting, log export.
• Document Storage and Retrieval: Integration, native format storage, version control, retention, metadata tagging.
• Document Security: Secure sharing, audit logs, cybersecurity compliance.
• Interface and User Experience: User-friendly design, customizable views, virtual folders, OCR, DAM, user management.
• Document Search: Consistent search across clients, metadata/content search, advanced query types, result export, OCR for searchability.
• Document Scanning: Native/third-party scanning support, batch workflows, automated indexing, image quality, OCR for scanned documents.
• Configurable Workflows: User-friendly workflow management, dashboards, conversion settings, approval workflows, rejection loops, external system integration, alerts, duplicate detection.
• Stakeholder Use Cases: Specific requirements for Historical Records, Finance/AP, Batch Scanning, Systems Administration, Constituent Services, Fleet Receipts, and Damage Photo workflows.
• Additional Requirements: Real-time alerts, batch ingestion, file validation, user management, post-ingestion OCR, duplicate detection, retention schedules, search interface, DAM, APIs, dashboards, conversion settings, approval workflows, rejection loops, external system mapping, architecture diagrams, and awareness of technology advancements.
• SLA Material: Uptime, search performance, ingestion time, response times, error notification, incident resolution, effort estimates, response/resolution windows, and retention policy adherence.

Offerors must use this matrix to detail their compliance with each mandatory (M) or required (R) requirement. For each requirement, bidders must select "Does Not Meet", "Meets", or "Exceeds" and provide comments. Optional (O) requirements are encouraged but not mandatory. This document is critical for proposal preparation and will be a key factor in the evaluation of the proposed solution's capabilities against the government's needs.

Form / Attachment / Pricing Sheet

This document, "Service Level Agreement with Incentives and Penalties," outlines the performance metrics, escalation procedures, and support commitments expected from the Contractor for the Senate Document Management Solution (SDMS). It defines the standards for solution availability, incident response and resolution, maintenance, reporting, and contractor responsibilities for solution failures.

• Definitions: Clarifies terms such as Uptime, Downtime, LOE (Level-of-Effort), NTE (Not-to-Exceed), and Severity Levels (1-4).
• Solution Availability: Mandates 99.9% or higher availability, including scheduled maintenance, with specific targets for unplanned downtime.
• Incident Response and Resolution: Details initial response times and resolution objectives based on incident severity, with a requirement for 98% of Severity 1-3 incidents to be resolved within defined windows.
• Escalation Process: Outlines steps for escalating unresolved incidents to senior technical personnel, management, and the COR.
• Maintenance: Specifies requirements for planned downtime notice and scheduling outside of normal business hours.
• Reporting: Requires monthly reports on uptime, incidents, response/resolution times, root cause analysis, user activity, workflow metrics, and quarterly risk mitigation reports.
• Penalties and Incentives: Defines a penalty schedule for failing to meet SLA metrics and a potential bonus for full SLA compliance.
• Labor Estimates: Requires written LOE estimates for additional tasks, including labor categories, hours, rates, and NTE costs, subject to COR approval.

This SLA establishes the performance standards and consequences for non-compliance that will govern the contract. Bidders must understand these requirements to accurately estimate costs, develop their technical approach, and assess their ability to meet the government's expectations for service delivery and performance. The penalty and incentive structure directly impacts the financial viability and success of the contract.

Form / Attachment / Pricing Sheet

This document is a Past Performance Questionnaire (PPQ) for Solicitation 2025-R-060, "Senate Document Management System." It is used to gather information from offerors regarding their past performance on previous contracts.

• Contract/Project/Task Order Information: Fields for the offeror to complete regarding the contract for which they are seeking a past performance reference (e.g., Name of Offeror/Subcontractor, Contract/Task Order Number, Contract Type, Project Name, Period of Performance, Brief Description of Work).
• Reference Information: Fields for the reference to complete regarding their company and role in managing the contract.
• Performance Assessment: A series of questions (1-8) requiring the reference to assess the contractor's performance using a rating scale (Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory, Not Applicable/Not Observed). Questions cover areas such as fulfilling requirements, delivery, problem-solving, personnel expertise, and overall program management.
• Contractor Re-hire Question: A question asking if the reference would contract with the contractor again, with a space for explanation if the answer is no.
• Further Comments: A section for any additional pertinent comments.

Bidders must ensure that the references they designate complete this questionnaire accurately and promptly. The information provided in this questionnaire will be used as Source Selection Information to evaluate the offeror's past performance, which is a critical factor in the source selection process for Solicitation 2025-R-060. The completed questionnaire should be emailed to acquisitions@saa.senate.gov within five (5) days of receipt.