12.07.2015 Views

wembley-plan-app (small) , item 9. PDF 8 MB - Meetings, agendas ...

wembley-plan-app (small) , item 9. PDF 8 MB - Meetings, agendas ...

wembley-plan-app (small) , item 9. PDF 8 MB - Meetings, agendas ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Wembley Area Action Plan - Proposed Submission Version143Delivery and Monitoring 17Performance MeasureTargetMonitoring PointSpecific Policies to be MonitoredLocal Output Indicators:Provision for new or extended public openspace.To meet open space targets in growthareasWembley - 2.4ha.Measure new open spaces createdand laid out as a result ofdevelopment.When: AnnuallyCP7, CP8, CP9, CP11, CP12 andCP18New Tree Planting for new neighbourhoods.To meet tree <strong>plan</strong>ting targets in growtharea set out in IIF, by 2017Wembley 1,000.Count of new trees <strong>plan</strong>ted ingrowth areas.When: AnnuallyCP7, CP8, CP9, CP10, CP11 andCP12STRATEGIC OBJECTIVE 10Achieving Sustainable Development including mitigating and adapting to climate change - By promoting mixed use, mixed tenure development in growthareas integrating infrastructure and housing provision, reducing energy demand in the growth areas from current building regulation standards and by achievingexemplar low carbon schemes and CHP <strong>plan</strong>ts.Delivery Agencies: Brent Council, Greater London Authority (GLA), PCTPerformance MeasureTargetMonitoring PointSpecific Policies to be MonitoredLocal Output IndicatorsSecure district wide CHP in Wembley Area.Complete one CHP <strong>plan</strong>t.To meet GLA energy hierarchy on verylarge regeneration schemes.When: AnnuallyCP717.5 In addition, the council will monitor the following indicators which relate to policy / proposals which are specific to the Wembley AAP which are not coveredby indicators set out in the Core Strategy.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!