2017 CG MOD 33 updates CG Planning Meeting Feb 9, 2017

In This Presentation Review of MOD 33 meeting in Jan 10 Meeting Action Items

Jan 2017 Meeting Review Discussion of the MOD 33 standards and technical issues, prepared to develop a CG process document. Review Existing Process from CAISO Discussion for future training and work group activities

Action Item: Process Document Outline for MOD 33 process document will be sent out at the end of February The final MOD 33 process document around 6/1/2017 Chelan PUD offer to share their MOD 33 process document to members when finalized. Confirm with NERC of using 6/30/2019 as the deadline Power Flow and Dynamic validation evidence. (confirmed)

Action Item: Event Selection CG MOD 33 will focus on major system events and main grid validation. Members can perform their own validation of local events on local system A MOD 33 work group will be formed for selected events Utilities will report in CG planning meeting for any significant events that can be used for MOD 33 validation. CG will call for participation after an event has been selected for MOD 33 purpose by at least one member. Once an event has been selected, a workgroup will be formed to hold regular meetings to work on the MOD 33 validation for this event. It should be no less than 2 months (planning meeting intervals), after an event being submitted to form a work group

Action Item: Data Acquisition Members provide CG an official authorizations for using measurement data (e.g. from Peak RC).

Action Item: Base case preparation MOD 33 will be primarily performed for event scenario. Power Flow and Dynamic validation can be performed using the same event together. MOD 33 base cases can be derived from two sources: Peak RC, or self developed by CG and members. On top of the base cases developed for MOD 33 events, CG will facilitate to develop certain peak hour cases (heavy summer or heavy winter) for power flow validation purpose (no event necessary).

Action Item: Acceptable Discrepancy At this point, members cannot determine the appropriate quantitative metrics for acceptable discrepancy. It is expected to use some general ranges with exception allowed. The range is expected to improve along the process. CG will obtain an existing recent validation case and measurement data from BPA, do some comparison and get an idea of the discrepancy. The discrepancy will be sent to members for review.

Action Item: Unacceptable Discrepancy In CG process document, a general guideline can be used for resolution of the unacceptable discrepancies. The unsolved discrepancy should also address the discrepancy come from the software aspects. Peak RC should also be involved for certain type of discrepancy observed.

Action Item: Software Platform PowerWorld will be the main tool

Action Item: Training CG will check with WECC for a training of preparing base cases for MOD 33 purpose. If available, CG will host a workshop. On the workshop, BPA will also give a training on local data validation and tutorial on base case tools.

Question: Bo Gong, gong@columbiagrid.org