Common use of Infrastructure Management Clause in Contracts

Infrastructure Management. 3.2.1 Provider’s Surface Optimization System shall support up to 100 simultaneous users. 3.2.2 Provider’s Services shall ensure that an unlimited number of transactions may be processed to County production database, but Provider may recommend that non-routine reports and queries be limited to certain timeframes, quantities or other specifications if Provider determines that such reports and queries cause degradation to response times affecting performance levels established in the SLA. 3.2.3 Provider will retain all database records for the Surface Optimization System regardless of number or size for a period of thirty (30) days from the date of creation of the record 3.2.4 Provider shall routinely apply upgrades, new releases, and enhancements to the System as they become available and shall ensure that these changes will not adversely affect the System. 3.2.5 To the extent Provider’s System includes an ad-hoc reporting tool and/or standard reports, Provider agrees to provide unlimited access to such functionality to County. Provider agrees to support an unlimited number of queries and reports against County’s data. County agrees that Provider may put reasonable size limits on queries and reports to maintain System performance, provided such limits do not materially impact County’s regular business operations. 3.2.6 A development and test system for Surface Optimization, which shall mirror the production system, shall be made available for use by County for testing purposes upon five (5) business days' request, including without limitation, upon request for County’s testing of application upgrades and fixes prior to installation in the production environment. 3.2.7 A demonstration/training system will be available for use by County upon five (5) business days' request. County may control data that is populated on the demonstration/training system by requesting that Provider: a) periodically refresh data from production; b) perform an ad-hoc refresh of data from production; c) not refresh data from production until further notice from County; or d) refresh data on an ad hoc basis with training data supplied by County.

Infrastructure Management. 3.2.1 4.2.1. During Prime Time, Provider shall ensure packet loss of less than one percent (1%) and less than sixty (60) milliseconds domestic latency within the Provider Platform. Provider shall maintain sufficient bandwidth to the Provider Platform and ensure the server processing time (or CPU processing capacity) to provide millisecond response times from the server. County and Provider recognize that end user response times are dependent on intermittent ISP network connectivity, and in the case of County's users, dependent on County's internal network health. 4.2.2. To the extent the Provider Platform provides or supports public access to users in Broward County or through the County's web pages, Provider’s Surface Optimization System 's Services shall support up to 100 simultaneous users500,000 site hits per calendar day and capture the number of site hits by page for performance to standards reporting. 3.2.2 Provider’s Services 4.2.3. Provider shall ensure that an unlimited number of transactions may be processed to County production database. Subject to County approval, but Provider may recommend that non-routine reports and queries be limited to certain timeframes, quantities or other specifications if Provider determines that such reports and queries cause degradation to response times affecting performance levels established in the this SLA. 3.2.3 4.2.4. Provider will retain all database records for the Surface Optimization System regardless of number or size for a period of thirty (30) days from the date of creation of the recordsize. 3.2.4 4.2.5. Provider shall routinely apply upgrades, new releases, and enhancements to the System Provider Platform as they become available after prior, written approval by the County and shall ensure that these changes will not adversely affect the SystemProvider Platform. 3.2.5 4.2.6. To the extent Provider’s System the Provider Platform includes an ad-hoc reporting tool and/or or standard reports, Provider agrees to provide unlimited access to such functionality to County. Provider agrees to support an unlimited number of queries and reports against County’s data's Data. County agrees that Provider may put reasonable size limits on queries and reports to maintain System performance, provided such limits do not materially impact County’s 's regular business operations. 3.2.6 4.2.7. Provider shall conduct full, encrypted System backups (including System and user data) weekly and shall conduct incremental, encrypted backups daily. Encrypted backups will be written to a backup device with sufficient capacity to handle the data. Provider shall maintain a complete current set of encrypted backups for County's System, including County Data, at a remote, off-site "hardened" facility from which data can be retrieved within one (1) business day at any point in time. Full System restoration performed as a recovery procedure after a natural disaster is included as part of Provider's required Services under this Agreement. Upon County's request, Provider shall also provide restoration of individual file(s). 4.2.8. A development and test system for Surface Optimizationsystem, which shall mirror the production system, shall be made available for use by County for testing or training purposes upon five two (52) business days' request, including without limitation, upon request for County’s 's testing of application upgrades and fixes prior to installation in the production environment. 3.2.7 A demonstration/training system will be available for use by County upon five (5) business days' request. County may control data that is populated on the demonstration/demonstration and training system by requesting that ProviderProvider perform any or all of the following: a) 4.2.8.1. periodically refresh data from production; b) 4.2.8.2. perform an ad-hoc refresh of data from production; c) 4.2.8.3. not refresh data from production until further notice from County; or d) 4.2.8.4. refresh data on an ad hoc basis with training data supplied by County.