SCAQMD RULE 2012-7 REMOTE TERMINAL UNIT (RTU) ELECTRONIC REPORTING
LAST REVISED 02/14/97

(Amended February 14, 1997)

Chapter 7 - Remote Terminal Unit(RTU) Electronic Reporting

Table of Contents
Chapter 7 - Remote Terminal Unit (RTU)

A. General

B. Products

C. Execution

D. Data Requirements

Appendix G - Diagrams

This chapter defines the tasks and characteristics for electronic reporting of emissions from all sources. The Facility Permit holder of a major source shall use an RTU to telecommunicate rule compliance data to the District Central Station Emissions Monitoring Computer. The RTU shall collect data, perform calculations, generate the appropriate data files, and transmit the data to the Central Station. The Facility Permit holder of a large source or process unit may elect to use an RTU. Alternatively, the Facility Permit holder of a large source or process unit shall compile the required rule compliance data manually, and transmit that data via modem in accordance with the data requirements of Section D in this chapter.

A. GENERAL

  1. General
  2. The Facility Permit holder of a major source shall telecommunicate rule compliance data to the District via Remote Terminal Units (RTU). This form of reporting may also be used for large sources or process units. The RTU shall collect data from a CEMS, a CPMS, or other equipment specified in the Facility Permit and send data periodically to the Central Station Emissions Monitoring Computer (Central Station ).

    This chapter specifies the tasks and characteristics required of the RTU and shall be used as a guide for providing the required software/hardware for the RTU. Emissions Data Collection System conformity as well as establishing and maintaining communications with the emission monitoring system and the Central Station shall be the responsibility of the Facility Permit holder. This chapter also serves as a functional guideline for operating requirements of the RTU, and provides information concerning RTU hardware/software procurement, configuration, installation, maintenance, and compatibility with the emission monitoring system and the Central Station.

  3. RTU and Supporting Equipment Description
  4. a. Purpose:

    The RTU shall interface to existing data acquisition systems or other field instrumentation, and shall gather and store data, and facilitate telecommunication with the Central Station Computer.

    b. Environment:

    i. Logical Environment:

    The signal chain includes the process equipment, sensing devices, data acquisition system, RTU, modem, communications link and District Central Station.

    ii. Physical Environment:

    Typical environments shall include "friendly" and "Central Station" environments. Friendly environments include clean, air conditioned areas such as computer rooms and offices. Hostile environments may include exterior spaces or interior spaces without benefit of air conditioning, and areas where free floating air particulates may impede the normal operation of exposed electronics. Each RTU shall be mounted in such a manner as to be environmentally qualified.

    iii. Electrical Environment:

    1) Connected Devices:

    Each RTU may receive information from a local computer (DAS) or various field sensing devices, calculate and/or store the specified parameters and shall make its data available to local and Central Stations.

    2) Sensor-based Data to be acquired:

    Where applicable, the RTU shall be able to directly monitor transducers which sense variables required for compliance determinations. At a minimum, input analog conversion hardware should operate with a medium level of resolution (i.e. 12 bit resolution) and a sampling rate sufficient to accurately characterize the sensor based data.

    iv. Description of Data to be transmitted:

    All data shall be made available at data output ports in ASCII format as described below:

    1) Data Sampling:

    Shall retain selectable status levels about its sensors.

    2) Rule-specific Data Sets:

    (as specified elsewhere)

    c. Functions:

    The RTU shall provide the following functions:

    i. Power-Up/Restart Mode:

    Upon resumption of power after a loss, the RTU shall automatically restart and reset itself to predetermined system settings.

    ii. Non-Communicating Mode:

    When in the non-communicating mode the RTU shall operate independently of the communications ports as well as store its transactions for later communications with the Central Station.

    iii. Failure Mode:

    In the event the RTU is unable to initiate communications with the Central Station, the RTU shall perform the following actions:

    1) The RTU shall first make four subsequent attempts to establish communications with the Central Station.

    2) Upon failure of the fourth attempt, the RTU shall:

    a Revert to the non-communicating mode for a period of fifteen (15) minutes and then again attempt to establish communications with the Central Station.

    b Each failure shall result in the execution of the failure mode sequence.

    3) Error Tolerance:

    The RTU shall perform its specified functions without misinterpretation of input information, errors in output signals, damage to internal components, and loss or change of stored information with either common mode to ground or differential mode transients present on the communication ports, circuits or power sources which shall be connected to the inputs and power supply terminals to the equipment.

B. PRODUCTS

  1. RTU Attributes
  2. a. Environmental Tolerances: Each RTU shall be installed in such a manner as to be environmentally qualified for the particular physical environment.

    b. Communications Provisions: The RTU shall provide a minimum of one (1) communications connection. The connection shall be labeled "Remote".

    c. Real Time Clock: The RTU shall be equipped with a battery-backed Real Time Calendar/Clock (RTC) to provide time signals for implementing time dependent programs. The battery back-up shall be field replaceable and shall not require replacement more often than once every two (2) years. An alarm message shall be generated when the battery reaches a low voltage point with at least one (1) month life under load left prior to the necessity for battery replacement.

    d. Internal Software:

    i. Data Collection and Storage: The RTU shall collect data from sensors, generate and store values, and perform calculations upon those values. Data shall be collected and stored in the Data Sampling memory.

    ii. Calculations and Message Storage: Calculated values and messages resulting from calculations performed upon sampled data shall be stored as ASCII data strings in memory.

    e. Security Provisions:

    >i. Message Security: The RTU shall utilize a standard protocol encryption method for communications with the remote Central Station incorporating error detection. The system shall not incorporate error correction. The code shall detect one hundred (100) percent of single, double and triple errors; one hundred (100) percent of burst errors of six bits or fewer; ninety- seven (97) percent of all seven-bit bursts; and ninety-eight point four (98.4) percent of all other burst as well as a substantial fraction of all random error patterns involving more than three (3) bits.

    ii. Message Checking: The RTU shall utilize bitsum checking for all messages.

    f. Modem: Provide a modem connected to the Remote Central Station communication port.i. Modem Self-Test: The modem shall be capable of being operated in self testing mode automatically on a periodic basis.

    g. Transient Suppression: Provide hardware, circuitry, components or extended component ratings or characteristics necessary to prevent interference to correct operation or equipment damage from induced transients which may be presented on communication circuits and power sources. Transient suppression shall utilize the latest revision of the ANSI C37.90a standard.

C. EXECUTION

  1. General
  2. a. Section (C) describes acceptable methods and practices for use in completion of this work.

    b. Standards: Perform the work in accordance with the latest revisions of the following standards:

    i. ANSI American National Standards Institute.
    ii. UL Underwriters Laboratories.
    iii. EIA Electrical Industries Association.
    iv. NEMA National Electrical Manufacturers Association.

  3. Project Plan
  4. Develop a project plan for accomplishing the requirements of this installation . The plan shall include a checklist for the Submittal date .

  5. Software Requirements Guideline
  6. The Software Requirement Guideline (SRG) shall specify tasks and characteristics required of the RTU and is to be used as a guide for providing the required software for the RTU. Emissions Data Collection System conformity as well as establishing and maintaining communications with the emission monitoring system and the Central Station shall be the responsibility of the Facility Permit holder.

    a. References

    This guideline shall be used in conjunction with the following Rules:

    Recordkeeping for Oxides of Sulfur (SOx) Emissions

    Recordkeeping for Oxides of Nitrogen (NOx) Emissions

    b. System Relation

    The RTU shall be the local plant data storage and processing point in a system which is reporting data to a Central Station for evaluation to determine regulatory compliance. Data formats shall be standardized between the Central Station and all monitored emissions sources. It is the function of the RTU to convert as necessary the data stream from the local monitoring system. The fundamental operation of the RTU is to:

    i. compile information from the emission monitoring system as specified in this guideline.

    ii. transmit the compiled data to the Central Station on a scheduled basis.

    c. Central Station Interface

    On scheduled updates the RTU shall download current data to the Central Station. The RTU data buffer shall be reset after each successful download to the Central Station.

    d. Software Responsibility

    The Facility Permit holder shall be responsible for providing all RTU software required to perform all specified tasks. This may include purchased commercial software packages or custom written programs.

    e. Product Function

    i. Software Context and Data Flow Diagrams

    The flow diagram at the end of this Chapter is a Context Diagram description and Data Flow Diagram which show how the different external functions tie to the RTU package. Plant data or operating information is collected by the emission monitoring system for evaluation of emissions. The RTU Unit is the process shown on this diagram and is the focus of this guideline.

    Data Values relating to emissions received from the emission monitoring system are processed by the RTU into data files for transmission to the SCAQMD Central Station. The type of message is shown on the RTU Context Diagram between the RTU and the Central Station. The message is data sets which are sent periodically.

    The RTU Data Flow Diagram is a graphical expansion of the RTU Unit process block. Emission monitoring system data is shown coming into the Network Driver and splitting to the other process blocks which represent RTU functions.

    ii. Communication End Points

    The RTU will communicate with both the emission monitoring system and the Central Station. Each end point has a different protocol and purpose. Data sent from the RTU to the Central Station shall be converted from floating point numbers used to perform calculations into ASCII standard to allow for different internal formats.

    f. Specific Requirements

    i. RTU Software

    The main RTU program shall receive input data, do calculations (if necessary) and store all data in non-volatile memory, as it is received.

    ii. Direct Field Input Data

    Many RTUs may be capable of reading direct field inputs which shall consist of analog and/or digital real values. Direct field input requirements shall be specified as required for each RTU. Communications software shall be capable of supporting the hardware required to receive these inputs. If analog data cards must be installed in the RTU any resulting values provided to the RTU data bus shall range from -32768 to +32767 for unscaled values. The same accuracy as emission monitoring system network data shall be provided for analog data values scaled on the I/O device before going onto the RTU data bus.

    iii. Input Data Conversion/Storage

    All input values shall be stored in as received ASCII format. These values shall then be parsed and converted to real numbers for calculations and averaging.

    iv. Output Data To Central Station

    The context diagram displays how the RTU software shall be configured to allow messages to be sent to the Central Station. File transfer for all messages shall be in ASCII format including a bitsum check value with a return acknowledgment expected by the RTU when the Central Station has verified the bitsum check.

    v. RTU To Central Station Communications Failure

    If the RTU cannot communicate with the Central Station the main program shall store all calculated values and reports in a special file in non-volatile memory. These special files shall be labeled to show that they have not been acknowledged as received by the Central Station.

    g. Performance Requirements

    i. Speed of Receiving DATA

    Incoming data from the plant or emission monitoring system shall be received at intervals specified in the appropriate emission monitoring guideline. Communication with the Central Station, Parsing, verification, storage and checking shall not block the receipt of new data.

    ii. RTU Non-Volatile Memory

    The RTU non-volatile memory shall have enough capacity to store all programs, data parameters, emission monitoring system input data and calculated data averages. Input data and calculated averages shall be allocated space using the first in first out (FIFO) method to store the quantity of data as required.

    h. Design Restraints

    i. Data Set Formats

    Section (D) indicates the data format that is to be sent to the Central Station at scheduled intervals. The Central Station will send a confirmation message back for each transmission received which will consist of an identification number unique to the Central Station and a transaction number which is sequentially issued.

    i. RTU External Interface Requirements

    i. Central Station Interface

    External interface to the RTU is shown on the Context Diagram at the end of this chapter. Central Station interface is described above as fixed format ASCII messages using a commercially available communication software package. In return the Central Station will send confirmation messages in ASCII form when a satisfactory message transfer has been completed.

  7. Required Installation Practices
  8. a. Standards: Install all devices in accordance with the standards set forth herein and in accordance with manufacturers recommendations and first class standard industry practice.

    b. Telephone Interface:

    RTU shall operate on a standard analog telephone line. Label the remote Central Station communications connector with the telephone number to which it is connected.

  9. Submittals
  10. a. Shop Drawing:

    i. Submit two (2) copies of the following in accordance with the applicable rule compliance dates.

    A Title Sheet

    Single Line Diagrams

    Wiring Diagrams or Run Sheets

    Physical Details of Custom Assemblies

    ii. Descriptions of the above shop drawings are as follows:

    a) Title Sheet containing a drawing list, abbreviations list, symbols list and schedules.

    b) Single-Line Diagram for each system showing signal relationships of devices within the system and device nomenclatures.

    c) Wiring Diagram for each assembly or enclosure or free standing device, showing the following:

    1) the layout of the devices within;

    2) wiring connections;

    3) wire numbers;

    4) voltage levels, and

    5) fuse values and types.

    d) Physical Details of contractor fabricated assemblies:

    1) Provide an assembly drawing showing the finished product. Show components comprising the assembly by manufacturer and model number.

    2) Provide a schematic diagram of the assembly, as described above.

    b. RTU Components List:

    i. The RTU Component List shall contain the following information for all materials, components, devices, wire and equipment used:

    Quantity for that system.

    Description (generic).

    Manufacturers Name and Model number.

    c. Software Design Description (SDD). Indicate how the developed software will meet the defined software requirements. The SDD shall be based on ANSI/IEEE standards, specifically 1016 (SDD) and 730 (Quality Assurance).

    d. Software Listing. Provide a source code listing of all developed software required by the applicable emission monitoring requirements.

D. DATA REQUIREMENTS

  1. General Requirements
  2. The District will accept data in the American Standard Code for Information Interchange (ASCII) format.

    The data file structure must be sequential. The record delimiter - a ~ (tilde) occurs only once following the end of each data record. There must be no delimiter before the first data record. The ASCII value for the delimiter is:
    ~ (decimal 126)

    Blank data records must not be reported

    In text fields, only upper case characters are to be used and must be left justified. Text fields that are not applicable must be filled with blanks. The ~ character (decimal 126) must never appear inside text fields.

    Numeric fields must be right justified and zero filled. Where decimal places are to be reported, they are to be implied - do not include the decimal point character. Numeric fields that are zeros or not applicable, must be zero filled.

    Date fields must be entered in the format "YYYYMMDD" and must always specify a valid date.

  3. Data File Description
  4. A properly composed data file is comprised of the following data records (shown indented to illustrate the logical grouping):

    Code 1A - Transmitter Record
    Code 1F - Facility Record
    Emission data record(s) from any of the following data records
    Code 1NP - NOx Process Unit and Large Source Record
    Code 1NM - NOx Major Source Record
    Code 1SP - SOx Process Unit Record
    Code 1SM - SOx Major Source Record
    Code 1FT - Facility Total Record
    Code 1F - Facility Record
    Emission data record(s)
    Code 1FT - Facility Total Record
    Code 1T - Final Total Record

    The Code 1A data record identifies the facility submitting the data file and must be the first data record in the data file.

    The Code 1T data record identifies the end of a data file and must be the last data record in the data file

    The Code 1F data record identifies the facility whose emission data records are being reported.

    The Code 1FT data record identifies the end of emission data records for a particular facility.

    Code 1F/1FT data records must not be nested inside of another 1F/1FT group and are repeated for each facility to be reported.

    Emission data records for a facility are reported following the Code 1F but before the 1FT data record for that facility and can comprise any of the following data record types:

    Code 1NP - NOx Process Unit and Large Source Record
    Code 1NM - NOx Major Source Record
    Code 1SP - SOx Process Unit Record
    Code 1SM - SOx Major Source Record

The following table summarizes valid Record Identifiers to be used starting January 1, 1998 to perform electronic reporting via a RTU or modem. The 1A through 1T records are used for identification and grouping purposes. The 1NP through 1SM records are the pre-existing emissions reporting records. Starting January 1, 1998, these records may only be used for devices which do not use multiple fuels and are not involved in multiple processes. Otherwise, sources shall report emissions by each fuel type or process conducted within the reporting period. If more than 50% of the emissions from a source is from the combustion of fuels, the emission report for such a source or process unit shall be reported based on the fuel combusted. Otherwise, emissions shall be reported based on the Source Classification Code (SCC) for the process conducted. The 1NPF through 1SUQ records are utilized for reporting emissions from devices with multiples fuels or processes. Record Identifiers starting with "2" are used to make corrections to submitted electronic emissions reports. Record Identifiers starting with "3" are used to delete previously submitted electronic emissions reports which were filed erroneously. Erroneous records to be corrected need not be deleted first.

Record Identifiers Summary Table

Record Identifier for
Adding a record Updating a record Deleting a record Description
1A* -- -- Transmitter Record
1F* -- -- Facility Record
1FT* -- -- Facility Total Record
1T* -- -- Final Total Record
1NP* 2NP 3NP NOx Emissions Report for Process Units
1NL* 2NL 3NL NOx Emissions Report for Large Sources
1NM* 2NM 3NM NOx Emissions Report for Major Sources
1SP* 2SP 3SP SOx Emissions Report for Process Units
1SM* 2SM 3SM SOx Emissions Report for Major Sources
1NPF 2NPF 3NPF NOx Emissions Report for Process Units by Fuel Type
1SPF 2SPF 3SPF SOx Emissions Report for Process Units by Fuel Type
1NLF 2NLF 3NLF NOx Emissions Report for Large Sources by Fuel Type
1NMF 2NMF 3NMF NOx Emissions Report for Major Sources by Fuel Type
1SMF 2SMF 3SMF SOx Emissions Report for Major Sources by Fuel Type
1NPS 2NPS 3NPS NOx Emissions Report for Process Units by SCC
1SPS 2SPS 3SPS SOx Emissions Report for Process Units by SCC
1NLS 2NLS 3NLS NOx Emissions Report for Large Sources by SCC
1NMS 2NMS 3NMS NOx Emissions Report for Major Sources by SCC
1SMS 2SMS 3SMS SOx Emissions Report for Major Sources by SCC
1NMM 2NMM 3NMM Monthly NOx Emissions Report for Major Sources

Record Identifers Summary Table (Continued)

Record Identifier for
Adding a record Updating a record Deleting a record Description
1SMM 2SMM 3SMM Monthly SOx Emissions Report for Major Sources
1NMQ 2NMQ 3NMQ Quarterly NOx Emissions Report for Major Sources
1SMQ 2SMQ 3SMQ Quarterly SOx Emissions Report for Major Sources
1NLQ 2NLQ 3NLQ Quarterly NOx Emissions Report for Large Sources
1NRF 2NRF 3NRF Quarterly NOx Emissions Report by fuel type for Rule 219 Exempt Equipment
1SRF 2SRF 3SRF Quarterly SOx Emissions Report by fuel type for Rule 219 Exempt Equipment
1NRS 2NRS 3NRS Quarterly NOx Emissions Report by SCC for Rule 219 Exempt Equipment
1SRS 2SRS 3SRS Quarterly SOx Emissions Report by SCC for Rule 219 Exempt Equipment
1NVF 2NVF 3NVF Quarterly NOx Emissions Report by fuel type for Equipment Operating under a Various Locations Permit
1SVF 2SVF 3SVF Quarterly SOx Emissions Report by fuel type for Equipment Operating under a Various Locations Permit
1NVS 2NVS 3NVS Quarterly NOx Emissions Report by SCC for Equipment Operating under a Various Locations Permit
1SVS 2SVS 3SVS Quarterly SOx Emissions Report by SCC for Equipment Operating under a Various Locations Permit
1NWF 2NWF 3NWF Quarterly NOx Emissions Report by fuel type for Equipment Operating Without Permit or District assigned Device IDs
1SWF 2SWF 3SWF Quarterly SOx Emissions Report by fuel type for Equipment Operating Without Permit or District assigned Device IDs
1NWS 2NWS 3NWS Quarterly NOx Emissions Report by SCC for Equipment Operating Without Permit or District assigned Device IDs
1SWS 2SWS 3SWS Quarterly SOx Emissions Report by SCC for Equipment Operating Without Permit or District assigned Device IDs
1NPQ 2NPQ 3NPQ Quarterly NOx Aggregate Emissions Report for Process Units
1SPQ 2SPQ 3SPQ Quarterly SOx Aggregate Emissions Report for Process Units
1NXQ 2NXQ 3NXQ Quarterly NOx Aggregate Emissions Report for Rule 219 Exempt Equipment
1SXQ 2SXQ 3SXQ Quarterly SOx Aggregate Emissions Report for Rule 219 Exempt Equipment

* Previously defined codes

Record Identifers Summary Table (Continued)

Record Identifier for
Adding a record Updating a record Deleting a record Description
1NTQ 2NTQ 3NTQ Quarterly NOx Aggregate Emissions Report for Equipment Operating under a Various Locations Permit
1STQ 2STQ 3STQ Quarterly SOx Aggregate Emissions Report for Equipment Operating under a Various Locations Permit
1NUQ 2NUQ 3NUQ Quarterly NOx Aggregate Emissions Report for Equipment Operating without a Permit
1SUQ 2SUQ 3SUQ Quarterly SOx Aggregate Emissions Report for Equipment Operating without a Permit

* Previously defined codes

Code 1A - Transmitter Record

The Code 1A data record is used to identify the facility submitting the data file and must be the first data record reported.

Location Field Length Description
1-4 Record Identifier 4 Constant "1A" followed by 2 blanks.
5-10 SCAQMD Facility ID 6 The 6-digit SCAQMD facility ID of the facility submitting the data file.
11-128 Filler 118 Blanks , used to fill unused remaining record positions.

Code 1F - Facility Record

The Code 1F data record is used to identify the facility whose emissions are being reported.

Location Field Length Description
1-4 Record Identifier 4 Constant "1F" followed by 2 blanks.
5-10 SCAQMD Facility ID 6 The 6-digit SCAQMD facility ID for the facility whose emissions are being reported.
11-128 Filler 118 Blanks , used to fill unused remaining record positions.

Code 1FT - Facility Total Record

The Code 1FT data record is used to identify the end of data emission records for a facility.

Location Field Length Description
1-4 Record Identifier 4 Constant "1FT" followed by 1 blank.
5-11 Number of Emission

Data Records

7 The total number of emission data records reported for the facility (excluding the 1F and the 1FT data records). Right justify and zero fill.
12-128 Filler 117 Blanks , used to fill unused remaining record positions.

Code 1T - Final Total Record

The Code 1T data record is used to identify the end of the data file and must be the last data record reported.

Location Field Length Description
1-4 Record Identifier 4 Constant "1T" followed by 2 blanks
5-11 Number of Data 7 The total number of data records reported (including the Code 1T) in the data file. Right justify and zero fill.
12-128 Filler 117 Blanks , used to fill unused remaining record positions.

Code 1NP and 1NL- NOx Process Unit and Large Source Record

The Code 1NP data record is used to report NOx emissions from NOx Process Units with SCAQMD assigned Device Ids. The Code 1NL data record is used to report NOx emissions from NOx Large Sources with SCAQMD assigned Device IDs. Starting January 1, 1998, these records shall only be used for devices which do not use multiple fuels and are not involved in multiple processes.

Location Field Length Description
1-4 Record Identifier 4 "1NP" or "1NL"followed by 1 blank
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 The date emitted in the format "YYYYMMDD"
19-27 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
28 - 128 Filler 101 Blanks , used to fill unused remaining record positions

Code 1NM - NOx Major Source Record

The Code 1NM data record is used to report NOx emissions from Major NOx sources with SCAQMD assigned Device IDs. Starting January 1, 1998, this record shall only be used for devices which do not use multiple fuels and are not involved in multiple processes.

Location Field Length Description
1-4 Record Identifier 4 Constant "1NM" followed by 1 blank
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 The date emitted in the format "YYYYMMDD"
19-27 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
28-36 Status Word 9 The nine character status word for the reporting day from the Status Word Table.
37 - 128 Filler 92 Blanks , used to fill unused remaining record positions

Code 1SP - SOx Process Unit Record

The Code 1SP data record is used to report SOx emissions from SOx Process Units with SCAQMD assigned Device IDs. Starting January 1, 1998, this record shall only be used for devices which do not use multiple fuels and are not involved in multiple processes.

Location Field Length Description
1-4 Record Identifier 4 Constant "1SP"followed by 1 blank
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 The date emitted in the format "YYYYMMDD"
19-27 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
28 - 128 Filler 101 Blanks , used to fill unused remaining record positions

Code 1SM - SOx Major Source Record

The Code 1SM data record is used to report SOx emissions from Major SOx sources with SCAQMD assigned Device IDs. Starting January 1, 1998, this record shall only be used for devices which do not use multiple fuels and are not involved in multiple processes.

Location Field Length Description
1-4 Record Identifier 4 Constant "1SM" followed by 1 blank
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 The date emitted in the format "YYYYMMDD"
19-27 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
28-36 Status Word 9 The nine character status word for the reporting day from the Status Word Table.
37 - 128 Filler 92 Blanks , used to fill unused remaining record positions

Code 1NMF and 1SMF - NOx and SOx Major Source Emissions Report by Fuel Type

The Codes 1NMF and 1SMF data records are used to report NOx and SOx emissions by fuel type from Major SOx sources with SCAQMD assigned Device IDs. Starting January 1, 1998, these records shall be used to report emissions from each Major SOx sources and each fuel used during a reporting day.

Location Field Length Description
1-4 Record Identifier 4 1NMF or 1SMF
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 The date emitted in the format "YYYYMMDD"
19-38 Fuel Type 20 Code for Fuel Type utilized. Left justified, blank filled
39-47 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
48-56 Status Word 9 The nine character status word for the reporting day from the Status Word Table.
57 - 128 Filler 72 Blanks , used to fill unused remaining record positions

Code 1NMS and 1SMS - NOx and SOx Major Source Emissions Report by SCC

The Codes 1NMS and 1SMS data records are used to report NOx and SOx emissions by Source Classification Codes (SCC) from Major SOx sources with SCAQMD assigned Device IDs. Starting January 1, 1998, these records shall be used to report emissions from each Major SOx sources and each process conducted during a reporting day.

Location Field Length Description
1-4 Record Identifier 4 1NMS or 1SMS
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 The date emitted in the format "YYYYMMDD"
19-26 SCC 8 Source Classification Code
27-35 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
36-44 Status Word 9 The nine character status word for the reporting day from the Status Word Table.
45 - 128 Filler 84 Blanks , used to fill unused remaining record positions

Code 1NLF, 1NPF and 1SPF - NOx Large Source and NOx and SOx Process Unit Emissions Report by Fuel Type

The Codes 1NLF, 1NPF and 1SPF data records are used to report NOx and SOx emissions by fuel type from NOx Large source, NOx and SOx Process Units, respectively, with SCAQMD assigned Device IDs. Starting January 1, 1998, these records shall be used to report emissions from each device and each fuel used during a reporting period.

Location Field Length Description
1-4 Record Identifier 4 1NLF, 1NPF, or 1SPF
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 End date of reporting period in the format "YYYYMMDD"
19-38 Fuel Type 20 Code for Fuel Type utilized. Left justified, blank filled
39-47 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
48-56 Status Word 9 The nine character status word for the reporting day from the Status Word Table.
57 - 128 Filler 72 Blanks , used to fill unused remaining record positions

Code 1NLS, 1NPS and 1SPS - NOx Large Source and NOx and SOx Process Units Emissions Report by SCC

The Codes 1NLS, 1NPS and 1SPS data records are used to report NOx and SOx emissions by SCC from NOx Large source, NOx and SOx Process Units, respectively, with SCAQMD assigned Device IDs. Starting January 1, 1998, these records shall be used to report emissions from each device and each process conducted during a reporting period.

Location Field Length Description
1-4 Record Identifier 4 1NLS, 1NPS, or 1SMS
5-10 SCAQMD Device ID 6 The SCAQMD assigned Device IDs for the equipment source. Left justify and fill with blanks
11-18 Date Emitted 8 End date of reporting period in the format "YYYYMMDD"
19-26 SCC 8 Source Classification Code
27-35 Total Emission 9(#######.##) The total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
36-44 Status Word 9 The nine character status word for the reporting day from the Status Word Table.
45 - 128 Filler 84 Blanks , used to fill unused remaining record positions

Code 1NMM, 1SMM, 1NMQ, 1NLQ, 1NPQ, 1SMQ, and 1SPQ - Aggregate Emissions Reports for Devices with District Assigned Device IDs

The Codes 1NMM and 1SMM data records are used to report monthly total NOx and SOx emissions, respectively, from all NOx and SOx Major Sources within a facility. The Codes 1NMQ, 1SMQ, 1NLQ, 1NPQ, and 1SPQ data records are used to report quarterly total NOx and SOx emissions, respectively, from all NOx and SOx Major, NOx Large Sources, and NOx and SOx Process Units within a facility. Starting January 1, 1998, these records shall be used to report aggregate emissions from applicable classification of devices within each facility.

Location Field Length Description
1-4 Record Identifier 4 1NMM, 1SMM, 1NMQ, 1SMQ, 1NLQ, 1NPQ, or 1SPQ
5-12 Date Emitted 8 End date of the reporting period in the format "YYYYMMDD"
13-21 Total Emission 9(#######.##) Enter the total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
22 - 128 Filler 107 Blanks , used to fill unused remaining record positions

Code 1NXQ, 1SXQ, 1NTQ, 1STQ, 1NUQ, and 1SUQ - Aggregate Quarterly Emissions Reports for Devices without District Assigned Device IDs

The Code 1NXQ, 1SXQ, 1NTQ, 1STQ, 1NUQ, and 1SUQ data records are used to report quarterly total NOx and SOx emissions, respectively, from all Rule 219 exempt equipment, equipment operating under a various locations permit (e.g. rental equipment) and equipment without permit. Starting January 1, 1998, these records shall be used to report aggregate emissions from all applicable devices within each facility.

Location Field Length Description
1-4 Record Identifier 4 1NXQ, 1SXQ, 1NTQ, 1STQ, 1NUQ, and 1SUQ
5-12 Date Emitted 8 End date of the reporting period in the format "YYYYMMDD"
13-21 Total Emission 9(#######.##) Enter the total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
22 - 128 Filler 107 Blanks , used to fill unused remaining record positions

Code 1NVF and 1SVF - NOx and SOx Emissions Reports by Fuel Type for Equipment Operated under a Various Locations Permit

The Code 1NVF and 1SVF data records are used to report NOx and SOx emissions, respectively, by fuel type from each device operating under a various location permit (e.g. rental equipment). Starting January 1, 1998, these records shall be used to report emissions from each device in this category.

Location Field Length Description
1-4 Record Identifier 4 1NVF or 1SVF
5-10 Permit Number 6 SCAQMD Permit Number. Left justified, blank filled
11-18 Date Emitted 8 End date of the reporting period in the format "YYYYMMDD"
19-38 Fuel Type 20 Code for Fuel Type utilized. Left justified, blank filled
39-47 Total Emission 9(#######.##) Enter the total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
47 - 128 Filler 82 Blanks , used to fill unused remaining record positions

Code 1NVS and 1SVS - NOx and SOx Emissions Reports by SCC for Equipment Operated under a Various Locations Permit

The Code 1NVF and 1SVF data records are used to report NOx and SOx emissions, respectively, by SCC from each device operating under a various location permit (e.g. rental equipment). Starting January 1, 1998, these records shall be used to report emissions from each device in this category.

Location Field Length Description
1-4 Record Identifier 4 1NVS or SVS
5-10 Permit Number 6 SCAQMD Permit Number. Left justified, blank filled
11-18 Date Emitted 8 End date of the reporting period in the format "YYYYMMDD"
19-26 SCC 8 Source Classification Code.
27-35 Total Emission 9(#######.##) Enter the total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
36 - 128 Filler 93 Blanks , used to fill unused remaining record positions

Code 1NRF, 1SRF, 1NWF, and 1SWF - NOx and SOx Emissions Reports by Fuel Type for Rule 219 Exempt Equipment, and Equipment Operated without a Permit

Code 1NRF, 1SRF, 1NWF, and 1SWF are used to report NOx and SOx emissions by fuel type from all devices which are exempt from permit under Rule 219 or from all devices operating without a permit. Starting January 1, 1998, these records shall be used to report emissions from all devices in each of these category.

Location Field Length Description
1-4 Record Identifier 4 1NRF, 1SRF, 1NWF, or 1SWF
5-12 Date Emitted 8 End date of the reporting period in the format "YYYYMMDD"
13-32 Fuel Type 20 Code for Fuel Type utilized. Left justified, blank filled
33-41 Total Emission 9(#######.##) Enter the total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
42 - 128 Filler 82 Blanks , used to fill unused remaining record positions

Code 1NRS, 1SRS, 1NWS, and 1SWS - NOx and SOx Emissions Reports by SCC for Rule 219 Exempt Equipment, and Equipment Operated without a Permit

Code 1NRS, 1SRS, 1NWS, and 1SWS are used to report NOx and SOx emissions by SCC from all devices which are exempt from permit under Rule 219 or from all devices operating without a permit. Starting January 1, 1998, these records shall be used to report emissions from all devices in each of these category.

Location Field Length Description
1-4 Record Identifier 4 1NRS, 1SRS, 1NWS, or 1SWS
5-12 Date Emitted 8 End date of the reporting period in the format "YYYYMMDD"
13-20 SCC 8 Source Classification Code.
21-29 Total Emission 9(#######.##) Enter the total emission in lb to 2 decimal places. Omit the decimal point, right justify and zero fill. No negative numbers.
30-128 Filler 99 Blanks , used to fill unused remaining record positions

Status Word Table

The Status Word Table is used to compile the status word for the required reporting period. True is 1 and False is 0.

Location Field Length Description
1-1 Valid Data 1 Enter true if valid data was obtained for the entire reporting period, else enter false
2-2 Calibration 1 Enter true if the monitoring system was calibrated during the reporting period, else enter false
3-3 Off-line 1 Enter true if the monitoring system was off-line at any time during the reporting period, else enter false.
4-4 Alternate Data Acquisition 1 Enter true if alternate data acquisition was used during the reporting period, else enter false.
5-5 Out of Control 1 Enter true if the CEMS was out of control during the reporting period, else enter false.
6-6 Fuel Switch 1 Enter true if more than one fuel type was used during the reporting period, else enter false.
7-7 10% range 1 Enter true if concentration was reported at 10% valid range when concentration value was below 10%, else enter false.
8-8 lower than 10% range 1 Enter true if concentration was reported at an actual value less than 10% valid range, else enter false.
9-9 non-operational 1 Enter true if equipment is non-operational for the entire day, else enter false.

Format for Correcting Emissions Reports

Name Description
Record Identifier Record Identifier starting with "2"
Record to be corrected All information contained in previously submitted record which is to be corrected, except the original Record Identifier field and the filler field.
Correct Record The correct record containing all information for the record type, except the original Record Identifier field and the filler field.
Filler This field is blank filled to complete the 128 character fixed length reporting record.

Format for deleting Emissions Reports

Name Description
Record Identifier Record Identifier starting with "3"
Record to be deleted All information contained in previously submitted record which is to be deleted, except the original Record Identifier field and the filler field.

APPENDIX G

DIAGRAMS

RTU Context Diagram