COMMON ATTRIBUTE. 30 To ensure uniformity of regional reliability standards, a regional reliability standard shall consist of the elements identified in this section of the procedure. These elements are intended to apply a systematic discipline in the development and revision of standards. This discipline is necessary to achieving standards that are measurable, enforceable, and consistent.
COMMON ATTRIBUTE. 28 Each standard shall enable or support one or more of the reliability principles, thereby ensuring that each standard serves a purpose in support of the reliability of the regional bulk power system. Each standard shall also be consistent with all of the reliability principles, thereby ensuring that no standard undermines reliability through an unintended consequence. COMMON ATTRIBUTE 29 While reliability standards are intended to promote reliability, they must at the same time accommodate competitive electricity markets. Reliability is a necessity for electricity markets, and robust electricity markets can support reliability. Recognizing that bulk power system reliability and electricity markets are inseparable and mutually interdependent, all regional reliability standards shall be consistent with NERC’s market interface principles. Consideration of the market interface principles is intended to ensure that standards are written such that they achieve their reliability objective without causing undue restrictions or adverse impacts on competitive electricity markets.
COMMON ATTRIBUTE. 33 Each requirement shall be addressed by one or more measures. Measures are used to assess performance and outcomes for the purpose of determining compliance with the requirements stated above. Each measure will identify to whom the measure applies and the expected level of performance or outcomes required demonstrating compliance. Each measure shall be tangible, practical, and as objective as is practical. It is important to realize that measures are proxies to assess required performance or outcomes. Achieving the measure should be a necessary and sufficient indicator that the requirement was met. Each measure shall clearly refer to the requirement(s) to which it applies. Measure(s)
COMMON ATTRIBUTE. 31 All mandatory requirements of a regional reliability standard shall be within the standard. Supporting documents to aid in the implementation of a standard may be referenced by the standard but are not part of the standard itself.
COMMON ATTRIBUTE. 8 An acceptable standard request shall contain a description of the proposed regional reliability standard subject matter containing sufficiently descriptive detail to clearly define the purpose, scope, impacted parties, and other relevant information of the proposed standard.
COMMON ATTRIBUTE. 20 Under no circumstances may the board substantively modify the proposed regional reliability standard.
COMMON ATTRIBUTE. 26 • Transparent — All actions material to the development of regional reliability standards shall be transparent. All standards development meetings shall be open and publicly noticed on the regional entity’s Web site. COMMON ATTRIBUTE 27 • Does not unnecessarily delay development of the proposed reliability standard.
COMMON ATTRIBUTE. 21 Once a regional reliability standard is approved by the board, the standard will be submitted to NERC for approval and filing with FERC [and applicable authorities in Canada and Mexico.]
COMMON ATTRIBUTE. 12 The standards process manager shall submit the proposed members of the drafting team to the Standards Committee. The Standards Committee shall approve the drafting team membership within 60 days of accepting a standard request for development, modifying the recommendations of the standards process manager as the committee deems appropriate, and assign development of the proposed standard to the drafting team.
COMMON ATTRIBUTE. 10 The [standards] committee may take one of the following actions: • Accept the standard request as a candidate for development of a new standard, revision of an existing standard, or deletion of an existing standard. The [standards] committee may, at its discretion, expand or narrow the scope of the standard request under consideration. The [standards] committee shall prioritize the development of standard in relation to other proposed standards, as may be required based on the volume of requests and resources. • Reject the standard request. If the [standards] committee rejects a standard request, a written explanation for rejection will be delivered to the requester within [no greater than 30] days of the decision. • Remand the standard request back to the requester for additional work. The standards process manager will make reasonable efforts to assist the requester in addressing the deficiencies identified by the [standards] committee. The requester may then resubmit the modified standard request using the process above. The requester may choose to withdraw the standard request from further consideration prior to acceptance by the [standards] committee.
