My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
OrangeBoy, LLC 10/29/2025
>
Contracts
>
Agreement
>
Software/SaaS Agreements
>
OrangeBoy, LLC 10/29/2025
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/3/2025 10:21:33 AM
Creation date
11/3/2025 10:21:11 AM
Metadata
Fields
Template:
Contracts
Contractor's Name
OrangeBoy, LLC
Approval Date
10/29/2025
End Date
10/6/2028
Department
Information Technology
Department Project Manager
Kevin Walser
Subject / Project Title
Incident Reporting for Library
Tracking Number
0005002
Total Compensation
$16,200.00
Contract Type
Agreement
Contract Subtype
Software/SaaS Agreements
Retention Period
6 Years Then Destroy
Imported from EPIC
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Download electronic document
View images
View plain text
Offsite/Cloud Addendum - 4 <br />6.20.23 <br />Data Dictionary: Vendor shall provide to <br />the City a data dictionary. <br /> Security Logs and Reports: Vendor shall allow the City access to <br />system security logs that affect the engagement under the Agreement, <br />its data and or processes. This includes the ability for the City to <br />request a report of the records that a specific user accessed over a <br />specified period of time. <br /> Contract Audit: Vendor shall allow the City to audit conformance to <br />Agreement terms, system security and data centers as appropriate. <br />The City may perform this audit or contract with a third party at its <br />at least 30 days advance written notice and shall not unreasonably <br />interfere with Vendor <br /> Subcontractor Disclosure: Vendor shall identify to City technical staff <br />all of its strategic business partners related to services provided under <br />the Agreement, including, but not limited to, all subcontractors or other <br />entities or individuals who may be a party to a joint venture or similar <br />agreement with Vendor, who will be involved in any application <br />development and/or operations. <br /> Third-Party Vendors: Vendor may use third-party vendors to provide <br />services to City. Vendor must ensure that any third-party vendor is also <br />SOC2 compliant and must provide to the City evidence of compliance <br />upon City request. <br /> Business Continuity: Vendor will maintain a comprehensive <br />continuity of operations plan consistent with SOC2 requirements and <br />will regularly review and update the plan as necessary. Vendor will <br />provide the City with notice of any changes to the continuity of <br />operations plan that may impact the City under <br />the Agreement. <br />In the event of a disruption of s operations, Vendor will <br />use commercially reasonable efforts to restore service as soon <br />as possible, consistent with SOC2 requirements. <br />Vendor will conduct regular tests of its continuity of operations <br />plan to ensure that it is effective and up-to-date. <br /> Operational Metrics: Vendor and the City technical staffs shall reach <br />agreement on operational metrics and document these metrics in the <br />Agreement or elsewhere in writing. Examples include, but are not <br />limited to: <br />Advance notice and change control for major upgrades and <br />system changes <br />System availability/uptime guarantee/agreed-upon maintenance <br />downtime
The URL can be used to link to this page
Your browser does not support the video tag.