A Joint Registration Organization (JRO) is an agreement between two or more entities where one entity is taking full compliance responsibility for the other Parties of the agreement. To submit, at least one entity must already be registered and will serve as the Lead Entity. The Lead Entity will submit the request to register a Joint Registration Organization (JRO) associated with the Parties through the JRO page in CORES. New JROs and changes to existing JROs require Regional Entity and NERC approval before they can be activated. An entity registering as a JRO becomes the JRO Lead Entity. The JRO Lead Entity assumes compliance responsibility for the other Parties in the agreement and for the function(s) for which they are registering. The Parties or related entities named in the JRO agreement need not be registered entities with NERC and assume no compliance responsibilities, unless the written JRO Agreement states otherwise.
The Commission (FERC) believed that NERC’s proposal to allow a member within a central organization to separately register to be accountable for a particular reliability function so the responsibility for reliability functions can be split would provide flexibility and would not require an entity to assume responsibility where it is not possible to do so. In addition, NERC’s proposal adequately addressed concerns that a joint action agency should be allowed to achieve compliance at the joint action agency level. This "central organization" or Joint Registration Organization was born. The original vision or example of when this would likely be to the benefit of entities was in the instance of cooperatives. This category enables cooperatives and similar organizations to accept responsibility for the Reliability Standards on behalf of their members, and to make an appropriate allocation between affiliated companies of responsibilities for the different Reliability Standards. (Source: Order On Joint Registration Organization (JRO) Filing dated July 19, 2007)
Order No. 693 approved, pursuant to section 215 of the Federal Power Act (FPA), proposed Reliability Standards developed by NERC. In its comments to the NOPR, NERC outlined proposed procedures for an organization to accept compliance responsibility on behalf of its members. NERC stated that each “central” organization should be able to register as being responsible for compliance for itself and collectively on behalf of its members. Each member within a central organization may separately register to be accountable for a particular reliability function defined by the Reliability Standards. Under NERC’s proposal, if the central organization and a member organization cannot agree that one organization or the other is responsible, or if the parties agree that the responsibilities for a particular reliability function should be split, NERC would register both entities concurrently. NERC and the Regional Entities would then have the authority to find either organization or both accountable for a violation of a Reliability Standard, based on the facts of the case and circumstances surrounding the violation. Order No. 693 directed the ERO to file these procedures.
Requirements from NERC Rules of Procedure(Section 507)
In addition to registering as the entity responsible for all function type(s) that it performs itself, an entity may execute an agreement to register as a Lead Entity of a JRO on behalf of one or more parties to the agreement for one or more function type(s) for which such parties would otherwise be required to register. The Lead Entity thereby, accept on behalf of such parties all compliance responsibility for the function types(s) covered by the JRO registration, including all reporting requirements.
The Lead Entity of a JRO must execute a written agreement with the parties on whose behalf it registers that:
NOTE: CORES makes registration activities very easy compared to previous methods.
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|