Amendment 1 RFP 16500-00015033 Ready for review.pdf
PDF 249 KB Posted
- Attached to
- Hosting Services for ArchivesSpace
- Solicitation number
- S-16500-00015033
- Issued by
- Marion County, Oregon
About this file
This is Amendment 1 to RFP S-16500-00015033 issued by the State of Oregon's Secretary of State Archives division for hosting services of ArchivesSpace software. The amendment adds three key components to the original solicitation: Attachment F (a CSV file containing approximately 1,600 accession records currently stored in FileMaker Pro with an estimated 22 fields, of which approximately 370 records lack accession dates), Attachment G (a PDF of finding aids serving as organizational tools containing detailed metadata about archive collections), and defined Splunk integration level requirements. The amendment modifies Section 2.3 (Scope of Work), Section 2.2.2 (Project Specific Definitions regarding Finding Aids), and Section 3.1.3 (Certification Requirements). The solicitation requires proposers to demonstrate the ability to integrate with the Agency's authentication and observability systems, specifically Microsoft Entra ID Single-Sign-On (SSO) and Splunk. According to the related contract opportunity summary, the pre-proposal conference is scheduled for January 20, 2026, with questions due by January 27, 2026, and proposals due February 24, 2026, at 10:00 AM PT through OregonBuys. The contract involves an initial five-year term with potential renewal for additional five-year periods, with project commencement expected by May 1, 2026.
The Splunk integration level requirement encompasses three specific functions: SOS User Access Logging (generating secure, tamper-proof logs of user login events with export capability), SOS User Audit Logging (maintaining detailed, searchable logs of user actions for compliance and forensic analysis), and Operational Health Monitoring (continuous monitoring of platform health with integration capabilities for external monitoring tools). Proposers must comply with CIS Control v8.x IG2 standards and WCAG 2.1 AA accessibility requirements, with all services and data required to be stored within the United States with no overseas access permitted. The evaluation criteria total 200 points distributed across proposer qualifications (40 points), key persons qualifications (30 points), approach and management plan (40 points), staffing plan (25 points), work plan and schedule (30 points), and cost-related factors (35 points). Proposers must demonstrate five years of experience providing hosting services for similar institutions and have at least five current customers using comparable ArchivesSpace hosting services. No incumbent vendor is mentioned, and no specific set-aside designations for disadvantaged enterprises are indicated.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFPAttA Sample Contract Host ArchivesSpace.docx | DOCX document | |
| Amendment 2 RFP 16500-00015033.pdf | ||
| RFPAttE Cost Proposal Submission Form ArchivesSpace Hosting.xlsx | XLSX spreadsheet | |
| RFPAttC - Proposer Information and Certification ArchivesSpace.docx | DOCX document | |
| RFPAttB - Disclosure Exemption Affidavit ArchivesSpace.docx | DOCX document | |
| RFPAttD Reference Check Option 2.docx | DOCX document | |
| Attachment F-Amendment 1 OSA_AccessionsRegister_CSV_Export.csv | CSV file | |
| Attachment F-Amendment 2 OSA_AccessionsRegister_CSV Headers_Export.csv | CSV file | |
| RFP Addendum 2.pdf | ||
| RFP 16500-00015033 Hosting for ArchivesSpace.pdf | ||
| Attachment G Finding aids PDF.zip | ZIP file |
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
SoS Version Dated 01/25/2019
RFP: S-16500-00015033– AMENDMENT #1
SECTION 1: PURPOSE
The purpose of this amendment is: to add accession record CSV file as Attachment F, add finding aids PDF as Attachment G and to define Splunk integration level requirement. The accession file, finding aid file and Splunk integration level will assist proposers with scope of work required.
1.1 MODIFICATION OF SECTION 2.3 Scope of Work
1.2 MODIFICATION OF SECTION 2.2.2 Project Specific Definitions / Finding Aid means
1.3 MODIFICATION OF SECTION 3.1.3 Certification Requirements / Splunk integration
SECTION 2: MODIFICAITONS
Section 2.3 Scope of Work and 3.1.3 Certification Requirements are modified as follows. New language is indicated by bold underlined font, deleted language is indicated by strikethrough font.
Section 2.3 Scope of Work
• One-time data migration for approximately 1,600 accession records currently in FileMaker Pro, see (Attachment F) CSV file. We estimate 22 fields.
Approximately 370 records do not have accession dates;
Section 2.2.2 Project Specific Definitions
Finding Aid means- an organization tool, a document containing detailed and processed metadata and other information about a specific collection of records within an archive See (Attachment G) PDF.
Finding aids are created as the primary tool for Agency customers to know what collections the Agency has in the Agency’s Archives and discover the contents of each collection. Over decades, the Agency has authored approximately over 100 200 finding aids.
Section 3.1.3 Certification Requirements
• Proposer must integrate with Agency authentication & observability systems. Proposer must provide a statement that proposer is able to integrate with Agency authentication & observability systems listed below:
Microsoft EntraID Single-sign On (SSO)
Splunk
Splunk integration level requirement is defined as follows:
https://learn.microsoft.com/en-us/entra/fundamentals/what-is-entra https://www.splunk.com/en_us/products/enterprise-security-essentials.html
SoS Version Dated 01/25/2019
1. SOS User Access Logging: The system must generate secure, tamper-proof logs of SOS user login events, including authentication method, access point details (IP, device, location), timestamps, and session information, with export capability for compliance and audits.
2. SOS User Audit Logging: The system must maintain detailed, searchable audit logs of user actions—such as configuration changes, data modifications, and administrative tasks—capturing user identity, action performed, timestamp, and affected resources for compliance and forensic analysis.
3. Operational Health Monitoring: The system must continuously monitor platform health and availability through operational logs, error reporting, performance metrics, and alerting mechanisms, while supporting integration with external monitoring tools.
SECTION 3: ATTACHMENTS
Attachment F: OSA AccessionsRegister CSV
Attachment G: Finding Aids PDF
| SECTION 1: PURPOSE |
| SECTION 2: MODIFICAITONS |
| SECTION 3: ATTACHMENTS |
File details come from the government source that posted it. Updated .