Download presentation
Presentation is loading. Please wait.
1
Management System of Engineering Structures
NVF Bridge Conference 2015 Mika Stenmark, Finnish Transport Agency
2
Need for a new system The present Bridge management system has an out-dated technological platform In the year 2010 highways, railways and waterways were combined under one agency => the new system must manage different structures on all traffic networks The current data model is based on bridges Tunnels, piers, canal structures and waterway navigation marks has been adapted in the system partly ‘forcing’ them into bridge structure In autumn 2014 the implementation project finally started with the working title “TREX” The goal = 1. version in spring 2016
3
Focus areas in the development
Web and mobile use Information security (= contains data important for defense) Opening the data through interfaces and services Flexibility (= need to manage different structures) Expandability Integration with documents, pictures and other file data Integration with related systems (Service Oriented Architecture) GIS (coordinate-data, map-integration) BIM-model integration User-friendliness
4
Statistics of the traffic network - roads, railways and waterways
km highways of which 800 km motorways 5 900 km railway network of which 90 % on single track 78 000 km of highway 5,350 km 4 300km coastal fairways 14,900 4 000 km inland waterways 11/6/2018
5
Engineering structures, what are they?
The Transport Agency defines engineering structures as: structures that are designed and constructed using strength calculations structural damage caused by design or construction errors can cause: danger to humans or damage to the traffic system remarkable repair costs to the structure or its immediate environment
6
State owned engineering structures
Bridges ~
7
State owned engineering structures
Bridges ~ Tunnels ~ 90
8
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200
9
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks
10
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~
11
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~ Noise walls
12
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~ Noise walls Retaining walls
13
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~ Noise walls Retaining walls Rock cuttings
14
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~ Noise walls Retaining walls Rock cuttings Pile plates
15
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~ Noise walls Retaining walls Rock cuttings Pile plates Culverts
16
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~ Noise walls Retaining walls Rock cuttings Pile plates Culverts Railway station structures
17
State owned engineering structures
Bridges ~ Tunnels ~ 90 Piers and quays ~ 200 Locks, canal structures ~ 40 locks Navigation marks and aids on waterways (non floating) ~ Noise walls Retaining walls Rock cuttings Pile plates Culverts Railway station structures Stairways
18
How can we manage different structures?
Data model has to be generic and flexible User interface must be mainly shared for all structures Some structures require their own special data e.g. bridges, bridge type and bearing capacity information
19
Hierachical data model of engineering structures
Structure 1 (Bridge) Sub-structure Abutment 1 Pier 1 Foundation Column Cap beam Properties - Material - Dimensions - … Pier 2 Abutment 2 Super-structure Surface-structure Railings Environ-ment Structure 2 (Bridge) Main structure Structures Components / Structural parts
20
BIM-model integration
Design / Construction phase Combined / coordination model Uses native formats of design tools IFC LandXML Dwg … Preparing the model for maintenance phase IFC ”TREX” Normalised / validated to FTA-standards
21
Use of the BIM-models in TREX-database
TREX interface for the IFC-transfer model TREX data storage Database data ”Conventional” text-based data Basic data of structures Property data etc Geometry data 2D coordinate data (point, line, area) 3D data of strutrural parts as triangular mesh Document management IFC-transfer file as it is
22
Benfits of BIM-model integration
Easier, partly automated data flow from design and construction data Visualisation of the data in 3D Using 3D-models to pinpoint damages in inspections
23
Thank you! Mika Stenmark mika.stenmark@fta.fi www.fta.fi
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.