Overall Requirements Sample Clauses
Overall Requirements. (a) The City shall not be obligated to provide funds for any Public Improvement except from the proceeds of the PID Bonds or from Assessments pursuant to a Reimbursement Agreement. The City makes no warranty, either express or implied, that the proceeds of the PID Bonds available for the payment or reimbursement of the Public Improvement Project Costs or for the payment of the cost to construct or acquire a Public Improvement by the City will be sufficient for the construction or acquisition of all of the Public Improvements. Any costs of the Public Improvements in excess of the available PID Bond Proceeds or Assessments pursuant to a Reimbursement Agreement, shall not be paid or reimbursed by the City. The Developer acknowledges and agrees that any lack of availability of monies in the Project Funds established under the Indentures to pay the costs of the Public Improvements shall in no way diminish any obligation of the Developer with respect to the construction of or contributions for the Public Improvements required by this Agreement, or any other agreement to which the Developer is a party, or any governmental approval to which the Developer or Property is subject.
(b) Upon written Acceptance of a Public Improvement, the City shall be responsible for all operation and maintenance, subject to any applicable maintenance-bond period, of such Public Improvement, including all costs thereof and relating thereto.
(c) The City’s obligation with respect to the reimbursement or payment of the Public Improvement Project Costs as finally set forth in the Service and Assessment Plan, shall be limited to the lower of actual costs or the available PID Bond Proceeds or Assessment revenues, and shall be payable solely from amounts on deposit in the Project Funds from the sale of the PID Bonds as provided herein and in the Indentures, or Assessments collected for the reimbursement or payment of such costs pursuant to Reimbursement Agreement. The Developer agrees and acknowledges that it is responsible for all costs and all expenses related to the Public Improvements in excess of the available PID Bond Proceeds and that the Developer Cash Contribution must be deposited at the time of the issuance of PID Bonds.
(d) The City shall have no responsibility whatsoever to the Developer with respect to the investment of any funds held in the Project Fund by the Trustee under the provisions of the Indenture, including any loss of all or a portion of the principal invested or an...
Overall Requirements. (a) The City shall not be obligated to provide funds for any Authorized Improvement except from Assessment Revenues or, if PID Bonds are issued, the proceeds of the PID Bonds. The City makes no warranty, either express or implied, that the proceeds of the PID Bonds available for the payment of the Actual Cost of the Authorized Improvements to be constructed for or acquired by the City will be sufficient for the construction or acquisition of all of those particular Authorized Improvements. The Parties anticipate that the Actual Cost to construct the Authorized Improvements may be greater than the proceeds of the PID Bonds available for Authorized Improvements.
(b) Upon written acceptance of an Authorized Improvement, and subject to any applicable maintenance-bond period, the City shall be responsible for all operation and maintenance of such Authorized Improvement, including all costs thereof and relating thereto.
(c) The Parties hereby acknowledge and agree that:
(1) Owner will construct or cause the construction of the applicable Authorized Improvements.
(2) Authorized Improvements are initially intended to be constructed pursuant to one or more Acquisition and Reimbursement Agreements and paid for by the Owner prior to the levy of Special Assessments and the issuance of the PID Bonds intended to fund the Actual Costs of such Authorized Improvements. Such funding of the Authorized Improvements will be governed by the applicable Acquisition and Reimbursement Agreement and Section 4.02 of this Agreement.
(3) Within sixty (60) days of receipt of an Assessment Levy Request, the City will consider the adoption of an Assessment Ordinance that (i) approves a Service and Assessment Plan (or amendment or update thereof) identifying the Special Assessments applicable to the District, (ii) levies said Special Assessments, and (iii) establishes the timeframe for collection of said Special Assessments. The City will levy and collect such Special Assessments in accordance with the approved Service and Assessment Plan, as amended or updated, and the applicable Assessment Ordinance, as further provided in this Agreement.
(4) Upon satisfying the conditions precedent described in Section 5.01 of this Agreement, the City Council intends to consider the issuance of the PID Bonds to refinance any unpaid Reimbursement Obligation Balance under an Acquisition and Reimbursement Agreement and, if applicable, to finance the Actual Costs of any Authorized Improvement not completed ...
Overall Requirements. Preparation: o Agree approach to and parameters of the work with ARO, taking into account stakeholder requirements, DFAT/ARO objectives, AMENCA principles and outcomes, relevant policy, the Palestinian context, which will further inform the scope of the work; o Inform the work through stakeholder consultations, and collaboration with ARO / ANGOs / Consortia / Advisers. • Implementation: o Carry out in a timely manner; raising any unexpected delays with ARO and Cardno; o Work collaboratively and in very close consultation and coordination with the ANGOs, Program Adviser, and other advisers and specialist as relevant, throughout the undertaking of this assignment; o Work with the AMENCA advisers to support ANGOS to put systems in place to ensure consistency in planning and implementation of their own trade facilitation activities. • Monitoring and Evaluation: o Work with the M&E Adviser to ensure the outcomes of this TOR are in line with trade targets and indicators. • Communications: o Report to ARO any ANGO resource constraints or requirements that would impede yourself or ANGOs from carrying out any activities related to Trade Facilitation. Provide ARO with reasonable solutions; o Determine any further capacity building requirements for ANGOs, Consortia and local partners, and provide recommendations to ARO; o Maintain strong communication with the Program Adviser; o Attend meetings with Cardno and the advisory team upon request; o Liaise with the Jordanian Exports Facilitator to the extent necessary and useful; o Meet with ▇▇▇ ▇▇▇▇▇▇▇▇ if and when requested; o Debrief ANGOs and advisers at the end of the duration of the contract, if requested. • Other reasonable and related tasks as determined by Head of Cooperation Ramallah and/or the Cardno Contractor Representative. Note: any travel to Palestinian Territories, if required (and safe/approved), will be located in Ramallah, with some travel in West Bank and Gaza. If travel is required, this will be by written agreement with Cardno and shall include provision or reimbursement of accommodation (if needed), transport and travel.
1. B2B facilitated event
2. Documentation of Point (2) above for each product, in a format agreed by the Program Adviser and of a quality standard approved by Cardno, submitted to the Program Adviser as completed but at least two weeks before the end of the contract. These documents shall also outline any ongoing recommendations for the AMENCA 3 program.
Overall Requirements. The SFMTA seeks to procure a modular charging solution for nine electric buses at the SFMTA’s ▇▇▇▇▇ Division, consisting of nine charging dispensers and nine power converters. This DC charging infrastructure solution will be required to meet all specifications in the following sections.
Overall Requirements. The Contractor shall ensure that the application and installation of major bus subcomponents and systems are compliant with all such subcomponent vendors’ requirements and recommendations. Contractor and Agency shall identify subcomponent vendors that shall submit installation/application approval documents with the completion of a first article bus. Components used in the vehicle shall be of heavy-duty design and proven in transit service. At a minimum, the following systems shall be subject to the provision of supplier review and application approval: Energy Storage System; Axles, suspension, foundation brakes; Fire Suppression; HVAC; The Contractor shall not make any substantive or material changes that would differentiate one bus from another bus, unless at SBCAG’s request. If the Contractor identifies a change during the manufacturing process that would materially improve the design, safety and/or performance of the bus, this change must (1) be discussed with the Agency and (2) be considered as a retrofit (if possible) to any previous buses manufactured or assembled. Any such changes must be approved by the Agency in accordance with the Section “Changes” in this Agreement. In the event of loss of power to the bus shall not cause the driver to lose control of the bus or to lose steering or braking. The bus shall be able to be safely brought to a controlled stop.
Overall Requirements. The scanning radar supplied, installed, commissioned, and given ongoing support under this Schedule are to be installed on or adjacent to live all lane running motorways operated by Customer in accordance with the requirements of this Schedule.
Overall Requirements. The Contractor shall ensure that the application and installation of major sub-components and systems are compliant with all such sub-component vendors’ requirements and
Overall Requirements. Over the course of the development of the Project, Developer shall be required to provide publicly-accessible off-street parking spaces serving new office development at a cumulative ratio between 0.5 and 0.645 spaces for each 1,000 square feet of Floor Area (which shall mean eighty-five percent (85%) of the total gross floor area) of such office buildings (the "Required Parking Ratio"). At the point of full build out of office space within the Downtown West project, the Required Parking Ratio shall be 0.645 spaces, and the project shall provide at least 4,000 publicly-accessible spaces. within 1/3 mile of the south entrance to the Arena (which radius shall be defined to include the entirety of the parking garage proposed to be located on Parcel F, as such Parcel is depicted in the DWDSG).
a. Once 4,000 publicly-accessible parking spaces are operational and in compliance with these terms, the Required Parking Ratio will no longer apply provided that the 4,000 publicly-accessible spaces shall be maintained as described herein.
b. Developer may construct up to 4,800 publicly-accessible parking spaces at its discretion; this parking would be reviewed as part of the Conformance Review process.
Overall Requirements. The following table contains a basic classification of the requirements that will be supported by the SODALES control and management plane. It also contains the basic description of each of the identified requirements. Requirement ID Title Type Priority Description CMP-REQ- 001 Resource abstraction mechanisms and associated data models Functional Essential The network management system must provide internal mechanisms in order to abstract the physical resources and thus enable the uniform management and operation of all the physical resources considered within the SODALES environment. Abstraction is the requirement that will enable the management platform to uniformly handle the different resources (CPE, CO, ARN). In fact, the management platform needs to provide mechanisms to create abstract descriptions of physical resources, by using a set of attributes, characteristics and functionalities while hiding unnecessary characteristics of the resources themselves. These descriptions will be produced according to the data models created within SODALES. They will also be used as the basis for virtual resources deployment. CMP-REQ- 002 On-demand slice-provisioning Functional Essential One of the key objectives of SODALES is to explore and implement virtualization mechanisms to support multi-tenancy for capabilities (Virtualization) service providers, and guarantee isolation between virtualized resources. On-demand slice-provisioning requirement responds to the necessity of the network owner (i.e. infrastructure or network provider) to create isolated slices as a function of the demands of the different service providers, who will be operating them. Thus, this requirement is twofold. On the one hand, the management system must be able to virtualize (partition) each physical resource and create virtual representations of each partition that behave as a physical resource by themselves. Isolation between virtual resources built on top of the same physical resource must be guaranteed. Virtualization of the resources will be realized over the abstracted resources, so all the resources belonging to the same type will have the same abstracted data model. On the other hand, the on-demand slice-provisioning requirement implies that the management system must be capable of creating virtual infrastructures in an on- demand basis to serve the service providers’ requests. These virtual infrastructures are composed of different virtual resources. Thus, the management system ...
Overall Requirements. Supplier’s Problem Management responsibilities include the following;
(i) Employing processes, procedures and tools for tracking, managing and escalating or resolving all Incidents with the objective of integrating and improving the Problem Management processes and procedures.
(ii) Supplier Stores Help Desk will utilize tools that allow the Stores Help Desk the ability to remote access the Covered Location’s systems to remotely resolve issues with or without the Covered Location’s knowledge. * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions.
(iii) Establishing processes to ensure that all logged Incidents are managed to closure or escalated to the team / Third Party Vendor who is accountable for resolution as defined by the Policy and Procedures Manual.
(iv) Co-ordinate processes that are flexible and which facilitate effective co-ordination of Problem Management activities across Gap Inc., the Covered Locations and other Third Party Vendors.
(v) Providing the functionality for quickly referring Incidents to the appropriate Third Party Vendor for resolution.
(vi) Providing the functionality to track information for each Incident submitted to (or originating from) Supplier to include the Ticket logging requirements as defined in Appendix B-5.
(vii) Providing a central and consolidated knowledge database system covering the Covered Locations and used to capture, store and retrieve best practices, methods, processes, troubleshooting and other information and solution used for re-use and sharing by Supplier, Gap, Gap Authorized Users, and Third Party Vendors (the “Knowledge Database”). Gap shall not provide access to the Knowledge Database without prior written consent of Supplier.
(viii) Providing prompt notification to Gap of * that have been raised as Incidents by Covered Locations, * so that they are treated with the * as identified in Appendix B.2.
(ix) If Supplier believes an Incident cannot be resolved:
(A) Communicate the nature of the Incident and efforts employed by Supplier to resolve the Service Center Ticket to the correct resolution group defined in the Knowledge Database;
(B) Escalate unresolved Incidents according to the procedures approved by Gap as described in the Policies and Procedures Manual and the Knowledge Database.; and
(C) Communicating the reason(s) why the Incident cannot be resolved within the Problem Manageme...