Understand the interface decision

A load reconnecting can immediately pull the system back below its shedding threshold. Without a coordinated recovery sequence, equipment can cycle repeatedly and disturb the electrical reference. Load priorities, minimum run times and process restrictions belong in the control design as well as the power balance.

Microgrid behavior must be reviewed as a coordinated system, including storage, generation, loads and auxiliary supplies. Capability at one port does not prove behavior in every operating mode. Confirm third-party equipment compatibility in the specific integration documents.

Put these inputs in the review record

Use a project-specific worksheet to capture the following information. For each entry, name the document, revision and person responsible for resolving any uncertainty.

• Load priorities and permitted interruption or restart conditions. Identify the exact configuration and the supporting document.
• The measured quantity used for shedding and reconnection. Keep the design assumptions visible in the project record.
• Separate trigger and recovery criteria with timing rules. Name the responsible reviewer and resolve any missing information.
• Source and storage behavior when several loads request reconnection. State how this entry will be verified during acceptance.

Define the acceptance boundary

Accept the strategy through defined declining-resource and recovery cases. Do not assume that every load can follow rapid wind changes. The control system should preserve any critical service and equipment-specific minimum cycling requirements.

The event record should show which load was shed, why, and when reconnection became permitted. This makes deliberate demand management distinguishable from an unexplained equipment outage or a failed start.