Unitywater Noosa Netserv Plan - Planning Assumptions · Attachment 1 - Draft Technical Note on Noosa Shire Netserv Plan Planning Assumptions

                                                        l   Noosa Netserv Plan Planning Assumptions June 2024




Within a DMaTT model, growth is automatically allocated to properties with the highest
development desirability index (DDI) until the aggregate of all property growth achieves set
population projections or GFA zone projections for each cohort year. For example, in early
cohort’s growth is allocated to properties with the highest DDI and in later cohort’s growth is
allocated to properties with the next highest DDI. The DDI is calculated at each projection
year and is continually variable to reflect changed conditions over time.

DMaTT development sequencing criteria within the BN considers:
     • Development influences:
            o Vacant land;
            o Ownership;
            o Property age;
            o Existing land use; and
            o Priority Infrastructure Area.
     • Proximity to development;
     • Approvals and applications:
            o Development approvals (MCU, RaL, building);
            o Connection approvals
            o Development applications; and
            o Infrastructure agreements.
     • Development margin;
     • SEQ Regional Plan Growth Monitoring Program Financial Feasibility Model
        (FFM);
     • Proximity to existing and future infrastructure
            o Water & sewer;
            o Local and main roads; and
            o Public transport.

Many of the above criteria relate to the ability to service with infrastructure (i.e. development
or connection approval, location within the PIA, PDA or structure planned area, proximity to
existing and planned infrastructure) whereby growth is allocated to properties with an ability
to service before other properties where possible.

To ensure robustness and transparency, the DDI score and individual node values for each
property are published within a GIS layer and included as part of the forecast model
documentation.

The configuration of each node is also set within the model website interface as shown
below in Figure 4.




                                                                                                       18