FAC-008-5 Facility Ratings

Building an Audit-Ready Engineering, Evidence, and Data Governance Program

An in-depth technical blog, compliance FAQ, and three anonymized composite case studies for Transmission Owners and Generator Owners

1: Executive Overview

FAC-008-5 - Facility Ratings is a core engineering governance standard for the reliable planning and operation of the Bulk Electric System. It applies to Generator Owners and Transmission Owners and is built around a simple but demanding principle: a Facility Rating must not exceed the most limiting applicable Equipment Rating of the equipment that comprises the Facility.

That principle sounds straightforward until it is applied across a real asset portfolio. A single Facility can include conductors, transformers, current transformers, circuit breakers, disconnect switches, wave traps, primary fuses, relay protective devices, terminal equipment, and compensation devices. The rating program must account for ownership boundaries, normal and emergency operating states, ambient conditions, temporary derates, field configuration, joint ownership, and the exact values used in planning and operations systems.

FAC-008-5 therefore operates as three connected control layers. Requirements R1, R2, and R3 establish the technical basis and documented methodology. Requirement R6 tests whether actual Facility Ratings remain consistent with that basis. Requirement R8 tests whether required rating and limiting-equipment information is provided to the appropriate reliability entities on the required schedule. Weakness in any layer can create audit exposure even when individual rating calculations appear technically reasonable.

Keentel Engineering supports registered entities by combining electrical engineering expertise, NERC compliance program design, audit-readiness services, and configurable compliance software. The objective is not merely to prepare a document for an audit. The objective is to build a sustainable Facility Ratings control environment in which rating decisions are reproducible, changes are governed, evidence is retained, and compliance information can be produced efficiently.

The audit-ready standard of performance

An auditor should be able to select a Facility, identify its ownership and rating boundary, trace the Facility Rating to each applicable Equipment Rating, confirm the limiting component, verify the values implemented in relevant systems, review approvals and changes, and locate any required R8 communications without relying on undocumented institutional knowledge.

2: Understanding FAC-008-5 and Why Facility Ratings Programs Fail

2.1: What FAC-008-5 is designed to accomplish

The stated purpose of FAC-008-5 is to ensure that Facility Ratings used in reliable BES planning and operation are determined using technically sound principles. Facility Ratings are essential inputs to System Operating Limits and influence transfer capability, outage analysis, generator deliverability, congestion management, and operating decisions.

The standard does not impose one universal calculation formula. For R2 and R3, the rating methodology may be based on manufacturer ratings or specifications, an industry standard developed through an open process, or a practice verified by testing, performance history, or engineering analysis. The entity must document the basis it uses and explain how standards, manufacturer information, ambient conditions, and operating limitations are considered.

2.2: Equipment Rating versus Facility Rating

An Equipment Rating describes the capability or operating limit of an individual component. A Facility Rating is the capability assigned to the Facility as a whole. The Facility Rating is constrained by the most limiting applicable component in the relevant electrical path and operating condition.

A conductor may have a higher thermal capability than the circuit breaker connected to it. A transformer may have a strong nameplate rating while a bushing, current transformer, disconnect switch, wave trap, or protection-related loadability limit is lower. A compliant process identifies the applicable equipment, determines valid Equipment Ratings, compares those ratings under the relevant normal or emergency condition, and assigns a Facility Rating that respects the limiting value.

2.3: Why rating programs fail despite having calculations

1: The methodology is incomplete and does not cover every equipment type that could limit the Facility

2: Ownership boundaries are unclear, particularly around the main step-up transformer, jointly owned switchyards, and interconnection equipment

3: The engineering method is documented, but the values loaded into EMS, planning, outage, or asset systems do not match the approved calculations

4: Normal and Emergency Ratings are stored as values without separately documented assumptions, durations, or calculation methods

5: Temporary derates are communicated operationally but are not consistently controlled, approved, retained, or reconciled

6: Terminal equipment and current transformers are excluded because the organization historically focused on conductors and transformers

7: R8 requests are handled through individual email accounts without a centralized due-date, response, or evidence-retention process

8: The entity cannot reconstruct why a rating changed, who approved it, or which systems were updated

Keentel Engineering perspective

The most effective FAC-008-5 programs treat Facility Ratings as a controlled engineering data lifecycle, not as a collection of calculation spreadsheets. The lifecycle begins with ownership and asset scope, continues through engineering determination and approval, and ends with implementation, communication, monitoring, and retained evidence.

3: Regulatory and Implementation Context

3.1: Transition from FAC-008-3 to FAC-008-5

FAC-008-5 resulted from the NERC Standards Efficiency Review effort. An earlier proposal would have retired both R7 and R8. FERC concluded that retirement of R7 would not create a reliability gap, but rejected retirement of R8 because identification and communication of limiting and next limiting equipment remained necessary for reliability. FAC-008-5 therefore retired R7 while retaining the R8 information-sharing obligations.

The implementation plan established a jurisdiction-specific transition in which FAC-008-5 would become effective on the first day of the first calendar quarter that is three months after applicable approval, unless an applicable authority provided otherwise. FAC-008-3 would retire immediately before FAC-008-5 became effective in the relevant jurisdiction.

3.2: Why the regulatory history matters to compliance teams

The regulatory history is important because it shows that R8 is not a minor administrative reporting provision. It is a reliability control intended to provide planners and operators with visibility into the current limiting equipment and the next constraint that would govern if the present bottleneck were removed or rerated.

For practical compliance, a registered entity should be able to determine whether an R8 request triggers only the scheduled information in R8.1 or also the 30-calendar-day next-limiting-equipment information in R8.2. The response process must connect compliance personnel, facility-rating engineers, asset data owners, planning personnel, and records management.

3.3: The RSAW as an audit lens

The FAC-008-5 RSAW converts the standard into an audit assessment workflow. It asks the entity to identify subject matter experts, provide a narrative compliance explanation, list evidence with document-level detail, and respond to requirement-specific applicability questions. The auditor sections emphasize clear assumptions, methodology completeness, limiting-equipment treatment, facility lists for sampling, and dated evidence of R8 requests and responses.

The RSAW also gives practical interpretation to equipment scope. For R2 and R3, the auditor note identifies wave traps, current transformers, disconnect switches, breakers, primary fuses, and any series-connected equipment that could have the most limiting rating as terminal equipment that should be addressed when owned by the entity.

Source basis: FAC-008-5 version history and requirements; Project 2018-03 Implementation Plan; FAC-008-5 RSAW regulatory language and audit approach.

4:The FAC-008-5 Compliance Operating Model

A sustainable FAC-008-5 program can be organized into three control layers supported by common governance. This model helps engineering, operations, planning, compliance, and information technology teams understand how their responsibilities connect.

4.1: Requirement applicability and risk map

4.2: Cross-functional ownership

1: Engineering owns the technical basis, assumptions, calculation methods, Equipment Ratings, limiting-equipment determination, and approval of Facility Ratings

2: Operations and planning own the correct use of approved values in operational and planning applications and the escalation of observed inconsistencies

3: Asset management owns accurate equipment attributes, ownership data, configuration records, and change notifications

4: Compliance owns requirement mapping, evidence strategy, retention, self-assessment, RSAW responses, and audit coordination

5: Information technology or application owners support controlled interfaces, role-based access, version history, and reporting

6: Management provides governance, resource prioritization, exception approval, and accountability for corrective actions

5: Requirement-by-Requirement Technical Compliance Guide

5.1: R1 - Generator Facility Rating Documentation

What R1 requires

R1 applies to a Generator Owner's solely and jointly owned generator Facilities. The applicable boundary depends on ownership of the main step-up transformer. When the Generator Owner does not own the main step-up transformer, R1 extends to the low-side terminals. When the Generator Owner owns the main step-up transformer, R1 extends to the high-side terminals.

The Generator Owner must maintain documentation containing the assumptions used to rate the generator and at least one qualifying technical basis. The basis may include design or construction information, manufacturer information, drawings, specifications, engineering analysis, industry-standard methods, verified engineering practice, commissioning tests, performance tests, or historical performance records. The documentation must also be consistent with the most-limiting-equipment principle.

Step-by-step implementation approach

1: Define the generator Facility and document the ownership boundary on an approved one-line diagram

2: Confirm whether the main step-up transformer is solely owned, jointly owned, or owned by another entity

3: Create a component inventory from the generator through the applicable low-side or high-side boundary

4: Document generator-rating assumptions, including operating configuration, auxiliary limitations, ambient basis, and performance constraints that are relevant to the selected method

5: Collect the technical source records supporting each applicable component rating

6: Determine the applicable Equipment Ratings for normal and other relevant operating conditions

7: Compare the component ratings and document the limiting equipment used to establish the Facility Rating

8: Obtain engineering review and approval and record the effective date and revision

9: Link the approved rating package to the facility master record and applicable operational or planning systems

10: Retain the current documentation and prior versions that were in force during the applicable audit period

Typical auditor questions

1: Who owns the main step-up transformer, and what evidence supports the ownership conclusion

2: How was the R1 boundary established and communicated to engineering and compliance personnel

3: What assumptions were used to determine the generator Facility Rating

4: Which manufacturer, design, construction, testing, performance, or engineering records support the rating

5: How does the entity demonstrate that the Facility Rating does not exceed the most limiting applicable Equipment Rating

6: How are jointly owned components addressed and how are rating changes coordinated with the other owner

Evidence package expected for R1

Evidence 1: Approved one-line diagrams and ownership records showing the generator and GSU boundary

Evidence 2: Generator Facility Rating calculation package and documented assumptions

Evidence 3: Manufacturer datasheets, nameplates, design drawings, specifications, and applicable engineering standards

Evidence 4: Commissioning tests, performance tests, historical operating records, or engineering analyses used as the technical basis

Evidence 5: Limiting-equipment comparison and approval record

Evidence 6: Revision history and evidence that the approved rating is implemented in relevant systems

Keentel Engineering service focus for R1

Keentel Engineering can perform generator ownership-boundary reviews, develop R1 rating documentation templates, evaluate supporting calculations and source records, create limiting-equipment matrices, and build audit-ready evidence indexes aligned to the RSAW.

Requirement basis: FAC-008-5 R1 and M1; RSAW R1 questions and compliance assessment approach.

5.2: R2 - Generator Owner Facility Ratings Methodology

What R2 requires

R2 applies when the Generator Owner owns equipment between the R1 generator boundary and the point of interconnection with the Transmission Owner. The Generator Owner must maintain a documented Facility Ratings methodology for its solely and jointly owned equipment in that portion of the interconnection.

The methodology must identify the technical basis used to establish Equipment Ratings, document underlying assumptions and design criteria, explain how standards, manufacturer information, ambient conditions, and operating limitations are considered, state that the Facility Rating respects the most limiting applicable Equipment Rating, and describe the rating determination process. The equipment scope must include conductors, transformers, relay protective devices, terminal equipment, and series and shunt compensation devices as applicable. Normal and Emergency Ratings must both be addressed.

Engineering scope that should not be overlooked

1: Conductors, including the thermal and physical assumptions used by the adopted rating practice

2: Transformers and associated components that may limit loading under normal or emergency conditions

3: Relay protective devices evaluated from the standpoint of safe loadability rather than merely the programmed trip setting

4: Terminal equipment, including wave traps, current transformers, disconnect switches, breakers, primary fuses, and other series-connected components that could limit the Facility

5: Series and shunt compensation devices and any associated equipment limitations relevant to the Facility

6: Normal Ratings and Emergency Ratings as separately supported rating classes

Step-by-step implementation approach

1: Confirm R2 applicability through an ownership and point-of-interconnection review

2: Define the Facility grouping and identify every GO-owned component between the R1 boundary and the TO connection

3: Establish equipment-specific rating methods using approved manufacturer information, open industry standards, or validated engineering practice

4: Document assumptions, design criteria, input data, and decision rules for each equipment category

5: Describe how ambient conditions are selected and applied, including seasonal, fixed, average, or real-time approaches used by the entity

6: Describe how operating limitations, impairments, and temporary derates are identified, approved, communicated, and removed

7: Define Normal and Emergency Rating methods, including any applicable duration, cooling state, recovery, or operator action assumptions

8: Document the process for comparing Equipment Ratings and selecting both the limiting and next limiting components

9: Require engineering approval and configuration control for methodology and rating changes

10: Test the methodology against representative Facilities and retain complete sample packages

Top real-world audit failure points

1: The methodology states that terminal equipment is considered but does not define a rating method for owned breakers, disconnects, current transformers, wave traps, or fuses

2: Ambient conditions are listed as an input but no values, sources, seasonal logic, or approval basis are documented

3: Emergency Ratings exist in a database but the methodology does not define how they are calculated separately from Normal Ratings

4: The relay section confuses protection settings with relay or protection-system loadability limitations

5: Joint ownership responsibilities are not clear and no process exists to reconcile rating changes with the other owner

6: The methodology is technically sound but is not followed consistently by individual calculation spreadsheets

Keentel Engineering service focus for R2

Keentel Engineering can develop or revise the Generator Owner Facility Ratings Methodology, establish equipment-category rating procedures, perform terminal-equipment and CT coverage reviews, define Normal and Emergency Rating governance, and create a repeatable calculation and evidence package for each interconnection Facility.

Requirement basis: FAC-008-5 R2 and M2; RSAW R2 audit approach and terminal-equipment notes.

5.3: R3 - Transmission Owner Facility Ratings Methodology

What R3 requires

R3 requires each Transmission Owner to maintain a documented Facility Ratings methodology for its solely and jointly owned Facilities, excluding the generating unit Facilities addressed under R1 and R2. The required methodology elements mirror the core R2 elements but apply across the transmission asset portfolio.

The Transmission Owner must document the technical basis for Equipment Ratings; the underlying assumptions, design criteria, and methods; the consideration of standards, manufacturer information, ambient conditions, and operating limitations; the most-limiting-equipment principle; the process used to determine ratings; the applicable equipment categories; and both Normal and Emergency Ratings.

Transmission engineering implementation considerations

1: Develop equipment-specific methods that are sufficiently detailed for engineers to reproduce ratings consistently across regions and asset classes

2: Use accurate field configuration and ownership data so the methodology is applied to the equipment that actually comprises the Facility

3: Evaluate actual field conditions where they may differ from design assumptions or manufacturer reference conditions

4: Address terminal equipment explicitly and define how missing manufacturer information, legacy equipment, or uncertain nameplates are resolved

5: Document treatment of seasonal ratings, emergency duration classes, temporary limitations, and restoration of normal capability

6: Establish a method for identifying the next limiting equipment so R8.2 responses can be produced without reconstructing the entire Facility under deadline

7: Coordinate jointly owned Facility Ratings and retain evidence of agreement, notification, or reconciliation

8: Link each Facility Rating to the applicable methodology revision and source calculations

Typical audit evidence

Evidence 1: Approved Transmission Facility Ratings Methodology and revision history

Evidence 2: Equipment-category procedures for conductors, transformers, relay protective devices, terminal equipment, and compensation devices

Evidence 3: Engineering standards, manufacturer records, testing information, and validated practices referenced by the methodology

Evidence 4: Representative calculation packages showing assumptions, Normal and Emergency Ratings, limiting equipment, and approvals

Evidence 5: Facility and equipment inventories, ownership records, and configuration diagrams

Evidence 6: Change-control records demonstrating that field modifications and reratings are incorporated into the program

Keentel Engineering service focus for R3

Keentel Engineering can perform a clause-by-clause methodology gap assessment, develop equipment-specific rating procedures, evaluate actual-field-condition controls, reconcile jointly owned Facilities, and validate representative transmission Facility Rating packages against the methodology and RSAW audit approach.

Requirement basis: FAC-008-5 R3 and M3; RSAW R3 audit approach; FERC discussion reproduced in the RSAW regarding actual field conditions.

5.4: R4, R5, and R7 - Reserved Requirements

R4, R5, and R7 are reserved in FAC-008-5. A registered entity should not create artificial compliance obligations for these reserved requirements. The compliance matrix, RSAW response, software configuration, and evidence index should identify them as reserved and exclude them from active evidence collection and testing.

1: Mark each reserved requirement accurately in the compliance register

2: Do not assign evidence owners, recurring tasks, or controls that imply an active obligation

3: Preserve version history showing that the current standard version was reviewed

4: Ensure automated dashboards do not report reserved requirements as overdue or incomplete

Requirement basis: FAC-008-5 R4, R5, and R7; RSAW reserved sections.

5.5: R6 - Consistency Between Methodology and Implemented Facility Ratings

Why R6 is the operational control

R6 requires each Transmission Owner and Generator Owner to have Facility Ratings for solely and jointly owned Facilities that are consistent with the associated documentation or methodology. R1, R2, and R3 can be complete on paper while R6 still fails if the actual ratings used by planning or operations do not match the approved engineering basis.

The RSAW directs auditors to review the Facility Ratings and requests a list of all solely and jointly owned Transmission and Generation Facilities for data sampling. This makes R6 a portfolio-level configuration management requirement. The entity should expect auditors to select Facilities and trace values across calculations, equipment data, rating repositories, EMS, planning models, operating tools, and change records.

Step-by-step R6 control process

1: Maintain a complete facility master list with ownership, status, equipment membership, and applicable methodology

2: Record each Normal, Emergency, seasonal, and temporary rating with its unit, duration or condition, effective date, and source

3: Link the Facility Rating to the limiting Equipment Rating and retain the comparison used to establish the value

4: Identify every downstream system that consumes the rating and assign an accountable system owner

5: Use a controlled change workflow for new Facilities, modifications, equipment replacements, reratings, impairments, and restoration from derates

6: Reconcile the approved rating repository to EMS, planning, outage, and other relevant systems on a defined frequency

7: Investigate discrepancies, document the authoritative value, correct affected systems, and retain closure evidence

8: Perform periodic sampling using the same traceability test an auditor is likely to perform

Common R6 failure modes

1: A conductor or transformer was replaced but the Facility Rating was not reassessed across all components

2: A temporary derate was applied in operations but was not reflected in the compliance rating record or was not removed after restoration

3: Planning and EMS values differ because each system was updated by a separate manual process

4: The limiting equipment changed after a modification, but the Facility master record still identifies the previous component

5: Joint owners use different ratings or effective dates for the same Facility

6: Emergency ratings exceed the methodology because legacy database values were never revalidated

Keentel Engineering service focus for R6

Keentel Engineering can perform Facility Rating data reconciliation, design source-of-truth controls, validate sampled Facilities, establish change-management workflows, review temporary derates, and configure exception dashboards that identify inconsistencies before an audit or operational event exposes them.

Requirement basis: FAC-008-5 R6 and M6; RSAW R6 sampling approach; FAC-008-5 evidence-retention provisions.

5.6: R8 - Providing Facility Ratings and Limiting-Equipment Information

What R8 requires

R8 applies to each Transmission Owner and each Generator Owner subject to R2. For existing Facilities, new Facilities, modifications, and reratings, the entity must provide requested information to its associated Reliability Coordinators, Planning Coordinators, Transmission Planners, Transmission Owners, and Transmission Operators.

Under R8.1, the entity provides Facility Ratings and the identity of the most limiting equipment as scheduled by the requesting entity. Under R8.2, the entity must provide the identity and Thermal Rating of the existing next most limiting equipment within 30 calendar days, or a later date specified by the requester, when the requested Facility's Thermal Rating causes one of the four listed reliability or service limitations.

The four R8.2 trigger conditions

1: The Facility causes an Interconnection Reliability Operating Limit

2: The Facility limits Total Transfer Capability

3: The Facility impedes generator deliverability

4: The Facility impedes service to a major load center

Step-by-step R8 response workflow

1: Log the request immediately with the requester, Facilities, information requested, received date, required schedule, and responsible owner

2: Confirm that the requester is an associated entity identified by R8 and determine whether the entity is responding as a TO or a GO subject to R2

3: Validate the current approved Facility Rating and most limiting equipment against the authoritative rating record

4: Determine whether any Facility in the request meets an R8.2 trigger condition

5: When R8.2 applies, identify the existing next most limiting equipment and its Thermal Rating using the approved engineering record

6: Perform an independent technical and compliance quality review before release

7: Transmit the response by the requester's schedule or the applicable 30-calendar-day deadline

8: Retain the request, technical support, approvals, response, attachments, and proof of delivery in a centralized evidence record

9: Track follow-up questions and amended responses as part of the same request history

R8 evidence expected by auditors

Evidence 1: Dated request from the RC, PC, TP, TO, or TOP, including the requested schedule

Evidence 2: Dated response containing the Facility Rating and most limiting equipment

Evidence 3: R8.2 applicability determination and, when applicable, the next limiting equipment and Thermal Rating

Evidence 4: Engineering validation and approval records

Evidence 5: Proof of delivery and any follow-up communications

Evidence 6: Request log demonstrating completeness, status, due dates, and retention

Keentel Engineering service focus for R8

Keentel Engineering can develop the R8 procedure, roles and responsibilities, trigger-assessment checklist, response templates, quality-review workflow, and centralized request tracker. Compliance software can automate due dates, escalation, evidence capture, and audit reporting.

6: Engineering Considerations for Limiting Equipment and Ratings

FAC-008-5 deliberately allows different technical rating approaches, but the entity must use them consistently and document the assumptions that make the result valid. The following engineering topics are common control points. The exact method and parameters remain entity-specific and should be approved in the Facility Ratings methodology.

6.1: Conductors

A conductor rating process should define the adopted thermal or performance method, input data sources, ambient assumptions, physical configuration, and field-condition validation. Typical engineering considerations may include ambient temperature, solar heating, wind assumptions, conductor material and size, emissivity, absorptivity, connections, sag and clearance constraints, and whether the entity uses fixed, seasonal, or real-time ratings. FAC-008-5 does not require one specific calculation standard, but it does require a documented and technically supported approach.

6.2: Transformers and associated components

Transformer capability is not always limited by the main tank nameplate. A rating review may need to consider cooling class, fan or pump availability, temperature-rise assumptions, emergency duration, bushings, leads, LTC or DETC position, cable or bus connections, tertiary loading, auxiliary-system status, manufacturer limitations, and operating history. The Facility Rating should reflect the applicable limiting component under the relevant condition.

6.3: Terminal equipment

The RSAW directs auditors to focus on series-connected equipment that could establish the most limiting Equipment Rating. The noted terminal-equipment examples include wave traps, current transformers, disconnect switches, breakers, and primary fuses. An effective methodology defines how each owned equipment type is rated, how source data is validated, and what happens when reliable manufacturer information is unavailable.

Audit risk

A methodology that merely states that terminal equipment is considered may not be persuasive if the entity cannot show an equipment-specific method, source data, and sample calculations for the terminal equipment it owns.

6.4: Current transformers

Current transformers deserve explicit treatment because they can be overlooked as protection-system components rather than evaluated as potentially limiting equipment. The RSAW permits a current transformer associated with a Protection System to be addressed under relay protective devices, terminal equipment, or both, depending on the methodology. Regardless of classification, all current transformers that could limit the Equipment Rating must be addressed.

6.5: Relay protective devices

The RSAW distinguishes relay loadability from a relay trip setting. For FAC-008-5 purposes, the relevant consideration is the loadability threshold at which the relay can safely operate without risking relay failure. The programmed trip setting is not automatically the Facility Rating. It becomes relevant when it is the actual limiting factor for the Facility. The methodology should clearly distinguish thermal equipment capability, protection settings, relay hardware capability, and any loadability analysis used to support the rating.

6.6: Series and shunt compensation devices

R2 and R3 require the methodology scope to include series and shunt compensation devices. The entity should document the equipment included, the rating basis, relevant bypass or protection states, auxiliary limitations, and the manner in which the devices affect the Facility grouping and limiting-equipment determination.

6.7: Normal and Emergency Ratings

Normal and Emergency Ratings must both be addressed as a minimum. A defensible methodology treats them as separate rating determinations rather than a single value with an informal multiplier. Emergency-rating documentation should define the conditions that permit the higher loading, the allowable duration or class, required cooling or operating state, temperature or aging assumptions where applicable, operator actions, and the recovery or post-event expectations that support the rating.

6.8: Ambient conditions and actual field conditions

The methodology must identify how ambient conditions are considered. It may use particular conditions, average conditions, seasonal values, or values that vary in real time. The RSAW's regulatory language also highlights the importance of actual field conditions when relying on design or nameplate information. The entity should therefore have a process for identifying field changes or discrepancies that could invalidate the original rating assumptions.

6.9: Operating limitations and temporary derates

Operating limitations include temporary deratings of impaired equipment and other conditions that reduce capability. A mature process defines who can initiate a derate, how the value is technically determined, which systems must be updated, how affected parties are notified, how the limitation is periodically reviewed, and what evidence is required before the normal rating is restored.

6.10: Jointly owned Facilities

Sole and joint ownership are explicitly within the scope of FAC-008-5. Joint ownership should be managed through clear equipment responsibility, rating authority, change notification, data exchange, and discrepancy-resolution controls. A joint owner should not assume that another party's rating record automatically satisfies its own evidence obligations. Each registered entity should be able to demonstrate how it fulfills the requirement applicable to its ownership and function.

7: Audit Evidence, Retention, and Internal Controls

7.1: Build evidence around the auditor's traceability path

An effective evidence package is organized so that an auditor can follow the rating decision from requirement applicability to implemented value. Uploading a large document repository without a cross-reference often increases audit effort and creates unnecessary follow-up questions. Keentel Engineering recommends a requirement-specific evidence index with precise file, revision, date, page, section, and description fields, consistent with the RSAW structure.

7.2: Evidence retention periods

1: For R1, the Generator Owner retains the current documentation and modifications that were in force since the last compliance audit period

2: For R2, the Generator Owner retains the current methodology and modifications that were in force since the last compliance audit period

3: For R3, the Transmission Owner retains the current methodology and modifications that were in force since the last compliance audit

4: For R6, the Transmission Owner and Generator Owner retain current Facility Ratings and changes to those ratings for three calendar years

5: For R8, the applicable Transmission Owner and Generator Owner retain evidence for three calendar years

6: When an entity is found noncompliant, information related to the noncompliance is retained until the entity is found compliant

The Compliance Enforcement Authority may request evidence covering the full period since the last audit when the stated retention period is shorter. Records management should therefore coordinate retention schedules with the entity's audit cycle and any investigation or preservation notice.

7.3: Internal audit testing model

1: Select a risk-based sample that includes different voltage classes, equipment types, ownership structures, recent modifications, temporary derates, and normal or emergency ratings

2: Verify the Facility boundary and ownership using approved diagrams and asset records

3: Recalculate or independently check the limiting Equipment Rating using the applicable methodology revision

4: Compare the approved Facility Rating with each relevant operational and planning system

5: Review change history and confirm that field modifications triggered a rating review

6: For R8, select requests and verify schedule, completeness, technical accuracy, response date, and proof of delivery

7: Record exceptions, assign corrective actions, verify closure, and retain the test package as evidence of ongoing monitoring

Audit preparation principle

The most persuasive evidence is contemporaneous evidence generated by a controlled process. A narrative created immediately before an audit cannot substitute for missing engineering approvals, source calculations, system records, or dated communications.

8: Keentel Engineering FAC-008-5 Compliance Services

Keentel Engineering provides FAC-008-5 services that connect the technical engineering basis with the NERC compliance controls needed for sustainable audit readiness. Engagements can focus on one requirement, one asset class, or the full Facility Ratings lifecycle.

1: Applicability and ownership boundary assessment - Review GO and TO registration applicability, generator and GSU boundaries, point-of-interconnection ownership, jointly owned Facilities, and responsibility for rating evidence

2: FAC-008-5 methodology gap assessment - Perform a clause-by-clause review of R1, R2, R3, R6, and R8 against the standard, implementation context, RSAW, internal procedures, and representative evidence

3: Facility Ratings Methodology development - Develop or revise generator and transmission methodologies, equipment-category procedures, assumptions, normal and emergency rating methods, limiting-equipment logic, and change controls

4: Engineering calculation and evidence validation - Review source records, calculations, terminal equipment, CTs, relay loadability, ambient assumptions, operating limitations, limiting equipment, and next limiting equipment

5: R6 data reconciliation - Compare approved engineering values across Facility Rating repositories, EMS, planning models, outage tools, operational databases, and joint-owner records

6: R8 workflow and response readiness - Create request intake, trigger assessment, due-date management, technical review, response templates, proof-of-delivery, and retention controls

7: RSAW and audit readiness support - Prepare compliance narratives, evidence indexes, sampled Facility packages, SME interview preparation, mock audit questions, and audit response coordination

8: Corrective action and remediation - Prioritize gaps by compliance and reliability risk, establish interim controls, revise methods, correct data, document root causes, and verify sustained closure

9: Training and role-based workshops - Train engineering, operations, planning, asset management, compliance, and system owners using the entity's Facility Ratings process and evidence expectations

10: Ongoing compliance program support - Provide periodic sampling, change-control review, R8 evidence monitoring, management reporting, and preparation for self-certification, spot checks, and audits

8.1: Typical Keentel Engineering deliverables

Service objective



Keentel Engineering's role is to help the registered entity establish defensible engineering and compliance controls. Compliance determinations remain the responsibility of the applicable entity and Compliance Enforcement Authority, and no service or software tool can guarantee an audit result.

9: Keentel Engineering NERC Compliance Software for FAC-008-5

Spreadsheets and shared drives can support small, stable rating programs, but they become difficult to govern when Facilities, ratings, equipment, owners, and systems change. Keentel Engineering's NERC compliance software approach can be configured to centralize FAC-008-5 control activities and preserve the relationship between engineering decisions and compliance evidence.

9.1: Recommended software data relationships

1: One Facility record links to the applicable owner, function, boundary, and methodology revision

2: Each Facility links to all applicable equipment, not only the currently limiting component

3: Each equipment record links to its rating source, assumptions, rating classes, and approval history

4: Each Facility Rating links to the most limiting and next limiting equipment for the applicable condition

5: Each rating change links to the initiating event, calculations, approvals, affected systems, and verification

6: Each R8 response links to the rating data snapshot used at the time of the response

7: Each compliance requirement links to its evidence and retention rule

9.2: Software should support engineering, not replace it

Compliance software is a governance and traceability tool. It should not assign Facility Ratings without approved engineering logic and controlled source data. The most effective implementation embeds the entity's approved methodology, requires qualified engineering review for technical decisions, records exceptions, and prevents unauthorized or incomplete values from becoming the operational source of truth.

Keentel Engineering software implementation approach



A successful deployment begins with process and data design. Keentel Engineering can map the current workflow, define the Facility and equipment data model, configure requirement and evidence relationships, migrate controlled records, establish interfaces, test role-based workflows, and train users before the software becomes the compliance system of record.

10: A Practical FAC-008-5 Implementation Roadmap

1: Establish governance - Name the standard owner, engineering authority, system owners, R8 coordinator, records owner, and management sponsor

2: Confirm applicability and ownership - Map GO and TO functions, GSU boundaries, points of interconnection, joint ownership, and responsibilities

3: Build the Facility population - Create a controlled list of all solely and jointly owned Facilities and the equipment that comprises each Facility

4: Inventory existing methodologies and evidence - Identify approved documents, calculation tools, source records, system values, and known gaps

5: Develop or revise the FRM - Address every R2 or R3 methodology element and create the R1 documentation structure

6: Validate equipment methods - Review conductors, transformers, relays, terminal equipment, current transformers, compensation devices, ambient conditions, and operating limitations

7: Determine limiting and next limiting equipment - Create traceable comparison records for normal, emergency, seasonal, and relevant temporary conditions

8: Reconcile implemented ratings - Compare the approved rating to EMS, planning, outage, operations, asset, and joint-owner records

9: Control changes and derates - Implement workflows for new Facilities, modifications, reratings, impairments, temporary derates, and restoration

10: Implement the R8 process - Log requests, evaluate triggers, manage due dates, validate responses, and retain proof of delivery

11: Perform internal sampling - Test representative Facilities and R8 requests using the RSAW audit approach

12: Sustain the program - Use dashboards, periodic reviews, training, corrective actions, and management reporting to keep the program current

11: Three Anonymized Composite Case Studies

Anonymity and accuracy note

The following case studies are anonymized composite scenarios developed from recurring industry control conditions. They contain no client names, project names, locations, or identifying details and should not be interpreted as claims about a specific engagement.

11.1: Anonymized Case Study 1 - Generator Ownership Boundary and R1/R2 Documentation

Compliance setting: A Generator Owner operated multiple generating Facilities with mixed main step-up transformer ownership and GO-owned high-side equipment extending toward the Transmission Owner interconnection.

Initial condition: Engineering records existed, but the organization treated the generator, GSU, high-side breaker, disconnect switches, current transformers, and interconnection conductor as one undifferentiated rating package. The R1 boundary was not stated consistently, and the R2 methodology did not clearly identify which GO-owned equipment was within scope.

Primary compliance risk: An auditor could question whether the entity had complete R1 documentation for the correct generator boundary and a complete R2 methodology for the equipment between that boundary and the TO point of interconnection. Joint ownership records and GSU responsibility were difficult to locate.

Keentel Engineering approach

1: Reviewed approved one-line diagrams, interconnection agreements, asset records, and ownership documents to establish the boundary at each Facility

2: Created an ownership and applicability matrix showing which assets were addressed under R1, R2, or another owner's responsibility

3: Separated generator rating documentation from the interconnection-equipment methodology while preserving the electrical relationship between the two

4: Documented generator assumptions and collected manufacturer, design, performance, and engineering support for the generator Facility Rating

5: Expanded the R2 methodology to cover the GO-owned conductor, breaker, disconnect switch, CT, and other terminal equipment

6: Created a limiting-equipment comparison showing the Facility Rating and next limiting equipment by applicable rating condition

7: Configured an evidence index linking each Facility to ownership records, methodology revision, calculations, approvals, and system values

Resulting control environment

The entity obtained a repeatable boundary determination, a clear division between R1 documentation and R2 methodology, and a consistent evidence package that could be reproduced for an audit sample. Engineering and compliance personnel no longer relied on memory to determine whether the GSU or high-side equipment belonged in a particular requirement response.

The key lesson was that technical accuracy alone did not resolve compliance scope. Ownership, boundary, and requirement mapping had to be documented with the same discipline as the rating calculation.

11.2: Anonymized Case Study 2 - Transmission Terminal Equipment and R6 Data Consistency

Compliance setting: A Transmission Owner maintained established conductor and transformer rating methods across a broad transmission portfolio.

Initial condition: The approved methodology referenced terminal equipment generally, but equipment-specific methods were not consistently documented. Breaker, disconnect switch, wave trap, and CT records were distributed across drawings, legacy databases, and station files. Planning and operations systems contained rating values that had been updated at different times.

Primary compliance risk: The methodology could be viewed as incomplete under R3, and sample Facilities could fail R6 because the implemented rating or listed limiting equipment did not match the latest approved engineering determination.

Keentel Engineering approach

1: Performed a methodology gap review against each R3.1 through R3.4 element and the RSAW terminal-equipment audit notes

2: Developed an equipment coverage matrix showing owned terminal equipment and the rating method, source, and responsible engineering group for each type

3: Prioritized Facilities with recent modifications, legacy equipment, higher loading, or known system discrepancies

4: Collected source records for breakers, disconnects, CTs, wave traps, and primary fuses and documented an approved approach for missing or uncertain data

5: Reperformed limiting-equipment comparisons for representative Facilities, including normal and emergency conditions

6: Reconciled the approved results to the Facility Rating repository, EMS, and planning database

7: Established a change workflow requiring engineering approval, system-owner confirmation, and post-change verification

8: Configured exception reporting to identify mismatched ratings and missing limiting-equipment records

Resulting control environment

The Transmission Owner gained an explicit, auditable terminal-equipment methodology and a traceable record of how each sampled Facility Rating was determined. Rating mismatches were corrected through a controlled process, and future changes could not be closed until each required system confirmed the approved value.

The key lesson was that R3 methodology completeness and R6 implementation consistency must be addressed together. Updating the methodology without reconciling system values would have left the principal operational risk unresolved.

11.3: Anonymized Case Study 3 - R8 Request Management and Compliance Software

Compliance setting: An applicable entity received Facility Rating information requests from multiple planning and operating organizations through email and shared files.

Initial condition: Requests were tracked by individual employees. The entity could usually provide a Facility Rating, but the identity of the most limiting equipment was not always included, R8.2 trigger assessments were not documented, and next-limiting-equipment information required time-consuming manual research.

Primary compliance risk: The entity could miss a requester schedule or the 30-calendar-day R8.2 deadline, provide incomplete information, or be unable to show dated proof that each request was answered.

Keentel Engineering approach

1: Developed a centralized intake form capturing requester, role, Facilities, information requested, received date, requested schedule, and response owner

2: Created a trigger-assessment checklist for IROL, TTC, generator-deliverability, and major-load-center conditions

3: Established a standardized technical response package containing the approved Facility Rating, most limiting equipment, and R8.2 information when applicable

4: Configured software due dates, reminders, escalation, technical review, compliance approval, transmission, and proof-of-delivery steps

5: Linked each request to the authoritative Facility and equipment records so the response used the approved rating snapshot

6: Applied retention rules to the request, analysis, response, attachments, and follow-up communications

7: Created an audit report showing all requests, status, timeliness, response content, and supporting evidence

Resulting control environment

R8 requests became a controlled compliance workflow rather than an email-dependent activity. Engineering personnel could identify the current limiting and next limiting equipment more efficiently, compliance personnel could monitor deadlines, and the entity could produce a complete request-and-response history for audit review.



The key lesson was that R8 readiness depends on both engineering data quality and workflow discipline. A request tracker cannot correct weak Facility Rating data, and accurate data cannot prevent a missed deadline without an accountable process

12: Conclusion and Service Call to Action

FAC-008-5 is not simply a requirement to maintain a list of ratings. It is a requirement to maintain a controlled engineering and compliance system that explains how ratings are determined, proves that the most limiting applicable equipment has been respected, confirms that approved values are implemented consistently, and demonstrates that required information is communicated and retained.

The strongest programs integrate methodology, equipment data, Facility grouping, normal and emergency rating logic, change control, temporary derates, joint ownership, system reconciliation, R8 response management, and evidence retention. When those controls are fragmented, the entity spends valuable engineering time reconstructing decisions and remains exposed to audit findings and operational inconsistency.

Keentel Engineering helps Transmission Owners and Generator Owners convert FAC-008-5 obligations into a practical operating model. Our NERC compliance services combine technical Facility Ratings expertise with methodology development, audit readiness, data governance, corrective-action support, training, and configurable compliance software.

Engage Keentel Engineering



Contact Keentel Engineering to discuss a FAC-008-5 readiness assessment, Facility Ratings Methodology review, limiting-equipment validation, R6 data reconciliation, R8 workflow implementation, RSAW preparation, or NERC compliance software deployment.

13: Technical FAQ for FAC-008-5 Compliance