This comment form is no longer interactive because the comment period is closed.

2015-07 Internal Communications Capabilities | COM-001-3

Description:

Start Date: 09/25/2015
End Date: 11/16/2015

Associated Ballots:

Ballot Name Project Standard Pool Open Pool Close Voting Start Voting End
2015-07 Internal Communications Capabilities COM-001-3 IN 1 ST 2015-07 Internal Communications Capabilities COM-001-3 09/25/2015 10/26/2015 11/06/2015 11/16/2015
2015-07 Internal Communications Capabilities COM-001-3 Non-binding Poll IN 1 NB 2015-07 Internal Communications Capabilities COM-001-3 Non-binding Poll 09/25/2015 10/26/2015 11/06/2015 11/16/2015

Filter:

Hot Answers

1)      We feel the SDT has not properly addressed the directive listed within FERC Order No. 808.  Paragraph 41 of this Order specifically addresses a reliability gap which was created when “internal communications,” which was listed within with the previous standard, COM-001-1.1, was not incorporated into COM-001-2.  The previous standard only applied to RCs, TOPs, and BAs.  We understand that FERC Order No. 693, Paragraph 508 directed the expansion of the standard’s applicability to include GOPs and DPs.  However, we feel that directive was already addressed in COM-001-2.  Does a GOP need to demonstrate internal communication capabilities between its operations dispatch or control center and its power plants?  We also question if communications with geographically separate operational or control centers applies to DPs.  Therefore, we feel the SDT should develop requirements that apply only to RCs, TOPs, and BAs to address the FERC directive. The inclusion of DPs and GOPs go beyond the scope of FERC Order No. 808.

2)      The measure of these proposed requirements do not align with other requirements within the standard.  While an applicable entity could provide proof of compliance through demonstration of a physical asset or proof of that asset’s use, these requirements expect an entity to include examples of all possible internal communications.  How would an entity demonstrate communication between staff physically located within the same room?  We recommend embedding the “Examples” criteria listed within the measures of these standards into the language of each proposed requirement.

3)      In light of our comments, we propose the SDT consider these two alternatives for the requirements:

a)      “Reliability Coordinators, Transmission Operators, and Balancing Authorities, each with geographically separate control centers, shall have Interpersonal Communication capabilities between each separate control center for the exchange of information that is necessary for the Reliable Operation of the BES.”

b)      “Each Balancing Authority and Transmission Operator shall have Interpersonal Communication capabilities with their field switching personnel for the exchange of information that is necessary for the Reliable Operation of the BES.”

Brian Van Gheem, On Behalf of: ACES Power Marketing, NA - Not Applicable, Segments 6

- 0 - 0

This language is too vague to properly address the direction from FERC Order No. 808 to include:

(1) communications between geographically separate control centers within the same functional entity;

(2) communications between a control center and field personnel.

While the language in the measures tries to address the two aforementioned items, the measures are not an auditable portion of the standard, and it is recommended the two items be specifically addressed in R12 and R13.

Joshua Andersen, On Behalf of: Salt River Project, WECC, Segments 1, 3, 5, 6

- 0 - 0

Other Answers

John Fontenot, 10/14/2015

- 0 - 0

John Fontenot, 10/26/2015

- 0 - 0

na

John Fontenot, 10/26/2015

- 0 - 0

 

We agree with adding these two requirements to address the FERC directive, but we do not support the proposed wording for these requirements.

 

Requirements R12 and R13 mandate the provision of internal interpersonal communication capabilities within the same entity when performing its reliability function. Without specific wording that such capabilities are only required for communication between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, these requirements can and will result in entities not having physically separated control centers or staff perform its tasks to be non-compliant. The IESO and most of ISOs and RTOs in North America fall into this category.

 

The Measures for these two requirements do make reference to physically separate control centers or staff in an example for evidence of compliance. However, the specific example only illustrates a way to comply with the requirement. Those entities that do not have physically separated control centers or deploy field staff will not be able to provide such evidence, and hence will fail the two requirements unless they incur in unnecessary expense to install internal interpersonal communication capabilities for communication within the control room, which serves no purpose and add no value at all.

 

To address the intent of the ERRC directive, which we interpret to be requiring internal interpersonal communication capabilities for physically separated control centers or between control center and field personnel within the same entity, we propose the following revisions to R12 and R13:

 

R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities for the exchange of information between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, that is necessary for the Reliable Operation of the BES.

 

R13. Each Distribution Provider shall have internal Interpersonal Communication capabilities for the exchange of information between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, that is necessary for the Reliable Operation of the BES.

 

Alternatively, these requirements can be rearranged as follows:

 

R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, for the exchange of information that is necessary for the Reliable Operation of the BES.

 

Similar rearrangement for the proposed R13.

Leonard Kula, Independent Electricity System Operator, 2, 11/6/2015

- 0 - 0

Jim McDougal, On Behalf of: Public Utility District No. 1 of Snohomish County, WECC, Segments 4

- 0 - 0

While TAL agrees that the new requirements address the FERC Order, we question what differentiates R12 and R13 from R1, R3, R5, R7 and R8.  It appears the only addition is the word “internal” and “for the exchange of information that is necessary for the Reliable Operation of the BES”.  The definition of Interpersonal Communication is “Any medium that allows two or more individuals to interact, consult, or exchange information.” This information is inherent to the reliable operation of the BES.

 

It seems that R12 and R13 are duplicative and do not add any clarity to the standard.  What is the difference between (R12 and R13) and (R1, R3, R5, R7 and R8)?   What is intended in R12 & R13 that would not be required in the existing R1, R3, R5, R7 and R8?

 

The additions as they stand are not clear and unambiguous, hence our Negative Vote.

John Williams, 11/9/2015

- 2 - 0

For a small DP, field communications between control center and operating personnel (both internal to the DP and with other functional entities) may or may not neccesarily flow through a control center or by means of communication that can be recorded, logged, or stored.  This requirement is overly burdensome and, by that token, could result in slower response during an emergency when pace of response is paramount.

Tom Haire, 11/9/2015

- 0 - 0

Scott Williams, 11/9/2015

- 0 - 0

Karen Webb, 11/9/2015

- 0 - 0

Comments to be provided by ACES and NRECA

William Hutchison, On Behalf of: Southern Illinois Power Cooperative, , Segments 1

- 0 - 0

R12 and R13 Evidence Retension prescribes retaining voice recordings for 90 calendar days. However, M12 and M13 do not necessarily require voice recordings at all; it could be logs, transcripts, test records .....

Joe O'Brien, NiSource - Northern Indiana Public Service Co., 6, 11/10/2015

- 0 - 0

While R3 is specific in regards to whom the communication capabilities are to be had *with*, R12 and R13 provide that specificity only within the Measure and not the Requirement.

The inclusion of the word ”or” within the third bullet of M12 and M13 may unintentionally imply a mutually exclusive relationship in regards to providing evidence of Interpersonal Communication capability “between geographically separate control centers within the same functional entity” *or* “ between a control center and field switching personnel”.

Thomas Foltz, AEP, 5, 11/10/2015

- 0 - 0

The comments in FERC Order No. 808 addressed concerns with COM-001-2 R1.1, which is applicable to Reliability Coordinators, Transmission Operators and Balancing Authorities.  The proposed changes include internal communications for Distribution Providers and Generator Operators.

 

R12 and R13 do not address the “adequacy” of the internal communications capabilities.

Matthew Beilfuss, On Behalf of: WEC Energy Group, Inc., RF, Segments 3, 4, 5, 6

- 0 - 0

1.  The broad nature of the proposed requirements allows flexibility for compliance, but creates confusion when identifying evidence requirements.  Entities with multiple communication options would have to consider collecting evidence on every available system to ensure they have evidence of communications in various communications system failure scenarios.  While this may not be the intent, this concern could arise in an audit environment.  The NSRF recommends that the SDT incorporate the newly formed “Implementation Guidance” within this updated Standard to assist entities with this compliance gap of “what types of evidence could we have to assure our internal capabilities are present and operational”. 

2. The broad nature of the proposed requirements also contributes to a concern with the proposed Violation Severity Levels (VSL) for R12 and R13, where failure to provide evidence for a single method of internal communications could lead to a Severe VSL classification.  With additional clarity added to R12 and R13, we recommend the High and Severe VSL classifications be used to address varying degrees of non-compliance, similar to other requirements in this standard.

3. The NSRF questions why GOP is contained in R12 when in part, the last paragraph of the Background Information (page 1) states: “The proposed Requirements address internal Interpersonal Communication capabilities as directed by FERC for Reliability Coordinators, Balancing Authorities, and Transmission Operators in Requirement R12 and for Distribution Providers and Generator Operators in Requirement R13”.  Recommend GOP be removed from R12 and moved to R13.

MRO-NERC Standards Review Forum (NSRF), Segment(s) 3, 4, 5, 6, 1, 2, 11/11/2015

- 0 - 0

While Dominion agrees that the SDT met the directive, and could support the standard as proposed, we have seen comments indicating that many do not. We can’t support the language we’ve seen in those posted comments and therefore offer the following for consideration.

 

 

Dominion, Segment(s) 5, 6, 1, 3, 9/9/2015

NCP draft comments Dominion submitted comments - Project_2015-07_Unofficial_Comment_Form_COM-001-3_Directive_09252015.docx

- 0 - 0

Entergy supports Dominion's comments on R12 and R13.

Oliver Burke, Entergy - Entergy Services, Inc., 1, 11/12/2015

- 0 - 0

Agree with PJM

Comments: Suggest replacing the phrase “internal communications” with another phrase such as “communications between personnel that are not physically co-located.” This change would ensure that the new requirement(s) applies explicitly and only to internal communications:

  • between geographically separate control centers within the same functional entity, or

  • between a control center and field personnel. 

John Falsey, On Behalf of: Invenergy LLC, FRCC, MRO, WECC, Texas RE, NPCC, SERC, SPP RE, RF, Segments 5

- 0 - 0

Andrea Jessup, On Behalf of: Bonneville Power Administration, WECC, Segments 1, 3, 5, 6

- 0 - 0

FE Supports both PJM's and the ISO/RTO Council Standards Review Committee position.

Suggest replacing the phrase “internal communications” with another phrase such as “communications between personnel that are not physically co-located.” This change would ensure that the new requirement(s) applies explicitly and only to internal communications:

·         between geographically separate control centers within the same functional entity, or

·         between a control center and field personnel.

 

The phrase “adequacy of internal communications capability” is ambiguous and needs to be clarified. Is this phrase intended to refer to creation of a requirement that the hardware can adequately handle a conversation, or is it being used in the more generic sense that any new requirement must be adequate to address the two bullet points above?

 

PJM supports the comments submitted by the ISO/RTO Council Standards Review Committee.

FE RBB, Segment(s) 1, 3, 4, 5, 0, 3/3/2015

- 0 - 0

NRECA does not believe the SDT has properly addressed the directive listed within FERC Order No. 808, but has unnecessarily included Generator Operator in requirement R12 and the stand alone R13 for Distribution Providers.   R12 should be modified to only include Reliability Coordinators, Balancing Authorities and Transmission Operators and R13 is not necessary

Patti Metro, On Behalf of: National Rural Electric Cooperative Association, , Segments 3, 4

- 0 - 0

FMPA supports the Bureau of Reclamation’s comments and believes the proposed revisions go beyond the scope of the FERC directive and what is required for BES reliability by including GOP and DP in the new requirements.

FMPA, Segment(s) , 11/13/2015

- 0 - 0

Scott Langston, Tallahassee Electric (City of Tallahassee, FL), 1, 11/13/2015

- 0 - 0

Internal Interpersonal Communications used solely to communicate within a Facility (i.e. radio communication between operators) are inherent and necessary for the safe and reliable operation of that Facility and should be excluded from COM-001-3 due to the lack of reliabilty benefit. 

Jay Barnett, 11/13/2015

- 1 - 0

The Bureau of Reclamation appreciates the drafting team’s efforts to address the reliability gap discussed in FERC Order No. 808 P 41 (Apr. 16, 2015) that was created when internal communications addressed in Requirement R1.1 of COM-001-1 were not included in COM-001-2.

As noted in P 41, Requirement R1.1 only applies to Reliability Coordinators, Transmission Operators and Balancing Authorities.  However, the proposed changes in COM-001-3 go beyond the scope of FERC Order No. 808 by adding requirements for internal communications for Generator Operators and Distribution Providers.  Reclamation suggests that the Generator Operator and Distribution Provider functions should be removed from requirements R12 and R13 proposed for COM-001-3. 

Reclamation believes that the proposed requirement for the Reliability Coordinator, Transmission Operator, and Balancing Authority functions fully addresses the reliability gap discussed in Order No. 808, P 41.  This suggestion is consistent with FERC’s acknowledgement in Order 808 of the lower impact of Generator Operator and Distribution Provider communications on the Bulk-Power System.

Erika Doot, 11/13/2015

- 0 - 0

Reliable operation of the BES requires that generation, transmission, and load operate in synchronism.  Communication between and within entities involved in generation, transmission, and distribution is an important element in ensuring reliability.  We agree with the inclusion of the GOP and DP entities in the standard.  However, we disagree that the VRF associated with the DP is somehow different than for the GOP or the TOP.  Load shed is an integral aspect of maintaining reliability and is preferred to be implemented at the distribution level rather than the transmission level to ensure the maximum level of reliability.

Meghan Ferguson, 11/16/2015

- 0 - 0

Talen Energy supports FERC’s objective in Order 808, but we believe that COM-001-3 R12 is presently worded so generically that interpretations by entities as to its practical meaning might miss the specific points that FERC emphasized, and might add plant-internal communications that FERC did not intend to cover.  We respectfully suggest that, similar to PER-005, only Control Centers should have a compliance obligation for R12.  That is, R12 should have a Generator Operator footnote stating, “This requirement applies for Generator Operators only for communications between geographically separate Control Centers and between Control Center operators and field personnel they direct.  It does not apply for operators located at a generator plant site.”

Donald Lock, 11/16/2015

- 0 - 0

As noted in FERC Order No. 808 P41, COM-001-1.1 Requirement R1.1 only applied to Reliability Coordinators, Transmission Operators and Balancing Authorities.  However, the proposed changes in COM-001-3 go beyond the scope of FERC Order No. 808 by adding requirements for internal communications for Generator Operators.  TVA suggests that the Generator Operator function should be removed from requirements R12 proposed for COM-001-3.

Joel Wise, On Behalf of: Tennessee Valley Authority - SERC - Segments 1, 3, 5, 6

- 0 - 0

Suggest replacing the phrase “internal communications” with another phrase such as “communications between personnel that are not physically co-located.” This change would ensure that the new requirement(s) applies explicitly and only to internal communications:

  • between geographically separate control centers within the same functional entity, or
  • between a control center and field personnel. 

The phrase “adequacy of internal communications capability” is ambiguous and needs to be clarified. Is this phrase intended to refer to creation of a requirement that the hardware can adequately handle a conversation, or is it being used in the more generic sense that any new requirement must be adequate to address the two bullet points above?

 

PJM supports the comments submitted by the ISO/RTO Council Standards Review Committee.

- 0 - 0

Illinois Municipal Electric Agency (IMEA) recommends deletion of proposed Requirement 13 since it is not necessary for Reliable Operation of the BES.  IMEA questions the necessity of both R12 and R3.  IMEA is not aware of any communication of event analysis information indicating the lack of internal Interpersonal Communication capabiltiy is an issue, or that the lack of this capability contributed to reduced reliabiltiy of the BES.  If for some reason R12 is needed, IMEA supports consideration of other survey suggestions.  R13 is not needed for reliability of the BES.

Bob Thomas, 11/16/2015

- 0 - 0

We feel that the wording of the two new measures M12 and M13 introduce several ambiguities.  The first is that the Measures seem to attempt to define what “internal” Interpersonal Communication capabilities are.  The wording of both measures is inconsistent as well.  It seems that demonstration of “capability” is being defined in the Measures as simply providing evidence of a physical asset or evidence that documentation of previous communication was made. 

 

There is also concern that it may not be clear to auditors that the “operating procedures” used to preserve or maintain the capability may not be the procedure or process used by operators sitting at the real-time desk.  These processes or procedures may be utilized by support staff such as IT staff that may do things behind the scenes to ensure the capability is maintained.

 

R12 and R13 may not be applicable to all registered entities mentioned.  In some cases, the registered entities may have no need for “internal” communication capability since all of the personnel necessary to perform their functional obligations are in the same room.  It seems the SDT intends that this is an acceptable arrangement, but we struggle to understand how internal communication capability can be demonstrated when under an audit but is not necessary for the registered entity to perform its obligations.

 

We also feel the SDT has exceeded the FERC directive by including the GOP and DP in the applicability of these new requirements and should be eliminated from the applicability of R12 and R13.

 

We suggest that the SDT consider rewriting R12 and R13 to be explicitly applicable to situations where the single, registered entity (RC, TOP, BA, GOP, DP) is required to have “internal” communication capabilities when it has either or both geographically separated control centers or a need to communicate with field personnel in carrying out its functional responsibilities.  This would remove or lessen the burden on the term “internal” being carried by the current wording.  The FERC directive seems to be limited to those two specific types of scenarios that were envisioned by the original COM-001-1 language. For example:

 

R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities for the exchange of information that is necessary for the Reliable Operation of the BES when:

  • The RC, TOP, GOP, or BA must communicate with its personnel who are residing in geographically separated control centers, or

  • The RC, TOP, GOP, or BA must communicate with field personnel.

 

Perhaps including in the Measure another bullet such as:  Evidence could include an analysis of reliability related tasks (as developed for PER-005-2) to be performed by the RC, TOP, BA, GOP, or DP that require use of an internal communication medium.  That medium is the internal communication capability that must be demonstrated.  Alternatively, a definition of Internal Intercommunication Capability could be created that clarifies when internal communication capabilities are required.

SPP Standards Review Group, Segment(s) 1, 3, 5, 11/16/2015

- 0 - 0

In requirement R12, the phrase “for the exchange of information that is necessary for the Reliable Operation of the BES” is ambiguous and needs to be clarified.  In addition, the requirement needs to specify which parties the RC, TOP, GOP, and BA need internal Interpersonal Communication capabilities with in order to be compliant.

- 0 - 0

LCRA Compliance, Segment(s) 6, 1, 5, 5/11/2015

- 0 - 0

- 0 - 0

Communication with field personnel may be done via cellphones.  The Standard should explain that it is sufficient to simply designate cellphone communications as the means to communicate and not require phone lists to be provided.

 

Does the Standard create an obligation for field personnel to be able to communicate immediately with the control center?  For example, a vegetation inspector may see a potential encroachment into a transmission line, but is in a cellphone dead zone.  Is being in a dead zone a violation of R13 since the internal Interpersonal Communication Capability was not capable of communicating?  There needs to be guidance that dead zones are allowed for field personnel. The Requirement should recognize non-functioning capability. 

 

What constitutes being “geographically separate”? How many miles? Who determines this distance?

 

 

We agree with adding these two requirements to address the FERC directive, but we do not support the proposed wording for these requirements.

 

Requirements R12 and R13 mandate the provision of internal interpersonal communication capabilities within the same entity when performing its reliability function. Without specific wording that such capabilities are only required for communication between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, these requirements can and will result in entities not having physically separated control centers or staff perform its tasks to be non-compliant. The IESO and most of ISOs and RTOs in North America fall into this category.

 

The Measures for these two requirements do make reference to physically separate control centers or staff in an example for evidence of compliance. However, the specific example only illustrates a way to comply with the requirement. Those entities that do not have physically separated control centers or deploy field staff will not be able to provide such evidence, and hence will fail the two requirements unless they incur in unnecessary expense to install internal interpersonal communication capabilities for communication within the control room, which serves no purpose and adds no value at all.

 

To address the intent of the FERC directive, which we interpret to be requiring internal interpersonal communication capabilities for physically separated control centers or between control center and field personnel within the same entity, we propose the following revisions to R12 and R13:

 

“R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities for the exchange of information between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, that is necessary for the Reliable Operation of the BES.”

 

“R13. Each Distribution Provider shall have internal Interpersonal Communication capabilities for the exchange of information between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, that is necessary for the Reliable Operation of the BES.”

 

Alternatively, these requirements can be rearranged as follows:

 

“R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities between geographically separate control centers within the same functional entity, or between a control center and field switching personnel, for the exchange of information that is necessary for the Reliable Operation of the BES.”

 

Similar rearrangement for the proposed R13.

RSC, Segment(s) 1, 0, 2, 3, 4, 5, 6, 7, 11/16/2015

- 0 - 0

Occidental Chemical Corporation (OCC) believes that the strategy taken by the Standards Drafting Team (SDT) to address FERC’s directives is too open ended.    Examples are provided in the associated Measures, but do not expressly limit the expansion in scope to (1) control center-to-control center and (2) control center-to-field personnel information exchange.  Since the Commission only required those two additions to the standard, it seems unnecessary to open the door for other communication pathways that may happen to exist.

 

FERC will see no material difference between two internal TOP Control Centers versus those operated by two separate Registered Entities – both requiring Alternative Interpersonal Communication capability.  Comparatively, a Distribution Provider’s internal work centers would not need this level of redundancy.

 

It was not easy for industry to reach consensus on COM-001-2.  It took six years to reach the right balance of precision and flexibility needed to specify the Entity-to-Entity information exchange links that are necessary for reliable electric system operations.  As such, we propose that the SDT leverage the standard’s existing structure to enact FERC’s directives.  This entails the addition of the two new specific communication pathways as sub-requirements to the existing requirements.  As an example, we suggest that R5.5 and R5.6 would be added as shown below:

 

R5. Each Balancing Authority shall have Interpersonal Communication capability with the following entities (unless the Balancing Authority detects a failure of its Interpersonal Communication capability in which case Requirement R10 shall apply):  [Violation Risk Factor:  High] [Time Horizon:  Real-time Operations]

5.1. Its Reliability Coordinator.

5.2. Each Transmission Operator that operates Facilities within its Balancing Authority Area.

5.3. Each Distribution Provider within its Balancing Authority Area.

5.4. Each Generator Operator that operates Facilities within its Balancing Authority Area.

5.5. Each Adjacent Balancing Authority.

5.6. Each internal control center which operates two or more Facilities within its Balancing Authority Area.

5.7. Field personnel who execute tasks that require element switching as part of that task.

Oxy, Segment(s) 7, 5, 7/15/2015

- 0 - 0

See Occidental Chemical Corporation's comments.

Michelle D'Antuono, On Behalf of: Michelle D'Antuono, , Segments 5

- 0 - 0

One of the Measurement bullets is stated as:

 

“Examples include, but are not limited to, geographically separate control centers within the same functional entity, or between a control center and field personnel”

 

This Measurement needs to be proofed, as it does not specify a “capability”.  It summarizes a condition which seems meant to describe what “internal” might mean – not what constitutes a Communications capability.  The Measurement bullet appropriately qualifies “geographically separate control centers” by referring to “within the same functional entity”, and could state the same with regard to “between a control center and field personnel [within the same functional entity]” to reinforce that the requirement is meant to be interpreted to “internal” communications only.

 

Field personnel may be too vague for registered entities.  Perhaps a reference could be made to personnel that operate or maintain Facilities (or some other term from the NERC Glossary).

 

Finally, because “internal” is not defined, the reference to “Including, but not limited to” may not be appropriate, because it creates an unbounded condition of an undefined term – rather than setting a baseline (i.e., a non-exclusive list) of the types of records or evidence that would demonstrate compliance with a requirement.

Scott McGough, Georgia System Operations Corporation, 3, 11/16/2015

- 0 - 0

Duke Energy , Segment(s) 1, 5, 6, 4/10/2014

- 0 - 0

Although the proposed requirements “address” the stated concerns, the proposals introduce an unneeded level of ambiguity. Please see our comments and suggestions under Q2.

ISO/RTO Council Standards Review Committee, Segment(s) 2, 5/11/2015

- 0 - 0

While Southern believes that the proposed requirements are a good attempt by the SDT to address the directive in FERC Order 808, we also believe that the current COM-001-2 standard already implies that the named functions should have Interpersonal Communications capabilities for the exchange of reliability information internally between such functions that are a part of the same organization, but are geographically dispersed.  To add additional requirements would be duplicative in nature, would only result in an added administrative burden on the industry and would not substantially contribute to the overall reliability of the system.

Southern Company, Segment(s) 1, 3, 5, 6, 3/27/2015

- 0 - 0

Essential Power supports the comments submitted by PJM regarding this proposed standard.

Gerry Adamski, 11/16/2015

- 0 - 0

- 0 - 0

Although the language in new Requirements 12 and 13 appears to mirror FERC-approved language in other existing COM-001 requirements that certain functions “shall have Interpersonal Communication capability,” the new standards do not incorporate the various provisions throughout the remainder of COM-001 that appear designed to ensure those communication capabilities are also adequate.  For example, under the current COM-001-3 requirements for external communications, Transmission Operators (TOPs) are required to maintain Interpersonal Communications capability (R3), as well as Alternative Interpersonal Communication capability with certain functions as a backup (R4).  In addition, TOPs are required to test Alternative Interpersonal Communications capability monthly (R9) and notify certain entities of any failure of its Interpersonal Communications capability lasting thirty minutes or longer (R10).  Taken together, these additional requirements appear to be designed to ensure that a TOP’s communications capabilities are reliable and adequate, particularly for communications that are necessary for BES reliability.

Texas RE recommends the SDT consider whether in the absence of these additional requirements of Alternative Interpersonal Communications, testing, and notification, Requirements 12 and 13 satisfy FERC’s directive to ensure “adequate” internal communications capability.  The SDT could address this issue by either: (1) incorporating appropriate requirements from the existing COM-001 requirements into Requirements 12 and 13; or (2) revising Requirements 12 and 13 to require registered entities to have “adequate” internal Interpersonal Communication capability.

Rachel Coyne, Texas Reliability Entity, Inc., 10, 11/16/2015

- 0 - 0

Comments: ERCOT respectfully suggests that Requirements R12 and R13 are overly broad as written, which could result in ambiguity and subjectivity regarding the communications capabilities that are necessary.  While the measures attempt to better bound the expectations, ERCOT suggests that the measure is not the appropriate location for ensuring the clarity of the proposed requirement.  To ensure that expectations are clear, concise, and definitive, ERCOT recommends the following revisions to Requirements R12 and R13:

R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities to exchange information as necessary to preserve the Reliable Operation of the BES between its:
•    Geographically separate control centers 
•    Geographically separate control centers and field personnel. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]

R13. Each Distribution Provider shall have internal Interpersonal Communication capabilities to exchange information as necessary to preserve the Reliable Operation of the BES between its:
•    Geographically separate control centers 
•    Geographically separate control centers and field personnel. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]

Alternatively, ERCOT suggests that requirements R12 and R13 be combined as follows:

R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, Distribution Provider, and Balancing Authority shall internal Interpersonal Communication capabilities to exchange information as necessary to preserve the Reliable Operation of the BES between its:
•    Geographically separate control centers 
•    Geographically separate control centers and field personnel. [Violation Risk Factor: High] [Time Horizon: Real-time Operations]

Elizabeth Axson, 11/16/2015

Project_2015-07_Unofficial_Comment_Form_COM-001-3_Directive_09252015_draft from CVB.docx

- 0 - 0

Colorado Springs Utilities does not see a reliability gap requiring the addition of Requirements R12. and R13.  Communication with field personnel is a requirement of conducting business.

Colorado Springs Utilities, Segment(s) 1, 6, 3, 5, 9/14/2015

- 0 - 0

ATC has the following cvoncerns:(as applicable to Transmiision Operators in Requirement 12) and ask that the SDT consider these in the next draft of Relaibility Standard COM-001:

The broad nature of the proposed requirement (Requirements R12 in the proposed COM-001-3) allows flexibility for compliance, but creates confusion when identifying evidence requirements.  Entities with multiple communication options would have to consider collecting evidence on every available system to ensure they have evidence of communications in various communications system failure scenarios.

 

The broad nature of the proposed requirements also contributes to a concern with the proposed Violation Severity Levels (VSL) for R12, where failure to provide evidence for a single method of internal communications could lead to a Severe VSL classification.

   

Andrew Pusztai, 11/16/2015

- 0 - 0

Hot Answers

1)      We are concerned that the changes proposed in Reliability Standard COM-001-3 are too vague and provide a wide range of interpretations for auditors.  We feel the SDT’s approach to addressing the FERC Order No. 808 directive could be handled through modification of existing requirements.

2)      The VSLs for Requirements R12 and R13 currently have only a Severe VSL identified.  We believe the VSL criteria for these requirements should focus less on the ability to possess Interpersonal Communication capabilities and more on how they will be used within a specific timeframe.  We feel this shift would move these requirements more towards human performance improvements and situational awareness for System Operators and supporting staff.

3)      We feel the six-month time frame listed within the implementation plan is too short for smaller entities, like DPs, to incorporate the infrastructure needed to demonstrate compliance with this standard.  We recommend a 18-month time frame to better prepare all entities, as this allow entities time to budget and allocate resources that support the documentation of internal communications.

4)      We thank you for this opportunity to comment on this standard.

Brian Van Gheem, On Behalf of: ACES Power Marketing, NA - Not Applicable, Segments 6

- 0 - 0

None

Joshua Andersen, On Behalf of: Salt River Project, WECC, Segments 1, 3, 5, 6

- 0 - 0

Other Answers

n/a

John Fontenot, 10/14/2015

- 0 - 0

na

John Fontenot, 10/26/2015

- 0 - 0

na

John Fontenot, 10/26/2015

- 0 - 0

 

Communication capabilities are the basic “tools” needed for applicable entities to perform their functions. As such, they are more suited for inclusion in the Organization Certification requirements, not Reliability standards which are intended to drive the right behavior to mitigate specific risks or achieve specific reliability outcomes. We urge the SDT and NERC to consider moving the proposed additional requirements and/or the entire COM-001 to Organization Certification Requirements.

Leonard Kula, Independent Electricity System Operator, 2, 11/6/2015

- 1 - 0

Jim McDougal, On Behalf of: Public Utility District No. 1 of Snohomish County, WECC, Segments 4

- 0 - 0

John Williams, 11/9/2015

- 0 - 0

Tom Haire, 11/9/2015

- 0 - 0

Scott Williams, 11/9/2015

- 0 - 0

Please see social survey

Karen Webb, 11/9/2015

- 0 - 0

None

William Hutchison, On Behalf of: Southern Illinois Power Cooperative, , Segments 1

- 0 - 0

Joe O'Brien, NiSource - Northern Indiana Public Service Co., 6, 11/10/2015

- 0 - 0

While AEP is supportive of the overall efforts of this project team, AEP has chosen to vote negative due to our concerns regarding R12 and R13. As stated previously, while R3 is specific in regards to whom the communication capabilities are to be had *with*, R12 and R13 provide that specificity only within the Measure and not the Requirement.

 

Thomas Foltz, AEP, 5, 11/10/2015

- 0 - 0

R12 and R13 as written do not meet the tenants of a results based standard.  Specifically they do not focus on required actions or results (the "what"), but rather focus on the methods by which to accomplish actions or results (the "how").  Results based standards require “each requirement to identify a clear and measurable expected outcome, such as: a) a stated level of reliability performance, b) a reduction in a specified reliability risk (prevention), or c) a necessary competency.”

It is difficult to contemplate a situation where a functional entity would be meeting existing reliability standards and not have an internal Interpersonal Communication capability between control centers or to field personnel necessary for the Reliable Operation of the BES.  The existing standards are the measures of entities Reliable Operation of the BES, not the existence of an internal communications capability.  The activity required as part of the R12 and R13 is the documentation associated with the measure.  As such, both requirements as written qualify under Paragraph 81 Criterion:

A. Overarching Criterion: “The Reliability Standard requirement requires responsible entities (“entities”) to conduct an activity or task that does little, if anything, to benefit or protect the reliable operation of the BES.” 

B1. Administrative:  “The Reliability Standard requirement requires responsible entities to perform a function that is administrative in nature, does not support reliability and is needlessly burdensome.”  In the case of R12 and R13 the requirement is purely documentation, having something in line with the measures.

B3. Documentation: “The Reliability Standard requirement requires responsible entities to develop a document (e.g., plan, policy or procedure) which is not necessary to protect BES reliability.  This criterion is designed to identify requirements that require the development of a document that is unrelated to reliability or has no performance or results-based function. In other words, the document is required, but no execution of a reliability activity or task is associated with or required by the document.

Matthew Beilfuss, On Behalf of: WEC Energy Group, Inc., RF, Segments 3, 4, 5, 6

- 0 - 0

Measure M9 in COM-001-2 contains guidance (also included in RSAW guidance) pertaining to evidence requirements for R9 that conflict with the R9 requirement scope.  Recommend that conflicting guidance be deleted or clarified to indicate that one applicable entity can be contacted to verify that an entity’s Alternative Interpersonal Communication capability works.  Requiring each entity to contact all other entities is redundant and wasteful under the Paragraph 81 concepts.  Since COM-001-2 or COM-001-3 R9 doesn’t state that “each” Alternative Interpersonal Communication capability path will be tested with “each” identified entity, then testing one Alternative Interpersonal Communication capability is acceptable under the R9 requirement scope.  NERC auditors should not expand the scope of a requirement through measures or through the RSAW process.

MRO-NERC Standards Review Forum (NSRF), Segment(s) 3, 4, 5, 6, 1, 2, 11/11/2015

- 0 - 0

Dominion, Segment(s) 5, 6, 1, 3, 9/9/2015

- 0 - 0

Entergy has no additional comments.

Oliver Burke, Entergy - Entergy Services, Inc., 1, 11/12/2015

- 0 - 0

John Falsey, On Behalf of: Invenergy LLC, FRCC, MRO, WECC, Texas RE, NPCC, SERC, SPP RE, RF, Segments 5

- 0 - 0

Andrea Jessup, On Behalf of: Bonneville Power Administration, WECC, Segments 1, 3, 5, 6

- 0 - 0

FE RBB, Segment(s) 1, 3, 4, 5, 0, 3/3/2015

- 0 - 0

The following are comments about how the term “capability” is used in the relationship of the term in the Requirements and the Measurement for R12 and R13:

  • The Requirement and Measurement establish that the registered entity must have internal Interpersonal Communications “capability”.  The Measurement bullet reading “Examples include, but are not limited to, between geographically separate control centers within the same functional entity, or between a control center and field switching personnel” does not specify a “capability.  It summarizes a condition which seems meant to describe what “internal” might mean. It does not appear to constitute a Communications capability.
  • The Measurement bullet appropriately qualifies “geographically separate control centers” by referring to “within the same functional entity”. Suggest modifying the requirements to state the same with regard to “between a control center and field personnel [within the same functional entity]” to reinforce that the requirement is meant to be interpreted to “internal” communications only. 

Assuming that R12 and R13 are modified because of the overreach of including the Generator Operators and Distribution Providers the following revised  R12 is provided for consideration:

  • R12 - Reliability Coordinators, Transmission Operators, and Balancing Authorities, each with geographically separate control centers, shall have Interpersonal Communication capabilities between each separate control center and with their field switching personnel for the exchange of information that is necessary for the Reliable Operation of the BES.

R12 and R13 are vague because “internal” is not clearly defined, therefore, the reference to “Including, but not limited to” may not be appropriate, because it creates an unbounded condition of an undefined term. A list of the types of records or evidence that would demonstrate compliance with a requirement should be included in the measure.

The six-month implementation time frame is not adequate to incorporate the infrastructure needed to demonstrate compliance with this standard which may include conducting training, developing procedures with internal controls and possibly installation of new equipment to monitoring capability. Suggest modifying the implementation to 12 to 18 months.

It is unclear whether it is necessary to demonstrate internal communication capabilities between control center and power plants. If it is necessary, it should be stated as such in the requirements.  

An explanation of what constitutes an “Alternative Interpersonal Communication” is required. It is unclear whether this form of communication is a “different medium” or a “different infrastructure”.

Patti Metro, On Behalf of: National Rural Electric Cooperative Association, , Segments 3, 4

- 0 - 0

FMPA, Segment(s) , 11/13/2015

- 0 - 0

Scott Langston, Tallahassee Electric (City of Tallahassee, FL), 1, 11/13/2015

- 0 - 0

No other comment.

Jay Barnett, 11/13/2015

- 0 - 0

Reclamation suggests that the drafting team develop a guidelines and technical basis section to clarify the scope of evidence required under normal and communications failure scenarios.  Reclamation notes that the broad nature of Requirements R12 and R13 allows flexibility for compliance, but also creates confusion when identifying evidence requirements.  Registered entities with multiple communication options would have to consider collecting evidence on all of them to ensure they have evidence of communication capability in various communications system failure scenarios.  While this may not be the intent of the drafting team, this concern could arise in an audit environment, and could be mitigated by a clarifying guidelines and technical basis section.

Erika Doot, 11/13/2015

- 0 - 0

Meghan Ferguson, 11/16/2015

- 0 - 0

Donald Lock, 11/16/2015

- 0 - 0

Joel Wise, On Behalf of: Tennessee Valley Authority - SERC - Segments 1, 3, 5, 6

- 0 - 0

- 0 - 0

NA

Bob Thomas, 11/16/2015

- 0 - 0

SPP Standards Review Group, Segment(s) 1, 3, 5, 11/16/2015

- 0 - 0

- 0 - 0

In Order No. 808, P 38, ITC comments that when communications are handled between functional entities within the same organization “face-to-face,” that the requirements in COM-001-2 would not apply.  While not a directive, in Order No. 808, P 40, the Commission states “requirements concerning Alternative Interpersonal Communication only apply when those communications are performed by means other than direct, face-to-face situations.”  For multi-registered entities that communicate face-to-face, we feel the standard should address those situations.

Additionally, while version 3 is being drafted, we feel the SDT should also review the associated RSAW.  Most notably under the “Evidence Requested” section of R9, it appears to require that entities must test their Alternative Interpersonal Communication capability with all applicable entities under R2, R4, or R6 respectively.  The requirement only states that the entity must test their Alternative Interpersonal Communication capability at least once per calendar month and the measure clarifies the testing to “its Alternative Interpersonal Communication capability designated in Requirements R2, R4, or R6.”

LCRA Compliance, Segment(s) 6, 1, 5, 5/11/2015

- 0 - 0

- 0 - 0

Suggest a Guidelines and Technical Basis Section be added in COM-001-3 to address the following:

 

A guideline and technical basis or specific Requirement language for Requirements R12 and R13 to explain and incorporate the FERC Directive that the concern is communication between “(1) communications between geographically separate control centers within the same functional entity; and (2) communications between a control center and field personnel.”  

 

This Standard requires that an Entity establishes the capability to exchange information.  The Standard intentionally requires the capability for Interpersonal Communication and not the ability for engaging in Interpersonal Communication.  Capability represents only a potential to engage in communication. By using the word capability the Standard allows for the communication medium to be non-functioning from time to time. 

 

Interpersonal Communication is defined in the NERC Glossary as “Any medium that allows two or more individuals to interact, consult, or exchange information.”  There is no restriction on the types of medium that can be used.  Common types are phone system, wireless, radio, written (paper and electronic) and in-person.

 

For R1 thru R8 the Interpersonal Communication capability is established between functional entities and not based on corporate affiliation.  For example if Company A is registered as a TOP and RC. The TOP function and RC function operate from different rooms in the same building.  Then Interpersonal Communication capability is required and an alternate Interpersonal Communication capability is designated.

 

The Standard does not require that Interpersonal Communication capability is functioning 100% of the time.  When the primary Interpersonal Communication capability fails the entity switches to the designated alternate Interpersonal Communication capability with recognition that there will be a point in time when no designated capability is available.

 

 

This Standard does not require the bailout of a specific type of communication infrastructure.

 

Communication capabilities are the basic “tools” needed for applicable entities to perform their functions. As such, they are more suited for inclusion in the Organization Certification requirements, not Reliability standards which are intended to drive the right behavior to mitigate specific risks or achieve specific reliability outcomes. We urge the SDT and NERC to consider moving the proposed additional requirements and/or the entire COM-001 to Organization Certification Requirements.

 

Please provide a Guidance Section with the following wording and provide the answers to the following questions:

QUESTION:  An open question under this proposed standard is whether both alternate technologies AND alternate forms of communications can serve as back-up?

Same Type - That is, can alternate technology substitute voice for voice; i.e., digital phone Voice Over IP (VOIP) is a viable alternative for dedicated analog lane lines or light-pipe lines?

QUESTION:  May we assume that an acceptable Alternative Interpersonal Communications capability is not necessarily the same type in the form of an alternate technology?

May a different types of communications serve as back-up; i.e., can cell phone voice be used as a substitute for or be backed-up by internet-based e-mail communications?

We suggest that the SDT, for the sake of clarification, add a Technical and Guidance Section of the Standard. For example, add the following suggested wording:

Guidance Section

Requirement R4: 

Same Type, Different Technologies - Alternative Interpersonal Communication capabilities are many and evolving with the changing technology. Current examples of viable Alternative Interpersonal Communication capabilities could include digital phone (Voice Over IP), Satellite phone, and/or a Cell Phone network that could individually or collectively serve as a viable alternate/back-up for a dedicated landline fiber-optics voice connection.

Different Types, Different Technologies - A viable Alternative Interpersonal Communication capability for a dedicated direct-digital computer communications protocol might include internet-based e-mail communications. Different types and technologies may be mixed in communicating with different entities. GOP back-up could be cell phone, while the RC back-up could be e-mail.

Requirement R9 – Each Reliability Coordinator, Transmission Operator, and Balancing Authority must test its Alternative Interpersonal Communication capability at least once each calendar month. If the test is unsuccessful, the responsible entity must initiate action to repair or designate a replacement Alternative Interpersonal Communication capability within 2 hours.

QUESTIONS:

•     Is the expectation that the repair be “initiated” within two (2) hours and is this realistic?

•     What is “initiate action to repair?” If the system operator sends an e-mail repair request to IT, is that sufficient to “initiate action to repair?”

•     If action cannot be initiated within two (2) hours, is this a reportable event?

•    What happens if the system operator must take other specific actions to follow an RC or TOP reliability directive, e.g., to protect system reliability, then does the entity get an exception, a free “pass,” on the two (2) hour requirement?

•     Would the SDT accept a longer initiation time, e.g., four (4) hours?

•     Would the SDT accept an exception clause for reliability directives and system emergencies, i.e., add the wording to R9 “… initiate action to repair within 2 hours, except during a declared system emergency or unless required to follow RC, BA or TOP directive(s) to protect, maintain or restore system reliability.”

 

There is an error in the R9 and R10 VSL table that has been carried over from the COM-001-2 version.  In the R9 Lower VSL column , it states “…but failed to initiate action to repair or designate a replacement Alternative Interpersonal Communication in more than 2 hours and less than or equal to 4 hours upon an unsuccessful test”. The RC, TOP, BA did not fail to initiate the action, they did the action, but not within the time required. The VSL should be rephrased to remove the word “failed”. The same comment applies to R9 Moderate, High and Severe VSL.

 

A similar comment applies to the R10 VSL. The RC, TOP and BA did not fail to notify the entities identified in R1, R3 and R5, they did it, just not in the time required. It should read “…notified the entities in R1, R3 and R5 respectively upon detection of a failure of its Interpersonal Communication capability, but in a delay of more than 60 minutes and less than or equal to 70 minutes). The same comment applies to R10 Moderate, High and Severe VSL.

RSC, Segment(s) 1, 0, 2, 3, 4, 5, 6, 7, 11/16/2015

- 0 - 0

 OCC does not agree that the statutory term “Reliable Operation”, which relates to the Bulk Power System, should be used in the context of requirements applicable to the Bulk Electric System.  They are not the same and are inconsistent with the principles of clarity that are fundamental to reliability compliance oversight.

 

Additionally, OCC believes that the proposed new requirements apply to two individuals located in the same work center.  Registered Entities with a large multi-function work center may choose to include those forms of communication, but that should be their choice.  However, M12 and M13 leave open the possibility that CEA’s will be second-guessing the Operating Entity’s choice of applicable communications – which we do not believe is  the SDT’s intent.

Oxy, Segment(s) 7, 5, 7/15/2015

- 0 - 0

Michelle D'Antuono, On Behalf of: Michelle D'Antuono, , Segments 5

- 0 - 0

Scott McGough, Georgia System Operations Corporation, 3, 11/16/2015

- 0 - 0

Duke Energy requests confirmation from the drafting team that the intent of this standard is to address only that an entity have the capabilities to exchange information that is necessary for the Reliable Operation of the BES, and not individual instances where field personnel may lose communication capability depending on geographic situation. For example, an entity may have the physical capability (via SAT Phone, etc) to communicate with field personnel, but said field personnel enters into an area where communication is limited based on mountainous terrain. It is our interpretation that this momentary interruption is not an instance of non-compliance, and that as long as a permanent capability to communicate exists (existence of the SAT phone), the entity would be considered compliant. Is this interpretation accurate?

Duke Energy suggests the removal of the term “switching” from the phrase “field switching personnel” found in the measure of both requirements. We feel that the removal of the term promotes greater flexibility for entity interpretation, and more closely aligns with the language that exists in FERC Order 808.

Duke Energy recommends the drafting team consider the following term and definition to be used in place of “internal Interpersonal Communication”:  

Intrapersonal Communication:

Any medium that allows two or more individuals to interact, consult, or exchange information within the same functional entity or between a control center and field personnel.

We feel that this definition fits the context with which the drafting team was intending, and helps bring clarity to an area that may be considered confusing to some in the industry.

Duke Energy , Segment(s) 1, 5, 6, 4/10/2014

- 0 - 0

The SRC recommends:

  • that the SDT offer the Industry the option (and FERC the alternative)  to make this capability a certification requirement  rather than a relativity standard requirement that the SDT

  • the phrase “information that is necessary for the reliable operation of the BES” be replaced by “Operating Instructions.” The phrase “necessary for reliable operation of the BES” is unnecessary; not addressed in the measures; and creates unneeded ambiguity.

  • the SDT revise Requirements 12 & 13 to clarify what “internal” communications means so that the Requirements are clear about the applicability of these requirements.  This issue could be addressed by moving the language from the 3rd bullet of Measures 12 & 13 which reads – “Geographically separate control centers within the same functional entity” – into the Requirements such that R12 and R13 will read:

    R12. Each Reliability Coordinator, Transmission Operator, Generator Operator, and Balancing Authority shall have internal Interpersonal Communication capabilities for the exchange of information between geographically separate control centers within the same functional entity that is necessary for the Reliable Operation of the BES.

    R13. Each Distribution Provider shall have internal Interpersonal Communication capabilities for the exchange of information between geographically separate control centers within the same functional entity that is necessary for the Reliable Operation of the BES.

    The 3rd bullet of Measures M12 & M13 needs to be deleted or corrected. The “example” provided in the 3rd bullet does not given an example of communications “capability”.  It provides an illustration of what “internal” means, and as noted above, that should be in the Requirement itself.

  • If the 3rd bullet of Measures M12 & M13 is kept, then fixing the bullet so that the references to communications between a control center and field switching personnel refer to such communications as occurring within the same Registered Entity (i.e., “internal”).

  • If the 3rd bullet in Measures M12 and M13 are kept, clarify the references to “field switching personnel” by including a reference to the NERC Glossary, so that the Measures are not relying on an undefined term.  Perhaps the Measures could refer to “personnel that operate or maintain Facilities” (or some other term from the NERC Glossary). 

ISO/RTO Council Standards Review Committee, Segment(s) 2, 5/11/2015

- 0 - 0

Southern recommends that the proposed requirements be modified as follows:

R12. Each Reliability Coordinator, Transmission Operator, and Balancing Authority that identifies the need to exchange information necessary for the Reliable Operation of the BES between geographically separate control centers within the same functional entity, or between a control center and field switching personnel shall have Interpersonal Communication capability addressing how this information is to be exchanged.

R13. Each Distribution Provider and Generator Operator that identifies the need to exchange information necessary for the Reliable Operation of the BES between geographically separate control centers within the same functional entity, or between a control center and field switching personnel shall have Interpersonal Communication capability addressing how this information is to be exchanged.

Southern Company, Segment(s) 1, 3, 5, 6, 3/27/2015

- 0 - 0

Essential Power supports the comments submitted by PJM regarding this proposed standard.

Gerry Adamski, 11/16/2015

- 0 - 0

The California ISO suggests that the drafting team consider removing the R5.3 requirement for interpersonal communications between the Balancing Authority (BA) and Distribution Provider (DP) since this relationship doesn’t always occur in practice.  In particular, in the ISO’s Balancing Authority Area communications with the Distribution Provider would occur through the Transmission Operator function, and as such there is no need for Interpersonal Communication between the BA and DP.

This same reasoning might apply to requirement R7.1 as well.

 

- 0 - 0

Texas RE is still concerned about the use of the term Transmission Operator Area (which appears in in R3.2, R3.3, R3.4, R4.2, and M4) and what that may introduce in terms of a responsible entity obligations.  Please see Texas RE’s comments submitted for the Initial Ballot of Project 2007-06.2.  While those requirements are not within the scope of this Standard Authorization Request, Texas RE is concerned there will be misunderstandings regarding the applicability of other requirements due to the use of the term.

Texas RE noticed the third bullet point in both Measure 12 (M12) and Measure 13 (M13) does not follow the same pattern as the previous two bullets. Texas RE recommends eliminating the third bullet in both M12 and M13 or, alternatively, move them into the language of the Requirements themselves. 

M12 lists types of evidence that a Reliability Coordinator, Transmission Operator, Generation Operator, and Balancing Authority “shall have and provide upon request,” including evidence of “physical assets” or “dated evidence, such as equipment specifications and installation documentation, operating procedures, test records, operator logs, voice recordings, transcripts of voice recordings, or electronic communications.”  M13 contains identical language regarding forms of evidence for Distribution Providers. 

In contrast to these evidentiary examples, the third bullet point in M12 and M13 does not list types of evidence necessary to demonstrate compliance.  Rather, it lists two examples, presumably taken from FERC Order No. 808, of situations in which internal Interpersonal Communication capability for the exchange of information could be necessary for the reliable operation of the Bulk Electric System (BES).  As such, it is confusing to include these elements in the list of evidence Registered Entities should retain to demonstrate compliance with Requirements 12 and 13. 

To address this, Texas RE recommends eliminating the third bullet point in M12 and M13.  In the alternative, the third point in these two measures should be moved to the text of Requirements 12 and 13, as well as clarified such that it refers to examples of situations in which adequate internal Interpersonal Communications are necessary for the reliable operation of the BES by revising it to read as follows: “Examples of situations in which the exchange of information could be necessary for the Reliable Operation of the BES include, but are not limited to, communications between geographically separate control centers within the same functional entity, or between a control center and field switching personnel.”

 

 

Rachel Coyne, Texas Reliability Entity, Inc., 10, 11/16/2015

- 0 - 0

Comments: ERCOT proposes the above revisions to the proposed requirements to ensure that there is clarity regarding the expectations and to allow those entities that are most familiar with their operating configuration to identify, determine, and establish the Interpersonal Communication capabilities that are most appropriate for its structure and operating characteristics.  Without clarity and the ability of entities to identify what communications capabilities best facilitate its operations, it is possible that significant cost and ongoing maintenance will be expended with little or no benefit to reliability.

Elizabeth Axson, 11/16/2015

- 0 - 0

Colorado Springs Utilities, Segment(s) 1, 6, 3, 5, 9/14/2015

- 0 - 0

Andrew Pusztai, 11/16/2015

- 0 - 0