METHOD FOR CONTROLLING A STATE OF A TUBE, METHOD FOR CONTROLLING A STATE OF WELL, SYSTEM, TUBE

Abstract

A method for controlling a state of a first tube, said first tube being intended to be integrated in an extraction structure, a first server managing a digital descriptor of the first tube, said digital descriptor having a first set of data stored on at least a first memory, said first set of data comprising at least: one identification number of the first tube and; a completion status and a planification status, the method includes generating a first request to a first server from a computer located near the first tube acquiring the identification number in order to generate an inventory status of the first tube, acquiring a first value of a completion status of the first tube, acquiring a second value of a planification status of the first tube, and generating at least one alert when the first or the second value is equal to a predefined state value.

Claims

1-24. (canceled)

25. A method for controlling a state of a first tube, said first tube being intended to be integrated in an extraction structure, a first server managing a digital descriptor of the first tube, said digital descriptor comprising a first set of data stored on at least a first memory, said first set of data comprising at least: one tracking code of the first tube and; a completion status and a planification status, wherein said method furthermore comprises: authenticating the first tube by capturing the tracking code of the first tube; generating a first request to a first server from a computer located near the first tube; acquiring an identification number in order to generate an inventory status of the first tube; acquiring a first value of a completion status of the first tube; acquiring a second value of a planification status of the first tube; generating at least one alert when the first or the second value is equal to a predefined state value.

26. The method according to claim 25, wherein the first set of data comprises at least: a first subset of geometrical data comprising at least one of the following features: an outside diameter; an internal diameter; a weight; a steel grade; a drift diameter; a wall thickness; a minimum wall thickness; an effective length; a material standard; a second subset of junctional component data comprising at least one of the following features: a connection type; a joint length total with another interface component; a third subset of workflow data comprising at least one of the following features: a pipe tracking code; a coupling tracking code; a serial number; a contract number indicating the position of the wells; a manufacturer's name; a manufacturing date; a fourth subset of job data comprising at least one of the following features: a job reference; a sequential number in a job.

27. The method according to claim 26, wherein the completion status is given for: a presence of at least one value in predefined fields of data of the first, the second and the third subsets of data of the first set of data; and/or, a specific field value of a completion status field in the first set of data.

28. The method according to claim 25, wherein the planification status is given for: a presence of at least one value in predefined fields of data of the fourth subsets of data of the first set of data; and/or, a specific value of a feature of the fourth subset of data.

29. The method according to claim 25, wherein the first set of data comprises a job reference of a job datasheet, said job datasheet comprising a sequence number, wherein said method furthermore comprises: generating a second request to a first server from a computer located near the first tube; extracting a job datasheet including a second set of data relating to a plurality of tubes, said plurality of tubes including the first tube; acquiring the sequential number of the first tube from the first set of data; comparing the sequential number of the first tube in said job datasheet with a sequential number of: another tube of the same job datasheet; the first tube being recorded in the first set of data; generating an alert when the comparison of both sequential numbers is inferior or superior to a predefined threshold.

30. The method according to claim 25, wherein the first set of data comprises at least a fourth value of a geometrical feature of said tube, said method defining a geometrical status, said method comprising: acquiring a value of the first geometrical feature by a user interface; comparing the fourth value of the geometrical feature comprised in the first set of data with the acquired value of the first geometrical feature of the first tube; generating a third alert when the comparison of the two fourth values is superior or inferior to a predefined threshold.

31. The method according to claim 30, wherein: when the first geometrical value is the total length of the first tube, said method defining a length status, the method comprises the steps of: automatically calculating the cumulated length of tubes integrated in the extraction structure which have a sequential number inferior to the sequential number of the first tube; comparing the calculated cumulated length with a reference value recorded in the workflow data; generating an alert when said comparison is superior or inferior to a predefined threshold.

32. The method according to claim 30, wherein: when the first geometrical value is the internal diameter of the first tube, said method defining a mud status, the method comprises the steps of: automatically calculating an estimated mud gain value; comparing the calculated estimation of mud gain value with an expected mud gain stored in the workflow data; generating an alert when said comparison is superior or inferior to a predefined threshold.

33. The method according to claim 30, wherein: when the first geometrical value is the outside diameter of the first tube, said method defining a cement status, the method comprises the steps of: automatically calculating an estimated cement volume to be introduced; comparing the calculated estimation of cement volume with an expected cement volume stored in the workflow data; generating an alert when said comparison is superior or inferior to a predefined threshold.

34. The method according to claim 25, wherein the acquisition of the data from the first memory comprises: reading a tracking code on the surface of the first tube by activating an optic sensor of a radio antenna; generating a request to a first server in order to extract at least a subset of the first set of data from the first memory; receiving the first set of data on a user device through a wireless interface.

35. The method according to claim 25, wherein the first server manages a plurality of memories in a cloud architecture, wherein the second set of data is stored on at least the first memory of the plurality of memories.

36. The method according to claim 25, wherein the first server periodically transmits the first set (SET1) of data to a central server.

37. The method according to claim 26, wherein it comprises: reading a tracking code on said first tube with an optic sensor or a radio antenna; modifying a data from the first subset of geometrical data or from the second subset of junction data of the first tube with a user interface; recording the modified data associated to a timestamp in the first memory; transmitting the modified data associated to the timestamp in a memory managed by the central server, said modified data being associated to the first tube in said memory; updating the digital descriptor of the first tube.

38. The method according to claim 25, wherein the method comprises a preliminary step of pairing the first set of data with the tracking code.

39. The method according to claim 25, wherein the tracking code on the first tube is an identification tags or a marking being arranged on the surface of the first tube.

40. A method for controlling a state of a well, a first tube being intended to be integrated in an extraction structure present in said well, a first server managing a digital descriptor of the first tube, said digital descriptor comprising a first set of data stored in at least a first memory, said first set of data comprising at least: one tracking code of the first tube; and an internal diameter; wherein said method furthermore comprises: authenticating the first tube by capturing the tracking code of the first tube; generating a first request to a first server from a computer located near the first tube; acquiring a value of the internal diameter of said first tube; automatically calculating an estimated mud gain value by taking account of the internal diameter of said first tube and a value issued from the extraction structure present in the well; comparing the calculated estimation of mud gain value with an expected mud gain value recorded in the first set of data; generating an alert when said comparison is superior or inferior to a predefined threshold.

41. A method for controlling a state of a well, a first tube being intended to be integrated in an extraction structure present in said well, a first server managing a digital descriptor of the first tube, said digital descriptor comprising a first set of data recorded in at least a first memory, said first set of data comprising at least: one tracking code of the first tube; and an outside diameter; wherein said method furthermore comprises: authenticating the first tube by capturing the tracking code of the first tube; generating a first request to a first server from a computer located near the first tube acquiring a value of the outside diameter of said first tube; automatically calculating an estimated structure external volume using at least the value of the outside diameter of said first tube; comparing the calculated estimation of structure external volume with an expected structure external volume value recorded in the first set of data; generating an alert when said comparison is superior or inferior to a predefined threshold.

42. A method for controlling a state of a well, a first tube being intended to be integrated in an extraction structure present in said well, a first server managing a digital descriptor of the first tube, said digital descriptor comprising a first set of data recorded in at least a first memory, said first set of data comprising at least: one tracking code of the first tube; and an outside diameter; wherein said method furthermore comprises: authenticating the first tube by capturing the tracking code of the first tube; generating a first request to a first server from a computer located near the first tube; acquiring a value of the outside diameter of said first tube; automatically calculating an estimated cement volume using at least the value of the outside diameter of said first tube; comparing the calculated estimation of cement volume with an expected cement value recorded in the first set of data; generating an alert when said comparison is superior or inferior to a predefined threshold.

43. A computer program comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method of claim 25.

44. A system for managing digital descriptors of a plurality of tubes, each tube being intended to be integrated in an extraction structure, said system comprising: a central server addressing a memory wherein a digital descriptor of a first tube is paired with a tracking code; at least one local server; a plurality of tubes located on different areas, each area being equipped with a local network infrastructure allowing establishing a communication between at least a first user computer and a local server; each tube comprising at least one tracking code on the surface of said tube by activating an optic sensor of radio antenna; at least one optic sensor or one radio antenna, called first sensor, arranged in each area, said first sensor being configured to capture the tracking code; a local computer receiving the tracking code; and generating a request to a local server, said first local computer furthermore comprises means for: receiving a first set of data comprising values associated to a tube features; editing at least one value of a tube feature; generating an associated timestamp; transmitting the new value with the associated timestamp to the first server; a communication interface allowing updating the first set of data managed by the central server, said updated data being recorded in at least one memory archiving the previous data added with the new data associated with the timestamp.

45. The system according to claim 44, for implementing a method for controlling a state of a first tube, said first tube being intended to be integrated in the extraction structure, a first server managing the digital descriptor of the first tube, said digital descriptor comprising a first set of data stored on at least a first memory, said first set of data comprising at least: one tracking code of the first tube and a completion status and a planification status, wherein said method furthermore comprises: authenticating the first tube by capturing the tracking code of the first tube; generating a first request to a first server from a computer located near the first tube; acquiring an identification number in order to generate an inventory status of the first tube; acquiring a first value of a completion status of the first tube; acquiring a second value of a planification status of the first tube; and generating at least one alert when the first or the second value is equal to a predefined state value.

46. A tube comprising at least six marks at it surface, each mark representing the same tracking code, a first set of marks being arranged in cylindrical symmetry so that they are spaced substantially 120° angle apart in a first distal portion of the tube, a second set of marks being arranged in cylindrical symmetry so that they are spaced of substantially 120° to each other in a second distal portion of the tube.

47. The tube according to claim 45, wherein: the first set of marks comprises another set of three marks being arranged in cylindrical symmetry so that they are spaced substantially 120° angle apart in a first distal portion of the tube and arranged at a first predefined distance of the first three marks of said set of marks, the second set of marks comprises another set of three marks being arranged in cylindrical symmetry so that they are spaced substantially 120° angle apart in a second distal portion of the tube and arranged at a second predefined distance of the first three marks of said set of marks.

48. The tube according to claim 45, wherein each mark comprising the tracking code on the tube is: an identification tags, such as RFID tag; a barre code or a QR code printed on the surface of the tube.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0130] FIG. 1: is a schematic representation of the system of the invention according to an embodiment wherein fourth local servers are associated to different areas where a tube may be manipulated, repaired or selected so that it digital descriptor may be requested.

[0131] FIG. 2: is a time line representing different modifications of digital descriptor of a tube evolving in different sites, having different treatments, and being assigned to a specific job in a given place.

[0132] FIG. 3: is a schematic representation of a tube according to one embodiment of the invention, said tube being on the area where a control according to one embodiment of the invention is operated so that to verify the compliance between the digital descriptor so said tube and a predefined job datasheet indicating the use of said tube.

[0133] FIG. 4: is a first flow chart showing the main steps of one embodiment of the method of the invention, wherein an inventory status of the first tube and a completion status of the first tube are verified according to the digital descriptor of said tube.

[0134] FIG. 5: is a second flow chart showing the steps of one embodiment of the method of the invention, wherein a value of geometrical data of junction data is verified according to a comparison between the digital descriptor and at least one input value.

[0135] FIG. 6: is third flow chart showing the steps of one embodiment of the method of the invention, wherein it comprises an updating step of a value of a data of the digital descriptor in a local/central server.

DESCRIPTION

Definitions

[0136] The term “component” as used here means any element or accessory used to drill or operate a well. The component may, for example, be a relatively great length tubular element (approximately ten meters in length), for example a tubular, or a tubular coupling of several tens of centimeters in length, or indeed an accessory for these tubular elements (a hanger, a cross-over, a safety valve, a tool gasket, sub or the like). The component may be a pipe comprising one great length tubular element assembled with a coupling.

[0137] A component may comprise one connection or connector or indeed threaded end and intended to be coupled via a threading to another component in order to constitute a threaded tubular connection with this other component.

[0138] The components of the invention, such as tubes, are intended to be integrated into a final assembly in the well, this final assembly is called the “extraction structure” in the present description and noted ST.sub.1. These components are generally connected one to another for dropping into the hydrocarbon well or similar wells. The extraction structure ST1 comprises all components intended to be introduced in a well, such as a drill stem, a casing string or liner string or indeed a tubing string, such as operating columns. For example, a typical well may comprise three casing strings of different diameters and lengths, and a liner string.

[0139] The terms “component”, “tubular component” and “tube” are used interchangeably in the present description to refer to a piece of an extraction structure ST.sub.1 in that the components are always going to be tubular pieces or substantially tubular pieces, or almost tubular pieces.

[0140] The term “job”, noted Jb, refers to a task considering the preparation of an assembly: the extraction structure ST.sub.1. A job also deals with its introduction in the well on the drill area. The introduction of the extraction structure ST.sub.1 is made component T.sub.k by component T.sub.k+1 following a predefined sequence SEQ.sub.1. The definition of a job Jb1 implies the definition of a reference, called “job reference”. All components which are concerned by the same extraction structure ST.sub.1 entering in the well W.sub.1 are referred in the job Jb1 by using a tally list.

[0141] A job is associated to the following list of items. [0142] A contract number, CN. The contract number refers to the place where the well is built. The contract number CN may refer to a location, a geographical position, or any information allowing defining the area where the well is built. [0143] A rig reference, which refers to a specific rig implemented in a chosen place where the well will be done. The rig may be a rig-type on the water or a on earth. Each rig-type may have specific features. [0144] A tally reference, the tally is list of components and their associated features which will be introduced in the well. [0145] Different actions that should be realized on each component. [0146] A Job status: preparation, running, finish.

[0147] The tally, noted TAL, deals with all types of equipment to be introduced in a well W.sub.1, such as drilling equipment, casing equipment, tubing equipment, etc. Each equipment listed in a tally TAL.sub.1 is associated with other items that could be indicated in the tally: [0148] a set of features indicating some properties of said component T.sub.k; [0149] a set of features indicating some properties of a list of components having interactions with others, such as a connection, a contact, a relative position; [0150] a tracking code; [0151] a job status: preparation, running, finish [0152] an effective length; [0153] an internal diameter; [0154] a sequence number gives an indication of the order in which each component should be introduced in the well. Moreover, the sequence number give an information on the relation between a component and other components that it should be connected within;

[0155] The tally also comprises some indicators such as: [0156] a cumulated length of a set of components T.sub.1 which form a part of the extraction structure ST.sub.1; [0157] a mud gain MG expressed in cubic meter, this indicator may, for example, be extracted from another document or from a computed result from a computer, the indicator may be displayed and aggregated to the tally so that it could be considered that is a part of the tally; [0158] the string inner volume SIV expressed in cubic meter, this indicator may also be extracted from another document or from a computed result from a computer, the indicator may be displayed and aggregated to the tally so that it could be considered that is a part of the tally.

[0159] The tally may be in different states as “pre-tally”, or “running tally”. One advantage is to generate a customized list of components T.sub.k depending on the place or the action to be taken on the component.

[0160] For instance, an operator on a rig place, such as site 40, needs to consult all components that are inside and outside the well W1. One advantage is to compute for example the cumulated length of the extraction structure at any time. Another advantage is the accuracy of the computed total length. This enables precise positioning of equipment along the structure, particularly equipment that could be attached to a specific tube.

[0161] In another example, an operator which is in site 30 would like to have the list of the components of specific job Jb1 in order to have a great attention to the last reparations. In this case, the operator does not need to access to the components which are already introduced in a well. In that objective, the operator, via a user interface, will request for a pre-tally for checking some actions.

Depending of the pre-tally of the tally list, a level of accuracy of the data describing the tubes may be documented in the local database.

[0162] According to an embodiment of the invention, an interface of a computer generates a list of the components T.sub.k of an extraction structure ST.sub.1 of a predefined well W.sub.1. A given job Jb.sub.1 allows presenting the list of the components T.sub.k to be introduced into the well W.sub.1 with an assigned order in a predefined sequence SEQ.sub.1. The predefined sequence SEQ.sub.1 ensures an operator that each action he will carry out on a component T.sub.k is done in a correct order. The sequence SEQ.sub.1 is generated by a management tool that is accessible with a computer of an operator. The sequence SEQ.sub.1 is recorded in the job Jb.sub.1.

[0163] The sequence SEQ.sub.1 allows generating an indicator relative to the integration of components in an extraction structure ST.sub.1 before or during their introduction into the well W.sub.1.

[0164] In that way, the sequence SEQ.sub.1 is a powerful tool allowing an operator at each stage to plan the next actions on components T.sub.k.

[0165] The invention allows offering an interface showing: [0166] all components intended to be introduced into a given well W.sub.1 and; [0167] metrics and indicators automatically generated for controlling actions made on said components during drilling and completion operations.

[0168] This interface may give access to all or part of information of the tally TAL.sub.1 and the associated job Jb.sub.1 relative, and consequently to, for instance, the drilling equipment, or casing and tubing equipment to be used in the well which are documented in the Tally.

[0169] An advantage of the sequence SEQ1 is to decrease errors made during the planning review of the installation of the extraction structure ST.sub.1. Moreover, it allows generating indicators with different levels of accuracy depending on the desired objective to be completed. Consequently, the activity reports that could be automatically generated are facilitated.

[0170] A “local server” SERV.sub.1i is a server assigned to an area “i” or a site where tubular components may be stored and where data relative to tube features may be recorded. In such place a local database DB.sub.1i is associated to the local server SERV.sub.1i. This local database DB.sub.1i may be the server memory or another memory.

[0171] In consequence, in the description of the present invention, it may be considered that a “local server” or a “local database” refers to the same network element having memory and accessibility capabilities such as a communication interface Ethernet, RJ45, optic fiber, etc.

[0172] Digital Descriptor

[0173] The digital descriptor DD.sub.1 of a tube comprises a first set of data SET.sub.1 which is stored in at least one memory M.sub.1. The first memory M.sub.1 is located at a central node of the network comprising different sub-networks. A first server SERV.sub.1 manages a plurality of digital descriptor D.sub.k of a plurality of components Tk, such as tubes, in the central node. The first memory M.sub.1 may be implemented in the server SERV.sub.1 or may be distributed in different servers as a cloud architecture in the central node.

[0174] According to one embodiment, the first set of data SET.sub.1 comprises different subsets of data SET.sub.11, SET.sub.12, SET.sub.13, SET.sub.14,

[0175] In one example, the first subset of data SET.sub.11 deals with geometrical data and comprises at least one of the following features: [0176] a real outside diameter; [0177] a nominal outside diameter; [0178] a real internal diameter; [0179] a nominal internal diameter; [0180] a real weight; [0181] a nominal weight; [0182] a steel grade; [0183] a drift diameter; [0184] a real wall thickness; [0185] a nominal wall thickness; [0186] a minimum wall thickness; [0187] a minimum wall thickness; [0188] an effective length, [0189] a material standard, [0190] a maximal torque; [0191] an optimal torque; [0192] a minimal torque; [0193] a minimal shoulder Torque; [0194] a maximal shoulder torque; [0195] a maximal delta turns; [0196] a shoulder slope; [0197] a make-up loss.

[0198] In one example, the second subset of data SET.sub.12 comprises junctional component data. This subset SET.sub.12 comprises at least one of the following features: [0199] a connection type; [0200] a total joint length (with another interface component; [0201] an effective joint length total [0202] a special clearance coupling, [0203] a reduced coupling OD which reduces the tensile efficiency of the connection, [0204] a special bevel to reduce risk of a coupling hanging up down the hole when having multiple strings in the same casing string, [0205] a match strength: modified couplings to achieve a 100% efficiency in tension, [0206] a dopeless: connection having a coating which allows the user not use dope to make-up the connections [0207] etc.

[0208] In one example, the third subset of data SET.sub.13 comprises workflow data, such as logistical data. This subset SET.sub.13 comprises at least one of the following features: [0209] a pipe tracking code, TC; [0210] a coupling tracking code, CTC; [0211] a contract number, CN; [0212] a manufacturer name, MN; [0213] a manufacturing date, MD.

[0214] In one example, the fourth subset of data SET.sub.14 comprises job data. This subset SET.sub.14 comprises at least one of the following features: [0215] a job reference Jb; [0216] a sequential number S.sub.3 in a job.

[0217] FIG. 1 represents the routing sequence of a tube T.sub.1 of the invention starting from a production site 10 until to the site 40, such a well W.sub.1, where the well W.sub.1 is tube T.sub.1 is introduced.

[0218] In FIG. 1, a production site 10, an equipment site of tubes 20, an inventory and repairing site 30 and a destination site 40 are represented. The invention is not limited to this site architecture. In different embodiments of the invention, a predefined tube may route from different sites before arriving in the destination site.

[0219] FIG. 2 illustrates an example of a routing sequence of a predefined tube T.sub.1, called first tube T.sub.1. At time t.sub.0, the first tube T.sub.1 is in site A for its production. At time t.sub.1, the tube T.sub.1 is transported into a second site 20 in order to be equipped with terminations to its ends. The tube T.sub.1, for example, built in stainless steel grade may also be suited to specific surface treatment in site 20. The tube T.sub.1 is then transferred, for instance by boat 23, at time t.sub.2, in site 30 for completing an inventory step 21. Furthermore, at this stage, the tube T.sub.1 may be assigned to a specific well W.sub.1. In this site 30, checks and controls may be completed by an operator. In the example of FIG. 2, the tube T.sub.1 is returned at time t.sub.3 to site 20. At this stage, the tube T1 is adapted or repaired in order to be compliant with a specific need for example specified in a job datasheet relating to a specific well W1. After reparation or adaptation, the tube T.sub.1 is sent at time t.sub.4 to site 30 and then, it is delivered at time t.sub.5, for instance by boat 3, to site 40. The site 40 if for example a well W.sub.1.

[0220] In other routing sequence, a second tube T2 may be directly delivered from site 10 to site 40. All combinations of routes may be envisaged in the different embodiments of the invention.

[0221] Each area 10, 20, 30, 40, or other sites not described, where a tube T.sub.1 may be transported comprises a local memory M.sub.1 comprising a first set of data SET.sub.1. The data describing said tube T.sub.1 are intended to grow and they may be completed all along the routing and the actions fulfilled on said tube T.sub.1.

In a preferred embodiment, the local memories are arranged in a server. In one example, each site 10, 20, 30, 40 comprises a local server SERV.sub.ii, SERV.sub.12, SERV.sub.13, SERV.sub.14. In one embodiment, each server may be accessible via a wireless interface such as WIFI. A terminal such as a mobile device or a computer comprising a management interface may communicate with a server. In some embodiments, an authentication server (not represented) may be dedicated to secure transmissions between a terminal and a local server.

[0222] According to one embodiment of the invention each local server transfers automatically or manually the first set of data with a central server SERV.sub.0. According to one embodiment, the first set of data may be recorded in a wearable memory which is then synchronized with the central server SERV.sub.0. This scenario may happen when the local server SERV.sub.14 is located at a rig, for example in the sea, without any wireless connection directly set with an access point. In such configuration, an operator may locally transfer the first set of data and then record the data in the central server SERV.sub.0 from another site. According to an embodiment, when possible, periodically a local server transfers the first set of data to the central server or the central servers.

[0223] The transmitted data are associated to a timestamp. The central server SERV0 records the second set of data SET1 by processing a treatment which allows associating the data to a specific timestamp when necessary.

[0224] A production mill 10 can produce a variety of tubes T.sub.k at different external and internal diameters and with different wall thicknesses and sometimes with some shape variations. A set of mechanical features of each tube may be entered in the first local server S.sub.11. FIG. 2 shows an example of what information could be stored in the server at the production of a tube T.sub.1. For instance, the effective length EL, the weight WE, outside diameter OD, the internal diameter ID and the wall thickness may be defined in site 10 during or after the production of tube T.sub.1. Other geometrical data may be recorded at this stage according to the different embodiments of the invention.

[0225] According to an embodiment of the invention the first set of data comprises workflow data SET.sub.13 used to traceability and logistical purposes. In one embodiment, a tube T.sub.1 comprises a serial number SN and a manufacturing date MD which are set in the first local server SERV.sub.11 during or after the production of tube T.sub.1. In other embodiments, other information may be recorded at this stage in the local server SERV.sub.11.

[0226] In one embodiment, numerous features of each tubular component T.sub.k produced are basically obtained via quality control and through nondestructive testing operations at the production mill.

[0227] Connections are not necessarily manufactured immediately after the fabrication of the tube T.sub.1 but they are made after at a finishing work facility next to the mill or distant from the mill in site 20. The invention allows considering both configurations: when connections are realized in the production mill 10 or in another site 20.

[0228] Most of time, a tube T.sub.1 of the invention is specialized with a connection in another site, for example site 20, from the production site, as site 10. A tube T.sub.1 is adapted, equipped or machined later with the appropriate features in function of the customer requirements and order. The second subset of data SET.sub.12 comprising junctional data may be recorded in site 20 latter after the production of tube T.sub.1. In the example of FIG. 2, the connection type CT(1) and the total joint length JLT of said tube T.sub.1 with a specific connection is entered in the local server SERV.sub.12 of site 20.

[0229] In site 20, other workflow data may be recorded in the server SERV.sub.12 as for instance a tracking code TC and a contract number CN. In one embodiment, each workflow data is recorded in the local server 12 with an associated timestamp t.sub.1.

[0230] The input data in the server SERV.sub.12 are then synchronized with a central server SERV.sub.0 in order to record all information in a central memory or a central database DB.sub.0. In one embodiment, each workflow data that is transmitted to the central server SERV.sub.0 is associated with an associated timestamp t.sub.1 so that each recording recorded in the central server SERV.sub.0 comprises each a timestamp.

[0231] In one embodiment, if there is a conflict between a workflow data that is already recorded in the central server SERV.sub.0 and the same workflow data with a new value which is transmitted from a local server SERV.sub.12 to the central server SERV.sub.0 in order to be recorded, the invention allows managing the conflict by recording the same workflow data with the two different values by associating each workflow data to their timestamp: t.sub.0, t.sub.1.

[0232] After their manufacture, some tubular components are shipped to a stocking destination. In one embodiment, the tube T.sub.1 is arriving in site 20 for being stocking, receiving a tracking code TC and optionally receiving adaptations, modifications or any customization for example as a thread at their ends or a specific connector or a coating treatment. In other examples, each tube Tk may receive specific adaptations, modifications or any customization in other stages of their routing.

[0233] One consequence is that some data from the second subset SET.sub.12 from the first set of data SET.sub.1 may be recorded in the local server SERV.sub.12.

[0234] In the example of FIG. 2, the tube T.sub.1 is modified to be prepared by receiving a connector INT.sub.1 at each end. An operator is accessing to the local server SERV.sub.12 via an interface for defining or updating the connection type TC of these connectors INT.sub.1 and the total joint length JLT of the tube T.sub.1 with said connectors. This operation is indicated with SET.sub.12(CT(INT.sub.1), JLT)

[0235] Following the routing sequence, the tube T.sub.1 is transported in site 30. In site 30 an operator assigns a Job reference and a sequential number S.sub.3 in the sequence SEQ.sub.1 of said job. In this example, after an inspection, an operator indicates that a modification should be made on the connectors INT.sub.1. An indication, such as INT.sub.M, is recorded in the local database. The tube T.sub.1 is routed to site 20 for being repaired or modified.

[0236] All data from the second and the third subsets SET.sub.12 and SET.sub.13 recorded in the local server SERV.sub.12 are automatically transmitted to the central server SERV.sub.0, for example by a backup storage planned every night at a predefined hour.

In this operation, each data is recorded in the central server SERV0 with their timestamp t.sub.2.

[0237] In one embodiment, tubular products T.sub.k can be sent to a location called rig prep, site 30 in FIG. 1, where the tubular products T.sub.k are prepared in view of their future use during a job on a yard or a rig such as site 40. Tubular components T.sub.k may stay in the well drilled and completed, or they can be sent back to rig prep, and be stocked for a future job or if need be, sent to a repair shop such as site 20.

[0238] In the example of FIG. 2, the tube T.sub.1 is returned to site 20 for a change on the connectors INT.sub.1, for example re-machining the thread of each connector INT.sub.1 arranged at each end of the tube T.sub.1. In this example, this operation leads to reducing the length of the total joint length JLT. The operation made, the operator set the new input in the local database, i.e. the local server SERV.sub.12, by generating a command SET.sub.12(CT(INT.sub.2), JLT.sub.2). In that example, the notation INT.sub.2 refers to the modified connector comprising a lengthening thread and JLT2 refers to the new total length of the Tube T.sub.1 considered with their connectors.

[0239] Different reasons may justify some reparations of tubes. For instance, a repair shop which may not be controlled by the initial manufacturer or the final user of the tubular component may measure the tubular component's length, according to the international API standard, requiring a length measurement with an accuracy of plus or minus 30 mm, whereas the final user may need an accuracy of plus or minus 3 mm. For these reasons, tubular components may be prepared during rig prep on yard or rig at stage 30 or 40.

[0240] On every stage, some controls may be done on tubular component. Features may be updated following the controls during rig prep. Also, the tubular components can be repaired at repair shops or any manufacturing or maintenance facility, thus modifying some of the initial features measured at the production mill as it is illustrated with the example of FIG. 2.

[0241] In the example of FIG. 2, the Tube T1 is sent to site 30 at time t4 and then to the well site, site 40 at time t.sub.5. At time t.sub.5 on the rig, an operator may modify a new feature, such as the effective length EL of tube T1 by measuring with an accurate method. In that example, the operator enters the new measured effective length in the local server SERV.sub.14. That operation may be realized so as to determinate with a huge amount of accuracy the mud gain in the well W.sub.1.

[0242] The geometrical data SET.sub.11 may be updated at this stage in the local server SERV.sub.14, such as the effective length EL. The data recorded in the server SERV.sub.14 are then transmitted to the central server SERV.sub.0, automatically or manually for their synchronization.

[0243] The invention provides a method and a system where updated features of the tubular products T.sub.k in a local place are recorded in a corresponding local database of the local server SERV.sub.11, SERV.sub.12, SERV.sub.13, SERV.sub.14. A local database contains local records relative to the tubular components T.sub.k. A local record comprises a data representative of a tubular feature associated with a timestamp such as t.sub.1, t.sub.2, t.sub.3, t.sub.4, in example of FIG. 2. A local server SERV.sub.1i may send to a central database SERV.sub.0 the local records. According to different embodiments, the sending of the local database can be done in real time or periodic.

[0244] In one embodiment, the local database SERV.sub.1i can be synchronized so that the local database receives central records from the central database SERV.sub.0.

[0245] A local database of local server can be a mill database, a rig database, a repair shop database. In this last example, a local database can be a field service database. A field service means an accessory and repair shop which have capacities to machine connections. Indeed, tubular components T.sub.k may need repair after transportation or use, or an accessory can be manufactured starting from another component.

[0246] When measures are done on the tubular component T.sub.k or modifications are brought to the tubular component T.sub.k which modifies one or more features of the tubular components, then one or more local records representative of the one or more features are recorded into the local database SERV.sub.1i via a local user interface.

[0247] The synchronization of a local database, i.e. local server, SERV.sub.1i with the central database, i.e. local server SERV.sub.0, can be done in real time when a communication interface allowing the central server to be accessible to the local server.

[0248] In one embodiment, during synchronization, for an item of the local database DB.sub.1i, local records of local database DB.sub.1i is compared to central records of central databases DB.sub.0. When there is no equivalent of a local record in local databases, then the local record is pulled out from local database DB.sub.1i to central database DB.sub.0. In FIG. 2, in the site 10 at time t0, the effective length EL is set for the first time in the local database DB.sub.1i. When this information is synchronized with the central database, the new entry is recorded in the central database DB.sub.0.

[0249] In one embodiment, the invention also provides means such as a local database DB.sub.1i containing data representative of the central records of the central database DB.sub.0. In one example, this local database DB.sub.1i may be configured to contain only a part of the items of the central database DB.sub.0.

[0250] According to one embodiment, the remote database DB.sub.1i is synchronized with the central database DB.sub.0, real time or periodically. Advantageously, the remote database DB.sub.1i contains the data relative to the tubular component T.sub.k in their latest known update. For instance, an operator in site 40 at time t.sub.5, who controls by a user interface the connection type CT of tube T.sub.1 will only see the connection type CT(INT.sub.2).

[0251] The central database DB.sub.0 contains: [0252] the features given by the mill 10 or by the repairing shop 20 having manufactured or adapted the tubular component T.sub.1, and; [0253] the updated data from a repair shop or a service company that have modified or controlled and measured features of the tubular component T.sub.1, or from another remote/local database DB.sub.1i.

[0254] The remote database DB.sub.14 may correspond to a rig database, i.e. site 40, where measurements are done to verify tubular component characteristics. These measurements are then recorded in the remote database DB.sub.14 as a remote record comprising a data representative of a tubular feature measured on the remote location 40 associated with a timestamp t.sub.4.

[0255] The remote database DB.sub.14 may send the remote records to the central database DB.sub.0.

[0256] A rig, as site 40, is likely not having a stable data link as a rig can be offshore or in a desert, or it is not always possible to obtain a link through the network of the operator running the rig. The remote database may be synchronized periodically, for example after the job has been done.

[0257] A central database DB.sub.0 contains data representative of central records from the central database at a first state, such as a state defined at time t.sub.0. A central database DB.sub.0 thus also may comprise data representative of remote records or local database under the form of central records at another state, for example records associated to another timestamp t.sub.3.

[0258] During drilling and completion operations in site 30 or 40, casing and tubing are expected to be run in a hole as planned in the sequence recorded in the job datasheet. This sequence SEQ.sub.1 ensures to guarantee well integrity and completion program.

[0259] The list of components necessary for casing and completing the well W.sub.1 is prepared in a job datasheet. This job data sheet comprises the tally which may be used for preparing rig operations.

[0260] According to the invention, the tally comprises a pre-list P-LIST.sub.1 that comprises a sequence SEQ.sub.1 of what and when components are supposed to be introduced in the well W.sub.1 with a predefined order. The differences between the prelist P-LIST.sub.1 and the list LIST.sub.1 of the job are set of tubular components that are already introduced in the well W.sub.1.

[0261] The level of detail in the tally depends on the complexity of the well W.sub.1. During running, this list is updated with the actual pipes lowered in well. The pre-list P-LIST.sub.1 becomes the LIST.sub.1. This list LIST.sub.1 is also called the run-in-hole, RIH, tally and is used to check the compliance with the plan and to report activities.

[0262] The invention allows controlling the sequence dynamically ordered in the tally for reducing errors that are made in the last steps of introduction of components in the RIG. The invention allows reducing the changes or the returns in components intended to be introduced in the well which are not compliant with tally.

[0263] According to one embodiment, the invention takes advantage of marking tube T.sub.k with a tracking code TC.sub.1 in order to synchronized changes in the management and the routing of tubular components from their manufacturing to their introduction into a well W.sub.1.

[0264] According to one embodiment, the tracking code TC.sub.k of a component T.sub.k is paired with an identifier of said component T.sub.k.

[0265] According to one embodiment, each tube T.sub.k intended to be introduced in a well is marked by a code physically marked on the surface of said tubes. According to one example, the marking is an optically readable marking such as a barcode, of the type of barcode 128 for instance, or a data matrix. In different embodiments, the marking is realized by painting, printing or by sticking a label on the surface of the tube T.sub.k. According to another example, the marking is made by laser marking.

[0266] According to another embodiment, the marking on tube T.sub.k may be realized by a radio tag such as a RFID tag. The tracking code TC may be recorded on a passive or an active RFID tag for example sticking on the surface of the tube T.sub.k.

[0267] At each stage of the routing of a tube T.sub.k, an operator can read the tracking code TC using an optical sensor, or more commonly called a reader, such as a camera or a radio antenna such as a RFID reader.

[0268] In one embodiment, the reader is arranged on a mobile terminal such as mobile device, a smartphone, a tablet or any laptop computer being mobile.

[0269] In another embodiment, the reader is arranged in a predefined position such as to be well oriented when a tube T.sub.k is moving or is displacing in front of the camera.

[0270] FIG. 3 represents a first tube T.sub.1 having a marking on its surface. In that scheme, the first tube T.sub.1 is close to be introduced into the well W.sub.1. When the tube T.sub.1 is upright standing over the well W.sub.1, and takes a position, the camera 10 acquires the barcode TC.sub.1. In this configuration, the camera may be placed in a range of 3 to 5 meters taking account of resolution and optical performance of lens.

[0271] In one embodiment, the camera 10 might be used in conjunction with IR or waveband selected light. One advantage is to define a solution compatible of the marking type.

[0272] In one configuration, the camera 10 is orientated downward, ability to read during rotation of the tube T.sub.k.

[0273] In one embodiment, compatible presence centralizers, motion detector or any algorithm reinforcing the decoding of the tracking code may be used with the camera.

[0274] The barcode TC.sub.1 is then decoded by a computer 2 which is connected to the camera 10. It is supposed that the camera comprised a communication interface in order to transmit the image to a local computer. An operator 3 may access through a software program and an interface 4 to the decoded barcode. The tracking code TC may be used so as to define an appropriated request to the local database DB.sub.14, for instance by the way of the local server SERV.sub.14.

[0275] The tracking code TC is used to recover all information relative to said tube Tk. Some geometrical information, workflow data or junctional data may be acquired in real time.

[0276] On advantage is to generate some indicators or metrics of the whole extraction structure ST.sub.1 thanks to the exploitation of information of the current component T.sub.1 which is analyzed.

[0277] Tube Marking

[0278] Preferably, the marking is placed at the end of the tubular component. In one embodiment, a marking is placed at each tubular end. In one embodiment, a plurality of markings is realized at each tubular end. For instance, two different markings are separated from 0.2 m along the axis of the tube T.sub.k as it is represented in FIG. 3. In one example, the markings are also separated from different angles, 120° in the FIG. 3. In one embodiment, the marking is 0.3 meters long.

[0279] Inventory Status

[0280] A first indicator that could be controlled with a reader acquisition is an identifier of the tube T.sub.1. This first indicator allows checking an inventory status S.sub.0 of a component T.sub.k. The identifier may be the tracking code TC, or a unique identifier identifying said tube T.sub.1. It could be the serial number SN for instance.

[0281] The acquisition of the tracking code TC thanks to the reader allows concluding in the fact that the tube T.sub.1 has been previously be paired, for instance at stage 10 or 20.

[0282] This control allows generating a secure indicator S.sub.0 by controlling each component manipulated in the rig 40. It may ensure that a previous component T.sub.n that have been removed from the local database DB.sub.14, for instance because it was not exploitable (too much damages on the piece) is not reused by a wrong rerouting engaged by a human.

[0283] Moreover, the first indicator S.sub.0 may ensure controlling the operation of inserting a tube T.sub.1 into the well by checking that the marking is not defaulting, for instance, because of a muddy surface of the component T.sub.1 that does not allow fully clear vision of the marking.

[0284] Completion Status

[0285] In another embodiment, a second indicator may be controlled by a reader acquisition. The second indicator deals with a completion status S.sub.1. In one embodiment the completion status S.sub.1 is an indicator set into the tally list. The second indicator may ensure that the tube is completed, it means according different embodiment that the following action(s) have been completed: [0286] all necessary modifications are done on tube T.sub.1 and/or; [0287] the tube T.sub.1 is equipped with all necessary junctional elements and/or; [0288] a set of necessary checking and measurements have been done previously at previous stages by at least one operator.

[0289] In one embodiment, the completion status S.sub.1 is analyzed regarding the value(s) of at least one feature of at least one subset of the first set of data SET.sub.1.

[0290] In one example, the presence of connection type CT and the effective length EL are controlled. If their values are in a predefined scale, the completion status S1 is favorably checked.

[0291] In another example, the total length with connectors is the unique parameter controlled for validating the completion status.

[0292] In the example of FIG. 3, a second operator 3′ is controlling the tube T.sub.k by a visual checking. Some results from a visual checking, a measuring checking, electrical checking or any other controls may be recorded in the local database DB.sub.14. The results are recorded by transmitting a new value of a feature or a compliance information. The invention allows recording all information recorded in the database DB.sub.14 with a timestamp, for instance t.sub.4. In one example, the second operator 3′ measures an effective length of the tube T.sub.1 which will be inserted in the well W.sub.1. The measured value of the effective length of a tube by the operator 3′ is then recorded in the database DB14. The computer allows generating a timestamped recording in the local database DB.sub.14.

[0293] Planification Status

[0294] In another embodiment, a third indicator S.sub.2 is controlled by decoding the tracking code TC. The third indicator S.sub.2 is a planification status. The planification status ensure an operator that the component is associated with a job reference.

[0295] The planification status may be defined as a specific feature in the fourth subset of data. The value of this specific value is then compared to the job reference of a job datasheet. The job datasheet may be described by a second set of data SET2. In one embodiment, this second set of data may be recorded in a second local database DB.sub.24, for example in the site 40.

[0296] According to an embodiment, the results of the comparison generate a planification status.

[0297] Sequence Status

[0298] In another embodiment of the invention, a fourth indicator S.sub.3 is controlled by decoding the tracking code TC. The third indicator S.sub.3 is a sequence status. The sequence status S3 ensure to an operator that the introduction of the component T.sub.1 in the well W.sub.1 is well-ordered. If the number of component T.sub.1 in the sequence SEQ.sub.1 defined in the job Jb1 is 13, it means that the previous component that has been inserted in the well has the previous number in the sequence SEQ.sub.1 which is 12.

[0299] One advantage is to reduce human errors, especially handling errors of tubes before they have to be introduced in the well W.sub.1. Sometimes a junctional piece should be inserted, or a caging element should be inserted between two successive tubes of a main structure.

[0300] The invention allows reducing errors made by improper handling of a component which is not planned in the sequence SEQ.sub.1.

[0301] The control of the third indicator S.sub.3 may be realized automatically by recording the number of the last component T.sub.k which was carried out into the well W.sub.1. In one example, the comparison of two successive number in the sequence may generate a planification status that can be easily checked by an operator on the interface of a computer.

[0302] Length Status

[0303] According to another embodiment, a fourth indicator is generated by decoding the tracking code TC.

[0304] The acquisition of the length of the tube T.sub.1 may be used to compute a total current length of the extraction structure ST.sub.1 integrating the first tube T.sub.1. The acquisition may concern the total length or an effective length of a tube T.sub.1.

[0305] The method of the invention allows extracting automatically the total length of the tube T.sub.1 which is introduced and the current total length of the extraction structure ST.sub.1 being already inside the well. In one embodiment, the current total length of the extraction structure ST.sub.1 is recorded in a memory of the computer 2 or a memory of the local database DB.sub.14. According to one embodiment, the current total length of the extraction structure ST.sub.1 is updated at each new entry.

[0306] The length status of the whole structure allows ensuring a theoretical value that is calculated in the job datasheet. The values may be compared in order to generate a length status.

[0307] Mud Status

[0308] According to another embodiment, a fifth indicator is generated by decoding the tracking code TC.

[0309] The acquisition of the internal diameter ID.sub.1 of the tube T.sub.1, along with outside diameter OD.sub.1 or wall thickness WT.sub.1 may be used to compute a mud gain that could appear in the well after the introduction of said tube T.sub.1.

[0310] The acquisition may concern the internal diameter ID.sub.1 or the outside diameter OD.sub.1 considering the value of the wall thickness WT.sub.1.

[0311] The method of the invention allows extracting the mud gain value automatically from the internal diameter value ID.sub.1 of the tube T.sub.1 and the mud gain value previously calculated of the current structure which is already inside the well W.sub.1. The invention allows surveying component by component the mud gain value by considering the current component intended to be inserted in the well W1 and the rest of the structure being inside the well.

[0312] In one embodiment, the current mud gain is recorded at each introduction in the well W.sub.1 in a memory of the computer 2 or a memory of the local database DB.sub.14. According to one embodiment, the current mud gain value of the extraction structure ST.sub.1 is updated at each new entry.

[0313] The mud status may be generated by a comparison of an updating value being calculated at each iteration of the introduction of a new tube T.sub.1 in the well W.sub.1 and an expected value of mud gain that can be acquired from the job datasheet. This value is a theoretical value that could be calculated according to the well properties.

[0314] This allows detection of loss of apparent volume of mud in the well, and alert of possible crack in the well, or this either allows detection of gain of apparent volume of mud in the well.

[0315] Structure External Volume Status

[0316] According to another embodiment, a sixth indicator is generated by decoding the tracking code TC.

[0317] The acquisition of the outside diameter OD1 and effective length EL of the tube T.sub.1 may be used to compute a structure external volume that is to be introduced in the well.

[0318] The structure external volume corresponds to the volume occupied by the extraction structure, without taking in account the interior free space in the volume calculation.

[0319] The acquisition may concern the outside diameter OD1 or the internal diameter ID.sub.1 considering the value of the wall thickness WT.sub.1.

[0320] The method of the invention allows extracting the extraction structure volume lowered in the well W.sub.1 automatically from the outside diameter value OD.sub.1 or from wall thickness WT.sub.1 and internal diameter ID.sub.1, and effective length EL of the tube T.sub.1 and structure external volume value previously calculated of the current structure which is already inside the well W.sub.1. In one embodiment, the current structure volume is recorded at in a memory of the computer 2 or a memory of the local database DB.sub.14. According to one embodiment, the structure volume value is updated at each new entry.

[0321] Cement Status

[0322] According to another embodiment, a seventh indicator is generated by decoding the tracking code TC.

[0323] In a similar manner to structure external volume, the acquisition of the outside diameter OD1 of the tube T.sub.1 may be used to compute a cement volume that could be introduced in the well for reinforcing the structure ST.sub.1 that is built component by component.

[0324] The acquisition may concern the outside diameter OD1 or the internal diameter ID.sub.1 considering the value of the wall thickness WT.sub.1.

[0325] The method of the invention allows extracting the cement volume automatically to inject into the well W.sub.1 from the outside diameter value OD.sub.1 of the tube T.sub.1 and the cement volume value previously calculated of the current structure which is already inside the well W.sub.1. The invention allows surveying component by component the cement volume that should be introduced into the well by considering the current component intended to be inserted in the well W.sub.1.

[0326] In one embodiment, the current cement volume is recorded at in a memory of the computer 2 or a memory of the local database DB.sub.14. According to one embodiment, the cement volume value is updated at each new entry.

[0327] The cement status may be generated by a comparison between an updating value being calculated at each iteration of the introduction of a new tube T.sub.1 in the well W.sub.1 and an expected value of the cement volume that can be acquired from the job datasheet. This value is a theoretical value that could be calculated according to the well properties. This method allows a greater accuracy of the cement volume needed for the consolidation of the well structure.

[0328] In a variation, the cement volume is extracted from data about the well which are determined by the operator of the well, and from the structure external volume of the extraction structure.

[0329] FIG. 4 illustrates an embodiment of the method of the invention comprising three steps.

[0330] A first step comprises the definition and the transmission of a request REQ.sub.1 from a user computer such a mobile device or work station to a local database DB.sub.1i. In this step, the method gets an identification number of tube T.sub.1. The identification number may be acquired by a camera of may be manually entered via an interface.

[0331] After generating a request REQ1, the local server transmits at least a first of data SET.sub.1. In an embodiment, the local server transmits a second set of data SET.sub.2 comprising at least the job datasheet. This last configuration may appear in site 30 or 40 for example.

[0332] The method comprises a step of receiving/acquiring data allowing generating at least one indicator, such as those defined previously. The method is noted ACQ. Different data may be received according different embodiments of the invention. The acquisition step may be automatically generated after reading a tracking code for instance. The acquisition may result on a form of displaying area on the computer showing a part of data acquired. The acquisition may point out in preference data that are in relationship with a customized request REQ.sub.1.

[0333] A third step of the method comprises the generation of an alert, especially when the value of the indicator resulting from an operation of the received data is superior, inferior, equal or different from an expected value of a predefined range of values.

[0334] FIG. 5 shows an embodiment of the invention where a preliminary step of reading a tracking code is led. This step may be conduced at each stage, i.e. in each site, where a local database DB.sub.1i is present. This step is called READ_CODE.

[0335] FIG. 6 illustrates an embodiment where a step of updating a central database DB.sub.0 is led. This step is called UPD. The updating of data in a central database DB.sub.0 allows updating each local database BD1I with current features of each tube T.sub.k.

[0336] In one example modifications of a tube T.sub.1 in site 20 may be recorded in the local database DB.sub.12 and an update in the central database DB.sub.0 may be then completed. When the tube T.sub.1 arrives in site 30, the modified features of tube T.sub.1 may be recovered in the local database DB.sub.13 thanks to its synchronization with the central database DB.sub.0.

[0337] One advantage of this step is proposing a method keeping up to date the values of features, modifications, adaptations, reports and checking of each component in each site. That ensures reducing errors, controlling the well integration of an extraction structure ST1 and reducing time to achieve such structure.