道路十年發(fā)展計劃10-YearPlan

1、Presented to:By:Venue:Date:Federal AviationAdministration10-Year Airport Pavement R&D PlanAirport Pavement Working GroupGordon Hayhoe, ANG-E262Sheraton Atlantic City Convention CenterApril 25, 20122Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 201210-Year Pla

2、n Outline Current Status. Areas of Work. Software Development. Non-destructive testing. Materials and construction.3Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Current Status Since publication of the first airport pavement R&D plan in 1993, a comprehens

3、ive 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. 4Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Computer Programs Since 1

4、9935Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Ancillary Computer Programs ConvertProfileFormat. Profile32. ProGroove. 10-View. NAPTF test vehicle control.6Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012National Airp

5、ort 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.7Federal AviationAdministrationAirp

6、ort Pavement Working Group 10-Year PlanApril 25, 2012Primary Areas of Work in New 10-Year Plan1. Pavement design, evaluation, and management software.2. Life cycle cost analysis.3. Non-destructive testing.4. Materials and construction processes.5. NAPTF.6. Field testing7. High Temperature Pavement T

7、est Facility.8Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Area 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

8、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.9Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Relationship

9、 Between Main Programs10Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Software 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

10、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.11Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Soft

11、ware 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.12Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25

12、, 2012Software 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.13Federal AviationAd

13、ministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Software 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 sh

14、ould be the target operating system. The future of Windows 8 is not clear.14Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Software Development Models PAVEAIR is an ASPX web application and will remain so. FAARFIELD and BAKFAA have been translated from VB 6.0

15、into VB.NET Windows Forms applications. ProFAA is being translated from VB 6.0 into a VB.NET Windows Presentation Foundation application.15Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Windows Forms Windows Forms is the traditional Microsoft Windows software

16、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).16Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Wi

17、ndows 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:17Federal AviationAdministra

18、tionAirport Pavement Working Group 10-Year PlanApril 25, 2012Features 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 functionalit

19、y. Can be translated to a Microsoft Silverlight application with reduced functionality with manageable effort.18Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Microsoft Silverlight Silverlight is Microsofts version of Adobe Flash. Can be compiled as a true sin

20、gle 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.19Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Life Cycle Cost Analysis (LCCA) Over 100 pages in AC 150

21、/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.20Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Life Cycle Cost Ana

22、lysis (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.21Federal AviationAdmi

23、nistrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Non-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.22Federal AviationAdministrationAirport P

24、avement Working Group 10-Year PlanApril 25, 2012Improve 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.23Federal AviationAdministrationAirport Pavement Working Group 10-Year PlanApril 25, 2012Improve the Efficiency of Pavement Condition Surveys for More Frequent and More Comprehensive Inputs Automated software applications for data processing. Crack detection. Crack