9 - Quality Assurance


Content on this page


9.1 The operator’s responsibility

The person responsible for the operator's reporting shall ensure:

  • that there is a complete overview of all the projects the operator is to report on
  • that a correct profile collection is linked to the various projects
  • that correct reporting is submitted to the authorities by the deadline stated in the dispatch letter
  • that there is consistency between data types
  • that contributions from the respective disciplines are quality assured

Quality implies that the reporting is in accordance with the requirements listed in the General Guidelines and in the Reporting file.

As previously mentioned in the guidelines, it is essential that no changes are made to the structure of the file. An automatic control whether there are reference errors are executed when saving the file. You should not be able to save the file if reference errors occur, it is recommended to undo actions that have affected formula references.


9.2 Consistency checks

As part of the quality control, several consistency checks are included in the spreadsheet, below the profile collection. Mainly these checks control the consistency between information reported various places in the spreadsheets. When a consistency check gives a result, there are two alternatives:

1) Change the input so that it is consistent

2) Explain why the data is still correct

To help secure that this is accomplished, a check is incorporated in the reporting file. If there are unclarified consistency checks, a warning will show up after 1 October indicating which profile sheet this relates to when closing the file.


Description of the checks:

Check 1, 3, 5 and 7:

Control that the same quantity is reported in the sheet ”Månedsdata”, as in the actual profile collection, as sale in 2018. A margin of 0.001 is granted for rounding off numbers. It is important that these numbers are correct, since they should be consistent with the production application.

Check 2, 4, 6 and 8:

Control that the resources reported in the profile collection equals the numbers reported in the project overview in the profile collection. A deviation of respectively 0.1 and 0.01 for “large” and “small” deposits is allowed.

Check 9 and 10:

Control that the different contributions to CO2- and NOx-emissions respectively, add up to the total emissions reported.

Check 11 and 12:

Control that there are CO2- and NOx-emissions every year with production. These checks are not active for profile collections containing reserves in fields without emission of fuel and flare. If there are consistency on a file level (Profil_Total) no comments are given, else there will be comments in the individual profile sheets with deviations between production and emissions.

Check 13:

Control that there is no production after shut down costs have been reported. A feedback will be given in the consistency check area in Profile 1 if the production continues after the reporting of the shut-down costs across the various projects in the file (the figures are taken from the Profil_Total, which sums the figures across the profile collections in the reporting file).

Check 14 and 15:

Is only shown in Profile 1 and is based on a summation of all profile collections in the file (Profil_Total). Control that annual cash flow and remaining net present value are positive. The intention is to check sales data versus cost data to reveal significant errors (for instance in units) in the report. In this connection, firm prices have been assumed for all petroleum products:

  • Oil: NOK 4500 per Sm³
  • Gas: NOK 2500 per 1000 Sm³
  • NGL: NOK 5000 per tonne
  • Condensate: NOK 4500 per Sm³

Consistency Check No. 15 includes assumption of a 7 % discount rate.

It is emphasized that these assumptions do not reflect the authorities' assumptions when evaluating individual projects, but are merely intended for use to reveal significant reporting errors.

Check 16 and 17:

Control gas balances for projects. Check that gas flow in and out of fields is in balance. Check 16 also includes use of gas on the field. These checks are not performed for profile collections containing reserves in fields without fuel and flare.

Check 18 and 19:

Control if comment boxes are used. It will be more useful to make comments in the text boxes prepared for this, than to comment in the space next to the response from the consistency check.

Check 20:

Control the consistency between sum of sales gas profiles per calendar year and gas year.

Check 21-24:

Control of drilling costs. This check will give a result when unit costs per well or unallocated well costs are outside the stated thresholds. The well number can be expressed as a decimal figure to correspond with accrued investments within the same year.

Check 25:

Is only shown in Profil_1. Control that operation costs are reported in the profile collection for the same period as for income. A feedback will be given in the consistency check area in Profile 1 if the condition mentioned above is not fulfilled for the file in total (the figures are taken from the Profil_Total, which sums the figures across the profile collections in the reporting file).

Check 26:

Control that removal and cessation costs are reported for projects in operation or projects containing investments in new infrastructure.

Check 27:

Control whether the table for uncertainty regarding production startup for projects in RC 2-5 is filled in and that the timing of respectively early, basis and late is consistent.

Check 28:

Control whether the table showing the project attributes is filled in. This table should be filled in for all projects with resources in RC 3-5.

Check 29:

Control whether there is a correlation between the development concept in the table of attributes and the development investment shown in the profile collections.

The control checks for investment numbers in the columns of floating or fixed facilities when these are selected as development solution, and that there is no investment numbers in these columns when subsea development is selected.

Check 30:

Control whether subsea facilities in RC 3-5 have reported associated pipeline investment and that necessary investments at the host platform are placed in the correct column.

Check 31:

Control whether discoveries have reported costs for concept studies. It also controls whether development projects have reported number of wells.

Check 32:

This check is not in use in RNB 2018. 

Check 33:

This check only appears in Profil 1 and controls whether there are negative values in the forecasted period in the total of all profiles in the reporting file (appears in Profile_Total).

Normally there should not be any negative figures in the total value for a field, discovery or facility. Negative costs should be recognized as income, negative production as injection etc.

Check 34:

Control that service provider are stated when tariffs are entered.


9.3 The spreadsheet Cost Control


The input in this sheet is the operator’s assumptions for general price increase, if not this is a constant value. In such cases input should be provided in cell AC28 in the sheet Profil_1. In addition, the sheet contains two visual consistency checks linked to the sheet ”Profil_Total”, which give a total of all the profile collections.

General price increase should be the operator's general assumption when converting current (nominal) NOK to fixed (real) NOK. For example, figures for 2018 apply to the general price increase from 2017 to 2018. This price increase must be used when converting the budget figures in current NOK to the reference year in fixed NOK. By definition, we expect the same general price increase (for instance the consumer price index) to be used for all projects reported by the same operator. We recommend that data are entered into the Cost Control spreadsheet by a coordinator before internal distribution to the projects.

The visual consistency checks below give a sum across all profile collections. Calculated net cash flow and costs per well are plotted against year. Any profile collections containing data outside a defined threshold value will be listed. Any comments, if the data is considered valid, should be made in the consistency check table for the relevant profile collections, checks 21-25.