AU2009101272A4 - Asset Management system - Google Patents

Description

P/00/012 Regulation 3.2 AUSTRALIA Patents Act 1990 ORIGINAL COMPLETE SPECIFICATION INNOVATION PATENT Invention Title: "ASSET MANAGEMENT SYSTEM" The following statement is a full description of this invention, including the best method of performing it known to us: 1 ASSET MANAGEMENT SYSTEM This invention relates to a method of operation of an asset management system using a surveying code so as to provide a complete 5 characterization of a site or asset being surveyed and displaying the data in a spreadsheet format. It is necessary in relation to local government authorities such as councils to have reports on infrastructure such as roads, buildings, services 10 including sewerage developments and pipelines during stages of development of such infrastructure. Such reports refer to relevant construction of this infrastructure and are known as "As Constructed" (AC) data or information. A vital component of this process is the involvement of public and private surveyors and service locators as they have the first 15 contact with AC data and are an integral component in the acquisition of AC data. AC data is provided by surveyors at regular intervals during construction and then reproduced as plans that identify the located construction materials and/or fittings used during development of the infrastructure. 20 The main problem surveyors have with the submission of AC data is incompatibility between plan drafting standards, the level of information noted on the plan and the audit process for each individual plan. A surveyor will identify and locate construction materials/fittings and then be required to 25 draft individual standard plans of AC data for different councils. However, drafting standards vary from council to council and often show a wide variance in what is required. Drafting standards require surveyors to manually input text based 30 options that are open to interpretation from individuals and do not allow for existing survey methodology to reduce raw field data into an electronic format.

2 AC surveys can best be described as any identification, location and recording of constructed materials/fittings within a works environment. The surveys are conducted during and after the completion of civil works to 5 provide a co-ordinated database of constructed works. Early reference to AC information was attained by the submission of 'engineering mark-ups'. These were replicas of the approved engineering drawings corrected to reflect construction and stamped as 'AS 10 CONSTRUCTED' on the plan. Traditionally, markings were made in red ink to indicate any design that had been changed during construction or highlighted by providing an easily recognisable asterisk (*) at areas of amendments. 15 Mark-ups were predominantly hand drawn in red ink to indicate if a location, level or materials/fitting was changed. If the plan was unmarked, then construction was as per design. Plans of this nature were easy to draft and submit. However, constant upgrading and monitoring had to be done to ensure plans were verified and changed at the time of construction. Some 20 common errors incurred during plan preparation were from: a. loss of original approved plans; b. loss of original marked-up plans; c. errors and omissions of data on plans; and d. acceptance that design was correct at construction without 25 survey. The production of said "engineering mark-ups" is still used today although their relevance in AC approval has decreased and is viewed for reference only. Councils require a new set of drawings that represent 30 constructed materials/fittings independent of design plans.

3 In view of advancements in technology and the inclusion of Computer Aided Drafting (CAD), councils now adopt various levels of sophistication towards identifying and referencing AC information but maintain a standard information request for infrastructure information on the following: 5 a. cadastre base, which includes spatial information that refers to land parcel boundaries and co-ordinates attained from corners and/or natural monuments that define a boundary and attribute information which includes lot and plan number area, road and street names, river and creek names, feature names, locality 10 names, alphabetic codes for tenure and numeric codes for local government, parish and locality; b. topographical and earthworks; c. roadworks; d. stormwater and roof water drainage; 15 e. water supply reticulation; f. sewerage reticulation; g. electricity; and h. road bridge and major culvert structures. 20 Hardcopy plans showing AC data is the first communication on constructed information for asset managers. Plans are drafted to standards that represent textual information on constructed assets. Drafting standards have been formulated from consultancy within council's and relevant agencies that best describes the asset they will possess and best enable 25 relevant personnel identify with the information displayed. Due to the numerous agencies requiring consultation and their individual interpretation on assets, no uniform drafting standard can be applied between government bodies. 30 Furthermore, drafting requirements are difficult to standardise and open to interpretation by the individual. Some errors discussed in the document 'As Constructed Audit Report-Information' from Gippsland Water 4 in 2003 that most often fail in audit reports are: a. insufficient location information, e.g. offsets, co-ordinates; b. maintenance structure numbering not in accordance with the existing system; 5 c. poor selection of location for valves, fireplugs and maintenance structures; d. presentation of the design does not meet the required standard; e. drawing scales not to standard; 10 f. lack of information supplied; and g. drawing titles do not meet the relevant locality authority's standard for title formatting. AC plans can be described as the final output of surveyed information. 15 The current standards require surveyed data to be manipulated from a Cartesian point into text format. This requires surveyors to maintain a vast knowledge of individual asset requirements and develop systems to aid the transformation of located points into text format. 20 ADAC (Asset Design and As Constructed) software is being adopted by a number of local councils within Queensland. Established in 2001, the aim of ADAC is to initiate and support efficient transfer of As Constructed asset information between industry and councils. The further development of ADAC is subject to expansion on a local and national scale. 25 Developed as an additional software application for CAD programs, i.e. AutoCAD, users are able to manually input surveyed data on water, sewer, stormwater, roads and cadastre as a record of asset information. Data compiled within the software will be uniform for all users and should 30 allow a better approach to the extraction and utilisation of asset management and spatial information.

5 A 'ADAC Asset Categories' spreadsheet within the ADAC model highlights requirements for both engineers and surveyors on attribute information for individual assets. The spreadsheet outlines the requirements for data acquisition of individual asset infrastructure. 5 Information requirements are broken down into the following sub categories: a. asset type: defines what the asset is used; b. component panel: defines the structure and usage; 10 c. primary attribute: defines the information required for attribute data; d. secondary attribute: categorises the primary attribute into acknowledged terminology for further interpretation; e. field variables: input data for ADAC software; 15 f. description: general description of individual data requirement; g. mandatory field check: software will report an error message if data required is not noted; h. mandatory field conditions: further software application to check parameters for individual data; 20 i. ensure value is blank conditions: software application to allow for zero values for attribute data not required; j. character check: software application to check if values are entered; k. visible attribute: software application to display entered 25 information; 1. field name: assigning of inputted data to fields; and m. data type: assigning of inputted data as numeric or alpha characters. 30 ADAC software adopts a menu driven application for the definition of entities. Users define attributes in a text box and then assign these features to existing points/nodes or strings/lines. Stored data is defined as a 'block' 6 and can then be viewed and edited through the 'edit existing block' option within the software. At present the software does not allow for direct input of raw data from 5 surveying instruments and has limited ability in the manipulation of existing data. This means that ADAC requires adjoining software applications to manipulate and examine surveyed data. More specifically, ADAC is point and line based but does not give 10 definition on what determines a point/vertex or string/line as AC data. In relation to points and strings, these were determined by the surveyor or individual user without differentiation between a length component such as a pipe or point components such as fittings or structures located on the pipe. Thus, in other words, the user inserts all the data in relation to the asset into 15 the ADAC software and then he can draft strings and points. In relation to KEAYS software which is another form of software currently being used in relation to surveying and construction, it is noted that such software did not include a code that included an asset type field and 20 asset component field in combination and this lead to incomplete characterisation of the asset in some cases. Another deficiency of the KEAYS software was that it did not include a type of location field or an optional added depth field and again this lead to incomplete characterisation of the asset in some cases. Also, in relation to the KEAYS software, it 25 included a variable field known as a PLOT CODE which included a number of variables or fields which were time consuming in regard to data entry. It is therefore an object of the invention to provide a surveying code or format that will best describe elements involved in the AC data such as 30 construction material and/or fitting and also has provision for attribute information on the material or fitting. Formatting the code to individual elements and standardising a structured format will ensure easy identification 7 and classification while allowing the information to be displayed in a standard spreadsheet format or text document. The code will therefore include the following: 5 (i) a primary code which includes an asset type field and an asset component field; (ii) a designator code which includes a string field and/or point field wherein structure relevant to the string field is defined by an alignment of a pipe from a start point to a 10 termination point and a point field is defined by a structure or a fitting along a constructed pipe that forms a function of that pipe; and (iii) an attribute code which includes a type of location field, a location point field and an optionally added depth 15 field. The invention will therefore include operation of an asset management system which includes the steps of: (b) identifying an asset in terms of AC data and assembling the 20 data into individual fields utilizing the code as described above; and (c) directly transferring data from step (a) from survey software and/or hardware to a spreadsheet or text document to obtain a complete characterisation of the asset. 25 In relation to the asset type field, codes in this field will represent known asset services within sewer, stormwater, water and roads and allows the use of suitable acronyms to start the code procedure with respect to relevant construction materials/fittings used. Formatting these at the start of 30 the coding fields aligns users' knowledge to only components constructed within that service area. Examples of these codes are as follows: 8 CODE DESCRIPTION GS Gravity Sewer SRM Sewer Rising Main VC Vacuum Sewer PW Potable Water RW Recycled Water SW Stormwater G Gas COM Communication E Electricity RD Roads TOPO Topography SURV Survey BDY Boundary CHK Check Shot In relation to the asset component field, a code in this field describes 5 actual constructed pipes, fittings or structures. These acronyms will define the usage or function of the component within the asset service. Derived from the first letter of their description or the description itself some examples of these are: CODE DESCRIPTION LUG Line underground LAG Line aboveground HBD Horizontal Bend BGD Vertical Bend CBD Compound Bend JUIL Jump up Invert JUTP Jump UpTop 9 MH Manhole MS Maintenance Shaft PIT Pit GP Gully Pit AP Anti Ponding Pit GPT Gross Pollutant Trap LID Lid AV Air Valve GRV Gas Release Valve BV Butterfly Valve SV Stop/Scour Valve FH Fire Hydrant SH Swabbing Hydrant WM Water Meter RTAP Reddy Tap ETS Electrofusion Tapping Saddle EC End Cap DE Dead End R Reducer T Tee CHK Check Shot In regard to the string or point field, software applications now allow surveyors to connect a series of points together to define an alignment. This 5 is particularly important for As Constructed data as this allows for a service to be aligned correctly and calculate constructed grades directly from field observations. It is also within this field in accordance with the invention that the distinction between a constructed pipe (the string) and a constructed structure/fitting (the point) is clearly defined. 10 During construction, pipes are fitted together that define direction for 10 the asset. These pipes can be constructed to a design grade or aligned at a nominal direction and depth. Alignment of pipes will always have a start location and a termination point, thus individual string numbers can be assigned to different alignments. Even when a structure or fitting is 5 constructed that deflects the alignment, the alignment does not terminate until the end of the last pipe on that alignment. Therefore a string is defined as 'a series of points linked together that define a nominated pipe direction from start to finish; excluding structures and fittings along the pipeline'. 10 Individual fittings and structures constructed on the pipe are not considered part of the string, only a means to change the alignment and/or supply a service. These components are classified as points requiring an individual location and classification. Therefore a point is defined as 'a structure or fitting along a constructed pipe that forms a function of that pipe'. 15 Some examples of these are manholes, valves, hydrants, tees, end caps, etc. By giving a definition to strings and points, classification is made between what is constructed pipe alignment and what are fittings and/or 20 structures along the pipe. This is important for compiling As Constructed data as asset information requirements are different for pipes and structures/fittings: pipelines require a grade calculation while structures and/or fittings require a usage. 25 Putting the above definitions into practice will involve the surveyor to locate fittings and/or structures twice. One location will identify a code for the pipe alignment and the other location will record a code for the fitting or structure. This may appear excessive considering that you may be locating the same location twice; however, this procedure provides distinction 30 between pipe and fitting/structure and a redundant check observation. Procedures to implementing points and strings along pipelines are: 11 " String points that have the same location, i.e. invert to invert or top to top (Note: this is not the obvert level as to do this you require the located point to be inside the pipe at the top). " Adopt a general rule of thumb that sewer and stormwater 5 require invert levels while water, communications and electricity require top of pipe levels. " For concrete structures, locate pipe alignment at inlets and outlets as part of a continuous string (Note: If more than one inlet is apparent, start a new string number for the new pipe 10 alignment). Location for individual components of the structure such as invert of centre of manhole and lids are individual points and not part of the string. . For maintenance shaft structures, string through the invert of centre of structure for the pipe alignment (Note: If more than 15 one inlet is apparent, start a new string number from the same location) and attain another point at the same location for structure identification. " For water fittings, locate a point at the top of fitting for stringing the alignment, then locate the same point for identifying the 20 fitting. " When a constructed pipe diameter changes through a structure or fitting, start a new string number to define the new pipe diameter. 25 Existing computer software has the ability to perform functions with registered strings. A field can be established to identify a functional requirement for a particular string or point within existing software. Such functions could be to offset a string at a known value, draw a vertical shape above the strung alignment or point and close a string back to the start 30 position. This field will need to work in conjunction with operation functions described in existing survey software and be assigned values that correspond to computer programming for that software.

12 For the type of location field, this is required to provide evidence on how the recorded point was accessed and sighted prior to registration. This is important for future reference as by recording the methodology adopted in 5 registering the data, users can imply a relative 'accuracy' for individual data dependant on how accessible and visible the asset was prior to registration, i.e. a direct shot onto an asset provides better accuracy than a shot requiring manipulation through the inability to access and view the asset. 10 Surveyed As Constructed data is acquired at various times during and after construction, concluding only when all assets are located and recorded. For this reason it is impossible to assume that surveyors will have direct access to all assets for location and identification. At various times during acquisition of data, surveyors will have to manipulate or add data from to the 15 direct reading in order to reflect the location point required for the asset. Surveyors may also require the assistance of other agencies to locate assets that have been buried beneath the surface that are not visible within structures. 20 The 'Type of Location' field has been designed to identify how the located point on the asset was attained and imply a relative accuracy in terms of accessibility and visibility for the asset. Codes in this field will reflect the seven distinctive procedures that define how a located point is registered and rate them in order of implied accuracy and examples of these are set out 25 below, i.e. 1. Sighted (S) - The surveyor has visually sighted and certified that the recorded shot is directly on the asset. These records are given as the most accurate location method as these records have the greatest compliance 30 with accessibility and visibility; 2. Pothole (P) - If a service was buried prior to survey, potholes are used to verify the location of assets.

13 Potholing of buried assets is the only accurate way for the surveyor to access and visually sight the asset prior to registration as a recorded mark. Potholes allow for the surveyor to take a direct reading on the asset, 5 however, these are not considered as 'sighted' due to the fact that the asset only became visible with the assistance of a pothole; 3. Reflectorless (R) - Hardware capabilities for some theodolites allows for points to be located via a reflected 10 beam. This means that surveyors can register point location through sighting the instrument telescope at the required location. Whilst generally complying with accuracy for visibility, accessibility is low due to the fact that the recorded mark was attained with the aid of a 15 reflected beam that has limited ability for recording an independent check shot. Therefore, recorded marks registered by this procedure are given a lesser accuracy than pole measurements; 4. Electronic (E) - Electronic Radio Detection is given a 20 low accuracy and as such should only be interpreted as a probable projection for the assets location. This form of location functions on a machine's ability to locate a magnetic field generated through the asset. No accuracy can be given for any electronically located 25 information as located points fulfil none of the accuracy requirements; accessibility and visibility for the asset. Electronically located information should only be used as a last resort for registering As Constructed data after all other procedures to access and visually verify the 30 asset have been exhausted; 5. Calculated (C) - Records with this notation will indicate that the user has calculated an interpretation of where 14 the asset and/or alignments are projected from existing plans. These may be calculated from field observations of existing alignments or scaled interpretations from existing plans. Calculated points are any recorded 5 points that are not derived from direct survey and require a calculation from existing assets/alignments and/or plans to generate a position. These are also points generated in software applications to help align the asset infrastructure environment; 10 6. Records (RC) - This will be used when the user inputs pre-determined values and has no accuracy, however, this notation is required for user input of existing information that has been attained from others and supplied in order to perform survey,. Data noted with 15 this notation will generally be from surveyors inputting existing control points, calculated setout positions for assets and any data that will not be collected by a direct surveyed reading at the time of survey; and 7. Image () - With advancements in service location and 20 survey hardware, this notation is used to describe image data obtained from Ground Penetrating Radar, Remote Sensing and Laser Scanning techniques. Coded information with this notation will reflect information that has been derived from imagery 25 principles that do not conform to the code used in this invention, i.e. the data is derived from an enormous amount of single points that would be difficult to individualism and code. Therefore data coded with this notation can only reflect a single point in the image and 30 not the whole image. Accuracy assignment for this information will be derived from the hardware adopted to generate the image.

15 In regard to the location point field, after defining how the recorded mark was located and implying an accuracy for the located mark, this field will identify at what location on the asset the recorded mark was taken. 5 Examples of such location points are shown in Figure 1, which diagrammatically identifies the location points which are explained as: * Invert Level (IL) - The invert level is attained at the lowest level within the internal structure of pipe and/or the lowest level for the inside of a structure. 10 e Obvert Level (OL) - The obvert level is attained at the highest level within the internal structure of pipe and/or the highest level for the inside of a structure, excluding lid collars. e Top (TP) - A general comment to define located points that are: located externally of the pipe, structure or fitting and are 15 situated at the top of the pipe, structure or fitting. * Bottom (BM) - A general comment to define located points that are: located externally of the pipe, structure or fitting and are situated at the bottom of the pipe, structure or fitting. * Surface Level (SL) - Are recorded locations above ground 20 and/or at natural surface. * Concrete Encased (CE) - This code is used when the surveyor encounters fittings that have been concrete encased and none of the above will generate the location point on the asset. This form of location will still register the asset by its name while 25 identifying to users that the asset was not accessed or visible at the time of occupation; and * NONE (NONE) - This code is inserted as further classification for using electronic location devices when recording the location of assets. As stated above, these devices are unable 30 to specifically locate the position on an asset, so therefore no attribute data can be assigned as to the location point of the asset on the surface.

16 In regard to the optional field known as "Added Depth" this can be explained in relation to assets that may be at depths lower than the initial pole height, or are inaccessible or can only be attained by adding a 5 measured distance to the pole height. This process involves adding a measured depth, between pole location and asset, to the initial pole height and recording this calculation as the target height. This field will only contain two options, YES or NO and will be used later during the verification process. 10 Additional attribute fields which may have relevance include the following: (a) PIPE DIAMETER In regard to the pipe diameter field, this will contain numerical data that identify diameters and sizes for the internal or 15 external dimension of pipes only. Locations can then be correlated against the 'asset component' and the 'location point' fields to determine if the scribed dimension is an internal or external measurement. A general approach to scribing diameters is: if the size is printed and sighted on the material, 20 adopt this as the notation, otherwise adopt external circumference for pipes as this will be the easiest to attain and are able to be checked against manufacturing specifications. (b) LENGTH/DIAMETER 25 Fields are now inserted for structures along the pipe alignment. These will commonly be manholes, pits and Gross Pollutant Traps. Note is taken that notations in this field will also include fittings, e.g. valves, hydrants as these are built to a specific pipe diameter. 30 Notations in this field will refer to the diameter of the structure, the longest length of the structure and/or a pipe diameter for a fitting. Software applications will be able to distinguish 17 between a circular, rectangular or square structure by cross referencing the 'Class' field which contains choices for the shape of the structure. For circular structures, notation would only be inserted into this field with the next field blank and for 5 non-circular structures this field contains the first measurement of the structure. (c) WIDTH/HEIGHT In regard to the width/height field, notations in this field are a 10 measurement of the shortest length of a rectangular structure, the same as the length for a square structure and/or a height of an alignment, e.g. fencing. This notation is required for software applications to insert a box of correct width that visually displays the structures size or to enable a vertical 15 height assigned to a particular alignment. Orientation for individual structures can be rotated within software applications from notes made in the 'Comments'field, e.g. "90, Road Align, NW Cnr. Bdy Align", or if the surveyor requires location of all corners for the structure the 'Diameter' 20 Length' field and 'Width' field will hold zero values and the 'String/Point' field will contain a string number. For structures such as fencing, the 'Length/Height' field will hold a zero value while the notation shown in this field will assign a vertical height to a strung line at the bottom of the 25 fixture. (d) MATERIAL In regard to the material field, it will be appreciated that all pipes, structures and fittings are made from distinctive 30 materials and/or a combination of materials. Codes in this field reflect industry recognised acronyms for specific materials. For easy identification in the field, acronyms for material types 18 are printed on the outside of certain pipes and fittings, otherwise manufacturers supply documentation on the materials used for their products or design drawings will make note of what material is to be used for what service. 5 (e) CLASS The class is derived from individual classifications for different materials. Records in this field will be derived from notation on the pipe, structure or fitting, researched from manufactures' 10 standards or by notations on design drawings. (f) PROTECTION The protection of the material is defined as extra material added to pipes, structures or fittings that enable compliance 15 with construction standards. Due to the large number of different variations in protection material the surveyor will require contractors to identify any protection added to pipes, structures and fittings prior to survey. 20 (g) NUMBER OF CONDUITS The term conduit is used in this field and is described as 'A pipe or channel for conveying fluids, such as water and a tube or duct for enclosing electric wires or cable' (The Free Dictionary.com). This gives better terminology for the field 25 than assigning the term pipe; 'A hollow cylinder or tube used to conduct a liquid, gas or finely divided solid' (The Free Dictionary.com). Therefore, for the purpose of defining information in this field adopt the principle that a pipe and conduit are the same thing. 30 Information noted in this field will convey that multiple asset services are within the same trench. Predominantly found in communications and electricity services and identified through 19 potholing, this field allows for occasions when the surveyor is unable to individually locate a point on all service conduits/pipes within the pothole to any assured accuracy. By recording a located point and referencing that a number of 5 extra conduits/pipes were identified in the same trench, external users become aware that the recorded mark does not reflect a location for individual conduits/pipes but a location for a packet of conduits/pipes within a defined trench. 10 (h) DEPTH This field is important for the verification stage and as a notation for implied field measurements. The use of the measured depth for verification will be discussed in the next chapter but for quality assurance of field survey, any implied 15 measurement added to a recorded mark must be registered prior to occupation. Notations will reflect direct measurements from field observations that were used to manipulate the recorded mark onto the service. 20 (i) SERVICE PROVIDER All assets are owned by unique agencies. This field will identify the individual owner of the located asset. Examples of these are individual councils, communication providers, electricity providers, gas providers, etc. 25 (j) SERVICE CONDITION This field is inserted to allow external users a general indication on the condition of the asset. There will be only three options in this field being: 30 GOOD - The asset has just been constructed and not yet in use. FAIR - The asset is in use and visually has no apparent 20 damage. POOR - A visual inspection indicates that the asset has been damaged. 5 (k) SOIL TYPE This field is a generalisation of the soil type viewed within the trench or surrounding the trench. Whilst it is known that surveyors are not geologists, this field can be added for the surveyor to make a general comment on soil type. This field 10 will also only contain four options: SAND - Small grains of soil that loosely bond together to create a surface area. CLAY - Soils that bond together to become plastic when wet or hardened when dry and devoid of rocks. 15 SHALE - Soils that contain a mixture of clay soil and rocks. ROCK - Soil content is predominately rocky outcrops. (1) COMMENTS This field is added for any additional comments that are not 20 already covered by existing fields. Notations in this field will be made if the information requirements of the asset are not covered by existing fields and additional information will make classification easier. 25 (m) TARGET HEIGHT This field is added as a direct output from data collectors. The target heights will be used as verification for 'measured' field observations and discussed in the next chapter. 30 (n) DATE & TIME STAMP The code is completed with the date and time stamp for the located point. These are also direct outputs from the data 21 collectors indicating when the located mark was registered. In regard to format and structure of the code of the invention, the main concept to formatting the code is not the amount of characters shown but 5 more the approach to writing the code. This means that the code is developed step by step to show information in a structured format that follows known field categories. If information is not required you simply continue to the next field for information. This method gives multiple variations but designates a defined structure when referencing information. 10 The format for this code is constructed in three parts: primary, designator and attribute. The first part of the code will be to combine the first two fields together to define a single primary 'field code'. These field codes will be used to design map files and code libraries in existing survey software 15 that assign symbols, linestyles and layers or models for inputted data. The second part to the code, the designator, is for identification of the recorded mark as a point or string, while the final fields are assigned as attribute data for As Constructed information. This format is shown in FIG 2. 20 PREFERRED EMBODIMENTS OF THE INVENTION FIG 3 represents records required to identify a sewer line between two manholes. The line in phantom indicates a strung alignment for the pipes while centre of manholes (X) are point data to identify the manhole. 25 The code for pipes is explained as: a gravity sewer line underground (GSLUG); that will have points strung together (01, 02); the located mark was sighted (S); at the invert level location (IL); no depth was added to attain the located mark (NO); for a 150 (150); Unplasticized Polyvinyl Chloride pipe (UPVC); no length/diameter or width was recorded (, , ,); having a 30 manufactures classification of SN8 (SN8); and no protection added (, ,); only one pipe was located (1); the recorded mark did not require a depth measurement to attain (, ,); the asset is owned by the Gold Coast City 22 Council (GCCC); and the pipe was in good condition (Good); lying in Clay soil (Clay); no other comments are required to identify this pipe (, ,). The code for the manhole is explained as: a gravity sewer manhole 5 (GSMH); that was located as a point (, ,); the located mark was sighted (S); at the invert level location (IL); no depth was added to attain the located mark (NO); no pipe diameter was recorded (, ,); for a 1050 diameter (1050) no width (, ,); precast (P); circular manhole (CIRCULAR); that has two part epoxy protection added (E); there was no pipe located (, ,); the recorded 10 mark did not require a depth measurement to attain (, ,); the asset is owned by the Gold Coast City Council (GCCC); the manhole was in good condition (Good); lying in clay soil (Clay); no other comments are required to identify this manhole (, ,). 15 FIG 4 represents three constructed water pipes with a manufactured fitting (X) along the pipe alignment. The codes for the pipe whilst differing slightly between usage and size can be defined as; a recycled/potable water line underground 20 (RWLUG/PWLUG); that will have points strung together (01/02/03); the located mark was sighted (S); at the top of pipe (TOP); no depth was added (NO); for a 800/508 (800/508); no length/diameter or width was recorded (, , ,); Moulded Steel Concrete Lined pipe (MSCL); with a manufactures classification of PN35/PN21 (PN35/PN21); and had no protection added(, ,); 25 only one individual pipe was located (1); the recorded mark did not require a depth measurement to attain (, ,); the asset is owned by the Gold Coast City Council (GCCC); and the pipe was in good condition (Good); lying in Clay soil (Clay); no other comments are required to identify this pipe (, ,). 30 The codes for the manufactured fittings whilst differing slightly between pipe alignments can be defined as; a recycled/potable water 23 horizontal bend (RWHBD/PWHBD); that was located as a point (, ,); the located mark was sighted (S); at the top of pipe (TOP); no depth was added (NO);the fitting was 800/508 (800/508); no length/diameter or width was recorded (, , ,); Moulded Steel Concrete Lined (MSCL); with a manufactures 5 classification of PN35/PN21 (PN35/PN21); and had no protection added (, ,); only one pipe continues through the fitting (1); the recorded mark did not require a depth measurement to attain (, ,); the asset is owned by the Gold Coast City Council (GCCC); and the pipe was in good condition (Good); lying in Clay soil (Clay); other comments required to identify this fitting were the 10 design deflection angle stamped on the fitting (85.2/80/74.8). The only real difference between the code data for the gravity sewer and water line is found in the 'Number of Conduits' field for the manhole as opposed to the water fitting. Note that the number of pipes for the manhole 15 is null, while the number of pipes for the water fitting is one. This is because when one locates water fittings, the pipe technically continues through the fitting and does not terminate and start again at the outlet and water fittings do not allow for direct access for maintenance procedures. Manholes on the other hand traditionally cut the pipe at the inlet and resume pipe lying from 20 the outlet. Any structure that terminates the pipe at the inlet, then resumes pipe lying at the outlet, should have a null record for the number of pipes to indicate that the service within the structure is visible and accessible. Other examples of these are communication pits, electrical pits and stormwater pits. 25 FIG 5 represents an existing stop valve fitting constructed along a potable water pipe line. The codes for the stop valve fitting can be defined as: a potable water 30 stop valve (PWSV); that was located as a point (, ,); the located mark was sighted (S); at the top of the fitting on the pipe (TOP); a depth was added to the original pole height (YES); no diameter, length/diameter or width was 24 able to be verified (, , ,); the fitting was ductile iron (DI); with no classification (, ,); and had powder coating added for protection (PC); no pipe was located (, ,); the recorded mark required a depth measurement to attain the location of the pipe (0.95); the asset is owned by the Gold Coast City 5 Council (GCCC); and the fitting was in fair condition (Fair); not able to identify the soil type (, ,); no other comments are required to identify this fitting (, ,). The codes for the stop valve lid can be defined as: a potable water lid 10 (PWLID); that was located as a point (, ,); the located mark was sighted (S); at the top of lid (TOP); no depth was added (NO); no diameter of pipe (m, ,); the length of the lid was (300); with a width of (150); made of cast iron (Cl); the lid was rectangular (RECTANGULAR); and had no protection (, ,); no pipe was located (, ,); the recorded mark did not require a depth 15 measurement to attain (, ,); the asset is owned by the Gold Coast City Council (GCCC); and the fitting was in poor condition (Poor); not able to identify the soil type (, ,); comment gives explanation to the condition of the lid (Broken). 20 Validation Processes Due to the complex nature of the code structure and the sheer amount of information required for an individual location point, a series of validation processes may be introduced to verify recorded marks. This may involve two separate procedures with different verification processes. The 25 following will discuss a validation process to ensure users that the information is spatially correct and that recorded information is correctly referenced. (i) Survey Software 30 Survey software will verify the spatial integrity of recorded marks as well as providing a visual representation of recorded marks. Regardless of survey software adopted by users, the following validation process can be 25 implemented to verify direct input of the codes records. STEP 1. Verify that correct layers or models have been produced When the data is inputted through a map file or code library, distinct 5 layers or models will be created that reflect the field codes used. If any layer or model created does not correlate with the designed code library, investigate the data to ascertain which code is incorrect or requires manipulation. 10 STEP 2. Verify the string alignments Visual representation of strung alignments will appear on the screen. If any individual alignment does not correlate with those preceding, investigate the data to ascertain the correct direction. 15 STEP 3. Verify that individual components along pipe lines have been generated as a point As per the definition given for a point and string as described above, all individual components of a pipe line should have their own recorded mark. This means that a visual representation will reflect a 20 strung alignment and an individual point referenced at each component. This may vary depending on the component located but at any single component there must be a minimum of two recorded marks, one for the alignment and the other for the component. 25 STEP 4. Verify recorded marks to design drawings to determine if any design features have been omitted or change During construction, design elements within the development may require a variation for a particular reason. The purpose for submitting As Constructed information is to record these variations. Therefore 30 when checking recorded information against design drawings surveyors can only identify if a design elements has changed or been omitted from design.

26 STEP 5. Visually verify the data with the aid of overlay plans Computer software allows for importing of external information which may include design drawings or cadastral boundaries. By overlaying 5 this information onto recorded information users can identify errors and omissions inherent in their location such as: alignments outside of allocated boundaries and changes or omissions to design. STEP 6. Verify that all data has been imported and correctly labelled 10 This will be done by exporting a spread sheet of recorded information and running macro programs to verify the information represented electronically. (ii) Spreadsheet 15 The spreadsheet is used to verify individual components of the code, verify manipulated data and provide another avenue for future calculations and transfer of As Constructed data. To export recorded data from survey software to spreadsheet format 20 users must be able to export a Common-Separated Values (CSV) file, adopting commas or tabs as the delineator. Viewing this file in its raw state reveals information held in all coded fields. As the spreadsheet structure is the same as coded information, when imported into spreadsheet software the information is aligned in columns 25 (description of field) and rows (point identifiers). The advantages to using a spreadsheet to verify recorded information is that individual fields can be verified, manipulation of target heights can be checked, check shots can be used to verify corresponding 30 information, the spreadsheet itself can be used to calculate a dollar amount for located fittings/structures and spreadsheets are a structured format for inputting of data into Geographical Information 27 Systems (GIS) software. As the structure of the code is aligned to specific elements of As Constructed data, recorded fields within the data can be verified 5 against a 'master' document that contains all possible variations. A programme can be written that compares the master fields to those referenced in the As Constructed spreadsheet. Any non-conformities found can be flagged and examined to resolve the problem. 10 By constructing a master spreadsheet for verification purposes, external users are able to verify compiled data to ensure that any data transferred will comply with existing As Constructed data. This will also reduce errors inherent in the identification of assets by allocating a specific code for each asset. 15 Part of the reporting process includes noting for 'ADDED DEPTH'. When this field is indicated with a notation of 'YES', this implies that the surveyor has added a distance to their target height to attain the location on the asset. As this will be common when the depth 20 exceeds the pole height or the location point on the asset is not accessible, e.g. manhole and maintenance shaft structures, Gross Pollutant Traps and potholes, the recorded depth needs to be checked against the target height for verification. 25 For this validation process to be effective, the surveyor will need to be aware of his target height before manipulating the target height in the data collector to incorporate the measured distance and note the original setting of the pole height in the 'COMMENTS' field. 30 The validation process involves a simple mathematical equation that subtracts the depth from the registered target height and then compares this to the pole height noted in the comments field or to a 28 known pole height, i.e. survey poles can be set to a nominal height for the duration of survey. If the calculated number does not equal the number in the comments field or the known pole height, the record will be flagged for investigation. The above equation can be visually 5 represented by FIGURE 6. Once the target height has been validated the next process is to verify that the measurement attained between the surface and invert was correct. This is completed through the addition of an extra recorded 10 'check shot' at the same location point as the measured shot. By locating the same point twice, one for the location on the asset and one for the point on the surface, we can calculate the difference between the generated levels. This calculated difference can then be 15 checked against the 'Depth' notation to validate that the user has correctly applied methodology to manipulate the data via the target height. Also this calculation will generate an error between recorded marks which can be viewed as the spatial accuracy between field measurement and recorded information. 20 Users should note that this validation procedure does not check the initial field measurement made between the surface level and the asset. This validation only ensures that the target height has been manipulated with the recorded depth me4ausrement. 25 A practical example of this is in the location of structures and pits. The located point at the invert of an existing completed manhole will have a depth recorded for the distance between the lid to invert. Subtracting this invert level from the level attained for the manhole lid 30 produces a height difference that can be compared against the recorded depth for that manhole and display any error in measurements. This displayed error can also help explain 'survey 29 accuracy' for As Constructed. Note is made that if the surveyor was recording a pit or structure that was not complete, the depth would be recorded later when the lid was 5 constructed thus allowing for the verification process. This process also allows the user to determine the level of construction when the point was located. If the depth was recorded when the surveyor located the structure/pit it can be assumed the structure/pit was constructed, whilst if a depth was recorded when the surveyor located 10 the lid, it can be assumed that the structure/pit was under construction when the manhole was first located. By being able to generate a spreadsheet users have the ability to generate 'Quantity' evaluations. This will involve the assigning of a 15 dollar amount to individual codes within the data set. The theory is similar to existing "Bill of Quantity" spreadsheets, in that a simple formula can be written to count the number of times a particular code appears in the data. This generated number is then multiplied by a pre-determined dollar amount and displayed on the spreadsheet. 20 This will be particularly relevant when determining bonding amounts and evaluating expenditure within the development as the figures generated will only reflect constructed materials/fittings that have been located by survey. 25 Most GIS software applications use tables to store and manipulate data. These tables are structured to a format that stores certain information within certain fields. The spreadsheet generated from 'actual' surveyed information is similar in design and can be used to 30 input data directly into software applications and perform graphical and/or analytical modelling.

30 Surveyed information is recorded in a structured format allowing GIS software to read a formatted spreadsheet and assign values by column and row. This allows for the data to be registered similar to the way it was assigned in the field, i.e. for Row 1 adopt: column 1 = 5 Point ID, column 2 = Easting, column 3 = Northing, etc; for Row 2 adopt: column 1 = Point ID, column 2 = Easting, etc. Similar to survey software, the added value to importing data into GIS software is for further verification of recorded data in respect of 10 location and identification. Local government agencies have GIS software that holds information on asset recognition and location. This existing information is often interpolated from existing plans and not a surveyed location. The 15 advantage to direct inputting of surveyed information is that the all points have a surveyed accuracy and as such, show the asset in a real time location referenced to a co-ordinate datum. This is particularly useful for maintenance as users will be able to locate the asset through survey and not rely on the accuracy of drafted plans. 20 A further advantage to the structure of the code is that extra fields can be added within the spreadsheet to allow for other information requirements particularly to that agency. A suitable spreadsheet using the code of the invention is attached herewith as FIG 7(a) and 25 FIG 7(b). Advantages of use of the code of the invention in an asset management system include the following: (i) The system allows for coding on all individual assets which are 30 collected in data sets representing constructed assets. By allocating individual codes for identification with the code system of the invention users can better clarify the individual components within the 31 assets service for reporting purposes. (ii) The structured format of the recorded data is such that when the initial point is located, information pertaining to the asset, i.e. 5 identification, location and time of acquisition are automatically assigned to the recorded mark. This methodology reduces the need for additional information to be scribed after initial contact and will help in reducing errors and omissions from having to remember elements of an asset after visual confirmation in the field. 10 The layout using the code of the invention also allows for the information to be directly inputted into various software applications for surveying, GIS and reporting procedures, e.g. spreadsheets. 15 (iii) The code system of the invention is written and structured so that the most amount of usable asset information is logged at the initial point of contact. Surveyors already adopt code systems to identify and describe located information so the code of the invention is an extension of existing methodology. 20 The descriptive codes will better clarify information attained by surveyors from initial visualisation and location, whilst providing a standard structured format for data that can be transferred between government agencies. 25 Inputting of data directly into software applications will reduce the amount of errors and omissions found when users have to manually input additional information. 30 With the additional software applications the code of the invention can be directly inputted into; further analysis on the integrity of data can be measured to enhance the accuracy of the data whilst reducing 32 costs attributed to the manipulation and transferring of data into other software applications. Further cost reductions are anticipated in the timeframes for approvals by adopting a singular standard format that all external users can use. 5 (iv) The code of the invention is adaptable to most existing software application by virtue of the fact that the data is registered in a structured format. A simple ascii text document can sustain transfer of data into survey software, while the creation of a spreadsheet will 10 facilitate transfer into GIS software. Note is made that certain parameter files need to be constructed within individual software applications, however, this is a minor hindrance when considering that the initial data can be transferred to multiple software without manipulation. 15 At present the code of the invention may be recorded and formatted in a Leica data collector with recorded information being directly inputted into 12d, Microsoft Excel and Mapinfo software. Other hardware and software may also be used.

Claims (5)

1. A method of operation of an asset management system which includes the steps of: 5 (a) identifying an asset in terms of As Constructed (AC) data and assembling the data into individual fields utilising a code which includes 1. a primary code which includes an asset type field and an asset component field; 10 2. a designator code which includes a string field and/or point field wherein structure relevant to the string field is defined by an alignment of a pipe from a start point to a termination point and a point field is defined by a structure or a fitting along a constructed pipe that forms 15 a function of that pipe; and

3. an attribute code which includes a type of location field, a location point field and an optionally added depth field; and (b) directly transferring data from step (a) from survey software 20 and/or hardware to a spreadsheet or text document to obtain a complete characterisation of the asset. 2. A method as claimed in claim 1, wherein the asset type field is represented by at least one of the following: 25 CODE DESCRIPTION LUG Line underground LAG Line aboveground HBD Horizontal Bend BGD Vertical Bend CBD Compound Bend JUIL Jump up Invert 34 JUTP Jump Up Top MH Manhole MS Maintenance Shaft PIT Pit GP Gully Pit AP Anti Ponding Pit GPT Gross Pollutant Trap LID Lid AV Air Valve GRV Gas Release Valve BV Butterfly Valve SV Stop/Scour Valve FH Fire Hydrant SH Swabbing Hydrant WM Water Meter RTAP Reddy Tap ETS Electrofusion Tapping Saddle EC End Cap DE Dead End R Reducer T Tee CHK Check Shot and wherein the asset component field is represented by at least one of the following: CODE DESCRIPTION LUG Line underground LAG Line aboveground HBD Horizontal Bend BGD Vertical Bend CBD Compound Bend JUIL Jump up Invert 35 JUTP Jump Up Top MH Manhole MS Maintenance Shaft PIT Pit GP Gully Pit AP Anti Ponding Pit GPT Gross Pollutant Trap LID Lid AV Air Valve GRV Gas Release Valve BV Butterfly Valve SV Stop/Scour Valve FH Fire Hydrant SH Swabbing Hydrant WM Water Meter RTAP Reddy Tap ETS Electrofusion Tapping Saddle EC End Cap DE Dead End R Reducer T Tee CHK Check Shot 3. A method as claimed in either of claims 1 or 2, wherein the type of location field is represented by at least one of the following: 1. Sighted (S); 5 2. Pothole (P); 3. Reflectorless (R);

4. Electronic (E);

5. Calculated (C);

6. Records (RC); and 10 7. Image (1). 36 4. A method as claimed in any one of claims 1 - 3, wherein the location point field is represented by one or more of the following: * Invert Level (IL); 5 * Obvert Level (OL); * Top (TP); e Bottom (BM); * Surface Level (SL); 0 Concrete Encased (CE); and 10 0 NONE (NONE). 5. A method as claimed in any one of claims 1 - 4, wherein additional attribute fields include one or more of the following: (a) TYPE OF LOCATION 15 (b) LOCATION POINT (c) ADDED DEPTH (d) PIPE DIAMETER (e) LENGTH/DIAMETER (f) WIDTH/HEIGHT 20 (g) MATERIAL (h) CLASS (i) PROTECTION (j) NUMBER OF CONDUITS (k) DEPTH 25 (1) SERVICE PROVIDER (m) SERVICE CONDITION (n) SOIL TYPE (o) COMMENTS (p) TARGET HEIGHT 30 (q) DATE & TIME STAMP