Ara Hills, Orewa development

Keep your delivery team. Simplify the network strategy.

Ara Hills, Orewa

01 / THE DEVELOPMENT

The development

A developer approached Halo with a medium-density terraced-housing development at Ara Hills, Ōrewa.

The developer already had an established civil and electrical delivery team working effectively across the project. Rather than requiring that team to be replaced, Halo structured the network pathway around the existing construction model.

This allowed the developer to retain control of the physical works while Halo took responsibility for the electricity-network strategy, establishment, acceptance and long-term operation.

02 / infrastructure challenge

The challenge

Residential development and electricity-network planning

The existing supply proposal included a large transformer and substantial boundary infrastructure on the roadside berm. The developer was concerned about the cost, physical impact and complexity of that solution and wanted to understand whether a more appropriate arrangement was available.

Halo reviewed the proposed supply capacity, likely development demand and boundary configuration. That assessment identified an opportunity to reduce unnecessary capacity and simplify the infrastructure required at the development boundary.

The original approach risked avoidable capital expenditure, additional coordination and oversized equipment occupying a prominent position beside the development.

02 / infrastructure challenge

The challenge

The existing supply proposal included a large transformer and substantial boundary infrastructure on the roadside berm. The developer was concerned about the cost, physical impact and complexity of that solution and wanted to understand whether a more appropriate arrangement was available.

Halo reviewed the proposed supply capacity, likely development demand and boundary configuration. That assessment identified an opportunity to reduce unnecessary capacity and simplify the infrastructure required at the development boundary.

The original approach risked avoidable capital expenditure, additional coordination and oversized equipment occupying a prominent position beside the development.

Residential development and electricity-network planning

03 / delivery model

The delivery

Halo developed a delivery structure that allowed the developer’s civil and electrical contractors to complete the internal physical works while Halo retained control of the network requirements, external interfaces and final acceptance process.

The developer’s team worked to Halo’s approved design, installation, testing and documentation requirements. Once the completed infrastructure had been inspected and the required certifications and as-built information supplied, Halo accepted the works into the Halo network.

Halo then assumed ownership and responsibility for the network’s ongoing operation, monitoring, maintenance and fault response.

Halo coordinated and retained responsibility for:
• Supply-capacity and network-strategy review
• Local network operator interface
• Point-of-supply and boundary infrastructure
• Gate-metering requirements
• Dwelling ICP establishment
• Registry and retailer-access requirements
• Design standards and documentation requirements
• Inspection and network acceptance
• Energisation coordination
• Long-term network ownership and operation

The developer’s contractors delivered:
• Civil trenching and ducting
• Internal LV reticulation
• Distribution cabinets and pillars
• Dwelling meter boxes and service connections
• Installation testing and electrical certification
• As-built drawings and completion documentation

04 / DEVELOPMENT OUTCOME

The outcome

Halo’s review enabled a simpler supply arrangement with lower infrastructure requirements at the development boundary.

The developer retained the civil and electrical teams already delivering the project, while Halo provided a clear pathway for network establishment, acceptance and long-term operation.

Lower upfront cost

Avoidable capacity and boundary infrastructure were removed from the proposed solution.


Simpler infrastructure

The boundary arrangement was reduced to a much simpler supply pillar, and better aligned with the development’s actual requirements.

Existing team retained

The developer’s established contractors continued delivering the internal civil and electrical works.

Long-term responsibility established

Following acceptance, Halo became the network owner and operator.


Lower upfront cost

Avoidable capacity and boundary infrastructure were removed from the proposed solution.


Simpler infrastructure

The boundary arrangement was reduced to a much simpler supply pillar, and better aligned with the development’s actual requirements.

Existing team retained

The developer’s established contractors continued delivering the internal civil and electrical works.

Long-term responsibility established

Following acceptance, Halo became the network owner and operator.


Planning something similar? Let’s review the electrical infrastructure early.

Halo can review the proposed supply, delivery structure and long-term network requirements before unnecessary cost or complexity becomes locked into the project.

Discuss a Development