1 / 28

10-Year Airport Pavement R&D Plan

10-Year Airport Pavement R&D Plan. Airport Pavement Working Group. Gordon Hayhoe, ANG-E262. Sheraton Atlantic City Convention Center. April 25, 2012. 10-Year Plan Outline. Current Status. Areas of Work. Software Development. Non-destructive testing. Materials and construction.

anahid
Download Presentation

10-Year Airport Pavement R&D Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 10-Year Airport Pavement R&D Plan Airport Pavement Working Group Gordon Hayhoe, ANG-E262 Sheraton Atlantic City Convention Center April 25, 2012

  2. 10-Year Plan Outline • Current Status. • Areas of Work. • Software Development. • Non-destructive testing. • Materials and construction.

  3. 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.

  4. Computer Programs Since 1993

  5. Ancillary Computer Programs • ConvertProfileFormat. • Profile32. • ProGroove. • 10-View. • NAPTF test vehicle control.

  6. 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.

  7. Primary Areas of Work in New 10-Year Plan • Pavement design, evaluation, and management software. • Life cycle cost analysis. • Non-destructive testing. • Materials and construction processes. • NAPTF. • Field testing • High Temperature Pavement Test Facility.

  8. 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.

  9. Relationship Between Main Programs

  10. 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.

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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).

  16. 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:

  17. 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.

  18. 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.

  19. 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.

  20. 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.

  21. 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.

  22. 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.

  23. 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.

  24. Vehicle for Evaluation of NDT Equipment and Software

  25. Project List

  26. Project List (continued)

  27. Download the Brochure for More Information http://www.airporttech.tc.faa.gov/10YearPlan/

  28. Also Download the 1993 Brochure http://www.airporttech.tc.faa.gov/naptf/download/index1.asp#docum

More Related