Using ArcView to Enhance Regional Mobility Through Ridematching

Authors: Melanie Rose & Ian Von Essen, Spokane County, Washington

Abstract
Defining Issue: Spokane County is affected by the Washington State Commute Trip Reduction (CTR) Law and is a non-attainment area for Carbon Monoxide (CO) and fine particulate matter (PM 10) air pollution. In order to meet the trip-reduction goals of the CTR Law and improve air quality, it is critical that aggressive measures are taken to decrease the use of single occupant vehicles, reduce traffic congestion and enhance regional mobility.
GIS Solution: Using a federal ISTEA grant (Intermodal Surface Transportation Efficiency Act), Spokane County enhanced its current ridematching software program, TransMatch, to an upgraded 2.0 version utilizing GIS technology (ArcView). TransMatch is used to provide free ridematching services to local employers, their employees and the general public. By using TransMatch to link commuters together into carpools and vanpools, the greater Spokane area will experience a decrease in traffic congestion and an improvement in air quality.
Application or Methodology: TransMatch 2.0 uses GIS technology to provide a visual ridematching tool which is both flexible and user-friendly. In essence, TransMatch links a database of applicants with ArcView to visually find potential carpool and vanpool partners. The matches are based on the commuter's origin, destination, work schedule and preferences (drive/ride; smoking/no smoking, etc.) ArcView is used to facilitate this process through multiple matching techniques: a radius match from the applicant's origin/destination, by neighborhood and corridor/route matching using the on-screen map. This visual matching also allows geographic barriers such as mountains, lakes, rivers, freeways, and bridges to be identified, for enhanced accuracy in matching potential ridesharing partners.
Software: The application was written using Microsoft Access, ArcView and Wessex street file data. The purpose of the paper is to highlight the application and its functions, as well as review the technical challenges encountered during the enhancement of TransMatch to incorporate GIS technology and meet the needs of other public agencies across the Pacific Northwest who are also using TransMatch 2.0 to provide ridematching services to the general public.

Introduction
Mobility is a growing issue in many communities. Roadways are becoming increasingly crowded with more people making trips in their automobiles, alone. Rising traffic congestion and air pollution have caused many organizations to seek solutions, such as encouraging solo drivers to share the ride.

In 1991, the Washington State Legislature adopted the Commute Trip Reduction (CTR) Law as part of the Washington Clean Air Act, to help improve air quality while reducing traffic congestion and energy consumption. The CTR law requires local jurisdictions in the state's most populated counties to adopt commute trip reduction ordinances detailing requirements for major employers. Employers with 100+ full-time, day shift employees must develop and implement trip reduction programs which encourage the use of alternatives to the single-occupant vehicle for the commute trip.

Specific goal reductions in employee single occupant vehicle trips (SOV) and vehicle miles traveled (VMT) are set forth by the CTR Law, in order to accomplish the broad policy objectives of reduced air pollution, traffic congestion and dependency on foreign fuel.

An employer's trip reduction program consists of a variety of actions to encourage employees to reduce the frequency and distance of solo commuting. Transportation alternatives include riding the bus, carpooling, vanpooling, bicycling, walking or telecommuting. Given the location of many employment sites, carpooling is the most realistic and popular option for employees. Therefore, employers often include "ridematching employees into carpools and vanpools" as a key strategy in their commute trip reduction programs.

Spokane County is one of nine counties affected by Washington State's Commute Trip Reduction (CTR) Law. Located in the far eastern portion of the state, Spokane County is bordered by several rural counties and North Idaho. Due to the topographical features of the area, Spokane County is a non-attainment area for Carbon Monoxide (CO) and fine particulate matter (PM 10) air pollution. In order to meet the trip reduction goals of the CTR Law and improve air quality, aggressive measures are needed to decrease the use of single occupant vehicles, reduce traffic congestion and enhance regional mobility.

In 1992, when implementation of the CTR Law began in Spokane County, the primary commute alternatives offered by the local transit agency to employers were transit and vanpool. However, these modes weren't realistic options for many employers, due to their location and size. In order to encourage widespread carpooling and help meet the goals of the CTR Law, employers needed a regional ridematching service which could match their own employees together into carpools or link them with employees at neighboring worksites, Although most employees live within the urban areas of Spokane County, a great many also live in the outlying areas of rural Spokane County, surrounding counties and North Idaho and travel great distances to their work locations.

The potential for success with a regional ridematching program had been demonstrated in many other regions throughout the state and country. At the time, Spokane's local transit agency offered a ridematching service which involved a manual matching process using commuter information tracked in a database. Not only was the matching process cumbersome and time-intensive (25 minutes per match), but the staffing level wasn't sufficient to handle the volume of ridematch requests. In addition, the existing data was not regularly maintained or purged. When the local transit agency did not express interest in improving and upgrading their ridematching system, Spokane County decided to acquire a system and provide ridematching services which would meet the needs of employers affected by the Commute Trip Reduction Law.

TRANSMATCH 1.0
Although Spokane County staff did not have a detailed list of program features, they had a vision of what would be needed from the new ridematching system. This vision included:

In the Spring of 1993, Spokane County began a national search for a regional ridematching system to meet their needs. Various rideshare and transit agencies across the United States were contacted and queried about their ridematching software. In most cases, the current ridematching software was DOS-based and run off a mainframe computer, which did not meet Spokane County's needs. And, the few PC-based ridematching programs which did exist were cost-prohibitive. In fact, there was a gap in the products available for ridematching employees. What was available served the limited needs of a single employer and the complex needs of a densely-populated, multi-county region. There was no reasonably-priced ridematching software on the market which served the needs of a mid-sized county, such as Spokane.

Spokane County then looked internally to its own System Services Department for a programmer to develop a ridematching program. The result of this effort was TransMatch 1.0, which was developed in about six months at a cost of approximately $10,000. Operating on a PC and based in FoxPro 1.0, TransMatch 1.0 performed three types of matches with commuter information.

  1. Radius matches - by the applicant's origin and destination
  2. Box matches - quasi-linear path where a series of boxes were created on the digitized map along the travel corridor to match applicants from outlying areas
  3. Other matches - by zip code or neighborhood

At the time, Spokane County's GIS department was in the process of geo-coding and creating street files for the entire County. This process was 62% complete and most outlying areas were not yet geo-coded when TransMatch 1.0 was developed. TransMatch 1.0 needed a map to perform the box matches, so the US West map for Spokane County was digitized and calibrated with X-Y coordinates and used to perform this function.

Although TransMatch 1.0 met the basic needs of Spokane County and employers, the box match feature continued to be problematic. The process to perform a box match was labor intensive, due to the time spent creating linked boxes on the computer screen. This function used a great deal of computer memory which further slowed down the process. In addition, because the outlying streets weren't accurately plotted, the matches created with the box technique were valid but not precise because the match area was much larger than was realistic and the operator had to go back in and sort through each match manually, to find the most realistic matches for the applicant. A typical box match took about 10 minutes to perform, while a standard radius match could be performed in under three minutes.

By the Spring of 1994, Spokane County was already identifying upgrades which were needed for TransMatch. Technology was rapidly improving, GIS street file data was nearly complete and FoxPro database software was being phased out in favor of MS Access.

UPGRADING TO TRANSMATCH 2.0
Spokane County recognized the need to upgrade the capabilities of TransMatch to meet growing employer needs, internal operational needs and strengthen the weaknesses of TransMatch 1.0. Using a federal ISTEA grant (Intermodal Surface Transportation Efficiency Act) secured, in part, to upgrade TransMatch, Spokane County set out to enhance its current ridematching software to an upgraded TransMatch 2.0 version utilizing GIS technology.

On the surface, the upgrade seemed easy -- take the basic functionality of TransMatch 1.0 and enhance it with current technology. However, three factors caused the project to become much more complicated:

  1. a change in the fundamental database program from FoxPro to Access;
  2. dramatic technological advances in GIS software; and
  3. meeting the needs of diverse public agencies from across the Northwest who now wanted to use TransMatch in their region.

The challenge of upgrading to TransMatch 2.0 had two parts -- to identify what was needed and then figure out how to do it. Beginning with the basic functions of TransMatch 1.0 on a blank page, the first challenge was to identify the critical functions and features needed for enhanced ridematching in Spokane County, including:

In addition to Spokane's needs, the other public agencies interested in using TransMatch identified their common and agency-specific requirements. The most common and feasible elements were added to Spokane's list and included:

Armed with a diverse set of user needs, one of the key challenges was to make TransMatch 2.0 specific enough for Spokane County, yet general enough to be used by multiple agencies. And, the related technological challenge was to create a software program which was not cumbersome, time consuming and complex for users.

The dramatic advances in GIS technology and the availability of complete street file data for most outlying areas were incorporated into TransMatch 2.0. On-screen mapping greatly enhanced the matching opportunities for linear path and outlying areas by allowing the user to select a corridor or route to generate matches. Potential matches could be selected and de-selected visually, allowing the user to better customize matches. And, the on-screen GIS map allowed the user to identify and compensate for geographic barriers.

A great deal of time was spent during the development of TransMatch 2.0 to ensure the mapping capabilities and street file data would enhance the usability of the software and the matching functions.

The on-screen mapping feature of TransMatch 2.0 is provided by ArcView 2.1 and street file data. After considering various GIS vendors, Spokane County selected Esri for the following reasons:

In addition to GIS software, Spokane County needed complete, updated street file data for the entire region to run TransMatch 2.0. Although Spokane County's own GIS street files were now complete, they did not include surrounding counties or North Idaho. Therefore, Spokane County looked to outside vendors for the needed street file information. Wessex was selected as the primary vendor of street file data because their data is compatible with TransMatch 2.0 and is provided at a reasonable price for the initial data and future upgrades. In addition, Wessex was willing to break down the street file data into regions and sell us only the files we needed, rather than the entire United States. The attractive price and flexibility of Wessex added to the cost-effectiveness of TransMatch.

The development, programming and testing of TransMatch 2.0 took nearly one year. Four beta test sites were established during the final stages of development, in exchange for a complimentary copy of TransMatch 2.0 and technical support, for a limited period of time. The beta sites included Spokane County, Kitsap Transit in Bremerton, Washington, the City of Salem, Oregon and Lane Transit in Eugene, Oregon.

PURPOSE AND FUNCTION OF TRANSMATCH 2.0
TransMatch 2.0 is a versatile software tool which can be used by public agencies, large employers, non-profit organizations and others to support regional trip reduction efforts. TransMatch 2.0 uses GIS technology to provide a visual ridematching tool which is flexible and user-friendly. In essence, TransMatch links a database of applicants with street file data to find potential ridesharing partners.

TransMatch facilitates ridesharing by matching potential carpool and vanpool partners together, as well as walking and bicycling buddies, from a single or multiple origins. Ridematching is performed using the flexibility of three methods:

The matches are based on the commuter's origin, destination, work schedule and preferences (e.g. drive/ride; smoking/no smoking, etc.). TransMatch generates a match list of potential names which are rank-ordered based on origin/destination, work/school schedule and applicant preferences. In addition, TransMatch allows matching to be internal or external exclusive, providing the flexibility of matching only with co-workers or specifically not with workers at identified employment sites. The ability to perform visual matching with the on-screen map allows geographic barriers such as mountains, large bodies of water, freeways and bridges to be identified. In addition, the operator can use their discretion to select and de-select matches for the applicant. Those features enhance the accuracy in matching potential ridesharing partners.

TransMatch simplifies administration for the agency or organization providing the ridematching services. An array of 29 commuter reports are generated including commuters by worksite, potential participants by origin/destination and TransMatch 2.0 system statistics. Users can design and save customized reports and letters to meet current and future needs. Database maintenance is streamlined with an internal tickler system and unique sensitivity to duplicate records. And, if the organization also provides a vanpool or HOV (high occupancy vehicle) program, TransMatch can track key information in a user-friendly database and generate an additional array of 28 HOV reports. A complete listing and description of the Commuter Reports and HOV Reports generated by TransMatch 2.0 is available in the appendix of this paper.

TransMatch ensures data security by limiting system access based on user status. Three user status options are available:

  1. SUPERGROUP has access to all screens and may add, change or delete any information. Only users in this group have access to the setup screens in TransMatch. The SUPERGROUP's SUPER user is the Administrator of TransMatch for the agency or organization.
  2. MAINGROUP has access to all screens, except the setup screens. Users in this group may add, change or delete any other information in the database.
  3. BACKUPGROUP has access to all screens, except the setup screens. View-only access is available to the maintenance screens. Users in this group may add, change or delete any other information in the database.

Designed for a PC environment, TransMatch 2.0 operates on a 486DX-66 (or better) in Windows 95 and can be linked to a network to allow multiple users. At least 16MB of RAM is needed, along with 20MB or more of virtual memory. Esri ArcView 2.1 is required, along with Wessex street data or an agency's own internal street data in an ArcInfo/ArcView compatible format.

CONCLUSION
The development and testing of TransMatch 2.0 has been completed. This software is effectively meeting the needs of the transit agencies, cities and counties which are using TransMatch to enhance regional mobility. Spokane County is an active user of TransMatch 2.0, with over 1,000 current applicants in the database. Primarily marketed to 96 worksites affected by the Commute Trip Reduction Law in Spokane County, TransMatch is used by employers as an internal and external ridematching tool which is provided at no cost. A complete set of collateral materials was developed to launch TransMatch 2.0 at Spokane-area worksites, including posters, flyers, a brochure with postage-paid TransMatch 2.0 ridematch application and letterhead for the match list letters.

Since its final completion after twelve months of development and testing, six organizations are using TransMatch 2.0 and several more are considering the acquisition of this innovative ridematching tool. The Complete TransMatch 2.0 Package includes the software on CD, a comprehensive User's Guide and limited TransMatch 2.0 promotional materials. Although an upgrade to TransMatch 3.0 is a possibility, there are currently no plans to undertake this project, as TransMatch 2.0 is performing well for the agencies which are facilitating multi-modal ridesharing and enhancing regional mobility with this flexible, user-friendly software program.

Acknowledgments:
Katy Taylor, Ross Kelley, Spokane County's Information Systems Department: Vickie Birkenthal, Tina Floberg, Cara Mohr, Richard Volz.

APPENDIX

TransMatch Report Descriptions

Commuter Reports
TM001 - Worksite Employee Participation- - Lists Commuter Names, Phones Numbers, Phone To Give Out and Contact Date. Selection for 1 or all Worksites, Report is Sorted By Worksite ID, then Commuter First Name. A page break occurs on each Worksite ID.

TM002 - Worksite Participation - Lists Worksite Mailing & site Addresses, and ETC Name & Phone. Selection for all, affected, or Non affected Worksites. Report is sorted by Affected/Non-affected, then by Worksite. A page break occurs on Affected/Non-affected. Total # of Worksites are given for affected and non-affected.

TM003- Commuter Interest - Lists Commuter Name, Worksite, Commuter Status and Commuter Phone numbers who have a status of "Prospect" or "Active-Open". Selection for Interest (Carpool, Vanpool, Bike Buddy, Walking Partner). Report is sorted by Worksite, then Commuter Last Name.

TM004- Commuter Participation - Lists Commuter Name, Worksite, and Commuter Phone Numbers who have a status of "Active-Open" or "Active-Closed". Selection for Participation (Carpool, Vanpool, Bike Buddy, Walking Partner). Report is sorted by Worksite, then Commuter Last Name.

TM005- Commuters With Special Needs - Lists Commuter Name, Mailing Address, Phone Number, and Worksite site Address, for commuters who have Special Needs Marked. Report is sorted by Worksite, then Commuter Last Name.

TM006- Commuters By Status - Lists Commuter Name, Worksite, Phone Numbers, Phone To Give Out and Contact Date. Selection For Commuter Status (Active-Open, Active-Closed, Inactive, Info Only, Prospect). Report is sorted by Worksite, then Commuter Last Name.

TM007- Employee Transportation Coordinators - Lists Worksite ETC Name, ETC Phone, and Worksite Name. Report is sorted by Worksite.

TM008- Information Requested - Lists Commuter Name, Mailing Address, (Phone Numbers are printed if they can be given out.), Requested Date, and Worksite Site Address. Selection for Available Information and a Requested Date greater than or equal to Start Date entered. Report is sorted by Worksite, then Commuter Last Name.

TM009- Group Members - Lists Commuter lDs, Commuter Name, Rider Type, Status that are in a Group. Group ID and Group Mgr. are also listed. Selection for 1 or all Groups. Report is sorted by Group ID, then by Rider Type, then by Commuter Last Name.

TM010- Commuters By Zip Code Destination - Lists Commuter Name, Mailing Address, Phone Numbers, Phone To Give Out, Status, Worksite Site Address. Selection For Worksite Zip Code, Report is Sorted by Worksite, then by Commuter Status, then Commuter Last Name.

TM011- Commuters By Zip Code Origin - Lists Commuter Name, Mailing Address, Phone Numbers, Phone To Give Out, Status, Worksite Site Address, Selection For Commuter Origin Zip Code (Origin Address is not shown on report). Report is Sorted by Worksite, then Commuter Status, then Commuter Last Name.

TM012 - Worksite Mailing Labels - Lists Worksite ETC Name, Worksite Name, Mailing Address. Labels are sorted by Worksite.

TM013 - Contact Follow-up List - Lists Commuter Name, Worksite, Phone #'s, Status and Contact Date that have a Contact Date greater than or equal to the Start date and less than or equal to the End date and are not in the "Info Only" status. Report is sorted by Worksite, then Last Name.

TM014 - Contact Follow-up Letter - Prints Letters for commuters with a Contact Date that is greater than or equal to the Start date and less than or equal to the End date and are not in the "Info Only" Status. Letters are sorted by Commuter Last Name.

You have a choice to automatically update the Commuter Letter History for Letter "MONTHLY", when these letters are created.

TM015 -Annual Follow-up Letter - Prints Letters for commuters that have a Contact Date Month that is equal to the Start Date Month and have a Contact Date Year Less than the Start Date Year. Letters are sorted by Commuter Last Name.

You have a choice to automatically update the Commuter Letter History for the Letter "ANNUAL', when these letters are created.

TM016 - Match Letter Follow-up - Lists Commuter Names, Phone #''s, Worksite, Contact Date, Letter Date that have a status of "Prospect" or "Active-Open". Selection for Match Letter with a Match Letter Sent Date that is greater than or equal to the Start Date and Less than or equal to the End date.

TM017 - Labels For Letter - List Commuter Name, Mailing Address. Selection For Letter and Start Date that equals Letter sent date. Labels are sorted by Last Name.

TM018 - Commuter Labels For Worksite - Lists Commuter Name, Mailing Address.

Selection for 1 or all Worksites. Labels are sorted by Commuter Last Name.

TM019- Commuters By Neighborhood - Lists Commuter Name, Phone Numbers, Phone To Give Out, Worksite, Status. Selection For I or All Neighborhoods. Sorted Neighborhood, then Commuter Last Name. Page Breaks on Neighborhood.

TM020 - Worksite Statistics - Lists by Commuter Status Counts for Preference and Active Vanpool, Carpool, Bike Buddy, Walking Partner, No Smoke. Also Count # of Commuter as a group and Rider Types. Counts Information Requested. Gives total commuters by Status. Selection for 1 or All Worksites. Sorted by Worksite ID. Page Break on Worksite ID.

TM021 TransMatch Statistics - Lists same as TM020 except it is for all Commuters in TransMatch. No Selection.

TM022 - Commute Without Origins - Lists Commuter ID, Commuter Name, Commuter Information Created By, Commuter Information Created On, for Commuters who do not have a Commuter Origin record created. Report is sorted by Created On Date in Descending Order.

TM023- Worksites Not Geocoded - Lists Worksite ID, Worksite, Site Address, Site Zip Code, for Worksites with a geocode status of N. Sorted by Worksite.

TM024- Frequently Used Addresses Not Geocoded Lists Description, Address, and Zip Code, for Frequently Used Addresses with a geocode status of N. Sorted by Description.

TM025 - Commuter Origins Not Geocoded - Lists Commuter ID, Origins Description, Origin Address, Origin Zip Code, for Commuter Origins with a geocode status of N. Sorted by Commuter ID.

TM026 - Labels For Commuter Interest - Lists Commuter Mailing Labels for Commuters with a status of "Prospect" or "Active-Open". Selection for Interest (Carpool, Vanpool, Bike Buddy, Walking Partner). Labels are sorted by Commuter Last Name.

TM027- Labels For Commuter Participation - Lists Commuter Mailing Labels for Commuters with a status of "Active-Closed" or "Active-Open". Selection for Participation (Carpool, Vanpool, Bike Buddy, Walking Partner). Labels are sorted by Commuter Last Name.

TM028- Commuter Labels For Status - Lists Commuter mailing Labels. Selection For Commuter Status. Labels are sorted by Commuter last Name.

TM029- Commuters Created By - Lists Commuter ID, Commuter Name, Status, and Created On Date. Selection For Created By and Created On Date is greater than or equal to Start Date. Sorted by Commuter ID.

Match letter 0 - Match Letter for Commuter with no matches, after Matching Process is done on the Commuter Origins screen. User will be asked if they want to print this letter when no matches are found. If Print Letter Button is Clicked on the Matched Prospect Screen and all Prospects are not Marked as Listed In Letter, Match Letter 0 will be printed.

Letter History for Match Letter 0 is automatically Updated when the letter is printed.

Match Letter 1 - Match Letter for Commuter with 1-4 Matches. If the Print Letter Button is Clicked on the Matched Prospects Screen and there are 1 to 4 Prospects Marked as List in Letter, Match Letter 1 will be printed. The Prospects will List Name, Phone Numbers that can be given out, Preferences (Carpool, Vanpool, Bike Buddy, Walking Partner) and their Rider Type Preference. Letter History for Match Letter 1 is automatically Updated when the letter is printed.

Match Letter 2 - Match Letter for Commuter with 5 or more Matches. If the Print Letter Button is Clicked on the Matched Prospects Screen and there are 5 or more Prospects Marked as List in Letter, Match Latter 2 will be printed. The Prospects will List Name, Phone Numbers that can be given out, Preferences (Carpool, Vanpool, Bike Buddy, Walking Partner) and their Rider Type Preference.

Letter History for Match Letter 2 is automatically Updated when the letter is printed.

HOV Reports

TMHI1 - HOV Incident - Lists the current Incident on the HOV Incidents screen. This is printed by Clicking the Print button on the HOV Incidents screen.

TMHM1 - HOV Monthly Activity - List the current Monthly Activity on the HOV Monthly Activity screen. This is printed by Clicking the Print button on the HOV Monthly Activity screen.

H0V01 - HOV Inventory - Lists HOV#, Group ID, Contact, Group Mgr. 's Name, Mailing address, Phone #'s, HOV Origin, Destinations, Default RT Miles, VIN, License, Year Make, Group Count, and Capacity. This Report is Sorted by HOV #,

H0V02 - HOV By Status - Lists Status and Status Description, HOV #, Group Mgr. Name, Group Mgr. Phone Numbers, Origin, Destination, Default Fare, Shift. The Report is sorted by Status, then by Origin.

H0V03 - HOV Labels - Labels for HOV Group Managers, lists Name, Mailing Address. Labels are sorted by Group Manager Last Name. Selection for I or all HOVs.

H0V04-HOV Commuters - Lists HOV#, Group ID, Status, HOV Type, HOV Type Description, Contact, Commuter ID, Commuter Name, Commuter Phone #''s, Worksite ID, Employer Name. Report is sorted by HOV #, Commuter Last Name. Capacity Count and Commuter Count is given for each HOV and Report Total. Total HOV Count is also given.

H0V05 - HOV Commuters By Worksite - Lists Worksite ID, Worksite, HOV #, Commuter ID, Commuter Name, Commuter Phone #'s' if they can be given out. Selection for 1 or all Worksites. Report is sorted by Worksite, HOV#, then Commuter Last Name. Page Break occurs on Worksite.

H0V06 - HOVs With Available Seats - Lists HOV Type, HOV Type Description, Shift, HOV #, Group ID, Capacity, Commuter Count, Origin, Destination, Group Mgr. Name, Contact, Group Mgr. Phone Numbers for HOVs that have a Capacity greater than their Commuter Count. Report is sorted by HOV Type, then by HOV #.

H0V07 - HOVs For Contact - Lists HOV#, HOV Type, Status, Group ID, Contact, Group Mgr. Name, Group Mgr. Phone #''s, Selection for 1 or all Contacts. Report is sorted By Contact, then by HOV #. Page Break occurs on Contact.

H0V08- Defensive Driving Renewals - Lists HOV#, Driver Commuter ID, Driver Commuter Name, Driver Worksite, Driver Renewal Date. Sorted by Renewal Date.

H0V09- Defensive Driving Renewal Letter - Letter RENEWAL for HOV Drivers. Selection Mo/Yr equal to Renewal Date Month and Year. Letters are sorted by Commuter Name.

Letter History for letter RENEWAL is automatically updated when letters are created. If user requests Update.

H0V10 - HOVs with Waiting Lists - Lists HOV #, HOV Type, HOV Type Description, Status, Contact, Shift, Group Mgr. Name, Group Mgr. Phone Numbers, Wait List Commuter Name, Request Date, Worksite ID, Employer Name, Commuter Phone #''s. Report is Sorted By HOV #, then by Request Date.

H0V11 - HOVs Monthly Costs - Lists HOV #, Mgr. Name, RT Miles, Trip Days, # of Pass., Van Cost Per Mile, Van Cost, Seat Cost, # of Pass. (Next Month), Monthly Fare, Seat Cost(Next Month), Subsidy, Pass. Cost(Next Month). If Monthly Record exists for HOV. Selection Mo/Yr of Monthly Activity. Report is Sorted By HOV #. Report Total of Cost is also given.

H0VI2 - HOV Fuel Usage - Lists HOV#, Mo/Yr, Mgr. Name, RT Miles, Fuel Used, Fuel Cost, Trip Days, Miles Per Gallon If Monthly Record exists for HOV and Fuel Used is greater than 0. Selection Mo/Yr of Monthly Activity. Report is sorted by HOV#. Report Totals of Fuel Usage is also given.

H0V13 - Unresolved Incidents - Lists Reported To, Mgr. Name, Mgr. Phone Numbers Date Reported, HOV #, Contact, Incident #, Description, Action Required, Results if Date Resolved is Blank. Report is sorted By Reported To, then by Date Reported.

HOV14 - Resolved Incidents - Lists Reported To, Date Resolved, Date Reported, HOV# Contact, Mgr. Name, Mgr. Phone #'s, Incident #, Description, Action Required, Results If Date Resolved is not Blank. Report is sorted By Reported To, Date Resolved.

HOVI5 - HOVs For Incident Type - List HOV #, HOV Type, HOV Type Description, Group ID, Contact, Group Mgr. Name, Group Mgr. Phone #'s, Reported To, Date Reported, Date Resolved, Incident #, Description, Action Required, Results. Selection for Incident Type. Report is Sorted by HOV#.

H0V16 - HOVs Service Information for Contact - Lists Contact, HOV #, Mgr. Name, Capacity, Default RT Miles, Last Service Date, Last Service Miles, Next Service Date, Next Service Miles, Service Comments, Selection Contact for I or All Contacts. Report is Sorted By Contact, then by HOV #

H0VI7 - HOVs Service Information By Next Service Miles - Lists Contact, HOV #, Mgr. Name, Capacity, Default RT Miles, Last Service Date, Last Service Miles, Next Service Date, Next Service Miles, Service Comments. Report Is Sorted By Contact, then by Next Service Miles (descending)

H0V18 - HOVs Service Information By Next Service Date - Lists Contact, HOV #, Mgr. Name, Capacity, Default RT Miles, Last Service Date, Last Service Miles, Next Service Date, Next Service Miles, Service Comments. Report is Sorted By Contact, then by Next 5ervice Date.

H0V19 - Potential Carpool Commuters By Origin - List Origin, Destination, Commuter ID, Commuter Name, Commuter Phone #''s,. Inquiry Date, Rider Type Pref., Employer Name For Commuters with an Origin that matches a Potential Carpool Origin. Carpool Preference is marked and in a status of "Prospect" or "Active-Open". Report is sorted by Origin, then by Destination. Page Break occurs on Origin.

H0V20 - Potential Vanpool Commuters By Origin - Lists Origin, Destination, Commuter ID, Commuter Name, Commuter Phone #'s Inquiry Date, Rider Type Pref., Employer Name For Commuters with an Origin that matches a Potential Vanpool Origin and Vanpool Preference is marked and in a status of "Prospect" or "Active-Open". Report is sorted by Origin, then by Destination. Page Break occurs on Origin.

H0V21- Potential Carpool Commuter By Destination - Lists Destination, Origin, Commuter ID, Commuter Name, Commuter Phone #''s, Inquiry Date, Rider Type Employer Name For Commuters with an Origin that matches a Potential Carpool and Carpool Preference is marked and in a status of "Prospect" or "Active-Open". Report is sorted by Destination, then by Origin. Page Break occurs on Destination. Pref., Origin

H0V22- Potential Vanpool Commuter By Destination - Lists Destination, Origin, Commuter ID, Commuter Name, Commuter Phone #'s, Inquiry Date, Rider Type Pref., Employer Name For Commuters with an Origin that matches a Potential Vanpool Origin and Vanpool Preference is marked and in a status of "Prospect" or "Active-Open". Report is sorted by Destination, then by Origin. Page Break occurs on Destination.

H0V23 - Prospects Not In A Potential Carpool - Lists Commuter Origin, Commuter ID, Commuter Name, Rider Type, and Destination For Commuters with a Status of Prospect, Carpool Pref. is Marked, an Origin that is not Blank and doesn't match a Potential Carpool Origin. Report is sorted by Origin, then by Destination.

H0V24 - Prospects Not In A Potential Vanpool - Lists Commuter Origin, Commuter ID, Commuter Name, Rider Type, and Destination For Commuters with a Status of Prospect, Vanpool Pref. is Marked, an Origin that is not Blank and doesn't match a Potential Vanpool Origin. Report is sorted by Origin, then by Destination.

H0V25 - MVET Local Renewal Tickler - Lists HOV#, MVET Status, Initial Application Date, State Renewal Date, Local Renewal Date, Confirmation Sent Date, Commuter ID, Name, Commuter Phone #''s For MVET Records with a Status of Not Inactive and Local Renewal Date is less or equal to the current date plus # of Months. Selection # of Months (add to Current Date). Report is Sorted By Local Renewal Date.

H0V26 - MVET State Renewal Tickler - Lists HOV#, MVET Status, Initial Application Date, State Renewal Date, Local Renewal Date, Confirmation Sent Date, Commuter ID, Name, Commuter Phone #'s For MVET Records with a Status of Not Inactive and Local Renewal Date is less or equal to the current date plus # of Months. Selection # of Months (add to Current Date). Report Is Sorted By State Renewal Date.

H0V27 - MVET Exemptions - Lists MVET Commuter ID, Commuter Name, Commuter Phone #'s, HOV #, HOV Type, Group ID, MVET Status, Signatures1 Initial Application, Confirmation Sent, Local Renewal, State Renewal, Vehicle Owner, VIN, Plate, Year, Make. Group Member Commuter ID, Name, Rider Type, Phone #'s. Sorted By MVET Key (HOV #, Commuter ID, Status), then by HOV Type. Page Break occurs for each MVET record.

H0V28 - MVET Letter - Letter MVET for MVIET Commuter that has a MVET Status of Not Inactive and Initial Application Month and Year Plus # of Month Selection that equals the Current Date, Second Page list all Group Member Names and Phone #'s that can be given out Selection # of Months. Letters are sorted by MVET Commuter ID.

Letter History for letter MVET is automatically updated when letters are created if user requests.

Author Information:
Melanie Rose, Transportation Demand Management Manager, Spokane County
1026 W. Broadway, Spokane, WA 99260
Phone: (509) 324-3169
Fax: (509) 324-3478,

Ian Von Essen, GIS Manager, Spokane County
1026 W. Broadway, Spokane, WA 99260
Phone: (509) 459-6344
Fax: (509) 324-3494