presented to: by: venue: date: federal aviation administration 10-year airport pavement r&d plan...

Presented to:

By:

Venue:

Date:

Federal AviationAdministration

10-Year Airport Pavement R&D Plan

Airport Pavement Working Group

Gordon Hayhoe, ANG-E262

Sheraton Atlantic City Convention Center

April 25, 2012

2Federal AviationAdministration

Airport Pavement Working Group – 10-Year PlanApril 25, 2012

10-Year Plan Outline

• Current Status.• Areas of Work.• Software Development.• Non-destructive testing.• Materials and construction.



Current Status• Since publication of the first

airport pavement R&D plan in 1993, a comprehensive collection of airport pavement design and evaluation computer programs have been developed.

• Development of the computer programs was supported by analytical and full-scale test work.



Computer Programs Since 1993

Name Date of

Adoption Advisory Circular

Description

PAVEAIR 2011 NA Web-based application for airport pavement management, including PCI evaluations.

COMFAA 3.0 2011 150/5335-5B Automatic PCN computation. FAARFIELD 1.3

2009 150/5320-6E FAA Rigid and Flexible Interactive Layer Design. Fully tested thickness design. Uses NIKE3D for rigid and LEAF for flexible.

ProFAA 2009 150/5380-9 Longitudinal roughness profile analysis, roughness index computation, and aircraft ride simulation.

LEDFAA 1.3 2003 150/5320-6D Change 3

Rewrite of LEDFAA 1.2 as a 32-bit program. Uses LEAF instead of JULEA. Updated flexible failure model. Updated aircraft library, includes A380.

FEAFAA NA 3D FEM program for rigid pavement response computation. Up to 9 slabs. Used to improve and extend FAA-NIKE3D.

FAA-NIKE3D NA 3D finite element modeling system. Custom modification of the NIKE 3D FEM system developed by Lawrence Livermore Labs.

COMFAA 2.0 2006 150/5335-5A ACN computation and thickness design by the FAA CBR and Westergaard methods.

BAKFAA 2003 Recomm-ended in

150/5370-11A

FAA Backcalculation of elastic layer properties using LEAF. Also computation of elastic layered system responses and used for LEAF development.

LEAF 2003 NA Layered Elastic Analysis FAA. Windows DLL layered elastic computational engine written in Visual Basic.

LEDFAA 1.2 1995 150/5320-16 FAA Layered Elastic Design. Windows-based 16-bit thickness design for flexible and rigid pavements. Used JULEA layered elastic computational engine. Development of DOS-Based LEDNEW by USACE.



Ancillary Computer Programs

• ConvertProfileFormat.• Profile32.• ProGroove.• 10-View.• NAPTF test vehicle control.



National Airport Pavement Test Facility

• CRDA with Boeing, joint funding and test plan development.

• Working group support and assistance.

• Primarily used to develop structural failure models for pavement thickness design procedures.

Six major construction cycles completed to date.



Primary Areas of Work in New 10-Year Plan

1. Pavement design, evaluation, and management software.

2. Life cycle cost analysis.

3. Non-destructive testing.

4. Materials and construction processes.

5. NAPTF.

6. Field testing

7. High Temperature Pavement Test Facility.



Area 1. Software

• Except for PAVEAIR, and a couple of others, the existing programs are considered to be technically mature.

• All require normal maintenance and adjustment to new pavement and computer technologies.

• Most require updating to the latest programming environments and operating systems.

• Integration of the programs and data structures is required.

• Web-based interoperability would be nice.



Relationship Between Main Programs



Software Structures• We are committed to further development

and maintenance of computer program applications.

• PAVEAIR is considered to be the “hub” application and should be the depository of almost all data required by the other programs.

• Current thinking is that the “satellite” programs should remain as individual applications linked to PAVEAIR by specialized services or other data pathways.



Software Structures (continued)

• All programs, including PAVEAIR, should be capable of being run stand-alone on individual personal computers.

• All programs should be capable of communicating with PAVEAIR over the internet.



Software Structures (continued)

• Different levels of integration.• FAARFIELD, COMFAA, and BAKFAA

should share pavement structures.• FAARFIELD and COMFAA should

share aircraft mixes.• ProFAA should probably be almost

completely independent, unless profiles are stored by PAVEAIR.



Software Development Models

• All programs except PAVEAIR were developed in VB 6.0.

• VB 6.0 is no longer supported by Microsoft and all programs must be translated into .NET applications, including all ancillary programs.

• Windows 7 should be the target operating system. The future of Windows 8 is not clear.



Software Development Models

• PAVEAIR is an ASPX web application and will remain so.

• FAARFIELD and BAKFAA have been translated from VB 6.0 into VB.NET Windows Forms applications.

• ProFAA is being translated from VB 6.0 into a VB.NET Windows Presentation Foundation application.



Windows Forms

• Windows Forms is the traditional Microsoft Windows software model.

• It might not be developed significantly beyond its current state.

• It is strictly a single computer software model.

• Communication over the internet is difficult (consider the 1-Click distribution model).



Windows Presentation Foundation

• Windows Presentation Foundation (WPF) is an alternative Windows software model with potential to displace Windows Forms for single computer use and allow a path to conversion to web-based applications.

• Features of WPF distinct from Forms are:



Features of WPF distinct from Windows Forms

• User interface and application code bases are almost completely separate (XAML versus VB).

• Automatic component resizing is built in.• Can be compiled as a browser plug-in

with reduced functionality.• Can be translated to a Microsoft

Silverlight application with reduced functionality with manageable effort.



Microsoft Silverlight

• Silverlight is Microsoft’s version of Adobe Flash.

• Can be compiled as a true single computer application or a true web-based application (plug-in) by changing only a couple of lines of code.

• Need to decide which model to use very soon.



Life Cycle Cost Analysis (LCCA)

• Over 100 pages in AC 150/5320-6E.– 4 ½ pages are devoted to LCCA.

• 300 pages in AIP Handbook, Order 5100.38C.– 1 page is devoted to LCCA methodology.

• This is not enough to provide guidance when jobs are bid based on LCCA.



Life Cycle Cost Analysis (continued)

• Modify the AAPTP AirCost Excel application to communicate with PAVEAIR.

• Run cost analyses and determine the data requirements to begin defining standard procedures for airport pavement LCCA.

• This will require expert help from engineering economist consultants.



Non-Destructive Testing

• After software development, non-destructive testing is seen as the next most important work area.

• The objective will be to improve the predictive capability of PAVEAIR.



Improve the Efficiency of Pavement Condition Surveys for More Frequent and More Comprehensive Inputs

• Automated equipment for data collection.– Crack surveys.– Roughness profile measurement.– HWD, RWD, GPR.



Improve the Efficiency of Pavement Condition Surveys for More Frequent and More Comprehensive Inputs

• Automated software applications for data processing.– Crack detection.– Crack characterization.– PCI from crack surveys.– ProFAA.– PCN and load evaluation.– Groove measurement and evaluation.



Vehicle for Evaluation of NDT Equipment and Software



Project List



Project List (continued)



Download the Brochure for More Information

http://www.airporttech.tc.faa.gov/10YearPlan/



Also Download the 1993 Brochure

http://www.airporttech.tc.faa.gov/naptf/download/index1.asp#docum

presented to: by: venue: date: federal aviation administration 10-year airport pavement r&d plan...

Documents

year plan

pavement structures

new pavement

test plan development

group support

software structures

ancillary programs

evaluation computer