1.0 PURPOSE

The requirement is to have a unique well identifier, recognised by the DTI and understood by all CDA members, and also to allow for wells to be identified differently by individual companies.

2.0 SPECIFIC REQUIREMENTS

2.1 To be able to identify wells uniquely prior to spud by target reference and/or slot number
2.2 To maintain aliases
2.3 To recognise components of DTI well number
2.4 To be able to sort wells efficiently

3.0 DTI WELL NAMES

3.1 A company wishing to drill a new well must apply to DTI for consent. This is now done online for all offshore wells through the DTI WONS system. The first application contains the company well name alias and provisional details of the proposed well. When the well is spudded the operating company submits details of the spud date and actual location of the well.

3.2 DTI then creates an official well name and advises the operating company.

3.3 On completion the operating company updates DTI with the completion date and other well attributes associated with the completed well.

3.4 The only official well number is the DTI well registration number. This is generated in accordance with the guidelines in the DTI notice PON12 and is supplied by the DTI once notification of spud has been received. The DTI will decide whether any sidetrack, applied for or notified, is allocated a new number or suffix on the basis of information supplied by the operating company.  Any disputes or problems on these will be handled by DTI. Companies may additionally carry their own well identifier, but when reporting or providing data to the DTI, the main well identifier must be the one generated by the DTI. Company chosen aliases may be used in addition to the DTI number for convenient cross-reference, but never on their own. If companies have wells not recognised by DTI then these can only be labelled with a DTI-like number in the official field if it is clearly differentiated as an identifier and not an officially recognised DTI well number. Such numbers will first be created in DEAL and may then be used by CDA for storage of data from wells not officially recognised by DTI.

4.0 DEAL WELL HEADERS AND WELL ATTRIBUTES: PARENT WELL AND WELL BORE

4.1 DEAL (http://www.ukdeal.co.uk/) will become the prime site for well header information in Q2 2003. At that time the DTI website will cease to publish well header data.

4.2 To comply with the POSC Well Header model well data passed from WONS will be held on the DEAL database as Parent Well and Well Bore each with their associated attributes.

4.3 The chief attribute of the Parent Well is the seabed location. Since any change in seabed location generates a new DTI well there will be no two Parent Wells with the same seabed location. It follows that re-spudding of a well results in a new parent well whereas a sidetrack will result in a new well bore.

4.4 A Parent Well may have one or many Well Bores. Most of the well header attributes, including spud and completion date, are associated with the well bore. Where a company has used the mechanical sidetrack suffix or the re-entry suffix this will be a Well bore name. A company might also wish to define other well bores not recognised by DTI but discriminated by the attributes associated with the well bore.

Example:

Parent Well	211 / 11a- 1	Well bore	211 / 11a- 1
		Well bore	211 / 11a- 1Z
		Well bore	211 / 11a- 1ZR01

4.5 Where a company wishes to use their own well bore name which nevertheless corresponds to a DEAL well bore then this name will be populated in the well bore alias field.

Example:

Parent Well	211 / 11a- 1
Well bore	211 / 11a- 1Z	Owner	DEAL	Alias	211 / 11a- 1ST1	Owner	RRI

There may be many aliases for the same well bore. Each alias will also have an owner of the well bore alias name.

4.6 When an exploration or appraisal well becomes a production well a new well bore will be created for the production well. The DTI will be recognised as the owner of both the exploration/appraisal and production well bore names. The latest status of the exploration/production well will become ‘Production’. The synonym names will also be shown as aliases to cross-reference the two wells.

Example:

Parent well	16/07a- 27
Well bore	16/07a- 27	Owner	DTI	Alias	16/07a-C1	Owner	DTI
Well bore	16/07a-C1	Owner	DTI	Alias	16/07a- 27	Owner	DTI

       
5.0 EXISTING DTI WELL NAMING STANDARD (PON 12)

5.1 The DTI recognise each new seabed location as a new well

5.2 The DTI well number comprises seven components (a) – (g) which uniquely define a well

5.3 Country Quad / Block Part Block - Platform Well Suffix

(a) (b) / (c) (d) - (e) (f) (g)
e.g. 211 / 30b- A21Z First sidetrack of well 21 on platform A in part block 211/30b

5.4 The current DTI standard allows for a single character well name suffix to describe the well status

211 / 11a- 1 First well drilled in retained part block 211/11a of quad 211 block 11
211 / 11a- 1A Re-spudded well (a new parent well)
211 / 11a- 1Z Sidetracked well

5.5 Defined suffix letters:

A, B, C, etc.– DTI Pon12 Re-Spud Wells 
Z, Y, X, etc. – DTI Pon12 Side Track Wells 

6.0 DEAL AMENDMENTS TO DTI WELL NAMING CONVENTION

6.1 SIDETRACKS NOT RECOGNISED BY DTI

For sidetracks not recognised by the DTI, but recognised by the Operator or Data Release Agent as separate well bores for which there may be data, it is recommended that suffixes J, K, L .... are used.  Where applied the well name would be a well bore associated with the official DTI parent well.

6.2 RE-ENTRY WELLS

Re-entry wells are considered by the PON 12 definition of a well to be the same surface location and therefore to be the same well number as the original. This causes difficulties for companies who wish to distinguish re-entries as separate events and thus be able to associate the well attributes and products with a distinct name.
Re-entry wells recognised by DEAL are distinguished by the addition of the suffix Rxx where xx is a number. Values less than 10 will be written as 0x to retain the full three characters. Where applied the well name would be a well bore associated with the official DTI parent well.

Examples: 
211 / 11a- 1 First well in retained part block 211 / 11a in quad 211 block 11
211 / 11a- 1A Respudded well
211 / 11a- 1AR01 First re-entry to respudded well
211 / 11a- 1AR02 Second re-entry to respudded well
211 / 11a- 2 Second well in retained part block 211 / 11a
211 / 11a- 2Z First sidetrack
211 / 11a- 2ZR01 First re-entry to first sidetrack

6.3 PILOT WELLS

For pilot wells not recognised by the DTI, e.g. those drilled as a part of a site survey, it is recommended that these are stored as unspudded wells with a target reference of EB (Exploratory Borehole). If two Exploratory Boreholes are drilled in the same block the second would have target reference EB2. It follows from this that EB is only an acceptable target reference for Exploratory Boreholes. If the Exploratory Borehole is later used for a purpose that makes it a well recognised by the DTI it will be numbered in the normal way.

6.4 DTI PON12 can be accessed from the DTI web site.

6.5 The latest set of DTI approved well numbers can now be accessed from DEAL.

 
APPENDIX A: ADDITIONAL WELL BORES
1.0 PROCEDURES FOR ADDING WELL BORES TO DEAL

1.1 The set of Parent Well and Well bore names currently on DEAL is derived from the CDA and DTI merged databases. Further parent wells and well bores have been added to enable data owners and Data Release Agents to match their well bore names to a DEAL well bore. The Parent Well and Well Bore names all comply with the CDA well naming standard CS2.

1.2 The Parent Well list should always agree with the DTI well names, since there must be a new DTI well name for every new seabed location. However the well bores recognised by Operators and the Data Release Agents may differ from those recognised by DTI. Any re-entry well will fall into this category but there are also sidetracks which are not recognised by DTI.

1.3 To be able to accurately match the well bore attributes to the true well bore additional well bores have to be created in DEAL. The source of information on these additional well bores will come from:

a. CDA DataStore, where data has been received for well bores which are not recognised by DTI and therefore cannot be loaded unless a new well bore is created.
b. UKOOA Scout database for E&A wells
c. Data Release Agent wellbore listings
d. Data Owners

1.4 Before creating any new well bore for new well data  BGS will confirm with DTI whether there is a reason why the well bore does not have official recognition. For legacy data the additional well bores will be adopted from the DRA lists to enable accurate data matching.

1.5 If a well bore is created in DEAL but the well is subsequently adopted as official by DTI then the DTI well bore name will become the official well bore name and the BGS created name will become an alias.   

1.6 Where DTI have recognised a re-spud well bore but have not created the original well bore this will be created with a standard name and with DEAL as the data owner. For example, if QQ/BB- 1A is an official DTI well bore then QQ/BB- 1 can be created without reference to DTI for confirmation. In this case a new DEAL parent well would be created as well as the well bore, since the re-spud has a different location than the original well. DEAL would be the owner of the parent well name.

1.7 When advice is received by BGS that an additional well bore is required, the name of the well bore will be kept as an alias and a new well bore name will be created according to CS2 standards. Where the well bore is a sidetrack which is not recognised by DTI then care will be taken to create a name that will not subsequently cause confusion with an official DTI name. For example, if a well QQ/BB- 1 has recognised sidetracks 1Z and 1Y then the next official DTI sidetrack will be 1X. If there is a sidetrack that is not recognised by DTI but which the Operator wishes to describe as a distinct well bore, BGS will create a new well bore with name QQ/BB- 1J, 1K etc. using the alphabet letters from J forwards to avoid potential clashes with DTI names.

1.8 In all cases the owner of the well bore name will be retained as an attribute (Well_Naming_System in the database). Thus, all Parent Well names and official DTI well bore names will have DTI as owner. Well bores required to load data to the DataStore or to match DRA or UKOOA Scout Group well bores will have DEAL as the  well bore name owner,  since the name will be created by DEAL according to the standards set out in CS-2, with the Data Owner, DRA or UKOOA name as an alias.. 

1.9 The Data Owners will be contacted to confirm the attributes of the well bores.

2.0 PROCEDURES FOR MAINTENANCE OF PARENT WELL/WELL BORE ATTRIBUTES

DTI OFFICIAL WELLS

2.1 When a new parent well and/or well bore has been created from WONS the initial attributes will be populated from the WONS XML transfer. Some attributes will not be available for alteration except by DTI, specifically the official DTI well name, the spud and completion dates. DTI may make changes to any attribute, including the well name, where obvious errors have been made. Such changes will be made to both the WONS and internal DTI database and will be onpassed to DEAL for correction.

2.2 If a completion date for a legacy well has not been submitted to WONS but the Data Owner supplies this attribute directly to BGS, then BGS will populate the attribute in DEAL and pass the information back to DTI. Completion dates for all new wells should be submitted through WONS.

2.3 Other attributes may be subsequently updated by the Data Owner, either directly to BGS or via the Landmark HelpDesk.

2.4 The surface location of the Parent Well may need to be updated to comply with the location of the Well Deviation Track. It is common for the surface location of platform wells to have a common co-ordinate at the centre of the platform. This is inadequate for deviated wells drilled from the platform and the surface location may be modified to be the accurate slot location. Data Owners will check their well header top-hole location and provide a list of corrections to the co-ordinates for the purpose of loading deviation data to the DataStore. This data will be sent to the Landmark HelpDesk, who will onpass it to BGS. All corrections to surface locations will be effected in DEAL and the corrected headers then downloaded from DEAL by Landmark for population of PetroBank.

2.5 The Current Data Owner attribute may change over time. The DataStore is a prime source of information on Current Data Owner because this information is vital for the submission of data and entitlement setting in the DataStore. Landmark will maintain the ‘Current data Owner’ in their database and provide a monthly update to BGS. BGS will then update DEAL from this update. 

2.6 The UKOOA Scout Group is also a prime source of ‘Current Well Owner’. Following the monthly update of well ownership from Landmark BGS will run a comparison against the Scout Well Ownership. Any differences found from the comparison, or in cases where a company contacts BGS directly to claim ownership of a well, then the following actions will then be taken:

a.  Where the Landmark and the UKOOA Scout listed Data Owners or a company claiming ownership directly to BGS are CDA Participants, then BGS will advise Landmark, who will confirm ownership with the relevant parties. This confirmation will be sent back to BGS
b. Where the Landmark Data Owner, or direct claimant, is a CDA Participant and the UKOOA Scout owner is not then BGS will advise Landmark, who will confirm ownership with the CDA Participant. If the CDA Participant denies ownership this information will be sent back to BGS. The non-CDA owner will be adopted and corrections made to both DEAL and the DataStore. Landmark will effect this change through the normal procedures, with CDA acting as signature for the non-CDA Participant. 
c. Where neither the Landmark nor the UKOOA Scout owner nor the direct claimant are CDA Participants then BGS adopt the UKOOA Scout or direct claimant owner and advise Landmark.

2.7 Other attributes can only be corrected by the Data Owner. If the listed Data Owner confirms in writing to BGS that certain of the well attributes are incorrect the attribute values will be changed in DEAL. If a non-owner advises BGS of an incorrect attribute value than BGS will request clarification from the Data Owner before making any change.

2.8 Any anomalies between the UKOOA Scout attribute values and the listed DEAL values will be queried with the Data Owner and, where the UKOOA Scout values is confirmed to be in error BGS will advise the Scout Group representative (Ray McIntyre).

NON-DTI WELL BORES

2.9 Attributes associated with non-DTI well bores created in DEAL to enable Data Owners and/or Data Release Agents to accurately match their catalogues in DEAL will be populated in the first instance from the source of the well bore.

2.10 When a new well bore is created in DEAL to match a well on the UKOOA Scout database then the attributes will be adopted from the Scout database. If this well bore is also matched in the Data Release Agents lists then the attributes will be cross checked with the DRA attributes to confirm that the same well bore is being matched.

2.11 If the Data Owner has supplied data to the DataStore and a non-DTI well bore is needed to load the data, Landmark will advise BGS. The Data Owner will be contacted and requested to provide the attribute values for the well bore.

2.12 If a DRA has supplied catalogue information to the Data Registry and a non-DTI well bore is needed to match the catalogue BGS will request the associated well bore attribute values from the DRA, and will populate these in DEAL. The Data Owner will be contacted and requested to check and confirm the attribute values for the well bore.