The Point Emissions are generated using the same Bridge Tool as used for the Facility Inventory. However, when producing the point emissions, fewer tables are used as only the facility identifiers, unit identifiers, and process identifiers are needed from the facility inventory tables. As with all the Bridge Tools, the records between tables are “linked” to the child records by a set of columns that uniquely define the record from the “parent” table. Please note that you cannot “switch” how you identify the records between the “parent” and the “child”. Once you choose a method of identification, you must be consistent throughout. We will discuss the columns that define the unique records in a table, show the “parent” table, and show what “child” tables are available. These pieces of information will provide you a map of what tables you will need to populate to create a successful XML file.
EmissionsProcess has the EmissionsUnit record as the “parent” and has several “child” tables to which it may be connected:
It should be noted that the EmissionsProcess records are also related to ReleasePointApportionment, AlternativeProcessIdentification, and Regulation. However, these tables are only used for Facility Inventory submissions and are covered under the listing for Facility Inventory Hierarchies.
Records in the EmissionsProcess table are uniquely identified by the EmissionsUnit unique key plus one of the following:
ReportingPeriod has the EmissionsProcess record as the “parent” and has several “child” tables to which it may be connected:
Records in the Point ReportingPeriod table are uniquely identified by the EmissionsProcess unique key plus the following: