# EMFAC2011

- SG

User’s Guide

September 19 , 2011PTSD

- MSAB Page 1 

# EMFAC2011

- SG

1.0 INTRODUCTION

EMFAC2011

- SG (Scenario Generator) is a new simplified tool that provides air quality planners, transportation planners, and other EMFAC users a tool for assessing emissions under different future growth scenarios. This includes conformity analyses of transportation plans and programs wit h the State Implementation Plans required by federal law, State Implementation Plan inventories, and alternative growth scenarios associated with regional transportation planning for greenhouse gas reductions

. EMFAC 2011

- SG takes the output from EMFAC 2011

- L DV and EMFAC 2011

- HD and applies scaling factors to estimate
emissions consistent with user

- defined vehicle miles of travel (VMT) and speeds. The EMFAC 2011

- SG module also estimates the benefits of Pavley

- I and LCFS.

EMFAC2011

- SG is developed in Microsoft ® Access platform, and replaces the functionalities of the WIS module in EMFAC for transportation conformity purposes. EMFAC2011

- SG is an external module that uses the inventory from
EMFAC2011

- LDV and EMFAC2011

- HD modules and scales the emissions based on changes in total VMT, VMT distribution by vehicle class, and speed distribution. EMFAC2011

- SG processes data only at a sub

- area level. Therefore, in order to process regional scenarios (State, Air Basin, Air District, MPO, County), the module needs to process all sub

Areas in its domain and aggregate the results. Therefore, for a single “Statewide” regional modeling scenario, the module will need to run and aggregate the results of all 69 sub

- areas (GAIs). Regional

- level outputs are aggregat ed as part of
module output. Therefore, the module will produce individual outputs for each GAI, but also produce the aggregated region

- level output (Statewide output). EMFAC2011

- SG uses the VMT

- weighted speed distribution at the daily level, and
allows u sers to generate MPO

- level outputs, in addition to the Statewide, Air Basin, Air District, County, and Sub

- Area level outputs. EMFAC2011

- SG inputs and outputs are generated in Microsoft Excel format (*.xls).PTSD

- MSAB Page 2

2.0 MODULE OPERATION AND LOGIC

Since transportation plans and policies are created by the local governments, the vehicle usage and speed profiles vary greatly at the sub

- area level (GAI or CoABDis). Therefore, the EMFAC2011

- SG module was also developed to process speed data at the sub

- area level.

EMFAC2011

- SG uses the combined Burden

- level outputs from the two module s ( EMFAC2011

- LDV and EMFAC2011

- HD) disaggregated by Model

- year and Speed (5

- MPH increments) as the base inventory. The base inventories are pre

processed by sub

- area, cal endar year and season, and are available to download along with the SG package. Users are required to download the inventories for the regions of interest to their computers.

Each sub

- area modeling case is called a „Scenario‟ (defined by sub

- area, calen dar year, and season). When a us er models a scenario, the EMFAC2011

- SG module imports the data from the corresponding base inventory file, and disaggregates the data into different parameters as shown in Figure 1

.

Figure 1 Schematic of EMFAC2011

- SG LogicPTSD

- MSAB Page 3

Based on the modeling parameters, SG uses the following equations to calculate the emissions by Vehicle Category (VC): [ ∑ ]

Where:PTSD

- MSAB Page 4

3.0 INPUT DATA ELEMENTS

EMFAC2011

- SG has three main inputs, and one optional input:

 Base Inputs

 VMT Distribution by Vehicle Category

 Speed Profiles

 Regional Scenario (optional)

The mod eling parameters in all three inputs are defined at the sub

- area level. In order to correlate the data in the three input sheets, the module identifies each case as a “Scenario”. In order to process regional scenarios, users are required to classify all the “scenarios” into groups; the module processes each scenario individually and aggregates data by groups
at the end of module execution.

User Input #1: Base Inputs

 This is the most important input for the module . It contains scenario definitions that include sub

- area, calendar year and season, and selections for VMT profile ( module defaults or user defined), VMT by Vehicle Category ( module defaults or user defined), and Speed distribution type ( module defaults or user defined) for each scenario.

o If the “VMT profile” entry for the scenario is User defined, then the user also needs to enter the “New Total VMT” data (miles/day)

 Input Variables:

a. Group (Integer)

– Identifier for grouping/aggregating the scenarios
b. Area (Text)

– Denotes the Area/Region name for each group

c. Scenario (Integer)

– Index representing order of modeling scenario
d. Sub

- Area (Text)

 Options: Selected from a list of 69 sub

- areas (CoABDis or GAI)

e. CalYr (Calendar year)

 Options: Any calendar year between 1990 and 2035PTSD

- MSAB Page 5

f. Season (Text)

 Options: “Annual”, “Summer”, or “Winter”

g. Title (Text)
h. VMT Profile (Text)

 Options: “Default” ( module default) or “User”(user

- defined)

i. VMT by Vehicle Category (Text)

 Options: “Default” ( module default) or “User”(user

- defined) j. Speed Profile (Text)

 Options: “Default” ( module default) or “User”(user

- defined)

k. New Total VMT (Numeric)

– Represents user

- defined total daily VMT (miles/day)

 If the scenario VMT Profile is designated as “Default”, then the “New Total VMT” cell can be empty (user entry for “New Total VMT” will b e ignored)

 If the scenario „VMT Profile‟ and the „VMT by Vehicle Category‟ are designated as “User” (user

- defined), then the “New Total VMT” cell can be empty (the VMT from the “VMT by Vehicle Category” table will be used in the calculations; user entry fo r “New Total VMT” will be ignored)

 If the scenario VMT Profile is designated as “User” (user

- defined), and the „VMT by Vehicle Category‟ is designated as “Default” ( module default), only then the “New Total VMT” cell needs to be populated (here, the Defaul t VMT fractions by Vehicle Class are used to apportion the User provided “New Total VMT”)

User Input #2: VMT by Vehicle Category

 Contains daily VMT data by Vehicle Category, and is a required input if the “VMT by Vehicle Category” entry for the
scenario is User defined,

o Data entered in the “VMT_by_VehCat” worksheet (in miles/day)

 Input Variables:

a. Group
b. Area

c. ScenarioPTSD

- MSAB Page 6

d. Sub

- Area

e. CalYr
f. Season

g. Title
h. Veh & Tech: EMFAC2011 Vehicle Category
i. New VMT: Daily VMT by Vehicle Category

User Input #3: Speed Profile

 Contains the speed distribution by vehicle category (represented by % VMT in each speed bin for an average day), and is a required input if the “Speed Profile” entry for the scenario is User defined

o Data entered in the “Speed_Profile” worksheet

 In put Variables:

a. Group
b. Area

c. Scenario
d. Sub

- Area

e. CalYr
f. Season

g. Title
h. Veh & Tech: EMFAC2011 Vehicle Category

i. EMFAC2007 Veh & Tech: EMFAC2007 Vehicle Category j

- w. 5MPH

- 70MPH: Speed Distribution (% VMT at each speed bin) for Speeds 5

- 70 MPH @ 5 MPH increments

Optional User Input: Regional Scenarios

 This is an optional input for modeling

o Allows users to create Regional (multi

- GAI) scenarios outside the module , and import them into the module

 Input Variables:

a. GroupPTSD

- MSAB Page 7

b. Group Type

c. Area
d. Calendar Year

e. Season

 Regional Scenario Groups

o All scenarios that need to be aggregated together should be classified in the same “Group” in the Scenario_Base_Inputs table

 So if the user needs to run “Statewide 2008 Annual” and “Statewide 2010 Annual”, then user should

create two “Groups”

 All scenarios related to Statewide Sub

- Areas that relate to 2008 Annual period in the first group

 All scenarios related to Statewide Sub

- Areas that relate to 2010 Annual period in the second

group

 All input tables (Scenario_Base_Inputs, Scenar io_VMT_by_VehCat, and Scenario_Speed_Profiles) need to identify the Group, Area name, Scenario, Sub

- Area, CalYr, Season, and Title for each Scenario

o If users only need Sub

- Area (GAI) runs, then

 All scenarios should be grouped in the „Default‟ Group # (1)

 Area name category should be “

- “ [Area name “

- “ denotes that it is not part of any “regional” run, and these results will not be aggregated by Group (results will still be generated))

o For any scenarios where Area name <> “

- “, outputs will be aggregated based on Group ID

o Module allows Regional Scenario table to be imported using the “Load/Run Regional Scenarios (External Files)” optionPTSD

- MSAB Page 8

4.0 MODULE EXTRACTION

1. Extract the “ EMFAC2011

- SG .zip ” file to the root C drive (“C: \ ”)

2. The process will create a folder on the root C Drive called “EMFAC2011

- SG” and will contain the following files:

 “EMFAC2011

- SG (Ver 1.0) .mdb” file

 “EMFAC2011

- SG (Ver 1.0)” Shortcut file

 <Application Files> folder containing :

o 1 Microsoft® Access file (“EMFAC2011

- SG Processor (Ver 1.0) .mdb”)

o < Inventory Files> folder containing 9,522 Microsoft® Excel (EMFAC Inventory files)PTSD

- MSAB Page 9

5.0 SYSTEM REQUIREMENTS

The SG module requires Microsoft XP or a more recent operating system; and Microsoft Access and Excel 2003 or newer
to run the module.

6.0 MODULE IN STALLATION (FIRST TIME USER)

EMFAC2011

- SG is created in Microsoft® Access (MS Access) and contains Visual Basic for Applications ( VBA ) code for processing the data. Therefore, first time users may get a “Security Warning” depending on their system‟s “ Security Settings” . If such an error message is received, follow the steps described below to enable the modeling processors.PTSD

- MSAB Page 10

6.1 MICROSOFT® OFFICE 20 07/2010 USERS :

1. Open the file < C: \ EMFAC2011

- SG \ EMFAC2011

- SG (Ver 1.0) .mdb>

2. Microsoft® Office 2007/2010 users may receive a yellow notification ribbon at the top: “Security Warning

– Some active content has been disabled. Click for more details.”PTSD

- MSAB Page 11

3. Click „File‟ to reach M icrosoft Access Menu

4. Click „ Privacy Option s‟ to reach Microsoft Access Options

5. Access Options will open upPTSD

- MSAB Page 12

6. Click on „ Trust Center ‟ buttonPTSD

- MSAB Page 13

7. Trust Center Options will open up

8. Click on „ Trust Center Settings

... ‟ buttonPTSD

- MSAB Page 14

9. Click on „Trusted Locations‟ option
10. Click on „Add new location‟ buttonPTSD

- MSAB Page 15

11. Microsoft Office Trusted Location window will open up

12. Type “C: \ EMFAC2011

- SG” in the „Path‟ field

o Check „ S ubfolders of this location are also trusted‟

o Click „OK‟

13. Click „ OK ‟ on all previous messages boxes , and continue

14. Access will require closing and re

- opening the EMFAC2011

- SG database for options to take effect

15. Close the SG Module to complete the installation procedurePTSD

- MSAB Page 16

6.2 MICROSOFT® OFFICE 20 03 USERS :

1. Double Click on the <EMFAC2011

- SG (Ver 1.0) .mdb> file to open it

2. First time users using Microsoft® Office 2003 may get a Security Warning :

3. Click on the „ Yes ‟ button

4. The following steps need to be followed for authorizing the digital signature “AV ARB” to allow SG processors :

If the ‘Always trust files from this publisher and open the automaticall y ’ option is available, check the option and click ‘ Open ’ ( If the check box is checked, the following steps need not be completed)

5. Click on the „Details‟ buttonPTSD

- MSAB Page 17

6. T he „Digital Signature Details‟ for the digital signature “AV ARB” will open up

7. Click the „View Certificate‟ buttonPTSD

- MSAB Page 18

8. T he „Certificate Information‟ will open up for the digital signature “AV ARB”

9. Click „Install Certificate‟ button to install the digital signature “AV ARB”PTSD

- MSAB Page 19

10. The „Certificate Import Wizard‟ will open

11. Click „Next‟PTSD

- MSAB Page 20

12. Select „Automatically select the certificate store based on the type of certificate‟, and click „Next‟PTSD

- MSAB Page 21

13. Click „Finish‟PTSD

- MSAB Page 22

14. A final security warning will be displayed. Click „Yes‟

15. Click „OK‟PTSD

- MSAB Page 23

16. The Security Warning will show again, and the „Always trust files from this publisher and open the automatically‟ option will be available . Ch eck the option (to authorize MS Access documents with the digital signature “AV ARB”)
and click „Open‟

17. Close EMFAC2011

- SG to complete the installation procedure.PTSD

- MSAB Page 24

7.0 MODULE OPERATION

Open the file < C: \ EMFAC2011

- SG \ EMFAC2011

- SG (Ver 1.0) .mdb>

EMFAC2011

- SG allows users to load scenarios in two different ways:

1. Create New Scenarios : Users can create new scenarios using the Graphical User Interface (GUI)

2. Load Existing Scenarios (External Files) : Users can load scenarios from an external Excel file (.xls)PTSD

- MSAB Page 25

7.1 CREATE SUB

- AREA SCENARIOS

1. Click on the „Create Sub

- Area Scenarios‟ button on the Master Switchboard pagePTSD

- MSAB Page 26

2

. M ain page will open

3 . Click on the „Enter Model Inputs‟ buttonPTSD

- MSAB Page 27

4 . The „ Model Inputs ‟ page will pop

- up.

5. Select the model inputs from drop down box [highlighted in green ]

 Once the Sub

- Area, Calendar year and Season inputs are selected, the Default Title and Default EMFAC VMT can be called using the „Create‟ buttons [highlighted in blue]PTSD

- MSAB Page 28

6 . The user is required to select/enter information in every field (sample below)PTSD

- MSAB Page 29

7 . After selecting/entering all input fields, the user can add additional scenarios by clicking on the highlighted button at the bottom of the „Model Inputs‟ page:PTSD

- MSAB Page 30

8 . After inputting all scenarios, click on the „Save and Continue‟ button to close the „Model Inputs‟ page and
continuePTSD

- MSAB Page 31

9. EMFAC2011

- SG also provides user assistance for entering the “Speed Profiles” and “VMT by Vehicle Category” data by creating standard (empty) templates for all required data points. Click on the „Save and Creat e Template for Input Data‟ button to close the „Model Inputs‟ page and create the template file (. xls format)PTSD

- MSAB Page 32

10 . If the user elected “User” selection for Speed Profile or clicked “Import VMT by Vehicle Category” checkbox for any scenario, then the module requires the user to provide the Speed Profile and/or External VMT inputs

(Step 10 is omitted if the user selects ‘Default’ Speed Profiles and ‘Default’ VMT Profile for all scenarios 

### )

10 .1. Message boxes pop up with information on the scenarios t hat require external Speed Profile and/or External VMT by Vehicle Category (Click OK)PTSD

- MSAB Page 33

10 .2 . Click on „ Enter VMT by Vehicle and/or Speed Profiles ‟ buttonPTSD

- MSAB Page 34

10 .3 . Select the Excel file (.xls) containing the Speed Profile and/or External VMT by Vehicle Category data, and click „Open‟PTSD

- MSAB Page 35

7.2 CREATE REGIONAL SCENARIO S

1. Click on the „ Create Regional Scenarios ‟ button on the „ Master Switchboard ‟ pagePTSD

- MSAB Page 36

2. The „ Scenario Builder ‟ page will open

3 . Select all the model inputs from drop down box es [highlighted in green ]PTSD

- MSAB Page 37

4 . The user is required to select information in every field (sample below)PTSD

- MSAB Page 38

5. After selecting/entering all input fields, the user can add additional Region S cenarios by clicking on the highlighted button at the bottom of the „ Scenario Builder ‟ page:PTSD

- MSAB Page 39

6. After inputting all Regional Scenarios, click on the „ Default Model Run ‟ or „ User Defined Model Run ‟ to continue

6.1. If the user selects „ User Defined Model Run ‟ (blue) , the „ Model Inputs ‟ page will open up. Continue by following Step 7 .1. 4PTSD

- MSAB Page 40

7.3 LOAD/RUN EXISTING SC ENARIOS (EXTERNAL FI LES)

EMFAC2011

- SG input files are saved as Microsoft Excel 2003 files (.xls).

1. Click on the „ Load Scenarios ‟ button

 „Load Regional Scenarios‟ option requires the input file to contain the base inputs for the Regional S cenarios

o If the input file also contains the Sub

- Area Scenarios, the module verifies if all required Sub

- Area
S cenarios for the Regional Scenario are available. If so, then the users have the option to run the
sub

- area scenarios contained in the input file, or use the regional scenarios parameters to create
new/different module runs

o If the input file doesn‟t contai n the Sub

- Area Scenarios, then the users can only create new module runs using the Regional Scenarios

 „Load Sub

- Area Scenarios‟ option require s the input file to contain base inputs for the Sub

- Area S cenariosPTSD

- MSAB Page 41

2. A file selection/browser window will o pen up. Browse to the input data file folder, select the file, and click „ OK ‟PTSD

- MSAB Page 42

3. If „Regional Scenarios‟ are loaded, then t he „Scenario Builder‟ page will open up, and display all the loaded regional scenarios. Click „Save and Continue‟PTSD

- MSAB Page 43

4. The „Sub

- Area Scenario Verification‟ window will open up.

 The module verifies if all required Sub

- Area Scenarios for the Regional Scenario are available.

5. To continue with the verification process, Click „Yes

 To cancel the verification process
, and return to the „Scenario Builder‟ page, Click „No‟

If the verification process fails (if all the required sub

- area scenarios for the regional scenario are not available),
EMFAC2011

- SG allows the user to create default output for the selected regional ca ses.PTSD

- MSAB Page 44

8.0 MODULE VERIFICATION

I f the user elected user

- defined Speed P rofile for any scenario , then the speed

- profile inputs are verified to ensure
that profiles sum up to 100% for each vehicle category (this step is omitted if the user selects default speed profiles)

.

1

. Click on the „ Verify Speed Data Quality ‟ buttonPTSD

- MSAB Page 45

2 . The „ Verify Speed Inputs ‟ page will open

If the user entered user

- defined speed profile using an external file , the „Verify Speed Inputs‟ database will be populated.

 If the Speed Profiles for all the Vehicle and Tech nology cases add up to 100%, the „Continue‟ button will be
enabled

o To proceed, click „Continue‟

 If the Speed Profiles for all cases are not available or do not add up to 100%, only the „Reset‟ button will b e enabled

o The Vehicle and Technology cases will be identified with an “ Error ” en try in the „Error Check‟ column

o The user will need to correct the speed profile in the input data file, and re

- import the scenario file.

o To re

- import the corrected speed profile, c lick the „ Reset ‟ button

The SG Module checks the speed totals for all scenarios where speed profiles are “user

- defined”. If it identifies any vehicle category case where speed fractions do not add up to 100%, it doesn’t allow the user to proceed (user may only reset and reload the corrected speed profiles). When the speed profiles for all scenarios add up to 100%, only then the “Speed Check / Speed QA” table will be empty, and the “Continue” but ton will be enabled

o The default inventories for many regions may have zero population for certain vehicle categories, resulting in the absence of speed profiles for those vehicle categories. Therefore, when the users modify the default speed profiles for any scenario, they must make sure that the speeds fractions for all vehicle category cases add up to 100%

.PTSD

- MSAB Page 46

9.0 MODULE EXECUTION

1

. The first step to module execution is to save the scenarios. 2. At this stage, t he „ Save Scenario ‟ button will be activated. Click on the button to save the inputs and co ntinue.PTSD

- MSAB Page 47

3 . The pop window will open up, allowing the user to save the input file. User can only enter the file name (the input file will be automatically saved as an Microsoft Excel 2003 file [.xls ]). Enter the desired file name and click „Save‟ to
continue.

4 . The input file location message will open. Click „OK‟ to continuePTSD

- MSAB Page 48

5 . The „Execute Model‟ button will be activated. Click on the button to start the processing.PTSD

- MSAB Page 49

6. The „Model Execution Options‟ page will open , and contains the following information/options:

 „EMFAC2011

- SG Processing Information‟ with the scenario information and expected module run time.

o The run time is only an estimate, and the process could vary depending on system configurations.

 Option to „Export De fault Input P arameters ‟ [in XLS or CSV Format]

o The Input Parameters file is denoted by “EMFAC2011

- SG Input Parameters” and contains the Input
Filename

 Option to select Default Output Format [in XLS or CSV Format]

 Option to „Create Additional Summary Outpu ts‟

 Option to „Create Separate Output Files for Each Regional Scenario‟

7. Click „ Start ‟ to begin module execution

 Click „No‟ to cancel module execution

Users may export the default input parameters (Speed profile or VMT by Vehicle Category) for a scenario, and re

use it in a later modeling run by defining the corresponding modeling conditions as

“User

- defined”.PTSD

- MSAB Page 50

8

. As t he module executes the scenarios, it indicates the Module Processing S tatus including the “Current Processing Scenario”, and the “Processing Stage” :PTSD

- MSAB Page 51

9 . After the module completes the processing for all the scenarios , a pop

- up message shows the output location (same as the Input file location)

.PTSD

- MSAB Page 52

10.0 DEFAULT MODULE OUTPUT S

The module outputs are denoted by “EMFAC 2011

- SG Output” and contain the Input File n ame (e.g. if the Input File n ame is “Sample”, the Output file will be called “EMFAC2011

- SG Output

- Sample”). The output files are created in Microsoft® Excel format (.xls) , and contain the following variables:

o Group

o Area

o Scenario

o Sub

- Area

o Calendar Year

o Season

o Title

o Veh & Tech

o EMFAC2007 Category

o Vehicle Population

o VMT (miles/average weekday )

o Trips (trips/average weekday )

o TOG Emissions (tons/average weekday )

o ROG Emissions (tons/average weekday )

o CO Emissions (tons/average weekday )

o NO x Emissions (tons/average weekday )

o CO2 Emission s (tons/average weekday )

o CO2 Emissions (including Pavley I and LCFS adjustments) (tons/average weekday )

o PM 10 Emissions (tons/average weekday )

o PM 2.5 Emissions (tons/average weekday )

o SO x Emissions (tons/average weekday )

o Fuel Consumption (1000 gal/ average week day): DSL and GAS (not adjusted for Pavley

- I or LCFS)PTSD

- MSAB Page 53

The following process emissions are generated for each pollutant:

o All Pollutants

- Running Exhaust, Idling Exhaust, Starting Exhaust, Total Exhaust

o ROG and TOG

- Diurnal Losses, Hot

- Soak Losses, Running Losses, Resting Losses, Total

o PM10 and PM2.5

- Break wear, Tire wear, Total

The module appends the outputs for all scenarios defined in an input file in the same output file. The module also aggregat es the results of all the scenarios that are classified in the same group, and appends the aggregated output for the group in the same file (along with the outputs for all sub

- areas).

o For a single statewide regional case, the module will create a single Excel output table containing 70 sets of outputs (69 sub

- area/GAI results, and 1 Statewide

- totals result). The number of data rows will depend on number of Vehicle Categories applicable to each sub

- area.PTSD

- MSAB Page 54

11.0 OTHER FUNCTIONS

“Reset” and “Reset / Return to Main Menu”

 This button can be clicked at any time before or after module execution to reset all inputs and return to the
Main Menu

“New Scenario”

 Users can click on the „New Scenario‟ button at the bottom of the „Main Switchboard‟ to create a new scenario

 This button can also be clicked any time before or after module execution to reset the scenarios

“Exit EMFAC2011

- SG ”

 This button resets all inputs, and exits the moduleAppendix A

– S ub

- Area Classification

Sub

- Area County Air Basin Air District MPO
Alameda (SF) Alameda San Francisco Bay Area Bay Area AQMD MTC Alpine (GBV) Alpine Great Basin Valley Great Basin Unified APCD
Amador (MC) Amador Mountain Counties Amador County APCD
Butte (SV) Butte Sacramento Valley Butte County AQMD BCAG Calaveras (MC) Calaveras Mountain Counties Calaveras County APCD
Colusa (SV) Colusa Sacramento Valley Colusa County APCD Contra Costa (SF) Contra Costa San Francisco Bay Area Bay Area AQMD MTC
Del Norte (NC) Del Norte North Coast North Coast Unified AQMD
El Dorado (LT) El Dorado Lake Tahoe El Dorado County APCD TMPO El Dorado (MC) El Dorado Mountain Counties El Dorado County APCD SACOG
Fresno (SJV) Fresno San Joaquin Valley San Joaquin Valley Unified APCD COFCG Glenn (SV) Glenn Sacramento Valley Glenn County APCD
Humboldt (NC) Humboldt North Coast North Coast Unified AQMD Imperial (SS) Imperial Salton Sea Imperial County APCD SCAG Inyo (GBV) Inyo Great Basin Valley Great Basin Unified APCD
Kern (MD) Kern Mojave Desert Kern County APCD KCOG Kern (SJV) Kern San Joaquin Valley San Joaquin Valley Unified APCD KCOG Kings (SJV) Kings San Joaquin Valley San Joaquin Valley Unified APCD KCAG Lake (LC) Lake Lake County Lake County APCD
Lassen (NEP) Lassen Northeast Plateau Lassen County APCD Los Angeles (MD) Los Angeles Mojave Desert Antelope Valley APCD SCAG Los Angeles (SC) Los Angeles South Coast South Coast AQMD SCAG
Madera (SJV) Madera San Joaquin Valley San Joaquin Valley Unified APCD MCTC Marin (SF) Marin San Francisco Bay Area Bay Area AQMD MTC
Mariposa (MC) Mariposa Mountain Counties Mariposa County APCD Mendocino (NC) Mendocino North Coast Mendocino County APCD
Merced (SJV) Merced San Joaquin Valley San Joaquin Valley Unified APCD MCAG
Modoc (NEP) Modoc Northeast Plateau Modoc County APCD Mono (GBV) Mono Great Basin Valley Great Basin Unified APCD Monterey (NCC) Monterey North Central Coast Monterey Bay Unified APCD AMBAG Napa (SF) Napa San Francisco Bay Area Bay Area AQMD MTC
Nevada (MC) Nevada Mountain Counties Northern Sierra AQMD Orange (SC) Orange South Coast South Coast AQMD SCAG
Placer (LT) Placer Lake Tahoe Placer County APCD TMPO
Placer (MC) Placer Mountain Counties Placer County APCD SACOG Placer (SV) Placer Sacramento Valley Placer County APCD SACOG
Plumas (MC) Plumas Mountain Counties Northern Sierra AQMD
Riverside (MD/MDAQMD) Riverside Mojave Desert Mojave Desert AQMD SCAG Riverside (MD/SCAQMD) Riverside Mojave Desert South Coast AQMD SCAG
Riverside (SC) Riverside South Coast South Coast AQMD SCAG Riverside (SS) Riverside Salton Sea South Coast AQMD SCAG
Sacramento (SV) Sacramento Sacramento Valley Sacramento Metropolitan AQMD SACOG San Benito (NCC) San Benito North Central Coast Monterey Bay Unified APCD AMBAG
San Bernardino (MD) San Bernardino Mojave Desert Mojave Desert AQMD SCAG
San Bernardino (SC) San Bernardino South Coast South Coast AQMD SCAG San Diego (SD) San Diego San Diego San Diego County APCD SANDAG
San Francisco (SF) San Francisco San Francisco Bay Area Bay Area AQMD MTC San Joaquin (SJV) San Joaquin San Joaquin Valley San Joaquin Valley Unified APCD SJCOG
San Luis Obispo (SCC) San Luis Obispo South Central Coast San Luis Obispo County APCD SLOCOG
San Mateo (SF) San Mateo San Francisco Bay Area Bay Area AQMD MTC Santa Barbara (SCC) Santa Barbara South Central Coast Santa Barbara County APCD SBCAG
Santa Clara (SF) Santa Clara San Francisco Bay Area Bay Area AQMD MTC Santa Cruz (NCC) Santa Cruz North Central Coast Monterey Bay Unified APCD AMBAG
Shasta (SV) Shasta Sacramento Valley Shasta County AQMD SCRTPA Sierra (MC) Sierra Mountain Counties Northern Sierra AQMD Siskiyou (NEP) Siskiyou Northeast Plateau Siskiyou County APCD
Solano (SF) Solano San Francisco Bay Area Bay Area AQMD MTC Solano (SV) Solano Sacramento Valley Yolo/Solano AQMD MTC
Sonoma (NC) Sonoma North Coast Northern Sonoma County APCD MTC Sonoma (SF) Sonoma San Francisco Bay Area Bay Area AQMD MTC

Stanislaus (SJV) Stanislaus San Joaquin Valley San Joaquin Valley Unified APCD StanCOG
Sutter (SV) Sutter Sacramento Valley Feather River AQMD SACOG Tehama (SV) Tehama Sacramento Valley Tehama County APCD Trinity (NC) Trinity North Coast North Coast Unified AQMD Tulare (SJV) Tulare San Joaquin Valley San Joaquin Valley Unified APCD TCAG
Tuolumne (MC) Tuolumne Mountain Counties Tuolumne County APCD Ventura (SCC) Ventura South Central Coast Ventura County APCD SCAG
Yolo (SV) Yolo Sacramento Valley Yolo/Solano AQMD SACOG
Yuba (SV) Yuba Sacramento Valley Feather River AQMD SACOGAppendix B

– EMFAC2011 Vehicle Category Classification

Index EMFAC2011 Veh & Tech EMFAC2011 Vehicle Description Source EMFAC2007 Vehicle CTEMFAC

Vehicle

1 LDA

- DSL
LDA Passenger Cars EMFAC2011

- LDV LDA Non

- Trucks

2 LDA

- GAS EMFAC2011

- LDV Non

- Trucks

3 LDT1

- DSL
LDT1 Light

- Duty Trucks (0

- 3750 lbs) EMFAC2011

- LDV LDT1 Non

- Trucks

4 LDT1

- GAS EMFAC2011

- LDV Non

- Trucks

5 LDT2

- DSL LDT2 Light

- Duty Trucks (3751

- 5750 lbs) EMFAC2011

- LDV LDT2 Non

- Trucks

6 LDT2

- GAS EMFAC2011

- LDV Non

- Trucks

7 LHD1

- DSL LHD1 Light

- Heavy

- Duty Trucks (8501

- 10000 lbs) EMFAC2011

- LDV LHDT1 Trucks

8 LHD1

- GAS EMFAC2011

- LDV Trucks

9 LHD2

- DSL LHD2 Light

- Heavy

- Duty Trucks (10001

- 14000 lbs) EMFAC2011

- LDV LHDT2 Trucks

10 LHD2

- GAS EMFAC2011

- LDV Trucks

11 MCY

- GAS MCY Motorcycles EMFAC2011

- LDV MCY Non

- Trucks

12 MDV

- DSL
MDV Medium

- Duty Trucks (5751

- 8500 lbs) EMFAC2011

- LDV MDV Trucks

13 MDV

- GAS EMFAC2011

- LDV Trucks

14 MH

- DSL
MH Motor Homes EMFAC2011

- LDV MH Non

- Trucks

15 MH

- GAS EMFAC2011

- LDV Non

- Trucks

16 T6 Ag

- DSL T6 Ag Medium

- Heavy Duty Diesel Agriculture Truck EMFAC2011

- HD

MHDT Trucks

17 T6 CAIRP heavy

- DSL T6 CAIRP heavy Medium

- Heavy Duty Diesel CA International Registration Plan Truck with GVWR>26000 lbs EMFAC2011

- HD Trucks

18 T6 CAIRP small

- DSL T6 CAIRP small Medium

- Heavy Duty Diesel CA International Registration Plan Truck with GVWR<=26000 lbs EMFAC2011

- HD Trucks

19 T6 instate construction heavy

- DSL T6 instate construction heavy Medium

- Heavy Duty Diesel instate construction Truck with GVWR>26000 lbs EMFAC2011

- HD Trucks

20 T6 instate construction small

- DSL T6 instate construction small Medium

- Heavy Duty Diesel instate construction Truck with GVWR<=26000 lbs EMFAC2011

- HD Trucks

21 T6 instate heavy

- DSL T6 instate heavy Medium

- Heavy Duty Diesel instate Truck with GVWR>26000 lbs EMFAC2011

- HD Trucks

22 T6 instate small

- DSL T6 instate small Medium

- Heavy Duty Diesel instate Truck with GVWR<=26000 lbs EMFAC2011

- HD Trucks

23 T6 OOS heavy

- DSL T6 OOS heavy Medium

- Heavy Duty Diesel Out

- of

- state Truck with GVWR>26000 lbs EMFAC2011

- HD Trucks

24 T6 OOS small

- DSL T6 OOS small Medium

- Heavy Duty Diesel Out

- of

- state Truck with GVWR<=26000 lbs EMFAC2011

- HD Trucks

25 T6 Public

- DSL T6 Public Medium

- Heavy Duty Diesel Public Fleet Truck EMFAC2011

- HD Trucks

26 T6 utility

- DSL T6 utility Medium

- Heavy Duty Diesel Utility Fleet Truck EMFAC2011

- HD Trucks

27 T6TS

- GAS T6TS Medium

- Heavy Duty Gasoline Truck EMFAC2011

- LDV Trucks

28 T7 Ag

- DSL T7 Ag Heavy

- Heavy Duty Diesel Agriculture Truck EMFAC2011

- HD

HHDT Trucks

29 T7 CAIRP

- DSL T7 CAIRP Heavy

- Heavy Duty Diesel CA International Registration Plan Truck EMFAC2011

- HD Trucks

30 T7 CAIRP construction

- DSL T7 CAIRP construction Heavy

- Heavy Duty Diesel CA International Registration Plan Construction Truck EMFAC2011

- HD Trucks

31 T7 NNOOS

- DSL T7 NNOOS Heavy

- Heavy Duty Diesel Non

- Neighboring Out

- of

state Truck EMFAC2011

- HD Trucks

32 T7 NOOS

- DSL T7 NOOS Heavy

- Heavy Duty Diesel Neighboring Out

- of

- state Truck EMFAC2011

- HD Trucks

33 T7 other port

- DSL T7 other port Heavy

- Heavy Duty Diesel Drayage Truck at Other Facilities EMFAC2011

- HD Trucks

34 T7 POAK

- DSL T7 POAK Heavy

- Heavy Duty Diesel Drayage Truck in Bay Area EMFAC2011

- HD Trucks

35 T7 POLA

- DSL T7 POLA Heavy

- Heavy Duty Diesel Drayage Truck near South Coast EMFAC2011

- HD Trucks

36 T7 Public

- DSL T7 Public Heavy

- Heavy Duty Diesel Public Fleet Truck EMFAC2011

- HD Trucks

37 T7 Single

- DSL T7 Single Heavy

- Heavy Duty Diesel Single Unit Truck EMFAC2011

- HD Trucks

38 T7 single construction

- DSL T7 single construction Heavy

- Heavy Duty Diesel Single Unit Construction Truck EMFAC2011

- HD Trucks

39 T7 SWCV

- DSL T7 SWCV Heavy

- Heavy Duty Diesel Solid Waste Collection Truck EMFAC2011

- HD Trucks

40 T7 tractor

- DSL T7 tractor Heavy

- Heavy Duty Diesel Tractor Truck EMFAC2011

- HD Trucks

41 T7 tractor construction

- DSL T7 tractor construction Heavy

- Heavy Duty Diesel Tractor Construction Truck EMFAC2011

- HD Trucks

42 T7 utility

- DSL T7 utility Heavy

- Heavy Duty Diesel Utility Fleet Truck EMFAC2011

- HD Trucks

43 T7IS

- GAS T7IS Heavy

- Heavy Duty Gasoline Truck EMFAC2011

- LDV Trucks

44 PTO

- DSL PTO Power Take Off EMFAC2011

- HD Trucks

45 SBUS

- DSL SBUS School Buses EMFAC2011

- HD SBUS Non

- Trucks

46 SBUS

- GAS School Buses EMFAC2011

- LDV Non

- Trucks

47 UBUS

- DSL UBUS Urban Buses EMFAC2011

- LDV UBUS Non

- Trucks

48 UBUS

- GAS EMFAC2011

- LDV Non

- Trucks

49 Motor Coach

- DSL Motor Coach Motor Coach EMFAC2011

- HD

OBUS Non

- Trucks

50 OBUS

- GAS OBUS Other Buses EMFAC2011

- LDV Non

- Trucks

51 All Other Buses

- DSL All Other Buses All Other Buses EMFAC2011

- HD Non

- Trucks