POSTED Addendum 298-FY26-ITS-RFP-GoogleBackup.pdf
PDF 124 KB Posted
- Attached to
- Google Backup
- Solicitation number
- 298-FY26-ITS-RFP-GoogleBackup
- Issued by
- Buncombe County, North Carolina
About this file
This is Addendum No. 1 to a Request for Proposals issued by the City of Asheville, North Carolina on August 21, 2026, for Google Backup services under Project Number 298-FY26-ITS-RFP-GoogleBackup. The addendum modifies the original RFP to clarify data retention requirements and provides responses to 16 bidder questions. The scope encompasses backup services for approximately 1,700 active Google Workspace users with an estimated 70 terabytes of data currently in scope. The City adds approximately 200 users annually and requires backup capabilities for all Google Workspace data types with a minimum 10-year retention period for all data, including deleted items. The addendum addresses key technical requirements, vendor qualifications, reference expectations, and implementation considerations. Failure to acknowledge this addendum in proposal submissions may result in bids being deemed non-responsive.
The addendum establishes specific security certification requirements including ISO/IEC 27001:2022, ISO/IEC 27017, ISO/IEC 27018, ISO/IEC 27701, ISO 9001, and SOC 2 Type II. References must be from state and local government clients or private companies with 1,500 to 3,000 employees and should include organizational name, contact person and email address, and product/service type used. The City currently utilizes three backup solutions (Datto Backupify, Spin.ai, and Google Workspace Vault) and has no platform preference for backup location provided data remains accessible within the United States. Backup data may be stored on secondary platforms such as Wasabi or AWS or remain on Google Cloud Platform. The City uses Microsoft Active Directory with Entra ID for directory services and anticipates fewer than 100 archived users requiring the full 10-year retention period. Interview selections, if conducted, will be scored separately from written proposals based on responsive submissions and evaluation criteria.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| POSTED Ad 298-FY26-ITS-RFP-GoogleBackup.pdf |
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
Addendum No. 1 Issue Date: 08/21/2026
Project Name: Google Backup Project Number: 298-FY26-ITS-RFP-GoogleBackup
TO: Prospective Applicants
This addendum forms a part of the Request for Proposals and modifies the original Project Number 298-FY26-ITS-RFP-GoogleBackup only to the extent specifically noted below.
Failure to acknowledge this addendum in the submittal may subject the submitter to being deemed non-responsive.
This Addendum is posted on the City procurement website at www.ashevillenc.gov/bids. This is the official source of this addendum. All addenda and attachments shall be published to the same location.
This Addendum consists of 3 pages in total.
This Addendum is to address Clarifications/Changes and Responses to Questions
Clarifications/Changes
The original Bid/RFP stated: Long-Term Data Retention: Maintain strict 10-year retention policies, including the continuous backup and retention of deleted items to ensure absolute data integrity.
This is now changed to: Long-Term Data Retention: Maintain data for at least 10-years, including the continuous backup and retention of deleted items to ensure absolute data integrity.
Answers to Questions
1. Question: How many active users will need to be backed up?
Response: 1700
2. Question: How many non-active users will need to be backed up (suspended, archived, etc)?
Response: Currently no archived users, but please describe any archived user options your platform provides.
3. Question: How much data, approximately, is in scope for backup?
http://www.ashevillenc.gov/bids
Response: 70TB.
4. Question: What kind of user roles will be required?
Response: We currently only utilize a single standard admin role, but would be interested in hearing what other role options your platform provides.
5. Question: Can the City of Asheville specify which security certifications will satisfy the city's requirements?
Response: Required certifications are as follows:
● ISO/IEC 27001:2022 (Information Security)
● ISO/IEC 27017 (Cloud Security)
● ISO/IEC 27018 (Cloud Privacy)
● ISO/IEC 27701 (Privacy Information Management)
● ISO 9001 (Quality Management)
● SOC 2 Type II (Trust Services Criteria)
6. Question: Can the City of Asheville define what qualifies as a 'comparable organization'?
Response: References from any State and local government clients preferred, or private companies with 1500 to 3000 employees.
7. Question: What information must be included with each reference (contact name/title, contract duration, scope of services, data volume, size of deployment)?
Response: Minimum Required Information from References: Organizational name, Contact Person and email address, product / type of service used by organization.
8. Question: Will the City of Asheville contact references directly, and if so, over what timeframe?
Response: We reserve the right to contact references, but will not be able to provide a distinct timeframe, as it will be determined by the Proposal process.
9. Question: How many vendors does the City of Asheville anticipate shortlisting for interviews?
Response: This will be determined based on the number of responsive submissions.
10.Question: Will interview invitations be based on a scored threshold or a fixed number of top-ranked respondents?
Response: Interviews, if held, will be scored and ranked separately from the written proposals. However, the City may use criteria similar to the above Evaluation Criteria to score and rank Proposers’ responses to interview questions or instructions, in addition to other relevant information provided or requested.
11. Question: Could you provide the number of inactive, suspended, archived, or former-user accounts that are expected to remain protected under the 10-year retention requirement?
Response: Currently backup options are all active, and no archived users are set up with our current providers. We estimate that less than 100 users will need to be backed up for the full 10 year length. Please describe any archived user options and retention rules that your platform provides to may be used to maintain data for this requirement.
12.Question: What is the approximate growth rate for data year over year?
Response: The City adds approximately 200 users a year.
13.Question: Do you require backup data to be stored on a secondary platform (Wasabi, AWS) or prefer backups stay on GCP?
Response: As long as the data stays accessible and within the US, we do not have a platform preference for backup location.
14.Question: What vendor is providing LDAP (Microsoft, Other)?
Response: We use a local Microsoft Active Directory configuration with Entra ID.
15.Question: What solution is used presently to backup this data?
Response: The City is using 3 different options: Datto Backupify, Spin.ai, Google Workspace Vault.
16.Question: Is the 10-year requirement uniform for ALL data types or a subset
Response: All data types must have the capability to be kept for a 10-year period minimum.
I understand that failure to acknowledge any addenda may cause this bid/proposal to be deemed non-responsive.
Authorized Signature Company Date
- End -
File details come from the government source that posted it. Updated .