Project-Level Account Sample Clauses

Project-Level Account. The Borrower shall, and shall cause the Property Manager to (a) deposit all Rents from the Projects, and all amounts received by the Borrower or the Property Manager constituting Rent or other revenue or sums of any kind from the Projects, into the applicable Project-Level Account for such Project in accordance with the Project-Level Account Security Agreement and (b) upon an Event of Default, and upon written request of the Administrative Agent, deliver irrevocable written instructions to all tenants under Leases to deliver all Rents payable thereunder directly to the applicable Project-Level Account for such Project. The Borrower shall not maintain any checking, money market or other deposit accounts for the deposit and holding of any revenues or sums derived from the ownership or operation of the Projects other than the Project-Level Account (except for such replacement or additional deposit accounts in which the Administrative Agent shall have been granted, pursuant to a written instrument in form and substance satisfactory to the Administrative Agent, a first priority security interest on the terms provided herein, in which case the “Project-Level Account” referred to herein shall include such replacement or additional account), other than (i) accounts into which funds initially deposited in a Project-Level Account have been, or may be, transferred in compliance with the Project-Level Account Security Agreement and (ii) any Cash Trap Account or Controlled Account required hereunder.
AutoNDA by SimpleDocs

Related to Project-Level Account

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Registry-­‐Level Fees (a) Registry Operator shall pay ICANN a registry-­‐level fee equal to (i) the registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-­‐level transaction fee (collectively, the “Registry-­‐Level Fees”). The registry-­‐level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-­‐accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-­‐level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met. Registry Operator’s obligation to pay the quarterly registry-­‐level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-­‐level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls. (b) Subject to Section 6.1(a), Registry Operator shall pay the Registry-­‐Level Fees on a quarterly basis to an account designated by ICANN within thirty (30) calendar days following the date of the invoice provided by ICANN.

  • Staffing Levels To the extent legislative appropriations and PIN authorizations allow, safe staffing levels will be maintained in all institutions where employees have patient, client, inmate or student care responsibilities. In July of each year, the Secretary or Deputy Secretary of each agency will, upon request, meet with the Union, to hear the employees’ views regarding staffing levels. In August of each year, the Secretary or Deputy Secretary of Budget and Management will, upon request, meet with the Union to hear the employees’ views regarding the Governor’s budget request.

  • Performance Levels (a) The Performance Levels which apply to the performance by the respective Parties of their obligations under this Agreement are set out in Part 1 of Schedule 5. A failure by either Party to achieve the relevant Performance Level will not constitute a breach of this Agreement and the only consequences of such failure as between the Parties shall be the consequences set out in this Clause 5.6. (b) If the Operator does not comply with the Operator Performance Level then the Access Holder must pay to QR Network the amount determined in accordance with Schedule 5 as part of the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following QR Network becoming entitled to that amount. Where there is no next Billing Period, the Operator must pay such amount to QR Network within fourteen (14) days after receipt of a Tax Invoice from QR Network. (c) If QR Network does not comply with the QR Network Performance Level then QR Network will credit to the Access Holder the amount determined in accordance with Schedule 5 by way of a deduction from the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following the Access Holder becoming entitled to that amount. Where there is no next Billing Period, QR Network must pay such amount to the Access Holder within fourteen (14) days after receipt of a Tax Invoice from the Access Holder. (d) The Parties must, if requested by either Party, meet to review the Performance Levels subject to such review not occurring within six (6) Months after the Commitment Date or any previous review of the Performance Levels. If either Party notifies the other that it considers that the Performance Levels are no longer appropriate, the Parties may agree on varied Performance Levels and any associated variations to the Agreement including the Base Access Charges and the Train Service Description. If the Parties are unable to agree to such variations, then the existing Performance Levels shall continue to apply unless varied by QR Network in accordance with the provisions of Clause 5.6(e). (e) In the event that the Access Holder and/or the Operator (i) does not comply in any material respect with the Train Service Description; and (ii) the Access Holder fails to demonstrate to the reasonable satisfaction of QR Network when requested to do so, that the Access Holder will consistently comply with the Train Service Description for the remainder of the Term then, following consultation with the Access Holder, QR Network will be entitled to: (iii) vary the Train Service Description to a level it reasonably expects to be achievable by the Access Holder for the remainder of the Term having regard to the extent of previous compliance with the Train Service Description (ignoring, for the purpose of assessing previous compliance, any non-compliance to the extent that the non-compliance was attributable to a Railway Operator (other than the Access Holder) or to QR Network); and (iv) vary the Agreement (including, without limitation, the Operator Performance Level and the Base Access Charges) to reflect the impact of the change in the Train Service Description. (f) The Access Holder shall be entitled to dispute any variation proposed by QR Network pursuant to Clause 5.6(e) and such dispute will be referred to an expert for resolution in accordance with Clause 17.3.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Service Level Credits If Verint does not meet the Uptime Percentage levels specified below, Customer will be entitled, upon written request, to a service level credit (“Service Level Credit”) to be calculated, with respect to the applicable Hosted Environment, as follows: • If Uptime Percentage is at least 99.95% of the month’s minutes, no Service Level Credits are provided; or • If Uptime Percentage is 99.75% to 99.94% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint; or • If Uptime Percentage is 99.50% to 99.74% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 7.5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint; or • If Uptime Percentage is less than 99.50% of the month’s minutes, Customer will be eligible for a credit of 10.0% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint. Customer shall only be eligible to request Service Level Credits if Customer notifies Verint in writing within thirty (30) days from the end of the month for which Service Level Credits are due. All claims will be verified against Verint’s system records. In the event after such notification Verint determines that Service Level Credits are not due, or that different Service Level Credits are due, Verint shall notify Customer in writing on that finding. With respect to any Services Level credits due under Orders placed directly by Customer on Verint, Service Level Credits will be applied to the next invoice following Customer’s request and Verint’s confirmation of available credits; with respect to any Service Level Credits due for SaaS Services under Orders placed on Verint by a Verint authorized reseller on Customer’s behalf, Service Level Credits will be issued by such reseller following Customer’s request and Verint’s confirmation of available credits and such Services Level Credits may only be used by Customer with respect to subsequent purchases of Verint offerings through that reseller. Service Level Credits shall be Customer’s sole and exclusive remedy in the event of any failure to meet the Service Levels. Verint will only provide records of system availability in response to Customer’s good faith claims.

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

  • Long Term Cost Evaluation Criterion # 4 READ CAREFULLY and see in the RFP document under "Proposal Scoring and Evaluation". Points will be assigned to this criterion based on your answer to this Attribute. Points are awarded if you agree not i ncrease your catalog prices (as defined herein) more than X% annually over the previous year for years two and thr ee and potentially year four, unless an exigent circumstance exists in the marketplace and the excess price increase which exceeds X% annually is supported by documentation provided by you and your suppliers and shared with TIP S, if requested. If you agree NOT to increase prices more than 5%, except when justified by supporting documentati on, you are awarded 10 points; if 6% to 14%, except when justified by supporting documentation, you receive 1 to 9 points incrementally. Price increases 14% or greater, except when justified by supporting documentation, receive 0 points. increases will be 5% or less annually per question Required Confidentiality Claim Form This completed form is required by TIPS. By submitting a response to this solicitation you agree to download from th e “Attachments” section, complete according to the instructions on the form, then uploading the completed form, wit h any confidential attachments, if applicable, to the “Response Attachments” section titled “Confidentiality Form” in order to provide to TIPS the completed form titled, “CONFIDENTIALITY CLAIM FORM”. By completing this process, you provide us with the information we require to comply with the open record laws of the State of Texas as they ma y apply to your proposal submission. If you do not provide the form with your proposal, an award will not be made if your proposal is qualified for an award, until TIPS has an accurate, completed form from you. Read the form carefully before completing and if you have any questions, email Xxxx Xxxxxx at TIPS at xxxx.xxxxxx@t xxx-xxx.xxx

  • DIRECT PERSONNEL EXPENSE 4.1. Direct Personnel Expense of employees engaged on the Project by the ARCHITECT/ENGINEER includes ARCHITECT/ENGINEERS, other engineers, designers, job captains, draftsmen, specification writers and typists, in consultation, research and design in producing Drawings, Specifications and other documents pertaining to the Project, and in services during construction at the site. 4.2. Direct Personnel Expense includes actual cost and of mandatory and customary financial benefits paid.

  • Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.

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