1. Data Interfacing
HTC INFRASTRUCTURE MANAGEMENT LTD

2. dTIMS Input Data File Most fundamental file
describes the attributes of each element in dTIMS
stored under the name of dt2699.dbf
There are two problems. One is that data are available, but are in different formats. Other is that the data are not available in the RAMM database either they are not collected by the RAMM system, or even they were required to be collected under RAMM system they are not available in RAMM database due to various reasons

3. dTIMS Data file vs. dt2699.dbf
Data prepared using DATA INTERFACING PROGRAMME
dT2699.dbf
One of the example of the data available in different formats are the condition data available in the RAMM database. As we know RAMM manual rating is done once annually or once in two years in all the roads in NZ. Hence condition data are available. But they are collected in quite different formats from those used by HDM system. For example HDM requires ALL CRACKING and WIDE CRACKING. WIDE CRACKING as such is not collected separately by RAMM. And also the cracking data in RAMM is based on length of the wheelpath where as HDM requires cracking data in % of carriageway area. Similarly Rutting data in RAMM is collected based on wheelpath length in m of the road with rutting more than 30 mm. However HDM need data in terms of mean rut depth and standard deviation of the rut depth

4. Data Field Categories Base Data Fields
Default fields available in dTIMS inventory file, can not be deleted or change the format
Minimum required by dTIMS
dTIMS ‘Hard coded’ equations use these field
Some fields are not used in our setup I.e. CUM_ESAL, AADT, AXLEQUIP, TRAV_WAY, LRSPLIT, YR_LSTWRK

5. Data Field Categories (…continued)
Performance Data Fields (Performance Index)
dTIMS keeps track of changes in this field
used for attributes whose value you want to vary over analysis period
should contain at least one Performance data field
Composite Index
combines other perfomance index values together
isn’t included in dT2699.dbf file

6. Data Field Categories (…continued)
Other Data Fields
For data fields used to describe the elements which are useful to create Filters and Expression
Special Data Fields
dTIMS treats these data field specially, when present
use to implement special features like ‘strip maps’ etc.

7. Modifying structure of the dTIMS data file
Structure of the inventory file can be modified inside dTIMS in the Setup mode only.

8. Modifying data of the dTIMS data file
Import from external file
using the formats Excel5, dBASE III+, ASCII text
Input/edit directly in the Inventory file
add and remove records
import and export data
edit the values
filter the element

9. Data Sources RAMM database Look up tables Default values User Input
Primarily from Treatment Length Table
Look up tables
Mean Monthly Precipitation
Unit costs
Default values
User Input
Other sources e.g. Strength Programme

10. Data requirements Road Referencing data Traffic Characteristics
Pavement properties
Pavement History
Road condition
Unit cost data
Strength Data

11. Road Referencing Data

12. Road Referencing Data Master Road List
based on Treatment Length Section of RAMM database
Contains 5 fields
Road Name
Road ID
Tl section ID
Tl Start m
Tl End m

13. Traffic Characteristics

14. Traffic data Average Traffic data Differential Traffic Classification
based on est_traffic_count of RAMM TL table
Differential Traffic Classification
based on pc_car, pc_lcv, pc_mcv, pc_hcvi, pc_hcvii, pc_bus of RAMM TL table
Default value provided for missing value based on traffic volume
Traffic Growth
Default values available for
Average Annual growth of Light Vehicles - GROWTH_L
Average Annual growth of Heavy Vehicles - GROWTH_L

15. Pavement Characteristics

16. dTIMS Surface Types and Base Types
Surfacing Types
Code
Surface Treatment, original ST
Asphalt concrete, original AM
Reseal on Surface treatment RS
Reseal in asphalt concrete RA
Asphalt overlay OV
Base Types
Granular GB
Cemented SB

17. dTIMS Surface types and the Last Surface thickness
RAMM Surface
Materials
Material Description
RAMM Pavement
Type
COAT1
First coat seal
TSF
COAT2
Second coat seal
TWO
Two seal coat
SAC
PSEAL
Prime and seal
RSEAL
Reseal
VFILL
Void fill seal
LOCK
Locking coat seal
TEXT
Texturising seal
SLRY
Slurry seal AC
Asphaltic concrete
OGEM
Open graded emulsion mix FC
Friction course
dTIMS Surface
Types
Last Surface
thickness, mm
(HNEW) ST 5 12 RA 10 AM
Surface_depth OV

18. dTIMS base type If rehab_stab_depth > 0 basetype = “SB” otherwise
basetype = “GB”

19. Converting RAMM Condition Data to dTIMS

20. Study Conducted parallel HDM and RAMM condition rating studies
5 x 500 m rural sections in Rodney District
7 x m urban sections in Waitekere City
3 x urban sections for cracking data

21. All Cracking

22. ACA Area of All Cracking, in %
ACW Area of Wide Cracking, in %

23. Scabbing
Loss of surface material
Equivalent to ravelling in HDM

24. ARV Area of Ravelling, in %

25. Potholes and Patching Average pothole size 0.05 m^2
Average patch size m^2

26. APT Area of Pot Holes, in %
APH Area of Patching, in %

27. Rut Depth
RAMM records the length of wheelpaths with rut depths > 30 mm

28. Problems ...
Pavements which are badly rutted can be missed

29. Solution Analysed State Highway rut depth data
Developed relationship between RAMM rut depth and mean rut depth
Need to change how we collect rut depths to record the mean

30. RDM Mean Rut Depth, in mm Hsd_Rutting avg IF HSDRUTT data is available
IF HSDRUTT data is not available

31. RDS Standard Deviation of Rut Depth, in mm
IF HSDRUTT data is available
Hsd_Rutting std
IF HSDRUTT data is not available
0.21 x RDM

32. ASF Area of Flushing, %

33. ASH Wheelpath length of shoving, in %

34. IRI Roughness in International Roughness Index, in m/km
All filters in dTIMS expressed in NAASRA

35. Historical Data

36. Surfacing Age - AGE2 Base on Surfacing_date of RAMM TL table
User are recommended to estimate the AGE2 using local experience when data are missing
Default pavement age will be base on the surface_material of RAMM TL table
IF Surface material = “COAT1” OR “TWO1” THEN AGE2 = 1
ELSE AGE2 = 6

37. Pavement Age - AGE3 Base on Layer_date of RAMM TL table
User are recommended to estimate pavement age using local experience
Default pavement age will be base on the surface_material, No_of_seal_layers etc
IF Surface material = “COAT1” OR “TWO1” THEN AGE3 = 1
ELSEIF Surface material = “COAT2” OR “TWO2” THEN AGE3 = 6
ELSEIF No_seal_layers >0 THEN AGE3 = 10 x No_of _seal_layers
ELSE AGE3 = 15

38. Old surfacing layer Thickness - HOLD
No data available in the RAMM
Collect the data based on local experience
Default HOLD
HOLD = THICK - HNEW

39. Total surface thickness - THICK
YES
Pavement type = “SAC” NO
THICK = MAX(100, Surf_depth)
SurfType = “ST” AND
Surface Material = “COAT1”
OR “COAT2”
OR “TWO1”
YES
THICK = HNEW NO
THICK = MAX(25, (8 x No of Seal Layers)

40. Converting Data Other Data Strength Programme RAMM dT2699 Database
Interface
programme
dT2699
Database

41. Data Interface Programme

42. Steps in Data Interfacing Programme
Create a database
Import data
Edit data
Validate Road Section data
Edit RAMM Exception File
Edit Default values
Import Strength data
Build dTIMS Input File
Validate dTIMS Input File
Edit dTIMS exception file
Export dT2699.dbf file

43. Creating new database

44. Import RAMM Data Import Master Road List
Import pavement and condition data

45. Import RAMM Data

46. Edit RAMM Data (if required)
Edit Master Road List (not recommended)
Edit pavement and condition data

47. Edit RAMM pavement and condition data

48. Edit Default values Edit Master Road List (not recommended)
Edit pavement and condition data

49. Validate Road Section Data

50. Edit RAMM Exception Table
Data in RAMM Exception table can be browsed and edited
Editing must be done before running ‘Build dTIMS Input File

51. Edit RAMM Exception Table

52. Edit Default values (if required)
Following Default values can be edited
General incl. Calibration coefficient
Unit Cost
Conversion coefficient
AADT
Default Composition
Surface Texture
Pavement Type Conversion
Monthly Precipitation

53. Edit Default values