Inquiries and Answers for RFP AADA 2027-0086 (Mod 4).pdf

PDF 286 KB Posted

Attached to
Archives Collection Management Database
Solicitation number
RFP AADA 2027000086 5
Issued by
Denver County, Denver City, Colorado

About this file

This document is an Inquiries and Answers (Q&A) response for RFP AADA 2027-0086, issued by the Colorado Department of Personnel & Administration (DPA) on behalf of the Colorado State Archives (CSA), concerning a cloud-based archival records management system. The State seeks to migrate approximately 4.3 million catalog records currently maintained in Proficio version 8.22.9035 (a Re:Discovery Software product) to a new cloud-based collections management system capable of supporting internal staff access and public portal functionality. The contract will include data migration, system implementation, integration, and ongoing managed services. The initial contract term is estimated to begin March or April 1, 2027, and end June 30, 2028 (to allow data migration prior to an estimated go-live date of July 1, 2027), with extension terms of one year each beginning July 1st and ending June 30th thereafter, for a total contract duration not to exceed approximately ten years and four months. The contract requires firm-fixed pricing for the entire term, including all extension options, with no guaranteed escalation or renegotiation; vendors are permitted to submit tiered pricing reflecting anticipated reasonable cost increases across the contract period.

Pricing must be submitted on a provided Exhibit C workbook and should include implementation, historical data migration and verification, and any integrations as separate line items; the State declined to disclose its established budget or not-to-exceed amount, instructing vendors to submit their best offer. The current incumbent is ReDiscovery/Proficio. The existing environment contains approximately 733 collection-level records, 4,679 series-level records, 125,033 file unit (box) records, and 4,046,184 item-level records stored in SQL tables totaling approximately 23 gigabytes; the export will include catalog metadata only, with no digital media attachments. Internal user licensing will not likely exceed 10 users (with concurrent usage typically around 5), and public portal users will be unlimited and unauthenticated. The system must achieve WCAG Level AA accessibility compliance by go-live, support search functionality returning results in under 10 seconds, maintain maximum downtime of two business days per incident (with planned maintenance conducted outside business hours), and comply with Colorado Special Provisions and Insurance requirements, which are stated as nonnegotiable; vendors may submit redlines on other contract terms but acceptance is not guaranteed. No set-asides are indicated in this solicitation.

View the file

Other files

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

DPA Solicitation #:

RFP AADA 2027*0086

Cloud-Based Archival Records Management System for Colorado State Archives

INQUIRIES AND ANSWERS

CHANGES IN RED

Question 1: Administrative Information §§2.4 and 6.4; Exhibit D Section 2.4 permits proposed contract redlines, while §6.4 states willingness to contract without exception and refers to nonnegotiable Special Provisions. May a proposal containing disclosed insurance, liability or audit exceptions remain eligible for evaluation? Please identify which provisions are nonnegotiable and clarify the applicable exhibit and section references in §6.4.

This question requests the process only, not acceptance of an exception.

Answer 1: Yes, proposals containing redlines or exceptions to terms such as insurance, liability, or audit will remain eligible for evaluation, provided the Offeror complies with Section 2.4.2 by submitting a redlined contract, proposed substitute language, and an explanation of the changes with its proposal. Per Section 2.4 and Section 6.4, the State does not guarantee acceptance of proposed redlines; final terms are subject to negotiation with the awarded vendor. The Special Provisions and the Accessibility provisions included in the Draft Contract (Exhibit D) are strictly nonnegotiable. Additionally, the reference in Section 6.4.1 to "Exhibit B" is corrected to Exhibit D (Draft Contract). The reference to "Section 10" should refer to "Section 19” and pertains to the Draft Contract rather than this Administrative Information document.

Question 2: Annual total cells G31:P31 appear to sum rows 11–28, excluding implementation, migration and integration rows 8–10, while grand total Q31 includes those rows. Will a corrected workbook be issued? Please specify how the initial term ending June 30, 2028 and possible total duration of 10 years and 4 months map to the ten annual columns, including any partial year.

Answer 2: Yes, a corrected workbook will be issued with this posting. The initial term will begin upon execution of the contract, estimated March or April 1, 2027, and end June 30, 2028 to allow for data migration prior to the estimated go-live date of July 1, 2027. The remaining contract terms will be periods of 1 year, which begin July 1st and end June 30th of each year.

Question 3: Exhibit A §§2.2 and 3.1; Administrative Information §5.2; Exhibit B §4 Are the similar-sized entity and more-than-two-years’ experience criteria scored preferences or pass/fail minimums? May an offeror propose a newly built system with accurately disclosed current functionality and implementation milestones, or must the proposed system already be in production at proposal submission?

Answer 3: These are scored preferences. Any solution must be in production and ready for use at time of bid.

Question 4: Exhibit A §§1.2.2, 3.1.2–3.1.5, 3.4 and 3.5.1 Please provide the source data dictionary or schema, export formats, approximate data size, hierarchy rules and known data-quality issues needed to estimate migration. Which party provides the export and cleanup, and must changes be captured during migration? What evidence will satisfy the complete-transfer audit? Does the retained preservation system require API, preview or download integration beyond catalog permalinks, and who provides interface access?

Answer 4: According to our database team, the size of the SQL tables supporting our current client is about 23 gigabytes. Responsibilities on data cleanup will be discussed once a pre-migration audit has been performed.

CSA can likely perform some of the data clean-up, but depending on what is discovered, the vendor may need to assist with some clean-up as well.

Our Preservation system operates independently from our catalog, and does not require any collaboration between the two.

Question 5: Exhibit A §§3.1.1.5, 3.1.1.8 and 3.5.2 What concurrent load, query mix and measurement method apply to the search-time and near-instant publishing requirements? Is the two-business-day downtime limit measured per incident, month, year or contract term, and how are planned maintenance and dependency outages treated?

Answer 5: Our system is used consistently through the day by 3-4 staff members performing queries and editing records. The public will be querying the same database through a public portal, and the site should be able to support that amount of traffic. Our goal is to provide fast and effective customer service.

Our downtime requirements apply by incident. We understand that planned maintenance is part of routine service, so we would ask that it be performed outside of business hours (Monday- Friday, 8am-5pm MT), and with advanced notice.

Question 6: Exhibit A §3.2; Exhibit D Information Technology Provisions Please identify the applicable data classifications and regulated-data categories, required hosting boundary and any agency identity integration. Will an annual SOC 2 Type II audit be required for this project? If an alternative audit is permitted, what scope and evidence would the State Information Security Office require? Please confirm which template HIPAA, FTI, CJI and FERPA provisions or associated forms apply to this catalog work.

Answer 6: The system will only contain indexing information to let users know a record exists, it will not contain any sensitive data itself. Therefore, HIPAA, FTI, CJI and FERPA provisions do not apply to this project. For hosting boundaries, we require all data to be stored in CONUS.

Question 7: Is there an incumbent?

Answer 7: Yes, our current subscription is with ReDiscovery/Proficio.

Question 8: Does the Colorado Department of Personnel & Administration have an established budget, estimated contract value, or maximum funding allocation?

Answer 8: Please submit your best offer. DPA is not able to disclose the available budget at this time. Please use the provided pricing sheet for software licensing and add-on features.

Question 9: Exhibit A 2.2; Exhibit B responses 1 and 3 and 2.1.4 May RGREALTECH LLC propose as prime with a named archival-software subcontractor and use the relevant organizational experience and client recommendations of that partner, clearly attributed? Must the prime independently meet any minimum experience or reference requirement?

Answer 9: Yes, with a description of how relationship and workload is distributed.

Question 10: Administrative Information 1.1.2 and 4.3.1.1.2.1 VSS registration is optional, but the executive summary requests a CORE VSS number. May an unregistered offeror state not registered without affecting responsiveness?

Answer 10: VSS registration is optional to submit a proposal and does not affect consideration for a contract. If the awarded vendor is not in VSS, then they must be added prior to execution of a contract.

Question 11: Administrative Information 4.3.1.1.3 This identifies a W-9 as Exhibit E, but only the administrative document and Exhibits A through D are posted. Is a current standard IRS Form W-9 acceptable?

Answer 11: Yes, a current, standard IRS Form W-9 is acceptable

Question 12: Exhibit A 3.5.2.1 What measurement period applies to the maximum two business days of system downtime, and does it include planned maintenance?

Answer 12: Two business days per incident. One business day is equivalent to one week day (Monday-Friday), between 8 am and 5 pm, mountain time. The two business days of downtime does not include planned maintenance;CSA expects that planned maintenance be completed outside of business hours (on evenings and weekends).

Question 13: Exhibit A 1.3.2; draft contract 2.C Exhibit A anticipates ten years and four months, while the draft contract states five years absent prior approval. Will the final contract align with the solicitation term?

Answer 13: Yes, the final contract will align with the solicitation term. The draft contract posted is a template and will be modified in collaboration with the awarded vendor.

Question 14: Draft contract Insurance If the named software partner hosts all records and RG serves as prime/project administrator without hosting data, what cyber liability limits must RG itself carry?

Answer 14: The prime vendor must meet the insurance requirements identified in the contract and must ensure that all subcontractors maintain required levels of insurance as well.

Question 15: Exhibit C Pricing, cells G31:P31 and Q31 The annual totals sum rows 11-28, excluding implementation, migration and integrations in rows 8-10, while the ten-year grand total includes rows 8-28. Should the annual totals include rows 8- 10? Please also confirm how to price the additional four months anticipated in Exhibit A when the template provides ten annual columns.

Answer 15: Yes, a corrected workbook will be issued with this posting. The initial term will begin upon execution of the contract, estimated March or April 1, 2027 and end June 30, 2028 to allow for data migration prior to the estimated go-live date of July 1, 2027. The remaining contract terms will be periods of 1 year, which begin July 1st and end June 30th of each year.

Question 16: Exhibit A 1.2 and 3.1.2 — Please identify the existing archival collections-management system, database platform, product version, and available database or export method for the approximately 4.3 million records.

Answer 16: CSA is currently using Proficio version 8.22.9035, by Re:Discovery Software. Our existing data set is hosted on SQL tables, with exports to be provided by the State’s IT Department.

Question 17: Exhibit A 3.1.1.2–3.1.5 — Please provide the approximate record counts at each hierarchical level, such as Collection, Series, Box, and Item, together with a data dictionary or representative anonymized data extract if one is available.

Answer 17: Collection Level: 733 records. Series Level: 4679 records. File Unit (Box): 125,033 records. Item level: 4,046,184 records.

Question 18: Exhibit A 1.2.2 and 3.1.1.9 — Does the migration include only catalog metadata, or are digital files, images, or other attachments included? If files are included, please provide the approximate file count and storage volume.

Answer 18: Export will only include catalog metadata, no media attachments.

Question 19: Exhibit A 1.2.2 and 3.1.1.9 — Please identify the existing digital asset management/digital preservation system and describe the required relationship or integration between that system, the new catalog, and the public portal.

Answer 19: Our digital preservation system is a stand-alone product, and does not require coordination with our catalog system.

Question 20: Exhibit A 3.1.4 — Please define the audit and acceptance criteria for confirming 100% transfer of the legacy data, including the required treatment of rejected records, duplicate identifiers, field-level discrepancies, and broken hierarchical relationships.

Answer 20: CSA will compare record counts, and will perform randomly-selected searches to confirm data transfer.

Question 21: Exhibit A 1.2.1, 3.1.1.9, and 3.5 — Please clarify the intended public-portal experience. Should anonymous users be able to search the complete public catalog, view or download digital content, submit record requests, export result lists, and access permanent record links?

Answer 21: The public portal should allow the user to search the public catalog and access permanent catalog record links.

Question 22: Exhibit A 3.1.1.5 and 3.5 — Please provide the anticipated peak concurrent public-user volume and explain how the less-than-10-second search requirement will be tested and accepted.

Answer 22: The most accurate data CSA has on portal use is based on daily traffic, as provided in the RFP, but does not include a number for concurrent users. The 10-second search time will be tested using a general search, like the last name “Smith,” across our largest table (Item Level), then measuring response time.

Question 23: Exhibit C and Exhibit A 4.1 — Please provide the anticipated number of internal users by role or license type and indicate whether the State has established a budget, affordability range, or not-to-exceed amount.

Answer 23: Internal user licenses is not likely to exceed 10 users, with concurrent users typically being half of that. DPA is not able to disclose the available budget at this time. Please use the provided pricing sheet for software licensing and add-on features.

Question 24: Exhibit C, Integrations — Please identify required integrations, including identity or single sign-on, the existing preservation system, the State website, public-record request systems, and analytics. Please also identify which integrations must be operational at go-live.

Answer 24: We do not require any integrations. Our customer request and preservation software systems operate independently. We use ZenDesk for customer requests, and if you have any integration options, we are open to learning about them.

Question 25: Exhibit A 2.1 and 3.3 and Exhibit B 5 — Please confirm the specific WCAG version that will govern acceptance and whether the required VPAT or Accessibility Conformance Report must cover the complete proposed public portal, including any custom-developed components.

Answer 25: Compliance should be at least Level AA of the most recent version of WCAG.

Report should cover the public portal and custom components.

Question 26: Exhibit A 3.1.1.4, 3.1.1.7, and 3.1.1.12 — Does the existing catalog use archival metadata or interchange standards such as DACS, EAD, EAC-CPF, MARC, Dublin Core, or another standard, and must the proposed system preserve or support those standards?

Answer 26: Our existing catalog roughly follows Dublin Core for field names, but the field content is relatively unstructured.

Question 27: Section 4.1.1 accepts proposals only for the entire Statement of Work, and Section

6.1.1 reserves the right to award in part to multiple Offerors. Please clarify how the Department will apply both provisions.

Answer 27: In accordance with Section 4.1.1. Offerors’ proposals must be for the entire Statement of Work in order to be considered responsive. Section 6.1.1. reserves the State’s right to make multiple awards should it be in the best interests of the State. In this case, the State’s intention is to award to one Contractor.

Question 28: Will Offerors price the option and extension terms in Exhibit C, and how will pricing be set after the initial term ends on June 30, 2028? Does the Department have a target go-live date, and must the migration be completed before the initial term ends?

Answer 28: The initial term will begin upon execution of the contract, estimated March or April 1, 2027 and end June 30, 2028 to allow for data migration prior to the estimated go-live date of July 1, 2027. The remaining contract terms will be periods of one (1) year, which begin July 1st and end June 30th of each year.

Question 29: Section 2.2.2.1.1 describes a similarly sized entity as a state or large municipality with 4+ million records and 1,000 unique daily web visits. Does the Department evaluate each reference against both measures, or does it weigh the references together?

Answer 29: CSA would weigh references together.

Question 30: Please describe the known data quality issues, such as special characters, irregular dates, and duplicate records, and the share of records affected. Who defines the normalization rules, and what level of State Archives staff participation does the Department expect for cleanup? Will the Department provide a representative data sample before the proposal deadline so Offerors can review data quality?

Answer 30: CSA has provided data samples; please see answer 39 for the link to this data. There are known quality issues with special characters, though the exact quantity is unknown.

Question 31: Please describe how the Department will measure a 100% transfer, for example by record counts, field-level comparison, or sampling. Who performs the audit of transferred records?

Answer 31: CSA will compare record counts, and will perform audits of randomly-selected records to check accuracy.

Question 32: Please clarify whether the limit of two business days of downtime applies to each incident, each month, or each year, and whether scheduled maintenance counts toward it.

Answer 32: Each incident. Scheduled maintenance is not included, however, CSA requests that planned maintenance exists outside of business hours (on evenings and weekends).

Question 33: Does the Department want features in development priced as separate optional lines in Exhibit C, and how will the Department weigh those lines in the evaluation?

Answer 33: Yes, features in development should be priced separately on Exhibit C. Future options are not included in the evaluation criteria at this time but may be considered for future options if the system is awarded a contract.

Question 34: If an Offeror uses a Subcontractor, must the proposal name the Subcontractor, and when does the State give written approval of the subcontract?

Answer 34: The proposal must name the subcontractor, as well as how the subcontractor meets or exceeds the scope of work.

Question 35: Offeror Response 6.1 asks for a copy of the current Business Continuity Plan. May Offerors submit the plan as separate Proprietary/Confidential material under Section 4.6?

Answer 35: Yes.

Question 36: The cyber liability tiers depend on record count, and the State Archives holds about 4.3 million records. Please confirm that the tier above 3,000,000 records applies. Does the Department accept one combined cyber and professional liability policy that meets the stated limits, and are certificates required with the proposal or within seven Business Days after the Effective Date?

Answer 36: The Contractor must carry the full cyber liability insurance required under the contract, as would their subcontractor.

Question 37: Please identify the specific requirements that constitute the “mandatory qualification requirements” scored on a Met / Not Met basis. In particular, are the four items listed in Exhibit A §2.2.2.1 mandatory pass/fail requirements, or are they scored under the Organizational Experience criterion?

Answer 37: There are no mandatory qualification requirements in the solicitation.

Question 38: Please identify the collections management system CSA uses today by product name, vendor and version, together with the underlying database platform (for example SQL Server, Oracle, MySQL, FileMaker or a flat-file system).

Answer 38: CSA currently uses Proficio version 8.22.9035 on a SQL server.

Question 39: Will the Department make available, prior to the Proposal Submission Deadline, a data dictionary or field list for the existing database and a representative sample export (de-identified if necessary) of several thousand records? Without visibility into the legacy schema and data condition, migration effort cannot be estimated with accuracy.

Answer 39: Sample data for each hierarchy level is available here:

https://drive.google.com/drive/folders/1_GubDQtu-CpICa9kXyJUPnY89dmfkTtD?usp=sharing

Question 40: Has CSA performed a data-quality assessment of the existing 4.3 million records?

Can the Department quantify the expected remediation (for example the percentage of records containing irregular dates, special characters, or incomplete hierarchy), or establish a defined scope or cap for cleanup, so that remediation effort can be priced? As written, the obligation to clean up data “as requested” is open-ended.

Answer 40: CSA does not know the number of records that will require remediation at this time.

If other metadata irregularities are discovered during the implementation process, CSA would like to have a collaborative relationship with the vendor to determine next steps. Pricing should be based on Offeror’s “best solution” to satisfy the requirements of Exhibit A - Specifications and Requirements, and should include pricing associated with potential remediation. If your pricing does not automatically include remediation or data cleanup, CSA suggests to price out 40 hours of remediation time as a separate add-on line item and then an hourly rate for any additional time after the 40 hour period.

Question 41: Has CSA performed a data-quality assessment of the existing 4.3 million records?

Can the Department quantify the expected remediation (for example the percentage of records containing irregular dates, special characters, or incomplete hierarchy), or establish a defined scope or cap for cleanup, so that remediation effort can be priced? As written, the obligation to clean up data “as requested” is open-ended.

Answer 41: See answer to question 40 https://drive.google.com/drive/folders/1_GubDQtu-CpICa9kXyJUPnY89dmfkTtD?usp=sharing

Question 42: How many CSA staff require system accounts, and how many are expected to use the system concurrently? Are there distinct user tiers (for example administrator, cataloger, read-only, volunteer or intern)? Does the Department prefer pricing on a per-named-user, per-concurrent-user, or enterprise/unlimited-user basis? Public portal users are presumed unauthenticated and unlimited; please confirm.

Answer 42: Internal user licenses are not likely to exceed 10 users, with concurrent users typically being half of that. Yes, tiered user profiles such Administrator, cataloger, and read-only would be preferred. Pricing should be competitive based on the number of users CSA needs. We confirm that portal users will be unauthenticated and should be unlimited.

Question 43: Please identify that system by product name and vendor. Is any integration, data exchange or linking between it and the new collections management system required or desired, and if so, by what method (API, persistent identifier, embedded viewer, scheduled export)? If no integration is required, please confirm that the two systems will operate independently.

Answer 43: Our Preservation system (Preservica), customer request platform (ZenDesk), and existing catalog system (Proficio) operate independently, and do not require any collaboration between systems.

Question 44: Does the public portal need to deliver or display digital objects (images, PDFs), or only catalog metadata together with a mechanism by which the public may request access? If a request mechanism is required, does CSA have an existing request, reference or order-fulfillment workflow (for example a web form, ticketing system or payment system) that the portal must feed or integrate with?

Answer 44: The public portal only needs to display catalog metadata. Our customer request platform (Zendesk) and payment systems operate independently and we do not require collaboration between systems.

Question 45: Does the public portal need to deliver or display digital objects (images, PDFs), or only catalog metadata together with a mechanism by which the public may request access? If a request mechanism is required, does CSA have an existing request, reference or order-fulfillment workflow (for example a web form, ticketing system or payment system) that the portal must feed or integrate with?

Answer 45: See answer to question 44.

Question 46: The annual column totals in row 31 sum from row 11 downward, which excludes row 8 (Implementation), row 9 (Historical Data Migration & Verification) and row 10 (Integrations). The 10-Year Grand Total in cell Q31 sums from row 8 and therefore includes them. As issued, the sum of the ten annual totals will not equal the 10-Year Grand Total for any Offeror that prices implementation, migration or integrations. Will the Department issue a corrected workbook? In the meantime, should Offerors leave the formulas as issued, or correct them to sum from row 8?

Answer 46: Please refer to the answer to Question 2.

Question 47: Exhibit C requests pricing for ten years. Exhibit A §1.3.2 states the total duration is not anticipated to exceed ten years and four months. Exhibit D §2.C states that the total duration, including all options, “shall not exceed five years from its Effective Date absent prior approval from the Chief Procurement Officer,” and the Sample Option Letter at Exhibit B to the contract provides for only four Extension Terms. Please reconcile these provisions and confirm the maximum contract duration for which Offerors should price.

Answer 47: The initial term will begin upon execution of the contract, estimated March or April 1, 2027 and end June 30, 2028 to allow for data migration prior to the estimated go-live date of July 1, 2027. The remaining contract terms will be periods of one (1) year, which begin July 1st and end June 30th of each year.

Question 48: Do the Year 1 through Year 10 columns correspond to State Fiscal Years (July 1 – June 30) or to contract years measured from the Effective Date? Given an estimated Effective Date of April 1, 2027 and an Initial Term ending June 30, 2028, should Year 1 represent the approximately three-month remainder of SFY 2027, the fifteen-month Initial Term, or a full twelve months?

Answer 48: Please see the answer to question 47.

Question 49: Please confirm that the per-year amounts an Offeror enters in Exhibit C become the fixed rates for the entire contract term, including all Extension Terms, and that no further escalation or renegotiation will be available. If that is the Department's intent, please confirm that Offerors may enter differing amounts in each year column in order to reflect anticipated cost escalation over the full term.

Answer 49: The Department intends for the pricing in Exhibit C to remain firm-fixed for the duration of the contract, including extension terms. Offerors should not submit bids with the expectation that rates will be renegotiated. While the Department retains the right to consider contract amendments or adjustments to the price if deemed necessary and in the best interest of the State, approval is not guaranteed and will be determined on a case-by-case basis. Offerors may enter varying amounts in Exhibit C to account for anticipated, reasonable cost increases over time.

Question 50: Several quantities required to price this work are not stated in the solicitation, notably the number of internal users to be licensed under Exhibit C row 11, and the volume of legacy data requiring remediation under Exhibit A §3.1.3. Please confirm that an Offeror may satisfy §4.1.2 by offering firm, fixed tiered pricing against clearly stated quantity assumptions recorded in column R of Exhibit C, and that doing so will not be treated as submitting estimated prices.

Answer 50: Internal user licenses are not likely to exceed 10 users, with concurrent users typically being half of that. CSA does not know how many records will require remediation.

Vendors should submit their best firm fixed pricing and may include tiered fixed pricing based on the available information.

Question 51: The HIPAA Business Associate Agreement is listed first in the order of precedence, above the Colorado Special Provisions and above the main body of the Contract.

Colorado State Archives holds archival government records, and nothing in Exhibit A indicates that Protected Health Information will be created, received, maintained or transmitted under this Contract. Will the Department remove Exhibit E from the resulting contract where no PHI is involved? We note that §7 of the HIPAA BAA provides that “any provision in the Contract limiting Contractor's liability shall not apply to Business Associate's liability under this Agreement, which shall not be limited”; retaining the BAA would therefore impose unlimited liability in a contract where no PHI exists.

Answer 51: There will be no PHI in the system, Therefore the HIPAA BAA may be removed during the contracting process.

Question 52: Two points require clarification. First, §6.4.1 identifies the draft contract as “Exhibit B”, whereas the Table of Contents and the issued file identify it as Exhibit D; please confirm Exhibit D is the governing draft. Second, in Exhibit D, §19 is the Colorado Special Provisions and §10 is Insurance. Please confirm that §6.4.1 means that both the Colorado Special Provisions and the Insurance requirements in §10, including the Cyber/Network Security and Privacy Liability limits in §10.D, are non-negotiable and are not open to redline under §2.4

Answer 52: Exhibit D is the governing draft. Offerors may submit redlines but the State does not guarantee acceptance of redlines. The acceptance of redlines by the State will be determined during the negotiation phase after the contract is awarded. §19 of the Contract, the Colorado Special Provisions are non-negotiable.

Question 53: Given that exceptions must be submitted with the proposal under §2.4.2 and that only 30 calendar days are allowed after award to conclude the contract, will the Department indicate before the Proposal Submission Deadline which categories of requested exception it would regard as unacceptable? Offerors would otherwise be required to choose between submitting exceptions their counsel considers necessary and risking the 30-day window, with no visibility into the Department's position.

Answer 53: The Department will not review or approve requested contract exceptions prior to the proposal deadline. In accordance with §2.4.2, all exceptions must be included with the proposal. Exceptions will be addressed exclusively during post-award negotiations. While the 30-day timeline in §6.3.3 does not require full execution within that period, the Department reserves the right to terminate negotiations and award to the next most advantageous Offeror if terms cannot be mutually agreed upon within 30 calendar days.

Question 54: For a commercially available software-as-a-service solution, please confirm that the Contractor's pre-existing platform, its source code and any configuration of that platform remain Contractor Property under §16.C, and that the Work Product assignment in §16.A is limited to deliverables created specifically for the State, such as migration mappings, documentation and reports. Absent that distinction, §16.A would assign the Contractor's commercial product to the State.

Answer 54: Pre-existing commercial software and proprietary source code are governed by §16.C (Contractor Property) and are not claimed as State-owned Work Product under §16.A.

Work Product is intended to encompass deliverables created specifically for the State. Any specific adjustments or clarifications regarding platform configurations must be submitted as redlines with the Offeror’s proposal per §2.4.2 and will be finalized during contract negotiations with the awarded Offeror.

Question 55: Please confirm how “records” is counted for the purpose of these tiers. Archival catalog records are predominantly descriptive metadata concerning government records, the substantial majority of which are intended for publication on a public portal and contain no personal information. If the tier is determined by records containing personal information, the applicable tier would be the lowest. If it is determined by total catalog records, the 4.3 million records to be migrated would place this Contract in the highest tier at $5,000,000 per claim and $10,000,000 in the aggregate. The distinction is material to pricing and should be settled before proposals are submitted.

Answer 55: CSA’s records contain high-level descriptive metadata and are catalog records only.

Collection Level: 733 records. Series Level: 4679 records. File Unit (Box): 125,033 records.

Item level: 4,046,184 records. See example data set from question 39.

Question 56: As drafted, the cap of three times the Contract Maximum Amount does not apply to any claim related to a breach of the Contractor's security obligations, which for a hosted system holding the State's records is the principal category of risk. The effect is unlimited liability for the most likely loss event. Will the Department consider a separate, higher aggregate cap for security-related claims, for example a multiple of fees or a limit aligned to the required cyber liability insurance, rather than no limit at all? We also note that §11 includes consequential, special, indirect, incidental, punitive and exemplary damages within the capped amount rather than excluding them; please confirm that is the Department's intent.

Answer 56: Vendors should submit redlines to this section of the contract with their proposals.

Modifications to this section will be reviewed and considered during negotiations once a vendor has been selected.

Question 57: Please confirm that an annual SOC 2 Type II audit is a contractual requirement rather than a preference, notwithstanding that Exhibit B §4.4 asks only whether backup controls are audited under such a report. Will an existing SOC 2 Type II report covering the proposed platform and its hosting environment satisfy this requirement, or must the report be scoped specifically to the State's instance? Where the Offeror's cloud infrastructure provider holds the SOC 2 Type II attestation for the hosting layer, will that be accepted for that layer?

Answer 57: Legislation SB26-185 indirectly impacts State Vendors. While SB26-185 does not mandate SOC 2 Type II into statute, OIT's published vendor security standards—which SB26- 185 places firmly under CISO authority—routinely require a SOC 2 Type II report (or equivalent third-party security attestation) during procurement if a vendor sells software directly to State of Colorado agencies.

Additionally, legislation SB26-189 written for AI pursuits, states that a SOC 2 Type II certification is not required. Instead, software developers must provide technical documentation (intended uses, training data categories, known limitations, and human-review instructions) to deployers and retain compliance records for at least three years.

Question 58: Reference text: “Contractor shall perform current background checks … on all of its employees and agents, including any Subcontractors and employees of Subcontractors, performing services or having access to State Records … A background check performed within 30 days prior to the date such employee or agent begins performance … shall be considered current.”

Question: For a multi-tenant software-as-a-service platform, does this obligation extend to all of the Contractor's platform engineering and support personnel who could technically access the hosting environment, or only to personnel assigned to this engagement and to those with logical access to the State's data? Will background checks completed under the Contractor's standard pre-employment process be accepted for existing personnel, or must each be re-run within 30 days before that person first works on this Contract?

Answer 58: All personnel who will have access to the State’s data are subject to this requirement. The Department is willing to discuss the selected Contractor's standard pre-employment screening process during negotiations, but does not guarantee it will be accepted in lieu of the Contract’s specific screening requirements.

Question 59: The transition assistance obligation is unbounded in scope and duration and is expressly uncompensated. Will the Department consider defining it, for example a stated number of hours or a defined period following expiration, with further assistance available at the Contract's rates? As drafted, the obligation cannot be priced.

Answer 59: CSA is unable to estimate the hours needed. As stated, we have approximately 4.3 million catalog records that must be transferred to a new system, which can be searched via public portal, all of which should be available and indexed when the system goes live.

Question 60: Does the Department have an established budget range, estimated annual value, or not-to-exceed amount for the initial term or the full contract term that it is able to disclose?

Answer 60: See answer 23.

Question 61: Reference text: “Offeror has provided service to a similar-sized entity (i.e. another state or large municipality with 4+ million records and 1,000 daily unique web visits).”

Question: Must a single reference engagement satisfy both the 4+ million record threshold and the 1,000 daily unique web visit threshold, or may the Offeror demonstrate these capabilities across more than one client engagement? Will the Department accept a comparable reference outside of state or municipal government, for example a federal agency, a national or university archive, a library consortium, or a historical society of equivalent scale, as a “similar-sized entity”?

Answer 61: Yes, CSA will accept a comparable reference.

Question 62: May an Offeror propose a commercially available third-party archival collections management product that the Offeror implements, configures, hosts and supports under its own service-level agreement, rather than software the Offeror itself develops? If so, whose experience and references are evaluated under Exhibit A §2.2.2: the Offeror’s, the software publisher’s, or both in combination?

Answer 62: Yes, an Offeror may propose a commercially available third-party archival collections management product that the Offeror implements, configures, hosts and supports under its own service-level agreement. Both experience and references for the offeror and the publisher will be evaluated in combination.

Question 63: May the organizational experience and reference requirements in Exhibit A §2.2.2 be satisfied in whole or in part by a proposed subcontractor, software publisher or teaming partner, provided the Offeror remains the single contracting party and single point of contact under §3.5.3.4.1? Is there a limit on the percentage of the work that may be performed by subcontractors?

Answer 63: CSA does not have a requirement for the percentage of work performed by subcontractors, so long as the Offeror is the ultimate accountability agent, and CSA has a single point of contact when issues arise.

Question 64: Reference text: Exhibit A §2.1.1 requires “Level AA of the most current version of the Web Content Accessibility Guidelines (WCAG)”; Exhibit B §5.2 and §5.4 reference

“WCAG 2.1+”.

Question: Which standard will be applied in evaluation and in the resulting contract: WCAG 2.2 Level AA as the current version, or WCAG 2.1 Level AA? Must conformance be achieved at go-live, or will the Department accept a documented remediation roadmap with committed dates for identified gaps?

Answer 64: Exhibit B, §5.2 and §5.4 have been corrected. Level AA of the most current version of the Web Content Accessibility Guidelines (WCAG) is required. Ideally, the vendor will be fully compliant at go-live.

Question 65: What system (product name and version) currently holds the approximately 4.3 million records to be migrated?

Answer 65: RE:Discovery Proficio version 8.22.9035.

Question 66: In what structured format(s) can CSA export all records from that system (for example CSV, XML/EAD, or a full database export)?

Answer 66: It is our understanding that the system uses an SQL database and that we can provide a full export if needed.

Question 67: Can the State share a sample export or a data dictionary describing the current record structure?

Answer 67: See answer 39.

Question 68: Please name each record type maintained in the current system (for example collections, series, boxes, items, accessions, depositors or other agents, subjects, locations, import batches) and the approximate number of records of each type.

Answer 68: See answers 17 and 39.

Question 69: Does every record carry a unique, persistent identifier that remains the same across exports?

Answer 69: Yes, each record has a unique identifier at each hierarchy level, typically labeled as “Record ID.”

Question 70: Does each record include an explicit reference to its parent record, so that its place in the hierarchy can be identified? If not, how is the hierarchy currently represented (for example through catalog-number patterns)?

Answer 70: The bulk of the records do not contain an explicit reference to a parent/child relationship in the existing data set, however, many relationships can be inferred from catalog number patterns. A significant number of our catalog records are missing data from one or more of the four hierarchy fields (Collection, Series, File Unit, or Item).

Question 71: Are depositors, creators, subjects and locations maintained as separate linked records, or recorded as text on each catalog record?

Answer 71: The bulk of our records are in a flat format, without references to external tables, though we do have a few instances where Creators, Accessions data, and a few other fields may be linked.

Question 72: Approximately how many distinct fields are in use for each record type?

Answer 72: Approximate number of fields used by Hierarchy Level:

Collection: 11 fields

Series: 7 fields

File Unit: 23 fields

Item: 17 fields

Question 73: Which fields are user-defined or locally defined, and are any fields known to be used inconsistently?

Answer 73: Yes, many of our fields are used inconsistently.

Question 74: How are restriction levels and publication status currently recorded for each record?

Answer 74: We have a small set of records with restrictions, typically marked in a Summary field. We currently have a publication field in use on most of our records.

Question 75: For References, Offeror Response 3 states "Provide references and letters of recommendation from other clients." Should we submit the letters with our response or should our customers send them directly to Jessica Carmer, Jessica.carmer@state.co.us?

Answer 75: Please submit references and letters of recommendation with your final proposal following the instructions in the Administrative Information Document for proposal submission.

Question 76: what information is required in the letters of recommendation?

Answer 76: Per Section Exhibit B, §2.1: Provide references and letters of recommendation from other clients for whom the Offeror has performed similar work, preferably government clients.

No more than five recommendations. Include any corrective actions plans related to this work experience.

File details come from the government source that posted it. Updated .