Ownership and Responsibilities Clause Samples

Ownership and Responsibilities. 2.1 As TU and TUSU are separate legal entities, both are individually registered as Data Controllers with the ICO as follows:

Ownership and Responsibilities. 5.1. Responsibility for this document rests with the Director of Nursing, Maternity & Allied Health Professionals. 5.2. The author of this Policy is ▇▇▇▇▇ ▇▇▇▇▇▇, Named Nurse for Safeguarding Children, RCHT in partnership with ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, Head of Service, East Cornwall, Children and Family Services. 5.3. Role of the Managers 5.4. Role of the SCOG Group/Committee 5.5. Role of Individual Staff

Ownership and Responsibilities. 3.1 El Toro shall be the sole owner of Project facilities. Metropolitan shall have no ownership right, title, security interest or other interest in the Project facilities. 3.2 El Toro shall be solely responsible for all design, environmental compliance, right-of- way acquisitions, permits, construction, and cost of the Project and all modifications thereof. 3.3 El Toro shall be solely responsible for operating and maintaining the Project, in accordance with all applicable local, state, and federal laws. Metropolitan shall have no rights, duties or responsibilities for operation and maintenance of Project facilities. 3.4 El Toro shall install, operate, and maintain metering devices for the purpose of measuring the quantity of Recovered Water and Allowable Yield delivered to each End User. 3.5 El Toro shall also provide electrical metering devices to accurately measure the energy used for the Project to determine incurred operation and maintenance costs. Metropolitan shall not pay for electrical energy costs if El Toro fails to install electrical metering devices. 3.6 El Toro shall at all times during the term of this Agreement, use its best efforts to operate the Project facilities to maximize Allowable Yield on a sustained basis. 3.7 El Toro shall assist Metropolitan in its effort to forecast future Project production and cost. 3.8 El Toro shall notify and provide Metropolitan with a copy of relevant agreements and payments if El Toro decides to convey water using Project facilities to any party that is not an End User.

Ownership and Responsibilities. Fishers will own and maintain the Southern Trunk Line between ▇▇▇▇▇ ▇▇▇▇▇▇ and ▇▇▇▇▇ ▇▇▇▇▇▇ from the INDOT right-of-way line west to and including the outfall as shown in Exhibit B. 2.2.1. All costs, including but not limited to, post-construction maintenance, inspection, repair and reconstruction will be the financial responsibility of Fishers. 2.2.2. Fishers shall submit maintenance plans upon initial completion of the Project and upon request of INDOT. All documentation obtained by Fishers concerning the Southern Trunk Line, including, but not limited to, reports and videos, from routine maintenance shall be shared with INDOT.

Ownership and Responsibilities. Client acknowledges that (i) Authorized Data is owned by Connected Users and is not owned or controlled by Validic and (ii) as between Validic and Client, Client shall be solely responsible for all use, storage, and disclosure of Authorized Data received by it.

Ownership and Responsibilities. 3.1 EVWD shall be the sole owner of all Project facilities. Valley District shall have no ownership right, title, security interest or other interest in the Project facilities. 3.2 EVWD shall be solely responsible for all design, environmental compliance, right-of-way acquisitions, permits, construction, and cost of the Project and all modifications thereof. 3.3 EVWD shall be solely responsible for operating and maintaining the Project, in accordance with all applicable federal, state, and local laws, ordinances, rules, and regulations. Valley District shall have no rights, duties or responsibilities for operation and maintenance of Project facilities. 3.4 EVWD shall install, operate, and maintain metering devices for the purpose of measuring the quantity of Recycled Water and Allowable Yield delivered to Valley District. Said

Ownership and Responsibilities. Equipment and applications within the scope of this policy must be administered by support groups approved by Information Technology Security for DMZ system, application, and/or network management. Support groups will be responsible for the following:  Equipment must be documented in the corporate wide enterprise management system. At a minimum, the following information is required: o Host contacts and location. o Hardware and operating system/version. o Main functions and applications. o Password groups for privileged passwords.  Network interfaces must have appropriate Domain Name Server records (minimum of A and PTR records).  Password groups must be maintained in accordance with the corporate wide password management system/process.  Immediate access to equipment and system logs must be granted to members of Information Technology Security upon demand, per the Audit Policy.  Changes to existing equipment and deployment of new equipment must follow and corporate governess or change management processes/procedures. To verify compliance with this policy, Information Technology Security will periodically audit DMZ equipment per the Audit Policy.

Ownership and Responsibilities. 3.1 Except as may be provided by separate agreement of the Parties, Participant shall be the sole owner of all Project facilities. Valley District shall acquire no ownership right, title, security interest or other interest in the Project facilities as a result of the LRIP or this Agreement. 3.2 Participant shall be solely responsible for all design, environmental compliance, right-of- way acquisitions, permits, construction, and cost of the Project and all modifications thereof.

Ownership and Responsibilities. 1. All facilities covered by this policy must present a University mission justification with sign-off at the Vice President level. Information Technology Security must keep the business justifications on file. 2. Facility owning organizations are responsible for assigning facility managers, point of contact (POC), and back up POC, for each facility. The facilitiy owners must maintain up to date POC information with Information Technology Security. Facility managers or their backup must be available around-the-clock for emergencies by an immediate electronic contact method. 3. Changes to the connectivity and/or purpose of existing facilities and establishment of new DMZ Labs must be requested through and approved by Information Technology Security. 4. All network connections must be maintained by a Information Networks. 5. Information Networks must maintain a firewall device between the facility, the remainder of the non-public campus network and the Internet. 6. Information Networks and Information Technology Security may interrupt lab connections if a security concern exists. 7. The facility will provide and maintain network devices deployed up to the Information Networks’ point of demarcation. 8. The Information Networks must manage and maintain all IP address space. 9. The facility managers are ultimately responsible for their facilities complying with this policy. 10. Immediate access to equipment and system logs must be granted to members of Information Technology Security and the Information Networks upon request, in accordance with the Audit Policy 11. Individual lab accounts which provide access to facilities must be deleted within three (3) days when access is no longer authorized. Group accounts are not permitted. 12. Information Technology Security will address non-compliance waiver requests on a case- by-case basis.