Scoping Meeting. 4.2.1 A scoping meeting will be held within ten (10) Business Days after the Interconnection Request is deemed complete, or as otherwise mutually agreed to by the Parties. The Utility and the Interconnection Customer will bring to the meeting personnel, including system engineers and other resources as may be reasonably required to accomplish the purpose of the meeting. The scoping meeting may be omitted by mutual agreement in writing.
Scoping Meeting. Within ten (10) Business Days after receipt of a valid Interconnection Request, Transmission Provider shall establish a date agreeable to Interconnection Customer for the Scoping Meeting, and such date shall be no later than thirty (30) Calendar Days from receipt of the valid Interconnection Request, unless otherwise mutually agreed upon by the Parties. The purpose of the Scoping Meeting shall be to discuss alternative interconnection options, to exchange information including any transmission data that would reasonably be expected to impact such interconnection options, to analyze such information and to determine the potential feasible Points of Interconnection. Transmission Provider and Interconnection Customer will bring to the meeting such technical data, including, but not limited to: (i) general facility loadings, (ii) general instability issues, (iii) general short circuit issues, (iv) general voltage issues, and (v) general reliability issues as may be reasonably required to accomplish the purpose of the meeting. Transmission Provider and Interconnection Customer will also bring to the meeting personnel and other resources as may be reasonably required to accomplish the purpose of the meeting in the time allocated for the meeting. On the basis of the meeting, Interconnection Customer shall designate its Point of Interconnection, pursuant to Section 6.1, and one or more available alternative Point(s) of Interconnection. The duration of the meeting shall be sufficient to accomplish its purpose.
Scoping Meeting. Within ten (10) Business Days after receipt of a valid Transmission Interconnection Application, the ISO shall establish a date agreeable to the Transmission Developer and the Connecting Transmission Owner(s) for the Scoping Meeting. The date shall be no later than thirty (30) Calendar Days from receipt of the valid Transmission Interconnection Application, unless otherwise mutually agreed upon by the Parties. The purposes of the Scoping Meeting shall be to discuss whether the Transmission Developer elects to pursue an Optional Feasibility Study or proceed to a System Impact Study for its Transmission Project, to discuss alternative interconnection options, to exchange information including any transmission data that would reasonably be expected to impact such interconnection options, to analyze such information and to determine the potential feasible Points of Interconnection. The ISO, Connecting Transmission Owner(s), and the Transmission Developer will bring to the meeting such technical data, including, but not limited to: (i) general facility loadings, (ii) general stability issues, (iii) general short circuit issues, (iv) general voltage issues, (v) general reliability issues, and (vi) general system protection issues, as may be reasonably required to accomplish the purpose of the meeting. The ISO, Connecting Transmission Owner(s) and the Transmission Developer will also bring to the meeting personnel and other resources as may be reasonably required to accomplish the purpose of the meeting in the time allocated for the meeting. The Transmission Developer shall in writing within five (5) Business Days of this meeting: (i) make its election as to whether it will pursue an Optional Feasibility Study or proceed to a System Impact Study for its Transmission Project, and (ii) designate the Point(s) of Interconnection for the Transmission Project. The duration of the meeting shall be sufficient to accomplish its purpose.
Scoping Meeting. Transmission Provider shall use Reasonable Efforts to establish within ten (10) Business Days after receipt of a valid Interconnection Request a date agreeable to Interconnection Customer for the Scoping Meeting. The purpose of the Scoping Meeting shall be to discuss alternative interconnection options, to exchange information including any transmission data that would reasonably be expected to impact such interconnection options, to analyze such information and to determine the potential feasible Points of Interconnection. Transmission Provider and Interconnection Customer will bring to the meeting such technical data, including, but not limited to: (i) general facility loadings, (ii) general instability issues, (iii) general short circuit issues, (iv) general voltage issues, and (v) general reliability issues as may be reasonably required to accomplish the purpose of the meeting. Transmission Provider and Interconnection Customer will also bring to the meeting personnel and other resources as may be reasonably required to accomplish the purpose of the meeting in the time allocated for the meeting. On the basis of the meeting, Interconnection Customer shall designate its Point of Interconnection, pursuant to Section 6.1, and one or more available alternative Point(s) of Interconnection. The duration of the meeting shall be sufficient to accomplish its purpose.
Scoping Meeting. 32.3.2.1 A scoping meeting will be held within ten Business Days after the Interconnection Request is deemed complete, or as otherwise mutually agreed to by the Parties. The ISO, the Connecting Transmission Owner, and the Interconnection Customer will bring to the meeting personnel, including system engineers and other resources as may be reasonably required to accomplish the purpose of the meeting. Before a Connecting Transmission Owner participates in a scoping meeting with its Affiliates, the ISO shall post on its OASIS an advance notice of the Connecting Transmission Owner’s intent to do so.
Scoping Meeting. At the beginning of each Project, Consultant shall be required to meet with the Contract Administrator and identify the scope of the job and deliverables. Consultant shall provide the City with a cost proposal and schedule for work after the scope meeting unless otherwise agreed upon by the City. Said cost proposal shall set a not to exceed price and break down hours per task and person doing the work. For projects requiring Land Surveying, City shall decide how the topographic survey and the boundary survey will be obtained. Survey limits shall be proposed by Consultant and approved by the City. All as- built, utility and field research required shall be the responsibility of the Consultant. The Consultant shall identify all other test, permits, reports or other information needed to complete the project in proposed scope. City written approval of scope provided by the Consultant is required prior to the start of work. Environmental permitting shall be done by the City, coordinated by the Consultant and shall be estimated in the schedule. The City reserves the right to request more than one cost proposal per Project and assign work to the consultant with the lowest cost for identified Project. Project begins with the issuance of a Notice to Proceed from the City.
Scoping Meeting. 4.2.1 A scoping meeting will be held after the Interconnection Request is deemed complete as within a timeframe mutually agreed to by the Parties. GUC and the Interconnection Customer will bring to the meeting personnel, including system engineers and other resources as may be reasonably required to accomplish the purpose of the meeting. The scoping meeting may be omitted by mutual agreement.
Scoping Meeting. Within ten (10) Business Days after IPA’s acknowledgement of a valid Interconnection Request pursuant to Section 3.2.3, IPA shall establish a date reasonably agreeable to Interconnection Customer for the Scoping Meeting. Such date shall be no later than thirty (30) calendar days from receipt of the valid Interconnection Request, unless otherwise mutually agreed by the Parties. The purpose of the Scoping Meeting shall be to discuss alternative interconnection options, to exchange information including any transmission data that would reasonably be expected to impact such interconnection options, to analyze such information and to determine the potential feasible Points of Interconnection. IPA and Interconnection Customer will bring to the meeting such technical data, including, but not limited to: (i) general facility loadings, (ii) general instability issues, (iii) general short circuit issues, (iv) general voltage issues, and (v) general reliability issues as may be reasonably required to accomplish the purpose of the meeting. IPA and Interconnection Customer will also bring to the meeting personnel and other resources as may be reasonably required to accomplish the purpose of the meeting in the time allocated for the meeting. At IPA’s sole discretion, a consultant approved by IPA, may be brought to the meeting and will be responsible for conducting the Feasibility Study. On the basis of the meeting, Interconnection Customer shall designate its Point of Interconnection, pursuant to Section 6.2, and one or more available alternative Point(s) of Interconnection.
Scoping Meeting. Transmission Provider will make Reasonable Efforts to conduct Scoping Meetings with each Interconnection Customer that has a valid Interconnection Request within forty-five (45) Calendar Days prior to executing the System Impact Study Agreement. Transmission Provider shall establish a date agreeable to Interconnection Customer for the Scoping Meeting. The purpose of the Scoping Meeting shall be to exchange information including any transmission data that would reasonably be expected to impact such Interconnection Customer’s interconnection options, to analyze such information and to review the requested Point of Interconnection. Interconnection Customer may prepare in advance for the Scoping Meeting by reviewing the Load and Resource Transmission Study and by attending an informational meeting that Transmission Provider may arrange at the beginning of the Request Window. At the Scoping Meeting, Interconnection Customer may identify an alternate, reduced level of generation output to be studied, up to sixty percent (60%) less than that stated in the Interconnection Request. Selection of such an alternative level of output will be at the sole determination of Interconnection Customer. Transmission Provider and Interconnection Customer will bring to the meeting such technical data, including, but not limited to: (i) general facility loadings, (ii) general instability issues, (iii) general short circuit issues, (iv) general voltage issues, and (v) general reliability issues as may be reasonably required to accomplish the purpose of the meeting. Transmission Provider and Interconnection Customer will also bring to the meeting personnel and other resources as may be reasonably required to accomplish the purpose of the meeting in the time allocated for the meeting. On the basis of the meeting, Interconnection Customer shall designate its Point of Interconnection, pursuant to Section 7.1, and one or more alternative Point(s) of Interconnection for purposes of the Interconnection System Impact Study.
Scoping Meeting. Within ten (10) Business Days after receipt of a valid Interconnection Request, the ISO shall establish a date agreeable to Developer and Connecting Transmission Owner for the Scoping Meeting, and such date shall be no later than thirty (30) Calendar Days from receipt of the valid Interconnection Request, unless otherwise mutually agreed upon by the Parties. The purpose of the Scoping Meeting shall be to reinforce the roles and responsibilities of all parties in the interconnection process, discuss alternative interconnection options, to exchange information including any transmission data that would reasonably be expected to impact such interconnection options, to analyze such information and to determine the potential feasible Points of Interconnection, and to determine if Developer wishes to proceed with an Optional Interconnection Feasibility Study. The ISO, Connecting Transmission Owner and Developer will bring to the meeting such technical data, including, but not limited to: (i) general facility loadings, (ii) general stability issues, (iii) general short circuit issues, (iv) general voltage issues,
