Understanding the Roles of Power-System Compliance Documents

Hello. In the previous lesson, you mapped interconnection from initial site screening through studies, agreements, commissioning, and model acceptance. This lesson adds the rulebook: when a study scope, model-data request, or upgrade recommendation cites a document, you need to know what kind of document it is, who it binds, and whether it controls the decision at hand.

That distinction is essential for independent work. A requirement to run an N-1 contingency, submit a dynamic model, install a breaker upgrade, or perform model-quality testing may sound equally mandatory in an email. Its actual authority can be quite different.

---

One project, several layers of authority

An interconnection is governed by a network of documents, not one universal hierarchy. The same technical subject—say, voltage ride-through—can appear in a federal reform order, a NERC standard, an ISO procedure, a transmission-owner technical specification, a study agreement, and an OEM model manual. Those documents do different jobs.

The practical question is therefore not merely, “What does the document say?” It is:

1. Who issued it and under what authority?
2. Who must comply?
3. Does it apply to this region, project type, voltage level, and process stage?
4. Is it a binding requirement, an implementation procedure, or engineering guidance?
5. Has it been incorporated into a tariff, agreement, or study scope?
6. Which revision was effective when the study or agreement was executed?

The following map is a useful starting point.

Document family	Main role	Typical engineering consequence	Key caution
FERC orders and process documents	Direct FERC-jurisdictional transmission providers to establish compliant interconnection processes and agreements	Explains why a provider must use a cluster process, readiness milestones, affected-system coordination, or particular interconnection provisions	The order is often implemented through a provider’s FERC-approved tariff; do not substitute an order’s general language for the current regional tariff
NERC Reliability Standards	Establish mandatory North American reliability obligations for applicable registered entities and functions	Drives planning, operating, protection, modeling, and disturbance-performance obligations	A developer may not itself be the directly registered entity, but obligations commonly reach the project through the transmission provider and agreement
Regional criteria and regional standards	Apply regional reliability interpretation, performance criteria, or approved variations	May define study assumptions, contingencies, voltage criteria, or performance expectations in a region such as WECC	“Regional” does not automatically mean advisory; identify the exact document and its binding status
ISO/RTO tariffs, protocols, and guides	Convert regulatory obligations into the region’s active process: queue rules, studies, data submissions, timelines, and operating requirements	Determines what a project must submit and how an interconnection study is run in SPP, ERCOT, or another region	A tariff, protocol, guide, and training presentation do not carry identical authority
Transmission-owner requirements	Specify the utility’s facilities, protection, communications, metering, design, and operating requirements	Can determine GSU connections, breaker ratings, relay schemes, SCADA points, or commissioning evidence	Check whether the requirement is tariff-based, agreement-based, formally adopted, or a requested design preference
Project-specific agreements	Bind the identified parties to the project definition, scope, cost responsibility, milestones, operating conditions, and facility configuration	Establishes the project’s particular obligations, including limits or mitigation commitments	An agreement cannot casually override mandatory reliability or regulatory requirements

A single requirement can therefore have more than one foundation. For example, a transmission provider may require dynamic models because it must plan reliably under NERC-related obligations; its tariff and procedural manual define the submission process; a study agreement identifies the project data due date; and the executed interconnection agreement may require the final as-built model.

---

FERC: federal process reform, then regional implementation

For most interstate transmission providers, FERC regulates the tariff framework that governs generator interconnection. FERC orders establish or revise the federal requirements that those providers must implement. They are not usually the daily checklist you use to submit a PSS®E case.

FERC Order No. 2023 is an important example. It reformed generator-interconnection processes by requiring cluster-study approaches, strengthening readiness requirements, addressing affected-system coordination, and improving treatment of newer resource configurations such as co-located resources. The operational details, however, appear in each transmission provider’s compliance implementation and tariff language.

The key distinction is:

• A FERC order establishes the regulatory direction for FERC-jurisdictional providers.
• A provider’s FERC-approved tariff sets the operative regional process that an interconnection customer follows.
• A regional manual, business practice, or guide may explain that process or specify implementation details. Its authority depends on whether the tariff or agreement incorporates it.

For an SPP generator project, the immediate work is normally governed by the current SPP tariff, associated business practices, cluster materials, study agreements, and eventually the Generator Interconnection Agreement. FERC’s order remains important context, particularly when interpreting why the process is structured as it is, but it is not a substitute for reading the current SPP provisions.

ERCOT is a necessary jurisdictional contrast

ERCOT does not follow the standard FERC-jurisdictional RTO tariff pattern for its intrastate interconnection framework. Its planning and interconnection requirements are principally shaped by Texas law and PUCT oversight, together with ERCOT’s Protocols, Planning Guide, Operating Guides, and project agreements with the applicable transmission or distribution service provider.

This difference affects document reading. For an ERCOT project, you should not assume that an SPP or FERC process rule applies merely because the technical equipment is similar. A 300 MW BESS may use comparable inverter technology in Texas and Kansas, but its interconnection process, terminology, responsible organizations, and controlling documents differ.

---

NERC Standards: reliability obligations, not a project checklist alone

NERC Reliability Standards form the North American reliability baseline. They address functions such as transmission planning, operations, protection, modeling, and disturbance performance. They are enforceable for the registered entities and functions to which each standard applies.

That last phrase matters. A solar developer is often not itself the registered Transmission Planner, Planning Coordinator, Reliability Coordinator, or Transmission Owner responsible for direct compliance with every planning standard. But the project can still be required to provide data, models, testing evidence, operating limits, and facility modifications because the interconnecting entities need those items to meet their obligations.

Consider an N-1 study finding:

• A transmission planner may have a direct reliability obligation to assess system performance under specified contingencies.
• The ISO/RTO or transmission provider’s tariff defines the interconnection-study process that evaluates the project.
• The transmission owner may identify a facility modification needed on its system.
• The project’s study agreement controls the particular scope, assumptions, costs, and schedule.
• The final agreement may require the project to fund or operate subject to the resulting facilities or limits.

Thus, it is imprecise to tell a developer, “NERC requires you to build this upgrade,” unless the standard directly says so and applies directly. More commonly, the defensible statement is:

The transmission provider identified a reliability criterion applicable to its planning obligation. Under the governing interconnection process and project agreement, the proposed project must address the resulting project-related limitation before interconnection or operate under an accepted mitigation.

That wording preserves the chain from reliability requirement to project obligation.

Regional criteria add specificity

Regional organizations may add criteria, interpretations, procedures, or formally approved variations suited to their grid. In the West, WECC materials can be central to planning and model-performance expectations. In other areas, regional reliability and planning rules may be expressed through the ISO/RTO rather than a separate regional document.

Do not use “WECC criteria” as a vague citation. Record:

• the full title and revision;
• whether it is a NERC Reliability Standard with a regional variance, a regional criterion, a planning policy, or guidance;
• its stated applicability;
• the entity responsible for compliance;
• how it reaches the project, if it does.

This discipline becomes especially important when evaluating proposed upgrades. A claimed requirement may be mandatory, but the specific study assumption used to demonstrate the issue may still be open to technical review.

---

ISO/RTO guides and transmission-owner requirements: the operational layer

An ISO/RTO is typically the entity coordinating regional planning, market operations, and interconnection administration. A transmission owner owns and maintains particular lines, substations, breakers, and protection systems. Their documents often appear together in a project folder but answer different questions.

ISO/RTO documents

For a FERC-jurisdictional RTO such as SPP, separate these categories:

• Tariff: the formal governing process, including interconnection rights, milestones, study framework, deposits, withdrawal rules, and agreement forms.
• Business practices, manuals, and procedural guides: practical instructions for administering the tariff and submitting data. Some are explicitly incorporated by reference; others are explanatory.
• Planning criteria and study manuals: define technical methods, base cases, contingency assumptions, rating treatment, or reporting expectations.
• Study report and study agreement: apply the process to the named project, with identified assumptions and deliverables.

A procedure may contain highly specific details—file naming, data templates, dynamic-model compatibility, or deadlines. Specificity alone does not determine authority. The authority comes from its connection to a tariff, protocol, agreement, or binding procedure.

Transmission-owner requirements

The transmission owner or transmission service provider is often the technical gatekeeper for the physical POI. Its requirements may address:

• POI substation arrangement and breaker configuration;
• GSU transformer ratings, grounding, impedance, and tap range;
• protection philosophy, relay settings, communications, and transfer-trip logic;
• revenue metering and SCADA telemetry;
• grounding, insulation coordination, fault-duty limits, and equipment ratings;
• commissioning tests and operating procedures;
• utility-specific PSS®E, PSCAD, or model-validation expectations.

Some of these requirements are clearly binding because they are incorporated into an interconnection agreement, tariff, or utility standard. Others are preliminary preferences that can still be negotiated or technically challenged. A good engineer does not dismiss the latter—but records their status accurately.

If a utility asks for an EMT model, for example, determine whether that request is:

1. required by an applicable regional or tariff-based study procedure;
2. required by the study agreement for a defined technical concern;
3. a transmission-owner requirement tied to its facilities;
4. a prudent but non-mandatory recommendation; or
5. an OEM model-availability issue requiring resolution.

Those paths may lead to the same PSCAD work, but they lead to different reporting language, escalation routes, and contractual consequences.

---

Project agreements: where general rules become this project’s obligations

Project-specific agreements are not merely commercial paperwork. They turn general rules and study conclusions into obligations for named parties.

Common examples include:

• a feasibility, system-impact, or facilities study agreement;
• an SPP Generator Interconnection Agreement;
• an ERCOT Standard Generation Interconnection Agreement;
• construction, facilities, or reimbursement agreements;
• operating agreements, outage coordination protocols, and protection agreements;
• affected-system agreements.

These documents normally establish the project definition, POI, maximum MW or MVA, study scope, required facilities, cost allocation, schedule, financial security, operating limits, data responsibilities, confidentiality, and amendment process.

A project agreement is highly binding between its signatories, but it should be read alongside—not in isolation from—governing law, regulation, tariffs, protocols, and reliability requirements. It normally cannot authorize an operating condition that violates an applicable mandatory reliability obligation. Conversely, an agreement may impose project-specific duties beyond a generic regional minimum, such as a particular remedial-action-scheme interface or a restricted BESS charging schedule.

The ERCOT Planning Guide provides a clear example of an internal document hierarchy and of how requirements move from general planning rules into the project process. The edition supplied here is dated, so use it to understand the structure rather than as a current compliance determination; for live work, always retrieve the effective revision.

The excerpt also shows why a study scope matters. ERCOT’s Full Interconnection Study may include steady-state, stability, short-circuit, facilities, and other studies necessary to determine reliability impacts. Yet the particular study elements, base cases, scenarios, and assumptions are defined in the project’s FIS agreement. The broad rule tells you what may be needed; the scoped agreement tells you what will be done for this project.

---

A practical classification method for every requirement

When reviewing a data request, study report, or design comment, create a requirement entry before deciding whether to comply, seek clarification, or challenge the conclusion.

Field	What to record
Requirement statement	Exact wording, including “shall,” “must,” “should,” or recommendation language
Source	Full document title, revision, section, page, and URL or controlled-document location
Issuer	FERC, NERC, regional entity, ISO/RTO, transmission owner, or agreement party
Authority path	For example: FERC-approved tariff; NERC Standard; ERCOT Protocol; incorporated utility standard; executed agreement
Applicability	Region, project type, voltage level, MW threshold, registered-function applicability, and process stage
Responsible party	Developer, interconnection customer, TSP/TO, ISO/RTO, OEM, consultant, or more than one party
Technical evidence	Study case, contingency, model, calculation, test, or drawing that demonstrates the need
Status	Mandatory, conditional, contractual, requested pending basis, or advisory
Consequence	Study delay, model rejection, redesign, operating limit, upgrade cost, or commissioning restriction
Open issue	Missing citation, questionable assumption, alternative solution, or need for legal/senior review

This prevents a frequent failure mode: treating all requirements as equally fixed. In reality, a requirement can be:

• Mandatory and directly applicable, such as an explicitly applicable tariff milestone.
• Mandatory but indirect, where an interconnection customer must provide information so a registered entity can satisfy a reliability obligation.
• Contractual, because the signed agreement incorporates a facility or operating condition.
• Conditional, applying only above a threshold, at a particular POI, or when a study identifies a defined risk.
• Advisory, representing sound engineering practice but not an enforceable obligation.
• Unsupported, because the citation, applicability, or technical basis has not yet been demonstrated.

For future PSS®E and PSCAD work, this classification changes the quality of your deliverables. Instead of writing “the model passes required tests,” you will be able to write:

The model was tested against the applicable interconnection and dynamic-model procedure, revision identified in the requirements register. The test used the project-specific POI operating point and network equivalent specified in the study scope. Results satisfy the stated acceptance metric, subject to the documented assumptions and model-version limitations.

That is traceable engineering language rather than a generic claim.

---

Applying the distinction: a solar-plus-BESS example

Suppose a 250 MW solar-plus-BESS project seeks transmission interconnection in SPP.

A consultant receives five statements:

1. “The project must meet cluster-study readiness milestones.”
2. “The N-1 thermal study must consider specified planning contingencies.”
3. “Provide an RMS dynamic model and an EMT model.”
4. “Use breaker-and-a-half protection and utility-approved relay settings at the POI.”
5. “Limit BESS charging to 100 MW under a specified contingency until a remote upgrade is in service.”

These should not be treated as five equivalent sentences.

Statement	Likely source path to verify
Cluster readiness milestones	SPP tariff and current cluster process materials, shaped in part by FERC interconnection requirements
Planning contingencies	Applicable NERC reliability obligations, regional planning criteria, and SPP study criteria or scope
RMS and EMT models	SPP or transmission-owner model requirements, the study agreement, and the technical rationale for EMT analysis
POI protection design	Transmission-owner facility and protection requirements, incorporated design standards, and the interconnection agreement
Temporary BESS charging limit	Project-specific study result, mitigation agreement, and operating procedures; potentially a condition in the GIA or a related operating agreement

The fifth item is particularly revealing. A charging limit may be completely binding once included in an executed agreement or operating procedure, yet it is not a universal BESS standard. It must remain traceable to the limiting condition, study cases, and assumed network-upgrade schedule. If those assumptions change, the limit may need reevaluation.

For an ERCOT project, the same engineering issue would be classified through ERCOT’s Protocols, Planning Guide, applicable operating documents, TSP requirements, the FIS agreement, and SGIA. The technical calculation may still be performed in PSS®E, but the governing-document path is different.

---

Key takeaways

FERC orders shape interconnection reform for FERC-jurisdictional transmission providers, while current regional tariffs and approved implementation documents govern the operational process. ERCOT requires separate treatment because its interconnection framework is principally rooted in Texas and ERCOT governance rather than the usual FERC-jurisdictional RTO tariff model.

NERC Reliability Standards establish mandatory reliability obligations for applicable registered entities. A project developer’s duties often arise indirectly through the transmission provider’s interconnection process and directly through project agreements.

Regional criteria, ISO/RTO guides, and transmission-owner requirements supply the technical and procedural detail that general standards do not. Their authority depends on their stated applicability and whether they are incorporated into a tariff, protocol, study scope, or agreement.

Finally, a study agreement or interconnection agreement makes a general framework project-specific: it identifies the POI, scope, assumptions, facilities, costs, operating limits, and responsibilities. For every technical requirement, record its source, authority path, applicability, responsible party, and supporting evidence.

Next, you will use this document-awareness framework to choose among steady-state, short-circuit, RMS dynamic, and EMT analysis for a stated interconnection question—and justify why that analysis answers the governing requirement.