1

An Introduction to Draft 

MOVES2009

FHWA Resource Center

EPA Office of Transportation and Air Quality

EPA-420-B-09-026
2

2

Course Outline

z MOVES overview

– What is Draft MOVES2009?

– Comparison to MOBILE6.2

z Making the transition to MOVES

z How does MOVES work?

z Running MOVES

– Creating a RunSpec for a simple national scale run

– Looking at MOVES output

– Basics of MySQL

– Using the County Data Manager to input local data

– Modeling Custom Domains

– Using the Project Level Data Manager

z Tips and tricks 
3

MOVES

z MOtor Vehicle Emission Simulator

z State-of-the-art modeling framework

z Will replace current models (MOBILE & NONROAD) 

and expand capabilities 

z Designed to allow easier incorporation of large 

amounts of in-use data from a variety of sources

– MOBILE structure limited ability to incorporate new emissions 

data
4

Why is EPA developing MOVES?

z CAA requires EPA to regularly update emission 

factors and emission factor models

z FORTRAN code used in MOBILE6.2 is obsolete and 

increasingly difficult to maintain

z Modular database structure more modern, easier to 

update with new emissions, fleet and activity data

z MOVES will eventually incorporate functions of the 

current NONROAD model, providing a single, 

comprehensive modeling system
5

Why is EPA developing MOVES?

z National Research Council 2000 review of EPA’s 

mobile source modeling program included several 

recommendations that are addressed by MOVES:

– Support for smaller-scale analyses (project-level analysis)

– Improved characterization of high emitters, heavy-duty 

vehicles and nonroad sources

– Improved characterization of particulate matter and toxics

– Improved model evaluation and uncertainty analysis

– Improved ability to interface with other models
6

How is MOVES better 

than MOBILE?
7

7

MOBILE6.2 Uses Text Input and Output Files
8

8

MOVES Has a Graphical User Interface

(MOVES can also be executed from a command line interface without

use of the GUI, for batch or unattended operation)
9

New Software Structure

z MOBILE6.2

– Written in Fortran, runs in DOS

– Many data elements hard-coded (difficult to modify/update)

z MOVES

– Java/MySQL software

– Data elements stored in database tables (easy to 

modify/update)
10

More Flexibility

z MOBILE6.2

– Gram/mile emission factors

– Fixed output formats

z MOVES

– Gram/mile emissions factors (grams/time for some processes)

– Total emissions: inventories for specific areas and time 

periods

– Easily customizable output (many levels of 

aggregation/disaggregation possible)
11

Multiple Geographic Scales

z MOBILE6.2

– Emissions rates based on regional-scale trip patterns (no 

specific geographic area)

z MOVES 

– Emissions inventories from national level to county level to 

project level

– Lookup table option for emission rates
12

Modal Emissions

z MOBILE6.2 rates based on aggregate driving 

cycles

z MOVES rates based on “operating modes”

– Second-by-second activity is captured by the model 

(does not need to be provided by users, but can be)
13

13

MOVES Uses New Data

9 Activity

– In-use vehicle trip patterns

– Rural area activity data

9 Light-duty vehicles

– Assessed millions of light-duty vehicles

– Landmark gasoline PM study (Kansas City)

– Remote Sensing Data

9 Heavy-duty vehicles

– More than 100 in-use vehicles from WVU

– New on-board real-world driving data from over 300 

vehicles
14

Energy and GHG analysis

z MOBILE6.2 had simplistic fuel economy and CO2 

calculations

z MOVES is designed from the ground up as an 

energy consumption model

z Also estimates greenhouse gases: CO2, methane, 

nitrous oxide, and CO2 equivalents of these

z While the energy and emissions rates are still 

officially “draft”, this is the best available tool for 

this type of analysis
15

How Do Emissions 

Estimates of Draft 

MOVES2009 Compare to 

MOBILE6.2?
16

Early Draft MOVES Results

z Data collected since MOBILE6 released drives differences 

between MOVES and MOBILE6

z National trends

– HC and CO emissions similar or lower than MOBILE6.2

– Total NOx emissions higher than MOBILE6.2

– Total PM emissions substantially higher than MOBILE6.2

z Local results may vary

– Local fleet mix, fuels, activity are important

– Temperature drives PM emissions

z For attainment analysis, relative change in emissions 

between base year and attainment year is more important 

than absolute emissions
17

Why are emissions different?

z New car and light truck emissions data

z New heavy truck emissions data

z New emissions processes not included in 

MOBILE6

z Updated fuel and vehicle standards
18

Significant new data in MOVES

z Updated emission rates

– Test results on millions of vehicles considered for MOVES

z Passenger Cars & Trucks

z Heavy Duty Trucks

z New fleet & activity defaults

– National defaults:

z Vehicle fleet from state registration data, VIUS

z Vehicle Miles Traveled (VMT) from HPMS

z Driving patterns from instrumented vehicle surveys

– For local modeling, local data is likely to be most accurate & 

up-to-date
19

Extensive analysis of Car & Light 

Truck emissions

z HC/CO/NOx rates based on ~ 70,000 vehicles 

randomly selected from Arizona IM program

– Able to tease out emissions from I/M and non I/M areas

z Checked against data from multiple sources

– I/M data from Illinois, New York, Missouri and Colorado

– Roadside remote sensing data from several cities

– Kansas City Study

z Extended to newest technology vehicles using 

compliance data

– In-use emissions data manufacturers required to collect

– About 2,000 laboratory tests per year
20

Gasoline PM a major focus

z Landmark study conducted in Kansas City 2004-05 

to address need for improved gas PM estimates

– Collaboration between EPA, DOE, DOT, States, Auto/Oils 

z 496 gasoline light-duty cars and trucks tested 

– Model Years 1968-2005

z Summer and winter testing

– ~ half of the vehicles tested each season @ ambient temps

– 43 vehicles tested in both winter and summer

z More information at 

http://www.epa.gov/otaq/emission-factors-research/
21

What we’ve learned about Car & 

Light Truck emissions

z New standards have been successful in reducing 

deterioration of HC/CO/NOx emissions

z On-Board Diagnostic (OBD) systems are a 

contributing factor to lower deterioration

– Owner response to repair identified malfunctions is better than 

MOBILE6 projected, particularly in non-I/M areas

z Gas PM emissions are much higher than MOBILE6 

projected 

– Higher in-use deterioration

– Significant increase at cold temperatures
22

Arizona I/M NOx data by Model Year and Age

drop in deterioration 

with Tier 1s

Flattening trend
23

Heavy Duty Diesel emissions 

updated based on real world data

z MOBILE6 relied on certification data

– Engine tests only

z Much research on in-use trucks since MOBILE6

– CRC E-55

z 75 trucks on chassis dynamometer 

z Only real-time PM data of it’s kind

– On-Board Measurement: ~350 trucks on road

z Provided most robust assessment of NOx emissions available

z Extended idle, crankcase, starts, tampering & malmaintenance factored in (not in MOBILE6)
24

What we’ve learned about Heavy 

Duty Diesel emissions

z NOx

– In-use emissions moderately higher than MOBILE6 projected 

– Extended idle (hoteling) emissions are significant

z And projected to grow as percent of NOx inventory 

z PM

– Significant speed effect

z MOBILE6 did not model any speed impacts

z Large increase in emissions at lower speeds vs. MOBILE6

– Crankcase emissions significant
25

Analysis of Local Area Impacts

z Did preliminary comparison of MOVES and 

MOBILE6 using surrogate local data to represent 3 

different urban counties

– Local data very limited, may not be consistent with what states 

will actually use

z Local data varied by:

– Fleet age distribution

– Fraction of light and heavy duty VMT

– Local fuel specifications

– Meteorology

– Other input factors
26

NOx

• I/M program data shows MOBILE6 

underestimated NOx emissions from 

light trucks

• On-road data on heavy trucks shows 

higher emissions than MOBILE6 

estimated from cert data

• Extended idle emissions become 

significant share of heavy-duty 

inventory in future

City B - NOx

0

5000

10000

15000

20000

25000

30000

35000

40000

2008 2015 2020

Annual Tons

MOVES

MOVES

MOVES

M6

M6

M6

HD

HD

LD LD

Extended 

Idle=34%

City A - NOx

0

10000

20000

30000

40000

50000

60000

70000

80000

90000

2008 2015 2020

Annual Tons

MOVES

MOVES

MOVES

M6

M6

M6

HD

HD

LD LD

City C - NOx

0

5000

10000

15000

20000

25000

2008 2015 2020

Annual Tons

MOVES

MOVES

MOVES

M6

M6

M6

HD

HD

LD LD
27

HC

• I/M program data shows MOBILE6 

overestimated HC emissions from 

newer technology cars 

• Evaporative emissions on newer 

technology vehicles very low; reevaluating leak emissions for final 

model

City B - HC

0

2000

4000

6000

8000

10000

12000

14000

16000

2008 2015 2020

Annual Tons

MOVES

MOVES

MOVES

M6

M6

M6

HD HD

LD LD

City A - HC

0

10000

20000

30000

40000

50000

60000

2008 2015 2020

Annual Tons

M6

M6 M6

MOVES

MOVES

MOVES

HD

HD

LD LD

City C - HC

0

2000

4000

6000

8000

10000

12000

2008 2015 2020

Annual Tons

MOVES

MOVES

MOVES M6

M6

M6

LD LD

HD

HD
28

PM2.5

• Kansas City program found high gas PM 

emissions esp. at cold temps

• New data on heavy trucks shows higher 

deterioration than MOBILE6

• MOVES accounts for impact of vehicle 

speed – MOBILE did not 

City B - PM2.5

0

300

600

900

1200

1500

2008 2015 2020

Annual Tons

MOVE

MOVE

MOVES

M6 M6

M6

HD

HD

LD LD

City A - PM2.5

0

1000

2000

3000

4000

2008 2015 2020

Annual Tons

MOVES

MOVES

MOVES

M6 M6

M6

HD

HD

LD LD

City C - PM2.5

0

150

300

450

600

2008 2015 2020

Annual Tons

MOVE

MOVE

MOVE

M6 M6

M6

HD

HD

LD LD
29

Percent Reduction in On-Road 

Emissions 

2008 to 2015

MOVES MOBILE6 MOVES MOBILE6 MOVES MOBILE6

HC 50% 50% 39% 32% 38% 31%

NOx 54% 56% 40% 52% 36% 53%

PM2.5 57% 40% 52% 40% 38% 23%

City A City B City C
30

What It Means

z Higher NOx and PM emissions mean mobile sources have 

bigger role in attainment

z Percent reduction from base year is key to attainment 

analysis

– PM2.5 shows higher overall emissions and higher % reductions

z Effect on attainment demonstrations could be positive

– NOx shows higher overall emissions but lower % reduction

z Harder to show attainment

z Future NOx control measures will have a bigger impact

z States may need to redo some motor vehicle emissions 

budgets to meet conformity requirements with MOVES
31

I/M Effects In MOVES

z Benefits are comparable to MOBILE6 now, 

but will shrink over time.

– Conservative M6 OBD assumptions not supported 

by data

z CRC did comprehensive survey of MIL response in non-I/M 

areas

z Found high response even after warranty

– Our analysis of I/M program data confirms that OBD 

works
32

Making the Transition to 

MOVES
33

MOVES Schedule

z January 2005

– MOVES2004 released

z Includes energy consumption, greenhouse gases

z May 2007

– MOVES Demo released

z Basic structure of MOVES without criteria pollutant emission factors

z April 2009

– Release of Draft MOVES2009

z Adds draft criteria pollutant emission factors

z End of 2009

– Planned release of official MOVES2009

z Final onroad criteria pollutant model

z 2009+

– Begin adding nonroad emissions to MOVES
34

Draft MOVES2009 – New 

Capabilities

z First release of MOVES that includes criteria 

pollutant emissions and toxics

z Adds more features to simplify regional and 

project-level analysis for SIPs and conformity

z County Data Manager

z Project Level Data Manager

z Data Importers
35

Draft MOVES2009 - Limitations

z Draft model

– No official use requiring Draft MOVES2009

– Cannot be used for SIPs or conformity analyses

z Does not include all data or features planned for 

official MOVES2009 and has known and unknown 

bugs, for example:

– Motorcycle emissions not yet included

– Plan to add more flexibility for VMT input

– Known bugs in refueling vapor and spillage processes and 

project level scale
36

Why release Draft MOVES2009?

z Help us identify problems with MOVES

z Provide feedback on whether MOVES meets user 

needs

– What we can do to improve it?

z Identify guidance issues

z Start learning MOVES now to be ready to use final 

MOVES2009 as soon as it is released

– Use MOVES2009 for SIPs due in 2012 and 2013
37

Official MOVES2009

z Official MOVES2009 planned for release at the end 

of 2009

z Will be official version of MOVES for on-road 

vehicles outside of California

z Use will be required for:

– State Implementation Plans (SIPs)

– Regional conformity analysis

z Following regional conformity grace period of 3 to 24 months

– Project level conformity analysis for PM and CO

z Following project level conformity grace period 

z NEPA analysis (e.g., air toxics)
38

Easing the Transition to MOVES

z Improved handling of different domain sizes

– Added GUI for nonattainment area and project level analysis to 

allow users to specify local inputs

z Developed data importers which:

– Ease conversion of MOBILE inputs to MOVES inputs

z More to come

– Allow input of data as text files

z Writing future guidance documents

– Technical guidance will address when and what type of local 

input is needed
39

39

Levels of Analysis in MOVES

z MOVES is designed to work at macro, meso, and 

micro scales

z These translate into different geographic domains: 

– National 

– Nonattainment Area or County

– Project

z Added GUI to Draft MOVES2009 for local inputs for 

nonattainment area and project level analysis
40

Default County Level Data in Draft 

MOVES2009

z National domain will produce results for the nation, 

specific states, or specific counties

– Current default county level data in MOVES is a mix of 

national defaults, national data disaggregated to county level 

with adjustment factors, and local data from various sources

– Users cannot rely on default county level data to be accurate 

or up to date and it should not be used for SIPs or conformity 

analysis

z For SIPs and regional conformity analysis, users 

should select the county domain and enter local 

data using the County Data Manager
41

What Are MOVES Data Importers?

z Software interfaces that can create alternate databases, tables,

and data records for use by MOVES

z Draft MOVES2009 includes data importers to simplify creation 

of local input files

z Advantages

– Do not require knowledge of database commands and syntax

– Can assure the updates are made only to the appropriate tables

– Can require complete information from users, preventing data 

gaps

– Can include some error checks

– Can be designed to convert data from MOBILE6 to MOVES format
42

Future Guidance Documents

z EPA expects to release several guidance 

documents that will help with the transition for 

final MOVES

– MOVES Technical Guidance for SIPs and conformity

– Project Level Conformity Guidance for PM

– MOVES SIP and Conformity Policy Guidance

z Will release draft guidance for comment sometime 

after release of Draft MOVES2009

z Final guidance documents will be available when 

Official MOVES2009 is released
43

43

MOVES Technical Guidance for 

SIPs and Conformity

z Answers these questions:

– When can model defaults be used?

– When is local information needed?

– What are acceptable sources of local information?

z See MOBILE6.2 Technical Guidance for examples 

of past answers to these questions:

– Registration (age) distribution

– Mileage accumulation
44

Project Level Guidance for PM

z How to do project level analysis for PM2.5 and 

PM10 with MOVES for conformity

z Similar to Technical Guidance, but focused on 

specific needs for project level analysis

z Will also address how to use air quality models for 

project level analysis
45

MOVES SIP and Conformity Policy 

Guidance

z Answers these questions:

– When should MOVES be used for development of new SIPs?

– When should MOVES be used for new conformity 

determinations?

z Conformity grace period can be 3 to 24 months

– Any other general policy questions for the transition from 

MOBILE to MOVES

z Actual date that MOVES becomes official for SIP 

and conformity purposes is based on Federal 

Register notice announcing availability
46

MOVES Documentation
47

47

MOVES Documentation

z User Guide

z Software Design/Reference Manual

z Technical documentation

z Presentations and summaries 

z Guidance

z Other documents

MOVES documentation takes many forms.
48

MOVES User Guide

z The MOVES User Guide describes:

– Installation instructions

– The features of the graphical user interface (GUI)

– Instructions on how to access each feature

– Step-by-step example run

– Accessing results using MS Access

– Running MOVES in a batch mode
49

MOVES Software Design and Reference 

Manual

z The Software Design and Reference Manual 

(SDRM) describes:

– The hardware and software requirements

– Software design components

– Overview of processing, data and control flow

– Functional design:

z Generators (process input data)

z Calculators (generate results)

z Aggregators (summarize input and outputs)

– Input and output database tables and design
50

MOVES Database

z MOVES database documentation is included when 

MOVES is installed

z The documentation is located in the “ReadMe”

directory of the MOVES MySQL database folder

z Documents include:

– Table and field descriptions with units

– Table relationship charts

– Database quality checks
51

Technical Reports

z MOVES technical reports describe the 

development of:

– Activity algorithms and default data

– Meteorological algorithms and default data

– Emission rate algorithms and default data

z These reports address the sources of the data 

used by MOVES

z New reports are written when the algorithms or the 

default data are updated
52

MOVES Presentations

z Presentations (such as this one) are made 

available on the MOVES web site

z Presentations can provide a summarized version of 

the information in the more detailed documentation

z Presentations often contain examples that were not 

included in the original detailed documentation
53

Other MOVES Documents

z The MOVES web site contains other documents 

that may be of interest to MOVES users:

– Physical Emission Rate Estimator (PERE)

– MOVES Design and Emissions Analysis Plans

– Federal Advisory Committee Act (FACA) Modeling Workgroup 

materials

– MOVES Training materials

– Validation results
54

How Does MOVES Work?
55

Master – Worker Structure
56

56

Geography and Time in MOVES

9 Modeling domain is the entire U.S.

– 50 States plus (DC, Puerto Rico, & Virgin Islands)

– 3222 Political subdivisions (counties as of CY 1999)

9 Calendar years (1990, 1999-2050)

9 12 months of the year

9 Week days and weekend days

9 24 hours of the day
57

57

Emission Processes

9 Running Exhaust

9 Start Exhaust

9 Extended Idle

9 Evaporative Processes

– Permeation, Vapor Venting, Leaks, Refueling 

Displacement, Refueling Spillage

9 Crankcase

9 Tire Wear

9 Brake Wear

9 Well-To-Pump (energy only)
58

58

MOVES Source Types

(vs. HPMS Vehicle Types)

HPMS 

Vehicle Type 

MOVES2004 & HVI Demo

 SourceType 

Motorcycle Motorcycle 

Passenger Car Passenger Car 

Other 4-tire, 2 

axle 

Passenger Truck 

Light Commercial Truck 

Bus Intercity Bus 

Transit Bus 

School Bus 

Single Unit Truck Refuse Trucks 

Short-haul Single Unit 

Long-haul Single Unit 

Motorhomes 

Combination 

Truck 

Short-haul Combination 

Long-haul Combination 

Sub-categories (like 

refuse trucks and 

motorhomes) will be 

addressed in guidance; 

EPA does not expect 

areas to have local data 

for all subcategories.
59

59

Road Types

9 For running emissions, county-level VMT 

is distributed to four road types:

 Rural Restricted Access (freeways and Interstates), 

 Rural Unrestricted Access, 

 Urban Restricted Access (freeways and Interstates), 

 Urban Unrestricted Access

z A fifth road type, “off-network”, is 

included to capture start, evaporative 

and extended idle emissions

– This is not the same as “off-network” vehicle 

activity in the travel modeling world.
60

60

Vehicle Ages

9 Emission rates can vary by age as well as 

model year; activity also varies by age

9 Vehicles 0-29 & 30+ years old modeled

9 Age groups used for emissions calculations

– 0 to 3 years old 

– 4 or 5 years old 

– 6 or 7 years old 

– 8 or 9 years old 

– 10 to 14 years old 

– 15 to 19 years old 

– 20 or more years old
61

Emissions by Source, Age, Mode
62

How MOVES handles vehicle 

activity - Definitions

z Vehicle Specific Power (VSP) – a measure of the 

energy the vehicle is using at a moment in time

– Affected by acceleration, road grade, resistance, etc.

z Operating Mode – what the vehicle is doing, i.e., 

accelerating, braking, cruising, idling

– Vehicles use different VSP in different operating modes

– MOVES defines 23 operating mode bins – combinations of 

speed and VSP for different running conditions plus additional 

operating modes for starts and evaporative emissions

z Drive Cycle – a second-by-second description of 

vehicle activity over time, typically including 

multiple operating modes
63

63

MOVES: Operating Mode Bins

9 Division of total activity into categories that 

differentiate emissions

9 Defined by speed and Vehicle Specific Power (VSP) 

for running emissions

9 There will be additional operating mode 

distributions for start and evaporative emissions in 

MOVES2009
64

64

Modal “Binning” Approach

9 Any driving pattern can be modeled

– Adds major flexibility compared to MOBILE

9 Allows direct use of data from many sources

9 Provides common emission rates for all scales

9 Independent validation has shown good results 

even for macroscale application
65

Running Operating Modes in 

MOVES

z MOVES uses second-by-second emissions data 

categorized in operating mode bins based on 

combination of speed and VSP

z MOVES includes default operating mode 

distributions based on typical driving cycles

– Different road types in MOVES have different default operating 

mode distributions

z Users can create other operating mode 

distributions based on other driving cycles

– Unlike MOBILE, any driving pattern can be modeled in 

MOVES
66

Operating Mode Bins

1-25 25-50 50 +

30 + 16 30 40

27-30

24-27 29 39

21-24

18-21

15-18

12-15 27

9-12 15 25

6-9 14 24 35

3-6 13 23

0-3 12 22 33

< 0 11 21

VSP Class (kW/tonne)

Speed Class (mph)

28 38

37

PLUS

One mode each for idle 

(Bin 0), 

and deceleration/braking 

(Bin 1)

------------------------

Gives a total of

23 opModes
67

HC Emission Rates By Bin

Source Bin: LDV Gasoline / 1996 MY 

0

1

10

100

braking

idle

<

0

0-3

3-6

6-9

9-12

> 12

<

0

0-3

3-6

6-9

9-12

12-18

18-24

24-30

>30

<

6

6-12

12-18

18-24

24-30

>30

VSP (KW/tonne)

HC Mean Emission Rate (g/hr)

0-3 year old 4-5 year old

< 25 mph 25 - 50 mph > 50 mph
68

Distribu tion of T ime by Mode

0%

10%

20%

30%

Brak ing

Idling

<0

0-33-66-9

9-12

>1 2

<0

0-3

3-6

6-9

9-12

12-1818-24

24-30

>3 0

<6

6-12

12-18

18-24

24-30

>3 0

VSP/Spe e d Bin

Percent of Time

Rural Highway Urban Non-Highway

< 25 mph 25-50 mph > 50 mph
69

New Analysis Opportunities

z Modal emission structure allows calculation of “Projectlevel” emission changes

– Changes in operating mode distribution Æ changes in emissions

z Includes an “importer” to help users input project-specific 

information on driving activity

– Users can enter operating mode distribution or driving pattern by link

z Areas will want tools to estimate how changing road design 

affects operating modes

– Adding lanes?

– Synchronizing signals?

– Replacing stop signs with rotaries?

z Creates need to better characterize driving patterns -

MOVES defaults may not characterize local patterns, esp project level
70

70

MOVES Databases

z MOVES stores information in MySQL databases

z The Draft MOVES2009 default database has 119 

different tables that store

– Lookup/reference information

– Conversion/adjustment factors

– Emissions data

– Activity data

z MOVES also uses databases to store intermediate 

results and final output
71

71

MOVES Databases

9 Input Databases (default or user-created)

− Default Input Database

− User Input Database(s) (optional-MOVES will run with just 

defaults for the National Scale)

9 Execution Database (created by MOVES)

− Resolves differences between the user input and default 

data

− Contain information needed for a particular run

− Temporary storage for intermediate results

− Resources for new modeling applications

9 Output Database (created by user)

9 Run results

9 Run diagnostics and documentation
72

72

Output

z Post-processing scripts

z MOVES Summary Reports

z Exporting MOVES output to EXCEL

z MySQL can also be used to summarize output
73

Errata Sheet

z Default vehicle miles traveled (VMT) projections may not match 

the VMT projections used in other EPA models (such and the 

National Mobile Inventory Model, NMIM).

z There will be no output of Benzene, Ethanol, MTBE, Naphthalene 

or Methane for the Refueling Vapor or Refueling Spillage loss 

processes, even though there are check boxes for these pollutants 

in the Pollutants and Processes panel.

z When you execute MOVES, you get the pop-up window that 

allows you to cancel. However, if you instead hit the X in the 

top corner of the box, the program will execute. The normal 

response should be to cancel the run.

z There will be no output of Methane for Evaporative Vapor, 

Evaporative Permeation or Evaporative Leak losses, even though 

there are check boxes for these processes for Methane in the 

Pollutants and Processes panel.
74

Errata Sheet

z There are no options to get non-methane hydrocarbon, non-methane 

organic gases, total organic gases or volatile organic compound 

speciation of total gaseous hydrocarbons or options for methane, nitrous 

oxide, benzene, ethanol, MTBE, naphthalene, 1,3-butadiene, 

formaldehyde, acetaldehyde or acrolein for the crankcase running, 

crankcase start or crankcase extended idle processes.

z There are no options to get non-methane hydrocarbon, non-methane 

organic gases, total organic gases or volatile organic compound 

speciation of total gaseous hydrocarbons or options for methane or 

nitrous oxide for the extended idle process.

z The sulfate particulate (PM10 and PM2.5) results from the Extended 

Idle Exhaust process are not correct. This will also cause the 

Primary Exhaust Particulate Total results (PM10 and PM2.5) for this 

process to be incorrect.

z When using the Project Level scale, the Extended Idle Exhaust 

process will only produce results for Total Energy Consumption. 
75

Errata Sheet

z In the Time Spans panel, if you choose the Time Aggregation 

Level Year, the panel will still allow you to choose Months, Days 

and Hours. Of course, since you want a total year, selecting 

anything other than all months, days and hours will cause 

problems. If you choose the Time Aggregation Level Year, you 

must select all months, days and hours.

z Similarly, if you choose the Time Aggregation Level Month, you 

must select all days and hours. If you choose the Time 

Aggregation Level Day, you must select all hours.

z When making a retrofit parameter file for importing for the On 

Road Retrofit Strategies panel, you must not use the PollutantID, 

ProcessID, FuelTypeID or SourceTypeID numbers. You must use 

the text names for these parameters.
76

Errata Sheet

z This version of MOVES does not include criteria pollutant or 

air toxic emission factors for motorcycles. Composite fleet 

emission rates of criteria pollutants or air toxics that are intended 

to include motorcycle emissions will not properly reflect their 

contribution.

z The Well-to-Pump emission process in this version of MOVES has 

not been updated and will not produce appropriate emission 

results. Users should not select Well-to-Pump process.

z The emission results for non-methane hydrocarbon, non-methane 

organic gases, total organic gases or volatile organic compound 

speciation of total gaseous hydrocarbons from Refueling Vapor 

and Refueling Spillage losses are not correct. Do not select these 

pollutants when including refueling emissions.
77

Errata Sheet

z The option to Manage Input Datasets or the Pre-Processing Data 

Importer option does not work properly in some circumstances. 

We are scoping the problem.

z The Calculation Type of Emission Rates on the Scale panel 

will produce emission rates only for the Exhaust Running 

process.

z If you select only the brake wear and tire wear toggle boxes for

PM, the Distance Traveled toggle box will be inaccessible. You 

will need to select another pollutant in the Running process in 

order to obtain vehicle miles traveled information along with brake 

wear and tire wear emissions 
78

Next Steps
79

What Should You Do Now?

z Update computer hardware

– Dual-core processor (faster is better)

– At least 1 GB memory (more is better)

– At least 40 GB storage (more is better, output files can be 

very large )

– Consider setting up a distributive network (specs of 

“master” computer are key)

– Windows XP or 32-bit Vista

z Current version of MySQL does not work on 64-bit Vista
80

What Should You Do Now?

z Build staff expertise in relational databases and 

MYSQL

– Not needed for simple runs

– Some basic knowledge gives users flexibility to customize 

outputs and view inputs

– In-house expert would be helpful for more advanced 

analysis

z Subscribe to MOBILENEWS email list for MOVES 

updates

http://www.epa.gov/otaq/models/mobilelist.htm
81

After Draft MOVES2009

z A lot will happen in the time between Draft 

MOVES2009 and Official MOVES 2009

– Give in-depth training

– Gather feedback from users during comment period

– Continue to improve usability and make any other necessary 

changes to MOVES

– Prepare MOVES guidance documents

z The more feedback you provide on Draft 

MOVES2009, the better Official MOVES2009 will be

– Please plan to begin testing and commenting on Draft 

MOVES2009 as soon as it is released
82

Feedback

z We need your comments and ideas

– Does MOVES meet your needs?

– Did you find errors in MOVES? 

z Official Comment Period:

– Begins when Draft MOVES2009 is released

– Comments are most effective when obtained early

z We are interested in your ideas to make MOVES 

better meet your needs

z Best way to provide comments:

– Send an email to: mobile@epa.gov
83

Visit the MOVES website:

http://www.epa.gov/otaq/ngm.htm

z Software, technical documentation, conference and meeting 

presentations, and other helpful background materials