The issue of road use and needs on National Forests has grown in visibility and importance. Road use data can be a surrogate indicator of human impact, sedimentation, vectors for pathogens etc. Maintaining extensive road monitoring systems is cost prohibitive in most areas. This project is to review current data collection methods, and statistically develop and verify a design, which would utilize a minimum number of monitors (traffic counters) to predict road use across a forest. The potential for cost effectively retrieving the data automatically will also be reviewed.

1. Define the frequency of data collection needed and the type of information traffic counters need to collect and store.
   
   
2. Based on preliminary methods and algorithms developed by the Forestry & Range Sciences Laboratory, prepare a counter placement procedure, data collection instructions and procedures, data collection forms and a data collection relational database that can be integrated seamlessly into data analysis.
   
   
3. Define test equipment needs and prepare a test plan for FY 01 testing of a developmental system.

1. Procure all needed test equipment and install it, if necessary, at test locations.
   
   
2. Develop final data analysis algorithms and software. Ready for beta testing by test forests and R6 engineering by the end of April 2001. The software shall be an integrated package consisting of the following modules:
   
   
• Data Collection & Review Module
  
  
• Allows review of raw data prior to final entry into database.
  
  
• Formats data into predefined fields and enters it into a data table.
  
  
• Provides for exportation of the data to Oracle, Access and INFRA.
  
  
• Counter Location Map w/ Data Filter Module
  
  
• Recalls data from database, with attributes, and creates a map overlay of counter locations.
  
  
• Allows interactive count comparisons between selected counters in a group.
  
  
• Allows the user to set an interactive comparison filter to determine the significance of count differences within a group, and for the elimination of redundant counters from the data set if desired by the user.
  
  
• Allows display of a revised counter layout on the map after each iteration of the data filter.
  
  
• Cluster Analysis Module
  
  
• Builds routes and determines the interrelationship between counters.
  
  
• Allows user to make final selection of counters to be used for future traffic estimates and year-by-year revalidation of forest traffic count model.
  
  
• Forest Count Modeling Module
  
  
• Uses future count data to estimate road use by week, month and season.
  
  
• Provides statistical algorithms to predict future road use and measure modeling validity.
  
  
• May provide interactive graphic displays (if desirable) for user decision making.
  
  
• Help Module
  
  
• Interactive help for the user integrated into each module.
  
  
3. Develop ARMAS user guides as follows:
   
   
• Scan R6 Traffic Surveillance Guide for electronic distribution as a ARMAS user general reference.
  
  
• Develop a Counter Placement Guide for ARMAS Users.
  
  
• Develop, if necessary, instructions for the use of ARMAS software. This document would supplement the ARMAS Program Help Module.
  
  
• Develop a ARMAS Training Module. This would most likely be a PowerPoint Slide Presentation to support the training of new ARMAS users.
  
  
4. R6 Engineering and Forests commence ARMAS system and software beta testing.
   
   
5. After 3 months of testing, based on preliminary testing results, define and make any software or hardware changes indicated.

1. Complete Module 1 and hardcopy of User's Guide. Deliver to R6 test Forests.
   
   
2. IMI Steering Committee meeting 2002: Demo Module 1 & 2, display reports, maps, route analysis and SAS routines.
   
   
3. Edit and reprint R6 Traffic Surveillance Manual.

ARMAS development was discontinued in FY03. Still needed:

1. Verify software algorithms and modify software as indicated.
   
   
2. Complete context sensitive help.Package software for distribution.
   
   
3. Support and/or monitor system implementation as needed.
   
   
4. Publish final report with instructions on system use, and recommendations on system implementation.