“Tah: 603) 87373320, Fax: (603) 8739 1904 ROAD ASSET MANAGEMENT SYSTEM APPLICATION AND USER MANUAL PART A: General Transport, esearchRoad Asset Management System Part A: General Acknowledgments This Manual, and the associated software collectively termed the Road Asset Management System, or RAMS, is the output of a Project funded by the Department of Public Works entitied ‘The development of a new Pavement Management System for Federal Roads in Malaysia’ which was carried out on behalf of the Roads Branch. The Project Team comprised the JKR Task Force listed below, and the Consultant team drawn from Kumpulan IKRAM Sdn Bhd, ARRB Transport Research Ltd (Australia), TRL Ltd (United Kingdom) and University of Birmingham (United Kingdom), and their contributions to the establishment of RAMS is gratefully acknowledged, This Manual was drafted by MrT Toole and Mr D Wightman, with additional editorial contributions from the JKR Task Force and Consultant Team. The PMS-4 software was adapted by Mr D Wightman and Mr J K Hasnut under the direction of Mr T Toole and Professor H R G Kerali. The HDM-4 Workspace was developed with contributions by various members of the Project Team. Copyright & Licence Arrangements The contents of this Manual are the property of the Department of Public Works, Malaysia and any reference to material contained herein should be duly acknowledged. Limited extracts from the text may be reproduced provided the source is acknowledged. For more extensive reproduction, please write to the address below. Director Roads Branch Department of Public Works Kuala Lumpur Malaysia Both HDM-4 and PMS-4 are both licensed software programmes, namely HDM-4 Whose ownership is vested in PIARC and PMS-4 which is owned by University of Birmingham —_ = In both cases specific copyright, license rules and warranty agreements apply to the use of each programme. Details of the relevant agreements are supplied with the respective software installation disks. These agreements shall apply to the software products supplied with this Manual, unless agreement is reached to the contrary and entered into by all interested parties. Version: 1.05 i Issue date: 22 October 2002Roads Asset Management System (RAMS) Final Project Report Acknowledgments This Report is the output of a Project funded by the Department of Public Works entitled “The development of a new Pavement Management System for Federal Roads in Malaysia’ which was carried out on behalf of the Roads Branch The Project Team comprised the JKR Task Force listed below, and the Consultant team drawn from Kumpulan IKRAM Sdn Bhd, ARRB Transport Research Ltd (Australia), TRL Ltd (United Kingdom) and University of Birmingham (United Kingdom), and their contributions to the establishment of RAMS is gratefully acknowledged The project would not have been possible without the support and encouragement of the Director General of JKR, Dato” Ir Haji Zaini bin Omar, and the Director of Roads Branch, Ir. Haji Mohamad Razali bin Othman, and this is gratefully acknowledged. ‘The members of the IKR Task Force who directed and supervised the project comprised :- Chairman: Ir, Mohamad Razali bin Othman, Director, Roads Branch. Project Manager: Ir. Dr. Safty Kamal Ahmad, Senior As Roads Branch. int Director, Maintenance Unit, Members: Ir Joseph Lim Chan San, Senior Superintendent Engineer, Maintenance Unit, Roads Branch. Ir Chin Wei Choong, S rnior Superintendent Engineer, Bridge Unit, Roads Branch. Dr, Azmi b. Hassan, Senior Assistant Director, Design Unit, Roads Branch. Ir Ng Kim Fook, Senior Assistant Director, Maintenance Unit, Roads Branch, Jamilah Mohd Marjan (Mrs), Senior Assistant Director, Road Safety Unit, Roads Branch, Ir Lai Khin Onn, Assistant Director, Maintenance Unit, Roads Branch. Ir Zulakmal Haji Suffian, Assistant Director, Maintenance Unit, Roads Branch, The Consultant Team comprised :- Project Director: Dato’ Ir, Chong Ket Pen, Kumpulan IKRAM Sdn Bhd Team Leader: Tyrone Toole, ARRB Transport Research Ld Team Members: Muhammad Zamri Hassan, Kumpulan IKRAM Sdn Bhd Mat Zin Hussain, Kumpulan IKRAM Sdn Bhd Raja Arman R M Arifin, Kumpulan IKRAM Sdn Bhd Geoff Jameson, ARRB Transport Research Ltd Dr Greg Morosiuk, TRL Ltd Professor Henry Kerali, University of Birmingham Jami Kabir Hasnut, University of Birmingham David Wightman, University of Birmingham Contributors: Paul Robinson, ARRB Transport Research Lidb Gavin MeL intock, ARRB Transport Research Ltd IKRAM/ ARRB TR/TRL/UoB 7 ‘October 2002Road Asset Management System PUBLIC WORKS DEPARTMENT ROADS BRANCH ROAD MAINTENANCE UNIT Part A: General ROAD ASSET MANAGEMENT SYSTEM APPLICATIONS AND USER MANUAL (Version: 1.05 - October 2002) PART A GENERAL 1. THE RAMS MANUAL 1.1. Background a 1.2 Purpose and Scope of the Manual 1.3 Development of the Manual 1.4 Structure of the Manual 1.5 Use and Updating of the Manual 1.6 References and Bibliography 2. ROLE AND STRUCTURE OF THE RAMS 2.1 Introduction 2.2 Overall Structure 2.3 Overall functionality 2.3.1 PMS-4, 2.3.2 HDM-4 2.4 System Outputs. 2.4.1 PMS-4... 2.4.2 HDM-4 2.5 Data and Models 2.5.1 PMS-4 2.5.2 HDM-4 2.6 System Operation and Management 2.6.1 Relation to Functional Roles 2.6.2. User access Version: 1.05 a PY PRYYPYYPRPYoS wea SeeNGSSSSSRSLETZGESREE Issue date: 22 October 2002Road Asset Management System Part A: General 1. THE RAMS MANUAL 4.4 Background The Department of Roads within the Malaysian Department of Public Works (JKR) has since the year 1997 commissioned comprehensive surveys of the Federal road network that employ state of the art mobile survey techniques to determine the road condition, geometry and other physical features. The survey data is an extremely valuable resource and has been collected at a significant cost to JKR. The data provides high quality baseline information on the condition of the Federal road assets. Similar surveys are now being conducted on a regular basis to enable trends in network performance to be adequately monitored as a means for determining long-term funding needs to support service levels to users, and to provide performance information on the highway network. The assembled data was first specified to conform with the input requirements for the HDW-II analysis engine that was incorporated within JKR’s Pavement Appraisal and Management Suite (PAMS), the purpose of which was to identify candidate links for maintenance, rehabilitation and improvement and to determine project alternatives for those lengths of road that warrant treatment. The system was developed in the late 1980's using the best technology available at the time. However, in comparison with modern road management systems and software technology, the PAMS became Gated and was subsequently replaced in 2002 by a new HDM-4 based Road Asset Management System, termed RAMS, in which HDM-4 acts as the investment planning tool, and a customised version of the commercial software package, PMS-4, forms the data base and data preparation tool. The HDM-4, Highway Development and Management Tools (HDM-4), which is the successor to the World Bank's Highway Design and Maintenance Standards Model (HDM Ill), was first launched during the PIARC World Road Congress held in Kuala Lumpur in October 1999. The HDM-4 meets many of the needs of senior road managers, engineers, planners and other professionals. Its development has been supported by various agencies including the Asian Development Bank (ADB), the World Bank, the UK Department for International Development (DFID), and others. Malaysia directly contributed to the developments by hosting the ADB funded Technical Relationships Study between 1994 and 1996, and has also made considerable investments in road research studies whose outputs have contributed to the development of HDM-4. ‘The new HDM-4 covers a wide range of subject areas, both from a technical and management perspective. From a technical viewpoint, the new model has a much wider scope and is capable of far greater application world-wide than HDM-III. Version: 1.05 14 Isgue date: 22 October 2002Road Asset Management System Part A: General Specific improvements include: a) Network level strategy and program analyses, in addition to project analysis; b) Concrete pavement models; ©) Effects of traffic congestion; d) Safety, energy and vehicle emissions; e) Improved and new models for estimating vehicle operating costs, road deterioration and road works effects. This improved capability should lead to increased use within the roads sub-sector, and in the wider transport sector. The HDM-4 comprises state-of-the-art Knowledge and Experience in highway management, and a suite of Models and Software Tools. Each part can be used support of road management activities, of as a component of an ‘overall management system ‘The HDM-4 is owned by the major sponsors and its development is managed through a PIARC Project Group, under the guidance of an Intemational Steering Committee. Malaysia actively contributes to such forums, and in turn is in the process of establishing its own National and Regional Working Groups to support its application and development. 1.2 Purpose and Scope of the Manual This Manual describes the general features, operation and use of the various components which make up the pavement management components of the Road Asset Management System (RAMS) which has been adopted by JKR Malaysia. The purpose and scope of the system is illustrated in Figure 1.1 below. Data PMs-4 HDM-4 Outputs &|- B- &- Import Data Analyse Policies | | | | | Figure 1.1 Purpose and Scope of RAMS Version: 1.05 1-2 Issue date: 22 October 2002Road Asset Management System Part A: General The Manual, and associated software tools, is for application to the management of the maintenance and rehabilitation of Federal road assets at a ‘network’ level. As such, its primary users are the senior JKR responsible for the identification of budget needs and future works programmes which are aimed at maintaining or improving the performance of the road network for road users. The system produces a variety of outputs in the form of reports on the condition of road assets, ‘indicative’ investment levels and works programmes for future years, and can be applied in the development of policies and standards. ‘Project’ level treatment design and procurement procedures will continue to be used to refine solutions, the deserving road sections having first been identified and prioritised through use of RAMS. External data suppliers will be interested in providing quality information for storage within the system, whilst the contractors who implement roadworks will also have an interest in the outputs of the system, since these will guide JKR in ordering works, and ensuring the objectives of the various works programmes are met. 4.3 Development of the Manual The Manual draws on the collective experience of the local and international ‘specialists engaged to produce the RAMS, and the experience gained by JKR in the earlier development and use of the PAMS, and in road works in general It specifically builds on the now well established 'HDM Technology’, comprising the Knowledge, Software and Models, developed through contributions by engineers, "economists and software systems developers over the past thirty years or so, and which embodies the principle of whole life costing of costs of road construction maintenance, vehicle operations and road safety. RAMS’ predecessor, PAMS, first employed such techniques in the early 1990's, building on the outcome of the Malaysian Axle Load Study in 1987. Although it was based on the HDIMHIII tool, PAMS included advanced features to investigate optimisation of a large selection of alternatives under budget constraint. It also ‘employed models to take account of traffic interaction, and congestion effects. The current system has essentially translated this capability onto a modern MS ‘Windows platform, with the HDM-4 model as its analytical tool The key steps in the development have included: 1. Migrating the existing PAMS ‘Engineering’ data to a new HDM-4 compatible “database; 2. Configuring and adapting HDM-4 for local use, including establishing typical values for a wide variety of parameters; 3. Calibrating the road deterioration and works effects (ROWE) models using the outputs of automated road monitoring surveys conducted in 1997, 2000 and 2001; 4. Assembling HDM-4 road networks, vehicle fleets and maintenance standards, and unit costs, and applying these in trial analysis on a sub-network, and producing and verifying outputs; 5. Customising the PMS-4 data base and data preparation tool, and subsequently populating it with ex-PAMS data; 6. Preparing operational guidance, and conducting training and dissemination activities. Version: 1.05 13 Issue date: 22 October 2002Road Asset Management System Part A: General The RDWE calibration activities were the most comprehensive undertaken so far in Malaysia, and also drew on the experience of local and regional studies conducted ‘since the 1980's. As explained later in this Manual, and in associated Technical Notes, these exist as a starting point for ‘network’ level application of the system, but. ‘can be improved upon as new data becomes available to extend the scope of the dataset and its representation of regional differences. ‘Separate Road User Effects studies were not undertaken, and resort was made of default relationships. Accident rates were also not investigated, but research on this subject has commenced in Malaysia and reference should be made to this when considering projects which will could possibly have a safety benefit or disbenefit. Thus there is a continuing need to improve the quality of this information to ensure the outcomes of the analysis reflect reality The applications studies focused on the maintenance and rehabilitation treatments common to Malaysia, and investigated ‘intervention levels’ using the economic criteria employed in HDM-4. These are believed to be reasonably soundly based, but will require refinement as more experience is gained in the use of the system ‘An area which requires further consideration is the provision of quality trafic data, in terms of speed-flow characteristics and axle loading. These have significant impacts on road transport economics, and therefore will sway the levels of justifiable investment and priorities. 4.4 Structure of the Manual ‘The Manual is structured in the following three Parts: Provides a general introduction to the operation and development RAMS, its Part A various components, functionality, outputs General and data input sources, and describes the various levels of User access which the system supports. _ This describes how to use the PMS-4 software for Malaysia, including installation, and the four main functions of data import, Using an Import Wizard, the Data Management module, the Report Module and the HDM-4 Export Wizard. It also includes details of the specification and sources of both PMS-4 and HDM- input data, including data supplied as defaults and in look-up tables used by the system Part B PMS-4 User Guide | Contains an overview of the HDM-4 highway | development and management tool, the | HDM-4 software environment or Workspace, | the configuration and adaptation of HDM-4 for Malaysia, descriptions of the HDM-4 Workspace for Malaysia, supplementary user guidance and a set of Malaysian case studies, A hard copy of the PIARC HDM-4 Software User Guide (Volume 3) is included for reference purposes. Part C HDM-4 Supplementary User Guide Version: 1.05 14 Issue date: 22 October 2002Road Asset Management System Part A: General 1.5 Use and Updating of the Manual The Manual will be subject to periodic updating through the issuing of amendments or replacement or supplementary material. As such is should be treated as a CONTROLLED DOCUMENT. Updating will be based on feedback from users, changes in policies, and as new information comes to light and warrants a change. Justification of changes will be required, as indeed was necessary in first providing the current documentation. For example, the accompanying series of Technical Notes document the basis for the selection of calibration factors for the road deterioration and works effects models employed by the system, and for the method employed to assign a structural strength value to in-service road pavements. The format of the Manual allows easy update, through the page numbering approach adopted. 1.6 References and Bibliography Highway Planning Unit (1987). Malaysian Axle Load Study. Final Report and Technical Notes. Highway Planning Unit, Malaysia Kerali, H R G (2000). Volume 1. Overview of HDM-4. The Highway Development and Management Series. The World Road Association (PIARC). Paris, France Jameson, G D (2002). Estimation of the Adjusted Structural Number. RAMS. Technical Note 1. Roads Branch, Department of Public Works, Malaysia, Jameson, G D and G Morosiuk (2002). Interim calibration of HDM-4 road deterioration and road works effects models. RAMS Technical Note 2. Roads Branch, Department of Public Works, Malaysia Jamilah Mohd Marjan, Safry Kamal Anmad and J B Odoki (2002). Modular approach to accident analysis. Paper No. 1. Proceedings of the 5" Malaysian Roads Conference, 7" — 9" October, 2002, Kuala Lumpur. JKR (Undated). PAMS User Manual Robinson, R, U Danielson and M S Snaith (1998). Road Maintenance Management, Concepts and Systems. MacMillan Press Ltd, Basingstoke, UK. TRL (1998). Guidelines on the design and operation of road management systems Overseas Road Note 15. Transport Research Laboratory, Crowthorne, United Kingdom Version: 1.05 45 Issue date: 22 October 2002Road Asset Management System Part A: General 2. ROLE AND STRUCTURE OF THE RAMS 2.1 Introduction This section provides an introduction to the RAMS including the customised version of PMS-4 which forms a key component of the RAMS, and its relation with HDM-4 and external data sources. The overall structure of the system recognises the role of PMS-4 in providing a seamless link with the Highway Development and Management tool, HDM-4, in producing management reports from an analysis of pavement condition data, traffic data, maintenance standards, unit costs and other data required for economic analysis. ‘Two major components of the system are recognised, namely the PMS-4 database and data preparation tool and the HDM-4 planning tool, each of which has different input requirements to meet its output requirements. The following description is structured to take account of the following aspects of the system, with further details provided in the RAMS manuals: i) Overall functionality by component ii) System outputs by component iii) System requirements and entry points, by component, in terms of data and models iv) Data input specifications, sources and formats 2.2 Overall Structure ‘The overall structure of RAMS is illustrated in Figure 2.1. Import Data Analyse Policies Manage Data aaa Strategios Generate Reports Programmes Export to HDM.4 Projects Figure 2.1 Structure of RAMS Version: 1.08 241 Issue date: 22 October 2002Road Asset Management System Part A: General The structure recognises the specific roles of the two main components of the software system The general flow of information in relation to PMS-4 is illustrate in Figure 2.2. Condition Surveys RAMS Database and HDM-4 data ‘Survey preparation tool Look Up Database Tosa Database | PMS-4 | L | 1 View : import Data | Data Export to HOM-4 mens {Map io] gy [ Select] gy | rue Aageaeon er) | nae Meee ae | 1 LWWerkstistoy] | | Produce — i | Reports Figure 2.2 Flow Chart of Data Flow and Key Processes related to PMS-4 2.3 Overall functionality 2.3.1 PMS-4 Within the system, PMS-4 provides the following functionality and outputs: i) _Itimports and stores survey data in a series of database tables; i) Validates the imported records to ensure compatibility with the internally held road ordinance tables, and traffic assignment and count stations tables; ili) Creates a variety of export files required by the HDM-4 applications taking account of - - User selection of road sections for individual or groups of States, or the entire network ~ Creation of homogenous treatment lengths using dynamic segmentation and aggregation, with manual ‘grouping’ of sections where desirable - assignment of default data for each homogenous section from look up tables - writes the HDM-4 road network file - writes ‘skeleton’ HDM-4 programme analysis files iv) Produces a variety of pre-defined reports directly from the PMS-4 database; v) Capable of producing a variety of ad-hoc reports from the PMS-4 ‘Master’ database using Standard database Query Language (SQL) procedures; Version: 1.05 2-2 Issue date: 22 October 2002Road Asset Management System Part A: General vi) Allows the system user (at a defined user access level) to access database tables and edit/update the look up tables held within the Master data base (MDB). 2.3.2 HDM-4 i) Accepts road network and ‘skeleton’ applications files exported from PMS-4; il) Stores user specified vehicle fleet, maintenance standards, default works costs, currencies and configuration data; iil) Produces multi year works programmes using the HDM-4 programme application; iv) Investigates optimum standards and budget levels using the strategic analysis application; v) Analyses project specific case studies using the HDM-4 project analysis application; vi) Allows the user to produce a variety of pre-defined reports in tabular and graphical format. 2.4 System Outputs 2.4.1 PMS-4 i) HDM-4 import files > HDM-4 road network import file > ‘Skeleton’ HDM-4 Programme Analysis file ii) Pre-defined reports — as Tables Traffic AADT (by Station) Pavement Condition (by Road) Pavement Drainage (by Road) Pavement Inventory (by Road) Pavement Structure (by Road) vvvvyv 2.4.2 HDM-4 ‘Standard reporting formats based on the 3 main applications, and described in the HDM-4 Software User Guide, Volume 3 (Wightman et al, 2000). A hard copy of the guide has been provided as Appendix C1 of RAMS Manual Part C. 2.5 Data and Models Data and models are required by each component to generate the required outputs. Data entry, either through user interfaces or file transfer, takes place in a preferred manner. For the vast majority of data, the primary data repository should be the PMS-4 database, whereas most models reside in the HDM-4 planning tool. The general structure is shown in Figure 3.3 below. In Figure 2.3, external data refers to information which is imported through file transfer, whereas internal data refers to data entered through a user interface within the particular component. For PMS-4, external data can be imported through a series of import wizards from data files provided in a pre-defined format. The two sets of external data identified for HDM-4 are imported from PMS-4. Version: 1.05 23 Issue date: 22 October 2002Road Asset Management System Part A: General External data Externaldata 7 lnventory ~ Road network (Programme level) = Pavement structure and = Default Works Codes | condtion Internal data | | Works history Vehicle feet | |- Traffic - Fully specified Works Standards & | | ternal data Costs | | - Look up tables, including ~ Configuration, including Traffic default date and ROWE flow, Speed flow and Climate calibration factors Models ~ Default Works Codes ~ RD/RUE Models | Models ~ Eoonomie models | SegmentatiovAgaregtion | |” SEE models Figure 2.3 General structure for data and models The main types of data, their sources and responsibilty for provision, are summarised as follows and illustrated in Figure 2.4: ‘System data, comprising all look up tables whose contents are managed by the ‘System Owner within PMS-4, or within the HDM-4 Workspace. Ordinance data, which is relatively fixed and comprises the lists of roads, states, traffic count stations, etc, and which are stored in tables are managed by the ‘System Owner within PMS-4 Survey data, comprising all data supplied by external data collection contractors or agencies, the scope of which includes the following > Condition data, which is dynamic in nature and recorded over fixed distance intervals, normally one-kilometre sections, and processed according to a Client defined specification. > Drainage data, which is dynamic in nature and recorded over fixed distance intervals, normally one-kilometre sections, and processed according to a Client defined specification Inventory data, which is also dynamic in nature but comprises both data recorded over fixed distance intervals and event data which records the presence of specific items at precise chainages. Structure data, which is collected at Client specified intervals. Traffic count data, which is supplied for specific count stations, the location details of which are stored within the system. Works history data, which is supplied by government agencies or contractors as a means of updating road construction and maintenance information for sections subjected to other than routine works. v vy v Version: 1.05 2-4 Issue date: 22 October 2002Road Asset Management System Part A: General Condition Drainage External Inventory ae Traffic ) ) ) Structure ) providers ) Works History) Figure 2.4 General structure for data and models 2.5.1 PMS-4 Data is stored within the PMS-4 master database (File name: ramsDB.mdb) in a variety of database tables. The types of data required and the relevant PMS-4 database within which they are stored are summarised in Table 2.1. The tables are classified into the three main types of data in Table 2.2. The specification for new ‘survey’ data is contained in a set of stand alone statements contained in Part B: Appendices B3 to B8 of the RAMS Manual. These requirements need to be met by external data providers, much in the same way as the earlier PAMS ENG files were populated by data supplied by external suppliers. The applicable specifications, sources and formats for external data are listed in Table 2.3. PMS-4 also accesses a Look Up table (Lookup.dbf), which comprises a list of strategic sections described later in section 6.1.1, populated with representative values for all 159 road network variables. The only model used within PMS-4 is that for Segmentation (including aggregation) in order to produce homogenous road segments which are subsequently populated with the full set of HDM-4 road network variables and imported into HDM-4. The appropriate rules are as follows, based on use of a dynamic process of first segmenting and then aggregating road data to produce uniform road segments for analysis: i) Adjacent homogenous sections (usually between 100 m and 1 km long) with pavement width difference not exceeding +15% are aggregated; Version: 1.05 2-5 Issue date: 22 October 2002Road Asset Management System Part A: General ii) Adjacent homogenous sections with IRI difference not exceeding +25% are aggregated; ili) The above rules are not executed if the following conditions are true: ‘+ road designation changed ‘+ surface type changed * traffic changed «a significant gap is found between the end and start chainages of two adjacent sections For each aggregation, appropriate aggregation functions are used to re-caloulate the various parameters [e.g. avg(IRI); sum(area of damage), etc} Table 2.1 ‘Summary of PMS-4 database tables ron Pre IramsCondition [Details of surveyed road condition. Stored as homogeneous sections the length lof which is determined by the survey interval (typically 100m) auetiedt iramsDrainage [Details of drainage facilities on road network iramsEvent™ [List of events (e.g. bridges, fly-overs, under-passes, etc.) on JKR road network lramsEventType _|List of supported event types on JKR road network (lookup table) Iramsinventory List of homogeneous sections for which inventory characteristics are constant lramsNode* List of nodes on JKR road network | lramsNodeType* [List of node types on JKR road network _ - IramsPavernentType [List of pavement types found on JKR road network (lookup table) lramsRoad [List of roads (routes) on JKR road network _ List of different road classifications found on JKR road network. A lookup table lwhich defines default values for the various road parameters lramsRoadClass’ lramsRoadinState [Specifies which portions of which roads lie in which states lramsShoulderType List of shoulder types on JKR road network (lookup table) lramsState List of states (major administrative regions) in Malaysia (as used by JKR) lramsStructure [List of homogeneous sections for which structure characteristics are constant |ramsTrafficCountAADT |List of traffic counts conducted on road network, and AADTS recorded for lvarious vehicle types ramsT raficCountStation [List of traffic count stations (count points) on JKR road network ramsTrafficCountType [List of different types of traffic counts conducted by HPU (e.g. 16-hour, 24- hour, ete a ‘Derivation —_|Used to control the derivation of AADT for roads with no count points, or for lroads with multiple count points ra IramsWorksHistory IRecord of works conducted on road network (recorded as where, when, and what) = not currently used Version: 1.05 2-6 Issue date: 22 October 2002Road Asset Management System Part A: General Table 2.2 Summary of PMS-4 database tables _ rvey Ordinance ‘System ramsCondition ramsNodes * RamsEventType ramsDrainage ramsRoads | RamsNodeType * ramsEvent * ramsRoadinState RamsPavementType ramsinventory ramsStates RamsRoadClass * ramsStructure ramsTrafficCountStations | RamsShoulderType ramsTrafficCountAADT _| ramsTrafficDerivation RamsTrafficCountTypes | ramsWorksHistory ee *=not currently used Table 2.3, External data sources, related PMS-4 tables and specification name Related PNS-a tables Data Specification IN ‘ramsCondition RAMS Manual Part B, Appendix 83 DRAIN ramsDrainage RAMS Manual Part 8. Appendix B4 INVENTORY, ramsinventory RAMS Manual Part B, Appendix 85 STRUCTURE ramsPaverentStructure RAMS Manual Part B, Appendix B6 TRAFFIC COUNT AADT | ramsTrafficCcountAADT ___| RAMS Manual Part B, Appendix 87 WORKS HISTORY ramsWorksHistory RAMS Manual Part B, Appendix B& 2.8.2 HDM-4 The types of data comprise the following, with further descriptions, parameter values ‘and their derivation given in Part C of the RAMS Manual, the HDM-4 Supplementary User Guide. These are stored within folders in the HDM-4 Workspace. > Vehicle fleet - Seven vehicle types have been specified > Works standards - Over 70 standards have been defined. v Traffic flow — A single flow pattern for Federal Roads, defined as ‘Interurban’, has been specified with a single flow period, > Speed flow - Two speed flow types have been defined, namely a 2-lane road and a 4-lane dual-carriageway, which is applicable to all multi lane divided carriageways. Accident rates have not been defined, but information is now. available from local research to be used in specific case studies > Climate - A single climate has been defined based on Tropical-humi. Standard HDM-4 Version 1.3 models have been used with appropriate calibration factors applied through look up tables in PMS-4 (for ROWE). The default relationships and model coefficients have been used for RUE models. Version: 1.05 27 Issue date: 22 October 2002Road Asset Management System Part A: General 2.6 System Operation and Management 2.6.1 Relation to Functional Roles The system has been developed to support particular functional roles within JKR’s Roads Branch The primary role of the system is — a) to provide and manage network information and b) to produce decision support outputs for road maintenance planning and programming at a network role; and in the examination of project economic feasibility The scope of application is currently limited to bituminous surfaced Federal Primary roads. ‘The management functions which are currently supported are described in Table 2.4. The system is administered by the Road Maintenance Unit of JKR’s Roads Branch, and they should be consulted regarding its institutional use. Table 2.4 Management functions, HDM-4 Applications and Users Management | RAMS Typical Aims Spatial Coverage and Function Application Time horizon Network PMS-4 [Management and reporting of | Network wide, with basic Information information on road pavement | data provided at a road assets section level updated at = Importation of survey data _| periodic intervals = Preparation of HDM-4 ‘compatible road networks Planning HMA = Formulation of strategic. Network-wide Strategy objectives Analysis - Defining standards Long term (strategic) = Determining resources to support defined standards and objectives Programming | HDM-4 Determining the work programme | Network-wide to State- Programme | that can be obtained within the | wide Analysis budget period and resource constraints Medium term (tactical) Preparation | HDM-4 = Economic feasibiliy of Defined project Project alternatives for major projects | Short - Medium term Analysis _ Not = Design of works ‘Sub-network, Road-ink, applicable | - Preparation and issue of Section or project contracts and works instructions Budget year, annually Operations | Not Planning and undertaking major or | Sections and Sub applicable | minor works to be done on sections on specific specific sections and projects __| projects or sub networks Version: 1.05 2-8 Issue date: 22 October 2002Road Asset Management System Part A: General 2.6.2 User access The fundamental structure for operating and managing the RAMS begins with the definition of User levels, the access which they may gain to the system, and its relevance to their day-to-day tasks. The following classification has been defined HDM-4 User - this class of users will use PMS-4 Malaysia primarily for the creation of data-sets for eventual use in HDM-4. As such, these users only have access to those functions relating to the creation of export data-sets. Primarily, this will involve use of the PMS-4 Export Wizard. In addition, these users may view database tables, and generate system reports. They will also have full access to HDM-4 to develop case studies for particular applications of the system, and to interpret and use these outputs. Data Admin - this group of users are responsible for the loading and maintenance of network survey data into the PMS-4 Malaysia system. They have access to all functions available to HDM-4 Users, plus those functions relating to the importing of ‘survey’ data into the PMS-4 database, and it's subsequent maintenance. In particular, Data Admin users have access to the PMS-4 Import Wizard (as described below), which manages the loading of survey data into PMS-4 database. In addition, they have full access to all survey data which has been imported into the PMS-4 database. This includes the ability to edit existing data, and to add and delete records. They will also assist HDM-4 users in preparing and running case studies within HDM-4, and in producing the required outputs. ‘System Administrator - these users have access to all the functions of the PMS-4 Malaysia software and HDM-4, although the latter does not incorporate different access levels for data security reasons. The functions available will include those accessed by other classes of users. In addition, System Administrators have access to advanced features such as the management of user accounts (including the creation of new users, setting of user level, passwords, etc.). They also have access to ‘non-survey’ database tables such as pavement types, states, roads, etc described as highway ‘ordinance’ and ‘system’ tables / data), Version: 1.05 2-9 Issue date: 22 October 2002| Kumputan Ikram Sdn Bhd aan ro rem (kam Park) dslan Serdang Kang $3000 Kajang Selangor. ‘Te: (603) #7373920, Fax: (608) 8789 1904 ROAD ASSET MANAGEMENT SYSTEM APPLICATION AND USER MANUAL PARTB: PMS 4 User Guide ar@b ten (tgs) TPP scteh ‘vert of rm inghonsRoad Asset Management System Part B: PMS-4 User Guide PUBLIC WORKS DEPARTMENT ROADS BRANCH ROAD MAINTENANCE UNIT ROAD ASSET MANAGEMENT SYSTEM APPLICATIONS AND USER MANUAL (Version: 1.06 —- November 2002) PART B PMS-4 USER GUIDE 1. INTRODUCTION...... 2._ INSTALLATION....... oe 2.1. Installing PMS-4 2.2 Update the Microsoft Jet 4.0 Database Access Driver Patch. 3. OVERVIEW OF THE PMS-4 USER INTERFACE 3.1 Running PMS-4 Malaysia...... 3.2 Description of the PMS-4 Main Window .. 4, IMPORTING SURVEY DATA 44 Overview... 4.2 Using the Import Wizard... 6. MANAGING DATA IN THE PMS-4 DATABASE 5.1 Overview... 5.2. Using the Data Management Module 6. GENERATING REPORTS 6.1 Overview...... 6.2 Generating Reports........ 7._ EXPORTING ROAD SECTION DATA TO 7.1 Overview of the Export Process 7.1.1, Segmentation. 7.1.2. Aggregation 7.1.3 Derivation of Values for Missing Data Items. 7.2 Using the PMS-4 Export Wizard. 8. Administrator Tools .. 9. Appendix B1: PMS-4 Database Structure: 10. Appendix B2: Description and source of the HDM-4 Road Network Variables 11. Appendix B3 Specification for External Data for Road Condition 12. Appendix B4: Specification for External Data: Drain Inventory and Condition 13. Appendix BS: Specification for External Data: Road Inventory 14. Appendix B8: Specification for External Data: Pavement Structure 15. Appendix B7: Specification for External Data: Traffic Counts. 16. Appendix B8: Specification for External Data: Works History Updates... 17. Appendix B9: PMS-4 Look Up Tables oe oetcpecince cence ae EATON NR GL ALARA SSSaR 12. 13-1 Version: 1.08 a Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide PART B PMS-4 USER GUIDE 1. INTRODUCTION PMS-4 is a software tool originally developed by the University of Birmingham, UK. The main purpose of PMS-4 is to simplify the conversion of road administration data for analysis in HDM-4. As a part of the RAMS project 2001/02, the PMS-4 software was adapted by the Consultant team (Kumpulan IKRAM Sdn Bhd, ARRB Transport Research, TRL Ltd and the University of Birmingham) to suit the needs of the Client, JKR. This adaptation has involved the following activities: i) tailoring of the PMS-4 database to reflect JKR survey data / procedures ii) development of import routines for importing the JKR survey data into the PMS-4 database iii) modification of the algorithm used to convert survey data into the HDM-4 import format iv) redefinition of the rules which govern the derivation of default values for those parameters required by HDM-4 which are not in the JKR data-set v) development of bespoke reports The resultant system, a version of PMS-4 adapted to Malaysian conditions, is hereafter referred to as ‘PMS-4 Malaysia’. It forms the database and data preparation component of the RAMS, described earlier in Part A of this Manual. This document is the PMS-4 Malaysia Software User Guide. It describes how to use the PMS-4 Malaysia software. The Guide begins with a description of how to install the software. It continues with an overview of the PMS-4 user interface. The Guide concludes with descriptions of PMS-4's four main functions: the Import Wizard, the Data Management module, the Report module, and the Export Wizard The document is also supported by a series of appendices, including Appendix B1, which contains a description of the contents and structure of the PMS-4 program, Appendix B2, which contains a full list and description of the HDM-4 road network variables and the source or derivation of these within RAMS, Appendices B3 — B8 which contain the ‘Specification for External Data’, and Appendix 9 which presents the current ‘Look Up’ table, later described in detail in Part C of this Manual, which is used in the Export process. The table is a representative HDM-4 road network derived for Malaysian conditions. Version: 1.08 141 Issue date: 14 Novernber 2002Road Asset Management System Part B: PMS~4 User Guide 2. INSTALLATION This section of the User Guide describes how to install the PMS-4 software on your PC. PMS-4 requires certain database access driver files to be present on your PC in order to operate correctly. The main installation program will ensure that most of the necessary driver files are installed on your PC. You will need to run a second installation program however, to ensure that the very latest version of the driver files is installed before running PMS-4 Installing PMS-4 is therefore a two-stage process. The following sections describe each of these stages in turn. 2.1 Installing PMS-4 Please note that you will require approximately S0Mb of disk space for a full installation of PMS-4. This includes space for the actual PMS-4 software, an MS Access database containing RAMS data, and a sample import data set. To install the PMS-4 software on your PC, first close any open applications, and then perform the following steps i) __ Insert the PMS-4 CD in your CD drive. ii) Select the ‘Run...’ option from the Windows ‘Start’ menu. iil) Click ‘Browse...’ and go to the root folder of the PMS-4 CD. iv) Select the ‘Setup.exe’ program, and then click ‘Open’ to return to the ‘Run’ dialog. v) Click ‘OK’ to start the installation program, and then follow the on-screen instructions. vi) You will be prompted to supply an installation folder. By default, PMS-4 will be installed in the folder ‘C:\Program Files\PMS-4 Malaysia’. If you wish PMS-4 to be installed in an alternative location, please specify the appropriate folder when requested. vil) Ifyou happen to get a ‘Path/File access error’ message during installation just press ‘Retry’ and the installation will continue. This is not a true error - it is 2 result of the installation program trying to delete temporary files. vil) If you are prompted to restart Windows when installation is complete, please do 80. The installation program will check whether the necessary database driver files are present ‘on your PC, and install them if not. On completion of the installation process, a ‘PMS-4 Malaysia’ program group will be added to the Windows ‘Start’ menu. This will contain a shortcut that can be used to start PMS-4, 2.2 Update the Microsoft Jet 4.0 Database Access Driver Patch In order for PMS-4 to operate correctly, the very latest version of the Jet Database drivers must be installed on your PC. To do this, first close any open applications, and then perform the following steps: Version: 1.08 Pa Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide Ensure the PMS-4 CD is in your CD drive. Select the ‘Run...’ option from the Windows ‘Start’ menu. Click ‘Browse...’ and then go to the ‘JETSP’ folder on the PMS-4 CD. Here you will find three sub-folders labelled ‘2000’, '95_98_NT" and ‘Me’. These contain the patches for the various supported versions of Microsoft Windows. Go to the sub-folder which corresponds to the version of Windows installed on your PC. Select the ‘Setup.exe’ program, and click ‘Open’ to return to the ‘Run’ dialog Click ‘OK ’ to start the installation program, and then follow the on-screen instructions. Version: 108 2-2 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide 3. OVERVIEW OF THE PMS-4 USER INTERFACE The main purpose of PMS-4 Malaysia is to automate the creation of data-sets which are suitable for subsequent analysis in HDM-4, using data from the various JKR road surveys. The PMS-4 software incorporates three main functions to support this purpose’ i Importation of network survey data, and conversion to a format which simplifies functions ii & ii ii) User viewing and editing of imported data, il) Creation of export data-sets in a format suitable for importing into HDM-4 for subsequent analysis. In addition, PMS-4 incorporates a number of subsidiary functions such as generation of database reports, and database backup / compression. Descriptions of all of these functions are given in the following sections of this user guide. This section describes the fundamental concepts of the PMS-4 software, and introduces the main components of the user interface. 31 Running PMS-4 Malaysia To run PMS-4 Malaysia, click on the Windows ‘Start’ button, and navigate to the ‘RAMS’ program group. From the ‘RAMS' program group, select the ‘PMS-4 Malaysia’ item. Doing so will cause the PMS-4 Malaysia Login screen to be displayed as shown in Figure 3.1 Er Figure 3.1: The PMS-4 Malaysia Login Screen Enter your username and password in the slots provided. PMS-4 Malaysia supports three separate user levels. These are as follows + HDM-4 Analyst - this class of users will use PMS-4 Malaysia primarily for the creation of data-sets for eventual use in HDM-4. As such, these users only have access to those functions relating to the creation of export data-sets. Primarily, this will involve use of the, PMS-4 Export Wizard (as described below). In addition, these users may view database tables, and generate system reports Version: 1.08 3-4 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide ‘© Data Admin - this group of users are responsible for the loading and maintenance of network survey data into the PMS-4 Malaysia system. They have access to all functions available to HDIV-4 Users, plus those functions relating to the importing of survey data into the PMS-4 database, and it's subsequent maintenance. In particular, Data Admin users have access to the PMS-4 Import Wizard (as described below), which manages the loading of survey data into PMS-4 database. In addition, they have full access to all survey data which has been imported into the PMS-4 database. This includes the ability to edit existing data, and to add and delete records. ‘System Administrator - these users have access to all the functions of the PMS-4 Malaysia software. This includes all the functions available to the other classes of users. In addition, System Administrators have access to advanced features such as the management of user accounts (including the creation of new users, setting of user level, passwords, etc.). They also have access to 'non-survey’ database tables such as pavement types, states, roads, etc. (these tables are referred to elsewhere as highway ordinance tables / data). Wherever possible, the PMS-4 Malaysia user interface adapts itself according to the user level. For example, in the ‘Data Management’ module, the amount of control a user has over the various tables (i.e. read / write / add / delete) will depend upon his user level. When you have entered a valid username and password in the Login screen, click ‘OK’. This will cause the ‘PMS-4 Main Window’ to be displayed as shown in Figure 3.2. Serres Figure 3.2: The PMS-4 Malaysia Main Window 3.2 Description of the PMS-4 Main Window The main components of the PMS-4 main window are the menu-bar, the tool-bar and the client-area. In Figure 3.2, the client-area is the empty white area below the tool-bar. The Version: 1.08 32 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide client-area is used to display the sub-windows that are used for the various PMS-4 functions (including importing survey data, editing imported data, viewing database reports, and generating an HDM-4 export file). The tool-bar contains a number of buttons which provide easy access to the most frequently used PMS-4 functions. The following section lists the available tool-bar buttons and describes their functions: £5] 'mport Survey Data - clicking on this button causes the ‘Import Wizard’ to be displayed. The Import Wizard is provided to simplify the task of transferring survey data into the database used by PMS-4. Data Management - this function provides access to the various tables in the PMS-4 database. According to the particular table, you will be able to edit existing data, add new records, and delete current records, to be displayed. This window allows you to generate any of the supported PMS-4 reports. Export — this causes the ‘HDM-4 Export Wizard’ to be invoked. The Wizard guides you through the various steps involved in creating the HDM-4 export file set. The result is a set of dBase files which can subsequently be imported into HDM-4 for analysis. ol Ba] View Reports - clicking this button causes the ‘Report Management’ window # Each of the tool-bar options described above are also available from the menu-hierarchy. For example, the ‘Export Wizard’ can also be invoked by selecting the ‘Export to HDM-4. option from the ‘Tools’ menu as shown in Figure 3.3 below: Figure 3.3: Invoking the Export Wizard from the Tools menu The following sections describe each of these menu / toolbar options in turn, starting with the ‘Import Wizard’, then the ‘Data Management’ module, the ‘Reports’ module, and finally the “Export Wizard’. Version: 1.08 3-3 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide 4, IMPORTING SURVEY DATA 4.1 Overview As stated above, the main purpose of the PMS-4 Malaysia system is to simplify the preparation of HDM-4 import data-sets based on JKR road network data. In performing this function, the PMS-4 software uses the various network data as input, and converts it into a format which is suitable for subsequent use in HDM-4. In order to ensure a robust, reproducible process, PMS-4 Malaysia incorporates it's own internal database in which the various network data are stored. The JKR network data comprises a number of separate data streams, including the relatively fixed ‘Ordinance’ data (e.g. roads, nodes, states, etc.), plus the regularly updated ‘Survey’ data (including condition pavement structure, traffic, etc.). All of this data is stored in the PMS-4 Malaysia database. Al of this data is required for the production of the HDM-4 export data-set. The storage of the required data in a single database helps to avoid data duplication and inconsistency, and helps to maintain the inherent relationships between the various data streams. In short, the provision of the PMS-4 Malaysia database helps to ensure data integrity and consequently, the accuracy of eventual analyses conducted using HDM-4. ‘As PMS-4 Malaysia uses the data stored in its internal database for the production of HDM-4 data-sets, it is imperative that the PMS-4 database is kept as up-to-date as possible. This means that any new or updated data should be loaded into the PMS-4 database as soon as it is available. For certain data-streams, where the scope of the changes is small (e.g. the addition of a new road), it will probably be easiest to edit the PMS-4 database directly. To do this, the ‘Data Management’ module should be used, as described in the next section. Where the amount of changed / new data is considerable (e.g. new ‘Survey’ data), entering the data manually would be both time-consuming and error-prone. For this reason, the PMS- 4 ‘Import Wizard’ is provided, The PMS-4 ‘Import Wizard’ is intended to simplify the loading of the ‘Survey’ data into the PMS-4 database, and provides an option to ‘Map’ this data into a second set of database tables which hold the RAMS data in HDM-4 Export file format. Please note that the Import Wizard requires that the ‘Survey’ data to be imported should be provided in a particular format. In all cases, the data should be provided in Microsoft Access format and conform to the specifications for each data stream as described in Appendices B3-8 of the RAMS manual. These appendices contain written instructions for supplying external data, named ‘Specifications for External Data’. They form an integral part of the system, and should be issued with the Terms of Reference employed by JKR for data collection activities. The Import Wizard comprises a two stage process: the first stage is the actual importing of the external survey data into the PMS-4 Malaysia database. The second stage is the ‘mapping’ (or conversion) of the PMS-4 data onto a separate, internal table which is used for the export process. In order for new survey data to be used in the export process, both stages of the import process must be completed. However, for reasons of convenience, either stage may be performed independently, without the need for the other stage to be performed. For example, the user may wish to import several survey data-sets (e.g. for separate states) before performing the mapping operation. The following section describes how to use the Import Wizard. Version: 1.08 4-4 Issue date; 14 November 2002Road Asset Management System Part B: PMS-4 User Guide 4.2 Using the Import Wizard To invoke the Import Wizard, either click on the respective button on the toolbar, or select the ‘Import Survey Data...’ option from the ‘Tools’ menu. Doing so causes the ‘Introduction’ screen of the Import Wizard to be displayed as shown in Figure 4.1 Figure 4.1: Introduction Screen of Import Wizard This screen explains the purpose of the Import Wizard and informs you what to do next. As described above, the import process normally consists of two stages; i) the actual importing of the survey data, and i) the mapping of the imported data onto the internal table / data structure which is used by PMS-4 for the production of the export file-set. The Import Wizard is primarily intended for performing both stages of the import process, one immediately after the other. However, the Wizard also allows you to perform either of the two stages independently. From the ‘Introduction Screen’, you would typically progress to the actual import stage. However, you may also choose to ‘skip’ the import stage, and go directly to the mapping stage. The setting of the ‘Skip to Mapping Phase’ tick-box determines which stage of the import process you will continue with. If you wish to import new survey data, then leave the tick-box unchecked. If you do not wish to import new data, but instead want to go straight to the mapping phase, ensure that the tick-box is checked. When you are happy with setting of the check-box, click ‘Next’ to proceed to the appropriate stage of the import process. If the tick-box was checked, then the ‘Mapping Phase Introduction’ screen will be displayed as shown in Figure 4.7 below. If the tick-box was not checked then the ‘Select Import File’ screen is displayed as shown in Figure 4.2 below: Version: 1.06 45 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide Select Import File ae stage of the process sto. spetify the namie of the Microsoft Access ‘mdb’ 2% that sot e survey date you Wish to import. Fo da this, ethet enter the relevant Mleneme i rel ones bods herent dead fle that-you specily must include a table which the file you: Figure 4.2: Select Import File Scr The first ‘proper’ step in the import process is to specify the file which contains the survey data you wish to import. Import data should be supplied in the form of a Microsoft Access. database file ('.mdb’ file), as described above and in the various appendices to this user guide. To specify the ‘mdb’ file which contains the data to be imported, either enter the name of the file (including path) directly into the edit box, or click on 'Browse..”, and use the resultant dialog to select the file you require (see Figure 4.3 below): [Snedsan SSCS Miciosoft Access Database (mdb) a Cancel Figure 4.3: Select Import File Screen of Import Wizard Version: 1.08 46 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide When you have specified the file you wish to import data from, click ‘Next’ to proceed to the next stage of the process. This causes the ‘Select Import Data Stream(s)’ screen to be displayed as shown in Figure 4.4 below: Raat Select Import Data Stream(s} The lethox below showe the supported data ereame in the selected databace, Select those data steams that you wan! to inpot by clicking on the corresponding entes inthe lst When you have selected the requited data steams, click Nex! to intiate the actual impott process. If enors are detected in any ofthe selected data streams, the relevant data willnot be imported, and you wil be notified ofthe problem. Inventory Stucture Figure 4.4: Select Import Data Stream(s) Screen of Import Wizard When this screen is opened, the specified database is searched for tables which contain data for one of the supported survey data-streams. In version 1.06 of PMS-4 Malaysia, the following streams of survey data are supported: Condition Drainage Inventory Structure Traffic Count AADT Works History viv The list-box on this screen shows the supported data streams that were found in the specified database. In the example shown in Figure 4.4, the database contained Condition, Inventory, and Structure data. Therefore, only these data streams are shown in the listbox. The data streams not shown in the listbox were not present in the database, To continue the import process, select the data streams that you wish to import by clicking on the respective entries in the list-box. Then click ‘Next’ to initiate the actual importing of the data. The progress of the import process is reported, as shown in Figure 4.5 below: Version: 1.06, 47 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide Sa ait) Select Import Date Sueam{s) The listbox below shows the suppotted data steams inthe selected database. Select thase data streams that you want to mpot by clicking onthe eartesponding enties inthe fs. When you have selected the requied data steams, cick Nev! to inate the actual import process. If enors are detected in ary of the selected data streams, the relevant data wil not be imported. and you wil be noted ofthe problem. Import Progress: Importing data from Inventory table... Figure 4.5: Progress of Import Process Sometimes the Import Wizard may encounter an error in the specified database which prevents some (or all) of the data from being imported. When this occurs, an error report will be displayed, informing you of the problem. The main types of errors that might be encountered are as follows: * database corrupt - the specified ‘mdb’ file may be corrupt, or may already be in use. In either case, you should exit the Import Wizard (by clicking ‘Cance'’) and correct the problem before proceeding with the import process. "error in data stream table - although the specified ‘mdb’ file contains tables with the appropriate names for the data streams selected, the structure of these tables does not match the description given in the appendices to this user guide. Alternatively, the respective tables may be corrupt. In either case you should quit the Import Wizard (by clicking ‘Cancel’) and correct the problem. In the case of such errors being reported, you will need to rectify the underlying problems before re-attempting to import the relevant data. If none of the selected data streams could be imported, you will not be allowed to continue the import process. Instead you will need to exit the Import Wizard and rectify the problems before trying again. If at least one of the selected data streams was imported successfully, the ‘Data Imported Successfully’ screen will be displayed (as shown in Figure 4.6), and you will be allowed to continue the import process. Version: 1.06 48 save date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide eae Data Imported Successfully ‘The Sttuctue data has been successful imported fiom the fle C:\Documents and Seltings\David\ My Documents\HDM-4\Projects\Malaysia\O8 - PMS 4\IKRAM. DatatSurveyD atePerak 2002, md. I you wish to import other data streams, navigate back tothe previous screen and proceed ae before, Ifyou have fished mpottng data, you ‘may ext the Import Wizard. However, you should note thet the newly mported data ‘cannot yet be used by the PMS-4 Expot Wizard, It must fist be ‘mapped’ onto the internal daa stuctute used by the Expot Wizard. In order to perform this mapping, you should ensure thatthe tick-box below is ticked and then click Nest. Ta ext the Inport Ward without perfoming the mappina. ensure thatthe tick box below is noticed, and then click Fish’ In tis caso, there wil be a short delay whist the PMS-4 database is ‘compressed This s dane in order to reduce database ‘boat which can occur ater importing data. TF Man imported data to Export Wizard format Figure 4.6: Data Imported Successfully Screen of Import Wizard At this point, you may wish to import further data streams before progressing. To do this, click ‘Back’, and repeat as before, until all the data streams have been imported. Please note however, that the actual importing of the data isn’t the end of the import process (as. described in the text in the above figure). Although the selected data has been appended to the respective PMS-4 Malaysia database tables, it is not yet ready for use by the Export Wizard. The Export Wizard does not use the various PMS-4 ‘base’ tables directly (i.e. ‘Condition’, ‘Structure’, ‘Inventory’, ‘Traffic’, etc.), but instead uses a dedicated internal table which is used solely for the creation of the export file-set. In order for the newly imported survey data to be used by the Export Wizard, it must first be ‘mapped’ onto this export table. This ‘mapping’ process constitutes the second phase of the import process, as described in the figure above. If you wish to exit the Import Wizard without performing this mapping, you should ensure that the tick-box labelled ‘Map imported data to Export Wizard format’ is not checked, and then click ‘Finish’. You may perform the mapping process at a later time. In order to perform the mapping process now, you should ensure that the tick-box labelled “Map imported data to Export Wizard format’ is checked, and then click ‘Next’, This will cause the ‘Mapping Phase Introduction’ screen to be displayed as shown in Figure 4,7. Version: 1.06 49 Issue date: 14 Novembar 2002Road Asset Management System Part B: PMS-4 User Guide a _ Mapping Phase Introduction Figure 4,7: Mapping Phase Introduction Screen This screen is used to initiate the mapping process. To commence the mapping of the newly imported data onto the export table, click ‘Next’. As the mapping process proceeds, progress will be displayed on the screen as shown in Figure 4.8 below: Figure 4.8: Mapping Progress If any errors are detected during the mapping process, they will be reported as illustrated in the example shown in Figure 4.9 below. Please take careful note of any such messages. Mapping problems are likely to mean that a full data-set will not be available for any subsequent export process. Consequently, you should endeavour to investigate any mapping problems, and resolve the underlying fault(s). Version: 1.08 4-10 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide Figure 4.9: Mapping Error Screen Once the mapping phase is complete, the ‘Mapping Completed Successfully’ screen wil be displayed as shown in Figure 4.9. Reaching this screen signifies that the mapping process has completed successfully, and that the newly imported data is ready for use in the export process. To exit the Import Wizard, click ‘Finish’. Import Wizard Figure 4.9: Mapping Completed Successfully Screen ‘Version: 1.08 an Issue date: 14 November 2002Road Asset Management System art B: PMS-4 User Guide 5. MANAGING DATA IN THE PMS-4 DATABASE 5.1 Overview As described in the previous section, PMS-4 Malaysia incorporates its own database, in which it stores the JKR network data used for creating HDM-4 compatible data-sets. The database is implemented using a Microsoft Access .MDB file. This file is password protected, and therefore cannot be edited directly (e.g. using MS Access) without the Password, which is known only by System Administrator users and the system's developers This protection has been employed in order to reduce the risk of the database becoming corrupted, which might prevent the PMS-4 Malaysia export function from working correctly. All access to the PMS-4 Malaysia database is facilitated using the ‘Data Management’ module. This provides basic, table level access to the various tables in the PMS~4 Malaysia database. The ‘Data Management’ module supports the following functions, according to user level (for information on PMS-4 user levels, see section 3) Viewing - users may view the various tables in order check the data contained in the PMS-4 Malaysia database. All tables may be viewed by all users. Editing - users may correct erroneous data, or update old data. Editing is only available for certain tables, and for certain levels of user. HDM-4 Users may not edit any data. Data ‘Admin users may edit all survey data (i.e. all data streams supported by the Import Wizard - see section 4), but may not edit ordinance data (e.g. roads, states, etc.), or other system tables (e.g. users). System Administrator users may edit all tables in the PMS-4 Malaysia database, ‘Adding - in certain cases, users may add new records to the PMS-4 Malaysia database. HDM-4 Users cannot add any new data. Data Admin users may add new records to the various survey data tables, but not to other tables. System Administrator users may add records to all tables. Deleting - similarly, users may delete existing records from the various tables in the PMS-4 Malaysia database. HDM-4 cannot delete data from any table. Data Admin users may delete records from all survey related tables. System Administrator users may delete records from all tables. Table 5.1 summarises the access rights to the various PMS-4 Malaysia database tables for the different user levels: Version: 1.08 54 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide 5 Ca PEER ViewEdivAdd/Delete | View/edivAcd/Delete_| View [Drainage View/Edit/Add/Delete_ Inventory View/EdivAdd/Delete Pavement Type ViewiEdivAdd/Delete Road View/EdivAdd/Delete [Road in State | View/EdivAdd/Delete |= = State View/EdivAdd/Delete | View View al Structure View/EdivAddiDelete_| View/Edt/AddiDelete | View Traffic Count AADT WEdivAdd/Delete_| View/Edit/Add/Delete_| View ‘Traffic Count Station | ViewEdivAdd/Delete |View | View ‘Traffic Derivation | View/Edit/Add/Delete | View si User. View/EdivAdd/Delete_| = 7 [Works History View/Edit/Add/Delete | View/EdtAdd/Delete | View Table 6.1: Database Access Right for PMS-4 Users 5.2 Using the Data Management Module To invoke the PMS-4 ‘Data Management’ module, click the appropriate button on the toolbar, or select the ‘Data Management’ option from the ‘Tools’ menu. The will cause the following window to be displayed, as shown in Figure 5.1 Figure 5.1: Data Management Console Window This listbox in this window shows the all the tables in the PMS-4 database that users have access to. The list of tables shown will depend upon the level of the current user. For example, if the current user has System Administrator status, then the ‘User’ table, and other system tables will be displayed. These tables will not be shown for other user levels. To open a table so that you may view / edit it, either double-click on the appropriate entry in the listbox, or select the appropriate entry and then click ‘Open... This causes the ‘Data View’ window to be displayed, as shown in Figure 5.2. Version: 1.08 5-2 Issue date: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide ri Tata ki Tend ki Torecton ans Teurvey date 2 OZT73000_|175 seh tT 31/12/00 caer7aa0 73 aes [2 sia Ey i oeziao000 |180 (oazt8T000 cozteio00_|t8t ~Josztwznog a2 ooztao0d |e (ouztaso00 oo2183000 ~ jouzte4000 | 84 oozteao00 fret [Biizron 317120 ai7i2/0 ~[onere6a00 0zt87000 iiceieeea| 1/1200 meee —joveae000 68 S20 0 | [srrta700 —jooztast00- cL ocziast00 Figure 5.2: Data View Window The ‘Data View' window contains a data-grid which is populated with the data from the selected table, Each row of the grid contains a separate row of the table. The table's field names are displayed in the column headers. At any given instance, the data-grid control has a current record. The identity of the current record is indicated by the presence of the '®’ symbol in the left-most column. As you move through the grid (e.g. using the arrow keys) the position of this symbol will change to indicate the change in the current record. To change the current record, you can either use the arrow keys, or click on any cell in the required row. Either way, the change of current record will be indicated. Various controls are provided to allow you to navigate through the table's data. Use the scroll bars to move through the table's records and fields. The record navigation control in the bottom-left of the window may also be used to navigate through the table's records. The various buttons are used as follows: [ia] First Record - sets the current record to the first record in the table. [M]_ Previous Record - changes the current record to the previous record in the table. a Next Record - changes the current record to the next record in the table. fi] Last Record - changes the current record to the last record in the table. Version: 1.08 5-3 Issue dato: 14 November 2002Road Asset Management System Part B: PMS-4 User Guide To edit a record, simply click in the cell that corresponds to the recordifield that you wish to edit, and then type the new value. To delete a record, set to be the current record by clicking anywhere in the respective row, and then press the ‘Delete’ key on your keyboard, To add a new record to a table, first navigate to the end of the table using either the arrow keys, the scroll bars, or the ‘Last Record’ button (described above). If your user level allows you to add records, then a blank record (an empty row) will be displayed at the bottom of the table, with a ‘i’ symbol in the leftmost column, To enter the new record, click anywhere in this row, and then enter the new data in the various fields, Version: 1.08 54 Issue date: 14 November 2002Road Asset Management System Part B: PMS~4 User Guide 6. GENERATING REPORTS 6.1 Overview PMS-4 Malaysia includes a number of in-built reports. These reports are used to provide detailed information on the current content of the ‘Survey’ data contained within PMS-4 database. Example hardcopies of the current reports are included in Appendix B10. 6.2 Generating Reports The ‘Report Management’ window provides access to the various reports built into PMS-4 Malaysia. To invoke this screen, either click on the appropriate button on the toolbar, or select the ‘Reports...’ option from the ‘Tools’ menu. This will cause the ‘Report Management’ window to be displayed as shown in Figure 6.1: Com Pavement Conaiton (by Road) Pavernent Disinage (by Flood) Pavement Inventory by Road) Pavement Stuuctize [by Road) Figure 6.1: Report Management Window The listbox in the window lists the various reports that are currently available in PMS-4 Malaysia. To view a particular report either double-click on its entry in the listbox, or select the appropriate entry and then click the ‘Open...’ button. This will cause the ‘Report Viewer’ window to be displayed as shown in Figure 6.2: Version: 1.08 61 Issue date: 14 November 2002