Trr No. 1311. Pavement Design, Management, And Performance, pp. 230-241
The Minnesota Department of Transportation (Mn/DOT) began the planning for its network level pavement management system (PMS) in the early 1980s, with actual development and implementation in the mid to late 1980s. Staging, preimplementation planning, and strong organizational support were major factors in the success of the PMS. A backgrund summary of the PMS development is provided and the requirements for preimplementation planning are identified. A system overview is presented of the overall logic and the major products. The PMS is comprehensive and incorporates a number of programs for data management functions, user interface, analysis and reporting. It operates on a personel computer workstation and is linked to the Transportation Information System on the Mn/DOT's mainframe computer. The PMS is flexible in the options provided to the user and in the range of detail for summarized graphical and tabular reporting functions. Two major subsystems are incorporated in the PMS : (a) Status and Needs Subsystem, and (b) Rehabilitation Optimization Subsystem. The former is capable of displaying the present status of each segment of the network, or the network as a whole, in terms of present serviceability rating, structural adequacy rating, surface rating, and a composite pavement quality index. The later is able to consider a large number of alternatives. It calculates capital, maintenance (optionally), and user delay (optionally) costs for each combination of alternative segment and possible implementation year (i.e., projects are considered in advance, and deffered, from the needs year). The outputs range from detailed calculations of optimized effectiveness for individual segments to summary reports of changes in a average performance index parameter for the network for different budget levels. Minnesota has a comprehensive, flexible PMS in place and oprtaional, tailored to its requirements. Among the key reasons for the successful development and implementation planning; strong support throughout the department including senior management; a sound technical basis for the system in terms of the data base, models, programs, and reporting functions; and a commitment by those responsible for its operation and use.