20150818AVU to Staff 90 Attachment B.pdf

Project Initiation Charter
Planning Phase Approval
Template Version #: 6 Avista Confidential Page 1 of 3

x This template is to be used to approve all Standard and Complex projects. It is typically filled out and submitted by the
Program Manager or Team Lead.
x Please read all blue help text & follow process instructions carefully then delete help text before submitting for approval.
Project Name:
Clarity Project ID: 8 digit number below the Project Name in Clarity
1 Key Roles
Fill in the names for each role below.
x Project Sponsor:
x Steering Committee:
x Other Stakeholders: List people who may be impacted but are not voting members of the steering committee.
x Program Manager:
x Project Manager (if known):
2 Project Profile
This is a section heading only – do not type in this space. Fill in the sections below to create the project profile. This profile refers to
the project as a whole, not just to the “planning” phase.
2.1 Business Need
Add a brief description of the purpose of the project. Include what is being purchased (HW, SW, etc) and whether it is refresh or
expansion. For Expansion work provide sufficient details to understand the current state and the reason expansion is needed.
2.2 Who Benefits?
Add two or three sentences describing how Avista stakeholders and customers benefit from the deliverables of the project.
2.3 High Level Project Deliverables
Project deliverables define the scope of what is to be delivered in the project. This should include requirements that, when
delivered, will result in the business need being met to the satisfaction of the project sponsors and stakeholders.
2.4 What will NOT be delivered?
List functionality that stakeholders might presume to be a deliverable but is not, or related functionality that will be delivered in
a future / separate project
2.5 Where will technology be deployed?
List Avista locations where technology will be deployed
3 Artifacts and Milestones
3.1 Project Artifacts to be delivered
x Project Initiation Charter
x Statement of Scope
x Project Management Plan
x Go-Live approval
x Approval to Close
Staff_PR_090 Attachment B Page 1 of 3
Project Initiation Charter
Planning Phase Approval
Template Version #: 6 Avista Confidential Page 2 of 3

3.2 Milestones
Description Target date for completion/approval
Project Initiation
Scope Approval w/VROMs (Go / No-go decision point)
Work Packages & ITE Design Review
PMP: Approval to Execute
Go-Live Approval (Go / No-go decision point)
Approval to Close
4 Assumptions & Constraints
4.1 Assumptions
External circumstances or events that must occur for the project to be successful
x
x
4.2 Constraints
A restriction that must be balanced with all other constraints to achieve project success: The four primary and universal project
constraints are scope, quality grade, time and resources
x
x
5 Compliance and Controls
Refer to the Business and Computer Control Impact Assessment process. Document any notes for what is known about
Compliance and Controls before the project moves into planning. Compliance and Controls must be addressed in Scoping.
NOTE: For each “yes”, add a bullet point to your “scope” stating that this listed item is a deliverable of the project
6 Planning Cost Estimate
(This planning cost estimate is based on high level scope assumptions)
Description Amount

Staff_PR_090 Attachment B Page 2 of 3
Project Initiation Charter
Planning Phase Approval
Template Version #: 6 Avista Confidential Page 3 of 3

6.1 FERC Allocation of Project Costs
FERC requires the cost of the project to be broken down into fixed asset types for depreciation and asset valuation
purposes. Of the total project cost estimate, break out the costs into the following asset categories**. Note that these
cost breakouts include the amount of effort (equipment, labor, loadings, and professional services) to put the asset into
service.

Installation
(107600)
Removal
(108000)
Accounting Asset Category
Hardware (FERC Account 391) $10,000 $2,000 $0 $12,000
Communications Equipment (FERC Account 397) $0 $0 $0 $0
Software (FERC Account 303) $2,000 $4,000 $0 $6,000
Estimated Total Cost: 12,000 6,000 $0 $18,000

FERC Definitions
1) Hardware examples: personal computers, printers, physical servers, racks, disk
2) Communication Equipment examples: phones, smart phones, radios, fiber optic cable, copper wire
3) Software examples: commercial off the shelf software purchased, virtual servers, operating system, data base
software.
4) “Removal” is labor, professional service and other misc. costs that are associated with the removal of equipment
that is retired.

GUIDE: The difference between Hardware and Communications Equipment is from an accounting perspective. Any
equipment that facilitates the physical communication between two sites is defined as communications equipment. To
clarify, equipment to ‘distribute’ the communications within a site is defined as hardware, not communications
equipment.

**Please consult with your Program Manager if you have any questions distinguishing Hardware from Communications
Equipment in your project.

Installation
(107600)
Removal
(108000)
Accounting Asset Category
Hardware (FERC Account 391) $0 $0 $0 $0
Communications Equipment (FERC Account 397) $0 $0 $0 $0
Software (FERC Account 303) $0 $0 $0 $0
Estimated Total Cost: $0 $0 $0 $0

After drafting this document, it is recommended to have at least one peer review prior to submit for approval via Clarity.
Staff_PR_090 Attachment B Page 3 of 3