Use and Access to Public Body’s Data Sample Clauses

Use and Access to Public Body’s Data. Upon the effective date of termination or cancellation of this Exhibit, Public Body’s data shall not be useable by or accessible to any other CLEMIS Member.
AutoNDA by SimpleDocs

Related to Use and Access to Public Body’s Data

  • Access to Public Records No records of District shall be made available for public inspection or copying by NWRDC, NWESD, or XXXXX without express written authorization of District. Requests pursuant to RCW 42.17 for inspection or copying of public records of District, held or maintained by NWRDC shall be referred to District.

  • RELEASE OF GENERAL INFORMATION TO THE PUBLIC AND MEDIA NASA or Partner may, consistent with Federal law and this Agreement, release general information regarding its own participation in this Agreement as desired. Pursuant to Section 841(d) of the NASA Transition Authorization Act of 2017, Public Law 115-10 (the "NTAA"), NASA is obligated to publicly disclose copies of all agreements conducted pursuant to NASA's 51 U.S.C. §20113(e) authority in a searchable format on the NASA website within 60 days after the agreement is signed by the Parties. The Parties acknowledge that a copy of this Agreement will be disclosed, without redactions, in accordance with the NTAA.

  • Access to Site 3.05.1 Contractor may enter and leave the premises at all reasonable times without charge. Contractor and its employees may use the common areas and roadways of the premises where it is to perform the services together with all facilities, equipment, improvements, and services provided in connection with the premises for common use. This excludes parking for Contractor’s personnel. Contractor shall repair any damage caused by it or its employees as a result of its use of the common areas.

  • Access to NID 2.7.3.1 NewPhone may access the customer’s premises wiring by any of the following means and NewPhone shall not disturb the existing form of electrical protection and shall maintain the physical integrity of the NID: 2.7.3.1.1 BellSouth shall allow NewPhone to connect its Loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premises; 2.7.3.1.2 Where an adequate length of the customer’s premises wiring is present and environmental conditions permit, either Party may remove the customer premises wiring from the other Party’s NID and connect such wiring to that Party’s own NID; 2.7.3.1.3 Either Party may enter the subscriber access chamber or dual chamber NID enclosures for the purpose of extending a cross-connect or spliced jumper wire from the customer premises wiring through a suitable “punch-out” hole of such NID enclosures; or 2.7.3.1.4 NewPhone may request BellSouth to make other rearrangements to the customer premises wiring terminations or terminal enclosure on a time and materials cost basis. 2.7.3.2 In no case shall either Party remove or disconnect the other Party’s loop facilities from either Party’s NIDs, enclosures, or protectors unless the applicable Commission has expressly permitted the same and the disconnecting Party provides prior notice to the other Party. In such cases, it shall be the responsibility of the Party disconnecting loop facilities to leave undisturbed the existing form of electrical protection and to maintain the physical integrity of the NID. It will be NewPhone’s responsibility to ensure there is no safety hazard, and NewPhone will hold BellSouth harmless for any liability associated with the removal of the BellSouth Loop from the BellSouth NID. Furthermore, it shall be the responsibility of the disconnecting Party, once the other Party’s loop has been disconnected from the NID, to reconnect the disconnected loop to a nationally recognized testing laboratory listed station protector, which has been grounded as per Article 800 of the National Electrical Code. If no spare station protector exists in the NID, the disconnected loop must be appropriately cleared, capped and stored. 2.7.3.3 NewPhone shall not remove or disconnect ground wires from BellSouth’s NIDs, enclosures, or protectors. 2.7.3.4 NewPhone shall not remove or disconnect NID modules, protectors, or terminals from BellSouth’s NID enclosures. 2.7.3.5 Due to the wide variety of NID enclosures and outside plant environments, BellSouth will work with NewPhone to develop specific procedures to establish the most effective means of implementing this section if the procedures set forth herein do not apply to the NID in question.

  • Access to PHI Business Associate shall provide access to PHI in a Designated Record Set to Covered Entity or as directed by Covered Entity to an Individual to meet the requirements under 45 CFR § 164.524. Business Associate shall provide such access in the time and manner reasonably designated by Covered Entity. Within three (3) business days, Business Associate shall forward to Covered Entity for handling any request for access to PHI that Business Associate directly receives from an Individual.

  • Access to Protected Information If BA maintains a designated record set on behalf of CE, BA shall make Protected Information maintained by BA or its agents or subcontractors in Designated Record Sets available to CE for inspection and copying within five (5) days of a request by CE to enable CE to fulfill its obligations under state law [Health and Safety Code Section 123110] and the Privacy Rule, including, but not limited to, 45 C.F.R. Section 164.524 [45 C.F.R. Section 164.504(e)(2)(ii)(E)]. If BA maintains Protected Information in electronic format, BA shall provide such information in electronic format as necessary to enable CE to fulfill its obligations under the HITECH Act and HIPAA Regulations, including, but not limited to, 42 U.S.C. Section 17935(e) and 45 C.F.R. Section 164.524.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Confidential System Information HHSC prohibits the unauthorized disclosure of Other Confidential Information. Grantee and all Grantee Agents will not disclose or use any Other Confidential Information in any manner except as is necessary for the Project or the proper discharge of obligations and securing of rights under the Contract. Grantee will have a system in effect to protect Other Confidential Information. Any disclosure or transfer of Other Confidential Information by Xxxxxxx, including information requested to do so by HHSC, will be in accordance with the Contract. If Grantee receives a request for Other Confidential Information, Xxxxxxx will immediately notify HHSC of the request, and will make reasonable efforts to protect the Other Confidential Information from disclosure until further instructed by the HHSC. Grantee will notify HHSC promptly of any unauthorized possession, use, knowledge, or attempt thereof, of any Other Confidential Information by any person or entity that may become known to Grantee. Grantee will furnish to HHSC all known details of the unauthorized possession, use, or knowledge, or attempt thereof, and use reasonable efforts to assist HHSC in investigating or preventing the reoccurrence of any unauthorized possession, use, or knowledge, or attempt thereof, of Other Confidential Information. HHSC will have the right to recover from Grantee all damages and liabilities caused by or arising from Grantee or Grantee Agents’ failure to protect HHSC’s Confidential Information as required by this section.

  • Access to Personal Information by Subcontractors Supplier agrees to require any subcontractors or agents to which it discloses Personal Information under this Agreement or under any SOW to provide reasonable assurance, evidenced by written contract, that they will comply with the same or substantially similar confidentiality, privacy and security obligations with respect to such Personal Information as apply to Supplier under this Agreement or any SOW. Supplier shall confirm in writing to DXC that such contract is in place as a condition to DXC’s approval of use of a subcontractor in connection with any SOW. Upon request of DXC, Supplier will provide to DXC a copy of the subcontract or an extract of the relevant clauses. Supplier shall ensure that any failure on the part of any subcontractor or agent to comply with the Supplier obligations under this Agreement or any SOW shall be grounds to promptly terminate such subcontractor or agent. If during the term of this Agreement or any SOW, DXC determines, in its exclusive discretion, that any Supplier subcontractor or agent cannot comply with the Supplier obligations under this Agreement or with any SOW, then DXC may terminate this Agreement in whole or in part (with respect to any SOW for which such subcontractor or agent is providing services), if not cured by Supplier within the time prescribed in the notice of such deficiency.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

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