1、Designation: E1166 00 (Reapproved 2009)Standard Guide forNetwork Level Pavement Management1This standard is issued under the fixed designation E1166; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision, the year of last revision. A numb
2、er in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope1.1 This guide outlines the basic components of a networklevel pavement management system (PMS).1.2 This guide is intended for use in the manag
3、ement oftraveled pavement surfaces, including roads, airfields andparking lots.1.3 This guide is not a standard method or practice, that is,it is not intended to provide a comprehensive PMS in a userspecific application.2. Referenced Documents2.1 ASTM Standards:2E867 Terminology Relating to Vehicle-
4、Pavement Systems3. Terminology3.1 Definitions: All terminology used in this guide conformsto Terminology E867.3.1.1 feature(see 3.1.4).3.1.2 network level analysisevaluation of a network ofpavement to enable selection of candidate projects, projectscheduling, and budget estimates.3.1.3 pavement cond
5、itiona quantitative representation ofdistress in pavement at a given point in time.3.1.4 pavement management section/segmenta contigu-ous pavement area considered to have uniform construction,maintenance, usage history, and condition.3.1.5 pavement performanceability of a pavement tofulfill its purp
6、ose over time.3.1.6 project level pavement analysisevaluation of pave-ment section to select the type and timing of rehabilitation ormaintenance.4. Significance and Use4.1 This guide provides network level PMS users with anoutline of the basic components of a PMS to ensure the specificsystem the use
7、r selects or develops fulfills the agency needsand requirements.4.2 This guide may be used by agencies or organizationswishing to develop, evaluate, or refine a network level PMS.4.3 The basic components of the PMS described in thisguide are location reference, information collection, data basemanag
8、ement, analysis, implementation, operation and mainte-nance.4.4 Within each basic component a list of possible types ofdata, information, models, etc. are provided for considerationby the user agency. These lists are neither all inclusive norexclusive. They are intended for guidance only.5. Basic Co
9、mponents of a PMS5.1 Location ReferenceReference and location for allpavements and information in the system should be identifiedby a consistent and time stable reference and locations method.Some of the common network referencing methods include: (a) link-node, (b) branch/facility, (c) section/feat
10、ure, (d) mile-post, (e) log-mile, and (f) geo-coordinates.5.2 Information CollectionThe fundamental informationused in a pavement management system includes: (a) pave-ment inventory, (b) pavement condition, (c) traffic characteris-tics, (d) environment, and (e) cost. This information is used todefin
11、e uniform sections/features whose locations are identifiedwithin the reference method used by the agency. Data collec-tion methods, sampling patterns and frequencies should bechosen that are appropriate to the reliability of informationrequired to meet the needs and objectives of the agency asdefine
12、d in 3.1.2. Resources should be available to sustain theinformation collection efforts. Methods should be flexible1This guide is under the jurisdiction of ASTM Committee E17 on Vehicle -Pavement Systems and is the direct responsibility of Subcommittee E17.42 onPavement Testing and Evaluation.Current
13、 edition approved Nov. 1, 2009. Published December 2009. Originallyapproved in 1991. Last previous edition approved in 2005 as E116600 (2005).DOI: 10.1520/E1166-00R09.2For referenced ASTM standards, visit the ASTM website, www.astm.org, orcontact ASTM Customer Service at serviceastm.org. For Annual
14、Book of ASTMStandards volume information, refer to the standards Document Summary page onthe ASTM website.1Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.enough to allow for special conditions. Data may be collectedobjectively, subje
15、ctively, or in combination.5.2.1 Pavement InventoryThe following data may beincluded: (a) length/width/area/geometrics, (b) pavementstructure, layer types, design strength, and thicknesses, (c)construction and rehabilitation history, (d) maintenance history,( e) drainage, and (f) functional classifi
16、cation.5.2.2 Pavement ConditionThe following data may beincluded: (a) distress, (b) roughness, ride quality, ( c) skidresistance, texture, (d) stiffness, deflection, (e) materials andlayer properties, and (f) drainage.5.2.3 Traffc CharacteristicsThe following data may beincluded: (a) volume, (b) loa
17、ds, (c) vehicle classifications, and(d) accidents.5.2.4 Environment The following data may be included:(a) freeze-thaw cycles, (b) precipitation, (c) solar radiation, and(d) pavement temperature variation and range.5.2.5 CostThe following data may be included: (a) con-struction by pavement type, (b)
18、 maintenance and rehabilitationby activity, and (c) user costs.5.3 Database ManagementThe use of computers for da-tabase management is strongly recommended. All pavementnetwork data should be integrated (see Note 1). Softwareanalysis should transform the data into usable information toassist and or
19、support the decision process. Software andhardware can facilitate the following activities:5.3.1 Interface the field data collection with a data storagesystem,5.3.2 Structure the data base for ready storage, retrieval,maintenance, verification, updating, and integration with othersystems,5.3.3 Inter
20、face database with analysis routines, and5.3.4 Interface with reporting system.NOTE 1Users, when planning a system, should be aware of the needto maintain and utilize a historical database in relation to pavementinventory, pavement condition, traffic characteristics, environment andcosts.5.4 Analysi
21、s ComponentThe analysis procedures in apavement management system should be agency specific.Models are commonly incorporated into pavement manage-ment systems to accomplish the following objectives: (a)performance predictions, (b) cost analysis, (c) prioritization,(d) optimization, and (e) consequen
22、ce analysis.5.4.1 Performance PredictionPerformance curves andmodels are used for predicting the future condition andserviceability or both, of both existing pavements and rehabili-tation or maintenance alternatives.5.4.2 Cost Analysis Reconstruction, rehabilitation, andmaintenance cost data are use
23、d to estimate current and futurebudget needs. Cost data, including user costs, are also used inlife cycle cost analysis, cost benefit analysis, prioritization,optimization and consequences analysis.5.4.3 Prioritization Prioritization models are used togenerate lists of candidate projects and schedul
24、ing. The presentpavement condition, rate of deterioration, traffic, and otheragency specific criteria are incorporated into the prioritizationequations or algorithms.5.4.4 Optimization Optimization is the analysis of variousmaintenance, rehabilitation, and reconstruction strategies at thenetwork lev
25、el to: (a) maximize benefits, or, (b) minimize costs,or, ( c) maximize the extended life of the pavement, or ( d)maximize cost-effectiveness. Optimization models typicallyuse mathematical techniques such as linear programming,integer programming, or dynamic programming.5.4.5 Consequence AnalysisCons
26、equence analysis pro-vides the agency with the ability to assess the impact ofalternative pavement strategies and budget levels on the stateof the network.5.5 Feedback ComponentIn addition to estimating needs,prioritizing candidate projects, and optimizing strategies, theperformance and cost data ca
27、n be used to evaluate mainte-nance, rehabilitation, and reconstruction designs and tech-niques. The data can also be used to calibrate design proce-dures, and other research purposes.5.6 Implementation Procedures need to be developed forimplementation of the PMS within the agency to assurecompatibil
28、ity, usefulness, and acceptability. The plan shoulddefine computer hardware and software, equipment, personnelrequirements, and organizational structure. The plan may alsoinclude a staging process to implement the PMS gradually.5.6.1 OperationProcedures need to be developed forcollection, data entry
29、, quality assurance of data, and ongoingtraining.5.6.2 Maintenance Procedures need to be developed forupdate of data, periodic reporting and other system work,review, evaluation/calibration and improvement of systemmodels.6. Keywords6.1 network level pavement management; pavement man-agement systemE
30、1166 00 (2009)2ASTM International takes no position respecting the validity of any patent rights asserted in connection with any item mentionedin this standard. Users of this standard are expressly advised that determination of the validity of any such patent rights, and the riskof infringement of s
31、uch rights, are entirely their own responsibility.This standard is subject to revision at any time by the responsible technical committee and must be reviewed every five years andif not revised, either reapproved or withdrawn. Your comments are invited either for revision of this standard or for add
32、itional standardsand should be addressed to ASTM International Headquarters. Your comments will receive careful consideration at a meeting of theresponsible technical committee, which you may attend. If you feel that your comments have not received a fair hearing you shouldmake your views known to t
33、he ASTM Committee on Standards, at the address shown below.This standard is copyrighted by ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959,United States. Individual reprints (single or multiple copies) of this standard may be obtained by contacting ASTM at the aboveaddress or at 610-832-9585 (phone), 610-832-9555 (fax), or serviceastm.org (e-mail); or through the ASTM website(www.astm.org). Permission rights to photocopy the standard may also be secured from the ASTM website (www.astm.org/COPYRIGHT/).E1166 00 (2009)3
