# APPENDIX D0

The Pittsburgh

- Beaver Valley Nonattainment Area for the

1997 Annual and 2006 24

- Hour PM2.5 NAAQS:

Emissions Inventory Using MOVES2010a

Technical Support Document

Mobile Source Highway Emissions Inventory

Executive Summary

Bureau of Air Quality

Department of Environmental Protection

### [ This page intentionally left blank

. ]

# APPENDIX D

The Pittsburgh

- Beaver Valley Nonattainment Area

f or t he 1997 Annual and 2006 24

- Hour PM 2.5 

# NAAQS :

Emissions Inventor y Using MOVES2010a

Technical Support Document

Mobile Source Highway Emissions Inventory

Executive Summary

June 20 1 4 Prepared for:

Mobile Sources Section, Bureau of Air Quality

Pennsylvania Department of Environmental Protection

PO Box 8468

Harrisburg, PA 17105

- 8468

Prepared by:

Michael Baker, Jr., Inc.

1304 Concourse Drive

Linthicum, MD 21090

410

- 689

- 3400

### Pittsburgh

- Beaver Valley Nonattainment Area :

Mobile Source Emissions Inventory

Executive Summary

June 20 1 4



# Exhibit of Contents

SUMMARY

................................ ................................ ................................ ................................ ................................ .. 1

R EVISED E MISSIONS I NVENTORY

................................ ................................ ................................ ............................... 2

A NALYSIS M ETHODOLOGY

................................ ................................ ................................ ................................ ........ 3

DATA SOURCES AND ANA LYSIS TOOLS

................................ ................................ ................................ ........... 5

A NALYSIS T OOLS

................................ ................................ ................................ ................................ ...................... 5

T RAFFIC D ATA S OURCE /F LEET D ATA I NPUTS

................................ ................................ ................................ ........... 6

T RAFFIC G ROWTH A SSUMPTIONS

................................ ................................ ................................ .............................. 8

V EHICLE P OPULATION G ROWTH A SSUMPTIONS

................................ ................................ ................................ ........ 9

I/M AND F UEL P ARAMETERS

................................ ................................ ................................ ................................ ..... 9

M ETEOROLOGY D ATA

................................ ................................ ................................ ................................ ............. 10

V EHICLE T ECHNOLOGY P ROGRAMS

................................ ................................ ................................ ........................ 10

RESOURCES

................................ ................................ ................................ ................................ ............................. 12



# List of Exhibit s

E XHIBIT 1: S UMMARY OF A PPENDICES

................................ ................................ ................................ ........................... 1

E XHIBIT 2: M OTOR V EHICLE E MISSIONS U SING MOVES2010 A

................................ ................................ .................... 2

E XHIBIT 3: S UMMARY OF A NALYSIS T OOLS

................................ ................................ ................................ ................... 5

E XHIBIT 4: PPSUITE P ROCESS

................................ ................................ ................................ ................................ ...... 6



# Summary of Appendices

Appendix D

- 1: Mobile Source Highway Emissions Inventory

– An Explanation of Methodology

Appendix D

- 2: Emission Results for PM2.5 (PM2.5, PM10, VOC, CO, NOx, SO2, NH3)

(By Year, Road Type

, Source Type and Process )

Appendix D

- 3 : MO VES Sample Input FilesPittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 1



# SUMMARY

This technical appendix supports the PM 2.5 

### State Implementation Plan (SIP) for the Pittsburgh

- Beaver

Valley area . The nonattainment area consists of:

 Allegheny County not including the townships part of the Liberty

- Clairton nonattainment area

which include Lincoln Borough

, Clairton City

, Glassport Borough

, Liberty

, and Port Vue

Borough ;

 Elderton Borough and Plumcreek and Washington Township s in Armstrong County ;

 Beaver County ;

 Butler County ;

 Monongahela Township in Greene County ;

 Taylor T ownship south of New Castle City in Lawrence County ;

 Washington County ; and

 Westmoreland County

.

To meet emission inventory requirements of section 172(c)(3) of the Clean Air Act, a regional mobile

source highway inventory has been prepared for direct and precursor PM 2.5 

### emissions. Emissions are

estimated for the 2002, 2007, 2011, 2017 and 2025 analysis years. The pollutants included in the

inventory are primary emissions (including condensibles) of PM 2.5 

### and PM 10 

### and the precursor emissions

of VOC, CO, NOx, SO 2 

### , and NH 3



### .

On March 2, 2010, EPA officially released MOVES2010a to be used for all SIP submittals and future

transportation conformity analyses after a grac e period through March 2, 2012. On February 15, 20 12,

EPA extended the grace period to March 2, 2013

. This state implementation plan provides emission

inventory for the 2002, 2007, 2011, 2017 and 2025 analysis years using MOVES2010a.

Appendix D has been provided to summarize the methodology and analysis results for the motor vehicle

emissions inventory. To complement this executive summary, attachments have been provided with

additional detail regarding the analysis methodology, the MOVES input parameters, and the output

vehicle miles of travel ( VMT ) an d emission results for the region . These include:



### Exhibit 1 : Summary of Appendices

Appendix Title Description

D

- 1 Explanation of Methodology Provides a detailed summary of the methodology used to

calculate the VMT and emissions.



### D

- 2 ( 

### PM 2.5 

### , PM 10 

### ,VOC, CO, NOx,

SO 2 

### , and NH 3 )

Emission Results Provides annual emission exhibits by county, road type,

source type and process categories in 2002, 2007, 2011,

2017 and 2025.



### D

- 3 MOVES Sample

Input File Provides examples of the MOVES input files.Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 2



## Revised Emissions Inventory

A summary of the motor vehicle emissions for the Pittsburgh

- Beaver Valley Area is provided in Exhibit

2

. The emission estimates for all pollutants have been developed using the MO VES2010a emission

model an d latest planning assumptions. Emissions have been estimated for 2002, 2007, 2011, 201 7 and

20 25

.



### Exhibit 2 : Motor Vehicle Emissions Using MOVES2010 a

( Short Tons/Year

)

Pollutants /

Year PM 2.5 PM 10 VOC CO NOX SO2 NH3

Allegheny (P artial )

2002 976.92 1,201.25 13,171.26 174,786.78 32,460.70 759.28 530.22

2007 769.61 981.49 10,201.09 144,902.94 22,432.29 187.37 436.74

2011 502.82 693.18 7,644.20 97,172.85 14,689.70 76.93 314.09

2017 316.48 501.91 4,353.69 68,329.52 7,952.32 60.01 230.21

2025 241.68 441.17 2,585.80 56,395.76 4,762.52 59.16 221.85

Armstrong (P artial )

2002 7.74 8.82 72.94 958.42 243.48 5.05 2.92

2007 8.26 9.47 60.92 820.50 222.90 1.31 2.54

2011 2.65 3.31 34.53 438.37 84.91 0.36 1.56

2017 1.53 2.17 20.07 310.05 46.34 0.29 1.16

2025 0.98 1.62 11.57 246.91 26.79 0.26 1.03

Beaver

2002 182.59 217.39 2,061.38 27,358.79 5,842.63 131.05 83.38

2007 131.80 164.15 1,658.82 23,247.83 3,787.99 30.02 68.87

2011 78.52 106.49 1,232.52 15,550.01 2,365.83 12.16 50.45

2017 48.80 76.02 704.25 10,969.83 1,281.29 9.52 37.14

2025 36.06 64.36 413.29 8,956.07 750.90 9.13 34.75

Butler

2002 227.34 261.82 2,657.60 35,345.93 7,417.22 157.95 96.91

2007 171.68 204.72 2,289.59 31,231.96 5,220.22 36.33 81.75

2011 108.24 139.05 1,672.83 21,200.51 3,527.63 15.91 67.86

2017 68.16 99.40 1,027.12 15,842.99 2,026.95 13.18 52.60

2025 54.01 91.90 651.63 14,179.60 1,351.31 14.31 55.28

Greene (Partial)

2002 3.04 3.47 38.10 501.58 102.27 2.05 1.35

2007 2.71 3.18 33.28 385.99 85.81 0.60 1.33

2011 1.35 1.73 17.27 226.22 47.69 0.21 1.09

2017 0.80 1.16 10.07 156.41 25.77 0.17 0.78

2025 0.54 0.89 5.48 116.56 13.81 0.15 0.65



### (continued on next page)Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 3 

### Exhibit 2 : Motor Vehicle Emissions Using MOVES2010a (continued)

(Short Tons/Year)

Pollutants/

Year PM 2.5 PM 10 VOC CO NOX SO2 NH3

Lawrence (P artial )

2002 2.74 3.20 30.85 428.46 88.40 1.87 1.27

2007 2.12 2.57 23.73 283.09 64.36 0.49 1.09

2011 1.29 1.71 13.95 182.24 40.90 0.18 0.88

2017 0.74 1.13 7.98 124.06 21.76 0.14 0.62

2025 0.48 0.88 4.37 91.90 11.73 0.13 0.52

Washington

2002 318.19 364.87 2,782.23 38,882.59 10,281.17 220.67 129.69

2007 228.50 271.27 2,213.72 32,218.29 6,560.05 47.04 104.40

2011 102.88 132.74 1,540.23 20,163.87 3,197.99 15.73 68.14

2017 64.96 94.37 891.70 14,581.09 1,781.37 12.78 52.10

2025 49.49 81.49 533.70 12,425.06 1,101.99 13.03 51.92

Westmoreland

2002 487.82 567.68 4,657.76 63,184.00 15,656.25 341.28 203.43

2007 377.26 450.38 3,713.32 52,455.36 10,678.81 75.16 161.03

2011 168.77 225.66 2,657.30 34,579.73 5,229.77 27.72 119.51

2017 107.03 162.80 1,534.13 24,741.97 2,849.50 21.92 88.80

2025 83.32 143.63 919.41 20,866.88 1,715.98 21.88 86.59

Nonattainment Area Total

2002 2,206.38 2,628.51 25,472.11 341,446.56 72,092.11 1,619.19 1,049.19

2007 1,691.94 2,087.22 20,194.47 285,545.96 49,052.43 378.31 857.75

2011 966.52 1,303.87 14,812.83 189,513.79 29,184.43 149.20 623.58

2017 608.50 938.95 8,549.01 135,055.92 15,985.30 118.01 463.41

2025 466.57 825.95 5,125.24 113,278.73 9,735.03 118.07 452.59



## Analysis Methodology

Guidance documents from EPA were used to develop the base and future year emissions inventories for

the Pittsburgh

- Beaver Valley Nonattainment Area . They include:

 Motor Vehicle Emission Simulator, User Guide for MOVES2010a, EPA

- 420

- B

- 10

- 036,

August 2010.

 Policy Guidance on the Use of MOVES2010 and Subsequent Minor Revisions for State

Implementation Plan Development, Transportation Conformity, and Other Purposes

, US

EPA Office of Transportation and Air Quality , EPA

- 420

- B

- 12

- 010, April 2012.

 Using MOVES to Prepare Emission Inventories in State Implementation Plans and

Transportation Conformity: Technical Guidance for MOVES2010, 2010a and 2010b

. US

EPA Office of Transp ortation and Air Quality , EPA

- 420

- B

- 12

- 028, April 2012.Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 4



### The highway m obile source emission inventory was developed using available travel data and EPA’s

MOVES2010 a emission model. The methodologies used to produce the emission data conform to the

recommen dations provided in EPA’s Technical Guidance . A mix of local data and national default

(internal to MO VES 2010a ) data has been used for this submission. Local data has been used for the

primary data items that have a significant impact on emissions. Thes e include:

 Vehicle miles of travel ( VMT ) by vehicle type

.

 Average s peed d istribution

.

 Vehicle type mixes

.

 Source t ype p opulation (for light

- duty vehicles)

.

 Vehicle age distribution

.

 Hourly distributions

.

 Meteorology data

.

 Inspection/Maintenance p rogram

.

 Fuel s upply

.

For this submission, the 2002 base year traffic data source and environmental assumptions are consistent

with past analyses and submissions . For the rest of the years, m ost local data inputs to the analysis

process reflect the latest planni ng assumptions based on 200 8 and 2011 data obtained from the

Pennsylvania Department of Transportation ( PennDOT )

, the Bureau of Moto r Vehicles , and other

local/national sources

. N ewer data was availa ble and was used for traffic forecast growth rates

, con trol

strategies (e.g. Inspection

- Maintenance programs) , vehicle age distributions and fuel characteristics.

The analysis methodology is consistent with past statewide inventory efforts including the 200 8 and 2011

National Emissions Inventory (NEI) submission s

. This includes the use of custom post processing

software to calculate hourly speeds and prepare key traffic input files to the MOVES2010 a emissi on

model. A detailed methodology is provided in Appendix D

- 1

. The following sections address the key

input data sources and analysis tools used for the emissions inventory for the Pittsburgh

- Beaver Valley

Area

.Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 5



# DATA SOURCES AND ANALYSIS TOOLS

This section provides a summary of the key input data and analys i s tools used for producing the emission s

inventory. The key elements to the modeling protocol are described in the sections below. A more

detailed description of the analysis process and tools is provided in the methodology report s in Appendix

D

- 1 throug h D

- 3

.



## Analysis Tools

The mobile vehicle emissions inventory analysis utilizes several key software/programs for producing the

county emissions totals. These tools are outlined in Exhibit 3

.



### Exhibit 3 : Summary of Analysis Tools

Tool Purpose

MO VES 2010 a Produces emission rates for primary

emissions (including condensibles) of PM 2.5



### and PM 10 

### and the precursor emissions of

VOC, CO, NOx, SO 2 

### , and NH 3



### PPSUITE Processes the highway data ; Calculates

hourly congested speeds for each state

roadway segment ; Prepares MO VES 2010a

input files ; Processes MO VES 2010a output

files into a summary report

.

CENTRAL Provides a batch menu driven process to

execute PPSUITE, MOVES 2010a and other

MYSQL steps

.

The inventory reflects the highway mobile source emission estimations using EPA’s MO VES 2010a

emission model. EPA’s MOVES model was officially released on March 2, 2010 and was followed with

a revised versi on (MOVES2010a) in August 2010. Subsequent to the start of this analysis, EPA released

a newer version, MOVES2010b, in April 2012 ; however, the emission rates for criteria pollutants remain

consistent to previous versions. The MOVES 2010a model provides a more robust estimate of emissi ons

as compared to its predecessor MOBILE6.2. MOVES2010a has been integrated with local traffic, vehicle

fleet, environmental, fuel, and control strategy data to estimate emissions

.

PPSUITE represents an enhanced version of the Post Processor for Air Qua lity (PPAQ) software system

that has been used for previous inventory and conformity submissions in Pennsylvania. The software has

under gone significant revision s to ensure consistency with the MO VES 2010a . PPSUITE was used to

calculate hourly congested s peeds for each roadway link, apply vehicle type fractions, aggregate VMT,

prepare MOVES 2010a traffic

- related input files and process MOVES 2010a outputs

.

The PPSUITE software and process methodologies are consistent with that used for state inventories and

transportation conformity analyses throughout Pennsylvania

. Exhibit 4 summarizes the key functions of

PPSUITE.Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 6



### CENTRAL is a menu

- driven software platform that execute s the PPSUITE and MOVES 2010a processes

in batch mode. The software allows users to execute runs for a variety of input options and integrates

custom MYSQL steps into the process. CENTRAL provides important quality control and assurance

steps including file naming and storage automation.



## Traffic Data Source/Fleet Data Inputs

Traffic Volume Data : The PennDOT Roadway Management System (RMS) data serves as the primary

highway data source for the county and functional class VMT esti mates. The data source is used to

provide a “snapshot” of the regional roadway system and traffic volumes in 2002

, 2008 and 2011

(consistent with past triennial updates of traffic data). The 2008 and 2011 data is also integrated with

traffic signal locations. The data includes the average annual daily traffic (AADT) volumes for all state

roadways in Pennsylvania. To account for additional local roadway VMT and to ensure consisten cy with

reported Highway Performance Monitoring System (HPMS) VMT totals, the VMT totals estimated from

PennDOT’s RMS are adjusted to match the annual 2002

, 2008 and 2011 HP MS VMT totals respectively,

as reported to FHWA. For analysis year 2007, VMT is ad justed to match the annual 2007 HPMS VMT

total.

Special processing is required to estimate travel in the partial county portions of the nonattainment area.

The townships within each area were identified based on the nonattainment

- maintenance area design ation

descriptions. Using GIS, township boundaries were over

- la id on the PennDOT RMS segments and used

to identify which road segments fell within the nonattainment

- maintenance area. These state roadway

segments were used for the analysis of VMT and emis sions for non

- local state

- owned roadways. 

### Exhibit 4 : PPSUITE ProcessPittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 7



### The RMS roadway data contains some local segments (those which are state

- owned and function as local

roads). Since the RMS database does not contain a comprehensive representation of local roads, local

VMT is typ ically reconciled to the reported HPMS local VMT for each county in Pennsylvania. However,

HPMS VMT is only reported at the county

- level. For the partial areas the following methods were used

to estimate local VMT:

 Option 1: Calculate local VMT based on local road segments in RMS database (as discussed this

could underestimate local VMT)

 Option 2: Using GIS, determine the fraction of CENSUS TIGER roadway local mileage in the

nonattainment

- maintenance area as compared to the county total . This fraction is then applied to

the county HPMS local VMT.

 Option 3: Determine the fraction of population in the nonattainment

- maintenance area as

compared to the total county population . This fraction is then applied to the county HPMS local

VMT.

Th e three above methods were analyzed for each nonattainment area and the highest values were chosen

to ensure that local VMT was not under

- represented in the analysis. These values were used to estimate

emissions for the partial nonattainment

- maintenance a rea. Note, based on more recent snapshots of RMS

data, revised CENSUS TIGER roadway coverage files, and updated population estimates, the amount of

partial area VMT may differ from previous SIP submissions.

Seasonal Adjustments : Within MOVES, annual VMT is split to monthly sub

- totals and then to

weekdays and weekends using seasonal factors

. The monthly seasonal factors are developed from data

contained in the document s

, 200 2 Pennsylvania Traffic Data

, 2008 Pennsylvan ia Traffic Data and 2011

Pennsylvania Traffic Data, prepared by PennDOT’s Bureau of Planning and Research (BPR). The

seasonal and daily factors provided in this document are based on statistical analyses of 2002

, 2008 and

2011 traffic counts taken at permanent and in

- pavement ATR (automatic t raffic recorder) locations

throughout the state.

Congested Speeds : B ased on the average annual daily traffic, a single set of hourly speed distributions

are estimated by the PPSUITE post processin g system and input to MOVES. To disaggregate the daily

RMS volumes to hourly volumes, auto and truck hourly pattern data from PennDOT’s 2002 Pennsylvania

Traffic Data

, 2008 Pennsylvania Traffic Data and 2011 Pennsylvania Traffic Data reports are used to

determine the temporal variations in traffic volumes

.

Vehicle Population : The information on the vehicle fleet including the number and age of vehicles has a

significant impact on forecasted start and evaporative emissions within MOVES. The MOVES model

requires the number of vehicles by 13 source types to de t ermine evaporative emissions . State 2002

, 2008

and 2011 vehicle registration data (consistent with past triennial updates of traffic data) was used to

estimate vehicle population for light

- duty vehicles and school buses. The data was split to source typ es

using MOVES2010a default population data. For transit buses, data from PennDOT and the National

Transit Database (NTD) was used to estimate transit bus populations by county for 2008

. State 2011

registration data was used to estimate transit bus popula tion by county for 2011. For all other heavy

- duty

vehicles, PPSUITE calculates vehicle population based on the analysis year VM T for each source type

and default MOVES ratios of VMT and source type population (e.g. the number of miles per vehicle by

source type).

VMT by Source Type : The total VMT is disaggregated to the 13 MOVES 2010a source types. For this

inventory, the vehicle mix was calculated for each county and functional class grou ping utilizing a

combination of:

 2002

, 2008 an d 2011 RMS truck percentagesPittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 8



###  2002, 2008 and 2011 school bus registration data

 2008 and 2011 PennDOT transit data

 2008 NTD transit data

EPA’s MOVES default distribution of VMT by source type was used to determine the remaining source

type VMT percentages. The development of vehicle type pattern data input to the MOVES2010b

software is described in more detail in Appendix D

- 1

.

Vehicle Age Distribution : Vehicle age distributions are required to be input by 13 source types . The

distributions reflect the percentage of vehicles in the fleet up to 31 years old. The 2002 , 2008, and 2011

vehicle age distributions have been used for the 2002 , 2007, and 2011 emissions inventories respectively.

The 2011 vehicle age distributions have been used for the 2011 and future years (2017 and 2025) for this

inventory

. Due to insufficient data, only information for light

- duty vehicles are used as local inputs; and,

heavy

- duty vehicles use the MOVES 2010 national default age distribution

. The registration data

download is based on M OBILE6.2 vehicle categories

. T he data was converted to source types using the

EPA convertor spreadsheets provided with the MOVE S2010a emission model.



## Traffic Growth Assumptions

Traffic growth forecasting p lays a pivotal role in estimating future year emissions for the region. There

are many uncertainties affecting projections of traffic growth including the current economic conditions,

potential fuel prices, the impacts of natural gas industry activities in many counties throughout the state,

and the future growth in population and employment. Growth rates for this emissions inventory were

based on an assessm ent of available data sources including the regional travel model maintained by the

So uthwestern Pennsylvania Commission (SPC) and PennDOT’s BPR growth rate forecasting system

.

All SIP mobile source highway inventories include the review and assessment of county

- specific growth

rates from a Penn DOT study originally completed in 2005 and do cumented in the report, Statistical

Evaluation of Projected Traffic Growth, Traffic Growth Forecasting System: Final Report, March 14,

2005

. As part of that study, a statewide traffic growth forecasting system was developed that incorporates

traffic data from P enn DOT’s Traffic Information System and socioeconomic forecasts. That forecasting

system is maintained by the PennDOT BPR and is updated on a periodic basis. This system was last

updated in January of 2011 to develop new statistical relationships b etween historic VMT growth and

population (thru 200 9)

. The forecast population was estimated from the Woods and Poole data “2010

State Profile”. The results of the study have been shared between P enn DOT, PaDEP, and other

Interagency Consultation Group me mbers

, including the P ennsylvania Transportation

- Air Quality Work

Group ( which also includes EPA, FHWA, and representatives from larger MPOs within the state )

.

The growth rates from the PennDOT BPR forecasting sy s tem are evaluated against other available data

including travel model growth and other insights. For the development of MVEBs, upper estimates of the

VMT growth range are used for the forecast analyses. From an air quality perspective, the use of the

upper bound ary is conservative, and provides for factors outside P enn DOT or PaDEP control (e.g.,

potential socio

- economic growth above current forecasts, fleet age distributions, vehicle type distribution)

that influence motor vehicle emissions.Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 9



## Vehicle Population Growth Assumptions

Vehicle population growth forecasting plays a n important key role in determining emissions for future

year s for the region . For this inventory, v ehicle population was forecasted considering the growth from

three different sources:

 Household growth

 Population Growth

 VMT Growth

The household and population data w ere obtained from the PennDOT study documented in the report as

discussed above, Statistical Evaluation of Projected Traffic Growth, Traffic Growth Forecasting System:

Final Report, March 14, 2005

. The forecast household and population w ere estimated from the Woods

and Poole data “2010 State Profile”. The final growth rate was calculated assuming the highest growth

rate of household and population data but then limiting it to the VMT growth rate

. This methodology has

been used for past conformity analyses and has been accepted using the interagency consultation process

( Pennsylvania Air Quality Workgroup ).



## I/M and Fuel Parameters

I/M Program: The i nspectio n m aintenance (I/M) program inputs to the MO VES 2010a model are based

on past and current programs within each county (all Pennsylvania I/M programs are based on county

boundaries). All analysis year s include Pennsylvania’s statewide program

. The MOVES 2010a model

ha s simplified the I/M program input parameter s compared to MOBILE6.2

. The default I/M program

parameters included in MOVES 2010a were examined for each county and necessary changes made to the

defaults to match the actual local program.

In or der to assure that emission controls are working properly, vehicle inspection and maintenance (I/M)

programs have been adopted in some nonattainment areas. These programs have the added benefit of

improving the fuel efficiency of vehicles

. The Pennsylvan ia inspection and maintenance (I/M) program

was upgraded and expanded throughout the state with a phase

- in period starting in September 2003 and

fully implemented by June 2004.

The program requirements vary by region (five regions) and include on

- board diagnostics (OBD)

technology that uses the vehicle’s computer for model years 1996 and newer to identify potential engine

and exhaust system problems that could a ffect emissions. The program, named PAOBDII, is

implemented by region, a s follows:

 Philadelphia Region

- Bucks, Chester, Delaware, Montgo mery and Philadelphia Counties

 Pittsburgh Region

- Allegheny, Beaver, Washin gton and Westmoreland Counties

 South Central and Lehigh Valley Region

- Berks, Cumberland, Dauphin, Lancaster, Lebanon,

Lehigh, Northampton and York Counties

 North Region

- Blair, Cambria, Centre, Erie, Lackawanna, Luzerne , Lycoming, and Mercer

Counties

The OBDII program is implemented in Philadelphia and Pittsburgh along with tailpipe (idle in Pittsburgh

and idle and ASM in Philadelphia) and gas cap tests. Tests in other regions include:

 Subject vehicles registered in the South Central and Lehigh Valley counties receive the visual,

OBD and gas cap tests.Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 10



###  Subject vehicles registered in the North region receive a gas cap test and visual inspection.

 Subject vehicles registered in the other 42 counties (67 total counties) receive a visual inspection

as part o f the annual safety inspection.

Fuel Assumptions : The MOVES 2010a default fuel formulation and fuel supply data were reviewed and

updated based on available local volumetric fuel property information. Within the Pittsburgh region, a

low RVP (7.8) fuel program is in place and assumed for base and future analysis years. MOVES2010a

defau lt data was used for many of the key parameters. Several of the key updates to default data

included:

 Using 7.8 RVP for summer months in Pittsburgh 7

- county region.

 Using 8.7 RVP for summer months outside of the Pittsburgh low

- rvp region

.

 Conventional gasoline used throughout the year for analysis year s 2002 and 2007

.

 10% ethanol used throughout the year for analysis year s 2011, 201 7 and 2025

.



## Meteorolog

y Data

Updated weather information has been obtained from WeatherBank, Inc. ( www.weatherbank.com ). The

10

- year (1998

- 2008) average minimum and maximum monthly temperature and relative humidity values

were obtained for each of the 9 airport locations in Pennsylvania.

The MOVES 2010a model requires temperature and relative humidity data for each hour of the day and

for all the 12 months for the annual analysis. EPA’s data converters were used to convert minimum and

maximum daily temperatures to an hourly temperature profile that could be in put to MOVES 2010a

. These assumptions are consistent with the 2008 and 2011 NEI inventory submission s

.



## Vehicle Technology Programs

Federal Programs

Current f ederal vehicle emissions control and fuel programs are incorporated into the MO VES 2010a

softwar e. The se include the National Program standards covering model year vehicles through 2016.

Modifications of default emission rates are required to reflect the early implementation of the National

Low Emission Vehicle Program (NLEV) program in Pennsylvania. To reflect these impacts, EPA has

released instructions and input files that can be used to model these impacts. This inventory utilized the

August 2010 version of the files ( http://www.epa.gov/oms/models/moves/tools.htm ).

State Programs

The Pennsylvania Clean Vehicles (PCV) Program, adopted in 1998, incorporated the California Low

Emission Vehicle Program (CA LEVII) by reference

, although it allowed automakers to comply with the

NLEV program as an alternative to this Pennsylvania program until MY 2006. Beginning with MY 2008,

“new” passenger cars and light

- duty trucks with a gross vehicle weight rating (GVWR) of 8,500 pounds

or less that are sold or leased and titled in Pennsylvania must be certified by the California Air Resources

Board (CARB) or be certified for sale in all 50 states. For this program, a “new” vehicle is a qualified

vehicle with an odometer reading less than 7,500 miles. Pa DEP and PennDOT worked with the

automobile manufacturers, dealers and other interested business partners and finalized procedures for

complying with these new requirements. DEP focus es its outreach effort with the manufacturers and

dealers regarding what vehicles can be offered for sale and how to certify that the vehicles are compliant.

PennDOT’s role is to ensure licensing and registration records include these certifications of compliancePittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 11



### or that the vehicle owner qualifies for an exemption to the requirements. In all cases, DEP will use

information obtained during PennDOT’s title and registration process to oversee and audit, as needed,

certain vehicle title transactions to determine compliance to the program.

The impacts of this program are modeled for a ll analysis years beyo nd 2008 using the same instructions

and tools as downloaded for the early NLEV analysis. EPA provided input files to reflect the CAL LEVII

program. Modifications to those files were made to reflect a 2008 start date for Pennsylvania.Pittsburgh

- Beaver Valley Nonattainment Area Emissions Inventory : Executive Summary 12



# RESOURCES

Statist ical Evaluation of Projected Traffic Growth, Traffic Growth Forecasting System: Final Report,

Michael Baker Jr., Inc., March 14, 2005.

200 8 Pennsylvania Traffic Data

, P enn DOT Bureau of Planning and Research, 200 8

.

Motor Vehicle Emission Simulator, User Guide for MOVES2010a, EPA

- 420

- B

- 10

- 036, August 2010.

Instructions for Using LEV and NLEV Inputs for MOVES, US EPA, EPA

- 420

- B

- 10

- 003a, August 2010.

Policy Guidance on the Use of MOVES2010 and Subsequent Minor Revisions for State Implementation

Plan Development, Transportation Conformity, and Other Purposes , US EPA Office of Transportation

and Air Quality , EPA

- 420

- B

- 12

- 010, April 2012.

Using MOVES to Prepare Emission Inventories in State Implementation Plans a nd Transportation

Conformity: Technical Guidance for MOVES2010, 2010a and 2010b . US EPA Office of Transportation

and Air Quality , EPA

- 420

- B

- 12

- 028, April 2012.

2011 Pennsylvania Traffic Data, PennDOT Bureau of Planning and Research, 2011.

Metrological Data from Weather Bank, Inc., www.weatherbank.com

# APPENDIX D 1

Mobile Source Highway Emissions Inventory

An Explanation of Methodology

Bureau of Air Quality

Department of Environmental Protection

### [ This page intentionally left blank

. ]

# APPENDIX D

- 1

Explanation of MethodologyAn Explanation of Methodology 

### Explanation of Methodology

May 20 1 4



# TABLE OF CONTENTS

INTRODUCTION

................................ ................................ ................................ ................................ ....................... 1

O VERVIEW OF E MISSIONS I NVENTORIES

................................ ................................ ................................ .................... 1

H IGHWAY V EHICLE E MISSION I NVENTORIES

................................ ................................ ................................ ............. 1

WHERE DOES PENNSYLVA NIA OBTAIN ITS DATA?

................................ ................................ ..................... 4

S UMMARY OF MOVES I NPUTS

................................ ................................ ................................ ................................ .. 4

V EHICLE M ILES OF T RAVEL (VMT)

................................ ................................ ................................ .......................... 5

A DJUSTMENTS TO R OADWAY D ATA

................................ ................................ ................................ .......................... 8

V EHICLE T YPE P ROCESSING

................................ ................................ ................................ ................................ ...... 9

V EHICLE F LEET AND P OPULATION D ATA

................................ ................................ ................................ ................ 10

E NVIRONMENTAL

, F UEL AND T ECHNOLOGY A SSUMPTIONS

................................ ................................ .................... 11

SPEED/EMISSION ESTIM ATION PROCEDURE

................................ ................................ .............................. 12

V OLUME /VMT D EVELOPMENT

................................ ................................ ................................ ............................... 12

S PEED /D ELAY D ETERMINATION

................................ ................................ ................................ .............................. 15

HPMS AND VMT A DJUSTMENTS

................................ ................................ ................................ ............................ 16

MOVES E MISSIONS R UN

................................ ................................ ................................ ................................ ........ 17

RESOURCES

................................ ................................ ................................ ................................ ............................. 18

HIGHWAY VEHICLE INVE NTORY GLOSSARY

................................ ................................ ............................. 19



# List of Exhibits

E XHIBIT 1: S UMMARY OF PPSUITE P ROCESS

................................ ................................ ................................ ................ 3

E XHIBIT 2: MOVES L OCAL D ATA I NPUT S UMMARY

................................ ................................ ................................ ..... 4

E XHIBIT 3: P ENN DOT U RBA N /R URAL AND F UNCTIONAL C LASS C ODES

................................ ................................ ....... 6

E XHIBIT 4: E MISSION F ACTOR VS

. S PEED V ARIANCES (PM2.5)

................................ ................................ ..................... 7

E XHIBIT 5: MOVES S OURCE T YPES AND HPMS V EHICLE G ROUPS

................................ ................................ .............. 9

E XHIBIT 6: PPSUITE S PEED / E MISSION E STIMATION P ROCEDURE

................................ ................................ .............. 13A

ppendix D

- 1 1 

# INTRODUCTION

The purpose of this document is to explain how the Pennsylvania Department of Environmental

Protection (Department) estimates emissions from highway vehicles for inclusion in its emission

inventories and State Implementation Plans.



## Overview of Emissions Inventories

The Department’s inventories generally categorize e missions into four categories:

 Highway vehicles.

 Point sources (major industrial, commercial and utility sources).

 Non

- point sources (smaller industrial/commercial sources, consumer products).

 Nonroad mobile sources (including construction and agricultura l equipment, lawn and garden

equipment).

An evaluation of emissions from point, area, and mobile sources is needed to develop a complete

inventory needed for a maintenance demonstration plan. This documentation addresses the mobile source

activity and em issions for base and future years used to support such a demonstration.

Of all of the sources of air pollution, only the emissions of some stationary sources are measured directly

and continuously through instrumentation. Emissions from all other sour ces must be modeled based on

available local data , including those from highway vehicles. In their very simplest form, estimates of

emissions follow the following pattern:

Emission rate x activity level = emissions per time period (usually day or year)

Most emission rates have been developed by the U

. S

. Environmental Protection Agency ( EPA ) , in

cooperation with industry and states, and are compiled and documented in to key references or emission

models. These include Compilation of Air Pollution Emission Factors (AP

- 42)

, the Motor Vehicle

Emission Simulator (MOVES) model, and the NONROAD model. Adding up the products of the

emission rates and activity levels for all sources of a given pollutant constitutes the emissi on inventory for

that pollutant.



## Highway Vehicle Emission Inventories

Highway vehicles contribute significantly to air pollution, particularly to ground

- level ozone, which is the

most persistent air pollutant in Pennsylvania. Ground

- level 

### o zone is not em itted directly to the

atmosphere, but is formed by photochemical reactions between volatile organic compounds

(VOCs) and oxides of nitrogen (NO

x 

### ) in the presence of sunlight. The long, hot, humid days of

summer are particularly conducive to ozone formatio n, so ozone levels are of concern primarily

during the months of May through September. Both VOCs and NOx are emitted from highway

vehicles. In addition, fine particulates are also emitted directly by motor vehicles as a result of the

combustion process (tailpipe emissions), re

- entrained and transportation construction dust; and formed

through reactions in the atmosphere among the precursors VOC, CO, NOx, NH3 and SOx.

Pennsylvania’s PM

- related emission inventory efforts focus on these pollutants.A

ppendix D

- 1 2 

### Obviou sly, direct measurement of emission levels from all vehicles in use is impossible. In comparison

to highway vehicles, estimating residential heating emissions is a fairly simple calculation because there

is a constant emission rate and a fairly simple mea sure of activity. However, f or highway vehicles

estimating the emission rate and activity levels of all vehicles on the road during a typical summer day is

a complicated endeavor.

If every vehicle emitted the same amount of pollution all the time, one could simply multiply those

emission standards (emission rate in grams of pollution per mile) times the vehicle miles traveled ( VMT )

to estimate total emissions. But emission rates fr om all vehicles vary over the entire range of conditions

under which they operate. These variables include air temperature, speed, traffic conditions, o perating

mode and fuel characteristics . The inventory must also account for non

- exhaust or evaporative emissions.

In addition, the fleet is composed of several generations and types of vehicles with different emission

control technologies. This requires the estimation algorithm include the composition of the fleet (vehicle

ages and types)

.

In order to estimate both the rate at which emissions are being generated and to calculate vehicle miles

traveled (activity level), Pennsylvania examines its road network and fleet to estimate vehicle activity.

For ozone

- related inventories, this is done for a typical summer weekday. For c arbon m onoxide (CO) and

p articulate m atter (PM) emission inventories, this may be done for a typical winter weekday , summer

weekday and/ or annual conditions. Not only must this be done for a baseline year, but it must a lso be

projected into the future. This process involves a large quantity of data and is extremely complex.

Computer models have been developed to perform these calculations by simulating the travel of vehicles

on the Commonwealth’s roadway system. The models also generate emission s rates (also called emission

factors) for different vehicle types for area

- specific conditions

, and then combine them in summary form.

The area

- specific conditions include vehicle and highway data, plus control measure c haracteristics and

future year projections of all variables. The key models used to generate this mobile source emissions

inventory are:

MO VES : EPA’s MOVES model was officially released on March 2, 2010 and was followed with a

revised version (MOVES2 010a) in August 2010. The MOVES model provides a more robust estimate of

emissions as compared to its predecessor MOBILE6.2. MOVES calculates average in

- use fleet emission s

for each of thirteen categories of vehicles under various conditions affecting in

- use emission levels (e.g.,

ambient temperatures, average traffic speeds, gasoline volatility) as specified by the model user.

For this mobile source inventory, Pennsylvania used MOVES2010a as approved by EPA. MOVES can

be used to estimate national, state, and county level inventories of criteria air pollutants, precursors,

greenhouse gas emissions, and some mobile source air toxics from highway vehicles. Additionally,

MOVES can make projections for energy cons umption (total, petroleum

- based, and fossil

- based).

PPSUITE : For the Department’s highway emissions inventory, a post processor named PPSUITE

(formerly named PPAQ

- Post Processor for Air Quality) is used , which consists of a set of programs that

perform the following functions:

 Analyzes highway operating conditions

.

 Calculates highway speeds

.

 Compiles vehicle miles of travel (VMT) and vehicle type mix data

.

 Prepares MO VES runs and processes MOVES outputs.

PPSUITE is a widely used and accepted tool for estimating speeds and processing emission s rat es. The

software is based upon accepted transportation engineering methodologies. For example, PPSUITE uses

speed and delay estimation procedures based on planning methods provided in the Highway CapacityA

ppendix D

- 1 3 

### Manual , a report prepared by the Transportation Research Board (TRB) summarizing current knowledge

and analysis techniques for capacity and level

- of

- service analyses of the transportation system.

The PPSUITE process is integral to producing key input fil es to the MOVES emission model. Exhibit 1

summarizes the key functions of PPSUITE and the traffic

- related input files prepared for the MOVES

County Data Manager (CDM).



### Exhibit 1 : Summary of PPSUITE Process

The following sections summarize the key data and methodologies used to produce the mobile source

emissions inventory. This includes a summary of local data sources and a step

- by

- step review of the

speed calculation process. The emission data and pr ocess has been developed according to

recommendations provided by EPA in key policy and technical guidance as provided below:

 Policy Guidance on the Use of MOVES2010 and Subsequent Minor Revisions for State

Implementation Plan Development, Transportation Conformity, and Other Purposes

, US

EPA Office of Transportation and Air Quality , EPA

- 420

- B

- 12

- 010, April 2012.

 Using MOVES to Prepare Emission Inventories in State Implementation Plans and

Transportation Conformity: Technical Guidance for MOVES2010, 2010a and 2010b

. US

EPA Office of Transportation and Air Quality , EPA

- 420

- B

- 12

- 028, April 2012.

The process has focused on developing an emissions inventory using the available tools and data to its

fullest extent. This includes the use of available local dat a for items that have a significant impact on

emissions and applying a robust calculation process to estimate hourly traffic speeds.A

ppendix D

- 1 4 

# WHERE DOES PENNSYLVANIA OBTAIN ITS DATA?

Summary of MOVES Inputs

A large number of inputs to MO VES are needed to fully account for the numerous vehicle and

environmental parameters that affect emissions . These include traffic flow characteristics (as determined

from the PPSUITE software), vehicle descriptions, fuel parameters, inspection/maintenance p rogram

parameters, and environmental varia bles

. MOVES includes a default national database of meteorology,

vehicle fleet, vehicle activity, fuel, and emission control program data for every county ; but EPA cannot

certify that the default data is the most c urrent or best available information for any specific area

. As a

result, local data is recommended for use for analyses supporting s tate i mplementation p lans (SIPs)

.

A mix of local and default data is used for this inventory. Local data sources are used for all inputs that

have a significant impact on calculated emission rates. Exhibit 2 summarizes Pennsylvania

- specific

inputs assembled and used for this inventory

. These data items are discussed in the following sections.



### Exhibit 2 : MOVES Local Data Input Summary

Traffic Vehicle Fuel Inspection Environmental

Data D escriptions Parameters Maintenance Variables

Vehicle Type Vehicle Type RVP Start Year H ourly

VMT Mix Model Year s Temperatures

Vehicle Vehicle Age Sulfur T est Standards

, Population Distribution Level Source Types, Humidity

Frequency

VMT Average Speeds Et hanol Stringency,

Fractions (PPSUITE) Volume Waiver Rate,

(PPSUITE) Compliance

Road Type Hourly Refueling

Distribution Distributions Controls

(PPSUITE)

R amp

Fraction

(PPSUITE)

Emission RatesA

ppendix D

- 1 5 

## Vehicle Miles of Travel (VMT)

The VMT input to emissions calculations for Pennsylvania is based on information from the Roadway

Management System (RMS) maintained by the Pennsylvania Department of Transportation’s

( P enn DOT’s ) Bureau of Planning and Research (BPR) . P ennD OT obtains this information from periodic

visual and electronic traffic counts. RMS data is dynamic

, since it is continually reviewed and updated

from new traffic coun ts and field visits conducted by P enn DOT. Information on roadways included in the

National Highway System is reviewed at least annually, while information on other roadways is reviewed

at least biennially.

On a triennial basis, a current “snapshot” of t he RMS database is taken and downloaded to provide an up

to

- date record of the Commonwealth’s highway system for estimating emissions. Th is emissions

inventory is based on the most current snapshot of the RMS data.

The RMS database contains all state hi ghways, including the Pennsylvania Turnpike, divided into

segments approximately 0.5 miles in length. These segments are usually divided at important

intersections or locations where there is a change in the physical characteristics of the roadway (e.g. t he

number of lane s changes). There are approximately 99,000 state highway segments for the 67

Pennsylvania counties contained in the 2008 RMS and about 120,000 segments in the 2011 RMS . Each

of these segments contains an abundance of descriptive data, bu t only the following information is

extracted for emission calculations:

 Lanes

.

 Distances

.

 Volumes representing Average Annual Daily Traffic (AADT)

.

 Truck percentages

.

 P enn DOT urban/rural classifications

.

 P enn DOT functional class codes

.

 Number of signals (based on linkage to PennDOT GIS signal location data)

.

RMS volumes and distances are used in calculating highway VMT totals for each county. As discussed

in the next section, adjustments are needed to convert the volumes to reflect annual conditions. I n

addition, the traffic volumes must be forecast to support future year emission inventories. Lane values

and traffic signals are an important input for determining the congestion and speeds for individual

highway segments. Truck percentages are used in the speed determination process and are used to split

volumes to individual vehicle types used by the MO VES software.

R oad segments are classified by function, as well as w hether it is located in an urban, small urban or rural

area, as indicated below in Exhibit 3 . The P enn DOT urban/rural (UR) and functional classes (FC) are

important indicators of the type and function of each roadway segment

. The variables provide insigh ts

into other characteristics not contained in the RMS data that are used for speed and emission calculations.A

ppendix D

- 1 6



### Exhibit 3 : PennDOT Urban/Rural and Functional Class Codes

Urban/Rural Code 1=Rural

2=Small Urban

3=Urban

Functional Class Rural Functional Classes Used Urban Functional Classes Used

For Rural Areas For Small Urban and Urban Areas

------------------------------------- ------------------------------------------ 1=Rural Freeway 11=Urban Fr eeway

2=Rural Other Principal Arterial 12=Urban Expressway

6=Rural Minor Arterial 14=Urban Principal Arterial

7=Rural Major Collector 16=Urban Minor Arterial

8=Rural Minor Collector 17=Urban Collector

9=Rural Local 19=Urban Local



### A dditional Network Information: The PPSUITE software system allows for many additional variables

other than those available in the RMS database. Using these variables improves the ability of the

Department to incorporate real roadway conditions into its estimates. The variables include information

regarding free

- flow speeds and capacities, signal characteristics and other physical roadway features that

can affect a roadway’s calculated congested speed. Th is data can be determined from lookup tables based

on a roadway segment’s urban/rural code and functional class. Much of the lookup table data was

developed from i nformation contained in the Highway Capacity Manua l

, PennDOT information on

speeds and signa l densities , and other e ngineering judgment

.

MOVES Traffic Inputs: The PPSUITE software uses RMS traffic data to prepare key inputs to the

MOVES emission model including :

 VMT

.

 T ravel speeds

.

 R oad type distributions

.

 Ramp fractions

.

VMT is the primary traffic input that affects emission results. The roadway segment distances and traffic

volumes are used to prepare estimates of VMT. PPSUITE performs these calculations and outputs the

MOVES annual VMT input f ile to the CDM

.

Emissions for many pollutants (including PM and precursors) vary significantly with travel speed. For

PM, higher emission rates are associated with lower speeds and lower rates are associated with higher

speeds, as illustrated in Exhibit 4. To obtain the best estimate of vehicle speeds, the Department uses the

PPSUITE set of programs, whose primary function is to calculate speeds and to organize and simplify the

handling of large amounts of data needed for calculating speeds and for preparing MOVES input files

. The PPSUITE software prepares the MOVES vehicle hours of travel (VHT) by speed bin file which

summarizes the distribution of speeds across all links into each of 16 MOVES speed bins for each hour of

the day. This robust process ensures that MOVES emission rates are used to the fullest extent and is

consistent with the methods and recommendations provided in EPA’s 

### Using MOVES to Prepare

Emission Inventories in State Implementation Plans and Transportation Conformity: Technical

Guidance for MOVES2010 , 2010a and 2010b

.A

ppendix D

- 1 7



### Exhibit 4 : Emission Factor vs. Speed Variances (PM2.5)

In MOVES, typical drive cycles and associated operating conditions vary by the type of roadway.

MOVES defines five different road types as follows:

1 Off

- Network

. 2 Rural Restricted Access

. 3 Rural Unrestricted Access

. 4 Urban Restricted Access

. 5 Urban Unrestricted Access

.

The off

- network road type includes emissions from vehicle starts, extended idle activity, and evaporative

emissions. Off

- network activity in MOVES is primarily determined by the Source Type Population

input

, as discussed in a followi ng section

. The remaining distribution among road types is determined by

equating the PennDOT functional class with each MOVES road type as follows:

 MOVES Road Type (2) = PennDOT Functional Class (1)

.

 MOVES Road Type (3) = PennDOT Functional Class (2,6,7 ,8,9)

.

 MOVES Road Type (4) = PennDOT Functional Class (11,12)

.

 MOVES Road Type (5) = PennDOT Functional Class (14,16,17,19)

.

For this inventory, the MOVES road type distribution file is automatically generated by PPSUITE using

the defined equivalencies.

Since ramps are not directly represented within the RMS database information, it is assumed that 8% of

the Freeway V H T is Ramp V H T. This is consistent with the recommendations provided in EPA’s

t echnical g uidance

. Source: Figure 3 from Implications of the MOVES2010 Model on Mobile

Source Emission Estimates, Air & Waste Management Association, July 2010.A

ppendix D

- 1 8 

## Adjustments to Roadway Data

Before the RMS data can be used by PPSUITE for speed and emission calculations, several adjustments

and additions must be made to the roadway data. These adjustments are summarized below.

HPMS Adjustments : According to EPA guidance, baseline inventory VMT comp uted from the RMS

highway segment volumes must be adjusted to be consistent with Highway Performance Monitoring

System (HPMS) VMT totals. The HPMS VMT reported for Pennsylvania is a subsystem of the RMS

established to meet the data reporting requirements o f the Federal Highway Administration (FHWA) and

to serve as P enn DOT’s official source of highway information. Although it has some limitations, the

HPMS system is currently in use in all 50 states and is being improved under FHWA direction.

Although th e HPMS VMT and the roadway data used for an inventory emissions analysis are both based

on data from the RMS system, differences do exist between them and include the following. First, the

HPMS and inventory roadway data are “snapshots” of the RMS data ta ken at different times. Since the

RMS is dynamic, changing constantly due to new data, differences will result between the data used for

calculating HPMS VMT totals and the inventory data used for an emissions analysis. Second

, since the

RMS does not con tain many of the local roadways, local road estimates of HPMS VMT are obtained

through alternative procedures developed by P enn DOT

. To account for such differences, adjustment

factors are calculated and used to adjust the inventory roadway data to the reported HPMS VMT totals

submitted to FHWA. The VMT contained in the HPMS reports are considered to represent average

annual daily traffic (AADT).

Adjustment factors are calculated which adjust the base year RMS download VMT to the reported HPMS

totals fo r that year. These factors are developed for each county and functional class combination and are

also applied to all future year runs. Adjustments for the “higher” functional classes (e.g. Freeway,

Arterials

- major routes) are close to 1.000 since HPMS VMT is derived from RMS information, and the

only difference in the data is that the “snapshot” for the emission calculations is taken at a different time

than for the HPMS. “Lower” classes (e.g. local roads) require greater adjustment since a large part of the

local system is not under state jurisdiction and is not in the RMS database. There is, of course, a

significant amount of local road mileage in the state. It is assumed that those local streets that are in RMS

are representative of all local stree ts in their area with respect to volume and speed, so that roadway

mileage adjustment is appropriate.

Seasonal Adjustments to Volumes : The RMS contains AADT volumes that are an average of all days in

the year, including weekends and holidays. PM and CO analyses require volumes representing monthly

average conditions (needed for producing annual totals). Therefore, the RMS volumes must be seasonally

adjusted. Seasonal factors were developed for each functional class and urban/rural code based on yearly

count information prepared by PennDOT’s BPR. These factors are applied to the existing RMS AADT

volumes to produce the monthly volumes. The same factors are also used to develop the MOVES daily

and monthly VMT fraction files

.

Hourly Adjustments : Speed s and emissions vary considerably depending on the time of day

. Therefore, it is important to estimate the pattern by which roadway volume varies by hour of the day.

The 24

- hour pattern data provides PPSUITE with information used to split the daily roadw ay segment

volumes to each of the 24 hours in a day. Pattern data is in the form of a percentage of the daily volumes

for each hour. Distributions are provided for each county and functional class grouping. This data is

developed from 24

- hour count data compiled by PennDOT’s B PR , according to the process in the

agencies annual traffic data reports. The same factors are also used to develop the MOVES hourly

fraction file.A

ppendix D

- 1 9 

### Traffic Volume Forecasts : Traffic growth forecasting plays a pivotal role in esti mating future year

emissions for the region. There are many uncertainties affecting projections of traffic growth

, including

the current economic conditions, potential fuel prices, the impacts of Marcellus Shale activities in many

counties throughout the state, and the future growth in population and employment. Growth rates for the

Department’s emissions inventor ies are based on an assessment of available data sources which include:

 PennDOT BPR growth rate forecasting system.

 Regional travel model, if available.

 Estimates of Marcellus Shale related activity growth, if applicable

.

All SIP mobile source highway inventories include the review and assessment of county

- specific growth

rates from a PennDOT study originally completed in 2005 and documented in the report, Statistical

Evaluation of Projected Traffic Growth, Traffic Growth F orecasting System: Final Report, March 14,

2005 . As part of that study, a statewide traffic growth forecasting system was developed that incorporates

traffic data from PennDOT’s Traffic Information System and socioeconomic forecasts. That forecasting

sys tem is maintained by the PennDOT BPR and is updated on a periodic basis to develop new statistical

relationships between historic VMT growth and population and updated demographic forecasts from

Woods and Poole , Inc. The growth rates from the PennDOT BPR forecasting system are evaluated

against other available data including travel model growth and other insights.



## Vehicle Type Processing

Emission rates within MOVES vary significantly by the type of vehicle. The MOVES model produces

emissions and rate s by thirteen MOVES vehicle source types. However, VMT is input to MOVES by six

HPMS vehicle groups. Exhibit 5 summarizes the distinction between each classification scheme.



### Exhibit 5 : MOVES Source Types and HPMS Vehicle Groups

SOURCE TYPES HPMS Class Groups

11 Motorcycle 10 Motorcycle

21 Passenger Car 20 Passenger Car

31 Passenger Truck 30 Passenger/Light Truck

32 Light Commercial Truck 40 Buses

41 Intercity Bus 50 Single Unit Trucks

42 Transit Bus 60 Combination Trucks

43 School bus

51 Refuse Truck

52 Single Unit Short

- haul Truck

53 Single Unit Long

- haul Truck

54 Motor Home

61 Combination Short

- haul Truck

62 Combination Long

- haul Truck



### The process used for this inventory includes a method to disaggregate the RMS traffic volumes to the

thirteen source types and then to recombine the estimates to the six HPMS vehicle classes. V ehicle type

pattern data is used by PPSUITE to divide the hour ly roadway segment volumes to the thirteen MOVES

source types. Similar to the 24

- hour pattern data, this data contains percentage splits to each source type

for every hour of the day. The vehicle type pattern data for this inventory is developed from sev eral

sources of information:A

ppendix D

- 1 10 

###  P enn DOT truck percentages from the RMS database

.

 Hourly distributions for trucks and total traffic compiled by PennDOT’s B PR

.

 Transit data from PennDOT and the N ational T ransit D atabase

.

 S chool bus registration data from PennDOT’s Bureau of Motor Vehicles Registration Database

.

The vehicle type pattern data is developed for each county and functional class combination. First, RMS

truck percentages are averaged for all roadways within a county and functional class g rouping. Using this

percentage data, the total roadway volume for any segment is divided to auto and truck vehicle type

categories. The transit data and school bus data is used to further disaggregate trucks

, resulting in four

vehicle groups (light

- duty, school, transit, and other heavy

- duty)

.

From these groups, MO VES default Pennsylvania county VMT distribution s by source type are used to

divide the four groups into each of the MO VES source type s

. P enn DOT hourly distributions for trucks

and total traffic are used to create source type percentage breakdowns for each hour of the day.

Vehicle Type Capacity Analysis Factors : Vehicle type percentages are provided to the capacity

analysis section of PPSUI TE to adjust the speeds in response to trucks. That is, a given number of larger

trucks take up more roadway space than a given number of cars, and this is accounted for in the speed

estimation process by adjusting capacity using information from the High way Capacity Manual

.



## Vehicle Fleet and Population Data

The information on the vehicle fleet including the number and age of vehicles has a significant impact on

forecasted start and evaporative emissions within MOVES. The MOVES Model requires the popul ation

of vehicles by the thirteen source type categories

. Pennsylvania county vehicle registration data is used to

estimate vehicle population for light

- duty vehicles and school buses. The data is split to source types

using MOVES default P ennsylvania county population data. For transit buses, data from PennDOT and

the National Transit Database (NTD) is used to estimate county transit bus totals. O ther heavy

- duty

vehicle population values are based on VMT for each source type using the vehicle mix and pattern data

discussed previously. The PPSUITE software automatically applies default MOVES ratios of VMT and

source type population (e.g. the number of mi les per vehicle by source type) to the local VMT estimates

to produce vehicle population.

Vehicle population is forecast based on projected household and population growth from Woods and

Poole Inc. for each Pennsylvania county. The growth rate methodology includes:

 Choosing the highest growth rate between population and households

.

 Limiting growth as to not exceed the VMT growth assumptions

.

Vehicle Age : Vehicle age distributions are input to MOVES for each county by the thirteen source types.

The distributions reflect the percentage of vehicles in the fleet up to 31 years old. The most recent

avai lable registration download from PennDOT’s Bureau of Motor Vehicles Registration Database has

been used for the inventory. Due to insufficient data, only information for light

- duty vehicles are used as

local inputs; and, heavy

- duty vehicles use the MOVES2 010 national default age distribution . The

registration data download is based on MOBILE6.2 vehicle categories. As a result, the data was

converted to source types using the EPA convertor spreadshe ets provided with the MOVES emission

model.A

ppendix D

- 1 11 

## Environmental, Fuel and Technology Assumptions

Information on environmental, fuel, vehicle technology and other control strategy assumptions were

determined based on a review of MOVES 2010a default information by the PaDEP.

Fuel Parameters : The same vehi cle will produce different emissions using a different type of gasoline.

Fuel control strategies can be powerful emission reduction mechanisms

. The MOVES2010a default fuel

formulation and fuel supply data were reviewed and updated based on available local volumetric fuel

property information. The gasohol market penetration and RVP values were updated for all the counties

. MOVES 2010a default data was used for the rest of the parameters.

Refueling Emissions : MO VES also allows users to calculate refueling emissions, the emissions created

when vehicles are refueled at service stations. Pennsylvania includes refueling emissions in its area

source inventory and not in its highway vehicle inventory. R efueling emissions are not included in the

highway emissio ns inventory.

Vehicle Emission Inspection/Maintenance (I/M) Parameters : MO VES allows users to vary inputs

depending on the I/M program in place for the area

. The inputs include:

 P rogram start year

.

 S tringency level

.

 F irst and last model years subject to the program

.

 W aiver rates

.

 Co mpliance rates

.

 P rogram type (test

- only, test

- and

- repair, etc.) and effectiveness

.

 F requency of inspection (annual, biennial)

.

 V ehicle type coverage

.

 T est type (idle, loaded, etc.)

The MOVES2010a default P ennsylvania assumptions were reviewed and modifications were made per

actual program parameters.

Environmental Variables : Ambient temperature and humidity are known to have a significant impact

on most pollutant processes for on

- road vehicles. In MOVES 2010, temperature and humidity affect

emissions through three mechanisms: 1) direct effect via a temperature adjustment on emission rates; 2)

direct effect via a humidity correction factor for NOx; 3) indirect effect via an air conditioning adjustment

for which temperature and relative humidity are used to populate a heat index which in turn is used to

calculate the fraction of vehicle fleet with air conditioning turned on. Hourly temperatures have been

compiled for each county based on information from W eatherBank, Inc. to specify temperatures from

nine airports within the state. Ozone analysis temperature and humidity values were determined using the

procedures documented in EPA’s technical guidance. Minimum and maximum temperatures for each

month were converted to hourly temperatures using EPA convertors supplied with the MOVES model.

A summary of the MO VES related inputs used for the inventory and future year estimates are attached

with the submission.A

ppendix D

- 1 12 

# SPEED/EMISSION ESTIMATION PROCEDURE

The previous sections have summarized the input data used for computing speeds and emission s for

Pennsylvania. This section explains how PPSUITE and MO VES use s that input data to produce emission

estimates. Exhibit 6 summarizes PPSUITE’s analysis procedure used for each of the RMS highway

segments in the state.

Producing an emissions inventory with PPSUITE requires a process of disaggregation and aggregation.

Data is available and used on a very small scale

-- individual 1⁄2 mile roadway segments 24 hours of the

day. This data needs to be processed individually to determine the distribution of vehicle hours of travel

(VHT) by speed and then aggregated by vehicle class to determine input VMT to the MOVES emission

model.



## Volume/VMT Development

Before speeds can be calculated and MO VES run, volumes acquired from RMS must be adjusted and

disaggregated. Such adjustments include factoring to future years, seasonal adjustments, and

disaggregating daily volumes to each hour of the day and to each of the thirteen MO VES source types.

Determine Future Year Volumes : The RMS database contains up

- to

- date current year volumes.

However, to conduct a future year analysis, these volumes must be factored to the year being analyzed.

Growth factors have been prepared for ea ch county and functional class grouping. These growth factors

are applied to the base year RMS volumes to obtain future year estimates that can be utilized by

PPSUITE.

Example:

A typical freeway link in the RMS database is I

- 80 segment 2500 in Luzerne County,

Pennsylvania. This link has an urban/rural code=1 which indicates the link is in a rural area, and a

functional class=1 indicating a rural freeway.

The average annual daily traffic (AADT) from the RMS database for this link in 200 8 is 12,077

ve hicles/day.

Growth factors have been developed to factor the 200 8 volume to future years. For example, to

factor the 200 8 volume to the year 20 14 , a growth factor of 1.282 would yield:

20 14 volume = 12,077 vehicles/day x 1.282 = 15,483 vehicles/dayA

ppendix D

- 1 13



### Exhibit 6 : PPSUITE Speed / Emission Estimation Procedure

Data From PPSUITE Input Files PPSUITE Analysis Process Data from Roadway Source (RMS)

The Following is Performed For

Each RMS Roadway Segment

Percent Pattern Distributions Expand to 24 hourly volumes RMS AWDT Adjusted Volumes

Apply VMT Adjustments Adjust Volumes for Peak Spreading

(V/C thresholds for spreading)

Vehicle Type Patterns Disaggregate to Vehicle Type RMS Truck Percentages

T ransit D ata

School Bus Data

Calculate Link & Signal Capacities Roadway Attributes

(Lanes, FC code, UR code)

Speed/Capacity Lookup Table

Calculate Link Calculate

Midblock Speed Approach Delay

Apply Post Speed VMT Adjustments

Prepare MOVES CDM Files

VHT by Annual RoadType SourceType Hourly Ramp

Speed Bin V MT Fractions Population Fractions Fractions

Per VMT < Default >

< Trucks >

Off

- line File Preparation

Vehicle Age

Distribution Run MOVES Importer

to convert county input data

Hourly into MYSQL data format

Temps/Humidity

I/M / Fuel

Parameters

Source Type Run MOVES

Population

Month/Day

VMT FractionA

ppendix D

- 1 14 

### Seasonal Adjustments : PPSUITE takes the input daily volumes from RMS ( which represent s annual

average daily traffic ( AADT ) ) and seasonally adjusts the volumes to an average weekday in July. This

adjustment utilizes factors developed for each functional class and urban/rural code. VMT can then be

calculated for each link using the adjusted weekday volumes.

Example:

Again, assume the rural freeway link: I

- 80 segment 2500 in Luzerne County, Pennsylvania. The

AADT for this link in 2008 is 12,077 vehicles/day.

Seasonal factors have been developed for urban/rural code and functional class combinations. For

an urban/rural code=1 and a functional class=1, the factor to convert from AADT to an average

weekday in July is = 1.15

.

Average Weekday July Volume = 12,077 x 1.15 = 13,889 vehicles/day

.

Total VMT (daily) for this link is calculated as volume x distance. The distanc e of this link as

obtained from RMS is 0.2 9 6 miles.

2008 VMT = 13,889 vehicles/day x 0.296 miles = 4,111 vehicle

- miles / day

.



### Disaggregation to 24 Hours : After seasonally adjusting the link volume, the volume is split to each hour

of the day. This allows for more accurate speed calculations (effects of congested hours) and allows

PPSUITE to prepare the hourly VMT and speeds for input to the MOVES model.

Example:

To support speed calculations and emission estimates by time of day, the July weekday volume is

disaggregated to 24 hourly volumes. Temporal patterns were previously developed from

P enn DOT count data and input to PPSUITE. For the I

- 80 rural freeway link with morning peak

volumes similar to evening peak hours (neutral), the following temp oral pattern is applied:

Using the I

- 80 segment, typical hourly volumes which result include:

8

- 9 a.m. 6.0% x (4,111 vehicle miles/ 0.296mi.) = 833 vehicles/hour (vph)

12

- 1 p.m. 5.0% x (4,111 vehicle .miles/ 0.296mi.) = 694 vph

5

- 6 p.m. 6.3% x (4,111 vehicle miles/ 0.296mi.) = 875 vphA

ppendix D

- 1 15 

### After dividing the daily volumes to each hour of the day, PPSUITE identifies hours that are unreasonably

congested. For those hours, PPSUIT E then spreads a portion of the volume to other hours within the

same peak period, thereby approximating the “peak spreading” that normally occurs in such over

- capacity

conditions.

Disaggregation to Vehicle Type : EPA requires VMT estimates to be prep ared by source type, reflecting

specific local characteristics. As a result, for Pennsylvania’s emission inventory runs, the hourly volumes

are disaggregated to the thirteen MOVES source types based on count data assembled by P enn DOT in

combination with M OVES defaults.

Example:

Disaggregation of the total I

- 80 VMT to the various source types would include the following:

Total Volume 8

- 9 am = 833 vph

Source Type Volume 8

- 9 am:

Motorcycle 11 0.5% 4 vph

Passenger Car 21 54.7% 456 vph

Passenger Truck 31 27.9% 232 vph

Light Commercial Truck 32 9.3% 78 vph

Intercity Bus 41 0.1% 1 vph

Transit Bus 42 0.1% 1 vph

School bus 43 0.1% 1 vph

Refuse Truck 51 0.0% 0 vph

Single Unit Shor t

- haul Truck 52 2.2% 19 vph

Single Unit Long

- haul Truck 53 0.3% 2 vph

Motor Home 54 0.1% 1 vph

Combination Short

- haul Truck 61 1.9% 16 vph

Combination Long

- haul Truck 62 2.6% 22 vph



## Speed/Delay Determination

EPA recognizes that the estimation of vehicle speeds is a difficult and complex process. Because

emissions are so sensitive to speeds, it recommends special attention be given to developing reasonable

and consistent speed estimates; it also recommends that VMT be disaggregated into subsets that have

roughly equal speed, with separate emission factors for each subset. At a minimum, speeds should be

estimated separately by road type.

The computational framework used for this analysis meets and exceeds that recommendation. Speeds are

individually calculated for each roadway segment and hour and include the delays encountered at signals.

Rather than accumulating the roadway segments into a particular road type and calculating an average

speed, each ind ividual link hourly speed is represented in the MOVES vehicle hours of travel (VHT) by

speed bin file. This MOVES input file allows the specificat i on of a distribution of hourly speeds.

For example, if 5% of a county’s arterial V H T operate s at 5 mph du ring the AM peak hour and the

remaining 95% operate s at 65 mph, this can be represented in the MOVES speed input file. For the

model runs, distributions of speeds are input to MOVES by road type and source type by each hour of the

day; VMT and VHT is accu mulated by the same groupings for the application of the emission factors to

produce resulting emission totals.A

ppendix D

- 1 16 

### To calculate speeds, PPSUITE first obtains initial capacities (how much volume the roadway can serve

before heavy congestion) and free

- flow spee ds (speeds assuming no congestion) from the speed/capacity

lookup data. As described in previous sections, this data contains default roadway information indexed

by the urban/rural code and functional class. For areas with known characteristics, values c an be directly

coded to the RMS database and the speed/capacity data can be overridden. However, for most areas

where known information is not available, the speed/capacity lookups provide valuable default

information regarding speeds, capacities, signal characteristics, and other capacity adjustment information

used for calculating congested delays and speeds. An effort has been made to enhance the RMS data with

traffic signal locations using other GIS signal data available from PennDOT’s Bureau of Highw ay Safety

and Traffic Engineering.

Example:

The speed/capacity lookup table is used to obtain important data used for link speed calculations.

For the I

- 80 link with an urban/rural code = 1 (rural) and a functional class = 1 (freeway), the

lookup table provides information including the following:

freeflow speed = 65 mph

capacity = 1800 vph per lane

number of signals = 0 (per RMS linkage to GIS traffic signal locations)

This information is used along with the physical characteristics of the roadwa y to calculate the

delay (including congestion) to travel this link during each hour of the day:

For example: The I

- 80 link is calculated to have a travel time, including delay of 17.76 seconds

for the 8

- 9am hour

.

Total travel time, in vehicle hours, fo r the 8

- 9am hour is calculated as:

VHT (8

- 9am) = 17.76 seconds x 833vph / 3600 sec/hr = 4.12 vehicle hours

.



### The result of this process is an estimated average travel time for each hour of the day for each highway

segment. The average time can be multiplied by the volume to produce vehicle hours of travel (VHT).



## HPMS and VMT Adjustments

Volumes must also be adjusted to account for differences with the HPMS VMT totals, as described

previously. VMT adjustment factors are provided as input to PPSUI TE, and are applied to each of the

roadway segment volumes. These factors were developed from the latest HPMS download (conducted

triennially) ; however, they are also applied to any future year runs. The VMT added or subtracted to the

RMS database assume s the speeds calculated using the original volumes for each roadway segment for

each hour of the day.A

ppendix D

- 1 17

Example:

Using the Luzerne County I

- 80 rural freeway link example, the daily assigned volume is adjusted

to account for reconciliation with the HPMS VM T. RMS VMT (in AADT) for Luzerne County

rural freeways totals 962,559 vehicle miles in 2008. HPMS VMT (in AADT) as supplied by

P enn DOT and reported to FHWA totals to 990,088 vehicle miles for the rural freeways. A factor

is developed by dividing the HP MS VMT by the RMS VMT:

HPMS adjustment factor for Luzerne County rural freeways = 990,088 / 962,559 = 1.029

.

This factor is held constant in all future years. As an example, this adjustment is made to the

I

- 80 freeway link VMT for the 8

- 9am hour afte r speed calculations are made, and produces the

final July weekday VMT for this hour used for Ozone runs.

I

- 80 Link VMT (8

- 9am) = 833vph x 0.296 miles x 1.029 = 254 vehicle miles /hour

.



## MO VES Emissions Run

After computing speeds and aggregating VMT and VHT, PPSUITE prepares traffic

- related inputs needed

to run EPA’s MOVES software, which is used to estimate emission factors in grams of pollutant per

vehicle mile and to produce total emissions based on input VMT to the model. The process uses

MOVES2010a, the officially released emissions model that was obtained directly from EPA.

The MOVES inputs prepared by PPSUITE include the following:

 Vehicle Type VMT

.

 Vehicle Population

.

 VMT fractions

.

 Average speed distributions

.

 Road Type Distribution

.

 Ramp Fractions

.

These files are text formatted files with a *.csv extension. The files are provided as input s within the

MOVES county data importer

. In addition the remaining MOVES input data including temperatur es,

I/M programs, fuel and vehicle ages are prepared manually outside of the PPSUITE process.

The MOVES county importer is run in batch mode. This program converts all data files into the MYSQL

formats used by the MOVES model. At that point a MOVES run specification file (*.mrs) is created

which specifie s options and key data locations for the run. MOVES is then executed in batch mode

.

MOVES can be executed using either the inventory or rate

- based approaches. For this highway

emissions inventory, MOVE S is applied using the inventory

- based approach. Under this method, actual

VMT and population are provided as input s to the model ; MOVES is responsible for producing the total

emissions for the region. Under the rate

- based approach, MOVES would produce e mission factors , after

which PPSUITE would apply the emission factors to the link data and calculate total regional emissions.A

ppendix D

- 1 18 

# RESOURCES

MO VES model

Modeling Page within EPA’s Office of Mobile Sources Website

(http://www.epa.gov/omswww/models.htm) contains a downloadable model, MO VES users guide and

other information.

Motor Vehicle Emission Simulator, User Guide for MOVES2010a, EPA

- 420

- B

- 10

- 036, August 2010.

Policy Guidance on the Use of MOVES2010 and Subsequent Minor Revisions for State Implem entation

Plan Development, Transportation Conformity, and Other Purposes , US EPA Office of Transportation

and Air Quality , EPA

- 420

- B

- 12

- 010, April 2012.

Using MOVES to Prepare Emission Inventories in State Implementation Plans and Transportation

Conformi ty: Technical Guidance for MOVES2010, 2010a and 2010b . US EPA Office of Transportation

and Air Quality , EPA

- 420

- B

- 12

- 028, April 2012.

Traffic Engineering

Highway Capacity Manual, Transportation Research Board, presents current knowledge and techniques

fo r analyzing the transportation system.

Traffic Data Collection and Factor Development Report, 200 8 Data, Pennsylvania Department of

Transportation, Bureau of Planning and Research.

Traffic Data Collection and Factor Development Report, 2011 Data, Pennsylvania Department of

Transportation, Bureau of Planning and Research.A

ppendix D

- 1 19 

# Highway Vehicle Inventory Glossary

AADT: Average Annual Daily Traffic, average of ALL days.

AWDT: Average Weekday Daily Traffic

.

Basic emission rates: MOBILE emission rates based on the applicable Federal emission standards and

the emission control technologies characterizing the fleet in various model years.

Emission rate or factor: E xpresses the amount of pollution emitted per unit of activity. For highwa y

vehicles, usually in grams of pollutant emitted per mile driven.

FC: Functional code, applied in data management to road segments to identify their type (freeway, local,

etc.)

.

Fuel volatility: The ability of fuel components to evaporate, thus ente ring the atmosphere as pollution.

Fuel volatility is usually measured as Reid Vapor Pressure (RVP) in pounds per square inch. The lower

the RVP, the less volatile the fuel.

Growth factor: Factor used to convert volumes to future years

.

HPMS: Highway Performance Monitoring System, PENNDOT’s official source of highway information

and a subset of RMS.

I/M: Vehicle emissions inspection/maintenance programs ensure that vehicle emission controls are in

good working order throughout the life of the vehicle . The programs require vehicles to be tested for

emissions. Most vehicles that do not pass must be repaired.

MOBILE: The model EPA has developed and which Pennsylvania uses to estimate emissions from

highway vehicles.

MOVES: The latest model EPA has developed with which Pennsylvania uses to estimate emissions from

highway vehicles.

Pattern data: Extrapolations of traffic patterns (such as how traffic volume on road segment types varies

by time of day, or what kinds of vehicles tend to use a road segment type) from segments with observed

data to similar segments.

PPSUITE: Post

- Processor for Air Quality, a set of programs that estimate speeds and processes MOBILE

emission rates.

RMS: Roadway Management System, a database maintained by PENNDOT fr om traffic counts and field

visits

.

Segment ( also referred to as link) : D i vision of roadway in the PENNDOT Roadway Management

System. Usually represents 0.5 mile segments of roadway.

UR: Urban/rural code, applied in data management to identify whether a road segment is urban, small

urban or rural.A

ppendix D

- 1 20 

### VHT: V ehicle hours traveled

.

VMT: V ehicle miles traveled. In modeling terms, it is the simulated traffic volumes times link length.

Veh icle Type : One of eight types, distinguished primarily by fuel type and/or weight, used in MOBILE

modeling.

Source Type : One of thirteen types, distinguished primarily by weight, used in MOVES modeling.

Road Type: Functional code, applied in data man agement to road segments to identify their type

(rural/urban highways, rural/urban arterials, etc.)

County Data Manager: U ser interface developed to simplify importing specific local data for a single

county or a user

- defined custom domain without requir ing direct interaction with the underlying MySQL

database.

# APPENDIX D 2

Highway Emissions Estimates

2007, 2011, 2017, 2025

(Provided in Electronic Form Only)

Bureau of Air Quality

Department of Environmental Protection

### [ This page intentionally left blank

. ]

# APPENDIX D-2

Pittsburgh-Beaver Valley Area Emission Summary Tables

A ppendix D-2-1

2002 Annual Emissions

Emission Summar y

Emission Summary by Road Type

Emission Summary by Source Typ e

Emission Summary by Proces s



### A ppendix D-2-2

2007 Annual Emissions

Emission Summar y

Emission Summary by Road Type

Emission Summary by Source Typ e

Emission Summary by Proces s



### A ppendix D-2-3

2011 Annual Emissions

Emission Summar y

Emission Summary by Road Type

Emission Summary by Source Typ e

Emission Summary by Proces s



### A ppendix D-2- 4

2017 Annual Emissions

Emission Summar y

Emission Summary by Road Type

Emission Summary by Source Typ e

Emission Summary by Proces s



### A ppendix D-2-5

2025 Annual Emissions

Emission Summar y

Emission Summary by Road Type

Emission Summary by Source Typ e

Emission Summary by Proces s

# APPENDIX D 3

MOVES Input Parameter Summary

Bureau of Air Quality

Department of Environmental Protection

### [ This page intentionally left blank

. ]

# APPENDIX D

- 3

Pittsburgh

- Beaver Valley Area MOVES Sample Input FilesAppendix D

- 3 1 

# MOVES Run Specification File Settings

Sample xml file format

<moves>

<importer mode="county" >

<filters>

<geographicselections>

<geographicselection type="COUNTY" key="42003" description="PENNSYLVANIA

- Allegheny County"/>

</geographicselections>

<timespan>

<year key="2025"/>

<month id="00"/>

<day id="2"/>

<day id="5"/>

<beginhour id="1"/>

<endhour id="24"/>

<aggregateBy key="Hour"/>

</timespan>

<onroadvehicleselections >

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="62" sourcetypename="Combination Long

- haul Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="61" sourcet ypename="Combination Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="41" sourcetypename="Intercity Bus"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="32" sourcetypename="Light Commercial Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="54" sourcetypename="Motor Home"/>

<onroadvehicleselection fueltypeid="2" fueltypedes c="Diesel Fuel" sourcetypeid="11" sourcetypename="Motorcycle"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="21" sourcetypename="Passenger Car"/>

<onroadvehicleselection fueltypeid="2" fuel typedesc="Diesel Fuel" sourcetypeid="31" sourcetypename="Passenger Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="51" sourcetypename="Refuse Truck"/>

<onroadvehicleselection fueltype id="2" fueltypedesc="Diesel Fuel" sourcetypeid="43" sourcetypename="School Bus"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="53" sourcetypename="Single Unit Long

- haul Truck"/>

<onroadvehi cleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="52" sourcetypename="Single Unit Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="42" sourcetypename="Transit Bus"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="62" sourcetypename="Combination Long

- haul Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="61" sourcetypename= "Combination Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="41" sourcetypename="Intercity Bus"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid=" 32" sourcetypename="Light Commercial Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="54" sourcetypename="Motor Home"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sour cetypeid="11" sourcetypename="Motorcycle"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="21" sourcetypename="Passenger Car"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sou rcetypeid="31" sourcetypename="Passenger Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="51" sourcetypename="Refuse Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline " sourcetypeid="43" sourcetypename="School Bus"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="53" sourcetypename="Single Unit Long

- haul Truck"/>

<onroadvehicleselection fueltypeid="1" fueltyp edesc="Gasoline" sourcetypeid="52" sourcetypename="Single Unit Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="42" sourcetypename="Transit Bus"/>

</onroadvehicleselections>

<o ffroadvehicleselections>

</offroadvehicleselections>

<offroadvehiclesccs>

</offroadvehiclesccs>

<roadtypes>

<roadtype roadtypeid="1" roadtypename="Off

- Network"/>

<roadtype roadtypeid="2" roadt ypename="Rural Restricted Access"/>

<roadtype roadtypeid="3" roadtypename="Rural Unrestricted Access"/>

<roadtype roadtypeid="4" roadtypename="Urban Restricted Access"/>

<roadtype roadtypeid="5" roadtypename= "Urban Unrestricted Access"/>

</roadtypes>

</filters>

<databaseselection servername="localhost" databasename="42003_2025_00_25_avgann_mi"/>

<agedistribution>Appendix D

- 3 2 <description>< ![CDATA[]]></description>

<parts>

<sourceTypeAgeDistribution>

<filename>C: \ PAMOVES11 \ MOVESInputs \ AgeDistribution \ 11Reg_RepCty \ 2025 \ 42019_2025_SourceTypeAgeDistr ibution.csv</filename>

</sourceTypeAgeDistribution>

</parts>

</agedistribution>

<avgspeeddistribution>

<description><![CDATA[]]></description>

<parts>

<avgSpeedDistribution>

<filename>C: \ PAMOVES11 \ Out \ 2025_Annual_PM25_PGH_SA \ \ 42003_2025_00_25_avgann \ CDM \ avgSpeedDistribution.csv</filename>

</avgSpeedDistribution>

</parts>

</avgspeeddistribution>

<imcoverage>

<description><![CDATA[]]></description>

<parts>

<imcoverage>

<filename>C: \ PAMOVES11 \ MOVESInputs \ IM \ 42000_2025_IMCoverage.csv</filename>

</imcoverage>

</parts>

</imcoverage>

<fuel>

<description><![CDATA[]]></description>

<parts>

<FuelSupply>

<filename>C: \ PAMOVES11 \ MOVESInputs \ Fuel \ MOVES2010a \ 42000_2012_FuelSupply.csv</filename>

</FuelSupply>

<FuelFormulation>

<filename>C: \ PAMOVES11 \ MOVESInputs \ Fuel \ 42000_FuelFormulation_MOVES2010a.csv</filename>

</FuelFormulation>

</parts>

</fuel>

<zonemonthhour>

<description><![CDATA[]]></description>

<parts>

<zoneMonthHour>

<filename>C: \ PAMOVES11 \ MOVESIn puts \ Meteorology \ 2008 \ 42003_2008_met.csv</filename>

</zoneMonthHour>

</parts>

</zonemonthhour>

<roadtypedistribution>

<description><![CDATA[]]> </description>

<parts>

<roadTypeDistribution>

<filename>C: \ PAMOVES11 \ Out \ 2025_Annual_PM25_PGH_SA \ \ 42003_2025_00_25_avgann \ CDM \ roadTypeDistribution.csv</filename >

</roadTypeDistribution>

</parts>

</roadtypedistribution>

<sourcetypepopulation>

<description><![CDATA[]]></description>

<parts>

<sourceTypeYear>

<filename>C: \ PAMOVES11 \ Out \ 2025_Annual_PM25_PGH_SA \ \ 42003_2025_00_25_avgann \ CDM \ SourceTypePopulation.csv</filename>

</sourceTypeYear>

</parts>

</sourcetypepopulation>

<rampfraction>

<description><![CDATA[]]></description>

<parts>Appendix D

- 3 3 <roadType>

<filename>C: \ PAMOVES11 \ MOVESInputs \ RampFraction \ rampfraction_defaults.csv</filename>

</roadType>

</parts>

</rampfraction>

<vehicletypevmt>

<description><![CDATA[]]></description>

<parts>

<hpmsVTypeYear>

<filename>C: \ PAMOVES11 \ Out \ 2025_An nual_PM25_PGH_SA \ \ 42003_2025_00_25_avgann \ CDM \ hpmsVTypeYear.csv</filename>

</hpmsVTypeYear>

<monthvmtfraction>

<filename>C: \ PAMOVES11 \ MOVESInputs \ MonthD ayHourFractions \ 2025_MonthFraction \ 42003_2025_MonthVMTFraction.csv</filename>

</monthvmtfraction>

<dayvmtfraction>

<filename> C: \ PAMOVES11 \ MOVESInputs \ MonthDayHourFractions \ dayvmtfraction_avgday.csv</filename>

</dayvmtfraction>

<hourvmtfraction>

<filename>C: \ PAMOVES11 \ Out \ 2025_ Annual_PM25_PGH_SA \ \ 42003_2025_00_25_avgann \ CDM \ hourvmtfraction.csv</filename>

</hourvmtfraction>

</parts>

</vehicletypevmt>

</importer>

</moves>



### Sample mrs file format

<r unspec>

<description><![CDATA[MOVES2010 RunSpec Created by CENTRAL4 Scenario: ALLE 2025 ANNAVG avgann Emission Inventory with user's data]]></description>

<modelscale value="INV"/>

<modeldomain value="SINGLE"/>

<geographicselections>

<geographicselection type="COUNTY" key="42003" description="PENNSYLVANIA

- Allegheny County"/>

</geographicselections>

<timespan>

<year key="2025"/>

<month id="1"/>

<month id="2"/>

<month id="3"/>

<month id="4"/>

<month id="5"/>

< month id="6"/>

<month id="7"/>

<month id="8"/>

<month id="9"/>

<month id="10"/>

<month id="11"/>

<month id="12"/>

<day id="2"/>

<day id="5"/>

<beginhour id="1"/>

<endhour id="24"/>

<aggregateBy key="Hour"/>

</timespan>

<onroad vehicleselections>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="11" sourcetypename="Motorcyc le"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="21" sour cetypename="Passenger Car"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="31" sourcetypename="Passenge r Truck"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcety peid="32" sourcetypename="Light Commercial Truck"/>Appendix D

- 3 4 <onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="11" sourcetypename="Motorcycle"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="21" source typename="Passenger Car"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="31" sourcetypename="Passenger Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="32" sourcetypename="Light Commercial Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="11" sourcetypename="Motorcycle"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="21" sourcetypename="Passenger Car"/>

<onroadvehi cleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="31" sourcetypename="Passenger Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="32" sourcetypename="Light Commercial Truck"/>

<onroadvehicleselection fu eltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="41" sourcetypename="Intercity Bus"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="42" sourcetypename="Transit Bus"/>

<onroadvehiclese lection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="43" sourcetypename="School Bus"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="41" sourcetypename="Intercity Bus"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="42" sourcetypename="Transit Bus"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="43" sourcetypename="School Bus"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc ="Gasoline" sourcetypeid="41" sourcetypename="Intercity Bus"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="42" sourcetypename="Transit Bus"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="43" sourcetypename="School Bus"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="51" sourcetypename="Refuse T ruck"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcety peid="52" sourcetypename="Single Unit Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="53" sourcetypename="Single U nit Long

- haul Truck"/>

<onroadvehicleselection fueltypeid="3" fueltypedes c="Compressed Natural Gas (CNG)" sourcetypeid="54" sourcetypename="Motor Home"/>

<onroadvehicleselection fueltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="61" sourcetypename="Combinat ion Short

- haul Truck"/>

<onroadvehicleselection fu eltypeid="3" fueltypedesc="Compressed Natural Gas (CNG)" sourcetypeid="62" sourcetypename="Combination Long

- haul Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="51" sourcetypename="Refuse Truck"/>

<onroadvehiclesele ction fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="52" sourcetypename="Single Unit Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="53" sourcetypename="Single Unit Long

- haul Truck"/>

< onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="54" sourcetypename="Motor Home"/>

<onroadvehicleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="61" sourcetypename="Combination Short

- haul Truck"/>

<onroadvehi cleselection fueltypeid="2" fueltypedesc="Diesel Fuel" sourcetypeid="62" sourcetypename="Combination Long

- haul Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="51" sourcetypename="Refuse Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="52" sourcetypename="Single Unit Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="53" sourcetypename="Single Unit Long

- haul Truck"/>

<onroadvehicleselectio n fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="54" sourcetypename="Motor Home"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="61" sourcetypename="Combination Short

- haul Truck"/>

<onroadvehicleselection fueltypeid="1" fueltypedesc="Gasoline" sourcetypeid="62" sourcetypename="Combination Long

- haul Truck"/>

</onroadvehicleselections>

<offroadvehicleselections>

</offroadvehicleselections>

<offroadvehiclesccs>

</offroadvehiclesccs>

<roadtypes>

<roadtype roadtypeid="1" roadtypename="Off

- Network"/>

<roadtype roadtypeid="2" roadtypename="Rural Restricted Access"/>

<roadtype roadtypeid="3" roadtypename="Rural Unrestricted Access"/>

<roadtype roadtypeid="4" ro adtypename="Urban Restricted Access"/>

<roadtype roadtypeid="5" roadtypename="Urban Unrestricted Access"/>

</roadtypes>

<pollutantprocessassociations>

<pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" pr ocesskey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="2" processname="Start Exhaust" />

<pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="16" processname="Crankcase Sta rt Exhaust"/>

<pollutantprocessassociation pollutantkey="2" pollutantname ="Carbon Monoxide (CO)" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="2" pollutantname="Carbon Monoxide (CO)" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="2" processname="Start Exhaust"/>

<pollutantprocessassociation po llutantkey="3" pollutantname="Oxides of Nitrogen" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantp rocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="17" processname="Crankcase Extended Idle Ex haust"/>

<pollutantprocessassociation pollutantkey="3" pollutantname="Oxides of Nitrogen" processkey="90" processname="Extended Idl e Exhaust"/>

<pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Methane Hydrocarbons" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Methane Hydrocarbons" processkey="2" proce ssname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Methane Hydrocarbons" processkey="11" processname="Evap Permeation"/>

<pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Methane Hydrocarbons" process key="12" processname="Evap Fuel Vapor Venting"/>Appendix D

- 3 5 <pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Methane Hydrocarbons" processkey="13" processname="Evap Fuel Leaks"/>

<pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Metha ne Hydrocarbons" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Methane Hydrocarbons" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutan tkey="79" pollutantname="Non

- Methane Hydrocarbons" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="79" pollutantname="Non

- Methane Hydrocarbons" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="2" processname="St art Exhaust"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="11" processname="Evap Pe rmeation"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="12" processname="Evap Fuel Vapor Venting"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="13" processname="Evap Fu el Leaks"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hyd rocarbons" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="16" processname="Crankca se Start Exhaust"/>

<pollutantprocessassociation pollutantkey= "1" pollutantname="Total Gaseous Hydrocarbons" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="1" pollutantname="Total Gaseous Hydrocarbons" processkey="90" processname="Extende d Idle Exhaust"/>

<p ollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="1" processname="Running E xhaust"/>

<pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="2" processname="Sta rt Exhaust"/>

<pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="11" processname="Evap P ermeation"/>

<pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="12 " processname="Evap Fuel Vapor Venting"/>

<pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="13" processname="Evap F uel Leaks"/>

<pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="16" processname="Crankc ase Start Exhaust"/>

<pollutantprocessassociation poll utantkey="87" pollutantname="Volatile Organic Compounds" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="87" pollutantname="Volatile Organic Compounds" processkey="90" processname="Extend ed Idle Ex haust"/>

<pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5

- Total" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5

- Total" processkey= "2" processname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5

- Total" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5

- Total" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5

- Total" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessa ssociation pollutantkey="110" pollutantname="Primary Exhaust PM2.5

- Total" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="116" pollutantname="Primary PM2.5

- Brakewear Particulate" processkey="9" processna me="Brakewear"/>

<pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5

- Elemental Carbon" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5

- Elemental Carbon " processkey="2" processname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5

- Elemental Carbon" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="112" pollut antname="Primary PM2.5

- Elemental Carbon" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5

- Elemental Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust "/>

<pollutantprocessassociation pollutantkey="112" pollutantname="Primary PM2.5

- Elemental Carbon" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5

- Organic Carbon" proces skey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5

- Organic Carbon" processkey="2" processname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2. 5

- Organic Carbon" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5

- Organic Carbon" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociatio n pollutantkey="111" pollutantname="Primary PM2.5

- Organic Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="111" pollutantname="Primary PM2.5

- Organic Carbon" processkey="90" processname=" Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5

- Sulfate Particulate" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5

- Sulfa te Particulate" processkey="2" processname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5

- Sulfate Particulate" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5

- Sulfate Particulate" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5

- Sulfate Particulate" processkey="17" processname=" Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="115" pollutantname="Primary PM2.5

- Sulfate Particulate" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="117" pollutantname="Prim ary PM2.5

- Tirewear Particulate" processkey="10" processname="Tirewear"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="1" processname="Running E xhaust"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="2" processname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociatio n pollutantkey="100" pollutantname="Primary Exhaust PM10

- Total" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10

- Total" processkey="2" processname="Start Exhaust"/>

<po llutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10

- Total" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10

- Total" processkey="1 6" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutantkey="100" pollutantname="Primary Exhaust PM10

- Total" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="100" polluta ntname="Primary Exhaust PM10

- Total" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="106" pollutantname="Primary PM10

- Brakewear Particulate" processkey="9" processname="Brakewear"/>

<pollutantprocessasso ciation pollutantkey="102" pollutantname="Primary PM10

- Elemental Carbon" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10

- Elemental Carbon" processkey="2" processname="Start Exha ust"/>

<pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10

- Elemental Carbon" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10

- Elemental Carbon" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutantkey="102" pollutantname="Primary PM10

- Elemental Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantk ey="102" pollutantname="Primary PM10

- Elemental Carbon" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10

- Organic Carbon" processkey="1" processname="Running Exhaust"/>

<pol lutantprocessassociation pollutantkey="101" pollutantname="Primary PM10

- Organic Carbon" processkey="2" processname="Start Exhaust"/>Appendix D

- 3 6 <pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10

- Organic Carbon" processkey="15" processname ="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10

- Organic Carbon" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10

- Organic Carbon" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="101" pollutantname="Primary PM10

- Organic Carbon" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociat ion pollutantkey="105" pollutantname="Primary PM10

- Sulfate Particulate" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10

- Sulfate Particulate" processkey="2" processname="Start Ex haust"/>

<pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10

- Sulfate Particulate" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10

- Sulfate Particulate" processkey="16" processname="Crankcase Start Exhaust"/>

<pollutantprocessassociation pollutantkey="105" pollutantname="Primary PM10

- Sulfate Particulate" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassocia tion pollutantkey="105" pollutantname="Primary PM10

- Sulfate Particulate" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="107" pollutantname="Primary PM10

- Tirewear Particulate" processkey="10" processname ="Tirewear"/>

<pollutantprocessassociation pollutantkey="116" pollutantname="Primary PM2.5

- Brakewear Particulate" processkey="9" processname="Brakewear"/>

<pollutantprocessassociation pollutantkey="117" pollutantname="Primary PM2.5

- Tirewear Particulate " processkey="10" processname="Tirewear"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="1" processname="Running E xhaust"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Con sumption" processkey="2" processname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="31" pollutantnam e="Sulfur Dioxide (SO2)" processkey="1" processname="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="2" processname="Start Exhaust "/>

<pollutantprocessassociation pollutantkey="31" pollutan tname="Sulfur Dioxide (SO2)" processkey="15" processname="Crankcase Running Exhaust"/>

<pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="16" processname="Crankcase St art Exhaust"/>

<pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="17" processname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="31" pollutantname="Sulfur Dioxide (SO2)" processkey="90" processname="Extended Idl e Exhaust"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="1" processname="Running E xhaust"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="2" processname="Star t Exhaust"/>

<pollutantprocessassociation pollutantkey="91" pollutantname="Total Energy Consumption" processkey="90" processname="Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="1" processna me="Running Exhaust"/>

<pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="2" processname="Start Exhaust"/>

<pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="15" processname="Crank case Running Exhaust"/>

<pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="16" processname="Crankcase Start Exh aust"/>

<pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="17" proces sname="Crankcase Extended Idle Exhaust"/>

<pollutantprocessassociation pollutantkey="30" pollutantname="Ammonia (NH3)" processkey="90" processname="Extended Idle Exhau st"/>

</pollutantprocessassociations>

<databaseselections>

<databaseselection s ervername="localhost" databasename="early_NLEV" description=""/>

<databaseselection servername="localhost" databasename="calevii08" description=""/>

</databaseselections>

<inputdatabase servername="" databasename="" description=""/>

< uncertaintyparameters uncertaintymodeenabled="false" numberofrunspersimulation="0" numberofsimulations="0"/>

<geographicoutputdetail description="COUNTY"/>

<outputemissionsbreakdownselection>

<modelyear selected="false"/>

<fueltype selected="false"/>

<emissionprocess selected="true"/>

<onroadoffroad selected="true"/>

<roadtype selected="true"/>

<sourceusetype selected="true"/>

<movesvehicletype selected="false"/>

<onroadscc selected="false"/>

<offroadscc selected="false"/>

<estimateuncertainty selected="false" numberOfIterations="2" keepSampledData="false" keepIterations="false"/>

<sector selected="false"/>

<engtechid selected="false"/>

<hpclass selected="false"/>

</outputemissionsb reakdownselection>

<outputdatabase servername="localhost" databasename="42003_2025_00_25_avgann_mo" description=""/>>

<outputtimestep value="Month"/>

<outputvmtdata value="true"/>

<outputsho value="true"/>

<outputsh value="true"/>

<outputshp value="true"/>

<outputshidling value="true"/>

<outputstarts value="true"/>

<outputpopulation value="true"/>

<scaleinputdatabase servername="localhost" databasename="42003_2025_00_25_avgann_mi" description=""/>

< pmsize value="0"/>

<outputfactors>

<timefactors selected="true" units="Hours"/>

<distancefactors selected="false" units="Miles"/>Appendix D

- 3 7 <massfactors selected="false" units="Grams" energyunits="Million BTU"/>

</outputfactor s>

<savedata>

</savedata>

<donotexecute>

</donotexecute>

<generatordatabase shouldsave="false" servername="" databasename="" description=""/>

<donotperformfinalaggregation selected="false"/>

<lookuptableflags scenarioid=" " truncateoutput="false" truncateactivity="false"/>

<internalcontrolstrategies>

<internalcontrolstrategy classname="gov.epa.otaq.moves.master.implementation.ghg.internalcontrolstrategies.rateofprogress.Rat eOfProgressStrategy"><![CDATA[

useParameters N o

]]></internalcontrolstrategy>

</internalcontrolstrategies>

</runspec>

# APPENDIX D 4

MOVES Input/Output Files

(Provided in Electronic Form Only)

Bureau of Air Quality

Department of Environmental Protection

### [ This page intentionally left blank

. ]