Copies of Data/Exit Strategy Sample Clauses

Copies of Data/Exit Strategy. Upon request of the City or in the event this Agreement is terminated, Contractor shall work with the City to ensure a smooth transition of all Data and Software to the City’s new environment. Additionally, upon request by the City and at no additional cost, Contractor shall provide City with a database export of the Data in a format acceptable to the City. At the termination of this Agreement, all Data at the Contractor’s (or Contractor’s subcontractor’s) facilities shall be purged when the City confirms that it has received a satisfactory copy of the Data. Contractor shall provide written verification to the City once all City Data has been purged.
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
Copies of Data/Exit Strategy. Upon request of the City or in the event this Agreement is terminated, Contractor shall work with the City to ensure a smooth transition of all Data and Software to the City’s new environment, including, but not limited to, providing the City with a copy of current source code, support materials, and sufficient time to effect the transition. City agrees to only use such code and materials to support the City’s use of the Software. Additionally, upon request by the City and at no additional cost, Contractor shall provide City with a database export of the Data in a format acceptable to the City. At the termination of this Agreement, all Data at the Contractor’s (or Contractor’s subcontractor’s) facilities shall be purged when the City confirms that it has received a satisfactory copy of the Data. Contractor shall provide written verification to the City once all City Data has been purged. All City Data provided to Contractor for the performance of the services specified herein is owned by the City and must be returned to the City upon contract termination.
Sample 1Sample 2Sample 3See All (4)

Related to Copies of Data/Exit Strategy

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Contact Information for Privacy and Security Officers and Reports 2.1 Business Associate shall provide, within ten (10) days of the execution of this Agreement, written notice to the Contract or Grant manager the names and contact information of both the HIPAA Privacy Officer and HIPAA Security Officer of the Business Associate. This information must be updated by Business Associate any time these contacts change.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!