Operational Flow Sample Clauses

Operational Flow. Getnet and/or its subsidiaries shall communicate to Santander Brasil, with minimum notice to be agreed between the Parties, any and all demand for Funding and shall send Santander Brasil the necessary information for it to assess the conditions for Funding (“Potential Santander Credit Operation Notice”). 6.2.1. Potential Santander Credit Operation Notice shall be accompanied by all the information and documents necessary for Santander Brasil to carry out the relevant analyses, as agreed between the Parties. 6.2.2. Santander Brasil may request additional information from Getnet and/or its subsidiaries, as the case may be, that is necessary to analyze the potential granting of Funding, according to the policies of Santander Brasil. 6.2.3. Once the necessary information has been received, Santander Brasil, within a period to be agreed between the Parties, shall inform Getnet and/or its subsidiaries of the possibility of granting Funding and the applicable conditions, including the applicable interest rate, total actual cost, deadline for the availability of resources and the need for any guarantees. If Getnet and/or its subsidiaries are in accordance with the conditions presented, the instrument necessary to formalize the granting of Funding shall be executed. 6.2.4. If there is no expression of interest by Santander Brasil or if Getnet and/or its subsidiaries are not in accordance with the conditions presented, Getnet and/or its subsidiaries shall be free to seek funding from other sources in the financial and capital markets.
AutoNDA by SimpleDocs
Operational Flow. The City currently sends bills to customers on a monthly basis broken down in cycles billed in three weeks once a week for three weeks throughout the month, ranging from 10,000 to 15,000 weekly. Final bill statements are also processed with each billing cycle, these are smaller runs containing less than 500 bills each. Delinquent notices will also be sent out monthly on non-bill stock and range in quantity. Significant volumes of notices are anticipated due to the financial impact associated with the COVID-19 pandemic.
Operational Flow. The City of Bend currently sends public notice and land use decision notices to customers on an as-needed basis throughout the year, ranging from 350 to 1,400 monthly and averaging 10,000 annually. An affidavit or other certification that individual notices were sent will be required for each of these notices, per Oregon Revised Statutes and Bend Development Code 4.
Operational Flow 

Related to Operational Flow

  • Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.

  • Operational Control Directing the operation of the Transmission Facilities Under ISO Operational Control to maintain these facilities in a reliable state, as defined by the Reliability Rules. The ISO shall approve operational decisions concerning these facilities, made by each Transmission Owner before the Transmission Owner implements those decisions. In accordance with ISO Procedures, the ISO shall direct each Transmission Owner to take certain actions to restore the system to the Normal State. Operational Control includes security monitoring, adjustment of generation and transmission resources, coordination and approval of changes in transmission status for maintenance, determination of changes in transmission status for reliability, coordination with other Control Areas, voltage reductions and Load Shedding, except that each Transmission Owner continues to physically operate and maintain its facilities.

  • Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.

  • Operational Support 2.1 Party A agrees, according to the operational needs of Party B, to act as the guarantor of Party B in the contracts, agreements, or transactions entered into between Party B and third parties, in order to fully guarantee the performance by Party B of such contracts, agreements, and transactions. 2.2 Party A agrees, according to the operational needs Party B, to recommend directors and senior management to Party B and Party B agrees to appoint such personnel recommended by Party A to be its directors and senior management. The relevant personnel recommended by Party A pursuant to this Article shall meet the qualification requirements for directors and senior management under applicable laws. 2.3 To ensure the performance of this Agreement, Party A agrees to provide to Party B cooperative policy advice and guidance, which is consistent with the daily operation and financial management and the employment policy of Party B.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Project Implementation The Borrower shall:

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Co-operation Each Party acknowledges that this ESA must be approved by the Department and agree that they shall use Commercially Reasonable efforts to cooperate in seeking to secure such approval.

  • 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.

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