Systems, Processes and Documentation Sample Clauses

Systems, Processes and Documentation. Excellent proposals will describe the systems, processes, and substantiating documentation (see 5.2.9.3 Section F for examples) that the Proposer has or will put in place that will allow the Proposer to accurately track and publicly report on the commitments, data, and unique key performance indicators associated with Proposer’s commitments. 5.2.9.3 SIP Work Approach Covered Contract SIP Program Requirements
AutoNDA by SimpleDocs
Systems, Processes and Documentation. Excellent proposals will describe the systems, processes, and substantiating documentation (see 5.2.11.3 Section F for examples) that the Proposer has or will put in place that will allow the Proposer to accurately track and publicly report on the commitments, data, and unique key performance indicators associated with Proposer’s commitments.

Related to Systems, Processes and Documentation

  • Subprocessors Provider shall enter into written agreements with all Subprocessors performing functions for the Provider in order for the Provider to provide the Services pursuant to the Service Agreement, whereby the Subprocessors agree to protect Student Data in a manner no less stringent than the terms of this DPA.

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • Data Ownership and Authorized Access 1. Student Data Property of LEA. All Student Data transmitted to the Provider pursuant to the Service Agreement is and will continue to be the property of and under the control of the LEA. The Provider further acknowledges and agrees that all copies of such Student Data transmitted to the Provider, including any modifications or additions or any portion thereof from any source, are subject to the provisions of this DPA in the same manner as the original Student Data. The Parties agree that as between them, all rights, including all intellectual property rights in and to Student Data contemplated per the Service Agreement, shall remain the exclusive property of the LEA. For the purposes of FERPA, the Provider shall be considered a School Official, under the control and direction of the LEA as it pertains to the use of Student Data, notwithstanding the above.

  • Authorized Use The Student Data shared pursuant to the Service Agreement, including persistent unique identifiers, shall be used for no purpose other than the Services outlined in Exhibit A or stated in the Service Agreement and/or otherwise authorized under the statutes referred to herein this DPA.

  • Provide Data in Compliance with Applicable Laws LEA shall provide Student Data for the purposes of obtaining the Services in compliance with all applicable federal, state, and local privacy laws, rules, and regulations, all as may be amended from time to time.

  • Subprocessor For the purposes of this DPA, the term “Subprocessor” (sometimes referred to as the “Subcontractor”) means a party other than LEA or Provider, who Provider uses for data collection, analytics, storage, or other service to operate and/or improve its service, and who has access to Student Data.

  • Training a. The employer, in consultation with the local, shall be responsible for developing and implementing an ongoing harassment and sexual harassment awareness program for all employees. Where a program currently exists and meets the criteria listed in this agreement, such a program shall be deemed to satisfy the provisions of this article. This awareness program shall initially be for all employees and shall be scheduled at least once annually for all new employees to attend.

  • SERVICE REQUIREMENTS FOR REFERRED CLIENTS A. Agent agrees to respond to any communications from a Referred Client within two (2) hours after receipt if such communication is received between 9:00am to 5:00pm local time. For communications received outside of these hours, Agent agrees to respond by 10:00am the next day.

  • Access Registry Operator will have the file(s) ready for download as of 00:00:00 UTC on the day designated for retrieval by ICANN. The file(s) will be made available for download by SFTP, though ICANN may request other means in the future.

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