MOD-032-1

R1 · Set data requirements and reporting procedures (Planning Coordinator and Transmission Planner)

What it means. Each Planning Coordinator and its Transmission Planners jointly develop steady-state, dynamics and short circuit modeling data requirements and reporting procedures for the planning area. They include the data in Attachment 1; the data format, level of modeling detail, case types or scenarios, and a submission schedule of at least once every 13 calendar months, consistent with Interconnection-wide case building; and how the requirements are distributed or posted so data providers can get them.

Evidence an auditor expects. Evidence that the Planning Coordinator and Transmission Planner jointly developed the data requirements and reporting procedures.

R2 · Submit modeling data

What it means. Each Balancing Authority, Generator Owner, Load Serving Entity, Resource Planner, Transmission Owner and Transmission Service Provider provides steady-state, dynamics and short circuit modeling data to its Transmission Planners and Planning Coordinators according to the R1 requirements. For unchanged data, written confirmation that it has not changed is enough. Attachment 1 assigns the Generator Owner generating unit data (gross maximum and minimum real power, reactive power limits, station service auxiliary load, regulated bus and voltage set point, machine MVA base, generator step-up transformer data, generator type and in-service status), dynamics data (generator, excitation system, governor, power system stabilizer, wind turbine data, photovoltaic systems, and static var systems and FACTS), and short circuit data. Attachment 1 also obliges the Generator Owner to supply other information the Planning Coordinator or Transmission Planner requests as necessary for modeling. A user-written model submitted in place of a generic or library model must include block diagrams, the values and names of all parameters, and a list of all state variables.

Evidence an auditor expects. Evidence such as email records or postal receipts showing recipient and date that the data, or the written confirmation that it has not changed, was submitted to the Transmission Planners and Planning Coordinators.

R3 · Answer technical concerns about submitted data

What it means. When a Planning Coordinator or Transmission Planner gives written notice of technical concerns with submitted data, including the technical basis, the notified entity provides either updated data or an explanation with a technical basis for keeping the current data, within 90 calendar days of receipt unless a longer period is agreed.

Evidence an auditor expects. Evidence such as email records or postal receipts that the response went out within 90 calendar days or the agreed period, or a statement that no such notice was received.

R4 · Make models available to the ERO (Planning Coordinator)

What it means. Each Planning Coordinator makes models for its planning area, reflecting the data provided under R2, available to the ERO or its designee to support the Interconnection-wide cases.

Evidence an auditor expects. Evidence such as email records or postal receipts that the models were submitted when requested by the ERO or its designee.

For inverter-based plants

Attachment 1 already lists wind turbine data and photovoltaic systems as Generator Owner dynamics data, and MOD-032-2 adds data items specific to IBRs and DERs and lets the Planning Coordinator and Transmission Planner specify standard library models, user-defined models, or both.