System and software product for managing the life cycle of risers, and related methods

NO20200225A1Inactive Publication Date: 2010-11-08VETCO GRAY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
NO20200225
Authority / Receiving Office
NO · NO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2009-02-11
Filing Date
2020-02-21
Publication Date
2010-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Current systems lack effective methods for tracking and managing marine riser parts, particularly riser lengths, to predict maintenance needs, optimize deployment, and extend the life of riser sections by monitoring stress and load conditions, especially under vortex-induced vibrations.

Method used

A system comprising a central database and software product that tracks riser parts, provides load history data, and includes sensors and receivers to monitor and manage riser lengths, offering real-time monitoring and predictive maintenance, with integrated hardware and software components for remote diagnostics and maintenance history management.

Benefits of technology

Enables efficient planning and execution of maintenance, extends the life of riser parts by optimizing their deployment and tensioning, and reduces downtime by predicting and mitigating vortex-induced vibrations, thereby reducing operational costs.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

A system, a software product and a method for monitoring and managing multiple marine riser sections are provided.The system may include one or more floating vessels each having a computer on board, a plurality of riser sections to be tracked and monitored, a riser section identification sensor arranged to identify selected riser sections being deployed to form a riser string, one or more riser length instrument modules arranged along the length of the riser string to provide load data for riser sections, a centralized data warehouse for storing identification and load data for riser sections deployed at multiple remote vessel locations, and a riser lifecycle management server and software product arranged to monitor the condition of riser sections, send out automated operational alerts based on actual usage information, maintain routine and unscheduled maintenance information, manipulate and categorize riser sections, and automatically reconstruct an exact riser system as it was actually deployed for any given drilling / completion operation.
Need to check novelty before this filing date? Find Prior Art

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to systems for managing risers. More specifically, the present invention relates to a system, a program product and associated methods for monitoring and managing multiple marine riser parts. 2. Description of Related Art A problem encountered in offshore operations for drilling for and production of hydrocarbons carried out from floating platforms or vessels is the need to establish a sealed fluid flow path between each wellbore or each well on the seabed and the working deck of the vessel on the sea surface. This The sealed fluid flow path is typically provided by a system of drill risers. Drill risers, used for offshore drilling, run from the drilling rig to a blowout preventer (BOP). Similarly, production risers from and enables communication between a subsea wellhead system and the floating vessel. A typical marine drill riser allows the passage of drill pipe that used to pump lubricating mud down the well during drilling operations, return of drilling mud that has been pumped through the drill pipe into the main pipe in the riser, together with any accompanying drill chips, and provides a connection between the drilling vessel and the well above the underwater BOP stack. The drill riser can be disconnected from the well above the BOP stack, allowing the drilling vessel to pull up the riser and temporarily move away from the drilling site if necessary for this (e.g. during a hurricane or in the event of a malfunction). The BOP stack, which sits left on the wellhead, provides for the shut-in of a live well while the vessel is not in place. When it returns, the vessel can deploy the riser, connect to the BOP stack and restore hydrocarbon communication with the well. The marine drilling riser also enables control of the well if the BOP the stack must be triggered (functioned). This typically occurs in connection with drilling through a zone with a geological fluid pressure that is significantly higher than that the drilling mud can dam up. During such events, the blowout protection is triggered, and well control is restored by pumping a mud of appropriate density through the kill line and eventually circulate it back to the surface via The marine drilling riser also makes it possible to increase the sludge circulation rate. When needed, this is done by pumping additional mud through the booster line and feed it into the riser bore at BOP stack. This increases the volume of mud in the riser, which increases The marine drilling riser enables further supply of hydraulic fluid to the control system for the BOP stack. This fluid is supplied through an external hydraulic line. For example, the drill riser is typically installed directly from a derrick on the platform on the vessel by connecting a sequence of interconnected riser lengths. After the riser has been connected to the wellhead on the seabed, the the riser placed under tension by buoyancy elements or deck-mounted tensioning systems. The riser is led up, through an opening in the vessel, called a basement deck floor (“moon pool”), for operating equipment and connections near a working floor on the vessel. During drilling operations, the drill string is guided through a drill riser, the drill riser serving to protect the drill string and to provide a return flow path outside the drill string for drilling fluids. Similarly, during production operations, a production riser is used for to provide a flow path for transporting oil and gas to the working deck. Basic components of a riser system typically include, from the mud line and up to the surface: a hydraulic wellhead connector that enables connection to a subsea wellhead, a BOP stack used for well control, a lower marine riser package that enables disconnection and connection of the marine riser at the BOP stack, several lengths of marine risers normally in the form of bare and floating lengths of pipe each equipped with a choke and kill line, a booster line and a hydraulic line, and a end pipe length which is a specialized riser length where external wiring is terminated and routed to the appropriate units on the vessel. For example, the kill line terminated and connected to the sludge pump via a flexible high-pressure line. The components also include a tension ring that provides the interface between the marine riser and the hydro-pneumatic the riser tensioning device arranged to provide resistance to lateral loads while providing a constant vertical tension, and a telescopic joint that typically formed by two sliding tubes sealed to each other using an elastomer which is primarily used to compensate for the movement of the vessel while also it enables the riser tensioning system to apply a near constant tension in the marine riser. The components also include a diverter that used to divert unwanted gas in the marine riser, a wobbler mounted on the rig floor used during lowering and retrieving of the marine the riser to dampen the pitching motion of the vessel, and a work table (spider) for marine drilling risers used during connection of each riser section to the next one. Other more specialized riser equipment includes a fill valve designed to prevent collapse of the riser due to the pressure difference between inside the riser and the surrounding water, an instrumented riser length that typically used to monitor the stretch and bend resulting from environmental impacts, and which enables adjustment of top tension and vessel positioning, vortex suppression equipment that helps suppress vortex-induced vibrations which typically occurs under conditions of high current and long risers, and a emergency disconnect for the riser that provides a specialized riser disconnection system to prevent catastrophic failure that typically occurs during conditions where incorrect vessel positioning or extreme environmental conditions may occur. During a typical field installation, the marine riser components are individually lifted from the deck, connected to each other at the work table and driven down. Riser lengths, which constitute the majority of the riser string length, are manufactured in lengths ranging from 15 meters (50 feet) to 27.5 meters (90 feet). Under the driving process, the part of the riser string that has been fully assembled will be landed on The next length of riser is then picked up and placed over the the workbench, directly above the suspended riser string. The two riser sections are then assembled using a mechanical coupling, etc. The most common type for a riser length has a bolted flange design. Marine risers are subjected to shock loads as well as unexpected lateral loads, such as will damage sensitive electronics. Marine risers are also exposed to environmental loads as well as vessel-generated loads. The relevant The environmental parameters include, among other things, wave height and period, water depth, currents, winds and tides. In the underwater environment, hydrostatic pressure can up to 310 bar (4500 psi) in deepwater areas, and will likely reach 380 bar (5500 psi) within a few years, and the seawater temperature can be as low as as -1.1°C (30°F). The high temperature of the drilling mud could also affect electronic equipment and sensing equipment, especially electronic equipment attached directly to the body of the riser (rise length). The vessel-generated loads include the applied top tension necessary to maintain the optimal shape of a riser string and those transferred to the marine riser string as a result of movement of the vessel when exposed to wave, wind and current loads. The most The critical environmental load component is generally the current load that is applied directly on the riser string. The current loads tend to vary with the water depth, but are in generally much greater near the surface. Some places around the world, such as the west coast of the Shetland Islands and The Gulf of Mexico presents unique challenges due to strong currents. In The Gulf of Mexico, for example, creates an environmental event called a seasonal coastal current. ("Loop Current") that moves in a circular pattern reaching a diameter of one hundred and sixty kilometers or more. Such coastal currents inflict extremely large ambient loads on a riser, often for weeks at a time. Large current loads can lead to to vortex shedding around a marine riser string, which, if it occurs in combination with an unfavorable riser attenuation, can result in a violent movement of a marine riser string, typically across the direction of flow. This is usually referred to as "vortex induced vibration" or "VIV – Vortex Induced Vibration". The large variation in the riser movement during VIV can lead to high tension levels in the riser string, which in turn dramatically reduces the service life of the individual riser lengths before fatigue. A single fatigue will could result in catastrophic failure of the marine riser string. Worse still, However, VIV can occur in higher modes, for example where only a small part of the riser string, possibly a hundred meters or more below the sea surface, is excited and subjected to VIV. The applicant of the invention realizes that in such a scenario, not an observer on the vessel, looking down at the visible parts of riser string, see any signs of this vibration. Fortunately, there have been few cases of catastrophic riser failure, and they have been far apart. A goal or set of goals for both drilling and production risers is to control stresses and loads on individual riser sections to enable fatigue analysis and thus enable the operator to set up a better plan for inspection, maintenance and replacement / rearrangement of riser lengths. If a single riser length in a riser string fails or is otherwise exceeds an operating limit that triggers a requirement for immediate maintenance, the an entire riser string could have to be pulled up and run down again. Deep water operations can take two or more days to run down or pull up a marine riser. Given the approximate rate of well over $500,000 per day for a fifth-generation drilling vessel, such a scenario would cost the operator over a million dollars just to establish communication with the underwater well. This The point illustrates the importance of saving time during drop-off and pick-up. the riser. It also illustrates the importance of lost time, and the accompanying the cost, resulting from the failure of a riser component. To date, it has However, there were no effective systems or procedures for effective tracking riser sections, efficient tracking of cumulative voltage or other load on each riser section or precise determination or differentiation of expected voltage levels between vessels or fields in order to correctly predict necessary maintenance. The applicant has therefore seen the need for a system, a software product and procedures for managing riser sections, especially riser lengths, which can provide equipment managers a list of all riser sections allocated to each vessel and enable a further division into the riser sections currently deployed, is on deck or is out for maintenance, along with the expected return time, a list of upcoming, planned maintenance events, an estimate of how much of the service life of a given riser section has been used up, and an estimate of the total cumulative service life used up by a given riser section, together with details of the most devastating events (e.g. a specific hurricane). Furthermore the need for a system, a software product and methods for managing riser parts, especially riser lengths, which includes a central database that can be used by field and maintenance personnel to maintain and communicate critical information regarding riser parts, which can improve both the planning of routine maintenance and the process of identifying a requirements for an unforeseen maintenance event. Furthermore, the need for such systems, software products and methods that can provide detailed information about riser maintenance history and critical / relevant production information as well as enabling correct tracking of riser parts so that they can be moved from one vessel to another with its history preserved. Furthermore, the need for such systems, software products and methods that can provide a timestamp for each riser deployment to make it possible to determine where, in the water column, each riser section was installed during a given drilling or production campaign, which in turn can provide the user with information that makes it possible to reconstruct a riser string from any any given deployment for analyzing the riser section performance and preferred location. Furthermore, the need for a system, a software product and methods that can allow a user to optimally position a given riser length at a specific position (depth) along the riser string, for example based on how much life is available (remaining), for example to match riser lengths with a lot of remaining life with the depths along the riser string that is expected to experience the highest stress. Even further, the need for a system, a software product and procedures for managing riser sections, especially riser lengths, such as includes means for controlling a riser tensioning system to extend the life of the various riser parts and to control riser performance, for example when exposed to vortex-induced vibration. SUMMARY OF THE INVENTION In light of the above, embodiments of the present invention provide invention provides a system, a program product and methods for managing riser parts, especially riser lengths, which can provide equipment managers with a list of all the riser sections allocated to each vessel and enable a further division into riser sections that are currently deployed, on deck, or out for maintenance, along with the expected return time, a list of upcoming, planned maintenance, an estimate of how much of the life of a given riser section is is used up, and an estimate of the total amount of life used by a given riser section, along with details of the most damaging events (e.g. a particular hurricane). Embodiments of the present invention provide also a system, a software product and methods for managing riser parts, especially riser lengths, which includes a central database that can be used by field and maintenance personnel to maintain and communicate critical riser information, which can improve both the planning of routine maintenance incidents and identify a requirement for an unforeseen maintenance incident. Embodiments of the present invention also provide a system, a program product and methods that can provide detailed information about maintenance history for riser parts and critical / relevant production information, and which can provide functionality for appropriate tracking of riser sections so that they can be moved from one vessel to another with their history preserved. Embodiments of the present invention also provide a system, a program product and methods that can provide a timestamp for each deployment of a riser section to enable determine where, in the water column, each riser section was installed during a given drilling campaign, which in turn can provide the user with information that makes it possible to reconstruct a riser string from any given deployment for with analyzing the performance and preferred positioning of the riser sections. Embodiments of the present invention also provide a system, a software product and methods that can allow a user to optimally place a given riser length at a specific position (depth) along the riser string, for example, based on how much life is available (remaining), for example to match riser lengths with long remaining life with deep along the riser string that is expected to be exposed to higher voltage. Embodiments of the present invention also provide a system, a software product and methods for managing riser parts, especially riser lengths, which include devices to control a riser tensioning system to extend the life of the various the riser sections and to control the riser performance, for example when it occurs vortex-generated vibration. More specifically, embodiments of the present invention provide a riser lifecycle management system to monitor and manage multiple marine riser sections that can be placed on one or more separate floating vessels such as each generally has a floor, a well bay that goes through this, a local communications network on board the vessel as well as a computer on the vessel that is in communication with the local the vessel communication network and which includes a processor and memory connected to the processor to store driving instructions. The system, according to an embodiment of the the present invention, the vessel includes a riser length identification sensor located in or near the wellhead and operatively connected to the vessel communication network, and several lengths of riser pipe carrying a identification tag, which can be deployed from the vessel to form a The system can also include multiple riser lengths. measuring instrument modules each positioned to sense the load applied on a single one of the multiple deployed riser lengths, and a riser length- cargo data receiver connected to the vessel at or near the sea surface (i.e. arranged in the wellhead or connected to a length of riser near the surface) and operationally connected to the local communications network on the vessel to receive direct or multiplexed load data for each of the multiple deployed the riser lengths from the multiple riser length measuring instrument modules. The riser length load data receiver and each of the multiple riser length the measuring instrument modules establish a communication path through a water column around the riser string. The system also includes a software product for managing riser parts. stored in the memory of the vessel's computer to monitor and manage multiple riser parts. The riser parts management software product may include instructions that, when executed by the computer on the vessel, cause the computer on the vessel to perform various operations including receiving riser length identification data from the riser length identification sensor for each single of the multiple riser lengths during deployment from the vessel to form the riser string, and determine a relative deployment position for each of the the multiple deployed riser lengths within the riser string. The program product for the management of riser sections may further include instructions that when they are executed by the computer on the vessel, causes the computer on the vessel to perform operations to receive the load data for each of the multiple deployed the riser lengths from the riser length data receiver, monitor the load on each of the multiple deployed riser lengths based on the load data provided by the multiple riser length measuring instrument modules, estimate a load condition for each of the multiple deployed riser lengths based on the load data for one or more of the multiple deployed riser lengths, and give an alarm in response to the estimated load condition approaching a design load or an upper operating limit. The system may also include at least one computer for remotely managing riser lengths for multiple separate vessel locations defining a server for life cycle management of risers with a processor and memory connected to the processor for to store driving instructions, a global communications network that provides a communication path between the computer on the vessel and the riser lifecycle management server to enable the transfer of information regarding riser parts between the computer on the vessel and the riser lifecycle management server, and a software product for managing riser lifecycle stored in memory in the riser lifecycle management server to manage several riser sections located at several separate vessel locations. The Riser Lifecycle Management software product may include instructions that when they are executed by the riser lifecycle management server, causes the riser lifecycle management server to perform operations to receive deployment and position data for the multiple deployed riser lengths, receive load history data for the multiple deployed riser lengths from the computer on the vessel, transform cargo history data received in the time domain from the computer on the vessel to load history data in the frequency domain, and send load history data in frequency domain of the computer on the vessel. The instructions may also include instructions for performing operations to determine the fatigue of each of the the multiple deployed riser lengths based on the received riser length- the load history data, estimate the remaining service life before fatigue based on the the received riser length load history data and the riser lengths material properties, schedule routine maintenance events for each single of the multiple deployed riser lengths, and plan for unforeseen maintenance events in response to an irregularity in the riser length the load history data resulting in the triggering of a preset fatigue trigger level requiring inspection. The instructions may further include instructions for performing operations to reconstruct a riser string with a any of the multiple riser lengths deployed on any of the the multiple separate vessel locations based on deployment and position data for the current riser string, and predict the magnitude of a load applied to a subsea wellhead system associated with the relevant riser string based on associated riser load history data for at least a subset of several riser lengths that form the relevant riser string. The system may further include a data warehouse that can be accessed by the processor in the riser lifecycle management server and which includes at least one database that stores equipment information, such as identification data, deployment and position data and load history data for the multiple riser lengths deployed at the several separate vessel locations, and at least one database that can accessed by the processor in a computer on the vessel and which stores equipment information, such as identification data, deployment and position data and load history data for each of the multiple riser lengths deployed from a respective vessel. Embodiments of the present invention may also include a computer program product, stored on a tangible data storage medium, which can be run on a computer to manage multiple marine riser sections that can be placed at one or more separate vessel locations. The computer program product may include instructions represented, for example, by the following computer program components: a deployment and positioning tracks for riser sections adapted to receive underwater deployment and relative positioning data for multiple riser lengths which will be deployed to form a marine riser string, a riser section- load sensor data receiver arranged to receive load data for each of the plurality of the riser lengths when deployed and forming the marine riser string, and a riser section fatigue tester arranged to estimate the condition of each of the multiple riser lengths based on the received riser length load data and / or riser voltage data determined from the received riser length load data for each of the several riser lengths. Embodiments of the present invention also provide various procedures related to monitoring and management of several marine riser sections. According to an embodiment of the present invention, a method of monitoring and management of multiple marine riser sections including steps to receive riser length identification data from a riser length identification sensor arranged inside a manhole, and determine a relative deployment position for each of several lengths of riser pipe deployed from the vessel to form a marine riser string. Each of the riser lengths includes associated characteristics that can is read by a riser length identification sensor to individually recognize each single of the multiple riser lengths among the multiple riser lengths. The method may also include receiving load data for each of the multiple riser lengths from multiple riser length measuring instrument modules each may be connected to an associated one of the multiple deployed riser lengths, and monitor the load on each of the multiple deployed riser lengths based on the load data provided by the multiple riser length- the measuring instrument modules. According to another embodiment of the present invention, a procedure for monitoring and managing multiple marine riser sections steps to determine a relative deployment position for each of several riser lengths deployed from a vessel and having characteristics that can is read by a riser length identification sensor to individually distinguish each one of the multiple riser lengths from the other of the multiple riser lengths below deployment of this, receive load data for each of the several deployed the riser lengths from multiple riser length measuring instrument modules connected in each drop a subset of the multiple deployed riser lengths, monitor the load on each of the multiple deployed riser lengths based on the load data provided by the multiple riser length measuring instrument modules, estimate the load condition for each of the multiple deployed riser lengths based on the load data for one or more of the multiple deployed riser lengths, and give an alarm in response to the estimated load condition approaching a design load or an upper operating limit for one or more of the several deployed riser lengths. According to another embodiment of the present invention, a method for monitoring and managing several marine riser sections such as located at one or more separate vessel locations include steps to receive deployment and position data for each of several deployed riser lengths deployed at one of several separate vessel locations that have the respective the riser length, receive load history data for each of the multiple riser lengths deployed at the multiple separate vessel locations from a computer on the vessel, transform load history data for riser lengths received in the time domain into load history data in the frequency domain, and determine the level of damage to each individual of the multiple deployed riser lengths based on at least one of the following: the the received riser length load history data or the transformed riser length the load history data. BRIEF DESCRIPTION OF THE DRAWINGS In order that the above-mentioned features and advantages of the invention, as well as as other features and advantages that will emerge in the following should be understood better, a more detailed description of the invention as briefly summarized above is given with reference to the embodiments thereof illustrated in the attached the drawings, which form part of this description. It should be noted, however, that The drawings only illustrate selected embodiments of the invention and therefore do not should be understood as a limitation of the scope of the invention, as it can also include other applicable embodiments. Figure 1 is a sketch of the environment for a monitoring and management system of several marine riser parts according to an embodiment of the present invention, Figures 2A-B are a sketch of the environment for part of the system for monitoring and management of multiple marine riser sections according to an embodiment of the present invention, Figure 3 is a perspective view of a riser length leading communication and identification equipment according to an embodiment of the present invention invention, Figure 4 is a schematic block diagram of a measuring instrument module for riser lengths according to an embodiment of the present invention, Figure 5 is a combination of a perspective sketch and a schematic block diagram of a clamping system according to an embodiment of the present invention invention, Figure 6 is a schematic block diagram of a software product for riser lifecycle management stored in memory in a riser lifecycle management server according to an embodiment of the present invention, and Figure 7 is a schematic block diagram of a software product for management of riser parts stored in the memory of a computer on a vessel according to a embodiment of the present invention. DETAILED DESCRIPTION The present invention will now be described in more detail in the following. with reference to the accompanying drawings, which illustrate embodiments of invention. This invention may, however, be embodied in many other forms and should not be construed as being limited to the embodiments illustrated herein. Rather are these embodiments shown for the purpose of this description to be consistently and completely, and fully convey the scope of the invention to the professional. Figures 1-7 illustrate an embodiment of a life cycle monitoring system for risers (RLMS – Riser Lifecycle Monitoring System) which provides a integrated tool designed to improve the life cycle performance of a marine riser by using remote diagnostics, online device management and easy access maintenance history for riser parts, and to enable remote management of riser parts, with particular focus on riser lengths. The life cycle management system for risers include integrated hardware and software / program product components that can be combined into a central database that is preferably located on land. This database can store equipment information about all risers worldwide that are equipped with the lifecycle management system. It can also enable the transfer of riser parts from one vessel to another while maintaining all historical data. The computers on The vessels can in turn retrieve the data from sensors placed, for example, on each riser section. Such riser placement information can be communicated between the sensors on the riser sections and the computer on board the ship using a simple radio frequency identification or "RFID" tag or other identifying characteristics of the riser section and a suitable receiver on a part of the vessel, so such as the drill riser workbench. When a riser length or a other riser section is extended or pulled up, the receiver will, for example, the riser workbench, reading the unique riser part identification label stored on the RFID tag and communicate this information to the computer on the vessel along with a time stamp. The riser lifecycle management system ensures useful for collecting load history data from risers. This data collection can include acquiring sensor data, multiplexing this data, and communicating it through the water column up to a vessel, while maintaining an acceptable level of fault tolerance is enabled. The data collected depends on the type of sensor which are used on the riser section. For example, if only accelerometers are used applied to the riser length, a representation of the riser accelerations will be available in real time. Further processing either by the computer on the vessel or the land-based computer can be made to calculate, for example, the information into a real-time representation of the stresses in the riser. Alternatively, if, for example, the strain or curvature of the riser length is measured on a riser length, the voltage data for the riser length can be calculated through a relatively simple processing of the data. The riser voltages, as a function of time, can then be further processed to estimate the state of riser length from a service life perspective. Such data provided by embodiments of the system may also enable planned and unplanned maintenance and management of an associated riser tensioning system. More specifically, Figures 1-2B illustrate several offshore drilling and / or production systems 21 and a riser lifecycle management system 30 to remotely managed marine riser sections located on one or more separate vessel / drilling / production system locations, according to an embodiment of the present invention invention. The drilling and / or production system 21 may include a deployed riser or channel defining a riser string 23 extending between a subsea wellhead system 25, such as the illustrated the subsea wellhead, and a floating vessel 27, such as a dynamic positionable vessel. The riser string 23 comprises several riser sections or lengths 29 that are connected together, for example by a bolt flange or other methods known to those skilled in the art. The vessel 27 includes a manhole 31 which through a floor of the vessel 27, and typically comprises a work table 32 arranged on an operating platform 33 in a wellhead 31 to support the riser string 23 when connections between riser lengths are assembled or disassembled during driving or retrieving the riser string 23. Note that although embodiments of the present invention can be used with both drilling and production riser, the drilling riser is chosen here for illustrative reasons as some additional components are required, such as the lower marine the riser package and blowout preventer shown within the underwater the wellhead system 25, which are generally not necessary for a production riser. The vessel 27 also includes a tensioning system 35, 35' arranged on the operating platform 33 which provides both resistance to lateral loads and vertical tension, preferably applied to a tensioning or tensioning ring 37 attached to the top of the riser string 23. The tensioning system 35, 35' comprises a riser tensioning control unit 39 (figure 5) provided to control the tension in the riser string 23 when it is finally deployed. The vessel 27 also includes a computer 41 on board communication with a local communication network 43 on board, e.g. a LAN. The computer 41 on the vessel may include a processor 45 and memory 47 connected to the processor 45. In communication with the communication network 43 on the vessel There is also a receiver / transmitter 44 which enables, for example, satellite-based communication to locations on land. At least one database 49 available for the processor 45 in the computer 41 on the vessel, which can be used to store equipment information for each of the multiple riser lengths deployed from vessel 27, may also be provided. Which will be described in more detail below such equipment information may include identification data, deployment and position data and load history data for each of the multiple riser lengths deployed from the vessel on 27. According to an embodiment of the present invention, the the life cycle management system 30 for riser shares on land and shares on each of The portion of the system 30 that is located on land or one or several other centralized locations may include at least one computer to remotely manage riser sections for several separate vessel locations, defining a riser lifecycle management server 51 that is in communication with a land-based local communication network 53. The riser lifecycle management server 51 can include a processor 55 and memory 57 coupled to the processor 55. In communication with the land-based communication network 53 also stands a receiver / transmitter 54 which enables, for example, satellite-based communication with multiple vessels / drilling / production installations each having a receiver / transmitter 44. This part of the system 30 may also include a global communications network. 61 which provides a communication path between the computers 41 on board on each respective vessel 27 and the riser lifecycle management server 51 to enable the transfer of information about riser parts between the computers on the vessels 41 and the riser lifecycle management server 51. Note that the memory 45, 55 may include volatile and non-volatile memory known for skilled person, including, for example, RAM, ROM and magnetic or optical plate bearings, just to name a few. It must also be understood that the preferred the implementation with the server on land and computers on board vessels is given as a example in Figures 1 and 2A-B, and that other types of servers or computers arranged according to various other methods known to those skilled in the art can In particular, the server 51, shown schematically for example in Figure 5, represents 1, a server or a cluster or group of servers and is not limited to one single, physical server. The server may be deployed as a server group or server cluster operated by a server provider. The number of servers and their architecture and execution can be expanded based on usage, demand and capacity requirements for the system 30. At the heart of this part of the system 30 is a data warehouse 63 which is capable of to store relevant data about each individual riser section equipped with a lifecycle management system anywhere in the world. Data Warehouse 63 can accessed by the processor 55 in the riser lifecycle management server 51 and can be implemented in hardware, software or a combination thereof. The data warehouse 63 may include at least one centralized database 65 arranged to store equipment information for multiple riser lengths 29 and other riser parts of interest deployed at several separate vessel locations. The equipment information can for example include part number, serial number, relevant manufacturing information, operating procedures, and all maintenance information (including detailed information about the nature of the maintenance), just to name a few. This information will be in generality entered into the system 30 during manufacture or maintenance. The database 65 can also maintain deployment and load history information, which is collected automatically from computers 41 on board each vessel 27 equipped with riser lifecycle management system. The computers 41 on the vessels can in turn extract the data from one or more identification devices 71 (see e.g. Figure 3) preferably located on each riser length 29 or other riser parts or other equipment to be tracked. According to an embodiment of the present invention, the identification and the deployment data for each riser length 29 (or other applicable riser sections) communicated, for example, to the computer 41 on the vessel by means of a label such as, for example, an RFID chip or label 71 (see e.g. Figure 3) arranged on each riser length 29, and a suitable riser length identification sensor or - receiver 73 which is arranged for example in or near the wellhead 31, preferably on the worktable 32, if one is used, and which is operatively connected to or otherwise in communication with the computer 41 on the vessel through the local communication network 43 on board the vessel. When a riser length 29, for example, is driven down or picked up reads the sensor / receiver 73 on the worktable 32 of the unique riser section identifier stored on the RFID tag 71, and it communicates this information to the computer 41 on the vessel together with a time stamp. The computer 41 on the vessel then compares identification data with the list of recently registered labels. If a duplicate riser section is reported, it is ignored. Specifically, when using automated reader sensors, the same the riser section could be scanned multiple times while being landed on the worktable 32 or during normal handling. Consequently, they can be preferred the handling procedures include discarding duplicate information or duplicate readings within a pre-selected time period. Note that even though RFID tags 71 provide certain advantages, other acceptable identification devices may include devices such as touch buttons, barcodes or other readable memory devices. Communication of load history data for each deployed riser length 29 (or other riser parts of interest) is far more complicated. Which will be described in more detail below, communication of load data for each riser length 29 require sensing and multiplexing of load data through the water column, while allowing an acceptable level of error tolerance. Various computer program components associated with the land-based database 65 and / or the computer 41 on the vessel then uses the load history for the riser to monitor the condition of the marine riser sections, and make appropriate recommendations regarding the timing and nature of the next maintenance event. As indicated above, in one embodiment of the present invention database 65 (and / or database 49) for example include three basic categories of data: data entered by an operator, data collected automatically from a sensor or computer on the vessel and final data derived directly from a computer program component from processing stored information. Basics fields in the database 65 and / or 49, according to an embodiment of the present invention invention, is described below in connection with database 65. In terms of entered data, the database 65 for each riser section can include a serial number, part number, and revision information, manufacturing information, maintenance information and operational service procedures. The serial number is the unique serial number of the particular riser section. The part number and revision information provide documentation of a riser part has been examined / renewed during its normal service life. The manufacturing information may include critical information typically needed during routine maintenance or condition monitoring. For example, material properties and welding types used in manufacturing are used to determine fatigue life as the riser section is subjected to loads. Conversely, certain manufacturing defects, and their nature, together with any details of examination / renewal dates, be of great use during routine maintenance procedures where repair may be necessary. The maintenance information includes a number of records that are documented under routine or unforeseen maintenance of the riser section. The structure of maintenance information ideally includes references to the cause of the maintenance, where and when the work was performed and who performed the work, and any special instructions for future maintenance. The service procedures provide documentation of the manufacturer's recommended operating procedures. The operating procedures are preferably stored in a separate location and linked to the part number in a way that is not viewed by the user, to facilitate the implementation of updates for the manufacturer. In the case of automatically collected data, the database can 65 for each riser section includes deployment information and one or more load history tables, together with a log for the tensioning device and / or other vessel-related data. The deployment information may include data identifying where and when the relevant riser section was used. As such, deployment information will refer to a given field, the timestamp of when the riser was run out and the timestamp for when it was pulled up. Other useful deployment information, such as the position of the riser section in relation to the waterline, can also be stored or determined automatically based on the deployment sequence and length of each riser length 29. According to an embodiment of the present invention, the deployment information sent to the database 65 via an RFID tag, which is incorporated into the riser section at a given location. Which will be described in more detail below movement of the RFID tag 71 past an RFID reader / sensor 73, positioned for example on the riser workbench 32, trigger the RFID tag 71 to send a signal to the sensor / receiver 73. The load history tables can provide a complete picture of the load applied to the riser section. The load history tables can include the history in the time domain and in The load history tables given in the time domain can provide real-time riser load for a user-defined time period (e.g. 3 months). Load history data older than the defined time period, or alternatively a However, the combination of such older data together with newer data can and will be preferably taken care of in the frequency domain, which spans all available riser load history. It is noted that the riser load history in the time domain becomes used to calculate riser loads in the frequency domain. In addition, the information can be in the time domain can be used to extract extremely large riser loads and the the current event they are associated with, and can be used for internal validation of the results derived from the frequency domain data. The measured time domain data may depend on the type of sensor used on the riser section. For example, if only accelerometers are used on a riser length 29 to identify the load on individual riser lengths, will A real-time image of the riser accelerations is then provided. Further processing can then be used to convert the information into a real-time representation of the riser stresses. For example, a model database can (not shown) be used to model the loads applied to each deployed riser length 29 based on the mapping of the accelerations in the riser, and / or specific curvature and / or direction of one or more of the deployed riser lengths 29. Alternatively, if strain of riser length 29 is measured, either directly or indirectly, the voltage data for the riser length can be calculated through a relatively simple processing of the strain data in combination with the prior knowledge of one or more riser section parameters, such as "stress amplification factor" (SAF - Stress Amplification Factor) in relation to the position of the load sensor (measuring instrument) on the riser. Regardless of the type of measuring instrument sensor or module arranged on the riser length 29 or another riser section, the structure of the database 65 can provide sufficient flexibility for future replacement and upgrade of the measuring instrument sensor or -module equipment to another type. Note that a distinction is made between time-domain and frequency-domain data. Dynamic data is generally represented in the time domain. For example is a graph that shows the height (amplitude) of a wave as a function of time over two years a simple time history of the wave represented in the time domain. This the information can also be represented in the frequency domain, generally in a in a far more compact way, but at the cost of some loss of detail. For example, in the example described above, instead of tracking the height of the wave as function of time, one can create a table with a hundred rows, each of which represents a range of wave heights (or more preferably the RMS value of wave heights) and also a period and a probability for each combination of wave height and wave period. The more rows in the table, the finer the range of wave heights, and thus better resolution. As can be expected, two years of wave height data, if represented in the time domain with a sampling rate at once a second, result in over 60 million data records, while the same the information represented in the frequency domain will result in a table with as little like a hundred data records. However, the frequency domain table will generally lose the information about transients between waves. Furthermore, the implementation of numerical operations on data sets represented in the frequency domain usually significantly more efficient, but at the cost of losing clarity during transients (in this case between two waves) and that one often has to spot check with analytical results from time domain data to ensure accuracy. Analyses in However, the frequency domain is accurate enough and satisfactory in most cases, and especially for evaluating fatigue according to an embodiment of the present invention invention. The clamping device log can enable the storage of various parameters, such as tension setting, applied tension and the travel of the the clamping device, which can be used alone or in combination with load history data for riser lengths to determine different settings necessary to adjust the load on riser lengths and to formulate control signals to make adjustments in real time, as described in more detail below. In terms of calculated data, the database 65 for each riser section can include a tensile reinforcement factor (SAF) table, the load history table in the frequency domain, a matrix of maximum amplitudes and estimated residuals fatigue life. The SAF table for the riser sections can be a compact table which lists the critical locations (positions) on the riser section where fatigue calculations should be carried out, for example on the coupling flanges. SAF- The table can also contain the actual SAF value for each respective location, together with SAF reference information (e.g. nominal outside pipe diameter and wall thickness). The frequency domain based load history table, as stated earlier, can provide operator a comprehensive depiction of the loads applied to each specific riser length 29 and ultimately the loads applied to the entire riser string 23. The frequency domain-based load history table can, for example, be used for to evaluate the total fatigue damage of the riser section. This information can be calculated through transformation of a large volume of time-domain-based riser load history into a relatively compact table in the frequency domain. A component of a computer program product can perform the transformation and can update the table regularly (e.g. once a day, or in response to a query, etc.). Regardless of the type of data collected by the load cell sensors / modules (e.g. accelerations, strain, curvature, etc.) of the riser section, the frequency domain table can be processed so that it only contains certain quantities that are of special interest (e.g. strains or stresses). In other words, two transformations can be performed simultaneously to generate the final table in the frequency domain, data conversion (calculation or modeling) to generate a quantity of interest and a data transformation from the time domain to the frequency domain. The matrix of maximum amplitudes can provide maximum amplitude values ​​for one or more parameters of interest. As the volume of data stored is relatively small, the maximum amplitude numbers can be stored for each riser section for each drilling / completion operation, with a reference to the name of the field and also on the well. The riser lifecycle management system 30 also includes various components on the vessel and on the riser. For example, the computer 41 on the vessel, together with the communication network 43 on the vessel, the database 49, The RFID tags 71 and the riser length identification sensor or receiver 73, already been identified. Furthermore, the system 30 may also include riser length- measuring instrument modules 91 each positioned to sense a load, represented by strain, riser curvature or accelerometer data, etc., applied to a single one of the riser lengths 29 forming the riser string 23, a riser length load data receiver 93 arranged on or otherwise connected to vessel 27 at or near the sea surface and operationally connected to the local the communication network 43 on the vessel to receive cargo data for each of the deployed the riser lengths 29 from the riser length measuring instrument modules 91, and an underground communication medium 95 illustrated as provided by a sequence of ROV-replaceable, wireless data telemetry stations that provide a communication path between each of the measuring instrument modules 91 and the load data receivers 93 through a water column in connection with the riser string 23. As shown in Figures 3 and 4, each instrument module 91 (e.g. data telemetry station) comprise a processor 101 in communication with at least one sensor element 103, cache memory 105 for storing collected load data, a power source 107, preferably comprising a battery or other energy storage device, and a data transmitter / multiplexer 109 to supply both collected and received load data to the riser length load data receiver 93, either directly or via one or more of the other instrument modules 91. A more detailed description follows below, including a description of other embodiments: The measuring instrument modules 91 can determine the magnitude of the loads applied to riser string 23 to calculate the voltage values ​​at different locations on riser length 29 or another riser section. There are a number of different methods that can be used to measure the stresses in the riser. A preferred alternative is a method that reads the strains in the riser at sensor 103, since Converting strain data to stresses is relatively simple and can be done by using a relatively simple computer program component. Alternatively, the riser can dynamics can be determined using accelerometers, which may require a more complicated set of operations for conversion to material stress, from which it the functional life (e.g. before fatigue) can then be calculated. Other measurement alternatives are, however, within the scope of the present invention. In any case measurement method, the load data sent to the riser lifecycle management server can 51 either be in the form of raw data or be converted to local voltages of the computer 41 on the vessel, or be in a temporary form if any of the the processing is performed by the instrument modules 91. In one embodiment of the present invention, the sensor 103 is carried by a thin sandwiched composite mat (not shown) that can be used for precise determination of the deflection of the riser length 29. In such an embodiment, the mat is preferably about 91 cm (3 feet) long and covering about 170 degrees of the periphery to the riser length 29. Each mat contains optical fibers connected to an electronic sensor 103 which is tuned to measure the wavelength of the light in the fibers. Since the stiffness of the composite mat is significantly less than that of the material forming riser length 29, the mat assumes the same curvature as the the riser length 29 it is connected to, thus changing the length of the fiber optic the wires incorporated into the mat and the measured wavelength. As stated above, various other ways of positioning or carrying the sensor 103 known to those skilled in the art within the scope of the present invention. In a preferred embodiment, the instrument readings are made by each measuring instrument module 91 sent from one riser length 29 or another riser section to the next, multiplexed with the current instrument readings and sent further until they reach receiver 93 on the vessel. This receiver 93 sends in turn the entire data stream to the computer 41 on the vessel for processing and communication back to the riser lifecycle management server 51 and the database 65 on land. Although data multiplexing is a well-understood concept, it creates communication through the water column presents certain challenges. Different options for data telemetry are cable-based, acoustic, electromagnetic and laser-based telemetry. Wired transmission media are probably the easiest method for communication of a large amount of data. The cable-based option has However, there are some important disadvantages. Among other things, a damaged wire, especially near the top of the riser string 23, could lead to total loss of data from a significant majority of the riser lengths 29 or other riser sections. In addition, a cable-based alternative typically requires watertight penetrations at every riser length 29. At During the deployment and collection of the riser string 23, these penetrations are postponed for a risky environment with regard to "mistreatment" and contaminants, which are always present during riser operations. The cable-based alternative may be more practical as a jumper between two adjacent riser lengths 29, but ideally only as a short-term solution when the primary data telemetry for the riser has broken together. Such an alternative will typically require a certain level of ROV anyway. intervention. Acoustics is probably the best established form of communication for underwater data telemetry. Acoustics has a number of advantages and some disadvantages, such as both are well understood. Over very short distances (about 70 meters) a data rate of 500 kbps achievable with a carrier frequency of ~1 MHz. This the bandwidth is greater than that required for telemetry over a distance spanning two riser lengths 29 or other riser sections. In a embodiment of the system using acoustics, each riser section is equipped with a transceiver device that receives data ignores the part that is not addressed to it, multiplexes the incoming data with its own sensor readings, encodes them with its identification and then sends it combined data package to the next riser section, which uses the same procedure to add additional data and send it on. In a preferred embodiment, each riser section initially programmed to communicate only with those the riser sections located immediately above and below it which have a gauge module 91, it ignores the data intended for other riser sections. This sequencing is performed during the deployment of the riser. If a If the data telemetry system on a riser section fails, a signal is sent out from the surface, for example, which runs through all riser sections equipped with a instrument module and performs a resequencing of the transmitter / receiver units so that that the defective riser section is removed from the chain. Alternatively, the instrument module 91 above the defective instrument module 91 for example include stored instructions that when it detects no signal from its adjacent instrument module 91, this module starts listening on the second nearest the instrument module 91. When acoustics are used, as with other non-wired telemetry options, battery life management is key to ensuring a satisfactory long operating time. To be robust, sufficient battery life, e.g. at least six months, can be easily assigned to each riser section in order for it to satisfy the requirements of its various subsystems throughout the drilling / completion campaign. Use of seawater batteries, as an alternative power source, can help compensate for this limitation. In addition, the instrument modules 91 be programmed to enable periodic transmission of data, for example, once every 30 seconds or less, so that the transceiver units 109 are in listening mode most of the time. Furthermore, the instrument modules 91 be provided with sufficient memory 105 not only to store data for the periodic transfers, but also to store data for a preselected time period if data communication breaks down while corrective measures are taken. In another embodiment of the present invention enables the acoustic system to have multi-band transmission both to compensate for single-band signal breakdown, when this occurs, and to increase the transmission bandwidth. Electromagnetic or EM (radio) communication can be used, although This is not particularly useful underwater. A fundamental problem with EM are the difficulties associated with providing data communication through it conducting seawater, which has traditionally required relatively long antennas and high power. EM communication offers an important advantage with regard to installation, but at the expense of a relatively limited range. For For example, a range of 55 meters will limit the communication transfer rate to double digits, and broadband communication typically has a transmission range limited to a few inches at best. A However, one of the most important advantages of using EM is the ability to provide a practical alternative to cables. In such cases, each measuring instrument module 91 may contain a sealed EM transceiver near each riser connection, preferably positioned so that they are located close to each of the other transceivers when the riser lengths are 29 are connected, thus enabling broadband communication. Data between riser connections on each individual riser length 29 are then communicated via cables. The sensor 103 and other hardware may conveniently be located somewhere (such as desired) along the length of the riser length 29, directly connected to the above cable. In In addition, such EM-based communication technology can be expanded with laser-based or acoustic communication to provide an overall more robust data telemetry system. Laser-based (optical waves) telemetry technology can also be used. Self if laser telemetry requires more directional precision than acoustics, laser telemetry is easy to realize, especially when applied to the relatively straight lines the riser lengths 29. However, optical waves will be affected by scattering. Regardless of the communication medium or media 95 used, a preselected level of error tolerance must be achieved. One has to assume that components in the gauge modules 91 on each riser section will be able may fail from time to time. However, such failure need not be a direct consequence of electronics, but may be related to the harsh environment / treatment that the equipment is exposed to during operation or deployment. Performances of one or more of the several underwater communication media 95 must nevertheless function when the electronics on one or more riser sections are not operational. The fault tolerance options chosen are a function of the environment, the type riser system and the desired operational performance. A few selected examples on telemetry options for fault tolerance are: use of resequencing of riser sections, use of variable power, use of wired jumpers, use of ROVs replaceable data telemetry stations as well as the use of larger RAM on the vessels. As stated earlier, the riser section resequencing option provides a fault tolerance method where data is sent to cover a span of more than one riser section, and where each measuring instrument module 91 operates on the data intended for it and ignores the rest of the data. In the event of an error in a riser length of 29 or a another riser section in the riser string 23 carrying a measuring instrument module 91, a signal can be sent from the surface to resequence the transmitter / receiver units 109 to skip the faulty module 91. This is possible because the range of the signal to the instrument modules 91 can be selected to cover two or more riser parts. The variable power option provides a fault tolerance method where, in conjunction with acoustics, for example, the instrument module 91 will tune the transmitter / receiver- the device 109 so that it will normally only communicate with the station immediately above or below it. In the event of a fault condition, a signal will be sent out from the surface which instructs each measuring instrument module 91 to broadcast at higher power, so that it reports to at least the two nearest stations. Such a system can used, among other things, to locate the fault and instruct the operating personnel the instrument modules 91 immediately above and below the defective instrument module 91 to run at higher power, and return the rest of the modules 91 to normal power consumption mode. The fault tolerance method with cable jumpers prescribes a remedial option requiring ROV intervention. In this scenario, a defect may measuring instrument module 91 is accessed by cable jumpers between it and the stations immediately above and below. The ROV replaceable data telemetry station option provides a fault tolerance method that is similar to the cable alternative, except that the entire the hardware package, usually minus the sensor 103 and associated delivery / installation equipment, can be easily replaced using an ROV. The option with RAM on the vessel is a failure method where a quantity of extra RAM or other memory 105 is provided to store data if the data telemetry portion of the instrument module 91 is not working, while the sensor 103 continues to collect data. The amount of memory 105 is linearly proportional to how a lot of time expected to be needed for corrective actions. A very robust system will be one that can store several months of sensor data locally, in addition to several days with sensor data from the riser section immediately below. This clearly depends on the amount and volume of information the operator wants to be collected by the sensors 103 and the price of the memory 105. While a few fault tolerance options are described above, it should be It should be noted that various other fault tolerance options can be incorporated into all subsystems. This may include integrity checks of data sent from the vessel to shore as well as the availability of a database by a redundant data center. Regardless of the medium or media for underwater communication, according to an embodiment of the present invention, the computer 41 receives the vessel the various sensor data, sorts them, adds additional information (i.e. field name, well number and other relevant information) and forwards them to the land-based data warehouse 63 over a communications network, such as for example the global communication network 61. As a backup, stores computer 41 on the vessel the entire history of the current well being drilled / completion / production operation, etc. is performed above. In the illustrated embodiment of the system, the computer 41 receives the vessel at regular intervals the latest cargo history for each of its riser parts in the frequency domain from the data warehouse 63. The computer 41 on The vessel also performs routine monitoring of the condition of the various the riser sections, for example, several times a minute. The computer 41 on the vessel can conveniently provide a primary alarm system for when either an irregularity is detected directly from a instrument module 91, or when faster fatigue damage is predicted. Examples of Irregularity in the sensed data could be excessively high voltages, deflections, accelerations, etc. Integrated routines provided by computer program components, described in detail below, can determine the source of the irregularity and notify the operator of the possible cause. For example vortex shedding vibration ("VIV") caused by vortex shedding VX may be reported on a 91-meter-long section of the riser around 150 meters below the waterline if it experiences high-frequency oscillating voltages across the flow movement. In such a case, the computer 41 on the vessel can initiate further monitoring of the excited riser length 29 or section, and predict the condition of the riser length 29 or section several days, weeks or months in advance. It is noted that in one embodiment of the present invention, the land-based riser lifecycle management server 51 comprises computer program components to perform more extensive condition monitoring checks, but at the cost of a time delay in reporting of the results. Furthermore, after discovering such an event, the computer 41 on the vessel, over the communication network 43 on the vessel, send commands to a tensioning device control unit 39 (Figure 5) to effect control of the tensioning system 35, 35' to reduce or suppress the impact of the vortex-generated vibrations. As can perhaps be best seen in Figures 6 and 7, embodiments of the present invention a software product for life cycle management of risers 120 stored in memory 57 in the riser lifecycle management server 55 to monitor and manage multiple riser sections comprising riser lengths 29 located on several separate vessel locations (e.g. on or deployed from each vessel 27). Similarly Embodiments of the present invention include a program product for management of riser sections 120' stored in the memory 47 of the computer 41 on the vessel to monitor and manage multiple riser sections comprising riser lengths 29 allocated to the vessel in question 27. Since most of the computer program components that run by the computers on the vessels 41 and the riser lifecycle management server 51 are functionally very similar, the computer program components will essentially be described with reference to those who are either exclusively or also driven by the riser life cycle management servant 51. Note that the riser lifecycle management software product 120 and the riser part management program product 120' may be in the form of microcode, programs, routines, and symbol-based languages ​​that provide one or more specific sets of ordered operations that control the behavior of the hardware and controls the operation thereof, which will be known to and understood by those skilled in the art. Note also that neither the riser life cycle management program product 120 nor the riser part management software product 120', in one embodiment of the present invention invention, in its entirety needs to be in volatile memory, but can be selectively loaded as necessary according to various methods, which will be known to and is understood by the skilled person. Furthermore, riser life cycle management includes- the program product 120 and the riser part management program product 120' both various functional elements that will be described in detail below, and which are grouped and named as they are only for ease of reference. The skilled person will understand that the different functional elements do not have to be physically realized in any any hierarchy, but can be easily realized as individual objects or macros. Various other forms may also be used, which will be familiar to and understood by one skilled in the art. Note further that although the following description of functional components are mainly aimed at riser lengths 29, the skilled person will see that this functionality may include other riser parts of interest. According to an embodiment of the present invention, the riser lifecycle management software product 120 includes a deployment and riser section position tracker 111, a riser section load history manager 123, a riser maintenance controller 125 and a riser section load data collection controller 127, which when run by the riser lifecycle management server 51 causes the server 51 to perform various operations as described below. Deployment and the position tracker 121 may serve to receive underwater deployment and relative positioning data for multiple riser lengths 23 arranged to be deployed to form various marine riser strings 23 in connection with the multiple vessels 27. The riser load history manager 123 manages and manipulates the load history. According to an embodiment of the present invention, the riser comprises the load history manager 123 a riser part load history receiver 131, a riser part load history recorder 133, a time-to-frequency domain data transformer 135 for riser part load history, and a riser part load history transmitter 137. Riser part the load history receiver 131 may serve to receive load history data for each of the riser lengths 29 or other riser parts from each vessel 27 and to store the load history in a database, such as database 65. Riser section- the load history recorder 133 may serve to create and store a time-domain-based load history table which, as described above, can provide in real time the riser load applied to each of the riser lengths 29 or other riser sub-equipment for each vessel 27 or other units for a pre-selected time period, and can serve to store maximum amplitudes for one or more parameters of interest for each of the riser lengths 29 or other riser sections, for example in the form of a matrix of maximum amplitudes, as described above. The time-to-frequency domain data transformer 135 may serve to transform time-domain based load history data to the frequency domain and to provide a frequency domain-based load history table, as described above, in order to enable the storage of essentially all available load history for each of riser lengths 29 or other riser sections, to reduce the requirement for storage space and to reduce the processing time required to analyze The riser section load history transmitter 137 may serve to transmit the frequency domain-based load history for a subset of the riser lengths 29 or other riser parts forming an associated deployed riser string 23 to a computer 41 on board the vessel 27 that deploys the subset of the multiple the riser lengths 29 or other riser parts. This can be done over a communication networks, such as the global the communication network 61. The riser maintenance manager 125 controls the determination and scheduling of maintenance requirements. The riser maintenance manager 125 may include a riser sub- fatigue determiner 141, a riser section fatigue life estimator 143, a subsea wellhead system analyzer 145, a riser section- maintenance planner 147 and a riser section maintenance alert 149. Riser section- the fatigue determiner 141 can serve to estimate the condition of each of the riser lengths 29 and other riser parts of interest from the riser length- the cargo data received from the computers on the vessels 41 or riser voltage data (as a function of time) either received from the computers on the vessels 41 or determined from the received riser length load data by the server 51, or a combination thereof, for each riser length 29 or other riser sections of interest across the spectrum of vessels and units in communication with the riser lifecycle management server 51. Riser part- the fatigue life estimator 143 can serve to estimate the remaining life before fatigue for each of the riser lengths 29 or other riser sections of interest from the received load data, stored load history data and specific material property data for each respective riser section, or a combination of this, and to send out a notification when the fatigue life for a respective riser section falls below a preset trigger level requiring inspection. The subsea wellhead system analyzer 145 can serve to predict the magnitude of the load applied to a subsea wellhead system 25 based on load history data for a subset of the riser lengths 29 and / or riser sections which forms an associated marine riser string 23. The riser section maintenance scheduler 147 may serve to generate a schedule of routine maintenance events for each riser length 29 or other riser sections of interest, based on the received load data, the stored the load history and the material properties of the respective riser sections, or a combination of this, and to generate unforeseen maintenance events based on a cargo data irregularity detected in the received cargo data and results in the triggering of a preset fatigue trigger level that requires inspection. The riser section maintenance alarm 149 can serve to send out an online notification that reminds a user of an imminent, scheduled maintenance event, and can serve to send out an online notification indicating a requirements for an unforeseen maintenance event when such an event occurs. The riser section load data collection manager 127 manages and examines the quality of the collected riser section load data. According to an embodiment of the The present invention includes the riser section load data collection controller 127 a riser part sensor failure controller 151, a riser part sensor irregularity detector 153, a riser section sensor data predictor 155, a riser section sensor integrity checker 157 and a riser part sensor data removal controller 159. The riser part sensor error controller 151 can serve to identify a defective measuring instrument module 91 associated with one or more of the multiple deployed riser lengths forming the marine riser string 23, and to signal to one or more measuring instrument modules 91 on adjacent riser lengths that they should bypass the defective gauge module 91 or to on another way to implement one or more of the fault tolerance methods described above, for by ensuring mainly continuous collection of load data for each riser length measuring instrument module 91 located below the defective the riser length measuring instrument module 91. Note that, as will be understood by those skilled in the art, The type of fault tolerance method used depends on the type communication media used, the type of sensors connected to the instrument modules 91 and the distance between the modules 91, which may or may not be provided on each riser length 29 forming the riser string 23. The riser section sensor anomaly detector 153 may serve to detect an irregularity in load data when it occurs based on the received load data / load history data. The riser section sensor data predictor 155 may serve to generate predicted sensor data as a riser length measuring instrument module 91 associated with one or more deployed riser lengths 29 or other riser sections of interest, should report based on recent load history for the respective the instrument module 91 and / or values ​​provided by other adjacent instrument modules 91 deployed on the same riser string 23. Riser section- the sensor integrity checker 157 can serve to compare sensor readings from a riser length measuring instrument module 91 associated with one or more deployed riser lengths 29 or other riser sections that form a deployed riser string 23, with sensor readings for at least two adjacent riser lengths 29 or other riser parts forming the riser string 23 in order to determine the integrity of the riser length measuring instrument module 91, and to flag sensor readings sent from the relevant instrument module 91 when the integrity is determined to be questionable. The riser section sensor data removal controller 159 may serve to remove flagged data from a defective sensor from active journal data, and optionally to replace the removed data with corresponding predicted data generated by riser-sensor data preacher 155. The functionality provided by riser lifecycle management- The 120 software products provide utility equipment managers with real-time and stored database information to maintain the various riser sections of interest. As an example, in one embodiment of the present invention, when a user logging into the system, the user will see the different vessels 27 that are equipped in accordance with embodiments of the present invention and which are associated with the user, along with graphical user interface elements such as allows the user to query data based on vessel, riser section, or field. The vessel query can conveniently provide the user with a list of all the riser sections that are allocated to the vessel and provide a further division into riser sections as for time is deployed, is on deck or is out for maintenance, together with expected return time. This consideration of the data can also be applied to to generate a list of upcoming scheduled maintenance events. Riser section- The query can usefully give the user an estimate of how much of the service life is used by a given riser section, along with details of the most destructive events (e.g. a given hurricane). This query can also provide detailed information about the maintenance history of the riser and critical / relevant manufacturing information. Individual riser sections will be able to be moved from one vessel 27 to another with its history preserved. The field query can provide the user with information to reconstruct a riser string from any given deployment. The availability of a timestamp for each riser deployment makes it possible to determine where, in the water column, each riser section was installed under any preferably given drilling campaign. This information can also be used for automatic to generate input to a riser analysis program. As stated above, the riser part management software products on the vessels can 120' generally encompass much of the functionality provided by riser lifecycle management program product 120, but preferably on local vessel level rather than at the operational plan, fleet or company level. Consequently, The riser management software product on the vessels 120' includes a deployment and position tracker 121', a riser section load history controller 123', a riser maintenance controller 125' and a riser section load data collection controller 127', which when run by the respective computer 41 on the vessel causes the computer 41 to perform various operations, as described below. The deployment and position tracker 121' may serve to receive underwater deployment and relative positioning data for multiple riser lengths 23 aligned to be deployed to form a marine riser string 23 in connection with the respectively the vessel 27. The riser load history manager 123' manages and manipulates the load history for riser lengths 29 or other riser sections of interest associated with the respective vessel 27. Although much of the functionality is preferably implemented by the riser lifecycle management server 51, is in an embodiment of the present invention the riser load history controller 123' is nevertheless provided with and comprises a corresponding riser section load history receiver 131', a recorder 133', a time-to-frequency domain data transformer for riser section- load history 135' and a riser section load history transmitter 137', in order to at least partially perform functions performed by the riser lifecycle management server 51. According to an embodiment of the present invention, the riser section can be the load history receiver 131' serves to receive load history data for each of riser lengths 29 or other riser parts from the riser lifecycle management server 51 and to store the load history in a database, so such as the database 49. This data is typically frequency domain based data. According to one embodiment of the present invention, a time-to- frequency domain data transformer for riser section load history 135' also, or alternatively, serve to independently transform time-domain load history data into the frequency domain and to provide a frequency domain-based load history table, as described above, thereby enabling the storage of essentially all available load history for each of the riser lengths 29 or other riser sections of interest associated with the deployed riser string 23 for the respective vessel 27, to reduce storage space requirements and to reduce processing time necessary to analyze the data. The riser section load history recorder 133' can serve to create and store a time-domain-based load history table which, as described above, can provide real-time riser load applied to each of the the riser lengths 29 or other equipment for each vessel 27 or other units for a preselected time period, and can serve to store maximum amplitudes for one or several parameters of interest for each of the riser lengths 29 or others riser parts, for example in the form of a matrix, as described above. Riser parts- The load history transmitter 137' can serve to send either raw data, time domain based data or frequency domain based load history for the riser lengths 29 or other riser sections of interest that form a associated deployed riser string 23, to the riser lifecycle management server 51 over a communications network, such as the global the communication network 61. The riser maintenance controller 125', similar to that for the riser life cycle management program products 120, can control determination and planning maintenance requirements for riser lengths 29 or other riser sections of interest, especially those of the vessel in question 27. Riser Maintenance Manager 125' may include a riser section fatigue determiner 141', a riser section fatigue life estimator 143', a subsea wellhead system analyzer 145', a riser section maintenance scheduler 147' and a riser section maintenance alerts 149'. The riser section fatigue determiner 141' may serve to estimate the condition of each of the riser lengths 29 and other riser parts of interest from load data for riser lengths, e.g. riser stress data (as function of time) either received from measuring instrument modules 91 or determined from the data received from the measuring instrument modules 91, stored load history data and material properties, or a combination thereof, for each riser length 29 or other riser parts of interest generally to the particular vessel 27 or unit. The riser section fatigue life estimator 143' is similarly arranged to estimate the remaining service life before fatigue for each of the riser lengths 29 or other riser sections of interest from the received load data, stored load history data and specific material property data for each respective riser section, or a combination thereof, and to send out an alert when the fatigue life of a respective riser part falls below a predetermined fatigue life trigger level requiring inspection. Underwater The wellhead system analyzer 145' is further similarly arranged to predict the magnitude of the load applied to a subsea wellhead system 25 based on the received load data and / or stored load history data for the deployed the riser lengths 29 or other riser sections of interest that form the current marine riser string 23. The riser section maintenance scheduler 147' may serve to generate a schedule of routine maintenance events for each riser length 29 or other riser section of interest based on the received load data, the stored the load history and the material properties of the respective riser sections, or a combination of this, and to generate unplanned maintenance events such as reaction to a load data anomaly when detected in the received the load data and results in triggering a predetermined fatigue life-based trigger level requiring inspection. The riser section maintenance alarm 149' can serve to send out an online notification reminding a user of an upcoming planned maintenance event, and can serve to send out an online notification such as indicates a requirement for an unforeseen maintenance event when it exists. The riser section load data collection manager 127' manages and examines the quality of the collected riser section load data. According to an embodiment of the The present invention includes the riser section load data collection controller 127' a riser part sensor fault controller 151', a riser part sensor irregularity detector 153', a riser section sensor data predictor 155', a riser section sensor integrity checker 157', a riser section sensor data removal controller 159' and a riser section load sense data receiver 161. The riser section load sensor data receiver 161 may serve to receive load data obtained from the measuring instrument modules 91 when the riser lengths 29 or other riser sections of interest have been finally deployed and form the riser string 23 and / or during deployment. The riser section sensor fault controller 151' may serve to identify a defective measuring instrument module 91 associated with one or more of the several deployed the riser lengths that form the marine riser string 23, and to signal to one or more adjacent measuring instrument modules 91 that the defective the measuring instrument module 91 shall be bypassed, or otherwise implement one or several of the fault tolerance methods described above, in order to ensure mainly continuous load data collection for each measuring instrument module 91 which is located below the defective gauge module 91. The riser section sensor irregularity detector 153' may serve to detect a load data anomaly when it occurs in response to the received The riser section sensor data predictor 155' may serve to generate predicted sensor data that each measuring instrument module 91 is associated with one or more deployed riser lengths 29 or other riser sections of interest should report based on recent load history for the current instrument module 91 and / or the data provided by other instrument modules 91 deployed on it the same riser string 23. The riser section sensor integrity checker 157' can serve to to compare sensor readings from a measuring instrument module 91 associated with one or several deployed riser lengths 29, or other riser sections forming a same deployed riser string 23, with sensor readings for at least two adjacent riser lengths 29 or other riser parts forming the riser string 23, for with determining the integrity of the riser length measuring instrument module 91 and to flag sensor readings from the respective instrument module 91 when the integrity is determined to be questionable. The riser section sensor data removal controller 159' may serve to to remove flagged data for a defective sensor from active journal data, and possibly to replace the removed data with corresponding predicted data generated by the riser sensor data predictor 155'. Riser Lifecycle Management software products 120 and / or The riser part management software product 120' may conveniently interface with a riser tension control software product 170 that can detect and control tension in risers or alternatively may include different program components to perform this function. Accordingly, an embodiment of the present invention may provide a riser tension recorder 171, a riser tensioning device- controller and a vortex-generated vibration warning controller. The riser draft recorder 171 can serve to record tension settings, applied riser tension and the tensioning device travel length for a riser tensioning system connected to a marine riser string 23. The riser tension controller 173 can serve to provide data that can be used by a control unit 39 in a riser tensioning system 35, 35' to adjust the tension setting so that it constantly applies an optimal tension to the riser based on riser tension data determined from the received load data. Vortex-generated vibration warning controller 175 can serve to detect an impending or ongoing vortex creation vibrational state and the approximate location of this along the length of the marine riser string 23 when it occurs based on at least the received the load data, to signal a crisis alarm in response to detection of the the vortex-generated vibration state, and to determine a measure to reduce or suppress the detected vortex-induced vibration. If implemented in the riser lifecycle management software product 120, this provides the program component a support for the vessel 27, although possibly with a significant delay. Embodiments of the present invention also include various methods for monitoring and managing multiple marine riser sections. According to an embodiment of the present invention, a method of monitoring and management of multiple marine riser sections include steps to receive riser length identification data from a riser length identification sensor 73 arranged within a wellhead 31 for each of a plurality of riser lengths 29 (or other riser sections of interest) during deployment from the respective vessel 27 to form a marine riser string 23, and determine a relative deployment position for each of the riser lengths 29 deployed from the vessel 27 to form the marine riser string 23. Each of the riser lengths 29 includes associated characteristics (e.g. an RFID tag 71) that can be read by a riser length identification sensor 73 to separately identify each of the riser lengths 29 from each of the other riser lengths 29. The method may also include receiving load data for each of the riser lengths 29 from multiple riser length measuring instrument modules 91, and monitor the load on each of the deployed the riser lengths 29 based on the load data provided by the riser length- the measuring instrument modules 91. The method may also include estimating a load condition for each of the deployed riser lengths 29 based on the load data for one or several of the deployed riser lengths 29, and give an alarm in response to the the estimated load condition approaches a design load or an upper operating limit one or more of the deployed riser lengths 29. The method may also, or alternatively, comprise estimating fatigue damage to the deployed riser lengths 29 based on the load data for one or more of the deployed riser lengths, and give an alarm that reaction to the estimated fatigue damage exceeding a pre-selected limit. The method may also, or alternatively, comprise detecting a irregularity in the load data for one or more of the deployed riser lengths 29, when it occurs, and give an alarm in response to the detection of the irregularity. The method may also, or alternatively, comprise receiving load data for each of the riser lengths 29 from multiple riser length measuring instrument modules 91, monitor the load on each of the deployed riser lengths based on the load data provided by the riser length measuring instrument modules 91, monitor tension settings, applied riser tension and the travel of the clamping device in a clamping system 35, 35', and supplying data to a tensioning device control unit 39 for controlling adjustment of the tension setting for the tensioning system to constantly apply an optimal tension in the riser based on the load data. According to another embodiment of the present invention, a method for monitoring and managing multiple marine riser sections include steps for determining a relative deployment position for each of a plurality of riser lengths 29 (or other riser sections of interest) deployed from a vessel 27 to form a marine riser string 23, receive load data for each of the deployed riser lengths 29 from multiple riser length measuring instrument modules 91 connected to at least a subset of the deployed riser lengths 29, monitor the load on each of the deployed riser lengths 29 based on the load data provided by the riser length measuring instrument modules 91, estimate a riser length load condition for each of the deployed riser lengths 29 based on the load data for one or more of the multiple deployed riser lengths 29, and give an alarm in response to the estimated load condition approaching determine a design load or an upper operating limit for one or more of the the deployed riser lengths 29. The method may also include a step in which a computer 41 on the vessel transmits deployment location data and relative deployment position and load data for the deployed riser lengths 29 to a central data warehouse (e.g., the data warehouse 63) which is located remotely from the vessel 27 and is arranged for to receive such data from several such vessels 27, each deploying riser lengths 29 which forms one or more riser strings 23. The method may also or alternatively include detecting an imminent or ongoing vortex creation vibrational state and the approximate location of this along the length of the riser string 23, and adjust the tension of the riser string 23 to reduce or suppress the detected vortex-induced vibration state. According to another embodiment of the present invention, a method for monitoring and managing several marine riser sections, such as e.g. located at one or more separate vessel locations, include steps for receiving deployment and position data for each of several deployed riser lengths 29 (or other riser sections of interest) deployed on one of several separate vessel locations having the current riser length 29, receive, from a computer 41 on board the vessel, load history data for each of the 29 riser lengths deployed on the multiple separate vessel locations, transform riser length load history data received in the time domain to load history data in the frequency domain, and determine a level of damage on each of the deployed riser lengths 29 based on the received the riser length load history data and / or the transformed riser length the load history data. The method may also, or alternatively, comprise estimating remaining functional life of riser lengths based on material properties for each respective riser length 29 and the received the riser length load history data and / or the transformed riser length the load history data, schedule routine maintenance events for each of the deployed riser lengths 29 and plan for unforeseen (e.g. immediate measures or emergency situations) maintenance events in response to an irregularity (e.g. an unexpected event) in the received riser length load history data resulting in the triggering of a preset fatigue trigger level that requires inspection. The method may further also, or alternatively, comprise: reconstruct a riser string comprising any of the riser lengths 29 deployed at any of the several separate vessel locations from deployment and position data for the current riser string 23, and predict the magnitude of a load applied to a subsea wellhead system 25 associated with it the current riser string 23 from the associated riser load history data for at least a subset of several riser lengths 29 that form the relevant riser string 23. Note that each riser length 29 does not need to have a separate associated instrument module 91. Furthermore, the method may also, or alternatively, comprising sending riser load history data in the frequency domain for each single of the several deployed riser lengths 29 to the respective computer 41 who is located at the relevant one of the several vessel locations and who is carrying it current deployed riser length 29. It is important to note that although embodiments of the present invention is described in connection with a fully functional system, one skilled in the art will understand that the principles of at least parts of the present invention and / or aspects thereof may be distributed in the form of a computer-readable medium with instructions in a variety of forms for running on one or more processors, or the like, and that the present invention is equally applicable regardless of the specific type of signal transmission media as used to realize the distribution. Examples of computer-readable media includes, but is not limited to: non-volatile, hard-coded media such as read-only memory (ROM), CD-ROM and DVD-ROM, or erasable, electrically programmable read-only memory (EEPROM), writable media such as floppy disks, hard drives, CD-R / RW, DVD-RAM, DVD-R / RW, DVD+R / RW, flash drives and others newer types of memory, and transmission media such as digital and analog communication connections. Such media can contain both driving instructions and operating instructions related to riser lifecycle management- the program products 120, the riser section management program product 120', the riser pulling or management software product 170 and the computer feasible method steps described above. Embodiments of the present invention provide a number of advantages. For For example, embodiments of the present invention provide a system comprising a central database that can be used by field and maintenance personnel to store and communicate critical riser information. This central database can also provide early visibility of an impending maintenance event and plan it accordingly. The storage of data regarding Marine risers can usefully provide a number of other opportunities for management and maintenance of marine field development equipment. For example, the load history information for risers can be used to improve the design of riser lengths, which are related to the availability of better knowledge about actual riser load history. In addition, the riser load history information for a given drilling or production operation, by extrapolation or through a separate riser analysis program, be used to predict the magnitude of the loads applied to the subsea wellhead system. This information can in turn be used for to optimize the design of future subsea wells within the same general area (i.e. same field development). Embodiments of the present invention also enables significant fault tolerance in the subsystem that believed to be most vulnerable, namely the data telemetry equipment, along with additional fault tolerance feature. Embodiments of the present invention also provide sufficient flexibility to communicate across third-party equipment. For example, The database stores key parameters for the riser tensioning device, such as migration and applied riser tension. Such system integration, together with real-time load data, can enable direct manipulation of the riser tensioning system for to improve the performance and extend the life of riser lengths. Embodiments of the system can automatically notify the user of both routine and unforeseen maintenance events. A routine A maintenance incident is an event that is planned some time in advance, but may have been assisted by cargo history information in the database. An unforeseen A maintenance incident is one related to an unexpected event. For example, one or more riser lengths in a string that have been directly affected by a hurricane could reach a predetermined fatigue life-based trigger level, which is at least requires inspection of the riser length(s). In such a scenario, the operator will have a high degree of certainty that the remaining riser sections are suitable for deployment water, which reduces the downtime associated with the entire riser string. Embodiments of the system may also automatically notify the user about both routine and unforeseen maintenance events. This application is related to and takes priority from US patent application 12 / 029,376 entitled "Riser Lifecycle Management System, Program Product, and Related Methods", filed February 11, 2008, and is also related to US- patent application 10 / 951,563 entitled "System for Sensing Riser Motion", filed September 28, 2004, now U.S. Patent 7,328,741. Both are incorporated herein by reference. reference in its entirety. In the drawings and description, a typical preferred embodiment is shown. of the invention, and although specific wording is used, this is intended only for to explain, and not to limit. The invention has been described in detail with specific reference to the illustrated embodiments. However, it should be It is clear that various modifications and changes can be made within the scope of the invention. framework and idea as described in the previous description. For example, even if the description primarily focuses on application for drilling platforms and drilling risers, embodiments of the present invention are equally applicable to TLP and SPAR type production platforms / rises.

Claims

1. Method for monitoring and managing multiple riser sections, where The method includes the steps of: determine a relative deployment position for each of multiple riser lengths deployed from a vessel to form a marine riser string, where each of the several The riser lengths have characteristics that can be read by a riser length meter. identification sensor to individually identify each of the multiple the riser lengths from each of the other of the several riser lengths below deployment of these, receive load data for each of the multiple deployed riser lengths from multiple riser length measuring instrument modules connected to at least a subset of the multiple deployed riser lengths, monitor load on each of the multiple deployed riser lengths based on the load data provided by the multiple riser length- the measuring instrument modules, estimate a load condition for each of the multiple deployed the riser lengths based on the load data for one or more of the multiple deployed the riser lengths, and give an alarm in response to the estimated load condition approaching determine a design load or an upper operating limit for one or more of the the multiple deployed riser lengths.

2. The method of claim 1, further comprising the steps of: detect an impending or ongoing vortex-induced vibrational condition and the approximate location of this along the length of the riser string, and adjust the tension in the riser string to reduce or suppress it detected the vortex-generated vibration state.

3. The method of claim 1, further comprising the step of sending deployment location data and relative deployment position and load data for the several deployed riser lengths to a central database repository that is remote from the vessel and is designed to receive such data from multiple vessels, each deploying riser lengths that form one or more riser strings.

4. Procedure for monitoring and managing multiple riser sections that located at one or more separate vessel locations, where the method includes the steps to: receive deployment and location data for each of several deployed the riser lengths, where each riser length is deployed on one of several separate vessel locations that have the relevant riser length, where each separate vessel location has an on-board computer, receive load history data for each of the multiple riser lengths deployed at the several separate vessel locations from an associated computer on the vessel, transform riser length load history data received in the time domain into load history data in the frequency domain, and determine the level of damage to each of the multiple deployed riser lengths based on at least one of the following: the received riser length load history data or the transformed riser length load history data.

5. The method of claim 4, further comprising the steps of: estimate the remaining serviceable life of riser lengths based on material properties for each respective riser length and at least one of the following: the the received riser length load history data or the transformed riser length the load history data, schedule routine maintenance events for each of the several deployed riser lengths, and plan unforeseen maintenance events in response to a irregularity in the received riser length load history data resulting in triggering a predetermined lifetime-based trigger level requiring inspection.

6. The method of claim 4, further comprising the steps of: reconstruct a riser string with any of the several the riser lengths deployed on any of the several separate the vessel locations based on deployment and position data for the relevant the riser string, and predict the magnitude of a load applied to a subsea wellhead system associated with the relevant riser string based on the associated riser- load history data for at least a subset of several riser lengths forming the relevant riser string.

7. The method of claim 4, further comprising the step of sending riser- load history data in the frequency domain for each of the several deployed the riser lengths to the respective computer on board one of the several the vessel locations that have the respective deployed riser length. 1 / 7 10 Co 0 (0 / 0) V) two ONE 4: C4 I II II II III IN 3 / 7 45 .49 Elk. 2B 4 / 7 29 in 0.3 Fig. 3 107 in 103 Fig4 5 / 7 35' Fig. 5 6 / 7 —57 the riser lifecycle management server Memory for —120 Riser Lifecycle Management Program Product before Utpiase- for riser parts —121 and location tracker [ -—123 Load history manager for riser parts —131 Riser section-Iast history-receiver —133 Stigerørdel-Iasthistorie registrar data converter Time-to-frequency domain —135 for riser section key history Stigerørdel-Iasthistorie transmitter —137 125 Riser maintenance guide —141 Exhaust pipe part-exhaust-controller Riser Section Fatigue Life Estimator — 143 Subsea Wellhead System Analyzer —145 Stiqer pipe parts maintenance plan games —147 Riser pipe maintenance warning —149 v— 127 for riser parts Load data collection manager —151 Riser section sensor error control —15.3 — Riser Part Sensor Irregularity Detector -155 Riser sensor data predictor —157 Riser section sensor integrity checker Riser Part Sensor Data Removal Controller —159 in 70 riser tension for control of Program product —171 Riser draft recorder IN —173 Riser pull-guide IN for notification Controls vortex-induced vibration IN —175 Fig. 6 7 / 7 —47 Memory of the vessels —120' of riser parts Program product for management riser sections —121' Deployment and position trackers for [ —123' Load history manager for riser parts —131' Riser tube part load history recorder Time-to-frequency domain data transform —133' for riser section load history Stigerørdel-Iasthistorie transmitter —135' Riser section-load history-receiver —137' —125' for risers Maintenance board —141' Riser section fatigue tester —143' Riser section fatigue life estimator —145' Subsea Wellhead System Analyzer —147' Riser section maintenance planner Riser section maintenance alerts —149' —127' Load data entry manager for riser sections —16? Riser section load sensor data receiver —151' Riser section sensor error controller —153' Riser Part Sensor Irregularity Detector —155' Riser pipe section felt data predictor —157' Stiqer tube sensor integrity checks —159' Ladder Ordel Sensor Data Removal Controller —170 riser tension for control of Program product —171 strato ge pipe stretch reg i List —173 Riser pull-guide by vortex-generated vibration Alert Manager —175 Fig. 7 - — —