16
Auckland Transport Database Operation Manual (ATDOM) Presented By: Ranjith De Silva(AT) and Royce Greaves (Opus)

Auckland Transport Database Operations Manual

Embed Size (px)

DESCRIPTION

RIMS Forum - 20 March 2013 Ranjith de Silva (Auckland Transport, and Royce Greaves - Opus

Citation preview

Page 1: Auckland Transport Database Operations Manual

Auckland Transport Database Operation Manual(ATDOM)

Presented By:

Ranjith De Silva(AT) and Royce Greaves (Opus)

Page 2: Auckland Transport Database Operations Manual

2

Auckland Council established by combining seven LGOs: 1st Nov’2010

• Rodney District Council• North Shore City Council• Auckland City Council• Manukau City Council• Waitakere City Council• Papakura District Council• Franklin City Council• (Auckland Regional Council)

AUCKLAND TRANSPORT: BACKGROUND

Page 3: Auckland Transport Database Operations Manual

3

Page 4: Auckland Transport Database Operations Manual

4

• RAMM system was historically primary road asset inventory for all these council owned and maintained assets

• Seven RAMM databases were merged to form single AT database

• RAMM 2008, migrate to RAMM 2011 in Mar’2013

Auckland Transport RAMM Database

Page 5: Auckland Transport Database Operations Manual

5

Why? • to maintain consistency cross the AKL region for data

collection, entry and management

How? • provides policies/ procedures for data integrity/

consistency overtime, independent of supplier.• procedures for inventory data collection, validation

and day to day collection (maint. and construction)• specifies fields and tables to be populated

AT Database Operation Manual (ATDOM) Version 1 - March 2013

Page 6: Auckland Transport Database Operations Manual

6

• Carriageway (Asset)• Carriageway Surfacing (Asset)• Footpath (Asset) • Pavement Structure (Asset)• Forward Work Programme (Asset Maintenance)• Maintenance Cost (Asset Maintenance)

ATDOM – Phase 1: addresses 10 key tables

Page 7: Auckland Transport Database Operations Manual

7

• Road Names (Information)• Treatment Length (Information)

• Traffic (Asset Demand)• Loading (Asset Demand)

continued>>>>

Page 8: Auckland Transport Database Operations Manual

8

• What? • What is collected?

• Why?• Why is it collected

• How?• How is it collected

Three main areas addressed:

Page 9: Auckland Transport Database Operations Manual

9

• Based on a data dictionary• Similar to Appendix 3 Asset Register of SHDOM• Defines compulsory and optional fields• Designed to ensures consistency in asset register

What is collected?

Page 10: Auckland Transport Database Operations Manual

10

• Gives context of the need to collect data• Assists with “buy in” of collectors• Outlines responsibilities

Why is it collected?

Page 11: Auckland Transport Database Operations Manual

11

• Step by step instructions on how to collect each field in each table

• Complete with diagrams, conventions, etc• Will improve consistency, completeness and quality• Needs to be supported by training and accreditation

How is it collected?

Page 12: Auckland Transport Database Operations Manual

12

• Includes LRMS section

How is it collected? (cont’d)

Page 13: Auckland Transport Database Operations Manual

13

• Other tables to be included in Phase 2• Web based document to make searching easy• U[grade to RAMM 2011• Training and certification as per NZTA

Where to from here?

Page 14: Auckland Transport Database Operations Manual

14

• OPUS assisted to develop ATDOM Version 1• BECA reviewed first draft• NZTA - Michaela McMinn for the their assistance in

using some material from NZTA.

Acknowledgements

Page 15: Auckland Transport Database Operations Manual

15

More Information …….. Ranjith de [email protected]

Page 16: Auckland Transport Database Operations Manual

Thank you.