S3ni3S SG'MVGNV.LS 3JNVN3.LNIVW GNV NDIS3a AVMHDIH 3Hl

Transcription

1 S3ni3S SG'MVGNV.LS 3JNVN3.LNIVW GNV NDIS3a AVMHDIH 3Hl Public Disclosure Authorized Public Disclosure Authorized Public Disclosure Authorized Public Disclosure Authorized

2 THE HIGHWAY DESIGN AND MAINTENANCE STANDARDS SERIES - User's Guide and PC Disks The World Bank Washington, D.C.

3 HDM-PC was prepared under the direction of Asif Faiz, transport operations adviser, in the Infrastructure Department. Rodrigo Archondo-Callao and Ravi Purohit wrote the manual and developed the tutorial and data management utilities for HDM-PC. The manual was edited by Kim Briggs. The core HDM-III and the Expenditure Budgeting Model (developed by Thawat Watanatada and others) were ported from mainframe to the personal computer environment by Anil Bhandari, Rodrigo Archondo-Callao, and Ravi Purohit. Copyright 1989 The International Bank for Reconstruction and Development I The World Bank 1818 H Street, N.W. Washington, D.C , U.S.A. All rights reserved Manufactured in the United States of America First printing January 1989 HDM-PC is designed for use on IBM XT, AT, or compatible personal computers with a 20 to 40 megabyte hard disk. A minimum installed memory of 640K is required to run the HDM-PC program, using MS-DOS version 2.2 or higher. The HDM-PC program was written to assist in the operational work of the World Bank. The HDM-PC is licensed for distribution and support to the Center for Microcomputers in Transportation (McTrans), University of Florida, 512 Weil Hall, Gainesville, FL., 32611, U.S.A. [(01) (904) ]. The authors, the World Bank, the members of its Board of Executive Directors, the countries they represent, and McTrans and its authorized distributors make no representation or warranty with respect to the HDM-PC program other than as specified in the User License Agreement. The purchaser assumes all risk for the installation and use of, and results obtained from, the program. The authors, the World Bank, and Me Trans shall not be liable for any error contained in the program or in the supporting manual or documentation supplied with the program or for incidental or consequential damage resulting from furnishing, performance, or usc of the program. Although every effort has been made to test HDM-PC and ensure its accuracy, the World Bank is not in a position to provide user support. McTrans will provide limited support to users who purchase the technically supported version of the HDM, as specified in the User Licence Agreement. IBM is a registered trademark of International Business Machines Corp., MS-DOS is a trademark of Microsoft Corp., Lotus is a trademark of Lotus Corporation, and Sidekick is a trademark of Borland Corp. Library of Congress Cataloging-in-Publication Data Archondo-Callao Rodrigo, HDM-PC. (The Highway design and maintenance standards series) 1. Roads--Design and construction--computer simulation. 2. Roads--Maintenance and repair- Computer simulation. I. Purohit, R. K. II. Title. III Series. TE175.A '072' ISBN

4 Preface Road construction and maintenance account for a large proportion of public expenditures, while the costs of vehicle operation and depreciation to road users are even greater. To minimize total road transport costs for individual road links and for the road network as a whole, alternative options for maintaining and improving roads must be compared and the tradeoffs between them carefully assessed. This requires the ability to quantify and predict the physical condition of roads and the effects of road geometry and condition on road user costs. The Highway Design and Maintenance Standards Study, initiated by the World Bank in 1969 and carried out in collaboration with leading research institutions and road agencies in several countries, provides empirical quantification of the tradeoffs between the costs of road construction and maintenance and vehicle operation. The empirical relationships resulting from this large-scale research program have been incorporated in the Highway Design and Maintenance Standards Model; its third version, HDM-III, was issued in HDM-III is designed to make comparative cost estimates and economic evaluations of different construction and maintenance options, including different time-staging strategies, either for a given road project on a specific alignment or for groups of links on an entire network. The user can search for the alternative with the lowest discounted total cost and can call for rates of return, net present values, or first-year benefits. If the HDM is used in conjunction with the Expenditure Budgeting Model (EBM), the set of design and maintenance options that would minimize total discounted transport costs or maximize net present value of an entire road network under year-to-year budget constraints can be determined. Since HDM-111 and EBM were originally developed for mainframe implementation, the large size of these models and the cumbersome data input/output procedures tended to discourage their use for routine project and network level evaluations. The possibility of porting these models for DOS implementation was investigated in early 1987, and a replicate of mainframe HDM-III was issued as HDM-PC in June The next stage was the development of HDM-PC Version 2.0, which includes the core HDM III model (with the same capability as the mainframe version), a constrained version of EBM, a number of data management utilities, and a tutorial. With its many user-friendly features, the current version of HDM-PC should be a versatile analytical tool for evaluating policies, standards, and programs of road construction and maintenance. The first version of HDM-PC has been extensively used for project evaluation and academic instruction in more than twenty countries. We hope that the HDM-PC (Version 2.0) will advance the art of highway project analysis and evaluation of highway expenditure programs. The flexibility of use offered by lll

5 HDM-PC should permit local experimentation with the model, including its calibration and adaptation to suit local conditions and requirements. To facilitate the distribution and continual support of the HDM-PC, Version 2.0, the software has been licensed to the Center for Microcomputers in Transportation (McTrans), University of Florida, Gainesville, Florida, 32611, U.S.A. [(01) (904) ]. McTrans distributes the software through a worldwide network on behalf of the World Bank, and provides on-going technical support in the use of the software, software maintenance, and functional enhancements. Limited support is available to users who purchase the technically supported version of thehdm. AsifFaiz Transport Operations Adviser Jeffrey Gutman Chief, Transport Division lv

6 Contents Acknowledgments Introduction General Use of the Model ix Foundations of the Model xi Structure of the Model xi Some Limitations of the Model xiv Data Requirements xiv Staffmg and Training Requirements xv Chapter 1. Installing HDM on Your Computer System Requirements 1 Program Installation 2 Work Area Setup 3 Program Backup 5 Chapter 2. The HDM Program The Program 7 The Input Data Files 7 The Output Files 9 The Run Control File 11 The Five Executable Modules 12 The Direct Access Files 15 The HDM Lotus Facility 15 The Read Program 16 The HDMPRINT Program 16 Chapter 3. Using the HDM Program The Procedural Steps 17 SettingUptheWorkArea 17 Creating the Input Data Files 18 Running the HDM Program 19 Viewing the Results 22 Printing the Results 23 Running the Lotus Facility 23 Vl1 ix v

7 Importing Results into Lotus Clearing the Work Area 35 Chapter 4. The Input Data Facility The Facility 37 The Data Cards 38 The Full-Screen Data Entry Forms 39 The Cards Editor 41 The Automatic Card Generator 42 The Run Control File Editor 42 The Help Screens 42 Chapter 5. Using the Input Data Facility The Procedural Steps 43 Setting Up the Work Area 43 Running the Input Data Facility 43 Using the Cards Editor 45 Using the Automatic Card Generator 57 Using the Run Control File Editor 64 Chapter 6. An HDM Application The Procedural Steps 67 Defining the Problem 67 Defming the Structure of the Run 69 Organizing the Input Data 74 Creating the Input Data Files 79 Running the HDM Program 90 Analyzing the Results 95 Chapter 7. Expenditure Budgeting Model The EBM Program 123 Installing the EBM Program 125 Using the EBM Program 125 General Format of Commands and Input Data 126 The Input Data 127 The Input File 131 The Standard Options File 131 The Optimization 132 Other Commands 133 HDM Interface 135 Running the EBM Program 140 EBM Commands Reference 147 EBM Error Messages V1

8 Acknowledgments The HOM-PC model is a refmed and user-friendly personal computer version of the Highway Design and Maintenance Standards Model (HOM-III). The main elements ofhdm-pc, namely the core HOM-III model and EBM, were developed for mainframe application by Thawat Watanatada, Clell Harral, William Paterson, Ashok Dhareshwar, Anil Bhandari, and Koji Tsunokawa. The idea for a personal computer implementation ofhdm-iii originated with Per Fossberg, who provided guidance and support throughout the development of HOM PC. The HOM-III model was adapted to the personal computer environment by Anil Bhandari and George Tharakan, for use with the Xenix operating system. This adaptation formed the basis for the DOS implementation of the model. William Paterson helped in drafting the introduction to the manual. The development of the model software and documentation benefited from the comments of many individuals. Special thanks go to Alfred Nickesen of GOPA Consultants, Bad Homburg, (Federal Republic of Germany), who tested an HOM-PC prototype, Torsten Bergh of the Swedish Road Administration, who tested the EBM program, and Renato Schultz, who applied HOM-PC to a road improvement and maintenance project. Vl1

9

10 Introduction The Highway Design and Maintenance Standards Model (HDM-III), issued in 1987, was developed by the World Bank to meet the needs of the highway community, particularly in developing countries, for evaluating policies, standards, and programs of road construction and maintenance. The original mainframe version of the model has been adapted to the personal computer environment and is available as HDM-PC, Version 2.0, which includes the core HDM-111 model, a facility to input data, a facility to use the HDM outputs with Lotus, and a constrained version of the Expenditure Budgeting Model (EBM). The model simulates total life-cycle conditions and costs and provides economic decision criteria for multiple road design and maintenance alternatives for one road link, a group of roads with similar characteristics, or an entire network of paved and unpaved roads. The primary cost set for the life-cycle analysis includes the costs of road construction and maintenance and vehicle operating costs, to which travel time costs can be added as an option. The costs of construction-related traffic delays, congestion, accidents, and environmental pollution can be entered in the model exogenously based on separate estimates. HDM-111 can be coupled with the companion EBM to find the best way of using road agency funds under budget constraints. General Use of the Model A common application of the model is to examine questions such as: What is the economic benefit of spending another dollar on maintenance, compared to spending it on new roads or improvements to existing alignments? Is it more economical to construct a strong, expensive pavement initially, thereby permitting the use of larger, more economical vehicles and reducing future road maintenance outlays, or to follow a stage construction strategy, economizing on initial cost, restricting vehicle axle loads, and paying more for maintenance, with the intent of upgrading the road later on when traffic growth warrants it? How much should be spent to maintain paved roads and how much to maintain and upgrade earth and gravel roads? What are the consequences of deferring certain road maintenance expenditures during years of financial stringency? IX

11 X Introduction What combination of maintenance policies yields the lowest overall economic costs for a specified level of maintenance funding? Within the planning, budgeting, and programming functions of a highway agency (Figure 1-1), the model may therefore be used to establish: Desired budget levels that would minimize the total cost of road transportation. Appropriate policies and standards for construction and maintenance programs that are consistent with minimizing total transport costs under existing resource constraints. Long-term and medium-term investment and expenditure programs. Appropriate, economically derived intervention criteria to develop short-term programs and annual budgets, based on an appropriate pavement management system. An important feature of the model is the analytical support it can provide to make a convincing case to legislatures and top decision makers for adequate funding for road maintenance. Figure 1-1. Role of HDM-III in Planning Highway Expenditures 0 Construction maintenance strategies C Representa tive road links o r segments Er HD~-111 life-cycle simulation of condition and cost streams Segment and strategy H Budget plan B, I I : Transport L. i policy [ : scenarios :! J l c--l~~~~~-il~~----- A , :----D;t~b--;s;- I 1 -traffic I : -network! -conditio n : -unit cos ts I I I j 1 l I Data : collection I ~ ~~~~~~~~~ I : Implementation ; I ' I I I I I I Pavement management system _l Short-term detailed program G F ;' J Total costs and benefits each case 1 Segment I Best strategy for link or project I l EB~ Network benefits :-budget (1' I ' I ' 1 Long-term K National 1 regional resource policy and standards allocation -strengthening -resurfacing -maintenance Intervention criteria Resource allocation N , I I : Local : i Budget! : proposal : I I ~

12 Introduction xi With appropriate choice of parameter values, it can also be used for applied research in engineering and economics. In engineering, for example, the model may be used to optimize road maintenance strategies, determine economic thresholds for programming road improvements, determine an economic optimum for axle loads, or simulate the type and extent of road deterioration as a function of cumulative traffic loads or time. In economics, the model has potential application in research related to user charges, pricing and taxation of automotive fuels, highway cost allocation, and road transport pricing. Foundations of the Model HDM-III is the result of eighteen years of research and analysis carried on in collaboration by the World Bank and major research institutions and highway organizations in Australia, Brazil, France, India, Kenya, Sweden, the United Kingdom, and the United States. The initial effort was directed at developing analytical methods and models, but it was soon found that quantitative data for implementing such models were deficient. Accordingly, the scope of the work was progressively expanded to establish the necessary quantitative foundations. These efforts focussed largely on field collection of primary information to establish the underlying physical and economic relationships between vehicle speed and road user inputs and road deterioration as related to road design and maintenance standards. Between 1971 and 1982, four major empirical studies were carried out in Kenya, the Caribbean, India and Brazil. The work is documented in a series of World Bank publications entitled: The Highway Design and Maintenance Standards Series. The titles are listed below: Vehicle Operating Costs: Evidence from Developing Countries. Andrew Chesher and Robert Harrison. Vehicle Speeds and Operating Costs: Models for Road Planning and Management. Thawat Watanatada, Ashok M. Dhareshwar, and Paulo Roberto S. Rezende Lima. Road Deterioration and Maintenance Effects: Models for Planning and Management. William D. 0. Paterson. The Highway Design and Maintenance Standards Model: Volume 1, Description of the HDM-I/1 Model. Volume 2, User's Manual for the HDM-III Model. Thawat Watanatada, Clell G. Harral, William D. 0. Paterson, Ashok M. Dhareshwar, Anil Bhandari, and Koji Tsunokawa. The first three volumes in the series provide theoretical foundations and statistical estimation of the underlying physical and economic relationships. The other two volumes describe the model and its use and together with this manual are essential references for applying HDM PC. Structure of the Model The broad concept of HDM-III is quite simple (Figure I-2). Three interacting sets of costs (related to construction, maintenance, and road use) are added together over time in discounted present values, where costs are determined first by predicting physical quantities of resource consumption and then by multiplying these quantities by their unit costs or prices. Economic benefits are then determined by comparing the total cost streams for various maintenance and construction alternatives with a base case (null alternative), usually representing minimal routine maintenance. HDM-III is designed to make comparative cost estimates and economic evaluations of different construction and maintenance options, including different time-staging strategies, either for a given road project on a specific alignment or for groups of links on an entire network.

13 xii Introduction INPUTS Figure I-2. Structure of the HDM-III Model SUBMODEL OUTPUTS Vehicle type, volume, growth, loading, physical parameters. Terrain, materials, rainfall, geometry, thickness, unit costs. Pavement type and strength, ESA, age, condition, maintenance strategy. Road geometry and roughness; vehicle speed, type; unit costs. Developmental, traffic delay, accident, environmental, others. Above outputs for analysis year. Annual records. TRAFFIC 1 ROAD CONSTRUCTION (when required) 1 ROAD DETERIORATION and MAINTENANCE 1 VEHICLE OPERATING COSTS 1 EXOGENOUS BENEFITS AND COSTS 1 ANNUAL RECORD 1 SUMMARY REPORTS Volume by vehicle type, equivalent standard axles. Construction quantities; new condition, type. Cracking, ravelling, potholes, rut depth (paved); gravel thickness (unpaved); roughness; maintenance quantities. Fuel, lubricant, tires, maintenance, fixed costs, speed, travel time, costs. Costs and benefits. Condition, quantities, costs by component for each year requested. Total costs by component; net present values and rates of return by link. It estimates the total costs for a large number of alternatives year-by-year for up to thirty years, discounting the future costs if desired at different specified discount rates, so that the user can search for the alternative with the lowest discounted total cost. The user can call for rates of return, net present values or first year benefits. Another capability of HDM-III used in conjunction with the Expenditure Budgeting Model, is finding the set of design and maintenance options that would minimize total discounted transport costs or maximize net present value of an entire highway system under year-to-year budget constraints. In addition to comparing alternatives, the model can analyze the sensitivity of the results to changes in assumptions about key parameters such as unit costs, traffic composition, traffic growth rates, the discount rate, the value of passenger time, and accident costs.

14 Introduction xiii Adequate analysis of the many possible combinations of alternatives is too large a task for manual calculations. Even when analysts have had access to computers of sufficient capacity, they have been hampered by the absence of two essential components. An efficient simulation program embodying an appropriate model and procedures for using it. An adequate body of empirically established relationships among the relevant variables. Until recently, for example, data on the effects of road roughness on vehicle operating costs were limited, and not fully reliable, as were data on the progression of road roughness, under different maintenance practices and environmental regimes. HDM-111 fills both of these needs. It is not only a readily usable program for handling the voluminous computations automatically; it is also a repository of the most extensive and consistent set of empirical relations between the construction and maintenance standards, traffic characteristics, road deterioration, and vehicle operating inputs. The operational framework for the MS-DOS implementation of the model (HDM-PC) is shown in Figure 1-3. Figure 1-3. Operational Framework for HDM-PC HDM-III, Vol. 1 HDM-III, Vol. 2 Define application area I Define structure of application I Collect data Create data files I Run HDM program I Obtain results of run I Print results Import results into Lotus I View results on screen l Use results for EBM program y Modify data files I Analyze results I In a single computer run, the model can evaluate up to twenty different links or typical groups of road links, each having up to twenty sections with different traffic conditions. In addition, up to thirty different maintenance strategies (scheduled or condition responsive) can be

15 xiv Introduction specified for different sections. At any time, a link can be upgraded (from earth to gravel, for example, or from gravel to paved surface), realigned or widened. Altogether, up to fifty pairs of alternatives can be compared in one run. Further cases can be handled in additional runs. In order to make a comparison of alternative construction and maintenance strategies, detailed specifications of construction programs, design standards, and maintenance alternatives are needed together with unit costs, projected traffic volumes, and environmental conditions. The model includes a checking program that examines the inputs for format errors and internal inconsistencies and determines whether the model is being used beyond its empirically validated range. The model estimates for each road section, year-by-year, the road condition and resources used for maintenance under each strategy, as well as the vehicle speeds and physical resources consumed by vehicle operation. The physical resources for road construction for each design option may be estimated from relations within the model, or may be directly specified by the user if more specific information or local data are available. After physical quantities involved in construction, maintenance, and vehicle operation are estimated, user specified prices and unit costs are applied to determine financial and economic costs; relative benefits are then calculated for different alternatives, followed by present value and rate-of-return computations. The user has a wide range of options in specifying what results are to be included in the reports. Some Limitations of the Model Although the model has a sound empirical base, model users should be aware of the following limitations. The submodel for vehicle operating costs does not include the effects of congested traffic conditions, but congestion costs may be entered as an exogenous input in the model. The road deterioration submodel does not include freezing climates but facility to adjust the submodel for most effects of freezing conditions is provided and has been validated. The model does not explicitly account for the effect of varying basic routine maintenance (shoulder and drainage maintenance, grass cutting, and maintenance of side slopes) on pavement performance, but this can be handled indirectly by adjusting pavement strength parameters. The model endogenously predicts neither road accidents and their costs, nor the indirect costs incurred during road construction or maintenance. Facility is provided, however, to incorporate accident costs, delays, and environmental impacts where exogenous estimates are available. The user confronted with any of the above conditions should make appropriate provisions or adaptations in the analysis. It is important to recognize, moreover, that the model is not intended to be used for final engineering design. The model can be incorporated as a planning and evaluation module in a pavement management system, as it is essentially a tool for economic analysis of alternative standards either at the project or the network level. Data Requirements Since the model is designed to represent realistically the actual road network and conditions to which it is applied, its use requires detailed information describing the characteristics and conditions of roads, the volumes and composition of traffic, the terrain, the climate, and the

16 Introduction unit costs of activities involved in construction and maintenance options to be evaluated. The data requirements for standard HOM applications may at first appear voluminous, but they are nothing more than those that should normally be on hand for planning purposes. For some data, default values built into the model are used if country specific values are not supplied. Other data must be supplied by the analyst. The basic data requirements for a network-based application are outlined below. Description of existing network: aggregate lengths of road links or sections grouped according to type of subgrade and surface, current condition, geometry, terrain, rainfall, and volume and composition of traffic. Construction options (one or several may be specified for any road section): geometry and surface characteristics as they would be after construction, project cost or physical quantities per kilometer with unit costs (although the model can estimate some physical quantities from terrain and geometry), and related cost streams (financial, economic, and foreign exchange). Maintenance standards (a number of alternative options may be specified) and unit costs: for example, a maintenance standard for a gravel road might be grading after every 6,000 vehicles passes. Another might be grading every two weeks. For a paved road, it might be patching potholes as they appear and applying a 40 mm bituminous overlay wherever the roughness index exceeds a critical threshold. The maintenance options can be specified according to a predetermined time schedule or in response to surface condition. Characteristics and unit costs for different types ofvehicles: axle loads and their configuration, power, fuel consumption, utilization, and unit costs offuel, tires, maintenance items and new vehicle purchase, for such categories as cars, buses, trucks, and articulated vehicles. Traffic volumes and projected growth: normal and generated, by vehicle type, for each road link or group of links; the generated traffic may differ for different construction options. Exogenous benefits and costs: such as, differences in travel time and accident costs, air pollution cost, and so on, based on separate calculations or estimates. Length of analysis period and discount rates. Figure 1-4 (next page) shows how the various data inputs are sequentially linked in the HOM model. Staffing and Training Requirements HOM-PC is a versatile tool but it must be used intelligently to obtain useful results. As the model attempts to simulate a rather complex engineering-economic system, it is possible to misuse the model and obtain results that may be impractical from an engineering standpoint. Hence the operation of the model requires a team consisting of an experienced highway engineer and a transport economist, one of whom should have some experience in computer applications. The two HOM-III volumes and the HOM-PC manual are self-instructive and it takes about three to four weeks to become conversant with the use of the model. Figure 1-5 shows the suggested order of reading this manual and the other volumes in the HOM series. Users conver-

17 xvi Introduction SERIES A Figure 1-4. HOM Data Requirements SERIESB SERIES C SERIES D SERIESE SERIES F Defmelink properties. Assign link ID's to roads. Defmeroad geometry and other characteristics. - Defmecon- Defme Defme Defme trafstruction road main- vehicle fleet fie sets. costs and tenance op- andvoc Specify the options. tions and unit costs. traffic ID's Specify units costs. Assign codes Specify construe- Defme to different average daily tion ID's standard vehicle traffic for and link surface ID groups, etc. each vehicle ID's af- codes. group. fected. r I SERIESG l Defmethe exogenous costs and benefits. Assign ID's to different benefits and costs options. Enumerate link alternatives, traffic ID's, - I--+ construction options, capital costs, maintenance expenses, and EXO-BC options. SERIESH Enumerate group alternatives group codes and link alternatives in each group. SERIES I Request various reports for link and group alternatives. r-- SERIESJ Compare link and group alternatives. SERIES K Specify run control information and titles for various reports.

18 Introduction xvii sant with computers and DOS applications, however, may skip directly to Chapter 6 after reading the first three chapters of the HDM-PC manual. Figure I-5. Suggested Order of Reading This Manual Chapter 1 Installing HDM on Your Computer J Chapter 2 The HDM Program 1 Chapter 3 Using the HDM Program J Chapter 4 The Input Data Facility., ~ HDM-III Volume 1 HDM-III Volume 2 1 Chapter 5 Using the Input Data Facility J HDM-III Chapter 6 Companion Volumes Volume 1 and 2 An HDM Application in HDM Series ~ ~ HDM-III Chapter 7 Volume 1 Expenditure Budgeting Model ~ 1 Attaining proficiency in the use of the HDM-PC model requires a three-stage process. Stage 1. Work carefully through the HDM-PC manual thus learning the mechanics of software usage and gaining a clear understanding of model structure and operation (means of data input, file organization and management). Stage 2. Use the HDM tutorial data sets (Chapter 6) to gain an understanding of the technical content of the model (highway engineering and economics) and to learn to create HDM input data sets for model application. Stage 3. Utilize HDM-PC for real-world problems beyond the scope of the tutorial data sets. Stage 1 can be completed with the help of the HDM-PC manual. Stage 2 requires a good understanding of the User's Manual (HDM-III, Volume 2) and some parts of Model Description (HDM-III, Volume 1). Stage 3 requires comprehensive knowledge of HDM-III, Volume 1 and relevant parts of the companion books in the HDM series on road deterioration and vehicle operating costs.

19

20 Chapterl Installing HDM on Your Computer This chapter describes the hardware and software system requirements and the procedures for program installation, backup, and work area setup. System Requirements You must satisfy certain hardware and software requirements before you can install HDM on your computer. Hardware An IBM AT, XT or compatible system. An IBM AT or faster 80286/80386 system is recommended because of the large processing time required to run the program. A 20 to 40 megabyte hard disk, depending on the size of the problem you want to analyze. To run the program at full capacity at least 30 megabytes of free disk space are needed. The minimum requirement is 10 megabytes of disk space. A minimum installed memory of 640 Kb. A color or monochrome monitor. A printer capable of printing 132 characters per line. A high-speed printer is recommended because of the large volume of output generated. Optional: A math co-processor -- strongly recommended because of the large amount of computations performed by the program. Software DOS version 2.2 or higher. Optional: A text editor capable of creating standard ASCII text files for data input. Optional: Lotus to analyze the results. 1

21 2 Installing HOM on Your Computer CONFIG.SYS File The HDM program requires a configuration of at least fifteen files at a time. This exceeds the number allowed by the DOS default configuration. To override this default, create or modify the CONFIG.SYS file in the root directory of your hard disk so that it will contain the following two lines: FILES=15 BUFFERS=15 DOS Setup Include in the AUTOEXEC.BAT file the PATH command to tell the computer where the DOS files are located. For example, if all DOS files are stored in a directory called DOS, include the following line in your AUTOEXEC.BAT file: PATHC:\DOS DOS Knowledge Running the HDM program requires a basic knowledge of DOS. You should know how to: Create new directories. Change directories. Copy files. Erase files. Back up files. Restore files. If you wish to usc a text editor to create the input data files, choose a text editor or word processor capable of creating ASCII text files. Most text editors and word processors on the market are capable of creating ASCII files. The notepad of Sidekick is recommended because Sidekick is a resident program with a built-in calculator and is easy to use... Program Installation To install the program on your hard disk using DOS commands, create a directory called HDM and copy all the files supplied on the program disks (six DSDD 51!4 inch disks or three DS 3 1/2 inch disks) into this directory. Follow the steps below. 1. Turn on your computer and at the DOS prompt C >,make a directory for HDM with the command: C>MD\HDM Note: In this manual commands needed to install and rnn the HDM program are printed in bold face. Only type the keys shown in bold face when you input program commands. 2. Change to the HDM directory with the command: C>CD\HDM 3. Place the first HDM program disk in drive A and enter:

22 Installing HOM on Your Computer 3 C>COPY A:*.* 4. Repeat Step 3 for all the HDM disks supplied. Note: Instrnctions for installing the EBM program are outlined in Chapter 7 of this manual. 5. List the files in the HDM directory with the command: C>DIR The files in the HDM directory should be the same as those listed in Table 1-1. Work Area Setup To avoid confusion, create and use a new hard disk directory for every HDM application. In this directory, you will store all the input data files required by the HDM program and the program will store all the results. To create and set up these work area directories, follow the steps below. 1. Name the directory you want to create, using a maximum of eight characters. Examples: HDMDATA PROJECT! HDMDEMO HDMCHINA For the demostration run used in Chapter 3, use the name HDMDEMO and follow the instructions below. 2. Make a new work area directory with the command: C > MD\HDMDEMO 3. Change directory with the command: C > CD\HDMDEMO 4. Copy the batch files stored in the HDM directory to the new directory with the command: C>COPY C:\HDM\*.BAT 5. Check that the following files have been copied to the directory HDMDEMO: RUNCLEAR.BAT RUNHDM.BAT RUNINPUT.BAT RUNREAD.BAT RUNLOTUS.BAT RUNPRINT.BAT by listing the files in the directory HDMDEMO with the command: C>DIR For each new HDM application, repeat Steps 1-5 above replacing the name HDMDEMO with the name of the new work area directory.

23 4 Installing HDM on Your Computer Table 1-1. HDM-PC Software Package Contents Disk Files Description 1 HDMl.EXE First HDM module 2 HDM2.EXE Second HDM module 1 HDM3.EXE Third HDM module 3 HDM4.EXE Fourth HDM module 4 HDM5.EXE Fifth HDM module 6 HDMLOTUS.EXE Lotus Facility 4 HDMPRINT.EXE Print Facility 3 READ.COM Read Facility 2 READ.ME Latest documentation 5 HDMINPUT.EXE HDM Input Data Facility 5 HDMOVl.OVL HDM input overlays 6 HDMOV2.0VL 3, 4, 5, 6, 7, 8 HDM input overlays 6 HDM CARD.DBF HDM input cards database 6 HDM SET.DBF HDM input set database 6 HDM WORK.DBF HDM input work database 6 HDMAUTO.MEM HDM input generator memory 6 HDM SES.MEM HDM input session memory 6 CARDSEQl.TXT 2, 3, 4, 5 Predefined sequences RUNCLEAR.BAT Clear batch file 2 RUNHDM.BAT HDM batch file 2 RUNINPUT.BAT Input Data Facility batch file 2 RUNREAD.BAT Read Facility batch file 2 RUNLOTUS.BAT Lotus Facility batch file 2 RUNPRINT.BAT Print Facility batch file 2 DEMOA.TXT Series A for sample run 2 DEMOB.TXT Series B for sample run 2 DEMOC.TXT Series C for sample run 2 DEMOD.TXT Series D for sample run 2 DEMOE.TXT Series E for sample run 2 DEMOF.TXT Series F for sample run 2 DEMOGHIJ.TXT Series G, H, I, J for sample run 2 DEMOK.TXT Series K for sample run 2 DEMORUN.TXT Run Control File for sample run 3 TUTORA.TXT Series A for tutorial 3 TUTORB.TXT Series B for tutorial 3 TUTOR C. TXT Series C for tutorial 3 TUTORD.TXT Series D for tutorial 3 TUTORE.TXT Series E for tutorial 3 TUTORF.TXT Series F for tutorial 3/4 TUTORGl.TXT G2, G3, G4 Series G, H, I, J for tutorial 3/4 TUTORKl.TXT K2, K3, K4 Series K for tutorial 3/4 TUTORUNl.TXT N2, N3, N4 Run Control File for tutorial

24 Installing HDM on Your Computer 5 Table 1-1 (cont). HDM-PC Software Package Contents Disk Files Description EBM.EXE EBMDESC.DAT EBMHELP.DAT EBMSTD.DAT EBMTEST.TXT EBMprogram EBM description EBM help flle EBM standard options file Data flle for EBM sample run Program Backup After you have installed the program on your hard disk, you will no longer need the disks supplied unless you want to install the program on another computer. For safety, make a backup copy of the HDM program in one of the following ways. 1. Use the DOS DISKCOPY command to make copies of the disks supplied. a. Enter the DISKCOPY command: C > DISKCOPY A: A: b. Insert the first program disk in drive A and follow the computer's instructions to copy all disks. 2. Use the DOS BACKUP command to back up the flles copied to the HDM directory. a. Format new disks using the command: C>FORMAT A: b. Enter the BACKUP command: C>BACKUP C:\HDM\*.* A: IS and follow the computer's instructions. Refer to the DOS manual for detailed instructions about these commands.

25

26 Chapter2 The HDM Program This chapter describes the structure of the HDM program and presents an overview of its modules. The Program The HDM program has a fairly simple structure (shown in Figure 2-1). It reads the input data from a series of input files and writes the results to a series of output files. Figure 2-1. HDM Program Structure Input files I HDM program I Output files The Input Data Files The input data required by the HDM program is divided into eleven series, each identified by a letter from A to K. Exihibit 2-1 shows partial samples of some series and Table 2-1lists the information contained in each series. A complete description of the structure and contents of each series is presented in the HDM-III User's Manual. The HDM program requires the information defined in the eleven series, but it reads only eight input files. One file stores the information from four series (G, H, I, and J) because these series defme the structure of the run; and the other seven files store one series each. 7

27 8 The HOM Program Exihibit 2-1. Sample of Input Data Series LINK GRAV GRAVEL ROAD 1 A101 SECTION A102 SECTION DATA U ALL A201 ENVIRONMENT A202 GEOMETRY A203 CONDITION 150. A309 SURFACE UPAV A301 BASE/SUBGRADE A302 HISTORY 0 A303 END LINK A211 UNIT COSTS C101 08ECONOMIC 6.0 C104 10ECONOMIC 6.0 C104 12ECONOMIC C104 STANDARD p STD1PAVD C ROUTINE MAINTENANCE C PATCHING C303C 10 OVERLAY C305B NAME CAR PICKUP LCAR TRUCK ARTIC D101 VEH TYPE D102 HP METRIC D104 EQX D107 ECONOMIC D401B VEHICLE D402 TIRE D403 MAINT LAB D404 PETROL D410 KM DRIVEN D503 VEH LIFE D504 HR DRIVEN D505 TRAFFIC TUNP N ElOl DESCRIPTUNPAVED TRAFFIC E102 NEWADT E103 NEWADT E103 END TRAFFIC E104 RUN TITLE HDM SAMPLE RUN BRAZ K101 DATE K102 CURRENCY DOLLARS DOLLARS K103 ROUGHNESS IR QI K104 READ: K106 ALL DATASETS K107 MODELLING 0 K114 EVALUATION K115

28 The HOM Program 9 Table 2-1. Input Data Series Series A B c D E F G H I J K Information Link characteristics Construction alternatives Maintenance alternatives Vehicle characteristics Traffic Exogenous costs or benefits Definition of link alternatives Definition of group alternatives Reports requests Comparison of alternatives Run characteristics The input data ftles may be created and edited using any text editor, or using the HDM Input Data Facility supplied with the HDM program and described in Chapters 4 and 5. The eight input data ftles can have any name or extension. Some suggestions are listed in Table 2-2. Table 2-2. Sample Input Filenames Series Suggested names A B c D E F G,H,I,J K DEMOA.TXT DEMOB.TXT DEMOC.TXT DEMOD.TXT DEMOE.TXT DEMOF.TXT DEMOGHU.TXT DEMOK.TXT MALIAAAA.TXT MALIBBBB.TXT MALICCCC.TXT MALIDDDD.TXT MALIEEEE.TXT MALIFFFF.TXT MALIGHU.TXT MALIKKKK.TXT HDMDATA.AAA HDMDATA.BBB HDMDATA.CCC HDMDATA.DDD HDMDAT A.EEE HDMDATA.FFF HDMDATA.ZZZ HDMDATA.KKK The Output Files The HDM program stores results in seven output files. Table 2-3lists the information contained in each output ftle. The seven output ftles can have any name or extension. Some suggestions are listed in Table 2-4. The Scan Files The scan ftles contain the input data in the same format as the input data ftles (one HOM card per line). These ftles also contain a description of the errors and warnings detected by the HDM program.

29 10 The HOM Program Table 2-3. Output Files File Scan 1 Scan2 Scan3 Scan4 Echo print Results EBMinput Information Scan of series K, A and B Scan of series C, 0, E and F Scan of series G, H, I, J and summary of input errors Simulation errors Echo print of input data Reports 1 to 11 Input data file for the EBM program The scan 3 file is of particular importance because it contains a summary of all the errors and warnings detected. The HOM program will not execute if any error is detected but will continue to compute results if a warning is detected. The Echo Print File The echo print file contains the input data in a format that is easier to read and check. The echo print presents full description and the values of all input variables. The size of this file is a function of the input data, so the file can be quite large. An option is available in series K for suppressing the echo print file. The Results File The results file contains the results generated by the HOM program. All the reports requested in series I and K will be stored in this file. The size of this file is a function of the number of reports requested, so the file can be quite large. The EBM Input File The EBM input file contains the input data required by the EBM (Expenditure Budgeting Model), that can be used to determine the best manitenance policy under budget constraints. The data generated by the HOM program may be used as input data for the EBM. See Chapter 7 for further information. Table 2-4. Sample Output Filenames Output files Suggested names Scan 1 Scan2 Scan3 Scan4 Echo print Results EBMinput SCAN LOUT SCAN2.0UT SCAN3.0UT SCAN4.0UT INPUT.OUT RESULTS.OUT EBMOATA.OUT MALISCNl.OUT MALISCN2.0UT MALISCN3.0UT MALISCN4.0UT MALIINPU.OUT MALIREST.OUT MALIEBM.OUT HOMOUT.SC1 HOMOUT.SC2 HOMOUT.SC3 HOMOUT.SC4 HOMOUT.INP HOMOUT.REs HOMOUT.EBM

30 The HOM Program 11 Refer to the HDM User's Manual for a full description of the output files and to Chapter 6 of this manual for examples. Table 2-5 summarizes the characteristics of all the output files generated by an HDM run. Table 2-5. Description of the Output Files File Record length Type Contents (characters) Scan Sequential Scan and error messages for data in series K, A and B. Scan2 132 Sequential Scan and error messages for data in series C, D, E and F. Scan3 132 Sequential Scan and error messages for data in series G, H, I, J and errors summary. Scan4 132 Sequential Summary of simulation errors. Echo print 80 Sequential Echo print of all input data. Results 132 Sequential Reports type EBMinput 80 Sequential Data file for EBM program. The Run Control File The HDM program needs as input the names of the eight input data files to read and the names of the seven output files to create. This information is stored in a separate file, called the Run Control File. The Run Control File is an ASCII text file with only fifteen lines. Each line corresponds to the name of one input or output file. Table 2-6lists the order of the filenames in the Run Control File. Note: A path can precede the filename, which means that the input and output files do not have to be in the same directory or disk drive. Storing all the input data files and output files in the same hard disk directory, however, is recommended to avoid confusion.

31 12 The HOM Program Line File Table 2-6. Run Control File Example Name of ftle for series K Name of ftle for series A Name of ftle for series B Name offtle for series C Name of ftle for series D Name of ftle for series E Name of file for series F Name of ftle for series G, H, I, J Name offtle for scan 1 Name of file for scan 2 Name of ftle for scan 3 Name of ftle for scan 4 Name of ftle for echo print Name of ftle for results Name of ftle for EBM input DEMOK.TXT DEMOA.TXT DEMOB.TXT DEMOC.TXT DEMOD.TXT DEMOE.TXT DEMOF.TXT DEMOGHIJ.TXT C:\HDMDEMO\SCANl.TXT C:\HDMDEMO\SCAN2.TXT C:\HDMDEMO\SCAN3.TXT C:\HDMDEMO\SCAN4.TXT A:INPUT.OUT C:\RESULTS\RESULTS.OUT A:EBMDAT A. OUT The Five Executable Modules To adapt the HDM-III (mainframe version) to the PC environment, the mainframe program was divided into five executable modules, and three new programs were created to form HDM-PC. To run the HDM program and obtain the results, the five modules must be executed in the correct order (see Figure 2-2). Figure 2-2. The Five Executable Modules HDMINPUT.EXE I HDMl.EXE HDM2.EXE Mainframe f--- HDM3.EXE HDM-PC HDM HDM4.EXE HDM5.EXE I HDMPRINT.EXE I HDMLOTUS.EXE I

32 The HOM Program 13 To execute the five HDM modules, run the RUNHDM batch file. The listing of the RUNHDM.BAT ftle is: C:\HDM\HDMl C:\HDM\HDM2 C:\HDM\HDM3 C:\HDM\HDM4 C:\HDM\HDM5 The primary functions of the five executable modules, including the input files read and the output ftles generated by each module, are summarized in Table 2-7. Table 2-7. Primary Functions of the Executable Modules I Module Primary function Input files read Output ftles generated HDMl Read data for series K, A, B (run control, link characteristics and construction projects) and give error messages. Series K Series A Series B Scan 1 HDM2 Read data for series C, D, E, F (maintenance unit costs and standards, vehicle characteristics and unit costs, traffic sets, and exogenous costs and benefits) and give error messages. Series C Series D Series E Series F Scan2 HDM3 Read data for series G, H, I, J (link alternatives, group alternatives, reports requests and comparison of alternatives) and give error messages. Series G Series H Series I Series J Scan3 HDM4 Produce a formatted echo print of input data. Echo print HDM5 Simulation (modelling) and evaluation of alternatives and production of reports. Scan 4, Results, EBMinput Figure 2-3 shows the basic HDM file structure for the demonstration run described in Chapter3.

33 14 The HOM Program Figure 2-3. HDM Structure DEMORUN.TXT (Run Control File) DEMOK.TXT DEMOA.TXT DEMOB.TXT DEMOC.TXT DEMOD.TXT DEMOE.TXT DEMOF.TXT DEMOGHIJ.TXT SCANl.TXT SCAN2.TXT SCAN3.TXT SCAN4.TXT INPUT.OUT RESULTS.OUT EBMDATA.OUT INPUTS Control (DEMOK.TXT) 1- I 1- Links (DEMOA.TXT) I 1- Const. (DEMOB.TXT) I Maint. (DEMOC.TXT),_ Vehicles (DEMOD.TXT) 1- Traffic (DEMOE.TXT) I 1- I E-BC (DEMOF.TXT) I I OUTPUTS HDMl.EXE -1 Scan of K, A, B I HDM2.EXE HDM3.EXE -I Scan of C, D, E, F I Scan of G, H, I, J } Input echo print I HDM4.EXE -I Errors I Reports(DEMOGHIJ.TX1 ~ ~ Reports 1-11 I HDMS.EXE Input for EBM I I L I Direct Access files

34 The HOM Program 15 The Direct Access Files The HDM program creates seven Direct Access files (HDM_1 to HDM_7) during its execution. These files are placed in the work area directory and store all the input data and results (the deterioration history and cost streams for all alternatives) in binary form readable only by the HDM program. The size of these files can be from 1 to 30 megabytes and is a function of the size of the problem being analyzed. The location and the names of these files are assigned by the HDM program itself and cannot be changed. These seven files are overwritten when the HDM program is run for a second time in the work area directory. After the HDM runs are over, these files should be erased because of the large amount of disk space taken up by them. The batch file R UNCLEAR.BA T is used to erase these seven Direct Access files. The HDM program does not erase these files automatically at the end of each run because the HDM Lotus Facility uses them to create the Lotus reports. Maintain the files after an HDM run, if you want to import the results for this run into Lotus The HDM Lotus Facility The HDM Lotus Facility is a program that allows you to import all HDM results into Lotus This facility is not available in the mainframe version of HDM. Figure 2-4 shows the relationship of the Lotus Facility to the HDM program. The Lotus Facility reads the Direct Access files created by the HDM program and presents you with a menu of options. The Lotus Facility creates tables that are imported into Lotus with the File Import Numbers option. Once the tables are in Lotus 1-2-3, you can create your own reports or graphs. Use the RUNLOTUS.BAT batch file to run the HDM Lotus Facility, after running the HDM program and before erasing the Direct Access files. Figure 2-4. HDM Lotus Facility I Input data HDM -l o_u_tp_u_t_fi_le_s_ program L ~----~~~ _D HDM ir_ec_t_a_c_c_e_ss_fi_il es 1- Lotus facility I Tables I Lotus I Customized I El Graphs

35 16 The HOM Program The Read Program The seven output flles created by the HOM program are 132 characters wide, many pages long, and designed to be printed. However, these flles can be reviewed on the screen with a text editor or word processor. The READ program supplied with the HOM program is a utility that allows you to easily browse through any file. The READ.ME file gives updated information about the program and this documentation. To print this flle, enter the command: C >PRINT C:\HDM\READ.ME To use the READ program, run the RUNREAD.BAT flle. The HDMPRINT Program The HOM program is written in Fortran so the output flles generated by the program contain some characters in the first column that control the printer. If you use the READ program to view these files on the screen you will notice that a series of l's or O's appears in the first column and that the flles will not be paginated. To print these flles with correct pagination and spacing, run the RUNPRINT.BAT batch flle.

36 Chapter3 Using the HDM Program This chapter describes the procedure for running the HDM program, using a demonstration run to illustrate each step. The demonstration run uses input data files supplied with the program. The Procedural Steps To use the HDM program, follow the steps outlined below: Set up the work area. Create the input data files. Run the HDM program. View the results. Print the results. Run the HDM Lotus Facility. Import the results into Lotus Clear the work area. Setting Up the Work Area The first step in running the HDM program is to set up a directory on the hard disk where you will create the input data files and the program will store the results. Create a directory on the hard disk and copy the batch files supplied with the program into that directory. For the demonstration run, use the HDMDEMO directory set up with the instructions given in Chapter 1. Remember that for each new HDM application, you need to set up a new directory with a name of your choice. If you have not already set up the HDMDEMO directory (see Chapter 1), follow the steps below: 1. Make a new work area directory with the command: C > MD\HDMDEMO 17

37 18 Using the HDM Program 2. Change directory with the command: C > CD\HDMDEMO 3. Copy the batch files stored in the HDM directory to the new directory with the command: C>COPY C:\HDM\*.BAT Creating the Input Data Files The next step in running the HDM program is to create the input data ftles with any text editor or with the Input Data Facility described in Chapters 4 and 5. The recommended procedure is to create the input data files using the Input Data Facility and to use a text editor or the Input Data Facility to edit these files when minor changes are necessary. In this chapter, you will run the HDM program using input data files supplied with the program. For your own application, however, you will need to create the input data files. Refer to the HDM-111 User's Manual for a complete description and examples of each input data series required by the HDM program. In this illustrative HDM example you will evaluate two improvement alternatives for an existing gravel road. Regravelling when existing gravel thickness falls below 50 mm. Paving the gravel road with a bituminous surface in the third year of the analysis period. You will simulate the physical performance of the road under the two improvement alternatives and determine the alternative that yields higher economic return. For this demonstration run, you need the following files: DEMOK.TXT DEMOA.TXT DEMOB.TXT DEMOC.TXT DEMOD.TXT DEMOE.TXT DEMOF.TXT DEMOGHIJ.TXT DEMORUN.TXT To copy these ftles into the HDMDEMO directory follow the steps below: 1. Change directory to HDMDEMO with the command: C > CD\HDMDEMO 2. Copy the demonstration files to the HDMDEMO directory with the command: C>COPY C:\HDM\DEMO*.* The DEMORUN.TXT file contains the filenames of the eight input data ftles and the seven output ftles. In this case, the output files that will be created by the HDM run are: SCANl.OUT SCAN2.0UT SCAN3.0UT

38 Using the HOM Program 19 SCAN4.0UT INPUT.OUT RESULTS. OUT EBMDATA.OUT The contents of the supplied files are listed in Table 3-1 and the files may be reviewed using the DOS TYPE command. For example: C>1YPE DEMORUN.TXT Table 3-1. Sample File Contents Filename DEMOK.TXT DEMOA.TXT DEMOB.TXT DEMOC.TXT DEMOD.TXT DEMOE.TXT DEMOF.TXT DEMOGHIJ.TXT DEMORUN.TXT Contents Run information Gravel road characteristics Paving characteristics Resurfacing characteristics Vehicle characteristics Traffic characteristics Exogenous costs due to paving Reports requests Run Control File Note: You must have all eight input data files named in the Run Control File, even if you are not using the entire data series (A to K). Create a dummy file for any series you are not using. Likewise, you must name all the output files, even the ones you are not requesting. Running the HDM Program After creating the input data files and before running the program, make sure there is enough disk space available on your hard disk to store the results and the Direct Access files. The space required is a function of the size of the problem. For this demonstration run, you need at least 1.5 megabytes of disk space; for a full HDM run you need 30 megabytes. To start the program enter the following command: C>RUNHDM The RUNHDM batch file loads the HDM1 module, which then prompts you for the name of the Run Control File. For this run, enter the name: DEMORUN.TXT The program now displays the computer's time and starts to read series K. Write down this time so that later you can compute the time required to run the program. The program reads series K, A, and B and then the first module displays the message "Stop Program terminated." The RUNHDM.BAT file then loads and executes the second module, and so on, until all the modules arc executed. Figure 3-1 depicts the RUNHDM.BAT file executing the five program modules.

39 20 Using the HDM Program Figure 3-1. Running the HOM Program I Run Control File I HDM1 HDM2 Displays initial time HDM3 HDM4 HDM5 Displays final time At the end of the last module the program again displays the computer's time. Use it to compute the time required to run the program. Some estimated times for the demonstration run are given in Table 3-2. Note that the use of a math co-processor reduces the computational time by 50 percent. Table 3-2. Estimated Times for the Demonstration Run System IBM 60 with math co-processor IBM AT with math co-processor IBM 30 with math co-processor IBM AT without math co-processor IBM 30 without math co-processor IBM XT without math co-processor Time 3 minutes 6 minutes 6 minutes 9 minutes 9 minutes 17 minutes The sequence of an HOM run is shown in Figure 3-2. Four types of errors can occur in running the program. 1. The HOM program detects some errors in one or more input data series. In this case, the program does not compute any results or produce any reports in Module 5 and the program ends without displaying the following two lines at the end of the fifth module: Modelling Evaluation A summary of all input data errors and warnings detected by the HOM program is presented at the end of the scan 3 file and descriptions of all errors and warnings are located throughout the scan 1, scan 2, and scan 3 files. Scan 4 summarizes all errors arising during the model simulation. If the Modelling and Evaluation lines are not displayed in Module 5, fmd the errors, correct them, and run the program again until the HOM executes the modelling and evaluation routines.

40 Using the HOM Program 21 Figure 3-2. HDM Run Sequence C>RUNHDM C > C:\HDM\HDM1 t:::: t:::: ~ HHH HHH HHH HHH t:::: t:::: ~ '"" '"" IIIIIIIIIIIIIIIII - - III III III lfflllllllltllfl '""'"" - III! III III III III III III '"" '"" '"" III III III '"" M '"" III III III '"" '"" III III III '"" '"" IIIIIIIIIIIIIIIII HICtfoiAY DESIGN AN> MAINTENANCE STAN>AROS MODEL THE WORLD BAN< Enter" Run Contr"ol File fi lenatne: OB1QRl..N.TXT The 11me Is 11 :23:23 Scanning: SeriesK Series A SeriesB Stop-Program terminated C > C:\HDM\HDM2 Scanning: SeriesC SeriesD SenesE SeriesF Stop-Program terminated C >C:\HDM\HDM3 Scanning: SeriesG Series H Series I SeriesJ Stop-Program terminated C > C:\HDM\HDM4 Echo print: Series A SeriesB Senese SeriesD SenesE SeriesF Series GH Series I SeriesJ Stop-Program terminated C > C:\HDM\HDM5 Modelling Evaluation The 11me Is 11:28:45 Stop-Program terminated 2. Some of the input data or results filenames in the Run Control File are not correct. The compiler displays an error message in the ftrst module but the batch file continues to execute the other modules giving other error messages. In this case, abort the program by pressing the Ctrl and Break keys simultaneously and ftx the Run Control File.

41 22 Using the HDM program 3. There is a format error detected by the compiler in Modules 1, 2, or 3. The error may result from a label in a numeric field, a number in a wrong column, some hidden characters in a file, and so on. In this case, the compiler gives an error message but the batch file continues to execute the other modules. Find the error and run the HDM program again. 4 There is a system error detected by the compiler in Module 5. The error may result from a division by zero, log of a negative number, real number too large, and so on. In this case, the program gives an error message and stops execution. Check the overall consistency of your input data and try running the program again. Note: To abort the program at any time, press the Ctrl and Break keys simultaneously. Viewing the Results After the modelling and evaluation routines have been executed, you are ready to review the results using the Read program. To view any input or output file on the screen, follow the steps below 1. Run the RUNREAD batch file with the command: C>RUNREAD 2. Enter the name of the file you want to view. For example: SCAN3.0UT The Read program displays the top of the file. To browse through the file, use the keys described in Table 3-3. Table 3-3. Keys and Their Functions Key Esc Right arrow Left arrow Uparrow Down arrow PgUp PgDn Home End Function Exit Read program Scroll to the right Scroll to the left Move one line up Move one line down Move one screen up Move one screen down Move to the top of file Move to the bottom of file You can now view the following output files created by the HD M program: SCAN3.0UT SCANl.OUT SCAN2.0UT SCAN4.0UT

42 Using the HOM Program 23 INPUT.OUT RESULTS. OUT It is always a good idea to view the SCAN3.0UT file first because this file contains the summary of errors and warnings. Printing the Results To print the output files, follow the steps below: 1. Check that your printer is on and that it is set up to print 132 characters per line. 2. Run the RUNPRINT batch file with the command: C>RUNPRINT 3. Enter the name of the file you want to print. For example: SCANl.OUT The HDMPRINT program prints the file with the correct pagination and spacing. The output files can be many pages long, so make sure there is enough paper on the printer. You cannot print a portion of a file with the HDMPRINT program; you must print the entire file. To abort the program at any time, press the Ctrl and Break keys simultaneously. You can also print the output files with the DOS PRINT command. In this case, the reports will not be paginated. Exhibit 3-1 shows a sample of the scan files obtained from the demonstration run. Exhibit 3-2 shows an example of echo print. Other typical reports are shown in the following exhibits. The road deterioration history is given in report type 4 (Exhibit 3-3). The vehicle operating costs are given in report type 5 (Exhibit 3-4). The economic costs are given in report type 7 (Exhibit 3-5). The evaluation of alternatives is given in report type 11 (Exhibit 3-6). Running the Lotus Facility After printing the results, you may wish to import them into Lotus to graph them or produce your own reports. The Lotus Facility is a menu driven program that creates tables to be imported into Lotus (see Figure 3-3). Figure 3-3. Running the Lotus Facility HDM -{ Direct Access files ~ Lotus Facility program H Reports ~ Lotus 1-2-3

43 24 Using the HOM Program Exhibit 3-1. Scan 1 File SERIES K : RUN CONTROL INFORMATION RUN TITLE HOM DEMO RUN BRAZ DATE CURRENCY DOLLARS DOLLARS ROUGHNESS IR QI READ: ALL DATASETS SCAN: ALL DATASETS ECHO PRINT: ALL DATASETS SUPPRESS OUTPUT REPORTS: REPORT 8 REPORT 9 REPORTlO MODELLING EVALUATION END SERIES K101 K K K104 K106 K107 K109 K107 K111 K107 Kl12 Kl13B Kl13C Kl13D 0 K114 Kl15 Kl16 SERIES A : EXISTING LINK CHARACTERISTICS LINK GRA V GRAVEL ROAD 1 SECTION SECTION DATA U ALL ENVIRONMENT GEOMETRY CONDITION 150. SURFACE UPAV BASE/SUBGRADE HISTORY 0 END LINK END SERIES A101 A102 A201 A202 A203 A309 A301 A302 A303 A211 A212 SERIES B : CONSTRUCTION OPTIONS AND COSTS CONSTRUCCNSTGRAVEL CONSTRUC 1 LINK GRAV 1 COST TIME STREAM EXO B-C EXB1 SECTION NEW SECTION DATA P ALL GEOMETRY SURFACE PAVD 1 1 BASE/SUBGRADE 1 STRENGTH PARAMETERS CONDITION SECTION TOTAL COST PER KM END CONSTRUCTION OPTION END SERIES B101 B102 B103 B106 B107 B201 B203 B204 B205 B206 B209 B401 B211 B212

44 Using the HOM Program 25 Exhibit 3-2. Echo Print for Series K HDMMODEL RUN NAME RUN DATE RELEASE3.0 HDMDEMORUN 88/02/20 READ DATA SERIES ABCDEFGHIJK SCAN DATA SERIES ABCDEFGHIJK ECHO DATA SERIES ABCDEFGHIJK MODEL PRINT OPTION 0 EVALUATE ANALYSIS PERIOD : REGION FOR VOC EQUATIONS: BRAZ ROUGHNESS UNIT DATA INPUTDATA IR COMPUTATION UNIT QI INTERCEPT.00 SLOPE BI-01 RELATIONSHIP: BI = 55.0 * 01 CURRENCY OF DATA INPUTDATA DOLLARS OUTPUT DATA DOLLARS OUTPUT CURRENCY MULTIPLIER EXCHANGE RATE: 1.0 DOLLARS TO 1 DOLLARS 1000 LINKS (KM) LENGTH(KM) GROUPS LENGTH GRA V: GRAVEL ROAD GRUP :

45 88/02/20 TWO- ANNUAL WAY TWO-WAY ADT ESA YEAR (VPD) (THOUS) Exhibit 3-3. Road Deterioration History HOff DEMO RUN REPORT TYPE II:PAGE 1 ANNUAL ROAD CONDITIONS REPORT LINK-ALI GRAV-ALTO SECTION 1 PAVED ROAD (MEDIUM STRENGTH SUBSECTION) END OF YEAR CONDITION YEARS SINCE LAST AREA AREA MEAN SO BEF/ ALL WIDE AREA AREA RUT RUT SURF/ AFTER SURF MOD CRACKS CRACKS RAVLD POTHD DEPTH DEPTH ROUGHNS REGRV CONS MAINT TYPE SN (%) (%) (%) (%) (MM) (MMJ (IR) 1. BEF GRAV AFT GRAV 2. BEF GRAV AFT GRAV 3. BEF GRAV AFT GRAV 4. BEF GRAV AFT GRAV 5. BEF GRAV AFT GRAV 6. BEF GRAV AFT GRAV 1. BEF GRAV AFT GRAV 2. BEF GRAV AFT GRAV 3. BEF GRAV AFT GRAV 4. BEF GRAV AFT GRAV 5. BEF GRAV AFT GRAV 6. BEF GRAV AFT GRAV 1. BEF GRAV AFT GRAV 2. BEF GRAV AFT GRAV 3. BEF GRAV AFT GRAV 4. BEF GRAV AFT GRAV 5. BEF GRAV AFT GRAV 6. BEF GRAV AFT GRAV 7. BEF GRAV AFT GRAV 1. BEF GRAV PERIODC MAINT APPLD RESU RESU RESU GRAVEL ROAD MEAN GRAVEL YEARLY THICKNS ROUGHNS (MM) (IR) \) Ol c (/) :; co -::r CD I 0 s:::..., -u 0 co iij 3

46 Exhibit 3-3 (cont). Road Deterioration History c C/) s (Q 88/02/20 HDM DEMO RUN REPORT TYPE 4 : PAGE 2 -;3" ANNUAL ROAD CONDITIONS REPORT (l) :X: LINK-ALT GRAV-ALTl SECTION PAVED ROAD (MEDIUM STRENGTH SUBSECTION) GRAVEL ROAD (Q OJ END OF YEAR CONDITION 3 YEARS TWO- ANNUAL SINCE LAST AREA AREA MEAN SD MEAN WAY TWO-WAY BEF/ ALL WIDE AREA AREA RUT RUT PERIODC GRAVEL YEARLY ADT ESA SURF/ AFTER SURF MOD CRACKS CRACKS RAVLD POTHD DEPTH DEPTH ROUGHNS MAINT THICKNS ROUGHNS YEAR (VPD) ( THOUS) REGRV CONS MAINT TYPE SN (%) (%) (%) (%) (~) (~) (IR) APPLD (~) (IR) BEF GRAV AFT GRAV BEF GRAV MT GRAV BEF GRAV AFT GRAV BEF ST CONS AFT ST BEF ST AFT ST :' BEF ST AFT ST BEF ST AFT ST BEF ST AFT ST BEF ST AFT ST BEF ST AFT ST BEF ST AFT ST BEF ST AFT ST BEF ST AFT ST BEF ST AFT ST BEF ST OVER AFT OVSA BEF OVSA AFT OVSA BEF OVSA AFT OVSA \) BEF OVSA AFT OVSA BEF OVSA AFT OVSA ; BEF OVSA ~ ""C...

47 Exhibit 3-4. Vehicle Operating Costs 88/02/20 HDM SAMPLE RUN REPORT TYPE 5 : PAGE 1 ANNUAL ROAD USER COSTS REPORT ECONOMIC COSTS IR DOLLARS YEAR LINK-ALT. SECTION CAR PICKUP LCAR TRUCK ARTIC 1988 GRAV-ALTO 1 AV. SPEED (KM/H) VOC PER VEHICLE-TRIP VOC PER 1000 VEHICLE-KM FUEL LUBRICANTS TIRES SPARE PARTS MAINTENANCE LABOR CREW DEPRECIATION INTEREST TOTAL RUNNING COST OVERHEAD COST TIME VALUE OF PASS TIME VALUE OF CRGO TOTAL TIME COST REDUCED PASSABILITY COST TOTAL COST RESOURCES PER 1000 VEHICLE-KM FUEL (LITERS) LUBRICANTS(LITERS) TIRES (NO OF COST- EQUIV NEW TIRES) SPARE PARTS (PRCNT NEW VEH PRICE) MAINT LABOR(LAB-H) CREW (CREW-H) DEPRECIATION (PCT NEW VEH PRICE) INTEREST (PRCNT OF NEW VEH PRICE) PASSENGERS (PASS-H DELAYED). 000 CARGO(VEH-H DELYD) \) co c (/1 :;- <C -:r (1) I 0 s:: ""tl... 0 <C til 3

48 Exhibit 3-5. Economic Costs 88702/20 HDM SAMPLE RUN REPORT TYPE 7 : PAGE 1 ECONOMIC AND FOREIGN EXCHANGE COSTS OF ALTERNATIVE IN MILLION DOLLARS LINK-ALI. GRAV-ALTO GRAVEL ROAD - ORIGINAL LENGTH KM YEAR ROAD CAPITAL COSTS ROAD RECURR COSTS EXISTING GENERATED EXISTING GENERATED VEHICLE VEHICLE VEHICLE VEHICLE NET OPERATING OPERATING TRAVEL TIME TRAVEL TIME EXOGENOUS COSTS COSTS COSTS COSTS COSTS TOTAL ECONOMIC COSTS TOTAL FOREIGN EXCHANGE COSTS TOTAL BENEFITS-COSTS - UNDISCOUNTED: ECONOMIC: FOREIGN: DISCOUNTED ECONOMIC COSTS AT.0 % % % % c (/) :; co -:r CD I 0 s::: ""0 0 co Q3 3 1\) <0

49 Exhibit 3-5 ( cont). Economic Costs 88/02/20 HDM SAMPLE RUN REPORT TYPE 7 : PAGE 2 ECONOMIC AND FOREIGN EXCHANGE COSTS OF ALTERNATIVE IN MILLION DOLLARS LINK-ALI. GRAV-ALTl GRAVEL ROAD - ORIGINAL LENGTH KM EXISTING GENERATED EXISTING GENERATED TOTAL ROAD ROAD VEHICLE VEHICLE VEHICLE VEHICLE NET TOTAL FOREIGN CAPITAL RECURR OPERATING OPERATING TRAVEL TIME TRAVEL TIME EXOGENOUS ECONOMIC EXCHANGE YEAR COSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS TOTAL BENEFITS-COSTS - UNDISCOUNTED: ECONOMIC: FOREIGN: DISCOUNTED ECONOMIC COSTS AT.0 % % % % w 0 c C/) :r <0 -:::T <D I 0 s::: '1J 0 <0 ii3 3

50 Exhibit 3-6. Evaluation of Alternatives 88/02/20 HDM SAMPLE RUN REPORT TYPE 11 : PAGE 3 SUMMARY OF COSTS AND COMPARISONS BY DISCOUNT RATE BASE IN MILLION DOLLARS DISCOUNT RATE; % ORIG LENGTH LINK (!<M) CONS I ECO/ RECON GEN FIN UPGRD ALI TRAF CSTS COSTS GRAV ALTO NO ECO FIN ALT1 NO ECO FIN PERIODIC ROUTINE MAINT MAINT COSTS COSTS TOTAL CONST & MAIN I COSTS VEHICLE NET OPERATING EXOGENOUS COSTS COSTS TOTAL COSTS NET PRES COMPARISON VALUE ALT1 VS ALTO INTRNAL RATE OF RETURN (%) 18.1 c (/) :; (.Q -:::r C1) I 0., :5:::... 0 (.Q ii3 3 c.:l...

51 32 Using the HOM Program The results output file created by the HDM program is in an ASCII format and can be directly imported into Lotus or a word processor. However, all the lines of the output file will appear in only one worksheet column so that analyzing the results becomes impossible. The Lotus Facility creates tables that, when imported into Lotus 1-2-3, have all the numbers in different cells and the labels aligned correctly. To run the Lotus Facility follow the steps below: 1. Run the HDM program to produce the results and the Direct Access files (see "Running the HDM Program" earlier in this chapter). 2. Run the RUNLOTUS batch file with the command: C>RUNLOTUS The batch file loads the Lotus Facility program that reads the Direct Access files and presents you with the main menu shown in Figure 3-4. Figure 3-4. Lotus Facility Main Menu HOM Lotus Facility Main Menu Your options are: 1. Tables for one link 2. Tables for all links 9. Exit the program Enter your selection - > 2 3. At the main menu, decide if you want the tables for one particular link or for all links in the run. For the demonstration run, select Option 2 (Tables for all links). After your selection, the program displays the menu of available tables shown in Figure At the tables menu, decide which table you want to create. For the demonstration run, select Option 4 (Economic costs). After your selection, the program asks for the name of the file in which to store the table. 5. Enter the table filename. You can use any legitimate DOS name with a.prn extension and include a destination path if necessary. For example: REPORT4.PRN A:ECONl.PRN C: \LOTUS\ WORK\ T ABLEl.PRN For the demonstration run enter COSTS.PRN as a filename. The program creates the table and returns to the tables menu.

52 Using the HOM Program 33 Figure 3-5. Available Lotus Tables Menu Tables for all links Your options are: 1. Traffic 2. Road cond~ions 3. Financial costs 4. Economic costs 5. Vehicle operating costs 6. Comparison of alternatives 7. Summary table 9. Go to main menu Enter your selection > 4 6. Repeat Steps 4 and 5 to create other tables. For the demonstration run, create a road conditions table with the instructions below: a. Select Option 2 (Road conditions) in the tables menu and the program displays a road conditions menu (see Figure 3-6). b. Select Option 1 (After maintenance) in the road conditions menu. c. Enter ROAD.PRN as the table filename. Notice that this table takes more time to process than the economic costs table. d. Select Option 4 (Exit) on the road conditions menu and go back to the tables menu. Figure 3-6. Road Conditions Menu --ROAD CONDITIONS- 1. After maintenance 2. Before maintenace 3. Before and after maintenance 4. Exit Enter your selection - > 1

53 34 Using the HOM Program 7. Exit the tables menu with Option 9 (Go to main menu). 8. Exit the program with Option 9 at the main menu (Exit the program). Option 1 on the main menu allows you to create tables for only one link. The program asks for the link code and presents you with the appropriate tables menu. Enter the link code in uppercase letters. If you give an incorrect code, the program will display all the codes available. Note: You decide in series I and K which reports to include in the results output file. U'hen you use the Lotus Facility, you can request tables of the reports defined in series K and I or other tables that you may need. Importing Results into Lotus To import the tables created by the HDM Lotus Facility into Lotus 1-2-3, follow the steps below: 1. Load following the instructions of that program. 2. Use the following sequence to change the current file directory to the disk and directory that contains the tables created by the Lotus Facility. Press or Enter I F D [Directory name] <Enter> For the demonstration run, use the sequence: IF D c:\hdmdemo <Enter> Explanation Press the slash key to call the menu Press F to request file option Press D to request directory option Enter directory name Press the Enter key to execute 3. Import a table into with the File Import Numbers option. Press or Enter <Home> I F I N [Table name] <Enter> For the demonstration run, use the sequence: < Home> I F I N cost.prn < Enter> 4. Increase the column size to 12. Press or Enter I w G c Explanation Press the Home key to go to the top Press the slash key to call the menu Press F to request file option Press I to request import option Press N to request numbers option Enter the name of the table to be imported Press the Enter key to execute Explanation Press the slash key to call the menu Press W to request worksheet option Press G to request global option Press C to request column-width option

54 Using the HOM Program <Enter> Enter the column width Press the Enter key to execute For the demonstration run, use the sequence: I W G C 12 < Enter> 5. Use the worksheet in Lotus You can now view, print, and graph the results and compute statistics. Follow the instructions for Lotus Save the worksheet. You can import more than one table into a worksheet to analyze different variables. For example, you can import the ROAD.PRN table into the worksheet that contains the economic cost data to graph roughness against total costs. Follow the steps below: Press or Enter <F5> M1 <Enter> I F I N road.prn <Enter> Explanation Press the F5 key (Go to) Enter cell M1 Press the Enter key Press the slash key to call the menu Press F to request file option Press I to request import option Press N to request numbers option Enter the name of the table to be imported Press the Enter key to execute The worksheet now contains the economic costs and roughness estimates for all link alternatives. The table created by the Lotus Facility for the economic costs (COSTS.PRN) is shown in Exhibit 3-7. Note the similarity between this table and the report type 7 created by the HDM program. Clearing the Work Area The Direct Access files created by the HDM program contain all the results of the HDM run and can be saved on disks and used again by the Lotus Facility at a later time. If you want to save these files on disks using disk drive A, follow the steps listed below: 1. Format a series of disks with the command: C>FORMAT A: 2. Back up the Direct Access files with the command: C>BACKUP C:\HDM\HDM_*.* A: IS At a later time you can restore these files with the DOS RESTORE command and run the Lotus Facility again. Use the following command. C>RESTORE A: C:\*.* IS The Direct Access files take a lot of hard disk space. When you are through with the Direct Access files, erase them using the RUNCLEAR batch file with the command: C>RUNCLEAR

55 Exhibit 3-7. Economic Costs Table (.) 0> HDM 123 REPORT ECONOMIC AND FOREIGN EXCHANGE COSTS DATE 88/02/20 RUN HDM SAMPLE RUN CURRENCY DOLLARS (MILLIONS) EXISTING GENERATED EXISTING GENERATED TOTAL ROAD ROAD VEHICLE VEHICLE VEHICLE VEHICLE NET TOTAL FOREIGN CAPITAL RECURR OPERATING OPERATING TRAVEL TIMETRAVEL TIMEEXOOENOUS ECONOMIC EXCHANGE YEAR COSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS LINK-ALT. GRAV-ALTO LENGTH (km) c LINK-ALT. GRAV-ALTl ~. LENGTH (km) 1000 ::J IC ~ <l) I CJ s:: "'tj IC ii'l

56 Chapter4 The Input Data Facility This chapter describes the structure of the Input Data Facility for creating and editing HDM input data files. The Facility The Input Data Facility is a program designed to create and edit input data files needed to run the HDM program. The facility provides an easier method for creating the HDM input data files than using a text editor or word processor. The Input Data Facility (Figure 4-1) provides: A line-oriented editor for creating and editing the HDM input data files. For every card required by the HDM program, a full-screen entry form gives a description of the input variables, including their types, defaults, and input ranges. An automatic card generator that presents a predefined sequence of cards required for an HDM application. After the information required for the card sequence is entered, the facility generates all the files necessary to run the HDM program. A run control file editor to create and edit the Run Control File required to run the HDM program. Figure 4-1. The Input Data Facility Cards editor r---- (You define the sequence of cards to be entered) Automatic card generator (The program presents a predefined card sequence) 37

57 38 The Input Data Facility The Data Cards A series of cards composes the HDM input data files. Each card corresponds to one line in the input files. For a complete description of the contents of these cards, refer to the HDM-III User's Manual. A sample of an HDM input data file is shown below: Exhibit 4-1. Sample Input Data File LINK IRI2GOOD CONDITION 1 A101 SECTION A102 SECTION DATA P ALL A201 ENVIRONMENT A202 GEOMETRY A203 SURFACE PAVD A204 BASE/SUBGRADE 1 8 A205 STRENGTH PARAMETERS A206 CONDITION A209 HISTORY A210 END LINK A211 LINK IRI4FAIR CONDITION 1 A101 SECTION A102 SECTION DATA P ALL A201 ENVIRONMENT A202 GEOMETRY A203 SURFACE PAVD A204 BASE/SUBGRADE 1 8 A205 STRENGTH PARAMETERS A206 CONDITION A209 HISTORY A210 END LINK A211 LINK IRI7POOR CONDITION 1 A101 SECTION A102 SECTION DATA P ALL A201 ENVIRONMENT A202 GEOMETRY A203 SURFACE PAVD A204 BASE/SUBGRADE 1 8 A205 STRENGTH PARAMETERS A206 CONDITION A209 HISTORY A210 END LINK A211 END SERIES A212 The input data files have a fixed format and require strict data entry rules specified by the FORTRAN compiler and the HDM program. The input data files have the following characteristics: The program reserves the first seventy-two characters of each card for data entries and the last eight characters (columns 73 through 80) for comments. Every card starts with an alphanumeric card description that identifies the card. These labels must be in uppercase and placed in a starting column that varies from card to card.

58 The Input Data Facility 39 A line that has an asterisk (*) in the first column is a comment card and is disregarded by the HDM program. Each card contains some input variables that must be placed in fields with predefined sizes and column locations. For example: Input: ENVIRONMENT ~ ~ Column: Integer input variables should be right aligned in the fields reserved to them. For example: HISTORY HISTORY D D Incorrect Correct Real input variables may be positioned anywhere in the field if the period is included; otherwise the real input numbers must be right aligned. Alphanumeric input variables may be placed anywhere in the field. Optional input variables that have a default value supplied by the HDM program may be omitted, with the fields left blank. The sequence and number of cards required in each series are not always the same. They vary depending on the structure, type, and size of the HDM run. This characteristic provides for great flexibility in HDM input data. You can define an unlimited number of traffic characteristics, vehicle characteristics, maintenance standards, and so on, using only a limited number of cards. For example, the card sequences for series E are shown below using four basic cards. Case 1 Case2 Case3 Case n-1 Casen El01 El01 E101 E101 E101 E102 E102 E102 E102 El02 E103 E103 E103 E103 E103 E101 E103 E103 E103 E102 E103 E103 E105 E103 E103 E101 E105 E105 E102 E103 E105 Note: If you do not want to use the Input Data Facility, you can create and edit all the input data files with any text editor or word processor. The Full-Screen Data Entry Forms The Input Data Facility facilitates the creation of the input data files by providing a full-screen data entry form for every card (like the one shown in Figure 4-2). Each of the full-screen data entry forms presents a screen that displays: The card number and card description.

59 40 The Input Data Facility The description of the requested input variables. The range, type, and default values of the input variables. Some useful notes about the input variables. The fields where you should enter your input data. Figure 4-2. Sample Data Entry Form CARD: A CONDITION VARIABLE DESCRIPTION TYPE REQD RANGE DEFLT INPUT DATA r'oo AREA OF ALL CRACKS % REAL 1) 0.00 AREA OF WIDE CRACKS (%) REAL (1). TO AREA RAVELLED(%) REAL (1). TO AREA OF POTHOLES (%) REAL (1).T MEAN RUT DEPTH (mm) REAL (2).T STD. DEV OF RUT DEPTH (mm) REAL (2). T ROUGHNESS Ql REAL (3) 5 TO 150 CONSTRUCTION FAULT CODE INT (4) TO 1 0 Notes: (1) (area of all cracks > ~(area of wide cracks) and (2) (mean rut depth) > ~(standard deviation of rut depth). (3) Rougness is specified in Ql units. Any compatible roughness unit may be used instead provided this is specified in card K1 04 (4) Required if surface type is ST, RSST, CMST or RSAC. 0 for good quality construction and 1 for poor quality construction. When a new card is added, the input data values displayed in the fields vary as follows: If the input variable is optional, the facility displays a blank field and does not check the input range. Either the field should be left blank to accept the default value provided by the HDM program or the input value should be entered right aligned. If the HDM program requires the input variable, the facility displays the minimum possible value and checks the input value to see if it is within the allowable range. Exception 1: For roughness, the program displays a blank field and does not check the range because the HDM program allows you to use any roughness unit with its own permissible range. All roughness values must be right aligned in the field. Exception 2: For all variables of series D, the program displays blank fields and does not check the range because the number of vehicle types can be changed for different runs within one HDM application. All input values must be right aligned. If the input variable is alphanumeric, the facility displays a blank field. The data may be entered anywhere in the field. Note: The number of decimal places of a real input variable is assigned by the Input Data Facility based on the possible input range and magnitude of the input variable. If it is necessary to overwrite this default to enter smaller or larger numbers, the free-fomt edit option of the cards editor should be used. For example: Variable range Default decimal places Use free-fomt edit option to enter O.Oto

60 The Input Data Facility 41 The Cards Editor The cards editor is a line-oriented editor that allows you to create and edit the HOM input data ftles, deciding which cards you should include in the file and in what order. The cards editor displays a screen divided into three parts: the menu at the top, the area in the middle where the program displays the input data, and the area at the bottom where the program displays messages and collects information. Table 4-1 describes the card manipulation options available to you and a sample cards editor menu screen is shown in Figure 4-3. Table 4-1. Cards Editor Options Option Add Insert Delete Next 14 Prev 14 View Write Read Save Edit Utilities Quit Description Add a card to the end of the file Insert a card in the file Delete a card Display next cards Display previous cards View a card against a ruler Write a block of cards to a file Append a block of cards from a file Save the current file Edit a card Use some DOS commands Exit the cards editor option Figure 4-3. A Sample Cards Editor Menu Press F1 for Help Add Write LINE Insert Read 1 LINK AC01GOOD 2 SECTION 3 SECTION DATA P 4 ENVIRONMENT 5 GEOMETRY 6 SURFACE PAVD 7 BASE/SUBGRADE Delete Save CONDITION ALL Lines: Next 14 Edit File: TESTAAA.TXT Prev 14 Utilities View Quit Use one of the arrow keys or press the highlighted letter

61 42 The Input Data Facility The Automatic Card Generator The automatic card generator is an option that creates all the files needed to run the HDM program by using a predefined card sequence that contains all the cards needed for the run. After a card sequence is selected, the program displays the full-screen data entry forms and requests inputs for all cards in that sequence, one after the other. After all the data for the cards in the sequence have been entered, the program generates the files needed to run the HDM program (See Figure 4-4). Figure 4-4. The Automatic Card Generator Select a predefined card sequence such as: The automatic card generator will display: Entry screen for card KlOl Entry screen for card K102 KlOl K102 AlOl A102 Entry screen for card AlOl Entry screen for card A102 G108 G108 Entry screen for card G108 Before using the automatic card generator, it is necessary to create and define the card sequences to be used. Up to nine card sequences may be defined at a time. The Run Control File Editor The run control ftle editor is an option that provides a facility for creating and modifying the run control ftles needed by the HDM program. The Run Control File contains the names of the eight input data ftles and the names of the seven output files created by the HDM run. The Help Screens Help is available in the main menu, cards editor menu, and the automatic card generator menu. To obtain help while in the main menu or the automatic card generator menu, press the Fl key. To obtain help in the cards editor menu, press the F1 key and then the highlighted letter of the option on which you need help.

62 ChapterS Using the Input Data Facility This chapter provides instructions on the Input Data Facility using a demonstration run. The Procedural Steps Use of the Input Data Facility requires the following steps. Setting up the work area. Running the Input Data Facility. Using the cards editor or the automatic card generator or the run control file editor. Setting Up the Work Area The first step in using the Input Data Facility involves setting up a directory on the hard disk to store the files needed for running the HOM program (see Chapter 1 for procedures to set up a work area directory). For the demonstration run, use the HDMDEMO directory. For a new HOM application you will need to set up a new directory using a directory name of your choice. Running the Input Data Facility The Input Data Facility program is located on the hard disk in the HOM directory under the name HDMINPUT.EXE. To run the Input Data Facility from your work area directory, execute the RUNINPUT batch file which loads the program and directs all the files that you create or modify to your work area directory (see Figure 5-1). Figure 5-1. Running the Input Data Facility HOM directory Your work area directory HDMINPUT.EXE and other required program files. RUNINPUT.BAT andyourhdm input files. 43

63 44 Using the Input Data Facility To run the Input Data Facility, follow the steps below. 1. Change directory to your work area directory with the command: C > CD\HDMDEMO where HDMDEMO is the work area directory for the demonstration run. Note: For your own application replace the name HDMDEMO with the name of your work area directory. 2. Run the RUNINPUT batch ftle with the command: C>RUNINPUT The program displays the initial logo and requests the work area directory (see Figure 5-2). Figure 5-2. Input Data Facility Logo HIGHWAY DESIGN AND MAINTENANCE STANDARDS MODEL INPUT DATA FACILITY 2.9 THE WORLD BANK Enter your work area disk and directory: ExaMples: C:\HDMDEMO\ A:\ C:\HDM\DATA\ Note: The Input Data Facility requires 640 Kb of memory. Before using the facility, remove any resident program that is loaded in the computer. 3. Enter the path of your work area directory. For example: C:\HDMDEMO\ where C:\HDMDEMO\ is the path of the work area directory. Note: Enter the complete path of your work area directory. The Input Data Facility creates and modifies data files in this specified directory and returns to this directory when you exit the facility. The program will keep prompting you for a valid directory name until you provide the co"ect name of your work area directory. The program will then display the main menu shown in Figure 5-3.

64 Using the Input Data Facility 45 Figure 5-3. Input Data Facility Maio Menu HOM INPUT DATA FACIUTY MAIN MENU 1. Use the cards editor 2. Use the automatic card generator 3. Use the run control file editor 4. Exit the program Please use the j or the j key to select an item Press the F1 key for he-'-ip -' Using the Cards Editor To use the cards editor, select Option 1 on the main menu and the program responds with the following message: Please enter the name of the file you want to create or modify in directory C:\HDMDEMO\ Note that the program displays the directory where all the input files will be stored. If an extension is not specified, the program appends an extension.txt to the filename. For the demonstration run, create an input file for series E. Enter the following as the name of the file you want to create: TESTEEEE The program responds with the following message: File TESTEEEE.TXT not found in directory C:\HDMDEMO\ Create a new one (YIN)? If you answer (N)o to this question, the program returns to the main menu. If you answer (Y)es, the program creates a new file named TESTEEEE.TXT and displays the cards editor menu screen (Figure 5-4). If a ftle named TESTEEEE.TXT exists in the directory C:\HDMDEMO\, the program will display the following message indicating that the ftle is ready for new cards to be added to it. File TESTEEEE.TXT already exists. New cards will be appended to this file.

65 46 Using the Input Data Facility Press Y and the program displays the cards editor menu shown in Figure 5-4. Figure 5-4. Cards Editor Menu Press Fl for Help Lines: 0 File : TESTEEEE.TXT Add Insert Delete Next t4 Prev 14 View Write Read Save Edit Utilities Quit UNE Use one of the arrow keys or press the highl"tghted letter The Add Option To add new cards to the file, press the A key or highlight the Add option with the Arrow keys and press the Enter key. After you select the Add option, the program prompts you to specify the card number of the new card you want to add with the following message: Enter the Card Number or <ENTER> to go back to the menu. If you do not remember a card number, enter a letter from A to K and the program will display all the card numbers available in the corresponding HDM series. For the demonstration run, enter ElOl as the card number and the program displays the corresponding full-screen data entry form shown in Figure 5-5. Figure 5-5. Traffic Data Entry Screen CARD: E101 TRAFFIC VARIABLE DESCRIPTION TYPE REQD RANGE DEFLT INPUT DATA ~FFIC ID CODE (2) ALPH I I REO RAFFICTYPE ALPH REO I TRF1 N Notes: 1. One traffic card is required for each traffic set 2. Traffic ID code : N-Normal, G-Generated

66 Using the Input Data Facility 47 Enter the Traffic ID code TRFl and the traffic type N, and the program again displays the message requesting a card number. Enter E102 as the card number and the program displays the screen in Figure 5-6. Figure 5-6. Description Data Entry Form CARD: E102 - DESCRIPT VARIABLE DESCRIPTION TYPE REOD RANGE DEFLT INPUTDATA Pescription of traffic set ALPH OPT TRAFFIC ONE Notes: (1) Description chosen by user for reporting purposes. Enter TRAFFIC ONE as the description of traffic set and E103 as the next card number to go to the screen in Figure 5-7. Figure 5-7. New ADT Data Entry Form CARD: E103 --NEW ADT VARIABLE DESCRIPTION TYPE REOD RANGE DEFLT INPUT DATA STARTING YEAR (NORMAL) STARTING YEAR (GENERATED) TRAFFIC GROWTH TRAFFIC GROWTH -GROUP! TRAFFIC GROWTH -GROUP2 TRAFFIC GROWTH -GROUP3 TRAFFIC GROWTH -GROUP4 TRAFFIC GROWTH -GROUP5 TRAFFIC GROWTH -GROUPS TRAFFIC GROWTH -GROUP? TRAFFIC GROWTH -GROUPS TRAFFIC GROWTH -GROUPS INT INT INT REAL REAL REAL REAL REAL REAL REAL REAL REAL REO 1900TO (1) (2) 1T030 REQ (3) REO REO REO REO REO REQ REO REO REO Notes: (1) Calendar year. Required for Normal traffic only. (2) Relative year. Required for Generated traffic only. (3) Types of annual traffic growth: 1- Fixed amount (vehld), 2-Annual increment 3-Annual percentage (%/y), 4-% of normal traffic Enter the input values shown in Figure 5-7 and note that, for this example, you should leave blank the field for STARTING YEAR (GENERATED) and right align the traffic growth values in the fields. If you enter an out of range value for a required variable, the program displays the correct range at the top of the screen. Press the space bar and enter a valid value. Note: Every time you enter an out of range value for a required variable the program displays the co"ect range at the top of the screen. Press the space bar to continue.

67 48 Using the Input Data Facility For the next card enter E104 and a message "END TRAFFIC card inserted" will be displayed on the screen. This card does not require any variable data to be entered. Press any key to add this card to the file. When prompted for a new card number, press the Enter key to return to the cards editor menu screen as shown in Figure 5-8. Figure 5-8. Cards Editor Menu with Input Data Press F1 for Help Unes: 4 File : TESTEEEE.lXT Add Insert Delete Next 14 Prev 14 Vi- Write Read Save Ed~ Utilities aun LINE 1 TRAFFIC TRF1 N 2 DESCRIPTTRAFFIC ONE 3 NEWADT END TRAFFIC Use one of the arrow keys or press the highlighted letter The Insert Option To insert a new card between other cards, select the Insert option, which displays the following message. Enter the line number BEFORE which the new card will be inserted or 0 to go back to the menu. If you change your mind, enter zero to go back to the cards editor menu screen. After you enter a greater-than-zero line number before which the new card will be inserted, the program requests the new card number. "' For the demonstration run, enter 4 to insert a new card before line 4. When prompted for the card number, enter the letter E and the program will display all card numbers in series E. Press any key to continue and enter EOOl as the card number when the program prompts for a new card number. The program will display the comment screen as shown in Figure 5-9. Note: All card numbers that end with 001 are comment cards and are disregarded by the HDM program....

68 Using the Input Data Facility 49 Figure 5-9. Comment Screen CARD: E001 - COMMENT VARIABLE DESCRIPTION COMMENT: TYPE IN YOUR COMMENT AS I HAVE TYPED IN MINE Enter any comment that you want. Press the Enter key when requested for a new card number and you will return to the cards editor menu screen as shown in Figure Figure Cards Editor Menu with Comment Card Press F1 for Help Lines: 5 File : TESTEEEE.TXT Add Insert Delete Next 14 Prev 14 View Write Read Save EdH Utilities Quit LiNE 1 TRAFFIC TRF1 N 2 DESCRIPTTRAFFIC ONE 3 NEWADT *TYPE IN YOUR COMMENT AS I HAVE TYPED IN MINE 5 END TRAFFIC Use one of the arrow keys or press the highlighted letter The Edit Option To edit a card using the same full-screen data entry form used in the Add or Insert options, select the Edit option, which prompts you with the following message: Enter the line number to edit or 0 to return to menu. If you change your mind, enter zero to return to the cards editor menu screen. After you enter a greater-than-zero line number, the program displays the same full-entry screen used with the

69 50 Using the Input Data Facility Add option but it now displays the input data values of the line being edited. Note that if you: enter a line number greater than the maximum number of lines in the file, the program displays an error message at the top of the screen. In that case, press the space bar and enter a correct value. For the demonstration run, edit line 1 to replace the traffic ID code from TRF1 to TLOW. The View Option The View option has two functions: 1. To check the placement of the input variables. All the input variables should be placed in the predefined column locations described in the HDM-III User's Manual. The HDM program will not execute the modelling and evaluation phase if any input variable is placed incorrectly. The View option allows you to check the placement of the input variables by viewing each card against a ruler. 2. To edit cards using free-form lines. This function allows you to edit a card that has an input variable placed in an incorrect column location or to change the default number of decimal places in a real input variable as assigned by the Input Data Facility based on the possible input range and magnitude of the input variable. In some cases, you will need to overwrite these defaults to enter smaller or larger numbers. For the demonstration run, select the View option, which prompts you to enter the line number to be viewed. Enter line number 3. The program displays a ruler, and the line you want to view and asks if you want to edit this line (see Figure 5-11). Figure View Prompt,.. t NEW ADT Would you like to ed~ this card (Y/N)? N Enter (Y)es and the program presents the line to edit in a free-form format as shown in Figure 5-12.

70 Using the Input Data Facility 51 Figure Edit Line Screen NEW ADT NEWADT Would you like to edit this card (YIN)? N You can now edit this line using the Arrow, Del, Ins and Backspace keys. When you edit a variable make sure you do not move the other variables out of place. The Delete Option To delete a line or a group of lines, select the Delete option, which prompts you to specify the lines to delete with the following message: Enter the range of lines to DELETE or 0 to 0 to return to the menu. Delete from line 0 to 0 If you change your mind, enter zero for the first and last line numbers to delete. For a group of lines, enter the first line number and the last line number of the range of lines to be deleted. For a single line, enter the same line number as the first and last line number to be deleted. Note: There is no way to recover lines deleted with this option, so be careful. For the demonstration run, delete line 4, the comment card, by entering 4 as the first and last line numbers. The Write Option The Write option is used to export a group of cards to a new file. This option together with the Read option is used to copy groups of cards or to move groups of cards within the file being edited. The Write option requests the name of the file to which the group of cards and the range of lines are to be exported as shown below. Enter the name of the file to WRITE data to or press <ENTER > to go back to the menu.

71 52 Using the Input Data Facility You can include in the filename a path or any extension. If you change your mind, press the Enter key to return to the cards editor menu screen. For the demonstration run, enter the file name TESTING and copy lines 1 to 4. The Read Option The Read option imports cards stored in a file and appends them to the end of the file being edited. The Read option requests the name of the file to be imported into the file being edited with the following message: Enter the name of the file to READ data from or press <ENTER> to go back to the menu. You can include in the filename a path or any extension. If you change your mind, press the Enter key to return to the cards editor menu screen. For the demonstration run, read the cards stored in the file TESTING that was just created with the Write option. Repeat this process three times to obtain a total of five copies of the traffic cards entered earlier with the Add and Insert options (see Figure 5-13). Figure Cards Editor Menu Press F1 for Help Lines: 20 File: TESTEEEE.TXT Add Insert Delete Next 14 Prev 14 View Write Read Seve Edit Utilities Quit LINE 1 TRAFFIC TLOW N 2 DESCRIPTTRAFFIC ONE 3 NEW ADT END TRAFFIC 5 TRAFFIC TLOW N 6 DESCRIPTTRAFFIC ONE 7 NEW ADT END TRAFFIC 9 TRAFFIC TLOW N 10 DESCRIPTTRAFFIC ONE 11 NEW ADT END TRAFFIC 13 TRAFFIC TLOW N 14 DESCRIPTTRAFFIC ONE ''" Use one of the arrow keys or press the highlighted letter The Next 14 and Previous 14 Options The first line of the cards editor menu screen displays the name of the file being edited and the total number of lines in the file. The number of lines are incremented whenever a new line is added to the current file. In the demonstration run, the current number of lines, after using the Read option four times, is twenty. To display the next fourteen lines in a file, select the Next 14 option; to display the previous fourteen lines, select the Prev 14 option. If you want to scroll one line at a time, use the + and - keys repeatedly until you get to the end or top of the file. Table 5-llists the keys that may be used to move around in the file.

72 Using the Input Data Facility 53 Table 5-1. Keys and Their Functions Key PgUp PgDn + Home End Function Displays the next fourteen lines Displays the previous fourteen lines Scrolls one line down Scrolls one line up Goes to the top of the file Goes to the bottom of the file For the demonstration run, display lines 15 through 20 with the Next 14 option and return to lines 1 through 14 by pressing the PgUp key or the Home key. The file being edited has five sets of the same traffic cards in the file. This is not necessary for the demonstration run, but you could now edit this file to obtain five different traffic sets. For example, you could use the edit command to make the following changes to the file: Line Change To 5 TLOW TMED 7 5,10,15,20 50,60,70,100 9 TLOW THIG 11 5,10,15,20 150,200,300, TLOW TVHI 15 5,10,15,20 400,500,130, TLOW TVVH 19 5,10,15, ,500,700,1000 The program would display the cards editor menu, as shown in Figure To complete this series, add the E105 (END SERIES) card to the end of the file. Figure Cards Editor Menu Press F1 lor Help Lines: 20 File : TESTEEEE.TXT Add Insert Delete Next 14 Prev 14 View Write Read Save Edit Utilities Quit UNE 1 TRAFFIC TLOW N 2 DESCRIPTTRAFFIC ONE 3 NEW ADT END TRAFFIC 5 TRAFFIC TMED N 6 DESCRIPTTRAFFIC ONE 7 NEW ADT END TRAFFIC 9 TRAFFIC THIG N 10 DESCRIPTTRAFFIC ONE 11 NEW ADT END TRAFFIC 13 TRAFFIC TVHI N 14 DESCRIPTTRAFFIC ONE Use one of the arrow keys or press the highlighted letter

73 54 Using the Input Data Facility The Save Option To save the file being edited, select the Save option, which asks you to confirm the name of the file where your data will be stored with the following message. Save file as C:\HDMDEMO\TESTEEEE.TXT To confirm that the file should be saved under the name displayed, press the Enter key. If you want to save the data under a new filename, enter the new name in the field. The new filename must include a path and the extension. After the file is saved, the program asks if you want to edit a new file or continue to edit the current file with the following message. Do you want to create or modify a new data file (YIN)? If you answer (N)o, the program returns to the cards editor menu screen and you can continue to edit the file. If you answer (Y)es, the program requests the name of the new file to edit with the following message and returns to the cards editor menu screen. Please enter the name of the file you want to create or modify For the demonstration run, save the file using the name displayed by the program (C:\HDMDEMO\TESTEEEE.TXT) and answer (N)o to the create or modify a new data file prompt. Note: Remember that you have to create a separate file for each HDM series. The Utilities Option The Utilities option allows you to execute some common DOS commands without having to leave the cards editor. If you select this option, the facility presents the menu shown in Figure To execute any command, use the arrow keys or press the highlighted letter. For each option, the program requests the parameters required by the DOS commands that are listed in Table 5-2. You must include the complete path for all the filenames because the program's default directory is C:\HDM\ while the Input Data Facility is running, and your files are in your work area directory, in this case C:\HDMDEMO\.

74 Using the Input Data Facility 55 Figure DOS Utilities Menu DOS UTILITIES Copy Erase Rename Dir Print Table 5-2. DOS Command Parameters Command Parameters Example Copy File to copy C:\HDMDEMO\ TESTEEEE.TXT Destination A:\ Erase File to erase C:\HDMDEMO\ TESTEEEE.TXT Rename File to rename C:\HDMDEMO\ TESTEEEE.TXT New name C:\HDMDEMO\SAMPLEEE.TXT Dir Directory to list C:\HDMDEMO\ Print File to print C:\HDMDEMO\ TESTEEEE.TXT The Help Option To get help, while in the cards editor menu screen, press the Fl key and the screen shown in Figure 5-16 will appear. To get help on a particular option, use the arrows or press the highlighted letter. To return to the cards editor menu screen, press the F1 key again or select the Quit option. For the sample run, press the letter A to get the help screen for the Add option (see Figure 5-17). Return to the menu by pressing the F1 key.

75 56 Using the Input Data Facility Figure Cards Editor Help Screen Press F1 to exn Help Unes: 20 File : TESTEEEE.TXT Add Insert Delete Next 14 Prev 14 View I Wrne Read Save Edit Utilities Quit Use any of the arrow keys or press the highlighted letter to get specific help Use one of the arrow keys or press the highlighted letter Figure Add Option Help Screen Press F1 to exit Help Lines: 20 File : TESTEEEE.TXT Add Insert Delete Next 14 Prev 14 View Write Read Save Edit Utilities Quit The line Add option is used to add new lines to the file. The new lines are appended to the end of the file. In this option you are requested to enter the card number for the new line. W the card number is found, a data entry screen will be displayed where you should enter the requested information. To ex~ this option just press < ENTER > when requested for a card number. For a list and description of all cards available refer to the HOM manual. Press any key to continue Use one of the arrow keys or press the highlighted letter...

76 Using the Input Data Facility 57 The Quit Option To return to the main menu, select the Quit option, which asks if you want to save the file being edited with the following message. Do you want to save your data (YIN)? If you answer (Y)es, the program asks you to confirm the name of the file where your data will be stored with the following message. Save flle as C:\HDMDEMO\TESTEEEE.TXT To confirm that the flle should be saved under the name displayed, press the Enter key. If you want to save the document under a new fllename, enter the new name in the field. The new fllename must include a path and the extension. If you answer (N)o, the program asks if you want to edit a new file with the following message. Do you want to create or modify a new data file (YIN)? If you answer (N)o, the program returns to the main menu. If you answer (Y)es, the program requests the name of the new file to edit and returns to the cards editor menu screen. For the demonstration run, select the Quit option and answer (N)o to the two questions. This will take you to the main menu and to the end of the cards editor demonstration. Using the Automatic Card Generator The second option of the Input Data Facility is the automatic card generator, which uses the same full-screen data entry forms used in the cards editor. The cards editor option allows you to create the required HDM input data files by asking the card number for each new line to be added to the flle and displaying the corresponding full-screen data entry form. The sequence of cards in each series is not necessarily the same for every HDM run. it depends on the structure, size, and type of the run, so you have to decide what cards to include in each series and in what order. Note: The automatic card generator should be used by experienced users. Beginners may skip this section and proceed directly to the section titled "Using the Run Control File Editor." The automatic card generator allows you to enter a complete sequence of cards one after another without having to worry about the card numbers to include because it uses predefined card sequences. This can be very helpful if you want to repeat a sequence of cards in different exercises.

77 58 Using the Input Data Facility The automatic card generator displays the first card of a predefined sequence of cards; when you finish entering the required information for this card, it displays the second card, and soon. To use the automatic card generator, follow these steps: 1. Create the card sequences to use. Decide what cards to use and in what order, and store this information in ftles called "card sequence ftles." 2. Defme the card sequences. Identify to the program the predefined card sequence ftles you created. You can define up to nine card sequences at a time, giving the description of the sequences and the names of the card sequence files. 3. Use a predefmed card sequence. Select one of the predefined card sequences available and enter the required information for all cards in that sequence. The program will then create all the necessary files to run the HDM program. Creating the Card Sequences to Use The card sequences required by the automatic card generator are stored in ASCII text files in two possible forms: 1. With one card number per line positioned in columns 1 through 5. Columns 6 through 80 should be left blank. 2. With one card number per line positioned in columns 73 through 77. Columns 1 through 72 can contain any text. Note that this is the format of the files created by the cards editor. Figure 5-18 depicts the card sequence files. Figure Card Sequence Files Option 1 Columns 1-5 Option 2 Columns K101 K102 A101 A102 SOME TEXT KlOl K102 AlOl Al02 G108 G108 The HDM program requires eight input data files (one file each for series A, B, C, D, E, F, K and one ftle for series G, H, I, J). If you are using the cards editor, create these ftles one-byone using a different name for each file. The automatic card generator creates from one to eight series files, depending on what cards are present in the predefined card sequence ftles. For example, if the card sequence file contains cards for every series, the automatic card generator creates the eight required ftles; if it contains only cards for series E, the program creates only the ftle for series E.

78 Using the Input Data Facility 59 To create the card sequence files, you can use either a text editor capable of creating ASCII ftles or the cards editor of the Input Data Facility. With a text editor, enter one card per line and position the card numbers starting at column 1 (see Figure 5-19). You can create as many files as you want, the files can have any name, and they can be stored in any directory of your hard disk. Figure Card Sequence Files with a Text Editor, Column 1 I K101 K102 B102 B104 With the cards editor, you do not need to enter any data in the input fields because you are interested only in the card numbers that are stored in columns 73 through 77 (see Figure 5-20). The card sequence file can have cards for one series or for two or more series. Figure Card Sequence Created with the Cards Editor TEXT TEXT TEXT Column 73 I K109 A209 B308 If you have already created some HDM input data files with the cards editor, you can use them as card sequence files because they contain the card numbers in columns 73 through 77. You can use these files individually or merge them (using the Read option) into one file that contains the card sequences for all series. If you use this merged file, the automatic card generator displays the cards for all series and creates the required input files for all series at one time (see Figure 5-21). Figure Merging the Input Files Your previously used input files Card sequence file for the automatic generator Series K Series A Series K Series A Series B Series B

79 60 Using the Input Data Facility Defining the Card Sequences After creating the card sequence files, you must define them to the program. To define the card sequences use the second option on the automatic card generator menu (see Figure 5-22). Figure Automatic Card Generator Menu AUTOMATIC CARD GENERATOR MAIN MENU 1. Use a predefined card sequence 2. Define the card sequences 0.. Exit to main menu Please use the j or the t key to select an item Press the F1 key for help When you select this option, the program presents you with a list of the sequences that have already been defined (see Figure 5-23). Figure Screen Showing Predefined Card Sequences DEFINE THE CARD SEQUENCES SEQUENCE NAME 1. All HOM cards 2. Link deterioration without maintenance 3. Link with four maintenance alternatives 4. Three links with four alternatives 5. Paving of gravel road CARD SEQUENCE FILE c:\hdm\cardseq1.txt c:\hdm\cardseq2.txt c:\hdm\cardseq3.txt c:\hdm\cardseq4.txt c:\hdm\cardseq5.txt Enter or edh the set names and the card sequence files using the arrows to move from sequence to sequence, and press the PgDn key to exit. For each card sequence file that you have previously created and want to use in the automatic card generator, you must define the following: The sequence name (a forty-character description of the sequence). The card sequences file (the name of the file where the card sequences are stored). This filename must include the complete path and extension.

80 Using the Input Data Facility 61 You can defme up to nine card sequences at a time. They are stored in the program's memory until modified later on. To modify any of the current settings, type over the previous setting and use the Backspace and Del key to delete any extra characters. To move from one sequence to the other use the Up and Down arrows, and to exit press the PgDn key (see Table 5-3.). Table 5-3. Keys and their Functions Key Del Backspace Insert Left arrow Right arrow Uparrow Down arrow PgDnkey Function Delete a single character Delete the previous character Insert/overwrite mode Move one character to the left Move one character to the right Move one field up Move one field down Exit After you press the PgDn key, the program stores all the definitions and returns to the automatic card generator main menu. The five predefmed card sequences listed in Figure 5-23 are supplied with the HDM program and are stored in the C:\HDM directory. Sequence 1 is simply a list of all possible cards required by the HDM program. These cards follow the sequence outlined in the User's Manual (HDM-111, Volume 2). The other four sequences represent real applications of the HDM program and should be helpful in understanding the different card sequences required for these particular applications. For the demonstration run, you will define a sixth sequence, using the file TESTEEEE.TXT (that you created with the cards editor), as a card sequence file. Select Option 2 in the automatic card generator menu and enter as the sixth sequence name "This is just a try" and as the sixth card sequence file c:\hdmdemo\testeeee.txt (see Figure 5-24). Figure Defining the Card Sequences DEFINE THE CARD SEQUENCES SEQUENCE NAME 1. All HOM cards 2. Link deterioration without maintenance 3. Link with four maintenance alternatives 4. Three links with four a~ernatives 5. Paving of gravel road 6. This is just a try CARD SEQUENCE FILE c:\hdm\cardseq1.txt c:\hdm\cardseq2.txt c:\hdm\cardseq3.txt c:\hdm\cardseq4.txt c:\hdm\cardseq5.txt c: \ hdmdemo \ testeeee.txt Enter or edit the set names and the card sequence files using the arrows to move from sequence to sequence, and press the PgDn key to exit.

81 62 Using the Input Data Facility Remember to include the complete path and extension of the card sequence file. Press the PgDn key and you should be back to the automatic card generator menu. Using a Predefined Card Sequence After creating the card sequences files and defining them, you are ready to use the automatic card generator. To use a predefined card sequence, select Option 1 in the automatic card generator main menu and the program displays the sequences available as shown in Figure Figure Using a Predefined Card Sequence Card Sequences: 1. All HOM cards 2. Unk deterioration without maintenance 3. Unk with four maintenance anernatlves 4. Three links with four anernatlves 5. Paving of gravel road 6. This Is just a try Exit to main menu Please select one of the choices. 2 Choose the sequence to use by selecting the appropriate number from the menu and the program displays the following message. Please enter the file pattern name to store your data in directory C:\HDMDEMO\ Use a maximum of seven characters. The automatic card generator creates two types of files: 1. One to eight files for the HDM series. 2. The Run Control File for the HDM run. The program stores these files using different names but the same file pattern. The file pattern is a seven-character-maximum name that is common to all the files created by the automatic card generator. For example, if you enter TEST as a file pattern the program creates the following files: TESTA. TXT TESTB.TXT TESTC.TXT TESTD.TXT TESTE.TXT TESTF.TXT TESTG.TXT

82 Using the Input Data Facility 63 TESTK.TXT and TESTR.TXT Note: Files TESTA. TXT to TESTK TXT are created only if there is at least one card for the corresponding series and TESTG. TXT stores cards for series G, H, I, and J. The format of the generated Run Control File is as shown in Figure Figure Run Control File XXXXK.TXT XXXXA.TXT XXXXB.TXT XXXXC.TXT XXXXD.TXT XXXXE.TXT XXXXF.TXT XXXXG.TXT SCAN LOUT SCAN2.0UT SCAN3.0UT SCAN4.0UT INPUT.OUT RESULTS.OUT EBMDATA.OUT Where XXXX is the file pattern For the demonstration run, select the second card sequence (Link deterioration without maintenance) and enter TEST as the file pattern. After you enter the file pattern to store your data, the program displays the first card of the sequence where you enter the required data. When you are finished, the program displays the second card in sequence, and so on. When you finish all the cards in the sequence, the program creates the necessary files and returns to the automatic card generator menu. For the sample run, enter the required data for a few cards in the sequence. Note that you cannot go backwards in the sequence. The number of cards in a sequence is, in most cases, large, so there is a way to halt the process and resume the data input at a later time. If you are in the middle of a sequence and you want to halt the program, press the Esc key. The program displays the following message: Do you wish to halt now (Y /N)?. If you answer (N)o, the program returns to the sequence. If you answer (Y)es, the program displays the following message and returns to the automatic card generator menu. All cards have been saved in file C:\HDMDEMO\TEST.TXT You may continue where you left off by providing the same file pattern when requested.

83 64 Using the Input Data Facility For the demonstration run, answer (Y)es. To continue with the sequence at a later time, select the same card sequence from the available sequences and give the same file pattern. The program displays the following message. File C:\HDMDEMO\TEST.TXTexists already. Do you wish to continue where you left off last time (Y /N)? If you answer (Y)es, you will be back to the last card you entered in the sequence. If you answer (N)o, you will start the sequence from the first card. When you halt a sequence, all your data is stored temporarily in a file named XXXX.TXT, where XXXX is the file pattern. When you finish with the sequence, this file is deleted. For the demonstration run, select again the second card sequence on the "Use a Predefined Card Sequence" menu and enter TEST as the file pattern to go back to the sequence you just left. Complete the sequence of cards and the program generates all the files needed to run the HDM program. In this case the facility creates all the eight series files because there are cards for all series in the sequence file. Note: If you want to continue with a sequence after halting the program, you must finish with the halted sequence first before starting a new sequence. Using the Run Control File Editor The third option of the Input Data Facility is the run control file editor. The run control file editor allows you to create and modify the Run Control Files needed by the HDM program. To use the run control file editor, select Option 3 in the main menu and the program displays the following message. Please enter the name of the Run Control File you want to create or modify in directory C:\HDMDEMO\ You may include a file extension. Enter MYTRY as the name of the file you want to edit and the program displays the following message if the file is not found. File MYTRY.TXT not found in directory C:\HDMDEMO\ Create a new one (YIN)? If you answer (N)o, the program returns to the main menu. If you answer (Y)es, the program displays the screen in Figure Since this is a new file, all the fields for the field names are blank. Enter the filenames for the files that contain the input data for each series and the files that will store the results. You should include the complete path and extension for all files.

84 Using the Input Data Facility 65 Figure The Run Control File Edit Screen RUN CONTROL FILE EDITOR File: C:\HDMDEMO\MYTRY.TXT File Type Series K Series A Series 8 SeriesC Series D Series E Series F Series G,H,I,J Scant Scan2 Scan3 Scan4 Echo print Reports EBM Input Filename Enter or edit the filenames using the arrows to move from file to file and press the PgDn key to ekil. To move from one filename to the other use the Up and Down keys and press the PgDn key to exit. (Refer to Table 5-3 for other keys you can use to manipulate the filenames.) After you press the PgDn key, the program asks you to confirm if you want to save the file with the original name. If you want to change the name, replace the old name with the new name, remembering to include the complete path and extension. After saving the file, the program returns to the main menu and the Run Control File is ready to be used by the HDM program. To modify an old Run Control File, enter the name of the Run Control File and the program brings back the file to be edited.

85

86 Chapter6 An HDM Application This chapter presents a complete application of the HOM program from problem definition to the analysis of the results in Lotus It also serves as a tutorial for the beginner HOM user. The Procedural Steps For all HOM applications, follow the steps below: Define the problem. Define the structure of the run. Organize the input data. Create the input data files. Run the HOM program. Analyze the results. Defining the Problem The first step is to define the scope of the HOM application, i.e., the number and types of road links to be evaluated, the traffic parameters, and the construction/maintenance alternatives. The HOM application presented in this chapter pertains to a road network consisting of four representative road classes or links (see Table 6-1). The purpose of the HOM analysis is to simulate the deterioriation of each road class under different maintenance regimes and traffic levels, and to determine the best strategy for each road type/traffic combination. The four road classes are: Paved road in good condition, International Roughness Index (IRI) = 2.0. Paved road in fair condition, IRI = 4.0. Paved road in poor condition, IRI = 7.0. Gravel road. 67

87 68 An HOM Application Table 6-1. Study Design for HDM Application Traffic level Road class Low Medium High Paved road At.. A*.. An At..A*.. An At.. A*.. An (good condition) Paved road At.. A*.. An At.. A*.. An At..A*.. An (fair condition) Paved road At.. A*.. An At..A*.. An At..A*.. An (poor condition) Gravel road At.. A*.. An At.. A*.. An At.. A*.. An Where A denotes strategy alternatives and A* is the best alternative for each road type/traffic combination. The traffic levels expressed as average daily traffic (ADT) are: Low volume for paved road, 100 for gravel road. Medium volume for paved road, 200 for gravel road. High volume for paved road, 400 for gravel road. The vehicle fleet is composed of: Small cars. Large cars. Pickups. Trucks. Truck-trailers. The strategy alternatives for paved roads are: Do nothing. Patch 100 percent of the potholes. Patch and reseal when the damaged pavement area exceeds 30 percent. Patch and overlay when roughness exceeds 4.0 IRI. Note: Including the ''Do-nothing" altemative, t!ze road is reconstrncted whenever roughness exceeds an IRI of 9. 0; basic routine maintenance (drain clearing, vegetation control, shoulder maintenance, etc.) is common to all altematives.

88 An HOM Application 69 The strategy alternatives for the gravel road are: Do nothing. Spot regravel equivalent to 30 percent of annual material loss. Resurface when gravel thickness falls below 50 rom. Pave the gravel road in 1990 followed by the maintenance alternative requiring 100 percent patching of potholes. Note: Except for the "Do-nothing" alternative, the gravel road is bladed once every 188 days; basic routine maintenance is common to all alternatives. Defming the Structure of the Run The structure of the HDM run is defined by: The location of the input and output files. The number ofhdm runs required. The filenames of the input data and output files. The required identification codes. The desired comparisons of alternatives and reports requested. Location of the Input and Output Files All the input data files and output files will be stored in a hard disk directory called HDMTUTOR. RequiredNumberofHDM Runs HDM runs can be structured in a number of ways ranging from one global run for all road classes, traffic levels, and maintenance alternatives to single runs for each combination of road class, traffic level, and maintenance alternative. For this analysis the HDM runs have been stratified by traffic level, that is, three HDM runs would be required as shown in Table 6-2. Table 6-2. Defining the Runs RUN1 Low traffic Good paved road Fair paved road Poor paved road Gravel road RUN2 Medium traffic Good paved road Fair paved road Poor paved road Gravel road RUN3 High traffic Good paved road Fair paved road Poor paved road Gravel road Alternatively the analysis could be carried out with twelve HDM runs, one for each road/traffic combination or only one run for all road and traffic classes.

89 70 An HOM Application Filenames ofthe Input Data and Output Files For each HDM run in this application, use the files listed in Table 6-3. Table 6-3. Files Needed for the HDM Application File type RUNl RUN2 RUN3 Run Control TUTORUNl.TXT TUTORUN2.TXT TUTORUN3.TXT Series K TUTORKl.TXT TUTORK2.TXT TUTORK3.TXT Series A TUTORA.TXT TUTORA.TXT TUTORA.TXT Series B TUTORB.TXT TUTORB.TXT TUTORB.TXT Series C TUTOR C. TXT TUTOR C. TXT TUTOR C. TXT Series D TUTORD.TXT TUTORD.TXT TUTORD.TXT Series E TUTORE.TXT TUTORE.TXT TUTORE.TXT Series F TUTORF.TXT TUTORF.TXT TUTORF.TXT Series GHIJ TUTORGl.TXT TUTORG2.TXT TUTORG3.TXT Scanl SCAN LOUT SCAN LOUT SCAN LOUT Scan2 SCAN2.0UT SCAN2.0UT SCAN2.0UT Scan3 SCAN3.0UT SCAN3.0UT SCAN3.0UT Scan4 SCAN4.0UT SCAN4.0UT SCAN4.0UT Echo print INPUT.OUT INPUT.OUT INPUT.OUT Results RESULTSl.OUT RESULTS2.0UT RESULTS3.0UT Ebminput EBMDATA.OUT EBMDATA.OUT EBMDATA.OUT Note that for the three HDM runs in this application, most of the flles are the same. Different flles are needed for: Run Control File -- to define the different files used in each run. Series K -- to change the name of the run. Series G, H, I, J --to change the traffic level, since the runs are stratified by traffic. Results -- to store the results in different files... Required Identification Codes For each HDM application, use a 4-character identification code for every: Surface type. Link. Construction option. Maintenance standard. Traffic set. Exogenous benefits-costs set.

90 An HOM Application 71 Link alternative. Group alternative. Comparison study. For this application, use two surface types with the following codes: P A VD for paved roads. UP A V for unpaved roads. The remaining codes for each input file are given below: Series A : Existing link characteristics. File= TUTORA.TXT IRI2 - Good paved road IRI4- Fair paved road IRI7 - Poor paved road GRA V- Gravel road Series B : Construction options. File = TUTORB.TXT CNST - Construction of the gravel road Note: In the HDM program, the strategy to pave the gravel road is a constluction option (Series B) and all the other strategies are maintenance alternatives (Series C). Series C : Road maintenance alternatives. File = TUTORC.TXT STPO - "Do-nothing" for paved roads STPl - Patch 100 percent of the potholes STP2 - Reseal at 30 percent of damaged area STP3- Overlay at 4.0 IRI STUO - "Do-nothing" for unpaved roads STUl - Spot regravel equivalent to 30 percent of annual material loss STU2 - Resurface when thickness falls below 50 mm Series E : Traffic volumes. File= TUTORE.TXT PLOW - Low traffic, paved road PMED - Medium traffic, paved road PHIG - High traffic, paved road ULOW - Low traffic, unpaved road UMED - Medium traffic, unpaved road UHIG - High traffic, unpaved road Series F : Exogenous benefits-costs. File = TUTORF.TXT EXBl - Exogenous construction cost of paving the gravel road

91 72 An HDM Application Series G,H,I,J. Listing of link alternatives, group alternatives, reports requests, and comparisons of alternatives. Files= TUTORGl.TXT, TUTORG2.TXT, OR TUTORG3.TXT - Link alternatives: IRI2 ALTO - Good paved road, do nothing IRI2 ALTl- Good paved road, patching IRI2 AL T2 - Good paved road, reseal IRI2 AL T3 - Good paved road, overlay IRI4ALTO- Fair paved road, do nothing IRI4 ALTl- Fair paved road, patching IRI4 ALT2- Fair paved road, reseal IRI4 ALT3- Fair paved road, overlay IRI7 ALTO - Poor paved road, do nothing IRI7 ALTl - Poor paved road, patching IRI7 ALT2 - Poor paved road, reseal IRI7 ALT3- Poor paved road, overlay GRA V ALTO- Gravel road, do nothing GRA V ALTl- Gravel road, spot regravel GRAV ALT2- Gravel road, resurface GRA V ALT3- Gravel road, pave - Group alternatives: GP A V ALTO - Paved roads with maintenance ALTO GPA V ALTl - Paved roads with maintenance AL Tl GPA V ALT2- Paved roads with maintenance ALT2 GPAV ALT3- Paved roads with maintenance ALT3 GUNP ALTO- Gravel roads with maintenance ALTO GUNP ALTl- Gravel roads with maintenance ALTl GUNP ALT2- Gravel roads with maintenance ALT2 GUNP ALT3- Gravel roads with maintenance ALT3 - Comparison of alternatives: BASE- Comparison with alternative ALTO Note that Series A, B, C, D, E, and F store the characteristics of the links, traffic sets, maintenance standards, etc., and that the 4-character codes identify these items. Series G, H, I, and J link the information of the other series using the identification codes to define the structure of the run. Series G, H, I, and J define what traffic corresponds to each link, what maintenance standards are applied to each link, when the maintenance standards are applied, what comparisons to make, and what reports to obtain. For example, the file TUTORGl.TXT defines the link and group alternatives for the low traffic volume run (see Tables 6-4 and 6-5). Comparison of Alternatives and Reports Desired The comparison of alternatives is the evaluation phase of the HDM run. In this application, three possible maintenance alternatives are compared against the "Do-nothing" alternative as shown below: e ALTl vs. ALTO. ALT2vs.ALTO. e ALT3vs.ALTO.

92 An HOM Application 73 Four discount rates are used for these comparisons (discount rates of 0, 6, 12 and 20 percent per annum are used in this application). It is also possible to carry out an incremental analysis by paired comparisons among alternatives 1, 2, and 3. For example: ALT2vs.ALT1. ALT3vs.ALT1. ALT3 vs. ALT2. Table 6-4. Definition of Link Alternatives for RUN 1 Link alternative IRI2ALTO IRI2ALT1 IRI2ALT2 IRI2ALT3 IR14ALTO IRI4ALT1 IRI4ALT2 IRI4ALT3 IRI7 ALTO IR17 ALTl IRI7 ALT2 IRI7 ALT3 GRAY ALTO GRAY ALTl GRAY ALT2 GRAYALT3 Link Traffic Maintenance Construction Exogenous costs IRI2 PLOW STPO IRI2 PLOW STP1 IRI2 PLOW STP2 IRI2 PLOW STP3 IRI4 PLOW STPO IRI4 PLOW STPl IRI4 PLOW STP2 IRI4 PLOW STP3 IRI7 PLOW STPO IRI7 PLOW STPl IRI7 PLOW STP2 IR17 PLOW STP3 GRAY ULOW STUO GRAY ULOW STUl GRAY ULOW STU2 GRAY ULOW STUO CNST EXBl STPl Table 6-5. Definition of Group Alternatives for RUN 1 Group alternative Link alternatives GPAY ALTO GPAY ALTl GPAYALT2 GPAY ALT3 IRI2ALTO IRI2ALT1 IRI2ALT2 IRI2ALT3 IRI4ALTO IRI4ALT1 IRI4ALT2 IR14ALT3 IRI7 ALTO IRI7 ALTl IRI7 ALT2 IRI7 ALT3 GUNP ALTO GUNPALTl GUNPALT2 GUNP ALT3 GRAY ALTO GRAYALTl GRAYALT2 GRAYALT3

93 74 An HDM Application The reports generated for this HOM application are: Traffic in years 1988,2000, and 2007 (IRI2-ALTO and GRAY-ALTO). Vehicle operating costs for paved road in years 1988,2000, and 2007 (IRI2-ALTO). Vehicle operating costs for gravel road in years 1988,2000, and 2007 (GRA V-ALTO). Road condition report for all link alternatives in years 1988 to Economic costs for all link alternatives. Comparison of alternatives. Organizing the Input Data After defining the structure of the run, organize the input data for the following series: Run control information. Existing link characteristics. Construction options and costs. Road maintenance standards and unit costs. Vehicle fleet characteristics and unit costs. Traffic volumes and growth characteristics. Exogenous benefits-costs. Note: The description and requirements of each of these series is given in the HDM-III User's Manual. Review the description of each series, establish the input variables and data requirements, and collect the required data for your HDM application. For this HDM application use the input variables that are listed in Tables 6-6 through Table 6-6. Run Control Information Information Run name Run date Analysis period VOC equations Roughness unit Roughness computation unit Roughness computation intercept Roughness computation slope Currency of input data Curreny of output data Currency exchange rate Input data LOW/MEDIUM/HIGH TRAFFIC 02/20/ Brazil IRI Dollars Dollars 1.0

94 An HOM Application 75 Table 6-7. Existing Link Characteristics Good Fair Poor Gravel Information road road road road Length (km) Average rainfall (m/month) Altitude (m) Rise plus fall (m!km) Horizontal curvature ( deg!km) Carriageway width (m) Shoulder width (m) Surface type (paved roads) AC AC AC Number of new layers Number of old layers Thickness of new layers (mm) Base type Granular Granular Granular Subgrade CBR (%) Structural number Total cracked area(%) Wide cracked area(%) Ravelled area (%) Pothole area(%) Mean rut depth (mm) Rut depth std. deviation (mm) Roughness (IRI) Years from last preventive tmt Years from last resurfacing Years from last construction Gravel surface Maximum particle size (mm) 34 Material passing 2.0 mm sieve (%) 39 Material passing mm sieve(%) 27 Material passing mm sieve (%) 21 Plasiticity index (%) 22 Gravel base/subgrade Maximum particle size (mm) 50 Material passing 2.0 mm sieve (%) 85 Material passing mm sieve(%) 74 Material passing mm sieve (%) 37 Plasiticity index (%) 45 Gravel thickness (mm) 150 Years from last regravelling 0

95 76 An HOM Application Table 6-8. Construction Options and Costs Information Construction period (years) Generated exogenous cost Financial cost ($ million per year) Economic cost ($ million per year) Salvage value(%) Construction characteristics Length (km) Rise plus fall (m!km) Horizontal curvature ( deg!km) Carriageway width ( m) Shoulder width (m) Surface type (paved road) Number of new layers Number of old layers Thickness of new layers (mm) Base type Subgrade CBR (%) Structural number Roughness (IRI) Input data 1 Yes ST Granular Table 6-9. Exogenous Benefits-Costs Information Exogenous construction costs Financial costs ($ million per year) Economic costs ($ million per year) Duration Input data years after construction Note: The exogenous costs in this example refer to slope protection works carried out after paving as a measure to enhance the roadside environment. These works are spread over a period of three years after completion of paving.

96 An HOM Application 77 Table 6-10a. Road Mabtenance Standards and Unit Costs Information Input data Financial Economic Unpaved Grading (per km) Spot regravelling (per cum) Gravel resurfacing (per cu m) Basic routine maintenance (per km/y) Paved Patching (per sq m) Resealing (per sq m) Overlay (per sq m) Pavement reconstruction (per sq m) Basic routine maintenance (per krn!y) Table 6-10b. Maintenance Standards Information Patching Resealing Overlaying Reconstruction Grading Spot regravelling Gravel resurfacing Input data 100 percent of pothholed area Reseal when total damaged area exceeds 30 percent Reseal type = surface treatment, thickness (mm) = 12 Strength coefficient = 0.25 Overlay when roughness exceeds 4.0 IRI Overlay type = asphalt concrete, thickness (mm) = 40 Initial roughness = 2.5 IRI, strength coefficient = 0.4 Reconstruct when roughness exceeds 9.0 IRI Surface type = asphalt concrete, surface layer (mm) = 50 Initial roughness = 2.0 IRI Base type = granular, structural number = 3.9 Grade every 188 days Spot regravel at 30 percent of annual material loss Resurface when gravel thickness falls below 50 mm Increase in thickness (mm) = 150 Maximum particle size (mm) = 55 Material passing 2.0 mm sieve = 40 Material passing mm sieve = 20 Material passing mm sieve = 6.0 Plasticity index (%) = 4

97 78 An HOM Application Table Vehicle Fleet Characteristics and Unit Costs lnpyt data Information Car Pickup L. car Truck Art. truck Vehicle type HPmetric GVW EQXL VAXLES Financial costs ($) Vehicle price Tire cost (per tire) Maintenance labor (per hour) Crew time cost (per hour) Interest (%) Petrol (per liter) Diesel (per liter) Engine oil (per liter) Economic costs ($) Vehicle price Tire cost (per tire) Maintenance labor (per hour) Crew time cost (per hour) Interest (%) Petrol (per liter) Diesel (per liter) Engine oil (per liter) Average km driven (per yr) Average vehicle life (years) Average hours driven (per yr) Table Traffic Volume and Growth Characteristics A~rag~ dail~ traffi~;; Road type -- traffic level Car Pickup L. car Truck Art. truck Total Paved --low Paved -- medium Paved -- high Unpaved --low Unpaved -- medium Unpaved-- high Growth rate increase(%)

98 An HOM Application 79 Creating the Input Data Files After collecting the required data, you can create the input data files. First, set up the work area directory. Setting Up the Work Area Directory All the input data files and output files will be stored in a hard disk directory called HDMTUTOR. To set up this directory, follow the steps below: 1. Create a directory with the command: C > MD\HDMTUTOR 2. Change to the HDMTUTOR directory with the command: C > CD\HDMTUTOR 3. Copy into the HDMTUTOR directory all the run batch files located in the C:\HDM\ directory with the command: C>COPY C:\HDM\RUN*.BAT Note that you should first install the HDM program in the C:\HDM\ directory (for instructions see Chapter 1) before setting up the work area directory. Creating the Files As described in Chapters 3 and 4, there are two options you can use to create the input data files. 1. The HDM Input Data Facility. 2. Any text editor. Using the HDM Input Data Facility is recommended because it gives a full-screen entry form for every HDM card, displays useful information about the card, checks if the input lies within the allowable input range, and ensures that the input data are placed in the correct column positions. Text editors, on the other hand, permit easier manipulation of input files. Note: If you want to use a text editor, the notepad option of Sidekick is recommended because it is a resident program and also has a built-in calculator. All the input data files required for this application are supplied with the HDM program. These files may be copied to the HDMTUTOR directory using the following steps: 1. Change to the HDMTUTOR directory: C > CD\HDMTUTOR 2. Copy all the tutor files into the HDMTUTOR directory: C>COPY C:\HDM\TUTOR*.* To understand the data entry procedures, it is recommended that you create all the input data files for this application following the steps below (see Table 6-13): 1. Create the required files for RUN 1.

99 80 An HDM Application 2. Make a copy of the files that are different for RUN 2 and RUN 3, using different names. 3. Edit these duplicate files to reflect the requirements for RUN 2 and RUN 3. Table Creating the Input Data Files Create Copy into and edit TUTORKl.TXT TUTORA.TXT TUTORAB TUTORC TUTORD TUTORE TUTORF TUTORGl.TXT TUTORUNl.TXT TUTORK2.TXT TUTORG2.TXT TUTORUN2.TXT TUTORK3.TXT TUTORG3.TXT TUTORUN3.TXT To create the input data files for RUN 1, review all the HDM series (described in the HDM III User's Manual) and find out what cards are needed and their sequence. With that information, create the files using the cards editor option of the Input Data Facility. Remember to create one file each for series A, B, C, D, E, F and K, and a single ftle for series G, H, I and J. The files required for RUN 1, including the card numbers, are shown in Exhibit 6-1. File= TUTORKl.TXT Series K: Run Control Information RUN TITLE DATE CURRENCY ROUGHNESS READ: LOW TRAFFIC DOLLARS IR ALL DATASETS SCAN: ALL DATASETS ECHO PRINT: ALL DATASETS SUPPRESS OUTPUT REPORTS: REPORT 8 REPORT 9 REPORTlO ~DELLING EVALUATION END SERIES Exhibit 6-1. Files Required for Run 1 BRAZ 20 DOLLARS QI 0.00 KlOl K102 Kl Kl04 K106 K107 K109 K107 Klll K107 K112 K113B K113C K113D 0 Kll4 K115 K116 Notes: The title of Run 1 is LOW TRAFFIC. The Brazilian equations are used for VOC estimation. Only rep01ts 7 and 11 are requested. Report 1 to 6 are defined in series I...

100 An HOM Application 81 File= TUTORA.TXT Series A : Existing Link Characterisics Exhibit 6-1. (coot) LINK IRI2GOOD CONDITION 1 A101 SECTION A102 SECTION DATA P ALL A201 ENVIRONMENT A202 GEOMETRY A203 SURFACE PAVD A204 BASE/SUBGRADE 1 8 A205 STRENGTH PARAMETERS A206 CONDITION A209 HISTORY A210 END LINK A211 LINK IRI4FAIR CONDITION 1 A101 SECTION A102 SECTION DATA P ALL A201 ENVIRONMENT A202 GEOMETRY A203 SURFACE PAVD A204 BASE/SUBGRADE 1 8 A205 STRENGTH PARAMETERS A206 CONDITION A209 HISTORY A210 END LINK A211 LINK IRI7POOR CONDITION 1 A101 SECTION A102 SECTION DATA P ALL A201 ENVIRONMENT A202 GEOMETRY A203 SURFACE PAVD A204 BASE/SUBGRADE 1 8 A205 STRENGTH PARAMETERS A206 CONDITION A209 HISTORY A210 END LINK A211 LINK GRA VGRA VEL ROAD 1 A101 SECTION A102 SECTION DATA U ALL A201 ENVIRONMENT A202 GEOMETRY A203 CONDITION 150. A309 SURFACE UPAV A301 BASE/SUBGRADE A302 HISTORY 0 A303 END LINK A211 END SERIES A212 Notes: The surface code for paved roads is PA VD and for unpaved roads is UPA V. There is only one section within a link in this case, and is designated by a four-digit code (e.g. 0001).

101 82 An HOM Application File = TUTORB.TXT Series B : Construction Options And Costs Exhibit 6-1 (coot). CONSTRUCCNSTGRAVEL CONSTRUC 1 LINK GRAV 1 1 COST TIME STREAM EXO B-C EXB1 SECTION NEW SECTION DATA P ALL GEOMETRY SURFACE PAVD BASE/SUBGRADE 1 8 STRENGTH PARAMETERS CONDITION SECTION TOTAL COST PER KM END CONSTRUCTION OPTION END SERIES B101 B102 B103 B106 B107 B201 B203 B204 B205 B206 B209 B401 B211 B212 Notes: Use the same link code (GRAV) as defined in series A. This option generates the exogenous costs (EXBJ), defined in series F. The paving of the gravel road will take place in a one year period. File = TUTORF.TXT Series F : Exogenous Benefits-costs EXO B-C EXB1 DESCRIPT NEW COSTS NEW COSTS END EXO B-C END SERIES Fl01 Fl02 F103 Fl03 Fl05 F106 Notes: Use the same exogenous code (EXBJ) as defined in series B. The exogenous costs amount to $2.0 million per annum and are spread over 3 years beginning the first year after constntction. Note that in the fourth year after constrnction, the exogenous costs become zero

102 An HDM Application 83 Exhibit 6-1 (cont). File = TUTORC.TXT Series C: Road Maintenance Standards And Unit Costs UNIT COSTS C101 1FINANCIAL 84.0 C103 2FINANCIAL 7.7 C103 3FINANCIAL 6.5 C103 4FINANCIAL C103 8FINANCIAL 6.3 C103 9FINANCIAL 2.2 C103 10FINANCIAL 7.0 C103 11FINANCIAL 11.0 C103 12FINANCIAL C103 1ECONOMIC 75.0 C104 2ECONOMIC 7.0 C104 3ECONOMIC 6.0 C104 4ECONOMIC C104 8ECONOMIC 6.0 C104 9ECONOMIC 2.0 C104 10ECONOMIC 6.0 C104 lleconomic 10.0 C104 12ECONOMIC C104 STANDARD P STPOPAVD C ROUTINE MAINTENANCE C RECONSTRUCTION C306B 31 RECONST EFFECT C307 STANDARD P STP1PAVD C ROUTINE MAINTENANCE C PATCHING C303C 11 RECONSTRUCTION C306B 31 RECONST EFFECT C307 STANDARD P STP2PAVD C ROUTINE MAINTENANCE C PATCHING C303C 09 RESEAL B C304B 11 RECONSTRUCTION C306B 31 RECONST EFFECT C307 STANDARD P STP3PAVD C ROUTINE MAINTENANCE C PATCHING C303C 10 OVERLAY C305B 11 RECONSTRUCTION DO C306B 31 RECONST EFFECT C307 STANDARD U STUOUPAV C ROUTINE MAINTENANCE C405 STANDARD U STU1UPAV C ROUTINE MAINTENANCE C GRADING C401B 02 SPOT REGRAVELLING C402B STANDARD U STU2UPAV C ROUTINE MAINTENANCE C GRADING C401B 03 RESURFACING C403B 23 SURFACE C404 END SERIES C309

103 84 An HOM Application Exhibit 6-1 (cont). File = TUTORD.TXT Series D: Vehicle Fleet Characteristics And Unit Costs NAME CAR PICKUP LCAR TRUCK ARTIC D101 VEH TYPE D102 HP METRIC D104 GVW D106 EQX D107 VAXLES D109 FINANCIAL D401A VEHICLE D402 TIRE D403 MAINT LAB D404 CREW D405 INTEREST D409 PETROL D410 ECONOMIC D401B VEHICLE D402 TIRE D403 MAINT LAB D404 CREW D405 INTEREST D409 PETROL D410 DEPRECIATE D501 UTILIZE D502 KM DRIVEN D503 VEH LIFE D504 HR DRIVEN DSOS END SERIES D510 Notes: You can give any name for the different vehicle types. The vehicle types are defined in the Description of the HDM model. The GVW is an optional input. The default characteristics of the Brazilian vehicles are used in this application; these... characteristics may be changed for other vehicle types. The DEPRECIATE and UTILIZE codes are set to 1..

104 An HOM Application 85 Exhibit 6-1 (cont). File = TUTORE.TXT Series E : Traffic Volumes And Growth Characteristics TRAFFIC PLOW N E101 DESCRIPTLOW TRAFFIC E102 NEW ADT E103 NEWADT E103 TRAFFIC PMED N E101 DESCRIPTMEDIUM TRAFFIC E102 NEW ADT E103 NEWADT E103 TRAFFIC PHIG N E101 DESCRIPTHIGH TRAFFIC E102 NEW ADT E103 NEWADT E103 TRAFFIC ULOW N E101 DESCRIPTLOW TRAFFIC U E102 NEW ADT E103 NEW ADT E103 END TRAFFIC E104 TRAFFIC UMED N E101 DESCRIPTMEDIUM TRAFFIC U E102 NEW ADT E103 NEW ADT E103 END TRAFFIC E104 TRAFFIC UHIG N E101 DESCRIPTHIGH TRAFFIC U E102 NEW ADT E103 NEW ADT E103 END TRAFFIC E104 END SERIES E105 Notes: The number of vehicles should correspond to the number of vehicles defined in series D. All traffic sets are normal traffic. The ADT values are for The annual traffic growth is 3 percent from 1989 for all vehicles. This file contains the traffic sets for all three runs.

105 86 An HOM Application Exhibit 6-1 (cont). File= TUTORGl.TXT Series G,H,I and J ALTERNATIVE IRI2ALTO TRAFFIC PLOW1988 MAINTENANCE STP01988 ALTERNATIVE IRI2ALT1 TRAFFIC PLOW1988 MAINTENANCE STP11988 ALTERNATIVE IRI2ALT2 TRAFFIC PLOW1988 MAINTENANCE STP21988 ALTERNATIVE IRI2ALT3 TRAFFIC PLOW1988 MAINTENANCE STP31988 ALTERNATIVE IRI4ALTO TRAFFIC PLOW1988 MAINTENANCE STP01988 ALTERNATIVE IRI4ALT1 TRAFFIC PLOW1988 MAINTENANCE STP11988 ALTERNATIVE IRI4ALT2 TRAFFIC PLOW1988 MAINTENANCE STP21988 ALTERNATIVE IRI4ALT3 TRAFFIC PLOW1988 MAINTENANCE STP31988 ALTERNATIVE IRI7ALTO TRAFFIC PLOW1988 MAINTENANCE STP01988 ALTERNATIVE IRI7ALT1 TRAFFIC PLOW1988 MAINTENANCE STP11988 ALTERNATIVE IRI7ALT2 TRAFFIC PLOW1988 MAINTENANCE STP21988 ALTERNATIVE IRI7ALT3 TRAFFIC PLOW1988 MAINTENANCE STP31988 ALTERNATIVE GRAVALTO TRAFFIC ULOW1988 MAINTENANCE STU01988 ALTERNATIVE GRAVALTl TRAFFIC ULOW1988 MAINTENANCE STU11988 ALTERNATIVE GRAVALT2 TRAFFIC ULOW1988 MAINTENANCE STU21988 ALTERNATIVE GRAVALT3 TRAFFIC ULOW1988 MAINTENANCE STU01988 CONSTRUCTIONCNST1990 MAINTENANCE STP11991 END SERIES GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl Gl02 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS GlOl G102 GlOS G103 GlOS GlOB Notes on series G: Series G defines the link alternatives. The first year of analysis is 1988 and maintenance standards are applied 1988 onwards. For the link GRA V alternative ALT3, the maintenance standard is STUO in 1988, the link is paved in 1990 and after paving, the maintenance standard is STP 1.

106 An HDM Application 87 File = TUTORGl.TXT (cont) GROUP ALTERNATIVE GPAVALTO LINK-ALT IRI2ALTO IRI4ALTO GROUP ALTERNATIVE GPAVALTl LINK-ALT IRI2ALT1 IRI4ALT1 GROUP ALTERNATIVE GPAVALT2 LINK-ALT IRI2ALT2 IRI4ALT2 GROUP ALTERNATIVE GPAVALT3 LINK-ALT IRI2ALT3 IRI4ALT3 GROUP ALTERNATIVE GUNPALTO LINK-ALT GRAVALTO GROUP ALTERNATIVE GUNPALTl LINK-ALT GRAVALTl GROUP ALTERNATIVE GUNPALT2 LINK-ALT GRAVALT2 GROUP ALTERNATIVE GUNPALT3 LINK-ALT GRAVALT3 END SERIES LINK IRI2 ALTERNATIVE ALTO TRAFFIC ANNUAL ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS USER COSTS DETAILED LINK IRI4 ALTERNATIVE ALTO ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI7 ALTERNATIVE ALTO ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI2 ALTERNATIVE ALT1 ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI4 ALTERNATIVE ALTl ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI7 ALTERNATIVE ALTl ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI2 ALTERNATIVE ALT2 ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI4 ALTERNATIVE ALT2 ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS Exhibit 6-1. (cont) IRI7ALTO IRI7ALT1 IRI7ALT2 IRI7ALT H101 H102 H101 H102 H101 H102 H101 H102 H101 H102 H101 H102 H101 H102 H101 H102 H104!101!105 Il06 Il06!106!107!101!106!106 Il06 Il01!106!106!106!101!106!106!106!101!106!106!106 Il01!106!106!106!101 I106!106!106!101!106!106!106 Notes on series H: Series H defines the group alternatives. Group GRAVis for paved roads. Group GUNP is for unpaved roads. The unpaved group must be defined even if there is only one gravel/ink.

107 88 An HOM Application File= TUTORGl.TXT (cont) Exhibit 6-1. (cont) LINK IRI7 ALTERNATIVE ALT ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI2 ALTERNATIVE ALT ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI4 ALTERNATIVE ALT ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK IRI7 ALTERNATIVE ALT ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK GRAV ALTERNATIVE ALTO 1101 TRAFFIC ANNUAL ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS !106 USER COSTS DETAILED !107 LINK GRAV ALTERNATIVE ALT ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK GRAV ALTERNATIVE ALT ROAD CONDITIONS ROAD CONDITIONS ROAD CONDITIONS LINK GRAV ALTERNATIVE ALT ROAD CONDITIONS ROAD CONDITIONS !106 ROAD CONDITIONS END SERIES!109 STUDY BASE J101 COMPARE J102 ALT1 GPAV ALTO J103 ALT2 GPAV ALTO J103 ALT3 GPAV ALTO J103 ALT1 GUNP ALTO J103 ALT2 GUNP ALTO J103 ALT3 GUNP ALTO J103 DISCOUNT RATES J106 END STUDY J107 END SERIES J108 Notes on series I and J: Series I defines the report requests. Report 3 (annual traffic) is requested for paved roads in good condition and the gravel road for years 1988, 2000, and Report 5 (use costs detailed) is requested for the paved road and the gravel road for years 1988, 2000 and Report 4 (road condition) is requested for all/ink alternatives for years 1988 through Series J defines the comaprison of alternatives. 17ze comaprison code is BASE. Alternatives ALT1, AL T2, and AL T3 are compared against the "Do-nothing" alternative, ALTO, for both the paved and unpaved roads. The discount rates used for the analysis are 6, 12, and 20 percent. '"

108 An HDM Application 89 The Run Control File for RUN 1 has the following lines: TUTORKl.TXT TUTORA.TXT TUTORB.TXT TUTOR C. TXT TUTORD.TXT TUTORE.TXT TUTORF.TXT TUTORGl.TXT SCAN LOUT SCAN2.0UT SCAN3.0UT SCAN4.0UT INPUT.OUT RESULTS1.0UT EBMDATA.OUT After all seven input data files and the Run Control File have been created, RUN 1 is ready for execution on the HDM. The files required for RUN 2 and RUN 3 are easier to create. Follow the steps below: 1. Duplicate the files that are different from the RUN 1 files using the DOS COPY command: C >COPY TUTORKl.TXT TUTORK2.TXT C >COPY TUTORKl.TXT TUTORK3.TXT C >COPY TUTORGl.TXT TUTORG2.TXT C >COPY TUTORGl.TXT TUTORG3.TXT C >COPY TUTORUNl.TXT TUTORUN2.TXT C>COPY TUTORUN1.TXT TUTORUN3.TXT 2. Verify that the files for RUN 2 and RUN 3 exist by using the DOS command: C>DIR 3. Edit the duplicate files to incorporate the changes shown in Table The Input Data Facility may be used to make the necessary changes. For example, to modify file TUTORK2.TXT, follow the steps below: a. Run the Input Data Facility with the command: C>RUNINPUT b. When prompted for the work area directory enter: C:\HDMTUTOR c. Once the main menu of the Input DataFacility is displayed, select Option 1 to use the cards editor. d. When prompted for a file name enter: TUTORK2 e. When the cards editor menu is displayed, select the edit option to make the changes by pressing the letter E.

109 90 An HOM Application f. Enter 1 as the line number to edit. g. An entry screen for card K101 will be displayed. Change LOW TRAFFIC to MEDIUM TRAFFIC. h. Select the save option in the cards editor menu to save the modifications. 1. Leave the cards editor by selecting the quit option. 4. Repeat the above steps to make all the changes shown in Table Table Editing the Files for RUN 2 and RUN 3 File TUTORK2.TXT TUTORG2.TXT TUTORG2.TXT TUTORUN2.TXT TUTORUN2.TXT TUTORUN2.TXT TUTORK3.TXT TUTORG3.TXT TUTORG3.TXT TUTORUN3.TXT TUTORUN3.TXT TUTORUN3.TXT Replace all LOW TRAFFIC PLOW ULOW TUTORKl.TXT TUTORGl.TXT RESULTSl.TXT LOW TRAFFIC PLOW ULOW TUTORKl.TXT TUTORGl.TXT RESULTSl.TXT With MEDIUM TRAFFIC PMED UMED TUTORK2.TXT TUTORG2.TXT RESULTS2.TXT HIGH TRAFFIC PRIG UHIG TUTORK3.TXT TUTORG3.TXT RESULTS3.TXT Running the HDM Program After creating the input data files, obtain the HDM results by following the steps below: 1. Run the HOM program for RUN Check if there is any input error. 3. View the results. 4. Print the results. 5. Run the Lotus Facility for RUN Repeat the above steps for RUN 2 and RUN 3. Running the HDM Program for RUN 1 Run the HDM program as follows: 1. Ensure that there are at least 8 megabytes of available disk space using the DOS command: C>CHKDSK. 2. Change to the HDMTUTOR directory with the command:

110 An HDM Application 91 C > CD\HDMTUTOR 3. Run the program with the command: C>RUNHDM 4. The program displays the initial logo and requests the name of the ftle with the input/output filenames (Run Control File). Enter: TUTORUNl.TXT The program displays the initial time and, when it completes Module 5, the fmal time. This run takes about 15 minutes on an IBM AT with a math co-processor and 50 minutes on an IBM model30 without a math co-processor. Checking the Program for Input Errors If there is any error in the input data, the program does not display the Modelling and Evaluation messages at the end of Module 5. To locate the errors, first view the input summary table (see Exhibit 6-2) given at the end of the scan 3 ftle and then locate the errors on all the scan ftles. If you are using the files supplied with the program, there should be no errors and the Modelling and Evaluation messages should be displayed on the screen. Even if you do not have any fatal errors, it is always a good practice to view the input summary table before proceeding because it also contains a summary of the input data warnings. To view the input summary table: 1. Run the Read program with the command: C>RUNREAD 2. Enter the name of the file to list: SCAN3.0UT 3. Display the Input Data Summary by pressing the End key. Exhibit 6-2. The Input Summary Table Data series Fatal errors Warnings A. EXISTING LINK CHARACTERISTICS B. CONSTRUCTION OPTIONS AND COSTS C. ROAD MAINTENANCE STANDARDS AND UNIT COSTS D. VEHICLE FLEET CHARACTERISTICS AND UNIT COSTS E. TRAFFIC VOLUME AND GROWTH CHARACTERISTICS F. EXOGENOUS BENEFITS-COSTS G. LINK ALTERNATIVES H. GROUP ALTERNATIVES I. REPORT REQUESTS J. COMPARISON OF ALTERNATIVES K. RUN CONTROL INFORMATION

111 92 An HOM Application 4. Exit the Read program by pressing the Esc key. Viewing the Results You can view the results, the scan files, and the echo print using the Read program. The steps are: 1. Run the Read program with the command: C>RUNREAD 2. Enter the name of the file to list. For example: RESULTSl.OUT 3. Browse through the file using the End, Home, PgUp, PgDn, and Arrow keys. 4. Exit the Read program by pressing the Esc key. Note: As the output files are quite large, it is best to print the files or use the Lotus Facility to imp01t the results into Lotus The last report on the RESULTSl.OUT file is report number 11 which contains the cost summary and the comparison of alternatives. The results for the low traffic run (RUN 1) derived from this report are summarized in Table Table Results for the Low Traffic Run (RUN 1) Road type Comparison of alternatives NPVat6% discount rate NPVat 12% discount rate Best alternative IRI2 IRI4 IRI7 GRAY ALT1 vs. ALTO ALT2 vs. ALTO ALT3 vs. ALTO ALT1 vs. ALTO ALT2 vs. ALTO AL T3 vs. ALTO ALT1 vs. ALTO ALT2 vs. ALTO ALT3 vs. ALTO ALT1 vs. ALTO ALT2 vs. ALTO ALT3vs.ALTO 1.3 * * * * 0.5 * * * * 43.8 ALTl ALT3 (at 6%) ALT1 (at 12%) ALT3 ALT3 (at 6%) ALT2 (at 12%) Note that the best alternative (with the highest NPV and indicated with an asterik *)varies with the condition of the road and the discount rate.

112 An HOM Application 93 Printing the Results To print any file created by the HDM program with correct pagination, use the HDMPRINT program. The steps are: 1. Turn on the printer. 2. Run the HDMPRINT program with the command: C>RUNPRINT 3. Enter the name of the file to print. For example: INPUT.OUT Note: The INPUT. OUT file contains the echo print of the input data. Always print and examine this file to check the input data for possible e"ors. For this run, the size and the number of pages for each output file are as shown in Table There is no correlation between the number of pages and the size of the files because the data in the files are not paginated. Table Size of Output Files File INPUT.OUT RESULTS1.0UT SCANl.OUT SCAN2.0UT SCAN3.0UT SCAN4.0UT Size (bytes) 93, ,447 6,619 9,207 13, Pages printed You can also print these files using the DOS print command. If you use the print command, the reports will not be paginated and a series of O's and 1's will appear in the first column. Using the Lotus Facility for RUN 1 To create tables for Lotus 1-2-3: 1. Use the HDMLOTUS program with the command: C>RUNLOTUS The program displays an initial logo and the main menu. 2. Select the desired tables and create the corresponding Lotus files as shown in Table 6-17.

113 94 An HOM Application Table Creating Lotus Files for RUN1 Report type Economic costs Comparison of alternatives Road conditions (before and after maintenance) Use filename ECONl.PRN COMPl.PRN ROADl.PRN One of the advantages of the Lotus Facility is that it allows you to decide what tables to create after the HDM program run have been completed. You may exit the Lotus Facility and at a later time run it again to obtain new tables. However, If you run the HDM program again, the Direct Access files will be overwritten and the Lotus Facility will generate tables for the new run. Repeating Steps for RUN 2 and RUN 3 After generating all the tables to be imported into Lotus for RUN 1, repeat the steps for the medium traffic roads (RUN 2) and the high traffic roads (RUN 3). For these new HDM and Lotus Facility runs, create the files listed in Table Table Creating Lotus Files for RUN 2 and RUN 3 Report Economic costs table Comparison table Road conditions table (Before and after maintenance) RUN2 ECON2.PRN COMP2.PRN ROAD2.PRN RUN3 ECOM3.PRN COMP3.PRN ROAD3.PRN Note that for each new HDM run, the following files will be overwritten: SCANl.OUT SCAN2.0UT SCAN3.0UT SCAN4.0UT INPUT.OUT EBMDATA.OUT But, the following results files will remain intact: RESULTl.OUT RESULT2.0UT RESULT3.0UT

114 An HOM Application 95 The tables to be imported into Lotus are: ECOMl.PRN COMPl.PRN ROADl.PRN ECOM2.PRN COMP2.PRN ROAD2.PRN ECOM3.PRN COMP3.PRN ROAD3.PRN Analyzing the Results To analyze the results, print all the output files. You can import the tables into Lotus to graph the results and compute summary statistics. To import a table into Lotus 1-2-3, follow the steps below: 1. Run the program. 2. Change the file directory to your data directory: I F D c:/hdmtutor 3. Import the table with the import number option: I F I N compl.prn 4. Change the column width to 12: /WGC12 Sample reports including a series of graphs produced in Lotus are shown in the following exhibits: Exhibit 6-3 Vehicle operating costs by vehicle type for paved road initially in good condition with medium traffic (alternative ALTO, years 1988, 2007) Road deterioration history for paved road initially in good condition with medium traffic (all alternatives). Life cycle economic costs for paved road initially in good condition with medium traffic (all alternatives). Comparison of alternatives for paved road initially in good condition with medium traffic (0, 6, 12, 20 discount rates). Graphs of road deterioration and NPV of maintenance alternatives for paved roads. Vehicle Operating Costs Vehicle operating cost estimates for five representative vehicles are shown in Exhibit 6.3 for paved roads. These are examples of report type 5, which provides for each vehicle type and for every specified link alternative/year combination the following information:

115 96 An HDM Application The average vehicle speed. The resources used per 1,000 vehicle-km. The road user costs per 1,000 vehicle-km. The results for the medium traffic paved road in good condition (IRI2) under alternative ALTO (Do-nothing) are shown in Table Table Vehicle Operating Costs for Paved Road Initially in Good Condition under the Do-Nothing Alternative Vehicle Average speed (km/hour) Road user costs (dollars per km) Roughness (IRI) from report type 4 Car Pickup Large car Truck Articulated Car Pickup Large car Truck Articulated Road Deterioration The road deterioration history of link IRI2 is shown in Exhibit 6-4 under four maintenance alternatives (ALTO, ALT1, ALT2, and ALT3). These are examples of report type 4 which gives for every specified link alternative/year the following information: The average daily traffic (ADT). The equivalent standard axles (ESA). The complete deterioration history. The years resurfacing or preventive maintenance is applied. Economic Costs The economic costs and their foreign exchange component corresponding to maintenance alternatives ALTO, ALTl, ALT2, and ALT3 for link IRI2 are shown in Exhibit 6-5. These are examples of report type 7 which gives for every specified link alternative the following information: The capital costs (reconstruction, overlay, reseal). The recurrent costs (routine maintenance, patching). The vehicle operating costs.

116 An HOM Application 97 The exogenous costs (slope protection to enhance roadside environment). The total costs (sum of the above costs). The foreign exchange costs. Total discounted costs at specified discount rates. Comparison of Alternatives An economic analysis of maintenance alternatives (report type 11) for the medium traffic run is presented in Exhibit 6-6. Report type 11 summarizes the following information for discount rates of 0, 6, 12, and 20 percent. Total capital costs. Total periodic maintenance costs. Total routine maintenance costs. Total agency costs (sum of the above costs). Total vehicle operating costs. Total exogenous costs. Total costs. Net present value of comparison of alternatives. Internal rate of return of comparison of alternatives. Note that for each link the best maintenance alternative is the one with the lowest total cost or the highest net present value. Graphs and Bar Charts The graphs (Exhibit 6-7) show for each of the representative link the following information: Progression of road deterioration (roughness) under different maintenance alternatives. Net present value (at different discount rates) of the various maintenance alternatives as compared to the "Do-nothing" maintenance alternative (ALTO). Note that in each case the best maintenance alternative varies with the type of road, traffic level, and discount rate used for the comparisons. A summary of the results for this HDM application is given in Table 6-20.

117 98 An HDM Application Table Summary of Results for HOM Application B~stls~~Qnd b~st maint~nan~~ alt~rnati~ Variable Low traffic Medium traffic High traffic At 0% discount rate Good paved road ALTl/ ALTO ALT3/ ALTI ALT3/ ALT2 Fair paved road ALT3/ ALTl ALT3/ ALTO ALT3/ALTO Poor paved road ALT3/ ALTO ALT3/ ALTO ALT3/ALTO Gravel road ALT3/ ALT2 ALT3/ALT2 ALT3/ ALTl At 6% discount rate Good paved road ALTl/ ALTO ALT3/ALT2 ALT3/ALT2 Fair paved road ALT3/ ALTl ALT3/ALTO ALT3/ALTO Poor paved road ALT3/ ALTO ALT3/ALTO ALT3/ ALTO Gravel road ALT3/ ALT2 ALT3/ALT1 ALT3/ ALTl At 12% discount rate Good paved road ALTl/ ALTO ALT3/ALT2 ALT3/ALT2 Fair paved road ALTl/ ALT3 ALT3/ ALTI ALT3/ ALTO Poor paved road ALT3/ ALTO ALT3/ ALTO ALT3/ALTO Gravel road ALT2/ ALTl ALT3/ ALTl ALT3/ ALTl At 20% discount rate Good paved road ALTl/ ALTO ALT3/ ALT2 ALT3/ ALT2 Fair paved road ALTl/ ALTO ALT3/ALT2 ALT3/ALT2 Poor paved road ALT3/ ALTl ALT3/ALTO ALT3/ALTO Gravel road ALT2/ ALTl ALTl/ ALT3 ALT3/ ALTl

118 Exhibit 6-3. Vehicle Operating Costs 88/02/20 MEDIUM TRAFFIC REPORT TYPE 5 : PAGE 1 ANNUAL ROAD USER COSTS REPORT ECONOMIC COSTS IN DOLLARS YEAR LINK-ALT. SECTION CAR PICKUP LCAR TRUCK ARTIC 1988 IRI2-ALTO 1 AV. SPEED (KM/H) VOC PER VEHICLE-TRIP VOC PER 1000 VEHICLE-KM FUEL LUBRICANTS TIRES SPARE PARTS MAINTENANCE LABOR CREW DEPRECIATION INTEREST TOTAL RUNNING COST OVERHEAD COST TIME VALUE OF PASS TIME VALUE OF CRGO TOTAL TIME COST TOTAL COST RESOURCES PER 1000 VEHICLE-KM FUEL (LITERS) LUBRICANTS(LITERS) TIRES (NO OF COST- EQUIV NEW TIRES) SPARE PARTS (PRCNT NEW VEH PRICE) MAINT LABOR(LAB-H) CREW (CREW-H) DEPRECIATION (PCT NEW VEH PRICE) INTEREST (PRCNT OF NEW VEH PRICE) PASSENGERS (PASS-H DELAYED) CARGO(VEH-H DELYD) )> ::I I 0 s:::: )> "0 "Q. [ ()" ::I ~

119 ... Exhibit 6-3 ( cont). Vehicle Operating Costs g 88/02/20 MEDIUM TRAFFIC REPORT TYPE 5 : PAGE 3 ANNUAL ROAD USER COSTS REPORT ECONOMIC COSTS IN DOLLARS YEAR LINK-ALT. SECTION CAR PICKUP LCAR TRUCK ARTIC 2007 IRI2-ALTO 1 AV. SPEED (KM/8) VOC PER VEHICLE-TRIP VOC PER 1000 VEHICLE-KM FUEL LUBRICANTS TIRES SPARE PARTS MAINTENANCE LABOR CREW DEPRECIATION INTEREST TOTAL RUNNING OVERHEAD COST TIME VALUE OF TIME VALUE OF COST o PASS.0.o CRGO.0.o TOTAL TIME COST TOTAL COST RESOURCES PER 1000 VEHICLE-KM FUEL (LITERS) LUBRICANTS(LITERS) TIRES (NO OF COST- EQUIV NEW TIRES) SPARE PARTS (PRCNT NEW VEH PRICE) MAINT LABOR(LAB-H) CREW (CREW-H) DEPRECIATION (PCT NEW VEH PRICE) )> INTEREST (PRCNT OF ::::::1 NEW VEH PRICE) ::I: PASSENGERS (PASS-H 0 DELAYED) s:: CARGO(VEH-H DELYD) )> '0 '2. 6" D) o... ::::::1 1 ~

120 Exhibit 6-4. Road Deterioration History > :::l :I: 88/02/20 MEDIUM TRAFFIC REPORT TYPE 4 : PAGE 1 0 ANNUAL ROAD CONDITIONS REPORT s:: , > LINK-ALT IRI2-ALTO SECTION cr PAVED ROAD (MEDIUM STRENGTH SUBSECTION) GRAVEL ROAD :::l END OF YEAR CONDITION YEARS TWO- ANNUAL SINCE LAST AREA AREA MEAN SD MEAN WAY TWO-WAY BEF/ ALL WIDE AREA AREA RUT RUT PERIODC GRAVEL YEARLY ADT ESA SURF/ AFTER SURF MOD CRACKS CRACKS RAVLD POTHD DEPTH DEPTH ROUGHNS MAINT THICKNS ROUGHNS YEAR (VPD) (THOUS) REGRV CONS MAINT TYPE SN (%) (%) (%) (%) (~) (~) (IR) APPLD (~) (IR) BEF AC o AFT AC o BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AFT AC AC o BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC o BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC "2. c; a

121 Exhibit 6-4 (cont). Road Deterioration History 88/02/20 MEDIUM TRAFFIC REPORT TYPE 4 : PAGE 4 ANNUAL ROAD CONDITIONS REPORT LINK-ALT IRI2-ALT1 SECTION \) PAVED ROAD (MEDIUM STRENGTH SUBSECTION) GRAVEL ROAD END OF YEAR CONDITION YEARS TWO- ANNUAL SINCE LAST AREA AREA MEAN SD MEAN WAY TWO-WAY BEF/ ALL WIDE AREA AREA RUT RUT PERIODC GRAVEL YEARLY ADT ESA SURF/ AFTER SURF MOD CRACKS CRACKS RAVLD POTHD DEPTH DEPTH ROUGHNS MAINT THICKNS ROUGHNS YEAR (VPD) (THOUS) REGRV CONS MAINT TYPE SN (%) (%) (%) (%) (~) (~) (IR) APPLD (~) (IR) BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC I BEF AC AFT AC s:: BEF AC )> AFT AC " BEF AC "2. AFT AC c=; BEF AC AFT AC a BEF AC ' ::J AFT AC BEF AC AFT AC BEF AC )> ::J

122 Exhibit 6-4 (cont). Road Deterioration History I 88/02/20 MEDIUM TRAFFIC REPORT TYPE 4 : PAGE 7 0 ANNUAL ROAD CONDITIONS REPORT s:: )> "0 "Q. LINK-ALT IRI2-ALT2 SECTION 1 c:; ~ o PAVED ROAD (MEDIUM STRENGTH SUBSECTION) GRAVEL ROAD END OF YEAR CONDITION YEARS TWO- WAY ANNUAL TWO-WAY SINCE LAST BEF/ AREA ALL AREA WIDE AREA AREA MEAN RUT SD RUT PERIODC GRAVEL MEAN YEARLY ADT ESA SURF/ AFTER SURF MOD CRACKS CRACKS RAVLD POTHD DEPTH DEPTH ROUGHNS MAINT THICKNS ROUGHNS YEAR (VPD) (THOUS) REGRV CONS MAINT TYPE SN (%) (%) (%) (%) (t-11) (t-11) (IR) APPLD (t-11) (IR) BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC RESE AFT RSAC BEF RSAC AFT RSAC BEF RSAC AFT RSAC BEF RSAC AFT RSAC BEF RSAC AFT RSAC BEF RSAC RESE AFT RSAC BEF RSAC AFT RSAC BEF RSAC AFT RSAC BEF RSAC AFT RSAC BEF RSAC AFT RSAC BEF RSAC RESE 0 w AFT RSAC BEF RSAC AFT RSAC BEF RSAC )> :::l :::l _.

123 Exhibit 6-4 (cont). Road Deterioration History 88/02/20 MEDIUM TRAFFIC REPORT TYPE 4 : PAGE io ANNUAL ROAD CONDITIONS REPORT LINK-ALT IRI2-ALT3 SECTION ~ PAVED ROAD (MEDIUM STRENGTH SUBSECTION) GRAVEL ROAD END OF YEAR CONDITION YEARS TWO- ANNUAL SINCE LAST AREA AREA MEAN SD MEAN WAY TWO-WAY BEF/ ALL WIDE AREA AREA RUT RUT PERIODC GRAVEL YEARLY ADT ESA SURF/ AFTER SURF MOD CRACKS CRACKS RAVLD POTHD DEPTH DEPTH ROUGHNS MAINT THICKNS ROUGHNS YEAR (VPD) (THOUS) REGRV CONS MAINT TYPE SN (%) (%) (%) (%) (M-1) (M-1) (!R) APPLD (M-1) (IR) BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC o AFT AC o BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC AFT AC BEF AC OVER AFT OVSA )> BEF OVSA :::l AFT OVSA :::c BEF OVSA AFT OVSA s::: BEF OVSA )> AFT OVSA "C BEF OVSA "2. AFT OVSA c:; BEF OVSA AFT OVSA e BEF OVSA " AFT OVSA :::l BEF OVSA AFT OVSA BEF OVSA

124 Exhibit 6-5. Economic Costs 81f/02/20 MEDIUM TRAFFIC REPORT TYPE 7.. :.PAGE 1 ECONOMIC AND FOREIGN EXCHANGE COSTS OF ALTERNATIVE IN MILLION DOLLARS LINK-ALT. IRI2-ALTO GOOD CONDITION - ORIGINAL LENGTH KM YEAR ROAD CAPITAL COSTS ROAD RECURR COSTS EXISTING GENERATED EXISTING GENERATED VEHICLE VEHICLE VEHICLE VEHICLE NET OPERATING OPERATING TRAVEL TIME TRAVEL TIME EXOGENOUS COSTS COSTS COSTS COSTS COSTS TOTAL ECONOMIC COSTS TOTAL FOREIGN EXCHANGE COSTS TOTAL BENEFITS-COSTS - UNDISCOUNTED: ECONOMIC: FOREIGN: DISCOUNTED ECONOMIC COSTS AT.0 X X X X )> ::s J: 0 s:: )> "'C "'Q. o ~ ::s _

125 Exhibit 6-5 (cont). Economic Costs EB?02!20 IUM TRAFFIC - REPORT TYPE 7 : PAGE 5 ECONOMIC AND FOREIGN EXCHANGE COSTS OF ALTERNATIVE IN MILLION DOLLARS LINK-ALT. IRI2-ALT1 GOOD CONDITION - ORIGINAL LENGTH KM YEAR ROAD CAPITAL COSTS ROAD RECURR COSTS EXISTING GENERATED EXISTING GENERATED VEHICLE VEHICLE VEHICLE VEHICLE NET OPERATING OPERATING TRAVEL TIME TRAVEL TIME EXOGENOUS COSTS COSTS COSTS COSTS COSTS TOTAL ECONOMIC COSTS TOTAL FOREIGN EXCHANGE COSTS o431 o o459 o TOTAL BENEFITS-COSTS - UNDISCOUNTED: ECONOMIC: FOREIGN: DISCOUNTED ECONOMIC COSTS AT :.0 % 6.0 % 12.0 % 20.0 % oooo Ol )> ::::J I 0 ~ )> "0 '2. (')' Q) -6' ::::J

126 Exhibit 6-5 (cont). Economic Costs ml MEDIUM TRAFFIC REPORT TYPE 7 : PAGE 9 ECONOMIC AND FOREIGN EXCHANGE COSTS OF ALTERNATIVE IN MILLION DOLLARS LINK-ALT. IRI2-ALT2 GOOD CONDITION - ORIGINAL LENGTH KM YEAR ROAD CAPITAL COSTS ROAD RECURR COSTS EXISTING GENERATED EXISTING GENERATED VEHICLE VEHICLE VEHICLE VEHICLE NET OPERATING OPERATING TRAVEL TIME TRAVEL TIME EXOGENOUS COSTS COSTS COSTS COSTS COSTS TOTAL ECONOMIC COSTS TOTAL FOREIGN EXCHANGE COSTS TOTAL BENEFITS-COSTS - UNDISCOUNTED: ECONOMIC: 42 FOREIGN: DISCOUNTED ECONOMIC COSTS AT.0 % % % % )> ::I I 0 s:: )> "'C "2. g o ::I

127 Exhibit 6-5 ( cont). Economic Costs g-g MEDIUM TRAFFIC REPORT TYPE 7 : PAGE 13 ECONOMIC AND FOREIGN EXCHANGE COSTS OF ALTERNATIVE IN MILLION DOLLARS LINK-ALT. IRI2-ALT3 GOOD CONDITION - ORIGINAL LENGTH KM YEAR ROAD CAPITAL COSTS ROAD RECURR COSTS EXISTING GENERATED EXISTING GENERATED VEHICLE VEHICLE VEHICLE VEHICLE NET OPERATING OPERATING TRAVEL TIME TRAVEL TIME EXOGENOUS COSTS COSTS COSTS COSTS COSTS TOTAL ECONOMIC COSTS TOTAL FOREIGN EXCHANGE COSTS TOTAL BENEFITS-COSTS - UNDISCOUNTED: ECONOMIC: 42 FOREIGN: DISCOUNTED ECONOMIC COSTS AT :.0 % % % % co )> ::I I 0 s::: )> "0 "Q. ~ cr ::I

128 Exhibit 6-6. Evaluation of Alternatives 88/02/20 MEDIUM TRAFFIC REPORT TYPE 11 : PAGE 1 SUMMARY OF COSTS AND COMPARISONS BY DISCOUNT RATE : BASE IN MILLION DOLLARS DISCOUNT RATE =.00 % CONST TOTAL INTRNAL ORIG ECO/ RECON PERIODIC ROUTINE CONST & VEHICLE NET NET RATE OF LENGTH GEN FIN UPGRD MAINT MAINT MAINT OPERATING EXOGENOUS TOTAL PRES RETURN LINK (l<m) ALT TRAF CSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS COMPARISON VALUE (%) IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO NONE FIN ALT2 NO ECO ALT2 VS ALTO FIN ALT3 NO ECO ALT3 VS ALTO FIN IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO MANY FIN ALT2 NO ECO ALT2 VS ALTO MANY FIN ALT3 NO ECO ALT3 VS ALTO MANY FIN IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO MANY FIN ALT2 NO ECO ALT2 VS ALTO MANY FIN ALT3 NO ECO ALT3 VS ALTO FIN GRAV ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO NONE FIN ALT2 NO ECO ALT2 VS ALTO NONE FIN ALT3 NO EGO ALT3 VS ALTO FIN )> ::s I 0 ~ )> "0 "Q. cr e cr ::s... 0 (0

129 Exhibit 6-6 ( cont). Evaluation of Alternatives... 88/62/20 MEDIUM TRAFFIC REPORT TYPE 11 : PAGE 2 0 SUMMARY OF COSTS AND COMPARISONS BY DISCOUNT RATE : BASE IN MILLION DOLLARS DISCOUNT RATE = 6.00 % CONST TOTAL INTRNAL ORIG ECO/ RECON PERIODIC ROUTINE CONST & VEHICLE NET NET RATE OF LENGTH GEN FIN UPGRD MAINT MAINT MAINT OPERATING EXOGENOUS TOTAL PRES RETURN LINK (KM) ALT TRAF CSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS COMPARISON VALUE (%) IRI ALTO NO ECO FIN ALT1 NO ECO ALT1 VS ALTO 43.3 NONE FIN ALT2 NO ECO ALT2 VS ALTO FIN ALT3 NO ECO ALT3 VS ALTO FIN IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO MANY FIN ALT2 NO ECO ALT2 VS ALTO MANY FIN ALT3 NO ECO ALT3 VS ALTO MANY FIN IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO MANY FIN ALT2 NO ECO ALT2 VS ALTO MANY FIN ALT3 NO ECO ALT3 VS ALTO FIN GRAV ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO NONE FIN :t> ::J ALT2 NO ECO ALT2 VS ALTO NONE FIN I ALT3 NO ECO ALT3 VS ALTO FIN ~ :t> '0 -g_ c:; -5" Q) ::J

130 )> Exhibit 6-6 ( cont). Evaluation of Alternatives ::J I 88/02/20 MEDIUM TRAFFIC REPORT TYPE 11 : PAGE 3 0 s:: SUMMARY OF COSTS AND COMPARISONS BY DISCOUNT RATE : BASE )> "C IN MILLION DOLLARS "2. c; DISCOUNT RATE = % e o CONS I TOTAL INTRNAL ::J ORIG ECO/ RECON PERIODIC ROUTINE CONST & VEHICLE NET NET RATE OF LENGTH GEN FIN UPGRD MAIN I MAINT MAIN I OPERATING EXOGENOUS TOTAL PRES RETURN LINK (KM) ALI TRAF CSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS COMPARISON VALUE (%) IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO 17.0 NONE FIN ALT2 NO ECO ALT2 VS ALTO FIN ALT3 NO ECO ALT3 VS ALTO FIN IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO MANY FIN ALT2 NO ECO ALT2 VS ALTO 6.2 MANY FIN ALT3 NO ECO ALT3 VS ALTO MANY FIN IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO MANY FIN ALT2 NO ECO ALT2 VS ALTO MANY FIN ALT3 NO ECO ALT3 VS ALTO FIN GRAV ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO 83.6 NONE FIN ALT2 NO ECO ALT2 VS ALTO 76.9 NONE FIN ALT3 NO ECO ALT3 VS ALTO FIN

131 Exhibit 6-6 (cont). Evaluation of Alternatives... 1\) 88702/20 MEDIUM TRAFFIC REPORT TYPE 11 : PAGE 4 SUMMARY OF COSTS AND COMPARISONS BY DISCOUNT RATE : BASE IN MILLION DOLLARS DISCOUNT RATE = % CONST TOTAL INTRNAL ORIG ECO/ RECON PERIODIC ROUTINE CONST & VEHICLE NET NET RATE OF LENGTH GEN FIN UPGRD MAINT MAINT MAINT OPERATING EXOGENOUS TOTAL PRES RETURN LINK (KM) ALT TRAF CSTS COSTS COSTS COSTS COSTS COSTS COSTS COSTS COMPARISON VALUE (%) IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO 5.4 NONE ALT2 NO FIN ECO o ALT2 VS ALTO FIN ALT3 NO ECO ALT3 VS ALTO FIN IRI ALTO NO ECO FIN ALT1 NO ECO ALT1 VS ALTO 1.0 MANY FIN ALT2 NO ECO ALT2 VS ALTO 7.5 MANY FIN ALT3 NO ECO ALT3 VS ALTO 51.8 MANY FIN IRI ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO MANY FIN o ALT2 NO ECO o ALT2 VS ALTO MANY FIN ALT3 NO ECO ALT3 VS ALTO FIN GRAV ALTO NO ECO FIN ALTl NO ECO ALT1 VS ALTO 56.4 NONE FIN )> ALT2 NO ECO ALT2 VS ALTO 49.4 NONE :J FIN I ALT3 NO ECO ALT3 VS ALTO FIN s:: )> "C 12. c; -5" D.l :J 1 1, ~

132 An HOM Application 113 Exhibit 6-7a. Low Traffic- Good Paved Road Roughness (IRI) Years 0 Do-nothing + Patch 0 Reseal 6 Overlay Net Present Value ($ million) 4~ , ~~~~7-n--~~~~~n---~~~~ryn.---a==r"n/.~ ~---r ~--~ Annual Discount Rate 1ZZJ Patch 1S::SJ Reseal IZZ! Overlay

133 114 An HDM Application Exhibit 6-7b. Low Traffic - Fair Paved Road Roughness (IRI) Years 0 Do-nothing Patch Reseal "' Overlay Net Present Value($ million) % 6% 12% 20% Annual Discount Rate IZZI Patch ls:si Raseal I22Zd Overlay

134 An HDM Application 115 Exhibit 6-7c. Low Traffic- Poor Paved Road Roughness (IRI) Years 0 Do-nothing + Patch Reseal Overlay Net Present Value ($ million) % 8% 12% Annual Discount Rate Patch rz::zj ~ Reseal tz::zj Overlay

135 116 An HOM Application Exhibit 6-7d. Medium Traffic - Good Paved Road Roughness (IRI) Years 0 Do-nothing + Patch Reseal., Overlay Net Present Value ($ million) 0 0% II% 12% 20% Annual Discount Rate [ZZJ Patch cs::sj Reseal I22Zl Overlay

136 An HOM Application 117 Exhibit 6-7e. Medium Traffic - Fair Paved Road Roughness (IRI) Years 0 Do-nothing + Patch 0 Reseal a Overlay Net Present Value ($ million) Annual Discount Rate 1ZZJ Patch 1S:SJ Reseal!2ZZ3 Overlay

137 118 An HOM Application Exhibit 6-7f. Medium Traffic - Poor Paved Road Roughness (IRI) Years 0 Do-nothing + Patch 0 Reseal Overlay Net Present Value ($ million) Annual Discount Rate [2'ZJ Patch 1:s::SJ Reseal I22ZI Overlay

138 An HDM Application 119 Exhibit 6-7g. High Traffic - Good Paved Road Roughness (IRI) Years 0 Do-nothing Patch 0 Reseal Overlay 350 Net Present Value ($ million) % 8% 12% 20% Annual Discount Rate [ZZJ Patch IS:Sl Reseal I2LZI Ove~ay

139 120 An HOM Application Exhibit 6-7h. High Traffic - Fair Paved Road Roughness (IRI) Years 0 Do-nothing + Patch Reseal Overlay 400 Net Present Value ($ million) % 8% 12'!6 20% Annual Discount Rate IZZl Patch rs::sj Reseal I22Zl Overlay

140 An HOM Application 121 Exhibit 6-7i. High Traffic - Poor Paved Road Roughness (IRI) Years 0 Do-nothing + Patch 0 Reseal " Overlay Net Present Value ($ million) Annual Discount Rate [2'2] Patch rs::s1 Reseal l2iz! Overlay

141

142 Chapter7 Expenditure Budgeting Model This chapter presents the scope of the Expenditure Budgeting Model (EBM), the procedure for installing the model, the description of program commands, and an EBM demonstration run. The EBM Program* The Expenditure Budgeting Model is an optimization program used for selecting an optimal set of projects under multi-period budget constraints. The scope of the problem that EBM is designed to solve is described below. First, you can define a set of up to fifty projects (e.g., road links). Each project can contain up to five mutually exclusive project alternatives. Each alternative should have annual values of economic costs and benefits relative to some base case for a given project and absolute annual amounts of the resources needed to implement the alternative. Up to three resources can be defmed. All these inputs constitute the project data. Next, you can define a set of up to twenty budgetary periods, one constraint level per resource and budgetary period, and one discount rate for computing a net present value (NPV) for each project alternative. The time periods, the constraints, and the discount rate constitute the problem data. The EBM program examines the resources consumed and the NPV produced from the implementation of each project alternative. Within the constraint that it must choose only one alternative for each project, the program selects the group of alternatives that produces an optimal NPV within the resource constraint levels for the defined budgetary periods. This is the optimization process. In addition, the program allows preselection of a particular project alternative for any or all of the projects as part of the final solution. The program then selects alternatives for the remaining projects to produce the optimal NPV with the remaining uncommitted resources. The asterisked sections are adapted from The Highway Design and Maintenance Standards Model: Volume 2, User's Manual for the HDM-lll Model, pp

143 124 Expenditure Budgeting Model The project data are defined only once, while the problem data may be defmed somewhat differently for each optimization. Consequently, the project data can be stored in an ASCII text file before the EBM begins execution and then be read once by the EBM program. The problem data, however, can be defined interactively (i.e., on-line) so that it can be changed repeatedly. The EBM program is particularly useful when used in conjunction with the HDM program. The EBM program reads the problem data generated by the HDM program and finds the optimal maintenance policy for a group of road links under budgetary constraints. When used with the HDM program, an EBM problem may be defined as shown in Table 7-1. Table 7-1. Road Network under Budgetary Constraints Maintenance alternatives Link 1 Link 2 Link 3 Link 4 Link 5 Link 6 Possible maintenance alternatives ALTO ALTl ALT2 ALT3 ALTO ALTO ALTl ALT2 ALT2 ALTO ALTl ALT2 ALT3 ALTO ALT3 ALTO ALTl ALT3 HDM solution for no budgetary constraints ALT2 ALTl ALT2 ALT3 ALTO ALT3 EBM solution for moderate budgetary constraints ALT2 ALTO ALT2 ALT2 ALTO ALTl EBM solution for severe budgetary constraints ALTl ALTO ALT2 ALTO ALTO ALTO The EBM program was originally developed for mainframe computers. The personal computer version differs from the mainframe version as shown in Table 7-2. Note: The number of alternatives and budgetary periods have been reduced from the mainframe version because of the 640K memory limit imposed by DOS.

144 Expenditure Budgeting Model 125 Table 7-2. EBM Program for Mainframe vs. Personal Computers Capabilities Maximum number of projects Maximum number of alternatives Maximum budgetary periods Optimization technique: TOTE method AHMED method Dynamic programming Mainframe Yes Yes Burroughs only Personal computers Yes Yes No Installing the EBM Program To install the program on your hard disk, create a directory called EBM and copy all the files supplied on the HDM-PC program disk 7 to that directory. Follow the steps below. 1. Turn your computer on and at the DOS prompt C >, create a directory for EBM with the command: C>MD\EBM 2. Change directory to EBM with the command: C>CD\EBM 3. Place the disk labelled EBM Program Disk in drive A and enter: C>COPY A:*.* Once all files have been copied, the EBM program is ready for use. Before you proceed further, check that the following files have been copied to your hard disk by using the DOS DIR command: EBM.EXE EBMDESC.DAT EBMHELP.DAT EBMSTD.DAT EBMTEST.TXT Using the EBM Program EBM program EBM description EBM help file EBM standard options EBM demonstration run data file The EBM program requires the full 640K of RAM. Therefore it is essential that no memoryresident program be loaded while working with the EBM program. To start the program, follow the steps below. 1. Change to the EBM directory by using the DOS command: C>CD\EBM 2. Run the program with the command: C>EBM

145 126 Expenditure Budgeting Model If the program fails to load, either you do not have a full 640K of RAM on your system or you have a memory-resident program loaded up. If you have the full640k of RAM, boot the system and bring it up without memory-resident programs and try the above two steps again. If the EBM is loaded successfully, the program displays the EBM logo, a screen with some reminders and instructions, and the prompt = = >. At this prompt, enter your input data and commands. After checking that your input is valid, the program either performs the required action and returns to the = = > prompt or gives an error message (described at the end of this chapter) and returns to the prompt. If you do not want to enter your input data or commands in an interactive mode, you can store the input data and a series of commands in an ASCII text file and read this information from the EBM prompt. To get help, enter the command HELP HELP at the EBM prompt. To exit the program, enter BYE at the EBM prompt. General Format of Commands and Input Data An input line is 72 characters long and all commands except the NAME RESOURCE command are format free, that is, additional spaces between names and numbers do not matter. An input line is composed of names, numbers, and delimiters, defined as follows: Name. A string ofletters (A-Z) and/or digits (0-9) that begins with a letter. Number. A string of digits (0-9) with or without a decimal point and with or without a mmus stgn. Delimiter. A space, a comma, or a hyphen. One or more of these must be used to separate one name or number from another. Names are used for commands, project names, and alternative names. Only the first four characters of a name are significant. Hence all project and alternative names are only four characters long and all commands can be reduced to the first four characters of each word. A name must not begin with a number. When entering numeric data, items with value 0 must be entered if they precede items with non-zero values; but items with value 0 following the last non-zero data item may be omitted. For example: ANNUAL VALUES may be reduced to ANNUAL VALUES but not to ANNUAL VALUES A special type of input line is the comment line. If an asterisk (*) appears in the first column, the program treats that line as a comment and ignores it. Note: In the following sections, when a word in a command is surrounded by angle brackets, e.g., <year-]>, you must supply an appropriate value. Wizen a word is capitalized and not surrounded by brackets, the word should be used exactly as it appears in the definition.

146 Expenditure Budgeting Model 127 The Input Data * The EBM program requires two types of input data: 1. The project data, consisting of a set of projects and project alternatives with annual values for economic costs and benefits. These values are relative to some base case for a given project and absolute amounts of resources necessary to implement the alternative. 2. The problem data, consisting of a set of budgetary periods, one constraint level per resource, and a discount rate to compute the NPV. The Project Data The project data are usually defined once and stored in an external ASCII text file which may then be read in by the program. A typical project data file created by the HDM program is shown in Exhibit 7-1. Exhibit 7-1. Sample Project Data File PROJECT PV01 MAINTENANCE ALTERNATIVE ALOO ANNUAL VALUES ALTERNATIVE ALTl ANNUAL VALUES PROJECT PV02 MAINTENANCE ALTERNATIVE ALOO ANNUAL VALUES ALTERNATIVE ALT1 ANNUAL VALUES A maximum of fifty projects (links) can be defined for a single run of the EBM program and each project can consist of up to five mutually exclusive alternatives. Each project is given a four-character project name (e.g., PVOl) and is defined as one of these three types: maintenance, new, or ongoing. * See footnote p. 123.

147 128 Expenditure Budgeting Model Maintenance Projects The data for a maintenance project are specified as: PROJECT <name> MAINTENANCE ALTERNATIVE <name 1 > ANNUAL VALUES < year-1 > < costs> <benefits > < res1 > < res2 > < res3 > < year-2 > <costs> <benefits> < res1 > < res2 > < res3 > <year-n> <costs> <benefits> < res1 > < res2 > < res3 > ALTERNATIVE <name 2 > ANNUAL VALUES < year-1 > < costs> <benefits > < res1 > < res2 > < res3 > < year-2 > <costs> <benefits> < res1 > < res2 > < res3 > <year-n> <costs> <benefits> < res1 > < res2 > < res3 > ALTERNATIVE <name n > ANNUAL VALUES <year-1> <costs> <benefits> <res1> <res2> <res3> < year-2 > <costs> <benefits> < res1 > < res2 > < res3 > <year-n> <costs> <benefits> < res1 > < res2 > < res3 > Each alternative has a four-character name and up to twenty years of annual data. The annual data consist of economic costs, economic benefits, and annual requirements for resource 1, resource 2, and resource 3. Economic costs and benefits are relative to some base which may or may not be present as an alternative. Note that in the project data file shown in Exhibit 7-1 there are two projects (PVOl and PV02), each project has two maintenance alternatives (ALOO and ALT1) and each maintenance alternative has data for four years. In this case, only two resources are being used so the values for the third resource are not specified. Note also that the EBM input is in free format. This means that the input variables can be located in any column. If all fifty projects, five alternatives, and twenty budgetary periods are used, the project data file becomes quite large. The HOM program, however, can be used to create this file directly. New Projects New projects differ from the maintenance projects only in that a zero-resource, zero-npv Donothing baseline alternative is automatically generated for new projects. The baseline alternative for a maintenance project is non-zero, that is, it is a minimum maintenance operation that incurs some positive resource consumption and a non-zero NPV. Therefore, this baseline cannot be automatically defined for maintenance projects..

148 Expenditure Budgeting Model 129 The data for a new project are specified as: PROJECT <name> NEW (alternative 1 data ) (alternative 2 data ) (alternative n data) Ongoing Projects Ongoing projects by definition have only a single base case and a penalty table. The penalty table specifies an additional non-recoverable financial cost for stopping an ongoing project after the Ith year of the project and not restarting the project for J years where, I = 1 to 4 and J = 1 to 3. In addition, a penalty may be specified if the project is to be abandoned altogether after the Ith year of the project. The data for an ongoing project are entered as follows: PROJECT <name> ONGOING ANNUAL VALUES < year-1 > <costs> <benefits> < rcs1 > < res2 > < res3 > < year-2 > <costs> <benefits> < res1 > < res2 > < rcs3 > <year-n> <costs> <benefits> < res1 > < res2 > < res3 > PENALTY TABLE < after-year-1 > < delay-1 > < delay-2 > < delay-3 > <abandoned> <after-year-i> <delay-1> <delay-2> <delay-3> <abandoned> Note that no alternative name need be specified for the base case of the ongoing project. There will be one alternative, generated automatically, for each non-zero entry in the penalty table. All alternative names are assigned by the EBM program. The Problem Data The problem data consist of time periods (up to twenty), resources (up to three), resource constraints (one per resource and time period), a discount rate for computing net present values, and preselected project alternatives (if any). Time Periods The TIME PERIODS command specifies all time periods and has the following form: TIME PERIODS <beginning year-end year> <beginning year-end year>... The years may be calendar years or relative years. Example : TIME PERIODS TIME PERIODS Time periods may be continued on another line without respecifying the TIME PERIODS command and may be one or more years in length. However, time periods must be specified before entering resource constraint levels, and time periods must neither overlap nor leave any gap between successive periods.

149 130 Expenditure Budgeting Model For example, the following time periods are invalid: TIME PERIODS TIME PERIODS Resource Constraints Overlapping Gaps left The commands for entering resource constraint levels are: RESl <constraint-!> < constraint-2>... < constraint-n > RES2 <constraint-!> < constraint-2>... < constraint-n > RES3 <constraint-!> < constraint-2>... < constraint-n > where n is the number of defined time periods. Like time periods, the constraint levels may be continued on another line if necessary, without respccifying the resource command. The names of these commands (RESl, RES2, RES3) can be changed by using the NAME RESOURCE command which has the following format: NAME RESOURCE< n > <command name> <description> where n = 1, 2, or 3. The NAME RESOURCE command is the only command that is sensitive to extra spaces. The command name must begin in column 17 and may be up to ten characters long, including at least one space (in column 27); the description must begin in column 28 and may be up to twenty-four characters long. Once the NAME RESOURCE command has been used for a given resource, the command name will be recognized as the command for defining the constraint level for that resource. For example, the following lines will rename resource 1 to be financial costs (with command name FINANCIAL) and will define the constraint in period 1 to be 10,000 and the constraint in period 2 to be 20,000. NAME RESOURCE 1 FINANCIAL FINANCIAL COSTS FINANCIAL Discount rate A discount rate is defined with the command: Example: DISCOUNT RATE <percentage> DISCOUNT RATE 12 Preselected Project Alternatives I COL17 I COL28 You can preselect an alternative for a project as part of the solution. Project alternatives can be preselected with the following command: PRESELECT < prjname-altname > < prjname-altname > < prjname-altname > where prjname-altname is a four-letter valid project name and a four-letter alternative name separated by a hyphen (-). If more than one project alternatives are selected for the same project, the last alternative specified will be used. Any number of projects can have preselected alternatives.

150 Expenditure Budgeting Model 131 The Input File * All of the project and problem data can be entered initially through an ASCII text file. However, new problem data such as new resource constraints or discount rates, may be entered interactively before each optimization. The general format of an input file is as follows: <NAME RESOURCE command> optional PROJECT <name> <type, either NEW or MAINTENANCE> ALTERNATIVE <name> < annual values > PROJECT <name> ONGOING < annual values> PENALTY TABLE TIME PERIODS <time periods> <resource name> <resource constraints> DISCOUNT RATE <percentage> END INPUT FILE Note: The resources should be named first, unless the default resources RESJ, RES2, and RES3 are used. Projects (links) can be entered in any order as can the altematives, but the time periods must be specified before the resource constraints. 17zis file can be created with a text editor capable of creating ASCII text files or, if you are using the EBM to analyze an HDM nm, the files created by the HDM program can be used. To read the infonnation contained in this file, use the READ INPUT command that requests the name of the file to read. The Standard Options File You may opt to store some standard commands that you use repeatedly in an ASCII text file that is read whenever the STANDARD OPTIONS command is used. For example, you may choose to name resource 1 BUDGET and resource 2 CAPACITY in this file, so that after entering the STANDARD OPTIONS command, you can use the following commands subsequently to enter resource constraint levels: BUDGET CAPACITY <constraint 1 > < constraint 2 >.... <constraint 1 > <constraint 2 >.... Similarly, commands such as DISCOUNT RATE or PRESELECT also can be included in this file as standard options. Notes: When the input data are made up, it is important to ensure that the various projects are independent of each other and their a/tematives are mutually exclusive. Thus, when specifying new construction projects, maintenance altematives should be part of the mutually exclusive altematives of the project. Specifying a separate maintenance project is an e"or because it then becomes independent of the new construction project. * See footnote p.123.

151 132 Expenditure Budgeting Model The READ INPUT FILE command simply instntcts the program to read off commands from an external file. Since the name of the data file has to be provided when this command is invoked, it is possible to optimize with a certain number of projects (from one file), then enlarge the data set (by reading from another file), and optimize again. This feature can be useful to simulate the effect of tightly constrained regional budgets as opposed to a country-wide budget. However, the maximum limits of projects and alternatives cannot be exceeded. The Optimization * The OPTIMIZE command causes the EBM to select project alternatives that produce the optimal NPV for a set of projects, given the resources required for each project alternative and the resource constraints for each time period. A report of the results is displayed automatically. Optimization cannot be performed unless all of the following conditions are met: At least one project, one time period, and one resource have been defined. The time periods are properly defined (without overlapping periods or gaps between the periods). The resources required for the preselected alternatives do not exceed the resource constraints. The minimum resources required to implement one alternative for each of the projects do not exceed the resource constraints. The constraint for each resource and time period is greater than zero. Two optimization methods can be used: an exhaustive search useful for small problems (TOTE) and a more limited search useful for large problems (AHMED). Unless overridden, the program will choose automatically between the exhaustive search and the modified search algorithms based on problem size. However, the OPTIMIZE command also allows you to specify the algorithm to be used. The format of the command is: OPTIMIZE <type> where <type> = TOTE, AHMED, or blank. The total enumeration method, TOTE conducts an exhaustive search of all alternatives. It is quite time-consuming and is therefore suitable for very small or highly aggregate analyses. The AHMED method can deal with large problems, including multiple constraints in conjunction with as many as twenty time periods. However, like any other heuristic method, it cannot guarantee an exact optimal solution. An important characteristic of this method is that it does not directly trade off the alternatives of one project with those of another. This happens indirectly as alternatives within each project are traded off. As a consequence, the algorithm can sometimes fail to find an initial feasible solution. To deal with this problem, slight modifications were made to AHMED's original formulation, focussing its search for an initial feasible solution on those alternatives that provide a reduction of at least one critical resource, and, if necessary, going to the project with the next higher effective gradient without dropping the current project. * See footnote p.123.

152 Expenditure Budgeting Model 133 As a result, only rarely does the modified algorithm fail to find a feasible solution. Should it happen, project alternatives should be preselected according to the following guidelines: 1. Find the most binding constraint - R T. 2. Find the project alternatives that have a low NPV/A ratio, where A = amount of most tightly constrained resource used by the alternative. 3. Preselect the DONT alternative (i.e., do not implement) or the base alternative (if a maintenance project) and then optimize. Other Commands * Send Command The SEND command is used to redirect the output to the screen or printer. By default, all output is directed to the screen. To send the output to a printer, use the SEND OUTPUT TO PRINTER command. The SEND OUTPUT TO TERMINAL command displays all output on the screen. Print Command The EBM program allows you to display the input data or the problem data by using the PRINT command. To redirect the output to the printer, use the SEND OUTPUT TO PRINTER command. The PRINT INPUT command will print the project data showing annual costs for economic costs, economic benefits, and resource requirements for a given project or alternative. It can also print a summary of the data entered for all project alternatives. The PRINT PROBLEM command will print the project data as they are used in the optimization, i.e., all annual data are aggregated by budget period and NPV, computed using the current discount rate. It can also print a summary of the problem data including the resource constraints, discount rate, and preselected project -alternative choices. The formats of the print commands are: PRINT INPUT < prjl-altl > < prj2-alt2 > PRINT INPUT < prjl > ALL PRINT INPUT ALL PRINT INPUT SUMMARY PRINT INPUT <prj 1 > PT AB Prints the annual values for the project -alternatives prjl-altl and prj2-alt2. Prints all alternatives for project prjl. Prints all the project project -alternatives. Prints a summary of input data for all the projects. Prints just the penalty table for project prjl if prjl is an ongoing project.. * See footnote p.123.

153 134 Expenditure Budgeting Model The PRINT PROBLEM command works the same way as the PRINT INPUT command, except that instead of printing annual values it prints out the total resources required for each time period and the computed net present value. Read Input File Command The READ INPUT FILE command causes an ASCII text file to be read from the disk. All input data and commands in this file will be executed as if they were typed in interactively. If an END INPUT FILE is encountered, no more commands will be read off from the file, and the next command will be read off the terminal. Standard Options Command The STANDARD OPTIONS command causes the program to read a standard options file in which you can store a standard set of commands to be used while running the EBM program. The STANDARD OPTIONS command will cause the program to read commands off a file named EBMSTD.DAT. Therefore, in order to use this command, the file EBMSTD.DAT must be on your default directory (i.e., the EBM directory). Keep and Show Commands The KEEP command will save all commands and comments as a record of work in a session (until turned off by another KEEP command). The SHOW command will output these on the screen. Once the SHOW command has been used, all old commands will be erased and only commands issued after the SHOW command will be kept. Save Command The SAVE command saves the results of the optimization done in a session. When this command is issued, you will be prompted to enter the name of a file where the results are to be saved. All output from the optimization will then be directed to this file (until turned off by another SAVE command). This file may be printed later for closer study of the results. NPV The NPV command allows the benefits and costs to be input as a single number, the net present value (NPV). The NPV is input instead of a yearly stream of benefits and costs. The streams of resources, however, must be entered as usual. The option is automatically turned off each time a new project is input, unless the NPV ALL command is given. Help Command The HELP command provides on-line documentation for the EBM program. The HELP command has the following formats: HELP HELP HELP <command name> HELP ALL Prints a table of command formats and size parameters for the program. Given the first word of a command name, the program prints a one paragraph description of that command. Prints a description of all commands.

154 Expenditure Budgeting Model 135 Bye Command The BYE command terminates the EBM session. HDM Interface Series K of the HDM program controls the preparation of data for interfacing with the EBM program. The Budget card (K-105) is used either: 1. To create a special benefit-cost output file, consisting oflink-alternative comparisons in a form that may be used directly by the EBM program, or 2. To reclassify the costs of certain maintenance operations as capital or recurrent costs. This reclassification may then be used in the output file prepared by the EBM program. By default, preventive treatment, resealing, overlaying, pavement reconstruction, and gravel resurfacing arc classified as capital expenditures. Patching, grading, and spot regravelling on the other hand are classified as recurrent expenditures. By specifing the appropriate switch (Cor R), any maintenance alternative may be reclassified in the Budget (K-105) card. The Base Alternative If the HDM outputs are going to be used by the EBM program, projects (links) are then defined as MAINTENANCE and the benefits are reported as net benefits relative to a base alternative specified in the Budget card (K-105) in series K of the HDM inputs. To allow for the possibility that a non-zero base alternative may be chosen in the optimization, it is essential that the base alternative be included as one of the maintenance alternatives. This is done by defining in series G of the HDM program a link alternative that is identical to the desired base alternative but has a different ID code. In this way, the base alternative (with zero net benefits compared with itself but normally non-zero resource costs) will also be included in the project data for that particular link. HDM Inputs for EBM Demonstration Run For the HDM application described in Chapter 6, to obtain the project data required by the EBM program, you have to modify series K and G. For the medium traffic case, the new series K and G, H, I, J are shown in Exhibits 7-2 and 7-3. The X in card K-105 indicates that exogenous costs will be treated as recurrent costs, while NULL indicates that all base alternatives will be assigned NULL as the ID code. Program defaults are used for other maintenance alternatives. Note: For each link, a new maintenance altemative (NULL) is created, by adding card GJOJ, that is identical to the Do-nothing maintenance altemative ALTO (the desired base altemative) and that is defined in series K of HDM as the base a/tentative. With this setup, alternative ALTO (equal to NULL) is the base alternative and the project data created by the HDM program will contain alternative ALTO as one of the possible maintenance options. In this HDM run, financial costs (report 6) are requested for all link alternatives. The resources used by each alternative are computed from the financial costs and the benefits from the economic costs.

155 136 Expenditure Budgeting Model Exhibit 7-2. Modified Series K File for EBM Program File= TUTORK4.TXT Series K : RUN CONTROL INFORMATION RUN TITLE MEDIUM I EBM RUN BRAZ DATE CURRENCY 88 DOLLARS DOLLARS ROUGHNESS IR BUDGET NULL X READ: ALL DATASETS SCAN: ALL DATASETS ECHO PRINT: ALL DATASETS SUPPRESS OUTPUT REPORTS: REPORT 7 REPORT 8 REPORT 9 REPORTlO REPORTll MODELLING EVALUATION END SERIES KlOl K K103 QI K104 K105 K106 K107 K109 K107 Klll K107 Kll2 Kll3A K113B K113C Kl13D Kll3E 0 K114 K115 Kll6

156 Expenditure Budgeting Model 137 Exhibit 7-3. Modified Series G, H, I, J File for EBM Program File = TUTORG4.TXT Series G,H,I and J ALTERNATIVE IRI2NULL GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP01988 GlOS ALTERNATIVE IRI2ALTO GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP01988 GlOS ALTERNATIVE IRI2ALT1 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP11988 GlOS ALTERNATIVE IRI2ALT2 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP21988 GlOS ALTERNATIVE IRI2ALT3 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP31988 GlOS ALTERNATIVE IRI4NULL GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP01988 GlOS ALTERNATIVE IRI4ALTO GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP01988 GlOS ALTERNATIVE IRI4ALT1 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP11988 GlOS ALTERNATIVE IRI4ALT2 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP21988 GlOS ALTERNATIVE IRI4ALT3 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP31988 GlOS ALTERNATIVE IRI7NULL GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP01988 GlOS ALTERNATIVE IRI7ALTO GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP01988 GlOS ALTERNATIVE IRI7ALT1 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP11988 GlOS ALTERNATIVE IRI7ALT2 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP21988 GlOS ALTERNATIVE IRI7ALT3 GlOl TRAFFIC PMED1988 Gl02 MAINTENANCE STP31988 GlOS

157 138 Expenditure Budgeting Model Exhibit 7-3 (coot). Modified Series G, H, I, J File ALTERNATIVE GRAVNULL TRAFFIC UMED1988 MAINTENANCE STU01988 ALTERNATIVE GRAVALTO TRAFFIC UMED1988 MAINTENANCE STU01988 ALTERNATIVE GRAVALT1 TRAFFIC UMED1988 MAINTENANCE STU11988 ALTERNATIVE GRAVALT2 TRAFFIC UMED1988 MAINTENANCE STU21988 ALTERNATIVE GRAVALTJ TRAFFIC UMED1988 MAINTENANCE STU01988 CONSTRUCTIONCNST1990 MAINTENANCE STP11991 END SERIES GROUP ALTERNATIVE GPAVALTO LINK-ALT IRI2ALTO IRI4ALTO GROUP ALTERNATIVE GPAVALT1 LINK-ALT IRI2ALT1 IRI4ALT1 GROUP ALTERNATIVE GPAVALT2 LINK-ALT IRI2ALT2 IRI4ALT2 GROUP ALTERNATIVE GPAVALTJ LINK-ALT IRI2ALT3 IRI4ALT3 GROUP ALTERNATIVE GUNPALTO LINK-ALT GRAVALTO GROUP ALTERNATIVE GUNPALTl LINK-ALT GRAVALTl GROUP ALTERNATIVE GUNPALT2 LINK-ALT GRAVALT2 GROUP ALTERNATIVE GUNPALTJ LINK-ALT GRAVALTJ END SERIES LINK IRI2 ALTERNATIVE ALTO FINANCIAL COSTS LINK IRI2 ALTERNATIVE ALT1 FINANCIAL COSTS LINK IRI2 ALTERNATIVE ALT2 FINANCIAL COSTS LINK IRI2 ALTERNATIVE ALTJ FINANCIAL COSTS LINK IRI4 ALTERNATIVE ALTO FINANCIAL COSTS LINK IRI4 ALTERNATIVE ALTl FINANCIAL COSTS LINK IRI4 ALTERNATIVE ALT2 FINANCIAL COSTS LINK IRI4 ALTERNATIVE ALTJ FINANCIAL COSTS G101 G102 G105 G101 G102 G105 G101 G102 G105 G101 G102 G105 G101 G102 G105 G103 G105 GlOB H101 IRI7ALTO H102 H101 IRI7ALT1 H102 H101 IRI7ALT2 H102 HlOl IRI7ALT3 H102 Hl01 H102 H101 H102 H101 H102 H101 Hl02 H104! I ! !102! !102 IlOl !102! !102! !102! !102.,

158 Expenditure Budgeting Model 139 Exhibit 7-3 (coot). Modified Series G, H, I, J File LINK IRI7 ALTERNATIVE ALTO FINANCIAL COSTS LINK IRI7 ALTERNATIVE ALTl FINANCIAL COSTS LINK IRI7 ALTERNATIVE ALT2 FINANCIAL COSTS LINK IRI7 ALTERNATIVE ALT3 FINANCIAL COSTS LINK GRAV ALTERNATIVE ALTO FINANCIAL COSTS LINK GRAV ALTERNATIVE ALT1 FINANCIAL COSTS LINK GRAV ALTERNATIVE ALT2 FINANCIAL COSTS LINK GRAV ALTERNATIVE ALT3 FINANCIAL COSTS END SERIES STUDY BASE COMPARE ALTl GPAV ALT2 GPAV ALT3 GPAV ALTl GUNP ALT2 GUNP ALT3 GUNP DISCOUNT RATES END STUDY END SERIES ALTO ALTO ALTO ALTO ALTO ALTO !101!102!101!102!101!102!101!102!101!102!101!102!101!102!101!102!109 J101 J102 J103 J103 J103 J103 J103 J103 J106 J107 J108

159 140 Expenditure Budgeting Model The files for series K (TUTORK4.TXT), series G, H, I, J (TUTORG4.TXT), and the Run Control File (TUTORUN4.TXT) required to obtain the EBM data for medium traffic are supplied on the HDM disks. The output from this run should be used as the input for the demonstration run of the EBM program. Running the EBM Program To the run the EBM program, follow the steps below: 1. Turn the computer on and at the DOS prompt enter: C>CD\EBM 2. Start the program by entering: C>EBM The EBM program will display the logo shown in Figure 7-1. Figure 7-1. EBM Logo EEEEEEEEEEE BBBBBBBBBBB MMMMM MMMMM EEEEEEEEEEE BBBBBBBBBBBBB MMMMMM MMMMMM EEEE BBBB BBBB MMMMMMM MMMMMMM EEEEEEEE BBBBBBBBBBB MMMMMMMM MMMMMMMM EEEEEEEE BBBBBBBBBBB MMMM MMMMMMM MMMM EEEE BBBB BBBB MMMM MMMMM MMMM EEEEEEEEEEE BBBBBBBBBBBBB MMMM MMM MMMM EEEEEEEEEEE BBBBBBBBBBBB MMMM MMHM EXPENDITURE BUDGETING MODEL THE WORLD BANM Do you wish to see the inst~uctions Y/H? 3. Press the Enter key to continue and the program will prompt: Do you wish to see any instructions : 4. Enter Y to see the instructions and the screen in Figure 7-2 will appear. 5. Press the Enter key to proceed and a second screen displaying the rest of the instructions appears (see Figure 7-3). 6. Press the Enter key again and the = = >prompt appears on the screen.

160 Expenditure Budgeting Model 141 Figure 7-2. EBM Instructions Screen 1 Welcome to the Expenditure Budgeting Model (2.0). This is a tool to help you solve large capital budgeting problems. The limitations of the program are as follows: NUMBER OF PROJECTS ALTERNATIVES PER PROJECT YEARS PER PROJECT ALTERNATIVE TIME PERIODS RESOURCES In no event should an attempt be made to run the program if the above specifications are execeeded. The prompt ~ > is the command line of the program and you have to type all your commands next to this prompt. On line help is available by typing in HELP HELP. If you wish to get help on a specific command then type HELP )()()()()()( where)()()()()()( is the command you wish to get help on. Figure 7-3. EBM Instructions Screen 2 Before you proceed here are some commonly used commands. HELP HELP READ TIME PERIODS 1-4 DISCOUNTRATE 10 PRINT INPUT PRINT PROBLEM SEND OUTPUT TO PRINTER OPTIMIZE RES SAVE KEEP SHOW BYE (displays the syntax of help commands) (reads data from an input file) (sets the time periods) (establishes the discount rate) (prints your input data) (prints the problem summary) (routes all output to printer) (performs the default optimization) (constraints on the resources) (save results in a disk file) (stores all your commands) (displays all commands issued) (terminates the program) 7. Start off by reading in the project data from the demonstration file provided, using the Read Input File command: = = >READ INPUT FILE The program prompts: 8. Enter: Please enter name of data file = > EBMTEST.TXT

161 142 Expenditure Budgeting Model The program displays the message: STARTING TO READ INPUT FILE EBMTEST.TXT After a short wait, the program displays: END READING FILE 0 ERRORS FOUND The EBMTEST.EBM file contains the project data obtained from running the HDM program with the tutorial run data (use the Run Control File TUTORUN4.TXT) for medium traffic. Once all the project data are read, the next step is to define the problem data interactively. 9. Defme the time periods: ==>TIME PERIODS Enter the capital (RES1) and recurrent (RES2) expenditure constraints for each time period. Enter very high constraints levels to obtain the solution for the unconstrained case: = = >RES = = >RES Define the discount rate: = = >DISCOUNT RATE Display the annual data summary: (Exhibit 7-4). = = >PRINT INPUT Exhibit 7-4. EBM Annual Data Summary ANNUAL DATA : SUMMARY PROJECT TYPE FIRST LAST YEARS ALTERNATIVE YEAR YEAR OF DATA IRI2 IRI4 IRI7 GRAV MAINTENANCE MAINTENANCE MAINTENANCE MAINTENANCE ALTO ALTl ALT ALT ALTO ALTl ALT ALT ALTO ALTl ALT ALT ALTO ALTl ALT ALT

162 Expenditure Budgeting Model Send the output to the printer with the SEND OUTPUT TO PRINTER command: = = >SEND OUTPUT TO PRINTER The program displays the message: OUTPUT WILL BE SENT TO THE PRINTER Note: In this demonstration rnn, maintenance costs and exogenous costs are considered recu"ent expenditures, while constrnction costs are treated as capital expenditures. It is important that a careful distinction be made between capital and recu"ent expenditures when using the EBM program. In some cases, periodic maintenance is classified as a capital expenditure. 14. Print the problem data summary (Exhibit 7-5): ==>PRINT PROBLEM SUMMARY PROBLEM DATA : SUMMARY Exhibit 7-5. Problem Data Summary RESOURCE CONSTRAINT NAME PERIOD LEVEL RES RES DISCOUNT RATE = 12.0 % PREDETERMINED PROJECT CHOICE ALTERNATIVES DEFINED IRI2 IRI4 IRI7 GRAV ALTO ALTl ALT2 ALT3 ALTO ALTl ALT2 ALT3 ALTO ALTl ALT2 ALT3 ALTO ALTl ALT2 ALT3 15. Turn on the switch for saving the optimization results with the SAVE command. The program prompts: Please enter name of file to save optimization results = > 16. Enter EBMOPTI.OUT

163 144 Expenditure Budgeting Model 17. Issue the command to perform the optimization (Exhibit 7-6). = = >OPTIMIZE Exhibit 7-6. EBM Optimization No. 1 OPTIMAL SOLUTION (METHOD TOTE) : ALTERNATIVE PREDETERMINED NET PRESENT RATIO OF PROJECT SELECTED CHOICES VALUE NPV/COST IRI2 ALT IRI4 ALT IRI7 ALT GRAV ALT TOTAL NPV TOTAL NPV/COST = AT 12.0% DISCOUNT (NOTE: NPV/COST IS SHOWN AS 0.0 IF ECONOMIC COST IS 0.0 RESOURCE CONSTRAINT OPTIMAL NAME PERIOD LEVEL LEVEL RES RES RESOURCE RESOURCE YEAR Note that for this unconstrained case (constraint levels much higher than optimal levels) the best alternative for all links is alternative ALT3 (the HDM solution).

164 Expenditure Budgeting Model Reduce the capital available to per period. = = > RES Once again, perform the optimization (Exhibit 7-7) with the OPTIMIZE command. Exhibit 7-7. EBM Optimization No.2 OPTIMAL SOLUTION (METHOD TOTE) ALTERNATIVE PREDETERMINED NET PRESENT RATIO OF PROJECT SELECTED CHOICES VALUE NPV/COST IRI2 ALTl IRI4 ALT IRI7 ALT GRAV ALT TOTAL NPV AT 12.0% DISCOUNT TOTAL NPV/COST = (NOTE: NPV/COST IS SHOWN AS 0.0 IF ECONOMIC COST IS 0.0) RESOURCE CONSTRAINT OPTIMAL NAME PERIOD LEVEL LEVEL RESl RES RESOURCE RESOURCE YEAR Note that with the per period capital constraint, the best alternative for link IRI2 has changed to ALT1; and the NPV is

165 146 Expenditure Budgeting Model 20. Next, reduce the capital available and recurrent expenditure to per period. = = > RESl = = >RES Perform the optimization. (Exhibit 7-8) with the OPTIMIZE command. Exhibit 7-8. EBM Optimization No.3 OPTIMAL SOLUTION (METHOD TOTE) : ALTERNATIVE PREDETERMINED NET PRESENT RATIO OF PROJECT SELECTED CHOICES VALUE NPV/COST IRI2 ALTl IRI4 ALT IRI7 ALT GRAV ALT TOTAL NPV AT 12.0% DISCOUNT TOTAL NPV/COST (NOTE: NPV/COST IS SHOWN AS 0.0 IF ECONOMIC COST IS 0.0) RESOURCE CONSTRAINT OPTIMAL NAME PERIOD LEVEL LEVEL RESl RES RESOURCE RESOURCE YEAR ,

166 Expenditure Budgeting Model 147 Note that, in this case, the best alternative for link IRI4 has changed to alternative ALT2 and the NPV is reduced to Note also that the capital expenditure for periods 3 and 5 is now (considerably less than that for periods 1, 2, and 4). If capital expenditures are to be evenly distributed over all periods, you must create new maintenance alternatives with higher capital expenditures in periods 3 and 5 (for example, postponing overlay for five years). If a capital resource constraint of per period or lower is entered, the program will not find a feasible solution. 22. Next send the output back to the terminal with the command: = = >SEND OUTPUT TO TERMINAL The program displays the message: OUTPUT WILL BE SENT TO YOUR TERMINAL 22. After all the optimizations are done, turn off the save switch with the command: ==>SAVE The program displays the message: STOPPED OPTIMIZATION RESULTS IN FILE EBMOPTI.OUT 23. Finally, exit the program with the command: ==>BYE Note: For additional samples of EBM rnns, refer to the HDM-Ill User's Manual. EBM Commands Reference < resnamel > <constraint-!> < constraint-2 >... < constraint-n > Defines the resource constraints for resource < resnamel >. A non-zero constraint must be defined for each defined time-period (maximum 13 per line). <resnamel> < constraint -1 > <constraint -2 > < constraint-n > resource name defined by NAME RESOURCE command (or resl by default). constraint for time period 1. = constraint for time period 2. = constraint for time period n. Similarly for resname 2 (res2) and resname 3 (res3) ALTERNATIVE <name> Starts the definition of a project-alternative by specifying the alternative name. < name> = up to 4 alphanumeric characters Note that only one base alternative can be defined for an ongoing project. ANNUAL VALUES <year> < ec > < eb > < resl > < res2 > < res3 > Defines the input data for one year of a project-alternative.

167 148 Expenditure Budgeting Model <year> <ec> <eb> <resl> <res2> <res3> up to 4 digits economic costs economic benefits amount of resource 1 expended amount of resource 2 expended amount of resource 3 expended The keywords ANNUAL VALUES are optional after the first card for a given project-alternative. Consistent units of measure must be used for all alternatives of all projects. Economic costs and economic benefits must use the same units. Each resource may use a different unit. Note: When using project data from the HDM program, the benefits come from the economic costs and the resources from the financial costs. BATCH BYE Causes all input lines from the terminal file to be printed. Should always be used as the first card input when running in batch. Ends the program. DISCOUNT RATE <percentage> Defmes the discount rate in percent to be used when computing net present values for optimization. END INPUT FILE Command located in an input data file. Ends the reading of data from the input file. HELP <command>. KEEP Prints documentation for each command. < command> = the first word of the command. If HELP HELP command is given, the format for all commands will be printed. If < command> = ALL, then all available documentation will be printed. Starts saving all commands and comments if the program had not been saving them, and stops saving them if it had. NAME RESOURCE < n > <command-name> <description> Defmes the command name and report title for resource < n >. <n> 1, 2, or 3 <command name> one word of up to ten characters; only first four characters will actually be used <description> description for resource of up to twenty-four characters beginning in column 28; description will be split into two twelve-character lines on reports

168 Expenditure Budgeting Model 149 NPV Changes NPV option. If ON, turns off and if OFF, turns on. If ON, allows input for current project simply as NPV and the annual stream of resource costs; if OFF, then inputs must include the time stream of benefits and costs. NPV ALL Allows input in NPV format for all projects when turned ON. PENALTY TABLE < after-yr > < dell > < del2 > < del3 > < ab > Defmes penalty alternatives for delaying or abandoning a project. Alternative names are predefined internally. <after-yr> <dell> <del2> <del3> <ab> 1, 2, 3, or 4 penalty for delaying project for one year penalty for delaying project for two years penalty for delaying project for three years penalty for abandoning the project Penalties are computed for resource 1 only. Alternatives are generated for all non-zero penalty amounts. For example, if < after-yr > = 1, then the set of alternatives generated internally will be named D1 Y1, D2Y1, D3Y1, ABYl. The keywords PENALTY TABLE are optional after the first card for a given ongoing project. OPTIMIZE <type> Starts optimization. Optimization report will display automatically. <type> TOTE, the total enumeration solution method will be used AHMED, the ahmed solution method will be used BLANK, the program will choose the solution method PRESELECT ALTERNATIVE < prj-alt > < prj-alt > < prj-alt >... Preselects specific project-alternatives to be used in an the solution. PRINT INPUT < prj-alt > < prj-alt > < prj-alt >... Prints a report of yearly input data for project- alternative < prj-alt > with the following additional options <prj-all> < prj > -alts, <prj > -ptab, All Summary prints all alternatives for project <prj > (for ongoing projects only) prints all alternatives for project <prj> (for ongoing projects only) prints the base alternative and penalty table for project < prj > prints all alternatives for all projects prints the input summary report. Note that to send the report to the printer you should use the SEND OUTPUT TO PRINTER command.

169 150 Expenditure Budgeting Model PRINT PROBLEM < prj-alt > < prj-alt > < prj-alt >... Prints a report for project-alternative < prj-alt > showing its data as it will appear to the optimization method. The following additional options are allowed: <prj-all> ALL SUMMARY PROJECT <name> <type> prints all alternatives for project <prj > prints all alternatives for all projects prints the problem summary report Initiates the definition of a project by specifying the < name> and < type>. <name> <type> READ INPUT FILE up to four alphanumeric characters MAINTENANCE, ONGOING, or NEW Starts reading the predefined input file. Reading of input data will be stopped by reading of the END INPUT FILE command in the input file or by reaching the end of the input file. SEND OUTPUT TO <output-device> Causes all subsequent reports to be directed at the specified output device. < output -device > TERMINAL PRINTER DISK Note that all error messages will be displayed on the terminal. STANDARD OPTIONS Starts reading input data from the standard options input file (EBMSTD.DAT), thereby setting any standard options. TIME PERIODS < ybegl-yendl > < ybeg2-yend2 > < ybeg3-yend3 >... Defines up to twenty time periods to be used in the optimization. Each time period may be for one or more years. Time periods must not overlap and must not leave any gaps between periods. EBM Error Messages As the EBM program runs, any errors found in the input are displayed on the screen. Each error message consists of the following parts: A copy of the input line that caused the error. The number of the error message. The message itself. The subsequent action that will be taken by the program. Printing a copy of the input line helps you to locate the source of the error, and the error number itself can be used to refer to this guide to get a detailed explanation of the error.

170 Expenditure Budgeting Model 151 This section lists all EBM error messages with their associated error numbers. 0.1 UNRECOGNIZED COMMAND. INPUT WILL BE IGNORED. The program is designed to read the first four letters of the first two words of each input line. If two commands have the same first word, then the presence of the second word is necessary to distinguish the two commands. This error message will be displayed when the first two words do not match any known command. A line containing only numeric data is assumed to use the same command as for the previous command. 0.2 NUMERIC DATA EXPECTED. INPUT WILL BE IGNORED. Numeric data is any data beginning with a minus sign or a digit (0-9). If the program finds a non numeric value when expecting a numeric, this error message will be displayed and subsequent data items on this line will be ignored. 0.3 ALPHANUMERIC OAT A EXPECTED. INPUT WILL BE IGNORED. Alphanumeric data is non-numeric (i.e., it does not start with a minus sign or a digit). This error message will be displayed if the program expects to find analphanumeric data item and finds a numeric instead. The data error and the subsequent values on the input line will be ignored. 0.4 NOT ENOUGH OAT A FOR THIS COMMAND INPUT WILL BE IGNORED. Not enough data were provided for execution of a command. The program ignores the command. 0.5 INVALID CHARACTERS IN A NUMERIC FIELD. INPUT WILL BE IGNORED. A numeric data value was entered containing an alphabetic character or possibly more that one decimal point. The entire input line will be ignored by the program. 1.1 TOO MANY TIME PERIODS. INPUT WILL BE IGNORED. Time periods defined exceed the maximum of twenty. Any additional time periods will be ignored by the program. Both beginning and ending years must be provided, separated by a delimiter, even if they are identical. 1.2 TIME PERIODS MUST BE DEFINED BEFORE CONSTRAINTS CAN BE DEFINED. INPUT WILL BE IGNORED. Time periods must be defined before attempting to define resource constraint levels. Constraint levels will be ignored until then. This is done to prevent a mismatch of time periods and resource constraints. 1.3 CONSTRAINT MISSING FOR SOME TIME PERIODS. OPTIMIZATION WILL BE INHIBITED. Either a resource constraint level has been explicitly defined as zero or a constraint level was not provided for at least one time period. Optimization will not be performed unless the constraint levels for all resources for all time periods are non-zero.