Home

Auckland Transport

1. How Can This Database Operations Manual Help You Accompanying this Table Overview are the following sections RAMM Pavement Layer Data Collection Guide Notes and FAQ s Section 4 7 9 includes diagrams and illustrations around standard pavement layer data collection conventions to ensure the data is collected consistently in the field Some typical FAQ s are also provided Pavement Layer Data Dictionary appended provides a column by column description of the Pavement Layer Table including what data is required how it is collected entered and managed and what are the allowable values Auckland Transport 4 7 9 Auckland Transport Database Operations Manual 65 Collectively these documents are designed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data RAMM Pavement Layer Data Collection Guide Notes and FAQ s The following guide notes are to be used as a reference when carrying out activities that affect the RAMM pavement layer updates The guide notes cover all the necessary information to collect RAMM pavement layer data in a consistent and accurate manner for all the mandatory fields that are required How do I record a granular pavement overlay project in RAMM An overlay is simply new pavement material placed over the top of an existing road surface It may or may not involve removal of existing surfaces via milling or scarifying
2. RAMM Carriageway Surfacings Data Collection Guide Notes and FAQ s The following guide notes are to be used as a reference when carrying out activities that affect the RAMM Carriageway Surfacings updates The guide notes cover all the necessary information to collect RAMM Carriageway Surfacings data in a consistent and accurate manner for all the mandatory fields that are required What does Removed Date mean And when do I populate it Removed date must be populated for surfaces that are physically removed from the Network Do not delete these surfaces from the database The Removed Date is a flag which differentiates between surfaces that are currently on the network and those that have been removed as part of some form of pavement renewal activity Be aware that most removed surfaces do not coincide exactly with the area of pavement renewal so you may have to split historical records into two or more records and apply Auckland Transport Auckland Transport Database Operations Manual 32 Removed Date only to that part of the surface which has been removed due to pavement renewal activity Cross Section BE Paverrent Renewal MOY aY SSS N STISISSIsst N All surfaces to have removed date populated Wy Ph After Pavement Renewal WH KEER NENE A E Figure 4 2 9 1 Cross sections of Pavement and Top Surface Before and After Pavement Renewal How Does Offset Work The
3. Data Custodians ccccccccccccccccccccececcecceeeceeeeeeeeeeeeeeeaeeeeeeeeeeeeeess 5 25 FULUIE ACTIONS Sissing soaadgnedenadeaoaadasagedanedegedeausadgedinde segue davsagasaacdngadasadeansscasadeaaes 5 3 REFERENCE DOCUMENTS ssssesrsisisasssasisasasas sasssasi asasasi asasasi asasasi asasasi ada asi abssad sasa asi ass asANA ANANASA 7 A RAMM TABLES stccsovecsscccccccccccsccscccsscssdecscecstecsdcccdecsdssctccstccsdecstsccdecsdsscdccsdecetesstecsdcssdsssdessdsssdcassccstscssest 8 t a E O Ta SAATE E E E 8 AD Cathlageway SUPACINGS ici s scacsSacsasdnsn secede sodas indadasace anana a e aR Ea RARE aE a aa RS E ARRERA 28 43 Foo ea A O A A AA N A O OARA 35 4 4 Forward Work Programme Treatments ccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeseeeeeeeenees 53 AS Kor 1o le ERRE T EE EE E E E E 56 4 6 Maintenance Costs isisisssisisisssdsssdassissicssadatedassiuinescabacedasssanadacboacaeessunadscussaasassanaadagnoaassaasans 59 47 Pavement AVE c ccccccccssccescssscctsatiuieccachesadacemasedddemadedecededadedusanadesudadaddaneadacasusedadauededacokedeciaci 62 AS ROIA NAMES oiana esses euvsnansudvensuiesvevevoedvevevsesvenev ede vocvues condevndvsvevondvenesooawenusts 69 A9 Cees eee eee ey eee ee ee ee eee eee eee 75 4 10 Treatment Length Maintenance ccccccccsceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeeeeeeeeeess 78 5 DATA DICTIONARY scsdecctecctecstccstecctecctecstcctievstcastecstcsstesstesstecstesstesstc
4. For new roads this will have to be confirmed by the corridor access department of Auckland Transport Database Management Comments Comes from the loading table This is a system calculated value This information comes through from the loading table This information comes through from the traffic table This information comes through from the traffic table This information comes through from the traffic table This information comes through from the traffic table Confirm TTM level with corridor access For most roads the required level will be similar to the surrounding roads or the road it comes off Allowable Values smallint 3 gt 0 and lt 100 Decimal 5 3 gt 0 and lt 99 999 integer 10 gt 0 and lt 999000 integer 10 gt 0 and lt 999000 char 5 Looks up on traff_manage_level 1 ADT lt 10 000 vpd 2 ADT gt 10 000 vpd 2L Meets 2L requirements 3 ADT gt 10 000 and high speed L ADT lt 500 vpd low volume Required by Software System Generated System Generated System Generated System Generated System Generated System Generated System Generated Compulsory 91 Required by Auckland Transport System Generated System Generated System Generated System Generated System Generated System Generated System Generated Compulsory Auckland Transport Carriageway Table Field Name naasra_max naa
5. work_position analysis_code external_id Auckland Transport Database Operations Manual Field Description end_m is the end displacement in metres of the work relative to the location of the road origin length_m is the length of the activity In almost all cases this is simply the end_m the start_m work_position is the position where the work took place relative to the centreline of the road facing in the increasing direction budget code used for financial analysis external_id is the External system transaction ID Data Collection Guidance Notes Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect end_m Only provide this data if the work length is not equal to end_m start_m Avoid use of Unknown and Not Applicable Can be entered where provided by Auckland Transport If RAMM Contractor is used then this defaults to the dispatch ID Database Management Comments Ensure that an end_m is provided for all work types that require a end_m Typically this will be equal to end_m start _m Good practice is to sort the data by various means i e activity or cost group prior to loading to ensure that the work_position data is logical This can be used to roll up costs to budget codes It can provide total cost to date and remaining budget can be calculated 145 Required by Auckland Transport Required by Software 1 9999
6. Auckland Transport ations Manual ir m Auckland 3 Transport An Auckland Council Organisation Auckland Transport Database Operations Manual i 1 Contents 1 INTRODUCTION isssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnssssssssssanansdassssssnsaassssasaassnsnaaaanansaniics 3 E PUPPOSEss seccssscesocssacdsacneacdseasanedeasbenadbensacadeaudesadtaudacadenadedademadaaagansssdegneadedadsnedemedsaadanadsacdanadess 3 12 0 tet cheereeeeereeecmeer eset eee ete per tenet eee eee ieee ee ee ee 3 1 3 Scope of High Priority Tables esisin tics ceves eee tneetevd exes sats etkeeceevesssessetteevesvevecctttieeeness 3 1 4 Previous High Priority Recommendations from RAMM Status Report 4 1 5 RAMM Database Metadata Specifications cccccccccccccccccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaeeeeeeeeeeeess 4 Le RAMM KONE E Giisiciticsttincciiacinncesthanescbatunatnatesatiannenaacaudeiudcaniened cnedeatecacetactiuteaateaaaceaccaatants 4 2 BACKGROUND wi iscscccsds cscs cccsccdiceds cade cacaccaceadeccdacecacaascecacadadeaacacaceaastaacecaseaassasendasteadaasss astassneaszasdeeaazenss 5 2 1 Formation of Auckland COUNCIL ccccccceeesssseeceeeesesessnneeeeeeeeesseceesaeeeeeeeessssenaeeeeeeesesesenaaaes 5 2 2 Database Amalgamation cccccccccccccscsscceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee nee eeeeeeeeeeeeeeeeeeeess 5 2 3 CONSISTENCY OrPo Yera ete re ch eee 5 2 4 Collaborative Approach
7. Database Operations Manual Field Description Estimated mean monthly precipitation Unique identifier for the asset owner The number of lanes on the left hand side of the road The number of lanes on the right hand side of the road Lighting category code for the road section The person or organisation who collected this data Data Collection Guidance Notes No data collection requirements The owner of the carriageway section The number of lanes on the left hand side of the road from the centreline The number of lanes on the right hand side of the road from the centreline No data collection requirements Database Management Comments Not generally used for previous local authority databases This will normally be defined as L for Local Authority C for crown roads i e State Highways etc This would only be of use for wide non divided carriageways as divided carriageways are split by side any way This would only be of use for wide non divided carriageways as divided carriageways are split by side any way This is the lighting code that would apply to the road section from the latest lighting code for roads and pedestrians Very minimal use at present The audit fields do keep a record of the logon name and details of this But the person entering the data may not be the person that collected it Allowable Values char 2 looks up on cway_est_mmp char 3 look
8. RAB is a standard abbreviation for roundabout For example if Great North Road was the main road and Te Atatu Rd was the minor road then the roundabout at the intersection of Great North Rd and Te Atatu Rd would be GREAT NORTH TE ATATU RAB Note that the RD component of both Great North and Te Atatu Roads has been removed in order to reduce clutter High Low Same Level Accessway Naming Conventions High Low Same Level Accesses are Council owned accesses that run parallel to the road they originate from They are typically located in areas of challenging topography where direct access onto the road is prevented from large cuts and fills on the main road The property numbers which are accessed from the High Low Same Level Access are used to assist in identifying the correct access For a Low Level Access on Don Buck Road accessing properties 20 to 32 the naming convention would be DON BUCK RD LLA 20 32 For a High Level Access on Abbots Way accessing properties 2 to 36 the naming convention would be ABBOTTS WAY HLA 2 36 The High Same Low Level Access needs to run in the same direction as the parent road therefore in some instances this will require the access to begin at the end and end on the parent road Walkway Naming Convention Walkways are named in such a way that clearly identifies all walkways from one another and also makes locating the walkway easy For example the Parry Harwood Walkway which runs
9. Rural Summer Recreational 8 Rural Feeder 9 Urban Residential 10 Urban Beach Roads 11 Rural Other UN Unknown Default Compulsory Compulsory Auckland Transport Carriageway Table Field Name cway_group_1 cway_group_2 cway_group_3 cway_group_4 cway_group_5 Auckland Transport Database Operations Manual Field Description Optional group columns that allows users to group carriageway sections according to individual requirements Optional group columns that allows users to group carriageway sections according to individual requirements Optional group columns that allows users to group carriageway sections according to individual requirements Optional group columns that allows users to group carriageway sections according to individual requirements Optional group columns that allows users to group carriageway sections according to individual requirements Data Collection Guidance Notes Dependent on grouping criteria Dependent on grouping criteria Dependent on grouping criteria Dependent on grouping criteria Dependent on grouping criteria Database Management Comments Use the current conventions from the legacy areas until a new global convention is established Use the current conventions from the legacy areas until a new global convention is established Use the current conventions from the legacy areas until a new global convention is established
10. This field is not required for data collection This field is not required for data collection Database Management Comments Only required if recycled materials used Correlate the surfacing reasons in the treatment length table with the treatment and enter this data in surf_reason Leave Blank Enter only applicable comments This date is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column Required by Software Allowable VEINES Not required Not required Looks up on surf_reason System Generated System Generated 112 Required by Auckland Transport Compulsory when certain conditions are met Compulsory Not required Compulsory when certain conditions are met System Generated System Generated Auckland Transport Surfacing Table Field NEMIS Auckland Transport Database Operations Manual Field Description chgd_on is the date that the data was changed in the database chgd_by is the RAMM username of the organisation that changed the data in RAMM Data Collection Guidance Notes This field is not required for data collection This fie
11. count readings Only associated with count type C This field describes the multiplier for adjusting NZTA Traffic monitoring System AADT to generate Traffic Estimates This field describes the unique header for the traffic load file Data Collection Guidance Notes Use tube and permanent count download information from contractors to determine the peak hour Not required to be collected The contractor report templates must note the carriageway section in where the physical counts are undertaken and include house number if outside properties The contractor must ensure Quality Assurance checks as per AT traffic count service requirements are carried out Not required Not required Database Management Comments This is important information required in relation to traffic modelling ensure peak start hour to be added Not required to be populated as added into notes field Check location description matches carriageway section in which counts are undertaken Not required for estimates Do not use commas or slashes Check QA reports obtained from contractor to ascertain data integrity Field not required to be populated Not required Not required 164 Required by Auckland Transport Required by Software ot required N N 7 N VarChar 35 e g required Road outside 0 Oo No 26 o o 7 t i required t Ft i Allowable VEINES Char 5 e g 10
12. current Treatment Definitions Table including what treatments are available and what are the recommended time periods for these treatments Collectively these documents are designed to assist both data collectors and database managers to achieve the ultimate outcome of accurate consistent and up to date data Table 4 4 Forward Work Programme Treatments Recommended Year for Treatment Code Overlay OLAY All years Development Project e g realignment All years Reconstruction All years Rejuvenation Seal All years Treatment Description Treatment Code Recycling cold milling RECY Years 1 4 Rehabilitation RHAB All years Reseal chip unknown Years 5 Reseal Small chip RSS Years 5 Reseal Big chip RSB Years 5 Reseal Multi chip RSM Years 5 Reseal single chip grade 2 RS2 Years 1 4 Auckland Transport Auckland Transport Database Operations Manual 55 Recommended Year for Treatment Code Seal Extension All Years Slurry Seal All Years Stone Mastic Asphalt SMA Years 5 Seal widening All Years Thin Asphaltic Concrete TAC Years 5 Texturising Seal All Years TNZ10 Years 1 4 TNZ15 Years 1 4 Ultra Thin Asphaltic Concrete UTA Years 1 4 Void Filling Years 1 4 Wheel track rutting Years 1 4 Water cutting WTCT Treatment Description Treatment Code Auckland Transport 4 5 Auckland Transport Database Operations Manual 56 Loading 4 5 1 4 5 2 4 5 3 4 5 4 Why is This Table Important Th
13. measured to the nearest 0 1m from the LHS of the sealed carriageway to the LHS of the layer being collected Data Collection Guidance Notes The layer date is the primary key for allowing accurate pavement structures to be created from the pavement_layer table This information can be obtained from the contractor s construction records Generally the layers will be put down over a number of days weeks The final roll date of each layer should be what is used This information must be provided when an existing layer is removed as part of a reconstruction project or a layer is recycled as part of a pavement rehabilitation project Offset only needs to be collected if the Pavement Layer is not full width Database Management Comments It is important that the dates are accurate and in the correct chronological order for multi layered pavement projects If you are entering a layer and the date of construction is only estimated use 01 01 XXXX as the layer_date If no roll dates are provided then ensure that the top pavement layer date is at least 1 day before the 1st coat surfacing date with any previous layers dated accordingly Ensure that the removed_date is applied to all layers which have been removed as part of construction and not just the top layer Depth of reconstruction recycling will determine how many layers are affected Offset layers need careful manipulation especially when adding them
14. notes field For new traffic counts being added via RAMM for Windows RAMM will automatically assign a traffic_id For new traffic counts being added via RAMM Manager Import Facility set traffic_id to O in the loadfile This date is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format Allowable VEINES C Counting system L Local Knowledge M Measured Flow T Transport Model varChar 255 e g Site 44 85th 61 0 9999999999 Required by Software Not required Not required Compulsory System Generated 165 Required by Auckland Transport Required if estimate is added updated Required for Count C Compulsory System Generated Auckland Transport Auckland Transport Database Operations Manual 166 Required by Auckland Transport Required by Software Trame Tabie Field Description Data Collection Guidance Notes Larabar e Menoremeni guess Field Name Comments VEINES added_by is automatically assigned added_by is the RAMM if you are adding data via RAMM username of the This field is not required for data for Windows If you are using the System System organisation that collection RAMM Manager Import facility you Generated Generated entered the data need to add your RAMM username to this column added_by This date is automatically up
15. s Road names start and end locations and descriptions for each road A traffic counting programme approved by Auckland Transport Calibrated certified and accurate traffic counting equipment A calibrated vehicle tripmeter with completed calibration form accurate to 1m over 1km 0 1 for locating exact count location Whatever electronic device your organisation needs to download the data from the counter An approved traffic management plan How is the Database Updated The Traffic Data Dictionary appended provides additional guidance to database managers who have read write access to the RAMM Traffic Table The database can be updated using four methods Automated uploading of bulk traffic count data through the RAMM Manager data import facility preferred for large quantities of traffic counting data Manual addition updating and deleting of traffic records in RAMM for Windows Manual updating of the estimates when making carriageway changes Automated updating of estimates based on current traffic count data if a network estimate model exists How can this Database Operations Manual Help You Accompanying this Database Operations Manual are the following sections AT will provide the data in a format that is required from the traffic count service provider Auckland Transport Auckland Transport Database Operations Manual 77 Traffic Data Dictionary appended provides a col
16. 2 methods Importing data from spreadsheets validating and moving to the Carriageway Surfacing Table preferred method for loading large amounts of data on new road construction where the new pavement layers have no effect on existing data as typically there is no existing data Manual addition updating and deleting of Pavement Layer records in RAMM for Windows preferred method as most new pavement layers on existing roads will affect existing layers in some way In addition to the above two methods there is a tool called the Pavement Builder Before using this tool you should be totally familiar with what it does and be prepared to do a check at the end to see that the outcome was what was expected Also be aware that no other database administrators can touch the Pavement Layer Table while you are using the tool as it locks the table Updating existing pavement layer records as a result of pavement layer reconstruction projects can be complicated The preferred way to undertake this work is in RAMM for Windows viewing the pavement layer data for each affected record in grid view than updating in detail view When the pavement layer records are updated always view the data again in grid view to ensure there are no overlaps or gaps in the pavement layer data It is important that a clear understanding and knowledge of how the pavement was built including the sequence of activities is known prior to updating the Pavement Layer Table
17. 5 1 Metadata Currency The data collection and Data Dictionary requirements for the manual have been based on the current operating version of RAMM for Auckland Transport s database At the time of writing this report it was RAMM 2008 2 5 2 Future Versions The Database Operations Manual will require updating to ensure alignment with metadata changes that occur with future versions of RAMM Any significant changes to table structure should be well known in advance to the industry prior to it being released This will enable changes in process and collection to be well understood and documented prior to implementation Where changes or additions to asset collection methodologies are agreed then documentation will be required to ensure consistency for the whole database All data providers will need to be advised to ensure homogenous metadata for the specific asset 2 6 RAMM Knowledge In preparing this manual a certain level of RAMM knowledge has been assumed To get to a point where you are either collecting data in the field or being responsible for database maintenance for Auckland Transport you must have NZTA RAMM L1 or L2 certification As a pre requisite organised on the job training would have been completed to ensure familiarity and proficiency in the required work RAMM Status Report Stage One April 2011 Opus International Consultants Limited Auckland Transport 2 1 2 2 2 3 2 4 2 5 Auckland Transport
18. Carriageways Full length Where a road has a physical median that separates each direction of travel over the full length of the road then each side has a separate road name and road id The road name is suffixed in brackets with the travel direction for that road i e TE IRIRANGI DR WESTBOUND and TE IRIRANGI DR EASTBOUND Single Divided Section Not full length of road If the physical median is not present for the full length then the increasing direction carriageway sections are contiguous with no direction suffixed in brackets after the road name i e TE IRIRANGI DR and decreasing section are added as required with the direction suffixed in brackets after the road name i e TE IRIRANGI DR EASTBOUND Multiple Divided Sections In the case where there is more than one divided section along the length of the road then the running distance continues from the end of the first divided section through to the end of the last divided section This will result in there being gaps between the divided sections as the running distance is contiguous from the start of the first divided section Example The table below shows an example of a road that has multiple divided sections along its length Start m End m Start name End name NOM EES Redoubt Rd 1000 John Rd Start divided e e O Ee Redoubt Rd 1000 1500 Start divided End divided 2 A a a ES Ea Redoubt Rd 1500 2000 End divided Smith Rd Start eN O O Ea Fe Redoubt Rd 2500 2800 End d
19. Comments Allowable VEINES decimal 12 4 gt 99 9999 and 9999999 9 Looks up on organisation 1 Generic GPS device 5 m 2 User clicked on map 10m 3 Update from RAMM Map 10m 4 Unknown no accuracy 5 Taken from asset no accuracy 6 Default no accuracy 104 Required by Auckland Transport Auckland Transport Required by Software Surfacing Table Field AEG surface_date removed_date Auckland Transport Database Operations Manual Field Description surface_date is the date that the surfacing was carried out removed_date is the date that the surface was removed surf_width is the average width of the surfacing to the nearest 0 1m Data Collection Guidance Notes This information can be obtained from the surfacing contractors sealing paving records In some instances a long surfacing treatment is carried out over a number of days Please use the last date of surfacing as the surface_date This information must be provided when an existing surface is milled as part of an asphaltic concrete resurfacing project or a surface is recycled as part of a pavement rehabilitation project surf_width is ONLY required when the surface treatment is NOT full width Database Management Comments surface_date is the primary key for allowing accurate surface structures to be created from the c_surface table It is important that the dates are accurate and in the co
20. Compulsory Required by Software Unique traffic link ystermgenerated For use in the traffic estimation integer 10 Optional System identifier oe module gt 0 and lt 999000 P Generated condition_wt Calculated condition weighting from assessment The overall condition of the road section No data collection requirements An overall condition score from 1 to 5 for the whole road section for all assets or as defined This field allows for an overall condition to be recorded for the carriageway section It can be a windshield condition assessment or one that is calculated and weighted from other recorded asset conditions Generally populate with default value U unless contractually required under a maintenance contract Decimal 5 3 gt 0 and lt 99 999 Char 1 1 Excellent 2 Good 3 Average 4 Poor 5 Very Poor U Unknown U Default value Not tional Opuona Required Compulsory Compulsory Auckland Transport Carriageway Table Field Name condition_date likelihood_wt risk_likelihood consequence_wt risk_consequence Auckland Transport Database Operations Manual Field Description The date the condition of the asset was established Calculated likelihood weighting from assessment Likelihood of the risk identified in the risk assessment Calculated consequence weighting from assessment The consequence of the asset failing or risk ev
21. Description location is the displacement of the physical count in metres relative to the location on the road that the count is located on The location is the distance from the start of the road to the start of the physical count on site This field describes the direction lane in which the count was undertaken Data Collection Guidance Notes Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect location You will need to know what the increasing direction of the road is before confirming the location You will need to know what the increasing direction of the road through the road schedule before confirming the direction lane Database Management Comments Ensure that the location is contained within the road carriageway length Not required to be populated for estimates Default values get populated with the carriageway_start_m Ensure that the direction lane is correctly populated especially for divided carriageways containing more than one lane in one direction Estimates can only be populated with B Both Lanes Allowable VEINES L left lane R right B both L1 Left lane 1 L2 Left lane 2 L3 Left Lane 3 L4 Left Lane 4 L5 Left Lane 5 R1 Right Lane 1 R2 Right Lane 2 R3 Right Lane 3 R4 Right Lane 4 R5 Right Lane 5 Required by Software Required for Count C Compulsory 132 Required by Auckland Transpo
22. Ensure raw download data classifies according to the NZTA 2011 classification system based on which percentages are calculated Ensure raw download data classifies according to the NZTA 2011 classification system based on which percentages are calculated Not required to be collected Not required to be collected Database Management Comments Check totals of individual categories add up to 100 Check totals of individual categories add up to 100 Not required to be populated as it is a calculated field when manual entry is done usually populated with a zero when loading through import files Not required to be populated as it is a calculated field when manual entry is done usually populated with a zero when loading through import files Allowable Values 0 000 99 999 0 000 99 999 Required by Software Required for Count C Required for Count C System generated System generated 135 Required by Auckland Transport Required for Count C Required for Count C System generated System generated Auckland Transport Auckland Transport Database Operations Manual 136 Required Required by by Auckland Software Transport This field describes the Not required to be populated as it is equivalent standard a calculated field when manual entry 0 000 System System axles ESA per heavy Not required to be collected is done usually populated with a i i 9
23. Pavement Layer 4 7 1 4 7 2 4 7 3 Why is this Table Important The Pavement Layer Table is to store information both historical and current on the structural pavement layers including the sub grade underneath the pavement This includes a single treatment structural asphaltic pavement layer with a total design depth gt 80mm Since it is impossible to verify the composition of the structural layers beneath a pavement once it has been sealed it is critical that this information is provided or recorded at the time of construction A further source of valuable information on pavement strength and layer depth is the information obtained when test pits are carried out note that testpit data can be stored in the pave_test_pit table Specifically the RAMM Pavement Layer Table includes Start and end locations of the pavement layer Length width thickness and offset of the pavement layer Type composition source and strength of the pavement layer Date the layer was constructed reconstructed or removed Stabilisation agents that may have been used to strengthen the pavement layer What is the Pavement Layer Table Used For Its primary use is for providing accurate contributing data towards An accurate pavement structure table Comparing with national annual achievement reporting for pavement renewal projects to NZTA The development of the pavement deterioration model What Activities Affect t
24. RP300 to RP600 at an average width of 3 5m using 150mm of GAP65 and 100mm of GAP40 There is currently a pavement layer record from RPO to RP1000 as shown in the following table ae Date ee Material Depth Reconstructed Width Offset O 1000 17 02 1990 K GAP40 100 N 10 o 0 1000 15 02 1990 K GAP65 150 N 10 0 Once you have added the widening layer to RAMM your layer data should now look like this sa m Date aie Material Depth Reconstructed Width Offset o 300 17 02 1990 K GAP40 100 N 10 0 o 300 15 02 1990 K GAP65 150 N 10 0 300 600 17 02 1990 K GAP40 100 N 10 3 5 300 600 15 02 1990 K GAP65 150 N 10 3 5 300 600 16 02 2005 K GAP40 100 N 3 5 0 300 600 15 02 2005 K GAP65 150 N 3 5 0 600 1000 17 02 1990 K GAP40 100 N 10 0 600 1000 15 02 1990 K GAP65 150 N 10 0 Note There are now eight rows of data where there were originally two The full width flag is unchecked or set to No for all layers within 300 to 600m As you will also be sealing the widening the same propagation of data must take place in the Surfacings Table Auckland Transport 4 8 Auckland Transport Database Operations Manual 69 Road Names 4 8 1 4 8 2 4 8 3 4 8 4 Why is this Table Important The Roadnames Table contains information about the type of road overall
25. This is illustrated in Diagram 4 1 5 below a E T Carriageway section end point Carriageway section start point End of approach island e g Start of approach island e g 0 1050m pn 1087 2160m 1050m yer A 51087m Lf so b Aon From SH 2 a To Garden Cres Great South Rd Roundabout area considered as a separate road Diagram 4 1 5 Example of Carriageway Sectioning of a Road Through a Roundabout Example GREAT SOUTH RD carriageways 0 1050m SH 2 WILLIAM ST and 1087 2160m WILLIAM ST GARDEN CRES Note that a gap exists between the displacements Any other roads that start or end at roundabouts start end at the approach islands do not encroach on the roundabout area Auckland Transport Auckland Transport Database Operations Manual 19 Cul De Sacs The following describes how cul de sacs are surveyed with respect to end position of the last carriageway section Cul de sacs with small islands are treated like standard cul de sacs measuring the extreme most point Diagram 4 1 6 shows a standard cul de sac with Diagram 4 1 7 having a small island Cul de sacs with large islands are surveyed by splitting the carriageway at the start of the island nose when approaching the cul de sac driving around the loop and ending the carriageway at the same point when exiting the cul de sac head This is shown in Diagram 4 1 8 Cul de sac head
26. WILLIAM ST GARDEN GR Auckland Transport Auckland Transport Database Operations Manual 27 Defining Carriageways Start and End Points Two Roads Starting Ending on Curve m gt gt To Garden Gr Great South Rd Power Pole Boundary Fence Sump Endeavour to start end roads at a well defined point e g power pole sump corner of boundary fence etc William St From SH 2 Diagram 4 1 13 Carriageway Section Definitions for Two Roads Starting and Ending on a Curve The carriageway sections for both roads will be as follows Road 1 WILLIAM ST carriageways 0 496m SH 2 GREAT SOUTH RD POWERPOLE RHS Road 2 GREAT SOUTH RD carriageways 0 1065m WILLIAM ST POWERPOLE RHS GARDEN GR Auckland Transport Auckland Transport Database Operations Manual 28 4 2 Carriageway Surfacings 4 2 1 4 2 2 Why is this Table Important The RAMM Carriageway Surfacings table provides a logical place to store current and historic surfacing data such as chipseals asphalts and slurries The accuracy of this table is absolutely critical as surfacing records contained in it represent significant investment by Auckland Transport AT The table is used extensively in conjunction with high speed data and other condition assessment tables to undertake high level condition analysis Specifically the RAMM Carria
27. Where these surfaces are not removed the pavement layer data can be simply added to the database Although the surfacings data has not been physically removed it is no longer acting as a surface i e it is now part of the pavement layer therefore all the surfaces under the overlay need to have a surface_removed date entered If the total combined depth of surfacings under the granular overlay exceeds 50mm then a new pavement layer record needs to be added to the Pavement Layer Table Use the pavement material code SEALS for this layer How do I record a rip and remake pavement reconstruction project in RAMM A rip and remake will not affect the pavement layer data unless the top layer of the pavement is changed in thickness or stabilised in some way but will require surfacings in the Surfacing Table to have removed date populated Make sure to add a note to the layers affected by the rip and remake and the date the rip and remake occurred How do I record stabilisation of an existing pavement The following fields must be populated if you have stabilised an existing pavement Stabilisation material Cement Lime Kiln Dust Stabilisation percentage typically between 2 and 10 Reconstructed must be set to yes Pavement date set this to the date that the pavement was stabilised This information is stored in a combination of tables Auckland Transport Auckland Transport Database Operations Manual
28. add the date to this column in dd mm yyyy format System Generated 146 Required by Auckland Transport System Generated System Generated System Generated Auckland Transport Maintenance Cost Table Field Name Auckland Transport Database Operations Manual Field Description chgd_by is the RAMM username of the organisation that changed the data in RAMM Data Collection Guidance Notes This field is not required for data collection Database Management Comments Allowable Values added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column Required by Software System Generated 147 Required by Auckland Transport System Generated Auckland Transport Auckland Transport Database Operations Manual 5 6 Pavement Layer Data Dictionary Pavement Layer Table Field Name layer_id road_id Field Description layer_id is the unique asset id assigned to the layer asset For new layers being added to RAMM this is set to 0 and RAMM assigns a layer_id once the asset is added to RAMM For existing layers that are currently being updated in RAMM the current layer_id needs to be used as reference to ensure the correct layer is updated road_id is the RAMM road_id of the road that the layer is on start_m is the start location of the pa
29. affect the surface structure need to have treatment lengths disabled for TSA FWP and Rating Auckland Transport Auckland Transport Database Operations Manual 5 DATA DICTIONARY 5 1 Carriageway Data Dictionary Carriageway Table Field Name carr_way_no carrway_start_m carrway_end_m Field Description Unique identifier for the carriageway section Unique RAMM road_id Start displacement of the carriageway section from the road origin End displacement of the carriageway section from the road origin Required Allowable Values by Software This is a system generated number For System generated each carriageway section of a road serial 10 Compulsory RAMM will assign the unique number This generally is a system generated number Where you want to keep the road id numbering consistent within System generated the old legacy council area then the integer 10 Compulsory assigned road id will have to be updated to the next sequential number in the assigned series Data Collection Guidance Database Management Notes Comments The displacement to the start of the carriageway section from the Cm nein of ne roan Try to Ensure the Om point is known and is ensure a physical point is used integer 5 Compulsory i i well defined where possible that is unlikely to change over time and that is easy to find The displacement to the end of the carriageway section from the Orri point or the r
30. by Software Compulsory Optional Looks up on surf_recycled_cpn Optional t Compulsory Allowable Values T True F False F Default 0 30 inclusive looks up on the pave_spec U Undisturbed R Reconstructed U Default 153 Required by Auckland Transport Compulsory when certain conditions are met Compulsory when certain conditions are met Compulsory when certain conditions are met Optional Compulsory Auckland Transport Auckland Transport Database Operations Manual Pavement Layer Table Field Name The plan number on the construction drawings Design Life of the new Pavement Estimated Design ESA design_esa Equivalent Standard Axle for the new pavement Forward Work Treatment that applies to this pavement layer Field Description design_life Miscellaneous Notes added_on is the date that the added_on data was added to the database Data Collection Guidance Notes Easily obtained from the Construction drawings Some pavement construction projects do not have drawings especially if the work is essentially in situ This information can be gained from the pavement designer This information can be gained from the pavement designer Not needed Add applicable notes This field is not required for data collection 154 Required Required by by Auckland Software Transport M mem Not ew i Compulsory Not when certain Req
31. data collection Required by Software Allowable VEINES Database Management Comments For new traffic loading counts being added via RAMM for Windows RAMM will automatically assign a loading_id For new traffic counts being added via RAMM Manager Import Facility set loading_id to 0 in the loadfile 0 9999999999 System Generated Compulsory This date is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column System Generated 139 Required by Auckland Transport Compulsory System Generated System Generated Auckland Transport Loading Table Field Name Auckland Transport Database Operations Manual Field Description chgd_on is the date that the data was chgd in the database chgd_by isthe RAMM username of the organisation that changed the data in RAMM Data Collection Guidance Notes This field is not required for data collection This field is not required for data collection Database Management Comments This date is automatically updated if you are changing data directly in RAMM for Windows If you are using the RAMM Manager Import facility you need to a
32. extremity 126m bS Miscellaneous Extra Area William St Great South Rd Diagram 4 1 6 Definition of a Cul de sac Carriageway Section The carriageway section for William Street will be as follows 0 126m GREAT SOUTH RD CUL DE SAC Auckland Transport Auckland Transport Database Operations Manual 20 Cul de sac Head with Small Island Cul de sacs with small islands that can be driven past without deviation through the cul de sac turning area to the end of the road will be treated like a normal cul de sac as shown in Diagram 4 1 7 below Cul de sac head extremity 175m Miscellaneous Extra Area rv l K Intersection Extra Areas Om Great South Rd Diagram 4 1 7 Definition of a Cul de sac With Small Head Island Carriageway Section The carriageway section for Williams Street will be as follows 0 175m GREAT SOUTH RD CUL DE SAC Auckland Transport Auckland Transport Database Operations Manual 21 Cul de sac Head with Large Island Always collect data in clockwise direction Create carriageway split adjacent island nose Miscellaneous Extra Area William St Intersection Extra Areas Great South Rd Diagram 4 1 8 Definition of a Cul de sac With Large Head Island Carriageway Section The carriageway section for Williams St will be as follows 0 96m GREAT SOUTH RD START ISLAND RHS 96 178m START IS
33. from road JOIN Footpath Joins another road NONE No adjustments made OCR Footpath starts and or ends on Other Council Road PARKS Parks and Reserves road PRV Footpath starts and or ends ona Private Road RAB Footpath length is affected by a Roundabout ISECT Footpath starts and or ends at an Intersection SH Footpath is on a State Highway UKN Footpath length adjustment is Unknown WW Footpath position is a Walkway WIDEN Footpath length is affected by road Widening Required by Software Allowable Values Looks up on Optional len_adjust _rsn p Required by Auckland Transport Compulsory when certain conditions are met Auckland Transport Footpath Table Field Name footpath_surf_mat overlay_depth Auckland Transport Database Operations Manual Field Description width is the width of the footpath to the nearest 0 1m area is calculated by the software as true length defined as the footpath length including the adjustment length_m x width if no other area is provided footpath_surf_mat is the predominant surfacing material over the length of the footpath overlay_depth the depth of the predominant footpath surfacing chip_size is the size of the aggregate of the predominant footpath surfacing Data Collection Guidance Notes Width can either be collected with a tape measure or measuring wheel For footpaths that do not have a regular width alo
34. has been stabilised Pavement builder will tag the previously unbound layers as removed and add a new stabilised layer with material type composite What do I do when stabilise a pavement layer but there is no data in RAMM that I can add the stabilising details to In this situation you will need to add an estimated layer to the Pavement Layer Table then you can add the stabilised details Set the estimated known field to E to show that the record is estimated use a default date of O1 01 xxxx as the pavement layer date including specifying the year The year can be assumed as 25 years before stabilisation i e if stabilisation has been done in 2012 the default date would be 01 01 1987 Add additional information in the notes field to provide any other relevant information How do differentiate between separate layers in a multi layer pavement Typically most pavements comprise of more than one layer e g prepared subgrade bottom layer GAP65 graded all passing 65mm sieve sub base middle layer and GAP40 graded all passing 40mm sieve basecourse upper or top layer RAMM determines the order of layers by their dates so the older the layer the lower the layer sits relative to surrounding layers The youngest layer sits on top Even if you place both GAP40 and Auckland Transport Auckland Transport Database Operations Manual 67 GAP65 on the same day you can nominate the GAP40 to be the top layer by a
35. included in this report e Auckland Transport e Downer e Fulton Hogan FH e RAMM Software Limited RSL e Beca BECA e Previous Local Government Organisation LGO staff from the various Councils e Opus International Consultants Ltd OPUS e Projenz Auckland Transport 2 1 2 2 2 3 Auckland Transport Database Operations Manual 3 INTRODUCTION Purpose This document in its current form is considered to be the starting point in the overall process of developing a complete Database Operations Manual for Auckland Transport It outlines methodology for both the field data collection and entry into Auckland Transport s RAMM database for purposely selected 10 key asset tables The draft manual outlines what is considered to be current best practice for the activities that were previously being undertaken by individual Councils of the Auckland Region The manual is intended to provide guidance to those individuals and organisations that supply Auckland Transport with services to deliver transportation outcomes that maintain change remove or upgrade physical assets resulting in subsequent changes to the asset register Objectives Phase one focused on selected high priority core asset tables identified in the RAMM Status Report and agreed with Auckland Transport Further work is required to complete the manual for all tables that Auckland Transport decides to maintain A primary objective of this first phase was to d
36. is on and where the footpath starts and ends in relation to the road and the position of the footpath on the berm road reserve Dimensional information such as footpath length width and area Physical attribute information such as the material that the footpath is made of what number and types of users use the footpath Other key information such as who owns and maintains the footpath when the footpath was constructed and surfaced when the footpath data was collected and by whom when the footpath data was added to RAMM and if the footpath record has been changed since it was added What is the Footpath Table Used For The RAMM Footpath Table is Auckland Transport s primary repository for all footpaths and shared pathway asset inventory and condition information and is used for monitoring condition forward planning determining levels of service undertaking valuations and capturing annual investment in both footpath construction and maintenance Accurate footpath data can also be used to spatially show footpath assets on aerial photographs or in GIS images What Activities Affect this Table There are three key activities that affect the footpath table in terms of physical changes to the asset that must be captured in RAMM to keep the table up to date The activities are New subdivision construction typically new footpaths are constructed as part of subdivision developments these new footpaths need to be added
37. needs to be entered when the expected life is different to the modified default life desinen System System esign_expiry Generated Generated System System design_life is the estimated design_life expected design life of the surfacing in years default_life Auckland Transport Auckland Transport Database Operations Manual 107 Required Required by by Surfacing Table Field Field Description NEMIS Software Data Collection Guidance Database Management Allowable Notes Comments VEINES Auckland Transport System System N S a A This field reflects the expected life for a given surfacing type pavement use and security zone It can be updated by making mod_default_life is the changes to the surface life table ieee found in RAMM revised life in years which For new surfacings this data is i m Manager Maintenance System mod_default_life can be updated bya system generated where modified dood 1 to 80 Optional ae Lookups Surface Material This is Generated database administrator at default lives have been defined i any tihe required to be populated setup y by Auckland Transport Once this is done then the modified default lives will be populated when the surfacing status update tasks are run via RAMM Manager mod_default_ System System expiry Generated Generated surf_material is the Use as built data or contractors A Looks up on surf_material material type of the surfaci
38. not significantl sealed_area calculated total area in sq additional area is surfaced side g 8 Y a to 99999 Optional Optional different to sealed_area and if m of the surfacing roads car parks etc and must be so investigate wh included in this total area f 8 y A Y Y eee If the sealed_area is measured a Defines if the measured j N No System sealed_area_ok ae including all the add on pieces then Compulsory sealed_area field is OK Generated the field should be Y otherwise N N Default Auckland Transport Surfacing Table Field AEG contract_number organisation polished_stone pct_recycled Auckland Transport Database Operations Manual Field Description Contract Number of the Sealing Project or AWPT Contract Sealing Contractor Contract end user spec code The polished stone value of the largest chip Average Least Dimension of largest sealing chip Only required for chipseals Does this seal contain recycled material Percentage of Recycled material DELICE AAEE EAE Notes Obtain the Contract Number from the Contract documents The Contractor Responsible for sealing under this contract The specification covering the way the contract is managed and warranted This is laboratory tested from stockpile samples This is laboratory tested from sealing chip stockpile samples Only populate if recycled components are present in the surfacing such as the use of
39. ownership and location details such as suburb and town This information helps to ensure duplication of location and name is avoided Specifically the RAMM Roadnames Table includes A unique database road identifier road_id for each road The road name as it was vested to Council with consistent abbreviations Location information such as suburb postal code and town Linkage to the NZTA funding region and the road controlling authority that owns the road What is the Roadnames Table Used For The RAMM Roadnames Table is Auckland Transport s primary repository for all vested roads that it is required to maintain and provides a primary linkage between RAMM and other asset management systems Private roads are also entered with just the roadnames detail This ensures the call centre can advise customers if this is not a road that Council is responsible for maintaining What Activities Affect this Table There are five key activities that affect the Roadnames Table in terms of changes to the asset register that must be captured in RAMM to keep the table up to date The activities are New road construction subdivisions Road renaming Stopping of roads and sale change of ownership from Council Revocation of state highways back to the local authority or private roads that Council vests as public Changes to existing road connectivity that break or create new roads resulting from new road constr
40. slag chip recycled rubber recycled asphalt Only required if recycled materials used Database Management Comments Important Information for filtering out data by contract This should fit within the envelope for the chip grade Set to False if no recycled materials were used Set to yes if recycled materials were used Only required if recycled materials used 111 Required by Auckland Transport Required by Software Allowable Values Free format 20 Characters long 3 character lookup which looks up on the organisation table 10 Characters long and looks up on the surf_spec table Compulsory when certain conditions are met 0 01 to 99 99 Compulsory Compulsory when certain conditions are met T True F False F Default Compulsory when certain conditions are met Auckland Transport Surfacing Table Field AEG surf_recycled_cp nt added_by Auckland Transport Database Operations Manual Field Description Surface Component that is Re cycled Reason for Surfacing Forward Work Treatment that applies to this surface Miscellaneous Notes addedc_on is the date that the data was added to the database added_by is the RAMM username of the organisation that entered the data Data Collection Guidance Notes Only required if recycled materials used This data will be provided by the database manager Not needed Add applicable notes
41. such as small domes or roundabouts with painted traversable islands are treated like standard intersections Roundabouts are named as follows MAJOR ROAD NAME MINOR ROAD NAME RAB e g GREAT SOUTH WILLIAM RAB Note that the street suffixes are excluded in the road name The start and end names are e g WILLIAM ST WILLIAM ST and include the suffixes For two major roads or roads of the same hierarchy naming is ordered alphabetically Starts and ends at intersecting Road e g 0 67m Great South Rd Great South Rd Roundabout area considered as a separate road Road named as GREAT SOUTH WILLIAM RAB William St Diagram 4 1 4 Roundabout Treated as a Separate Road Additional Notes Great South Road is the major road so the naming convention is GREAT SOUTH WILLIAM RAB with start end names 0 67 WILLIAM ST NORTH WILLIAM ST NORTH Auckland Transport Auckland Transport Database Operations Manual 18 Roundabout Intersecting Roads Where roads start end or intersect a roundabout the carriageway sections will start end at the roundabout approach islands The island nose closest to the roundabout itself is used as the start end point Where a road passes through the roundabout the displacements are measured between the approach islands and a gap is in the displacements The gap allows high speed data to be continuous when passing through the roundabout
42. the carriageway section is not divided Collect the extra seal areas that are not included as part of the width or irregular width calculations These are typically widened areas at an intersection and may include short lane gains typically less than 100m where a separate carriageway section is not created to account for this Also included are short left turn slip lanes No data collection requirements Assumed to be local authority unless advised otherwise Be sure to be clear around the roles and difference between owner controller maintained and managed by Database Management Comments Where minor safety work involves modification addition deletion of islands care needs to be taken to update and reflect this information in the carriageway table Minor safety works traffic signal upgrades that include lane arrangement changes can change this figure The total area is calculated using 2 n cway_area_m misc_area bus_bays intersections islands Should be confirmed by the subdivision plan with the vested owner denoted Currently AT is the controller of the network therefore AT must be used at the organisation controlling the network Required Allowable Values by Software Compulsory Compulsory smallint 4 gt 0 and lt 9999 Default value of 0 smallint 4 gt 9999 and lt 9999 System Generated smallint 5 gt 99999 and lt 99999 Char 1 C Crown L Loca
43. the smallest chip for a multicoat chipseal pave_source is the quarry that the aggregate used for chip sealing or asphalt mix is sourced from Data Collection Guidance Notes For chipseal surfacings this does not need to be provided For all asphaltic concrete slurry and concrete surfacings the depth of the surfacing needs to be recorded Obtain this information from the mix design and or contractors surfacing records This flag should be set to N for chipseals and Y for Asphaltic Concrete Use sealing records or seal designs to obtain this information usually included in the as builts Use sealing records or seal designs to obtain this information usually included in the as builts Use sealing records to obtain this information sometimes it is included in the as builts Note that this is NOT the name of the organisation that owns the quarry or the AC plant it is the source of the aggregate quarry name Database Management Comments All mix type surfacings require a depth Chipseal surfacings can be entered as depth 0 Ensure that the larger chip size for multicoat seals is entered in this field Ensure that the smaller chip size for multicoat seals is entered in this field Ensure that the data provided is in fact the quarry source and not the name of an organisation Each quarry produces aggregates with unique geological properties by having accurate pave_source data these properties can be inves
44. to be collected Use tube and permanent count download information from contractors to determine location description of physical traffic counts Database Management Comments Check QA reports obtained from contractor to ascertain data integrity Field not required to be populated Not required Add Estimate if default values do not give you the approximate classification categories due to unique commercial vehicle flow characteristics of the road e g near a quarry CBD areas etc The notes field is usually populated with the location description 138 Required Required by by Auckland Software Transport Allowable Values Required if estimate is added updated C Counting system L Local Knowledge M Not required Measured Flow T Transport Model varChar 255 eg approx 100 soit Not required Optional Road outside No 26 Auckland Transport Loading Table Field Name loading_id added_on added_by Auckland Transport Database Operations Manual Field Description loading_id is the unique asset id assigned to the traffic row added_on is the date that the data was added to the database added_by is the RAMM username of the organisation that entered the data Data Collection Guidance Notes For data collection of new traffic loading counts loading_id is not required This field is not required for data collection This field is not required for
45. to new roads or carriageway sections created Default dates are created automatically when the RSL update processes are run for new amended carriageway sections in the loading table Compulsory Compulsory C Count E Estimate orD Default Every carriageway section requires a traffic count estimate which will need to be populated in the traffic count table Compulsory Compulsory Default C Auckland Transport Loading Table Field Name default_category Auckland Transport Database Operations Manual Field Description This field describes the category used for default values used in loading data based on the carriageway hierarchy and urban_rural type This field describes percentage of traffic that are cars This field describes percentage of traffic that are light commercial vehicles This field describes percentage of traffic that are medium commercial vehicles This field describes percentage of traffic that are heavy commercial vehicles type 1 Data Collection Guidance Notes Not required to be collected Ensure raw download data classifies according to the NZTA 2011 classification system based on which percentages are calculated Ensure raw download data classifies according to the NZTA 2011 classification system based on which percentages are calculated Ensure raw download data classifies according to the NZTA 2011 classification system based on which percen
46. to the LHS This will mean all existing layers will need to be moved and have an offset added Allowable VEINES dd mm yyyy dd mm yyyy 0 to 60 Default 0 Required by Software Compulsory Compulsory when certain conditions are met Compulsory 150 Required by Auckland Transport Compulsory Compulsory when certain conditions are met Compulsory Auckland Transport Pavement Layer Table Field Name full_width_flag estimate_status layer_strength Auckland Transport Database Operations Manual Field Description width is the average width of the pavement layer to the nearest 0 1m full_width_flag is a means of signalling if the layer extends across the full width of the carriageway This is a flag which indicates if the pavement layer data is based on known or estimated data The strength of the layer measured in CBR or UCS Data Collection Guidance Notes Pavement Layer width is collected using a calibrated measuring wheel It is the average distance along the length of the layer from edge of seal to edge of seal measured to the nearest 0 1m For uniform width seals this is straightforward to collect however for layers with varying width this needs to be collected by taking the average of the total number of readings taken at 50 to 100m intervals depending on the variation For layers whose widths vary greater than 0 5m over a 100m length consider collectin
47. typical FAQ s are also provided This document is designed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data RAMM Treatment Length Data Collection Guide Notes and FAQ s The following guide notes are to be used as a reference when carrying out activities that affect the RAMM treatment length updates The guide notes cover all the necessary information to accurately and consistently manage RAMM treatment length data in a consistent and accurate manner for all the mandatory fields that are required Key to Guide Note diagrams Active treatment lengths arrow denotes increasing direction Disabled treatment lengths arrow denotes increasing direction Start and end locations of je surfacing joins RP 326m Carriageway nodes Route positions Auckland Transport Auckland Transport Database Operations Manual 81 Establishing and Disabling Treatment Lengths Treatment lengths need to be established primarily on the top surface of the Surface Structure Table The process of automatic treatment length generation based on surface structure will insert treatment lengths within surfacing gaps These treatment lengths need to be disabled for TSA rating and NOMAD in the treatment length maintenance screen of RAMM for Windows In the case of a standard T junction the automatically generated treatment length between 0 and 19 that needs to be disabl
48. which are run by RSL overnight should check the latest status for counts 160 Required by Auckland Transport Required by Software Compulsory Compulsory Compulsory Compulsory Compulsory Allowable VEINES Looks up on table roadnames Compulsory Looks up on table carriageway 0 99999 LorN L Default Auckland Transport ELRES Field Name count_date time_of_day count_duration week_day Auckland Transport Database Operations Manual Field Description Date when physical traffic count was STARTED or estimate was revised added Lets you know if the row is a physical traffic count or an estimate This field describes the time of day when count occurred This field describes the analysis period used to obtain ADT values for physical counts This field describes the day of the week the count estimate was done added based on the count date This is a calculated field Data Collection Guidance Notes Use tube and permanent count download information from contractors to determine start date for the analysis and reporting in case of physical traffic counts Any values obtained from a physical traffic count are known as a count while any data added through desktop analysis e g in the case for new subdivision roads is called an estimate Only required to be noted if undertaking a part day count Use tube and permanent count download information from contract
49. wider If a surfacing spans the full width of the carriageway then you do not need to provide a surfacing width simply tick the full width flag This avoids the proliferation of strip seals running parallel to the main seals when the top surface profile of the road is generated in the surface structure table gt Surface Vvidth Length of Surface vVidth Resuracing _ gt Surface VYvidth Figure 4 2 9 2 Example of a surfacing with average widths What is Surface Function Surface function defines a surfacing into one of the following categories e 1 1 coat seal Auckland Transport Auckland Transport Database Operations Manual 34 e 2 2 coat seal M membrane seal R reseal An accurate surfacing table will have 1 coat seals for all corresponding pavement data gt 1 15 days older than the pavement date and have corresponding 2 coat seal gt 6 36 months older than the 1 coat data Two chip seals are commonly entered into the surfacing table as surface function 2 this is incorrect unless the two coat is a second coat Use surface material to correctly code single chip and multi chip seals How do deal with Surface Function when I put a membrane seal down Membrane seals are usually a chip seal waterproofing surface underlying an asphaltic concrete surfacing In this situation M should be used as the surface function for the membrane seal and the asphaltic surfacing has a surface f
50. 00 Required for Count C Not required Required for Count C Approx 100m east of Wairere N decimal 7 6 required Not required required Auckland Transport ELRES Field Name est_derived_from Auckland Transport Database Operations Manual Field Description This field describes the method used to populate new traffic estimates This field includes general comments relevant to the traffic count traffic_id is the unique asset id assigned to the traffic row addedc_on is the date that the data was added to the database Data Collection Guidance Notes Does not need to be collected The contractor can also provide the 85th speeds relating to the traffic count for population into this field as well as the permanent count site id if a permanent count For data collection of new traffic counts traffic_id is not required This field is not required for data collection Database Management Comments Check estimates for new subdivision roads are populated through estimating the number of vehicle trips along the length of road based on the number of properties Local knowledge modelling or the estimation module can be used to update estimates for other sections of road where traffic volumes have changed due to changes in the road network Ensure the notes field is populated as given in the AT data template for permanent count sites Avoid the use of commas and slashes in the
51. 4 1 7 4 1 8 Auckland Transport Database Operations Manual 10 What Fields are Collected and Why The Carriageway Data Dictionary appended outlines the data that must be collected and provided by suppliers carrying out activities that affect the Carriageway Table This data is required to ensure that the objectives of the Carriageway Table can be met What Resources are Required to Collect Carriageway Data To collect Carriageway data you will need the following equipment and reference material ATDOM which will assist you in identifying what specific data is required Current carriageway list which shows road ID s road names start and end locations and descriptions for each road A calibrated vehicle tripmeter with completed calibration form accurate to 1m per 1000m 0 1 A calibrated measuring wheel with completed calibration form accurate to 0 1m per 100m 0 1 Whatever electronic device your organisation needs to download the data from the counter An approved traffic management plan for the work activity to be undertaken RAMM data collection forms or equivalent How is the Database Updated The Carriageway Data Dictionary appended provides additional guidance to database technicians who have read write access to the RAMM Carriageway Table The database can be updated using 3 methods e Automated bulk uploading of Carriageway data through the RAMM Manager data import faci
52. 66 How do I record pavement details where have done widening Pavement data is treated the same as surfacings data where widening is concerned Refer to surfacing section for further details Note that the existing pavement record that runs through the area of widening may need to be split into three records when LHS widening occurs How short does a pavement layer need to be before don t put it into RAMM Any pavement renewal shorter than 50m should be loaded as a pavement repair in the Maintenance Cost table and not loaded into the Pavement Layer table unless the road section is a ramp or roundabout and is less than 50m long Do need to change existing pavement layer data when load new data New pavement layer data with exception to overlays must be integrated into existing pavement layer records This is mandatory when you have stabilised an existing layer or are undertaking LHS widening refer to offsets pavement layers described below When do populate the removed_date in the Pavement Layer Table If the existing pavement material has been removed or stabilised during pavement construction then it will need to be tagged as removed in the Database This is done by populating the removed_date field with the date that the pavement layer material was removed Typically this is at least 1 day before the new pavement layer date This is generally done using pavement builder such as when a pavement
53. 9 999 generated generated commercial vehicles zero when loading through import type 2 files This field describes the Not required to be populated as it is equivalent standard a calculated field when manual entry 0 000 System System axles ESA per heavy Not required to be collected is done usually populated with a 99 999 generated generated commercial vehicles zero when loading through import type 2 files Loading Table cage Data Collection Guidance Database Management Allowable Field Description Field Name Notes Comments Values wept Ensure raw download data This field is the sum of w classifies according to the NZTA ee heavy the pc_mcv pc_hcv_1 2011 classification system based Check totals of individual categories 0 100 omp lsory Required for E pc_hcv_2 and pc_bus eweh percente e add up correctly to pc_heavy Count Cc fields is E calculated This field calculates the Not required to be populated as it is ESA per heavy vehicle 3 calculateditield when man al entry 0 000 Required for esa_heavy P i y Not required to be collected is done usually populated with a Compulsory q ee categories MCV HCV1 99 999 Count C HCV2 and Bus zero when loading through import files load_method i field deseribes the Not required to be collected Not required to be checked C E S U V Not required Not required loading survey method and W Auckland Transport Loading Table Field Name counter_desc Auckla
54. 9 Compulsory 0 99999 B Both sides C Centre F Full width L Left N Not Applicable R Right U Unknown Allowable Values Compulsory only when certain conditions are met System generated Compulsory Compulsory _ System generated Auckland Transport Maintenance Cost Table Field Name added_on added_by Auckland Transport Database Operations Manual Data Collection Guidance Notes Field Description added_on is the date that the data was added to the database This field is not required for data collection added_by is the RAMM username of the organisation that entered the data This field is not required for data collection chgd_on is the date that the data was changed in the database This field is not required for data collection Required Allowable Values by Software Database Management Comments This date is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format System Generated added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column System Generated This date is automatically updated if you are changing data directly in RAMM for Windows If you are using the RAMM Manager Import facility you need to
55. 9 and 9999999 11 decimal 12 4 gt 99 9999 and 9999999 12 98 Required by Auckland Transport Compulsory Compulsory Compulsory when Optional certain conditions are met Auckland Transport Required by Software Carriageway Table Field Name gps_by gps_method_id map_gps_date map_gps_by map_import_dat e map_import_by rnm_edit_date Auckland Transport Database Operations Manual Field Description The organisation that collected the GPS data Unique identifier for GPS method used Populated when new GPS coordinates are supplied by the user The logon of the person who set the map_gps_date Populated with the date of the Critchlows map The logon of the person who ran the initial population of the map The date this section was last changed using network manager Data Collection Guidance Notes No data collection requirements No data collection requirements No data collection requirements No data collection requirements No data collection requirements Database Management Comments When new coordinates are replaced inserted into the map before a new map is supplied by RAMM When changes are made to the map co ordinates the logon of the person who made the changes Map import date This keeps a record of when the last change to the road section was made using network manager Allowable Values Looks up on organisation 1 Generic GPS de
56. Affect this Table The activities that affect the Treatment Definitions Table are when a new treatment is being used or when an old treatment is no longer used The table needs to be kept up to date with all possible treatment types that are programmed to be applied to roads on the network Only a database manager can update the treatment definitions The applicable period of the FWP is important because it specifies which years the particular treatment may be applied For example in years 1 3 very specific treatments such as RS35 reseal grade 3 5 or AC10 asphaltic concrete mix 10 can be applied and the treatment type and specific chip size should be known Treatments in years 4 are less detailed and only the general treatment type and general chip size is known For treatments beyond 10 years the treatment should be very generic CS or AC as beyond 10 years we are unlikely to accurately predict the specific chip size Who Provides the Data and How is the Database Updated Database managers are responsible for making sure that the treatments contained in the Treatment Definitions Table are an accurate representation of the treatments being physically undertaken in the network How Can This Database Operations Manual Help You Accompanying this Table Overview is the following section Auckland Transport Auckland Transport Database Operations Manual 54 Forward Work Programme Treatments Table 4 4 provides a description of the
57. Database Operations Manual 5 BACKGROUND Formation of Auckland Council The establishment of Auckland Council and its coming into power on 1 November 2010 resulted in a number of activities being implemented prior to this date One such activity was the creation of a single asset repository for the Council controlled organisation of Auckland Transport AT The Road Assessment and Maintenance Management RAMM system has historically been the primary transport asset repository for all Council owned and maintained assets The creation of Auckland Council resulted in combining seven previous Local Government Organisations LGO including their RAMM databases for Rodney District Council North Shore City Council Waitakere City Council Auckland City Council Manukau City Council Papakura District Council and approximately half of Franklin District Council Database Amalgamation The primary merging of the seven RAMM databases was managed by the Auckland Regional Transport Agency ARTA another previous Local Government Organisation with the work completed by RAMM Software Limited RSL who are the software developers and providers of RAMM Part of this process included combining seven previous individual lists for each of the 700 800 lookup tables for each database to form one for the Auckland Transport Database Consistency of Policy With each of the seven databases being managed by a separate organisation there exists differences in ap
58. How is the Database Updated The Loading Data Dictionary appended provides additional guidance to database managers who have read write access to the RAMM Loading table The database can be updated using four methods Automated uploading of bulk loading count data through the RAMM Manager data import facility preferred Manual addition updating and deleting of loading records in RAMM for Windows Manual updating of the estimates when making carriageway changes Automated updating of estimates based on current loading count data if a network estimate model exists Auckland Transport Auckland Transport Database Operations Manual 58 4 5 8 How Can This Database Operations Manual Help You Accompanying this Database Operations Manual are the following sections AT Data Template format as required by AT Loading Data Dictionary appended provides a column by column description of the RAMM Loading Table including what data is required how it is collected entered and managed and what are the allowable values Collectively these documents are designed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data Auckland Transport Auckland Transport Database Operations Manual 59 4 6 Maintenance Costs 4 6 1 4 6 2 Why is this Table Important The Maintenance Cost Table contains information regarding specific road asset maintenan
59. LAND RHS END ISLAND RHS Note The last carriageway section is usually only one lane Auckland Transport Auckland Transport Database Operations Manual 22 Hammerheads For roads with hammerheads set the main access road and hammerhead up as separate roads e g WILLIAM ST and WILLIAM ST HAMMERHEAD Survey the main access road from the road origin to the centreline of the hammerhead Survey the hammer head from one cul de sac through to the other describing the start and end points e g CUL DE SAC SOUTH It is also desirable to create a carriageway split where the main road intersects to avoid any confusion regarding which end to start the survey This is shown in the diagram below If the orientation of the hammerhead section is not obvious i e hammerhead does not run from east to west or north to south then house numbers may be used to describe the start end and name fields of the hammerhead William St Hammerhead Om 125m 60m _ ae m m p B m 52m William St Great South Rd Diagram 4 1 9 Definition of a Hammerhead Carriageway Section The carriageway section for Williams Street will be as follows Road 1 WILLIAM ST 0 52m GREAT SOUTH RD WILLIAM ST HAMMERHEAD Road 2 WILLIAM ST HAMMERHEAD 0 60m CUL DE SAC WEST WILLIAM ST and 60 125m WILLIAM ST CUL DE SAC EAST Auckland Transport Auckland Transport Database Operations Manual 23 Loop
60. Use the current conventions from the legacy areas until a new global convention is established Use the current conventions from the legacy areas until a new global convention is established Required Allowable Values by Software Char 4 Looks up on cway_group_1 Char 4 Looks up on cway_group_2 Char 4 Looks up on cway_group_3 Char 4 Looks up on cway_group_4 Char 4 Looks up on cway_group_5 93 Required by Auckland Transport Auckland Transport Carriageway Table Field Name house_start_lhs house_end_lhs house_start_rhs house_end_rhs coastal_inland Auckland Transport Database Operations Manual Field Description The house number of the left hand side at the start of the section The house number of the left hand side at the end of the section The house number of the right hand side at the start of the section The house number of the right hand side at the start of the section The general categorisation of the terrain for the road section Indicator if the road section is coastal or inland Data Collection Guidance Notes The house number of the left hand side at the start of the section The house number of the left hand side at the end of the section The house number of the right hand side at the start of the section The house number of the right hand side at the start of the section The general topography of the road section Not gen
61. ad_id of the road that the traffic count is counted estimated on carrway_start_m is the start of the carriageway relating to the road origin It identifies the section of road where the traffic count estimate is located This is measured in metres relative to the road origin This field describes whether a count or estimate is the latest count for the current location in terms of physical traffic counts or the carriageway section in terms of estimates Data Collection Guidance Notes Use the RAMM carriageway table list to obtain this information If you do not have this information provide the full roadname as a minimum Use the RAMM carriageway table list to obtain this information If you do not have this information provide the location of the count as a minimum Any new physical counts or estimates resulting from subdivision data collection would need to be identified with a latest tag Database Management Comments Ensure that the road_id provided on the RAMM update sheet correlates with the road name shown on the carriageway list Ensure that the carriageway_start_m provided on the RAMM update sheet correlates with the carriageway section under the roadname shown on the carriageway list If data is loaded through RAMM Manager then carrway_start_m is automatically assigned Ensure that the values used comply with the allowable value list If not populated default to L Latest The processes
62. ainage Crossings Review of all lookup tables for the matching tables that have been completed to date Finalising the form the final document be made available such as web based and downloadable in PDF format and how to receive and incorporate feedback updates Development of a training and certification accreditation process for both data collectors and database managers to ensure the knowledge contained in ATDOM is understood by suppliers and applied when collecting and managing the asset register Auckland Transport Auckland Transport Database Operations Manual 7 REFERENCE DOCUMENTS The following publications and manuals have been referred to for this work State Highway Database Operations Manual SM050 New Zealand Transport Agency May 2009 Franklin District Council RAMM Database Operations Manual Opus Consultants Limited 2010 Manukau City Council RAMM Database Operational Requirements Opus International Consultants Limited February 2012 revision RAMM Computer Users Manual CJN Technologies Ltd 1998 This is commonly referred to as the Yellow Book as it was contained in a yellow ring binder Local Authority Database Operations Manual PFM7 Transfund New Zealand 1997 Work Instruction for Waitakere City Council Road Network Treatment Lengths and Forward Works Programme 2009 Opus International Consultants Limited October 2009 Auckland Transports Code of Practice As Built Data Requirements Au
63. and Transport Auckland Transport Auckland Transport Database Operations Manual 118 Required by Auckland Transport Not tional a a Required by Software Allowable Values Field Description Data Collection Guidance Notes Footpath Table Field Name local_name is the local name that this local_name p footpath is known by Database Management Comments accuracy 6 Default no accuracy If this is left blank then the RAMM length_m is the The length of most footpaths is simply the end_m start_m however there are some exceptions For software will automatically update this value for most types of footpaths For certain position types you will need to length of footpath measured in metres footpaths that do not run directly parallel to the road the length may be different in which case you will need to collect the length adjustment and length adjustment reason data provide a length as not all footpath position types have an end_m Where the length_m is not equal to end_m start_m you need to populate both length_adjust_m and length_adjust_reason length_adjust_m 0 30000 Compulsory 7 length_adjust_m is the length that the calculated length end_m start_m needs to be changed by to reflect the true length of the footpath For footpaths whose length is not equal to end_m start_m you will need to collect the length adjustment information so that the tru
64. anding of footpath attributes notes is a free text that aren t captured elsewhere on field for collecting the RAMM update form Some any other typical comments include Enter only relevant comments Enter all information about FOOTPATH WIDTH VARIES ALONG comments in CAPITAL LETTERS Avoid non Free text 255 the footpath asset LENGTH text and numerical characters in your char that cannot be FOOTPATH SURFACING VARIES comments such as S etc inputted into any of ALONG LENGTH the other fields FOOTPATH SEVERELY DAMAGED FOOTPATH POSITION OFFSET VARIES ALONG LENGTH FOOTPATH AGE VARIES ALONG LENGTH It is the general tip for the assessor Not as_tip_note f Not required to be collected Optional when assessing the required asset Compulsory when Optional certain conditions are met Auckland Transport Footpath Table Field Name bridge_id collect_name collect_date added_on Auckland Transport Database Operations Manual Field Description bridge_id the footpath is attached to collect_name is the name of the organisation that collected the data collect_date is the date that the footpath data was collected added_on is the date that the data was added to the database Data Collection Guidance Notes Not required to be collected Use the organisation lookup codes to populate this field or alternatively provide an accurate description of the organisation that is res
65. are approximately 70 fields in the Footpath Table nearly half of these fields are mandatory The remaining half are either mandatory subject to certain conditions being met optional not required or generated by the RAMM software or other suppliers The reason for the collection of this data is to ensure sufficient information is known about footpaths location dimensions age and condition to enable intelligent and informed asset management related decisions to be made around the future management and maintenance of Auckland Transport s footpath assets What Resources are Required to Collect Footpath Data To collect footpath data you will need the following equipment and reference material ATDOM which will assist you in identifying what specific data is required Current carriageway information including Road ID s Road names start and end locations and descriptions for each road Current footpath information including Road ID s Road names start and end locations and descriptions for each footpath A calibrated vehicle tripmeter with completed calibration form accurate to 1m per 1000m 0 1 A calibrated measuring wheel with completed calibration form accurate to 0 1m per 100m 0 1 Auckland Transport 4 3 7 4 3 8 Auckland Transport Database Operations Manual 37 As built drawings for renewals and subdivision projects Pocket RAMM or similar device approved by Auckland Tra
66. ata obtained from contractor For estimates indicate duration based on ADT volume Ensure the unit for the analysis period is correctly populated for physical counts based on data obtained from contractor For estimates indicate duration based on ADT volume As counts loaded into RAMM are for the 7 day period not required to be populated Not required to be populated as added into notes field Allowable Values Varchar 20 1 0 999 9 e g 7 0 D Days or H hours Char 10 Required by Software Not required Required for Count C Required for Count C Not required Not required 137 Required by Auckland Transport Not required Required for Count C Required for Count C Not required Not required Auckland Transport Loading Table Field Name confidence survey_number est_derived_from Auckland Transport Database Operations Manual Field Description This field describes the statistical confidence of count readings Only associated with count type C This field describes the unique header for the Traffic loading file This field describes the method used to populate new loading estimates This field includes general comments relevant to the traffic loading count Data Collection Guidance Notes The contractor must ensure Quality Assurance checks as per AT traffic count service requirements are carried out Not required Does not need
67. ations Manual Help You Accompanying this database operations manual are the following sections RAMM Footpath Data Collection Guide Notes and FAQ s Section 4 3 9 includes diagrams and illustrations of standard footpath data collection conventions to ensure the data is collected consistently in the field Some typical FAQ s are also provided Footpath Data Dictionary appended provides a column by column description of the Footpath Table including what data is required how it is collected and entered and allowable values Collectively these documents are designed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data Auckland Transport Auckland Transport Database Operations Manual 38 4 3 9 RAMM Footpath Data Collection Guide Notes and FAQ s The following guide notes are to be used as a reference when carrying out RAMM footpath surveys The guide notes cover all the necessary information to collect RAMM footpath data in a consistent and accurate manner for all the mandatory fields that are required Key to Guide Note diagrams Increasing direction Start and end locations of footpath assets Carriageway nodes Route positions RP 326m Auckland Transport Auckland Transport Database Operations Manual Footpath Start Position for Normal Tee Intersection Te Dot 3 a ep d A Be a4 aE x Pa
68. bays and intersections contribute to the total carriageway area for calculation of approximate seal areas etc An example of a miscellaneous area would include parking bays Bus bays or stops may be in other user defined tables so check these as well as the bylaws as bus bays may be in here as well as bus stop signs in the signs table Allowable Values Char 1 I IrregularR Regular decimal 3 1 gt 1 and lt 60 1 Default value R smallint 4 gt 0 m and lt 9999 Default value of O smallint 4 gt 0 and lt 9 999 Required by Software Compulsory Optional Compulsory Compulsory 88 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory Auckland Transport Carriageway Table Field Name intersection controlled_by Auckland Transport Database Operations Manual Field Description The total area of traffic islands in m These areas are taken away from the total carriageway area Any extra area at intersections to be included in the total area calculation This is a system calculated field The owner of the road section i e the title holder The authority which controls the road section Data Collection Guidance Notes The total area m for all traffic islands that is located within the carriageway section This includes splitter islands kerb projection islands planted islands and short lengths of median islands if
69. between Parry and Harwood Streets and has a start on Parry Street at RP 210m on the LHS would be named PARRY HARWOOD WWAY RP210 LHS Walkways get their own separate Roadname where they have other assets that are required to be recorded against them For example they have drainage features bridges and or other structures lights signs bicycle hoops etc The footpath asset still gets recorded in the Footpath Table to ensure it gets rated with the other footpaths The Carriageway Table records the sections the walkway is broken into along with its locational and dimensional information Accessway or Walkway are commonly the type of hierarchy used for walkway Auckland Transport Auckland Transport Database Operations Manual 74 Where a walkway is connected to a road and does not have additional assets to be recorded against it then it does not have its own Roadname and is recorded in the Footpath Table for the road it is connected to Cycleway Naming Convention Onroad Cycleways These are considered as part of the carriageway and have their assets recorded accordingly Joint Footpath Cycleways Joint walkways cycleways that are recorded in the Footpath Table are not recorded as a separate road This avoids duplication Off Road Cycleways These are named ina similar way to walkways and require their own Roadname when they have other assets to be recorded against them i e drainage features bridges and or other str
70. cal boundary information such as ward and community board areas Urban and rural classification based on the NZTA definitions Information on the length of sealed and unsealed roads in the network NZTA maintenance group classification Other general characteristics such as road class pavement type hierarchy traffic volume and loading traffic management levels and average roughness data What is the Carriageway Table Used For The RAMM Carriageway Table is Auckland Transport s primary repository for all locational dimensional organisational and summary statistical information for each road section The table can be used to produce carriageway lists report network lengths by centreline and Auckland Transport 4 1 4 4 1 5 Auckland Transport Database Operations Manual 9 lane length and undertake further network length analysis by urban rural pavement type maintenance area and maintenance category The actual sectioning of the road to create carriageway sections is detailed in this table The same sectioning is used for all other asset tables in the database The Treatment Length Table is the only table that does not use this sectioning method However treatment lengths be sectioned by carriageways or more typically using the top surface seal seams What Activities Affect this Table There are 10 key activities listed that affect the Carriageway Table in terms of physical changes to the asset that must b
71. ce activities undertaken within the Auckland Transport roading network It includes the normal cost activities and the associated cost for completing that activity Cyclic activities are not required to be loaded into this table Specifically the RAMM Maintenance Cost Table includes Locational information such as the road the activity that was carried out the length side and position of the completed works The cost group specific to the schedule item The activity which was carried out The fault that instigated the maintenance activity The cost of the activity Quantity of the work completed for that activity Unit for quantity i e metres square metres each etc The date the activity was carried out The ability to tag items to a budget code so that spent to date and remaining budget can be calculated What is the Maintenance Cost Table Used For The RAMM Maintenance Cost Table is Auckland Transport s primary repository for all maintenance related activities of their road assets this generally excludes annual renewals such as pavement rehabilitation and resurfacing This table provides detailed information including cost quantity position activity type and when the maintenance activity was carried out This table is used for the following purposes As a key input into pavement predictive modelling Optimised decision making process at a strategic level i e net present value analysis or w
72. ced Flexible U Unsealed 1 ADT lt 100 2 ADT 100 500 3 ADT 500 2 000 4 ADT 2 000 4 000 5 ADT 4 000 10 000 6 ADT 10 000 20 000 7 ADT gt 20 000 Compulsory Compulsory Compulsory Compulsory 1 Class 1C Class C Auckland Transport Carriageway Table Field Name cway_hierarchy Auckland Transport Database Operations Manual Field Description Urban or rural zone The functional classification of the road section The number of traffic lanes The average lane width The length of the carriageway section in metres Data Collection Guidance Notes This is currently defined using the NZTA definition in the programme and funding manual It is based on the permanent posted speed A rural road is one that has a permanent posted speed greater than 70km hr urban is less than or equal to 70 km hr This information is generally obtained from the office Just record the number of traffic lanes Flush median and parking lanes are not counted as traffic lanes The average lane width for all lanes from left hand to right hand edgeline for the defined road section This is the actual length of the road and excludes the length from the kerb line out to the point where the two roads centrelines intersect z point Database Management Comments Make sure that you know exactly where the gazetted speed areas are to ensure the zone is correctly selected If in do
73. cility set c_surface_id 0 Ensure that the road_id provided on the RAMM update sheet correlates with the road name shown on the carriageway list When adding surfacing data it is considered best practice to review the underlying surfacing layers and match up to the new top surface seal joins to ensure accurate reporting in treatment length summarisation and ensure the data is easier to view in grid format This may require start and end displacements of underlying seals to be adjusted by up to 10m Allowable VEINES Looks up table roadnames 0 99999 Required by Software Compulsory Compulsory Compulsory 102 Required by Auckland Transport Compulsory Compulsory Compulsory Auckland Transport Surfacing Table Field AEG end_name northing_end Auckland Transport Database Operations Manual Field Description end_m is the end location of the surfacing seal join in metres relative to the location on the road that the surfacing end position is located on Data Collection Guidance Notes Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect end_m start_name is the description to be used for the start location of the surfacing Typically this field is simply SEAL JOIN end_name is the description to be used for the end location of the surfacing Typically this field is simply SEAL northing is the GPS reading in northings an
74. ckland Transport Auckland Transport Database Operations Manual 8 4 RAMM TABLES 4 1 Carriageways 4 1 1 What is a Carriageway 4 1 2 4 1 3 The RAMM system defines a carriageway as a section of road with homogenous traffic and loading volumes pavement type sealed unsealed structural bridge width number of lanes and urban rural classification along its length The organisational i e maintenance contractor and administrational i e ward or sub area aspects of the road also need to be homogenous over the length of a carriageway section A road may be broken down into multiple carriageway sections if any of the above criteria change along its length such as e The number of lanes change i e from 2 to 3 at the start of a passing lane e The speed limit changes to greater than 70km hr urban to rural e The width changes by more than 2 5m over a significant length typically gt 100m e Traffic volumes and or composition change significantly such as at major intersections e The road changes in surface type i e sealed to unsealed thin surface flexible to bridge Why is this Table Important The Carriageway Table contains dimension and road section characteristics and provides the principal framework for all road reserve assets to be attached to Specifically the RAMM Carriageway Table includes Dimensional characteristics such as length width number of lanes area and road reserve width Politi
75. classified counting is typically responsible for the provision of loading counting data that is compatible with RAMM Database managers are responsible for amending the estimates contained in the Loading Table when making changes the carriageway sections Auckland Transport 4 5 5 4 5 6 4 5 7 Auckland Transport Database Operations Manual 57 What Fields are Collected and Why The Loading Data Dictionary appended outlines the data that must be collected and provided by suppliers carrying out activities that affect the Loading Table What Resources are Required to Collect Loading Data To collect Loading data you will need the following equipment and reference material ATDOM which will assist you in identifying what specific data is required Current carriageway list which shows Road ID s road names start and end locations and descriptions for each road A classified counting programme approved by Auckland Transport Calibrated certified and accurate classified counting equipment A calibrated vehicle tripmeter with completed calibration form accurate to 1m per 1000m 0 1 A calibrated measuring wheel with completed calibration form accurate to 0 1m per 100m 0 1 Whatever electronic device your organisation needs to download the data from the counter An approved traffic management plan for collecting classified count data RAMM data collection forms or equivalent
76. code for the individual road Not 2 numbers Required Allowable Database Management Comments Values controlling authority Currently this is populated with the previous local government organisation codes The road region for Auckland Transport is Auckland with a road region code of 2 This field is currently unpopulated in the Auckland Transport Database as a code had not been added for Auckland Council this will need to be defined and added to the database Ensure a standard lookup is used for Auckland Council for consistency 158 Required by Auckland Transport Compulsory when certain conditions are met Compulsory To be confirmed Auckland Transport Roadnames Table Field AEG added_by Auckland Transport Database Operations Manual Field Description This defines the type of road asset added_on is the date that the data was added to the database added_by is the RAMM username of the organisation that entered the data chgd_on is the date that the data was chgd in the database chgd_by isthe RAMM username of the organisation that changed the data in RAMM Data Collection Guidance Notes This field will be populated by a database administrator This field is not required for data collection This field is not required for data collection This field is not required for data collection This field is not required for data collection Database Managemen
77. ct Manager prior to collection These forms are provided in good faith by Auckland Transport with responsibility for their currency remaining with the user Any inconsistencies found between the forms and the requirements in the manual shall be reported to the Manager Asset Systems and Monitoring
78. ct for intersections that are very close together lt 30m For rural roads intersections may be too far apart so another obvious and easily locatable but permanent physical feature such as a catchpit box culvert transformer or power pole may be used Rural carriageway sections generally should not exceed 3km Change in pavement type i e thin surfaced flexible T to structural asphaltic concrete S or T to unsealed U or to a bridge deck B etc Typically bridges longer than 50m have their own carriageway section Significant changes in traffic volume which occurs around major intersections and major accesses Changes in organisational area as recorded in the area field i e ward change Change in ownership i e end of public road and start of private road Significant width changes i e a lane gain or drop or width change gt 2 5m for a length of 100m or more A change from urban road lt 70 km hr to rural road gt 7Okm hr as defined by the NZTA definition SHA KELLY GROVE GREEN STREET SHA ROAD SECTION ROAD SECTION ROAD SECTION ROAD SECTION PAVEMENT EG CHANGE IN TYPES WHITE ROAD BLACK ROAD SHA Diagram 4 1 3 Example of Carriageway Sectioning Auckland Transport Auckland Transport Database Operations Manual 17 Roundabouts All large roundabouts are surveyed as a separate road Roundabouts are deemed large if approach islands are present Small roundabouts
79. cted Data Collection Guidance Notes Use as built drawings to collect this information This can be a subjective field to collect as the use of a footpath can change from day to day week to week and year to year As such the values you can choose allow for this The general rules apply for footpaths in the following areas Cul de sacs and dead end streets use 1 2 Local and sub collector roads use 2 3 arterials and collector roads use 2 4 around shopping precincts use 4 5 around schools use 4 5 Recreational areas such as parks and reserves use 3 4 A scooter is defined as a mobility scooter The use of mobility scooters is increasing therefore it is important to collect this information The general rules apply for footpaths in the following areas Hospitals use 2 3Retirement villages use 2 3Shopping precincts use 3 4Recreational areas such as parks and reserves use 3 4All other footpaths use 1 Database Management Comments Ensure that the pedestrian use data provided correlates to the area the footpath is located in Defined as 1 Low 2 Low medium 3 Medium 4 Medium high 5 High U Unknown Ensure that the scooter use data provided correlates to the area that the footpath is located in Defined as 1 Low 2 Low medium 3 Medium 4 Medium high 5 High U Unknown 121 Required by Auckland Transport Required by Software Allowable Values Looks up on table surf_bind
80. ction Guidance Notes If the section is on a bridge deck then select bridge If the top surface is concrete then select concrete If a single asphaltic treatment comprises a total depth greater than 80mm then it is considered structural AC If the top surface is unsealed select U for unsealed otherwise it will typically be a thin surfaced flexible pavement This is generally the most common type of pavement construction in NZ Based on traffic volume associated with the section Not collected in the field Database Management Comments When you receive the as built information it should contain a typical cross section that will allow you to identify the pavement type You will need to ensure that you have the surfacing details as well as the granular layers The default value is T for thin surfaced flexible Pavement use may change as the traffic volumes are updated in the database Ensure that any new traffic count volumes area reflected in this field All roads are generally class one unless defined and gazetted as class C Class C roads are defined as roads that are collector routes that may be used by heavy motor vehicles only for the purpose ofdelivery or collection of goods and passengers at a destination located on the class C road 85 Required by Auckland Transport Compulsory Compulsory Required Allowable Values by Software B Bridge C Concrete S Structural AC T Thin Surfa
81. cycling pct_recycled surf_recycled_cp nt pave_spec reconstructed Auckland Transport Database Operations Manual Field Description Does this layer contain recycled material Percentage of Recycled material Layer Component that is Re cycled Contract end user spec code Flag that determines if the layer remains undisturbed or is reconstructed Data Collection Guidance Notes Only populate if recycled components are present in the layer such as slag metal recycled AC recycled basecourse as shoulder material Only required if recycled materials used This is an approximate for the amount of recycled materials used in construction of the new pavement Only required if recycled materials used The specification covering the way the pavement construction contract is managed and warranted Most new layers will go in as undisturbed Existing layers may get reconstructed with the addition of lime or cement Database Management Comments Set to False if no recycled materials were used Set to yes if recycled materials were used Only required if recycled materials used Only required if recycled materials used Additional data manipulation is required when granular overlays have been stabilised as part of the rehabilitation project Some of the underlying pavement layers will need to be tagged as reconstructed if the stabilisation depth exceeds the overlay depth Required
82. d N If there is a sign posted name or well known local reference that is different to This is generally only populated where A local name used for car N external_name ark walkway cy l wa the database road name there is a common well known name that 35 characters Required Optional pars veey y then collect this information is different to the road name a and populate this field i e Countdown Car Park etc Auckland Transport Not required Roadnames Table Field AEG external_id road_region road_council Auckland Transport Database Operations Manual DJ ten Oo aXei do a Guidance Notes Field Description External ID that may link to another asset system The region code is obtained from the NZTA Programme and Funding Manual The road controlling authority region code This field does not have a data collection requirement and will be populated by a data administrator The two digit code for the road controlling authority the road is vested to Required by Software This field can be used to provide a linkage between one system to another For example in the legacy Manukau database this field was used to provide a link idtharacers Not between the RAMM road id and that used Required in Councils GIS system Any population of this field requires specific instruction from Auckland Transport staff This code is populated using the NZTA Not 2 numbers Required allocated
83. d eastings at the START of the surfacing easting is the GPS reading in northings and eastings at the START of the surfacing northing is the GPS reading in northings and eastings at the END of the surfacing Database Management Comments Refer to start_m Avoid populating this field if possible A standard SQL routine can be used to provide appropriate start and end names if required Avoid populating this field if possible A standard SQL routine can be used to provide appropriate start and end names if required Allowable Values 1 99999 Free text Free text decimal 12 4 gt 99 9999 and 9999999 9 decimal 12 4 gt 99 9999 and 9999999 9 decimal 12 4 gt 99 9999 and 9999999 9 103 Required by Auckland Transport Compulsory Compulsory Required by Software Not Required Required Auckland Transport Surfacing Table Field AEG easting_end gps_date gps_by gps_method_id Auckland Transport Database Operations Manual Field Description easting is the GPS reading in northings and eastings at the END of the surfacing gps_date is the date that the start and end data was collected gps_by is the organisation that collected the data gps_method_id is the ID of the method that was used to collect the data and indicates both the type of equipment used and the accuracy of that equipment Data Collection Guidance Database Management Notes
84. dated if you are changing data directly in This field is not required for data RAMM for Windows If you are System System collection using the RAMM Manager Import Generated Generated facility you need to add the date to this column in dd mm yyyy format chgd_on is the date that the data was chgd in the database added_by is automatically assigned if you are adding data via RAMM This field is not required for data for Windows If you are using the System System collection RAMM Manager Import facility you Generated Generated need to add your RAMM username to this column chgd_by is the RAMM username of the organisation that changed the data in RAMM Auckland Transport DATA COLLECTION FORMS Current available Auckland Transport data collection forms are listed within this section Electronic versions of the forms can be requested from the relevant AT project managers Current forms available for tables in RAMM are e Barrier Fence Railing e Berm e Bus Shelter e Bridge e Carriageway Structure e Carriageway Surface e Crossings Vehicle e Drainage e Footpath Cycleway e Islands e Minor Structures e Retaining Walls e Signs o Electronic Signs User Defined Table ex ACC e Street Lights e Stormwater User Defined Table ex ACC e Surface Water Channel As the structure of the RAMM database changes the forms will require updating The user should be aware of this and confirm the data requirements with the AT proje
85. dd the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column Allowable VEINES Required by Software System Generated System Generated 140 Required by Auckland Transport System Generated System Generated Auckland Transport Auckland Transport Database Operations Manual 5 5 Maintenance Cost Data Dictionary Maintenance Cost Table Field Name transaction_id transaction_date financial_year cost_group Field Description transaction_id is the Unique identifier for the Maintenance Cost Transaction batch_id is the RAMM batch_id for the Maintenance Cost Batch Header transaction_date is the date that the work was completed financial_year is the financial year 1 July to 30 June of the transaction e g 2011 12 cost_group is the maintenance cost group code for the activity carried out Data Collection Guidance Notes Not required for data collection purposes Provide the date in the correct format dd mm yyyy Future dates will be rejected Each schedule item must properly replicate a cost group Avoid use of OTHER Database Management Comments Allowable Values Automatically assigned by RAMM 0 9999999999 Each batch that is entered into RAMM is allocated a unique batch id En
86. developing a forward work programme What Activities Affect This Table There are six key activities that affect the Carriageway Surfacings Table in terms of physical changes to the asset that must be captured in RAMM to keep the table up to date The activities are General maintenance resurfacing with chipseals asphaltic concrete or slurries ensure that surface function is set to 2 for 2 coat or R for reseal depending on the function of the seal Milling of existing surfacings as a pre treatment to further resurfacing work ensure that the milled surface has removed date populated Area wide pavement treatments AWPT s where usually all existing surfaces are removed and new pavement constructed ensure that surface function is set to 1 and that all underlying surfacings have removed date populated Rehabilitations including rip and remake treatments where usually all existing surfaces are removed and existing pavement rehabilitated ensure that surface function is set to 1 and that all underlying surfacings which are removed as part of the rehabilitation have removed date populated Construction projects including new roads and road realignments ensure that surface function is set to 1 or M for membrane seals under asphaltic concrete surfacings Seal widening projects ensure that offset and width are populated for the surfacings associated w
87. do not have this information provide the full roadname as a minimum Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect start_m Start_m is not required for footpath position R remote from road You will need to know what the increasing direction of the road is before confirming the start_m Database Management Comments For new footpaths being added via RAMM for Windows RAMM will automatically assign a footpath_id For new footpaths being added via RAMM Manager Import Facility set footpath_id to 0 in the load file For existing footpaths being updated ensure that the footpath id that is provided with the update sheets matches the footpath that is being updated Ensure that the road_id provided on the RAMM update sheet correlates with the road name shown on the carriageway list Ensure that the footpath start_m is contained within the road length 114 Required by Auckland Transport 0 99999 Compulsory Compulsory Compulsory Compulsory Optional Required by Software Allowable Values Looks up on table roadnames Compulsory Not F text ti re a ee ee epee Required Auckland Transport Auckland Transport Database Operations Manual 115 Required Requires Footpath Table Field Data Collection Guidance Der Roe A RR EA Commerc Allowable b 3 by Field Name Description Notes amp Values Y Auckland Software Transport end_m is the end location in met
88. e ADT volumes need to be checked and updated based on latest traffic count ADT Pavement use bands in the carriageway table also need to cross checked when updating estimates Ensure that the direction lane is correctly populated especially for divided carriageways containing more than one lane in one direction Estimates can only be populated with B Both Lanes This is information required in relation to traffic modelling ensure peak volume is added into the notes field Allowable VEINES 1 999000 L Left Lane R Right Lane B Both Lanes L1 Left Lane 1 L2 Left Lane 2 L3 Left Lane 3 L4 Left Lane 4 L5 Left Lane 5 R1 Right Lane 1 R2 Right Lane 2 R3 Right Lane3 R4 Right Lane 4 R5 Right Lane 5 1 99999 163 Required by Auckland Transport Required by Software Compulsory Compulsory Compulsory Compulsory Not required Required for Count C Auckland Transport ELRES Field Name location_desc confidence traffic_ adjustment survey_number Auckland Transport Database Operations Manual Field Description This field describes the peak hour Only associated with traffic count C This field describes the site where the count was undertaken associated with NZTA networks Permanent site location ids have usually been included in the notes field This field describes the location of the count site This field describes the statistical confidence of
89. e Loading Table contains details on the composition of vehicle flow namely classification bins as per NZTA 2011 classification requirements Specifically the RAMM Loading Table includes Loading classification for carriageway sections relating to both physical counts and estimates Default values are also provided where there are no counts or estimates based on urban rural and carriageway hierarchy criteria Dates relating to when the last loading count estimate was updated added into the database Classification history at a particular location Notes in relation to the loading survey What is the Loading Table Used For The RAMM Loading Table is Auckland Transport s primary repository for all classified count data and loading estimate data Loading information is an important parameter in pavement design economic evaluations and for higher level asset management tools such as forward work programming treatment selection analysis pavement deterioration modelling and asset valuation What Activities Affect this Table There are three key activities that affect the Loading Table in terms of physical changes to the asset that must be captured in RAMM to keep the table up to date The activities are Changes to carriageway nodes resulting from new road construction or carriageway reviews Classified traffic counting Traffic and loading estimate reviews Who Provides the Data The supplier carrying out the
90. e Operations Manual 51 Condition Description 4 Poor aged footpath in poor condition requiring replacement in 1 5 years substantial evidence of repairs 4 extensive defects trip hazards ravelling extensive sections of repairs Auckland Transport Auckland Transport Database Operations Manual 52 Condition Typical Example s Description gt Ps e 5 Very poor aged and deteriorated footpath requiring replacement immediately extensive defects trip hazards chronic ravelling extensive cracking sections of failing repairs Auckland Transport 4 4 Auckland Transport Database Operations Manual 53 Forward Work Programme Treatments 4 4 1 4 4 2 4 4 3 4 4 4 4 4 5 Why is This Table Important The Treatment Definitions Table contains information regarding the treatments used in the forward work programme FWP Specifically the RAMM Treatment Definitions Table includes The code representing each treatment type A description of the treatment The period of the forward work programme where the treatment is applicable The funding group that the treatment belongs to What is the Treatment Definitions Table Used For The RAMM Treatment Definitions Table is Auckland Transport s primary repository for information regarding possible treatments that can be entered into the forward work programme What Activities
91. e RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column Allowable Values Required by Software System Generated System Generated System Generated 155 Required by Auckland Transport System Generated System Generated System Generated Auckland Transport Auckland Transport Database Operations Manual 156 5 7 Roadnames Data Dictionary Roadnames Table Field NEMS road id This is the unique road_id that is assigned to the road Data Collection Field Description Guidance Notes Not required to be collected in the field Add the Council approved name to the database The legal name of the road The name of the suburb the road is located in The name can be obtained from a local map List all suburbs if a road passes through multiple suburbs i e Great North Rd The name can be obtained from a local map The town the road is located in Required by Auckland Transport Required by Software Allowable Database Management Comments WET es This generally is a system generated number Where you want to keep the road id numbering consistent within the old legacy council area then the assigned road id will have to be updated to the next seque
92. e activity gps_by is the organisation that collected the data gps_method_id is the ID of the method that was used to collect the data and indicates both the type of equipment used and the accuracy of that equipment road_id is the RAMM road_id of the road that the footpath is on start_m is the end displacement in metres of the work relative to the location of the road origin Data Collection Guidance Notes Use the RAMM carriageway table list to obtain this information If you do not have this information provide the full roadname as a minimum Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect start_m Database Management Comments Ensure that the road_id provided on the RAMM update sheet correlates with the road name shown on the carriageway list Ensure that an start_m is provided for all work types that require a start_m Allowable Values decimal 12 4 gt 99 9999 and 9999999 9 decimal 12 4 gt 99 9999 and 9999999 10 Looks up on organisation 1 Generic GPS device 5 m 2 User clicked on map 10m 3 Update from RAMM Map 10m 4 Unknown no accuracy 5 Taken from asset no accuracy 6 Default no accuracy Looks up on table roadnames 144 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory Required by Software Auckland Transport Maintenance Cost Table Field Name
93. e can be achieved What Resources are Required to Collect Carriageway Surfacings Data To collect Carriageway Surfacings data you will need the following equipment and reference material Auckland Transport s Database Operation Manual ATDOM which will assist you in identifying what specific data is required Current carriageway list which shows road ID s road names start and end locations and descriptions for each road A calibrated vehicle tripmeter with completed calibration form accurate to 1m per 1000m 0 1 A calibrated measuring wheel with completed calibration form accurate to 0 1m per 100m 0 1 Contractor surfacing records Pocket RAMM or similar device if this is your preferred method of data capture RAMM data collection forms or equivalent How is the Database Updated The Carriageway Surfacings Data Dictionary appended provides additional guidance to database managers who have read write access to the RAMM Carriageway Surfacings Table The database can be updated using 2 methods Importing data from spreadsheets validating and moving to the Carriageway Surfacing Table preferred method for loading large amounts of data such as annual resurfacing records Auckland Transport 4 2 8 4 2 9 Auckland Transport Database Operations Manual 31 Manual addition updating and deleting of Carriageway Surfacings records in RAMM for Windows preferred method for
94. e captured in RAMM to keep the table up to date The activities include but are not limited to New road construction new carriageway sections need to be generated Existing road reconstruction sometimes that can result in changes to the pavement type from thin surfaced flexible to structural asphaltic concrete pavement Changes to existing carriageway nodes resulting from new road construction Changes to existing carriageway nodes resulting from carriageway reviews Seal extensions as this changes some of the characteristic fields such as pavement type and usually width Seal widening projects as this affects the width Minor safety works that result in additional lanes at intersections creating new carriageway sections as a result of changes to the carriageway width and number of lanes Speed review changes as the section may change from rural to urban Political maintenance boundary changes Other works that create a change to the existing data held within the Carriageway Table Who Provides the Data The supplier carrying out the physical work resulting in changes to the Carriageway Table is typically responsible for the provision of Carriageway data that is compatible with RAMM Database managers are required to ensure that all major work activities that could impact on the Carriageway Table are identified and the appropriate changes made to the RAMM database Auckland Transport 4 1 6
95. e length of the footpath asset can be entered into RAMM E J R and insome instances B K and M footpaths required this information to be collected Ensure that for footpaths where the length is not equal to end_m start_m this field is populated This is typically provided for the following footpath positions E J R L A Typically for all other footpath positions this does not need to be populated Compulsory when certain conditions are met Auckland Transport 119 Auckland Transport Database Operations Manual Footpath Table Field Name len_adjust_rsn Field Description len_adjust_rsn is the reason why the calculated length end_m start_m is not the true length of the footpath Data Collection Guidance Notes Self explanatory codes provide a description of the reason why the footpath length needs to be adjusted Guidance notes also provide examples of the various types of reasons for adjusting the length of a footpath asset Database Management Comments Avoid the use of UKN Unknown The following lookup codes need to be used CORNR Additional footpath on inside of Corner ANGLE Footpath is Angled to road COM Footpath is on a Common section CUL Footpath ends in a Cul de sac CYCLE Footpath is a Cycleway DUMMY Footpath is a Dummy of no length AWAY Footpath ends Away from road BYOND Footpath ends Beyond road PATH Footpath only LOOP Footpath Loops away
96. e road carriageway asset condition pavement and surfacing inventory and asset demand data that is used to model programme and prioritise future treatments and maintenance Specifically the RAMM Treatment Length Table includes Location information start and end displacements of treatment lengths Condition related information this is sourced automatically by the software from other tables such as the condition rating table and high speed data tables Physical attributes such as pavement and surfacing inventory this information is also sourced from other RAMM tables Asset demand such as traffic volumes this information is also sourced from other RAMM tables The key objective of this overview is to focus on the general principals around how the start and end displacements of treatment lengths are managed Accurate treatment lengths are the key starting point to robust forward work programming and network management Auckland Transport 4 10 3 4 10 4 4 10 5 4 10 6 Auckland Transport Database Operations Manual 79 What Activities Affect this Table There are four key activities that affect the Treatment Length Table in terms of physical changes to the asset that must be captured in RAMM to keep the table up to date The activities are New sub divisional roads and road realignments these require new treatment lengths to be created Road reconstruction projects these require existing trea
97. ected and Why The Pavement Layer Data Dictionary appended outlines the data that must be collected and provided by suppliers carrying out activities that affect the Pavement Layer Table The dictionary defines the minimum data required to meet the requirements of an accurate and consistent pavement layer table What Resources are Required to Collect Pavement Layer Data To collect Pavement Layer data you will need the following equipment and reference material ATDOM which will assist you in identifying what specific data is required Current carriageway list which shows road ID s road names start and end locations and descriptions for each road A calibrated vehicle tripmeter with completed calibration form accurate to 1m per 1000m 0 1 A calibrated measuring wheel with completed calibration form accurate to 0 1m per 100m 0 1 As built drawings including specific information pavement designs Details on stabilisation agents including percentage and type Auckland Transport 4 7 7 4 7 8 Auckland Transport Database Operations Manual 64 Pocket RAMM or similar device if this is your preferred method of data capture RAMM data collection forms or equivalent How is the Database Updated The Pavement Layer Data Dictionary appended provides additional guidance to database managers who have read write access to the RAMM Pavement Layer Table The database can be updated using
98. ed is shown in the diagram below Treatment Length Maintenance at Four Way Intersections Every section of every road needs to have only one treatment length assigned to it In the situation of a four way intersection the treatment length that makes up the intersection needs to be assigned to the major road whilst the dummy treatment on the minor road through the intersection is disabled as shown in the diagram below Auckland Transport Auckland Transport Database Operations Manual 82 Treatment Length Maintenance at Roundabouts A roundabout is treated in a similar way to a four way intersection however additional allowance needs to be made to account for the carriageway gap that exists within the roundabout for both the major road and minor road as shown in the diagram below The roundabout itself needs to have its own treatment length assigned so it can be assessed for condition and future treatments planned and prioritised just like any other section of road Note that the treatment lengths between the seal joins and the carriageway nodes are also disabled Managing Short Treatment Lengths Typically a treatment length needs to be at least 50m in length to allow sufficient length for condition rating and justify programming forward work treatments however there are some exceptions to this cul de sac turning heads small roundabouts etc Short sections of interlocking blocks pavers speed humps raised tables which
99. edestrians use the footpath C Cycleway only cycles use the footpath F Footpath the footpath is only used by pedestrians Allowable Values Required by Software Compulsory when certain conditions are met Compulsory when certain conditions are met Compulsory 126 Required by Auckland Transport Compulsory when certain conditions are met Compulsory when certain conditions are met Compulsory Auckland Transport Footpath Table Field Name maintained_by asset_owner use_default_rc original_cost Auckland Transport Database Operations Manual Field Description maintained_by is the organisation that is responsible for the maintenance of the footpath asset_owner is the organisation that owns the footpath asset This is the unique Identifier for the asset valuation standard replacement cost User default replacement cost assigned for asset valuation It is the original cost of installing or constructing the asset It is the replacement Cost of the asset Data Collection Guidance Notes For almost all footpaths the maintained_by field will be the organisation responsible for footpath maintenance for the Auckland Transport footpath network however there may be some footpaths that are maintained privately or by other organisations For almost all footpaths the asset_owner will be Auckland Transport footpath however there may be some footpaths that a
100. en eee j obtain this information usually If no additive agent is used leave Looks up on surf_additive adhesion used in the oy certain Compulsory included in spray dockets or seal blank surf_additive aine ER Data Collection Guidance Database Management Allowable Heauired Table Field Field Description by Notes Comments Values ANEIS Software binder conditions designs are met Compulsory s Use sealing records or seal designs to polymer_mod_pcnt is the ogee If there is polymer present in the when polymer_mod_pc obtain this information usually P percentage of polymer binder then this data must be Optional certain nt S Ta included in spray dockets or seal a modification in the binder entered conditions designs are met Not Not elastic_recover Not required Not required astie yecovery Notrenured noteare required Required k Not Not fteni int Not d Not d ccs chair ea SS ike ai tical a required Required Rate tothe reside Use sealing records or seal designs to application rate in litres per obtain ches ee ae u li 8 Ensure that the rate that has sq m for chipseals OR the y been provided matches the 0 2 to 9 99 Optional Compulsory included in spray dockets or seal binder in a mix type surf_material designs surfacing TASS typically the length x width or Ensure the difference between sealed_area is the the surfacing however sometimes length x width is
101. ent occurring Data Collection Guidance Notes The date the condition survey was undertaken No data collection requirements No data collection requirements No data collection requirements No data collection requirements Database Management Comments The value of this field needs to be considered as it is mostly populated with default data therefore being of no real value Use for risk assessment when defined in the assessment module For the risk analysis being undertaken in the assessment module the allocated risk likelihood of a defined risk event occurring The value of populating field with a default value needs to be considered Generally populate with default value Ue Use for risk assessment when defined in the assessment module For the risk analysis being undertaken in the assessment module the allocated risk consequence of a defined risk event occurring The value of populating field with a default value needs to be considered Generally populate with default value U Allowable Values Decimal 5 3 gt 0 and lt 99 999 Char 1 1 Rare 2 Unlikely 3 Possible 4 Likely U Unknown U Default value Decimal 5 3 gt 0 and lt 99 999 Char 1 1 Insignificant 2 Minor 3 Moderate 4 Major 5 Extreme U Unknown U Default Value Required by Software Compulsory when certain conditions are met System Generated Compulsor
102. er Looks up on table footpath_use E Looks up on table footpath_use To be confirmed Auckland Transport Auckland Transport Database Operations Manual Field Description Footpath Table Field Name bicycle_use is an indicative guide of the bicycle use of bicycle_use the footpath at the time that the footpath data is collected ere i ee extra_area is the additional area of footpath over and extra_area above the area calculated by the true length_m x width total_area is the total area of footpath and is total_area caleu lated by adding the extra_area to the true length_m x width area constructed is the date that the footpath was constructed DELICE IAEE EAS Notes The general rules apply for footpaths in the following areas Schools use 3 4 Shared pathways use 3 5 All other footpaths use 1 It is important that this area is collected as it affects the overall value of the footpath asset Extra area comes in the form of pram crossings sealed entrances to carparks and other buildings and changes in width This does not need to be collected in the field This data is automatically generated by the RAMM database once the data is collected This information can be obtained from the surfacing contractors sealing paving records In most cases a footpath is constructed over a number of days Please use the last date of construction as the constructed date Allowable Databa
103. erally collected Database Management Comments This was used to assist field crews with locating themselves Not so much on an issue with for those that use pocket RAMM or an equivalent device that locates the job in the field This was used to assist field crews with locating themselves Not so much on an issue with for those that use pocket RAMM or an equivalent device that locates the job in the field This was used to assist field crews with locating themselves Not so much on an issue with for those that use pocket RAMM or an equivalent device that locates the job in the field This was used to assist field crews with locating themselves Not so much on an issue with for those that use pocket RAMM or an equivalent device that locates the job in the field This can be done by general observation or can be assessed using topography maps with contours and set criteria for each category This field has not typically been collected for local authority databases Allowable Values char 10 char 10 char 10 char 10 char 1 F Flat M Mountainous R Rolling S Soft char 1 C Coastal l Inland Required by Software 94 Required by Auckland Transport Not Required Not Required Not Required Not Required Not Required Not Required Auckland Transport Carriageway Table Field Name asset_owner right_lanes lighting_category collect_name Auckland Transport
104. erated Integer 5 0 to 999999 This area is calculated by multiplying the length_m x cway_width field System No data collection requirements a Generated Auckland Transport Carriageway Table Field Name Auckland Transport Database Operations Manual Field Description Irregular or regular carriageway width indicator Road reserve width x 2 Area in m of miscellaneous areas The area of bus bays within the carriageway section Data Collection Guidance Notes Where the measured width variation is less than 1 0m use regular and if greater use irregular Typically urban kerb and channelled roads will be regular with rural roads often irregular due to seal widening on corners etc This is the road reserve width from boundary to boundary Often supplied with the road reserve to vest plans These are miscellaneous areas that exist within the carriageway section that are not bus bays islands or intersection areas i e parking areas etc These are areas that are not included in the measurement of the carriageway width or any part of the irregular carriageway width If the bus bay is not indented and included as part of the carriageway width then don t add it in the bus bay area field Database Management Comments This is not always the fence to fence width so ensure the vested survey plans are used Typically 20 1m was used for older subdivisions These areas as for bus
105. evelop and establish a framework for data collection data entry and maintenance that future phases could build upon Scope of High Priority Tables The 10 tables selected in phase one included Carriageway asset Carriageway Surfacing asset Footpath asset Forward Work Programme Treatments asset maintenance Loading asset demand Maintenance Cost asset maintenance Pavement Structure asset Road Names information Traffic asset demand Treatment Length information The tables have been ordered alphabetically and are not represented in order of priority Section five has the tables ordered in the same way for ease of finding the information required Auckland Transport Auckland Transport Database Operations Manual 4 2 4 Previous High Priority Recommendations from RAMM Status Report A number of high priority tasks were identified from the analysis undertaken while preparing the RAMM Status Report one of which was creation of the Database Operations Manual A full commentary and supporting analysis discussion is contained in the full report 2 5 RAMM Database Metadata Specifications In the preparation of the Data Dictionary in Section five reference has been made to the on line information provided in RAMM Manager by RAMM Software Limited RSL This information has been included in the report in good faith as the authors are not software or metadata experts 2
106. g these as separate records Please tick this if the pavement layer is full carriageway width Enter either E for Estimated or K for Known This information should be gained from laboratory test results Endeavour to provide layer strength as CBR instead of UCS Database Management Comments Width is only required when the pavement layer is not the full carriageway width Full width flag must be checked for all full width pavements and unchecked for non full width pavements Generally all new pavement data should be K Historic data that has been estimated will be tagged E Subgrade CBR strength needs to be provided for all new layers Allowable VEINES Y Yes N No N Default E Estimate K KnownDefault 0 to 120 for CBR O to 999 for UCS Required by Software Compulsory when certain conditions are met Compulsory Compulsory Optional 151 Required by Auckland Transport Compulsory when certain conditions are met Compulsory Compulsory Compulsory when certain conditions are met Auckland Transport Pavement Layer Table Field Name pave_subgrade pave_material pave_source Auckland Transport Database Operations Manual Field Description The method used to measure the layer strength Subgrade material The thickness of the pavement material The material used to construct the pavement layer The quarry that produced the pavemen
107. geway Surfacings Table includes e Road that the surfacing is on e The start and end locations of the surfacing e Surfacing dimensions such as length width and area e Surfacing material properties such as seal type and chip size aggregate source and properties such as PSV and ALD e Surfacing function i e first coat second coat membrane seals and reseals e Surfacing date e Surfacing additives flux cutter adhesion e Binder type and application rates e Surface reason the primary reason for undertaking the surfacing e Design life of the surfacing particularly if done under a performance specified P 17 specification Information on who carried out the surfacing work What is the Carriageway Surfacings Table Used For The RAMM Carriageway Surfacings Table is Auckland Transport s primary repository for all surfacing records It contains all of the current and historical information on all resurfacing activity including surfacings that have been removed A complete and accurate Carriageway Surfacings Table is necessary to Create an accurate top surface profile surface structure Provide accurate annual reporting on resurfacing achievement Provide accurate treatment selection reporting Provide input to research projects Auckland Transport 4 2 3 4 2 4 Auckland Transport Database Operations Manual 29 Provide a critical input into establishing and maintaining treatment lengths and
108. guous reseal surface spans across both the bridge and its approaches and the bridge is in the Carriageway Table with pavement type B and the approaches are pavement type T then three treatment lengths need to be established two for each Auckland Transport 4 10 7 4 10 8 4 10 9 Auckland Transport Database Operations Manual 80 approach and one for the bridge itself despite the top surface being uniform across the bridge and its approaches What Fields are Maintained As stated above a significant number of the fields in the Treatment Length Table are populated with data that is sourced from other tables However the following fields are not and their status in terms of required data is outlined in the table below Field Data Status Comment road _id Required Looks up on Roadnames tl name Not required tl start_m Required Can be automatically generated tl_end_m Required Can be automatically generated tl_disabled Required Defaults to N Refer to guide notes on disabling treatment lengths tl_cost_set Required Looks up on tl_cost_set How can this Database Operations Manual Help you Accompanying this Database Operations Manual is the following section RAMM Treatment Length Data Collection Guide Notes and FAQ s Section 4 10 9 includes diagrams and length data conventions to ensure the database is managed consistently in the database Some illustrations around standard treatment
109. h or berm width changes in hotosrabhs footpath these situations measure the p ee SMALLEST offset Not tional mes PE apie required Auckland Transport Footpath Table Field Name offset_kerb_end offset_Ihs_end footpath_position Auckland Transport Database Operations Manual Data Collection Guidance Notes Field Description footpath_position describes the general position of the footpath relative to the road and the road reserve Use the guidance notes to ensure you are using the correct code northing is the GPS reading in northings and eastings at the START of the footpath Database Management Comments Note that for certain types of footpath position specific data is required such as other_road_id other_side and other_start_m for J footpaths E Footpaths Ends away from road J Footpath Joins another road B Footpath runs parallel to the road but flush to the road reserve Boundary K Footpath runs parallel to road but flush with Kerb L Footpath Loops away from road M Footpath runs parallel to road and in Middle of berm R Footpath starts and ends Remotely from road U Footpath position is Unknown W Footpath runs parallel to road over Whole berm width P Footpath ends away from road in a Park or Reserve not generally a roading asset S Footpath is berm footpath for pedestrian Safety used for State Highways Allowable Values Looks up on footpath_ po
110. his Table There are five key activities that affect the Pavement Layer Table in terms of physical changes to the asset that must be captured in RAMM to keep the table up to date The activities are New road construction i e new subdivision roads and realignments Road reconstruction i e rehabilitation Auckland Transport 4 7 4 4 7 5 4 7 6 Auckland Transport Database Operations Manual 63 Rip and remake projects Structural AC projects Testpit investigation which usually provides some information on pavement thickness and subgrade properties should be added or used to validate existing data Who Provides the Data The supplier carrying out the physical changes to the asset is typically responsible for the provision of RAMM updates Therefore in terms of the activities that affect the Pavement Layer asset listed above the following suppliers are responsible New road construction including subdivisions and realignments the project consultant for the subdivision as specified in the as built process Pavement layer maintenance including rip and remake and pavement rehabilitation projects the project consultant and or contractor delivering the maintenance renewal project as specified in the as built process Structural asphaltic concrete pavement projects the project consultant and or contractor delivering the project as specified in the as built process What Fields are Coll
111. hole of life cost analysis Annual funding allocation process Preparing estimates for maintenance contracts Asset condition monitoring and development of maintenance cost curves Auckland Transport 4 6 3 4 6 4 4 6 5 4 6 6 Auckland Transport Database Operations Manual 60 What Activities Affect this Table The following types of typical maintenance activities need to be recorded as maintenance costs and entered into the RAMM Maintenance Cost Table Digout repairs for a section of failed pavement Milling repairs for a section of failed asphaltic concrete surfacing Replacement of vandalised signs Filling of a pothole on a suburban street Repairs to a concrete footpath Grading unsealed roads It is important to note that not all maintenance cost activities affect the Maintenance Cost Table Who Provides the Data The supplier carrying out the maintenance activities is responsible for the provision of RAMM maintenance cost updates They are also responsible for transferring the maintenance cost data into the Maintenance Cost Table on a monthly basis Specific activities and the supplier responsible are shown below Maintenance activities the project consultant and or contractor delivering the maintenance renewal project Scheduled items the consultant and or contractor is responsible for defining the schedule items with the right cost activity and fault codes Auditing
112. hway Database Operations Manual SHDOM to improve consistency accuracy and completeness of the Auckland Transport Asset Register Typical examples include duplicated lookup codes for the same activity significant variation in population of tables and individual fields and evidence of different approaches in terms of management of treatment lengths and forward work programming Robust asset management decision making relies upon the accuracy completeness and consistency of information contained in the asset register This includes quantity location condition and value of all assets owned and maintained by Auckland Transport When this information is to the appropriate standard reliable and accurate renewal and replacement programmes with respective funding requirements can be developed The reliability and confidence of decision support outcomes is directly linked to the quality of the asset register data Generally this comes from the asset management information system which can originate from a single source or multiple sources In order to obtain a consistent accurate complete and up to date asset register systems and processes are required This includes documentation of data collection methodologies data entry checks and ongoing continuous validation to provide total database management This Manual is the starting point to developing an overarching document for Auckland Transport and their suppliers It sets out a database manageme
113. icant 2 Minor 3 Moderate risk_consequence Not required to ecollecteduniess Typically enter U Major Compulsor Compulsor 4 specifically instructed ue 5 Extreme p y p Y U Unknown Default U 1 Very low 2 Low 3 Medium Not required to be collected unless 4 High specifically instructed Typically enter u 5 Extreme Compulsory Compulsory U Unknown Default U Date the risk value Not Not required to be collected Date Optional was last updated required You only need to collect this data for other_road_id is J Footpaths Use the RAMM the road_id of the carriageway table list to obtain this road that J information If you do not have this footpaths end on information provide the full roadname as a minimum Compulsory Compulsory Ensure that the road_id provided on the Looks up on when when RAMM update sheet correlates with the table certain certain road name shown on the carriageway list roadnames conditions conditions are met are met other_road_id Auckland Transport Footpath Table Field Name other_location other_side purpose Auckland Transport Database Operations Manual Field Description other_location is the displacement in m along the road that J footpaths end on other_side is the side of the road that the J footpath ends on purpose is the purpose of the footpath Data Collection Guidance Notes You only need to collect this data for J Footpaths Use the RAMM carriageway tab
114. il GIS or Google maps may be sufficient for this RAMM data collection forms or equivalent How is the Database Updated The Roadnames Data Dictionary appended provides additional guidance to database managers who have read write access to the RAMM Roadnames Table The database can be updated using 2 methods Automated upload of bulk Roadnames data through the RAMM Manager data import facility for large amounts of data not typically used as the roadnames table is relatively static Manual addition updating and deleting of Roadnames records in RAMM Network Manager This is the preferred option for smaller quantities of work relating to Roadnames Note that Roadnames cannot be updated through the RAMM for Windows screen Auckland Transport 4 8 8 4 8 9 Auckland Transport Database Operations Manual 71 How Can This Database Operations Manual Help You Accompanying this Table Overview are the following sections RAMM Roadnames Data Collection Guide Notes and FAQ s Section 4 8 9 includes information around standard Roadnames naming conventions such as abbreviations to ensure the data is collected consistently in the field Some typical FAQ s are also provided Roadnames Data Dictionary appended provides a column by column description of the Roadnames table including what data is required how it is collected and entered and what are the allowable values Collectively these documents are de
115. ine to the intersecting centrelines for carriageway sections that start at 3 or 4 way intersections Allowable Values integer 5 Required by Software Optional 87 Required by Auckland Transport Compulsory when certain conditions are met Extra length or reduced length_adjust_m length from the length_m value The reason for len_adjust_rsn adjusting the calculated length Looks up on length_adj_rsn This is a 5 character field and can only be populated with the allowable lookup values Compulsory when certain conditions are met This is only to be populated when a length adjustment is required and the reason obtained from the allowable lookups Ensure that the appropriate lookup code is used for describing the length adjustment reason Optional For sealed roads this is the width measured from kerb face to kerb face For a non kerbed carriageway this is the surfaced width including any sealed shoulders For unsealed roads this is the trafficable lane width The carriageway width should be measured and recorded at least every 100m In some instances the recorded sealed width may be channel lip to channel lip for a kerbed situation Be sure you know what is recorded for the existing data decimal 3 1 The width of the gt 0 5 and lt 99 9m carriageway tem This is a system y ia calculated field cway_width Compulsory Compulsory Default value 1 0 System Gen
116. is does not need to be collected in the field Not required to be collected unless specifically instructed Allowable Database Management Comments Values Be aware that the condition of as footpath can change always check the condition date before using the condition data as a guide to the condition of the asset Defined as 1 Excellent new or near new footpath 2 Good good condition but not new 3 Average aged footpath but still in reasonably good condition not requiring replacement for 5 20 years some minor repairs 4 Poor aged footpath in poor condition requiring replacement in 1 5 years substantial evidence of repairs 5 Very poor aged and deteriorated footpath requiring replacement immediately U Unknown condition is unknown Default U Date 1 Rare 2 Unlikely 3 Possible 4 Likely 5 Almost Certain U Unknown Typically enter U Default U 124 Required by Auckland Transport Compulsory Compulsory Required by Software u z Not tional Optiona required Compulsory Compulsory Auckland Transport Auckland Transport Database Operations Manual 125 Required Requires Footpath Table Field Data Collection Guidance A ena a Comers Allowable b a by Field Name Description Notes amp Values Y Auckland Software Transport Calculated caste ds This does not need to be collected in P Not consequence_wt weighting from Optional the field required assessment 1 Insignif
117. ith seal widening activities Generally the total combined surface equals the carriageway width Safety projects where resurfacing was a component of the project Top surface reviews and validations Who Provides the Data The supplier carrying out the physical changes to the asset is typically responsible for the provision of RAMM updates Therefore in terms of the activities that affect the Carriageway Surfacings Asset listed above the following suppliers are responsible Road construction and reconstruction including subdivisions realignments widening rehabilitations and area wide pavement treatments the project consultant for the project as outlined in the as built process Auckland Transport 4 2 5 4 2 6 4 2 7 Auckland Transport Database Operations Manual 30 Annual resurfacing projects the project consultant and or contractor delivering the resurfacing works Safety projects with a resurfacing component the project consultant for the safety project as outlined in the as built process Top surface reviews the consultant carrying out the top surface review What Fields are Collected and Why The Carriageway Surfacings Data Dictionary appended outlines the data that must be collected and provided by suppliers carrying out activities that affect the Carriageway Surfacings Table This Data Dictionary represents the minimum data requirements to ensure that the objectives of the surfacing tabl
118. ivided median Redoubt Rd 500 Start divided Smith Rd End Westbound median divided median Redoubt Rd 2000 2500 Smith Rd Start End divided divided median median 2 2 Redoubt Rd 1000 1500 Start divided End divided 2 Westbound median median Note that Redoubt Rd Westbound is measured in the direction of the traffic and the start node for the section is 0 not 300 i e 2800 minus 2500 i e do not confuse this approach with the NZTA approach for increasing decreasing sections of State Highway Auckland Transport Auckland Transport Database Operations Manual 15 v E on 1000m 1500m 2000m 2500m 2800m i i J i 1 i 1 Redoubt Rd i i 0m ee Se ee e p EES v we dee pom ioes ook Soe ix F i Redoubt Rd Westbound o i i 1 1500m 1000m 500m om a Qa v l E 7 Diagram 4 1 2 Example of Multiple Divided Sections gt Divided Road Eastbound Divided Road Westbound Om point for Road A in a Reads divided road situation Diagram 4 1 3 Zero Point for Side Road Onto a Divided Road Auckland Transport Auckland Transport Database Operations Manual 16 Creating Carriageway Sections Each road will have carriageway sections established using the standard rules for creating carriageway sections such as ROAD SECTION At an intersection Generally in urban areas carriageway breaks occur at all intersections expe
119. k programming treatment selection analysis TSA pavement deterioration modelling and asset valuation What Activities Affect this Table There are three key activities that affect the Traffic Table in terms of physical changes to the asset that must be captured in RAMM to keep the table up to date The activities are e Changes to carriageway nodes resulting from new road construction or carriageway reviews Traffic volume counting surveys Traffic volume estimate reviews Who Provides the Data The supplier carrying out the traffic counting is typically responsible for the provision of traffic counting data in a format that is compatible with RAMM Database managers are responsible for amending the estimates contained in the Traffic Table when making changes to existing carriageway sections such as inserting new carriageway sections or adding new carriageway sections Auckland Transport 4 9 5 4 9 6 4 9 7 Auckland Transport Database Operations Manual 76 What Fields are Collected and Why The Traffic Data Dictionary appended outlines the data that must be collected and provided by suppliers carrying out activities that affect the Traffic Table What equipment is required to collect Traffic data To collect Traffic data you will need the following equipment and reference material ATDOM which will assist you in identifying what specific data is required Current carriageway list which shows Road ID
120. l Authority P Private Char 3 looks up on organisation Compulsory 89 Required by Auckland Transport Compulsory when certain conditions are met Compulsory System Generated Compulsory Compulsory Auckland Transport Carriageway Table Field Name maintained_by managed_by road_group estimate_loading loading_status Auckland Transport Database Operations Manual Data Collection Guidance Notes Field Description The name of the roading contractor who is contracted to do the maintenance work on the road section Completed in the office The name of the roading authority or contractor who manages the road section Completed in the office NZTA groups for Maintenance Guidelines Is the estimate loading figure estimated or from traffic counting data Completed in the office The origin of the loading information Completed in the office System assigned based on ADT Database Management Comments Update to match the current contractor who has the contract to carry out the maintenance work on the network For some boundary roads the road section may be jointly owned but will be managed by one of the boundary Councils Waikato DC Hauraki DC or Kaipara DC Used for NZTA reporting on road groups System generated through status update process in RAMM Manager Comes from the loading table 90 Required by Auckland Transport e _ Compul
121. ld is not required for data collection Allowable Values Database Management Comments This date is automatically updated if you are changing data directly in RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column Required by Software System Generated System Generated 113 Required by Auckland Transport System Generated System Generated Auckland Transport Auckland Transport Database Operations Manual 5 3 Footpath Data Dictionary Field Description Footpath Table Field Name footpath_id Footpath_id is the unique asset id assigned to the footpath asset road_id is the RAMM road_id of the road that the footpath is on start_m is the start location of the footpath in metres relative to the location on the road that the footpath start position is located on The start_m is the distant from the start of the road to the start of the footpath DELICE IAOEE EAE Notes For data collection for new footpaths footpath_id is not required For data collection for existing footpaths which are being reconstructed the current footpath_id is required Use the RAMM carriageway table list to obtain this information If you
122. le list to obtain this information Measure the distance the same way you would with any other asset using a calibrated tripmeter or measuring wheel Check that you are measuring the distance in the right direction along the other road You only need to collect this data for J Footpaths Make sure you collect the right side of the road in relation to the increasing direction of the road that the J footpath ends on Footpath purpose is an onsite assessment of the purpose of the footpath Typically this field will either be B or F as there are very few cycle specific footpaths most cycleways will be used as shared pathways by both cyclists and pedestrians Database Management Comments Ensure that the other location displacement provided sits within the road length of the other road You can use aerial imagery to confirm that the data is correct Ensure that the other_side provided is correct in relation to the increasing direction of the other road You can use aerial imagery to confirm that the data is correct Defined as C footpath is located in Centre of road L footpath is located on the Left hand side of the road R footpath is located on the Right hand side of the road U footpath position is Unknown Typically this field will either be B or F as there are very few cycle specific footpaths most cycleways will be used as shared pathways by both cyclists and pedestrians Defined as B Both both cycles and p
123. lity preferred method for large amounts of load data but not the typical approach e Manual updating of some minor attribute data in RAMM for Windows preferred method for making those small minor changes such as changes to start and end names e All manual major or significant changes to dimensional related data can be done through RAMM Network Manager including adding new sections splitting joining and deletion Unsealed to sealed changes to carriageway sections can also be made in RAMM Network Manager Database managers require specific training in the use of RAMM Network Manager before using this module to ensure the desired outcome is obtained Auckland Transport 4 1 9 4 1 10 Auckland Transport Database Operations Manual 11 How Can this Database Operations Manual Help You Accompanying this table overview is the following sections RAMM Carriageway Data Collection Guide Notes and FAQ s Section 4 1 10 includes diagrams and illustrations around standard Carriageway data collection conventions to ensure the data is collected consistently in the field Some typical FAQ s are also provided Carriageway Data Dictionary appended provides a column by column description of the Carriageway table including what data is required how it is collected entered and managed and what are the allowable values Collectively these documents are designed to assist both data collectors and database managers achieve the ul
124. lt and chipseal footpaths most other footpaths are reconstructed Required by Software Footpath Table Field Data Collection Guidance Allowable i Pee Database Management Comments Field Name Description Notes Values ru_life is the remaining useful Optional as life of the footpath 3 Not required to be collected unless Typicallyemter N 7 rese O ee specifically instructed Tpialyemer n Apa N computsry ONR Iculat wes calci a ed This does not need to be collected in s Not Not condition_wt weighting from Calc Weight the field required required assessment Auckland Transport Footpath Table Field Name condition_date likelihood_wt risk_likelihood Auckland Transport Database Operations Manual Field Description condition is the condition of the footpath using the 1 5 scale of condition rating condition _date is the date that the footpath condition was assessed Calculated weighting from assessment Data Collection Guidance Notes This is a subjective guide to represent the average footpath condition over its length For brand new footpaths resulting from reconstruction or subdivision projects this will be 1 For footpaths requiring immediate replacement this will be 5 Use the guide to assist you in assessing condition of the remaining footpath condition This is usually the date that the RAMM data was collected however there may be some exceptions to this Th
125. lues Required by Software System Generated 101 Required by Auckland Transport System Generated Auckland Transport Auckland Transport Database Operations Manual 5 2 Carriageway Surfacing Data Dictionary Surfacing Table Field NEMS c_surface_id road_id Field Description c_surface_id is the unique asset id assigned to the surfacing asset For new surfaces being added to RAMM this is set to 0 and RAMM assigns a c_surface_id once the asset is added to RAMM For existing surfacings that are currently being updated in RAMM the current c_surface_id needs to be used as reference to ensure the correct surfacing is updated road_id is the RAMM road_id of the road that the surfacing is on start_m is the start location of the surfacing seal join in metres relative to the location on the road that the surfacing start position is located on Data Collection Guidance Notes For data collection of new surfacings c_surface_id is not required For data collection for existing surfaces which are being reconstructed the current c_surface_id is required Use the RAMM carriageway table list to obtain this information If you do not have this information provide the full roadname as a minimum Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect start_m Database Management Comments For importing large quantities of data through RAMM Manager Import fa
126. ly be populated from the office but when collection the data you will need to know what is to be populated Office populated Database Management Comments Check to ensure spelling is consistent and in accordance with the road naming conventions Check to ensure spelling is consistent and in accordance with the road naming conventions Existing population of this field relates to the previous local government organisations There is a user defined table called reporting area that contains the ward board and subdivision areas for Auckland Council The historic data has been populated for variety of purposes and AT will have to decide what data they will populate this field with such as board or subdivision could be possible options for reporting This relates to the urban and rural maintenance group numbered 1 to 7 84 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory Required Allowable Values by Software 35 Characters Optional 15 Characters Optional smallint 4 Urban and rural 1 to 7 35 Characters Optional Not Auckland Transport Carriageway Table Field Name pavement_type pavement_use road_class Auckland Transport Database Operations Manual Field Description The predominant type of underlying pavement for the carriageway section Approximate traffic volume band associated with the section Road class Data Colle
127. me i e from m to m quantity Maintenance Database Required Data Collection Guid Cost Table Field Description a Ee Aa Management Allowable Values by Notes Field Name Comments Software nit is the unit of qty_unit qey unit is toeunit o Avoid use of wrong unit of measure e g m m3 km ea Optional Compulsory measure Maintenance failure data is provided by the F P contractor on a monthly darts the failure aes ere must properly basis This is either Looks up on mc_failure Optional Optional Boy P transferred via RAMM Contractor or RAMM Manager input function asset id only needs to be provided ne f if you are carrying out maintenance asset_id is the unique 7 ye If the maintenance i work on or around a bridge rae identifier of any asset activity is related to a structure If you don t know the id aer 2 that the maintenance j specific asset then an Optional Optional er a f of the bridge asset please provide activity is being carried os asset_id should have outon some additional information about been provid d the bridge so this data can be p sourced by others Auckland Transport Maintenance Cost Table Field Name gps_by gps_method_id Auckland Transport Database Operations Manual Field Description northing is the GPS reading in northings and eastings of the maintenance activity easting is the GPS reading in northings and eastings of the maintenanc
128. nce notes The diagram shows that the increasing direction of Road A runs from left to right as indicated by the arrow When looking in the direction of the arrow footpaths on the LHS of the road are r i coded L and footpaths on the l RHS of the road are coded R Pad FAQ s m ae Footpath A LHS i A Is this approach the same Footpath A RHS ae for one way or multi lane 4 roads A Yes the direction of traffic or the number of lanes doesn t not change this Auckland Transport Auckland Transport Database Operations Manual 45 Footpath Offset Guidance notes Footpath offsets are the estimated distance to the nearest metre from the centre of the road to the side of the footpath closest to the road The offset of footpath A is shown by the white arrow FAQ s i Q How accurate do need to be at measuring offsets A You only need to estimate the offset Therefore you only Offset to Footpath A LHS need to record your estimated offset to the nearest metre p s p Q What do I do when the footpath asset changes along the 4 r length of the footpath PE A Record an average offset only Remember it is only an Offset to estimated offset only Footpath A n lt a lt Be pa oO a fe e ma Footpath A RHS wt 5 a Auckland Transport Footpath Position Auckland Transport Database Operations Manual 46 Position Ty
129. nd Transport Database Operations Manual Field Description This field describes the counter type used for collection of the loading data This field describes the number related to the analysis period used to obtain ADT values for physical counts This field indicates whether the analysis period is in days or hours This field indicates the start time of the analysis period in 24 00 hour format This field describes the site where the count was undertaken associated with NZTA networks Permanent site location ids have usually been included in the notes field Data Collection Guidance Notes Not required to be collected Use tube and permanent count download information from contractors to determine duration of analysis period in case of physical traffic counts The duration the tubes are actually placed out on site as this is usually longer than the analysis period Use tube and permanent count download information from contractors to determine duration in case of physical traffic counts The duration the tubes are actually placed out on site as this is usually longer than the analysis period Use tube and permanent count download information from contractors to determine start time in case of physical traffic loading counts Not required to be collected Database Management Comments Not required to be checked Ensure the analysis period is correctly populated for physical counts based on d
130. need to add your RAMM username to this column This date is automatically updated if you are changing data directly in RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column Allowable Values Required by Software System Generated System Generated System Generated 130 Required by Auckland Transport System Generated System Generated System Generated Auckland Transport 5 4 KE AELIG Field Name carrway_start_m Auckland Transport Database Operations Manual Loading Data Dictionary Field Description road_id is the RAMM road_id of the road that the traffic loading is counted estimated defaulted on carrway_start_m is the start of the carriageway relating to the road origin It identifies the section of road where the traffic loading count estimate default is located This is measured in metres relative to the road origin This field describes whether the traffic loading row is the latest for the current location in terms of physical counts or the carriageway section in terms of estimates and default values There can be only one latest count either a count estimate or default value if no estimate or co
131. ng records to collect this surf material Compulsory Compulsory surfacing information Note that surface_date will dictate the chronological order of For first coat seals on new pavement multiple surface layers in RAMM reconstruction excluding membrane not the surf_function Be careful or waterproofing seals use 1 For of membrane seals which must s Paa 1 First Coat Seal surf_function is the second coat seals seals immediately be treated as surf_function M y ar 2 Second Coat Seal function of the surfacing in placed over a first coat seal not be and typically feature underneath Compulsory Compulsory i M Membrane Seal terms of seal coat number confused with 2 coat seals use 2 For all first coat AC s Also if previous i R Reseal membrane seals use M For all other surfacings have been removed seals over a 2nd coat or a reseal use refer removed_date then this R may change the surface function of the surfacing that you are adding Auckland Transport Surfacing Table Field NEG use_calc_depth chip_2nd_size pave_source Auckland Transport Database Operations Manual Field Description surf_depth is the depth of the most recent surfacing layer A flag which determines if the depth of the seal should be calculated or provided chip_size is the grading size of the biggest chip for a chipseal or the top size aggregate in a mix surfacing chip_2 size is the grading size of
132. ng their length take an average width Always field check any data provided directly off plans and as built drawings If width x length does not reflect the true area of the footpath then provide the additional footpath area as extra area see field extra area Circle the correct surfacing material for the footpath For footpaths with multiple surfacing types choose the most predominant surfacing type Use as built information to collect this information There are maximum and minimum values for surfacing depth for each type of footpath surfacing Use as built drawings to collect this information Database Management Comments Ensure widths are consistent with typical footpath widths for the area and road type that the footpath is situated in Allowable VEINES 0 30000 0 30000 Looks up on surf _mat 0 500 Required by Software 120 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory Compulsory Auckland Transport Footpath Table Field Name pedestrian_use scooter_use Auckland Transport Database Operations Manual Field Description surf_binder is the binder type that was used in the surfacing of the footpath pedestrian_use is an indicative guide of the use of the footpath at the time that the footpath data is collected scooter_use is an indicative guide of the scooter use of the footpath at the time that the footpath data is colle
133. nsport if this is your preferred method of database capture RAMM data collection forms or equivalent How is the Database Updated The Footpath Table is typically updated by suppliers sending their collected RAMM data to Auckland Transport or a nominated consultant Trained and certified database managers then enter the data into RAMM In some instances the supplier collecting the data will also have read write access to the database in which case they will update the database directly The database can be updated using two methods Automated mass upload of new footpath records via the RAMM Manager data import facility Manual addition updating and deleting of footpath records in RAMM for Windows preferred or via Pocket RAMM Updating existing footpath records as a result of footpath resurfacing and reconstruction projects can be complicated The preferred way to undertake this work is in RAMM for Windows viewing the footpath data for each affected record in grid view than updating in detail view When the footpath records are updated always view the data again in grid view to ensure there are no overlaps or unwanted gaps in the footpath data Also ensure all relevant fields have been populated as outlined in the Footpath Data Dictionary The Footpath Data Dictionary provides additional guidance to trained and certified database managers who have read write access to the RAMM Footpath Table How Can This Database Oper
134. nt framework for the collection delivery management and desktop validation of road asset inventory and some core condition data This first phase contains the template database operations manual for 10 key RAMM asset tables It contains a table overview then provides additional key information on the mandatory fields and how these are populated Data Dictionary Guidance notes are provided on data collection and management for each section The ATDOM is a living document that will be continually updated and developed over time Further work is anticipated to complete templates for outstanding tables Any comments suggestions should be sent to Manager Asset Systems and Monitoring Auckland Transport Auckland Transport Auckland Transport Database Operations Manual 2 ACKNOWLEDGEMENTS In preparation of this manual there have been a number of organisations and individuals that have contributed Contributions range from verbal conversations to supply of written literature and are not in any priority order e New Zealand Transport Agency NZTA Making available electronic copy of SMO50 State Highway Database Operations Manual which is referenced in Section 4 of this document e Auckland Transport AT Staff For various inputs and review and taking the initiative to continue the pursuit of more robust asset registers e These organisations were involved in the consultation process for the RAMM Status Report portions of which are
135. ntial number in the assigned series Integer 6 Compulsory Compulsory Ensure the name that is added to the database is that approved by Council Use the road vesting road naming documentation received from Council In some cases the physical street name blade may be incorrect and should not be relied upon 35 Characters Compulsory Compulsory 25 Characters 30 Characters Compulsory To ensure consistency check what is recorded for roads near to the road being added or the road it comes off Record the suburb at the point of origin of the road in the suburb field of the roadnames table if the road passes through more than one suburb Ensure that the correct suburb that the road passes through is captured in the carriageway table Optional Compulsory To ensure consistency check what is recorded for roads near to the road being added or the road it comes off Auckland Transport Auckland Transport Database Operations Manual 157 Roadnames Required Resin ieee Data Collection Allowable by Table Field Field Description e aN Database Management Comments Valuas y ead Transport 4 Characters N N N N N N N N N N NENIE Software The postal code that relates Postal code confirmed from This is the postal code used for mailing postal_code i to the road office purposes arai ii lala ee aoa sl oo h z o ot ot ot ot ot ot ot ot Not required sh_ramp_type Not required Not Require
136. oad Try me Ensure the Om point is known and is ensure a physical point is used integer 5 Compulsory f well defined where possible that is unlikely to change over time and that is easy to find 83 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory Auckland Transport Carriageway Table Field Name end_name cway_area cway_sub_area Auckland Transport Database Operations Manual Field Description A description of the start point of the carriageway section If it is a road then it shall be spelt the same as the road name for consistency A description of the end point of the carriageway section If it is a road then it shall be spelt the same as the road name for consistency A defined area the road resides within A sub area of the carriageway area The NZTA Maintenance group as per State Highways Data Collection Guidance Notes Ensure the spelling is correct Try to make this point an intersection island nose etc or physical point that is easily identifiable in future Ensure the spelling is correct Try to make this point an intersection island nose etc or physical point that is easily identifiable in future This is often a political boundary such as Ward and would generally be entered form the office This has been used for community board areas previous maintenance areas and a variety of other uses It will most like
137. offset of a surfacing is simply the distance from the left hand edge of seal to the left hand edge of the offset surfacing Offset should be recorded where a lane treatment or widening activity gt 2 5m widening over a significant length gt 100m is undertaken For example if you construct a new 2 5m wide shoulder on the left hand side LHS on an existing 6m wide road then the shoulder widening work will have e Offset 0m e Width 2 5m The existing surfacing that runs concurrently with the shoulder widening will need to be updated to have e Offset 2 5m e Width 6 0m e Full width flag unchecked Make sure that all underlying surfaces are manipulated to match the new offsets resulting from the construction of the shoulder widening If a new 2 5m wide shoulder is constructed on the right hand side RHS of an existing 6m wide road then the shoulder widening will have e Offset 6 0m Auckland Transport Auckland Transport Database Operations Manual 33 e Width 2 5m e Full width flag unchecked The existing surfacing record that runs concurrently with the shoulder widening will need the full width flag unchecked What is the Definition of Surface Width Surface width is the average of several measurements from left hand edge of seal to right hand edge of seal Surfaces that span one or more intersection can have a greater nominal width than the surrounding carriageway sections as intersections are typically
138. on Full Name Abbreviation Avenue AVE DEC Terrace TCE RHS ane a war rm D a E If the same road name exists in two different parts of the network then the road name is written as road name with the ward in brackets Example CROSS ST DRURY CROSS ST RED HILL It is important that the naming conventions are consistent Refer to the Carriageway Table section 4 1 for further information on start and end name naming convention which follows the same general principles of Roadnames naming convention Service Lane Naming Convention The following naming convention applies where service lanes do not have a specific local name e g MCDUFF LANE To help find service lanes the service lane name will be recorded along with the RP i e the displacement of the service lane measured on the main road and side of the road on which the service lane resides i e EAST ST SERVICE LANE RP334 RHS This describes a service lane located on the right hand side of East St at displacement 334m The service lane is then surveyed as a separate road Roundabout Naming Convention Roundabouts are named in such a way that clearly identifies all roundabouts from one another In almost all cases a roundabout has more than one road associated with it and one of those roads will be more major than the other road The naming convention is as Auckland Transport Auckland Transport Database Operations Manual 73 follows MAIN RD MINOR RD RAB
139. onary appended provides additional guidance to database managers who have read write access to the RAMM Maintenance Cost Table The database can be updated using two methods Automated upload of bulk Maintenance cost data through the RAMM Manager data import facility on a monthly basis this is the preferred method and is required by AT unless specified differently in existing contracts Transfer of Maintenance cost data through RAMM Contractor on a monthly basis this is NOT the preferred option as there is insufficient validation checks of the data via loading Maintenance cost data needs to be loaded in monthly batches RCI updates are maintained by RAMM Software Limited Note that maintenance cost data is only deleted when a road is realigned Those maintenance cost records that were attached to the section of road that has been bypassed can be deleted How Can This Database Operations Manual Help You Accompanying this Database Operations Manual is the following section Maintenance Cost Data Dictionary appended provides a column by column description of the Maintenance Cost Table including what data is required how it is collected entered and managed and what are the allowable values This document is designed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data Auckland Transport Auckland Transport Database Operations Manual 62 4 7
140. or on NZTA networks Permanent count location site id information is usually added into the notes field Allowable VEINES 1 up to 52 Q1 Q2 Q3 or a4 0 99999 Looks on tc_count_site Required by Software Optional System Generated Optional Optional 162 Required by Auckland Transport System Generated System Generated Required for Count C Not required Auckland Transport Traffic Table Field Name Auckland Transport Database Operations Manual Field Description This field gives you the Average Daily Traffic volumes for the count C or Estimate E based on the count duration This field describes the direction lane in which the count was undertaken This field describes the average traffic volumes for the peak hour Only associated with traffic count C Data Collection Guidance Notes Use tube and permanent count download information from contractors to determine ADT in case of physical traffic counts Methodology of collection quality assurance as described in contractors methodology You will need to know what the increasing direction of the road through the road schedule before confirming the direction lane Use tube and permanent count download information from contractors to determine the peak hour traffic Database Management Comments Check ADT volumes against historic data if available at same location to ascertain data validity Estimat
141. ors to determine duration in case of physical traffic counts The duration the tubes are actually placed out on site as this is usually longer than the analysis period Use tube and permanent count download information from contractors to check the count day Database Management Comments Ensure the date field is correctly populated as this determines whether a count or estimate is the latest or not For physical count data this is the date when the count was STARTED for analysis volume purposes For estimates the date when the estimate was revised added due to new roads or carriageway sections created Every carriageway section requires a traffic count estimate which will need to be populated in the traffic count table Should be noted only if part day count is to be entered into RAMM Ensure the duration is correctly populated for physical counts based on data obtained from contractor For estimates indicate duration based on ADT volume As this is a calculated field there is no need to populate the data Allowable VEINES dd mm yyyy C Count or E Estimate AM or PM 24H 24hours 3H 3hours or 7D 7 Days 1 Monday 2 Tuesday 3 Wednesday 4 Thursday 5 Friday 6 Saturday 7 Friday 161 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory Required by Software Not required unless part Optional p day count completed System Gene
142. parallel to the road over the Whole berm width no mowable or landscaped berm between the road and the boundary s Footpath occupying whole berm width P Footpath ends away from road in Park or reserve Note Not to be used S Footpath is berm footpath for pedestrian Safety Note Not to be used Auckland Transport Auckland Transport Database Operations Manual Footpath Condition 49 Footpath condition is the average subjective condition on a scale of 1 excellent to 5 very poor for an individual footpath section Use the comments field to collect information relating isolated defects that require immediate intervention condition rating table Note that detailed footpath condition data can be found in the footpath Condition Typical Example s Description 1 Excellent new or near new footpath No defects Less than or equal to 5 years old 1 Auckland Transport Auckland Transport Database Operations Manual 50 Condition Typical Example s Description g 2 Good good condition but not new No defects Greater than 5 years old 2 3 Average aged footpath but still in reasonably good condition not requiring replacement for 5 20 years some minor defects or repairs such as cracking 3 ravelling discolouration short sections lt 5m of repaired and or resurfaced areas Auckland Transport Auckland Transport Databas
143. pical Example s Description Footpath Ends away from the road has a start displacement but no end displacement E Footpath has a length requiring a length adjustment E Footpath Joins another road has a start displacement but no end displacement requires a start displacement on both roads requires a side on each road has a length requiring a length adjustment Auckland Transport Auckland Transport Database Operations Manual 47 Position Typical Example s Description Footpath runs parallel to the road but flush with the Boundary no mowable or landscaped berm between the road reserve boundary and the footpath mowable or landscaped berm between the footpath and the road kerb B Footpath runs parallel to the road but flush with the Kerb no mowable or landscaped berm on the road side of the footpath mowable or landscaped berm between the footpath and the boundary K L Footpath Loops away and joins back onto the road Auckland Transport Auckland Transport Database Operations Manual 48 Position Typical Example s Description M Footpath runs parallel to the road in the Middle of the berm there is a mowable or landscaped berm on either side of the footpath between the kerb and the boundary R Footpath starts and ends Remotely from the road U Footpath position is unknown Note Not to be used Ww Footpath runs
144. ponsible for collecting the data Provide the date that the RAMM data was collected This field is not required for data collection Database Management Comments Where a footpath exists on a bridge that section is recorded against the bridge This ensures no double counting of assets for valuation etc This date is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format Allowable Values Looks up on organisation Required by Software System Generated 129 Required by Auckland Transport Compulsory when certain conditions are met Compulsory Compulsory System Generated Auckland Transport Footpath Table Field Name added_by Auckland Transport Database Operations Manual Field Data Collection Guidance Description Notes added_by is the RAMM username of the organisation that entered the data This field is not required for data collection chgd_on is the date that the data was changed in the database This field is not required for data collection chgd_by is the RAMM username of the organisation that changed the data in RAMM This field is not required for data collection Database Management Comments added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you
145. proach methodology and recorded data that need to be understood managed and updated to provide a consistent database over time for the whole Auckland Council Collaborative Approach Data Custodians Responsibility around maintenance and management of the Council asset data now becomes a joint responsibility between three main parties Auckland Transport Systems and Monitoring Road Corridor Maintenance and their contractors and three asset management consultants each awarded one contract area north central and west and south Therefore it is vitally important to define clear roles and responsibilities and documented guidelines to ensure the database is maintained as one with consistent rules and metadata populated within each table Future Actions The current form of the Auckland Transport Database Operations Manual ATDOM addresses the first phase of priority actions In order to progress the ATDOM further the following phase needs to be implemented Auckland Transport Auckland Transport Database Operations Manual 6 Complete the following tables in a format that is consistent with this phase one document Updated specifications such as those prepared for the recent contracts will need to be considered i e road rating in the road corridor maintenance contracts and High Speed Data HSD specifications from the HSD contract Rating Roughness High speed roughness High speed texture High speed rutting Dr
146. rated Auckland Transport ELRES Field Name count_site_id Auckland Transport Database Operations Manual Field Description This field describes the week the count estimate was done added based on the count date This is a calculated field This field describes the quarter of the year the count estimate was done added based on the count date This is a calculated field location is the displacement of the physical count in metres relative to the location on the road that the count is located on This field describes the unique count site used for NZTA networks and the traffic estimation module Data Collection Guidance Notes Use tube and permanent count download information from contractors to determine the count week Use tube and permanent count download information from contractors to determine the quarter Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect location You will need to know what the increasing direction of the road is before confirming the location Not required to be collected Database Management Comments As this is a calculated field there is no need to populate the data As this is a calculated field there is no need to populate the data Ensure that the location is contained within the road carriageway length Not required to be populated for estimates Not required to be populated unless using traffic estimation module
147. re owned privately or by other organisations that need to be in RAMM Not required to be collected Not required to be collected Not required to be collected Not required to be collected Database Management Comments maintained_by needs to be updated whenever there is a change in the organisation responsible for maintenance of the footpath Enter the value in the database if the cost information is available 127 Required by Auckland Transport o Compulsory Not Required by Software Allowable Values Looks up on organisation Looks up on Compulsor asset owner P Y System Generated Looks up on av_standard_rc D Default U User System Generated System Generated Auckland Transport Auckland Transport Database Operations Manual 128 Required by Auckland Transport System 0 333399 Generated Required by Software Footpath Table Field Data Collection Guidance Allowable rene Database Management Comments Field Name Description Notes Values It is the depreciated replacement cost of the asset Not required to be collected Date when the last valuation_date valuation was Not required to be collected carried It is the annual System annual_drc_value depreciation of the Not required to be collected Optional y Generated asset System Optional Please provide any comments that may assist with the entry of data into RAMM and improve the underst
148. res Compulsory of the footpath end_ eae tor footpaths Ensure that an end_m is provided for all when with type E ends away from road J oh h relative to the B footpath position types that require a 0 99999 Optional certain joins another road R remote starts nn location on the road and ends away from road footpath end_m conditions that the footpath Y i are met end is located on A Not end_desc Free text Optional S Required Please avoid the use of U Unknown ie C footpath is located in Centre of road side is defined as The left side of the road is on your p C Centre ae L footpath is located on the Left hand side the side of the road left when you are looking in the L Left y sth igs of the road Compulsory Compulsory that the footpath is increasing direction of the road R Right R footpath is located on the Right hand located on Avoid the use of Unknown gt U Unknown side of the road U footpath position is Unknown required Offset is the ESTIMATED distance offset is defined as estimated to the nearest 1m based offset is critical for plotting footpaths in the distance in on observations made from the RAMM Map View the footpath in RAMM metres from the survey vehicle Offsets can vary h Map to ensure that offset provided 0 200 Optional Compulsory centreline of the along the length of a footpath as f matches what is observed in aerial road to the road widt
149. riageway length 3 000m Auckland Transport Auckland Transport Database Operations Manual 12 Exceptions to these should be avoided but will be required in certain circumstances Generally the length of a carriageway section is equal to the end metres minus the start metres However for first carriageway section of most roads starting from a three way or four way intersection the length needs to be adjusted to be the end metres minus the start metres less the distance between the intersecting centreline of each road to the kerb line This length adjustment needs to be completed using the length adjustment option This also needs to be done for roads that end at a three way or four way intersection Diagram 4 1 1 demonstrates this length adjustment End 84m Adjusted Length 80m Distance from centreline to kerb 4m Start Om located at intersecting centrelines Diagram 4 1 1 Example of Carriageway Length Adjustment Auckland Transport Carriageway Table Data The following data is non dimensional data that cannot be measured on site but is still required for collection Guidance is provided below on how this data is assessed Carriageway Field Pavement Type B C S T U Pavement Use 1 2 3 4 5 6 7 Lanes 1 2 3 4 5 6 7 8 Urban Rural U R Carriageway Area Hierarchy Assessment Method Based on visual assessment on site This depends upon the average dail
150. rmation should be obtained for all new roads through the regulatory process Be careful not to record to much in this field as you can easily sort or filter on this information Avoid the use of commas dashes slashes and hyphens Optional varchar 255 This field is not currently being used at all varchar 255 This date is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format System Generated added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column System Generated 100 Required by Auckland Transport System Generated Compulsory when certain conditions are met Optional Not Required System Generated System Generated Auckland Transport Carriageway Table Field Name Auckland Transport Database Operations Manual Field Description chgd_on is the date that the data was changed in the database Data Collection Guidance Notes This field is not required for data collection Database Management Comments This date is automatically updated if you are changing data directly in RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format Allowable Va
151. road being measured At all poorly defined intersections well defined and easily locatable features such as sumps or power poles may also be used to further define the node e g SMITH ST SUMP LHS means that the node is located at Smith St adjacent a sump on the left hand side The following diagrams show methodologies for dealing with typical carriageway start and end point situations Auckland Transport Auckland Transport Database Operations Manual 25 Defining Carriageways Start and End Points Right Angle Intersection gt To Garden Gr 391m William St Great South Rd Start End carriageway sections at Tee of Intersection 391m Great South Rd From SH 2 Diagram 4 1 11 Carriageway Section Definitions for a Through Road Making a Right Angle Turn in an Intersection The carriageway sections for Great South Road will be as follows 0 391m SH 2 WILLIAM ST AT TEE 391 689m WILLIAM ST AT TEE GARDEN GR Auckland Transport Auckland Transport Database Operations Manual 26 Defining Carriageways Start and End Points Acute Angled Intersection William St _ _ mal Increasing direction 3016m Great South Rd 3850m Garden Gr Diagram 4 1 12 Carriageway Section Definitions for Intersections at an Acute Angle The carriageway sections for Great South Road will be as follows 3016 3850m
152. rrect chronological order for multi layered surfacing projects such as membrane seals under asphalts If you are entering a seal and the date of construction is only estimated use 01 01 XXXX as the surface_date Ensure that the underlying surfacings of any asphaltic concrete surfacing projects have not been milled off removed If the surfacings have been milled off then the date that the milling work was completed is the removed_date This also applies for any surfacings recycled or removed as part of pavement rehabilitation works For offset and partial width surfacings ensure that the carriageway width is updated and seal widths do not create strip seals when top surface is regenerated after the next full width resurfacing treatment Allowable VEINES dd mm yyyy dd mm yyyy decimal 3 1 surf_width gt 0 5 lt 60 0 Required by Software Compulsory Compulsory when certain conditions are met Compulsory 105 Required by Auckland Transport Compulsory Compulsory when certain conditions are met Compulsory when certain conditions are met Auckland Transport Auckland Transport Database Operations Manual 106 Required by Auckland Transport full_width_flag is a means YN full width fla of signalling if the surfacing Please tick this if the surfacing is full Please tick this if the surfacing is Sanuulber Campulson Te extends across the full width full
153. rt Required for Count C Compulsory Auckland Transport Loading Table Field Name count_site_id survey_date load_status Auckland Transport Database Operations Manual 133 Field Description This field describes the unique count site used for NZTA networks and the traffic estimation module Date when physical traffic count was started or estimate was revised added Lets you know if the row is a physical traffic count or an estimate Data Collection Guidance Notes Not required to be collected Use tube and permanent count download information from contractors to determine start date for the analysis and reporting in case of physical traffic counts Any values obtained from a physical traffic count are known as a count while any data added through desktop analysis e g in the case for new subdivision roads is called an estimate Required Required by by Auckland Software Transport 1 Allowable VEINES Database Management Comments Not required to be populated unless using traffic estimation module or on NZTA networks Permanent count location site id information is usually added into the notes field Ensure the date field is correctly populated as this determines whether a count or estimate is the latest or not For physical count data this is the date when the count was started for analysis volume purposes For estimates the date when the estimate was revised added due
154. s This case is similar to hammerheads with the loop section being set up as a separate road e g WILLIAM ST LOOP Separating these elements into individual roads allows clear identification of each element and the start and end locations for each section This is shown in the diagram below William St Loop William St Great South Rd Diagram 4 1 10 Definition of a Loop Carriageway Section The carriageway section for Williams Street will be as follows Road 1 WILLIAM ST 0 81m GREAT SOUTH RD WILLIAM ST LOOP Road 2 WILLIAM ST LOOP 0 345m WILLIAM ST WILLIAM ST Auckland Transport Auckland Transport Database Operations Manual 24 Intersections In the interests of accuracy an attempt has been made to reduce the amount of ambiguity that exists at intersections The following rules have been applied when determining carriageway start end points For both marked and unmarked intersections approaching at a right angle the centre of the intersection is used For both marked and unmarked intersections approaching at a small angle the centre of the intersection is used For marked intersections approaching at an acute angle the point of the marking or middle of the median island will be projected at a right angle to the road being measured For unmarked intersections approaching at an acute angle the middle of the intersection will be projected at a right angle to the
155. s information usually included in spray dockets or seal designs Use sealing records or seal designs to obtain this information usually included in spray dockets or seal designs Database Management Comments Ensure that the surf_binder provided is compatible with the surface_material and surf_function If no flux is used enter 0 If no cutter is used enter 0 If no cutter was used leave blank If no adhesion is used enter 0 If no adhesion agent is used leave blank Allowable VEINES Looks up on surf_binder E180 E80 B180 B80 B60 PORT WATR O0to9 0 Default 0 to 20 0 Default KERO Kerosene OTHR Other TURP Turpentine Oto5 0 Default Looks up on surf_adhesion Required by Software Compulsory Compulsory Compulsory Compulsory when certain conditions are met Compulsory Compulsory when certain conditions are met 109 Required by Auckland Transport Compulsory To be confirmed Compulsory Compulsory Compulsory Compulsory Auckland Transport Auckland Transport Database Operations Manual 110 Required by Auckland Transport additive is the amount of oe S to 0 to 99 additive additive in pph used in the i y If no additive is used enter 0 Compulsory Compulsory h included in spray dockets or seal binder 0 Default designs Compulsory heon Use sealing records or seal designs to surf_additive is the type of ana m wh
156. s up on asset_owner smallint 1 gt 1 and lt 9 smallint 1 gt 1 and lt 10 char 3 D P1 Pedestrian 1 P2 Pedestrian 2 P3 Pedestrian 3 P4 Pedestrian 4 looks up on lighting category Char 3 Looks up on organisation Required by Software 95 Required by Auckland Transport Not Required Compulsory Not Required Not Required Not Required Compulsory Auckland Transport Carriageway Table Field Name collect_date travel_direction Auckland Transport Database Operations Manual Field Description The date the person or organisation collected this data The permitted direction of travel for the road section Data Collection Guidance Notes The default entry is both therefore you need to change this if the road section only permits travel in one direction Database Management Comments The audit fields do keep a record of the logon date The allowable lookups may need to be reviewed for AT roads as the travel direction will most likely always be increasing i e the displacement of the road section increases as you drive down it It may be appropriate to use a heading such as eastbound only etc Therefore the look ups may need to include Northbound Southbound Eastbound and Westbound only Allowable Values char 1 B Both D Decreasing only Increasing only B Default Value 96 Required by Auckland Transport u Compulsory
157. se Management Comments Values Ensure that the scooter use data provided correlates to the area that the footpath is located in Defined as 1 Low 2 Low medium 3 Medium 4 Medium high 5 High U Unknown Looks up on table footpath_use This does not need to be collected in the field This data is automatically generated by the RAMM database once the data is collected Calculated by the database This date should not change if the footpath is simply RESURFACED However if the footpath is RECONSTRUCTED then the footpath will need to be deleted from the database and a new record added 122 Required by Auckland Transport To be confirmed Not t Peon required Compulsory when Optional certain conditions are met System Optional A Optional Compulsory Auckland Transport Required by Software Auckland Transport Database Operations Manual 123 Required by Auckland Transport Calculated by System System 8 the database Generated Generated Typically the surface_date is the same as the constructed date unless surface_date is the If the footpath has been resurfaced only the footpath has been resurfaced date that the gt then the surface_date will need to be surface_date since it was constructed Resurfacing Date Optional Compulsory footpath was last AE changed subject to the same surface being surfaced of footpaths is usually limited to placed on the footpath aspha
158. signed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data RAMM Roadnames Data Collection Guide Notes and FAQ s The following guide notes are to be used as a reference when carrying out activities that affect the RAMM Roadnames updates The guide notes cover the necessary information to collect RAMM Roadnames data in a consistent and accurate manner for all the mandatory fields that are required Roadnames road start end name convention and abbreviations All roads must have a consistent naming convention To reduce clutter all future road name additions must have abbreviated road and start end names e g if a road name is Ascot Road then it should be written as ASCOT RD not ASCOT ROAD Where road names are to have north and south added for clarity but these are not part of the actual name then the latter part shall be placed in brackets e g ASCOT RD NORTH This rule applies to all other suffixes that may need to be added to Roadnames such as ASCOT RD WESTBOUND but excludes Roundabouts Walkway High Low Same Level Access Loop Service Lane Walkway and Hammerhead suffixes Table 4 8 below describes abbreviations to be used in the Road Names Table and also in the start and end name fields of the Carriageway Table Auckland Transport Auckland Transport Database Operations Manual 72 Table 4 8 Road Name Abbreviations for RAMM IENEI Abbreviati
159. sition E J B K L M R U Ww P S decimal 12 4 gt 99 9999 and 9999999 9 Required by Software 116 Required by Auckland Transport Not tional Optiona required Not t optiona required Not tional ppriona required Compulsory Compulsory Auckland Transport Footpath Table Field Name northing_end gps_by gps_method_id Auckland Transport Database Operations Manual Field Description easting is the GPS reading in northings and eastings at the START of the footpath northing is the GPS reading in northings and eastings at the END of the footpath easting is the GPS reading in northings and eastings at the END of the footpath gps_date is the date that the start and end data was collected gps_by is the organisation that collected the data gps_method_id is the ID of the method that was used to collect the data and indicates both the type of equipment used and the accuracy of that equipment Data Collection Guidance Notes Database Management Comments Allowable VEINES decimal 12 4 gt 99 9999 and 9999999 10 decimal 12 4 gt 99 9999 and 9999999 11 decimal 12 4 gt 99 9999 and 9999999 12 Looks up on organisation 1 Generic GPS device 5 m 2 User clicked on map 10m 3 Update from RAMM Map 10m 4 Unknown no accuracy 5 Taken from asset no Required by Software 117 Required by Auckl
160. sory Required Allowable Values by Software Char 3 looks up on organisation Char 3 looks up on organisation Integer 4 Urban A ADT gt 10 000 Urban B ADT 5 10 000 Urban C ADT 1 5 000 Urban D ADT 200 1 000 Urban E ADT lt 200 Rural B ADT gt 5 000 Rural C ADT 1 5 000 Rural D ADT 200 1 000 Rural E ADT 20 200 Rural F ADT lt 50 Optional Compulsory Compulsory System Generated True or False Default Estimate Char 1 C Count D Default E Estimate System Generated Auckland Transport Carriageway Table Field Name loading_pc _heavy loading_esa_hea vy loading_date traffic_adt_est estimate_date traffic_adt_count count_date traff_manage_ level Auckland Transport Database Operations Manual Field Description Percentage of heavy vehicles from latest loading count RAMM calculated Equivalent Standard Axles Date of the latest loading record for this road section The latest ADT traffic estimate for this road section The date the latest estimate was done The ADT for the latest traffic count on the road section The date of the latest traffic count for the road section The traffic management level that applies to this road section Data Collection Guidance Notes From traffic count surveys System calculated System generated System generated System generated System generated System generated
161. sory Compulsory Compulsory Database Management Comments Required Allowable Values by Software Maintenance activity data is provided by the contractor on a monthly basis This is either transferred via RAMM Contractor or RAMM Manager input function Maintenance fault data is provided by the contractor on a monthly basis This is either transferred via RAMM Contractor or RAMM Manager input function Looks up on mc_fault Cost amount data is provided by the contractor on a monthly Note that the RCI values CCI adjusted maintenance cost amount need to be kept up to date to ensure that these values are accurate basis for the work that is being carried out This is Optional either transferred via RAMM Contractor or RAMM Manager input function System t Opiiona Generated Auckland Transport Auckland Transport Database Operations Manual 143 Required by Auckland Transport Quantity data is provided by the contractor ona ee monthly basis for each of quantity is the Each activity must have a the work carried out This quantity maintenance cost sou i 0 00 to 999999999999 Compulsory Compulsory transaction quantity corresponding qty is either transferred via RAMM Contractor or RAMM Manager input function Adjusted quantity is the ak Siete soni eta The quantity is altered if the client adj_quantity cottransaction wishes all measurements to be the Optional Not required i sa
162. sra_avg cway_use_ category Auckland Transport Database Operations Manual Field Description Minimum latest roughness value in NAASRA counts km Maximum latest roughness value in NAASRA counts km Average latest roughness value in NAASRA counts km This is a classification assigned to the road Data Collection Guidance Notes System generated System generated System generated section that defines the type and nature of the traffic flow distribution during the week No data collection requirements Database Management Comments This is a system calculated value This is a system calculated value This is a system calculated value This field was populated for the national traffic database survey undertaken in the mid 1990s to assign typical traffic patterns and loadings to the whole database It doesn t appear to have been maintained and is unlikely to be with the default set to unknown 92 Required by Auckland Transport Required Allowable Values by Software Default U smallint 3 gt 10 and lt 999 System Generated System Generated smallint 3 gt 10 and lt 1000 System Generated System Generated smallint 3 gt 10 and lt 1001 System Generated System Generated char 2 1A Urban Arterial A2 Urban Commercial 13 Urban Industrial 4 Urban Collector 4B Urban Other 5 Urban Rural Fringe 6 Rural Strategic 7A
163. ssigning it a younger date in relation to the GAP65 one day younger will suffice 1 Lee eee TIT ILI I PST Subgrade Figure 4 7 9 1 Example of a multi layered pavement layer Note use of layer dates to ensure the correct sequencing of the layers in RAMM Worked example 1 AWPT with stabilisation from route position RP 0 to RP1000 You have ripped up and removed the existing surface adding 100mm of new pavement material GAP40 and stabilised to a depth of 200mm using cement as a stabilisation agent at 2 There is no existing pavement layer data in RAMM Once you have completed the changes using RAMM Pavement Builder your Pavement Layer Table previously blank will now look like Start End m Date Removed Est ee Depth Recon Stab Stabilised m Date Known structed Agent 0 1000 17 2 2005 K COMPOSITE 200 Y 2 Cement 0 1000 15 2 2005 17 2 2005 K GAP40 100 N 0 1000 1 1 1980 17 2 2005 E UNK 100 N Notes The unknown layer dated 1 1 1980 will need to be the first layer added during the pavement builder process The filter for removed date is null will need to be cleared in order to see the removed layers Pavement Builder will tag the historic surfacings that runs concurrently with the AWPT as removed Auckland Transport Worked example 2 LHS seal widening from RP300 to RP600 Auckland Transport Database Operations Manual 68 You are seal widening from
164. sstcsstesessinesessicssiessdesstesstvsstesstessts 83 5 1 Carriageway Data DICHON ALY sisssiissscasscivensssccssasecersnaseneaaasversasaccanaaauseevsieeascacsauseseanencnnaeaayes 83 5 2 Carriageway Surfacing Data Dictionary ccssssccccccessssesssneeeeeecesssessnnseeeeeees sesssnnaaeeeeees 102 5 3 Footpath Data Dictionary sscscscctecstsssndieasssncsensssbsssnsashsssndsshsssndssbsssndssbsssvesensnebecenssenctenstes 114 5 4 Loading Data Dictionary eee ee eae 131 5 5 Maintenance Cost Data Dictionary ccccccccsseeccceeeeececseesceecseeeceeaaueseesseueseesaeeseessaaages 141 5 6 Pavement Layer Data Dictionary 0 0 0 cece eceeeecccecaaeeeeeeeeeeeeeaaaaueeeeeeeeeeaaaaaaeeeeeeeeeeaaaaaees 148 5 7 Roadnames Data Dictionary ccccccccsssssseeeeccceeecaaeeeeeeceeeessaeasseeeeeeeeesaaeseseeeeeeeesaaaagass 156 BiG maie Bat DICHOMANY sstec cece sven cectan scott Cok cvesekt cue vos cues aed T 160 6 DATA COLLECTION FORMS issiccscscscccscscececeiscccscaissssectessscacsassssscsesessssssnabsscssnassacss cesssasssessssssnenesssanesesans 1 Auckland Transport Auckland Transport Database Operations Manual 1 OVERVIEW The merging of seven individual asset registers into one reinforced the need for an overall Auckland Transport Database Operations Manual ATDOM Analysis of the individual sets as outlined in the previous RAMM Status Report clearly reinforced the industry need for a local authority equivalent of the State Hig
165. sure the batch id table is filled in correctly The batch name must follow the format YYYY MM Contract This relies on accurate Contract setup in RAMM Contractor looks up on mc_batch_header The data must be in the correct dd mm yyyy format i e 15 11 2011 e g 2011 12 1990 91 2030 31 Maintenance fault data is provided by the contractor on a monthly basis This is either transferred via RAMM Contractor or RAMM Manager input function Looks up on mc_cost_group 141 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory Required by Software Compulsory Compulsory Compulsory Compulsory Compulsory Compulsory Auckland Transport Maintenance Cost Table Field Name activity cost_amount_rci Auckland Transport Database Operations Manual 142 Field Description activity is the maintenance activity carried out within each specific cost group fault is the maintenance fault code which describes the fault that requires intervention by maintenance cost_amount is the cost of the maintenance activity cost_amount _rci is the Data Collection Guidance Notes Each schedule item must properly replicate an activity Each schedule item must properly replicate a fault Avoid use of UNKNOWN Each schedule item action must properly replicate a cost amount Required by Auckland Transport Looks up on mc_activity Compulsory Compulsory Compul
166. t Comments The abbreviations to be used are L Local Authority Council roads C Car Parks R Parks and Reserves W Walkway or cycleway P Private Road S State Highway This date is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column This date is automatically updated if you are changing data directly in RAMM for Windows If you are using the RAMM Manager Import facility you need to add the date to this column in dd mm yyyy format added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column Allowable Values Looks up on road_type Required by Software Compulsory System Generated System Generated System Generated System Generated 159 Required by Auckland Transport Compulsory System Generated System Generated System Generated System Generated Auckland Transport 5 8 Traffic Table Field Name carrway_start_m Auckland Transport Database Operations Manual Traffic Data Dictionary Field Description road_id is the RAMM ro
167. t material Data Collection Guidance Notes This information should be gained from laboratory test results the material at the subgrade level that the pavement is built on This is only applicable to new roads This data can be gained from the construction records and is measured in mm This data can be gained from the construction records This data can be gained from the construction records Database Management Comments The value will depend upon the type of material used Every pavement material has a lower and upper level value for thickness Thickness does not need to be provided for subgrade layers This field can be left blank for subgrade layer records Record the name of the quarry not the organisation or company name that supplied the material Allowable VEINES C CBR U UCS C Default Material Types e g CLAY Looks up on pave_subgrade 0 to 99999 Looks up on the pave_material Looks up on the pave_source Required by Software Compulsory Compulsory when certain conditions are met Compulsory when certain conditions are met Compulsory when certain conditions are met Optional 152 Required by Auckland Transport Compulsory Compulsory when certain conditions are met Compulsory when certain conditions are met Compulsory when certain conditions are met Compulsory Auckland Transport Pavement Layer Table Field Name re
168. t runs through carriageway section at the intersection of Road A and Road B FAQ s Q Where is the footpath start position for roads that are not at 90 degrees to one another A Endeavour to start the footpath record for these types of intersection half way around the corner If all data is collected in this fashion then the risk of overlapping footpath records and inaccurate length reporting is reduced Footpath Start and End Positions Around Roundabouts Auckland Transport Auckland Transport Database Operations Manual x Extra length Footpath A1 LHS Start Position and End Position for J Footpaths footpaths between two roads Extra length Footpath A2 RHS 41 Guidance notes As Roundabouts are treated as separate intersections footpaths need to start and end where the carriageway section ends and starts for the road running through the roundabout Road A Footpath length beyond the end and start positions of the carriageway section can be added as a length adjustment Do not add any footpath records to roundabout carriageway sections Put the additional length of footpaths on the main road Road A running through the roundabout Auckland Transport Auckland Transport Database Operations Manual A om AY v E RP 326m 42 Guidance notes The diagram shows a J Footpath Joins another road connecting Road A with Road B This footpath is collected from
169. tages are calculated Ensure raw download data classifies according to the NZTA 2011 classification system based on which percentages are calculated Database Management Comments If urban_rural and carriageway hierarchy type in carriageway table are correct this should not be required to be checked Check totals of individual categories add up to 100 Check totals of individual categories add up to 100 Check totals of individual categories add up to 100 Check totals of individual categories add up to 100 Allowable Values RO Rural Other RS Rural Strategic UA Urban Arterial UO Urban Other Required by Software Not required Required for Count C Required for Count C Required for Count C Required for Count C 134 Required by Auckland Transport Not required Required for Count C Required for Count C Required for Count C Required for Count C Auckland Transport Loading Table Field Name Auckland Transport Database Operations Manual Field Description This field describes percentage of traffic that are heavy commercial vehicles type 2 This field describes percentage of traffic that are buses This field describes the equivalent standard axles ESA per medium commercial vehicles This field describes the equivalent standard axles ESA per heavy commercial vehicles type 1 Data Collection Guidance Notes
170. te lt a 4 i 7 le me Footpath Start Position and End Position Around Multiple Tee Intersections 39 Guidance notes Road A only has a footpath on the RHS This footpath starts half way around the intersection 45 degrees for a right angle intersection of Footpath B1 RHS and Footpath A RHS As there is no footpath on the LHS of Road A Footpath B2 RHS starts as shown in the diagram FAQ s Q Do vehicle crossings count as a footpath A Yes as the vehicle crossings are serving as a footpath You do not need to stop and start footpath assets at vehicle crossings Q Is the data for footpaths on one way or multi lane streets collected in the same fashion as two way streets A Yes irrespective of the number of lanes or the directional nature of the road the data is collected in the same fashion Q If have a vehicle crossing with no footpath either side does the vehicle crossing then count as a footpath A No as the vehicle crossings primary purpose is as a crossing and not a footpath Auckland Transport Auckland Transport Database Operations Manual 40 Guidance notes For right angle intersections the footpath record for the side road starts at 45 degrees around the corner of the intersection There is no overlapping in the collection of footpath lengths for footpaths that transition from main roads into minor roads There is no break in the contiguous footpath B1 RHS records tha
171. the Road A with a start position of RP 326 on the RHS of Road A The footpath ends on the RHS of Road B at RP 97 The length is the measured distance between the start and end position FAQ s Q Should the record for a J footpath start on the major road or the minor road A It doesn t matter there needs to be a record for the start position of the J footpath on both roads so neither road has priority Auckland Transport Auckland Transport Database Operations Manual 43 Length Adjustment for a Footpath in a Cul de sac oan Guidance notes Where a footpath follows around a cul de sac head as shown in the photo the actual length around the outside may be different to the road centre line length Where this is the case the additional measured length of the footpath is added under length adjustment field and the length adjustment reason of CUL DE SAC is used The end point for the both the LH and RH footpath is shown by the dashed line aA er 3 ARERR n IER a i o FAQ s Q As shown in the photo it appears that the footpath ends past the end of the road which is the end of the seal in the cul de sac shown by the arrow head Do need to make the end of the footpath greater than the length of the road A No use the same displacement for the end of road as the footpath Auckland Transport Auckland Transport Database Operations Manual 44 Footpath Side Guida
172. the consultant and or contractor who is auditing the data prior to or after transferring the data into the RAMM Maintenance Cost Table What Fields are Collected and Why The Maintenance Cost Data Dictionary outlines the data that must be collected and provided by suppliers carrying out activities that affect the Maintenance Cost Table These are the minimum data requirements that will ensure that the maintenance cost data contained in RAMM can be used for its intended purposes as discussed above What Resources are Required to Collect Maintenance Cost Data To collect maintenance data you will need the following equipment and reference material ATDOM which will assist you in identifying what specific data is required Auckland Transport 4 6 7 4 6 8 Auckland Transport Database Operations Manual 61 Current carriageway information including Road ID s Road names start and end locations and descriptions for each road This will assist you in locating yourself correctly on the network A calibrated vehicle tripmeter with completed calibration form accurate to 1m per 1000m 0 1 A calibrated measuring wheel with completed calibration form accurate to 0 1m per 100m 0 1 Pocket RAMM or similar device approved by Auckland Transport if this is your preferred method of data capture RAMM data collection forms or equivalent How is the Database Updated The Maintenance Cost Data Dicti
173. tigated further if required Allowable VEINES 0 500 0 Default Y Yes N No Yes Default Looks up pave_source Required by Software Compulsory Compulsory Compulsory Compulsory when certain conditions are met Compulsory 108 Required by Auckland Transport Compulsory Compulsory Compulsory Compulsory when certain conditions are met Compulsory Auckland Transport Surfacing Table Field NEG cutter_type Auckland Transport Database Operations Manual Field Description surf_binder is the binder type used in the surfacing both asphalts and chipseals flux is the amount of flux in pph used in the binder cutter is the amount of cutter in pph used in the binder cutter_type is the type of cutter used in the binder adhesion is the amount of adhesion in pph used in the binder surf_adhesion is the type of adhesion used in the binder Data Collection Guidance Notes Use sealing records or seal designs to obtain this information usually included in the as builts Use sealing records or seal designs to obtain this information usually included in spray dockets or seal designs Use sealing records or seal designs to obtain this information usually included in spray dockets or seal designs Use sealing records or seal designs to obtain this information usually included in spray dockets or seal designs Use sealing records or seal designs to obtain thi
174. timate outcome of accurate consistent and up to date data RAMM Carriageway Data Collection Guide Notes and FAQ s The following guide notes are to be used as a reference when carrying out activities that affect the RAMM Carriageway updates The guide notes cover all the necessary information to collect RAMM Carriageway data in a consistent and accurate manner for all the mandatory fields that are required Survey Direction Existing conventions need to be considered regarding survey direction Auckland Transport may require roads surveyed in a specific direction However when validating or setting up a new database roads should be surveyed from the major traffic end to the minor traffic end as follows Arterial road to collector road Collector road to local road Local road to the end of the road or to the cul de sac end Exceptions to this are one way roads where traffic flow dictates the survey direction Minimum and Maximum Carriageway Lengths As described above changes in width number of lanes urban rural pavement type traffic volumes and administrational areas require a new carriageway section However to avoid the proliferation of short carriageway sections such as changes to no of lanes around signalised intersections or short bridges the following guidelines apply Urban area minimum carriageway length 30m maximum carriageway length 1500m Rural area minimum carriageway length 50m maximum car
175. tment lengths to be adjusted Annual resurfacing this activity may require existing treatment lengths to be adjusted Carriageway and surfacing reviews these reviews may require existing treatment lengths to be adjusted Who Provides the Data The supplier carrying out the physical changes to the asset is typically responsible for the provision of RAMM updates However treatment lengths are based on the physical properties of a road such as the surfacing age and type pavement strength and traffic volumes all of which can be determined from other data that is provided such as RAMM surfacing records Therefore treatment length data is not actually collected it is more interpolated by a trained and certified database manager What Fields are Collected and Why As stated above no specific data is collected in the field however it is important to note that surfacing and pavement layer start and end displacements must be collected accurately in order for a trained and certified database manager to be able to establish or update treatment lengths How is the Database Updated The database can be updated using two methods Automated generation of treatment lengths based on the carriageway surfacing and carriageways Manual addition updating and deleting of treatment length records in RAMM for Windows preferred Note that treatment lengths cannot span changes in carriageway pavement type For example if a conti
176. to RAMM Footpath maintenance renewals when existing footpaths are resurfaced over significant lengths as part of footpath renewal and maintenance projects the current footpath data in RAMM for the affected footpaths needs to be updated Street scaping these projects significantly affect current footpath data in RAMM and as a result require RAMM data updates Auckland Transport 4 3 4 4 3 5 4 3 6 Auckland Transport Database Operations Manual 36 Who Provides the Data The supplier carrying out the physical changes to the asset is typically responsible for the provision of RAMM updates Therefore in terms of the activities that affect the footpath assets listed above the following suppliers are responsible New subdivision construction the project consultant for the subdivision through the subdivision as built process Footpath maintenance renewals the project consultant and or contractor delivering the maintenance renewal project through requirements of the as built process Street scaping the project consultant and or contractor delivering the street scaping project through the requirements of the as built process for which the work was procured i e maintenance contract or capital contract What Fields are Collected and Why The Footpath Data Dictionary appended outlines the data that must be collected and provided by suppliers carrying out activities that affect the Footpath Table There
177. ubt check Auckland Transport Road Corridor Operations The assigned hierarchy is generally consistent with that defined in the District Plan The number of traffic lanes recorded impacts on other statistics such as vehicle kilometres travelled vkt so ensure it is recorded to reflect the number of traffic lanes only The default for data entry is 2 Lane widths can vary between remarks after resurfacing Ensuring this is done consistently results in accuracy for reported network length and doesn t double count as defined in the original RAMM User Manual yellow ringbinder It is the end_m start_m any length_adjust_m Allowable Values U Urban R Rural These will have to be rationalised as currently the field is populated with the legacy councils hierarchy lanes gt 1 and lanes lt 9 Default 2 0 1 up to 99 1 integer 5 Required by Software Compulsory Compulsory Compulsory 86 Required by Auckland Transport Compulsory Compulsory Compulsory Not Required Compulsory Auckland Transport Carriageway Table Field Name Auckland Transport Database Operations Manual Field Description Data Collection Guidance Notes Use this column to populate the difference in length and provide an explanation for the reason under len_adjust_rsn Database Management Comments Typically this relates to the difference in length from the kerb l
178. uction Who Provides the Data Generally this information will be provided by Council through their processes New subdivision roads will be advised with location and extent maps and required road name s Road name changes will be advised through the regulatory process including delegation Auckland Transport 4 8 5 4 8 6 4 8 7 Auckland Transport Database Operations Manual 70 and revocation of state highways and change of ownership of other roads Changes to the road network resulting from capital maintenance projects will be advised through the as built data process What Fields are Collected and Why The Roadnames Data Dictionary appended outlines the data that must be populated with all of this information able to be entered into the database from the office It will be necessary to obtain location and extent maps for all required changes What Resources are Required to Collect Roadnames Data To collect and manage Roadnames data you will need the following reference materials ATDOM which will assist you in identifying what specific data is required A map showing the extent and location of the road to be added removed A copy of the resolution from the appropriate Council committee approving the changes endorsed or supplied by the Auckland Transport asset management team A mapping tool that can assist in confirming suburb town and postal code if this information is not supplied Quickmap Counc
179. uctures lights signs bicycle hoops etc For example an off road cycleway that starts from Smith Road RP127 on the right hand side and ends at Brown Road would be named SMITH BROWN CYWAY RP 127 RHS All cycleways are recorded in the footpath table regardless of surface material For all cycleways hierarchy is recorded as Cycleway Auckland Transport 4 9 Traffic 4 9 1 4 9 2 4 9 3 4 9 4 Auckland Transport Database Operations Manual 75 Why is this Table Important The RAMM Traffic Table contains traffic volume count information on some carriageway sections of some roads and traffic volume estimates on all carriageway sections of all roads Specifically the RAMM Traffic Table includes Traffic volumes noted average daily traffic ADT for carriageway sections relating to both physical counts and estimates Dates relating to when the last traffic count was updated added into the database Traffic volume history at a particular location Notes in relation to 85th percentile speeds What is the Traffic Table Used For The RAMM Traffic Table is Auckland Transport s primary repository for all traffic count and traffic estimate data Traffic Volumes are used to update the pavement use group in the Carriageway Table and are an important parameter in pavement design economic evaluations temporary traffic management requirements and for higher level asset management tools such as forward wor
180. uired conditions are met This date is automatically assigned if you are adding data via RAMM for Windows If you are using System the RAMM Manager Import Generated Database Management Comments Allowable Values Not all pavement layers will be provided with a plan number Free form 20 Characters long This data is only applicable to newly designed pavements This data is only applicable to newly designed pavements Leave blank Enter only applicable comments System Generated facility you need to add the date to this column in dd mm yyyy format Auckland Transport Pavement Wl E Field Name added_by Auckland Transport Database Operations Manual Field Description added_by is the RAMM username of the organisation that entered the data chgd_on is the date that the data was chgd in the database chgd_by is the RAMM username of the organisation that changed the data in RAMM Data Collection Guidance Notes This field is not required for data collection This field is not required for data collection This field is not required for data collection Database Management Comments added_by is automatically assigned if you are adding data via RAMM for Windows If you are using the RAMM Manager Import facility you need to add your RAMM username to this column This date is automatically updated if you are changing data directly in RAMM for Windows If you are using th
181. umn by column description of the Traffic Table including what data is required how it is collected entered and managed and what are the allowable values Collectively these documents are designed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data Auckland Transport Auckland Transport Database Operations Manual 78 4 10 Treatment Length Maintenance 4 10 1 4 10 2 What is a Treatment Length A treatment length is a section of road that is subject to the same traffic loadings exhibits the same condition the same structural properties usually and the same surfacing type and age usually along its length It is also a section of road that is going to be treated simultaneously along its full length sometime into the future Typical examples of treatment lengths include the following Cul de sac turning heads usually AC e Bridge decks can be any surfacing type e Intersections including roundabouts can be any surfacing type Cobbled areas such as raised pavement tables A homogenous length of reseal with similar condition along its length You do not need to maintain treatment lengths for unsealed roads Note that treatment lengths must not span changes in pavement type located in the Carriageway Table Why is this Table Important and What is it Used For The RAMM Treatment Length Table is an important table as it contains all th
182. unction of 2 i e 2 coat seal How short should a resurfacing treatment be before you shouldn t add it to RAMM Do not add reseal lengths that are shorter than 50m UNLESS they are valid surfacing lengths A reseal this length can be considered a patch and thus shouldn t be entered unless it is an expensive treatment say AC OGPA etc or the road section itself is lt 50m ramp roundabout etc When is AC no longer thin asphaltic surfacing Single treatment AC layers greater than 80mm are considered structural layers and need to be incorporated in the pavement layer table and the carriageway pavement type changed from T to S thin surfaced flexible to structural AC The wearing course that sits above the structural AC needs to be entered into the surfacing table Ideally the maximum thickness of thin asphaltic surfacing is 40mm however surfaces between 40 80mm are not structural as such these would have to go in the surfacing table Auckland Transport 4 3 Auckland Transport Database Operations Manual 35 Footpath 4 3 1 4 3 2 4 3 3 Why is This Table Important The footpath table contains asset related information on all footpath and shared pathway assets including footpaths that run parallel to the road start at but end away from the road join roads and start and end away from roads Specifically the RAMM footpath table includes Location information such as the road the footpath
183. unt is available Data Collection Guidance Notes Use the RAMM carriageway table list to obtain this information If you do not have this information provide the full roadname as a minimum Use the RAMM carriageway table list to obtain this information If you do not have this information provide the location of the count as a minimum Any new physical counts or estimates resulting from subdivision data collection would need to be identified with a latest tag Database Management Comments Ensure that the road_id provided on the RAMM update sheet correlates with the road name shown on the carriageway list Ensure that the carriageway_start_m provided on the RAMM update sheet correlates with the carriageway section under the roadname shown on the carriageway list If data is loaded through RAMM Manager then carrway_start_m is automatically assigned Ensure that the values used comply with the allowable value list If not populated default to L Latest Database processes which are run by RSL should check the latest status for counts 131 Required Required by by Auckland Software Transport Compulsory Compulsory Compulsory Compulsory Compulsory Allowable VEINES Looks up on table roadnames Compulsory Looks up on table carriageway 0 99999 LorN Default Latest N not latest Auckland Transport KE AEG Field Name Auckland Transport Database Operations Manual Field
184. vement layer in metres relative to the location on the road that the pavement layer start position is located on DELICE axed OEEO EAS Notes For data collection for new layers layer_id is not required For data collection for existing layers which are being reconstructed the current layer_id is required Use the RAMM carriageway table list to obtain this information If you do not have this information provide the full roadname as a minimum Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect start_m Database Management Comments For importing large quantities of data through RAMM Manager Import facility set c_surface_id 0 Ensure that the road_id provided on the RAMM update sheet correlates with the road name shown on the carriageway list When adding pavement layer data it is considered best practice to review the adjacent layers Underlying layers may need to be adjusted due to earlier measuring errors and to ensure that the pavement layer records align with treatment lengths 148 Required Required by by Auckland Software Transport Allowable Values Compulsory Compulsory Looks up table roadnames Compulsory Compulsory 0 99999 Compulsory Compulsory Auckland Transport Pavement Wl E Field Name end_name layer_subgrade Auckland Transport Database Operations Manual Field Description end_mis the end location of the pa
185. vement layer in metres relative to the location on the road that the pavement layer end position is located on start_name is the description to be used for the start location of the pavement layer end_name is the description to be used for the end location of the pavement layer Flag to indicate if the record relates to a pavement Layer or a Subgrade Layer Data Collection Guidance Notes Use either a calibrated measuring wheel or a calibrated vehicle tripmeter to collect end_m Not required Not required Determine whether you are dealing with the pavement or subgrade Typically work on new subdivisions will contain both where rehabs of existing roads will just be pavement layers Database Management Comments Refer to start_m Typically this field is START OF followed by the name of the job Typically this field is simply END OF followed by the job name Allowable VEINES 1 99999 Varchar 35 Varchar 35 L Layer S Subgrade Default 149 Required Required by by ANTEO Software Transport Compulsory Compulsory Not Required Not Required Compulsory Compulsory Auckland Transport Pavement Layer Table Field Name layer_date removed_date Auckland Transport Database Operations Manual Field Description layer_date is the date that the pavement layer was built removed_date is the date that the pavement layer was removed Offset is the distance
186. vice 5 m 2 User clicked on map 10m 3 Update from RAMM Map 10m 4 Unknown no accuracy 5 Taken from asset no accuracy 6 Default no accuracy varchar 20 Default Value User varchar 20 Default Value User 99 Required by Auckland Transport System t Optiona Generated Optional gt System Optiona Generated System System Generated Auckland Transport Required by Software System Generated Carriageway Table Field Name rnm_edit_by vested_date as_tip_note added_by Auckland Transport Database Operations Manual Field Description The logon of the person who made the last network manager changes The date the road section was vested to Council General comments for information not contained above General tip for the assessor addedc_on is the date that the data was added to the database added_by is the RAMM username of the organisation that entered the data Data Collection Guidance Notes No data collection requirements No data collection requirements Record comments for things that are out of the ordinary and could make it easier for people in the future No data collection requirements This field is not required for data collection This field is not required for data collection Required Allowable Values by Software Database Management Comments varchar 20 Default Value User This info
187. widening rehabilitations and other resurfacing project where the number of records is small and the existing surfacing data requires some manipulation Updating existing Carriageway Surfacings records as a result of Carriageway Surfacings resurfacing and reconstruction projects can be complicated The preferred way to undertake this work is in RAMM for Windows viewing the Carriageway Surfacings data for each affected record in grid view then updating in detail view When the Carriageway Surfacings records are updated always view the data again in grid view to ensure there are no overlaps or gaps in the Carriageway Surfacings data How Can This Database Operations Manual Help You Accompanying this Table Overview are the following sections e RAMM Carriageway Surfacings Data Collection Guide Notes and FAQ s Section 4 2 9 includes diagrams and illustrations around standard Carriageway Surfacings data collection conventions to ensure the data is collected consistently in the field Some typical FAQ s are also provided e Carriageway Surfacings Data Dictionary appended provides a column by column description of the Carriageway Surfacings Table including what data is required how it is collected entered and managed and what are the allowable values for each field Collectively these sections are designed to assist both data collectors and database managers achieve the ultimate outcome of accurate consistent and up to date data
188. width p Y P Y width of the carriageway Offset seals require careful manipulation when loading into RAMM as they will greatly affect A the surface structure table if surf_offset is the distance measured to th nearest offset only needs to be collected if entered incorrectly Consider the surfacing is NOT full width or for only adding offset seals if they 0 to 60 0 1m from the LHS of the CE sealed carriageway tothe non full width surfaces that are not are a significant width gt 2 5m Compulsory 6 A Y flush with the LHS edge of sealed over a significant length gt 100m O Default LHS of the surfacing being i collected carriageway otherwise these surfacings should be entered into the i Required ae ae Data Collection Guidance Database Management Allowable poe Table Field Field Description by Notes Comments Values NEMIS Software Y Default value maintenance cost table as maintenance cost Never enter surfacings with a negative offset Compulsory Compulsory when certain conditions are met Ensure the design life reflects the likely estimated life of the surfacing given AADT HCV traffic stresses etc If a surfacing design life should be provided with spans a major change in traffic the surfacing design available from volume then consider adding the Not the design consultant or the surfacings as two separate required surfacing contractor records with separate design lives Design life only
189. y Optional Compulsory 97 Required by Auckland Transport Compulsory when certain conditions are met System Generated Compulsory Compulsory when certain conditions are met Compulsory Auckland Transport Carriageway Table Field Name easting easting_end Auckland Transport Database Operations Manual Data Collection Guidance Field Descripti ield Description Nar The risk of the asset failing or overall risk for the road section No data collection requirements Date the risk value was No data collection requirements last updated q Easting value at the start of the road section Northing value at the start of the road section Easting value at the end of the road section Northing value at the end of the road section The date when the GPS data was collected Database Management Comments The overall risk for the road section of a risk or multiple risks occurring as set up in the assessment module The value of this field needs to be considered when populated with defaults Generally populate with default value U The date will come through form the assessment module if this is where the assessment was done Allowable Values Char 1 1 Very Low 2 Low 3 Medium 4 High 5 Extreme U Unknown U Default value decimal 12 4 gt 99 9999 and 9999999 9 decimal 12 4 gt 99 9999 and 9999999 10 decimal 12 4 gt 99 999
190. y traffic Generally the traffic count data provided in the database will be used to determine the pavement use For new sub divisional roads a rate of 1 vehicle movement per meter of total road length is used as a basis to estimate number of vehicles per day The numbers of marked traffic lanes are counted This may vary from road to road Unmarked roads less than 4m wide are considered one lane The NZTA definition for urban is any road section that has a posted speed limit of 70 km hr or less i e10 20 30 40 50 60 70km hr Rural road sections have a posted speed limit of gt 70 km hr i e 80 90 100km hr This information is entered from ward sub area maps provided by Auckland Transport This is determined from road hierarchy maps provided by Auckland Transport Typically they are from the District Plan Auckland Transport Database Operations Manual 13 Additional Notes B C and U are obvious You may need access to as built drawings to differentiate between T and S for carriageways surfaced with AC Review the count and estimate data for surrounding carriageway sections to assist in calculating a reasonable estimate of AADT which then can be used to assign a pavement use band to the carriageway section For divided median sections northbound southbound the number of lanes in each direction are used Auckland Transport Auckland Transport Database Operations Manual 14 Roadname Divided

Auckland Transport

Contents

Download Pdf Manuals

Related Search

Related Contents