The Facility Inventory set of tables are the most complex of all the Bridge Tool 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 in order to create a successful XML file.

The highest-level table is the FacilitySite table. Consequently, it does not have a “parent” table. FacilitySite has several “child” tables to which it may be connected:

• AlternateFacilityName (no children exist beyond this table)
• AlternativeFacilityIdentification (no children exist beyond this table)
• EmissionsUnit
• ReleasePoint (no children exist beyond this table)
• FacilityNAICS (no children exist beyond this table)
• SiteControl
• SiteControlPath

Records in the FacilitySite table are uniquely identified by either

• Program System Code + Agency Identifier + FIPS State and County where the facility is located
OR
• EIS Facility ID

EmissionsUnit has the FacilitySite record as the “parent” and has several “child” tables to which it may be connected:

• AlternativeUnitIdentification (no children exist beyond this table)
• EmissionsProcess
• Regulation (no children exist beyond this table)

Records in the EmissionsUnit table are uniquely identified by the FacilitySite unique key plus one of the following:

• Program System Code + Agency Unit Identifier
OR
• EIS Unit ID

EmissionsProcess has the EmissionsUnit record as the “parent” and has several “child” tables to which it may be connected:

• ReleasePointApportionment (no children exist beyond this table)
• AlternativeProcessIdentification (no children exist beyond this table)
• Regulation (no children exist beyond this table)

It should be noted that the EmissionsProcess records are also related to DeleteReportingPeriod and ReportingPeriod. However, these tables are only used for Emissions submissions and are covered under the listing for Point Hierarchies.

Records in the EmissionsProcess table are uniquely identified by the EmissionsUnit unique key plus one of the following:

• Program System Code + Agency Process Identifier
OR
• EIS Process ID

SiteControl has the FacilitySite record as the “parent” and has several “child” tables to which it may be connected:

• AlternativeFacilitySiteControlIdentification (no children exist beyond this table)
• SiteControlPollutant (no children exist beyond this table)

Records in the SiteControl table are uniquely identified by the FacilitySite unique key plus one of the following:

• Program System Code + Agency Control Identifier
OR
• EIS Site Control ID

SiteControlPath has the FacilitySite record as the “parent” and has several “child” tables to which it may be connected:

• AlternativeFacilitySiteControlPathIdentification (no children exist beyond this table)
• SiteControlPathPollutant (no children exist beyond this table)
• PathDefinition (no children exist beyond this table)

Records in the SiteControl table are uniquely identified by the FacilitySite unique key plus one of the following:

• Program System Code + Agency Control Path Identifier
OR
• EIS Site Control Path ID