March 28, 2001 (REV.)
CERTIFICATION AND FUEL ECONOMY
INFORMATION SYSTEM (CFEIS)
MANUFACTURERS' USER GUIDE (CMUG)
United States Environmental Protection Agency
Office of Mobile Sources
Vehicle Programs and Compliance Division
National Vehicle and Fuel Emissions Laboratory
2000 Traverwood
Ann Arbor, MI 48105
-------
March 28, 2001 (REV.)
This page is intentionally left blank.
-------
March 28, 2001 (REV.)
CONTENTS
1.0 INTRODUCTION 1
1.1 About CFEIS 1
1.1.1 CFEIS Databases 1
1.1.2 CFEIS Subsystems 1
1.2 Purpose 3
1.3 References 3
1.4 Organization 5
2.0 SYSTEM DESCRIPTION 7
2.1 System Overview 7
2.2 Personnel Interaction 9
2.3 System Configuration and Operation 9
2.4 Input Data Structure 12
2.4.1 Data Entry 14
2.4.2 Input Data Formats 14
2.4.3 Decimals in Input Data 14
2.4.4 Input Data File Names 15
2.4.5 Input Notes and Calculations 15
3.0 CAR LINE 17
3.1 Car Line Input/Output File Names 17
3.2 Car Line Transaction Process Codes 17
3.3 Car Line Input Notes 18
3.3.1 Add and Modify Transactions 18
3.3.2 Delete Transactions 19
3.3.3 Input Record Dependencies 19
3.4 Conversion of MTS CFEIS Car Line and Manufacturer Codes 19
4.0 ENGINE SYSTEMS INFORMATION (ESI) 23
4.1 ESI Input/Output File Names 23
4.2 ESI Transaction Process Codes 23
4.3 ESI Input Notes 24
4.3.1 ^(^Transactions 24
4.3.2 Modify and Replace Transactions 25
4.3.3 Delete Transactions 27
4.3.4 Cancel Transactions 27
4.3.5 E2 and ES Input Records 27
4.3.6 Input Record Dependencies 31
in
-------
March 28, 2001 (REV.)
5.0 EVAPORATIVE SYSTEMS INFORMATION (EvSI) 33
5.1 EvSI Input/Output File Names 33
5.2 EvSI Transaction Process Codes 33
5.3 EvSI Input Notes 34
5.3.1 Add Transactions 34
5.3.2 Modify or Replace Transactions 35
5.3.3 Delete Transactions 36
5.3.4 Cancel Transactions 37
5.3.5 Input Record Dependencies 37
6.0 VEHICLE INFORMATION (VI) 39
6.1 VI Input/Output File Names 39
6.2 VI Transaction Process Codes 39
6.3 VI Input Notes 40
6.3.1 Add, Modify, Change, and CarryAcross Transactions 40
6.3.2 Add or Change or CarryAcross Transactions 41
6.3.3 Modify Transactions 42
6.3.4 Delete Transactions 43
6.3.5 Carry Over Transactions 44
6.3.6 Input Record Dependencies 44
7.0 SHIFT SCHEDULE 47
7.1 Shift Schedule Input/Output File Names 47
7.2 Shift Schedule Transaction Process Codes 47
7.3 Shift Schedule Input Notes 48
7.3.1 Add, Replace, and Change Transactions 48
7.3.2 Add and Replace Transactions 49
7.3.3 Modify and Change Transactions 49
7.3.4 Add and Change Transactions 49
7.3.5 Modify, Delete, and Replace Transactions 49
7.3.6 Input Record Dependencies 50
8.0 EPA/MANUFACTURER TEST DATA (MTDS) 51
8.1 MTDS Input/Output File Names 51
8.2 MTDS Transaction Process Codes 51
8.3 MTDS InputNotes 52
8.3.1 Add Transactions 53
8.3.2 Modify and Replace Transactions 54
8.3.3 Delete Transactions 55
IV
-------
March 28, 2001 (REV.)
8.3.4 Carry Over or Carry Across Transactions 56
8.3.5 Input Record Dependencies 57
8.4 System-Generated Calculations 58
8.4.1 Unrounded Unadjusted Fuel Economy/Measured Fuel Properties 59
8.4.2 Unrounded Unadjusted Fuel Economy/Methanol
Flexible-Fueled Vehicles 60
8.4.2.5 Unrounded Unadjusted Fuel Economy Equation
for Ethanol Flexible-Fueled Vehicles 60
8.4.3 Unrounded System Miles or Kilometers 61
8.4.4 Conversion of System Kilometers to System Miles 62
8.4.5 Unrounded Mileage-Adjusted Fuel Economy 62
8.4.6 Fuel Economy Calculations for Vehicles Tested on California Phase 2
Gasoline 62
8.4.7 Fuel Economy Calculations for Vehicles Tested Using Natural Gas Fuel
64
8.4.8 Fuel Economy Calculations for Vehicles Tested Using Diesel Fuel .... 65
8.4.9 Test Type/Test Purpose 67
8.4.10 Test Procedure Codes 68
8.4.11 Valid Combinations of Test Type/Test Purpose
and Test Procedure Codes 70
9.0 SUMMARY SHEET 72
9.1 Summary Sheet Input/Output File Names 72
9.2 Summary Sheet Transaction Process Codes 72
9.3 Summary Sheet Input Notes 73
9.3.1 For All Transactions 73
9.3.2 Add Transactions 73
9.3.3 Add and Replace Transactions 73
9.3.4 Re-process, Delete, and Report Transactions 73
9.3.5 Replace, Re-process, and Delete Transactions 73
9.3.6 Input Record Dependencies 73
10.0 GENERAL LABEL 75
10.1 General Label Input/Output File Names 75
10.2 General Label Transaction Process Codes 75
10.3 General Label Input Notes 76
10.3.1 Input Record Dependencies 76
10.4 System-Generated Calculations 77
10.4.1 Multiple tests on one test vehicle within one subconfiguration 78
10.4.2 Subconfiguration-level MPG/City or Highway 78
-------
March 28, 2001 (REV.)
10.4.3 Configuration-level MPG/City or Highway 78
10.4.4 Configuration-level MPG/Combined 79
10.4.5 Base-level MPG/City, Highway, or Combined 79
10.4.6 Model-level MPG/City, Highway, or Combined 80
10.4.7 Estimated Model Type MPG/City 80
10.4.8 Estimated Model Type MPG/Highway 81
10.4.9 Estimated Model Type MPG/Combined 81
10.4.10 Annual Fuel Cost 82
10.4.11 Averaging/Weighting of tests 82
10.4.12 Fuel Economy Range/City or Highway 83
10.4.13 Adjusted MPG Calculation for Gas Guzzler 83
11.0 CORPORATE AVERAGE FUEL ECONOMY (CAFE) 85
11.1 CAFE Input/Output File Names 85
11.2 CAFE Transaction Process Codes 85
11.3 CAFE Input Notes 86
11.4 System-Generated Calculations 86
11.4.1 CAFE 86
11.4.2 Adjusted Combined CAFE 87
11.4.3 Multiple tests on one test vehicle within one subconfiguration 89
11.4.4 Subconfiguration-level MPG/City or Highway 89
11.4.5 Configuration-level MPG/City or Highway 89
11.4.6 Configuration-level MPG/Combined 90
11.4.7 Base-level MPG/City, Highway, or Combined 90
11.4.8 Model-level MPG/City, Highway, or Combined 91
11.5 Input Record Dependencies 92
12.0 REPORTS 93
12.1 Car Line 93
12.2 Engine Systems Information 94
12.3 EvSI Systems Information 94
12.4 Vehicle Information 94
12.5 Shift Schedule 95
12.6 Manufacturer/EPA Test Data 95
12.7 Summary Sheet 96
12.8 General Label 96
12.9 Corporate Average Fuel Economy 97
13.0 ERRORS 99
13.1 User-induced Errors 99
13.2 System or Database Errors 99
VI
-------
March 28, 2001 (REV.)
APPENDIX A Acronyms
APPENDIX B Error Messages
APPENDIX C Reports
APPENDIX D Input Data Record Layouts
APPENDIX E Input Forms
APPENDIX F EPA Standardized Engine and Evaporative Family Names
APPENDIX G Sample Input Forms (filled-in)
EXHIBITS
Exhibit 2-1. CFEIS Operations 8
Exhibit 2-2. Electronic File Transfer 10
Exhibit 2-3. Processing by the CFEIS Server 11
Exhibit 2-4. Transaction Type Summary 13
Exhibit 2-5. CFEIS Mail Box Files 15
Exhibit 3-1. Sum of Averages per Class Code 18
Exhibit 3-2. Car Line Input Record Dependencies 19
Exhibit 3-3. Sample Car Line Code Conversion 20
Exhibit 4-1. Sales Area Codes (Federal and California) 28
Exhibit 4-2. Light-Duty Vehicle Class Codes (Federal and California) 29
Exhibit 4-3. Light-Duty Vehicle Class Codes (Federal and California)
For Model Years 1995, 1996 and 1997 Only 29
Exhibit 4-4. Codes for Exhaust Emission Standards (Federal and National) 30
Exhibit 4-5. Exhaust Emission Standards Codes (California) 31
Exhibit 4-6. ESI Input Record Dependencies 32
Exhibit 5-1. EvSI Input Record Dependencies 38
Exhibit 6-1. VI Input Record Dependencies 44
Exhibit 7-1. Shift Schedule Input Record Dependencies 50
Exhibit 8-1. MTDS Input Record Dependencies 57
Exhibit 8-2. Test Type/Test Purpose Codes 67
Exhibit 8-3. Test Procedures Codes 68-69
Exhibit 8-4. Valid Combinations of Test Procedure Codes and Test Type/Test
Purpose Codes 70-71
Exhibit 9-1. Summary Sheet Input Record Dependencies 74
Exhibit 10-1. General Label Input Record Dependencies 77
Exhibit 11-1. CAFE Input Record Dependencies 92
vn
-------
March 28, 2001 (REV.)
This page is intentionally left blank.
Vlll
-------
March 28, 2001 (REV.)
1.0 INTRODUCTION
The Certification and Fuel Economy Information System (CFEIS) is Environmental Protection
Agency's (EPA) Relational Database Management System (RDBMS) for processing vehicle
emission and fuel economy information. This information, gathered from automobile
manufacturers, testing laboratories, and EPA analysts, is used to determine if a particular car or
truck is in compliance with federal regulations so EPA can certify it for sale in the United States.
CFEIS also provides information for reports to other federal agencies, state and local
governments, and public inquiries under the Freedom of Information Act (FOIA).
1.1 About CFEIS
CFEIS resides on a Sun UNIX database server that can be accessed over the EPA's National
Vehicle and Fuel Emissions Laboratory (NVFEL) Ethernet network from UNIX workstations
and other computers running X Window software. CFEIS is a host-based system (i.e., a
server/workstation setup), meaning that all processing of CFEIS data occurs on the server, with
each client workstation handling presentation functions. CFEIS runs under version 7.2.2 of
Oracle, a multi-user RDBMS.
1.1.1 CFEIS Databases
For security and efficiency, CFEIS comprises several databases. All data submitted to CFEIS
first resides in a submission database. This serves as a holding area for data waiting to be
processed, as well as a record of all data exactly as they were submitted. Data from the
submission database is checked before processing, and if errors are found, an error report is sent
to the user who submitted the data. If the data pass this edit check, they are placed into the
production database. This is the database of record, against which searches can be conducted and
reports generated.
CFEIS also maintains an output database, which holds reports generated by the system or
requested by users. This database also serves as an archive of reports as they were sent to the
user, should there be a need to recreate a report after the data on which it was based has been
changed.
1.1.2 CFEIS Subsystems
For the purposes of manufacturers' data submission, CFEIS is organized into nine subsystems,
each of which is responsible for processing or reporting particular certification and fuel economy
information.
-------
March 28, 2001 (REV.)
These subsystems are as follows:
Car Line (CL). Allows for the receipt, validation, and update of Car Line information
from manufacturers. This information is entered by the manufacturer and is used to
identify those Car Lines to be included in emission certification, fuel economy label, and
Corporate Average Fuel Economy (CAFE) calculations.
Engine System Information (ESI). Allows for the receipt, validation, update, and
reporting of ESI received from manufacturers applicable to emission certification and fuel
economy labeling. This information is grouped by family and is used to identify the
applicable standards that those families must meet.
Evaporative System Information (EvSI). Allows for the receipt, validation, update,
and reporting of EvSI received from manufacturers applicable to emission certification
and fuel economy labeling. This information is grouped by family and is used to identify
the applicable standards that those families must meet.
Vehicle Information (VI). Allows for the receipt, validation, update, and reporting of
VI. Additionally, it provides descriptive information for fuel economy and certification
test vehicles. VI data submission should also be prepared when fuel economy data
vehicle packages are assembled, when vehicles (and their data) are submitted for carry
over/carry across, or when vehicles are built or re-configured for running change/field fix
testing. The VI submission cannot be processed until the ESI, EvSI, and Car Line data
are accepted.
Shift Schedule (SH). Allows for the receipt, validation, update, and reporting of Shift
Schedule information received from the manufacturers. Additionally, it provides the
capability for a vehicle manufacturer to enter unique transmission shift schedules that are
used to produce video driving traces for vehicle emission and fuel economy tests
performed at NVFEL. The manufacturer submits Shift Schedule data into the Shift
Schedule database.
EPA/Manufacturer Test Data (MTDS). Allows for the receipt, validation, update, and
reporting of EPA and manufacturer test data applicable to emission certification and fuel
economy labeling. The manufacturer performs and submits the results of emission and
fuel economy tests into the EPA database. The test data cannot be processed until the
ESI, EvSI, and VI data have been accepted.
Summary Sheet (SS). Allows for the receipt, validation, update, and reporting of
Summary Sheet information received from the manufacturers. It provides the means
-------
March 28, 2001 (REV.)
for accepting the manufacturer's vehicle summary information by (engine family/ test group) /
(evaporative family/refueling family) combination. The Summary Sheet submission includes a
concise description of all test vehicles, test results, and procedures used to support the issuance
of each Certificate of Conformity, together with a list of all Car Lines covered by the particular
certificate. The data cannot be processed until the ESI, EvSI, Car Line, VI, and MTDS data have
been processed.
General Label (GL). Allows for the receipt, validation, update, and reporting of General
Label information received from the manufacturers. This processing includes the
verification of the manufacturer submitted self-approved fuel economy calculations. The
data cannot be processed until the ESI, Car Line, VI, and MTDS data have been accepted.
Corporate Average Fuel Economy (CAFE). Allows for the receipt, validation, update,
and reporting of CAFE Information. It uses reported or generated manufacturer test data
and the actual sales volume to produce manufacturers CAFE by compliance category.
The data cannot be processed until the ESI, Car Line, VI, and MTDS data have been
accepted.
1.2 Purpose
This guide gives manufacturers the information they need to exchange data with CFEIS. It
introduces the procedures for physically submitting data to NVFEL and briefly explains the
sequence of data submission that is important across the various subsystems.
1.3 References
This subsection identifies documents applicable to or referenced by this guide.
Government Documents
Draft Certification Division Application Software Development Guidelines, EPA,
May 1994.
Hardware and Software Standards, EPA, December, 30, 1994.
Draft Standard for Data Element Naming Conventions., EPA, August 28, 1992.
Draft Standard for Data Element Attribution, EPA, August 28, 1992.
-------
March 28, 2001 (REV.)
Draft Standard for the Formulation of Data Definitions, EPA, September 15, 1992.
EPA Information Security Manual.
EPA Common User Interface Standards.
EPA Systems Development Center User Support Operations and Procedures Manual.
EPA Systems Development Center Information Systems Engineering Methodology
(ISEM).
OMB Circular A-13 0, Management of Federal Information Resources.
Title H of the Clean Air Act (CAA).
Energy Policy and Conservation Act (EPCA).
Motor Vehicle Information and Costs Savings Act (MVICSA).
40 CFR Part 86, Certification Compliance Program.
40 CFR Part 600, Fuel Economy Compliance Program.
Advisory Circulars.
Dear Manufacturer Guidance Letters.
Information Security Plan for Development and Maintenance ofCFEIS
(SDC-0055-078-RA-4007, dated November 18, 1995).
EPA Security Manual.
EPA Personal Security Computer Manual.
Specific VPCD Information Security Guidance.
Systems Development Center (SDC) Documents
The Certification and Fuel Economy Information System (CFEIS) Database Conversion
Plan. SDC document no. SDC-0055-078-AG-4003.
-------
March 28, 2001 (REV.)
The Certification and Fuel Economy Information System (CFEIS) Requirements
Specification. SDC document no. SDC-0055-078-WB-5011.
The Certification and Fuel Economy Information System (CFEIS) Logical Design
working papers. SDC document no. SDC-0055-078-WB-4015, WO through W14.
SDC Systems Engineering Environment (SEE), containing:
SDC Guidelines for the Change Control Board. SDC document no. SDC-0055-
028-SS-20052 (January 8, 1993)
SDC Procedure 1 - Product Development Process. SDC document No. SDC-
0055-028-2054 (June 15, 1993)
- SDC Procedure 1 - Product Development Process Briefing. SDC document no.
SDC-0055-028-2055 (April, 1994)
- SDC Standard - Application Development Process Environment (ADPE)
Elements. SDC document no. SDC-0055-028-SS-3004 (March 1, 1994)
- SDC ADTE Plan - Plan for the EPA Systems Development Center Application
Development Technology Environment Plan. SDC document no. SDC-0055-028-
3006A (May 13, 1994)
- SDC Telecommunications Services Request (TSR) Process Briefing. SDC
document no. SDC-0055-028-TB (January, 1994)
SDC Document Style Guide (Second Edition). SDC document no. SDC-0055-
028-PK-4027 (July 15, 1995)
Certification and Fuel Economy Information System (CFEIS) Input Data Record Layouts.
1.4 Organization
This document consists of the following:
Section 1.0. Introduction, explains the guide's purpose and organization.
-------
March 28, 2001 (REV.)
Section 2.0. System Description, gives an overview of the system, the configuration and
operation of the parts of the system that manufacturers access, the logical parts of the
system as they relate to processing manufacturer-submitted data, and a high-level
discussion of the internal structure of a submission file.
Sections 3.0 through 11.0, explains how to format data submissions for each subsystem
and what validations or calculations the system performs on the data submitted.
Section 12.0. Reports, describes what reports CFEIS generates from the data
submissions.
Section 13.0. Errors, discusses the errors that the user can expect to receive as a result of
submitting data. Such errors fall into two groups: (1) errors that the user caused (that is,
user-induced errors) and (2) system or database errors (errors generated independently
from the content of a user's data submission).
Appendices contain Acronyms and Abbreviations (Appendix A), Error Messages
(Appendix B), Reports (Appendix C), Input Data Record Layouts (Appendix D), Input
Forms (Appendix E), and EPA Standardized Engine and Evaporative Family Names
(Appendix F).
-------
March 28, 2001 (REV.)
2.0 SYSTEM DESCRIPTION
2.1 System Overview
CFEIS is installed at the Vehicle Programs and Compliance Division (VPCD) located at NVFEL
in Ann Arbor, Michigan. The system employs a workstation/server architecture in a Local Area
Network (LAN) environment using version 7.2.2 of the Oracle RDBMS.
Like its mainframe predecessor, CFEIS uses batch processing. This means that CFEIS
periodically processes the data left in users' mailboxes, or placed in the submission database by
EPA analysts. Transaction reports and other report requests are also processed in this periodic
fashion. CFEIS picks up submissions and drops off reports every 2 hours.
As shown in Exhibit 2-1, the system accepts the information that constitutes the manufacturer's
application for a Certificate of Conformity for vehicle emissions. It also accepts the information
required to perform the calculations for the fuel economy label and CAFE. CFEIS generates the
Certificate of Conformity and calculation results that verify the fuel economy calculations
performed by the manufacturer.
The system periodically transmits Shift Schedule information to the Testing Services Division's
(TSD) Laboratory Network System (LNS), which performs the confirmatory tests. LNS, in turn,
transmits the confirmatory test results to CFEIS. Once in the system, the confirmatory test
results are reviewed by the certification analyst responsible for issuing the Certificate of
Conformity.
CFEIS generates standard reports that VPCD must provide to external entities (that is, an
organizational unit outside of EPA). The external entities and the reports they receive are as
follows:
CAFE Report., Department of Transportation.
Fuel Economy Guide, Department of Energy.
Gas Guzzler Tax Report, Internal Revenue Service.
Annual Certification Test Results Report, public distribution.
General Label Test Car Lists, public distribution.
Freedom of Information Act (FOIA) responses to public inquiries.
Ad hoc queries meeting a variety of internal and external requests.
In addition to the reports listed above, CFEIS generates processing reports that provide feedback
to manufacturers about their data submissions. The system generates one or more reports in
response to every type of submission processed.
-------
March 28, 2001 (REV.)
i
£
ill
Exhibit 2-1. CFEIS Operations
-------
March 28, 2001 (REV.)
2.2 Personnel Interaction
A number of different types of users and operators interact with CFEIS. The first and most
important is the manufacturer. CFEIS facilitates the processing of information submitted by the
manufacturer for the Certificate of Conformity and fuel economy calculations. CFEIS accepts all
of the manufacturer's submissions and checks the information for consistency and accuracy. The
system then generates the Certificate of Conformity and the results of the fuel economy
calculations. The manufacturer receives both products.
Two types of VPCD personnel interact with CFEIS. The first is the certification analyst, who
interacts with the manufacturer and reviews the manufacturer's submissions. CFEIS automates
much of the edit checking that must be performed on manufacturer submissions. The
certification analyst monitors the submission acceptance process and reviews final submission
information to determine if the manufacturer's application for certification can be accepted. If a
manufacturer's test results must be verified, the certification analyst schedules a confirmatory test
with TSD.
VPCD's Automated Data Processing (ADP) analyst also interacts with CFEIS. The ADP analyst
maintains CFEIS and monitors technical system operations to ensure that the system functions
properly. Among the ADP analyst's duties are database administration, maintenance of the
business process and data models, maintenance and development of software to support
functionality outside the scope of CFEIS, resolution of manufacturer and EPA user problems,
and incorporation of new regulations into future versions of CFEIS.
2.3 System Configuration and Operation
CFEIS consists of a database server, workstations, and an electronic interface used by
manufacturers at remote sites for submitting and storing data and for processing reports. The
RDBMS stores and retrieves CFEIS data. The ADP analysts use CFEIS to perform their
technical functions.
CFEIS gives each manufacturer access to a single UNIX workstation connected to the CFEIS
LAN. A modem and a UNIX File Transfer Protocol (FTP) enable the manufacturer to both send
submission files to and receive report files from the CFEIS server through the workstation's data
storage disk. The CFEIS server periodically (that is, every 2 hours) reads the data from the
workstation's hard disk into its own mass storage. The workstation is capable of maintaining up
to six concurrent dial-in sessions. Appendix D, Input Data Record Layouts, contains instructions
for formatting the electronic files used for submissions.
-------
March 28, 2001 (REV.)
Manufacturers are assured of having a secure repository within CFEIS for their data submissions
and the reports requested or generated by the system. The CFEIS workstation is configured with
a 5-megabyte UNIX partition for each manufacturer, and no manufacturer can access or view the
files in another manufacturer's partition. Regardless of the data submission's source (magnetic
diskette, paper forms from the NVFEL, or electronic data transfer), the system identifies the
manufacturer who originated the file and stores the file in that manufacturer's partition. Exhibit
2-2, illustrates disk partitioning on the workstation.
The system transfers data from the manufacturer's workstation to the CFEIS server for
processing. The system identifies the manufacturer making the submission and places a copy of
the Submission Summary Report in the manufacturer's partition. The system also places an
identical copy of each Submission Summary Report in an archive partition. The archive partition
is not accessible to manufacturers, but EPA-designated system users may retrieve the Submission
Summary Reports that are generated. The system retains the archived Submission
Summary Reports online for at least 60 days.
Manufacturer #1
Interface Workstation
Modem
Modems
cummin
Telephone Dial-up
Telephone Dial-up
|EHEHEHEH<
Modem
EHEHEHEIK
EHEHEHEIK
EHEHEHEH<
EHEHEHEIK
EHEHEHEH<
linn
linn
Interface Workstation
Hard Disk
Manufacturer #2
Exhibit 2-2. Electronic File Transfer
10
-------
March 28, 2001 (REV.)
After the 60-day online period, they are copied to archive tapes. The system automatically moves
the Submission Summary Report to the manufacturer's workstation partition after processing
has been completed. All EPA users interact with the CFEIS server, while all manufacturers
interact only with the workstations. Exhibit 2-3 illustrates CFEIS processing of manufacturer
data.
The manufacturers are responsible for managing, cleaning up, and removing the Submission
Summary Reports in their partitions on the workstation.
EPA computer operations accepts manufacturers' data submissions in ASCII format copied
onto 3.5-inch magnetic diskettes.
CFEIS Ethernet LAN
M anufacturer's
P a rtitio n
File 2
File 3
Report 1
Report 2
CFEIS
in itia te s file
pickup
R eport 3
CFEIS
drops off
transaction
report
C o nte nts
of
F
lie
2
Exhibit 2-3. Processing by the CFEIS Server
11
-------
March 28, 2001 (REV.)
The submission data are represented as flat-file ASCII formats corresponding to those defined in
Appendix D, Input Data Record Layouts.
Manufacturers may submit data on paper forms. Appendix E, Input Forms, contains the paper
forms used for paper submission. To enter the data from the paper forms into CFEIS, the flat-file
ASCII formats are prepared using a data input software package. The system processes the flat
file just as if it had been delivered to NVFEL on a diskette or through a telecommunications link.
Reports for the data submitted on diskette or paper forms will be generated in hard copy
printouts.
2.4 Input Data Structure
Submissions to CFEIS are for one subsystem and one manufacturer. Each submission contains
one or more transactions. A transaction is a type of action that CFEIS performs on the data
submitted (for example, Add, Modify, Delete, Report, etc). A transaction contains one or more
input records followed by a ZZ record. The ZZ record indicates to CFEIS that the transaction has
ended.
Each subsystem has different allowable transaction types. The transaction type is generally
determined by the process code for the first input record of the transaction. Some record types do
not have process codes. In that case, the transaction type is determined by the presence or
absence of other record types within the transaction. The scope of a process code can be limited
to a subset of the fields in a single input record; however, within a transaction different
combinations of process codes are allowed.
When submitting data to CFEIS, you should do the following:
Organize your data by CFEIS subsystem.
Verify subsystem data dependency
Organize subsystem data by valid transaction type (Add, Modify, Delete, etc.).
Find the correct input record type (within each subsystem) in Appendix D or E for each
of your data entries.
Verify input record dependencies.
Some input records are independent while others require one or more specified input
records in the same submission to make the record complete. Sections 3.0 through 11.0
each contain a table listing these dependencies. Ensure that your submission
12
-------
March 28, 2001 (REV.)
includes the additional input record(s) for each dependent record. Exhibit 2-4
summarizes the transaction types for each subsystem.
Transaction Process
Code
Add (A or blank)
Modify (M)
Replace (R)
Delete (D)
Change (N)
Report (P)
Summary Report (Y)
Cancel (F)
Carryover (C)
Carry Across (X)
Re-activate (G)
Re-process (S)
CFEIS Subsystem
CL
ESI
EvSI
VI
SH
MTDS
SS
GL
CAFE
Exhibit 2-4. Transaction Type Summary
When entering your data you should do the following:
Observe the data input rules discussed in Sections 3 through 11, Input Notes.
Observe the Valid Range/Entry Criteria for each data field as shown in Appendix D, or
the Entry Field Description for each field in Appendix E.
Ensure that all required field entries are correct and complete. Appendix D shows the
required and optional fields for each transaction type and input record.
End each transaction with a ZZ record.
13
-------
March 28, 2001 (REV.)
2.4.1 Data Entry
Data may be entered into CFEIS from magnetic diskette, paper forms, or electronic data transfer
(FTP). If you want to enter your data on paper forms, you will find the input forms you need in
Appendix E. On the back of the form are the valid range/entry criteria to help you determine
what values to put into each block.
If you want to enter your data on magnetic diskettes or through electronic data transfer, use the
input data record layouts found in Appendix D. The input data record layouts give the field
names, transaction types; indicate whether the field is allowable, required, or optional; and show
the position, length, data type, and valid range/entry criteria for each record type allowable for
each subsystem. Since CFEIS processes the input data record layouts by subsystem, record type,
and column position, make sure to include only the submission record types for one subsystem
using the proper column position for the field placement.
2.4.1.1 Field Justification
Alphanumeric fields should be left justified. Numeric fields may be left or right justified. It is
recommended that right justification be used.
2.4.2 Input Data Formats
When you input your data, either on paper forms or electronically, use the following formats (see
also Appendix D):
A = Alphanumeric character.
R = Real number (with precision defined as n.n under the element Length).
I = Integer number.
D = Date (in the format of MMDDYYYY).
2.4.3 Decimals in Input Data
If you are entering data that contain decimals, you must include the decimal point. The system
will not put it in for you.
14
-------
March 28, 2001 (REV.)
2.4.4 Input Data File Names
Exhibit 2-5 shows the names of the files that the manufacturers drop off in CFEIS and the names
of the Submission Status Report files that the system sends back to the manufacturers. The
input data record layouts in Appendix D show the required fields in each transaction, the starting
position of the field in the input record, the length and type of the fields, and so on.
Input File
Name
carline.in
esi.in
evsi.in
vi.in
shift, in
mtds.in
summary.in
gl.in
cafe.in
Output File
Name
carline.out
esi.out
evsi.out
vi.out
shift.out
mtds.out
summary.out
gl.out
cafe.out
File Content
Car Line
ESI
EvSI
Vehicle Information
Shift Schedule
Manufacturer Test Data
Summary Sheet Data
General Label Fuel Economy
Corporate Average Fuel
Economy
Exhibit 2-5. CFEIS Mail Box Files
2.4.5 Input Notes and Calculations
Each subsystem has validations that are performed and for some subsystems CFEIS computes
values from the input data submitted. The following subsections describe the rules you must
follow to ensure successful validation of the data submitted. We have called those rules Input
Notes. In addition, if CFEIS makes calculations on the data you submit, we give you the
equations that CFEIS uses to perform those calculations.
15
-------
March 28, 2001 (REV.)
This page is intentionally left blank.
16
-------
March 28, 2001 (REV.)
3.0 CAR LINE (CL)
3.1 Car Line Input/Output File Names
Input file name: carline.in
Output file name: carline.out
3.2 Car Line Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
M (Modify)
D (Delete)
Use this code to enter new data into the Car Line database. CFEIS
will generate an exception condition if the data are already in the
database. The exception condition results in the transaction being
rejected after the input data have been scanned for as many
additional error conditions as possible. See also Car Line Input
Notes Subsection 3.3.
Use this code to modify existing data in the Car Line database. For
Modify process codes, optional fields containing non-blank input
data replace existing data in the database. CFEIS leaves existing
data in the database unchanged if the input value is blank. To
blank out a numeric field, enter an * in any column of the field.
To blank out a text field, enter an * in every column of the field.
If the asterisks do not fill the entire field, they will become part of
the text. CFEIS generates an exception condition if the database
does not contain the data to be modified. The exception condition
results in the transaction being rejected after the input data have
been scanned for as many additional error conditions as possible.
See also Car Line Input Notes Subsection 3.3.
Use this code to delete existing data in the Car Line database.
CFEIS generates an exception condition if the database does not
contain the data to be deleted. The exception condition results in
the transaction being rejected after the input data have been
scanned for as many additional error conditions as possible. See
also Car Line Input Notes Subsection 3.3.
17
-------
March 28, 2001 (REV.)
3.3 Car Line Input Notes
3.3.1 Add and Modify Transactions
The rules are as follows:
Specify passenger and luggage volumes for at least one body style on a C2 record if the
vehicle is a passenger car and not a 2-seater.
When you create a new Car Line, use an Add process code on the C1 record with a new
Car Line code.
The sum of the average passenger and luggage volumes that you enter for a Car Line
must be within the tolerances specified for the Class code (see Exhibit 3-1).
Class
Code
2
3
4
5
6
7
8
9
Sum of Averages
Minimum
>1
85
100
110
120
1
130
160
Maximum
<85
<100
<110
<120
200
<130
<160
200
Exhibit 3-1. Sum of Averages per Class Code
When you enter passenger and luggage volumes for the following:
- 2-door.
- 4-door.
- Hatchback vehicles.
the values must be within 20 percent of the average volume specified.
18
-------
March 28, 2001 (REV.)
Vehicle Information, Summary Sheet, General Label, and CAFE may need to be
re-processed if Car Line data are modified.
3.3.2 Delete Transactions
The CFEIS will not allow you to delete a Car Line that you have used in a General Label index,
Vehicle Configuration, or Summary Sheet.
3.3.3 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 3-2 shows the Input record
dependencies for the Car Line subsystem.
Car Line
Input Record
Type
Cl
C2
CS
zz
Input Record
Dependency
None
None
Cl
Valid Transactions
A^D1
Implied M
A,D
All Transactions
CFEIS Table(s)
Car Line
Car Line
Car Line State Restrictions
Exhibit 3-2. Car Line Input Record Dependencies
1 Transactions Legend:
A= Add M= Modify D= Delete
ZZ= Termination
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
3.4 Conversion of MTS CFEIS Car Line and Manufacturer Codes
CFEIS uses different Car Line and Manufacturer codes than the Michigan Terminal System
(MTS)CFEIS did. In MTS CFEIS, a Car Line was defined by a 3-digit Car Line Manufacturer
code and a 2-digit Car Line code. A Car Line Manufacturer code less than or
19
-------
March 28, 2001 (REV.)
equal to 500 indicated a car manufacturer, and a code greater than 500 indicated a truck
manufacturer.
In CFEIS, the 3-digit Car Line Manufacturer code has been replaced by a 2-digit Division code.
Each Car Line manufacturer is assigned a Division code based on the alphabetically ordered Car
Line manufacturer names for a specific VI manufacturer. For example, Chrysler's Car Line
Manufacturer codes convert as shown in Exhibit 3-3.
Car Line
Manufacturer Name
Chrysler
Chrysler
Dodge
Dodge
Eagle
Eagle
Imperial
Jeep
Jeep
Plymouth
Plymouth
Car Line
Manufacturer Code
130
620
160
650
161
651
214
850
652
320
910
Division Code
1
1
2
2
3
3
4
5
5
6
6
Exhibit 3-3. Sample Car Line Code Conversion
The distinction between car and truck manufacturers is no longer relevant at the division level in
CFEIS. Instead, the car/truck division is made for each Car Line using the Class code. Each
Class code is identified as either a car or truck. As a result, the Car Line code is not always
unique within a division. Therefore, if the Car Line Manufacturer code is greater than 500, then
100 is added to the MTS Car Line code for the translation to CFEIS. For example, Car Line
code 95 is a Q-Car for Car Line Manufacturer 130 and the same Car Line code 95 is a Caravan
4WD for Car Line Manufacturer 620. Both Car Line Manufacturers 130 and 620
20
-------
March 28, 2001 (REV.)
become Division Code 1 in CFEIS. Therefore, Car Line code 95 for Car Line Manufacturer 620
(that is, Caravan 4WD) translates to Car Line code 195 in CFEIS.
21
-------
March 28, 2001 (REV.)
This page is intentionally left blank.
22
-------
March 28, 2001 (REV.)
4.0 ENGINE SYSTEMS INFORMATION (ESI)
4.1 E SI Input/Output File Names
Input file name: esi.in
Output file name: esi.out
4.2 ESI Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
M (Modify}
D (Delete}
R (Replace}
Use this code to enter new data into the ESI database. CFEIS will
generate an exception condition if the data are already in the
database. The exception condition results in the transaction being
rejected after the input data have been scanned for as many
additional error conditions as possible. See also ESI Input Notes
Subsection 4.3.
Use this code to modify existing data in the ESI database. For
Modify process codes, optional fields containing non-blank input
data replace existing data in the database. CFEIS leaves existing
data in the database unchanged if the input value is blank. To
blank out a numeric field, enter an * in any column of the field.
To blank out a text field, enter an * in every column of the field.
If the asterisks do not fill the entire field, they will become part of
the text. CFEIS generates an exception condition if the database
does not contain the data to be modified. The exception condition
results in the transaction being rejected after the input data have
been scanned for as many additional error conditions as possible.
See also ESI Input Notes Subsection 4.3.
Use this code to delete existing data in the ESI database. CFEIS
generates an exception condition if the database does not contain
the data to be deleted. The exception condition results in the
transaction being rejected after the input data have been scanned
for as many additional error conditions as possible. See also ESI
Input Notes Subsection 4.3.
Use this code to replace with input data all existing data in the ESI
database. Replace can be considered equivalent to a Delete
transaction followed by an ^^transaction. Unlike the Modify
23
-------
F (Cancel)
March 28, 2001 (REV.)
process code, a blank input in optional fields does replace existing
database values. CFEIS generates an exception condition if the
database does not contain data to be replaced. The exception
condition results in the transaction being rejected after the input
data have been scanned for as many additional error conditions as
possible. See also ESI Input Notes Subsection 4.3.
A Cancel process code is used to cancel an Engine subsystem.
Canceling an ESI subsystem preserves existing information in the
CFEIS database while indicating that it will not be used. See also
ESI Line Input Notes Subsection 4.3.
A Re-activate process code is used to re-activate an Engine
subsystem that was previously canceled.
A Report process code is used to generate an Engine Family/ Test
Group report for a given manufacturer.
G (Re-activate)
P (Report)
4.3 ESI Input Notes
4.3.1 Add Transactions
The rules are as follows:
In the ESI database, a transaction must begin with and include only one El or E2 input
record. This means that operations can be performed for a single Engine system or
Engine subsystem in a transaction. If you are adding an El or E2 input record only to
provide key field data for other input records in the transaction, you must include a
Modify M process code in the El or E2 record.
If you do not specify the following:
- Emission standard.
- Phase-in-percentage.
- Additive DF.
- Multiplicative DF.
24
-------
March 28, 2001 (REV.)
when you add an EG record, CFEIS will look up and apply a corresponding emission
standard based on model year, tier, useful life, Cert/In-Use code, LVW range, ALVW
range, ignition type, emission name, sales area, GVW category, and fuel type. If the
database does not contain a corresponding emission standard, it assigns 0 to the additive
DF, 1 to the multiplicative DF, and 0 to the phase-in percentage.
If you enter a value less than 0 for additive DF, CFEIS will use value 0 for calculation of
certification level. However, the entered value is retained in the CFEIS database.
If you enter a value less than 1 for multiplicative DF, CFEIS will use value 1 for
calculation of certification level. However, the entered value is retained in the CFEIS
database.
4.3.2 Modify and Replace Transactions
The rules are as follows:
You cannot modify or replace ESI data if there is a VI record against it. ESI subsystems
may be added even if a VI exists for an engine system.
When modifying or replacing an E2 record, you must include a non-blank value for DF
type if you have never entered the DF type for the Engine subsystem that you are
modifying.
If you do not specify the following:
- Emission standard.
- Phase-in-percentage.
- Additive DF.
- Multiplicative DF.
when you replace an EG record, CFEIS will look up and apply a corresponding emission
standard based on model year, tier, useful life, Cert/In-Use code, LVW range, ALVW
range, ignition type, emission name, sales area, GVW category, and fuel type. If the
database does not contain a corresponding emission standard, it assigns 0 to the additive
DF, 1 to the multiplicative DF, and 0 to the phase-in percentage.
25
-------
March 28, 2001 (REV.)
If you enter a value less than 0 for additive DF, CFEIS will use value 0 for calculation of
certification level. However, the entered value is retained in the CFEIS database.
If you enter a value less than 1 for multiplicative DF, CFEIS will use value 1 for
calculation of certification level. However, the entered value is retained in the CFEIS
database.
To replace the following:
- Combustion cycle.
- Ignition type.
- Fuel system.
- Valves per cylinder.
- Turbocharger supercharger.
- Catalyst.
- Trap.
- California OBD.
- Federal OBD.
- Production code.
the pre-conversion codes must match the values associated with the existing Engine
Family/Test Group.
A Replace process code on an El input record replaces an Engine system, not an Engine
Family/Test Group.
Vehicle Information, Summary Sheet, General Label, and CAFE may need to be
re-processed if ESI data are modified or replaced.
26
-------
March 28, 2001 (REV.)
4.3.3 Delete Transactions
The rules are as follows:
You may delete a subsystem without deleting the associated system.
You cannot delete ESI data if you have used the data in a Summary Sheet and that
Summary Sheet is locked.
You cannot delete a subsystem if the Engine system containing the subsystem is used by
a vehicle configuration and the vehicle configuration references a sales area that
corresponds to the subsystem.
The Delete process code on the El input record deletes an Engine system and all its
associated Engine subsystems. You cannot perform any Delete operations on an Engine
system until CFEIS is no longer using any of the associated subsystems. If the last
Engine system that you are deleting is also the last one for that family, the Engine
Family/Test Group will be deleted.
You cannot delete subsystem numbers unless they are the highest numbered subsystem
in the Engine system.
4.3.4 Cancel Transactions
You cannot cancel a subsystem more than three times.
4.3.5 E2 and ES Input Records
Exhibits 4-1 through 4-7 give the codes to be entered on the E2 and ES input records for sales
area, vehicle class, and exhaust emission standards.
For California sales areas, note that EPA uses the federal definition of LVW and ALVW and
EPA's definition is not necessarily the same as California's. For example, California has used
two different definitions of LVW: one for 1994 and another for later model years. For 1994,
California's definition of LVW is the same as the federal definition of LVW. For later model
years; however, California's definition is the same as the federal definition of ALVW. The
following exhibits, including those for California, use the federal definitions.
27
-------
March 28, 2001 (REV.)
Engine Family/Test Group Names
EPA standardized Engine Family/Test Group names are described in detail in Appendix F of
this document.
Engine Family/Test Group Related Information
Sales Area Codes
Codes
CA
FA
NL
NE
CF
-6T
Sales Area
California + Section 177 States (includes California Tier 1,
TLEV, LEV, ULEV, ZEV vehicles)
Federal All Altitude (Tier
NLEV - All States Trading
ULEV, ZEV)
NLEV - Northeast Trading
ZEV in 1999; TLEV Only
1)
Region (TLEV, LEV,
Region (TLEV, LEV, ULEV,
in 2000. Obsolete in 2001.)
Federal Clean Fueled Fleet Areas (LEV, ULEV,
ILEV, ZEV)
(Obsolete)
If Certified to Same Standards:
CE
CL
NF
CA + NE
CA + NL
CA + NL + CF
Exhibit 4-1. Sales Area Codes (Federal and California)
28
-------
March 28, 2001 (REV.)
Vehicle Class Codes: 1998 and Later
Code
V
Tl
T2
T3
T4
T5
T6
VT
Fuel
Any
Description
GVWR
0-6000
>6000
ALVW
LDV or CARB's PC
Any
3751-5750
>5751
3751-5750
>5751
LVW
0-3750
3751-5750
0-3750
>3751
LDV and LDT1 (or CARS' s PC and LDT1)
Tierl
LDV
LDT1
LDT2
LDT3
LDT4
LDT3
LDT4
LVT
Exhibit 4-2. Light-Duty Vehicle Class Codes (Federal and California)
Vehicle Class Codes: 1995, 1996 and 1997
Code
V
1
2
3
4
5
6
7
8
Fuel
Any
Description
GVWR ALVW LVW
LDV or CARB's PC
0-6000
>6000
N/A
Any
3751-5750
>5751
3751-5750
>5751
N/A
0-3750
3751-5750
0-3750
>3751
0-3750
>3751
Tierl
LDV
LDT1
LDT2
LDT3
LDT4
LDT3
LDT4
N/A
TierO
LDV
N/A
LDT-A-NOx 1.2
LDT-B-NOx 1.7
Exhibit 4-3. Light-Duty Vehicle Class Codes (Federal and California)
For Model Years 1995, 1996 and 1997 Only
29
-------
March 28, 2001 (REV.)
HC/CO/NOx
TierO
Tierl
TLEV
TLEV + ILEV
LEV
LEV + ILEV
ULEV
ULEV + ILEV
ZEV
ZEV + ILEV
In use
TierO
TierO
Tier 11
Tier IF
TLEV
TLEV + ILEV
LEV
LEV + ILEV
ULEV
ULEV + ILEV
ZEV
ZEV + ILEV
PM
TierO
Tierl
TierO
Tierl
TierO
Tierl
TierO
Tierl
TLEV
TLEV + ILEV
LEV
LEV + ILEV
ULEV
ULEV + ILEV
ZEV
ZEV + ILEV
Cold CO
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
Y
N
N
N
Standards Code
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
30
32
Exhibit 4-4. Codes for Exhaust Emission Standards (Federal and National)
30
-------
March 28, 2001 (REV.)
Code
CO
Cl
CT
CL
CU
cz
cs
Description
TierO
Tierl
TLEV
LEV
ULEV
ZEV (Electric)
SLEV
Exhibit 4-5. Exhaust Emission Standards Codes (California)
Codes for Exhaust Emission Standards: 1998 LEV Standards
To determine emission standards from the Engine Family/Test Group name, you must determine
the ALVW and LVW for the vehicle class, combustion cycle, fuel, and standards. For Clean
Fuel vehicles, the definition of test weight in 40 CFR, Part 86.101-94, is identical to the
definition of ALVW.
4.3.6 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 4-8 shows the Input record
dependencies for the ESI subsystem.
31
-------
March 28, 2001 (REV.)
Engine System Information
Input Record
Type
El
EE
EC
ZZ
E2
ES
EG
ET
ZZ
Input Record
Dependency
None
El
El
None
E2
ES
E2
Valid Transactions
AMRAPJsG1
A,D
A,M,R
All Transactions
A,M,R,D,P,F,G
A,M,R,D
A,M,R,D
A,M,R
All Transactions
CFEIS Table(s)
Engine Family/Test Group
Engine System
Engine System Emission Component
Engine System
Engine Subsystem
Engine Subsystem Fuel
Engine Subsystem Standard
EG Standard Cross Reference
Engine Subsystem
Exhibit 4-6. ESI Input Record Dependencies
"Transactions Legend:
A= Add M= Modify R= Replace D= Delete
F= Cancel G= Re-activate ZZ= Termination
P= Report
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
NOTE: Either an El or an E2 must be included in a transaction; however, both cannot be
included in the same transaction.
32
-------
March 28, 2001 (REV.)
5.0 EVAPORATIVE/REFUELING SYSTEMS INFORMATION (EvSI)
5.1 EvSI Input/Output File Names
Input file name: evsi.in
Output file name: evsi out
5.2 EvSI Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
M (Modify)
D (Delete)
R (Replace}
Use this code to enter new data into the EvSI database. CFEIS will
generate an exception condition if the data are already in the
database. The exception condition results in the transaction being
rejected after the input data have been scanned for as many
additional error conditions as possible. See also EvSI Input Notes
Subsection 5.3.
Use this code to modify existing data in the EvSI database. For
Modify process codes, optional fields containing non-blank input
data replace existing data in the database. CFEIS leaves existing
data in the database unchanged if the input value is blank. To
blank out a numeric field, enter an * in any column of the field. To
blank out a text field, enter an * in every column of the field. If
the asterisks do not fill the entire field, they will become part of the
text. CFEIS generates an exception condition if the database does
not contain the data to be modified. The exception condition
results in the transaction being rejected after the input data have
been scanned for as many additional error conditions as possible.
See also EvSI Input Notes Subsection 5.3.
Use this code to delete existing data in the EvSI database. CFEIS
generates an exception condition if the database does not contain
the data to be deleted. The exception condition results in the
transaction being rejected after the input data have been scanned
for as many additional error conditions as possible. See also EvSI
Input Notes Subsection 5.3.
Use this code to replace with input data all existing data in the
EvSI database. Replace can be considered equivalent to a Delete
transaction followed by an ^^transaction. Unlike the Modify
33
-------
F (Cancel)
G (Re-activate)
P (Report)
5.3 EvSI Input Notes
5.3.1 Add Transactions
The rules are as follows:
March 28, 2001 (REV.)
process code, a blank input in optional fields does replace existing
database values. CFEIS generates an exception condition if the
database does not contain data to be replaced. The exception
condition results in the transaction being rejected after the input
data have been scanned for as many additional error conditions as
possible. See also EvSI Input Notes Subsection 5.3.
Use this code to cancel an EvSI subsystem. Canceling an EvSI
subsystem preserves existing information in the database while
indicating that it will not be used. See also EvSI Input Notes
Subsection 5.3.
Use this code to re-activate an EvSI subsystem that you previously
canceled.
Use this code to generate an Evaporative Family Report for a given
manufacturer.
In the EvSI database, a transaction must begin with and include only one PI or P2 input
record. This means that operations can be performed for a single Evaporative system or
Evaporative subsystem in a transaction. If you are adding a PI or P2 input record only
provide key field data for other input records in the transaction, you must include a
Modify M process code in the PI or P2 record.
If you do not specify the following:
- Emission standard.
- Phase-in-percentage.
- Additive DF.
- Multiplicative DF.
34
-------
March 28, 2001 (REV.)
when you add an EG record, CFEIS will look up and apply a corresponding emission
standard based on model year, tier, useful life, Cert/In-Use code, LVW range, ALVW
range, ignition type, emission name, sales area, GVW category, and fuel type. If the
database does not contain a corresponding emission standard, it assigns 0 to the additive
DF, 1 to the multiplicative DF, and 0 to the phase-in percentage.
If you enter a value less than 0 for additive DF, CFEIS will use the value 0 for
calculation of certification level. However, the entered value is retained in the CFEIS
database.
If you enter a value less than 1 for multiplicative DF, CFEIS will use the value 1 for
calculation of certification level. However, the entered value is retained in the CFEIS
database.
When you add an Evaporative system on a PI record, also include a vapor storage system
and combustion cycle.
5.3.2 Modify or Replace Transactions
The rules are as follows:
You cannot modify or replace EvSI data if you have used the data in a Summary Sheet
and that Summary Sheet is locked.
When affecting a change to the fuel material, you should use the 'A', 'R', or 'D' process
code for the PM input record, which would be contained within a PI Modify transaction.
Use multiple PM input records to append more than 72 characters of new text.
When modifying or replacing a P2 record, you must include a non-blank value for DF
type if you have never entered the DF type for the Evaporative subsystem that you are
modifying or replacing. No fuel material validation checks are performed to the text
field; however, the fuel material field should indicate the type of material: plastic, metal
or combined.
If you do not specify the following:
- Emission standard.
- Phase-in-percentage.
35
-------
March 28, 2001 (REV.)
- Additive DF.
- Multiplicative DF.
when you replace an EG record, CFEIS will look up and apply a corresponding emission
standard based on model year, tier, useful life, Cert/In-Use code, LVW range, ALVW
range, ignition type, emission name, sales area, GVW category, and fuel type. If the
database does not contain a corresponding emission standard, it assigns 0 to the additive
DF, 1 to the multiplicative DF, and 0 to the phase-in percentage.
If you enter a value less than 0 for additive DF, CFEIS will use the value 0 for
calculation of certification level. However, the entered value is retained in the CFEIS
database.
If you enter a value less than 1 for multiplicative DF, CFEIS will use the value 1 for
calculation of certification level. However, the entered value is retained in the CFEIS
database.
You cannot Add, Modify, or Delete canister configurations on a Replace transaction.
Vehicle Information, MTDS, and Summary Sheet may need to be re-processed if EvSI
data have been modified or replaced.
5.3.3 Delete Transactions
The rules are as follows:
You may delete a subsystem without deleting the associated system.
You cannot delete EvSI data if you have used the data in a Summary Sheet and that
Summary Sheet is locked.
You cannot delete a subsystem if the Evaporative Family system containing the
subsystem is used by a vehicle configuration and the vehicle configuration references a
sales area that corresponds to the subsystem.
The Delete process code on the PI input record deletes an Evaporative Family system and
all its associated Evaporative Family subsystems. You cannot make any deletes on an
Evaporative Family system until CFEIS is no longer using any of the associated
subsystems. If the Evaporative Family system that you are deleting is the last one for the
family, CFEIS will delete the entire family.
36
-------
March 28, 2001 (REV.)
5.3.4 Cancel Transactions
You cannot cancel a subsystem more than three times.
5.3.5 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 5-1 shows the Input record
dependencies for the EvSI subsystem.
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
NOTE: Either a PI or a P2 must be included in a transaction; however, both cannot be included
in the same transaction.
Evaporative Family Names
EPA standardized evaporative family names are described in detail in Appendix F of this
document.
37
-------
March 28, 2001 (REV.)
Evaporative System Information
Input Record
Type
PI
PF
PM
PE
PC
ZZ
P2
PS
PT
PG
ZZ
Input Record
Dependency
None
PI
PI
PI
PI
None
P2
P2
PS
Valid Transactions
AMRAP^G1
A,M,D
A,M,D
A,D
A,M,R
All Transactions
A,M,R,D,P,F,G
A,M,R,D
A,M,R
A,M,R,D
All Transactions
CFEIS Table(s)
Evaporative Family
Evaporative Family System
Evaporative Family
Evaporative Family System
Evaporative System Emission Component
Evaporative Family Subsystem
Evaporative Family Subsystem
Evaporative Family Subsystem Fuel
Evaporative Family Subsystem
Evaporative Family Subsystem Standard
PG Standard Cross Reference
Exhibit 5-1. EvSI Input Record Dependencies
transactions Legend:
A=Add M= Modify R= Replace D= Delete
F= Cancel G= Re-activate ZZ= Termination
P= Report
38
-------
March 28, 2001 (REV.)
6.0 VEHICLE INFORMATION (VI)
6.1 VI Input/Output File Names
Input file name: vi.in
Output file name: vi out
6.2 VI Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
M (Modify)
D (Delete)
N (Change)
(CarryAcross)
Use this code to enter new data into the VI database. CFEIS will
generate an exception condition if the data are already in the
database. The exception condition results in the transaction being
rejected after the input data have been scanned for as many
additional error conditions as possible. See also VI Input Notes
Subsection 6.3.
Use this code to modify existing data in the VI database. For
Modify process codes, optional fields containing non-blank input
data replace existing data in the database. CFEIS leaves existing
data in the database unchanged if the input value is blank. To
blank out a numeric field, enter an * in any column of the field. To
blank out a text field, enter an * in every column of the field. If
the asterisks do not fill the entire field, they will become part of the
text. CFEIS generates an exception condition if the database does
not contain the data to be modified. The exception condition
results in the transaction being rejected after the input data have
been scanned for as many additional error conditions as possible.
See also VI Input Notes Subsection 6.3.
Use this code to delete existing data in the VI database. CFEIS
generates an exception condition if the database does not contain
the data to be deleted. The exception condition results in the
transaction being rejected after the input data have been scanned
for as many additional error conditions as possible. See also Car
Line Input Notes Subsection 6.3.
Use this code to duplicate and create a new instance of a
configuration using existing configuration data. The Change/
39
-------
March 28, 2001 (REV.)
CarryAcross transaction is similar to Add, except that for Change
or CarryAcross CFEIS creates a new record with a configuration
number equal to the next available unused configuration number.
If there is test data for the configuration being changed or carried
across, the test data will be carried across to the new configuration.
See also VI Input Notes Subsection 6.3.
C (Carry Over) Use this code to carry over the specification data for a particular
vehicle configuration from one year to another year. Vehicle
configurations can be carried forward as well as back. All the tests
for the configuration will be automatically carried over to the new
model year See also VI Input Notes Subsection 6.3.
P (Report) Use this code to generate a VI report for a given manufacturer.
6.3 VI Input Notes
6.3.1 Add, Modify, Change and CarryAcross Transactions
The rules are as follows:
On an ^^transaction, specify at least the following:
- One fuel system using a VF record.
- The Engine system.
The CFEIS database must contain a DF type for each Engine subsystem that you identify
for the vehicle.
The CFEIS database must contain a DF type for each Evaporative subsystem that you
identify for the vehicle.
If the engine type is 03 and the fuel type is 09 and the vehicle is not equipped with any
add-on exhaust control systems, use a value of 002 for the emission control system.
When specifying the manufacturer coastdown time, also specify the following:
- Tire manufacturer.
- Tire construction code.
40
-------
March 28, 2001 (REV.)
- Recommended in-use front tire pressure.
- Recommended in-use rear tire pressure.
- Tire pressure units.
Specify 099 (Other) for the exhaust control system for a vehicle with the ESI exhaust
emission-related component codes of 01 (Combustion Chamber/Non-Conventional Valve
Train), 60 (Detonation Sensor), 61 (Electronic Controls - Analog), 62 (Electronic
Controls - Digital), or 99 (Other).
For engine type use only Otto Spark 01, Stratified Charge 02, or Diesel 03 for the Engine
Type code.
If you specify Ignition Timing #1, you must also specify the following:
- Ignition timing before/after code.
- Ignition timing RPM tolerance.
- Ignition timing degree tolerance.
- Ignition timing RPM.
- Ignition timing gear code.
If you specify idle RPM, you must also specify the following:
- Idle RPM tolerance.
- Idle gear code.
6.3.2 Add or Change or Carry Across Transactions
The rules are as follows:
If you are submitting a VP record that specifies an EvSI system, you must also specify the
following:
41
-------
March 28, 2001 (REV.)
- Canister type.
- Bed volume per canister.
- Working capacity per canister.
- Total number of canisters of that type on the vehicle.
6.3.3 Modify Transactions
The rules are as follows:
Specify an existing vehicle-configuration number for the following:
- Manufacturer code.
- Vehicle identification.
- Model year.
If the Engine or EvSI subsystem DF Type code is 1, 2, 3, 4, 5, or 6 and the vehicle is a
durability vehicle, you cannot correct the Sales Area code.
You cannot change the following:
- Design gross vehicle weight.
- Design curb weight.
- Design equivalent test weight.
- Manufacturer ETW units code.
- Ignition timing #1.
- Ignition timing #1 before/after code.
- Ignition timing RPM.
- Ignition timing RPM tolerance.
42
-------
March 28, 2001 (REV.)
- Ignition timing degree tolerance measure.
- Transmission-configuration code.
- Odometer correction sign indicator code.
- Odometer initial correct measure.
- Odometer correction factor measure.
- Idle RPM measure.
- Idle RPM tolerance measure.
- Idle gear code.
You cannot submit a VT record with a. Modify process code if you have conducted a test
on the vehicle configuration for the test procedure and vehicle fuel type identified by the
VT record that you are submitting.
MTDS, Summary Sheet, General Label, and CAFE may need to be re-processed if VI
data are modified.
6.3.4 Delete Transactions
You cannot do the following:
- Remove the last fuel system for a vehicle.
- Delete a vehicle configuration if the system number for the Engine Family specified
in the VI data has been certified.
- Delete a vehicle configuration if the system number for the Evaporative Family
specified in the VI data has been certified.
- Delete a vehicle configuration if the CFEIS database contains tests associated with
the vehicle configuration.
- Delete a vehicle configuration if the data have been carried over to another model
year.
43
-------
March 28, 2001 (REV.)
6.3.5 Carry Over Transactions
You cannot do the following:
- Carry over a durability vehicle to a non-durability vehicle.
- Carry over a non-durability vehicle to a durability vehicle.
6.3.6 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 6-1 shows the Input record
dependencies for the VI subsystem.
Vehicle Information
Input Record
Type
VI
V2
V3
V4
V5
VP
VF
VT
VC
zz
Input Record
Dependency
None
VI
VI
VI
VI
VI
VI
VI
VI
Valid Transactions
A^AN^C1
A,M,N
A,M,N,C
A,M,N,C
A,M,N
A,M,D
A,M,D
A,M,D
A,M,N,C
All Transactions
CFEIS Table(s)
Vehicle Configuration
Vehicle Configuration
Vehicle Configuration
Vehicle Configuration
Vehicle Configuration
Vehicle Evaporative System
Vehicle Fuel System
Test Procedure Fuel
Vehicle Configuration
Exhibit 6-1. VI Input Record Dependencies
"Transactions Legend:
A=Add M= Modify D= Delete P= Report
N= Change C= Carry Over ZZ= Termination
44
-------
March 28, 2001 (REV.)
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
NOTE: An add transaction must have at least one VI, one V3, and one VF record.
45
-------
March 28, 2001 (REV.)
This page is intentionally left blank.
46
-------
March 28, 2001 (REV.)
7.0 SHIFT SCHEDULE (SH)
7.1 Shift Schedule Input/Output File Names
Input file name: shift.in
Output file name: shift.out
7.2 Shift Schedule Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
M (Modify)
D (Delete)
Use this code to enter new data into the Shift Schedule database.
CFEIS will generate an exception condition if the data are already
in the database. The exception condition results in the transaction
being rejected after the input data have been scanned for as many
additional error conditions as possible. See also Shift Schedule
Input Notes Subsection 7.3.
Use this code to modify existing data in the Shift Schedule
database, for Modify process codes, optional fields containing
non-blank input data replace existing data in the database. CFEIS
leaves existing data in the database unchanged if the input value is
blank. To blank out a numeric field, enter an * in any column of
the field. To blank out a text field, enter an * in every column of
the field. If the asterisks do not fill the entire field, they will
become part of the text. CFEIS generates an exception condition if
the database does not contain the data to be modified. The
exception condition results in the transaction being rejected after
the input data have been scanned for as many additional error
conditions as possible. See also Shift Schedule Input Notes
Subsection 7.3.
Use this code to delete existing data in the Shift Schedule database.
CFEIS generates an exception condition if the database does not
contain the data to be deleted. The exception condition results in
the transaction being rejected after the input data have been
scanned for as many additional error conditions as possible. See
also Shift Schedule Input Notes Subsection 7.3.
47
-------
March 28, 2001 (REV.)
R (Replace) Use this code to replace with input data all existing data in the
Shift Schedule database. Replace can be considered equivalent to
a Delete transaction followed by an ^^transaction. Unlike the
Modify process code, a blank input in optional fields does replace
existing database values. CFEIS generates an exception condition
if the database does not contain data to be replaced. The exception
condition results in the transaction being rejected after the input
data have been scanned for as many additional error conditions as
possible. See also Shift Schedule Input Notes Subsection 7.3.
N (Change) Use this code to create a new Shift Schedule by modifying a copy
of a standard EPA Shift Schedule or an existing manufacturer Shift
Schedule. See also Shift Schedule Input Notes Subsection 7.3.
P (Report) Use this code to generate a Shift Schedule Family report for a
given manufacturer.
Y (Summary Report) Use this code to generate a report of all Shift Schedules submitted
by one vehicle manufacturer.
7.3 Shift Schedule Input Notes
The rules are as follows:
You must provide an SI record type for all Shift Schedule transactions regardless of the
process code.
Only one SI record type may exist per transaction.
7.3.1 Add, Replace, and Change Transactions
The rules are as follows:
Specify only one record for each of the following record types:
- S2.
- S3.
48
-------
March 28, 2001 (REV.)
- S4.
- S7.
Specify at least one S8 record type.
On the S3 and S4 records, specify declutch speeds for each consecutive gear as follows:
- Gearl_2.
- Gear2_3.
- Gear3_4.
- Gear4_5.
- Gear5_6.
If you specify declutch speeds for cruise, also specify declutch speeds for non-cruise.
If you specify declutch speeds for non-cruise, also specify declutch speeds for cruise.
7.3.2 Add and Replace Transactions
You must provide shift points using SP records for Add and Replace transactions.
7.3.3 Modify and Change Transactions
On SP records, Modify and Change process codes for Shift Schedule transactions cause the shift
points to merge with the shift points already in the CFEIS database.
7.3.4 Add and Change Transactions
The Add and Change process codes for Shift Schedule transactions cause CFEIS to assign a new
shift schedule number to the Shift Schedule.
7.3.5 Modify, Delete, and Replace Transactions
You cannot Modify, Delete, or Replace Shift Schedule data if the Shift Schedule has been used
in a test.
49
-------
March 28, 2001 (REV.)
7.3.6 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 7-1 shows the Input record
dependencies for the Shift Schedule subsystem.
Shift Schedule
Input Record
Type
SI
S2
S3
S4
S5
S6
S7
S8
SP
sc
zz
Input Record
Dependency
None
SI
SI
SI
SI
SI
SI
SI
SI
SI
Valid Transactions
A^RAN^Y1
A,M,R,N
A,M,R,N
A,M,R,N
R
R
A,M,R,N
A,M,R,N
A,M,R,N
A,M,R,N
All Transactions
CFEIS Table(s)
Shift Schedule
Shift Schedule (Data Originator)
Drive Schedule
Shift Schedule Model Year
Shift Point
Shift Schedule
Exhibit 7-1. Shift Schedule Input Record Dependencies
"Transactions Legend:
A= Add M= Modify
N= Change Y= Summary Report
R= Replace D= Delete P= Report
ZZ= Termination
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
50
-------
March 28, 2001 (REV.)
8.0 EPA/MANUFACTURER TEST DATA (MTDS)
8.1 MTDS Input/Output File Names
Input file name:
Output file name:
Output file name:
mtds.in
mtds.out
mtds.epa (EPA confirmatory tests)
8.2 MTDS Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
M (Modify)
D (Delete)
Use this code to enter new data into the MTDS database. CFEIS
will generate an exception condition if the data are already in the
database. The exception condition results in the transaction being
rejected after the input data have been scanned for as many
additional error conditions as possible. See also MTDS Input
Notes Subsection 8.3.
Use this code to modify existing data in the MTDS database. For
Modify process codes, optional fields containing non-blank input
data replace existing data in the database. CFEIS leaves existing
data in the database unchanged if the input value is blank. To
blank out a numeric field, enter an * in any column of the field. To
blank out a text field, enter an * in every column of the field. If
the asterisks do not fill the entire field, they will become part of the
text. CFEIS generates an exception condition if the database does
not contain the data to be modified. The exception condition
results in the transaction being rejected after the input data have
been scanned for as many additional error conditions as possible.
See also MTDS Input Notes Subsection 8.3.
Use this code to delete existing data in the MTDS database.
CFEIS generates an exception condition if the database does not
contain the data to be deleted. The exception condition results in
the transaction being rejected after the input data have been
scanned for as many additional error conditions as possible. See
also MTDS Input Notes Subsection 8.3.
51
-------
R (Replace)
C (Carry Over)
X (Carry Across)
March 28, 2001 (REV.)
Use this code to replace with input data all existing data in the
MTDS database. Replace can be considered equivalent to a Delete
transaction followed by an ^^transaction. Unlike the Modify
process code, a blank input in optional fields does replace existing
database values. CFEIS generates an exception condition if the
database does not contain data to be replaced. The exception
condition results in the transaction being rejected after the input
data have been scanned for as many additional error conditions as
possible. See also MTDS Input Notes Subsection 8.3.
Use this code only to carry over those test data that did not get
carried over during the vehicle configuration carry over process.
CFEIS generates a new set of model-year-dependent data for the
carried over data See also MTDS Input Notes Subsection 8.3.
Use this code to carry across test results to a different vehicle
configuration. CFEIS generates a new set of configuration-
dependent data for the carried across data. See also MTDS Input
Notes Subsection 8.3.
Use this code to re-capture any corrected/updated data in related
subsystems and re-calculate affected results (Cert Level, Pass/Fail,
etc.) for the specified configuration and the model year.
Use this code to generate an MTDS report for a given
manufacturer.
S (Re-process)
P (Report)
8.3 MTDS Input Notes
The rules are as follows:
CFEIS generates a unique test number for each new MTDS submission.
EPA test numbers are generated outside of CFEIS and submitted by TSD.
During the processing of EPA test data into CFEIS, the input is placed into a file named
mtdstsdin under the manufacturer's subdirectory. This file is appended to the mtds.in at
the time CFEIS processing occurs at the even hour. The file, mtdstsdin
52
-------
March 28, 2001 (REV.)
should not be altered or removed by the manufacturer. The EPA test results are placed in
the manufacturer's mtds.out file, along with manufacturer test results, if any.
CFEIS assigns a test number with a value of 1XXXXXX (X = 0-9) for a manufacturer
test.
Manufacturers must use a valid Vehicle ID for the Manufacturer code that you specify.
Only EPA may enter a reason for confirmation, and it may only be entered for a
confirmatory test.
8.3.1 Add Transactions
The rules are as follows:
If the fuel type is diesel, you cannot specify the following:
- Batch ID.
- Container ID.
- Fuel calibration number.
If the fuel type is diesel, you do not need to specify a Test Lab Site code.
For EvSI tests, you do not need to specify the following:
- Dyno site.
- Test analyzer site.
- Test Lab Site code.
For cold CO, light truck idle CO, or short tests, you do not need to specify the following:
- Test Group code.
- Average code
A Fuel Batch calibration (T4 record) may only be entered on an add transaction for a city
or highway test, where the VI fuel type is not diesel.
53
-------
March 28, 2001 (REV.)
8.3.2 Modify and Replace Transactions
The rules are as follows:
You must specify a test number that already exists in the MTDS database.
You cannot change the values for the Manufacturer code and vehicle ID.
You cannot change the values for model year or configuration number if the test has been
carried over or carried across to another vehicle configuration.
You may change the model year or configuration number to values present in the VI
database, if the test data have not been carried over or carried across to another vehicle
configuration.
You cannot modify or replace test data that have been used to support a Certificate of
Conformity for the specified EvSI or Engine system (diesel-fueled vehicles).
You may modify test data (other than dispositions) only if the value for certification
disposition or fuel economy disposition is one of the codes representing the following:
- No disposition.
- Undefined because of error.
If some other value for certification disposition or fuel economy disposition has been
stored in the database, you can modify data only if your input contains certification
disposition or fuel economy disposition codes that remove existing dispositions.
You may not modify any EPA test data except the Fuel Economy Disposition code.
If a test has been carried over or carried across, you may modify only the following fields:
- Test purpose.
- Certification disposition.
- Fuel economy disposition.
54
-------
March 28, 2001 (REV.)
If you submit a correction for a specified configuration and model year and the Engine or
EvSI Family system has not been certified, CFEIS re-calculates all configuration model-
year data.
Summary Sheet, General Label, and CAFE may need to be re-processed if MTDS data
are modified, replaced, or re-processed.
Measured fuel property data for a Fuel Batch ID/Calibration Number need only be
entered once as a part of the first test's input.
Measured fuel property data for a Fuel Batch ID/Calibration Number may only be
modified on a. Modify transaction for a city or highway test, where the VI Fuel Type is not
diesel and the test being modified references the fuel batch.
Measured fuel property data for a Fuel Batch ID/Calibration Number may only be
modified if none of the tests that reference the fuel batch support a locked certificate.
If a measured fuel property data for a Fuel Batch ID/Calibration Number are modified,
the fuel economy results for all tests that reference the fuel batch are re-calculated and the
disposition codes are re-assigned accordingly (CFEIS Release 2.0 and later).
8.3.3 Delete Transactions
The rules are as follows:
You cannot delete test data used to support a locked Certificate of Conformity.
You may delete configuration model-year-dependent test results (for example, rounded
emission results, certification levels, etc.) only if they are associated with the following:
- Test number.
- Configuration number.
- Vehicle ID.
- Model year.
55
-------
March 28, 2001 (REV.)
that you specify when you delete test data. If your deletion removes the last occurrence of
configuration model-year-dependent results for the test number that you specify,
CFEIS deletes the test number and all test data associated with it.
A Fuel Batch cannot be deleted from the system once entered.
8.3.4 Carry Over or Carry Across Transactions
The rules are as follows:
You cannot Modify Manufacturer code and configuration number when you are carrying
over test data.
You cannot Modify Manufacturer code and Vehicle ID when you are carrying across test
data.
You cannot Carry Over or Carry Across test data until the technical disposition for a test
has been assigned.
When you carry over test data, specify a new value for model year.
When you Carry Over or Carry Across test data, CFEIS generates a new instance of the
configuration model-year-dependent test results and updates the CFEIS database with the
results. Configuration model-year-dependent results include the following:
- Rounded emission results.
- Deterioration factors.
- Certification levels.
- Emission standards used for the test.
- Emission level pass/fail.
- Test level pass/fail.
- Test fuel economy.
56
-------
March 28, 2001 (REV.)
When you Carry Across test data, specify a new configuration number (required) and
model year (optional).
8.3.5 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 8-1 shows the Input record
dependencies for the MTDS subsystem.
EPA/Manufacturer Test Data System (MTDS)
Input Record Type
Tl
T2
T3
T4
TR
TC
ZZ
Input Record
Dependency
None
Tl
Tl
Tl
Tl
Tl
Valid Transactions
AMRAPA^S1
A,M,R
A,M,R
A,M,R
A,M,R
A,M,R
All Transactions
CFEIS Table(s)
Test
Test
Fuel Batch
Test
Fuel Batch
Unrounded Emission Results
Test
Exhibit 8-1. MTDS Input Record Dependencies
"Transactions Legend:
A=Add M= Modify R= Replace D= Delete P= Report
C= Carry Over X= Carry Across S= Re-process ZZ= Termination
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
57
-------
March 28, 2001 (REV.)
8.4 System-Generated Calculations
CFEIS takes unrounded test results received from either a manufacturer or TSD, and rounds
them to meet the minimum precision specified in the Code of Federal Regulations (CFR).
CFEIS rounds test results according to the following rounding criteria:
When the digit following the digit in the rounding position is less than 5, CFEIS
truncates the digits following the digit in the rounding position.
When the digit following the digit in the rounding position is greater than 5, CFEIS
truncates the digits following the digit in the rounding position and adds 1 to the digit in
the rounding position.
When the digit following the digit in the rounding position is 5 and there are no trailing
digits (or only zeroes), CFEIS truncates the digits following the digit in the rounding
position and adds 1 to the rounding digit if it is odd. If any trailing digits exist beyond the
5 following the rounding digit, CFEIS truncates the digits following the digit in the
rounding position and adds 1 to the rounding digit.
CFEIS determines certification levels. These certification levels are the adjusted
exhaust/evaporative emission test results after deterioration factors and rounding methods have
been applied. CFEIS compares the adjusted emission values against the standard to determine
vehicle compliance.
CFEIS determines emission level pass/fail. Pass/fail determinations are made by comparing the
adjusted emission values (certification levels) to the emission standards. A passing emission
value is less than or equal to the emission standard. These standards are set forth by the Clean
Air Act and stated in the CFR.
CFEIS determines sales area pass/fail. If you are requesting certification of an Engine/
Evaporative family that is to be sold across sales areas, (that is, CA - California, FA - federal all-
altitude, NL - national LEV, CF - Clean Fuel vehicle, CT - Clean Fuel vehicle/ Tier 1), submit
test data for each sales area. CFEIS determines vehicle compliance based on a comparison to
the standard values applicable for each individual sales area.
CFEIS assigns a Certification Disposition code to vehicle tests that are either performed by the
manufacturer or EPA The Certification Disposition code identifies how a test is used in the
certification process. CFEIS disallows assignment of a Certification Disposition code other than
the codes for Undefined Because of Error or No Disposition until the Technical Disposition
code has been assigned.
58
-------
March 28, 2001 (REV.)
CFEIS assigns a Fuel Economy Disposition code to vehicle tests performed by the manufacturer
or EPA. The Fuel Economy Disposition code is used to indicate how a test is used in the fuel
economy process. CFEIS disallows assignment of a Fuel Economy Disposition code until the
Certification Disposition code has been assigned.
CFEIS internally stores and retrieves 2-digit disposition codes. You indicate these codes
through the use of 1-digit user codes, and CFEIS recognizes these 1-digit codes as representing
the corresponding 2-digit codes on the basis of the input records employed and the position of
the 1-digit codes within the input records.
CFEIS performs fuel economy calculations based on constant fuel (diesel only), measured fuel,
or methanol flexible-fuel, natural gas fuel, or California Phase 2 fuel properties. There are no
fuel calculations for ethanol, hydrogen, or LPG. The results of these calculations are compared
to manufacturer reported fuel economy values for accuracy. These calculations are performed in
accordance with the provisions defined in the CFR. Specifically, the following formulas, as
stated in Part 600, Subpart F, §600.113-93 of the July 1, 1994, edition of the 40 CFR, are
identified for these calculations. The mathematical notation in the equations below has been
revised to make it consistent with the notation most commonly used in Federal regulations.
8.4.1 Unrounded Unadjusted Fuel Economy/Measured Fuel Properties
This equation is used to perform fuel economy calculations for 1988 and later model year
vehicles.
UUFEmfp = [51740000.0 x CWFxSG]/[((CWFxHC) +(0.429 x CO) +
(0.273 x CO2)) x ((0.6 x SG x NHV) + 5471)]
where:
UUFEmfp = Unrounded unadjusted fuel economy using measured fuel
properties.
CWF = Test fuel carbon weight fraction.
SG = Test fuel specific gravity.
NHV = Test fuel net heating value.
HC = Hydrocarbons in grams per mile.
59
-------
March 28, 2001 (REV.)
CO
CO,
Carbon monoxide in grams per mile.
Carbon dioxide in grams per mile.
8.4.2 Unrounded Unadjusted Fuel Economy/Methanol Flexible-Fueled Vehicles
UUFE,
'mfiv
where:
'mfiv
EXHC
UUFE,
CWF
SG
CWF
HC
CO
CO2
CH3OH
HCHO
[3781.8 x CWF x SG] / [(CWFEXHC x HC) +(0.429 x CO) + (0.273
x CO2) + (0.375 x CH3OH) + (0.400 x HCHO)]
Unrounded unadjusted fuel economy for vehicles tested
on methanol test fuel.
Test fuel carbon weight fraction.
Test fuel specific gravity.
Carbon weight fraction of exhaust hydrocarbons.
Hydrocarbons in grams per mile.
Carbon monoxide in grams per mile.
Carbon dioxide in grams per mile.
Methanol in grams per mile.
Formaldehyde in grams per mile.
8.4.2.5 Unrounded Unadjusted Fuel Economy Equation
for Ethanol Flexible-Fueled Vehicles:
UUFE
'efiv
[3781.8 x CWFblend x SGblend] / [ CWFEXHC x HC) + (0.429 x CO)
(0.273 x CO2) + (0.375 x CH3OH) + (0.400 x HCHO) +
(0.521 x C2H5OH) + (0.545 x C2H4O)]
where:
60
-------
March 28, 2001 (REV.)
UUFEefiV = Unrounded unadjusted fuel economy for vehicles tested
on ethanol test fuel.
CWF = Carbon weight fraction of the fuel.
SG = Specific gravity of the fuel.
CWFEXHC = Is assumed to be equal to CWFblend.
and emissions are expressed in grams/mile.
8.4.3 Unrounded System Miles or Kilometers
(1) If
Odometer Correction Sign = +
then
USYSMI/KM = (Odometer x Factor) + Initial
(2) If
Odometer Correction Sign = -
then
USYSMI/KM = (Odometer - Initial) x Factor
where:
USYSMI/KM = Unrounded system miles or kilometers.
Odometer = Test odometer reading, rounded to the nearest whole
number.
Initial = Initial odometer reading (reported with VI).
Factor = Correction factor (reported with VI).
NOTE: The odometer correction sign is reported with VI.
61
-------
March 28, 2001 (REV.)
8.4.4 Conversion of System Kilometers to System Miles
This equation is used if the odometer reading is reported in kilometers.
SYSMI = USYSMI/(KM x 0.62137119)
where:
SYSMI = System miles.
USYSMI = Unrounded system miles.
KM = Kilometers.
NOTE: The result is rounded to the nearest whole number.
8.4.5 Unrounded Mileage-Adjusted Fuel Economy
NOTE: The adjustment takes place only if the system miles is greater than 6200.
UMAFE = FE / [(0.00000525 x SYSMI) + 0.979]
where:
UMAFE = Unrounded mileage-adjusted fuel economy.
FE = Unadjusted fuel economy rounded to one decimal place.
SYSMI = System miles.
8.4.6 Fuel Economy Calculations for Vehicles Tested on California Phase 2 Gasoline
CFEIS calculates fuel economy values for vehicles tested on California Phase 2 gasoline.
These calculations are performed in accordance with the procedures set forth in the Dear
Manufacturer letter CD-95-09, MPG Calculations for Certification Vehicles Tested on
California Phase 2 Gasoline.
62
-------
March 28, 2001 (REV.)
(1) UUFECO
where:
UUFE
[CWFblendxSGblendx 51740000] /
[((1.03 x CWFexHC x HC) + (.429 x CO) + (.273 x CO2)) x
((0.6 x SGblend x NHVblend) +5471)]
Corrected unrounded unadjusted fuel economy for vehicles
fueled using CARB Phase 2 gasoline. This is the official
EPA mpg value for certification vehicles tested on CARB
Phase 2 gasoline. Data indicate that this mpg value is
partially corrected for the differences in fuel properties
between Phase 2 test fuel and 1975 EPA test fuel.
CFWblend = Carbon weight fraction of the fuel.
= Specific gravity of the fuel.
CWFexHC = Carbon weight fraction of exhaust hydrocarbons.
NHVblend = Net heating value of the fuel.
HC = Hydrocarbons in grams per mile.
CO = Carbon monoxide in grams per mile.
CO2
(2) UUFEuncoir
where:
= Carbon dioxide in grams per mile.
[CWFblendxSGblendx 3781.8] /
[(1.03 x CWFexHC x HC) + (.429 x CO) +(.273 x CO2)]
UUFEuncorr = Uncorrected unrounded unadjusted fuel economy for
vehicles fueled using CARB Phase 2 gasoline. This is the
uncorrected (volumetric) mpg value for certification
vehicles tested on CARB Phase 2 gasoline.
63
-------
March 28, 2001 (REV.)
CFWblend = Carbon weight fraction of the fuel.
Sgbiend = Specific gravity of the fuel.
CWFexHC = Carbon weight fraction of exhaust hydrocarbons.
NHVblend = Net heating value of the fuel.
HC = Hydrocarbons in grams per mile.
CO = Carbon monoxide in grams per mile.
CO2 = Carbon dioxide in grams per mile.
8.4.7 Fuel Economy Calculations for Vehicles Tested Using Natural Gas Fuel
CFEIS calculates fuel economy values for vehicles tested using natural gas fuel as specified in
the 40 CFR Parts 80, 85, 86, 88, and 600, Standards for Emissions From Natural Gas-Fueled,
and Liquefied Petroleum Gas-Fueled Motor Vehicles and Motor Vehicle Engines, and
Certification Procedures for Aftermarket Conversions; Final Rule.
UUFENo = [CWFHC/NGxDNGx 121.5] /
[(0.749 x CH4) + (CWFNMHc x NMHC) + (0.429 x CO) +
(0.273 x (C02 - C02NG))]
where:
= Miles per equivalent gallon of natural gas
CWFHC/NG = Carbon weight fraction based on the hydrocarbon
constituents in the natural gas fuel.
DNG = Density of the natural gas fuel [grams per foot3 at 680F
(200C) and 760 mm Hg (101.3 kPa)]
CH4 = Weighted mass exhaust emissions in grams per mile for
methane.
64
-------
NMHC
CO
CO9
CWF
NMHC
CO
2NG
where:
FC
NG
where:
March 28, 2001 (REV.)
Weighted mass exhaust emissions in grams per mile for
nonmethane hydrocarbons.
Weighted mass exhaust emissions in grams per mile for
carbon monoxide.
Weighted mass exhaust emissions in grams per mile for
carbon dioxide.
Carbon weight fraction of the non-methane HC constituents
of the fuel as determined from the speciated fuel
composition.
Grams of carbon dioxide in the natural gas fuel consumed
per mile of travel, equal to FCNG x DNG x WFC02
Cubic feet of natural gas consumed per mile.
CWF
NG
WF,
CO2
[(0.749 x CH4) + (CWFNMHc x NMHC) + (0.429 x
CO) + (0.273 x C02)] / [CWFNG x DNG]
Carbon weight fraction of the natural gas
fuel.
Weight fraction carbon dioxide of the
natural gas fuel calculated using mole
fractions and molecular weights of the
natural gas fuel constituents.
8.4.8 Fuel Economy Calculations for Vehicles Tested Using Diesel Fuel
UUFEn = 2778 / [(0.866 0x0 x HC) + (0.429 x CO) + (0.273 x CO2)]
where:
65
-------
March 28, 2001 (REV.)
= Uncorrected unrounded unadjusted fuel economy for
vehicles fueled using diesel fuel.
HC = Weighted mass exhaust emissions in grams per mile for
hydrocarbons.
CO = Weighted mass exhaust emissions in grams per mile for
carbon monoxide.
CO2 = Weighted mass exhaust emissions in grams per mile for
carbon dioxide.
66
-------
March 28, 2001 (REV.)
8.4.9 Test Type/Test Purpose
CFEIS associates Test Purpose/Test Type codes with definition strings as shown in
Exhibit 8-2.
Test Type/Test Purpose Code
01
02
04
05
06
07
08
11
21
22
23
24
25
26
30
31
32
33
45
Definition String
Emission data
Durability
Surveillance
Experimental
Sulfate
Particulates
Manufacturers' development
Correlation
Experimental (TSD)
Recall
Emission factor
In-use feasibility
Fuel tampering
Independent commercial importer
TSD other
Fuel economy data
Analytical fuel economy data
Certification or fuel economy for other years (carry over)
Methanol
Exhibit 8-2. Test Type/Test Purpose Codes
67
-------
March 28, 2001 (REV.)
8.4.10
Test Procedure Codes
CFEIS associates Test Procedure codes with definition strings, as shown in two parts in Exhibit
8-3.
Test Procedure Code
02
03
10
11
13
15
21
23
24
25
27
28
31
34
35
38
41
43
44
45
47
51
Definition String
CVS 75 - & Later (EPA city test w/o canister loading)
HWFE (Highway test)
Idle CO
Cold CO
Constant temperature evaporative (2-hr evap)
Spitback test
Federal Fuel 2-day Exhaust (C4H10 can load)
Federal Fuel 2-day Evap Test (C4H10 can load)
Federal Fuel Refueling Test (ORVR) (C4H10 canister loading)
California Fuel 2-day Exhaust (C4H10 can load)
California Fuel 2-day Evap Test (C4H10 can load)
California Fuel Refueling Test (ORVR) (C4H10 canister loading)
Federal Fuel 3-day Exhaust (C4H10 can load)
Federal Fuel 3-day Evap Test (C4H10 can load)
California Fuel 3-day Exhaust (C4H10 can load)
California Fuel 3-day Evap Test (C4H10 can load)
Federal Fuel 2-day Exhaust (heat fuel tank to load canister)
Federal Fuel 2-day Evaporative Test (heat fuel tank to load canister)
Federal Fuel Refueling Test (ORVR)
California Fuel 2-day Exhaust (heat fuel tank to load canister)
California Fuel 2-day Evaporative Test (heat fuel tank to load canister)
California Fuel SOT Exhaust Test
Exhibit 8-3. Test Procedures Codes
68
-------
March 28, 2001 (REV.)
Test Procedure Code
52
71
72
73
74
76
Definition String
Federal Fuel SOT Exhaust Test
CST - Idle Test (EPA Only)
CST - 2-speed Idle Test
CST - Loaded Test (EPA Only)
CST - Preconditioned Idle Test
(EPA Only)
CST - Preconditioned 2-speed Idle Test (EPA Only)
Exhibit 8-3. Test Procedure Codes (Continued)
69
-------
8.4.11
March 28, 2001 (REV.)
Valid Combinations of Test Type/Test Purpose and Test Procedure Codes
Exhibit 8-4, as shown in two parts, are combinations of Test Procedure codes with Test
Type/Test Purpose codes, where the presence of an X indicates that the combination is valid.
Test Procedure Code
02
03
10
11
13
15
21
23
24
25
27
28
31
34
Definition String
CVS 75 & Later (EPA city test
w/o canister loading)
HWFE (Highway test)
Idle CO
Cold CO
Constant temperature evaporative (2-hr evap)
Spitback test
Federal Fuel 2-day Exhaust (C4H10 can load)
Federal Fuel 2-day Evap Test
(C4H10 can load)
Federal Fuel Refueling Test (ORVR)
(C4H10 canister loading)
California Fuel 2-day Exhaust
(C4H10 can load)
California Fuel 2-day Evap Test
(C4H10 can load)
California Fuel Refueling Test (ORVR)
(C4H10 canister loading)
Federal Fuel 3-day exhaust
(C4H10 can load)
Federal Fuel 3-day Evap Test
(C4H10 can load)
Test Type/Test Purpose Code
01
X
X
X
X
X
X
X
X
X
X
X
X
X
X
02
X
X
X
X
X
X
X
X
X
X
X
X
X
OS
X
X
X
X
X
X
X
X
X
X
X
X
X
X
31
X
X
X
X
X
X
X
X
X
X
X
X
X
X
32
X
X
33
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Exhibit 8-4. Valid Combinations of Test Procedure Codes and Test Type/Test Purpose
Codes
70
-------
March 28, 2001 (REV.)
Test Procedure Code
35
38
41
43
44
45
47
51
52
71
72
73
74
76
Definition String
California Fuel 3-day Exhaust
(C4H10 can load)
California Fuel 3-day Evap Test
(C4H10 can load)
Federal Fuel 2-day Exhaust (heat fuel tank
to load canister)
Federal Fuel 2-day Evaporative Test
(heat fuel tank to load canister)
Federal Fuel Refueling Test (ORVR)
(heat fuel tank to load canister)
California Fuel 2-day Exhaust
(heat fuel tank to load canister)
California Fuel 2-day Evaporative Test
(heat fuel tank to load canister)
California Fuel 50°F Exhaust Test
Federal Fuel 50°F Exhaust Test
CST - Idle Test (EPA Only)
CST - 2-speed Idle Test
CST - Loaded Test (EPA Only)
CST - Preconditioned Idle Test
(EPA Only)
CST - Preconditioned 2-speed Idle Test
(EPA Only)
Test Type/Test Purpose Code
01
X
X
X
X
X
X
X
X
X
X
X
X
02
X
X
X
X
X
X
X
X
X
X
X
X
OS
X
X
X
X
X
X
X
X
X
X
X
X
X
X
31
X
X
X
X
X
X
X
X
X
X
X
X
32
33
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Exhibit 8-4. Valid Combinations of Test Procedure Codes and Test Type/Test Purpose
Codes (Continued)
71
-------
March 28, 2001 (REV.)
9.0
9.1
SUMMARY SHEET (SS)
Summary Sheet Input/Output File Names
Input file name:
Output file name:
summary.in
summary, out
9.2 Summary Sheet Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
D (Delete)
R (Replace)
S (Re-process)
P (Report)
Use this code to enter new data into the Summary Sheet database.
CFEIS will generate an exception condition if the data are already
in the database. The exception condition results in the transaction
being rejected after the input data have been scanned for as many
additional error conditions as possible. See also Summary Sheet
Input Notes Subsection 9.3.
Use this code to delete existing data in the Summary Sheet
database. CFEIS generates an exception condition if the database
does not contain the data to be deleted. The exception condition
results in the transaction being rejected after the input data have
been scanned for as many additional error conditions as possible.
See also Summary Sheet Input Notes Subsection 9.3.
Use this code to replace with input data all existing data in the
Summary Sheet database. Replace can be considered equivalent to
a Delete transaction followed by an ^^transaction. Unlike the
Modify process code, a blank input in optional fields does replace
existing database values. CFEIS generates an exception condition
if the database does not contain data to be replaced. The exception
condition results in the transaction being rejected after the input
data have been scanned for as many additional error conditions as
possible. See also Summary Sheet Input Notes Subsection 9.3.
Use this code to re-capture any corrected/updated data in other
subsystems See also Summary Sheet Input Notes Subsection
9.3.
Use this code to generate a report for a Summary Sheet index.
72
-------
March 28, 2001 (REV.)
9.3 Summary Sheet Input Notes
9.3.1 For All Transactions
For all transactions except Delete, CFEIS produces a report showing out-of-range data for the
car lines, Engine system, Evaporative system, tests, and vehicles associated with the Summary
Sheet information provided in the transaction. No Certificate of Conformity can be generated by
the VPCD ADP Analysts as long as out-of-range data are associated with the Summary Sheet.
Correct the out-of-range data by creating submissions in the subsystem where the error occurred
(for example, Car Line, ESI, EvSI, VI, or MTDS).
9.3.2 Add Transactions
When you input an Add process code, CFEIS generates a new Summary Sheet index number.
9.3.3 Add and Replace Transactions
Specify at least one XI, X2, and XT record in the transaction.
9.3.4 Re-process, Delete, and Report Transactions
Specify at least one XI record in the transaction.
9.3.5 Replace, Re-process, and Delete Transactions
You cannot change the Summary Sheet information if you have a Certificate of Conformity for
that Summary Sheet and the Certificate of Conformity is locked.
9.3.6 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 9-1 shows the Input record
dependencies for the Summary Sheet subsystem.
73
-------
March 28, 2001 (REV.)
Summary Sheet
Input Record
Type
XI
X2
xc
XT
zz
Input Record
Dependency
None
XI
XI
XI
Valid Transactions
A^D^S1
A,R
A,R
A,R
All Transactions
CFEIS Table(s)
Summary
Summary
Summary
Summary
Exhibit 9-1. Summary Sheet Input Record Dependencies
"Transactions Legend:
A=Add R= Replace D= Delete P= Report
S= Re-process ZZ= Termination
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
NOTE: Add and Replace must contain one XI and at least one X2 and one XT record.
74
-------
March 28, 2001 (REV.)
10.0 GENERAL LABEL
10.1 General Label Input/Output File Names
Input file name: gl.in
Output file name: gl out
10.2 General Label Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
D (Delete)
R (Replace)
S (Re-process)
Use this code to enter new data into the General Label database.
CFEIS will generate an exception condition if the data are already
in the database. The exception condition results in the transaction
being rejected after the input data have been scanned for as many
additional error conditions as possible. See also General Label
Input Notes Subsection 10.3.
Use this code to delete existing data in the General Label database.
CFEIS generates an exception condition if the database does not
contain the data to be deleted. The exception condition results in
the transaction being rejected after the input data have been
scanned for as many additional error conditions as possible. See
also General Label Input Notes Subsection 10.3.
Use this code to replace with input data all existing data in the
General Label database. Replace can be considered equivalent to a
Delete transaction followed by an ^^transaction. Unlike the
Modify process code, a blank input in optional fields does replace
existing database values. CFEIS generates an exception condition
if the database does not contain data to be replaced. The exception
condition results in the transaction being rejected after the input
data have been scanned for as many additional error conditions as
possible See also General Label Input Notes Subsection 10.3.
Use this code to re-compute or re-evaluate any corrected/ updated
General Label data and to record re-computed or re-evaluated
results See also General Label Input Notes Subsection 10.3.
75
-------
March 28, 2001 (REV.)
10.3 General Label Input Notes
The rules are as follows:
Use a Manufacturer code and Index number that when concatenated together represent a
unique Basic Engine Index within a model year.
If you specify lock-up RPM data, you must also specify lock-up range numbers.
If you are spanning multiple input records for a group of city or highway tests, you must
specify an averaging group indicator.
You cannot re-process fuel economy data after their release date has passed (that is, the
date on which the label information can be released to the public).
10.3.1 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 10-1 shows the Input
record dependencies for the General Label subsystem.
76
-------
March 28, 2001 (REV.)
General Label
Input Record
Type
Gl
G2
GM
GF
GR
GL
GT
GC
ZZ
Input Record
Dependency
None
Gl
G2
G2
GF
GF
GF
Gl
Valid Transactions
A^AS1
A,R
A,R
A,R
A,R
A,R
A,R
A,R
All Transactions
CFEIS Table(s)
General Label Basic Engine
General Label Base Level
General Label Model Type
General Label Submodel Type
General Label Configuration
General Label Subconfiguration
General Label Configuration Xref
General Label Gear Ratios
General Label Lockup RPM
General Label Test Group
General Label Basic Engine
Exhibit 10-1. General Label Input Record Dependencies
"Transactions Legend:
A= Add R= Replace D= Delete S= Re-process
ZZ= Termination
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column shows the kind of transactions that you
can submit. Your input record data will be stored in the respective CFEIS table.
10.4 System-Generated Calculations
CFEIS performs fuel economy calculations based on a manufacturer's General Label data
submission. The General Label calculations are performed in accordance with the provisions
defined in the CFR. Specifically, the following formulas (as stated in Part 600, Subpart F,
§600.207-86, §600.208-77, §600.209-85, and §600.513-81 of the July 1, 1994, edition of the 40
CFR) are identified for these calculations.
77
-------
March 28, 2001 (REV.)
10.4.1 Multiple tests on one test vehicle within one subconfiguration
FEVdty/hwy = n / £°i=i (1.0 DO / FET;)
where:
FEVcity/hwy = City or highway fuel economy for this vehicle.
DO = Double precision.
FET; = Fuel economy of test i which has been ASTM rounded to 1
decimal place.
City test are used for FEVcity calculation and highway tests
are used for FEVhwy
10.4.2 Subconfiguration-level MPG/City or Highway
FEScity/hwy = ASTM(4)[ n/£°i=1 (1.0 DO / FEV;)]
where:
ASTM(4) = round to 4 decimal places in accordance with the
"Rounding-Off Method" specified in ASTM E 29-67.
Throughout this document, ASTM(i) indicates ASTM rounding to i-th
decimal places.
FEScity/hwy = City or highway fuel economy for this subconfiguration.
DO = Double precision.
FEV; = City or highway fuel economy for vehicle i (from section
10.4.1) within this subconfiguration.
10.4.3 Configuration-level MPG/City or Highway
FECcity/hwy = ASTM(4)[ 1.0 DO / £°i=1 (SF; / FES;)]
where:
FECcity/hwy = City or highway fuel economy for this configuration.
78
-------
March 28, 2001 (REV.)
DO = Double precision.
SF; = ASTM(4)[ Sales; / Total Sales ]
Sales; = Sales for tested subconfiguration i within this
configuration.
Total Sales = Total tested subconfiguration sales within this
configuration.
FES; = City or highway fuel economy for subconfiguration i (from
section 10.4.2) within this configuration.
10.4.4 Configuration-level MPG/Combined
FECcomb = ASTM(4)[ 1.0 DO / (0.55 DO / FECdty+ 0.45 DO /
FEChwy)]
where:
FECcomb = Combined fuel economy for this configuration.
DO = Double precision.
FECcity = City fuel economy for this configuration from section
10.4.3.
FEChwy = Highway fuel economy for this configuration from section
10.4.3.
10.4.5 Base-level MPG/City, Highway, or Combined
FEE = ASTM(4)[ 1.0 DO / £ni=i (SF; / FEQ)]
where:
FEE = City, highway or combined fuel economy for this base
level.
79
-------
March 28, 2001 (REV.)
DO
Sales:
Sales
'total
FEC
Double precision.
ASTM(4)[ Sales; / Salestotal]
Sales for tested configuration i within this base-level.
Total tested configuration sales within this base level.
City, highway or combined fuel economy for configuration
i (from section 10.4.3 or 10.4.4) within this base-level.
10.4.6 Model-level MPG/City, Highway, or Combined
FEM = ASTM(4)[ 1.0 DO / £ni=i (SF; / FEB;)]
where:
FEM
DO
SF;
Sales;
Salestotal
City, highway or combined fuel economy for this model
type.
Double precision.
ASTM(4)[ Sales; / Salestotal]
Sales for base-level i within this model type.
Model type sales.
FEE;
City, highway or combined fuel economy for base-level i
(from section 10.4.5) within this model type.
10.4.7 Estimated Model Type MPG/City
FEEdty = ASTM(0)[ FEM(0.9 DO)]
where:
80
-------
FEEd,
FEM
DO
March 28, 2001 (REV.)
Estimated city fuel economy for this model type.
City fuel economy for this model type (from section
10.4.6).
Double precision.
10.4.8 Estimated Model Type MPG/Highway
FEE,
hwy
where:
FEE,
hwy
FEM
DO
ASTM(0)[ FEM(0.78 DO)]
Estimated highway fuel economy for this model type
Highway fuel economy for this model type (from section
10.4.6).
Double precision
10.4.9 Estimated Model Type MPG/Combined
FEE
where:
FEE
_L l j* >
comb
DO
FEIVL^
FEM,
hwy
ASTM(0)[ 1.0 DO / (0.55 DO / FEMdty(0.9 DO) + 0.45 DO /
FEMhwy(0.78 DO))]
Estimated combined fuel economy for this model type.
Double precision.
City fuel economy for this model type (from section
10.4.6).
Highway fuel economy for this model type (from section
10.4.6).
81
-------
March 28, 2001 (REV.)
10.4.10 Annual Fuel Cost
AFC
where:
AFC
FUCOST
FEEinv
DO
r EE,.,m|.
ASTM(0)[ FUCOST(15000 (FEEinv))]
Annual fuel cost for this model type.
Dollars per gallon (fuel cost).
ASTM(4)[1.0DO/FEEcomb)]
Double precision.
Estimated combined fuel economy of a given model
type (from section 10.4.9), or as submitted by manufacturer
on Gen. Label record type "GM".
10.4.11 Averaging/Weighting of tests
FEA = ASTM(1)[ £ni=i (FET; (WTi))]
where:
FEA = Average city or highway fuel economy for this group.
FET; = Fuel economy for test i (if a single test on a vehicle
configuration) or harmonically averaged fuel economy for
vehicle configuration i within the averaging group.
City or highway values are used as applicable.
V n. = 1 WT; = 1
NOTE: If multiple test data exist on a single test vehicle configuration, the harmonic average of
fuel economy values is first calculated for each vehicle configuration before weighted averaging
takes place.
82
-------
March 28, 2001 (REV.)
10.4.12 Fuel Economy Range/City or Highway
FERlow.end = 85(FEE)/100
FERugh^ = (115(FEE) + 99) / 100
where:
PER,
low-end
FEE
Fuel economy range minimum value.
Fuel economy range maximum value.
Adjusted city/highway fuel economy for this model type
(from section 10.4.7 or 10.4.8).
NOTE: FERlow.end and FERWgh.end are both truncated to whole numbers.
10.4.13 Adjusted MPG Calculation for Gas Guzzler
FEadj
where:
ASTM(1)[ FEMcomb [(0.55ac + 0.45c + 0.5556a + 0.4487) / (0.55a
+ 0.45)] + Iwg ]
FEadj
FEM,
comb
FEM,
hwy
FEM
r nivi
Adjusted fuel economy to be used for gas guzzler
assessment.
Combined fuel economy for this model type (from section
10.4.6).
ASTM(4)[FEMhwy/FEMdty]
Highway fuel economy for this model type (from section
10.4.6).
City fuel economy for this model type (from section
10.4.6).
2.501x 10'2 for model year 1980.
83
-------
March 28, 2001 (REV.)
2.184x 10-2formodel year 1981.
9.260x ID'3 for model year 1982.
1.435x 10-2formodel year 1983.
1.420x 10'2 for model year 1984.
1.490x 10-2formodel year 1985.
= l.SOQx 10"3 for model year 1986 and later model years.
Iwg = 0.0092917(SF3IWCG)(FE3IWCG)-
0.0035123(SF4ETWG)(FE4IWCG).
Any calculated value of Iwg less than zero shall be set to equal to zero.
SF3IWCG = ASTM(4)[ (sales at 3 000 IblWT)/total model type sales].
SF4ETWG = ASTM(4)[ (sales at 4000 Ib ETW)/ total model type sales ].
FEsiwcG = FEE (base-level combined fuel economy) at 3000 IWT
(from section 10.4.5).
FE4IWCG = FEB (base-level combined fuel economy) at 4000 IWT
(from section 10.4.5).
NOTE: Gas Guzzler calculation applies to passenger cars only.
84
-------
March 28, 2001 (REV.)
11.0 CORPORATE AVERAGE FUEL ECONOMY (CAFE)
11.1 CAFE Input/Output File Names
Input file name: cafe in
Output file name: cafe out
11.2 CAFE Transaction Process Codes
Process code explanations are as follows:
blank, A (Add)
D (Delete)
R (Replace)
S (Re-process)
Use this code to enter new data into the CAFE database. CFEIS
will generate an exception condition if the data are already in the
database. The exception condition results in the transaction being
rejected after the input data have been scanned for as many
additional error conditions as possible. See also CAFE Input
Notes Subsection 11.3.
Use this code to delete existing data in the CAFE database. CFEIS
generates an exception condition if the database does not contain
the data to be deleted. The exception condition results in the
transaction being rejected after the input data have been scanned
for as many additional error conditions as possible. See also
CAFE Input Notes Subsection 11.3.
Use this code to replace with input data all existing data in the
CAFE database. Replace can be considered equivalent to a Delete
transaction followed by an ^^transaction. Unlike the Modify
process code, a blank input in optional fields does replace existing
database values. CFEIS generates an exception condition if the
database does not contain data to be replaced. The exception
condition results in the transaction being rejected after the input
data have been scanned for as many additional error conditions as
possible See also CAFE Input Notes Subsection 11.3.
Use this code to re-compute or re-evaluate any corrected/ updated
CAFE data and to record re-computed or re-evaluated results. See
also CAFE Input Notes Subsection 11.3.
85
-------
March 28, 2001 (REV.)
11.3 CAFE Input Notes
The rules are as follows:
Use a Manufacturer code, compliance category, and index number that when
concatenated together represent a unique Basic Engine Index within a model year.
If you are spanning multiple input records for a group of city or highway tests, you must
specify an averaging group indicator.
Only refer to Engine subsystems whose data are active in the CFEIS database for ESI or
EvSI.
11.4 System-Generated Calculations
CFEIS calculates the official CAFE for a manufacturer based on their submission of the actual
total sales for a specified compliance category. The CAFE calculations are performed in
accordance to the provisions as defined in the CFR. Specifically, the following formulas, as
stated in Part 600, Subpart F, § 600.207-86, § 600.208-77, § 600.209-85, § 600.510-86 of the 7-
1-94 edition of the 40 CFR, are identified for these calculations:
11.4.1 CAFE
CAFE
where:
ASTM(4)[ Total Sales / £ni=i (Sales; (1.0 DO) / FEM;) ]
CAFE = City, highway or combined CAFE for a compliance
category.
Total Sales = Total of all model type sales within a compliance category.
Sales; = Sales of model type i within a compliance category.
DO = Double precision.
FEM; = City, highway or combined model type mpg (from section
11.4.8)
as applicable.
86
-------
March 28, 2001 (REV.)
NOTE: Combined CAFE rounded to 1 decimal place instead of 4 is the official CAFE for
trucks. If rounding to a different number of decimal places are called for, i in ASTM(i) will be
adjusted as applicable.
11.4.2 Adjusted Combined CAFE
Note: Adjusted Combined CAFE applies to passenger automobiles only
CAFEadj = ASTM(l)[CAFEcomb (0.55ac + 0.450c + 0.5556a + 0.4487) / (0.55a
+ 0.45) +FEIW
where:
CAFEadj = Adjusted CAFE for a compliance category.
CAFEcomb = Combined CAFE for a compliance category (from section
11.4.1).
a = ASTM(4)[CAFEhwy/CAFEdty].
CAFEdty = City CAFE (from section 11.4.1) .
CAFEhwy = Highway CAFE (from section 11.4.1) .
c = 0.0022, for model year 1986.
0.0050, for model year 1987.
0.0011, for model year 1988.
0.0011, for model year 1989.
0.0010, for model year 1990.
0.0011, for model year 1991.
0.0010, for model year 1992.
87
-------
March 28, 2001 (REV.)
0.0095, for model year 1993.
0.0011, for model year 1994.
0.0011, for model year 1995.
0.00095, for model year 1996.
0.001, for model year 1997.
FEIW = 0.0092917(SFIW3000)(FEIW3000) -
0.0035\23(SFEW4000)(FEIW4000)
Note: Any calculated value of FEIW less than zero shall be set equal to zero.
SFIW3000 = ASTM(4)[(sales at 3000 Ib IWT) / total sales ] .
SFEW4000 = ASTM(4)[ (sales at 4000 Ib ETW) / total sales ] .
FE^wsooo = ASTM(4)[ 1 / £ni=1 (SF3000 / base-level i combined fuel
economy at 3000 IWT) ]
SF3000 = ASTM(4)[ base-level i sales at 3000 IWT / total sales at
3000 IWT ]
FE^ooo = ASTM(4)[ 1 / £ni=1 (SF4000 / base-level i combined fuel
economy at 4000 IWT) ]
SF4000 = ASTM(4)[ base-level i sales at 4000 IWT / total sales at
4000 IWT ]
base-level i fuel economy = Combined fuel economy FEB from section
11.4.7.
Total Sales = Total production sales of a compliance category.
NOTE: If rounding to a different number of decimal places are called for, i in ASTM(i) will be
adjusted as applicable.
88
-------
March 28, 2001 (REV.)
All the terms and equations are applicable within a particular compliance category, e.g., "base-
level i fuel economy at 4000 IWT" indicates that each base level i is within the compliance
category being worked on.
11.4.3 Multiple tests on one test vehicle within one subconfiguration
FEVdty/hwy = n / £°i=i (1.0 DO / FET;)
where:
FEVcity/hwy = City or highway fuel economy for this vehicle.
DO = Double precision.
FET; = Fuel economy of test i which has been ASTM rounded to 1
decimal place.
City test are used for FEVcity calculation and highway tests
are used for FEVhwy
11.4.4 Subconfiguration-level MPG/City or Highway
FEScity/hwy = ASTM(4)[ n/£°i=1 (1.0 DO / FEV;)]
where:
FEScity/hwy = City or highway fuel economy for this subconfiguration.
DO = Double precision.
FEV; = City or highway fuel economy for vehicle i (from section
11.4.3) within this subconfiguration.
11.4.5 Configuration-level MPG/City or Highway
FECcity/hwy = ASTM(4)[ 1.0 DO / £°i=1 (SF; / FES;)]
89
-------
March 28, 2001 (REV.)
where:
FECdty/hwy = City or highway fuel economy for this configuration.
DO = Double precision.
SF; = (ASTM(4)[ (Sales; / Total Sales)]
Sales; = Sales for tested subconfiguration i at this configuration.
Total Sales = Total tested subconfiguration sales at this configuration.
FES; = City or highway fuel economy for subconfiguration i (from
section 11.4.4) within this configuration.
11.4.6 Configuration-level MPG/Combined
FECcomb = ASTM(4)[ 1.0 DO / (0.55 DO / FECcity+ 0.45 DO /
FEChwy)]
where:
FECcomb = Combined fuel economy for this configuration.
DO = Double precision.
FECcity = City fuel economy for this configuration from section
11.4.5.
FEChwy = Highway fuel economy for this configuration from section
11.4.5.
11.4.7 Base-level MPG/City, Highway, or Combined
FEE = ASTM(4)[ 1.0 DO / £ni=i (SF; / FEQ)]
where:
90
-------
FEE
DO
SF;
Sales;
Salestotal
PEG
March 28, 2001 (REV.)
City, highway or combined fuel economy for this base
level.
Double precision.
ASTM(4)[ (Sales; / Salestotal)]
Sales for tested configuration i within this base-level.
Total tested configuration sales within this base level.
City, highway or combined fuel economy for configuration
i (from section 11.4.5 or 11.4.6) within this base-level.
11.4.8 Model-level MPG/City, Highway, or Combined
FEM = ASTM(1)[ 1.0 DO / £ni=i (SF; / FEB;)]
where:
FEM
DO
SF;
Sales;
Salestotal
FEE;
City, highway or combined fuel economy for this model
type.
Double precision.
ASTM(4)[ (Sales; / Salestotal)]
Sales for base-level i at this model type.
Model type sales.
City, highway or combined fuel economy for base-level i
(from section 11.4.7) within this model type.
91
-------
March 28, 2001 (REV.)
11.5 Input Record Dependencies
Because there are combinations of input records that can be submitted, you must follow the
allowed valid transaction and input record dependency rules. Exhibit 11-1 shows the Input
record dependencies for the CAFE subsystem.
Corporate Average Fuel Economy
Input Record
Type
Fl
F2
FF
FR
FL
FT
FC
FS
ZZ
Input Record
Dependency
None
Fl
F2
FF
FF
FF
Fl
None
Valid Transactions
A,R,D,S'
A,R
A,R
A,R
A,R
A,R
A,R
A,R,D,S
All Transactions
CFEIS Table(s)
CAFE Basic Engine
CAFE Base Level
CAFE Configuration
CAFE Subconfiguration
CAFE Configuration Xref
CAFE Gear Ratios
CAFE Lockup RPM
CAFE Test Group
CAFE Basic Engine
MFR Average Fuel Economy
Exhibit 11-1. CAFE Input Record Dependencies
"Transactions Legend:
A= Add R= Replace D= Delete
S= Re-process ZZ= Termination
The Input Record Types are the first two characters in the input record submission format. See
Appendix D or E for other field content and format. The Input Record Dependency column
shows whether the input record is independent or must be accompanied in the transaction by an
additional input record. The Valid Transactions column show the kind of transactions that you
can submit. Your input record data are stored in the respective CFEIS table.
92
-------
March 28, 2001 (REV.)
12.0 REPORTS
All entries submitted either by paper form or electronically result in generating a Submission
Status report. Part I of the Submission Status Report is a printout of the data submitted. The
data is arranged in columns as specified in the input data record layout for each subsystem.
Errors found during the processing of a submission are embedded after the applicable record.
Errors generated because of faulty data input should be corrected by entering a new submission
with a replacement for the rejected transactions, and Modify/Replace transactions for the
transactions that were accepted with numeric data out of range. Any out-of-range data not
corrected prior to requesting a Summary Sheet, result in the Summary Sheet request being
rejected.
Part II of the Submission Status Report provides statistics on how many transactions were
accepted and rejected, how many of each record type were accepted and rejected, and total
quantities of transactions and records of a given type.
Part in of the Submission Status Report varies depending on the subsystem. For all subsystems,
Part in contains the content of the CFEIS database, for the specified subsystem, as a result of
processing the submission. The content of Part HI is restricted by the key information for the
subsystem. The specific restrictions on Part in are explained by subsystem in subsections 12.1
through 12.9.
In addition to the Submission Status Report, some of the subsystems have Report transactions.
The reports that are generated as a result of the Report transactions are described by applicable
subsystem in subsections 12.1 through 12.9.
12.1 Car Line
As a result of all Car Line submissions, you will receive a Submission Status Report. Part IH of
the Submission Status Report contains the content of the CFEIS database for Car Lines that
match the model year, Manufacturer code, Division code, and Car Line codes specified in the
transactions contained in the submission. See Appendix C for a sample of the car line
Submission Status Report.
There is no Report transaction for the Car Line subsystem.
93
-------
March 28, 2001 (REV.)
12.2 Engine Systems Information
As a result of all ESI submissions you will receive a Submission Status Report. Part HI of the
Submission Status Report for ESI contains two parts: (1) Engine Family/Test Group, Sales, and
System Summary information; and (2) Exhaust Emission Specification and Deterioration Factor
Summary information. The data presented in this subsection are constrained by the Engine
Family/Test Group names and Engine system numbers supplied as part of the ESI submission.
As a result of an ESI Report transaction, you will receive an ESI Database Report. The ESI
Database Report has the same format as Part HI of the Submission Status Report. The
difference is that the data contained in the ESI Database Report are constrained by the input
report parameters; whereas, Part HI of the Submission Status Report is constrained by the data
submitted as part of the ESI submission.
12.3 EvSI Systems Information
As a result of all EvSI submissions you will receive a Submission Status Report. Part HI of the
Submission Status Report for EvSI contains two parts EvSI Family, Sales, and System Summary
information; and Evaporative Emission Specification and Deterioration Factor Summary
information. The data presented in this subsection are constrained by the Engine Family/Test
Group names and Engine system numbers supplied as part of the EvSI submission.
As a result of an EvSI Report transaction, you will receive an EvSI Database Report. The EvSI
Database Report has the same format as Part HI of the Submission Status Report. The
difference is that the data contained in the EvSI Database Report are constrained by the input
report parameters; whereas, Part HI of the Submission Status Report is constrained by the data
submitted as part of the EvSI Submission.
12.4 Vehicle Information
As a result of all VI submissions you will receive a Submission Status Report. Part in of the
Submission Status Report for VI contains all of the information in CFEIS database about the
specified vehicles. The data presented in this subsection are constrained by the Manufacturer
code, vehicle Ids, vehicle configuration numbers, and certification model years specified or
implied by the VI submission.
As a result of a VI Report transaction, you will receive a VI Database Report. CFEIS will
forward a copy of the VI Database Report to EPA's LNS computer as a delimited file without
94
-------
March 28, 2001 (REV.)
titles and column headers. The VI Database Report has the same format as Part in of the
Submission Status Report. The difference is that the data contained in the VI Database Report
are constrained by the input report parameters; whereas, Part in of the Submission Status Report
is constrained by the data submitted as part of the VI Submission.
12.5 Shift Schedule
As a result of all Shift Schedule submissions you will receive a Submission Status Report.
Part in of the Submission Status Report for Shift Schedule contains all of the information in
CFEIS database about the shift schedules specified in the submission. Part IH of the Submission
Status Report for Shift Schedule is actually three separate reports, the Shift Schedule Report, the
Shift Point Report, and the Manufacturer Submission Summary Report.
As a result of the Shift Schedule Report transaction, you will receive a Shift Schedule Report
and a Shift Point Report. These reports have the same format as the corresponding subsection of
Part III of the Submission Status Report for Shift Schedule. As a result of the Report transaction
you will receive a Manufacturer Submission Summary Report. The Manufacturer Submission
Summary Report has the same format as the corresponding subsection of Part HI of the
Submission Status Report for Shift Schedule. The difference between the Report transactions
and Part HI of the Submission Status Report is that the data contained in each of the reports are
constrained by input report parameters; whereas, Part HI of the Submission Status Report is
constrained by the data submitted as part of the Shift Schedule submission.
12.6 Manufacturer/EPA Test Data
As a result of all MTDS submissions you will receive a Submission Status Report. Part HI of
the Submission Status Report for MTDS contains three reports, the MTDS Database Report, the
Projected Pass/Fail Report, and the Carry Over/Carry Across Report. They are described as
follows:
MTDS Database Report: This report lists the test data submitted by the manufacturer
and relevant VI.
Projected Pass/Fail Report: This report lists the emissions test results, the maximum
amount of emissions permitted for each emission type (as required by the emissions
standards), and a pass/fail indicator showing whether the vehicle met the maximum value
permitted by the standard during the test.
Carry Over/Carry Across Report: This report lists the carried over or carried across
data, identifying the test data specific to each model year that the test data were used.
95
-------
March 28, 2001 (REV.)
NOTE: This report is only generated if there were Carry Over or Carry Across transactions
included in the MTDS submission.
As a result of the MTDS Report transaction, you will receive a MTDS Database Report and a
Projected Pass/Fail Report. These reports have the same format as the corresponding subsection
of Part in of the Submission Status Report for MTDS. The difference between the Report
transactions and Part HI of the Submission Status Report is that the data contained in each of the
reports are constrained by input report parameters (Manufacturer code and test number);
whereas, Part in of the Submission Status Report is constrained by the data submitted as part of
the MTDS Submission (Manufacturer code, test number, and Carry Over/Carry Across
transactions).
12.7 Summary Sheet
As a result of all Summary Sheet submissions, you will receive a Summary Sheet Submission
Status Report. Part HI of the Submission Status Report for Summary Sheet contains all of the
information in CFEIS database about the summary sheets specified in the submission. Part in of
the Submission Status Report for Summary Sheet contains three reports: Summary Sheet
Database Report, Summary Sheet Vehicles Covered by Certificate, and Summary Sheet
Emission Data Vehicles.
As a result of a Report transaction, you will receive the following three reports: Summary Sheet
Database Report, Summary Sheet Vehicles Covered by Certificate, and Summary Sheet
Emission Data Vehicles. The format of the reports generated by a Report transaction is the same
as the corresponding subsections of Part in of the Summary Sheet Submission Status Report.
12.8 General Label
As a result of all General Label submissions you will receive a Submission Status Report. Part
III of the Submission Status Report for General Label contains three reports, the Fuel Economy
Calculations, the Fuel Economy Range Report, and the Receipt Letter. They are described as
follows:
Fuel Economy Calculations: Lists the results of vehicle-configuration-level, base-level,
and model-level calculations in addition to the attributive data defining each level of
aggregation. Additionally, this report displays the Test Car List and the Fuel Economy
Guide.
96
-------
March 28, 2001 (REV.)
Fuel Economy Range Report: Lists ranges of fuel economy values achieved by each
class of comparable automobiles.
Receipt Letter: Generates a letter to the manufacturer and an enclosure displaying fuel
economy label values.
There is no Report transaction for the General Label subsystem.
12.9 Corporate Average Fuel Economy
As a result of all CAFE submissions you will receive a Submission Status Report. Part in of the
Submission Status Report for CAFE contains two reports: the CAFE Report, and the
Manufacturer Fuel Economy Calculations. They are described as follows:
CAFE Report: This report summarizes the calculated CAFE values along with a
statistical listing of model year data, to include the number of model types, number of
base levels, number of vehicle configurations, percent of total production represented by
test vehicles, total number of vehicles tested, and the total number of vehicles reported by
compliance category for a manufacturer.
Manufacturers Fuel Economy Calculations: This report lists the results of vehicle-
configuration-level, base-level, and model-level fuel economy calculations in addition to
the attributive data defining each level of aggregation.
There is no Report transaction for the CAFE subsystem.
97
-------
March 28, 2001 (REV.)
This page is intentionally left blank.
98
-------
March 28, 2001 (REV.)
13.0 ERRORS
Two types of errors are reported on the Submission Status Report and on the database reports:
user-induced errors and system or database errors. User-induced errors are caused by problems
in the data submitted. System or database errors are caused by circumstances outside of the
submitted data. User-induced errors need to be fixed by the manufacturer submitting the data.
System or database errors should be reported to the CFEIS system administrator.
13.1 User-induced Errors
CFEIS processes the submissions for each subsystem. CFEIS checks all submissions to make
sure that the record types are allowable for the subsystem, the fields on the record are of the
proper type, and required fields are present. If applicable, CFEIS also checks to see if the data
fall within allowable ranges and appear on a list of values.
In addition, most subsystems have rules that must be followed regarding the relationship
between two or more fields in the transaction or between fields in the transaction and fields in
the CFEIS database. CFEIS checks to make sure that these relational rules are followed. In
addition, CFEIS detects errors.
Failing any edit check generates an error message that is written to the Submission Status
Report, Part I. The error message indicates the nature of the problem. It is extracted from a
common list of error messages and pre-fixed or appended with additional information for clarity.
Appendix B contains the common list of error messages.
Out-of-range data are reported on the Submission Status Report but do not cause the transaction
to be rejected. All other errors cause the transaction to be rejected until the errors are corrected
and the transaction re-submitted. Although CFEIS stores out-of-range data, the certification
analyst cannot generate a Certificate of Conformity until the out-of-range data have been
corrected.
13.2 System or Database Errors
While processing a batch submission, CFEIS may encounter errors independent of the data in
the submission. Most of those problems must be resolved by the CFEIS Systems Administrator.
The nature of the problem is reported on the Submission Status Report, Part I, which appears
after the record that was being processed when the error occurred.
99
-------
March 28, 2001 (REV.)
If your partition is too full to handle the reports requested, remove all unnecessary files. If the
Submission Status Report cannot be written to the report directory, contact the VPCD ADP
analyst, who will retrieve a copy of the Submission Status Report and deliver it to you. You
cannot re-send your submission as it has already been processed. To prevent space problems
from occurring, remember to remove report files from your partition.
100
------- |