-
Notifications
You must be signed in to change notification settings - Fork 1
Administration
- only shown to external users, who can only be associated with one operator per user account
- displays current data known about the operator
If an operator's business structure is a General Partnership, the operator can have 1 or multiple partners. For each partner company, the partner's CRA Business Number and BC Corporate Registry Number will be collected.
An operator can have 0, 1, or multiple parent companies. The parent compan(y)/(ies) may or may not be located inside Canada. If the parent company is within Canada, the CRA Business Number must be collected. If the parent company is outside Canada, a more generic "Tax ID Number" should be collected, and the address field is a freeform text field rather than broken down into explicit fields for municipality, province, postal code, etc.
- an operator can have a maximum of 1 Linear Facility Operation (LFO) assigned to them. They may have zero LFOs
- an operator can have 1 or more Single Facility Operations (SFOs) assigned to them, or they may have zero SFOs
-
Registered
: an external user acting on behalf of their operator has completed the form to register the operation. A status of "Registered" doesn't necessarily indicate that IRC has issued a BORO ID or BCGHG ID to the operation -
Transferred
: the operation previously belonged to the operator, but has since been reassigned to another operator. Operators need access to their historical operations for Reporting purposes. The new operator will see this transferred operation with a status of "Registered" -
Temporarily Shutdown
: the operation has been marked as Temporarily Shutdown using the "Report an Event" workflow, and no corresponding Restart event has been created for the operation at the present time -
Closed
: a Closure event has been reported for the operation. No corresponding Restart event has been created for the operation at the present time -
Draft
: partial data for the operation exists in the BCIERS database, but no external user acting on behalf of the operator has yet submitted the complete registration form data. This status also applies to operations that were either imported from SWRS or newly created under Registration 1, until the operator updates the operation data and officially submits the registration form. - an operation that was previously Closed or Temporarily Shutdown and then subsequently Restarted will have a status of
Registered
by default (unless other conditions exist, i.e., it's been transferred)
- granted only to operations
- the BORO ID is auto-generated by BCIERS, but is only issued to a registered operation upon an internal user manually confirming (button click) that a BORO ID should be granted to the operation
- format
yy-nnnn
whereyy
indicates the year that the BORO ID was issued in, andnnnn
is a 4-digit number generated sequentially. At the start of each calendar year,nnnn
resets to0001
- granted to operations. An SFO will have one BCGHG ID in total. An LFO will have one BCGHG ID per facility, and an additional BCGHG ID for the operation as a whole.
- see BCGHG ID below for further details
- facilities are always tied to a specific operation
- a facility may have a BCGHG issued to it
- granted to each facility within an LFO
- auto-generated by BCIERS, but is only issued when an internal user manually confirms (by button click) that a new BCGHG ID should be created for the selected facility
- format: 11-digit number constructed as
{o}{cccccc}{nnnn}
where {o} is1
for LFOs or2
for SFOs, {cccccc} is the NAICS code applicable to the facility, and {nnnn} is a 4-digit number generated sequentially based on the 7-digit number preceding it, starting from0001
- Example: 12212100001 indicates a facility belonging to an LFO with NAICS code 221210, and it was the first facility of that (operation type, NAICS code) combo. A subsequent facility that also belongs to an LFO and has a NAICS code of 221210 would be issued the BCGHG ID '12212100002'. A new facility with the same NAICS code but belonging to an SFO would therefore be issued the ID '22212100001'.
A "Contact" is a generic term for a person who works for an operator. They may or may not be a BCIERS user. A contact can be assigned zero-to-many roles within BCIERS across modules. A contact can be soft-deleted from BCIERS (for example, if they no longer work for the operator) but before deletion, they must be unassigned from all places where they have been assigned a role. This could mean that another contact needs to be assigned as their replacement.
- Operation Representative - assigned at the operation level. An operation must have at least 1 assigned Operation Representative, but can have multiple assigned at the same time
- Person Responsible for Reporting - assigned for each emissions report (per operation, per reporting year)
- Primary Account Representative
- Secondary Account Representative
- lists all external users associated with the relevant operator
- users with the app role of "industry_admin" can manage user access levels, including declining an access request (so that the requestor has no permissions for the operator at all), assigning the role of "reporter" (has access to everything except User Access Requests), or the role of "admin" (has access to everything)
- note that the roles assigned to a user are entirely separate from the roles assigned to a contact