Timescale for implementation Clause Samples
The 'Timescale for implementation' clause sets out the specific timeframe within which certain obligations or actions under the contract must be completed. It typically details deadlines for deliverables, milestones, or the overall project completion, and may include provisions for extensions or penalties if deadlines are missed. This clause ensures that all parties are clear on the expected schedule, helping to manage expectations and reduce the risk of disputes over timing.
Timescale for implementation. Core NRAs requested Core TSOs that the wrong reference “to the Agency” (instead of relevant NRAs) as well as the wrong reference to “Article 6 (1 and 2)” in paragraph 1 is corrected. Core TSOs changed the reference accordingly. Core NRAs requested Core TSOs to clarify the timings of the implementation process as it was unclear what exactly is meant with the “entry into force of this methodology”. Core TSOs added an additional milestone to Article 15 under 3(a) clarifying that the implementation of ROSC, IDCC and the CGMES data format is a prerequisite for the BTCC process.
Timescale for implementation. 1. The LFCBOA will enter into force 3 months after its approval by the National Regulatory Authority, ▇▇▇▇ (not earlier than 1 January 2019) in line with SOGL Article 119(2).
Timescale for implementation. The implementation of the methodology for CRIDAs on all the concerned borders (borders within Italy and Greece-Italy border) shall be contingent on the implementation of XBID at least in the Italian bidding zones. For the Greece-Italy bidding zone border, it should explicitly be stated that the CRIDAs could be implemented before the SIDC is extended to this border. Once the details for the implementation of the IDCZCP methodology are known, the CRIDA proposal shall be amended in order to coordinate the two methodologies. Furthermore, elements that cannot be described clearly at the stage of drafting the amended proposal on CRIDA shall be subject to an amendment of the CRIDA proposal at a later stage. Such an amendment shall be initiated by concerned NEMOs and TSOs following Art. 9(13) of CACM Regulation once details on these elements are available. This may for example concern the algorithm used and products offered for the purpose of carrying out the CRIDA, as well as the specific timings and the duration of the auction.
Timescale for implementation. With reference to the France-Italy and Austria-Italy borders, the implementation of the methodology for CRIDAs shall be contingent on the following two milestones: • Implementation of the methodology for intraday cross-zonal capacity pricing pursuant to Article 55(1) of CACM GL; • Implementation of XBID (and thus single intraday coupling) on all bidding zone border within the geographic scope considered for the CRIDAs. The methodology for CRIDA might be implemented at the same point in time as the latest to be implemented milestone listed above. With reference to the Italy-Slovenia border, the implementation of the methodology for CRIDAs shall be contingent only on the implementation of XBID (and thus the single intraday coupling) on the bidding zone. Once the details for the implementation of the IDCZCP methodology are known, the CRIDA proposal shall be amended in order to coordinate the two methodologies. Furthermore, elements that cannot be described clearly at the stage of drafting the amended proposal on CRIDA shall be subject to a binding amendment of the CRIDA proposal at a later stage. Such an amendment shall be initiated by concerned NEMOs and TSOs once details on these elements are available. This may for example concern the algorithm used and products offered for the purpose of carrying out the CRIDA, as well as the specific timings and the duration of the auction.