Business Purpose The Company may conduct any and all lawful business appropriate in carrying out the Company’s objectives, as permitted under Section 00-00-000 of the Act.
Business Purposes The Loan is solely for the business purpose of Borrower, and is not for personal, family, household, or agricultural purposes.
Partnership Agreements Each of the partnership agreements, declarations of trust or trust agreements, limited liability company agreements (or other similar agreements) and, if applicable, joint venture agreements to which the Company or any of its subsidiaries is a party has been duly authorized, executed and delivered by the Company or the relevant subsidiary, as the case may be, and constitutes the valid and binding agreement of the Company or such subsidiary, as the case may be, enforceable in accordance with its terms, except as the enforcement thereof may be limited by (A) the effect of bankruptcy, insolvency or other similar laws now or hereafter in effect relating to or affecting creditors’ rights generally or (B) the effect of general principles of equity, and the execution, delivery and performance of such agreements did not, at the time of execution and delivery, and does not constitute a breach of or default under the charter or bylaws, partnership agreement, declaration of trust or trust agreement, or limited liability company agreement (or other similar agreement), as the case may be, of the Company or any of its subsidiaries or any of the Agreements and Instruments or any law, administrative regulation or administrative or court order or decree.
Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its Reliability Planning Process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Short-Term Reliability Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the STAR or Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Short-Term Reliability Process Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.
Operating Partnership Agreement The Operating Partnership Agreement, in substantially the form attached hereto as Exhibit B, shall have been executed and delivered by the partners of the Operating Partnership and shall be in full force and effect and, except as contemplated by Section 2.03 or the other Formation Transaction Documents, shall not have been amended or modified.
Permitted Uses and Disclosures of Phi by Business Associate Except as otherwise indicated in this Agreement, Business Associate may use or disclose PHI, inclusive of de-identified data derived from such PHI, only to perform functions, activities or services specified in this Agreement on behalf of DHCS, provided that such use or disclosure would not violate HIPAA or other applicable laws if done by DHCS.
Operating Agreement The Borrower will not amend, modify, waive or terminate any provision of its operating agreement without the prior written consent of the Administrative Agent.
Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.
Unbundled Copper Loop – Non-Designed (UCL-ND 2.4.3.1 The UCL–ND is provisioned as a dedicated 2-wire metallic transmission facility from BellSouth’s Main Distribution Frame to a customer’s premises (including the NID). The UCL-ND will be a “dry copper” facility in that it will not have any intervening equipment such as load coils, repeaters, or digital access main lines (“DAMLs”), and may have up to 6,000 feet of bridged tap between the end user’s premises and the serving wire center. The UCL-ND typically will be 1300 Ohms resistance and in most cases will not exceed 18,000 feet in length, although the UCL-ND will not have a specific length limitation. For loops less than 18,000 feet and with less than 1300 Ohms resistance, the loop will provide a voice grade transmission channel suitable for loop start signaling and the transport of analog voice grade signals. The UCL-ND will not be designed and will not be provisioned with either a DLR or a test point.
2.4.3.2 The UCL-ND facilities may be mechanically assigned using BellSouth’s assignment systems. Therefore, the Loop Make Up process is not required to order and provision the UCL-ND. However, Talk America can request Loop Make Up for which additional charges would apply.
2.4.3.3 At an additional charge, BellSouth also will make available Loop Testing so that Talk America may request further testing on the UCL-ND.
2.4.3.4 UCL-ND loops are not intended to support any particular service and may be utilized by Talk America to provide a wide-range of telecommunications services so long as those services do not adversely affect BellSouth’s network. The UCL- ND will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the loop to the customer’s inside wire.
2.4.3.5 Order Coordination (OC) will be provided as a chargeable option and may be utilized when the UCL-ND provisioning is associated with the reuse of BellSouth facilities. Order Coordination -Time Specific (OC-TS) does not apply to this product.
2.4.3.6 Talk America may use BellSouth’s Unbundled Loop Modification (ULM) offering to remove bridge tap and/or load coils from any loop within the BellSouth network. Therefore, some loops that would not qualify as UCL-ND could be transformed into loops that do qualify, using the ULM process.
Vendor Encouraging Members to bypass TIPS agreement Encouraging entities to purchase directly from the Vendor or through another agreement, when the Member has requested using the TIPS cooperative Agreement or price, and thereby bypassing the TIPS Agreement is a violation of the terms and conditions of this Agreement and will result in removal of the Vendor from the TIPS Program.
