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.
Denominations: Provisions for Payment The Securities shall be issuable as registered Securities and in the denominations of one thousand U.S. dollars ($1,000) or any integral multiple thereof, subject to Section 2.01(a)(13). The Securities of a particular series shall bear interest payable on the dates and at the rate specified with respect to that series. Subject to Section 2.01(a)(23), the principal of and the interest on the Securities of any series, as well as any premium thereon in case of redemption or repurchase thereof prior to maturity, and any cash amount due upon conversion or exchange thereof, shall be payable in the coin or currency of the United States of America that at the time is legal tender for public and private debt, at the office or agency of the Company maintained for that purpose. Each Security shall be dated the date of its authentication. Interest on the Securities shall be computed on the basis of a 360-day year composed of twelve 30-day months. The interest installment on any Security that is payable, and is punctually paid or duly provided for, on any Interest Payment Date for Securities of that series shall be paid to the Person in whose name said Security (or one or more Predecessor Securities) is registered at the close of business on the regular record date for such interest installment. In the event that any Security of a particular series or portion thereof is called for redemption and the redemption date is subsequent to a regular record date with respect to any Interest Payment Date and prior to such Interest Payment Date, interest on such Security will be paid upon presentation and surrender of such Security as provided in Section 3.03. Any interest on any Security that is payable, but is not punctually paid or duly provided for, on any Interest Payment Date for Securities of the same series (herein called “Defaulted Interest”) shall forthwith cease to be payable to the registered holder on the relevant regular record date by virtue of having been such holder; and such Defaulted Interest shall be paid by the Company, at its election, as provided in clause (1) or clause (2) below:
(1) The Company may make payment of any Defaulted Interest on Securities to the Persons in whose names such Securities (or their respective Predecessor Securities) are registered in the Security Register at the close of business on a special record date for the payment of such Defaulted Interest, which shall be fixed in the following manner: the Company shall notify the Trustee in writing of the amount of Defaulted Interest proposed to be paid on each such Security and the date of the proposed payment, and at the same time the Company shall deposit with the Trustee an amount of money equal to the aggregate amount proposed to be paid in respect of such Defaulted Interest or shall make arrangements satisfactory to the Trustee for such deposit prior to the date of the proposed payment, such money when deposited to be held in trust for the benefit of the Persons entitled to such Defaulted Interest as in this clause provided. Thereupon the Trustee shall fix a special record date for the payment of such Defaulted Interest which shall not be more than 15 nor less than 10 days prior to the date of the proposed payment and not less than 10 days after the receipt by the Trustee of the notice of the proposed payment. The Trustee shall promptly notify the Company of such special record date and, in the name and at the expense of the Company, shall cause notice of the proposed payment of such Defaulted Interest and the special record date therefor to be sent, to each Securityholder not less than 10 days prior to such special record date. Notice of the proposed payment of such Defaulted Interest and the special record date therefor having been sent as aforesaid, such Defaulted Interest shall be paid to the Persons in whose names such Securities (or their respective Predecessor Securities) are registered in the Security Register on such special record date.
(2) The Company may make payment of any Defaulted Interest on any Securities in any other lawful manner not inconsistent with the requirements of any securities exchange on which such Securities may be listed, and upon such notice as may be required by such exchange, if, after notice given by the Company to the Trustee of the proposed payment pursuant to this clause, such manner of payment shall be deemed practicable by the Trustee. Unless otherwise set forth in a Board Resolution or one or more indentures supplemental hereto establishing the terms of any series of Securities pursuant to Section 2.01 hereof, the term “regular record date” as used in this Section with respect to a series of Securities and any Interest Payment Date for such series shall mean either the fifteenth day of the month immediately preceding the month in which an Interest Payment Date established for such series pursuant to Section 2.01 hereof shall occur, if such Interest Payment Date is the first day of a month, or the first day of the month in which an Interest Payment Date established for such series pursuant to Section 2.01 hereof shall occur, if such Interest Payment Date is the fifteenth day of a month, whether or not such date is a Business Day. Subject to the foregoing provisions of this Section, each Security of a series delivered under this Indenture upon transfer of or in exchange for or in lieu of any other Security of such series shall carry the rights to interest accrued and unpaid, and to accrue, that were carried by such other Security.
Certification of Funds; Budget and Fiscal Provisions; Termination in the Event of Non-Appropriation This Agreement is subject to the budget and fiscal provisions of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement. THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Modifications and Updates to the Wire Center List and Subsequent Transition Periods 5.4.6.1 In the event AT&T identifies additional wire centers that meet the criteria set forth in Sections 5.4.2.1 or 5.4.2.2 above, but that were not included in the Master List of Unimpaired Wire Centers or AT&T’s List of Unimpaired Wire Centers, AT&T shall include such additional wire centers in a CNL. Each such list of additional wire centers shall be considered a Subsequent Wire Center List. AT&T will follow any limitations on the frequency with which it may issue such lists and notification procedures set forth in applicable Commission orders.
5.4.6.2 TWTC shall have thirty (30) business days to dispute the additional wire centers listed on AT&T’s CNL. Absent such dispute, effective thirty (30) business days after the date of a AT&T CNL providing a Subsequent Wire Center List, AT&T shall not be required to provide DS1 and DS3 Dedicated Transport, as applicable, in such additional wire center(s), except pursuant to the self-certification process as set forth in Section 1.9.1 of this Attachment.
5.4.6.3 For purposes of Section 5.4.6.1 above, AT&T shall make available DS1 and DS3 Dedicated Transport that were in service for TWTC in a wire center on the Subsequent Wire Center List as of the thirtieth (30th) business day after the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Embedded Base) until one hundred eighty (180) days after the thirtieth (30th) business day Version: 4Q06 Standard ICA 11/30/06 from the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Transition Period).
5.4.6.4 The rates set forth in Exhibit B shall apply to the Subsequent Embedded Base during the Subsequent Transition Period.
5.4.6.5 No later than one hundred eighty (180) days from AT&T’s CNL identifying the Subsequent Wire Center List, TWTC shall submit an LSR(s) or spreadsheet(s) as applicable, identifying the Subsequent Embedded Base of circuits to be disconnected or converted to other AT&T services.
5.4.6.5.1 In the case of disconnection, the applicable disconnect charges set forth in this Agreement shall apply.
5.4.6.5.2 If TWTC chooses to convert DS1 and/or DS3 Dedicated Transport to special access circuits in existence as of the Effective Date of this Agreement, AT&T will include such DS1 and/or DS3 Dedicated Transport within TWTC’s total special access circuits, and apply any discounts to which TWTC is entitled from the transition period of 3/11/2006 to the conversion date. Conversions will be subject to the switch-as-is charge set forth in Exhibit A to this Attachment 2.
5.4.6.5.3 AT&T shall not impose disconnect or nonrecurring installation charges when transitioning the Subsequent Embedded Base of DS1 and DS3 Dedicated Transport in existence as of the Effective Date of this Agreement.
5.4.6.6 If TWTC fails to submit the LSR(s) or spreadsheet(s) for all of its Subsequent Embedded Base by one hundred eighty (180) days after the date of AT&T’s CNL identifying the Subsequent Wire Center List, AT&T will identify TWTC’s remaining Subsequent Embedded Base, if any, and will transition such circuits to the equivalent tariffed AT&T service(s), or in the case of Georgia, to the equivalent 271 service(s) set forth in Exhibit 1. In the states of Florida, Kentucky, Mississippi and South Carolina, those circuits identified and transitioned by AT&T shall be subject to the applicable disconnect charges as set forth in this Agreement and the full nonrecurring charges for installation of the equivalent tariffed AT&T service as set forth in AT&T’s tariffs. In the states of Alabama, Georgia, North Carolina and Tennessee, those circuits identified and transitioned by AT&T shall be subject to the applicable switch-as-is rates set forth in Exhibit A of Attachment
Incorporation of Administrative Code Provisions by Reference The provisions of Chapters 12B and 12C of the San Francisco Administrative Code are incorporated in this Section by reference and made a part of this Agreement as though fully set forth herein. Contractor shall comply fully with and be bound by all of the provisions that apply to this Agreement under such Chapters, including but not limited to the remedies provided in such Chapters. Without limiting the foregoing, Contractor understands that pursuant to §§12B.2(h) and 12C.3(g) of the San Francisco Administrative Code, a penalty of $50 for each person for each calendar day during which such person was discriminated against in violation of the provisions of this Agreement may be assessed against Contractor and/or deducted from any payments due Contractor.
Contract Provisions for Orders Utilizing Federal Funds Pursuant to Appendix II to 2 Code of Federal Regulations (CFR) Part 200, Contract Provisions for Non-Federal Entity Contracts Under Federal Awards, Orders funded with federal funds may have additional contractual requirements or certifications that must be satisfied at the time the Order is placed or upon delivery. These federal requirements may be proposed by Participating Entities in Participating Addenda and Purchasing Entities for incorporation in Orders placed under this Master Agreement.
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.
Special Provisions for Affected Systems For the re-payment of amounts advanced to Affected System Operator for System Upgrade Facilities or System Deliverability Upgrades, the Developer and Affected System Operator shall enter into an agreement that provides for such re-payment, but only if responsibility for the cost of such System Upgrade Facilities or System Deliverability Upgrades is not to be allocated in accordance with Attachment S to the ISO OATT. The agreement shall specify the terms governing payments to be made by the Developer to the Affected System Operator as well as the re-payment by the Affected System Operator.
Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:
a. for adaptive learning or customized student learning purposes;
b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product;
c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or
