Directive 065 - Energy Resources Conservation Board
Directive 065 - Energy Resources Conservation Board
Directive 065 - Energy Resources Conservation Board
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Step 2: Corporate Record Check<br />
All applications are subject to a corporate check to verify acceptable performance records and<br />
other information in ERCB files.<br />
Applicants seeking formal approval must hold a valid company code issued by the ERCB’s<br />
Corporate Compliance Group. If you are a first-time applicant, you must obtain a company<br />
code by filing a corporate profile with the ERCB’s Corporate Compliance Group.<br />
Information packages are available from the Corporate Compliance Group at (403) 297-8320.<br />
You must update your corporate profile when asked to do so by the ERCB.<br />
ERCB approvals identify the applicant as the holder of the approval, and this party is<br />
responsible and accountable for compliance with all regulations and the approval conditions.<br />
Applicants requesting changes to a general order of the ERCB, reservoir description, and<br />
operational practices not requiring a change to an approval do not need to have a company<br />
code but must have a valid interest in the pool.<br />
If you are on “refer” status due to an unresolved serious noncompliance problem, the ERCB<br />
may ask additional questions, including questions related to corporate accountability,<br />
technical competency, and corporate commitment to compliance with provincial standards, as<br />
part of the ERCB enforcement policy detailed in <strong>Directive</strong> 019: Compliance Assurance. In<br />
the case of a “refer” status, ERCB <strong>Board</strong> members are directly involved in the consideration<br />
of any application, which may include a decision to go to a hearing. Otherwise, the<br />
application is normally reviewed and, if appropriate, approved by the delegated work groups<br />
within the ERCB.<br />
Step 3: Application Returned or Delayed if Incomplete<br />
Effective October 1, 2000, the ERCB will no longer process an application identified in this<br />
directive if it is substantially incomplete (i.e., has a major deficiency). It will be returned to<br />
you with an explanation. An example of such a major deficiency is the complete omission of<br />
an entire key information segment of any unit requirements, such as the geological<br />
description. If the application has minor deficiencies, such as lacking specific information<br />
needed to make a decision, you will be provided with a clear explanation and given 5<br />
working days to respond. Failure to respond in this time frame will result in the ERCB<br />
closing and returning your application with written notification of the reason. The ERCB is<br />
prepared to correct small errors in the submitted information, as long as applicants show<br />
improvement in submitting better-quality applications.<br />
Note that if the ERCB returns a severely deficient and incomplete application that you filed<br />
in response to an ERCB request, such as for improvement in recovery or operational<br />
performance, you will be subject to any consequences or penalties previously identified at the<br />
time of the request.<br />
Step 4: Application Evaluation<br />
This directive identifies some circumstances that may reduce application requirements and, in<br />
turn, result in a faster decision on the application. You may want to consider the long-term<br />
benefits of creating some of these circumstances, such as equity agreements and poolwide<br />
plans, before you file a competitive, partial pool application.<br />
The evaluation of your application may also be expedited if your definition of the pool extent<br />
is consistent with the ERCB’s pool designation or you provide a discussion on any variances.<br />
8 • ERCB <strong>Directive</strong> <strong>065</strong>: <strong>Resources</strong> Applications / How to Use This <strong>Directive</strong> (March 2012)