REQUEST FOR PROPOSAL (RFP) BACKUP, RECOVERY, AND ARCHIVAL SOFTWARE SOLUTION RFP # 14GH07P3

(1)

REQUEST FOR PROPOSAL

(RFP)

BACKUP, RECOVERY, AND

ARCHIVAL SOFTWARE SOLUTION

RFP # 14GH07P3

Canyons School District

Purchasing Department

(2)

CANYONS SCHOOL DISTRICT

REQUEST FOR PROPOSAL

BACKUP, RECOVERY, ARCHIVAL SOFTWARE SOLUTION

RFP #14GH07P3

I. GENERAL

A. Intent of Request for Proposal

The purpose of this request for proposal is to solicit competitive sealed proposals from qualified suppliers/individuals for a Backup, Recovery, Archival Software Solution (“The Solution”) for Canyons School District (CSD). CSD has a need to properly secure its electronic data through the use of an integrated enterprise level software solution. CSD plans to procure and implement a software solution that will provide backup, recovery, file and email archiving, e-discovery, and Hierarchical Storage Management (HSM). We would like this project fully implemented and functional by August 29, 2014.

This RFP is designed to provide interested Suppliers with sufficient basic information to submit proposals meeting minimum requirements, but is not intended to limit a proposal’s content or exclude any relevant or essential data. Suppliers are at liberty and are encouraged to expand upon the specifications to evidence service capability under any agreement.

All proposal preparation costs and any associated activities related to this RFP are the sole responsibility of the Supplier. CSD is not liable for any costs incurred throughout the entire selection process.

B. Eligibility Requirements

In order to be eligible to respond to this RFP, the Supplier must meet all of the following minimum qualifications:

1. Licensed – The proposing Supplier must be properly licensed to conduct business in the State of Utah.

(4)

C. Addendum to RFP

If it becomes necessary to revise this RFP in whole or in part, an addendum will be posted on www.bidsync.com. Suppliers who obtained this RFP by download are required to check www.bidsync.com for any addenda.

D. Right of Rejection

The CSD Board of Education reserves the right to reject any and all proposals or to waive any non-statutory informality. The Board of Education further reserves the right to make the contract award deemed by the Chief Procurement Officer of the School District to be in the best interest of the District. The Board's decision to accept or reject the contract shall be final.

E. Oral Presentations

An oral presentation by a Supplier to clarify a proposal may be required at the sole discretion of CSD. However, Canyons School District may award a contract based on the initial proposals received without discussion with the Supplier. If oral

presentations are required, they will be scheduled after the submission of proposals.

F. Written Agreement

The selected supplier must enter into a written contract with CSD to provide a Backup, Recovery, Archival Software Solution required by the District for the term of the contract. The contract must be performed in accordance with CSD Standard Terms and Conditions, rev. date 1/12/10 (Attachment A).

G. Contract Period

This agreement shall commence on the date of RFP acceptance by the Board of Education and continue for one (1) year. Each proposal must include an option whereby the Board, in its sole discretion, can extend the contract for two (2) one (1) additional year on the same terms, prices, and conditions set forth in the proposal. The option shall be exercisable at the end of the first year. If the option is not exercised, then the contract shall automatically expire at the end of the contract term. Notice of exercise of the option must be given at least thirty (60) days prior to the end of the contract term.

H. CSD Contacts

All inquiries relative to this Request for Proposal must be submitted through

www.bidsync.com.

(5)

with this requirement may result in disqualification. I. Supplier Proposal

Proposals must be signed by the Supplier’s authorized official binding the RFP and the Supplier for a period sixty (60) days from the date of receipt by Mr. Gary O. Hansen, Chief Procurement Officer.

J. Submitting Your Proposal

1. All bids shall be submitted via www.bidsync.com. Bids delivered by e-mail or fax will not be considered or evaluated.

2. All information requested must be completed and submitted by the date and time listed in BidSync. Proposals received after that will be deemed non-responsive. Neither faxed nor emailed bids will be accepted.

3. Responses submitted in BidSync are completely secure. No one (including the purchasing staff) can see responses prior to the deadline. Once proposals are submitted in BidSync, you may make changes at any time before the solicitation deadline. Allow sufficient time to complete any applicable online forms and/or upload documents. Please do not upload any embedded or password protected

documents (zip files, mov, wmp, and mp3 files) as they cannot be opened, unzipped and included in your submittal. The solicitation will end precisely at the closing

time listed. If you are in the middle of uploading your bid at the closing time, BidSync will stop the process and your bid will not be received.

4. Each Supplier shall submit only one (1) proposal. Alternate or multiple proposals from a single Supplier are prohibited. On any item where multiple bids are submitted, that item may be deemed non-responsive.

5. All inquiries relative to this bid must be submitted through www.bidsync.com and will be answered through BidSync up to the Q & A deadline.

6. When the award is made, it will be posted on www.bidsync.com. In the event that the bid is canceled after the closing date, that information will be posted on BidSync as well.

7. Conform to Response Form Guidelines - All proposed information must be submitted on the Proposal Response forms found in Section IV.

II. DETAILED SCOPE OF WORK

The successful Supplier is expected to replace our current Backup, Recovery, Archival, and Disaster Recovery of electronic data with a new solution according to

specifications and requirements outlined in this RFP.

(6)

A. Planning

1. Evaluate current environment and system requirements to implement new solution.

2. Ensure all best practices and policies as defined by stakeholders of data retention and management are understood and rolled into project plan.

3. Create detailed project plan with milestones, tasks and deadlines to ensure completion by August 29, 2014.

4. Train District Engineering Team on new concepts, methodologies, and all technical details and tasks.

5. Identify impact and any downtime. Communicate these details to all stakeholders and confirm project as defined is agreeable to all stakeholders.

B. Implementation

1. Install and configure new infrastructure while training District technical staff on procedures and processes.

2. Migrate backup data and backup policies off of existing system and onto new solution, including, but not limited to:

a. Tape-to-tape b. Disk-to-disk c. Disk-to-tape

3. Document all configuration processes and data locations. 4. Test functionality of disaster recovery.

5. Setup and run reports.

C. Testing

1. Test disaster recovery, backup restore functionality, and all other major aspect required to ensure solution is complete, stable, and completely functional. 2. Have official sign-off by stakeholders that tests performed on all critical

processes have functioned to a satisfactory level and fully understood.

D. Training

1. Provide final training to stakeholders.

2. Provide detailed documentation on procedures required to complete critical processes.

(7)

E. Follow-up and final sign off

1. Final technical follow up to ensure systems are functioning according to specification and policy requirements.

(8)

III. REQUIREMENTS

Requirements: M=Mandatory D=Desired (e.g. M1, M2,… are Mandatory; D1, D2…. are Desired) All mandatory components as described in the RFP must be fully functional and be commercially available as a GA release (non-beta) before bid closing. Mandatory components must be met by Vendors wishing to be considered as responsive/responsible to the RFP.

All features labeled as desired are not mandatory; however, desired features will be scored based on ability to fully comply with functionality specification as determined by evaluation committee reviewing response documentation.

*If any Mandatory requirement is not met, the bidder may be considered non-responsive/non-compliant.

Section/Requirement

Comply Yes/No Reference Page/ Paragraph Response

Describe how requirement is met. Please include relevant documentation or narrative to support

statements.

General System

Specifications

M1 Must be able to perform data reduction by removing duplicate data in the repository.

M2 Capable of data deduplication at the block level on source-side across all movement and copies of data on disk, tape, or the cloud.

M3 To reduce network bandwidth impact when copying data over Local Area Network (LAN) and the Wide Area Network (WAN), solution must be capable of deduplication at the source machine site and at the remote target site

M4 Allow recovery of data locally or remotely from any remote office using a common web interface for backup, replication and archive.

M5 Must be able to perform offsite copies of the deduplicated data in a deduplicated format and have separate retentions for each copy of the data

(9)

Section/Requirement

statements. M7 The console/centralized

management system that host the physical backup and archive devices must work, install, deploy, on any edition of Microsoft Windows Server 2008 and above.

M8 Work and interoperate with the following file systems

a. NT File System (NTFS) b. Hierarchical File System

(HFS, HFS+)

c. VMware File System (VMFS) d. Extent 3 File System (ext3) e. Journal File System (JFS,

JFS2)

M9 Support the copy of backup data directly from backup media to backup media over the Local Area Network (LAN) and the Wide Area Network (WAN) including: a. Tape to tape b. Tape to disk c. Disk to disk d. Disk to tape e. Backing up/archiving to Linear Tape Open (LTO-3 and LTO-6)

M10 The software solution must work and interoperate with the following storage platforms:

a. HP EVA 6000 b. HP P2000 G3 MSA c. 3PAR F400 SAN d. 3PAR 7200 SAN e. HP MSL 6000 (LTO3) f. HP MSL 2024 (LTO6) g. NAS h. iSCSI

(10)

Section/Requirement

statements. M12 Data protection of the catalogue,

index and database of the backup server, in order to ensure the recovery of the backup environment to its fully functioning state. M13 Must backup and restore

systems running the following operating systems: a. Microsoft Windows 2003 Servers (all editions/revisions) b. Microsoft Windows 2008 Servers (all editions/revisions) c. Microsoft Windows 2012 Servers (all editions/revisions) d. MAC OSX 10.5 and above e. IBM AIX ver. 5.x and above f. Linux Servers (Centos ver.

4.x and Debian ver. 10.x) and above

M14 Must backup, recover, restore following systems as specified below:

a. MySQL Database Server v 4.0 and above

b. Microsoft SQL Server 2005 and above: both a clustered and unclustered

configurations.

c. Microsoft Exchange Server 2010

d. Microsoft SharePoint Server 2010

(11)

Section/Requirement

statements. f. Individual recovery of

Active Directory users and attributes backed up in accordance with above versions

g. Microsoft Windows Server 2008 and Server 2012 Hyper-V

h. VMware ESX Server ver. 5.x and above.

i. Backup of most current versions of VMware virtual machines at file level j. VMware images using

VMware disk format (VMDK)

M15 Capable of performing multiple simultaneously restores M16 Centralized backup and restore

functionality, where multiple remote sites backup to a central site as well as isolated sites backup locally, but are managed from a central site.

M17 Automatic restart of a failed backup job. This functionality must be configurable by the administrator at the backup job level.

M18 Web based system search tool not dependent on a client software type

M19 The system shall support the ability to index all file types, including emails and email attachments, in order to allow the data to be searchable. It must include the ability to search on exchange mailboxes and archived email

M20 Ability to integrate with our existing tools used to archive and purge files.

(12)

Section/Requirement

statements. M22 Functionality to manage backup

and HSM/archive operations and data retention through

configurable policies as defined by the systems administrator. M23 Management Console must

include Graphical User Interfaces (GUI) in order to administer all the functionalities of the software backup, restore, HSM, and archival.

M24 Centralized manageability of all enterprise backup servers from a single console.

M25 Automatic and manual scheduling of backup jobs on the backup server as required by system administrator.

M26 Automated alerts and

notifications using Simple Mail Transport Protocol (SMTP). The functionality must be configurable to allow the notification of

administrators about backup, restore, HSM, archiving failures, and catalogue backup information for disaster recovery.

M27 Must be able to manage and report on the effectiveness of the deduplication from the same management console that is used for managing the backup and HSM environments

M28 The software solution must allow the administrator to configure user definable conditions that will trigger alerts, including:

a. Software solution errors b. Failed and successful restore

job

c. Tape libraries errors d. Backup disk subsystems

errors

e. Failed and successful backup job

(13)

Section/Requirement

statements. D1 Capable of identifying and

marking data as read only to preserve the content in the case of an evidence preservation

request/e-discovery request D2 Interoperate with Microsoft

Windows Volume Shadow Copy services

D3 Use our existing folder structure for archived email, and migrate existing archived email keeping its existing retention

D4 Backup, recover and restore Progress databases as specified below:

a. Eliminate need to dump Progress database files to local disk prior to backup

b. Eliminate necessity to shutdown Progress databases while backups are taken c. Provide full/incremental and

transaction log backups of Progress databases

d. Restore Progress databases to a point in time based on transaction logs

e. One click restore of Progress databases (or single line command), to restore full, all incremental, and "after images" (transaction logs) to restore and recover the Progress database to any point in time

Maintenance and Support

Warranty coverage of The Solution will be included in base bid. Please provide information on your maintenance and support model, showing levels of responsibility and support source.

The warranty period shall include hardware and software maintenance and upgrades and shall be for a minimum duration of 1 (one) year to begin on the date of Final Acceptance of The Solution.

Maintenance costs after the expiration of the warranty period shall be provided to the District as a separate annualized expense item.

(14)

Maintenance plan should include 24x7 monitoring and technical support accesses. 4 (four) hour response required for hardware faults.

Include a detailed summary of how software and firmware upgrades are performed with The Solution. Specific attention should be around any requirements for data protection and archival hardware and software

downtime. Vendors are requested to attach user instructions on upgrading the system during the last minor update (or point release) and user instructions on upgrading the system during the last major version upgrade.

Vendor Responsibility

Vendors shall not omit any part or detail which is normally considered to be standard even though such part or detail is not mentioned in this document.

Proposal must include all hardware and software components required to make a completely operational solution.

Vendors shall include all itemized pricing for components in order for the District to consider cost modifications based on storage specifications. Please follow the Bid Pricing Sheet format provided in the Appendix of the RFP.

All required equipment shall identified by manufacturer's name and model description.

System Implementation

Solution must be fully implemented and functional according to agreed scope prior to June 2014

Vendor is to provide project plan and execute the migration of the archived data from the current backup software to the new vendor proposed solution

Include a description of your overall approach to each of the following task areas (if applicable): a. System installation

b. System configuration c. Data migration

d. Test planning and execution

e. System interface design and support f. System roll-out, procedures, and support

Project Management Methodology

Project Implementation Plan Include a typical timeline with this proposal including major milestones for tasks and subtasks, dates and both vendor and customer resources. The required format for the timeline is MS Project format. The plan should adhere to any pertinent milestone dates in the RFP Schedule

Please describe your current project management methodology and include samples of the following project management deliverables used in your process:

a. Status Reports

b. Change Management Plan c. Communication Plan d. Risk Management Plan

Documentation, On-line Help, Error Messages

Identify all documentation included with the proposed system. This includes on-line help, user manuals, installation procedures, configuration and maintenance procedures, and operations manuals for all elements within the proposed system.

Training

Describe what types of end user training are offered and costs associated with the training? (online computer based, in-person classroom training)

Setup and Configuration

(15)

IV. CURRENT ENVIRONMENT

A. Network

CSD is part of the Utah Education Network (UEN) and part of the Utah backbone that extends from the north at Utah State University to Dixie State College in St. George, Utah. Our district currently has two 1 Gb Ethernet connections to the POP located at Salt Lake Community College.

The Canyons School District network is a classic hub and spoke architecture. The Data Center is located at the Canyons Support Services Center (CSSC) and is the hub of our network.

We currently have a single point of ingress/egress to the Internet through a Cisco 6503 provided by UEN & Century Link. A Cisco 6506 is the aggregation point to our Data Center which consists of 1 Gb Ethernet connections to approximately 50 locations. Internally, we have 10 Gb links between the Cisco 6506 and an HP A9512 switch, the core device of the Canyons School District network. We currently have three HP blade enclosures housing HP blade servers. The majority of systems are running on the blades are virtual servers. One of the blade enclosures is connected by a 10 Gb link to the A9512. The other two enclosures are connected to the A9512 by a 1 Gb link.

A large percentage of our production data is located on a 3PAR F400 Storage Area Network (SAN) that is connected via Fiber Channel to our blade enclosures using Brocade switches. We also have an HP EVA6000 SAN connected via Fiber Channel to the blade enclosures using the same set of Brocade switches. The EVA6000 is

reaching its end of it and we expect it will be decommissioned in the next year. It is being replaced with an HP Modular Smart Array P2000 G3 and will be connected via Fiber Channel to the blade enclosures using the same set of Brocade switches noted above.

Our WAN consists of single 1 Gb Ethernet links to all of our schools through the Cisco 6506 and Cisco switch at each school. We use the lower half of a Class B address space.

Every school has a core HP 4800/5800 core switch that aggregates all school connectivity and connects to the Cisco switch. Our firewall is a Palo AltoPA-5050 appliance.

(16)

alternate route to/from CSSC.

B. Backup and Disaster Recovery Topology

CSD currently uses Symantec Netbackup as our primary backup software in addition to simple file archival. Netbackup currently backs up a little less than six Terabytes of front-end data. There are also other data that are directly backed up to disk without utilizing Netback for short-term backups and a tape library for long-term backup archival. The device we currently use for tape backup is an HP MSL 6000 that uses LTO-3 media. We have purchased an HP MSL 2024 Ultrium 6250 Tape library that utilizes LTO-6 media to replace the HP MSL 6000 library, and this

project need to include assistance with migration of archived data from tape-to-tape of the old device to the new device.

We maintain an offsite server that hosts our student, personnel, and financial systems in addition to an Exchange mailbox database server at our Canyons Administration Building (CAB).

(17)

C. CSD-IT Current Backup Summary

BACKUP

DESTINATION & SIZE (GB)

SERVERS SERVER OS SERVER _TYPE FILE _TYPE SAN TAPE

AIX Server

AIX Physical JFS2 397

AIX Physical JFS2 14

AIX Physical JFS2 383

MAC Server 1 OS X Physical HFS+ 29

MAC Server 5 OS X Physical HFS+ 8 MAC Server 6 OS X Physical HFS+ 24

Windows 2003 Server 1 Windows2003 Virtual NTFS 1

Windows 2003 Server 1 Windows2003 Virtual MS SQL 2

Windows 2003 Server 8 Windows2003 Physical MS SQL 13

Windows 2008 Server 1 Windows2008 Physical NTFS 77 Windows 2008 Server 2 Windows2008 Physical MS SQL 2

Windows 2008 Server 3 Windows2008 Virtual NTFS 2 Windows 2008 Server 4 Windows2008 Virtual MS SQL 1 Windows 2008 Server 5 Windows2008 Physical NTFS/AD 10

Windows 2008 Server 6 Windows2008 Physical NTFS/AD 10 Windows 2008 Server 7 Windows2008 Virtual NTFS 62 Windows 2008 Server 8 Windows2008 Virtual NTFS 62 Windows 2008 Server 9 Windows2008 Virtual NTFS 62 Windows 2008 Server 10 Windows2008 Virtual NTFS 1024 Windows 2008 Server 11 Windows2008 Virtual MS SQL 1

(18)

Windows 2008 Server 14 Windows2008 Physical NTFS 24 Windows 2008 Server 15 Windows2008 Physical NTFS 1553 Windows 2008 Server 16 Windows2008 Virtual NTFS 100 Windows 2008 Server 17 Windows2008 Virtual NTFS 1 Windows 2008 Server 18 Windows2008 Physical NTFS 26 Windows 2008 Server 19 Windows2008 Virtual NTFS 4 Windows 2008 Server 20 Windows2008 Physical MS SQL 1

Windows 2008 Server 23 Windows2008 Physical MS SQL 1

Windows 2008 Server 24 Windows2008 Physical NTFS 1015

Windows 2008 Server 26 Windows2008 Physical NTFS 267

Windows 2008 Server 27 Windows2008 Physical MS SQL 30 Windows 2008 Server 28 Windows2008 Physical MS SQL 1 Windows 2008 Server 29 Windows2008 Virtual MS SQL 16

Windows 2008 Server 32 Windows2008 Virtual NTFS 19 Windows 2008 Server 33 Windows2008 Physical MS SQL 1

Windows 2008 Server 34 Windows2008 Physical NTFS 1250 Windows 2008 Server 35 Windows2008 Physical NTFS 955

Windows 2008 Server 36 Windows2008 Physical MS SQL 45 Windows XP-1 WinXP Physical MS SQL 1

Windows XP-2 WinXP Physical NTFS 131

TOTAL BACKED UP TO DISK: 2,939 GB

TOTAL BACKED UP TO TAPE: 7,241 GB

(19)

V. EVALUATION CRITERIA

The District will evaluate each proposal submitted based on responsiveness to the District’s overall needs. The award of contract, if made, will be the firm who is

responsive and responsible to all administrative and technical requirements of the RFP; who has demonstrated competence and qualifications in regards to providing the services required; the cost and prices for the services offered; and who receives the highest rating based upon all of the criteria set forth in the RFP.

The process of award will be by committee. The committee will base their evaluation on the criteria listed below then apply a score based on the weighted value of that criteria. The Supplier receiving the highest score will be awarded the contract.

A Supplier must use the following schedules, or copies thereof, in submitting a proposal. The schedules must be completed in their entirety. Other materials that support these schedules may be included in the proposal document.

10 Points: Qualifications/Experience

20 Points: Technical Requirements 25 Points: Integration

15 Points: Scope of Services 30 Points: Cost Proposal

(20)

Schedule A

CERTIFICATION OF PROPOSAL

We have read the CSD Request for Proposal and fully understand its intent. We certify that we have adequate personnel and resources to fulfill the proposal requirements. We further understand that our ability to meet the criteria and provide the required services shall be judged solely by CSD.

We further certify that, since the receipt of this RFP, no contact, discussion, or

negotiations have been made nor will be made regarding this proposal with any CSD employee or Board member other than the listed contact people in the RFP. We understand that any such contact could disqualify this proposal.

We further certify that we are properly licensed to conduct business within the scope of this RFP, in the State of Utah.

We certify that all schedules and addenda contained herein shall be considered part of the entire RFP response and that the complete document submitted shall be considered a legally binding document.

Submitted by:

Firm Name

Authorized Signature

Name and Title

Telephone

(21)

Schedule B

EXECUTIVE SUMMARY

(22)

Schedule C

DETAILED RESPONSE

This section should constitute the major portion of the proposal and must contain at least the following information.

A. A complete narrative of the Firm’s assessment of the work to be performed, the Firm’s ability and approach, and the resources necessary to fulfill the

requirements. This section should demonstrate that the Firm understands the desired overall performance expectations. Clearly indicate any options or alternatives proposed.

(23)

Schedule D

QUALIFICATIONS/EXPERIENCE

Provide a detailed response describing all abilities, skills and related experiences pertinent to the purpose and scope of this RFP.

(24)

Schedule E

REFERENCES

Provide a minimum three (3) and a maximum five (5) references. Include the organization name, contact person, and telephone number.

1. Company Name Contact Name Address

City State Zip Telephone Fax

Email

Description of Work Scope

Email

(25)

Schedule E, continued

Email

(26)

Schedule F

COST PROPOSAL

Cost will be evaluated independently from the technical proposal. Please enumerate all costs on this or an attached sheet. Pricing MSUT to be submitted in a separate file via BiDSYNC. The following is provided for your information only. Please supply your pricing per the Excel file included with this solicitation.

Vendor Product and Maintenance Pricing QTY UNIT COST TOTAL COST

Describe your pricing model. For example, list all package structures(licenses and the pricing, monthly fees, any set up

fees)

Describe any suite bundling options versus stand-alone

modules

Suite Bundling Name: ₁ _{$__________}

Includes Modules: 1.

2.

. . .

Additional required Modules not included in Suite:

1. 1 $__________

2. 1 $__________

. . . 1 $__________

Suite Bundling TOTAL: $__________

Stand-Alone Modules: 1. 1 $__________ 2. 1 $__________ . . . 1 $__________ Stand-Alone TOTAL: $__________ Hardware: 1. 1 $__________ 2. 1 $__________ . . . 1 $__________ Hardware TOTAL: $__________

Licenses - Describe any additional Licenses not included

above

1. 1 $__________

2. 1 $__________

(27)

Describe your pricing for the most basic maintenance package,

and summarize the services, deliverable and terms included (for example, bug fixes, patches, service packs and associated services)

Basic Maintenance Package- Includes:

1st Year Basic Maintenance 1 $__________

2nd and subsequent years Basic Maintenance 1 $__________

Describe your tiered pricing for the most advanced

maintenance package, and the deliverables, options and terms that differentiate it from the basic offering (including the period of coverage and response times).

Advanced Maintenance Package- Includes:

1st Year Advanced Maintenance 1 $__________

2nd and subsequent years Advanced Maintenance 1 $__________

Do you price maintenance as a percentage of total discounted license purchases (as opposed to basing it on the list price)? Do you offer caps on year-over-year increases in maintenance fees?

Describe any other miscellaneous costs to implement solution not already listed above to meet requirements.

Miscellaneous Item 1: 1 $__________

Miscellaneous Item 2: 1 $__________

Miscellaneous Items TOTAL: $__________

Training, Services and Support

Describe your professional services during implementation (service desk, incident, problem, change); include transition assistance.

Implementation Services - Includes:

1 $__________

Implementation Services TOTAL: $__________

Describe your administration training (describe options and provide costs).

(28)

Administrative Training - Option 1 1 $__________

Administrative Training - Option 2 1 $__________

Administrative Training TOTAL: $__________

Describe various technical support options available during business hours and provide pricing.

Technical Support Option 1:

1 $__________

Technical Support Option 2:

1 $__________

Technical Support TOTAL: $__________

Describe other support that is not included in the Maintenance Contracts or Technical Support Options, and provide costs.

Other Support 1 - Includes: ₁ _{$__________}

Other Support 2 - Includes:

1 $__________

Other Support TOTAL: $__________

Describe On-site support that is not included in the any above items, and provide costs.

OnSite Support - Includes:

1 $__________

OR, Daily cost of onsite support template (including hotel/food/labor - airfare to be tracked separately)

A. Hotel 1 $__________

B. Car Rental 1 $__________

C. Per Diem (food/entertainment) 1 $__________

D. Air Fare 1 $__________

E. Daily Onsite Daily Work Rate 1 $__________

F. Additional Travel Expenses Not Listed Here 1 $__________

Define: $__________

Additional desired services if not covered anywhere else

Daily Remote Service/Support - 24 x 7 x 365 1 $__________ Next business day advanced hardware replacement 1 $__________ Code/software/subscription automated updates 1 $__________ Contractor shall list any additional costs not mentioned above.

Detail of any offsite/onsite costs not covered above. Canyons School District will not pay any costs not detailed

(29)

Total of Installation and 1st year Normal Costs: $__________

Respectfully Submitted,

Name of Bidder

Title

REQUEST FOR PROPOSAL (RFP) BACKUP, RECOVERY, AND ARCHIVAL SOFTWARE SOLUTION RFP # 14GH07P3

REQUEST FOR PROPOSAL

(RFP)

BACKUP, RECOVERY, AND

ARCHIVAL SOFTWARE SOLUTION

RFP # 14GH07P3

Canyons School District

Purchasing Department

Table of Contents

CANYONS SCHOOL DISTRICT

REQUEST FOR PROPOSAL

BACKUP, RECOVERY, ARCHIVAL SOFTWARE SOLUTION

RFP #14GH07P3

I. GENERAL

II. DETAILED SCOPE OF WORK

III. REQUIREMENTS

Section/Requirement

General System

Specifications

Section/Requirement

Section/Requirement

Section/Requirement

Section/Requirement

Section/Requirement

Maintenance and Support

Vendor Responsibility

System Implementation

Project Management Methodology

Documentation, On-line Help, Error Messages

Training

Setup and Configuration

IV. CURRENT ENVIRONMENT

V. EVALUATION CRITERIA

CERTIFICATION OF PROPOSAL

DETAILED RESPONSE

QUALIFICATIONS/EXPERIENCE

REFERENCES

COST PROPOSAL