We are hiringCome build the future of the grid with us.Find your role

Modules · Modeling studies · Module 036

MOD-032-1 Modeling Data Package and Model Development

Steady-state, dynamics and short-circuit model data developed and submitted to the Planning Coordinator's specification.

About this module

What this module covers.

NERC MOD-032-1 requires Planning Coordinators (PC) and Transmission Planners (TP) to jointly develop steady-state, dynamics, and short-circuit modeling data requirements and reporting procedures. These requirements establish the specifications for providing models and modeling data by asset owners such as Transmission Owners (TOs), Generator Owners (GOs), etc. Each asset owner must provide this data according to the requirements developed by the PC and TP. As new inverter-based resource (IBR) projects become commercially operational, they must provide this data to the TP and PC in compliance with the rules established.

This module develops the models, or compiles the steady-state, dynamics and short-circuit model information, that the TP and PC require under MOD-032-1.

At a glance

Module: 036
Kind: Modeling studies
Governing body: NERC
Applies to: Before and after commercial operation
Typical time: Two to three weeks, all in, including your review

Dashboard capabilities

  • Model Workspace Management: your plant's simulation model files kept in one dashboard workspace, with version tracking

Support services

What GridStrong does inside this module.

Task 1: Model Requirements and Site Documentation Collection

  • Gather the TP and PC modeling requirements, per MOD-032-1, for the specific IBR plant.
  • Gather all IBR plant documentation and as-left settings as you supply them.
  • Coordinate with you and the applicable original equipment manufacturer(s) (OEMs) to gather and review all supplied site-specific models.
  • Support clarification and coordination with the OEM to gather necessary documentation and information for modeling purposes.

Task 2: PSS/E Model Development

  • Develop plant-level equivalent PSS/E standard library model that is an aggregate representation of the IBR plant using industry standard practices.
  • (If needed) Develop detailed PSS/E standard library model that provides details of each inverter, feeder, etc.
  • Configure the model(s) to represent the as-left/as-designed IBR plant configuration, impedances, controls, settings, etc.
  • NOTE: If user-defined models (UDMs) are required, they will incur additional costs but follow the same process, with UDM-specific modeling practices applied.

Task 3: PSCAD Model Development

  • Develop plant-level equivalent PSCAD model using industry standard practices.
  • (If needed) Develop detailed PSCAD model using industry standard practices.
  • Configure the model(s) to represent the as-left/as-designed IBR plant configuration, impedances, controls, settings, etc.
  • Note: If the PSCAD model provided by the OEM is generic (uses PSCAD standard library components), it is expected that the model response will deviate from the actual equipment performance.
  • Note: Model parameterization in Tasks 2 and 3 includes matching as-left/as-designed settings as you provide them.

Task 4: ASPEN Model Development

  • Develop plant-level equivalent ASPEN model using industry standard practices.
  • (If needed) Develop detailed ASPEN model using industry standard practices.
  • Configure the model(s) to represent the as-left/as-designed IBR plant configuration, impedances, controls, settings, etc.

Task 5: Model Compilation and Review Support (if models are already developed)

  • Gather the TP and PC modeling requirements, per MOD-032-1, for the specific IBR plant.
  • Gather all IBR plant documentation and as-left settings as you supply them.
  • Compare the as-left settings of site equipment with the models and identify any issues or discrepancies that must be addressed.
  • If specific models must be developed for the IBR plant, these can be considered on a case-by-case basis.

Final deliverables

  • Equivalent standard library model (PSS/E) (powerflow and dynamic)
  • Detailed standard library model (PSS/E) (powerflow and dynamic)
  • Equivalent UDM (PSS/E) (powerflow and dynamic)
  • Detailed UDM (PSS/E) (powerflow and dynamic)
  • Equivalent PSCAD model (project case file, other files necessary to run the case, and documentation)
  • Detailed PSCAD model (project case file, other files necessary to run the case, and documentation)
  • Plant-level aggregate ASPEN model (.olr file, associated model files)
  • Plant-level detailed ASPEN model (.olr file, associated model files)
  • Model documentation

What we need from you

  • You provide the IBR plant location, the applicable TP and PC, and the associated MOD-032-1 requirements for the site.
  • Single-line diagram of the facility including the inverters, generator step-up transformers (GSUs), main power transformer(s), shunt devices, and cable layout and lengths.
  • Impedances of the cables for each cable type used for collector system, impedance of GSUs, and main power transformer(s).
  • If main power transformer(s) includes an online tap changer, details of tap settings, tap size, regulated bus with deadband ranges.
  • Standard library and user-defined PSS/E dynamic models of the inverter, power plant controller, and dynamic reactive power devices provided by the OEM(s), as applicable.
  • PSCAD model(s) of the inverter, power plant controller, and any dynamic reactive power devices provided by the OEM(s). The inverter OEM should provide DC-side representation, which may include DC-DC converter(s).
  • User manuals, datasheets, documentation, and attestations including instructions for setting up and running the PSS/E and PSCAD models.
  • Inverter and generator short-circuit data (maximum fault current contribution and negative-sequence behavior) and positive, negative and zero sequence impedances of the transformers, collector system and gen-tie for the ASPEN model.

Assumptions and considerations

How the scope is bounded.

Run this module on one site.

Tell us the plant and the deadline. An engineer confirms the inputs, the schedule and what the Dashboard needs from you.