Project closure. 17.7.1 Save and except as provided in Clause 17.6, the Concessionaire shall not close any part of the Project for undertaking maintenance or repair works not forming part of the Maintenance Program, except with the prior written approval of the Independent Engineer. Such approval shall be sought by the Concessionaire through a written request to be made to the Independent Engineer, and a copy thereof furnished to the Authority, at least 7 (seven) days before the proposed closure and shall be accompanied by particulars thereof. Within 3 (three) days of receiving such request, the Independent Engineer shall grant permission with such modifications as it may deem reasonable and necessary in conformity with the Maintenance Manual and Maintenance Program and a copy of such permission shall be sent to the Authority.
Project closure. All projects will be required to produce a project closure report at the end of the project, which demonstrates that: all activities have been delivered in accordance with the offer letter; all funding has been spent appropriately in line with the projected financial profile for the project; there are no outstanding risks or action that need to be taken to sign the project off (by the account/contract manager); and all relevant outputs and key milestones have been achieved. Following the delivery of the project closure report, all applicants that have received SIF funding will be required to complete a benefits realisation report (within 3 months of completion) to measure the impact of the investment and identify lessons learnt for future projects.
Project closure. 13.2.1 Within one month of the completion of the WISP Build/Access Seeker Build, the Registered Party will provide the Access Provider with the Project Closure Checklist completed in accordance with Appendix H of this Operations Manual. The Project Closure Checklist will include:
Project closure. When all work for a project is believed to be completed, Seller’s Project Manager will submit to the Purchaser’s Contact a project closure form. Purchaser’s Contact will have five (5) business days to review, approve or dispute, in writing, the project closure. If no written notice of dispute or rejection from the Purchaser’s Contact is received by Seller, the implementation shall be deemed accepted and completed in accordance with the Purchaser’s specifications, at which time Purchaser shall be invoiced by Seller in accordance with the terms and conditions set forth in the Sales Agreement. Appendix B Maintenance and Support Services The additional service terms and conditions set forth for certain Maintenance and Support Services (“Support Services”) (i.e. Enterprise Assist, Hardware Maintenance, and Technician on Demand) that are available for purchase by Purchaser from Seller, with specific requirements to be further defined or specified in an individual Order, Service Agreement, or a Sales Agreement, which shall be subject to the Agreement.
Project closure. 17.7.1 The Concessionaire shall not close any part of the Project for undertaking maintenance or repair works except with the prior written approval of the Independent Engineer. Such approval shall be sought by the Concessionaire through a written request to be made at least 7 (seven) days before the proposed closure of the Project and shall be accompanied by particulars thereof. Within 3 (three) days of receiving such request, the Independent Engineer shall grant permission with such modifications as it may deem necessary and a copy of such permission shall be sent to the Authority.
Project closure. The RCA Technical Cooperation Projects implemented under the TC Programme of the Agency are closed by the Agency following the delivery of the planned project inputs. While recognising that project duration shall depend on the nature and scope of the project, and, therefore, that the timelines of the projects should be flexible, there is generally a need for projects to be active for some additional time to facilitate fully achieving the desired outcomes and objectives set out in the project design. In such cases, RCA Projects may be considered to be active for a further two-year period in order that the full impact of the projects can be assessed. The progress of these projects would continue to be monitored during this period, through NPC and LCC reports to the NRM.
Project closure. During this phase the official closure of the Project is performed and finally documented (e. g. end project report including follow-on action recommendations and lessons learned, validation accept, FME approval).
Project closure. Timeline: Submit Project Closure Report within 5 business days of final acceptance of the last deliverable for deliverable No. 7. As the project completes, EY will issue a Project Closure Report that captures critical information that may not be included in previous deliverables. EY will leverage this report as a handoff of knowledge materials, key lessons learned throughout the process, and the finalized RAIC log that has been leveraged throughout the project to capture key decisions and changes. The key components of this report are detailed in the table below: Project Closure Deliverable Description Lessons Learned Project Report This report will not only document key challenges faced throughout the project and the lessons learned from those instances but from the positive lessons learned along the way as well. Project Release Document This document will serve as the official closeout of the project. It will be provided to the Client for signature, inclusive of all accomplishments and updates noted from the duration of the project.
Project closure. Conduct project closure meeting to review project results, and documentation. Out of Scope By definition any item not deemed in scope is considered out of scope, but for clarity the following specific items are not included: Ref Description OS1 Any work outside of normal business hours, Monday to Friday excluding public holidays, is considered out of scope of the project and will be subject to additional fees at two times the standard MSRP consultancy day rate, charged in minimum half day increments. OS2 Consultancy relating to any products not specified in the “In Scope” section of this document Assumptions The project will proceed with the following identified assumptions. Any further assumptions that are identified as the project progresses will be subject to a change control and an impact analysis, which may affect the cost and timescales of the project. Where these changes were not reasonably identifiable by Ivanti then the Customer will bear any costs. Ref Assumptions A1 If onsite engagement, the Consultant will be provided with a desk and chair within an office environment preferably with internet access. A2 If onsite engagement, Customer will provide advance notification of any site-specific requirements such as security clearance, identification and safety training. A3 Customer representatives are available to answer requirements and design questions supply logon credentials, IP addresses, and server names to the Ivanti Certified Consultant as reasonably requested. A4 Customer representatives are available in order that the Ivanti Consultant can transfer knowledge regarding the configuration and usage of the software. Ref Assumptions A5 Network connectivity and all relevant cabling will be in place, so as not to impede the progress of work. A6 The agreed physical and logical infrastructure will be provided and access will be provided to the Ivanti consultant as necessary in order to enable the completion of required tasks A7 Ivanti will supply licenses under a separate commercial agreement outside of the scope of this Statement of Work. Any additional non-Ivanti software license requirements (e.g. Microsoft licenses) will be sourced by Customer. A8 For engagements requiring product installation, the latest release of Ivanti software or the required components will be installed unless otherwise agreed. A9 If onsite engagement, delivery of Services assumes inclusion of travel and expense (T&E) rate in the Purchase Order (PO); if no T&E is included i...
Project closure. 17.7.1 The Concessionaire shall not close any part of the Project for undertaking maintenance or repair works not forming part of the Maintenance Programme, except with the prior written approval of the Independent Expert. Such approval shall be sought by the Concessionaire through a written request to be made to the Independent Expert, and a copy thereof furnished to the Authority, at least 7 (seven) days before the proposed closure and shall be accompanied by particulars thereof. Within 3 (three) days of receiving such request, the Independent Expert shall grant permission with such modifications as it may deem reasonable and necessary and a copy of such permission shall be sent to the Authority. However, it shall be noted that the maximum period for such closure, not forming part of the Maintenance Programme, shall not be more than [7 (seven)] days in a year. For any unforeseen event / major overhaul required due to technical reasons / machinery breakdown., requiring closure of the facility beyond 7 days, Concessionaire shall seek approval of the Authority in writing detailing out the reasons requiring such closure. However, the Concessionaire may seek further extension to the above project closure period from the Authority on grounds of operations, management, unforeseen event and major overhaul beyond the original period approved under this Clause arising out of exceptional or extraordinary circumstances. The Authority shall provide its decision within 7 (seven) days of such request. For avoidance of doubt, the Authority shall respond with 7 (seven) days of receiving a request from the Concessionaire and if the Authority does not respond within the said period, the request of the Concessionaire shall be deemed to be approved.
