Spatially Enabling an Asset Management Database

Transcription

1 Spatially Enabling an Asset Management Database John Woollett, GIS Manager (Operations) Tube Lines Ralph Diment Intergraph UK Helen Neaves Intergraph UK Bruce Aquila Intergraph

2 Introduction Background Information Business Objectives Data Requirements Verification and Construction Problems GIS Programme Outline Data Exploitation Benefits of GIS Lessons Learned

3 The London Underground The oldest and one of the largest mass transit railways in the world.

4 Who is Tube Lines? The company selected by the UK Government to regenerate and modernize the following London Underground (LU) Lines: Jubilee, Northern and, Piccadilly (JNP).

5 The JNP Network 207 miles of track 251 trains 100 stations 227 escalators 71 lifts 2,395 buildings and structures 1.75 M illion Passengers each W eekday Approximately 2,500 employees

6 Public Private Partnership (PPP) - Service Contract Performance Contract between Tube Lines and London Underground. Tube Lines is contracted to improve the assets and the service. Pain/gain based on five measurement criteria: Capability - Journey time minutes, Availability - Lost customer hours, Service Points - Number of system faults, Ambience - Mystery Shopper Surveys, Stations Delivery - Delivery of projects against set dates.

7 PPP (Service) Contract Contract duration is 30 years. Reviewed every 7.5 years by Statutory Arbiter. The initiative requires moving from reactionary maintenance to a preventative-whole life approach. The contract prompted a review of the existing systems. Review led to the replacement of these systems with a unified enterprise system.

8 Distribution of Investment for First 7.5 years Project Group 7 ½ Year Budget Line Upgrades Projects Track Stations Lifts, Escalators & Structures Rolling Stock Communications and Data Transfer New Works Total * 720 M 390 M 350 M 290 M 200 M 149 M 180 M 2,450 M Line Upgrades Projects Permanent Way Stations Lifts, Escalators & Structures Rolling Stock Communications and Data Transfer New Works * Including unallocated contingency $4,572,790,317

9 Business Objective - Asset Register A complete register of all assets including: Each section of track, Train components, All the signals and structures on the three lines and, Assets within the 100 maintained stations. ***This provides Tube Lines managers a clear picture of the assets they hold.***

10 Business Objective - Asset Monitoring Better monitoring of each assets condition. ***A more informed approach to maintenance and renewals.*** A more proactive approach to managing asset performance and reliability. *** Accomplish this through analysis of trends in faults and maintenance.***

11 Data Requirements - Need to capture track complexity in a Database Track diagrams don t always display track complexities. Representing each piece of rail was not practical and compromises had to be made. Detailed survey drawings were often not available.

12 Data Requirements - Storing of track linear assets details in the Database Database/Network design rationale: Station to Station defines a unique asset/network segment. Each asset/network segment has detailed characteristics with an associated linear measure. Among characteristics managed are: Ballast type Age of rail Sleeper type. 0m 100m 200m Rail type LH Sleeper type Ballast type bullhead concrete granite flat bottom wooden limestone Characteristics are held for each rail (left and right hand) and conductor (electric) rails.

13 Data Requirements - LCS Code/Key Definition Basis of the LRS is to have a unique code that allows any position on the track to be coded. The code is from a legacy system used across all of London Underground. The LRS needs to allocate a code for each length of track. Legacy coding based on a unique number for each station and separate numbers for the area in between stations. The distance measure starts at zero in each area.

14 Data Requirements - LCS Code/Key Definition Code consists of: N124 = unique area code N = northern line EB = eastbound track LO = local track 101 = 101 metres along track in direction from start of an area

15 Data Requirements - Storing of track linear assets details in the Database Discrete assets such as signals and lubricators are held in another table. LCS location and Signal Number Distance from start of LCS area Maximo entry for a Signal GIS view of this Signal The signal is plotted on GIS map using the LRS location from the asset record. Selecting the signal in GIS brings up a view of the Oracle record.

16 Data Verification and Construction - LRS Code To verify the legacy codes, existing track diagrams were annotated with the track and point (switch) codes. These are sent out to be verified by the local managers against marker plates that are fixed on to the track.

17 Data Verification and Construction - Building the calibrated LRS The Track Diagram showing allocated codes Background map Crown Copyright. All rights reserved. London Underground Ltd 2005 LRS of track centreline with point&crossing (switch) areas allocated in GIS

18 Data Verification and Construction - GIS LCS Model Creation (Track linear assets) Detail - all tracks and points given LCS coding. Overview - all Tube Lines tracks, centre lines drawn out to grid full size. All Points & crossings (switches) represented as discrete area assets in the track model and in Maximo. Location Coding System (LCS) coded into the model. The best available track alignment data was used for codes and direction. Model produced by drawing over existing Ordnance Survey maps in open areas. In tunnels surveys and old record drawings used.

19 Track Survey CAD files to update the LRS Model CAD survey plot drawn full size to common grid GIS LRS model CAD survey overlaid on GIS LRS model

20 Problems Many areas not surveyed to a common grid (tunnel areas). Some alignment data was known to be outdated. Model will be updated as new surveys and as made drawings from track replacements are generated. Track codes not in a consistent format: N062-N-SBLO, N062/NNBLO, N062 N NBLO. Track codes had to have 1:1 match with codes in the Maximo Oracle database: Discrepancies appeared when connecting GIS model to the asset data thus helping to cleanse the data.

21 GIS Programme Outline Current Data Track Centre Line Track Linear Assets Track Discrete Assets Signals Track Project Locations Short Term (6-12 months) Earthworks Projects Track Drainage System Tunnels Asset Data Aerial photographs & contours Survey Control Overlays: Background Mapping Property boundary Tunnel Outline Earthworks Civil Structures Geology (Long Section data) Borehole Locations Future (Beyond 12 months) Track Recording Vehicle Ground Penetrating Radar (Ballast depth, foundations, obstructions) Surveys Environmental Key: Maximo other database CAD, Raster

22 Relationship between GIS/GeoMedia and Maximo GIS shows assets & work orders etc.. geographically Geometry Maximo shows details of assets & issuing work orders, etc. Access database(s), with asset data (temporary) Asset data Work orders Oracle database, geometry held in spatial cartridge, asset and work order data

23 Data Exploitation Analysis of Work Orders (Desktop) Detail Area Work orders are displayed in their geographical locations for a particular time period.

25 Data Exploitation Asset Data Records Asset data from Maximo is displayed via a join relationship with spatial features in the GIS. ORACLE GIS Crown Copyright. All rights reserved. London Underground Ltd 2005

27 Data Exploitation Live View Single source of truth represents the current/best knowledge of an asset and it s condition.

28 Data Exploitation Track Patrol Routes in Maximo Detail description and LRS references reside in Oracle. These are issued as work orders by Maximo at the designated frequency.

29 Data Exploitation - Geographical Display of Track Patrol Routes Patrolman can see on a map the extent of the track to be inspected. GIS can verify all areas are patrolled. Crown Copyright. All rights reserved. London Underground Ltd 2005 Overview of Route Detail View

30 Future Web Enablement 1 Display Selection Choose what to show by selecting one or more option below. Assets Work Orders Projects Overlays Custom Views Find Chainage Default Map The default map shown on the Home Page gives a representation of the entire Tube Lines network. It shows a number of default features such as track centre line and stations. Clear All Update Map

31 Benefits of GIS More accurate inventory of Tube Lines Assets. Poor asset condition easily identifiable (spatially/linearly). Fault and wear trends are analyzed geographically. Relationship between performance of assets is understood better (i.e. track subsidence related to blocked drainage). Assets now plotted by the GIS using location component.

32 Benefits of GIS Track Patrol areas plotted geographically allowing more effective planning. Clash detection of possession bookings: Areas to be booked are viewed geographically. This provides confidence the area needed is properly covered. This helps to reduce over-booking of areas. Potential clashes can be identified (i.e. breaking into a track drain by mistake). More effective planning of engineering works: Visualizing the assets in an area allows work packages to be scheduled to correct all the faults in the area.

33 Lesson Learned GIS has great utility for data cleansing: Location verification, Identifying data gaps and inconsistencies. ***Location notations that are not clear in the database are very clear in the context of a map.*** Day to day users must 'take ownership' of the system/data (Must update the data after work is completed). Marking out the LRS on the railway is a problem: Marker plates in wrong position or just missing, GPS helps in the open, but tunnels are a problem.

34 Lesson Learned Discipline of using the LRS must be accepted by users (Free form text entries of locations unacceptable). LRS is a foundation that allows data from various business streams to be simultaneously analyzed.

35 Q uestions and Thank Y ou!!