Motor Vehicle Emission Simulator (MOVES): User Guide for MOVES2010a


            Motor Vehicle Emission Simulator
            (MOVES)
            User Guide for MOVESZOlOa
&EPA
United States
Environmental Protection
Agency

-------
       Motor Vehicle Emission Simulator
                       (MOVES)
           User Guide for MOVESZOlOa
                   Assessment and Standards Division
                  Office of Transportation and Air Quality
                  U.S. Environmental Protection Agency
 ** rnA
^J*5^^™f^fcA Environmental Protection
                                              EPA-420-B-10-036
Agency                                          August 2010

-------
August 2010                                                                     MOVES User Guide

-------
MOVES User Guide                                                                       August 2010

                                        Table of Contents
                                                                                            Page
  Preface	iii
  1.0. Getting Started with MOVES	1
     1.1 About MOVES	1
     1.2 MOVES Documentation	2
       1.2.1 About this Manual	2
       1.2.2 Other Documentation and Online Help	2
       1.2.3 What's Next? Working with MOVES	3
     1.3 Installation	4
       1.3.1 System Requirements	4
       1.3.2 Starting and Testing Your Installation	5
     1.4 Executing Example Run Specification	5
       1.4.1 Step-by-step Example Run	6
       1.4.2 MOVESExecution Database	6
       1.4.3 MOVES Output Structure	7
  2.0 Using MOVES	9
    2.1 Overview of MOVES User Interface	10
    2.2 Navigation Panel	12
       2.2.1 Description	13
       2.2.2 Scale	14
         2.2.2.1 Domain/Scale	14
         2.2.2.2 Calculation Type	16
       2.2.3 Time Spans	17
         2.2.3.1 Time Aggregation Level	18
         2.2.3.2 Years	18
         2.2.3.3 Months	19
         2.2.3.4 Days	19
         2.2.3.5 Hours	19
       2.2.4 Geographic Bounds	19
       2.2.5 Vehicles/Equipment	26
       2.2.6 Road Type	27
       2.2.7 Pollutants and Processes	28
         2.2.7.1 Processes	30
         2.2.7.2 Pollutants	30
       2.2.8 Manage Input Data Sets	31
       2.2.9 Creating and Using Internal Control Strategies	33
         2.2.9.1 Adding Strategy Files	34
         2.2.9.2 Deleting Strategy Files	35
         2.2.9.3 Exporting Strategy Files	35
         2.2.9.4 Naming Strategy Files	36
         2.2.9.5 Saving and Transferring Strategy Files	36
         2.2.9.6 Creating AVFT files outside of MOVES	36
         2.2.9.7 Managing On-Road Vehicle Retrofit Data	37
         2.2.9.8 Importing Retrofit Data	38
         2.2.9.9 Rate of Progress Calculation	39
       2.2.10 Output	39
         2.2.10.1 Specifying  Database, Time Period, and Units in Output	40
            2.2.10.1.1 Output Database	40
            2.2.10.1.2 Units	41
            2.2.10.1.3 Activity	41
         2.2.10.2 Specifying  Emission Distinctions in Output	42
United States Environmental Protection Agency                                                      Page i

-------
August 2010	MOVES User Guide

           2.2.10.2.1  Always	43
           2.2.10.2.2  For All Vehicle/Equipment Categories	44
           2.2.10.2.3  On Road/Off Road	44
           2.2.10.2.4  Estimate Uncertainty	45
      2.2.11  Advanced Performance Features	45
    2.3 Main Menu Bar	47
      2.3.1 File	47
      2.3.2 Edit	47
      2.3.3 Preprocessing	48
        2.3.3.1 Database	50
        2.3.3.2 RunSpec Summary	51
        2.3.3.3  Tools	52
           2.3.3.4 Data Managers (Importers)	53
             2.3.3.4.1 Meteorology Data Importer	59
             2.3.3.4.2 Source Type Population Importer	59
             2.3.3.4.3 Age Distribution Importer	59
             2.3.3.4.4 Vehicle Type VMT and VMT Fractions	59
             2.3.3.4.5 Average Speed Distribution Importer	61
             2.3.3.4.6 Road Type Distribution Importer	61
             2.3.3.4.7 Ramp Fraction Importer	62
             2.3.3.4.8 Fuel Formulation Importer	62
             2.3.3.4.9 Fuel Supply Importer	63
             2.3.3.4.10 I/M Importer	64
             2.3.3.4.11 Zone Road Activity Importer	65
             2.3.3.4.12 Links Importer	65
             2.3.3.4.13 Link Source Types Importer	66
             2.3.3.4.14 Operating Mode Distribution Importer	67
             2.3.3.4.15 Link Drive Schedules Importer	67
             2.3.3.4.16 Off Network Importer	67
      2.3.4 Action	68
      2.3.5 Postprocessing	69
        2.3.5.1  Run MySQL Script on Output Database	69
        2.3.5.2  Produce Summary Report	70
        2.3.5.3  Produce State/County Map	74
      2.3.6 Tools	76
      2.3.7 Settings	80
        2.3.7.1 Configure MOVES	80
      2.3.8 Help	81
 Appendix A - Using MOVES to Generate Lookup Tables	
 Appendix B  - Linking MySQL Tables from MS ACCESS or MS Excel (includes ODBC usage)	
 Appendix C  - Using the Batch Command Line Interface	
 Appendix D - Creating an On-Road Retrofit Input File	
 Appendix E  - Best Practices	
 Appendix F  - Stage II Refueling Control Programs	
 Appendix G - MOVES Project Level Example	
 Appendix H - County Data Manager Example and Basic MySQL Queries for Analyzing Output	
 Appendix I - MOVES DECODER	
Page ii                                                     United States Environmental Protection Agency

-------
MOVES User Guide August 2010
Preface

MOVES2010a, released in August 2010, is a minor update to MOVES2010, EPA's state-
of-the-art tool for estimating emissions from highway vehicles.. EPA has released MOVES2010a
to allow MOVES users to easily account for emissions under new car and light truck energy and
greenhouse gas standards and to benefit from several improvements to MOVES general
performance.

MOVES2010a incorporates new car and light truck greenhouse gas emissions standards
affecting model years 2012-and-later (published May 7, 20101) and updates effects of corporate
average fuel economy standards affecting model years 2008-2011.2 MOVES2010a includes
reductions in greenhouse gases associated with those standards in future calendar years, and
small reductions in refueling and sulfur-related emissions associated with the reductions in
vehicle fuel consumption.

MOVES2010a also includes a number of other improvements. Major changes are listed
in the table below. The net impact of these changes on criteria pollutant emissions is small.
Compared to MOVES2010 (released in December 2009), most regional inventory runs should
see an increase in methane emissions and a small decrease in the associated Volatile Organic
Compound (VOC) and air toxics emissions. However, comparisons for runs that focus on a
particular project or sourcetype may vary.

Instructions for downloading and installing MOVES2010a are available on the MOVES
web page http://www.epa.gov/otaq/models/moves/. Users will find that runspecs and input
databases developed with MOVES2010 may need modification to be able to run with
MOVES2010a. Users should regenerate fuelFormulation input files and Alternate Vehicle
Fuels & Technologies (AVFT) strategy files. Output databases will need to be recreated with a
new name since several new tables have been added. Users should always specify what version
of MOVES was used to create emissions results.
1http://www.regularions.gov/search/Regs/home.html#documentDetail?R=OQOOOo648oae8a.^8
2http://www.regularions.gov/search/Regs/home.html#documentDetail?R=OQOOOo648o2cefcdand
http://www.regulations.gov/search/Regs/home.html#documentDetail?R=OQOOOo648oQ.^7.ciea
United States Environmental Protection Agency Page iii

-------
August 2010
                    MOVES User Guide
                       Changes from MOVES2010 to MOVES2010a
Change from MOVES2010 to MOVES2010a
1) Updated light duty energy and carbon
dioxide rates and algorithm to account for new
fuel economy/CO2 regulations.
2) Incorporated all data corrections distributed
in May 15, 2010 version of the MOVES
database (i.e. data in MOVESDB20100515).
See MOVES2010 Errata/Information Sheet
(May 15, 2010) for additional information.
3) Improved algorithm for brakewear and
tirewear so emissions are always zero at idle.
4) Improved MOVES algorithm for calculating
emissions on ramps.
5) Improved methane algorithm and updated
methane rates. Better accounts for methane
variation with temperature, driving activity,
etc. Adds methane emissions for some
processes where it was not calculated.
6) Fixed error that reduced temperature
correction for temperatures greater than 100F.
7) Fixed error in pre-aggregation by month that
occurred in some HD runs.
8) Repaired an error in the ammonia emissions
calculations.
9) Improved calculation of air toxics emissions,
Implication
Reduced energy consumption and carbon dioxide
emissions for light duty gasoline vehicles; reduced
hydrocarbon emissions from refueling and sulfate
emissions from fuel consumption.
For users who have switched to the May 15, 2010
database, these changes will have no impact.
Compared to MOVES2010 as released in December
2009, MOVES2010a will change NO and NO2
emissions (no change in NOx), decrease hydrocarbon
evaporative emissions slightly, change diesel vehicle
volatile organic compound (VOC) and air toxics
emissions for calendar years 1999-2006, change
hydrocarbon emissions for vehicles running on gasoline
containing ethanol in calendar years 1999-2004, and
reduce particulate matter emissions for 2021-and-later
light-duty diesel emissions.
Reduced brakewear and tirewear emissions. Change is
very small for regional inventories, but larger for
projects with substantial idling on steep grades.
Negligible changes for regional emissions calculated
using Inventory mode (emissions inventory output).
Increase in emissions on highways (restricted access
roadtypes) for those using Emission Rate mode (rate-
per-distance emissions).
Methane emissions increased substantially. VOC and
other non-methane hydrocarbons are reduced by a
small amount. "Carbon Dioxide Equivalent"
emissions are increased less than 1 percent by this
change and when combined with the impact of the new
regulations (see above), total greenhouse gas emissions
decline.
When methane output is desired, users now must
calculate total hydrocarbons also.
Increases hydrocarbon, CO, and NOx emissions for
temperatures greater than 100F. Users who have
modeled days with temperatures over 100F should
evaluate emission changes that result from this
revision.
Some runs will see an increase in emissions for
medium and heavy duty trucks and buses for VOC and
other hydrocarbons.
Increases ammonia emissions for passenger and light
commercial trucks.
Increases air toxic emissions from diesel vehicles.
Page iv
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
Change from MOVES2010 to MOVES2010a
particularly for diesel vehicles.
10) Updated default national heavy truck and
bus sales-growth and VMT-growth factors to
account for more recent data and updated
projections.
11) Fixed errors in motorcycle scrappage,
migration and sales growth defaults.
12) Fixed error that increased emissions when
users selected "placeholder" fuel.
13) Added a new output option ~ emission
rates by SCC.
14) Changed units for project-level start &
extended idle rates (see Users Guide).
15) Improved MOVES user interface,
including run spec editor, importers, summary
reporter and "Multiple Run Spec Creator."
16) Improved error checking in MOVES
importers.
17) Allow the batch creation of import
databases.
1 8) Allow user to add new fuel formulations
rather than just editing existing formulations.
19) Made MOVES more compatible with
UNIX/Linux.
20) Updated the "Example" files distributed
with MOVES.
21) Improved MOVES run time and added
tools to better monitor MOVES performance.
22) Improved MOVES robustness by adding
additional error checking.
23) Improved Custom Domain functioning.
24) Corrected a problem in which evaporative
permeation emissions were not always
aggregated correctly. Previous output
Implication

Increased default population, sales and emissions for
buses and heavy trucks. This does not affect emissions
in runs using local inputs for bus and truck populations.
Increases default population of motorcycles. This does
not affect emissions in runs using local inputs for
motorcycle populations.
Reduces emissions, sometimes substantially, in runs
where "Placeholder fuel" was selected. Even with
MOVES2010a, use of "Placeholder" fuel is not
recommended.
Eliminates some users' need to calculate SCC rates in
post-processing. Adds an additional column to
emission rate output tables.
Users may need to modify post-processing to apply
rates properly.
Many small changes that should make MOVES easier
to use.
A number of changes that should make MOVES easier
to use.
Makes it easier for users to create a group of similar
import databases.
Provide more flexibility for users changing default fuel
characteristics.
Makes it easier to adapt MOVES to run with
UNIX/Linux systems. While EPA does not have the
resources to provide or fully support such adaptations,
we encourage Linux/UNIX users to contact us to share
information.
Example file runs correctly with MOVES2010a.
MOVES runs slightly faster and users can better
diagnose performance problems.
Improved code that sometimes led to MOVES crashes.
Allow users to calculate Custom Domain emissions for
"off-network" roadtype without requesting output for
other roadtypes.
More accurate post-processing.
United States Environmental Protection Agency
     Page v

-------
August 2010
                       MOVES User Guide
Change from MOVES2010 to MOVES2010a
sometimes had rows with duplicate key fields.
Depending on the post-processing method
used, totals could have been miscalculated.
25) Made the "DecodeMOVESOutput" script
compatible with new version of MOVES.
26) Corrected several other minor errors in the
MOVES program.
Implication

Decode script should run without error.
Negligible impact on emissions.
Page vi
United States Environmental Protection Agency

-------
MOVES User Guide August 2010

1.0. Getting Started with MOVES

MOVES is the U.S. Environmental Protection Agency's (EPA) Motor Vehicle Emission
Simulator. It helps the user to answer "what if questions, such as "How would paniculate
matter emissions decrease in my state on a typical weekday if truck travel was reduced during
rush hour?" or "How does the total hydrocarbon emission rate change if my fleet switches to
gasoline from diesel fuel?" The purpose of the tool is to provide an accurate estimate of
emissions from mobile sources under a wide range of user-defined conditions.

In the modeling process, the user specifies vehicle types, time periods, geographical
areas, pollutants, vehicle operating characteristics, and road types to be modeled. The model
then performs a series of calculations, which have been carefully developed to accurately reflect
vehicle operating processes, such as cold start or extended idle, and provide estimates of bulk
emissions or emission rates. Specifying the characteristics of the particular scenario to be
modeled is done by creating a Run Specification, or RunSpec.

The MOVES model is different from previous EPA mobile source emissions models in
that it was deliberately designed to work with databases. With this design, new data that may
become available can be more easily incorporated into the model. In addition, MOVES allows
and facilitates the import of data specific to a user's unique needs.

The MOVES model includes a "default" database that summarizes emission relevant
information for the entire United States. The data for this database comes from many sources
including EPA research studies, Census Bureau vehicle surveys, Federal Highway
Administration travel data, and other federal, state, local, industry and academic sources. The
MOVES team continually works to improve this database, but, for many uses, up-to-date local
inputs will be more appropriate, especially for analyses supporting State Implementation Plans
(SIPs) and conformity determinations.

1.1 About MOVES

MOVES2010a is the latest version of the MOVES emissions modeling tool.
MOVES2010a builds on the functionality of previous MOVES versions: MOVES2004,
MOVESDemo, DraftMOVES2009, and MOVES2010. MOVES can be used to estimate
national, state, and county level inventories of criteria air pollutants, greenhouse gas emissions,
and some mobile source air toxics from highway vehicles. Additionally, MOVES can make
projections for energy consumption (total, petroleum-based, and fossil-based).

MOVES2010a is intended for official use. Please see the MOVES2010a policy
statement available on the EPA's MOVES web site
http://www.epa.gov/otaq/models/moves/index.htm for EPA's policy on selecting appropriate
models for official mobile source emission estimates.

Future versions of MOVES will be able to estimate pollutants from other mobile sources
such as aircraft, locomotives, and commercial marine vessels. In addition, the capability to
estimate non-highway mobile source emissions is planned.
United States Environmental Protection Agency Page 1

-------
August 2010 MOVES User Guide

MOVES is distributed free of charge by EPA pursuant to the GNU General Public
License (GPL). It is written in Java and uses the MySQL relational database management
system. Oracle Corporation owns, operates, and supports MySQL, and allows distribution of the
database system pursuant to the GNU GPL. The principal user inputs and outputs, and the
internal working storage locations for MOVES are MySQL databases. The MOVES model
includes a "default" input database, which uses national data and allocation factors to
approximate results for the 3,222 counties in the United States, District of Columbia, Puerto
Rico, and the U.S. Virgin Islands. MOVES is capable of modeling emissions for the calendar
years 1990 and 1999-2050.

MOVES is set up to run both a "Master" and one or more "Worker" sub-programs. This
allows users to operate MOVES on a single computer system or on a network of computers. See
the MOVES2010a Installation Guide and/or the Software Design Reference Manual for more
information about specific requirements and computer configurations.

1.2 MOVES Documentation

The following discussion highlights the contents of this manual, how best to use the
manual, and where additional information may be found.

1.2.1 About this Manual

The MOVES User Guide focuses on operating MOVES software to create and execute
Run Specifications (RunSpecs).

Throughout this document, information may be highlighted to make it easier to find
solutions to problems or to avoid errors using the following prompts:

XCAUTION! Cautions must be observed to avoid errors in execution or to ensure the
intended execution will occur.

? NOTE Notes contain important information about the panel being described.

Tips contain hints for input or better operation of the run.

The MOVES2010 User Guide is accessible as a .pdf file under the Help menu in the
MOVES interface.

1.2.2 Other Documentation and Online Help

Additional documentation covering the following topics is available for MOVES2010.

Installation: A README text file is included on the MOVES Installation CD.
It guides the user through the MOVES system requirements and the process for installing
the MOVES program and associated software.
Page 2 United States Environmental Protection Agency

-------
MOVES User Guide August 2010

Software Design: The MOVES Software Design and Reference Manual
(SDRM) will be available on the MOVES website. The SDRM covers the basic concepts
and functional design of the software and the underlying MySQL database, including
technical specifications for all calculations performed in the model. It is intended to
answer more detailed and substantive questions about the MOVES software than those
addressed in this guide.

MOVES Database Documentation: More detailed documentation of the
MOVES database can be found within the README folder of the database itself. For
example, C :\MySQL\data\movesdbyyyymmdd\readme

1.2.3 What's Next? Working with MOVES

Depending on the status of your installation and how familiar you are with MOVES, you
have several options for next steps to get up and running with MOVES.

If you have just installed MOVES or are uncertain about your installation,
follow instructions in "Testing Your Installation," provided in Section 1.3.2 of
this guide.

If MOVES is installed and operational on your computer, you should run the
example to become more familiar with the tool before moving on. See
"Executing Example MOVES2010 Run Specification" included in Section
1.4.

If you would like to become more familiar with MOVES terminology and
design, see the "MOVES Software Design and Reference Manual," available
in .pdf format on the MOVES website.

If you have questions about the MOVES Graphical User Interface (GUI) or
executing a run, see "Overview of MOVES RunSpec User Interface" in
Section 2 of this guide.

If you are ready to begin using MOVES, see "Starting MOVES," also in
Section 2 of this guide.

If you would like to work through an example, a set of sample scenarios is
included in the Appendices.

If you would like to get started using MOVES for regular work, advice and
guidance on using MOVES is available on the MOVES website.

The rest of this guide provides information on using the MOVES2010 model.
United States Environmental Protection Agency Page

-------
August 2010
                     MOVES User Guide
     1.3 Installation

        Step-by-step instructions on installation are supplied by EPA in the MOVES2010a
 Installation Suite.  The MOVES2010a Software Installation Suite consists of the required
 installation programs (MySQL 5.1.32, Java 1.6.0_12, and MOVES2010, MySQL Query
 Browser, and MySQL ODBC).
    MOVES2010 Installation Suite
                          ,- Unix
                           MOVES2010a Installation Suite
      To install MOVES, review the System Information (the left-most tab), then work through the tabs in order from left to right.
System Install Java
Information 1 .6 0_1 2




Windows System Inf
Windows version:
Windows directory:
System directory:
CPU:
Remove
Existing
MySQL 5.0

Setup MySQL
5.1.32
Install MOVES Install Query Install MySQL Help /Contact
Application Browser ODBC 3.51 Info

Windows XP 32 Bit version
5.1.2
C:\WINDOWS
C:\WINDOWS\system32
Type: 586
Number of processor(s): 8
Physical Memory (MB): Total: 3326 Available: 2218

MOVES System Info
Component Ve

rsion
MOVES Application: MOVES201 00826
MOVES Database: Unknown
Java1.6.0_12: 1.6.0J2
MySQL 5.1 .32: 5.1.32
MySQL data: 5.1.32

Query Browser: 5.0.16

Status Insl

Refresh
tall Location

Unknown Unknown
Unknown Unknown
Installed C:\Program Files\Java\idk1 .6.0_1 2
Installed C:\Program Files\MySQL\MySQL Server 5.1
Installed C:\MySQL
Installed C:\Program Files\MySQL\MySQL Tools for 5.0
     This Suite invokes DOS screens to perform necessary tasks during installation; please disregard all popup DOS screens.
                                                                                Exit Suite
        1.3.1  System Requirements

        MOVES is a 32-bit application and has been developed to work with Microsoft Windows
 XP, VISTA, and Windows 7 environments. Note that installing MOVES with Microsoft Vista
 or Windows? may require changes to the User Access Control (UAC) security settings
 Computer(s) used to run either of the MOVES application programs must have at least 512 MB
 of RAM, although it is recommended that additional memory be available to improve execution
 times. Because execution run time performance is a constraint with MOVES, high speed
 processor(s) are highly recommended.

        The MOVES program is open source and is written in JAVA and MySQL.
Page 4
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
The MOVES Default database distributed with MOVES2010 requires approximately 1.0
GB of disk storage. MOVES Worker and Output databases are often large, so several additional
gigabytes of disk space should be available on all machines used to run either the MOVES
Master and/or the MOVES Worker program. Users who conduct many MOVES runs will want
to use late-model, high-performance microcomputer systems.

1.3.2 Starting and Testing Your Installation

After all necessary components of the MOVES2010a Installation Suite have been
executed, test the installation with the following steps.

1. Double-click the MOVES Master program icon.

2. When starting the MOVES Master program, the About MOVES panel will
appear in the center of the GUI screen. Click the "OK" button to continue.
About MOVES
MOVES
This version: 2010/08/26
Computer ID: DC275GE
Copyright U.S. Environmental Protection Agency
Licensed for use pursuant to the GNU General Public License (GPL)
For information about the GPL see http://Vvww.gnu.org/1icenses/
^ NOTE This panel identifies the version of MOVES that is in use and includes the version date,
the EPA copyright, and a link for the GNU General Public License (GPL) website.
Also included is the Computer ID or name. This panel will appear only at start-up.

3. Execute the Example Run Specification (MOVES2010aExample.mrs) as
described in the following section.

1.4 Executing Example Run Specification

The MOVES2010a Example Run Specification (MOVES2010aExample.mrs) models
the entire U.S. for one year (1999) at the most aggregate level. It estimates total energy
consumption and emissions of methane and nitrous oxide for the running, start, and extended idle
processes for all vehicle (use) types (gasoline, diesel, and CNG transit buses) and roadway types.
Vehicle Miles Traveled (VMT) is also estimated.
United States Environmental Protection Agency
Page 5

-------
August 2010 MOVES User Guide

1.4.1 Step-by-step Example Run

If MySQL and MOVES2010 have been installed, the MySQL server and the MOVES
Master program have been started, and the MOVES Worker program(s) are operational, the
example RunSpec can be executed as follows:

1. Select File, Open on the Main Menu Bar.

2. Navigate, if necessary, to the top level of the MOVES directory.

3 Select the MOVES2010aExample.mrs file

4. Select Output, then General Output on the Navigation Panel, which is the left-side
panel. Select or click on Create Database to establish a database into which results
should be placed. Select or enter a database name.

? NOTE Many MOVES features request that the user create input or output databases. These
database names must be consistent with MYSQL naming conventions. In general, this
means they may contain letters, numbers, "_"(underscore) and "$". They may not
contain spaces, special characters, or be "reserved words" (SQL words such as "select",
"where", "delete", etc.). See Appendix E, "Best Practices" for additional advice on
naming MOVES databases.

5. Select Action, Execute on the Main Menu Bar to start the RunSpec. The GUI will
ask you if you want to save the RunSpec before executing. You may choose Yes, No or
Cancel. The RunSpec will execute if either Yes or No are chosen, but selecting Cancel
will not execute and will allow users to make changes to the RunSpec. This RunSpec
may take up to 15 minutes to process.

6. The output will be saved in the MySQL relational database named in Step 4. The
output can be reviewed using the Post-Processing menu options described in Section
2.3.5, below, or by viewing the database directly using MYSQL commands, either
through the command prompt window or through MySQL Query Browser.

1.4.2 MOVESExecution Database

After Execute has been selected, MOVES begins to compile and populate all the
necessary tables in the MOVESExecution database. This database is in many respects similar
to the default database, but there are several key differences.

The MOVESExecution database is the location where conflicts are resolved
between the default database and user input databases. First, information is pulled from the
Domain Input Database on the Geographic Bounds panel (see Section 2.2.4) MOVES takes
note of the tables and key fields within the tables that are imported and uses that to limit what is
imported from database tables that are lower in the hierarchy. Next to be added to the
MOVESExecution database are user input databases listed on the Manage Input Data Sets
panel (see Section 2.2.8), with the last database listed taking priority over those listed above it.
Page 6 United States Environmental Protection Agency

-------
MOVES User Guide August 2010

Finally, MOVES uses the default database to populate the remaining tables not provided by the
user.

Also, the MOVESExecution database contains data in tables that are empty in the
default database and additional tables that are not present in the default database. These tables
are often not complete: to save memory, much of these additional data are cleared after they are
used in calculations. Users can save more of this data by checking one or more Save Data boxes
on the Advanced Performance Features panel (see Section 2.2.11) Note that the Save Data
process lengthens run time and the tables it produces are often difficult to interpret correctly.

1.4.3 MOVES Output Structure

The output database will typically contain eleven tables. The tables are:

1. movesoutput: This table contains the inventory emission results (emissionQuant) of
the run disaggregated by parameters such as Year, Month, Day, Source Type, County,
Fuel, Model-Year, Road-type, SCC, and Emission Process.

XCaution! If the Emission Rates calculation type is selected on the Scale panel, the
emissionQuant values will represent an intermediate step in the rates
calculations rather than the real emissions for that time and place. To reduce
the size of the MovesOutput table, use the Aggregation and Data
Handling panel on the Advanced Peformance Features screen to select
"Clear MOVESOutput after rate calculations."

2. movesactivityoutput: This table provides information on the vehicle activity
generated and used in the run. It is disaggregated by parameters such as Year, Month,
Day, County, Fuel, Model-Year, Road-type, and SCC. Activity is not distinguished by
pollutant and process. If a certain activity type (see also Section 2.2.10.1.3) is not
needed for the emission processes in a run, it is not generated.

7 NOTE In the MOVESActivityOutput table, population always has month, day & hour
keys of zero (i.e. "doesn't matter") because population is assumed constant in
time across an entire year. This scheme reduces table size, but requires care
when filtering results and when joining to other tables. Also, if you assign some
VMT to a road type, but then do not select that road type in the RunSpec, the
population will be lower than it should be. This is because the assigned VMT is
not used when calculating population. Users should model all road types
(where VMT is allocated) to ensure proper calculations.

XCaution! If the calculation type Emission Rates is selected on the Scale panel, the
activity values will represent an intermediate step in the rates calculations
rather than the real activity for that time and place. To reduce file size, use
the Aggregation and Data Handling panel on the Advanced Peformance
Features screen to select "Clear MOVESActivityOutput after rate
calculations."
United States Environmental Protection Agency Page 1

-------
August 2010 MOVES User Guide

3. movesrun: This table contains information about the date and time of the run,
information about the run specification, and the name of the units in which MOVES
outputs are represented. These include units for energy (i.e., joules), emissions (i.e.,
tons), VMT (i.e., miles), and time units (i.e., months, days, hours, etc.).

4. moveserror: This table contains any error messages or diagnostic information that
might be generated if the MOVES run is unsuccessful.

5. movesworkersused: This table contains information as to which copy of theMOVES
Worker Program processed portions of the run. It is of interest if the run is executed on a
multi-computer configuration.

6. activitytype: This table lists the activity types that can be reported in the
movesactivityoutput table and provides their activitytypeid. In MOVES2010 this table
lists: distance traveled, source hours, extended idle hours, source hours operating, source
hours parked, population, and starts. (See also Section 2.2.10.1.3)

7. moveseventlog: This table is used by MOVES programmers for storing diagnostic
results. It contains no information useful to users.

8. rateperdistance: When "Emission Rates" is selected on the Scale panel, the
RatePerDistance table stores emissions as rates per distance (e.g. grams per mile) with
the units depending on those selected in the run specification. This table includes rates
for exhaust and evaporative emissions that occur while vehicles are on "real roads", but
does not include rates for starts, extended idle, or evaporative emissions (with the
exception of refueling) that occur while a vehicle is parked.

9. rateperprofile: When "Emission Rates" is selected on the Scale panel, the
RatePerProfile table stores vapor venting emissions from parked vehicles as rates per
vehicle (e.g. grams per vehicle). Note that the denominator is the total vehicle
population—not just the vehicles that are parked. The temperature profile id in this table
refers to a particular daily pattern of temperatures, important because vapor venting
depends on temperatures in both the current and previous hours.

10. ratepervehicle: When "Emission Rates" is selected on the Scale panel, the
RatePerProfile table stores emissions from starts and extended idle, and some evaporative
emissions (permeation and liquid leaks) from parked vehicles as rates per vehicle (e.g.
grams per vehicle). Note that the denominator for national and county level runs is the
total vehicle population—not just the vehicles that are parked. However, for project-level
runs the denominator for start emission rates is the number of starts in the hour, and the
denominator for extended idle emission rates is the vehicle-hours of extended idle
activity in the hour.

11. movestablesused: This table contains a list of the tables used when executing the
RunSpec and the source database for each table. The numbering of the
tableUseSequence is such that lower numbers take priority. Some tables may be listed
more than once; this occurs when information comes from both the user and default
databases.

Page 8 United States Environmental Protection Agency

-------
MOVES User Guide August 2010
12. bundletracking: This table contains information about data that is processed by the
MOVES master and workers. It is mainly used by the MOVES developers for tracking
MOVES performance.
2.0 Using MOVES

Using MOVES, the user can model various scenarios in order to determine specific
emissions profiles. To use MOVES the user prepares a Run Specification (RunSpec) to define
the place, time, vehicle, road, fuel, emission producing process, and pollutant parameters. The
RunSpec is an XML file that can be edited and executed directly or with the MOVES Graphical
User Interface (GUI). This section of the User Guide gives an overview of the screen layout and
navigation functions of the GUI, and provides details on how to create and modify a RunSpec.

Appendix C provides instructions for how MOVES can be executed without running its
graphical user interface. This may be useful in situations where repeated or unattended runs are
needed, or when another computer program is used to execute MOVES. This "batch mode," or
"command line" interface presumes that a MOVES RunSpec file has been prepared.

Although a full range of default data is available in MOVES, the allocation of the default
data down to the county level is based on a generalized algorithm and will not be the most recent
nor best available local data. Therefore, MOVES is designed to allow the user to customize the
model. The primary reasons a user would customize MOVES are:

• To better represent conditions and vehicle activity in a local area, especially for use in
conformity demonstrations or for SIP purposes; and,

• To alter inputs for "what-if analysis, such as the use of different I/M or fuel scenarios.

Several components of the model are intended to facilitate customization. These include
the Strategies procedures described below. MOVES also allows users to provide User Input
Databases and to use various Importers with the County Data Manager, and Project Data
Manager described later in this document.

For future versions of MOVES, EPA intends to develop additional data importers or
strategies to make it easier to incorporate alternate activity inputs.

-------
August 2010
                    MOVES User Guide
     2.1  Overview of MOVES User Interface

        The MOVES Graphical User Interface (GUI) consists of a Main Menu Bar, a Navigation
 Panel, and a Detail Panel.  The Main Menu Bar and Navigation Panel are available on every
 screen as the user prepares for execution of the RunSpec.  When the user selects a menu item
 from the Navigation Panel, the Detail Panel displays data elements specific to the parameter(s)
 defined by the menu item, and provides a platform for user input of parameter specifications.
Page 10
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
During execution of a RunSpec, a progress indicator will appear on the screen.
El MOVES C:\EpaWove5\MOVESGHGSource_12_02_2009\MOVES2010Exaniple.mrs ID 1830327669245506414
File Edit Preprocessing Action Postprocessing lools Settings Help
Generating bundles

estimating completion...

Progress Indicator

Execute active RunSpec
The Main Menu Bar will remain available, allowing the user to pause, resume, or stop
(cancel) the RunSpec during execution.

The MOVES model features "mouse hover" user help throughout the model. To use it,
the user simply places the mouse over a particular MOVES GUI icon or command and keeps it
still. A small help box will appear with a brief text message; for example, the readiness status of
a Navigation Panel icon, the keyboard combination required to execute a command from the
Main Menu Bar, or a brief description of a Detail Panel icon.

Most panels use buttons and scroll or drop down list boxes, typified by the "Select All"
"Delete" and "Add" buttons. These buttons will be enabled or disabled based upon selection in
the associated list box. For example, a "Delete" button will be disabled until a selection is made
in the associated list box.

^ Note When a selection is identified (e.g., by highlighting one state or county in a
Geographic Bounds list box), the user must click the "Add" button to add the selection
to the RunSpec. The user can consult the associated icon in the Navigation Panel to
determine if the parameter has been sufficiently defined. If the parameter icon changes
from exclamation point to check mark, the parameter definition is sufficient to allow
the RunSpec to be executed.
United States Environmental Protection Agency
Page 11

-------
August 2010
                     MOVES User Guide
     2.2 Navigation Panel

        The Navigation Panel appears on the left side of the MOVES screen and includes
 parameters the user must consider when setting up a RunSpec.
                H MOVES - ID 2548641089035511532
                File  Edit  Pre Processing Action  Post Process
                 ^^•2  Description

                       :  Scale

                         Time Spans

                         Geographic Bounds

                 \+\     Vehicles/Equipment

                         Road Type

                         Piiilkit.il its And Processes

                         Manage Input Data Sets

                 [+]     Strategies
                         Output
                         Advanced Performance Features
                Ready-
         Selecting an item from the Navigation Panel will open a user interface in the Detail Panel
 in the center of the MOVES screen.  In some cases, the RunSpec parameter listed on the
 Navigation Panel is split into sub-topics; these items are shown with an icon (m or lid) that
 allows the list of sub-topics to be expanded or collapsed. The user must click on the sub-topic
 for the user interface to be opened.

         The Navigation Panel includes icons that display the readiness status of the various
 RunSpec parameters. A RunSpec will not be executable if an exclamation mark is shown for
 any parameter.
Page 12
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
Icon
T
y
fef*jB
EB/E
Meaning
Needs additional user supplied data.
Sufficiently filled in to run.
Default data present, but otherwise sufficiently filled
in to run.
Parameter expand/collapse.
  7 Note  Parameters may be visited in any order, however some choices affect the choices
          available in other screens. In particular, changing the "Scale" parameters can impact
          other parameter choices. You may wish to save your Run Spec before switching Scales
          and to pay attention to the Navigation Panel icons after making any selection to make
          sure it did not affect another parameter.

       The icons shown on the sample GUI in this document do not necessarily indicate which
       sections/subsections will have default data available.

       A RunSpec cannot be executed  until all necessary data are supplied.

        2.2.1  Description

        Select Description, the first item on the Navigation Panel, to open a scrollable text
 window that allows the user to give the RunSpec a particular textual description.  This is useful
 for keeping track of various RunSpecs or providing information for someone else looking at the
 file (such as "This run produces annual total energy consumption for the nation in 1999"). The
 text entered in the Description Panel is for documentation purposes only. Its contents are
 reported for each run in the MOVESRun table.
United States Environmental Protection Agency
   Page 13

-------
August 2010
MOVES User Guide
MOVES - ID 89876001 977131 31 248
File Edit Pre Processing Action Post Processing lools Settings Help
/
^3 Scale
Time Spans
,
Geographic Bounds
\+\ ' Vehicles/Equipment
Road Type

Pollutants And Process

Manage Input Data Set'
\+\ f Strategies
El Output
j Advanced Performanci ^
< III \^ IH

Description:

Ready...
Up to 5,000 characters of text may be entered to describe the RunSpec.

The default Description is blank and the MOVES model can be run without a Description.
However, it is considered a best practice to carefully describe each and every version of a
RunSpec. This will assist in documenting the purpose of that particular MOVES2010 run.
See Appendix E, Best Practices, for additional information.

2.2.2 Scale

Select "Scale" on the Navigation Panel to choose the level of detail represented by the
MOVES input database and whether the model will calculate emissions sum or emissions rate
data.

2.2.2.1 Domain/Scale

National Domain/Scale is the default selection in MOVES. If National Domain/Scale
is selected, data collected on a nation-wide level is apportioned or allocated to states or counties.
This data will differ from data collected for a specific state or county. For example, consider
vehicle miles traveled. If using the National Domain/Scale, the primary input is national VMT
data which is then allocated to a county or state. The allocation does not take into account
factors that may differ between areas of the country (e.g. age distribution). Consequently, a
model run for two states or counties that uses the National Domain/Scale may not provide an
accurate portrayal of specific emission differences between these counties or states that would
occur due to dissimilar vehicle age distributions or other factors. For these reasons, the National
Domain/Scale cannot be used by states for preparing SIP or conformity analyses.
Page 14
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
E MOVFS - ID 166-I85969629B550561
File Edit Pre Processing Action Post Processing lools Settings Help
j Description

Time Spans

a
Geographic Bounds

B J Vehlcles€quipment

' OnRoadVehic

) RoadTwe

Pollutants And ProcE
/ Manage Input Data S
B
Alternative Vel
DomainiScale

* National Use the default national database with default state and local allocation factors.
I Caution: Do not use this scale setting for SIP or conformity
A analyses. The allocation factors and other defaults applied at
/|\ the state or county level have not been verified against specific
*^^ state or county data and do not meet regulatory requirements for
SIPs and conformity determinations.
i ' County Select or define a single county that is the entire domain.
Note: Use this scale setting for SIP and regional conformity analysis.
Use of this scale setting requires user-supplied local data for most
activity and fleet inputs.
0 Project Use project domain inputs.
Note: Use this scale setting for project-level analysis for conformity,
NEPA, or any other regulatory purpose. Use of this scale setting requires
user-supplied data at the link level for activity and fleet inputs that
describe a particular transportation project.
Calculation Type

® Inventory
Mass and/or Energy within a region and time span.
0
Emission Rates Mass and/or Energy per unit of activity.
MOVESScenariolD:
/X Caution: Changing these selections changes the contents of other
/ ' N input panels. These changes may include losing previous data contents.
For a finer level of detail about a particular area, the user can choose the County
Domain/Scale. With this scale choice, the model will replace national default allocations with
user-supplied data. Only one year and one county (or custom domain) can be selected in the
Time Span and Geographic Bounds panels, respectively. By supplying local data through the
County Data Manager (see Section 2.3.3) the user can provide more accurate information about
a particular state or county than would be provided using the National Domain/Scale. The
County Domain/Scale is intended to be used when doing SIP or regional conformity analyses.

Project Domain/Scale is the finest level of modeling in MOVES. It allows the user to
model the emission effects from a group of specific roadway links and/or a single off-network
location. The definition of a roadway link is a section of any road where a vehicle is moving for
more than three seconds. An off-network location is an area of activity that is not a roadway, for
example a parking lot where vehicle starts and extended idling emissions are produced. The use
of the Project Domain/Scale requires the user to completely define the individual project (i.e.,
specify all individual roadway links and/or the off-network area). All of the project level data is
entered in the Project Domain Manager (see Section 2.3.3.3.2) for data input details). If
specified correctly, the MOVES Project Domain/Scale will utilize MOVES emission rates and
other factors to correctly calculate emission inventory results for the user's defined project.

7 Note MOVES2010 is not capable of modeling any evaporative emission processes when
using Project Domain/Scale. EPA plans to add this feature in future versions of
MOVES.
United States Environmental Protection Agency
Page 15

-------
August 2010 MOVES User Guide

Note that switching scales is a major change to the RunSpec. It affects the operation of
other Navigation Panel items and may cause previous RunSpec specifications to be changed or
lost. You may wish to save your RunSpec before switching scales. Also, the choice the user
makes on the Domain/Scale panel affects the selections that will be presented in the Geographic
Bounds detail panel. These differences are covered in greater detail in Section 2.2.4 Geographic
Bounds.

2.2.2.2 Calculation Type

In this section of the panel, the user can choose the type of calculation that will occur in
the Run. MOVES will calculate the quantity of emissions and/or energy used within a region
and time span if the user selects the "Inventory" button. This output is stored in the
MOVESOutput and the MOVESActivityOutput tables.

The rate at which emissions occur (the mass and/or energy per unit of activity) is
calculated if the user selects the "Emission Rates" button. This output is stored in the
RatePerDistance, RatePerProfile and RatePerVehicle Tables.

Calculation Type
O Inventory Mass and/or Energy within a region and time span.
(•) Emission Rates Mass and/or Energy per unit of activity.
MOVESSeenarioID:
If you select Emission Rates, you must assign a MOVESScenarioID which will be used
in the rates tables. The MOVESScenarioID should be a unique identifier for the scenario for
which the rates apply. See Appendix A for more information on defining scenarios.

^ Note Calculating Emission Rates requires more run time and more output space than
inventory calculations, so this choice should be selected with care. See Appendix A for
advice on using the Emission Rates option to develop a "lookup table" of rates.

? Note While activity is "divided out" in the Emission Rates output, the amount of time spent
driving affects the evaporative emission rates. Therefore, it is important to input
realistic VMT, Population, Average Speed Distribution and Road Type Distribution
information.

^ Note If Emission Rates is selected as the Calculation Type, then several other panels are
affected:

1) If National Domain/Scale is selected, only "Zone & Link" can be chosen in
the "Region" section of the Geographic Bounds panel, or Ib) if County or Project
Domain/Scale is selected, only "Zone & Link" or "Custom Domain" can be chosen;

2) The "Distance Traveled" and "Population" boxes on the General Output
panel are automatically checked; and
Page 16 United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
               3) The "Road Type" and "Emission Process" boxes are automatically selected
          on the Output Emission Detail panel.

        2.2.3 Time Spans

        MOVES can be set to model specific time periods by selecting Time Spans on the
 Navigation Panel.  Clicking "Time Spans" will open the panel shown below.
         H MOVES ID 39220281797785936B7
1 File Edit Pre Processing Action Post Processing lools Settings Help
Description
r
Geographic Bounds
E] ' Vehicles E(|iii|)niMit
Road Type
Pollutants And Proces
Manage Input Data Set
[T] Strategies
El Output
Advanced Performanc
^\ ^^^^^


OYear O Month O Day ® Hour
V M Itth
Select Year: 2000 |^| Add 0 January DJuly
Years: Q February D August
D March D September
D April D October
D May D Novemlier
D June D December
| Remove Select All | Clear All


ays ours



D Weekend Start Hour: [lO:OQ- 10:59 |-^|
0 Weekdays End Hour: |l1:00- 11:59 1"|
Select All || Clear All Select All Clear All


Ready...
        This panel is divided into five sections with boxes, buttons, or drop-down menus in each,
 allowing the user to select specific aggregation levels, years, months, days, and hours. These
 panel sections are used to define the time period for which emissions will be modeled in the Run.
 In the screenshot depicted above, the user has specified that the Run should calculate emissions
 for the two hours from 10 am to noon on a typical January weekday in the year 2000. The
 emissions for each hour will be calculated separately.
United States Environmental Protection Agency
   Page 17

-------
August 2010 MOVES User Guide

2.2.3.1 Time Aggregation Level

Click in the Time Aggregation Level section to set the level of pre-aggregation that is
desired. Only one choice can be selected. The default level is "Hour" and implies no pre-
aggregation of the MOVES data by time. If the user chooses a longer aggregation level time
period such as "Year", "Month", or "Day", the model will pre-aggregate (i.e., compute a
weighted average of) all underlying MOVES internal data that are differentiated by hour (e.g.,
temperatures, VMT distributions, etc) prior to execution of the run. For example, if the user
chooses "Month", the model will average the temperatures of all selected Days and Hours into
an average "Month" set (it may be a set because the temperatures will not necessarily be
averaged by geography unless that has also been pre-aggregated), and perform the simulation
with these average values. Pre-aggregation sacrifices precision to improve model run time.

7 Note Once the user has selected a higher aggregation level than "Hour", the model's GUI
will automatically fill in the required lower GUI inputs. For example, if the user selects
the "Month" button in the Time Aggregation Level panel, the model will fill in all of
the hours and days input. After the initial automatic selection, the user may de-select
particular hours, kinds of days, or months. If such a de-selection is done, the user will
end up with results that are based on aggregations that do not include de-selected hours,
days, or months. For example, if the user selects "Months" in the Time Aggregation
Level panel and de-selects "Weekends", the final emission result will represent a
monthly aggregation that includes "Weekdays" only.

7 Note The proper levels of time aggregation for SIP and conformity analysis will be addressed
in guidance documents.

XCaution! Because of non-linearity in the general MOVES algorithm, differences may arise
between aggregated results and non-aggregated results. For example, the emission
results from a run where all 24 hours are selected and the Time Aggregation Level
is set to "Hour" may not match the results from a run where the Time Aggregation
Level is set to "Day".

2.2.3.2 Years

Select a calendar year(s) in the Years section and click on the "Add" button. Select a
year by clicking the black triangle to see a drop-down list of calendar years and select an
individual year. Click on "Add" to have that year appear in the Year selection pane. This can
be repeated to select as many years as desired if National Domain/Scale has been chosen.
However, if County or Project Domain/Scale was chosen on the Scale panel, only 1 year can
be selected in the Year pane. Use the "Remove" button to deselect years.

At least one calendar year must appear in the Years Selection panel to obtain a
valid Time Spans input
Page 18 United States Environmental Protection Agency

-------
MOVES User Guide August 2010

2.2.3.3 Months

Click one or more individual months to model to select the appropriate boxes in the
Months section. At least one Month box must be selected. Click the "Select All" button to
select all of the months. Similarly, the "Clear All" button removes all of the previously chosen
months.

? Note If the Project Domain/Scale is selected, the Run Spec may cover only a single month..

2.2.3.4 Days

Click one or more kinds of days of the week to model to select the appropriate boxes in
the Days section. At least one kind of Day box must be selected. Click "Select AH" button to
select all of the days. Similarly, the "Clear All" button removes all of the previously chosen day
types.

^ Note If the Project Domain/Scale is selected, the Run Spec may cover only a single type of
day.

2.2.3.5 Hours

The default time resolution for MOVES at both National and County Domain/Scale is
hourly, with hours expressed in military time ranging from midnight - 12:59 am (expressed as
00:00-00:59) to 11 pm - 11:59 pm (23:00 - 23:59). Use the drop down menu to select the
appropriate Start and End hours from the list. Click the "Select All" button to select all of the
hours of the day. Similarly, the "Clear All" button removes all of the previously selected hours
of the day.

The times selected are relative to the time zone so that 7:00 to 9:59 AM is 7:00 to 9:59 AM
in each selected county-state combination.

If only one hour of output is desired, select the same entry for start time and end time (i.e.,
0-0:59 and 0-0:59). This will produce one hour of output.

7 Note If the Project Domain/Scale is selected, the Run Spec may cover only a single hour..

? Note The hours selected are run for all chosen days, so it is not possible, for example, to
model only from 11:00 PM on Friday to 01:59 AM on Saturday. It is also not possible
to run the model for a group of months that span a year end. That is, the user cannot
run the model for just December of 2003 through January 2004. However, the model
can be run multiple times with different RunSpec time spans to accomplish these tasks,
or it can be run for multiple days or years and then manually post-processed to
eliminate the un-needed times.

2.2.4 Geographic Bounds

Selecting Geographic Bounds allows the user to define the region to model. The
options available on this panel depend on the choice of Domain/Scale and Calculation Type

United States Environmental Protection Agency Page 19

-------
August 2010
MOVES User Guide
(see Section 2.2.2 of this User Guide). If the user has chosen Inventory calculations at the
National scale, the following screen will appear:
Pre Processing Action Post Processing Tools Settings Help

Description
ALABAMA
ALASKA
ARIZONA
ARKANSAS
CALIFORNIA
COLORADO
CONNECTICUT
DELAWARE
DISTRICT OF COLUMBIA
»
-

O Nation

Ostate

• County

O Zone & Link

O Custom Domain
Geographic Bounds Requirements
Please select a state and county.
Caution: For SIP or regional conformity analyses, you must go back to the
} Scale window and select "County" before specifying a county in this window.
Caution: You have selected National scale with detail at the State or County level.
MOVES will use the default national database with default state and local allocation
} factors. These factors have not been verified against actual state or county level
data and do not meet regulatory requirements for SEPs and conformity determinations.
Ready...
Three buttons, "Nation", "State" and "County" are normally available. Choose the one
appropriate for your desired run.

XCaution! Your choice of "Region" will impact your results. If the user chooses the "Nation"
or "State" input options, the model will pre-aggregate (i.e., compute a weighted
average of) all underlying data that is a function of geography (temperatures, road
types, etc) and execute the "National" or "State" run as if it were a single county
run. Thus, a run at "Nation" or "State" level will be faster than a "County" level run
for the same area, but it will be less accurate.

For example, if the user chooses "State" and "Michigan," the model will average the
temperatures of all Michigan counties into a single average set (it will be a set because the
temperatures will not necessarily be averaged by time) and perform the simulation with these
average values. The report "MOVES2004 Validation Results" includes a sensitivity analysis of
different pre-aggregation levels. An alternative method of computing a state simulation is to
select "County" Region and then selecting all the individual counties in the desired state. If the
user chooses this option, no pre-aggregation will be done and the model will execute separate
simulations for each county in the particular state. This option will likely produce a slightly
different emission result than if the geographic specific data were first aggregated and then used
because of non-linear calculations in some algorithms.
Page 20
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
  XCaution!  Be advised that if an entire state or nation is run at the county level, execution times
               may be quite long.  For such runs, we generally recommend multiple-computer
               processing.

         Nation: Choose "Nation" to run scenarios and compute emission inventory results for
  all counties/parishes in the United States and Territories.  The "Nation" button is generally
  chosen if the user wishes to create a simple national U.S.  emission inventory.
         E MOVES - ID 7216242696906493518
         File Edit Pre Processing Action Post Processing lools Settings Help
                           Region:
                           Ostate

                           O County

                           O Zone & Link

                           O Custom Domain
                              Geographic Bounds Requirements
                                        Caution: For SIP or regional conformity analyses, you must go back to the
                                       t Scale window and select "County" before specifying a county in this window.
         State:  Choose "State" to run scenarios and compute emission inventories for particular
  States or Territories within the United States. This panel has two parts (States, and Selections)
  and buttons for choosing the appropriate selections.
United States Environmental Protection Agency
   Page  21

-------
August 2010
MOVES User Guide
Edit Pre Processing Action
Postprocessing Tools Settings Hell)
ALABAMA
ALASKA
ARIZONA
ARKANSAS
CALIFORNIA
COLORADO
C County

O Zone & Link
DELAWARE
DISTRICT OF COLUMBIA
Geographic Bounds Re(|tiiiemen1 :
Caution: For SIP or regional conformity analyses, you must go back to the
Scale window and select "County" before specifying a county in tliis window.
Caution: You have selected National scale with detail at the State or County level.
MOVES will use the default national database with default state and local allocation
factors. These factors have not been verified against actual state or county level
data and do not meet regulatory requirements for SIPs and conformity determinations.
To choose the desired state(s):

1. Scroll to desired state in "States" box and click on it to highlight. Click
the "Add" button under box. State will appear in the "Selections" box.
2.
available.
Click the "Select AH" button to choose all U.S. states and territories
To remove a previously selected state, highlight it in "Selections" box and click the
"Delete" button.

? Note The "Add" and "Delete" buttons are inactive if no states are highlighted.

County: Choose "County" to run scenarios and compute emission inventories for
specific counties within a state. If the "County" button is selected, a new bounds panel will
show in the Detail Panel, as shown below.
Page 22
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
0 MOVES ID 7?1 624265690649351 6 - d X
File Edit Pie Processing Action Post Processing Tools Settings Help
Description
j Scale
' Time Spans
El | Vehicles/Equipment
Road Type
Pollutants And Proces
Manage Input Data Sei
El , Strategies
El Output
Advanced Performartc
^^^^^ii^^^^^^^^^M
Region: states: Counties: Selections:
O Nation ALABAMA »
ALASKA
ARIZONA
« County ARKANSAS
CALIFORNIA
COLORADO
0 Custom Domain CONNECTICUT
DELAWARE
DISTRICT OF COLUMBIA -

Select All
Geographic Bounds Requirements
Please select a state and county.
/\ Caution: For SIP or regional conformity analyses, you must go back to the
/!\ Scale window and select "County" before specifying a county in this window.
Caution: You have selected National scale with detail at the State or County level.
/\ MOVES will use the default national database with default state and local allocation
tlj factors. These factors have not been verified against actual state or county level
data and do not meet regulatory requirements for SIPs and conformity determinations.
< I III .
Ready...
The process for selecting a specific county is similar to selecting a state, outlined above.

When using the County Domain/Scale and Inventory calculation type, the Region
portion of the Geographic Bounds detail panel indicates County by default, and the user must
specify the state and county in the manner detailed above.

When using the Project Domain/Scale and Inventory calculation type, the Region
portion of the Geographic Bounds detail panel indicates County by default, and the user must
specify the state and county in the manner detailed earlier.

When a user selects the Emission Rates calculation type on the Scale panel, the
Geographic Bounds panel allows a choice of Zone & Link at the National scale, and Zone &
Link or Custom Domain at the County and Project scales.

When either the County or Project is chosen on the Scale panel, the user can also define
a "custom county" by selecting the Custom Domain option in the Region portion of the
Geographic Bounds panel, as shown in the screen shot below.
United States Environmental Protection Agency
Page 23

-------
August 2010
MOVES User Guide
File Edit Pre Processing Action Post Processing Tools Settings Help
Generic County
State ID: 5
County ID:

Description:

GPA Fraction: [o 0
Bar. Pressure:

Vapor Adjust:

Spill Adjust: rn
| 1-999, labels the county within a state.
Fraction of county within a fuel Geographic Phase-in Area
inHg (avg. for low altitude is 28.9, avg. for high is 24.6)
Refueling Vapor Program Adjustment Fraction
Refueling Spill Program Adjustment Fraction
Domain Input Database
The County domain scale requires a database of detailed data.
Server:
Enter'Edit Data
Geographic Bounds Requirements
3lease select a domain database.
In this case, the user must provide a short county identifier (1-999) that will combine with
the state ID (99 for generic) to form the standard 5 digit county identifier used throughout
MOVES. In addition, the user must provide a description and GPA (Geographic Phase-in Area)
fraction. The Geographic Phase-in Area refers to a group of counties in the western U.S. that
had special gasoline sulfur requirements under Tier 2 regulations. See 65 Fed. Reg. 6755-6759
for details on the GPA. The user must also provide the Barometric Pressure (in inches of
mercury, inHg) and the Vapor and Spill Adjustment factors, which describe the Stage II
Refueling program in the area.

7 Note Barometric Pressure must be indicated by the user for two reasons: 1) it is a required
input for some MOVES calculations; and 2) the area is assigned a "Low" or "High"
altitude depending on the user's input (areas with pressure less than or equal to 25.8403
are high altitude; areas with pressure greater than 25.8403 are low altitude).

A user might want to use the Custom Domain option to represent an area that
encompasses a portion of a county, multiple counties, or an area that crosses state
boundaries (a nonattainment area may have these characteristics).

When either the County or Project is chosen on the Scale panel, the Geographic
Bounds panel will contain an area in which to define the Domain Input Database for the
model, as shown in the following screenshot.
Page 24
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
Region:

O Nation

O State

• County

O Zone & Link

O Custom Domain
ALABAMA
ALASKA
ARIZONA
ARKANSAS
CALIFORNIA
COLORADO
CONNECTICUT
DELAWARE
DISTRICT Of COLUMBIA
*

Domain Input Database
The County domain scale requires a database of detailed data.
"• EnterJEditData
Geographic Bounds Requirements
Please select a state and county.
Please select a domain database.
For both the County and Custom Domain option, the user must specify the user-
supplied database that will contain county-specific data. For Project scale, a database of detailed
information on the project is required. See section 2.3.3.3 Data Importer, County Data
Manager and Project Domain Manager for more information. In most cases, this database
will be located on the server "localhost" (generally the user's own machine); however, the user
can specify a different host server in the Server box. After specifying a server, the user must
identify a database to receive the data that will be imported. If the user has already created the
database, it can be selected by clicking on the drop-down arrow adjacent to the Database box
and making a selection from the drop-down list. If the database has not been created or if the
user wants to make changes to the database, the user can click the "Enter/Edit Data" button to
open the County Data Manager

The user should be sure to fill out all panels and fields to define the RunSpec before using
the County Data Manager or Project Domain Manager The selections in the Run Spec
are used by the County Data Manager to define the data needed for the county data to be
complete, and to filter the data used when creating export or template files.

XCaution! Defaults that are exported from the MOVES database are generally not appropriate
for SIP or conformity analyses. See MOVES Policy Guidance document for more
information.

7 Note If the user selects Custom Domain, the County Data Manager will not export any
default data; therefore, the user must have all the required information to use this
option.
United States Environmental Protection Agency
Page 25

-------
August 2010
MOVES User Guide
The user can clear the selected database and update the list of available databases by
clicking the "Refresh" button.

The Geographic Bounds panel includes the text box, Geographic Bounds
Requirements, which defines what is expected of the user on the panel.

2.2.5 Vehicles/Equipment

To select which on-road vehicles are to be modeled, click on Vehicles/Equipment in the
Navigation Panel. This will open the On Road Vehicle Equipment Detail Panel. Two lists
(Fuels and Source Use Types) appear to the left of this panel to allow distinct selections for the
vehicles/equipment.
7 Note We hope to add additional fuels in the future, and the "Placeholder Fuel Type" is an
incomplete step in this direction. However, the Placeholder Fuel is not currently active,
and there is no reason to select it.
Compressed Natural Gas (CNG)
Diesel Fuel
Electricity
Gasoline
Liquefied Petroleum Gas (LPG)
Placeholder Fuel Type
Combination Long-haul Truck
Combination Short haul Truck
Intercity Bus
-iglit Commercial Truck
Motor Home
Motorcycle
Passenger Car
Passenger Truck
Ftefuse Truck
School Bus
Single Unit Long-haul Truck
Single Unit Short-haul Truck
Transit Bus
Add Fuel Type Combinations
Please select a Fuel and Source Use Type combination.
On Road Vehicle Equipment Requirements
Ready...
1. Click and highlight the Fuels choice or click the "Select All" button to choose all the
choices.

2. Click and highlight the Source Use Types choice or click the "Select All" button to
choose all the choices.

3. Click "Add Fuel/Type Combinations" button to move the selected choices to the
Selections box
Page 26
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
To clear highlighted selections from Selections box click "Delete"

? Note No default selection will appear on this panel, and the model cannot be run without a
selection made.

7 Note The On Road Vehicle Equipment panel contains a small subpanel at the bottom that
reminds the user that they are required to select a Fuel and Source Use type. This panel
disappears after the user makes a valid Fuel and Source Use Type selection. If a
selected combination is not in the database, the subpanel will notify the user that the
combination is invalid (e.g. "Diesel fuel/Motorcycle combination is not in the
database"). These non-existent combinations do not need to be removed from the
RunSpec, but no results are reported for such vehicles.
2.2.6 Road Type

If any on-road vehicle has been selected (see Section 2.3.4 Vehicles/Equipment), the
Road Type panel becomes available on the Navigation Panel, allowing the selection of road
type. All Road Type panel controls are disabled otherwise.
File Edit Pre Processing Action Post Processing lools Settings Help
, Description
Time Spans

Geographic Bounds

Vehicl es.Equ ip ment

1 On Road Vehicle Equipmerv
Available Road Types:
Selected Road Types:
Off Network
Rural Restricted Access
Rural Unrestricted Access
Urban Restricted Access
Urban Unrestricted Acces
The user must select at least one road type.

1. Click and highlight the desired Road Types from the list.
2. Click the "Select AH" button to select all Road Types in list.
United States Environmental Protection Agency
Page 21

-------
August 2010 MOVES User Guide

3. Click the "Add" button to move choice to the Selected Road Types box.

Click the "Delete" button to clear the highlighted selections.
7 Note The list of Road Types is the complete list of roadway types present in the underlying
MOVES database. The default database has Road Types that represent urban and rural
driving on roads with restricted and unrestricted vehicle access. Restricted access
roadtypes are usually used to model freeways and interstates; ramps are considered part
of restricted access roadtypes. The Ramp Fraction tab of the CDM (see Section
2.3.3.4) will only become available if an unrestricted road type (i.e. 2 or 4) is selected.

7 Note "Off Network" is automatically selected when start or extended idle processes are
selected on the "Pollutants and Processes" panel. All Road Types are automatically
selected when any evaporative or refueling processes are selected on the "Pollutants
and Processes" panel.

All Road Types in an area on which VMT is allocated should be selected to correctly
calculate population.

XCaution! Selected Road Types may or may not exist in the geographic bounds of the
RunSpec. For example, a county may have no urban roads. MOVES will display
results only for road types that exist in the selected geographic area.

2.2.7 Pollutants and Processes

To select the pollutants and processes to include in the RunSpec, the user should choose
Pollutants and Processes on the Navigation Panel. A matrix will appear in the Detail Panel,
with "Pollutants" listed as rows and "Processes" listed as columns. When a pollutant/process
combination is selected by clicking a check box, it is included in the RunSpec. When the
RunSpec is run, the model will compute emissions for that pollutant/process combination.
Page 28 United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
File Edit Pie Processing Action Postprocessing Tools Settings Help
Manage Input Data Set

\+\ t Strategies

' Output

Advanced Petfoi
There is no limit to the number of boxes that may be checked; however, at least one box
must be checked to produce a valid MOVES RunSpec input.

7 Note It may be necessary to scroll the Pollutants and Processes panel to see all of the
Process columns or Pollutant rows.

^ Note Checking the box on the left side of the panel will select all of the processes for that
pollutant. The box on the left side of the panel will also show a check if any process is
selected. Additionally, unchecking the box on the left side of the panel will deselect all
processes for that pollutant.

^ Note In order to replicate MOBIL6.2 runs (e.g. to compare the results of the two models), all
processes except extended idle need to be selected.

XCaution! Users are cautioned that the number of check boxes selected will affect execution
time. Large runs calculating many pollutant/process combinations may require
processing times of several hours, so users are advised to begin with only a few
pollutant/process combinations.

A Pollutant/Process Requirements box is included at the bottom of the Detail Panel.
Text in this box actively responds to pollutant/process combination selections made in the
matrix. In some cases, a specific pollutant/process calculation depends upon another
pollutant/process calculation, and the user must select the base pollutant/process combination in
order to be able to select the dependent combination. An error message will appear in the
Pollutant/Process Requirements box should the user not select the base combination.
United States Environmental Protection Agency
Page 29

-------
August 2010 MOVES User Guide
2.2.7.1 Processes

In MOVES, "Process" refers to the mechanism by which emissions are created. Engine
operation creates Running Emissions Exhaust, Start Emissions Exhaust (the addition to
running emissions caused by the engine start), and Extended Idle Emissions Exhaust (i.e.,
"hotelling" emissions from a combination long-haul truck). MOVES also distinguishes
Crankcase Running Exhaust, Crankcase Start Exhaust, and Crankcase Extended Idle
Exhaust to describe the exhaust gases that escape around the piston rings and enter the
crankcase during normal operation.

MOVES models evaporative emissions, situations in which unburned fuel escapes the
vehicle's fuel system, through the "Evap Fuel Vapor Venting", "Evap Permeation", and "Evap
Fuel Leaks" processes. In addition, vehicle refueling can cause "Refueling Spillage Loss" and
"Refueling Displacement Vapor Loss" "Brakewear" and "Tirewear" describe the non-
exhaust paniculate emissions that result from brake use and tire wear.

2.2.7.2 Pollutants

MOVES allows the user to calculate emissions of criteria pollutants, greenhouse gases,
and air toxics associated with motor vehicle operation. MOVES also calculates energy
consumption. For many pollutants, the emissions calculation is based on the prior calculation of
another pollutant emission. As noted earlier, the Pollutant/Process Requirements box will
display an error message if the user selects a dependent pollutant but not the base pollutant.
Pollutants and base pollutants are listed in Table 2.2.7.2 below.
Page 30 United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
Pollutant Name
Total Gaseous Hydrocarbons
Hon-methane Hydrocarbons
Hon-inethane Organic Gases
Total Organic Gases
Volatile Organic Compounds
Carbon Monoxide
Oxides of Nitrogen
Ammonia.
Nitrogen Oxide
Hirrogen Dioxide
SuHur Dioxide
Primary PMO Total
PEPMID Organic Carbon
PEPMID Ekmental Carboi
PEPM10 SuHate PMtiailatje
PEPMID BrahewearParnculalje
PEPMIO Tin-wear ParLUnlate
Primary PM25 Total
PEPM25 Organk Carbcti
PEPM25 Ekmsntal Carbon
PEPM25 Suffide Pattioihrje
PEPM25 BrakewsarPaitioalate
PEPM2 5 Tirswear Paniculate
Total Energy Ccnsunpticn
Petrolemii Energy CcnsumptictL
Fossil Fuel Etuergy CctfiAjmpricti
Methane (CIL)
Hirrou; Oxide (H;0)
AtmospiKii: Carbon Dicodd* ( C 0 : )
C 0 : equiiralent
Benzene
Ethaool
Methyl tsrtiary bayl eiher (MBTE)
Naplthakne
13Butadi*ne
Fonruddehydie
AcetaBel^de
Ajcrolan
Abb relation
THC
HMHC
HMOG
TOG
VDC
CO
HO.
HH-
HO
H0:
SO:
PM1D
PM1DOC
PMIDEC
PM1DSO,

PM2JOC
PM2JEC
PM2JSO,

TEC
PEC
FFEC
CIL
N;0
CO:
C0;e
C,H.
C:H,0
C.H,;0
C,.H,
CJI.
CH;0
C;H,,0
CH.O
Includes

HOJTO;

PM100C
PM10EC
PM1DSO.

PM2JOC
PM2JEC
PEPM2JSO,,

C0;, CHL,H;0

Depends on

THC and CIL
HMHC
HMOGaidCH-
HMHC

HO.
HO.

PM2JOC
PM2JEC
Total Eneigy CctismMftictt.

Total Energy CcnsunipticrL

Total Eneigy CcnsumpticfL
Total Etieigy Cct^urcoticti

Total Energy Ccnaimpticn

VOC
iroc
VOC
PM1D Total
THC
VOC
VOC
VOC
VOC
Table 2.2.7.2

2.2.8 Manage Input Data Sets

Select Manage Input Data Sets on the Navigation Panel to specify databases containing
user-supplied data to be read by the model during execution. Databases entered using this
feature will overlay existing databases tables (or portions of a table, if a table containing only a
subset of records is provided) in the MOVES default database tables, if they exist. No default
selections exist for this panel and the model can be run without any selections on this panel.

^ Note Each database added through this feature can consist of one or more MOVES input
database tables.
United States Environmental Protection Agency
Page 31

-------
August 2010
MOVES User Guide
B MOVES - ID 2101066914948040296 (_J(nJ(Xj
File Edit Pre Processing Action Post Processing Tools Settings Help
Description
y Scale
Time Spans
Geographic Bounds
0 F VehiclesiEquipment
On Road Vehicle Equipment
Road Type

BE
B strategies

Alternative Vehicle Fuels &
f On-Road Retrofit
/ Rate Of Progress
B > Output
General Output
Output Emissions Detail
Advanced Performance Features
^^ ^^^ I >

Server: Selections:
Database: •*
Description: j
Refresh

Create Database...

Move Up 1 1 Move Down Delete

teady...
7 Note These databases must adhere to the MOVES schema and use the database management
system (DBMS) used by MOVES. In practice this means that individual tables in the
user-supplied database must have identical names as the MOVES default input database
and the individual fields in the tables must have identical lengths and types as MOVES
default tables. For details regarding the MOVES database schema see the Software
Design Reference Manual.

The data in user input databases take priority over data from the MOVES default database.

^ Note Entries in the Manage Input Data Sets panel are used in the run, but will not change
the values in the MOVES default database.

To create a new database with empty tables of the proper schema on an existing local or
remote server, type the server and a new database name and click the "Create Database" button.
Leaving the server box blank creates the new database on the localhost server.

You can use database tools outside of MOVES, such as MySQL, to populate new database
tables with alternate values. Within MOVES, the Data Importer, County Data Manager, and
Project Domain Manager also aid in creating and populating User Input databases. For more
information about each of these tools, see Sections 2.3.3.3 Data Importer, County Data
Manager and Project Domain Manager.
Page 32
United States Environmental Protection Agency

-------
MOVES User Guide August 2010

Databases created with the County Data Manager or Project Domain Manager are
selected in the Domain Input Database pane of the Geographic Bounds panel rather
than the Manage Input Data Sets panel.

To choose a database, select it from the dropdown list, and click the "Add" button to add the new
or existing database to the input databases, shown in the Selections window. MOVES will first
validate that the combination of server and database are unique within the selections. The same
server-database combination cannot be added more than once. Click the "Move Up" or "Move
Down" buttons to modify the order in which a particular database selection is used. To remove a
database, highlight it and click the "Delete" button.

The order in which these databases are applied to the default data is important. If two or
more alternate databases are specified in the Selections list, the one that appears last in the
list will replace any previous ones in cases where the internal tables and records of each
database overlap.
2.2.9 Creating and Using Internal Control Strategies

In MOVES, "Strategies" are sets of parameters that replace MOVES defaults, and thus
allow the user to model different future scenarios. MOVES has two internal control strategies
that are built into the RunSpec Navigation Panel. The "Alternate Vehicle Fuels &
Technologies" (AVFT) strategy allows users to modify the fraction of vehicles using different
fules and technologies in each model year. The "On-Road Retrofit" strategy allows the user to
enter information about diesel trucks and buses that have been retrofit with emission control
equipment. The use of control strategies is optional; if the user does not select any strategy, the
RunSpec will use data from the MOVES default database.
United States Environmental Protection Agency Page 33

-------
August 2010
                    MOVES User Guide
        The selection of either strategy opens a split panel on the screen. The left side of the
 panel is common for both Strategies menu options. It is called the Strategies Management
 panel (shown in the screen shot above), and contains buttons that enable the user to add, import,
 export, delete, and check data. Detailed information specific to the strategy appears to the right,
 on the Strategies Detail panel.

        The buttons on the Strategies Management panel are used to manipulate the strategy
 data sets, or "objects", needed for each RunSpec, as explained below.  The panels and tools for
 the AVFT and On-Road Retrofit Strategies are similar, but not identical.

 XCaution! A RunSpec may have only one AVFT and one On-Road Retrofit strategy. The
             "New" button cannot be selected without first clicking "Delete" to remove any
             existing loaded object.  If a strategy data set is already loaded and the user imports a
             new file, the import action will overwrite the existing data set.

           2.2.9.1  Adding Strategy Files

        Users can add new strategy data to a RunSpec by clicking the "New" button or the
 "Import" button.

        Clicking the "New" button creates a new strategy data set, which is added to the
 RunSpec. The new strategy data appears on the list of "Loaded Objects" as "(default)".
 However, in MOVES, the "Loaded Objects" window does not function as intended and should
 be ignored.

        Clicking the "Import" button allows the user to import an appropriate input file. The
 AVFT Strategy allows the user to import XML, tab-delimited text, and Microsoft Excel files.
Page 34
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
 The On-Road Retrofit Strategy allows the user to import Microsoft Excel (.xls), tab-delimited
 text files, or comma-delimited text. Typically, the import file is created by exporting a template
 file, editing it in a spreadsheet, saving the edited version as a tab-delimited text file, and
 importing this text file.
        B MOVES - ID 2101066914948040296
        File Edit Pre Processing Action Post Processing Tools Settings Help
                                                 Use the "Import..." button to select an AVFT parameter file.
       Ready...
  ^ Note  The AVFT will not import comma-separated data files.

            2.2.9.2  Deleting Strategy Files

        The user may delete a strategy data set from the RunSpec by clicking the "Delete" button.
 MOVES will prompt the user for confirmation before actually removing the data set.

            2.2.9.3  Exporting Strategy Files

        The "Export" button allows the user to write strategy parameter sets to file for storage.
 When the user clicks "Export", a standard Windows file browser appears from which the user
 can name a file to which to write the data as tab-delimited text.

        To create a  template file for the AVFT, the user should "Export Default." To create a
 template file for the On-Road Retrofit strategies, the user chooses "New," and then exports a file
 containing only headers.  Both the AVFT and the On-Road Retrofit Strategies allow the user to
 export previously imported files.
United States Environmental Protection Agency
   Page 35

-------
August 2010
MOVES User Guide
2.2.9.4 Naming Strategy Files

By clicking the "Description" button, the dialog box shown below is displayed:
Changing the description will change the text shown in the "Loaded Objects" window.
However, importing different files will not change the description.

The Desciption text can be misleading since it must be manually updated if new strategy
files are loaded. Users may wish to leave it blank.

2.2.9.5 Saving and Transferring Strategy Files

Strategies can exist both inside and outside of a RunSpec, that is, the parameters can be
saved as part of a RunSpec and/or as a separate file that can be re-used from one RunSpec to the
next. This feature can help a user create a set of RunSpecs that use a consistent set of strategy
settings. The "Import" and "Export" buttons allow for the transfer of strategy data between
RunSpecs.

Using the File menu to save and open RunSpecs automatically saves and loads the
Strategies embedded within the RunSpecs. The files containing the strategies do not need to be
imported separately. However, the version of the file embedded within the RunSpec is set at the
time of the import; in other words, if any change are made to the strategy file outside of
MOVES, the file must again be imported for the RunSpec to reflect the changes made.

2.2.9.6 Creating AVFT files outside of MOVES

To create AVFT strategy files outside of MOVES, it is easiest to start by exporting the
default parameters as a template, then opening the saved file with a spreadsheet program such as
Microsoft Excel.

The first row contains field names: "SourceTypelD", "ModelYear", "fueltypelD",
"EngTechID" and "FuelEngFraction". Default SourceTypelDs and FuelTypelDs are defined in
the SourceUseType and Fuel Type tables of the MOVES Default Database and are summarized
in Appendix I. "ModelYear" refers to the model year of the vehicles. "EngTechID" refers to
the engine technology type: "Conventional Internal Combustion" for most fuels, "Electric" for
vehicles with a Fueltype of "Electricity.",. "FuelEngFraction" refers to the fraction of the
sourcetype in that model year that have that combination of fueltype and engine technology.

Beneath the field names are data rows. For MOVES2010a, there are about 2046 rows in
an AVFT file if all source types are selected. Users can add rows for new fuel/engine technology
Page 36
United States Environmental Protection Agency

-------
MOVES User Guide August 2010

combinations if they are allowed for that sourcetype, or delete rows for combinations that the
user does not want included. Once the user has decided upon a complete set of fuel and engine
technologies for a source type/model year combination, the user should edit the
"FuelEngFraction" in each row so that the fractions entered sum to 1 within the source
type/model year combination.
The edited AVFT file should be saved as a tab-delimited text file and then imported into
the desired RunSpec(s) using the "Import" button.

If all years do not sum to one, the panel will display an error message and an option to
"Normalize" the data. Normalizing will proportionally adjust the entries so that each
sourcetype/modelyear combination sums to one.

If you "Normalize" imported AVFT data, it can be useful to export and view the
normalized data to make sure that the normalization adjustments lead to the
vehicle mix you intended

2.2.9.7 Managing On-Road Vehicle Retrofit Data

MOVES has the capability to model on-road vehicle retrofit strategies for all exhaust
pollutants for diesel trucks and buses. Appendix D provides detailed instructions for creating an
On-Road Retrofit data file
To add on-road vehicle retrofit data, the user should click the On-Road Retrofit option
under Strategies on the Navigation Panel. This will open the On-Road Retrofit panel, which
displays the Strategies Management Panel on the left side of the panel as described earlier in
the Strategies section. The "Description", "New", "Export", "Delete", and "Check" buttons
work as described earlier.
^ Note The Retrofit Strategy only works for non-passenger diesel trucks and buses. Importing
a strategy for motorcycles, cars, passenger trucks or for other fuel types will generate
an error.

The "Import" button is similar to the AVFT import and is described below.
United States Environmental Protection Agency Page 37

-------
August 2010
                                        MOVES User Guide
         O MOVES  ID 2101066914948040296
         File Edit Pre Processing Action Post Processing  Tools Settings Help
            j Description

              Scale

              Time Spans

             ' Geographic Bounds

         B  ' Vehicles/Equipment

                 On Road Vehicle Equipment

              Road Type

              Pollutants And Processes

              Manage Input Data Sets

         B / Strategies

               ,  Alternative Vehicle Fuels &



                 Rate Of Progress

         B  ' Output

                 General Output

               j  Output Emissions Detail

              Advanced Performance Features
                                          -Road Vehicle Retrofit
Use the "Import..." button to select a retofit parameter file.
            2.2.9.8 Importing Retrofit Data

         When the user clicks on "On-Road Retrofit", the Detail Panel to the right of the
  Strategies Management Panel instructs the user to click the "New" button first and then click
  the "Import" button to select a retrofit parameter file.  The "Import" button enables the user to
  import On-Road Retrofit data as a tab delimited, comma separated (.csv), or .xls file. When the
  user clicks on  "Import", a standard Windows file browser window appears from which the user
  can select the file. If an  .xls file is imported, MOVES will prompt the user to specify a
  worksheet from which the  data should be imported

         Once data are imported, the display in the Detail Panel will show the name and location
  of the imported file ("Data Source").  A "Reload" button that will also appear next to the file
  name can be clicked on to  capture any changes to the imported data file.

         Importing retrofit data automatically saves the data to the RunSpec, but it does not
  automatically apply the retrofit parameters to the emission results that MOVES produces.  To
  apply the retrofit parameters to the emission results, the user must check, the Use the On-Road
  Retrofit Settings box that appears at the top of the On-Road Retrofit panel. This allows the user
  to turn retrofit on and off without reloading the files.

  X CAUTION! If the user  does not select Use the On-Road Retrofit Settings, the retrofit inputs
               will not be used.
Page 38
                  United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
If there are any data format or consistency issues in a file that the user is trying to import
(e.g., incorrect number of columns or data that are inconsistent with what the user selected
elsewhere in the MOVES GUI), a message(s) will appear in the Messages window at the bottom
of the panel. Importing data for retrofits requires that the user enter the description of the field
(e.g. NOX rather than pollutant 3).

2.2.9.9 Rate of Progress Calculation
El MOVES ID 2101066914949040296
File Edit Preprocessing Action Postprocessing Tools Settings Help
Description

Scale

Time Spans

Geographic Bounds

El Vehicles/Equipment

' On Road Vehicle Equipment

Road Type

,
Pollutants And Processes

J Manage Input Data Sets

B Strategies

/ Alternative Vehicle Fuels &

On-Road Retrofit
Output Emissions Detail

Advanced Performance Features
HH Compute Rate-of-Progress "No Clean Air Act Amendments" Emissions

The Rate-of-Progress Calculation strategy supports users modeling vehicle
emissions for Reasonable Further Progress SIP requirements. It models a
"No Clean Air Act Amendments" scenario by assigning 1993 model year
emission rates to all post 1993 vehicles.

See the MOVES user guide and guidance documents for more details.
icly...
If the user selects "Compute Rate-of-Progress 'No Clean Air Act Amendments'
Emissions, the MOVES model will assign 1993 model year emission rates to all post-1993
vehicles.

Under the Clean Air Act, some State Implementation Plans (SIPs) must include a
demonstration that the state is making "reasonable further progress" in reducing hydrocarbon and
NOx emissions. To compute the rate of progress to this goal, the Act requires calculating
emissions with and without the impact of the Clean Air Act Amendments of 1990. To perform
the highway vehicle portion of these calculations with MOVES, users should use the Rate of
Progress feature. They should also set inspection maintenance programs and fuel programs to
appropriate parameters. For more information, see the MOVES Technical Guidance.

2.2.10 Output
United States Environmental Protection Agency
Page 39

-------
August 2010
                                      MOVES User Guide
         Selecting Output on the Navigation Panel expands to show General Output and Output
 Emissions Detail. Each of these panels allows the user to specify aspects of the output data.

            2.2.10.1 Specifying Database, Time Period, and Units in Output

         Click on the General Output panel to specify the output database, the units, and the
 activity types reported.  The panel has three sub-panels:  Output Database, Units, and Activity.
              Pre Processing Action Post Proc
                              essing Tools Settings Help
              Description

              Scale

              Time Spans

              Geographic Bounds

              Vehicles/Equipment

                 On Road Vehicle Equipmerr

              Road Type

              Pollutants And Processes

              Manage Input Data Sets

              Strategies

                 Alternative Vehicle Fuels &

                 On-Road Retrofit

                 Rate Of Progress

              Output
Mass Units:

Energy Units:

Distance Units:
                 Output Emissions Detail

              Advanced Performance Feature
D Distance Traveled

D Source Hours

Q Source Hours Idling

Q Source Hours Operating

Q Source Hours Parked

G Population

D Starts
                2.2.10.1.1  Output Database

         The first box, Output Database, contains input boxes for the server name and the output
  database name. A blank server box is the default and it indicates that the localhost (the MySQL
  data folder located on the user's computer) is to be used.  Most users should leave this blank.
  The second box contains the name of the MySQL output database where the user desires the
  MOVES output to be written.  The user must select an existing MOVES output database or
  create a new MOVES output database into which the results should be placed. If the output
  database already exists and contains rows within its output tables,  a warning icon is displayed.  A
  new run of the MOVES model will add its results to an existing  MOVES output database, and
  automatically give them the next available MOVES Run identification number. MOVES output
  records in an existing output database cannot be deleted or replaced from within the MOVES
  GUI.
Page 40
                United States Environmental Protection Agency

-------
MOVES User Guide August 2010

A user choosing to create a new MOVES output database must choose a unique name
and may click the "Create Database" button. All new output databases begin with a MOVES
Run identification number of one.

XCaution! The user should never attempt to create a new output database with the same name
as the MOVES default database or of any user-supplied MOVES input databases.

The output database should follow a naming convention to differentiate it from other
databases; typically, using "_out" at the end of the database name is recommended.

2.2.10.1.2 Units

The Units box contains user choices for the mass, energy, and distance units in which the
results will be reported. The choices for mass are kilograms, grams, pounds, or US tons (short
tons). The available energy units are Joules, Kilojoules, or Million BTUs (British Thermal
Units). The available distance units are miles or kilometers. The user may choose only one unit
for each of the three measurement types. The units are reported in the output database in the
MySQL output table "movesrun."

Make sure to choose units of the appropriate magnitude for your RunSpec. For instance,
if the RunSpec is very narrow spatially, temporally, and in terms of vehicle and road
types, then choosing "Tons" as the "Mass Units" may not give you the desired level of
detail.

2.2.10.1.3 Activity

The Activity panel allows users to choose which vehicle activity to report in the
MOVESActivityOutput table.

If "Emission Rates" is selected on the "Scale" panel, "Distance Traveled" and
"Population" will be selected automatically since their values are needed for the rates
calculations.

XCaution! If the calculation type Emission Rates is selected on the Scale panel, the activity
values will represent an intermediate step in the rates calculations rather than the
real activity for that time and place. To reduce file size, use the Aggregation and
Data Handling panel on the Advanced Peformance Features screen to select
"Clear MOVESActivityOutput after rate calculations."

^ NOTE In the MOVESActivityOutput table, population always has month, day & hour keys of
zero (i.e. "doesn't matter") because population is assumed constant in time across an
entire year. This scheme reduces table size, but requires care when filtering results and
when joining to other tables. Also, if you assign some VMT to a road type, but then do
not select that road type in the RunSpec, the population will be lower than it should be.
This is because the missing VMT is not used when calculating population. Users
should model all road types (where VMT is allocated) to ensure proper calculations.
United States Environmental Protection Agency Page 41

-------
August 2010
                     MOVES User Guide
  7 NOTE Activity is generated only when at least one process that uses that activity is chosen on
          the Pollutants/Processes panel.  If the user chooses an activity but does not choose the
          associated process, the MOVESActivityOutput table will not include the desired
          results.

         The following Table 2.2.10.1.3 lists and describes the activities MOVES can output,
 their units, and the processes that generate their information.
Activity TypelD
1
2
3
4
5
6
1
Description
Distance traveled
Source Hours
(population times the
number of hours)
Source Hours Idling
(the number of hours
that combination long
haul trucks spent in
extended idle mode)
Source Hours
Operating (the number
of hours that vehicles
spent operating)
Source Hours Parked
(the number of hours
that vehicles were
parked)
Population (the
number of vehicles —
assumed constant for
each year)
Starts (the number of
engine starts)
Units
Distance
units as set
in a RunSpec
Hours,
regardless of
time unit
aggregation
Hours,
regardless of
time unit
aggregation
Hours,
regardless of
time unit
aggregation
Hours,
regardless of
time unit
aggregation
SourceUseT
ype count
Number of
starts
ProcesselD
1
11, 12, 13
90
1,9,10,11,
12, 13
11, 12, 13
1, 2, 9, 10,
11, 12, 13,
90
2
Notes
Also needed for
proper calculation of
evaporative
emissions when
doing "Rates"
calculations

Offnetwork roads
only

Offnetwork roads
only

Offnetwork roads
only
 Table 2.2.10.1.3

            2.2.10.2 Specifying Emission Distinctions in Output

        Select Output Emissions Detail on the Navigation Panel (after expanding Output) to
 specify distinctions desired in the output data. The Output Emissions Detail Panel consists of
 four sub-panels: Always, for All Vehicle/Equipment Categories, On Road/Off Road, and
 Estimate Uncertainty.
Page 42
United States Environmental Protection Agency

-------
MOVES User Guide
August 2010

HO MOVES - ID 2101066914948040296 | . || 3 || X | 1
File Edit Preprocessing Action Postprocessing lools Settings Help
Description
, Scale
Time Spans
Geographic Bounds
El Vehicles/Equipment
' On Road Vehicle
Road Type
Pollutants And ProcH

Manage Input Data Sel

El / Strategies
t Alternative Vehii
On-Road Retrofit
y Me Of Pr.gr J

B jj Output
' General Output
^^m ^output Emission
Advanced Performanc
^\«^^\ |> :











0Tlme
0 Location




















Hour
COUNTY | f\

•••

0 On Road/Off Road

0 Pollutant
for All Vehicle tquipment Categories
G Model Year

G Fuel Type
G Emission Pr



>cess









G Estimate Uncertainty
Number of iterations:
[;








On Road
G Road Type
G Source Use Type
Gscc
Off Road
G Segment

Gscc
G HP Class
D








G Keep pseutlo randomly sampled input


G Keep output


I oin each Itera1i(




































Ready...






















  7 Note  Selecting detailed output here and using MYSQL  post-processing to aggregate the
          output to the desired level allows the user control over the aggregation level without re-
          running the model.  This is often the best choice for intial investigation of a question
          and smaller runs. However, if a run includes many times,  locations, source types, etc.,
          the user may want to reduce the number of items selected on this screen to avoid
          producing unmanageably large output files and longer post-processing queries.

               2.2.10.2.1  Always

        The Always box at the upper left is a reminder that the output data will always contain
 dimensions for time, location, and pollutant.  The Always box also contains two buttons that
 allow the user to specify the level of output aggregation by time and location level.

        By default, the "Time" button will report the same time level as selected in the Time
 Spans panel. The user may change the time  level in the "Time" button to a value that is equal or
 longer than the Time Aggregate Level specified in the Time Spans panel. For example, if the
 Time Aggregate Level is set to "Hour" in the Time Spans panel, then the "Time" button can be
 set to "Hour", "24-Hour Day", "Portion of Week", "Month", or "Year"

        The "Time" selection requires explanation.  The "24-Hour Day" selection does not select
 a particular day of the week but a kind of day of the  week and the results are for  one day of each
 kind of day requested in the RunSpec (e.g. one weekend day and/or one weekday). Similarly, the
 "Hour" selection will result in hourly output  for each kind of day requested in the RunSpec. In
 the default case where the MOVES input database specifies two kinds of days, reporting by
United States Environmental Protection Agency
   Page 43

-------
August 2010 MOVES User Guide

"Portion of Week" reports weekday results as a total of five weekdays and weekend results as a
total of two weekend days.

^ Note The behavior of the aggregation function of the Time selection may cause unexpected
results. For example, if only two hours of the day are selected in the Time Spans
panel, but "24-Hour Day" is selected in the Output panel, the daily results will only be
the sum of the two selected hours, not all 24. Similarly, selecting only weekdays in the
Time Spans panel, but selecting "Month" in the Output panel will result in a monthly
total that only includes weekdays. See the MOVES Software Design Reference Manual
for more information about how MOVES aggregates output.

By default, the "Location" button will report the same geographic aggregation level as
selected in the Geographic Bounds panel. The user may change the aggregation level in the
"Location" button to a value that is equal to or larger than the level set in the Geographic
Bounds panel. For example, if the Geographic Bounds panel is set to "County", then the
"Location" button can be set to "County", "State", or "Nation".

^ Note The choice of "State" or "Nation" will aggregate results from the areas chosen in the
Geographic Bounds panel. For example, if only two counties from a state are
specified in a RunSpec, the output results for "State" will be the sum of the emissions
from only these two counties.

A "Pollutant" button is not available because MOVES pollutants are always reported
separately in the output. Where aggregation of pollutants is available, the aggregate is listed as a
separate pollutant on the Pollutants And Processes panel. (For example, "Primary Exhaust
PM2.5 - Total.")

2.2.10.2.2 For All Vehicle/Equipment Categories

The dimensions that apply to both on road and off road sources are "Model Year", "Fuel
Type", and "Emission Process". Checking any or all of these items means that the output will
be distinguished by that factor. For example, if "Emission Process" is checked, the output will
be distinguished by the emissions processes selected, such as Running Exhaust, Start Exhaust,
etc.

2.2.10.2.3 On Road/Off Road

MOVES does not include the ability to model Off Road emissions, as yet. Thus, within
the On Road/Off Road only the On Road section is functional. In the On Road box, options
are available to report by "Road Type", "Source Use Type", or Source Classification Code
(SCC)". If none of these options are checked, no vehicle or road classification distinctions will
be made in the output. Instead, the results will be reported as summed across all vehicle and
road classes.

"Source Use Type" and "SCC" are mutually exclusive. Source Use Types are native to
MOVES, so this is the preferred option. MOVES can report by Source Classification Code
(SCC), but this introduces an additional approximation step in the calculations to convert
output by Source Use Type to SCC.

Page 44 United States Environmental Protection Agency

-------
MOVES User Guide August 2010
XCaution! If "Custom Domain" is chosen on the Geographic Bounds panel and output is
distinguished by "SCC", the user must manually populate the
"sccRoadTypeDistribution" table in MySQL and input it as a user-input database in
the Manage Input Data Sets panel. As stated earlier, the default database contains
no default data about custom domains, but this table cannot be edited in the County
Data Manager so it must be provided separately by the user. Additionally, while
there is default information for individual counties, users may want to review the
"sccRoadTypeDistribution" table to determine how the MOVES road types
translate to the SCC roads types for the county of interest.
Several interdependences exist among these items. For example, reporting by SCC
implies that FuelTypes, but not RoadTypes will be distinguished. (The SCC itself includes an
indication of both the fuel type and the roadway classification.)

2.2.10.2.4 Estimate Uncertainty

The Estimate Uncertainty function is not yet available..

2.2.11 Advanced Performance Features

The Advanced Performance Features panel invokes a variety of options. Some will be
use to many users, others require specialized knowledge.

Many of these are features which may be used to diagnose problems with the model
software, or to improve the run time for long model runs by saving and reusing intermediate
results. Use of these features requires knowledge of the detailed software components of the
MOVES program, the inputs they require, and the outputs they produce. Users interested in
these features should review the MOVES Software Design and Reference Manual.
United States Environmental Protection Agency Page 45

-------
August 2010
                                                  MOVES User Guide
       0 MOVES - ID 21010(6914948040296
       File Edit Preprocessing Action Postprocessing  lools Settings Help
             Description

             Sea,*

            ' Time Spans

            ' Geographic Bounds

        B  ' Vehicles/Equipment

               ' On Road Vehicle

            'J Road Type

            ' Pollutants And Proces

             Manage Input Data Set

        El  / Strategies

              / Alternative Vehil

                On-Road Retrofit

               / Rate Of Progres-

        E3  ' Output

               ' General Output
Masterloopable Components
Component
Total Activity Generator (TAG)
uperatino Mode Distiibution i^tTi Crater ounnmq uMD'.-'j
Start Operating Mode Distribution Generator
evaporative Operating Mode Distribution Generator
Tirewear Operating Mode Distribution Generator
Source Bin Distribution Generator (SBDG)
Meteorology Generator
Tank Temperature venerator
Tank Fuel Generator
-uel Effects Generator
Lookup ijppiatinut t'.-ludp Distribution L-pneratoi
^mission Calculators
On-Roaci Retrofit
^roject-Domain Total Activity Generator
Pnniert-Domam upeiatmq Mode Distribution oenetator frunnmq exhaust)
Rate Of Progress Strategy
Don! Execute



















I]
3
3
2






1
1
[I







Save Data










1






































1 1 Create Database
Refresh
Destination User Dataset
G Copy Saved Generator Data
Server:

Database:

Aggregation and Data Handling
Q Do Not Perform Final Aggregation
G Clear MOVESOutput after rate calculations
G Clear MOVESAclrvityOutput afler rale calculations

Custom Input Database
Server:
             Advanced PerfotimiiM
                                                    "^   Create Database
         This panel allows users save intermediate results from various portions of the model and
  to turn off portions of the model code.

         This panel also allows the user to "turn off" final aggregation of MOVES results.
  Selecting the "Do Not Perform Final Aggregation" option can reduce execution time for large
  runs.  When this option is selected, the MOVES  output tables may include rows with duplicate
  key fields.  The results from these rows must then be summed to produce useful output. Use this
  feature with great care.

         When the Emission Rates calculation type is selected on the Scale panel, the user may
  choose to "Clear MOVESOutput after rate calculations" and "Clear
  MOVESActivityOutput after rate calculations."  These options are recommended because
  the tables they affect may be quite large, and the values the tables hold represent only an
  intermediate step in the rates calculations rather than the real activity for that time and place.

         Finally, this panel includes a sub-panel where the user can specify an input database to be
  used instead of the MOVES default input database.  Most users will not need this option.
Page 46
                           United States Environmental Protection Agency

-------
MOVES User Guide
August 2010
2.3 Main Menu Bar

The Main Menu Bar runs across the top of the screen and contains eight drop down
menus: File, Edit, Pre Processing, Action, Post Processing, Tools, Settings, and Help
Menus can be opened by either clicking on the menu command, or by using a keyboard
combination, defined as ALT and the underlined letter of the menu command (e.g., ALT + F for
the File menu, ALT + R for the Pre Processing menu).

2.3.1 File

File provides a drop-down menu typical of those used when manipulating documents.
Click File to open the drop down menu and then on a menu item to select New, Open, Close,
Save, Save As, Print, Exit, or to choose to open recently opened files. Use the File commands
to create, load, and save RunSpec objects. The Example RunSpec may be opened from this
menu (see Section 1.4 for details). MOVES provides the option to execute file manipulation
commands using keyboard combinations as well; for example, the File Open procedure can be
initiated by selecting the Alt and O keys simultaneously when the File drop down box is opened.
Key sequences required to execute the file manipulation commands are displayed using the
"mouse hover" feature while placing the cursor over the desired command. Note that the Print
command prints the XML version of the RunSpec, not a screen shot.
MOVES - C:\Epa\Moves\MOVESGHGSource\MOVES2009Example.rnrs - ID 4!
File Edit Pre Processing Action Post Processing Tools Settings Help
[# New...

-------
August 2010
MOVES User Guide
File Edit Pre Processing Action Post Processing Tools Settings Help
2.3.3 Pre Processing

The Pre Processing menu contains four active options, IM Importer, Data Importer,
County Data Manager, and Project Domain Manager. Each option enables the user to access
importers for individual tables in order to create user-supplied databases for direct entry of data
into MOVES. The Project Domain Manager, in particular, requires the user to provide
virtually all of the data required to model a specific project.
MOVES - ID 15597916264946779
File Edit Pre Processing Action Pa
Execute Data Importer.,
I.M Importer
Data Importer
County Data Manager
Project Data Manager
The County Data Manager (CDM) and the Project Data Manager (PDM)are means
by which the user can define the county-specific or project-specific data required if the user
selects County Domain/Scale or Project Domain/Scale when defining the Scale parameter of
the RunSpec. Neither the County Data Manager nor the Project Data Manager menu options
will be enabled unless the user has made the County Domain/Scale or Project Domain/Scale
choice. The I/M Importer also provides users with the ability to define county-specifc data by
allowing the user to edit the inspection and maintenance programs in an area. The I/M
Importer can be used at any Scale.

The County Data Manager and Project Data Manager are designed to specify all the
inputs required for certain kinds of runs and the I/M importer only allows I/M programs to be
modified. The Data Importer, on the other hand, allows the user to select individual importers
"ala carte" from the importer menu.

XCaution! All tabs/fields in the County Data Manager and Project Data Manager should be
completed to ensure the output generated is correct. In some cases, a RunSpec may
execute even though all the tabs in the County Data Manager or Project Data
Manager were not completed; however, the results from such RunSpecs may
Page 48
United States Environmental Protection Agency
-------
MOVES User Guide
August 2010
populate the incomplete tabs with default data, which may not be appropriate due to
how MOVES generates, calculates, and allocates various data.

The user does not have to specify a database containing county or project data that was
created with the County Data Manager or Project Data Manager in the Manage Input
Data Sets panel. These databases only have to be selected in the Domain Input Database
pane of the Geographic Bounds panel. However, databases created with the Data
Importer or I/M Importer should be input using the Manage Input Data Sets panel

From the user perspective, there are three major differences between working with
importers through the Data Importer and working with the same importers through the County
Data Manager and the Project Data Manager (leaving the I/M Importer aside, for the
moment). First, as "domain managers" the County Data Manager and Project Data Manager
indicate whether the user has imported all of the data that is needed to establish a new domain.
To this end, the County Data Manager and the Project Data Manager will identify the
parameters where data is needed by displaying red "x-circles" on the importer tabs (see
screenshot below). Green checks indicate where data has been properly and completely
imported. The Data Importer does not display such information.
El MOVES County Data Manager
@ Source Type Population [ @ Vehicle Type VMT | Q I/M Programs | Tools
@ Fuel Supply
Q Fuel Formulation
@ Meteorology Data
Q Road Type Distribution
RunSpec Summary
Database
@ Age Distribution
U Average Speed Distribution
Select or create a database to hold the imported data.
Server: localhost
Database:
\T\\ Create Database
Refresh
Clear All Imported Data
Database
Done
Secondly, because of the level of detail required and the structure of the underlying data
tables, the County Data Manager restricts the RunSpec to a single county and single calendar
year, and the Project Data Manager restricts the RunSpec to a single hour, daytype, month and
county. The Data Importer can be used with any RunSpec.
United States Environmental Protection Agency
Page 49
-------
August 2010
MOVES User Guide
Thirdly, the Data Importer is generally used to import data for a RunSpec at the
National Domain/Scale. Therefore, when importing Population or Vehicle Type VMT at the
National Domain/Scale, these inputs should be national values even if only a small number of
counties are selected. MOVES will use the default allocation factors for the counties selected in
the RunSpec to apportion data to each county.

This user guide will use the Data Importer screens to explain functionality of individual
importers, including the I/M Importer.. Specific instructions associated with using the County
Data Manager or the Project Data Manager to establish a new domain are included where
appropriate.
When the user selects one of the data manager options, the manager window will open.
This window contains several tabs to aid the user in defining the data source, destination, and
database structure for the imported data. Importer tabs provide templates for collecting user-
provided data.

2.3.3.1 Database