Recommended Guidelines for the Collection and Use of Geospatially Referenced Data for Airfield Pavement Management (2010)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

The proposed guidelines are the recommendations of ACRP Project 9-01 staff at Applied Research Associates, Inc. and CIVIC Engineering, Inc. The guidelines have not been approved or otherwise formally accepted as a standard by ACRP or any other agency. A T T A C H M E N T Recommended Guidelines for the Collection and Use of Geospatially Referenced Data for Airfield Pavement Management

TABLE OF CONTENTS SUMMARY: RECOMMENDED GUIDELINES FOR THE COLLECTION AND USE OF GEOSPATIALLY REFERENCED DATA FOR AIRFIELD PAVEMENT MANAGEMENT...............................................A-1 RESEARCH SIGNIFICANCE............................................................................................. A-1 PROJECT OBJECTIVE AND SCOPE ................................................................................ A-1 SUMMARY OF GUIDELINES........................................................................................... A-2 APPLICATION .................................................................................................................... A-2 ANTICIPATED BENEFITS ................................................................................................ A-3 1 GENERAL INFORMATION............................................................................................... 1.1 INTRODUCTION .................................................................................................... A-5 A-5 1.2 SCOPE ...................................................................................................................... A-5 1.3 ANTICIPATED BENEFITS .................................................................................... A-6 1.4 CONVENTIONS ...................................................................................................... A-6 1.4.1 Compliance Conventions .............................................................................. A-6 1.4.2 Terms and Definitions................................................................................... A-6 1.5 REFERENCES ......................................................................................................... A-7 2 DATA USERS.................................................................................................................... 2.1 PURPOSE OF DEFINING USER CATEGORIES................................................ A-11 A-11 2.2 USER DATA CATEGORIES DEFINITIONS ...................................................... A-11 2.2.1 Owners ........................................................................................................ A-11 2.2.2 Developers .................................................................................................. A-11 2.2.3 Administrators............................................................................................. A-12 2.2.4 Maintainers ................................................................................................. A-12 2.2.5 Users ........................................................................................................... A-12 2.3 SUGGESTED USER DATA CATEGORY ORGANIZATIONAL CHART........ A-13 3 STORAGE METHODS...................................................................................................... 3.1 DATA REPRESENTATIONS ............................................................................... A-15 A-15 3.1.1 Point Data.................................................................................................... A-15 3.1.2 Polyline Data............................................................................................... A-15 3.1.3 Polygon Data............................................................................................... A-15 3.1.4 Numerical Data ........................................................................................... A-15 3.1.5 Text Data..................................................................................................... A-15 3.1.6 Temporal Data ............................................................................................ A-15 3.2 FILE FORMAT ...................................................................................................... A-15 3.3 COORDINATE SYSTEMS AND SPATIAL DATUM......................................... A-16 3.4 USE OF THREE DIMENSIONAL DATA ............................................................ A-16 4 PRECISION AND ACCURACY....................................................................................... 4.1 ACCURACY REQUIREMENTS .......................................................................... A-17 A-17 4.2 PRECISION REQUIREMENTS............................................................................ A-17 4.2.1 Measurement Precision............................................................................... A-17 4.2.2 Representation Precision............................................................................. A-17 5 COLLECTION METHODOLOGIES ................................................................................ 5.1 SPATIAL DATA REPRESENTING PAVEMENT............................................... A-19 A-19 5.2 SPATIAL DATA REPRESENTING NON-PAVEMENT ENTITIES .................. A-19 6 DATA FRAMEWORK ...................................................................................................... A-21

6.1 UML REPRESENTATION .................................................................................... A-21 6.2 AIRPORT REFERENCE POINT ........................................................................... A-23 6.3 BRANCH LOCATION .......................................................................................... A-23 6.4 SECTION LOCATION .......................................................................................... A-25 6.5 SECTION DISTRESSES ....................................................................................... A-27 6.6 SAMPLE UNIT LOCATION ................................................................................. A-28 6.7 SLAB LOCATION ................................................................................................. A-29 6.8 PHOTOGRAPH LOCATION ................................................................................ A-31 6.9 AIRFIELD EVENT ................................................................................................ A-33 6.10 AIRFIELD DISTRESS ........................................................................................... A-35 6.11 AIRFIELD CONSTRUCTION .............................................................................. A-36 6.12 DISTRESS ATTRIBUTE FIELDS ........................................................................ A-37 6.13 DOMAIN VALUES ............................................................................................... A-39 6.13.1 network_pcr7 .............................................................................................. A-39 6.13.2 network_pcr3 .............................................................................................. A-39 6.13.3 network_friction_rating .............................................................................. A-39 6.13.4 network_ea .................................................................................................. A-39 6.13.5 branch_use .................................................................................................. A-39 6.13.6 branch_pcr7................................................................................................. A-40 6.13.7 branch_pcr3................................................................................................. A-40 6.13.8 branch_friction_rating................................................................................. A-40 6.13.9 branch_ea .................................................................................................... A-40 6.13.10 section_use .............................................................................................. A-40 6.13.11 section_rank ............................................................................................ A-40 6.13.12 section_pms_surface ............................................................................... A-41 6.13.13 section_ol ................................................................................................ A-41 6.13.14 section_surface ........................................................................................ A-41 6.13.15 section_base ............................................................................................ A-41 6.13.16 section_subbase ....................................................................................... A-42 6.13.17 section_subgrade_unit ............................................................................. A-42 6.13.18 section_pcr7 ............................................................................................ A-42 6.13.19 section_pcr3 ............................................................................................ A-42 6.13.20 section_friction_rating ............................................................................ A-42 6.13.21 section_ea ................................................................................................ A-42 6.13.22 construction_material .............................................................................. A-43 7 METADATA ...................................................................................................................... 7.1 METADATA FORMAT ........................................................................................ A-45 7.2 METADATA CONTENTS .................................................................................... A-45 APPENDIX A CREATING GML FILES ............................................................................. A.1 AUTOCAD TO GML ............................................................................................. A-47 A-47 A.2 ARCGIS TO GML .................................................................................................. A-49 APPENDIX B DATA TRANSLATION GUIDE FOR MICROPAVER AND AIRPAV ... B.1 AIRPORT REFERENCE POINT ........................................................................... A-53 A-53 B.2 BRANCH LOCATION .......................................................................................... A-53 B.3 SECTION LOCATION .......................................................................................... A-54 B.4 SECTION DISTRESSES ....................................................................................... A-55 A-45

B.5 SAMPLE UNIT LOCATION ................................................................................. A-55 B.6 SLAB LOCATION ................................................................................................. A-56 B.7 PHOTOGRAPH LOCATION ................................................................................ A-57 B.8 AIRFIELD EVENT ................................................................................................ A-57 B.9 AIRFIELD DISTRESS ........................................................................................... A-58 B.10 AIRFIELD CONSTRUCTION .............................................................................. A-58 A-59APPENDIX C CONSTRUCTION LAYER RECORD SET EXAMPLE ............................

A-1 SUMMARY: RECOMMENDED GUIDELINES FOR THE COLLECTION AND USE OF GEOSPATIALLY REFERENCED DATA FOR AIRFIELD PAVEMENT MANAGEMENT RESEARCH SIGNIFICANCE The collection of d ata on pavement structure, pavement condition, traffic, climate, maintenance actions, testing and evaluation, a nd ot her items is essential fo r effective mana ge ment of airfield pavement; such data are re gu larl y collected as part of airfield pa ve ment mana ge ment s y stems by m an y a irports across the country . However, the data and infor ma tion collected b y various agencies have often differed i n definition and format, making it difficult for others to interpret and us e. Also, state-of-the-art technol og ies and processes applicable to data collection ha ve not been effectivel y used for collecting airfield management s y stems data. The use of global positioning s y stems in developing g eospatially referenced da ta is one of the technol og ie s that will gr eatly enh anc e the e ff ectiv eness of air field mana ge ment s y stems. Theref or e, there was a need to develop guidelines for the collection and use of geospatiall y referenc ed data f or use i n th e management of airfi eld pavements. These gu idelines will promote compatibilit y of da ta collected at different facilities; improve integration, interag en cy sharing, and anal y sis of da ta ; provide an effective m eans for economical ly addressing issues of common concern; and help better manage investments in airfield pa ve ments. The g uidelines will also aid organizations in providing a standard schema for displa y and exchange of spatial Pavement Management Sy stem (PMS) data b y providing methods and standards for: Organizing user interaction with the data . Defining d ata pr ecision and accu ra cy r equire me nts for data collection and storage. Collecting g eospatiall y referenced data . Storin g geos patiall y referenced data and linking it to non-geospatiall y r ef er enced da ta . A data dictionar y and fr amework for geospatiall y r eferenc ed ai rfie ld pavement mana gem ent data and asso ciated metadata . PROJECT OBJECTIVE AND SCOPE The objective of t his research w as t o de velop guidelines f or t he c ollecti on and use of geospatiall y r eferen ced pavement-r elated data f or t he m ana gem ent o f airfield pavements. T o accomplish this objective, the research inclu de d the following six tasks : 1. Collection and review of relevant information and current practices. The literature review verified that the re were no existing standards addressing geospatial PMS data and documented the cont ent and structure o f rela te d standards from the aviation, Geographic In formation Sy stem (GI S) , and pavem ents fields. R esearch into cu rrent a nd emerging PMS and G IS technologies identified Computer Aided Drafting (CAD), G IS , and Global Positioning S y stem (GPS) as the technolog ies most likely to be used to develop geospatial PMS data now and in the near future. An interview questionnaire that was sent to various airport ope ra tors throu gh out the count ry w as used to identify the geospatial PMS data that are current ly being collected and used. The responses indicated that MicroPAVER is the predominant PMS software in use.

of the underlying database structure of the various PMS packages used by airport operators, approximately 300 data elements were identified for inclusion in the guidelines. Also, users were divided into categories based on the means for interacting with the PMS and GIS data. 3. Preparation of a plan for developing the guidelines based on the findings of the work performed in previous research activities. 4. Organizing the data elements into feature classes and assigning data definitions that will provide the most portability across PMS software packages. 5. Providing a formal data dictionary and recommending data collection methods in the form of these guidelines. 6. Preparation of the guidelines. 7. Preparation of a project report that documents all research and development performed to support the development of the guidelines. This report is provided as Attachment 1 to guidelines. SUMMARY OF GUIDELINES The guidelines are organized into 7 chapters. Chapter 1 is an introduction and provides information concerning purpose, scope, and appropriate use of the guidelines as well as term definitions and references. Chapter 2 presents the recommended five data user categories: owners, developers, maintainers, administrators, and users. It also identifies the various modes of interaction that different users can have with the data, and provides an overview of the various activities that must be performed to maintain geospatial data. Chapter 3 specifies data storage methods, focusing primarily on software storage methods. To ensure maximum portability, only six data types are defined as acceptable in these guidelines: three spatial types (points, lines, polygons) and three attribute types (text, numbers, dates). This chapter also defines the Simple Features profile of Geographic Markup Language (GML) as the preferred format for data transfer, and includes provisions for the use of other GIS and CAD formats. Chapters 4 and 5 specify acceptable precision, accuracy, and collection methods for data elements, which are closely related. Data elements representing pavement entities should be collected using methods defined in Federal Aviation Administration Advisory Circular 150/5300-18 (current version) and meet the precision and accuracy requirements in that standard. Specific collection methods and precision requirements are not defined for non-pavement data elements (e.g., test points and photographs). Chapter 6 categorizes the approximately 300 data elements included in the guidelines into 10 feature classes and provides data definitions for each. Chapter 7 provides the data definitions for the metadata that should accompany the data elements. APPLICATION The guidelines describe methods of collecting spatial data in support of an airfield Pavement Management System (PMS) and organizing the data for integration into a Geographic Information System (GIS) system such that the data may easily shared with other departments and organizations. As such, the guidelines may be used for any airport pavement management project involving spatial data. 2. Identification and categorization of pavement management system elements that should be included in the guidelines. Based on the results of the airport operators’ survey and analysis A-2

The data schema defined in the guidelines is intended for data export to and display in a GIS, and for transfer of PMS data with a spatial aspect among differing organizations. The data elements defined in this report include only the most common PMS data elements that can be displayed in a GIS. Use of the guidelines will help ensure that data elements from any PMS software at any organization will be provided in a consistent manner for transfer or display in a GIS. ANTICIPATED BENEFITS The primary anticipated benefit of implementing these guidelines is improved capability to analyze and display pavement management data using GIS. The guidelines provide a standardized means for transferring the spatial aspects of PMS data for both business (financial planning) and technical (engineering analysis) purposes. Practically, these guidelines provide a means to transmit not only tables and reports representing pavement conditions and maintenance needs, but also maps representing PMS data and analyses. It is anticipated that these guidelines will lead to increased data sharing among organizations, resulting in the use of larger data sets for analyzing issues of common concern among the various organizations in the airfield pavement community. In this manner, these concerns can be adequately addressed and resolved. A-3

This page intentionally left blank.

1 GENERAL INFORMATION 1.1 INTRODUCTION The information collected, organized, and stored according to these guidelines can be used in part to complete the following tasks: Provide base map data for pavement management systems (PMS) with mapping capabilities. Geospatially reference inventory, condition, and other pavement data stored in PMS software systems. Record the location of PMS related events such as test points, distresses, or maintenance activities. Organize PMS-related geospatial data for efficient analysis. Allow efficient exchange of PMS-related geospatial data among organizations. These guidelines were developed to support surveys and pavement evaluations at airfields. 1.2 SCOPE The guidelines are intended to provide a data schema and other relevant information required to develop specifications and standards for integrating geospatial data into a PMS. They are compatible with Federal Aviation Administration Advisory Circular 150/5300-18A, but are not promulgated by the FAA. The guidelines are also compatible with the Federal Geographic Data Committee Framework Data Content Model Air Part, which are technically equivalent to the guidelines provided in the advisory circular. These guidelines are also compatible with the Aeronautical Information Exchange Model (AIXM) in the sense that the subject data are not specifically addressed by AIXM and do not violate general AIXM concepts, although metadata requirements for AIXM and these guidelines are slightly different, with AIXM generally more focused on internationalization of data. The guidelines were developed for capturing and organizing spatial data for PMS and integrating it into GIS and Computer Aided Drafting (CAD) systems. Specific topics included in these guidelines are: Data user roles and responsibilities. Precision and accuracy requirements of spatial data elements. PMS-related data elements and definitions. PMS-related metadata elements and definitions. Methods for associating PMS attribute data with spatial data. A schema for organizing, storing, and transporting spatial and attribute data. File formats for storing and transporting spatial and attribute data. The guidelines constitute a complete specification for integrating spatial data into a PMS such that the data can be readily accessed by GIS and CAD programs. The guidelines address only PMS-specific spatial data elements. Data elements that are related to PMS but typically not collected as part of a pavement management program (e.g., climate or traffic data) are not included in the guidelines. These data elements that are useful in a PMS but not collected for the primary purpose of including in a PMS, and may have a standard schema defined by another organization such as NOAA or the FAA. Integration of these data elements into the PMS data set is accomplished by means of a foreign key. Addition A-5

of user-defined data elements to the data schema in these guidelines by an organization is acceptable. The guidelines are intended for use with airside PMS and GIS systems. Landside pavement management systems and GIS are not addressed; however, many of the principles, schemas, data elements, and recommendations contained in these guidelines may be readily adapted for use in landside applications. 1.3 ANTICIPATED BENEFITS Use of these guidelines will facilitate more streamlined exchange of geospatial PMS data both within and between organizations and thus enhance the quality and types of analyses available for PMS operators. It should also allow investigating issues of common interest to the airfield pavements community using data from a broad cross section of airfields. 1.4 CONVENTIONS 1.4.1 Compliance Conventions “Shall” indicates that conformance is mandatory for compliance with these guidelines. “Should” indicates the preferred option. 1.4.2 Terms and Definitions The following terms and definitions apply: AC: Advisory Circular. ACRP: Airport Cooperative Research Program AIXM: Aeronautical Information Exchange Model Attribute Data: Information concerning the properties of an object or event other than location or extent. CAD: Computer Aided Drafting, a computer system used for production of maps, blueprints, and other technical drawings. CSDGM: Content Standard for Digital Geospatial Metadata, a standard method of transmitting geospatial metadata developed by the FGDC. Data Element: A piece of information about an object or event, usually corresponding to a database field. Data Set: A group of related data elements. Database: A computer system used to store and retrieve information. DGN: The computer filename extension used to identify MicroStation files; it can also be used to signify any file of that format. DWG: The computer filename extension used to identify Autodesk AutoCAD files; it can also be used to signify any file of that format. Event: An entity, procedure, or data for which temporal (time) data are significant. FAA: Federal Aviation Administration. A-6

FGDC: Federal Geographic Data Committee, an U.S. Federal Government interagency committee that promotes the coordinated development, use, sharing, and dissemination of geospatial data on a national basis. Field: The named portion of a record in which a particular data element is recorded. Geodatabase: A database that has the capability to store spatial data. Georeferenced: An object or event having spatial data that uniquely identify its location or extent on the Earth. Geospatially Referenced: See “Georeferenced.” GIS:G eographic Information System, a computer system used for producing, organizing, and analyzing spatial and attribute data. GML: Geographic Markup Language, a subset of XML for storing and transmitting spatial data. Inherently Spatial Data: Data collected for the primary purpose of storing/analyzing/displaying location information. Metadata: Data concerning the origin, quality, or use of a dataset, or other information related to a dataset but not part of that dataset. NOAA: National Oceanic and Atmospheric Administration Object: An entity or data for which temporal (time) data are not significant. Record: A complete set of data elements for a single object or event. ShapeFile: A file format defined by the company ESRI for use in its GIS products. Spatial Attribute Data: Location data for a data element or record for which location information is not the primary purpose of collecting/storing/analyzing/displaying the data. Spatial Data: Information that identifies the location or extent of an object or event. SQL:S tructured Query Language, a computer language used to interact with database systems. UML: Universal Modeling Language, a computer language for representing computer systems, databases, programs, and other software items and processes. XML: Extensible Markup Language, a computer language for storing and transmitting diverse types of data. 1.5 REFERENCES The following documents were used in the development of the guidelines: Aho, B. (Engineer, Applied Research Associates), Personal Interview (April 9, 2007). Applied Research Associates (ARA), AIRPAV for Windows 3.1: Advanced Airport Management Software, Applied Research Associates, Inc., Madison, WI (2005) Computer Software. A-7

Architecture and Standards Working Group (ASWG), Inspire Architecture and Standards Position Paper. Smits, P. (Ed). JRC-Institute for Environment and Sustainability, Ispra, Italy (October, 2002) 64 pp. ASTM D 5340, Standard Test Method for Airport Condition Index Surveys, American Society for Testing and Materials, West Conshohocken, PA (2004) 55 pp. Benton, A. R., Jr. and P. J. Taetz, Elements of Plane Surveying, McGraw-Hill, New York (1991) 420 pp. Brunk, B. K. and E. Prosnicu, “A Tour of AIXM Concepts,” 24th Annual ESRI User Conference, San Diego, CA, Proceedings, (2004) Paper 2190, 30 pp Presentation http://www.faa.gov/aixm/media/A%20tour%20of%20AIXM%20Concepts.pdf. City of Dallas Aviation Department (Dallas), Dallas Love Field Love Notes, http://www.dallas- lovefield.com/lovenotes/lovenotes.html. (As of December 15 2009) DPLI Working Group (DWG), INSPIRE Data Policy & Legal Issues Working Group Position Paper. Environmental Agency for England and Wales (2002) 45 pp. Environmental Systems Research Institute (ESRI), ESRI Shapefile Technical Description, Environmental Systems Research Institute, Redlands, CA (1998) 28 pp. Federal Aviation Administration (FAA), Standards for Specifying Construction of Airports (FAA Advisory Circular 150/5370-10A, Federal Aviation Administration, Washington, DC (1991) electronic. Federal Aviation Administration (FAA), Specification for the Wide Area Augmentation System (WAAS), FAA-E- 2892b, Change 2, Federal Aviation Administration, Washington, DC (2001) 156 pp. Federal Aviation Administration (FAA), Airport Pavement Management Program, FAA Advisory Circular 150/5380-7a, Federal Aviation Administration, Washington, DC (2006a) 15 pp. Federal Aviation Administration (FAA), General Guidance and Specifications for Aeronautical Survey Airport Imagery Acquisition and Submission to the National Geodetic Survey, FAA Advisory Circular 150/5300-17, Federal Aviation Administration, Washington, DC (2006b) 13 pp. Federal Aviation Administration (FAA), General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards, FAA Advisory Circular 150/5300-18, Federal Aviation Administration, Washington, DC (2006c) 359 pp. Federal Aviation Administration (FAA), General Guidance and Specifications for Aeronautical Surveys: Establishment of Geodetic Control and Submission to the National Geodetic Survey, Advisory Circular 150/5300-16, Federal Aviation Administration, Washington, DC (2006d) 120 pp. Federal Aviation Administration (FAA), General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards, Advisory Circular 150/5300-18A, Federal Aviation Administration, Washington, DC (2007) 380 pp. A-8

Federal Aviation Administration (FAA) and European Organization for the Safety of Air Navigation (EUROCONTROL), EUROCONTROL – Aeronautical Information Exchange, http://www.aixm.aero (as of January 24, 2007). Federal Geodetic Control Subcommittee (FGCS), GPS & Selective Availability Q&A, http://www.ngs.noaa.gov/FGCS/info/sans_SA/docs/GPS_SA_Event_QAs.pdf. (As of January 21, 2007) 7 pp. Federal Geographic Data Committee (FGDC), Content Standard for Digital Geospatial Metadata (revised June 1998), FGDC-STD-001-1998, Federal Geographic Data Committee, Washington, D.C. (1998). Fort Wayne Allen County Airport Authority (FWA), Fort Wayne International Airport, Smith Field Airport: Fort Wayne Allen County Airport Authority, http://www.fwairport.com/default.aspx. (As of December 9, 2009). Garmin, Garmin | What Is GPS?, http://www.garmin.com/aboutGPS/. (As of January 21 2007). Giesecke, F. E., et. al., Technical Drawing (9th ed.), Macmillan Publishing Company, New York (1991) 938 pp. Green, W. H. and R. A. Eckrose, Airport Pavement Inspection by PCI (2nd Ed.), Eckrose/Green & Associates, Madison, WI (1988) 178 pp. INSPIRE Environmental Thematic Coordination Group (IETC), Environmental Thematic User Needs Position Paper: Version 2, Lillethun, A. (Ed), European Environmental Agency (2002) 154 pp. International Organization for Standardization (ISO), Geographic Information – Metadata, ISO 19115, International Organization for Standardization, Geneva (2003). Mississippi Board of Licensure for Professional Engineers and Surveyors (PEPLS), Rules and Regulations of Procedure: Effective September 1, 2006, Jackson, MS (2006) Appendix B. http://www.pepls.state.ms.us/pepls/web.nsf/webpages/LN_RR_PAGE_RR/$FILE/RulesWebSite September2006.doc?OpenElement National Geospatial-Intelligence Agency (NGA), NSG Feature Information Catalog: Version 1.7, National Geospatial-Intelligence Agency (2006) Excel Spreadsheet. The Oklahoma Aeronautics Commission (OAC), Pavement Management for Oklahoma’s General Aviation Airfields, http://apms.aeronautics.ok.gov. (As of January 21, 2007). Parsons, T., Development of an Airport Pavement History and Information Delivery System (AFID), University of Oklahoma, Norman, OK (2001) 133 pp. Proposal for a Directive of the European Parliament and of the Council: Establishing an Infrastructure for Spatial Information in the Community (INSPIRE), COM(2004) 516 final, Brussels, Belgium (2004) 32 pp. RDM Working Group (RDMWG), Reference Data and Metadata Position Paper, Rase, D., et al (Eds.), EUROSTAT, 45 pp. Shahin, M. Y., Pavement Management for Airports, Roads, and Parking Lots, Kluwer Academic Publishers, Boston, MA (1994) 450 pp. A-9

Shahin, M. Y., MicroPAVER: Version 5.2.6, US Army Corp of Engineers-Construction Engineering Research Laboratory, Champaign, IL (2007) Computer Software. http://www.cecer.army.mil/paver/Paver.htm. Shahin, M. Y., et al., MicroPAVER 5.2 User Manual, US Army Corp of Engineers-Construction Engineering Research Laboratory, Champaign, (2004) 141 pp. Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE), http://www.sdsfie.org. (As of January 21, 2007). United States Geological Survey (USGS), mp: Version 2.9.10, (2009) Computer Software. http://geology.usgs.gov/tools/metadata/tools/doc/mp.html A-10

2 DATA USERS 2.1 PURPOSE OF DEFINING USER CATEGORIES User categories are defined to allow an organization to more effectively control and use its PMS data. Each user category relates to the data in a different manner, with a unique set of recommended responsibility and authority with respect to the data. These user categories serve the purpose of identifying the tasks required to effectively manage PMS data and to providing a starting point for assigning data access rights (permissions) to the various staff that use PMS data. The user categories defined in these guidelines may also be applied to non-PMS data sets. 2.2 USER DATA CATEGORIES DEFINITIONS 2.2.1 Owners Owners are responsible for the data, but may not use it in day-to-day operations. The Owner sets data policy (e.g., what types of data should be collected and how often), and then uses the data to make decisions concerning the activities of the organization. Owners typically hold an executive position in an organization. An Owner may be a group, such as a board of aviation, city council, or state aeronautics commission. Owners in this context should not be confused with “owners” in the context of IT administration, in which an owner refers to a person with complete control over a database or file system. Owners should have read access permission to data sets, but, due to the technical difficulty of manipulating data, should rarely have write access to data sets. Due to the executive nature of the position, Owners typically request complex data analyses and reports from Administrators or other technical staff rather than directly manipulating data. Data are then provided to the Owners in an appropriately summarized format for their review and analysis. Implementation of the guidelines will make more data available to Owners for pavement management system analysis. Requiring data providers, both in-house and consultant, to follow the guidelines will improve the consistency of data products. 2.2.2 Developers Developers are responsible for the initial production of a data set, which typically involves collecting field data. Developers are typically called on when a new type of data is required, or a dataset for which an incremental update is inappropriate becomes out of date. Developers typically possess specialized skills and/or equipment for technically sophisticated tasks, such as surveying or production of orthorectified aerial photography. Developers typically hold a technical position (surveyor, engineer, technician, or similar) in an organization or are contractors. Developers should be trained appropriately and/or hold an appropriate certification for the data collection method being used to ensure adequate data quality (e.g., registered land surveyor). Developers should consider the requirements of these guidelines when collecting data in order to provide a complete, accurate data set and to prevent excess post-processing to make the data conform to the guidelines. Developers should have read and write access rights to a data set, and rarely, to an entire database. The recommended practice is to have the developer create a working data set independent of the actual in-use production database and then merge the new data from the working data set into the production database once it has been verified and checked for quality. A-11

Implementation of the guidelines will reduce the amount of effort required to provide data to Owners because data will be developed to the same standard for different users. Developers will also be able to more easily re-use older data developed by other organizations because data will be provided in a consistent manner regardless of origin. 2.2.3 Administrators Administrators are responsible for the day-to-day use of the data, including keeping the data secure and up to date. The primary responsibilities of a data Administrator are to maintain data integrity, to control access to the data, and to implement the policies set by the owner. Administrators also oversee and review data provided by developers and maintainers. While Administrators have some responsibility for maintaining the data, these responsibilities are primarily in the information technology and administrative realms. For example, maintenance might include keeping track of the most recent aerial photography and arranging for updates of this particular data according the policies set forth by the Owners or ensuring that the entire database is properly backed up. Administrator duties may be divided between an information technology professional and an engineering professional. Administrators should have complete read and write access to the entire database, including administrative functions such as setting access permissions for other users. They are responsible for seeing that all users can access the data they require, but still minimize the possibility for corruption of the database. They would be responsible for merging data delivered by a developer into the production database as well as for acquiring data, directly or through developers or maintainers, to provide analyses or reports to Owners. Implementation of the guidelines will provide uniformity in data presentation and exchange of spatial PMS both within the organization and outside the organization. GIS analysis packages will only need to recognize a single format to use the spatial data; thus eliminating the need to tune the data for display. Data exchanged between the engineering and IT departments or provided by an outside consultant will be treated the same in software, thus reducing the amount of effort required to integrate a dataset into an organizations over GIS. 2.2.4 Maintainers Maintainers are responsible for performing the database updates. Data maintainers are typically responsible maintaining the detailed technical contents of the database, (e.g., entering the data related to completion of a repair project or work order into the database). This activity differs from the maintenance responsibilities of an Administrator, who is more concerned with the quality of entire data sets and the information technology principles of database and computer maintenance. Maintainers typically hold a technical, clerical, or production position in the maintenance, information technology, or engineering departments of an organization. Maintainers should have read and write access to limited portions of the database that are required to perform their job functions. Implementation of the guidelines should have very little impact on maintainers. 2.2.5 Users Users are allowed to view and analyze but not to manipulate data. Users are generally responsible for performing technical analyses and producing charts, tables, and maps for presentation to beneficiaries. Users typically hold technical or maintenance positions within an organization. A-12

Users should have read access to all data sets to allow them to perform complex analysis and reporting functions. Some users will require write access to portions of the database to perform specific analyses, such as performing a time intensive computation and saving the results. It is recommended that users not be given write access to primary data (to prevent accidental corruption of difficult-to-replace primary data) provided by developers or maintainers; however, users may be given write access to secondary data that can be re-computed if corrupted. User access to secondary data is less dangerous, as it may always. Users in a maintenance position use the data to plan specific tasks such as crack sealing or patching. Implementation of the guidelines will provide uniformity of the data available for analysis. Users will be able to use compliant data from any source without the need to re-map data fields or study the data set dictionary to understand what each data field represents. 2.3 SUGGESTED USER DATA CATEGORY ORGANIZATIONAL CHART Figure 2.1 shows the suggested organization chart and relationships between the various data user categories. The user categories will not necessarily have a one-to-one correspondence with personnel or departments. In smaller agencies, a single person may fit into multiple categories. For example, the duties of Administrator, maintainer, and user all require similar data manipulation skill sets. However, a large agency may divide responsibilities, (e.g., having multiple data Administrators). For example, Administrator duties may be divided among an IT professional who manages the technical aspects of the database and an engineering professional who manages the data quality aspects of the database and oversees acquisition of new data. Figure 2.1. Suggested organization chart for the recommended user data categories. A-13

This page intentionally left blank.

3 STORAGE METHODS 3.1 DATA REPRESENTATIONS The number of data representations used in the guidelines has been minimized to increase inter-agency compatibility. Spatial data are represented by points and polygons, and attribute data are represented by numerical data, text data, and temporal (time) data. 3.1.1 Point Data Point data shall be used to represent objects or events for which extent is not important; that is, a location. A photograph location is a good example of point data. Most test data may be represented by points. 3.1.2 Polyline Data Polyline data shall be used to represent objects or events which are linear in nature; (i.e., data with a defined starting and stopping point with a path between the two for which the width of the path is not important). Crack location or pavement roughness trace data are examples of polyline data. 3.1.3 Polygon Data Polygon data shall be used to represent objects with location and extent; (i.e., an area). All pavement and divisions of pavement shall be polygon data. 3.1.4 Numerical Data Numerical data shall be used to represent only inherently numeric data. These data cannot be represented as anything except a number, such as a length or width. Data that are arbitrarily numeric, such as a pavement rank or sample number, shall be stored as text. In addition to physical properties, some condition data may be represented numerically. All numerical data shall be stored as floating point data. Boolean data shall also be stored as numerical data with 0 being false and non-zero numbers being true. 3.1.5 Text Data Text data shall be used to represent all descriptive data that is neither inherently numeric nor temporal. This data includes all pavement identification codes for all levels of inventory. 3.1.6 Temporal Data Temporal data shall be used to represent times. All temporal data shall be capable of storing a 4-digit year (Y2K compliant). Time intervals should be represented by two temporal data elements clearly marked “start” and “end” or similar, as appropriate. 3.2 FILE FORMAT Data shall be transmitted in a vector representation using Simple Features Profile (formerly Level 0 Profile) of Geographic Markup Language (version 3) (GML) or an equivalent. Equivalent formats must be convertible to GML and back using the import/export tools of commercial off-the-shelf software with no other data manipulation, no loss of spatial data, and no loss of attribute data, including the properties of individual data fields. Raster data (aerial photography) standards are defined in FAA AC 150/5300-17 if required. A-15

The guidelines require the use of GML. However, other data formats, (e.g., personal Geodatabase), are acceptable if both the originating organization and the receiving organization agree on the transmission format and that the data can be provided in GML if requested. In addition, the following formats can be used when submitting data to the FAA in accordance with AC 150/5300-18 if they contain both spatial and attribute data: DWG/DXF (Autodesk AutoCAD version 2002 or later) SHP (ESRI Shapefile) DGN (MicroStation Design File version 8 or later) The guidelines do not address the format that an organization selects for in-house data storage and manipulation. 3.3 COORDINATE SYSTEMS AND SPATIAL DATUM Spatial data shall be provided in conformance with FAA AC 150/5300-18 paragraph 9-5. 3.4 USE OF THREE DIMENSIONAL DATA PMS data representing pavement shall be provided in three dimensions when possible, especially if other datasets collected by an organization are three-dimensional. Derived PMS datasets shall match underlying three-dimensional spatial data. If underlying spatial data are two-dimensional, data may be represented in two dimensions. PMS data representing non- pavement entities (events, distresses, photographs, and construction) shall be three-dimensional when pavement data are three-dimensional. Three dimensional spatial data representing construction data shall represent the top surface of the material layer indicated. Three dimensional data are desired to provide compatibility with other airfield data sets that are required to be represented in three dimensions by FAA AC 150/5300-18 (current version). Three dimensional data also allows the user to create complex visualizations of construction layers. Three-dimensional data are generally desired; but it is not always available and PMS data currently are often represented in a two-dimensional plan view. A-16

4 PRECISION AND ACCURACY 4.1 ACCURACY REQUIREMENTS Accuracy is the difference between the location or attribute value of an object and its representation in a dataset. Unless otherwise stated, the minimum accuracy requirements are a 95% confidence level of five (5) feet horizontally and ten (10) feet vertically for airfield pavement elements and other inherently spatial data. Spatial data elements representing pavements or portions thereof shall meet or exceed the accuracy requirements defined in AC 150/5300-18 (current version) Part 1 Chapter 4 and Part 2 Chapter 10. Spatial data that are derived (calculated) from another spatial data set shall meet the accuracy requirements of field- collected data. Spatial data for non-pavement entities collected in the field have no accuracy requirements, but the accuracy of each data set shall be documented in the associated metadata. However, it is expected that non-pavement entity accuracy generally will not exceed the minimum precision of readily available commercial-off-the-shelf consumer GPS receivers. Numerical attribute data representing condition data or test results shall meet the accuracy requirements of the standard defining the test method or condition index. Numerical attribute data representing pavement dimensions derived from inherently spatial data shall meet the same accuracy requirements as the primary data. Temporal data shall have a minimum accuracy of one day unless more precision is required by a test method or other standard defining the data element of which the temporal data is an attribute. Textual attributes shall have accuracy requirements defined by the data set owner, and shall be expressed in terms of percent of records containing an error in any textual data element. 4.2 PRECISION REQUIREMENTS Precision is the level of repeatability or exactness of the data. Precision has two components: measurement precision and representation precision. 4.2.1 Measurement Precision Measurement precision is defined as the resolution of the measuring device used to collect data about an object. The precision of all measurements of a data object shall meet or exceed the accuracy requirements for that object. Derived (calculated) data shall not have more precision than the primary (measured) data from which it is developed. Temporal data shall be precise to the nearest day unless more precision is required by a test method or other standard defining the data element of which the temporal data is an attribute. 4.2.2 Representation Precision Representation precision is defined as the resolution of the storage format, typically vertex spacing for a vector file format, pixel size for raster data, field length for text data, and the number of significant digits for numerical data. Representations of an object shall be capable of storing and displaying the full precision of all measurements of the object. A-17

This page intentionally left blank.

5 COLLECTION METHODOLOGIES 5.1 SPATIAL DATA REPRESENTING PAVEMENT The acceptable methods of data collection for spatial data entities listed, in order of preference are as follows. 1. Collection according to the methods described in FAA AC 150/5300-17 and FAA AC 150/5300-18 (current version) 7-1 and 7-2. These methods are field surveying and feature extraction from a stereo model. 2. Editing a data set collected according to the methods described in FAA AC 150/5300-17 and FAA AC 150/5300-18 (current version). This can include subdividing existing features or adding new features. If new features are added, the data set may only be used for PMS applications. 3. Feature extraction from georeferenced orthorectified aerial photography. 4. Editing existing data sets, such as Architectural/Engineering drawings. Methods 3 and 4 may only be used for data sets used exclusively in PMS. 5.2 SPATIAL DATA REPRESENTING NON-PAVEMENT ENTITIES There are no restrictions placed on the collection and development of spatial data representing events, except that the method used to collect the data and a determination or estimation of precision shall be provided in the metadata for the data set. If the data are derived data, the precision of the primary data set also shall be provided. For example, if photograph locations are recorded using dead reckoning methods and marked on a map, the metadata should state in the Data_Quality_Information Positional_Accuracy fields the accuracy of the spatial data, and then note in the Data_Quality_Information Lineage field that the data were collected using dead reckoning and also list the base map used in the dead reckoning process. A-19

This page intentionally left blank.

6 DATA FRAMEWORK Spatial PMS data are divided into nine record sets. Record set names are to be appended with the FAA airport identifier code. For example, the Airport Reference Point dataset for John F. Kennedy International Airport in New York City, New York would be named AIRFIELD_PMS_ARP_JFK. The primary key of each feature class is indicated in boldface type. Foreign keys may be added to any feature class to incorporate data that are related to PMS but not primarily PMS data (e.g., climate and traffic). Climate data is a good example of this type of data. Climate data are important to pavement management, but not collected primarily for the purpose of pavement management. As such, standards and systems for storage of climate data already exist. A foreign key for climate data has been included in the AIRFIELD_PMS_ARP feature class to access this data. For example, the AWOS station identification of an AWOS station near an airfield could be stored as the climate data foreign key. Database links or joins then use the foreign key to access the AWOS system and retrieve climate and weather information about the airport. 6.1 UML REPRESENTATION Figures 6.1 and 6.2 present the data framework, illustrating data types and entity relationships in UML format. The nomenclature “1…*” in a relational UML chart indicates a “one-to-many” relationship between feature classes, meaning that a single feature in one feature class may be related to multiple features in another feature class (a single branch can contain multiple sections). The symbol in a feature definition UML chart indicates inheritance, or that properties of the parent feature class are transferred to the child feature class unless explicitly changed. Figure 6.1 defines which data types that each feature class may consist of. In UML, this is done by defining top-level feature classes for each geometry type, and then specifying from which domains a feature class is allowed to inherit. General users will rarely if ever encounter or use these top-level features. In general, entities representing pavement defined using polygons or surfaces, photos and the airport reference point are defined using a point, and distresses and events may use points, polygons/surfaces, or lines. Figure 6.2 defines the relationship of each feature class to the other feature classes. While each feature class is designed to be complete and independent data set, there are real world relationships between the entities each feature class represents, such as airports are divided into branches, which are in turn divided into sections, which are further divided into samples. The data schema is designed to organize data using these relationships. Each feature class contains at least one foreign key to define the parent feature of a particular entity, as shown in Figure 6.2. A-21

-branch_PMS_key : String Airfield_PMS_Branch -section_PMS_key : String Airfield_PMS_Section +image_id : String Airfield_PMS_Photos -event_id : String Airfield_PMS_EventPoint +feature_id : String Airfield_PMS_Feature -geometry : Point Airfield_PMS_Point -geometry : Surface Airfield_PMS_Surface AirField Feature -event_id : String Airfield_PMS_EventSurface -network_PMS_key : String Airfield_PMS_ARP -section_PMS_key : String Airfield_PMS_Section_Dist -sample_PMS_key : String Airfield_PMS_Sample -slab_PMS_key : String Airfield_PMS_Slab -construction_PMS_key : String Airfield_PMS_Construction -network_PMS_key : String Airfield_PMS_DistressPoint -geometry : Polygon Airfield_PMS_Polyline -event_id : String Airfield_PMS_EventPolyline -network_PMS_key : String Airfield_PMS_DistressPolyline -network_PMS_key : String Airfield_PMS_DistressSurface Figure 6.1. Data framework features in UML format. Airfield_PMS_Branch -branch_PMS_key : String Airfield_PMS_Section -section_PMS_key :String Airfield_PMS_Photos +image_id : String Airfield_PMS_Event -event_id : String Airfield_PMS_ARP -network_PMS_key : String Airfield_PMS_Section_Dist -section_PMS_key : String Airfield_PMS_Sample -sample_PMS_key : String Airfield_PMS_Slab -slab_PMS_key : String Airfield_PMS_Construction -construction_PMS_key : String 1 BranchHasSection 1 * ARPHasBranch 1 * SectionHasSlab 1 * BranchHasSectionDistress 1 * SectionHasSample 1 * SextionHasPhotos 1..* *SectionHasConstruction 1 * SectionHasEvent 1 * SampleHasSlab * * Section_DistHasSection -section_PMS_key : String Airfield_PMS_Distress 1 * SampleHasEvent 1 * SlabHasPhotos 1 * SampleHasPhotos 1 * SlabHasDistress 1 * SlabHasEvent 1 * SectionHasDistress 1 * SampleHasDistress Figure 6.2. Data framework feature relationships in UML format. A-22

6.2 AIRPORT REFERENCE POINT Name: AIRFIELD_PMS_ARP Definition: A point representing the location of the airfield, intended for large-scale analysis, such as viewing all the airfields in a state at once. Sensitivity: Unclassified. FAA AC 150/5300-18A Equivalent: Airport Reference Point. SDS Entity Equivalent: airfield_surface_site Geometry: Point Requirements: Each airfield shall have one point representing the airfield location. Data Capture Rule: The airport reference point shall be determined according to FAA AC 150/5300-18 (CURRENT VERSION) Appendix 2 Section 2-1. Attribute data shall be averages or other aggregated attribute data of pavement divisions in the airport. Attributes: Attribute DataType Minimum Length Definition network_short_name Text 10 Network ID or short name network_name Text 60 Network name network_pms_key Text 20 Primary key from PMS database network table network_area Number Float Total area in the network in square feet. network_pci Number Float Area-weighted average PCI from ASTM D5340 network_pcr7 Text 10 Seven-category PCR from ASTM D5340 network_pcr3 Text 4 Three-category PCR from ASTM D5340 network_paser Number Float Area-weighted average PASER rating from FAA AC 150/5320-17 network_fod Number Float Area-weighted average FOD index. Specify calculation method in metadata network_friction_index Number Float Friction index, from mu-meter or similar. Specify collection method in metadata. network_friction_rating Text 4 Friction rating, from USAF ETL 04-09 network_pcn_value Number Float PCN from AC 150/5335-5 (civil) or PCASE (military). Specify roll-up method in metadata. network_pcn_descriptor Text 4 Letters after the PCN numerical value from AC 150/5335-5 (civil) or PCASE (military), e.g., R/A/W/T for rigid pavement on subgrade strength A with unlimited tire pressure determined by technical evaluation network_ea Text 14 Engineering assessment from ETL 04-09 network_climate Text 20 Climate data foreign key. Specify source in metadata. 6.3 BRANCH LOCATION Name: AIRFIELD_PMS_BRANCH Definition: The location of each portion of pavement with a specific use, as shown in Figure 6.3. Branches are generally named portions of pavement, e.g., Runway 09/27, Taxiway A, or Air Cargo Apron. A-23

Figure 6.3. Branch Location definition. Sensitivity: Restricted. FAA AC 150/5300-18A Equivalents: Runway, Stopway, Helipad TLOF, Taxiway Segment, Taxiway Intersection, Apron, Runway Blastpad, Shoulder. SDS Entity Equivalent: airfield_surface_site. Geometry: Polygon. Requirements: Each pavement branch shall be collected as a polygon or group of polygons. Branches shall correspond with branches defined in the PMS. Data Capture Rule: Adjoining polygons shall be collected with collocated or shared vertices and edges. Branch location data should be collected by field surveying or remote sensing methods. Branch location data may consist of derived data developed by combining polygons from the section location data set. Attribute data shall be averages or other aggregated attribute data of pavement divisions in the branch. Aggregation method shall be specified in associated metadata. Attributes: Attribute Data Type Minimum Length Definition branch_short_name Text 10 Branch ID or short name branch_name Text 50 Branch name branch_pms_key Text 20 Primary key from PMS database branch table FAA_key Text 25 Globally unique FAA primary key defined in AC 150/5300- 18A 9-3-2 branch_area Number Float Total area in the branch in square feet. branch_use Text 8 Branch use: APRON, HELIPAD, OVERRUN, RUNWAY, TAXIWAY. network_short_name Text 10 Short name of parent network. network_pms_key Text 20 Primary key of parent network from PMS database. branch_area Number Float Total area in the branch in square feet. branch_pci Number Float Area-weighted average PCI from ASTM D5340. branch_pcr7 Text 10 Seven-category PCR from ASTM D5340. branch_pcr3 Text 4 Three-category PCR from ASTM D5340. branch_paser Number Float Area-weighted average PASER rating from FAA AC 150/5320-17 A-24

Attribute (continued) DataType Minimum Length Definition branch_fod Number Float Area-weighted average FOD index. Specify calculation method in metadata. branch_friction_index Number Float Friction index, from mu-meter or similar. Specify collection method in metadata. branch_friction_rating Text 4 Friction rating, from USAF ETL 04-09. branch_pcn_value Number Float PCN from AC 150/5335-5 (civil) or PCASE (military) branch_pcn_descriptor Text 4 Letters after the PCN numerical value from AC 150/5335-5 (civil) or PCASE (military), e.g., R/A/W/T for rigid pavement on subgrade strength A with unlimited tire pressure determined by technical evaluation branch_ea Text 14 Engineering assessment from ETL 04-09 6.4 SECTION LOCATION Name: AIRFIELD_PMS_SECTION Definition: The location of each portion of pavement that is unique with respect to construction history and use, shown in Figure 6.4. Attribute data describes pavement structure, condition, and use. Figure 6.4. Section Location definition. Sensitivity: Restricted. FAA AC 150/5300-18A Equivalent: PavementSection. SDS Entity Equivalent: airfield_surface_site Geometry: Polygon. Requirements: Each pavement section shall be collected as a polygon or group of polygons. Sections shall correspond with sections defined in the PMS. Groups of polygons (multipart polygons) shall be used when a pavement section is non- contiguous (e.g., a group of parking pads or hard stands that make up a single section). Data Capture Rule: Adjoining polygons shall be collected with collocated or shared vertices and edges. Section location data should be collected by field surveying or remote sensing methods. Data collection shall be as specified for the parent A-25

branch in FAA 150/5300-18A, except that accuracy requirements are relaxed to 5 feet horizontally and 10 feet vertically unless the data will be used for applications other than PMS. Section data may consist of derived data developed from a branch location data set by dividing polygons appropriately. Attribute data should be developed from existing record sets such as as-built drawings and from field investigations such as bore holes and pavement evaluation surveys. Attributes: Attribute Data Type Minimum Length Definition section_id Text 10 Section ID or short name section_pms_key Text 20 Primary key from PMS database section table FAA_key Text 25 Globally unique FAA primary key defined in AC 150/5300-18A 9-3-2 branch_short_name Text 10 Branch ID of pavement branch branch_pms_key Text 20 Primary key of parent branch from PMS database network_short_name Text 10 Short name of parent network network_pms_key Text 20 Primary key of parent network from PMS database section_area Number Float Area in the section in square feet. section_use Text 8 Branch use: APRON, HELIPAD, OVERRUN, RUNWAY, TAXILANE, TAXIWAY section_rank Text 1 Pavement PMS priority (Primary, Secondary, Tertiary) section_pms_surface Text 3 Surface type for purposes of condition survey. section_constructed Date Date section was constructed section_maint Date Date section was last maintained section_insp_date Date Date section was last inspected section_ol Text 5 Overlay type: AC, PCC, or item identifier from AC 5300- 10A. section_ol_thick Number Float Overlay thickness in inches section_surface Text 5 Original surface type: AC, PCC, or item identifier from AC 5300-10A. section_surface_thick Number Float Original surface thickness in inches section_base Text 5 Base material: GRAN for unspecified granular base or item identifier from AC 5300-10A section_base_thick Number Float Base thickness in inches section_subbase Text 5 Subbase material: GRAN for unspecified granular subbase or item identifier from AC 5300-10A section_subbase_thick Number Float Subbase thickness in inches section_subgrade Text 5 USCS soil classification of subgrade section_subgrade_strength Number Float Subgrade strength CBR or k-value section_subgrade_unit Text 3 “CBR” for strengths expressed as CBR or “PCI” for strengths expressed as k-values or PSI for moduli section_design_gear Text 5 Gear designation from FAA Order 5300.7 of design aircraft landing gear. section_design_mtow Number Float Maximum take-off weight of design aircraft Section_design_passes Number Float Design passes for design aircraft section_pci Number Float Area-weighted average PCI from ASTM D5340 section_pcr7 Text 10 Seven-category PCR from ASTM D5340 section_pcr3 Text 4 Three-category PCR from ASTM D5340 section_paser Number Float Area-weighted average PASER rating from FAA AC 150/5320-17 section_fod Number Float Area-weighted average FOD index. Specify calculation method in metadata A-26

Attribute (continued) Data Type Minimum Length Definition section_friction_index Number Float Friction index, from mu-meter or similar. Specify collection method in metadata. section_friction_rating Text 4 Friction rating, from USAF ETL 04-09 section_pcn_value Number Float Numerical PCN value from AC 150/5335-5 (civil) or PCASE (military) section_pcn_descriptor Text 4 Letters after the PCN numerical value from AC 150/5335-5 (civil) or PCASE (military), e.g., R/A/W/T for rigid pavement on subgrade strength A with unlimited tire pressure determined by technical evaluation section_ea Text 14 Engineering assessment from ETL 04-09 section_traffic Text 20 Foreign key referencing traffic records. 6.5 SECTION DISTRESSES Name: AIRFIELD_PMS_SECTION_DIST Definition: The location of each portion of pavement that is unique with respect to construction history and use. The geospatial aspect of the data is identical to Section Location, shown in Figure 6.4. Attribute data describes distresses present on the pavement surface collected using the PCI (ASTM D5340) or PASER (AC 150/5320-17) methods. Sensitivity: Restricted. FAA AC 150/5300-18A Equivalent: None. SDS Entity Equivalent: airfield_surface_site Geometry: Polygon. Requirements: Each pavement section shall be collected as a polygon or group of polygons. Sections shall correspond with sections defined in the PMS Data Capture Rule: Adjoining polygons shall be collected with collocated or shared vertices and edges. Data collected in the field shall be collected as specified for the parent branch in FAA 150/5300-18A, except that accuracy requirements are relaxed to 5 feet horizontally and 10 feet vertically unless the data will be used for applications other than PMS. Section data may consist of derived data developed from a branch location data set by dividing polygons appropriately. Attribute data should be developed from field investigations such as pavement evaluation surveys. Distress density (distress quantity divided by section area) provides an estimate of each type of distress in a pavement section, and may be directly measured or can be calculated as the area-weighted average of the distress density of sample units in a pavement section. A-27

Attributes: Distress attribut e f ields are the distress densit y for th e entire s ection. Attribute Data Type Minimum Length Definition section_id T ex t 1 0 S ection ID or short na me section_pms_key T ex t 2 0 P ri ma ry k ey f ro m PM S database section tabl e FA A_ ke y T ex t 2 5 G loball y un ique F AA prim ar y ke y defi ne d in A C 150/5300 - 18A 9 -3 -2 bran ch_short_n am e T ex t 1 0 B ranch ID o f pa ve ment b ranc h pm s_ke y T ex t 2 0 P ri ma ry k ey o f pare nt b ranch fr om PMS databas e ne tw or k_ sh ort_ na me T ex t 1 0 S ho rt nam e of parent ne tw or k ne tw or k_ pm s_ke y T ex t 2 0 P ri ma ry k ey of parent ne tw ork fr om PMS databas e section_area Nu mb er Floa t A rea in the sec tion in square feet . section_us e T ex t 8 Bran ch use: A PR ON, H EL IP AD , OVE RR UN, RUNW AY, T AX IL AN E, T AX IW AY section_rank T ex t 1 0 P av em ent PMS priority ( P ri ma ry , S eco nd ar y, T ertiary ) section_ in sp_date Date Date the section wa s in spected . DIST RESS AT T RI BU T E FI ELDS IN P AR AGR AP H 6.12 INCO RP OR AT ED BY REFERENC E 6.6 SAMPLE UNIT LOCATION Name: A IR FI EL D_PMS_SAMPLE Definition: The location of pavement sectio n s ubdivisions used to reduce the effort required to perform a c ondition survey , shown in Figure 6.5. Sample units are smallest discrete unit of AC pavement in a PMS. Figu re 6.5. Sample Unit L ocation de finition. A-28

Attribute Sensitivity: Restricted. FAA AC 150/5300-18A Equivalent: None. SDS Entity Equivalent: airfield_surface_site Geometry: Polygon. Requirements: Each sample unit should be collected as a polygon or group of polygons. Data Capture Rule: Adjoining polygons shall be collected with collocated or shared vertices and edges. Data collected in the field shall be collected as specified for the parent branch in FAA 150/5300-18A, except that accuracy requirements are relaxed to 5 feet horizontally and 10 feet vertically unless the data will be used for applications other than PMS. Dead reckoning methods are acceptable when locating sample units. Sample unit data may consist of derived data developed from a section location data set by dividing polygons appropriately. Attributes: Data Type Minimum Length Definition sample_id Text 10 Sample ID sample_pms_key Text 20 Primary key (from PMS database sample table if available) sample_date Date Date sample was inspected section_id Text 10 Section ID of parent section section_pms_key Text 20 Primary key of parent section from PMS database branch_short_name Text 10 Branch ID of parent branch branch_pms_key Text 20 Primary key of parent branch from PMS database network_short_name Text 10 Short name of parent network network_pms_key Text 20 Primary key of parent network from PMS database sample_area Number Float Area in the section in square feet for AC surfaced and slabs for PCC surfaces. Sample_pms_surface Text 8 Sample surface at time of inspection sample_type Text 10 Sample is a RANDOM or ADDITIONAL sample sample_pci Number Float Sample PCI from ASTM D5340 sample_pcr7 Text 10 Seven-category PCR from ASTM D5340 sample_pcr3 Text 4 Three-category PCR from ASTM D5340 section_fod Number Float Sample FOD index. Specify calculation method in metadata DISTRESS ATTRIBUTE FIELDS IN PARAGRAPH 6.12 INCORPORATED BY REFERENCE 6.7 SLAB LOCATION Name: AIRFIELD_PMS_SLAB Definition: The location of each PCC pavement slab on the airfield. Slabs are the smallest discrete unit of PCC pavement in a PMS, as shown in Figure 6.6. Sensitivity: Restricted. FAA AC 150/5300-18A Equivalent: None. SDS Entity Equivalent: airfield_surface_site Geometry: Polygon. A-29

Requirements: Each slab should be collected as a pol yg on. Data Capture Rule: Adj oining pol yg ons shall be collected with collocated or shared vertices and ed ges . D ata collected in the field sha ll be collected as sp ecified for the parent branch in FAA 150/5300-18A, except that accura cy r equi re ments are relax ed to 5 feet horizont al ly and 10 feet vertical ly unless the data will be used for applications other than P MS. Slab data may cons is t of derived data developed from a section location data set b y dividing pol yg ons appropriate ly . Fig ur e 6.6. Slab Lo cation definitio n. Attributes : Attribute Data Type Minimum Length Definition slab_i d T ex t 1 0 S lab ID slab_pms_key Te xt 20 Pr im ar y ke y (f ro m PM S database slab tabl e i f av ailable) sa mp le_date Date Date s am ple wa s inspected sa mp le_i d T ex t 1 0 S am ple ID o f pare nt s am pl e sa mp le_p ms _k ey Te xt 20 Pr im ar y ke y of parent sa mp le f ro m PM S database section_id Te xt 10 Section ID of parent sect io n section_ pm s_ke y T ex t 2 0 P ri ma ry k ey o f pare nt sect ion fr om PMS databas e bran ch_short_n am e T ex t 1 0 B ranch ID o f pa ve ment b ranc h bran ch_p ms _k ey Te xt 20 Pr im ar y ke y of parent bran ch f ro m PM S database ne tw or k_ sh ort_ na me Te xt 10 Short na me o f pare nt n et wo rk ne tw or k_ pm s_ke y T ex t 2 0 P ri ma ry k ey o f pare nt n et wo rk f ro m PM S database A-30

Attribute (continued) DataType Minimum Length Definition blowup_low Number Float Low-severity blowups present on slab. Blowup_medium Number Float Medium-severity blowups present on slab. Blowup_high Number Float High-severity blowups present on slab. Corner_break_low Number Float Low-severity corner breaks present on slab. Corner_break_medium Number Float Medium-severity corner breaks present on slab. Corner_break_high Number Float High-severity corner breaks present on slab. Ltd_crack_low Number Float Low-severity LTD cracking present on slab. Ltd_crack_medium Number Float Medium-severity LTD cracking present on slab. Ltd_crack_high Number Float High-severity LTD cracking present on slab. D_crack_low Number Float Low-severity durability cracking present on slab. D_crack_medium Number Float Medium-severity durability cracking present on slab. D_crack_high Number Float High-severity durability cracking present on slab. Jsd_low Number Float Low-severity joint seal damage present on slab. Jsd_medium Number Float Medium-severity joint seal damage present on slab. Jsd_high Number Float High-severity joint seal damage present on slab. Mi_cracking Number Float Manhole and inlet cracking present on slab. Patch_small_low Number Float Low-severity small patching present on slab. Patch_small_medium Number Float Medium-severity small patching present on slab. Patch_small_high Number Float High-severity small patching present on slab. Patch_large_low Number Float Low-severity large patching present on slab. Patch_large_medium Number Float Medium-severity large patching present on slab. Patch_large_high Number Float High-severity large patching present on slab. Popouts Number Float Popouts present on slab. Potholes Number Float Polishing present on slab. Polishing Number Float Potholes present on slab. Pumping Number Float Pumping present on slab. Scaling_low Number Float Low-severity scaling present on slab. Scaling_medium Number Float Medium-severity scaling present on slab. Scaling_high Number Float High-severity scaling present on slab. Faulting_low Number Float Low-severity faulting present on slab. Faulting_medium Number Float Medium-severity faulting present on slab. Faulting_high Number Float High-severity faulting present on slab. Shattered_slab_low Number Float Low-severity shattered slab. Shattered_slab_medium Number Float Medium-severity shattered slab. Shattered_slab_high Number Float High-severity shattered slab. Shrinkage_crack Number Float Shrinkage cracks present on slab. Spall_joint_low Number Float Low-severity joint spalling present on slab. Spall_joint_medium Number Float Medium-severity joint spalling present on slab. Spall_joint_high Number Float High-severity joint spalling present on slab. Spall_corner_low Number Float Low-severity corner spalling present on slab. Spall_corner_medium Number Float Medium-severity corner spalling present on slab. Spall_corner_high Number Float High-severity corner spalling present on slab. 6.8 PHOTOGRAPH LOCATION Name: AIRFIELD_PMS_PHOTO Definition: The location where a photograph was taken. Sensitivity: Restricted. FAA AC 150/5300-18A Equivalent: None. A-31

SDS Entit y Equivalent: photograph_location_point Geomet ry : Point . Requirements: Collect the location of each photog ra ph taken . Data Capture Rule: Point location and photograp h direction the cam era is f acin g shall be collected f or each photograph. Dead reckoni ng is an acceptable method of obtaining the photograph location. Figu re 6.7. Phot og raph Lo cation definitio n. A-32

Attributes: Attribute Data Type Minimum Length Definition image_id Text 100 Primary key (from PMS database if available) FAA_key Text 25 Globally unique FAA primary key defined in AC 150/5300- 18A 9-3-2 img_time Text 6 Time of day the image was taken in 24-hour clock units Format for time of day is HHMMSS. Use the standard 24 hour clock. Img_date Text 8 The date the photo was taken. Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915). Img_direction Text 3 Direction the camera was facing when the photograph was collected. Use compass heading (045) or compass points (NE). img_narrative Text 240 A description or other unique information concerning the subject item. img_filenpath Text 255 The file name of the digital file of the image including the path indicating the location on the particular operating system of the digital file for this image. Slab_id Text 20 Slab ID of associated slab slab_pms_key Text 20 Primary key of associated slab from PMS database sample_id Text 10 Sample ID of associated sample sample_pms_key Text 20 Primary key of associated sample from PMS database section_id Text 10 Section ID of associated section section_pms_key Text 20 Primary key of associated section from PMS database branch_short_name Text 10 Branch ID of pavement branch branch_pms_key Text 20 Primary key of associated branch from PMS database network_short_name Text 10 Short name of associated network network_pms_key Text 20 Primary key of associated network from PMS database 6.9 AIRFIELD EVENT Name: AIRFIELD_PMS_EVENT Definition: An activity, condition, or item not part of the airfield pavements or appurtenances that occurs at a specific place and time on an airfield. Examples of events include: geotechnical boreholes, non-destructive testing, acceptance cores, and friction testing. Photographs are technically events, but should be placed in AIRFIELD_PMS_PHOTO. All test results related to PMS should be stored as events. All distresses should be stored as events. It is permissible to provide more than one AIRFIELD_PMS_EVENT provided the contents of each file are clearly described in the metadata. The GML file name may also be extended to identify the contents of multiple instances of AIRFIELD_PMS_EVENT. For example, boreholes and HWD testing can both be stored in the same instance of AIRFIELD_PMS_EVENT, but they may also be placed into the separate instances of AIRFIELD_PMS_EVENT_HWD and AIRFIELD_PMS_EVENT_BOREHOLE with appropriate documentation in the metadata. The intent of AIRFIELD_PMS_EVENT is to provide a general feature class to store a wide variety of data related to pavement management. Sensitivity: Unclassified. A-33

FAA AC 150/5300-18A Equivalent: None. SDS Entity Equivalent: None. Geometry: Point, Polyline, or Polygon. Requirements: Collect the location of each event that is directly related to pavement management, typically a test that determines some property of the pavement. Data Capture Rule: Collect data with a test point grid spacing of less than the typical slab size of an airfield, or 25-ft by 25-ft for airfields with no PCC surfaces, as a polygon. Collect all other data as point data. Dead reckoning is an acceptable method for determining location. Event records shall have either a simple result or a link to the complete event dataset. Attributes: Attribute Data Type Minimum Length Definition event_id Text 30 Primary key (from PMS if available) FAA_key Text 25 Globally unique FAA primary key defined in AC 150/5300- 18A 9-3-2 event_type Text 30 Description of event event_time Text 6 Time of day the event occurred in 24-hour clock units Format for time of day is HHMMSS. Use the standard 24 hour clock. event_date Text 8 The date the event occurred. event_longitude Number Float Longitude of event, west negative. event_latitude Number Float Latitude of even, south negative. event_elevation Number Float Elevation of event in feet event_depth Number Float Depth below existing surface of event at time of event in inches narrative Text 240 A description or other unique information concerning the subject event. filenpath Text 255 The file name of the digital file containing data from the event (e.g., PDF or DWG file) including the path indicating the location on the particular operating system of the digital file for this image. event_table Text 50 Record set identifier for event data stored in database format event_foreign_key Text 25 Record set identifier for event data stored in database format event_number Text 30 Common identifier of event (e.g., borehole B-1) event_num_result Number Float Simple numerical result generated by event event_text_result Text 30 Simple textual result generated by event. slab_id Text 20 Slab ID of associated slab slab_pms_key Text 20 Primary key of associated slab from PMS database sample_id Text 10 Sample ID of associated sample sample_pms_key Text 20 Primary key of associated sample from PMS database section_id Text 10 Section ID of associated section section_pms_key Text 20 Primary key of associated section from PMS database branch_short_name Text 10 Branch ID of pavement branch branch_pms_key Text 20 Primary key of associated branch from PMS database network_short_name Text 10 Short name of associated network network_pms_key Text 20 Primary key of associated network from PMS database A-34

6.10 AIRFIELD DISTRESS Name: AIRFIELD_PMS_DISTRESS Definition: A distress on a pavement. Sensitivity: Unclassified. FAA AC 150/5300-18A Equivalent: None. SDS Entity Equivalent: None. Geometry: Point, Polyline, or Polygon. Requirements: Collect the location of each distress. Data Capture Rule: Collect area distresses in AC and PCC distresses using polygons. Collect linear distresses using polylines. Corner breaks and joint seal damage may be considered linear or area distresses. Spalling is considered an area distress. Distresses less than two feet in any dimension may be collected as points. Dead reckoning is an acceptable method for determining location. Figure 6.8. Representation of pavement distress (note linear and area distresses would be stored in different data sets). A-35

Attributes: Attribute Data Type Minimum Length Definition distress_id Text 30 Primary key (from PMS database if available) FAA_key Text 25 Globally unique FAA primary key defined in AC 150/5300- 18A 9-3-2 distress_type Text 30 Description of distress (full name from ASTM D5340 or AC 150/5320-17) distress_severity Text 6 Distress severity (high, medium, or low) distress_quantity Number Float Quantity of distress distress_units Text 10 Units of distress_quantity distress_date Text 8 The date the distress was recorded. distress_longitude Number Float Longitude of distress, west negative. distress_latitude Number Float Latitude of distress, south negative. distress_elevation Number Float Elevation of distress in feet slab_id Text 20 Slab ID of associated slab slab_pms_key Text 20 Primary key of associated slab from PMS database sample_id Text 10 Sample ID of associated sample sample_pms_key Text 20 Primary key of associated sample from PMS database section_id Text 10 Section ID of associated section section_pms_key Text 20 Primary key of associated section from PMS database branch_short_name Text 10 Branch ID of pavement branch branch_pms_key Text 20 Primary key of associated branch from PMS database network_short_name Text 10 Short name of associated network network_pms_key Text 20 Primary key of associated network from PMS database 6.11 AIRFIELD CONSTRUCTION Name: AIRFIELD_PMS_CONST Definition: A pavement construction or project area on an airfield, including soil and other subsurface layers. Sensitivity: Restricted. FAA AC 150/5300-18A Equivalent: Construction Area. SDS Entity Equivalent: construction_site. Geometry: Polygon. Requirements: Collect the location of each pavement construction event at an airfield. Data Capture Rule: The outer edges of each constitutive layer of construction and maintenance project limits must be captured. If data are three-dimensional, capture the top surface of the layer. Due to the complexity of representing multiple construction projects through time, a sample record set is provided in Appendix B. A-36

Attributes: Attribute Data Type Minimum Length Definition construction_pms_key Text 20 Primary key from PMS database work/construction history table construction_date Date Date of construction/maintenance section_id Text 10 Section ID of parent section section_pms_key Text 20 Primary key of parent section from PMS database branch_short_name Text 10 Branch ID of pavement branch branch_pms_key Text 20 Primary key of parent branch from PMS database network_short_name Text 10 Short name of parent network network_pms_key Text 20 Primary key of parent network from PMS database construction_activity Text 60 Description of construction activity construction_reference Text 30 Project, Task Order, Delivery Order, or other project reference. construction_material Text 10 AC, PCC, granular, or material code from AC 5300-10A construction_thickness Number Float Thickness of construction material construction_thick_unit Text 10 Units of construction material thickness construction_strength Number Float Strength of construction material construction_str_unit Text 10 Units of construction material strength construction_str_def Text 20 Name of test method used to determine construction strength 6.12 DISTRESS ATTRIBUTE FIELDS The following attributes are included in feature classes AIRFIELD_PMS_SAMPLE and AIRFIELD_PMS_SECTION_DIST. Attribute Data Type Minimum Length Definition alligator_low Number Float Distress density in percent of low-severity alligator cracking. alligator_medium Number Float Distress density in percent of medium-severity alligator cracking. alligator_high Number Float Distress density in percent of high-severity alligator cracking. bleeding Number Float Distress density in percent of bleeding. block_low Number Float Distress density in percent of low-severity block cracking. block_medium Number Float Distress density in percent of medium-severity block cracking. block_high Number Float Distress density in percent of high-severity block cracking. corrugation_low Number Float Distress density in percent of low-severity corrugation. corrugation_medium Number Float Distress density in percent of medium-severity corrugation. corrugation_high Number Float Distress density in percent of high-severity corrugation. depression_low Number Float Distress density in percent of low-severity depression. depression_medium Number Float Distress density in percent of medium-severity depression. depression_high Number Float Distress density in percent of high-severity depression. jet_blast Number Float Distress density in percent of jet blas. joint_reflect_low Number Float Distress density in percent of low-severity joint reflection cracking. joint_reflect_medium Number Float Distress density in percent of medium-severity joint reflection cracking. joint_reflect_high Number Float Distress density in percent of high-severity joint reflection cracking. long_trans_low Number Float Distress density in percent of low-severity longitudinal and transverse cracking. long_trans_medium Number Float Distress density in percent of medium-severity longitudinal and transverse cracking. long_trans_high Number Float Distress density in percent of high-severity longitudinal and transverse cracking. A-37

Attribute (continued) Data Type Minimum Length Definition oil_spillage Number Float Distress density in percent of oil spillage. patch_low Number Float Distress density in percent of low-severity patching. patch_medium Number Float Distress density in percent of medium-severity patching. patch_high Number Float Distress density in percent of high-severity patching. polished_aggregate Number Float Distress density in percent of polished aggregate. raveling_low Number Float Distress density in percent of low-severity raveling. raveling_medium Number Float Distress density in percent of medium-severity raveling. raveling_high Number Float Distress density in percent of high-severity raveling. rutting_low Number Float Distress density in percent of low-severity rutting. rutting_medium Number Float Distress density in percent of medium-severity rutting. rutting_high Number Float Distress density in percent of high-severity rutting. shoving_low Number Float Distress density in percent of low-severity shoving. shoving_medium Number Float Distress density in percent of medium-severity shoving. shoving_high Number Float Distress density in percent of high-severity shoving. slippage Number Float Distress density in percent of slippage. swell_low Number Float Distress density in percent of low-severity swelling. swell_medium Number Float Distress density in percent of medium-severity swelling. swell_high Number Float Distress density in percent of high-severity swelling. blowup_low Number Float Distress density in percent of low-severity blowups. blowup_medium Number Float Distress density in percent of medium-severity blowups. blowup_high Number Float Distress density in percent of high-severity blowups. corner_break_low Number Float Distress density in percent of low-severity corner breaks. corner_break_medium Number Float Distress density in percent of medium-severity corner breaks. corner_break_high Number Float Distress density in percent of high-severity corner breaks. ltd_crack_low Number Float Distress density in percent of low-severity LTD cracking. ltd_crack_medium Number Float Distress density in percent of medium-severity LTD cracking. ltd_crack_high Number Float Distress density in percent of high-severity LTD cracking. d_crack_low Number Float Distress density in percent of low-severity durability cracking. d_crack_medium Number Float Distress density in percent of medium-severity durability cracking. d_crack_high Number Float Distress density in percent of high-severity durability cracking. jsd_low Number Float Distress density in percent of low-severity joint seal damage. jsd_medium Number Float Distress density in percent of medium-severity joint seal damage. jsd_high Number Float Distress density in percent of high-severity joint seal damage. meander_cracking Number Float Distress density in percent of meander cracking. mi_cracking Number Float Distress density in percent of manhole and inlet cracking. patch_small_low Number Float Distress density in percent of low-severity small patching. patch_small_medium Number Float Distress density in percent of medium-severity small patching. patch_small_high Number Float Distress density in percent of high-severity small patching. patch_large_low Number Float Distress density in percent of low-severity large patching. patch_large_medium Number Float Distress density in percent of medium-severity large patching. patch_large_high Number Float Distress density in percent of high-severity large patching. popouts Number Float Distress density in percent of popouts. potholes Number Float Distress density in percent of potholes. pumping Number Float Distress density in percent of pumping. scaling_low Number Float Distress density in percent of low-severity scaling. scaling_medium Number Float Distress density in percent of medium-severity scaling. scaling_high Number Float Distress density in percent of high-severity scaling. faulting_low Number Float Distress density in percent of low-severity faulting. faulting_medium Number Float Distress density in percent of medium-severity faulting. faulting_high Number Float Distress density in percent of high-severity faulting. shattered_slab_low Number Float Distress density in percent of low-severity shattered slabs. shattered_slab_high Number Float Distress density in percent of high-severity shattered slabs. A-38

Attribute (continued) Data Type Minimum Length Definition shrinkage_crack Number Float Distress density in percent of shrinkage cracks. spall_joint_low Number Float Distress density in percent of low-severity joint spalling. spall_joint_medium Number Float Distress density in percent of medium-severity joint spalling. spall_joint_high Number Float Distress density in percent of high-severity joint spalling. spall_corner_low Number Float Distress density in percent of low-severity corner spalling. spall_corner_medium Number Float Distress density in percent of medium-severity corner spalling. spall_corner_high Number Float Distress density in percent of high-severity corner spalling. 6.13 DOMAIN VALUES All material specifications are from Advisory Circular 150/5370-10 (current version) unless otherwise noted. 6.13.1 network_pcr7 Value Remarks Value Remarks Value Remarks Value Remarks Value Remarks excellent PCI value 86-100 very_good PCI value 71-85 good PCI value 56-70 fair PCI value 41-55 poor PCI value 26-40 very_poor PCI value 11-25 failed PCI value 0-10 6.13.2 good PCI value 71-100 fair PCI value 56-70 poor PCI value 0-55 6.13.3 good Mu-meter* value >0.50 fair Mu-meter *value 0.35 to 0.50 poor Mu-meter *value 0.00 to 0.34 * see USAF ETL 04-9 table 2 for determining friction ratings using other equipment 6.13.4 adequate pavement rates as “adequate” by USAF ETL 04-9 degraded pavement rates as “degraded” by USAF ETL 04-9 unsatisfactory pavement rates as “unsatisfactory” by USAF ETL 04-9 6.13.5 network_pcr3 network_friction_rating network_ea branch_use APRON aircraft parking, loading, and maintenance areas HELIPAD helicopter landing area OVERRUN paved safety area beyond runway ends RUNWAY pavement for aircraft landing and take off TAXIWAY pavement for aircraft to move from place to place on the ground SHOULDER non-aircraft pavement at edges of aircraft operation areas A-39

6.13.6 excellent PCI value 86-100 very_good PCI value 71-85 good PCI value 56-70 fair PCI value 41-55 poor PCI value 26-40 very_poor PCI value 11-25 failed PCI value 0-10 6.13.7 good PCI value 71-100 fair PCI value 56-70 poor PCI value 0-55 6.13.8 good Mu-meter* value >0.50 fair Mu-meter *value 0.35 to 0.50 poor Mu-meter *value 0.00 to 0.34 * see USAF ETL 04-9 table 2 for determining friction ratings using other equipment 6.13.9 adequate pavement rates as “adequate” by USAF ETL 04-9 degraded pavement rates as “degraded” by USAF ETL 04-9 unsatisfactory pavement rates as “unsatisfactory” by USAF ETL 04-9 6.13.10 APRON aircraft parking, loading, and maintenance areas HELIPAD helicopter landing area OVERRUN paved safety area beyond runway ends RUNWAY pavement for aircraft landing and take off TAXIWAY pavement for aircraft to move from place to place on the ground SHOULDER non-aircraft pavement at edges of aircraft operation areas 6.13.11 branch_pcr7 branch_pcr3 branch_friction_rating branch_ea section_use section_rank P Primary pavement (critical to operations) S Secondary pavement (non-critical for operations) T Tertiary pavement (tow-only and non-structural pavement) Value Remarks Value Remarks Value Remarks Value Remarks Value Remarks Value Remarks A-40

6.13.12 section_pms_surface AAC asphalt overlay of asphalt pavement AC asphalt pavement ACT asphalt over cement treated base APC asphalt overlay of PCC pavement PCC Portland cement concrete pavement RMP resin modified pavement ST surface treatment X other 6.13.13 section_ol AC asphalt overlay PCC pcc overlay P401 asphalt meeting AC 5370-10 specification P-401 P402 porous friction course meeting AC 5370-10 specification P-402 P501 PCC meeting AC 5370-10 specification P-501 6.13.14 section_surface AC asphalt surface PCC pcc surface P401 asphalt meeting P-401 specification P402 porous friction course meeting P-402 specification P501 PCC meeting P-501 specification 6.13.15 section_base GR granular base (unspecified) P208 aggregate base P209 crushed aggregate base course P210 Caliche base course P211 lime rock base course P212 shell base course P213 sand-clay base course P301 soil cement base course P304 cement treated base course P306 econocrete base course P401 asphalt stabilized base course meeting P-401 specifications Value Remarks Value Remarks Value Remarks Value Remarks A-41

6.13.16 section_subbase GR granular subbase (unspecified) P154 subbase meeting P-154 specification P155 lime treated subgrade P208 aggregate subbase P209 crushed aggregate subbase course P210 Caliche subbase course P211 lime rock subbase course P212 shell subbase course P213 sand-clay subbase course P301 soil cement subbase course P304 cement treated subbase course P306 econocrete subbase course P401 asphalt stabilized subbase course meeting P-401 specifications 6.13.17 section_subgrade_unit CBR strength is expressed as a CBR for flexible pavement PCI inch-pounds per square inch; strength is a modulus of subgrade reaction (k-value) for rigid pavement psi strength is expressed as a modulus in pounds per square inch 6.13.18 section_pcr7 excellent PCI value 86-100 very_good PCI value 71-85 good PCI value 56-70 fair PCI value 41-55 poor PCI value 26-40 very_poor PCI value 11-25 failed PCI value 0-10 6.13.19 section_pcr3 good PCI value 71-100 fair PCI value 56-70 poor PCI value 0-55 6.13.20 section_friction_rating good Mu-meter* value >0.50 fair Mu-meter *value 0.35 to 0.50 poor Mu-meter *value 0.00 to 0.34 * See USAF ETL 04-9 table 2 for determining friction ratings using other equipment 6.13.21 section_ea adequate pavement rates as “adequate” by USAF ETL 04-9 degraded pavement rates as “degraded” by USAF ETL 04-9 unsatisfactory pavement rates as “unsatisfactory” by USAF ETL 04-9 Value Remarks Value Remarks Value Remarks Value Remarks Value Remarks Value Remarks A-42

6.13.22 construction_material GR granular subbase (unspecified) AC asphalt (unspecified) PCC Portland cement concrete (unspecified) P154 subbase meeting P-154 specification P155 lime treated subgrade P208 aggregate subbase P209 crushed aggregate subbase course P210 Caliche subbase course P211 lime rock subbase course P212 shell subbase course P213 sand-clay subbase course P301 soil cement subbase course P304 cement treated subbase course P306 econocrete subbase course P401 asphalt stabilized subbase course meeting P-401 specifications P402 porous friction course meeting AC 5370-10 specification P-402 P501 PCC meeting AC 5370-10 specification P-501 Value Remarks A-43

This page intentionally left blank.

7 METADATA 7.1 METADATA FORMAT Metadata shall be provided compliant with Federal Geospatial Data Committee Content Standard for Digital Geospatial Metadata (FGDC CSDGM) FGDC-STD-001-1998. The North American Profile of ISO 19115 is expect in the near future; upon implementation, metadata shall be provided compliant with it. 7.2 METADATA CONTENTS Metadata elements shall meet the content requirements for metadata of FAA AC 150/5300-18A 9-4. The minimum metadata elements are listed below. The equivalent metadata elements from FAA AC 150/5300-18A and the CSDGM are also listed. Metadata elements not part of the general FAA metadata element set but used in PMS data sets are identified with the phrase “PMS Specific Element”. Metadata for a record set shall be transmitted in a file of the same name as the record set, except that the file name extension shall be “xml”. For example, if a record set is transmitted as GML in the file AIRFIELD_PMS_ARP_JFK. GML, the metadata would be transmitted as AIRFIELD_PMS_ARP_JFK.XML. Metadata shall generally be collected and provided at the feature level, however, metadata may be provided at the feature class level if all features in an instance of a feature class have identical metadata. Identification of metadata granularity is provided by the Identification_Information, Citation, and Other Citation Details metadata fields, which are used to identify to which specific features the metadata pertain. If all features in a feature set have the same metadata, the Other Citation Details field may be omitted. FGDC CSDGM Element FAA Metadata Element Definition Identification_Information Description Abstract Description of the contents of the data. SpecificUsage Description of how the data should be used Identification_Information Point_of_Contact IndividualName Name of person that developed data OrganizationName Organization that developed the data PositionName Title of person that developed the data DeliveryPoint Street address of the person that developed the data City City AdministrativeArea State PostalCode ZIP Code ElectronicMailAddress email address VoicePhoneLine Phone number Identification_Information Status Status Status of the data being submitted. Identification_Information Citation Dataset List of feature classes to which the metadata pertains Identification_Information Citation Other Citation Details Features List of features to which the metadata pertains A-45

Identification_Information Time_Period_of_Content BegUsageDateTime The first date/time for which the data are valid EndUsageDateTime The last date/time for which the data are valid Data_Quality_Information Positional_Accuracy HorizontalAccuracy EvaluationMethodName Name of data quality evaluation method EvaluationMethodDescription Description of data quality evaluation method VerticalAccuracy EvaluationMethodName Name of data quality evaluation method EvaluationMethodDescription Description of data quality evaluation method Pass Indication of whether data set passed or failed quality evaluation Data_Quality_Information Lineage Statement Description of the source of the data Spatial_Data_Organization_Information Point_and_Vector_Object_Information Point and Vector Object Count GeometricObjectCount Number of feature instances in data set. Spatial_Reference_Information Horizontal_Coordinate_System_Definition HorizontalDatum Horizontal datum of data set Code Four digit code for the state plane coordinate system Spatial_Reference_Information Vertical_Coordinate_System_Definition VerticalDatum Vertical datum of data set Entity_and_Attribute_Information Detailed_Description Attributes List of attributes to which the metadata pertains PMS Specific Element: rollUpMethod Description of averaging or other method used to develop condition values for higher order pavement entities. PMS Specific Element: ConditionMethod Name of condition index method PMS Specific Element: ConditionStandard Standard governing condition index method PMS Specific Element: FODMethod Name of FOD index method PMS Specific Element: FODStandard Standard governing FOD index method PMS Specific Element: FrictionMethod Device/method used to collect friction data FGDC CSDGM Element (continued) FAA Metadata Element Definition A-46

APPENDIX A CREATING GML FILES A.1 AUTOCAD TO GML Exporting Data from an AutoCAD data file that contains feature attributes to GML requires the use of AutoCAD Map: 1. Launch AutoCAD Map and open the desired data to be exported to GML. The example below is a simple branch data set. 2. Once the AutoCAD data is loaded, navigate to File>Export> Map 3D Export. A-47

3. Next, change the export File of Type to GML – Geography Markup Language and provide a Path and File name for the export GML and click OK. 4. The GML export options dialog will appear. The Dialog contains three tabs: Selection, Data and Options. Selection allows for specific features to be selectively exported, or you can choose to export all features. Data provides for the ability to map AutoCAD feature attributes to the corresponding ACRP standard field names, if the source data is not name congruent, but does contain compatible data and data types. The Options tab allows for modification of the resulting output coordinate system. A-48

5. Once these setting are set, clicking OK, initiated the file output process. The resulting output files will be found in the location that was sp ecified in the earlier step. The output location should contain a GML Data File and th e accompan yi ng XML Schema File. A.2 ARCGIS TO GML Ex porting Data from ArcGIS to G ML using the Si mple Features Profile requires the use of the ArcGI S Data I nteroperabilit y ex tension. However, to use the GM L ex port tools does not require activation or a license the I nteroperabilit y ex tension; however the extension mus t be installed. To export data sources to GML : A-49

1. Launch ArcCatalog or ArcMap 9.2 or higher (GML support begin with v9.2), for this example, ArcCatalog is used. 2. Locate and click the ArcToolbox icon on the Standard Menu button toolbar: 3. Once the ArcToolbox menu of tools appears, expand the Data Interoperability Tools Group and double-click Quick Export and the Quick Export dialog should appear. A-50

4. In the Quick Export dialog for the Input Layer navigate to an ArcGIS data source (Personal Geodatabase, File Geodatabase or SDE database) and select the feature class that you wish to export as GML Simple Features. For this example, a Personal Geodatabase is used. 5. Once the feature class has been added, you will be returned to the Quick Export Dialog. Verify the Input Layer is correct and click the button in the bottom left of the dialog under the Output Dataset section. Next, select GML SF-0 (Geography Markup Language Simple Features Level SF-0 Profile) as the Format and for Dataset select the path where you wish for the GML data files to be saved. If you wish to re-project the data (change coordinate systems or units) in the Output GML Data, you can select the new Coordinate system in this step as well. In this example, the output GML will be in the same coordinate system as the source feature class. 6. After setting the options in the Specify Output Data Destination dialog, click OK to return to the Quick Export Dialog. The Quick Export Dialog should reflect the settings by showing the name of the output GML data file as well as the output format (GMLSF). Once the settings are confirmed, click OK. A-51

7. After Clicking OK, the export process should begin running. Depending on the size of the data set this process can take a few seconds to several minutes to complete. At the end of the process the dialog should report the number of features exported successfully. If there is an error, this dialog will provide details of the errors encountered. 8. As a final step, verify the datafiles have been written to to speficifed folder in the file system. The output location should contain an GML Data File and the accompanying XML Schema File. A-52

APPENDIX B DATA TRANSLATION GUIDE FOR MICROPAVER AND AIRPAV AirPAV uses a numer ic al namin g sche me to denote branches and does not provide ex plicit branch identifiers. Taxiway s have feature I D’s of 100 throu gh 2600 with 100 being Ta xi wa y A an d 2600 be in g Ta xi wa y Z. Runw ay s appear to start at 6000, with aprons having featur e ID ’s b etween 2 700 and 6000. These numbers can be used for branch_pms_ke y, a lthoug h the user would have to have a strong understandi ng of the databas e to kno w that it would be possible to have both a branch 100, repre se nting all of Taxiway A, and a section 100, repres enting onl y a si ng le section in Taxiway A . NA=data not nativel y av ailable in source data set B.1 AIRPORT REFERENCE POINT Attribute MicroPAVER AirPAV Attribute MicroPAVER AirPAV ne tw or k_ sh ort_ na me ne tw or k. ne tw or ki d f eatures.aptid ne tw or k_ na me ne tw or k. na me NA network_pms_key ne tw or k. _nun iqueid feat ures.ap tid ne tw or k_ area sum(branch._area) sum(fe at ures.area) ne tw ork _pci calculate f ro m conditio ns.c onditio n wh ere conditions._latest= ye s calculate f ro m features. ins ppc i ne tw ork _pcr7 fr om airfield_p ms _arp. ne tw ork _pc i f ro m airfield_p ms _arp. ne tw ork _pc i ne tw ork _pcr3 fr om airfield_p ms _arp. ne tw ork _pc i f ro m airfield_p ms _arp. ne tw ork _pc i ne tw ork _pase r N A N A ne tw or k_ fo d calculate f ro m conditio ns.c onditio n wh ere conditions._latest= ye s NA ne tw or k_ fr iction_ in de x N A N A ne tw or k_ fr iction_ratin g N A N A ne tw ork _pc n_ va lu e N A N A ne tw ork _pcn _descriptor NA NA ne tw or k_ ea NA NA ne tw or k_ climat e N A N A B.2 BRANCH LOCATION bran ch_short_n am e b ranch.branchid determ ine fr om f eatur es .f eatur e_id bran ch_n am e b ranch.na me NA branch_pms_key bran ch._buni qu ei d d etermine f ro m featur es .f eatur e_id FA A_ ke y N A N A bran ch_are a b ranch._are a s um (f ea tures.area) bran ch_us e b ranch.us e f eature_cl (Shapefile o nl y) ne tw or k_ sh ort_ na me pare nt in ne tw or k.ne tw or ki d A PTID ne tw or k_ pm s_ke y b ranch._nuni qu ei d A PTID bran ch_pci calculate f ro m conditio ns.c onditio n wh ere conditions._latest= ye s calculate f ro m features. ins ppc i bran ch_pcr7 fr om airfield_p ms _bran ch.br an ch_pc i f ro m airfield_p ms _bran ch.br an ch_pc i bran ch_pcr3 fr om airfield_p ms _bran ch.br an ch_pc i f ro m airfield_p ms _bran ch.br an ch_pc i bran ch_pase r N A N A A-53

branch_fod calculate from conditions.condition where conditions._latest=yes NA branch_friction_index NA NA branch_friction_rating NA NA branch_pcn_value NA NA branch_pcn_descriptor NA branch_ea NA NA B.3 SECTION LOCATION section_id section.sectionid features.desc section_pms_key section._suniqueid features.feature_id FAA_key NA NA branch_short_name from parent in branch.branchid NA branch_pms_key section._buniqueid determine from featrures.feature_id network_short_name from parent in network.networkid features.aptid network_pms_key from parent in branch._nuniqueid features.aptid section_area section._length*section._width +section.[_area adjustment] features.area section_use from parent in branch.use determine from features.feature_id section_rank section.rank NA section_pms_surface section.surface features.pavetype section_constructed section.const_date features.conyear section_maint determine from table [work tracking] NA section_insp_date determine from table inspections features.inspdate section_ol NA NA section_ol_thick NA NA section_surface NA NA section_surface_thick NA NA section_base NA NA section_base_thick NA NA section_subbase NA NA section_subbase_thick NA NA section_subgrade NA NA section_subgrade_strength NA features.cbr or features.kvalue section_subgrade_unit NA NA section_design_gear NA from features.desacft section_design_mtow NA from features.desacft section_design_passes NA features.desops section_pci determine from conditions.condition features.insppci section_pcr7 from airfield_pms_section.section_PCI from airfield_pms_section.section_PCI section_pcr3 from airfield_pms_section.section_PCI from airfield_pms_section.section_PCI section_paser NA NA section_fod determine from conditions.condition NA section_friction_index NA NA section_friction_rating NA NA section_pcn_value NA NA section_pcn_descriptor NA NA Attribute (continued) MicroPAVER AirPAV Attribute MicroPAVER AirPAV A-54

section_ea NA NA section_traffic NA NA B.4 SECTION DISTRESSES section_id section.sectionid features.desc section_pms_key section._suniqueid features.feature_id FAA_key NA NA branch_short_name from parent in branch.branchid NA branch_pms_key section._buniqueid from features.feature_id network_short_name from parent in network.networkid features.aptid network_pms_key from parent in branch._nuniqueid features.aptid section_area section._length*section._width +section.[_area adjustment] features.area section_use from parent in branch.use determine from features.feature_id section_rank section.sectionid NA section_insp_date determine from table inspections features.inspdate Distress data elements in Paragraph 6.12, Distress Attribute Fields, have a one-to-one correspondence with the fields features.ac_allig_h through features.pcc_cornerspall_l. To determine the density, perform the calculation [features].[ac_allig_h]÷[features].[area]. Distress density data in MicroPAVER must be extracted from [extrapolated distress].[auxreal1], which has a many-to-one relationship with sections. B.5 SAMPLE UNIT LOCATION sample_id samples.samplenr NA sample_pms_key samples._smpuniqueid NA sample_date from parent in inspections.date NA section_id from parent in section.sectionid NA section_pms_key from parent in inspections._suniqueid NA branch_short_name from parent in branch.branchid NA branch_pms_key from parent in section._buniqueid NA network_short_name from parent in network.networkid NA network_pms_key from parent in branch._nuniqueid NA sample_area sample._samplesize NA sample_pms_surface from parent in inspections.inspected_surface NA sample_type sample.sampletype NA sample_pci NA NA sample_pcr7 NA NA sample_pcr3 NA NA sample_fod NA NA Attribute (continued) MicroPAVER AirPAV Attribute MicroPAVER AirPAV Attribute MicroPAVER AirPAV A-55

B.6 SLAB LOCATION slab_id NA NA slab_pms_key NA NA sample_date NA NA sample_id samples.samplenr NA sample_pms_key samples._smpuniqueid NA section_id from parent in section.sectionid NA section_pms_key from parent in inspections._suniqueid NA branch_short_name from parent in branch.branchid NA branch_pms_key from parent in section._buniqueid NA network_short_name from parent in network.networkid NA network_pms_key from parent in section.sectionid NA blowup_low from child data in distresses._quantity NA blowup_medium from child data in distresses._quantity NA blowup_high from child data in distresses._quantity NA corner_break_low from child data in distresses._quantity NA corner_break_medium from child data in distresses._quantity NA corner_break_high from child data in distresses._quantity NA ltd_crack_low from child data in distresses._quantity NA ltd_crack_medium from child data in distresses._quantity NA ltd_crack_high from child data in distresses._quantity NA d_crack_low from child data in distresses._quantity NA d_crack_medium from child data in distresses._quantity NA d_crack_high from child data in distresses._quantity NA jsd_low from child data in distresses._quantity NA jsd_medium from child data in distresses._quantity NA jsd_high from child data in distresses._quantity NA mi_cracking from child data in distresses._quantity NA patch_small_low from child data in distresses._quantity NA patch_small_medium from child data in distresses._quantity NA patch_small_high from child data in distresses._quantity NA patch_large_low from child data in distresses._quantity NA patch_large_medium from child data in distresses._quantity NA patch_large_high from child data in distresses._quantity NA popouts from child data in distresses._quantity NA potholes from child data in distresses._quantity NA polishing from child data in distresses._quantity NA pumping from child data in distresses._quantity NA scaling_low from child data in distresses._quantity NA scaling_medium from child data in distresses._quantity NA scaling_high from child data in distresses._quantity NA faulting_low from child data in distresses._quantity NA faulting_medium from child data in distresses._quantity NA faulting_high from child data in distresses._quantity NA shattered_slab_low from child data in distresses._quantity NA shattered_slab_medium from child data in distresses._quantity NA shattered_slab_high from child data in distresses._quantity NA shrinkage_crack from child data in distresses._quantity NA spall_joint_low from child data in distresses._quantity NA spall_joint_medium from child data in distresses._quantity NA spall_joint_high from child data in distresses._quantity NA spall_corner_low from child data in distresses._quantity NA Attribute MicroPAVER AirPAV A-56

spall_corner_medium from child data in distresses._quantity NA spall_corner_high from child data in distresses._quantity NA B.7 PHOTOGRAPH LOCATION image_id file image.iml images._imguniqueid NA FAA_key NA NA img_time NA NA img_date NA NA img_direction NA NA img_narrative file image.iml images.name NA img_filenpath file image.iml images._fullpath NA slab_id NA NA slab_pms_key NA NA sample_id NA NA sample_pms_key NA NA section_id from parent in section.sectionid NA section_pms_key file image.iml images._imuniqueid NA branch_short_name from parent in branch.branchid NA branch_pms_key from parent in section._buniqueid NA network_short_name from parent in network.networkid NA network_pms_key from parent in branch._nunuiqueid NA B.8 AIRFIELD EVENT event_id NA NA FAA_key NA NA event_type NA NA event_time NA NA event_date NA NA event_longitude NA NA event_latitude NA NA event_elevation NA NA event_depth NA NA narrative NA NA filenpath NA NA event_table NA NA event_foreign_key NA NA event_number NA NA event_num_result NA NA event_text_result NA NA slab_id NA NA slab_pms_key NA NA sample_id NA NA sample_pms_key NA NA section_id NA NA section_pms_key NA NA branch_short_name NA NA branch_pms_key NA NA network_short_name NA NA network_pms_key NA NA Attribute (continued) MicroPAVER AirPAV Attribute MicroPAVER AirPAV Attribute MicroPAVER AirPAV A-57

B.9 AIRFIELD DISTRESS distress_id distresses._duniqueid (MicroPAVER 6.x only) NA FAA_key NA NA distress_type distresses.description NA distress_severity distresses.severity NA distress_quantity distresses._quantity (metric) NA distress_units distresses._quantityunits NA distress_date from parent in inspections.date NA distress_longitude from distresses.utm_x NA distress_latitude from distresses.utm_y NA distress_elevation NA NA slab_id NA NA slab_pms_key NA NA sample_id from parent in samples.samplenr NA sample_pms_key distresses._smpuniqueid NA section_id from parent in section.sectionid NA section_pms_key from parent in inspections._suniqueid NA branch_short_name from parent in branch.branchid NA branch_pms_key from parent in section._buniqueid NA network_short_name from parent in network.networkid NA network_pms_key from parent in branch._nuniqueid NA B.10 AIRFIELD CONSTRUCTION construction_pms_key [work tracking]._whuniqueid concat(features.feature_id,”HistoryX”) where 1<X<10 construction_date [work tracking].date parse from features.historyX section_id from parent in section.sectionid features.desc section_pms_key [work tracking]._suniqueid features.feature_id branch_short_name from parent in branch.branchid NA branch_pms_key from parent in section._buniqueid from features.feature_id network_short_name from parent in network.networkid features.aptid network_pms_key from parent in branch.branchid features.aptid construction_activity [work tracking].work parse from features.historyX construction_reference [work tracking].project parse from features.historyX construction_material [work tracking].mattype parse from features.historyX construction_thickness [work tracking]._thickness parse from features.historyX construction_thick_unit [work tracking]._thickness_units parse from features.historyX construction_strength NA NA construction_str_unit NA NA construction_str_def NA NA Attribute MicroPAVER AirPAV Attribute MicroPAVER AirPAV A-58

APPENDIX C CONSTRUCTION LAYER RECORD SET EXAMPLE Consider the following hypothetical pavement section originally constructed in 1990 and rehabilitated in 2005: 1990 2005 The attributes for this hypothetical section are shown in the following table. A-59

Table C.1. c o n s t r u c t i o n _ p m s _ k e y c o n s t r u c t i o n _ d a t e s e c t i o n _ i d s e c t i o n _ p m s _ k e y b r a n c h _ s h o r t _ n a m e b r a n c h _ p m s _ k e y n e t w o r k _ s h o r t _ n a m e n e t w o r k _ p m s _ k e y c o n s t r u c t i o n _ a c t i v i t y c o n s t r u c t i o n _ r e f e r e n c e c o n s t r u c t i o n _ m a t e r i a l c o n s t r u c t i o n _ t h i c k n e s s c o n s t r u c t i o n _ t h i c k _ u n i t c o n s t r u c t i o n _ s t r e n g t h c o n s t r u c t i o n _ s t r _ u n i t c o n s t r u c t i o n _ s t r _ d e f 0001 3/1/1990 A01B 0001 Apron 1 0006 JFK 0001 Construct Apron 1 JFK-1990-01 SM 10 % CBR 0002 4/1/1990 A01B 0001 Apron 1 0006 JFK 0001 Construct Apron 1 JFK-1990-01 P-154 12 inch 30000 psi HWD 0003 5/1/1990 A01B 0001 Apron 1 0006 JFK 0001 Construct Apron 1 JFK-1990-01 P-304 12 inch 450,000 psi HWD 0004 6/1/1990 A01B 0001 Apron 1 0006 JFK 0001 Construct Apron 1 JFK-1990-01 P-401 6 inch 250,000 psi HWD 0005 6/1/2005 A01B 0001 Apron 1 0006 JFK 0001 Rehab Apron 1 JFK-2005-36A Mill -2 inch 0006 6/15/2005 A01B 0001 Apron 1 0006 JFK 0001 Rehab Apron 1 JFK-2005-36A P-401 2 inch 200,000 psi Design Description of each project. Note projects may require multiple lines if they involve multiple layers. Pavement network, branch, and section identifiers. These are all the same because this project occurs entirely within one section of one branch of one network. Date of construction. If date of completion of individual layers is known it can be used, otherwise the date of project completion should be used. PMS-assigned primary key for construction records. User assigned project number. Description of layer material and thickness. Note that removing material is considered a layer with negative thickness. Milling is shown, but this is applicable to all demolition activities. Material strength descriptor. Note that multiple strength methods can be used. This example shows a CBR for subgrade and moduli for constructed layers. Note that moduli based on HWD testing are shown for 1990 construction layers, but a design modulus is shown for the 2005 overlay. A -60