-
Notifications
You must be signed in to change notification settings - Fork 1
Registration
- a multi-step form has been created to guide external users through the registration process. Only operations that aren't yet fully registered will be listed as options from the operation dropdown. If an operator wants to update information about a registered operation, they must do so via the "Operations" tile in the Administration module
- internal users do not need to "Approve" or "Decline" operation registrations, but they do need to issue BORO IDs and BCGHG IDs to registered operations (that don't already have one) by manually clicking buttons in the operation's registration form. (i.e., these numbers will not be automatically issued upon the external user's completion of the registration form, but will be auto-generated once the internal user reviews the registration form and confirms they want to issue a BORO ID and/or BCGHG ID to the operation)
- an operation only needs to be registered once. If an operation is transferred to another operator, the operation will still be considered "registered" under the new operator
When registering an operation, external users must specify what category or "registration purpose" their operation falls under. The registration purpose selected determines some of the data fields shown later in the registration workflow.
A user will only be permitted to select exactly one option for registration purpose. The selected registration purpose will be saved in the pertinent operation's data.
The diagram below describes the relationships between the 6 available options for registration purpose. For example, any operation that is registered as "OBPS Regulated Operation" can also be considered a Reporting Operation.
All operations categorized as "Reporting" operations will be expected to submit annual emissions reports.
Users who select "EIO" as their Registration Purpose will be shown a simplified version of the registration workflow that doesn't prompt them for Facility Information (to avoid confusion on the part of external users), since EIOs don't have facilities. However, when an EIO is registered, a facility for the operation will be created in the BCIERS database, largely using the operation's information. This is necessary because the Reporting module relies on facility information when constructing reporting forms.
If an industry user selects "Opted-in Operation" as their operation's registration purpose, a related record called OptedInOperationDetail
will be created and stored in the database, for the purpose of storing their responses to questions specific to opted-in operations. There is also an opt_in
boolean flag on the operation record that will be set to True
for operations registered as Opted-In. This is for the purpose of making filtering opted-in operations in Metabase more user-friendly.
Per GGERR, all operators are expected to report to BCIERS any of the following events within 30 days of their occurrence.
- can apply to either an entire operation or to one or more facilities within an operation. If multiple facilities are selected, they must all be within the same LFO
- in the database, events have separate columns for operation ID and facility IDs. Only one of these fields will ever be populated, indicating whether the event is at the operation-level or the facility-level
- each event type has a separate form and is expected to be filled out by the external user only - no action is required by IRC staff, although they can view the data submitted in these forms from all operators
- in order for a Restart event to be created, there must first be a corresponding Temporary Shutdown or Closure event
- can apply to either an entire operation or to one or more facilities within an operation. If multiple facilities are selected, they must all be within the same LFO
- if operation is being transferred, the assigned BORO ID for the operation will also be transferred over to the receiving operator
- guidance that IRC will be circulating to external users is that both operators involved in a transfer are expected to submit a transfer form (i.e., there will be 2 forms submitted for each transfer event)
- operators submit transfer form to request the transfer of an entity. IRC staff review the data submitted in the forms, then fill out an additional form either confirming which facilities/operations are to be transferred, or "completing" (i.e., not transferring) the entities
- if an entire LFO is being transferred to another operator, the external users only need to select the operation being transferred, not the individual facilities within the LFO
- an operator is only permitted to have a maximum of 1 LFO, so if a facility is being transferred to another operator, the receiving operation can be inferred based on the operator receiving the facility