ePlan Workshop for Surveying Industry in Victoria - Spear
ePlan Workshop for Surveying Industry in Victoria - Spear
ePlan Workshop for Surveying Industry in Victoria - Spear
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>ePlan</strong> <strong>Workshop</strong> <strong>for</strong><br />
<strong>Survey<strong>in</strong>g</strong> <strong>Industry</strong> <strong>in</strong> <strong>Victoria</strong><br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision<br />
11 February 2011
Agenda<br />
• Introduction to <strong>ePlan</strong><br />
• The <strong>ePlan</strong> Project Implementation <strong>in</strong> <strong>Victoria</strong><br />
• <strong>ePlan</strong> Bus<strong>in</strong>ess Case<br />
• <strong>ePlan</strong> File Structure<br />
• <strong>ePlan</strong> Applications – Overview<br />
• Download<strong>in</strong>g Content <strong>for</strong> <strong>ePlan</strong> Files<br />
• Prepar<strong>in</strong>g <strong>ePlan</strong> Files us<strong>in</strong>g Third-party Software<br />
• Validat<strong>in</strong>g <strong>ePlan</strong> Files<br />
• Visualis<strong>in</strong>g <strong>ePlan</strong> Files<br />
• Creat<strong>in</strong>g an Application with an <strong>ePlan</strong> <strong>in</strong> SPEAR<br />
• Exam<strong>in</strong><strong>in</strong>g and Register<strong>in</strong>g <strong>ePlan</strong> Files<br />
• Updat<strong>in</strong>g Land In<strong>for</strong>mation Data Bases
Introduction to <strong>ePlan</strong><br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Vision <strong>in</strong> <strong>Victoria</strong><br />
<strong>ePlan</strong> Vision<br />
Pr<strong>in</strong>ciples<br />
Cadastral and Survey<br />
In<strong>for</strong>mation Download<br />
Survey and<br />
Cadastral Data Reuse<br />
Efficiency <strong>in</strong> Plan Preparation,<br />
Exam<strong>in</strong>ation and Registration<br />
Outcomes<br />
Authoritative Digital<br />
Cadastral In<strong>for</strong>mation<br />
Standardised Data Exchange<br />
between Databases and Users<br />
eLand Development<br />
Means<br />
Survey-accurate<br />
Digital Cadastral Database<br />
Digital Plans of Subdivision<br />
Fully Electronic Subdivision<br />
and Exam<strong>in</strong>ation Processes
<strong>ePlan</strong> Process Loop<br />
<strong>ePlan</strong> Validation<br />
& Visualisation<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong> Preparation<br />
Work Station<br />
Vicmap Property VOTS LANDATA SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Data<br />
Delivery Service<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database
What is <strong>ePlan</strong>?<br />
• National <strong>in</strong>itiative by the Intergovernmental<br />
Committee on <strong>Survey<strong>in</strong>g</strong> and Mapp<strong>in</strong>g (ICSM)<br />
through the <strong>ePlan</strong> work<strong>in</strong>g group<br />
• National adoption of a data transfer standard <strong>for</strong><br />
cadastral and survey <strong>in</strong><strong>for</strong>mation<br />
• Development of a system to replace the use of<br />
paper and / or PDF versions of a subdivision<br />
plan with an electronic file of subdivision and<br />
survey<strong>in</strong>g data
National Activity<br />
• F<strong>in</strong>alis<strong>in</strong>g the <strong>ePlan</strong> Protocol<br />
– F<strong>in</strong>al approval of the protocol by ICSM – November 2009<br />
– F<strong>in</strong>al approval of Model Governance document – November 2009<br />
– F<strong>in</strong>al approval of the <strong>ePlan</strong> preparation guidel<strong>in</strong>es – November 2010<br />
• Sett<strong>in</strong>g up <strong>for</strong> adopt<strong>in</strong>g <strong>ePlan</strong><br />
– Implementation timetable <strong>for</strong> each jurisdiction<br />
– Development of related specifications eg validation, delivery tools<br />
– Management of the <strong>ePlan</strong> Protocol<br />
• Work<strong>in</strong>g with draft<strong>in</strong>g / survey<strong>in</strong>g<br />
application vendors<br />
– Vendor <strong>for</strong>ums – National and <strong>in</strong> <strong>Victoria</strong><br />
– Meet<strong>in</strong>g <strong>in</strong>dividual vendors – as needed
Technical Prov<strong>in</strong>g <strong>in</strong> <strong>Victoria</strong><br />
• Test<strong>in</strong>g the standard<br />
– Tested that the standard is complete and comprehensive<br />
– Developed an <strong>in</strong>itial proof of concept<br />
– Conducted a trial back-capture pilot<br />
• Us<strong>in</strong>g the standard<br />
– Identified technical issues and needs<br />
– Specified prelim<strong>in</strong>ary bus<strong>in</strong>ess requirements of technical<br />
components needed to use <strong>ePlan</strong><br />
– Investigated the use of <strong>ePlan</strong> <strong>in</strong> other areas,<br />
eg Subdivision Branch, SII, CAD / survey<strong>in</strong>g package vendors<br />
• Sett<strong>in</strong>g up <strong>for</strong> adopt<strong>in</strong>g <strong>ePlan</strong><br />
– Def<strong>in</strong>ed the <strong>in</strong>itial Land <strong>Victoria</strong> / Registrar’s requirements <strong>for</strong><br />
electronic Plans of Subdivision<br />
– Developed the first version of <strong>Victoria</strong>n-specific <strong>ePlan</strong> data
Implementation Timel<strong>in</strong>es<br />
• Queensland<br />
– 2nd half 2011<br />
• New South Wales<br />
– 4th quarter 2011<br />
• <strong>Victoria</strong><br />
– 2nd half 2011<br />
• Other Jurisdictions<br />
– In plann<strong>in</strong>g stages; watch<strong>in</strong>g 3 larger States
Project Progress<br />
• National Communication<br />
– Form<strong>in</strong>g the National <strong>ePlan</strong> Work<strong>in</strong>g Group<br />
– Standardis<strong>in</strong>g document <strong>for</strong>mats and contents<br />
– Liais<strong>in</strong>g with ICSM and <strong>for</strong>malis<strong>in</strong>g <strong>ePlan</strong><br />
documentation<br />
– Meet<strong>in</strong>g with draft<strong>in</strong>g / survey<strong>in</strong>g application vendors<br />
to workshop issues and solutions
Project Progress<br />
• <strong>Victoria</strong>n Communication<br />
– Brief<strong>in</strong>g survey<strong>in</strong>g <strong>in</strong>dustry bodies and universities<br />
– Form<strong>in</strong>g the <strong>ePlan</strong> Implementation Consultative<br />
Committee<br />
– Meet<strong>in</strong>g with survey<strong>in</strong>g firms to understand processes<br />
– Meet<strong>in</strong>g with surveyors to workshop issues and<br />
solutions<br />
– Brief<strong>in</strong>g survey<strong>in</strong>g <strong>for</strong>ums on <strong>ePlan</strong> and<br />
implementation progress<br />
– Meet<strong>in</strong>g with draft<strong>in</strong>g / survey<strong>in</strong>g application vendors<br />
to workshop issues and solutions
Project Progress<br />
• Draft<strong>in</strong>g / <strong>Survey<strong>in</strong>g</strong> Application Vendors’ Meet<strong>in</strong>gs<br />
– National Level<br />
• March 2009 - Brisbane<br />
• August 2009 - Adelaide<br />
• November 2009 - Melbourne<br />
• August 2010 - Sydney<br />
• September 2011 - New Zealand ?<br />
– In <strong>Victoria</strong><br />
• March 2010 - Introduction / Overview<br />
• April 2010 - Plan<br />
• July 2010 - Survey<br />
• December 2010 - Individual meet<strong>in</strong>gs<br />
• March 2011 - Individual meet<strong>in</strong>gs
Key <strong>ePlan</strong> Issues<br />
• National<br />
– National Specification <strong>for</strong> the Structure of <strong>ePlan</strong> Files<br />
• Drives changes to vendors’ software<br />
• Used by vendors <strong>for</strong> creation of <strong>ePlan</strong>s<br />
– Jurisdiction Specifications <strong>for</strong> Structure of <strong>ePlan</strong> Files<br />
– Visualisation of <strong>ePlan</strong> files<br />
• One national product<br />
• Discussion paper on procurement, fund<strong>in</strong>g, host<strong>in</strong>g,<br />
ma<strong>in</strong>tenance and enhancement<br />
• Used by jurisdictions to create the ‘official’ PDF<br />
– Draft<strong>in</strong>g / survey<strong>in</strong>g application vendors –<br />
national co-ord<strong>in</strong>ation
Key <strong>ePlan</strong> Issues<br />
• <strong>Victoria</strong><br />
– <strong>Victoria</strong>n Specification <strong>for</strong> the Structure of <strong>ePlan</strong> Files<br />
• Drives validation <strong>in</strong> <strong>Victoria</strong><br />
• Specifies data delivery opportunities<br />
• Used <strong>for</strong> visualisation (national specification) and <strong>Victoria</strong>n<br />
presentation stylesheets (<strong>Victoria</strong>n specification)<br />
• Used by vendors <strong>for</strong> surveyor’s benefit<br />
– Possible change to Land <strong>Victoria</strong>’s requirements <strong>for</strong><br />
subdivision plans<br />
• Currently, based essentially on requirements <strong>for</strong> paper plans<br />
• Some current requirements are not suitable <strong>for</strong> electronic data,<br />
e.g. easements, offsets, roads<br />
• Revision of what data Land <strong>Victoria</strong> requires is needed
Key <strong>ePlan</strong> Issues<br />
• <strong>Victoria</strong> (cont)<br />
– Visualisation of <strong>ePlan</strong> files<br />
• Need <strong>for</strong> a Land <strong>Victoria</strong> visualisation application<br />
• Creates a verifiable PDF version of the <strong>ePlan</strong> data file<br />
• Then, the PDF can be relied upon when used <strong>for</strong> other<br />
purposes, <strong>in</strong>ternally and externally<br />
– Interim exam<strong>in</strong>ation of <strong>ePlan</strong> files aga<strong>in</strong>st surveyorsupplied<br />
visualisation PDF’s<br />
– Surveyors’ use of (up to 3) computer applications<br />
– Back-capture of exist<strong>in</strong>g plans
Key <strong>ePlan</strong> Issues<br />
• <strong>Victoria</strong> (cont)<br />
– Abstract of Field Records <strong>in</strong> <strong>ePlan</strong> <strong>for</strong>mat<br />
• Created at various time from at the start to after SOC<br />
• Agreement on the basics (travers<strong>in</strong>g, survey marks,<br />
radiations) with <strong>ePlan</strong> ICC<br />
• Surveyors want paper version <strong>in</strong>to the future<br />
• Consideration of difficulty of hav<strong>in</strong>g abstract <strong>in</strong><strong>for</strong>mation <strong>in</strong><br />
the <strong>ePlan</strong> file as well as a paper version of the abstract –<br />
conclusion that this is not a problem <strong>for</strong> LV<br />
– Draft<strong>in</strong>g / survey<strong>in</strong>g application vendors –<br />
<strong>Victoria</strong>n co-ord<strong>in</strong>ation
The <strong>ePlan</strong> Project Implementation<br />
<strong>in</strong> <strong>Victoria</strong><br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Implementation Project<br />
• Stag<strong>in</strong>g and Timel<strong>in</strong>es<br />
– Stage 1 - To <strong>in</strong>troduce and implement digital plans of<br />
subdivision (<strong>ePlan</strong>) <strong>in</strong> <strong>Victoria</strong> by December 2011<br />
• Phase 1 - detailed IT and stakeholder plann<strong>in</strong>g<br />
1 January - 30 November 2010<br />
• Phase 2 - design, build, test and deployment of specified<br />
software and hardware<br />
1 December 2010 - 30 September 2011<br />
• Phase 3 - implementation at user level with a postimplementation<br />
review<br />
1 October - 31 December 2011<br />
– Stage 2 – Possible further development of the<br />
validation and data delivery services
<strong>ePlan</strong> Implementation Project<br />
• Inclusions<br />
– Requirements of Land <strong>Victoria</strong> <strong>for</strong> digital plans <strong>for</strong><br />
land subdivision<br />
– <strong>ePlan</strong>-enabled SPEAR<br />
– Validation service<br />
– Data delivery service<br />
– Visualisation service<br />
– Consideration of some 3D plans<br />
– <strong>ePlan</strong> stakeholders’ engagement
<strong>ePlan</strong> Implementation Project<br />
• Exclusions<br />
– Consideration of the development of a<br />
survey-accurate cadastral database<br />
– Requirements of Land <strong>Victoria</strong> <strong>for</strong><br />
build<strong>in</strong>g subdivisions<br />
– Consideration of rema<strong>in</strong><strong>in</strong>g 3D plans<br />
– Development of exam<strong>in</strong>ation applications <strong>for</strong><br />
<strong>in</strong>ternal LV use<br />
– Development of processes / methods <strong>for</strong><br />
updat<strong>in</strong>g <strong>in</strong>ternal databases us<strong>in</strong>g digital plans
<strong>ePlan</strong> Implementation Project<br />
• National Activities<br />
– Management of the <strong>ePlan</strong> protocol<br />
– F<strong>in</strong>alisation and management of<br />
support<strong>in</strong>g documentation<br />
• Model governance document<br />
• Enumeration lists / LV requirements / examples<br />
• Vendor Guidel<strong>in</strong>es<br />
– National Specification <strong>for</strong> the<br />
Structure of <strong>ePlan</strong> Files<br />
– Visualisation of <strong>ePlan</strong> files<br />
– Coord<strong>in</strong>ation of Draft<strong>in</strong>g / <strong>Survey<strong>in</strong>g</strong><br />
Application Vendors
<strong>ePlan</strong> Implementation Project<br />
• Timel<strong>in</strong>e summary<br />
– Bus<strong>in</strong>ess Requirements<br />
• July – December 2010<br />
– Solution Design<br />
• December 2010 – February 2011<br />
– Specification<br />
• March – April 2011<br />
– Development<br />
• April – June 2011<br />
– Test<strong>in</strong>g<br />
• July – September 2011<br />
– Pilot<strong>in</strong>g<br />
• June 2011 ongo<strong>in</strong>g<br />
– Production<br />
• September 2011
<strong>ePlan</strong> Bus<strong>in</strong>ess Case<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Bus<strong>in</strong>ess Case<br />
• LV commissioned Dench McClean Carlson<br />
to produce a draft Bus<strong>in</strong>ess Case<br />
• Dench <strong>in</strong>terviewed key LV stakeholders<br />
(Subdivision Branch, OSG, SII) and<br />
(a limited number of) surveyors<br />
• Three Options<br />
– Base Case - do noth<strong>in</strong>g<br />
– Option 1 - data based on <strong>ePlan</strong><br />
– Option 2 - data based on exist<strong>in</strong>g proprietary<br />
data <strong>for</strong>mat, e.g. dwg, dxf
<strong>ePlan</strong> Bus<strong>in</strong>ess Case<br />
Summary<br />
Base Case<br />
Option 1<br />
Option 2<br />
Budget ($)<br />
Nil<br />
$2.7M<br />
$2.7M +<br />
(See note <strong>in</strong><br />
2.10.2)<br />
Benefits / Outcomes<br />
Nil<br />
Critical step <strong>in</strong> the process of achiev<strong>in</strong>g a survey<br />
accurate map base<br />
Improved quality of data <strong>in</strong> and out of database<br />
which will result <strong>in</strong> efficiency ga<strong>in</strong>s <strong>for</strong> all<br />
database users<br />
<strong>ePlan</strong> tied to proprietary <strong>for</strong>mat<br />
Departure from national direction<br />
Inefficient system from validation perspective<br />
Some benefits identified <strong>for</strong> all stakeholders<br />
Additional costs to redo work completed to date<br />
based around different <strong>for</strong>mat<br />
Delay to realise sav<strong>in</strong>gs and efficiencies from <strong>ePlan</strong>
<strong>ePlan</strong> Bus<strong>in</strong>ess Case<br />
• Initially, <strong>ePlan</strong>s will deal with approximately<br />
60% of subdivisions <strong>in</strong> <strong>Victoria</strong><br />
- further work needed <strong>for</strong> other 40% of plans<br />
• Uptake will <strong>in</strong>crease progressively over<br />
(at least) five years<br />
• Benefits are relatively small and net benefits smaller<br />
• Implementation costs to many users<br />
(particularly surveyors) may be significant
<strong>ePlan</strong> File Structure<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> File<br />
• <strong>ePlan</strong> Model is a conceptual model <strong>for</strong> cadastral survey<br />
data <strong>in</strong> Australia and New Zealand<br />
• LandXML has been chosen as the schema to implement<br />
the <strong>ePlan</strong> Model<br />
• The <strong>ePlan</strong> has been designed so that it can be adapted<br />
<strong>for</strong> specific jurisdictional requirements while still<br />
con<strong>for</strong>m<strong>in</strong>g to the LandXML standard<br />
• Extension is CIF (stands <strong>for</strong> Cadastral In<strong>for</strong>mation File)
<strong>ePlan</strong> File<br />
LandXML<br />
subset<br />
<strong>ePlan</strong><br />
extended by<br />
<strong>Victoria</strong>n Specific<br />
Data
What is LandXML?<br />
• A specialized XML<br />
data file <strong>for</strong>mat<br />
• Conta<strong>in</strong>s civil<br />
eng<strong>in</strong>eer<strong>in</strong>g and<br />
survey measurement<br />
data<br />
• Can be used <strong>in</strong> the<br />
Land Development<br />
and Transportation<br />
Industries
LandXML Data Model<br />
Adm<strong>in</strong>istrative Data<br />
• Project<br />
– Project name and description, date<br />
• Application<br />
– Application used to produce the data, version<br />
• Author<br />
– Who created the data?<br />
• Units<br />
– L<strong>in</strong>ear, angular, area, time, temperature, pressure, diameter, volume, flow and velocity<br />
– Elevation unit and Lat/Long Angular unit<br />
• Coord<strong>in</strong>ate Systems<br />
– Grid and Projected coord<strong>in</strong>ate systems<br />
• Survey<br />
– Equipment, and data collection parameters<br />
– Optical, EDM and GPS supported<br />
– Personnel, survey<strong>in</strong>g company<br />
– Annotations<br />
– Acts<br />
– Field book data: raw and reduced survey observations<br />
– Scale Factor
LandXML Data Model<br />
Design Geometry Data<br />
• Po<strong>in</strong>ts<br />
– The basic 3D po<strong>in</strong>t with name, number, description, code and<br />
purpose<br />
– All po<strong>in</strong>ts support Latitude, Longitude, ellipsoid elevation<br />
attributes<br />
• L<strong>in</strong>e<br />
– Contiguous l<strong>in</strong>es, circular curves, spirals, irregular l<strong>in</strong>es and<br />
cha<strong>in</strong>s<br />
• Parcels<br />
– Area, centroid, owner, class, type<br />
– 3D parcel volumes<br />
• Monuments<br />
– Survey monument data<br />
– Survey order, class, type, description
LandXML Data Model<br />
Design Geometry Data<br />
• Alignments<br />
– Road centerl<strong>in</strong>e 2D coord<strong>in</strong>ate geometry<br />
– Profiles: vertical design alignments and sampled ground profiles<br />
– Cross Sections: design cross sections (1.1) and<br />
sampled surface sections<br />
– Superelevations<br />
– Station Equations<br />
• Surfaces (digital terra<strong>in</strong> models)<br />
– TIN – The computed Triangulated Irregular Network of<br />
3-po<strong>in</strong>t triangle faces<br />
– Grid – 4-po<strong>in</strong>t grid faces<br />
– Source Data: breakl<strong>in</strong>es, contours and po<strong>in</strong>ts used to compute<br />
the TIN or GRID<br />
• PlanFeatures<br />
– Generic geometric data like fence l<strong>in</strong>es, as-built data (curbs, build<strong>in</strong>g<br />
outl<strong>in</strong>es, etc.)
<strong>Victoria</strong>n Specific Data<br />
• Adm<strong>in</strong>istrative area list<br />
– LGA list<br />
– Parish list<br />
• Annotation def<strong>in</strong>itions list<br />
– Covenants, Owners Corporation Limitation<br />
• Jurisdiction enumerated types<br />
– Easement purpose : Water, power l<strong>in</strong>e, …<br />
– Monument type: Bolt, Plug, Disc, …
<strong>ePlan</strong> Applications - Overview<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Process Loop<br />
<strong>ePlan</strong> Validation<br />
& Visualisation<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong> Preparation<br />
Work Station<br />
Vicmap Property VOTS LANDATA SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Data<br />
Delivery Service<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database
<strong>ePlan</strong> <strong>in</strong> Third-party Software<br />
• A mechanism to prepare an<br />
<strong>ePlan</strong> file by surveyors<br />
– Upgraded pack of the current<br />
draft<strong>in</strong>g / survey<strong>in</strong>g application<br />
vendors packages that can export to<br />
<strong>ePlan</strong><br />
– Some software already exports to<br />
LandXML but need to be tailored <strong>for</strong><br />
<strong>ePlan</strong><br />
– Engagement with the draft<strong>in</strong>g /<br />
survey<strong>in</strong>g application vendors on a<br />
regular basis<br />
– National approach will be an<br />
<strong>in</strong>centive <strong>for</strong> the vendors<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
<strong>ePlan</strong> Validation Application<br />
• Self check<strong>in</strong>g facility <strong>for</strong> surveys to<br />
reduce requisitions<br />
• Prelim<strong>in</strong>ary exam<strong>in</strong>ation facility <strong>for</strong><br />
Land <strong>Victoria</strong> to facilitate the<br />
exam<strong>in</strong>ation process<br />
• <strong>ePlan</strong> validation application<br />
– will be embedded <strong>in</strong> SPEAR<br />
– will communicate with the third-party<br />
software<br />
– will be available <strong>in</strong> a stand-alone web<br />
page<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
• Equipped with validation report<strong>in</strong>g<br />
– identification of errors<br />
– prompt<strong>in</strong>g to errors<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
<strong>ePlan</strong>-enabled SPEAR<br />
• Version of SPEAR with<br />
capabilities of<br />
– upload<strong>in</strong>g<br />
– validat<strong>in</strong>g<br />
– visualis<strong>in</strong>g and<br />
– locat<strong>in</strong>g <strong>ePlan</strong> files, and<br />
– annotat<strong>in</strong>g the validation report<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
Computer-assisted Exam<strong>in</strong>ation<br />
• Automat<strong>in</strong>g the exam<strong>in</strong>ation<br />
process<br />
• Mak<strong>in</strong>g queries on digital plans<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
• Reduc<strong>in</strong>g exam<strong>in</strong>ers’ work load<br />
by modell<strong>in</strong>g the exam<strong>in</strong>ation<br />
steps <strong>in</strong> a software package<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
• L<strong>in</strong>ked to VOTS, Vicmap, SMES,<br />
etc to facilitate content validation<br />
– e.g. title verification<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
Updat<strong>in</strong>g Databases<br />
• Interface <strong>for</strong> updat<strong>in</strong>g<br />
– Vicmap property<br />
– VOTS<br />
– SMES<br />
– ….<br />
• Interface between <strong>in</strong>ternal<br />
databases and <strong>ePlan</strong> Data<br />
Delivery Application<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
• Interface between SPEAR<br />
and <strong>in</strong>ternal database<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
<strong>ePlan</strong> Data Delivery Application<br />
• Onl<strong>in</strong>e application <strong>for</strong> extract<strong>in</strong>g<br />
data from<br />
– the <strong>ePlan</strong><br />
– Vicmap property, and<br />
– VOTS databases<br />
• Comb<strong>in</strong><strong>in</strong>g the extracted data to<br />
create a LandXML file<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
• Third-party software will<br />
communicate with this<br />
application to create<br />
an <strong>ePlan</strong> file<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
Download<strong>in</strong>g Content <strong>for</strong> <strong>ePlan</strong> Files<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
Data Delivery Service<br />
• Pre-populate <strong>ePlan</strong>s with exist<strong>in</strong>g<br />
data<br />
– Vicmap<br />
– SMES<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
– VOTS<br />
– Other new databases<br />
• Adm<strong>in</strong>istrative and Graphical<br />
data<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
• Integrate exist<strong>in</strong>g survey data<br />
sources, mak<strong>in</strong>g it easier and<br />
quicker to per<strong>for</strong>m survey<br />
search<strong>in</strong>g<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
Data Delivery Service<br />
• What is it?<br />
– An <strong>in</strong>teractive map-based search (similar to LASSI)<br />
– Download pre-populated <strong>ePlan</strong>s<br />
– Download PDF documentation<br />
• Abstract and Surveyor’s Report<br />
– Data available <strong>in</strong>cludes:<br />
• Parcel view<br />
• Road names<br />
• Adm<strong>in</strong> Boundaries<br />
• Addresses<br />
• Survey and SMES labels
Data Delivery Service<br />
• How will surveyors use it?<br />
Client Request<br />
Quote Data Discovery 1<br />
Quick search <strong>for</strong> quot<strong>in</strong>g<br />
purposes.<br />
- Mapbase (LASSI)<br />
Job Init<br />
Plan Design<br />
Field/Desk Survey<br />
Draft Plan<br />
Beg<strong>in</strong> SPEAR Process<br />
Data Discovery 2<br />
Data Discovery 3<br />
Comprehensive search<br />
-Sometimes use<br />
professional searcher<br />
-LANDATA, ACSV<br />
broker(s), VicMap<br />
(LASSI), SMES<br />
-Titles, Plans, AFRs,<br />
Survey Reports, …<br />
Follow up search<br />
-No marks left from<br />
previous surveys, look at<br />
older surveys.<br />
-PMs destroyed, go to<br />
SMES <strong>for</strong> other PMs (<strong>for</strong><br />
MGA connection)
Data Delivery Service<br />
• Features <strong>in</strong> depth<br />
– Search<br />
• Lot/Plan; Vol/Fol; Address; etc<br />
• Buffer radius / polygon<br />
– Selection<br />
• Select data <strong>for</strong> download straight off the map<br />
– Preview<br />
• Highlight selected items on map or provide list of selected items <strong>for</strong><br />
confirmation<br />
– Download<br />
• Digital data file <strong>for</strong> import <strong>in</strong>to software package<br />
• PDF/image data <strong>in</strong> aggregated or separate files <strong>for</strong> pr<strong>in</strong>t<br />
– Save<br />
• Ability to save search session and load previous search
Screen Mockup<br />
Survey Data Interactive Search<br />
Selected Search Area (orange)<br />
Select <strong>for</strong> Download<br />
Preview AFR<br />
Preview Report<br />
Select <strong>for</strong> Download<br />
Preview SMES Report<br />
Preview Sketch Plan<br />
Preview Data List<br />
Save Search<br />
Download
Screen Mockup<br />
Survey Data Interactive Search<br />
Data Download Preview List<br />
Digital Data<br />
Parcels<br />
- 1\PS509066<br />
- 2\PS509066<br />
- etc<br />
Survey Marks<br />
- PCM113220054<br />
- PCM113220055<br />
- etc<br />
Documents<br />
AFR and Surveyors Reports<br />
- LP16100<br />
- PS313197<br />
- etc<br />
PM Sketch Plans<br />
Adm<strong>in</strong> Areas<br />
- LGA Moonee Valley<br />
- Parish Doutta Galla<br />
- etc<br />
Back to Map<br />
Save Search<br />
Download
Key Benefits <strong>for</strong> Surveyors<br />
• Surveyor is able to easily access up to date<br />
survey data<br />
• Pre-filled <strong>ePlan</strong>s reduce data entry ef<strong>for</strong>t<br />
• Reduce the possibility of data entry<br />
mistakes / typos
Prepar<strong>in</strong>g <strong>ePlan</strong> files us<strong>in</strong>g<br />
Third-party Software<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
Survey Software Packages<br />
• Currently work<strong>in</strong>g with<br />
software vendors to build <strong>in</strong><br />
<strong>ePlan</strong> functionality<br />
• First prototypes <strong>in</strong> com<strong>in</strong>g<br />
few months
Prepar<strong>in</strong>g an <strong>ePlan</strong><br />
• The process<br />
– Download pre-populated <strong>ePlan</strong> OR start from scratch<br />
– Enter all survey measurements and fix survey<br />
– Generate lots<br />
– Enter all secondary <strong>in</strong>terests e.g. easements and<br />
restrictions<br />
– Add notations where necessary<br />
– Software will provide screens to populate adm<strong>in</strong> data<br />
(normally on page 1)<br />
– * Validate from with<strong>in</strong> software<br />
– Export to <strong>ePlan</strong>
Plan Preparation<br />
• Differences to current plan prep processes<br />
– The whole plan is prepared <strong>in</strong> one package (probably<br />
the survey<strong>in</strong>g / calcs package)<br />
– Features such as easements that are traditionally<br />
drawn are now entered with dimensioned boundaries.<br />
• e.g. <strong>in</strong>stead of just draw<strong>in</strong>g easement boundaries and stat<strong>in</strong>g<br />
the width, now the boundaries are entered with dimensions<br />
• same <strong>for</strong> restriction footpr<strong>in</strong>ts (if applicable **)<br />
– Text / notations are typed <strong>in</strong>to the package and stored<br />
rather than captured as dumb text <strong>in</strong> a CAD file
The Details<br />
• What an <strong>ePlan</strong> file captures<br />
– Plan Adm<strong>in</strong> Info (i.e. cover page <strong>in</strong>fo)<br />
– Plan Diagram data<br />
– Survey control traverse<br />
• All travers<strong>in</strong>g from PMs, PCMs and RMs<br />
– Most surveyors report <strong>in</strong>fo <strong>in</strong>clud<strong>in</strong>g<br />
• Datum <strong>in</strong>fo, datum sw<strong>in</strong>g<br />
• Some adoption <strong>in</strong>fo (plan references and free text notations)<br />
• What an <strong>ePlan</strong> file doesn’t capture<br />
– Occupation<br />
– Surveyors will be required to cont<strong>in</strong>ue prepar<strong>in</strong>g an Abstract of<br />
Field Records outl<strong>in</strong><strong>in</strong>g the relationship to occupation<br />
– Currently do not have the capacity to capture occupation <strong>in</strong><br />
<strong>ePlan</strong> without significant changes<br />
– One step at a time
Some Examples
Some Examples
Summary<br />
• <strong>ePlan</strong> will require changes to<br />
– survey<strong>in</strong>g software<br />
– plan preparation processes<br />
– plan creation m<strong>in</strong>dset<br />
• <strong>ePlan</strong> will gradually move us from a<br />
“draw<strong>in</strong>g”-oriented m<strong>in</strong>dset to a<br />
“data”-oriented m<strong>in</strong>dset
Validat<strong>in</strong>g <strong>ePlan</strong> Files<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Validation<br />
• Pre-exam<strong>in</strong>ation validations<br />
– Identifies potential issues be<strong>for</strong>e lodgement<br />
– Ability to annotate each validation rule<br />
• Ensures completeness and consistency of <strong>ePlan</strong>s<br />
– Survey Accuracy<br />
• Adjustment discrepancies – area, misclosures<br />
• Internal consistency – owners corporation setup, multipart parcels<br />
• External consistency – mark names, addresses<br />
– Survey Exam<strong>in</strong>ation Rules<br />
• Mandatory fields – road / reserve vest<strong>in</strong>g authorities<br />
• Appropriate title connections<br />
• Connection of reference marks<br />
• Easement fix<strong>in</strong>g
<strong>ePlan</strong> Validation - Categories<br />
• <strong>ePlan</strong> Rules<br />
– LandXML structural consistency<br />
– Should be handled by vendor packages<br />
– Examples:<br />
• VR001 – <strong>ePlan</strong> CIF Schema Validation<br />
• VR003 – Multipart Parcel Completeness<br />
• Exam<strong>in</strong>er Rules<br />
– Manual rules that exam<strong>in</strong>ers may apply dur<strong>in</strong>g <strong>for</strong>mal validation<br />
– Most will show up as “For In<strong>for</strong>mation Only”<br />
– Examples:<br />
• VR020 – Date of Survey Plan Manual Check<br />
• VR051 – Easement Purpose Manual Check
<strong>ePlan</strong> Validation - Categories<br />
• External Rules<br />
– Check values aga<strong>in</strong>st Land <strong>Victoria</strong> data sources<br />
– Examples:<br />
• VR040 – Address <strong>in</strong> Vicmap Address<br />
• VR041 – Title Reference <strong>in</strong> VOTS<br />
• VR044 – Road Name <strong>in</strong> Vicmap Transport<br />
• VR075 – Permanent Mark <strong>in</strong> SMES
<strong>ePlan</strong> Validation - Categories<br />
• Survey Rules<br />
– Surveyor General’s survey requirements<br />
– Land <strong>Victoria</strong>’s bus<strong>in</strong>ess exam<strong>in</strong>ation rules<br />
– <strong>Victoria</strong>n <strong>ePlan</strong> model con<strong>for</strong>mance<br />
– Examples:<br />
• VR025 – Primary and Secondary Purpose Comb<strong>in</strong>ation<br />
• VR045 – Road Vest<strong>in</strong>g<br />
• VR047 – Easement Benefit<br />
• VR052 – Easement Fix<strong>in</strong>g<br />
• VR061 – Owners Corporation <strong>for</strong> Created Common Property<br />
• VR071 – Parcel Observation Closure<br />
• VR073 – Title Connection
<strong>ePlan</strong> Validation - Results<br />
Pass<br />
Warn<strong>in</strong>g – Requires Input<br />
Fail – Requires Fix<strong>in</strong>g<br />
For In<strong>for</strong>mation Only<br />
Skipped – Not applicable or skipped due to previous fail<br />
conditions
Validation Report - Examples
Validation Report - Examples
Validation Report - Examples
Validation Report - Examples
Summary<br />
• Rules are <strong>for</strong> quality assurance purposes<br />
• Critical errors will not reach Land <strong>Victoria</strong> thus<br />
reduc<strong>in</strong>g requisitions<br />
• About 80 rules so far<br />
• Not all will be <strong>in</strong> <strong>in</strong>itial release
Visualis<strong>in</strong>g <strong>ePlan</strong> Files<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Visualisation Application<br />
• A facility that provides the equivalent visualisation<br />
features available <strong>in</strong> paper / image / PDF plans<br />
• Ability to view plan <strong>in</strong> a graphical <strong>for</strong>mat <strong>in</strong> the same<br />
manner that it is displayed on paper or image / PDF<br />
<strong>for</strong>mats<br />
• Ability to view non-graphical data <strong>in</strong> an organised <strong>for</strong>mat<br />
that is easy to read and search
Need <strong>for</strong> Visualisation Application<br />
• Rely<strong>in</strong>g on visualisation of <strong>ePlan</strong> files prepared by<br />
surveyors creates issues<br />
• It <strong>in</strong>volves import<strong>in</strong>g / export<strong>in</strong>g data and human<br />
<strong>in</strong>tervention<br />
• Visualisation of the <strong>ePlan</strong> file might not be a correct<br />
representation of the data file<br />
• The exam<strong>in</strong>ation process us<strong>in</strong>g the visualisation<br />
provided by the surveyor may have used different data<br />
from the updat<strong>in</strong>g of the cadastre us<strong>in</strong>g the <strong>ePlan</strong> file
Available Viewers<br />
• Qld <strong>ePlan</strong> viewer<br />
– Based on open source products<br />
– PDF output<br />
• NSW <strong>ePlan</strong> viewer<br />
– Based on a proprietary<br />
– Web-based on screen and PDF outputs<br />
• LandXML.org generic LandXML viewer<br />
– Open source graphical LandXML-1.0 and 1.1 viewer<br />
based on .NET<br />
– Open source graphical LandXML-1.0 based on Java<br />
• Google Map / Google Earth Viewers<br />
– Based on API and file conversion<br />
– Web based on screen
<strong>ePlan</strong> Visualisation Application<br />
• Different views <strong>for</strong> users<br />
– Plan of Subdivision view<br />
– Title Diagram view<br />
– Abstract of Field Records view<br />
– Surveyor’s Report view<br />
– Council view<br />
– Land developers’ view<br />
– Conveyanc<strong>in</strong>g view
Current Status <strong>in</strong> <strong>Victoria</strong><br />
• High level requirements have been specified<br />
• Some sample <strong>Victoria</strong>n <strong>ePlan</strong> files were tested aga<strong>in</strong>st<br />
Qld visualisation application, Google Map and<br />
Google Earth<br />
• Detailed requirements will be specified<br />
• Work<strong>in</strong>g on a national approach based on Qld’s<br />
visualisation application
Creat<strong>in</strong>g an Application with<br />
an <strong>ePlan</strong> <strong>in</strong> SPEAR<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Process Loop<br />
<strong>ePlan</strong> Validation<br />
& Visualisation<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong> Preparation<br />
Work Station<br />
Vicmap Property VOTS LANDATA SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Data<br />
Delivery Service<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database
Upload<strong>in</strong>g an <strong>ePlan</strong>
Details View
Document View
Exam<strong>in</strong><strong>in</strong>g and Register<strong>in</strong>g <strong>ePlan</strong> Files<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong>-enabled SPEAR<br />
• Version of SPEAR with<br />
capabilities of<br />
– upload<strong>in</strong>g<br />
– validat<strong>in</strong>g<br />
– visualis<strong>in</strong>g and<br />
– locat<strong>in</strong>g <strong>ePlan</strong> files, and<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
– annotat<strong>in</strong>g the validation<br />
report<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
Exam<strong>in</strong><strong>in</strong>g <strong>ePlan</strong> Files<br />
• Extend the functionality of the “Land <strong>Victoria</strong>”<br />
screens <strong>in</strong> SPEAR<br />
• SPEAR data can populate exist<strong>in</strong>g and new<br />
VOTS exam<strong>in</strong>ation screens<br />
• Exam<strong>in</strong>ers will be able to use the visualisation<br />
application to verify the <strong>ePlan</strong> data<br />
• Exam<strong>in</strong>ers will be able to use the validation<br />
application
Lodgement Screen
<strong>ePlan</strong> Validation Application<br />
• Self check<strong>in</strong>g facility <strong>for</strong> surveys to<br />
reduce requisitions<br />
• Prelim<strong>in</strong>ary exam<strong>in</strong>ation facility <strong>for</strong><br />
Land <strong>Victoria</strong> to facilitate the<br />
exam<strong>in</strong>ation process<br />
• <strong>ePlan</strong> validation application<br />
– will be embedded <strong>in</strong> SPEAR<br />
– will communicate with the third-party<br />
software<br />
– will be available <strong>in</strong> a stand-alone web<br />
page<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
• Equipped with validation report<strong>in</strong>g<br />
– identification of errors<br />
– prompt<strong>in</strong>g to errors<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
Computer-assisted Exam<strong>in</strong>ation<br />
• Automat<strong>in</strong>g the exam<strong>in</strong>ation<br />
process<br />
• Mak<strong>in</strong>g queries on digital plans<br />
<strong>ePlan</strong><br />
Validation Web<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
(Enhanced<br />
SPEAR)<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
• Reduc<strong>in</strong>g exam<strong>in</strong>ers’ work load<br />
by modell<strong>in</strong>g the exam<strong>in</strong>ation<br />
steps <strong>in</strong> a software package<br />
<strong>ePlan</strong><br />
Preparation<br />
Work Station<br />
(Enhanced CAD<br />
Software)<br />
VicMap Property VOTS LANDATA<br />
SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
• L<strong>in</strong>ked to VOTS, Vicmap, SMES,<br />
etc to facilitate content validation<br />
– e.g. title verification<br />
<strong>ePlan</strong> Delivery<br />
Web Service<br />
(Enhanced<br />
LANDATA)<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database<br />
(Enhanced<br />
VOTS)
Exam<strong>in</strong><strong>in</strong>g <strong>ePlan</strong> Files<br />
• New Land <strong>Victoria</strong> project <strong>for</strong><br />
“Computer-assisted Exam<strong>in</strong>ation”<br />
• New VOTS exam<strong>in</strong>ation screens<br />
• New exam<strong>in</strong>ation processes<br />
• <strong>ePlan</strong> data can populate exist<strong>in</strong>g and new VOTS<br />
exam<strong>in</strong>ation screens<br />
• Exam<strong>in</strong>ers will be able to use the visualisation<br />
application<br />
– Creation of “Plan of Subdivision” view<br />
– Creation of “Title Diagram” view<br />
– Creation of “Abstract of Field Records” view
Updat<strong>in</strong>g Land In<strong>for</strong>mation Data Bases<br />
<strong>ePlan</strong><br />
Electronic Plans of Subdivision
<strong>ePlan</strong> Process Loop<br />
<strong>ePlan</strong> Validation<br />
& Visualisation<br />
Service<br />
<strong>ePlan</strong>-enabled<br />
SPEAR<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Database<br />
<strong>ePlan</strong> Preparation<br />
Work Station<br />
Vicmap Property VOTS LANDATA SMES<br />
<strong>ePlan</strong><br />
Exam<strong>in</strong>ation<br />
Workstations<br />
<strong>ePlan</strong> Data<br />
Delivery Service<br />
<strong>ePlan</strong> Database<br />
Server<br />
<strong>ePlan</strong><br />
Registration<br />
Database
Updat<strong>in</strong>g Databases<br />
• Automat<strong>in</strong>g the updat<strong>in</strong>g of key land <strong>in</strong><strong>for</strong>mation<br />
data bases, e.g.<br />
– Vicmap<br />
– VOTS<br />
– SMES<br />
• Run as separate projects<br />
• Needs co-ord<strong>in</strong>ation with SII