NERC MOD-032-2 sets how Planning Coordinators collect steady-state, dynamic and short-circuit data from owners, including inverter-based resources, and MOD-033-3 sets how planners validate their system models against real behavior at least every 24 months. A plant owner supplies data in the format the planner defines.
Short answer
NERC MOD-032 and MOD-033 are the North American Electric Reliability Corporation (NERC) data and validation standards behind the system models that transmission planners use. MOD-032-2 says what data owners provide: steady-state, dynamic and short-circuit data. MOD-033-3 says how the Planning Coordinator checks the combined model against actual system behavior. The Federal Energy Regulatory Commission (FERC) approved both on 19 February 2026, as part of the same package as MOD-026-2.
The owner’s job is to deliver data in the planner’s format and keep it current. The wider framework is in the US electrical codes and grid interconnection guide. Verification of the plant’s own dynamic models is in the MOD-026 guide.
What MOD-032-2 asks
The Planning Coordinator (PC) and its Transmission Planners (TP) develop data requirements and reporting procedures. An attachment lists the data for near-term and long-term planning. The standard now asks for data on inverter-based resources (IBR), including those that are distributed energy resources (DER). The approval also added a NERC glossary definition of DER. Owners and other listed entities, such as Generator Owners and Transmission Owners, submit:
- steady-state data, such as impedances, ratings and generation capability;
- dynamic data, as standard library models, user-defined models or both;
- short-circuit data for fault studies.
If a planner needs a user-defined model description, the owner provides it on request. MOD-032-1 retires immediately before MOD-032-2 takes effect. Check NERC’s implementation plan for the dates that apply to your facility.
What MOD-033-3 asks
The PC validates its planning models at least once every 24 calendar months, under R1. The validation compares steady-state power flow results with actual system data, and dynamic simulation with recorded local events. Reliability Coordinators (RC) and Transmission Operators (TOP) provide the actual behavior data. MOD-033-3 replaces MOD-033-2.
For a plant owner this has an indirect effect. If your model does not match the events recorded at your plant, the planner will see it in the validation and ask you to correct it.
How the data flows
- Owner data. Steady-state, dynamic and short-circuit data in the planner's format
- Planner model. Planning Coordinator combines the data into the interconnection model
- Validation. Model compared with real system behavior every 24 months
- Correction. Owner updates the data where the comparison shows a mismatch
Per-unit data: the usual trap
Planners want data on a common base, usually 100 MVA for the system, while equipment is labeled on its own base. A base conversion error is an easy way to get a submission rejected. The guide on load flow studies shows where the base enters the calculation.
Worked example (illustrative)
The plant data below are illustrative assumptions.
Assumptions. A 34.5 kV collector system has an equivalent impedance of 2.1 + j5.8 ohms. The step-up transformer is rated 120 MVA with 8 percent impedance on its own base. The planner asks for data on a 100 MVA base.
Step 1. Base impedance of the collector. Z base = 34.5² ÷ 100 = 11.9025 ohms.
Step 2. Resistance in per unit. 2.1 ÷ 11.9025 = 0.1764 per unit.
Step 3. Reactance in per unit. 5.8 ÷ 11.9025 = 0.4873 per unit.
Step 4. Transformer to the new base. 0.08 × (100 ÷ 120) = 0.0667 per unit.
Step 5. Record it. The submission shows the collector as 0.1764 + j0.4873 per unit and the transformer as 0.0667 per unit, all on 100 MVA. A line stating the base prevents a later misreading.
Validation timing. If a planner completed a validation on 30 June 2026, the next one falls due no later than 30 June 2028 under the 24 month cycle.
Practical points for owners
Start with the planner’s procedure. Every Planning Coordinator publishes its own data requirements and templates. Two coordinators can ask for the same information in different forms, so a package prepared for one may not be accepted by another.
Name the base on every number. A value in per unit has no meaning without its base. Put the base MVA and base kV next to each table, and keep one conversion sheet for the project.
Describe the plant as it is. The planner needs the equivalent of the collector system, the main transformer, the reactive devices and the plant controller. A short single-line diagram that matches the data sheet avoids many questions.
Keep a revision log. Plants change. Inverters are replaced, collector circuits are extended and controllers get new firmware. Each change can alter the data the planner holds. Record what changed, the date and the version of the submission.
Do not wait for the validation cycle. MOD-033 puts the planner on a 24 month cycle, but a mismatch between your model and a recorded event is better found by you. Run your own comparison after significant events, using the same records the planner will use.
The load-flow side of the data is covered in our load flow guide, and the verification side in the MOD-026 guide.
Reading the result
A good submission can be read without the author in the room. The table of values states its base, the single-line diagram matches the table, and the version of the data is clear. When the planner returns a question, the answer should come from the record, not from memory.
Keep one engineer responsible for the submission and one place where the latest version lives. Two versions circulating at the same time delay the review, and the fix is simple: one owner, one folder, one revision log.
Checklist for the engineer
- Ask the Planning Coordinator for its MOD-032 data requirements and reporting procedure.
- Read the current MOD-032 and MOD-033 text and implementation plans on NERC’s site.
- Collect equipment data on its own base, then convert to the planner’s base.
- Confirm whether the planner accepts library models or needs user-defined ones.
- Include inverter-based resources and any distributed resources behind the point of interconnection.
- Keep a record of what you submitted and when.
- Compare your model against recorded events before the planner does.
- Resubmit after any equipment or control change.
Who signs and seals
In the United States, study and data packages are normally reviewed and sealed by a professional engineer licensed in the state of the project. Our work is delivered ready for your engineer of record to review and stamp. Tiza does not sign, seal or certify work in the United States. Compliance with a NERC standard stays with the registered entity; our studies support its analysis and evidence.
How Tiza can help
If your plant needs its model data compiled and converted to the planner’s format, Tiza provides power-system studies in English, ready for your engineer of record to review and stamp. Contact us with the equipment data and the planner’s procedure.
Frequently asked questions
Who defines what data a plant submits?
The Planning Coordinator, together with its Transmission Planners, defines the data requirements and reporting procedures under MOD-032-2. The plant owner submits to those procedures, so the first step is to ask the planner for them.
How often are system models validated?
Under MOD-033-3, Planning Coordinators validate their planning models against actual system behavior at least every 24 calendar months, using steady-state and dynamic comparisons.
Does the plant model need user-defined models?
It depends on the planner. Planners accept standard library models, user-defined models or both. If the planner's software library cannot represent your plant control, you may need to provide a user-defined model.