Grid application pack
Paperwork pre-filled from the design, with blanks the design cannot answer.
Reviewed
What this is for
The connection application, pre-filled from the design and the project. The claim is only worth making if a reader can see which fields were answered for them. Each line says where its value came from - derived, typed, typed over a derived one, or nothing yet. Fields nothing in the product can answer (the account number on the customer's bill, the property reference, the installer's registration, the commissioning date) are printed blank and marked required rather than quietly dropped.
What the project already knows goes straight onto the form: the customer's name, email and phone, the site's address and coordinates, its network and supply group, its phases and the rated capacity per phase from the Grid connection card, and the design's export limit. Fill those in on the project once and every pack picks them up.
This article calls it the grid application. The product's own name for the pack is the one this market uses.
Steps
- On Compliance, Start the grid application. That creates a pack and opens it. Do not invent a link; the list of packs on Compliance is the way in.
- The strip: how many fields were populated from the design, of how many there are, and how many are still outstanding (required, and no design can answer them). Zero outstanding is "nothing left to type".
- Where it has got to: the network the pack is addressed to, status, reference number, submitted on, decided on, decision notes, written by its own Save. Moving the status to submitted, awaiting approval or approved moves the project's own status with it, which is what the dashboard's awaiting-approval figure counts; a project already won or lost is left where it is. A viewer may read and print; they may not change it.
- Delete is offered on a draft only, and a submitted application cannot go back to draft. Once an application has been submitted it is the record of what the network was sent, so set its status to
Withdrawninstead, and start a new one if it is to be filed again. - The form itself: each field shows its value and a Source - from the design, typed, typed over, or not filled in. A star marks a field the network refuses the form without. A value is written when you leave its box. The production figures come from the newest simulation that still matches the design, and the field says which conditions it was run against; when every run predates a change to the array or its wiring, they stay blank until you simulate again. Below the form, the design's own Single-line diagram is attached, with Single-line PDF for a portal that wants the drawing as a file; an unwired design says there is nothing to attach, so generate the wiring before filing.
- Regenerate from the design refreshes derived fields. An overridden field keeps the design's value beside it. Regenerating never discards a correction, and never leaves one standing against a figure that has since moved without showing both.
- Out of date names every field the design or the project no longer agrees with - a changed phone number or export limit counts as much as a moved module. Regenerate before submitting, or the network reads an installation that is not being built.
- Print opens the application as an A4 document: the form on two sheets, the drawing on a landscape sheet, and a provenance line on every page. A required field nobody has answered prints as a line to complete by hand, and there is a line to sign and date. Print it, or save it as a PDF from the browser's print dialog. Filing portal is the network's own site, when one is published. The product does not file.
Tips and common mistakes
- Do not type a derived figure to "make it round". The beside-value is then a disagreement you have to explain.
- Outstanding blanks are the feature working. Filling them with a guess is how a pack goes out with a breaker nobody measured.
- Changing the design and sending the old pack is the stale banner. The old PDF still exists; it describes a different array.
- Regenerating a pack that has already been submitted updates your copy, not the one the network holds. If the network needs the corrected figures, it needs a new submission.
- Starting a pack needs a plan that includes connection-application packs; without one, Start is refused and names the plan that carries it. The compliance checks themselves are on every plan.