Download - Spear
Download - Spear
Download - Spear
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
SPEAR<br />
Surveying and Planning through Electronic Applications and Referrals
Agenda<br />
1. Welcome<br />
2. SPEAR Subdivision Update<br />
3. SPEAR Planning Update<br />
4. Street Addressing Updates<br />
- Rob Morrison, Information Services Division<br />
- Rafe Benli, Office of Geographic Names<br />
5. SPEAR IT<br />
- PE List<br />
- Release 3.4 – Content<br />
- Release 3.5/3.6 – Proposed<br />
6. Morning Tea
Agenda: Group Session<br />
Applicants, Councils and Referral Authorities<br />
7. Group Session – Topics<br />
- Changes to Planning and Environment Act and impact on planning permit process<br />
(by Paula O’Byrne, Planning and Building Systems, DTPLI)<br />
- Changes to Referral Process (Planning and Environment Act)<br />
- Lapsing Applications<br />
- Endorsing Plans<br />
- Renaming Secondary Consents<br />
- Planning Report<br />
- Application ‘On Hold’<br />
- Guest Access<br />
- Subdivision Changes Regarding Telecommunication Services<br />
- Form 1<br />
- A-SPEC discussion<br />
- Owners Corporation Data (in XLS)<br />
- SPEAR Payments<br />
- SMES Upgrade
Agenda: Group Session<br />
Applicants, Councils and Referral Authorities<br />
8. Training/Service Desk Update<br />
- Compatibility View<br />
- Password Storage in SPEAR<br />
- Conditions for SOC<br />
- System Errors<br />
- Paper Correspondence<br />
9. User Issues<br />
10. Light Lunch
SPEAR Subdivision Update
SPEAR Subdivision Update<br />
SPEAR Subdivision Sign-up Progress<br />
• 77 councils signed up (with 75 operational)<br />
and the other 2 expressing interest<br />
– 10 Certification Only Councils<br />
– 12 SPEAR Payments Councils<br />
• 145 surveying firms (with 299 licensed surveyors)<br />
• 53 Referral Authorities<br />
• Nearly 3,300 SPEAR Subdivision users
SPEAR SUBDIVISION - MUNICIPALITY STATUS<br />
MILDURA *<br />
SWAN HILL<br />
HINDMARSH<br />
YARRIAMBIACK<br />
BULOKE<br />
GANNAWARRA<br />
MOIRA<br />
WANGARATTA<br />
WODONGA<br />
WEST<br />
WIMMERA<br />
GLENELG<br />
LODDON CAMPASPE * GREATER<br />
INDIGO<br />
SHEPPARTON BENALLA<br />
CENTRAL<br />
$<br />
GOLDFIELDS<br />
NORTHERN<br />
GREATER<br />
HORSHAM<br />
GRAMPIANS<br />
BENDIGO<br />
STRATHBOGIE<br />
ALPINE<br />
$<br />
MOUNT<br />
PYRENEES ALEXANDER * MITCHELL<br />
$<br />
MANSFIELD<br />
HEPBURN<br />
MACEDON<br />
RANGES<br />
MURRINDINDI *<br />
SOUTHERN<br />
ARARAT BALLARAT<br />
MOORABOOL<br />
GRAMPIANS<br />
YARRA RANGES *<br />
GOLDEN<br />
WELLINGTON<br />
$<br />
PLAINS<br />
BAW BAW *<br />
CARDINIA*<br />
MOYNE<br />
$<br />
CORANGAMITE SURF<br />
LATROBE<br />
COAST<br />
COLAC<br />
$<br />
SOUTH<br />
OTWAY<br />
GIPPSLAND<br />
WARRNAMBOOL<br />
$<br />
GREATER<br />
GEELONG<br />
MORNINGTON<br />
PENINSULA<br />
BASS<br />
COAST<br />
*<br />
TOWONG<br />
EAST GIPPSLAND *<br />
SPEAR Subdivision Status<br />
Active - 75<br />
Signed Up - 2<br />
Proposed - 2<br />
Certification Only - 10<br />
$ Online Payments - 12<br />
Last Updated: 24/7/2013
HUME<br />
WHITTLESEA<br />
NILLUMBIK<br />
MELTON<br />
BRIMBANK<br />
$<br />
MOONEE<br />
VALLEY<br />
MARIBYRNONG<br />
MORELAND<br />
DAREBIN<br />
BANYULE<br />
$<br />
MANNINGHAM<br />
$<br />
BOROONDARA<br />
MAROONDAH<br />
YARRA RANGES *<br />
HOBSONS BAY<br />
STONNINGTON<br />
$<br />
WHITEHORSE<br />
WYNDHAM<br />
MELBOURNE<br />
DOCKLANDS<br />
GLEN EIRA<br />
MONASH *<br />
KNOX<br />
PORT PHILLIP<br />
YARRA<br />
GREATER GEELONG<br />
BAYSIDE<br />
KINGSTON<br />
GREATER<br />
DANDENONG<br />
FRANKSTON<br />
CASEY<br />
CARDINIA*<br />
$ $<br />
QUEENSCLIFFE *<br />
MORNINGTON<br />
PENINSULA<br />
FRENCH ISLAND<br />
Active<br />
Signed Up<br />
Proposed<br />
Certification Only<br />
*<br />
$ Online Payments
SPEAR A2A<br />
• SPEAR conducted an inaugural SPEAR A2A UGM<br />
on 2 July<br />
• Attendees were Melbourne Water, VicRoads,<br />
Yarra Valley Water, City West Water,<br />
Casey City Council, Melbourne City Council and<br />
Open Office - CFA was an apology<br />
• SPEAR A2A web services were explained<br />
• Updates from organisations were presented
SPEAR A2A<br />
• Testing requirements and timelines were<br />
discussed<br />
• The documentation available for SPEAR Web<br />
Services was identified<br />
• Planned and suggested SPEAR Potential<br />
Enhancements for the existing services<br />
were discussed<br />
• The SPEAR Adaptor was discussed – it is not<br />
being supported and has now failed
SPEAR A2A<br />
• There will be a SPEAR A2A UGM before each<br />
SPEAR Release<br />
• Subsequently, Casey, Melbourne and Banyule<br />
met with SPEAR to consider how SPEAR A2A can<br />
be rolled out further to Tech One councils and<br />
then to Infor and Civica councils, initially<br />
• Planning to conduct (three) meetings of groups<br />
of councils who use the same software provider
SPEAR A2A<br />
• Will discuss A2A business requirements and how<br />
to commission software upgrades as a group<br />
• Also need to deal with funding and ongoing<br />
support for each group<br />
• More details at the next UGM
SPEAR Enhancement Program<br />
• SPEAR is running a series of workshops with<br />
interested councils with the aims of:<br />
- Optimising councils interactions with, and<br />
knowledge of, SPEAR, and<br />
- Improving SPEAR’s training program<br />
• Initially, starting with councils<br />
• Applicants and Referral Authorities will follow<br />
in 2014
SPEAR Enhancement Program<br />
• First workshops with Melbourne, Banyule,<br />
Mitchell and Kingston with cross sections of<br />
council SPEAR users<br />
• Commenced with a review of the activities<br />
council currently undertakes with SPEAR<br />
• Issues regarding the councils systems and<br />
SPEAR were discussed as well as possible IT<br />
enhancements to SPEAR
SPEAR Enhancement Program<br />
• A report of the outcomes of the workshop has<br />
been prepared for each council indicating possible<br />
future actions and suggested refresher training<br />
• The workshops will continue to roll out with the<br />
volunteer councils over the coming months<br />
• At the end of this period, an assessment of the<br />
benefits of the program will be done to determine<br />
if the program will be continued
Australia Post / Australian and<br />
Victorian Electoral Commissions<br />
• It was initially proposed that SPEAR would send street address<br />
allocations data to Australia Post, AEC, VEC and others<br />
• Discussions held with these parties concluded that they will<br />
need to obtain address data via their existing arrangements<br />
with PSMA rather than from SPEAR<br />
• AEC (tbc) and VEC now do not require addresses from councils<br />
• Councils that have arrangements for the provision of street<br />
addresses to Australia Post should enquire as to whether this<br />
arrangement is still required or can be terminated<br />
• They will still need to be able to follow-up with councils<br />
with checks and clarifications in the future
User Experience Review<br />
• SPEAR has commissioned a consultant to review the system to<br />
enhance the user interfaces<br />
• The aim is to make the system more consistent, intuitive and<br />
improve functional interactions<br />
• A preliminary report has identified a number of potential<br />
improvements, the main ones being:<br />
1. Placement of SPEAR “Buttons”, e.g. “Next>”, “Cancel” and “
Gatekeeper 2 and<br />
Digital Signing Certificates<br />
• Symantec is streamlining its processes for the issue and<br />
renewal of digital certificates<br />
• This includes the replacement of the existing Gatekeeper 1<br />
digital certificate with a new Gatekeeper 2 (GK2) one, with<br />
more security features to comply with Commonwealth<br />
requirements - Symantec is in the final stages of accreditation,<br />
which is expected later this year<br />
• SPEAR has the ability to determine when it will migrate to the<br />
new certificates and is proposing to do this early 2014<br />
• Then, all certificates issued / renewed will be GK2 ones<br />
• From Release 3.4, SPEAR will accept either<br />
certificate type for digital signing
ePlan<br />
Where are we at?
What Can Be Lodged Using ePlan?<br />
• Most Subdivision Act application types currently<br />
supported by SPEAR can be lodged as ePlans<br />
– Section 22, 23, 24A, 32, 32a, 35, 35(8) (See SPEAR User Guide 1)<br />
– Must be connected to MGA94 bearing datum - this also applies to<br />
non-survey and partial survey plans<br />
– Boundaries can be defined by buildings (footprint only)<br />
• Except for Boundary Plans and Section 37 Staged Plans<br />
– Stage 1 plans may still be submitted, however subsequent stages<br />
are not yet compatible with LV examination process for compilation<br />
• 3D building plans are not yet supported
Implementation Progress<br />
Stage 1<br />
– Commissioned in September<br />
2011<br />
– ePlan as supporting document<br />
(like AFR)<br />
– Testing SPEAR and surveying<br />
software<br />
– Pilot program with surveyors<br />
Stage 2 On-going<br />
– In production since May 2013<br />
– ePlan as the Plan of Subdivision<br />
/ Consolidation<br />
– Plan PDF derived from the ePlan<br />
(via Visualisation)<br />
– Further development of the<br />
validation and data delivery<br />
services
Implementation Update<br />
• Surveying Industry<br />
– Pilot Program: 12 firms participated & produced 10 trial ePlans<br />
– Production: 4 ePlans as Plans of Subdivision in SPEAR<br />
• 1 has been registered<br />
– Group workshop Individual consultation Support in execution<br />
• Software Vendors<br />
– Geocomp Consulting / ePlan Services (ePSALON) : Beta<br />
– LISTECH (LISCAD) : In production<br />
– 12D, Autodesk (Civil 3D) and Bentley (Microstation) : In planning stages
SPEAR Planning Update
SPEAR Planning Statistics
Future of SPEAR Planning<br />
• No updates have been scheduled for SPEAR<br />
Planning<br />
• This will be the norm until outcomes from internal<br />
department discussions are available<br />
• PBH, DTPLI (formerly DPCD) is still providing<br />
support for this service
Contact for PBH, DTPLI<br />
(formerly DPCD)<br />
John Phillips<br />
Director, Planning and Building Systems<br />
Phone: 03 9223 5344<br />
email: john.m.phillips@dtpli.vic.gov.au
Street Addressing Updates
SPEAR Addressing<br />
Information Session Update<br />
Robert Morrison<br />
Land Administration Data Management Team Leader
Presentation Overview<br />
• SPEAR Address Processing Flowchart<br />
• Maintenance Figures Sourced for SPEAR<br />
• Trending of SPEAR Maintenance<br />
• Last Months Processing<br />
• Common / Emerging Issues<br />
• Process Improvement Suggestions
SPEAR Processing Flowchart<br />
Addressing to<br />
SPEAR<br />
Forwarded to<br />
ISD Via NES<br />
Weekly<br />
Combined M1<br />
LGA<br />
Applications<br />
SPEAR<br />
Same Day<br />
ISD<br />
• Timeline<br />
• Applications prior to certification<br />
• SPEAR – same day<br />
• ISD – 3 weeks behind NES<br />
• Maintainer – 5 days to process +<br />
1 week to supply to Vicmap LAT<br />
Vicmap LAT<br />
Maintainer<br />
Weekly Data<br />
Supply<br />
Vicmap LAT
SPEAR Sourced Address<br />
Maintenance Figures<br />
• Trending over the last<br />
two years (Six Month<br />
Snapshots)<br />
Month No. of<br />
LGAs<br />
Dec-11 14<br />
Jun-12 33<br />
Dec-12 57<br />
Jun-13 68<br />
No. of<br />
CRs<br />
89<br />
197<br />
561<br />
553<br />
No. of<br />
Records<br />
352<br />
1061<br />
2913<br />
2992<br />
No. of LGAs<br />
80<br />
60<br />
40<br />
20<br />
0<br />
Apr-13<br />
Jun-13<br />
Dec-11<br />
Feb-12<br />
Apr-12<br />
Jun-12<br />
Aug-12<br />
Oct-12<br />
Dec-12<br />
Feb-13<br />
600<br />
500<br />
400<br />
300<br />
200<br />
100<br />
0<br />
No of CRs<br />
Jun-13<br />
Dec-11<br />
Feb-12<br />
Apr-12<br />
Jun-12<br />
Aug-12<br />
Oct-12<br />
Dec-12<br />
Feb-13<br />
Apr-13<br />
3500<br />
3000<br />
2500<br />
2000<br />
1500<br />
1000<br />
500<br />
0<br />
No. of Records<br />
Jun-13<br />
Dec-11<br />
Feb-12<br />
Apr-12<br />
Jun-12<br />
Aug-12<br />
Oct-12<br />
Dec-12<br />
Feb-13<br />
Apr-13
Last Months Processing<br />
• 876 CRs for July<br />
– Approximately 35 per day<br />
– 6517 M1 records in total<br />
• ISB Vet results<br />
– 58% sent for Loading<br />
– 9% awaiting plan maint.<br />
3799<br />
– 33% ceased processing<br />
• 95% in Mapbase (2042 records)<br />
July M1 Records<br />
58%<br />
• 3% Duplicate records (65 records)<br />
• 2% Incorrect/Insufficient Information<br />
(43 records)<br />
568<br />
9%<br />
2150<br />
33%<br />
On Hold Closed Forwarded
Last Months Processing<br />
6517<br />
M1 Records<br />
Vetting Process<br />
M1 Loading<br />
DATE<br />
Records<br />
on Hold<br />
In<br />
Mapbase<br />
Duplicate<br />
records<br />
Insufficient<br />
Details<br />
Erroneous<br />
Data<br />
LGA Loaded<br />
Prior to<br />
SPEAR M1<br />
Total SPEAR<br />
M1 Records<br />
Loaded<br />
July 1 - July 7 97 693 22 15<br />
July 8 - July 14 142 528 17 11<br />
July 15 - July 21 212 472 15 10<br />
July 22 - July 28 75 281 9 6<br />
July 29 - Aug 4 42 67 2 1<br />
TOTAL 568 2043 65 43<br />
1 31 426<br />
2 20 897<br />
1 40 786<br />
8 21 759<br />
0 20 787<br />
12 132 3655<br />
• Insufficient details are declined<br />
• Erroneous data are corrected
Common & Emerging Issues<br />
• Vicmap Links<br />
Vicmap LAT Link<br />
Unique Identifiers<br />
Property Parcel Address<br />
Standard<br />
Parcel<br />
Identifier<br />
Plan<br />
No.<br />
Lot<br />
No.<br />
lot_number<br />
plan_number<br />
spi<br />
address_PFI<br />
parcel_PFI<br />
property_PFI<br />
PS711269 1<br />
PS707110<br />
PS718435<br />
PS725110<br />
RP006543<br />
RES NO 1<br />
COMM PROP1<br />
ROAD NO 1<br />
1<br />
RES1<br />
CM1<br />
R1<br />
RP6543
Common / Emerging Issues<br />
• Property Details<br />
New/Existing<br />
Base Property<br />
No.<br />
base_propnum<br />
Property Details<br />
New/Existing<br />
Property<br />
No.<br />
propnum<br />
303.11 X<br />
35678 X<br />
New/Existing<br />
Parcel<br />
No.<br />
crefno<br />
• Propnum format is an<br />
integer in SPEAR<br />
– Some LGAs have full stop<br />
embedded in Propnum<br />
EG: PROP_PROPNUM 44940.005<br />
– These councils must load<br />
property details via NES M1<br />
• Population of Parent<br />
Propnum
Common / Emerging Issues<br />
• New Road Indicator Missing<br />
• Ingenious ways of addressing<br />
Address - Road and Locality information<br />
New<br />
Road<br />
(Y or N)<br />
Road<br />
Name<br />
Road<br />
Type<br />
Road<br />
Suffix<br />
Locality<br />
locality_name<br />
road_suffix<br />
road_type<br />
road_name<br />
new_road<br />
Y<br />
BUNYIP<br />
LANE<br />
CLYDE NORTH<br />
REQUIRED<br />
ROAD NAME<br />
ROAD<br />
YARRAWONGA
Common / Emerging Issues<br />
• Multi Assessments<br />
Administrative Vicmap LAT Link Property Details Address - Building Sub Unit Address - House No. Address - Road and Locality information Edit Type<br />
New<br />
LGA<br />
Subdivisio<br />
Unique<br />
n<br />
identifier<br />
(Y or N)<br />
Plan<br />
No.<br />
Lot<br />
No.<br />
New/Existing<br />
Property<br />
No.<br />
Building<br />
Sub Unit<br />
Type<br />
Building<br />
Sub Unit<br />
Prefix<br />
1st<br />
Building<br />
Sub Unit<br />
No.<br />
1<br />
Building<br />
Sub Unit<br />
Suffix<br />
1st<br />
House<br />
No.<br />
Prefix<br />
1st<br />
House<br />
No.<br />
1<br />
House No.<br />
Suffix<br />
1st<br />
New<br />
Road<br />
(Y or N)<br />
Road<br />
Name<br />
Road<br />
Type<br />
Roa<br />
d<br />
Suff<br />
ix<br />
Locality<br />
Edit Code<br />
B / C / E / P / S / Z<br />
A / R<br />
edit_code<br />
locality_name<br />
road_suffix<br />
road_type<br />
road_name<br />
new_road<br />
house_suffix_1<br />
house_number_1<br />
house_prefix_1<br />
blg_unit_suffix_1<br />
blg_unit_id_1<br />
blg_unit_prefix_1<br />
blg_unit_type<br />
propnum<br />
lot_number<br />
plan_number<br />
new_sub<br />
lga_code<br />
311<br />
PS707710<br />
2 1<br />
31<br />
HIGH<br />
ROAD<br />
NHILL<br />
S<br />
311<br />
PS707710<br />
2<br />
2<br />
31<br />
HIGH<br />
ROAD<br />
NHILL<br />
S<br />
311<br />
PS707710<br />
2<br />
3<br />
31<br />
HIGH<br />
ROAD<br />
NHILL<br />
S<br />
• Edit Code for Multi Assessments is ‘A’<br />
• Won’t be loaded
Common & Emerging Issues<br />
• Address Location<br />
Distance<br />
Related<br />
(Y or N)<br />
distance_related_flag<br />
Primary<br />
Property<br />
Access<br />
Point<br />
(Y or N)<br />
is_primary<br />
Address - Location<br />
Easting<br />
easting<br />
Property Access Point Details<br />
Co-ordinates<br />
Northing<br />
northing<br />
Datum/<br />
Projection<br />
datum/proj<br />
O/S<br />
Property<br />
(Y or N)<br />
Y Y XXXXX XXXXX MGA94 N<br />
Y<br />
outside_property<br />
• Coordinates<br />
falling outside<br />
property polygon<br />
• Primary Access<br />
Indicator<br />
– Load scripts looking<br />
for all five to be filled<br />
in
Potential Process Improvements<br />
• Local Government<br />
– Population of forms with M1 Loading Rules in mind<br />
– Improve internal processes to eradicate duplication<br />
• SPEAR<br />
– Combined Weekly M1<br />
– Ability to cater for Multi Assessments<br />
• Information Services Division<br />
– Improve processing efficiencies<br />
– Rely more on automatic validation<br />
processes<br />
– Agree on the best method for issue<br />
resolution
Questions?
SPEAR User Group<br />
Meeting 2013<br />
Office of Geographic Names<br />
Presented by Rafe Benli
Office of Geographic Names<br />
Overview<br />
• Who are we?<br />
• What does the Office do?<br />
45
Audits - Results<br />
As of 31 May 2012 1 July 2013<br />
Number of councils on SPEAR 64 councils 75 councils<br />
Councils audited to date 22 councils 45 councils<br />
Number of plans of subdivisions 39 plans 93 plans<br />
audited to date<br />
Non-conforming plans 14 plans 23 plans<br />
Conforming plans 25 plans 70 plans<br />
Percentage of compliant plans 64% 75%<br />
46
Logical addressing<br />
• How can you help?<br />
• Who can help you?<br />
• Guidelines for Geographic Names 2010 Version 2<br />
• AS/NZS4819:2011 Rural and urban addressing<br />
• Councils<br />
• Office of Geographic Names<br />
• Vicmap<br />
• Why is this so important?<br />
47
ANZAC Commemorative Naming Project<br />
www.dse.vic.gov.au/namingplaces> ANZAC Commemorative Naming Project
Questions<br />
Further information<br />
Guidelines:<br />
www.dse.vic.gov.au/namingguidelines<br />
VICNAMES:<br />
www.dse.vic.gov.au/vicnames<br />
Office of Geographic Names:<br />
www.dse.vic.gov.au/namingplaces<br />
Contact details:<br />
Office of Geographic Names: geo.names@dtpli.vic.gov.au<br />
Vicmap Addressing: vicmap.address@dse.vic.gov.au<br />
49
SPEAR IT
PE List<br />
• Discussion on priorities<br />
• Issues raised by users
Release 3.4 Content -<br />
Wizard Improvements<br />
The subdivision application wizard has been<br />
redesigned to improve user experience and<br />
reliability<br />
• All subdivision applications are now<br />
created in the subdivision wizard<br />
• “Joint Application” types are permissible<br />
for Section 35 and Section 37 plans
Release 3.4 Content -<br />
Wizard Improvements<br />
• Applicant Contact and/or the Responsible<br />
Authority are able to select a ‘primary<br />
parcel’ for identification of the application<br />
• The Applicant Contact will be required to<br />
indicate the number of unlimited and<br />
limited Owners Corporations being created
Release 3.4 Content -<br />
Supplementary Abstract of Field Records<br />
Supplementary Abstract of Field Records<br />
(SAFR) can be lodged with Land Victoria via<br />
SPEAR. Applicant Contact will need to:<br />
– indicate whether a SAFR is required<br />
– provide an estimated date for completion of<br />
works (modifiable)<br />
Land Victoria is notified when the SAFR is<br />
attached. If necessary, the SPEAR<br />
requisition process will apply
Release 3.4 Content -<br />
Owners Corporation Declaration<br />
An Owners Corporation declaration is now<br />
required for all s.32 applications<br />
If applicable, the Applicant Contact must<br />
upload the Unanimous Resolution of Owners<br />
Corporation Members or a VCAT Order under<br />
section 34D of the Subdivision Act 1988
Release 3.4 Content -<br />
Public Open Space<br />
If, at Certification, a requirement for Public<br />
Open Space had not been satisfied, the<br />
Responsible Authority must revisit the Public<br />
Open Space requirement prior to issuing<br />
Statement of Compliance<br />
Statement of Compliance cannot be issued<br />
where the Public Open Space requirement<br />
has not been satisfied
Release 3.4 Content -<br />
Re-referrals<br />
SPEAR will display a warning message if a<br />
re-referral results in the closure of an<br />
existing referral<br />
Responsible Authority users can acknowledge<br />
the warning and continue, or change the<br />
re-referral request to avoid the unwanted<br />
closure of one or more referrals
Release 3.4 Content -<br />
Street Addressing<br />
A Street Addressing column on the<br />
Application List will indicate to Responsible<br />
Authority users whether the street address<br />
allocations have been completed for each<br />
application
Release 3.4 Content -<br />
Refused Planning Permits<br />
If the Planning Permit in a joint application<br />
has been refused, the Responsible Authority<br />
can continue to process or refuse the<br />
Certification component of the application
Release 3.4 Content -<br />
Referral Authority Refused Consent<br />
Where a Referral Authority has objected to,<br />
or refused consent, for a s.55 or s.8 referral,<br />
the outcome will be displayed in red text on<br />
the Details screen<br />
• Responsible Authority users receive a<br />
warning when making a Planning Permit or<br />
Certification decision if one or more<br />
Referral Authorities have objected or<br />
refused consent
Release 3.4 Content –<br />
Linked Applications<br />
When viewing an application that has been<br />
linked with another (i.e., Certification that<br />
references an earlier SPEAR permit), the<br />
summary screen now contains links to allow<br />
navigation between applications<br />
The status of the SPEAR planning permit is<br />
displayed to the Responsible Authority when<br />
making the certification decision
Release 3.4 Content -<br />
Planning Permit and Associated Documents<br />
The Planning Permit and any endorsed<br />
documents will now be displayed on the<br />
Summary screen as a group
Release 3.5 - General<br />
• Overhaul of the application list<br />
– performance improvement<br />
– usability improvement<br />
• Improve the assessment of proposed<br />
changes (to the application) workflow<br />
• Re-label the application document<br />
– "Plan of Subdivision" or "Plan of Consolidation"<br />
• Improve the usability of existing reports<br />
• Reflect the status of ‘Withdrawn at LV’
Release 3.5 - Applicant<br />
• Selection of application parcels using a<br />
map user interface<br />
– View existing application parcels via a map GUI<br />
• Attach Supplementary Abstract of Field<br />
Records (SAFR) as an ePlan<br />
• ‘Owners Corporation Entitlements’ can be<br />
attached as a spreadsheet
Release 3.5 –<br />
Responsible Authority<br />
• ‘Payment Details’ document to be<br />
formatted as a tax invoice<br />
• Capture the planning permit issue and<br />
expiry dates<br />
• Planning and Environment Act<br />
Amendments<br />
– Enhance referral request information<br />
– Differentiate between ‘determining’ and ‘recommending’<br />
referral authorities
Release 3.5 –<br />
Responsible Authority<br />
• Enhance council reference number labels<br />
• Always include a mandatory action to<br />
respond to an RFI from a Referral Authority<br />
• Allow the withdrawal of an RFI<br />
• Allow internal referrals to comment on<br />
Permit, Cert and SOC
Release 3.5 - Other<br />
• Display the compiled plan sheets on the<br />
LV lodgment screen<br />
• ePlan validation and schema changes<br />
• Include an action to ‘Recommend Title<br />
Plan for Certification’<br />
• Allow OSGV examiners to add ‘condition<br />
sheets’ to TPs<br />
• Notify LV when the status is ‘Lodged at LV’
Release 3.6/4.0<br />
• Provide the ability for a lodging party to<br />
lodge an application in SPEAR<br />
– Ability to complete the application lodging document<br />
online<br />
– Ability to pay the lodging fee<br />
– Ability to add additional lodging documents<br />
– Ability for the Plan Acceptance Officer to accept and<br />
lodge the application from SPEAR into VOTS<br />
• Enable surveyors to lodge Boundary Plan<br />
applications and pay the fee in SPEAR
Release 3.6/4.0<br />
• Free-text option when creating an<br />
Other Document Type<br />
• Reporting improvements<br />
• Usability improvements<br />
• Form 1 improvements<br />
• VicSmart planning permit process<br />
improvements<br />
• Enable supply of A-SPEC information in<br />
SPEAR (tbc)
Morning Tea
Discussions – Group Session<br />
Applicants, Councils and Referral Authorities
Planning and Environment<br />
Amendment (General) Act<br />
2013 and regulations<br />
VicSmart permit process<br />
How they affect the permit process
Planning and Environment Amendment<br />
(General) Act 2013<br />
Referral authorities<br />
• Two types of referral authority:<br />
- determining referral authority<br />
- recommending referral authority<br />
• A referral authority has specific duties<br />
• Referral authorities must keep a register<br />
• Referral authorities must act promptly<br />
• Referral authority liable to pay compensation where permit cancelled because of an<br />
act or omission of the referral authority<br />
• Certain information must be exchanged<br />
73
Two types of referral authority<br />
Determining referral authority<br />
• Same powers as existing referral authority<br />
- Authority objects ≈ application must be refused<br />
- Authority requires permit conditions ≈ must be included on permit<br />
Recommending referral authority<br />
• Can object, not object or specify conditions<br />
• Responsible authority makes the final decision<br />
• Authority can appeal decision of responsible authority if it:<br />
- objected to the grant of the permit<br />
74<br />
- recommended conditions that were not included in the permit
Two types of referral authority<br />
66.01 Subdivision referrals<br />
An application of the kind listed in the table below must be referred to the person or body specified as the referral authority.<br />
The table below specifies whether the referral authority is a determining referral authority or a recommending referral<br />
authority.<br />
Kind of application Referral authority Type of referral authority<br />
To subdivide land outside the<br />
metropolitan fire district which<br />
creates a road, where the<br />
requirements of Clause 56.09-3<br />
are not met.<br />
Country Fire Authority<br />
Determining referral authority<br />
To subdivide land if the only<br />
access to a lot is over Crown<br />
land which has not been<br />
reserved or proclaimed as a<br />
road.<br />
Minister administering the<br />
Land Act 1958<br />
Determining referral authority<br />
75<br />
To subdivide land crossed by a<br />
gas transmission pipeline or a<br />
gas transmission pipeline<br />
easement.<br />
The relevant gas supply<br />
authority<br />
Determining referral authority
Is the referral process different for each type<br />
of referral authority?<br />
NO - referral process is the same:<br />
• both must be given a copy of an application without delay (unless the referral authority has<br />
previously stated in writing that it does not object)<br />
• both have 21 days to request more information<br />
• both must consider every referred application<br />
• both may object, request conditions or advise that it does not object<br />
• both may apply to the Minister under s 56(4) for an extension of time<br />
76
What happens if a recommending referral<br />
authority objects or requests conditions?<br />
Responsible authority<br />
• may either grant a permit or refuse the application<br />
• if a permit is granted, the responsible authority must give the recommending<br />
referral authority notice of its decision<br />
• permit cannot be issued until any review by VCAT has occurred<br />
Recommending referral authority<br />
• has 21 days to apply to VCAT for review of the decision of the responsible authority<br />
• is a party to proceedings for review<br />
• is entitled to notice of an application for review by the applicant<br />
77
Duties of referral authorities<br />
New duties are set out in section 14A<br />
• must have regard to the objectives of planning in Victoria<br />
• must have regard to the Minister’s directions<br />
• must comply with the Planning and Environment Act 1987<br />
• must have regard to the planning scheme<br />
• must provide information and reports as required by the Minister<br />
78
Referral authority register<br />
Referral authority must keep a register containing the prescribed<br />
information<br />
Prescribed information is:<br />
• name of the responsible authority referring the application<br />
• permit application number<br />
• reference number given by referral authority<br />
• date the referral authority received the application<br />
• address of the land affected by the application<br />
• proposed use, development or other matter for which the application is made<br />
• date and decision of the referral authority<br />
79
Exchange of information<br />
Between responsible authority and referral authority<br />
Responsible authority must give referral authority a copy of the permit with<br />
prescribed information.<br />
Prescribed information is:<br />
• permit application number<br />
• date the responsible authority received the application<br />
• description of why the permit is required<br />
• list of clauses in the scheme that require the application to be referred<br />
• copy of the applicable scheme description of the kind of application required<br />
to be referred<br />
80<br />
• whether the referral authority is determining or recommending
Exchange of information<br />
Between the referral authority and the applicant<br />
Referral authority must give a copy of its decision and comments to the applicant<br />
81
When does the General Act come into<br />
operation?<br />
Stage 1 came in on 22 July 2013<br />
• duties of referral authority<br />
• referral authority may be liable to pay compensation<br />
• referral authorities must act expeditiously<br />
Stage 2 comes in on 28 October 2013<br />
• the two kinds of referral authority<br />
• responsible authority to provide referral authority with certain information<br />
• referral authority must keep a register of all applications referred to it<br />
82
Where do I go to get more information on<br />
the General Act and proposed Regulations?<br />
Two guides on the DTPLI website:<br />
• A guide to the Planning and Environment Amendment (General) Act 2013<br />
• Guide to the proposed Planning and Environment Regulations 2013<br />
http://www.dpcd.vic.gov.au/planning/theplanningsystem/<br />
legislation-and-regulations<br />
83
VicSmart permit process<br />
A new shorter permit assessment process<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
decision within 10 business days<br />
exempt from advertising<br />
no ‘statutory’ further information request<br />
referral approval prior to lodging<br />
pre-set information requirements<br />
assess against pre-set decision guidelines<br />
decision by CEO or delegate<br />
applicant has right of review<br />
new VCAT process<br />
84
When is an application VicSmart?<br />
An application is a VicSmart application if:<br />
<br />
<br />
<br />
<br />
the application is listed in the scheme as a VicSmart application<br />
the application does not require a permit under another provision that is not listed<br />
any permit will not result in a breach of a restrictive covenant<br />
the application has obtained the relevant referral authority approval<br />
85
Classes of VicSmart application<br />
Twelve classes of application:<br />
<br />
<br />
<br />
<br />
<br />
<br />
minor subdivisions<br />
fences<br />
minor buildings and works in employment areas<br />
removal of one tree<br />
minor buildings and works in the Heritage Overlay<br />
development in the Special Building Overlay<br />
signs up to 10m 2<br />
<br />
waiving of car parking<br />
86
Classes of subdivision application<br />
Three classes:<br />
<br />
<br />
subdivide to realign common boundary between 2 lots<br />
subdivide into lots each containing an existing building or car parking space if:<br />
- buildings/spaces have been constructed in accordance with scheme/permit<br />
- a certificate of occupancy for building was issued in previous 5 years<br />
<br />
subdivide into 2 lots if an approval for buildings or works on the land exists and<br />
construction has lawfully started<br />
Applies in residential zones, industrial zones, commercial zones,<br />
Capital City Zone and Docklands Zone, Heritage Overlay and<br />
Special Building Overlay<br />
87
88<br />
Questions?
Changes to Referral Process<br />
(Planning and Environment Act)<br />
• From 28 October 2013, Responsible Authorities will<br />
be required to provide additional details to Referral<br />
Authorities (RAs) in accordance with the Planning<br />
and Environment Act amendments:<br />
– whether the RA is a determining RA or a recommending RA<br />
for the application<br />
– a description of why a permit is required<br />
– a list of the clauses in a planning scheme that require the<br />
application to be referred to that RA<br />
– a copy of the applicable description in a planning scheme of<br />
the kind of application required to be referred to that RA
Changes to Referral Process<br />
(Planning and Environment Act)<br />
• When referring in SPEAR, Responsible Authorities<br />
must use the ‘add comment’ function to include<br />
required information
Changes to Referral Process<br />
(Planning and Environment Act)<br />
• In SPEAR Release 3.5, additional fields will be<br />
available to assist with these new requirements
Lapsing Applications<br />
• Proposed automatic lapsing of Certification<br />
applications once expired<br />
• The expired application would move to the<br />
completed list<br />
• Any foreseeable issues?
Endorsing Plans<br />
• Applicants can propose changes to an<br />
Endorsed Plan by submitting a new<br />
version for endorsement<br />
• Should this be accompanied by an<br />
Application to Amend a Planning Permit or<br />
a Request for Secondary Consent?
Renaming Secondary Consents<br />
Currently, an applicant uses ‘Request<br />
Consent Regarding a Condition of a Permit’<br />
• SPEAR is proposing to rename this action<br />
‘Request Secondary Consent’<br />
• Comment?
Planning Report<br />
• SPEAR requires a “Planning Report” for a<br />
building subdivision prior to submission to<br />
council<br />
• What is it?<br />
• Is it needed?
Application ‘On Hold’<br />
• Should SPEAR allow an applicant to place<br />
an application ‘On Hold’?<br />
– This would prevents the application moving to<br />
certification or lodgement at LV<br />
– Current practice is to not sign the plan and<br />
ignore the reminders<br />
• Comment?
Guest Access<br />
• Should SPEAR allow Guests to use the<br />
watch functionality in SPEAR to receive<br />
notifications?
Subdivision Changes Regarding<br />
Telecommunications Services<br />
Changes to referral process (VC81, VPP)<br />
Council no longer refers to Telstra. Instead must<br />
have, in most instances, a permit condition for land<br />
owner entering agreements with providers of<br />
telecommunications services, including fibre<br />
• Should telecommunications agreements be a<br />
mandatory action against the Applicant Contact?
Subdivision Changes Regarding<br />
Telecommunications Services<br />
Additionally, the Responsible Authority cannot issue<br />
SOC until the permit applicant has provided written<br />
confirmation that all lots are connected/ready for<br />
telecommunications and fibre ready facilities installed<br />
• Should Applicant contact be required to enter this<br />
information into SPEAR?
Form 1<br />
• Applicant Contact currently provides a<br />
signed Form 1 (“Owner’s Consent”)<br />
• Propose to make the SPEAR Application<br />
form the Form 1
Form 1<br />
• If the Applicant Contact indicates that<br />
he/she is also the Applicant, a separate<br />
Form 1 is not required<br />
• Owner’s Consent will be required as per<br />
the Subdivision Regulations:<br />
I/We consent to the applicant submitting this<br />
plan to the Council for certification.<br />
Signed<br />
[Name and signature of Owner]
Form 1<br />
• If the Applicant Contact is not the<br />
Applicant, a signed Form 1 is required to<br />
be supplied<br />
• Comment?
A-SPEC discussion<br />
Proposal is to allow A-SPEC documents to be<br />
loaded in SPEAR<br />
• How many councils want this?<br />
• At what time in the subdivision process<br />
are they provided and by whom?<br />
• How many documents types are there?<br />
• How many documents will there be and<br />
what size are they?<br />
• Discussion?
Owners Corporation Data<br />
• Surveyors will be able to upload owners<br />
corporation schedules in spreadsheet<br />
(XLS) format to SPEAR<br />
• The ability for LV plan examiners to<br />
handle lot entitlement and liability<br />
information directly from a spreadsheet<br />
will save time and reduce manual<br />
processing errors
SPEAR Payments<br />
Payments in SPEAR are an optional action at either<br />
the time of submission or later<br />
It has been suggested that this be a mandatory<br />
action at time of submission to council<br />
However, advice has been received that a VCAT<br />
decision handed down recently allowed for the<br />
application fees be paid between 30 to 60 days<br />
from submission of the application<br />
• Comment?
SMES Upgrade<br />
Next year, the SMES system will be improved to<br />
allow submission of PM Sketch Plans<br />
• SPEAR is proposing to remove PM Sketch Plans<br />
from SPEAR<br />
• Are there any reasons to keep processing PM<br />
Sketch Plans in SPEAR?
Training / Service Desk<br />
Update
Compatibility View<br />
• In release 3.4, missing search boxes and<br />
signing issues (previously fixed by<br />
activating ‘Compatibility View’ in IE) will<br />
be resolved<br />
• If ‘Compatibility View’ is enabled in your<br />
web browser, you will need to deactivate<br />
the setting post-release
Password Storage in SPEAR<br />
SPEAR is changing hardware providers<br />
• SPEAR users will be prompted to update their<br />
passwords the first time they log in after the<br />
release date<br />
• The release is currently scheduled for<br />
18/10/2013
Conditions for SOC<br />
• Many Responsible Authorities are now<br />
using the ‘Conditions for SOC’ document<br />
• This allows them to keep track of<br />
outstanding Planning Permit conditions
Conditions for SOC<br />
• Applicants can tick off these conditions as<br />
they are met - SPEAR will notify the Council<br />
• Referral Authorities can also use this<br />
document if the Responsible Authority has<br />
listed their conditions
Conditions for SOC<br />
• The Responsible Authority must confirm<br />
that all conditions have been satisfied<br />
before the SOC can be issued
System Errors<br />
• Occasionally users<br />
may receive a system<br />
error. If this occurs,<br />
closing your web<br />
browser and trying<br />
again can resolve the<br />
issue<br />
• If this does not help,<br />
contact the SPEAR<br />
Service Desk
Paper Correspondence<br />
• Some organisations may still be posting paper<br />
documentation to other parties<br />
• Users are urged to take advantage of SPEAR to<br />
minimise time and postage costs<br />
• SPEAR notifies interested parties when a key<br />
document or decision is added<br />
• Parties to a SPEAR application should not send or<br />
receive a paper copy of any document that has<br />
been supplied in SPEAR
User Issues?
Lunch