Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.
OBLIGATIONS AND ACTIVITIES OF CONTRACTOR AS BUSINESS ASSOCIATE 1. CONTRACTOR agrees not to use or further disclose PHI COUNTY discloses to CONTRACTOR other than as permitted or required by this Business Associate Contract or as required by law. 2. XXXXXXXXXX agrees to use appropriate safeguards, as provided for in this Business Associate Contract and the Agreement, to prevent use or disclosure of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY other than as provided for by this Business Associate Contract. 3. XXXXXXXXXX agrees to comply with the HIPAA Security Rule at Subpart C of 45 CFR Part 164 with respect to electronic PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY. 4. CONTRACTOR agrees to mitigate, to the extent practicable, any harmful effect that is known to CONTRACTOR of a Use or Disclosure of PHI by CONTRACTOR in violation of the requirements of this Business Associate Contract. 5. XXXXXXXXXX agrees to report to COUNTY immediately any Use or Disclosure of PHI not provided for by this Business Associate Contract of which CONTRACTOR becomes aware. CONTRACTOR must report Breaches of Unsecured PHI in accordance with Paragraph E below and as required by 45 CFR § 164.410. 6. CONTRACTOR agrees to ensure that any Subcontractors that create, receive, maintain, or transmit PHI on behalf of CONTRACTOR agree to the same restrictions and conditions that apply through this Business Associate Contract to CONTRACTOR with respect to such information. 7. CONTRACTOR agrees to provide access, within fifteen (15) calendar days of receipt of a written request by COUNTY, to PHI in a Designated Record Set, to COUNTY or, as directed by COUNTY, to an Individual in order to meet the requirements under 45 CFR § 164.524. If CONTRACTOR maintains an Electronic Health Record with PHI, and an individual requests a copy of such information in an electronic format, CONTRACTOR shall provide such information in an electronic format. 8. CONTRACTOR agrees to make any amendment(s) to PHI in a Designated Record Set that COUNTY directs or agrees to pursuant to 45 CFR § 164.526 at the request of COUNTY or an Individual, within thirty (30) calendar days of receipt of said request by COUNTY. XXXXXXXXXX agrees to notify COUNTY in writing no later than ten (10) calendar days after said amendment is completed. 9. CONTRACTOR agrees to make internal practices, books, and records, including policies and procedures, relating to the use and disclosure of PHI received from, or created or received by CONTRACTOR on behalf of, COUNTY available to COUNTY and the Secretary in a time and manner as determined by COUNTY or as designated by the Secretary for purposes of the Secretary determining COUNTY’S compliance with the HIPAA Privacy Rule. 10. CONTRACTOR agrees to document any Disclosures of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, and to make information related to such Disclosures available as would be required for COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 11. CONTRACTOR agrees to provide COUNTY or an Individual, as directed by COUNTY, in a time and manner to be determined by COUNTY, that information collected in accordance with the Agreement, in order to permit COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 12. XXXXXXXXXX agrees that to the extent CONTRACTOR carries out COUNTY’s obligation under the HIPAA Privacy and/or Security rules CONTRACTOR will comply with the requirements of 45 CFR Part 164 that apply to COUNTY in the performance of such obligation. 13. If CONTRACTOR receives Social Security data from COUNTY provided to COUNTY by a state agency, upon request by COUNTY, CONTRACTOR shall provide COUNTY with a list of all employees, subcontractors and agents who have access to the Social Security data, including employees, agents, subcontractors and agents of its subcontractors. 14. CONTRACTOR will notify COUNTY if CONTRACTOR is named as a defendant in a criminal proceeding for a violation of HIPAA. COUNTY may terminate the Agreement, if CONTRACTOR is found guilty of a criminal violation in connection with HIPAA. COUNTY may terminate the Agreement, if a finding or stipulation that CONTRACTOR has violated any standard or requirement of the privacy or security provisions of HIPAA, or other security or privacy laws are made in any administrative or civil proceeding in which CONTRACTOR is a party or has been joined. COUNTY will consider the nature and seriousness of the violation in deciding whether or not to terminate the Agreement.
System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.
Regulatory and Special Allocations Notwithstanding the provisions of Section 6.1: (a) If there is a net decrease in Company Minimum Gain (determined according to Treasury Regulations Section 1.704-2(d)(1)) during any Fiscal Year, each Member shall be specially allocated income and gain for such Fiscal Year (and, if necessary, subsequent Fiscal Years) in an amount equal to such Member’s share of the net decrease in Company Minimum Gain, determined in accordance with Treasury Regulations Section 1.704-2(g). The items to be so allocated shall be determined in accordance with Treasury Regulations Sections 1.704-2(f)(6) and 1.704-2(j)(2). This Section 6.2(a) is intended to comply with the “minimum gain chargeback” requirement in Treasury Regulation Section 1.704-2(f) and shall be interpreted consistently therewith. (b) Member Nonrecourse Deductions shall be allocated in the manner required by Treasury Regulations Section 1.704-2(i). Except as otherwise provided in Treasury Regulations Section 1.704-2(i)(4), if there is a net decrease in Member Nonrecourse Debt Minimum Gain during any Fiscal Year, each Member that has a share of such Member Nonrecourse Debt Minimum Gain shall be specially allocated income and gain for such Fiscal Year (and, if necessary, subsequent Fiscal Years) in an amount equal to that Member’s share of the net decrease in Member Nonrecourse Debt Minimum Gain. Items to be allocated pursuant to this paragraph shall be determined in accordance with Treasury Regulations Sections 1.704-2(i)(4) and 1.704-2(j)(2). This Section 6.2(b) is intended to comply with the “minimum gain chargeback” requirements in Treasury Regulations Section 1.704-2(i)(4) and shall be interpreted consistently therewith. (c) In the event any Member unexpectedly receives any adjustments, allocations or Distributions described in Treasury Regulations Section 1.704-1(b)(2)(ii)(d)(4), (5) or (6), income and gain shall be specially allocated to such Member in an amount and manner sufficient to eliminate the Adjusted Capital Account Deficit created by such adjustments, allocations or Distributions as quickly as possible. This Section 6.2(c) is intended to comply with the qualified income offset requirement in Treasury Regulations Section 1.704-1(b)(2)(ii)(d) and shall be interpreted consistently therewith. (d) The allocations set forth in paragraphs (a), (b) and (c) above (the “Regulatory Allocations”) are intended to comply with certain requirements of the Treasury Regulations under Code Section 704. Notwithstanding any other provisions of this Article VI (other than the Regulatory Allocations), the Regulatory Allocations shall be taken into account in allocating Net Income and Net Losses among Members so that, to the extent possible, the net amount of such allocations of Net Income and Net Losses and other items and the Regulatory Allocations to each Member shall be equal to the net amount that would have been allocated to such Member if the Regulatory Allocations had not occurred. (e) The Company and the Members acknowledge that allocations like those described in Proposed Treasury Regulation Section 1.704-1(b)(4)(xii)(c) (“Forfeiture Allocations”) result from the allocations of Net Income and Net Loss provided for in this Agreement. For the avoidance of doubt, the Company is entitled to make Forfeiture Allocations and, once required by applicable final or temporary guidance, allocations of Net Income and Net Loss shall be made in accordance with Proposed Treasury Regulation Section 1.704-1(b)(4)(xii)(c) or any successor provision or guidance.
Application of other Rules and Special Commitments 1. Where a matter is governed simultaneously both by this Agreement and by another international agreement to which both Contracting Parties are parties, nothing in this Agreement shall prevent either Contracting Party or any of its investors who own investments in the territory of the other Contracting Party from taking advantage of whichever rules are more favourable to his case. 2. If the treatment to be accorded by one Contracting Party to investors of the other Contracting Party in accordance with its laws and regulations or other specific provisions of contracts is more favourable than that accorded by the Agreement, the more favourable shall be accorded.
Construction Liens (1) If any lien under the Construction Act, R.S.O. 1990, c. C30, or any like statute shall at any time be registered against the Demised Premises by reason of work done or materials supplied for or to the Tenant or for or to anyone holding an interest in the Demised Premises through the Tenant or if the Landlord is given notice of any such lien, the lien shall be discharged or vacated from the title to the Demised Premises by the Tenant within ninety (90) days after the lien is filed or sooner if the Demised Premises are in jeopardy of forfeiture or sale by the party performing the Work in respect of which the lien was filed even if the validity of the lien is being contested, if requested by the Landlord, or by a Leasehold Mortgagee. If the Tenant wishes to contest the amount or validity of any lien and has so notified the Landlord and if the Tenant has deposited with the Landlord or paid into court to the credit of the lien action the amount of the lien plus a reasonable amount for costs and has registered a discharge of such lien, the Tenant may defer payment of such lien for a period of time sufficient to enable the Tenant to contest the lien with due diligence, provided always that the Demised Premises shall not thereby become liable to forfeiture or sale. (2) The Landlord may, but shall not be obligated to, discharge or vacate any construction lien if in the Landlord's judgment, exercised reasonably, the Demised Premises become liable to immediate forfeiture or sale or the Demised Premises is otherwise in jeopardy, and any amount paid by the Landlord in so doing, shall be reimbursed to the Landlord by the Tenant as Additional Rent within thirty (30) days after demand. If a construction lien is not discharged and vacated within three (3) months of registration, notwithstanding that the lien may be contested, the Landlord shall have the right, on written notice to the Tenant, to terminate the Lease. (3) Nothing herein contained shall authorize Tenant, or imply any consent or agreement or request on the part of the Landlord to subject the Landlord's estate or interest in the Demised Premises and/or the Building to any construction lien or any other lien of any nature or kind whatsoever. Notice is hereby given to all parties that the Landlord expressly refuses and denies any consent or agreement or request to permit their estate or interest in the Demised Premises and/or the Building to be subject to any construction lien or other lien of any nature or kind whatsoever without the express written agreement of the Landlord to this effect. Tenant acknowledges that the Landlord is not, and should not be held to be, an owner as that term is defined in the Construction Act with respect to the construction of any work on the Demised Premises by, or on behalf of Tenant.
Notice to Proceed - Site Improvements The Recipient shall not commence, or cause to be commenced, any site improvements or other work on the Land until the Director has issued a Notice to Proceed to the Recipient. Such Notice to Proceed will not be issued until the Director is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and has completed any land acquisition required by the Project. A Notice to Proceed shall be required for all Project prime contractors or direct procurement initiated by the Recipient following execution of this Agreement.
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Subloop that may diminish the capability of the Loop or Subloop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the BellSouth’s TR 73600 Unbundled Local Loop Technical Specification. 2.5.2 BellSouth will remove load coils only on copper Loops and Subloops that are less than eighteen thousand (18,000) feet in length. 2.5.3 For any copper loop being ordered by NewPhone which has over six thousand (6,000) feet of combined bridged tap will be modified, upon request from NewPhone, so that the loop will have a maximum of six thousand (6,000) feet of bridged tap. This modification will be performed at no additional charge to NewPhone. Loop conditioning orders that require the removal of bridged tap that serves no network design purpose on a copper Loop that will result in a combined total of bridged tap between two thousand five hundred (2,500) and six thousand (6,000) feet will be performed at the rates set forth in Exhibit A. 2.5.4 NewPhone may request removal of any unnecessary and non-excessive bridged tap (bridged tap between zero (0) and two thousand five hundred (2,500) feet which serves no network design purpose), at rates pursuant to BellSouth’s SC Process as mutually agreed to by the Parties. 2.5.5 Rates for ULM are as set forth in Exhibit A. 2.5.6 BellSouth will not modify a Loop in such a way that it no longer meets the technical parameters of the original Loop type (e.g., voice grade, ADSL, etc.) being ordered. 2.5.7 If NewPhone requests ULM on a reserved facility for a new Loop order, BellSouth may perform a pair change and provision a different Loop facility in lieu of the reserved facility with ULM if feasible. The Loop provisioned will meet or exceed specifications of the requested Loop facility as modified. NewPhone will not be charged for ULM if a different Loop is provisioned. For Loops that require a DLR or its equivalent, BellSouth will provide LMU detail of the Loop provisioned. 2.5.8 NewPhone shall request Loop make up information pursuant to this Attachment prior to submitting a service inquiry and/or a LSR for the Loop type that NewPhone desires BellSouth to condition. 2.5.9 When requesting ULM for a Loop that BellSouth has previously provisioned for NewPhone, NewPhone will submit a SI to BellSouth. If a spare Loop facility that meets the Loop modification specifications requested by NewPhone is available at the location for which the ULM was requested, NewPhone will have the option to change the Loop facility to the qualifying spare facility rather than to provide ULM. In the event that BellSouth changes the Loop facility in lieu of providing ULM, NewPhone will not be charged for ULM but will only be charged the service order charges for submitting an order.
Data Protection Impact Assessment and Prior Consultation Processor shall provide reasonable assistance to the Company with any data protection impact assessments, and prior consultations with Supervising Authorities or other competent data privacy authorities, which Company reasonably considers to be required by article 35 or 36 of the GDPR or equivalent provisions of any other Data Protection Law, in each case solely in relation to Processing of Company Personal Data by, and taking into account the nature of the Processing and information available to, the Contracted Processors.
