# APPENDIX 5 C

Development of MANE-VU Mobile Source Projection Inventories

# Technical Memorandum



# Development of MANE-VU Mobile Source Projection Inventories for SMOKE/MOBILE6 Application

Jun 2006, NESCAUM

I. Background

The MANE-VU Emissions Inventory workgroup chos e to utilize in-house expertise to develop future year mobile source emission estimates for use in Ozone, PM 2.5 

# , and Regional Haze SIP modeling. Jung-Hun Woo, NESCAUM, and Me gan Schuster, MARAMA compiled all the information necessary to run Mobile6 with Spar se Matrix Operator Kernel Emissions (SMOKE) based on the state submitted data. The purpose of this document is to describe how member states and NESCAUM/MARAMA pr epared the mobile source activity data (i.e. non-link based VMT & Speed), Mobile6 scenario input file s, and accompanying files in SMOKE/MOBILE6 format in support of future year projection inventory development.



# II. Procedure

2.1. Base year (Y2002) inventory file

The MANE-VU 2002 base year SMOKE/M6-ready mob ile source files served as a starting point for projection inventory developm ent; hence, the procedures em ployed for the development of these files are summarized here. E.H Pechan, a contractor for MANE-VU, compiled MANEVU 2002 mobile source inventories. The onroad emissions invent ory was compiled from data supplied by the MANE-VU State agencies in th e form of onroad emissions input data or emissions inventories either directly to M ANE-VU or to EPA through their CERR submittal. States provided information in one or more of the following ways: (1) an onroad emission inventory submittal to EPA, (2) MOBILE6 inputs and VMT data in National Mobile Inventory Model (NMIM) format to EPA, (3) portions of MOBILE6 inputs or full MOBILE6 input files and supporting files plus VMT to EPA, or (4 ) portions of MOBILE6 inputs or full MOBILE6 input files and supporting files pl us VMT to MANE-VU. Different procedures were followed in developing the MANE-VU 2002 onroad emission i nventory depending upon how the data were submitted. All States provided information on 2002 onroad activity in the form of vehicle miles traveled (VMT) estimates, although the level of de tail of the VMT data varied by State. After integration of all these data, Pechan compile d onroad mobile source files in a SMOKE/Mobile6 ready format.

2.2. Preparing technical guidance to create SMOKE/Mobile6 ready information

As described above, States had the ability a nd experience to develop their mobile source inventory data in NMIM, stand- alone Mobile6, and emissions i nventory format. They, however,

# were not familiar with procedures for integratin g files and converting them into a model ready format. To assist the State workgr oup in the creation of an inventor y in (as close as possible to) the SMOKE/Mobile6–ready format, NESCAUM/M ARAMA developed a technical guidance

document ( http://www.marama.org/visibility/Inventory %20Summary/FutureEmissionsInventory.htm ). In the document, we also explained how State workgroup could download the year 2002 files ( ftp.marama.org ) and update them to create projection inventory files.

In the technical guidance, States were reque sted to supply NESCAUM and MARAMA with the data described below, under Required Data. St ates also had the option to supply NESCAUM and MARAMA with the information listed under Optional Data.

REQUIRED DATA:



# 1) SMOKE/IDA Activity File a. Go to MARAMA FTP site (above), click on Onroad/ Final Smoke Files/
MANEVU_2002_mbinv.txt b. Open the MANEVU_2002_mbinv.txt file c. Delete all data that is not your state’s. d. Update file with new header and annual VMT by SCC for 2009
e. Name file: state_2009_mbinv.txt f. Repeat steps ‘b’ thr ough ‘e’ for years 2012 and 2018

2) MOBILE6 input scenario files a. Go to MARAMA ftp site, click on MANE-VU Onroad/ Final Smoke Files/ MANEVU_2002_SMOKE_M6_InputFiles_12032004.zip /m6_2002/month/statecounty.in b. Provide updated statecounty.in files for each month and year 2009, 2012 and 2018 c. Use same naming convention as the 2002 files – statecounty.in

OPTIONAL DATA:



# 1) If a state wants to, they can update registration data to either 2004 or 2005

a. Go to MARAMA FTP site - Onroad/ Final Smoke Files/MANEVU_2002_SMOKE_M6_ExternalFiles.zip b. As an example, open file 0900002.reg (or any files with extension .reg) c. There is a long header followed by the real data. Real data starts at the line called REG DIST. (See example file below). d. States should update the registration data by vehicle class and age for 2004 or

2005. e. If you update this data and change the na me of the file, make sure the M6 input scenario file (required data from abov e) includes the correct file name for registration data (REG DIST).

# 2.3. States data submittal and compiling future inventory

As States submitted their projected mobile sour ce files as listed above , NESCAUM started to integrate Y2018 files and convert them into regional (i.e. M ANE-VU) files. The following subsections summarize the compilation process for act ivity input, scenario i nput files, external

files and other SMOKE related files.

1) Activity input data (VMT/Speed)

- All member states submitted VMT and speed data. There were minor issues in data

formatting but nothing major.

- DE and MA re-submit VMT file at Oc tober, 2005 (MA change 2002 VMT, too) - Merge update 2002 MBINV file, ptpro/ptref, scenario input files for CT and NJ 2) Scenario input files

- VT used the same input file for all the c ounties. So, only 36 input files (i.e. 12months * 3

future years) were provided. VT set 050001 as a reference county (MCREF). - VT uses January as reference month for August processing. VT has confirm that they want to

change reference month for Apr-Sep as July instead of January. - ME submitted all monthly data in a file. NESCAUM split it by month. - MA submitted only three input files (Avg Summer day, Typ Ozon da y, Avg Winter day)

which were submitted to PECHAN to develop ba se year input files. NESCAUM created *.in files by copying MANE-VU 2002 base-year *.in f iles, then change years into 2009/2012/2018

and the link to the new external file s (LEV2CERT.D, LEV2EVAP.D, LEV2EXH.D).

- CT submitted *.IN files on 9/22/2005. The “> I/M DESC” file path had been removed. - RI scenario input files have 044yyc.IN na me convention that are supposed to be

044ccc.IN(yy stands for 2digit year and ccc stan ds for 3digit county FIPS). They are renamed and populated for 12months. - Some states(MD) put "REBUILT EFFECTS" after “SCENARIO RECORD” line. They were

moved ahead of it. - PA put “ANTI-Tamp” records in external files that need to be in Scenario input files.

NESCAUM wrote a Fortran code (p a_input_4_override.f) and a C-shell script(cp_antitamp_4_pa.csh) to put those records in scenario input files - NJ has 2012 year tag in 2009 scenario input files. NESCAUM put them back to 2009. - For 2002 scenario input files update (10/27/2006), CT puts 0.07 Re build effect, NJ didn't put

any. So, I put 0.1 to NJ 2002 input files. - Putting future year rebuild effect is a m odeling decision that needs to be a constant

throughout the region. So NESCAU M didn’t correct that in f ile compilation. Modelers’ put 10% for the base year (2002) and 90% for the future years(2009/2012/2018). NYSDEC put 0.9 into year 2009 files and NESCAUM put 0.9 in to year 2018 files before SMOKE/Mobile6 processing. 3) External files

- VT uses some of NY state external files (e.g. NYLEV2.D, NYL2EXH.D, NYL2EVAP.D,

and NYL2CERT.D) - RI didn't provide any future-specific extern al files. 2002 MANE-VU M6 external files were

used

# - MA and ME used the same named files whic h have identical contents to each other: LEV2CERT.D, LEV2EVAP.D, and LEV2EXH.D - DE, PA, and NJ submitted the same named files wh ich have identical contents to each other:

NLEVNE.D - DC file produce warnings (but not errors) from SMOKE/Mobile6 test run “User Supplied HC IM240 Cutpoint of 0.500 for year 1 and Vehicle Type 1 is Too Low

and has been Reset to 0.80 g/mi.” Consulted w ith DC and get a confirm that it’s ok to use it

as-is.

4) Other SMOKE related files

- MCREF/MVREF Update MANEVU_2002_mcref.txt for Ma ine because Penobscot county (23019) was not

found from MAINE_pointerfile.x ls. Tammy Gould @ Maine conf irmed that Penobscot (019) has to be added where Piscataquis (0 21) is. Correct this problem on both MANEVU_2018_mcref.txt and MAINE_pointer file.xls. MANEVU_2018_mvref.txt is updated by deleting non-ref counties in ME.

- MTPRO/MTREF Add CT and NJ's temporal pr ofile/x-ref to 2018 MANEVU files



# III. Sample model run

Even though NESCAUM had not run SMOKE/Mobile 6 for any of the complete projection years, we ran a day worth of each year: 1) to test compatibility of compiled data with SMOKE/Mobile6 system and 2) to examine trends in submitted projection data. As seen in the Figure 1 and Figure 2, VMT increases 10~20% compared to the base year (i.e. year 2002) for the most of states whereas speed remains the same except for NY and PA.

0 100 200 300 400 500 600

Connect i cut Del awar e

Di

str

i ct

of

C

o l um bi a M ai ne M ar y l a n d M assac h usett s

N

ew

Ham p sh

i r e New Jer

sey

N

ew Y o r k Pennsyl vani a Rhod e

I sl

an

d

V e r m ont**M i l** **l i** **ons**VM T



# VM T_02 VM T_09 VM T_12 VM T_18

## 0 50 100 150 200 250 300 350

C

o n n e c t i c u t

D

e l a w

a r e

D

i s t r i c t

o f

C

o l u m

b i a

M a i n e

M a r y l a n d

M

a s s a c h

u s e t t s

N

e w

H

a m p

s h i r e

N

e w

J

e r s e y

N e w

Y

o r k

P

e n n s y l v a n i a

R

h

o d

e

I s l a n d

V e r m o

n t**Thousand s** Speed



# SPD_02 SPD_09 SPD_12 SPD_18



# Figure 1. VMT(upper) and Speed (lower) for one day (August 1) of year 2002, 2009, 2012, and

2018

0 200 400 600 800 1000 1200

C

o n n e c t i c u t

D

e l a w

a r e

D

i s t r i c t

o f

C

o l u m

b

i a

M a i n e

M a r y l a n d

M

a s s a c h

u s e t t s

N

e w

H

a m

p s h i r e

N

e w J

e r s e y

N

e w

Y

o r k

P

e n n s y l v a n i a

R

h

o d

e

I s l a n d

V e r m o

n tTPD



# NO x_02 NO x_09 NO x_12 NO x_18

## 0 1000 2000 3000 4000 5000 6000 7000 8000

Co

nn

ect

i cu

t

Del aw

ar

e

Di

st

r i ct

of

C

ol

um b i a M ai ne

M ar

yl

an

d

M

assa chuset t s

New Ham pshi r e

Ne

w

J er

se

y

N

ew

Yor

k Pennsyl vani a Rhode I sl

an

d

Ve r m on tTPD



# C O _02 C O _09 C O _12 C O _18



# Figure 2. NOx(upper) and CO (lower) emission s for one day (August 1) of year 2002, 2009, 2012, and 2018

Despite VMT increases, NO

x 

# and CO emissions decrease dramatically due to future-year control programs. Emissions decrease a bit mo re slowly after 2009 given fewer anticipated controls during post-2009 years.

NOx reductions seen from Figure 2 can be veri fied in the spatial (by county) NOx emission maps which were calculated using SMOKE/Mobile6 for August 1 of each year. As region wide emissions decreased by years, emissions from high emission areas (e.g. urban centers) decreased,

as well.Figure 3. Spatial distribution of emissions from SMOKE/Mobile6 (August 1, NOx)