WECC-0075Mod to Purpose Statement

INT-019-WECC-CRT-1

W. Shannon Black

Manager, Business Practices and Standards Processes

December 9, 2010

Welcome!

Defining the Basics Who’s on the Team Getting Around the Web Email Communications Connect Pro Team Obligations Development Principles Meeting Structure The Process

Team

● Team Chair Pam Hunt

● Vice Chair To Be Determined

● Secretary To Be Determined

● Team Members Refer to Agenda

Getting Around

● Request● http://www.wecc.biz/Standards/Development/Lists/Request%20Form/DispForm.a

spx?ID=75&Source=/Standards/Development

● Team Site: http://www.wecc.biz/Standards/Development/WECC-0075/default.aspx

Calendar Load to your Outlook Minutes and their location

Documents Surveys

● Can use the WECC-0075 DT exploder Email exploders

Connect Pro

● Unless otherwise noticed all meetings will be held via Connect Pro

● Check the header of the Team Site

● URL

● Call-in Number

● Passcode

● Load the software Click the URL Follow the instructions Allow the software to load when asked

Team Obligations

● The Team serves the WECC Your focus is on the interconnection

Avoid “personal” positions Avoid “company” positions

● The Team serves a reliability function

● To be a “Team” requires participation Stay active and informed Bring your expertise and creative ideas Do your homework “before” the meeting

Read minutes and other documents “before” the meeting

Development Principles

● All meetings of the DT shall be open to the public and broad participation is encouraged.

● All participants eligible to vote at a WECC Standing Committee retain full opportunity and representation to vote on the final document when presented at the Standing Committee.

● Nothing in these Development Principles shall infringe on an individual’s rights to appeal a Standing Committee vote regarding the resultant document.

● All DT members are encouraged to always be present; proxy voting by a DT member is not allowed.

● The Process does not require a quorum to be present before a DT vote is taken.

● The Process does not require notice that a DT vote will be taken.

● The Process does not require notice that a DT subset group will meet.

Development Principles

● It takes only a simple majority to carry a vote on any DT issue.

● DT voting may take place face-to-face, electronically, in real-time or within a scheduled window.

● Voting on which position to adopt on a drafting issue is reserved for the DT members.

● Voting on inclusion or exclusion of specific language in the document under development is reserved for the DT members.

● Voting on minutes and related business motions is reserved for the DT members.

● Straw Polls are of excellent advisory value but the DT is not obligated to abide by a straw poll.

Notice / Conducting Meetings

● Notice Full Team meetings require 30-day notice; Sub teams don’t Put future meeting dates in each set of minutes Posted on Team Site in the Calendar Post the most current version of the document

● Be prepared for meetings Read the minutes and do your homework

● Roberts Rules of Order (Abridged) Debate

May be limited by the chair Chair may rule you “Out of order”

Process and Related Documents

● Process for Developing and Approving WECC Standards http://www.wecc.biz/Standards/Development/

Documents/Standards_Development_Process_Approved.pdf Developing a new Regional Criterion

● The WECC Bylaws http://www.wecc.biz/library/WECC

%20Documents/Business%20and%20Governance%20Documents/WECC%20Bylaws%202009.pdf

Process Sequence

● Determine “Do we move on or not?”

● 45 day Posting Answer “each” of the Comments

● 30 day Posting Answer “each” of the Comments

● Must repost if there is a “substantive” change Substantive = “Surprise”

● Repeat until done

● Vote to forward to Standing Committee

● 30 day notice to SC

● Vote

Questions?