Skip to content
Storage and compliance

Grid-code compliance

Verdicts against the grid code, not a stamp from the market.

Reviewed

What this is for

What the grid code says about this design, before a proposal goes out. Nothing here refuses a design. A breach is reported at the severity the pack assigned it and the design remains a design. Discovering a threshold after quoting a timeline is the timeline.

Which code applies is a deployment fact. Only a check run says whether this design meets it. Building "compliant" from "this market requires registration" stamps the word on every export whether or not a single rule was evaluated.

Steps

  1. Open Compliance. The identity strip names the grid code. Pick the design, same control Electrical uses.
  2. Re-check runs every rule the pack ships. Start begins the grid application pack. Both write; viewers can read the verdicts.
  3. After a check:
    • Blocking must be resolved before filing. Typical blocking findings: the design has not been wired, so no AC limit can be measured; the site has not stated how many phases the connection has. A zero is drawn plain, not as a red zero.
    • Warnings are worth reading before quoting a timeline. The grid application not started is a warning, not a block. A warning still changes the application route.
    • Checks run and Checked against a layout version. A design nobody has checked yet draws the same strip with the counts absent.
  4. Out of date means the verdicts were evaluated against an older layout version than the design is at now. Re-check before relying on them.
  5. If the site names no network, export checks have nothing to measure against and those checks do not run. They are missing from the list rather than failed, and the warning above the strip that no network is chosen is the only place that says so - the count of checks run is short by them.
  6. The report footer on a production report prints one of five statements from this verdict, never from the market requiring registration. That is the provenance article.

Tips and common mistakes

  • A missing compliance line on a PDF is not a pass. Nothing printed means nothing was claimed.
  • No network chosen is not a failed export check. The notice says those checks did not run.
  • Blocking is not a louder warning. One refuses a filing; the other changes the application route.
Something went wrong. Reloading the page usually fixes it. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.