Glenholme School (MOE 1724)

1. ✓1. School loadedthe engine2026-09-04
   what happens here, and what it needs

   The school’s Directory record comes in — address, roll, the recommended kW band, the key contact — and the flags that decide later steps are derived from the Ministry’s list. Closes when: The record is on the project. The engine closes this itself when the school is loaded.

   The tender pack names no document for this step.

2. ▶2. Site assessedPV Power2 documents to come
   The buildings are assessed from the record and the imagery: ownership and any waiver, asbestos, roof material and remaining life, works already under way. A building that cannot carry solar is excluded here, with its reason, and the exclusion stays on the record. Closes when: The site assessment is recorded for every building on the list.

   Documents this step expects

   • –Outline Plan (Appendix A)still to comeGuidance Document, Appendix A — Outline Plan Template — Or the waiver below, where the Ministry accepts one instead.
   • ·Outline Plan Waiver request (Appendix B)only where it appliesGuidance Document, Appendix B — Outline Plan Waiver Template — Instead of the Outline Plan, where a waiver is sought.
   • –Roof condition and material evidencestill to comeRequirements for installers, Pre-assessment — roof material, condition and remaining life — Photographs showing the roof material and its condition; asbestos or a roof needing replacement within ten years excludes the building.
3. ·3. Electrical capturedPV Power2 documents to come
   what happens here, and what it needs

   Every connection point is captured: the ICP or ICPs, single or three phase, the main board’s supply and breaker, spare capacity, the network’s export limit, and an inverter position pinned to the board it feeds. Closes when: The electrical record holds every board and every ICP the school has.

   Documents this step expects

   • –Solar Installation – Electrical Design (Appendix C)still to comeGuidance Document, Appendix C — Solar Installation Electrical Design Template
   • –Switchboard and distribution board photographsstill to comeRequirements for installers, Pre-assessment — confirmation of sufficient capacity at the switchboard
4. ·4. DesignedPV Power
   what happens here, and what it needs

   The array is laid on the design page over the laser scan, the strings are set inside the inverter’s window, and the Ministry’s roof rules are applied. The design page is one door away from here. Closes when: A design is saved with its panels, strings and inverter.

   The tender pack names no document for this step.

5. ·5. Cost–benefit runthe engine
   what happens here, and what it needs

   The half-hourly usage — the school’s own metering where it exists, the roll-based estimate where it does not — is laid against the design’s production over the occupied days, at the Ministry’s discount rate, to give self-consumption and the benefit. Closes when: The cost–benefit figures are on the record. The engine closes this itself.

   The tender pack names no document for this step.

6. ·6. Structural reviewPV Power1 document to come
   what happens here, and what it needs

   Where a trigger applies — an array over 40 m², a high wind zone, any tilt frame — a structural review is arranged and its finding recorded. Where no trigger applies the step is excluded with that reason. Closes when: The review is recorded, or the step is excluded with its reason.

   Documents this step expects

   • –Building Structure Inspection Report (Appendix D)still to comeGuidance Document, Appendix D — Building Structure Inspection Report Template — Where a Tier 1 trigger applies — an array over 40 m², or a wind zone above High.
   • ·Tier 2 Structural Review (Appendix E)only where it appliesGuidance Document, Appendix E — Tier 2 Structural Review Template — Only where a tilt frame is used.
7. ·7. Document packthe engine2 documents to come
   what happens here, and what it needs

   The Ministry’s appendices, the single-line diagram, the network application forms, the cable lengths, the string voltage proof and the equipment list are generated from the design and placed in the school’s file. Closes when: The pack is in the file. The engine closes this itself.

   Documents this step expects

   • –Single-line diagramstill to comeGuidance Document §2.4 — document pack
   • –Equipment list with make, model and capacitystill to comeRequirements for installers, Quotes — quantity, make, model and capacity of all key components
8. ·8. Ministry sign-offthe Ministry1 document to come
   what happens here, and what it needs

   The Ministry reads the design and the cost–benefit and signs the school off, or sends it back with what needs to change. Closes when: The Ministry’s sign-off is recorded.

   Documents this step expects

   • –The Ministry’s sign-off, in writingstill to comeEOI §3 — Ministry sign-off on design and CBA — The Ministry reads on this page; PV Power files what the Ministry sends.
9. ·9. Network applicationPV Power · statutory clock2 documents to come
   what happens here, and what it needs

   The distributed generation application goes to the lines company, batched with the other schools on that network. From the day it is lodged a clock set by law runs in business days, counted against this school’s anniversary calendar. Closes when: The application is lodged and its date recorded.

   Documents this step expects

   • –Distributed generation application to the lines companystill to comeRequirements for installers, Post-installation — a DG1 under 10 kW, or a DG2 and DG3 over 10 kW
   • –The lines company’s approval and connection contractstill to comeRequirements for installers, Post-installation — the EDB should have provided a connection contract
10. ·10. Handed to the installerPV Power
    what happens here, and what it needs

    The pack is released to the appointed installer, the school’s key contact is named to them, and the equipment list is confirmed. Closes when: The installer holds the pack and is a member of this school’s project.

    The tender pack names no document for this step.

11. ·11. Installer site visitthe installer2 documents to come
    what happens here, and what it needs

    The installer walks the site and signs the pre-assessment checklist the programme requires before any work. Closes when: The signed checklist is in the file.

    Documents this step expects

    • –Signed pre-assessmentstill to comeRequirements for installers, Pre-assessment — every factor assessed before works commence
    • –Itemised quote on the programme formstill to comeRequirements for installers, Quotes — a transparent, itemised full cost breakdown, with warranty information on all equipment — The pack requires the pre-assessment evidence to come with the quote.
12. ·12. Installedthe installer2 documents to come
    what happens here, and what it needs

    The install is scheduled, carried out and finished, and the as-built record — photos, serial numbers, what was fitted where — goes into the file. Closes when: The as-built record is in the file.

    Documents this step expects

    • –As-built drawingsstill to comeRequirements for installers, Post-installation — as-built drawings detailing the locations of key system components
    • –Photographs showing make, model and serial numbersstill to comeRequirements for installers, Post-installation — photographic evidence of the products installed
13. ·13. Commissioned and certifiedthe installer3 documents to come
    what happens here, and what it needs

    The system is commissioned and tested, the Certificate of Compliance and Electrical Safety Certificate are issued, and the evidence pack is lodged. Closes when: The certificates and the evidence pack are in the file.

    Documents this step expects

    • –Electrical Safety Certificatestill to comeRequirements for installers, Post-installation — a licensed electrician or inspector must provide an ESC
    • –Certificate of Compliancestill to comeRequirements for installers, Post-installation — a CoC and/or Record of Inspection
    • ·Record of Inspectiononly where it appliesRequirements for installers, Post-installation — a CoC and/or Record of Inspection — Where an inspection is carried out.
    • –Test documentation on the finished systemstill to comeRequirements for installers, Post-installation — test documentation on the ‘as installed’ performance
14. ·14. Handed overthe installer3 documents to come
    what happens here, and what it needs

    The handover pack goes to the school and the Ministry, with the manuals, the monitoring access and the maintenance schedule. Closes when: The handover pack is in the file.

    Documents this step expects

    • –Handover packstill to comeRequirements for installers, Post-installation — handover to the school, safe and fully commissioned
    • –Operational manuals and warranty certificatesstill to comeRequirements for installers, Post-installation — manuals, software passwords and warranty certificates passed to the school
    • –Maintenance schedule and aftersales contactsstill to comeRequirements for installers, Post-installation — user maintenance, ideally a maintenance schedule, and aftersales contact information

Everything the programme produces or the installer lodges lands here: the Ministry’s appendices, the single-line diagram, the network forms, the certificates and the handover pack. A document added against a step on the route appears here too — one file, two doors into it.

Nothing is in this school’s file yet.

Sign in to add a document or open one.

The spec sheets, warranties and certificates for the gear THIS design uses. They are filed once against the product, not against the school, so a newer revision reaches every school at once — and the one it replaced stays here, marked superseded, because the tender wants the trail.

No design is drawn on this school yet, so there is no hardware to list documents for.

For the CPEng structural review: the tier by the Ministry’s Guidance Document, the measured roof, the proposed array and its dead load, the engineer’s reference sheet and the Appendix D checklist pre-filled with what the desktop knows. Every figure states its basis; what is not held says so and is the site visit’s or the engineer’s.

No pack has been generated for this school yet.

Anything worth writing down about this school. Every seat sees every note, each one carries who wrote it and when, and nothing is ever deleted — a correction is another note.

Notes are for the seats on this school. Sign in to read and add them.

Sign in to add a note.