Connect a load requirement to equipment and delivery
Create a source-backed requirement, assign an owner and retain its equipment and stage associations.
Current Revision 2 Reviewed Oct 25, 2026
On this page
Before you beginHypothetical synthetic planning exampleInputs and terminologyProcedureVerify the resultWhat happens nextTroubleshootingBefore you begin#
- Project record-write permission; separate review permission for review dispositions.
- A recorded committed-load or scenario-input assumption with its value, unit and source evidence.
Hypothetical synthetic planning example#
For an illustrative Facility A / Phase 1 / 2027 basis, record a 2 MW real-power requirement and one compatible, in-period confirmed supply row of 1.5 MW. With all listed inputs supported, the recorded arithmetic leaves 0.5 MW unresolved. A committed-load assumption describes demand; it is not confirmed available supply. Adding an assumed/requested supply row or a missing/incompatible value makes the conservative aggregate unknown rather than silently adding a partial total. This exercise is not an electrical capacity approval.
Inputs and terminology#
| Term | Meaning |
|---|---|
| Requirement | A coordination record connecting a stated load need, needed-by date, accountable owner, equipment and delivery stages. |
| Coordination complete | A recorded coordination outcome. It does not certify capacity or physical readiness. |
Procedure#
Create the requirement
Open Power Planning → Requirements → Add requirement.
Enter the requirement name and optional phase, select the recorded load assumption, then set the needed-by date and owner. Save the record.
Add the delivery associations
Open the requirement and link the authorized equipment and delivery stages. Inspect the business identifiers rather than guessing internal IDs.
Check the coverage and issues beside each association; a linked record may still be retired, blocked, late or awaiting source review.
Record the coordination outcome
Review the load and retained sources with the appropriate reviewer. Record the outcome and rationale.
If completion prerequisites are unresolved, keep the requirement open and assign the missing work. Recheck the coverage after changes.
Verify the result#
The requirement retains its load association, owner, needed-by date, linked records and revision history. Open issues remain visible.
What happens next#
Associations track coordination; they do not calculate usable supply or satisfy engineering authorization.