Conceptual Financing Strategy Sample Clauses

Conceptual Financing Strategy. Proposers shall provide a discussion of their proposed financing strategy and indicate the types of financing (including equity) that will be used over the entire term of the concession. For each type of financing, the Proposer shall include the following information: • Anticipated proceeds • Term including details of grace periods, repayment or redemption schedules • Fees, Interest rate, and margins • Repayment terms • Significant financial covenantsDescription of anticipated security, bonding, insurance or guarantee requirementsOther requirements or conditions that materially impact the Proposer’s ability to raise financing or draw down on committed financing after financial close Proposers are encouraged to identify potential financing approaches that they have considered, the advantages of the approach they have selected and include a justification as to why the proposed financing strategy presents the most efficient and effective way to finance the transaction.
AutoNDA by SimpleDocs

Related to Conceptual Financing Strategy

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

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

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement. a. Develop a Work Breakdown Structure (WBS) for each project. b. Evaluate Scope Statement to develop a preliminary cost estimate and determinate whether project be vendor bid or be executed under a Job Order Contract (JOC).

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Staff Development ‌ The County and the Association agree that the County retains full authority to determine training needs, resources that can be made available, and the method of payment for training authorized by the County. Nothing in this subsection shall preclude the right of an employee to request specific training.

  • Staff Development Leave (a) An employee will be granted leave without loss of pay, at their basic rate of pay, to take courses (including related examinations) or attend conferences, conventions, seminars, workshops, symposiums or similar out-of-service programs, at the request of the Employer. The amount of pay received by an employee will not exceed the full-time daily hours of work as outlined in Clause 14.2 (Hours of Work). When such leave is granted, the Employer will bear the full cost, including tuition fees, entrance or registration fees, laboratory fees, and course-related books. The Employer will also reimburse the employee for approved travelling, subsistence, and other legitimate, applicable expenses. (b) An employee may be granted leave without pay, with pay, or leave with partial pay, to take work related courses in which the employee wishes to enrol to acquire the skills necessary to enhance opportunities. (c) Approval of requests will be given reasonable consideration and leaves pursuant to this article will be administered in a reasonable manner. (d) Should the employee noted above terminate their employment for any reason during the six month period following completion of the above-noted leave, the employee will reimburse the Employer for all expenses incurred by the Employer (i.e. tuition fees, entrance or registration fees, laboratory fees, and course-required books) on a proportionate basis.

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

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

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation 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 Generator Deactivation 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 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 Generator Deactivation 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.

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

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