Web-Based Airport Pavement Management System PAVEAIR Web-Based Airport Pavement Management System IPMS Summit, Singapore Gordon Hayhoe, FAA Airport Technology R&D Branch October 8, 2008

Outline FAA sponsorship of airport pavement data management software applications and relationship with other software applications. Development, specifications, and current status of a new Web-based airport pavement data management system called PAVEAIR. Problem with computing PCN for large international airports. Integration of pavement design and evaluation software applications.

FAA Sponsored Pavement Management Systems Development of Mainframe PAVER was started in 1968 for use on mainframe computers. Development was by the United States Army Corps of Engineers (ACOE) for use by the Department of Defense (DOD). Development of MicroPAVER was started in 1985 for use on microcomputers. Funding was by the FAA and development by the ACOE.

History of PAVER, cont. Delivered in 1987, the FAA version of MicroPAVER had the following functions: Divide airport pavements into uniform sections to comply with the existing FAA pavement management Advisory Circular. Store the pavement condition history in accordance with the Pavement Condition Index (PCI) method. Store pavement construction and maintenance history. Store deflectometer test results for overlay design. Generate network level reports for planning, budgeting, inspection scheduling, and pavement condition at any time. Provide project level analysis for maintenance and repair (M&R) requirements and perform economic analyses for different M&R alternatives.

AC 150/5380-7A Requires PMS Software

PAVEAIR Background A joint initiative between the FAA and the National Association of State Aviation Officials (NASAO) to develop a system for sharing information to optimize the expenditure of funds. An Internet (Web) based system was deemed to be the best option considering the mature status of web-based applications.

PAVEAIR Background The FAA also has a need for system-wide dissemination and analysis of the performance of FAA sponsored pavement projects. A collection of airport pavement design and evaluation computer programs has also been developed and a dedicated PMS software application would tie these programs together.

FAA Pavement Software Applications FAARFIELD Thickness Design BAKFAA Strength Evaluation ProFAA Roughness Condition Evaluation COMFAA PCN Load Rating PAVEAIR Web-Based PMS

Software Categories Pavement Thickness Design. LEDFAA – layered elastic design model (AC 150/5320-6D). FAARFIELD – layered elastic and finite element design models (Draft AC 150/5320-6E). COMFAA – CBR and Westergaard design models (AC 150/5320-6D). Pavement Load Evaluation. COMFAA – ACN-PCN analysis (AC 150/5335-5A). Pavement Condition Evaluation. BAKFAA – backcalculation of layer properties with layered elastic model (AC 150/5370-11A). ProFAA – pavement profile analysis and roughness index calculation (Draft AC 150/5380-9).

Software Categories Pavement Response Analysis. LEAF – layered elastic model, BAKFAA is the user interface. FEAFAA – finite element model, stand alone user interface. Pavement Data Management. PAVEAIR – internet-based database management system currently under development. The first version will have the same functionality as Micro PAVER 5.3. Subsequent development will expand the pavement management functionality and integrate the pavement design and evaluation tools listed above.

PAVEAIR Requirements ● Web-based application that provides a system for easy dissemination of information for airport pavement construction, maintenance, and management. ● Data for multiple airports available on a single server connected to the web. ● Suitable for installation and use on: - Single PC, - Private network, - Intranet, or Internet.

PAVEAIR Requirements, cont. The FAA to have a server installed at the WJHTC to be a repository for civil airport projects funded under the Airport Improvement Program (AIP). Make the complete application available for free download: As a set of installation files. Full source code. Documentation for installation and operation.

PAVEAIR Architecture Workstations Server DEN JFK DCA … Disk Drive(s)

Database Architecture System Databases Import Databases User Databases

ASPNETDB Created by the Microsoft ASP.NET Logon Control Authentication and authorization Stores user information, session variables, session states, etc. Uses ASP.Net Logon control Uses ASP.Net Create User Wizard Uses ASP.Net Reset password, change password controls Uses ASP.Net Logon View control Uses ASP.Net Membership provider Uses ASP.Net Profile provider

Registration form in new UI

Membership Configuration in Web. Config Membership Configuration in Web.Config. (fields are set by the database administrator). <connectionStrings> <add name="PDMSASPNET" connectionString="Data Source=PAVEMENTS; Initial Catalog=ASPNetDB;Integrated Security=True" /> … </connectionStrings> <membership defaultProvider="PDMSMember" > <providers> <add name="PDMSMember" type="System.Web.Security.SqlMembershipProvider" connectionStringName="PDMSASPNET" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" passwordStrengthRegularExpression="" /> </providers> </membership>

Profile Configuration <anonymousIdentification enabled ="true" cookieless ="AutoDetect"/> <profile defaultProvider ="PDMSMember" enabled ="true "> <providers > <add name ="PDMSMember" type ="System.Web.Profile.SqlProfileProvider" connectionStringName="PDMSASPNET" applicationName="/"/> </providers> <properties > <add name="FirstName" type ="String"/> <add name="Lastname" type ="String"/> <add name="Title" type ="String"/> <add name="Organization" type ="String"/> <add name="Address1" type ="String"/> … <add name="CurrentDatabase" type="String" allowAnonymous ="true"/> </properties> </profile>

Authentication and authorization <authentication mode="Forms" > <forms name =".DMSAUTH" loginUrl="Login.aspx" protection="All" timeout="30" path="/" requireSSL="false" slidingExpiration="true " cookieless="AutoDetect"/> </authentication > <location path ="Datamanagement"> <system.web > <authorization > <deny users ="?"/> </authorization> </system.web> </location>

PDMSStatic Stores top level configuration data. PCI categories, colors, pavement roughness categories, etc.

Databases: Import Compatible with MicroPAVER. Import Steps: Able to import Micro Paver e60 file. Able to import Micro Paver MDB file. Import Steps: Data is uploaded into PDMSPaverImport. Data is converted and temporally stored in PaverToPDMS. Data is then copied to a new PAVEAIR database.

PAVEAIR User Databases A User Database is created for each Inventory (data owner). Logically divided into Networks, Branches, and Sections. All work is performed on individual sections. The database engine is Microsoft SQL Server.

Microsoft SQL Server Six Versions. Workgroup, Standard, and Enterprise ($750 to $9,000 and up depending on the number of client licenses) Compact, Express, and Developer (free, free, and $49) The first three are intended for medium-to-large Internet-connected applications. The second three are intended for small Internet-connected applications and for single-user stand-alone applications

Microsoft SQL Server The single-user version of PAVEAIR uses SQL Server Express Edition as the default. Use on a single PC requires the installation of Microsoft Internet Information Services (IIS), available free. SQL Server Express is a component of the Microsoft Framework and is installed with the operating system for Windows XP and Vista.

FAA Compliance Requirements Use of FAA approved page and form templates and request for waivers. Modifications required for some UI components, such as menu bar. Modifications to be documented and justification provided. Registration of web application with the FAA IT organization.

U.S. Government Section 508 Accessibility Requirements § 1194.1 Purpose. The purpose of this part is to implement section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d). Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

Section 508 Accessibility Requirements Text equivalent for non-text elements. Information conveyed with color is also available without color. Table Row & Column headers should be identified. Use automatic Compliance Check Tools. Accessibility Checker (Visual Studio & Expression Web) Fangs (a screen reader emulator). Online Web Accessibility Initiative Checker.

Section 508 Accessibility Requirements Unacceptable without an alternative shaded version or maybe mouse-over text descriptions of the color code.

Other Requirements ASTM Formulas and functions ASTM D 5340, Standard Test Method for Airport Pavement Condition Index Surveys, as listed in AC 150/5380-7A, Airport Pavement Management Program. Formulas and functions Based on those published in “Pavement Management for Airports, Roads, and Parking Logs” by M. Y. Shahin. Federally mandated Privacy Policy

Current Status of PAVEAIR – Subject to Testing and Reviews Prototype User Interface and master page template completed. Database structure defined and implemented. Micro PAVER import completed. Logon and profile modules completed. Inventory and Work modules completed. Now working on the PCI module. Tentative first deployment – January, 2010.

Registration form in new UI

Possible PAVEAIR Implementations By the FAA for AIP projects. By FAA regions for small airports. By state DOT’s for GA airports (NASAO interest). By consulting and engineering services companies for private or customer only access. Will continue support and development after initial deployment; for example include functions to comply with existing FAA GIS Standards.

PAVEAIR Point of Contact Albert Larkin FAA Airport Technology R & D Branch AJP-6312, Building 296 William J. Hughes Technical Center Atlantic City, NJ 08405 Phone: (609) 485-5552 Email: albert.larkin@faa.gov

ACN-PCN ACN is Aircraft Classification Number. ICAO requires that aircraft manufacturers publish ACN charts for all of their aircraft. PCN is Pavement Classification Number If the ACN of a particular aircraft is larger than the PCN of an airfield pavement then the aircraft must operate at reduced load or at reduced traffic level.

ACN-PCN is an ICAO Standard

AC 150/5335-5A Methodology The procedure for computing PCN on rigid pavements given in AC 150/5335-5A sometimes gives unreasonable PCN values when the aircraft mix contains: A large number of narrow body aircraft (737, A320, etc.). A relatively small number of new large wide bodies such as the Boeing 777-300 ER. The procedure tends to produce a PCN for one of the narrow bodies as the critical aircraft, indicating that the wide body operations should be restricted.

ACN-PCN Working Group A small working group is currently working on trying to modify the procedure for computing PCN. It is intended to widen the scope of the working group next year to provide a review body and an implementation body. Points of contact for more information are: Rodney Joel, FAA AAS-100, rodney.joel@faa.gov. Ken DeBord, Boeing Commercial Airplane Co., Kenneth.J.DeBord@boeing.com.

Procedure for Computing PCN 1) Identify pavement features and properties. 2) Determine traffic mixture. 3) Convert traffic to equivalent traffic of “critical”airplane (very time consuming). 4) Determine maximum allowable operating weight of the critical airplane (time consuming). 5) Determine the ACN of the critical airplane at its maximum allowable weight. 6) Report PCN.

Modifications to COMFAA Added a batch mode for computing the design thickness for all airplanes in the mix. Added an alternative cumulative damage factor procedure for finding equivalent departures to replace the current ratio-of-wheel-loads procedure in AC 150/5320-6D. Automated the computation of equivalent traffic of the critical airplane. Automated the computation of the maximum allowable load. Improved the external file functions.

Batch Thickness Computation

Batch Thickness Output Rigid Pavement Thickness Design by the PCA Method - Units are English No. Aircraft Name Gross Wt. Coverages k Value Des. Thickness 0 A300 375,000 17,091 323.0 13.23 1 A380-Body 1,235,000 353 323.0 11.60 2 A380-Wing 1,235,000 393 323.0 11.74 3 B727-200 172,000 2,616 323.0 11.00 4 B737-300 150,500 442,660 323.0 13.57 5 B737-700 174,700 597,077 323.0 14.72 6 B747-400 873,000 5,306 323.0 12.84 7 B757 250,000 102,589 323.0 11.49 8 B767-300ER 478,000 54,861 323.0 15.57 9 B777-200 662,000 28,899 323.0 14.44 10 DC-10 458,000 9,330 323.0 12.45 11 DC-8-63 358,000 1,785 323.0 11.84 12 DC-9-30/40 115,000 177 323.0 8.84 13 MD11 621,000 905 323.0 12.26

Batch Gross Weight Computation

Batch Gross Weight Output Conversion Conversion Airplane Critical Airplane No. Airplane Airplane Covs Covs-to-Failure Equivalent Covs 1 A300 17,091 2,105,638 2,496 2 A380-Body 353 669,522 162 3 A380-Wing 393 1,075,368 112 4 B727-200 2,616 25,233,793 32 5 B737-300 442,660 29,166,483 4,667 6 B737-700 597,077 9,536,103 19,255 7 B747-400 5,306 1,291,115 1,264 8 B757 102,589 52,971,458 596 9 B767-300ER 54,861 307,531 54,861 10 B777-200 28,899 500,671 17,751 11 DC-10 9,330 3,085,253 930 12 DC-8-63 1,785 2,600,681 211 13 DC-9-30/40 177 > 100,000,000 0 14 MD11 905 812,110 343 Library file name = C:\D Current\ACN-PCN\COMFAA 09-26-06\COMFAAaircraft DIA Rigid.Ext Evaluation pavement type is rigid Equivalent coverages computed with the PCA method. Maximum gross weight computed with the PCA method. k Value = 323.0 lbs/in^3 flexural strength = 650.0 psi Evaluation pavement thickness = 17.00 in Critical Airplane = B767-300ER Critical Airplane Coverages-to-Failure = 307,531 Critical Airplane Total Equivalent Coverages = 102,680 Critical Airplane Allowable Gross Weight = 514,185 lbs B767-300ER, English Units WEIGHT PCNT ON MAIN NO. OF WHLS. CONTACT AREA CONTACT PRESSURE lb in^2 psi 514,185 92.40 4 297.19 200.00 Coordinates of wheels End ACN Start ACN Input No. X Y X Y X Y 1 0.00 0.00 0.00 0.00 0.00 -22.50 2 0.00 45.00 0.00 45.00 0.00 22.50 3 56.00 0.00 56.00 0.00 56.00 -22.50 4 56.00 45.00 56.00 45.00 56.00 22.50 SUPPORT PAVEMENT RAD. REL. WHEEL K VALUE THICKNESS STIFFNESS ACN STRESS FACTOR 73.68 19.33 76.05 104.94 398.88 8/4 147.36 17.42 59.14 92.60 398.87 0/4 294.72 15.35 45.23 78.58 398.86 0/4 552.58 13.41 34.92 65.40 398.86 0/4

Batch Gross Weight Output Cont. k Value = 323.0 lbs/in^3 flexural strength = 650.0 psi Evaluation pavement thickness = 17.00 in Critical Airplane = B767-300ER Critical Airplane Coverages-to-Failure = 307,531 Critical Airplane Total Equivalent Coverages = 102,680 Critical Airplane Allowable Gross Weight = 514,185 lbs B767-300ER, English Units WEIGHT PCNT ON MAIN NO. OF WHLS. CONTACT AREA CONTACT PRESSURE lb in^2 psi 514,185 92.40 4 297.19 200.00 Coordinates of wheels End ACN Start ACN Input No. X Y X Y X Y 1 0.00 0.00 0.00 0.00 0.00 -22.50 2 0.00 45.00 0.00 45.00 0.00 22.50 3 56.00 0.00 56.00 0.00 56.00 -22.50 4 56.00 45.00 56.00 45.00 56.00 22.50 SUPPORT PAVEMENT RAD. REL. WHEEL K VALUE THICKNESS STIFFNESS ACN STRESS FACTOR 73.68 19.33 76.05 104.94 398.88 8/4 147.36 17.42 59.14 92.60 398.87 0/4 294.72 15.35 45.23 78.58 398.86 0/4 552.58 13.41 34.92 65.40 398.86 0/4

FAA Pavement Software Applications FAARFIELD Thickness Design BAKFAA Strength Evaluation ProFAA Roughness Condition Evaluation COMFAA PCN Load Rating PAVEAIR Web-Based PMS

Integration of the Software Applications? Current attempts at integrating the different applications is to Make the file formats compatible, and all XML. Maybe launch other applications from PAVEAIR. Tighter integration is not currently planned. Would tighter integration be useful or would it just make life more complicated?

Conclusion QUESTIONS?