Visual Asset Management System (VAMS)

for Periodic Road Network Monitoring

2019-07-01

TECHNICAL PROPOSAL

7/1 1st Floor, 80 Feet Road, Indiranagar

Bangalore, Karnataka 560038
Ph: +91 80 25207500/01 e: info@infycons.com www.infycons.com
Table of Contents
1. Introduction ............................................................................................................................................................... 1

Background .............................................................................................................................................................. 1

VAMS Overview ...................................................................................................................................................... 1

Broad study areas of VAMS ............................................................................................................................ 1

Key objectives of VAMS ................................................................................................................................... 1

Usage of RAMS data ........................................................................................................................................ 1

Road Categories in VAMS perspective .............................................................................................................. 2

Applicability of VAMS study based on Road & CD Category ..................................................................... 2

2. INTERFACE OVERVIEW ........................................................................................................................................ 3

2.1 GIS INTERFACE ................................................................................................................................................. 3

2.2 IMAGE VIEW – STREET LEVEL ....................................................................................................................... 3

2.3 SEARCH, FILTERING AND REPORTING ........................................................................................................ 3

2.4 CITIZEN CENTRIC LIVE FEED .......................................................................................................................... 4

3. OUTPUT DETAILS-OBJECT CATALOGUE ........................................................................................................... 5

3.1 DETAIL-NETWORK .................................................................................................................................... 5

3.2 ALIGNMENT PARAMETERS ............................................................................................................................ 6

3.2.1 HORIZONTAL ALIGNMENT:................................................................................................................... 6

3.2.2 VERTICAL ALIGNMENT ........................................................................................................................... 6

3.3 STRUCTURE OF THE OBJECT CATALOG (OC) .................................................................................... 6

3.4 AREA TYPE ......................................................................................................................................................... 7

3.4.1 LANE SURFACE (AREA) ........................................................................................................................... 7

3.4.2 PUBLIC PLACES (AREA) ........................................................................................................................... 7

3.4.3 SIDEWALK PLACES (AREA) .................................................................................................................... 8

3.4.4 MEDIAN/DIVIDING STRIP (AREA) ........................................................................................................ 8

3.4.5 PEDESTRIAN AREA (AREA) ..................................................................................................................... 8

3.4.6 BUS STOP (AREA) .................................................................................................................................... 9

3.4.7 PARKING -PARKING LANE AND PARKING BAY (AREA) ................................................................. 9

3.4.8 GREEN AREA (AREA) ............................................................................................................................... 9

3.4.9 CROSSING SECTIONS (AREA) ........................................................................................................... 10

 3.5 LINE TYPE ........................................................................................................................................................ 11

3.5.1 BRIDGE (LINE) ........................................................................................................................................ 11

3.5.2 ROAD DRAINAGE CHANNEL (LINE) .................................................................................................. 11

3.5.3 PROTECTION STRUCTURE (LINE) ....................................................................................................... 12

3.6 POINT OBJECTS ............................................................................................................................................ 12

3.6.1 CULVERTS ............................................................................................................................................... 12

3.6.2 TRAFFIC SIGNS ..................................................................................................................................... 13

3.6.2 ELECTRIC POLES/STREET LIGHTS ...................................................................................................... 14

3.6.3 CABLE BOX / CONROL BOX/TRANSFORMER............................................................................... 14

3.6.4 MANHOLE COVER ............................................................................................................................... 14

3.6.5 RAIN PIPE TUNNEL ................................................................................................................................ 15

3.6.6 WATER DISPENSER............................................................................................................................... 15

3.6.7 BOLLARD ................................................................................................................................................ 15

3.6.8 MONUMENT .......................................................................................................................................... 15

3.4.10 WAYSIDE BUILDINGS ....................................................................................................................... 16

3.4.10 ROAD LANE BARRIER/SPEED BREAKER (AREA) ............................................................................ 16

3.6.9 WAYSIDE CONSTRUCTION ............................................................................................................... 17

3.4.8 CABLE DUCT (AREA) ............................................................................................................................. 17

3.6.10 SENSITIVE LOCATIONS..................................................................................................................... 18

3.4.15 PLACE OF STAY (AREA) .................................................................................................................... 18

3.8 ATTRIBUTE – MATERIAL................................................................................................................................ 19

3.9 ATTRIBUTE – CONDITION ........................................................................................................................... 20

3.9.1 CONDITION RECORDING FOR ROAD LANE .................................................................................. 20

4. IMPLEMENTATION SCHEDULE ........................................................................................................................... 21

1. Introduction

Background
Road network is the key backbone for overall development of any region. State of Meghalaya has
9667 Km of road which includes National Highways, State Highways, Major District Roads, Other District
Roads, Village Roads & Urban Roads. Apart from these listed roads, there are various other private
roads which exists. Since multiple agencies are involved, comprehensive information on network level
development status, current condition and a complete Road link model is not available easily which
hinders the process of overall decision making, progress status and larger planning.

The development of a Web based Visual Asset Management System (VAMS) addresses all this concern.
Visual Asset Management System (VAMS) is a strategic and systematic process of developing,
maintaining, upgrading, and operating assets effectively. Information collected and made available
through this system will be useful for the agencies responsible for district level development, road
development and maintenance, investors, as well as citizens.

VAMS Overview

Broad study areas of VAMS

 Assets & Inventory
 Pavement surface condition
 Pavement sub-surface condition & status
 Bridge information & condition

Key objectives of VAMS

 GIS Map
 Condition
 Pavement Management

Usage of VAMS data

 Statistical analyses like
o Length of road network
o Area of asphalt
o Assets to manage
 Base level information for DPR Projects
 Detailed view of the current condition with reflects to:
o Driving comfort (view of the user)
 Structural deficits (view of the maintenance)

1
Road Categories in VAMS perspective
Roads can be broadly categorized based on their condition, functionality and the development program
planned.

A. Road in poor condition: Stretches of road which is currently in poor health and will require re-
construction of entire pavement, including re-alignment possibilities, widening etc. if necessary.
B. Road needs widening: Stretch of road which is unable to meet existing traffic flow efficiently
and requires widening. The activities will involve re-alignment.
C. Road maintenance: Stretch of road which requires minor & major maintenance in pavement of
structure but does not require any major re-construction or re-alignment
D. Road in good condition: Stretch of road which are in good condition and does not need any
intervention.

Applicability of VAMS study based on Road & CD Category

Study Description Poor Widening Maintenance Good
Condition condition
1. Road Network
A. Road link model x x x x
B. Horizontal alignment x x x
C. Layout parameters x x x
2. Asset maps
A. Area objects x x
B. Linear objects x x x x
C. Point objects x x x x
3. Pavement Condition
A. Surface distress such as- x x x
Cracks, ravelling, patch &
pothole
B. Pavement composition x x x
4. Bridge & CD structure condition x x x x
2. INTERFACE OVERVIEW
Interface will be accessible through browser from any Computer, mobile or tablet and have the following
interface and general functionalities.

2.1 GIS INTERFACE

A GIS map view will be displayed with online maps in background. Background map can be configured
to use Google Rest services, Open Street Map or Bing Map. Information pertaining to road and assets
with be overlaid on top and separate layer with option for visibility toggle, zoom to layer option. A
representative view is shown below

2.2 SEARCH, FILTERING AND REPORTING

Searching based on Road, District, village, concerned department etc. with option for combined criteria-
based search will be available. Attribute information can be used in combination to create custom
dashboard. There will be option to save the recent search trend for quick usage in future. Customizable
reporting will be provided in PDF format for direct exchange and print.

Slab

HPC

0 5 10 15 20 25

Poor Fair Good

3
2.3 IMAGE VIEW – STREET LEVEL
A Street level camera view will be displayed for any position in the road network. There will be option
to select historical imagery based on data availability which can act as ready reference on status,
progress and deterioration comparison and overall development status for road. The image view will
be dynamically linked with GIS layer to display location on GIS view. There will be option for play
through for quick overview of any road stretch.

2.4 CITIZEN CENTRIC LIVE FEED

An android App will be provided for all citizens to enable them to report issues related to pavement
condition, structural condition, accessibility problem etc. which is of immediate nature. These live feeds
will automatically be linked with appropriate road segment and priority list and reporting can be done.
Notification can be enabled on necessary action from the administration

4
3. OUTPUT DETAILS-OBJECT CATALOGUE
Based on the Georeferenced imagery, GIS map for assets would be created with attributes related to
these assets. The following section describes the output in detail.

3.1 DETAIL-NETWORK
The Detail-Network is an explicit and complete Road-network. It’s based on the existing node-edge-
models (point-line-model). In case, node-edge model does not exist, it will be created based on center
line as mapped in GIS and appropriate node edge model will be developed. It includes all information
of the road-network, various object-information and it is compatible to the regional reference system
(RBS). Every Network element defines a specific road-section in the detail-network with points of
connection and geometry. Additional to this there will be information saved about the element-type, &
position. The technical data, like the classification system of the road (e.g. road names, district) and
other classification systems (e.g. road classes, public easement, road types, road description), will be
assigned to the elements. The connection points get a reference to the complex nodes (points).

A full node link model will be created with the following parameters:

- Centreline in the middle of the road if the road has a divider – two centre line must be created
- Road network must be routable
- Must have the information
o From Node, to node
o Name of the Road
o Average daily traffic (ADT)
o Percentage of heavy traffic
o Number of lanes
o Road Type
o Responsible district
o Responsible agency

Technical data, which have an additional exact point or exact distance data assignment within the
network-element, get more technical description. A lot of applications need these descriptions.
Important descriptions are the number of lanes, lanes with traffic usage type, lane directions with
corresponding attributes. Only for the practicability of a routing function, prohibited or recommended
driving relationships as well as traffic restrictions with needed specifications on lanes, will be recorded
for this technical data.
For all objects following data structure will be present:

SHAPE TYPE Point/Polyline/Polygon

DESIGNATION Name of the object based on the object catalogue
GIS_ID Li_Datum_Nr /Fl_Datum_Nr /Pk_Datum_Nr

5
3.2 ALIGNMENT PARAMETERS
Based on the center line (Polyline) the horizontal and vertical alignment parameters need to be
extracted/calculated. The following parameters are needed:

3.2.1 HORIZONTAL ALIGNMENT:

- Radius
- Straight line
The complete alignment axis along should be extracted conforming to design guidelines and the
information should be compatible to be used directly This axis can be imported in popular design &
estimation software such as MX Road, Civi3D, AutoPlotter Road Estimator etc. The calculated axis must
fit with the centreline with a maximum distance of 5 m. The axis must be improved to minimize the number
of elements as much as possible.

3.2.2 VERTICAL ALIGNMENT

Full Gradient should be extracted which reflects the design guidelines. The calculated Gradient must fit
with the centreline with maximum distance of 100 m. The Gradient has to be improved to minimize the
number of elements as much as possible.

3.3 STRUCTURE OF THE OBJECT CATALOG (OC)

In the OC the following, relevant Attributes will be listed.
OBJECT DESCRIPTION Geometry
The object description will be recorded as full text and has Data Type as text.
Attribute Data Type Unit Range
Attribute name/ Text On measurable Selections/numerical
meaning Integer dimensions, like the length, values
Double the unit will be specified
Boolean

6
3.4 AREA TYPE

3.4.1 LANE SURFACE (AREA)

The lane surface is a traffic area which is only for vehicles. A lane surface will be recorded from the one
BT/curb stone/CC edge to the other BT/curb stone/CC edge on the other roadside. There are different
condition recordings for main roads and side roads.

For main roads with direction-lanes, single-polygons created

On main roads with direction-lanes, one polygon for every lane will be created. Direction-lanes which
are separated with double-markings (wide stroke) count also as direction-lanes. Main roads with one
lane in every direction will be record as one polygon independent from the kind of marking.

Attribute Data Type Unit Range

Area Double m² 0-…
Material Text Type of Material
Condition recording Varies – based on material

3.4.2 PUBLIC PLACES (AREA)

Public Places is a traffic area in urban regions or a flat, fixed or unfixed Area, which has a special
function (e. g. Traffic, markets, festivals and events). The Public place belongs to the public road region.

Attribute Data Type Unit Range

Area Double m² 0-…
Material Text Type of Material
Condition recording sidewalks Varies – based on material

7
3.4.3 SIDEWALK PLACES (AREA)
The Sidewalk is the part of the traffic area, which
is only designated for pedestrian. If there is a
sidewalk-classification in upper strip, walk lane
and lower stripe and so on, than different areas
with corresponding attributes will be created.
The border of recording the upper strip is the
border of surrounding property (wall, house
wall, fence, hedge and so on).

Attribute Data Type Unit Range

Area Double m² 0-…
Sidewalk structure Text 1= upper strip
2 = footway
3= lower strip
4= secondary structure dividing strip
5 = other
Material Text Type of Material
Condition recording Varies – based on material

3.4.4 MEDIAN/DIVIDING STRIP (AREA)

A median/dividing strip is a road area part which is located
between two lanes or on a lateral position to a lane. The
different dividing strips will be recorded when they are

bigger than 0.3 m otherwise, they will be

marked as divider (line object). Rotaries
traffic island is also recorded as dividing
street with position between two lanes

Attribute Data Type Unit Range

Area Double m² 0-…
Position Text 1 = between two lanes
2 = lateral lane
Material Text Type of Material
Condition recording Varies – based on material

3.4.5 PEDESTRIAN AREA (AREA)

A pedestrian area is a traffic area where pedestrians have priority over all other. Beginning and end
of a zone is marked with the traffic signs.

Attribute Data Type Unit Range

Area Double m² 0-…
Material Text Type of Material
Condition recording Varies – based on material

8
3.4.6 BUS STOP (AREA)
Area designated for public transport stoppage will be marked with the following attributes

Attribute Data Type Unit Range

Area Double m² 0-…
Material Text Type of Material
Condition recording Varies – based on material

3.4.7 PARKING -PARKING LANE AND PARKING BAY (AREA)

Parking lots will be recorded as parking if the section is designated, signposted or marked as such. If
there is no marking and no structural differentiation, then the area will belongs to the road lane. Parking
areas which are situated on the road lane (because the surface is the same) will be recorded as overlain
area (marked parking = overlain area). Condition values and material types will not be identified for
the overlain areas. All other parking areas which have a structural differentiation will be recorded as
separate areas.

Structural differentiator Perpendicular to the Road Parallel to road lane

Attribute Data Type Unit Range
Area Double m² 0-…
Type Text 1= parking with differentiation
2= marked parking
Material Text
Condition recording sidewalks

3.4.8 GREEN AREA (AREA)

Green areas are park-like or garden-like area in the public sector. Playgrounds and special green areas
like the botanical garden or zoological garden will not be recorded. Green areas beside a road are
also green areas. Green stripes which are located at sidewalk structures (upper strip, lower strip,
secondary structure dividing strip) will recorded as components of this area.

Attribute Data Type Unit Range

Area Double m² 0-…

9
3.4.9 CROSSING SECTIONS (AREA)
These are sections where especially pedestrian and bicycles can cross a road. Crossing sections are
crosswalks (zebra crossing), pedestrian and bicycle passages (markings at light-signal systems) and
crossing assistances (center lanes & center islands). All crossing section will be recorded as overlain
objects.

Passenger passage

Cross walk

Center Island

Attribute Identifier Data Type Unit Range

Area AR Double m² 0-…
Crossing Section UEBS Text 1 = crosswalk
2 = pedestrian passage (light-signal system)
3 = center island
4 = dividing strip
5 = sidewalk pre-stretch
6 = tram crossing section
7 = combination

10
3.5 LINE TYPE

3.5.1 BRIDGE (LINE)

A bridge is a construction so that one traffic way carries over another traffic way. This could be a river,
valley, another street or rails. The bridges should only separate on their values of bridge buildings. In
case of visible working seams or ramp changeover on a bridge, these will be borders of the bridge. If
this is not the case, then the beginning and the ending of the caps are marked. The object is recorded on
the center axis as an overlain line.

Attribute Data Type Unit Range

Length Double m 0 -…
Width Double m 0 -…
Footpath Double m 0 -…
Type Text 1 = RCC Bridge
2 = Bottom Girder Bridge
3 = Arch Bridge
4 = Cable Stayed Bridge
5 = Wooden Bridge
6 = Rubble Stone Masonry Bridge
7 =Others
Span Text Span arrangement
Major Bool As per IRC classification
Bridge usage Text 1 = pedestrian/ bicycles
2 = road lane
3 = traffic (road lane/ pedestrian/ bicycles)
4 = traffic incl. Tram/train
5 = traffic incl. train and subway
6 = other
Condition Based on visual classification (Good, Fair, Poor)
Remark Additional Information pertaining to bridge

3.5.2 ROAD DRAINAGE CHANNEL (LINE)

These are drainage channels to absorb and deduce the rainwater. Generally, all drainage channels in
the public space will be recorded. Drain attributes will also be recorded to indicate whether the channel
is lined, unlined, boxed, covered etc.

Attribute Data Type Unit Range

Length Double m 0-…
Drain Type Text 1=RCC Box Drain
2=Footpath +Covered drain
3=Trapezoidal lined drain
4=Rubble masonry drain
5=Saucer drain
6=Unlined drain
7=Others
Width Double m 0-…
Condition Visual condition (Good/Fair/Poor)

11
3.5.3 PROTECTION STRUCTURE (LINE)
Protection structures are constructed along road edges for either protection or
demarcation. Various kind of protection structures are in use in hilly terrain, some
of which are for passive safety and others are for slope protection. In plane
areas, a wall is used for boundary demarcation.

Attribute Data Type Unit Range

Length Double m 0-…
Type Text 1 = Guard wall
2 = Crash barrier
3 = Gabion wall
4= Breast wall
5= Wall
6 = Fence
7 = Pillar
8 = Retaining wall
9 = others
Side Text 1 = LHS
2 = RHS
Offset Double m 0-…
Condition Visual condition (Good/Fair/Poor)

3.6 POINT OBJECTS

3.6.1 CULVERTS
All cross-drainage structures will be recorded at center location.

Attribute Data Type Unit Range

Width Double m 0 -…
Length Double m 0 -…
Type Text 1 = HPC
2 = Slab
3 = Box
4 = Causeway
5 = Laid Pipe
6 =Others
Span Text Span arrangement
Condition Based on visual classification (Good, Fair, Poor)
Remark Additional Information pertaining to culvert

12
3.6.2 TRAFFIC SIGNS
For the recording of traffic signs count the specifications of the IRC will be followed Street name signs
and additional signs with text content will be recorded. The traffic signs will be recorded start from left
and after this from top to down (VKS_LNR). All traffic signs will have information about direction.

Attribute Data Type Unit Range

Traffic sign from IRC Catalogue (if exists, otherwise create new catalogue)
Current number of the Integer 1, …
traffic sign at the mast
Content of the sign Text content
Appliance for standing Text 0 = no data
1= lighting mast
2= traffic light mast
5 = lighting and traffic light mast
10 = cantilever arm
16 = others
19 = cement/concrete pillar
22 = house wall
23 = sign bridge
temporary Short Integer 0 = no
1 = yes
Location Text 1 = R (right)
2 = L (left)

Orientation Double 1 = 0° normally (parallel alignment)

2 = 315°/-45° (inclined alignment)
3 = 270°/-90° (vertical alignment)
Position Text 1 = beside road lane
2 = on island
3 = on the center lane
4 = above the road lane

13
3.6.2 ELECTRIC POLES/STREET LIGHTS
All Electric Poles will be recorded. The point will be recorded in the center of the mast foot.

Attribute Data Type Unit Range

Side Text 1=LHS
2=RHS
Offset Double m 0 -…
Mast types (from light signal systems) Text 1 = normal
2 = cantilever arm
3 = Extended arm

3.6.3 CABLE BOX / CONROL BOX/TRANSFORMER

Cable and control boxes standing mostly on
the sidewalk or Pole. The point must be
recorded in the center of the object

Attribute Data Type Unit Range

Quantity Text 1 = single
2 = double
3 = triple

3.6.4 MANHOLE COVER

In the most cases metal covers for service chambers from
underground supply lines. Mostly for drains. The point will be
recorded in the center of the object

14
3.6.5 RAIN PIPE TUNNEL
A rain pipe tunnel is a part of the road-dewatering. It absorbs raining
water from the ground level. The point will be recorded in the center of the
object.

3.6.6 WATER DISPENSER

A water dispenser is a drinking water spring in the public space.

3.6.7 BOLLARD
Bollards are vertical, with the ground
attached poles or equivalents with the
same function. Bollards which are not listed
under number 1 till 4 become “other” as
bollard type. Bollards will be recorded in
the public road space.

Attribute Data Type Unit Range

Bollard Type Text 1 = fixed
2 = reversible
3 = retractable
4 = fixed with chain
5 = other

3.6.8 MONUMENT
A monument is a big representation of a person or an event to remember on that. These include statues,
war memorials, memorials, and triumphal arches and so on. Maximum contour of a monument will be
identified.

15
3.4.10 WAYSIDE BUILDINGS
Public Buildings along the route will be recorded in this section. Public Building will have attribute for
type of roof, number of floors, usage and name attribute

Attribute Data Type Unit Range

Position Text 1=Left
2=Right
Type Text 1=Office
2=Post Office
3=Police Station
4=Police Check Post
5=Bank/ATM
6=School
7=College
8=Commercial
9=Hut
10=Hospital
11=Clinic
Description Text …

3.4.10 ROAD LANE BARRIER/SPEED BREAKER (AREA)

It is an artificial uprising of the road lane. It could consist of the same material like the road lane or
other material.

Attribute Identifier Data Type Unit Range

Area AR Double m² 0-…
Material MATERIAL Text

16
3.6.9 WAYSIDE CONSTRUCTION
Buildings like these have different functions and complete the
highway use in the public space. These include all Buildings with
function but not those with a habitation function. Example of such
building are toilet, police watch house, snack bar, kiosk, info
boxes, and pharmacy

Attribute Identifier Data Type Unit Range

Usage KLB Text 1 = kiosk / snack bar
2 = public toilet/rest room
3 = other

Advertising panel/ WER Boolean 1 = yes

information panel 0 = no

3.4.8 CABLE DUCT (AREA)

This is identified as coverage of a cable duct on the earth’s surface.

Single Double Triple

Attribute Identifier Data Type Unit Range
Area AR Double m² 0-…
Type TYP Text 1 = single
2 = double
3 = triple

17
3.6.10 SENSITIVE LOCATIONS
Buildings located along ROW which are used for the purpose of praying or gr is categorized by this
object.

Attribute Identifier Data Type Unit Range

Usage KLB Text 1 = Mandir
2 = Masjid
3 = Church
4 = Gurdwara
5 = Buddhist Gompa
6 = Graveyard
7 = others

3.4.15 PLACE OF STAY (AREA)

Buildings that have facility for boarding & lodging located along route is categorized by this object.

Attribute Data Type Unit Range

Area Double m² 0-…
Usage Text 1 = Only Food
2 = Only Boarding
3 = Both

Identifier Text Name of facility

18
3.8 ATTRIBUTE – MATERIAL
In the area objects, material field is recorded based on this definition. All the materials are not recorded
for conditions. The table shows the materials recorded for conditions

Condition Recording NO Condition Recording

1 = cement/concrete 13 = water bound road surfacing
2 = asphalt 14 = unsealed (sand, and so on)
3 = mosaic cobbles (ca 50/50 mm) 15 = green
4 = little stone cobbles (ca. 90/90mm) 17 = other material
5 = big stone cobbles
6 = cement/concrete cobbles
7 = sidewalk-board cement/concrete
8 = sidewalk-board natural stone
9 = granite board large format (old/new)
10 = cement/concrete board large format
11 = asphalt cover on cobbles
12 = asphalt cover on cement/concrete
16 = tightened mixed area

Cement/concrete cobbles Sidewalk board (Cement/concrete) Sidewalk board(natural stone)

Granite board (large format) Granite board (large format) Big stone cobbles

Little stone cobbles Mosaic cobbles Promenade attachment

19
3.9 ATTRIBUTE – CONDITION
In area objects, road lanes and sidewalk have condition recording which is based on following definition

3.9.1 CONDITION RECORDING FOR ROAD LANE

For the main roads the condition values will be recorded for each lane independent from the polygons
created for shape.
Attribute Identifier Data Type Unit Range
Edge EDGE Text
Material MATERIAL Text 1 = asphalt
2 = cement/concrete

EITHER: condition recording asphalt

Crack in the total RIS Double % 0 – 100
area
Inlaid EFLI Double % 0 – 100
Mends/Patches
Disposed AFLI Double % 0 – 100
Mends/Patches
Other surface OBS Double % 0 – 100
damages in the total
area
Potholes AUSBR Boolean 1=Yes 0 =No
Open seam, gap ONF Double m 0-…
OR: condition recording cement/concrete
Longitudinal and LQRP Double % 0 – 100
transverse cracks
Angle and edge EKSP Double % 0 – 100
damages
Bituminous cover BTEP Double % 0 – 100
fragment

20
4. IMPLEMENTATION SCHEDULE

• Reconnaissance at site. Involves planning of suitable Control station locations.

STAGE 1

• VAMS survey for all lanes.

STAGE 2

• Data processing as per section 3

STAGE 4

• Delivery & training

STAGE 5

5. RECOMMENDED FREQUENCY OF STUDY & TIME ESTIMATE

Task Recommended Time Process

Frequency

Data collection for VAMS Annual 40-200 Lane Automatic

Km/day/system

Date processing for Inventory & GIS Concurrent activity 1-4 Lane Km/day/person Semi
output

Date processing for pavement Concurrent activity 10-40 Lane Semi

condition & reporting for Km/day/person
cracks/potholes etc.

Setup of Inventory management Continuous update 6 months for Beta Periodic Manual
database and maintenance for update
3 years

21