P#### Project Name
Connection Plan
[Insert Market Participant Name]
[Insert Project Name]
AESO Project Number: [0000]
Company Name / Name / Date / Signature[Insert Market Participant Name]
[Insert Studies Consultant (if applicable)]
[Insert TFO]
[Insert AESO Project Coordinator]
[Author: Where TFO is also acting as Studies Consultant, indicate each role in brackets after the company name in the Company Name column. i.e. AltaLink, L.P. (Studies Consultant) and AltaLink, L.P.(TFO) respectively]
[Insert Date]
Version: [Insert Version #]
To use the automatic fields select File>Properties and in the Summary tab replace or change the Title, and Subject fields. Next, click the Custom Tab and in the Properties list box select Document Number and change the version/revision number in the Value field. After closing the Properties dialog, automatic fields may be updated throughout the document by selecting Edit>Select All and pressing F9, or click on the field and press F9. This must be done separately for Headers and Footer.
Ensure that under Tools-> Options -> View tab that you click on Formatting Marks Hidden Text.
Default Table of Contents uses 1.0 Heading and Style Heading 2 + Italic
V6 DRAFT2017-11-06 / 2 / Transmission Projects
Public
Connection Plan V#
P#### Project Name
Table of Contents
1. Purpose 2
2. Project Description 3
3. Study Area Description 4
4. Roles and Responsibilities RACI 5
5. Project Considerations 9
6. Project Risks 10
7. Project Milestones 12
1. Purpose
The Connection Plan is a high-level document, similar to a Project Charter, which provides a quick overview of the Project identified in Section 2 (the “Project”). This includes a description of the Project and study area, definition of roles and responsibilities up to and including filing of the Needs Identification Document, Project considerations, general Project risks and high-level Project milestones and dates. The Connection Plan will be drafted by the Integrated Project Manager. The Connection Plan is a static document that summarizes the Project at a high level at the onset. Once executed by all parties, the Connection Plan must not be modified. Any changes to the Project that occur subsequent to execution of the Connection Plan will be tracked through change management procedures.
[No changes should be made to this section. All notes and italicized fonts provided throughout this template in [square brackets] must be removed from all drafts of this document. This document should not include discussion of the proposed alternatives for the Project as these will be identified in the Connection Study Scope. The Integrated Project Manager should draft as much of the Connection Plan as possible in advance of the External Kick-off meeting. The intent of the External Kick-off meeting is to complete the Connection Plan and obtain sign-off if possible. Once the Connection Plan is executed modifications must not be made throughout the life of the Project.]
2. Project Description
[This section should be completed by the Integrated Project Manager. The description must align with the Project Information provided in the System Access Service Request and the Project Description in the Connection Study Scope and include a brief description of the Project, requested in-service date, Market Participant name, AESO Project name and physical land location where the Project will be located. If further information is required the Integrated Project Manager can contact the AESO and the Project Coordinator for support.]
3. Study Area Description
[This section should be completed by the AESO Project Studies Engineer. A brief description of the system in the area the Project is located in and any known system reinforcement dependencies. If possible, a single line diagram should be provided. When the Integrated Project Manager initiates drafting of the Connection Plan, proper communication should occur with the AESO Project Coordinator to ensure Section 3 is completed properly.]
4. Roles and Responsibilities RACI
[This section should be completed by the Integrated Project Manager with input from AESO Project Coordinator, Market Participant, Studies Consultant and TFO. The RACI provided below represents the most common arrangement (shown in italicized text). Remove italics for final draft once roles and responsibilities have been agreed upon.]
Please note this table is not to be changed or edited during Connection Plan review.
The RACI chart below outlines the roles and responsibilities established for the Project up to and including filing of the Needs Identification Document.
Deliverable / AESO / [Insert Name of Studies Consultant] / [Insert Market Participant Name] / [Insert TFO] / [Integrated PM*]Kick-off Meeting / C / C / C / C / A,R
Connection Plan / R / C / A,R / R / R
Connection Study Scope / A, R / R / R / R / R
Connection Studies / C / R / A, R / C / R
Connection Proposal / R / R / A, R / C / R
Construction Contribution Decision / A,R / N/A / I / I / I
Stage 3/4 Security / C / N/A / A,R / R / I
Functional Specification and Directions / A,R / C / C / C / C
Participant Involvement Program (PIP) / R / N/A / I / A,R / I
Proposal to Provide Services (PPS) / R / N/A / I / A,R / I
Need Identification Document / A,R / I / I / C / I
Facility Application / C / N/A / I / A,R / I
PDUP – Stage 1 and 2 / R / R / A,R / C / R
PDUP – Stage 3 and 5 / R / R / R / A,R / R
*Integrated PM: TFO, Market Participant or Consultant. The AESO retains the right to be the integrated PM as required.
RACI – Responsible, Accountable, Consulted, Informed
Responsible = “the doer”. Those who do work to achieve the task. There can be multiple resources responsible. The act of approving a deliverable can be categorized under the responsible party.
Accountable = “the buck stops here”. The resource ultimately answerable for the correct and thorough completion of the task (also approver). There can only be one “A” specified for each task.
Consulted = “in the loop”. Those whose opinions are sought. Those who have special knowledge or expertise needed to make decisions or solve problem. Two-way communication.
Informed = “in the picture”. Those who are kept up-to-date on progress and decisions (once made). May be impacted by decision but are not active in final decision. One-way communication.
[Keep the following paragraphs (a-d) when the Market Participant/Consultant completes the Connection Studies and Connection Proposal]
Where the Engineering Study Report and the Facility Design Report (collectively the "Reports") are prepared by the Market Participant or Studies Consultant as outlined in the RACI:
(a) Base Cases must be received from the AESO and converted into study cases as outlined in the Connection Study Scope;
(b) both Reports must be authenticated (signed, stamped and dated) by a professional engineer registered in the Province of Alberta;
(c) both Reports must be submitted to the AESO for acceptance. Upon review, the AESO may:
(i) accept one or both of the Reports;
(ii) require revisions to one or both of the Reports; or
(iii) reject one or both of the Reports;
(d) following acceptance of the Reports, the AESO will require any revisions of information contained in these reports to be captured in the Connection Engineering Study Report for AUC Application Stage 3 and/or in the Functional Specification as it is developed.
The table below defines the contacts for each entity with respect to the Project. The identified Project representative for each organization should be included in all communications with respect to the Project unless otherwise indicated.
Project Manager/ Coordinator
Project Studies Engineer
Stakeholder Consultation
1 TFO column refers to specific TFO activities excluding those activities they may perform in the role of Studies Consultant which are to be captured in the Studies Consultant column.
5. Project Considerations
[This section should be completed by the Integrated Project Manager with input from AESO Project Coordinator, Market Participant, Studies Consultant, and TFO The intent of this section is to document any early known Project considerations regarding Project assumptions, key objectives or delivery approach that have been agreed upon by the Project team.]
Project considerations outlined in this section include early known considerations regarding Project assumptions, key objectives or delivery approach as agreed upon by the Project team. Considerations have been divided into 2 areas: Filing Strategy and Other Considerations, if applicable.
5.1 Filing Strategy
Filing Considerations / Executor5.2 Other Considerations
[If applicable, document any other Project considerations regarding Project assumptions, key objectives or delivery approach not related to regulatory applications or stakeholder consultation noted above.]
6. Project Risks
[This section should be completed by the Integrated Project Manager with input from AESO Project Coordinator, Market Participant, Studies Consultant, and TFO. The intent of this section is to identify any known risks to the delivery of the Project that have been agreed upon by the Project team, including study risks or risks against some of the Project considerations noted in Section 5. For example, list any known interdependencies on system work or if there is a requirement for winter construction.. Please note that as the Project progresses the risks identified in this document must be managed by the Integrated Project Manager and tracked through change management procedures.]
Project risks identified in this section include any known risks to the delivery of the Project as agreed upon by the Project team, including study risks or risks against some of the Project Considerations noted in Section 5. The Project risks identified will likely have some impact on the cost, schedule, or scope for the Project should they occur therefore they are being identified for consideration. For identified risks it is necessary to also document the potential mitigation strategy that is being proposed. As the Project progresses the risks identified in this section will be managed by the AESO Project Coordinator and tracked through change management procedures.
PROJECT RISKS /Identified Risk / Identified By1 / Mitigation Strategy / Assigned To1 /
Project Schedule & Scope
Project Resourcing
Operational
Project Complexity
Regulatory
Stakeholder Relations
Market and/or Vendors
Indicate entity rather than individual responsible (i.e. AESO, Market Participant, Integrated Project Manager, Studies Consultant or TFO)
7. Project Milestones
[This section should be completed by the Integrated Project Manager with input from the AESO Project Coordinator, Market Participant, Studies Consultant and TFO. The Integrated Project Manager must first undertake the scheduling exercise by filling in the milestone dates in the table below. The milestones in the template must be provided as a minimum, additional milestones may be added depending on the complexity of the Project. The Integrated Project Manager should consult with their AESO Project Coordinator before making any changes/additions to the template. As the Project progresses, updates to the Project schedule will be maintained by the Integrated Project Manager outside of this document and tracked through change management procedures.]
The Project milestones outlined in this section provide a high-level summary for the Project schedule and establish a base line schedule for the Project. As the Project progresses, updates to the Project schedule will be maintained separately by the Integrated Project Manager, communicated to the Project team and managed through change management procedures.
Milestone / Owner / Target DateFinalize Connection Plan
Finalize Connection Study Scope
Connection Proposal Submission
Connection Proposal Approval
Stage 3/4 Security
Directions & Functional Specification to TFO
Finalize NID Study Scope*
NID Study Results Submission*
Service Proposal Submission
PIP Report Submission
NID Filed
Facility Application Filed
AUC Approvals
In-Service Date
*Line item can be deleted if the NID studies are completed by the AESO.
V6 FINAL2018-01-03 / 7 / Transmission Projects
Public