Design tool for pipeline operational procedures

Abstract

A tool to design an operational procedure for a subsea pipeline, configured to receive input data from a user relating to the operational procedure and to output to the user at least one work product

Description

This invention relates to a tool for use in designing pipeline operations, and more particularly to a design tool for modelling and designing operational procedures (such as installation) of subsea pipelines, especially subsea flexible umbilical pipelines. Typically, when planning and preparing for a pipeline operation (or operational procedure, the terms being used interchangeably herein), subsea engineers are required to perform detailed engineering calculations, testing and planning in order to determine information necessary for implementing the operation in question. Specifically, the appropriate components, equipment, process steps, operational conditions and parameters, and an optimum schedule. Careful planning is needed in order to select an appropriate combination of components and equipment types, the appropriate operational processes and associated pipeline configurations to utilise, and to determine the optimum schedule for any given pipeline operation. For example, in a typical installation operation for a subsea flexible umbilical, around 50 different components and pieces of equipment are utilised. The properties of each component and piece of equipment used all then need to be assessed and analysed to ensure that an appropriate (optimum) combination is selected for the installation operation, and that this combination can allow for an optimum set of operation processes. Given the sheer number and variety of components, equipment and pipeline accessories that need to be taken into consideration, the planning process for any given operational procedure can be lengthy and detailed. Due to the number of variables that need to be accounted for, the calculations required to carry out such planning analyses are complex and time-consuming; they also typically require in-depth knowledge and extensive experience of pipeline operations. There are significant costs associated with equipment production, as well as with the operation itself. For example, a typical installation operation will require the use of multiple vessels for several weeks, and therefore cost several millions of dollars. As such, any miscalculations (or sub-optimal results obtained) during the planning process can have a significant negative impacton implementation of the operational procedure, and on its associated costs. As a result, the planning process for a typical pipeline operation usually requires an extended timescale (several months to a year), and / or involves the input of a large team of experienced subsea engineers. Each operation will have different requirements and conditions, and therefore the planning process needs to be conducted anew for each operation. There are, however, increasingly instances of very tight turnaround timescales (on the order of a few days or weeks) between notification of an operation being required and the desired date for beginning the operation. A corresponding level of detailed planning and analysis is nevertheless still required to prepare for these installation operations. The present invention has been devised to address one or more of the issues discussed above. According to a first aspect of the present invention, there is provided a computer-implemented design tool arranged to design an operational procedure for a subsea pipeline. The design tool comprises at least one input configured to receive input data from a user relating to the operational procedure; at least one processor and an operatively coupled memory, the memory being programmed with instructions that when executed cause the at least one processor to perform functions; and at least one output configured to output, to the user, at least one work product relating to implementation of a final operational procedure design. The input data comprises: (i) pipeline composition data defining a plurality of pipeline components forming the subsea pipeline and associated equipment for use in the operational procedure; and (ii) operational process data comprising a plurality of operational parameters defining a plurality of operational processes carried out to implement the operational procedure. The processor is configured to: generate a proposed design for the subsea pipeline and for the operational procedure based on the received pipeline composition data and operational process data; and calculate one or more sets of properties of the proposed design for the subsea pipeline and / or the operational procedure. For each of the one or more sets of properties, the processor is further configured to: determine whether the set of properties meets a predefined criterion for one or more of the plurality of operational processes to be successfully performed; and display, via an interactive user interface to the user, the set of properties, in association with an indication of whether the set of properties meets the predefined criterion. In dependence on the predefined criterion not being met, the processor is configured to (i) request updated input pipeline composition data and / or operational process data from the user, (ii) generate an updated proposed design for the subsea pipeline and / or for the operational procedure based on the received updated input data, and (iii) re-perform the preceding calculation, determination and display functions until the predefined criterion is met. In dependence on the predefined criteria being met, the processor is configured to (i) determine the final operational procedure design based on the updated proposed design for the subsea pipeline and for the operational procedure, and (ii) generate the at least one work product relating to implementation of the final operational procedure design. The above-described design tool provides functionality which ensures that both pipeline composition data (properties of pipeline constituent components and operational equipment), and pipeline operational process data (operational parameters required to implement one or more process steps of the overall procedure) can be taken into account when designing a pipeline operational procedure. The presentApplicant has appreciated that these two aspects are interrelated and interdependent to a certain degree, and that altering factors of one aspect may have an effect on the other aspect. The design tool has therefore been devised to ensure that this interdependence can be taken into account. The design tool also provides its functionality in such a way that iterative analysis and feedback can be achieved. Specifically, a first set of input data is analysed to ascertain whether this input data will result in a pipeline composition design and an operational procedure design that is likely to be successful. If not, factors that need to be changed in relation to either or both aspects in order to arrive at a successful result are identified to the user for alteration. The design tool also issues a prompt for updated data to be provided so as to improve aspects of the pipeline composition design and the operational procedure design to achieve a (more) successful result. Optionally, the operational procedure corresponds to a pipeline installation, and / or a pipeline demobilisation. In some instances, the subsea pipeline is flexible. The advantages associated with the design tool are most evident when the tool is used in relation to the installation of a flexible subsea pipeline, since such operational procedures in relation to flexible pipelines can require the consideration of a particularly large number of variables in order to arrive at a suitable final design. The design tool can nevertheless be tailored for implementation in relation to other types of procedures and / or pipelines (e.g., rigid pipelines). In some instances, the predefined criterion corresponds to whether the set of properties lies within an acceptable range of values that avoids causing fatigue and / or damage to the subsea pipeline during the operational procedure. The acceptable range of values (or alternatively, an acceptable one or more values) may reflect the real-world effects of the proposed pipeline composition design and of the operational procedure design. The designs are updated if it is determined that fatigue and / or breakage could occur as a result of the current design parameters. This provides a useful automated feedback mechanism that ties the pipeline composition and pipeline operational processes together in a way that they would be during the real-world implementation. In this regard, the design tool advantageously allows the pipeline composition design and operational procedure design to be rigorously tested and modelled virtually in relation to its subsequent desired real-world implementation. An optimal design is thereby achievable without the attendant material costs of real-world testing. Optionally, the plurality of operational processes comprise any one or more of the following processes: a vertical connection or disconnection, a pull-in, a pull-out, an abandonment, a recovery, a horizontal connection or disconnection; a connection or disconnection to a well and / or seabed storage; or a connection or disconnection to a surface platform and / or vessel. These processes may occur at first and / or second ends of the subsea pipeline during the course of the operational procedure. It will be appreciated that in the above list of processes, disconnections will typically take place during demobilisation procedures, whereas connections will more usually take place during installation procedures. In some instances, the plurality of operational parameters may define any one or more of the following: (i) water depth at a location of the operational procedure; (ii) water movement at the location of the operational procedure; (iii) properties of a vessel to be used during the operational procedure; or (iv) actions to be taken during one of the plurality of operational processes. Optionally, the pipeline composition data comprises any one or more of the following: (i) a type of the subsea pipeline; (ii) a proposed form of the subsea pipeline to be achieved during the operational procedure; or (iii) properties of one or more accessories and / or pieces of equipment that will form part of the subsea pipeline or be used during the operational procedure. For example, the type of pipeline may correspond to any one or more of: a gas injection line, gas lift line, oil export line, production pipeline or an umbilical. As another example, the proposed pipeline form to be achieved may be defined by any one or more of the following: whether a lazy wave is desired; a number and / or type of buoyancy(s) required; the quantity of portions of the pipeline (e.g., number of pipe sections making up the overall pipeline composition design and the lengths of each of the pipe sections); a friction factor between the pipeline and seabed soil; pipeline weight and bending stiffness. The accessories / equipment properties required can include: torque value and lubricant to be applied; connector dimensions, maximum load and minimum area for support at a vessel worktable. In general, the above-described design tool allows a wide variety of operational parameters and pipeline composition variations to be combined with one another and taken into consideration when modelling an optimised pipeline operational procedure design. More specifically, factors that cannot be controlled (e.g., constraints relating to the conditions or environment of the operational procedure) can be analysed and taken into account during the modelling and design process. A variety of other factors that can be altered by the user are also accounted for. There are a very large number of such factors, and the above-described design tool provides the flexibility to account for as many of these factors as possible, in an automated, consistent and robust manner. In some instances, the request for updated input pipeline composition data and / or operational process data from the user may comprise: (a) information that enables the user to determine why the predefined criterion has not been met, and / or (b) instructions for the user to update the pipeline composition data and / or operational process data to ensure the predefined criterion is met. The above-described design tool can therefore not only inform the user of potential issues that may arise from the proposed design, but can also inform the user of the appropriate actions that will need to be taken in order to prevent such issues from arising. For example, as noted above, by instructing the user on how they need to alter the pipeline composition and / or operational process data in order to arrive at an improved overall design. Optionally, the one or more sets of properties relate to any of the following: (i) loads on a pipeline catenary during the operational procedure; (ii) pressure exerted by one or more tensioners during the operational procedure; (iii) wave movements experienced during the operational procedure; or (iv) a transfer angle of the subsea pipeline during the operational procedure. The above-described sets of properties are those which have a potentially significant risk of minor design inaccuracies resulting in fatigue and / or breakage of the subsea pipeline. The design tool is therefore able to model the properties of the pipeline composition and / or the operational procedure in relation to various ones of these properties that are key to maintaining integrity of the subsea pipeline, and thereby ensure that an appropriate pipeline composition and appropriate operational processes are implemented to minimise risk of such fatigue or damage occurring. It is further noted that additional sets of properties, which may be derived via calculations carried out by the processor, may include any one or more of the following sets of properties I outputs: (a) vessel movements experienced due to possible wave conditions during the operational procedure; (b) transfer angles (of the vessel and floating production winches) during a pull-in or pull-out operational procedure; (c) stress in hang-off structures used to support the pipeline in a vessel worktable; (d) an amount of dead weight necessary to anchor the pipeline during pull-in operational procedures; and / or (e) torque and pressure required in torque tools to connect two pipeline connectors. In some instances, the at least one work product may comprise an operational diagram comprising information and instructions about the pipeline composition and the plurality of operational processes associated with the final design for the pipeline operational procedure. In this manner, the design tool is capable of conveying a comprehensive operational procedure visualisation / diagram (or even a set of diagrams, with each diagram corresponding to one of the operational processes needed to install a pipe section, for example) containing a large amount of detailed information regarding the final operational procedure design, in a manner that is clear and easy to understand. The ability of the design tool to robustly model the operational procedure and output the required information in an automated manner significantly reduces the time and effort required to generate this information. Additionally or alternatively, the at least one work product may comprise a materials list defining the pipeline components, accessories and equipment to be used during implementation of the final design for the operational procedure. As such, a detailed breakdown of the final pipeline composition that is required to implement the operational procedure design can be derived, and presented to the user such that the implementation can take this into account. Additionally or alternatively, the at least one work product may comprise a plurality of lay table diagrams, each lay table diagram comprising: an indication of a pipeline configuration that may be generated during one or more of the plurality of operational processes; and an associated indication of whether the pipeline configuration would enable the corresponding one or more operational processes to be successfully performed. A lay table diagram may be generated for each step in the operational procedure, and each lay table diagram may therefore include one or more of the following pieces of information: tensions, angles and physical distances resulting from the operational processes associated with each lay table diagram step; and / or vessel movement between lay table diagram steps. Additionally or alternatively, the at least one work product may comprise a plurality of sea state tables, each sea state table comprising an indication of wave movement in a location of one of the plurality of operational processes that would enable the corresponding operational process to be successfully performed. The above term ‘successfully performed’ is used hereinabove to indicate that implementing the operational process(es) does not result in fatigue I damage I breakage of the pipeline. The sea state tables indicate the vessel movements that would be experienced, as a result of wave movements and wave conditions, during each of the operational processes. The design tool is able to model and output the above-described tables, lists and diagrams in an automated manner, thereby significantly reducing the amount of time and effort required from subsea engineers. Moreover, the design tool is able to do this in a robust manner that minimises the amount of human input (and hence the corresponding risk of human introduced error) during the analyses. The design tool also guides the user in how to alter the input data so as to arrive at the desired result. The resulting final design that is arrived at is robust, as it is comprehensively modelled and tested. Additionally or alternatively, the at least one work product may comprise a set of instructions defining a workflow to be followed when implementing each of the plurality of operational processes in the final design for the operational procedure. The work product may additionally or alternatively comprise a schedule that defines the timings and order of a series of tasks that are to be carried out as part of each of the plurality of operational processes. For example, the set of instructions may include a detailed breakdown of all of the steps I tasks forming part of the workflow that are necessary to implement the entire operational procedure designed by the tool, along with an indication of the expected duration of each step I task. This breakdown is presented in a manner that is immediately understandable to the user and to the third party. The design tool therefore provides tangible outputs that improve the translation between procedural design and the final real-world implementation, whilst minimising the amount of human input involved in deriving this translation, and thereby reducing the instances of human error that may occur. Optionally, the at least one work product may be configured to be output to a third-party service provider who will be performing the operational procedure. As such, the design tool may output the work product(s) that have been generated to the appropriate entity (i.e., the service provider) who will need the information contained therein in order to prepare for and implement the desired operational procedure. Efficiency of the design process is hence improved. In some instances, the memory may be further programmed with instructions that when executed cause the at least one processor to determine if the received input data contains new information, and if so, to update a database to include the new information in the received input data. This processing can be performed in relation to both the data that was initially received by the design tool, as well as any updated data that is received subsequently. In some instances, each of the plurality of pipeline components and equipment may have an associated identifier. In such instances, the memory may be further programmed with instructions that when executed cause the at least one processor to determine if the received input data contains new information. This may be done by comparing a first identifier received in the input data for each of the plurality of pipeline components and equipment with a second identifier stored in the database in association with a stored set of pipeline components and equipment; and if the first and second identifiers do not match, determining that the input data contains the new information. Optionally, the memory may be further programmed with instructions that when executed cause the at least one processor to: retrieve stored data from a database, the stored data comprising information relating to use of one or more of the plurality of pipeline components and equipment during at least one previous operational procedure; and calculate at least one of the one or more sets of properties based on the retrieved stored data. The design tool is able to draw on stored data from previous (successful) operational procedures, which beneficially reduces the potential for a less successful procedure to be designed, since at least some of the properties that are under consideration will already previously have been deemed to be acceptable. The number of iterations of modelling and re-design, and the corresponding amount of time required to complete the design process, are therefore reduced. Optionally, the input of the design tool may be configured to, at predefined intervals, receive one or more data updates comprising information about use of one or more of the plurality of pipeline components and equipment during the at least one previous operational procedure. In such instances, the memory may be further programmed with instructions that when executed cause the at least one processor to update the stored data in the database based on the received data updates. In some instances, the one or more data updates may comprise one or more of the following: instructions and / or advice from engineers relating to the at least one previous operational procedure; changes to the predefined criterion; and changes to one or more of the plurality of operational parameters. As such, data and / or information (learnings) from previous procedures, derived by engineers at the time, can be incorporated into the design tool. Any changes to the predefined criterion (e.g., from previous learnings or new decisions) can also be taken into account. This improves the analysis and modelling functionality of the design tool, and therefore improves its ability to design an optimal operational procedure. Considered another way, the design tool is effectively self-learning. The number of iterations of modelling and re-design, and the corresponding amount of time to complete the design process, is therefore reduced. Optionally, the memory may be further programmed with instructions that when executed cause the at least one processor to display, via the interactive user interface: a visual representation of the pipeline composition that will form part of the proposed design for the pipeline operational procedure; and one or more user-selectable icons that, upon interaction by the user, alter at least one property of the visual representation. In such options, the instructions when executed may further cause the at least one processor to, upon interaction by the user, update (i) the visual representation to take into account the alteration of the at least one property, and (ii) the proposed design for the operational procedure. Optionally, the at least one property of the visual representation comprises any one or more of the following: (i) an order of the plurality of pipeline components and equipment for implementation in the proposed design for the pipeline operational procedure; or (ii) a type, identity or number of the plurality of pipeline components and equipment. As such, the user can clearly visualise the effect of implementing certain pipeline combinations (and certain changes to the pipeline composition) dynamically and substantially in real time. The user is able to achieve this benefit for a variety of changes that are made to the pipeline composition, without having to reperform any of the other calculations or definitions that have been carried out thus far to arrive at the proposed design. The user can also therefore take action in relation to aspects of the pipeline composition design, based on what they view on the user interface, and potentially based on feedback of the effects of such pipeline composition on the efficacy of the operational processes that are to be performed. According to another aspect of the present invention, the is provided a computer-implemented method arranged to design an operational procedure for a subsea pipeline. The method comprises receiving, from a user, input data relating to the operational procedure; generating a proposed design for the subsea pipeline and for the operational procedure based on the received pipeline composition data and operational process data; calculating one or more sets of properties of the proposed design for the subsea pipeline and / or the operational procedure; and outputting to the user, at least one work product relating to implementation of a final operational procedure design. The input data comprises: (i) pipeline composition data defining a plurality of pipeline components forming the subsea pipeline and associated equipment for use in the operational procedure; and (ii) operational process data comprising a plurality of operational parameters defining a plurality of operational processes carried out to implement the operational procedure. For each of the one or more sets of properties the method comprises: determining whether the set of properties meets a predefined criterion for one or more of the plurality of operational processes to be successfully performed; and displaying, via an interactive user interface to the user, the set of properties, in association with an indication of whether the set of properties meets the predefined criterion. In dependence on the predefined criterion not being met, the method comprises (i) requesting updated input pipeline composition data and / or operational process data from the user, (ii) generating an updated proposed design for the subsea pipeline and / or for the operational procedure based on the received updated input data, and (iii) re-performing the preceding calculation, determination and display functions until the predefined criterion is met. In dependence on the predefined criterion being met, the method comprises (i) determining the final operational procedure design based on the updated proposed design for the subsea pipeline and for the operational procedure, and (ii) generating the at least one work product relating to implementation of the final operational procedure design. Corresponding effects, benefits and additional features that were set out above in relation to the design tool are also applicable to the method. For example, the operational procedure may correspond to a pipeline installation and / or a pipeline demobilisation. Optionally, the subsea pipeline may be flexible. In some instances, the predefined criterion may correspond to whether the set of properties lies within an acceptable range of values that avoids causing fatigue and / or damage to the subsea pipeline during the operational procedure. The plurality of operational processes may comprise any one or more of the following processes occurring at first and / or second ends of the subsea pipeline during the course of the operational procedure: a vertical connection or disconnection, a pull-in, a pull-out, an abandonment, a recovery, a horizontal connection or disconnection; a connection or disconnection to a well and / or seabed storage; or a connection or disconnection to a surface platform and / or vessel. The plurality of operational parameters may define any one or more of the following: (i) water depth at a location of the operational procedure; (ii) water movement at the location of the operational procedure; (iii) properties of a vessel to be used during the operational procedure; or (iv) actions to be taken during one of the plurality of operational processes. Optionally, the pipeline composition data may comprise any one or more of the following: (i) a type of the subsea pipeline; (ii) a proposed form of the subsea pipeline to be achieved during the operational procedure; (iii) properties of one or more accessories and / or pieces of equipment that will form part of the subsea pipeline or be used during the operational procedure. In some instances, the request for updated input pipeline composition data and / or operational process data from the user may comprise: (a) information that enables the user to determine why the predefined criterion has not been met, and / or (b) instructions for the user to update the pipeline composition data and / or operational process data to ensure the predefined criterion is met. Optionally, the one or more sets of properties may relate to any of the following: (i) loads on a pipeline catenary during the operational procedure; (ii) pressure exerted by one or more tensioners during the operational procedure; (iii) wave movements experienced during the operational procedure; or (iv) a transfer angle of the subsea pipeline during the operational procedure. The at least one work product may comprise an operational diagram comprising information and instructions about the pipeline composition and the plurality of operational processes associated with the final design for the pipeline operational procedure. Additionally, or alternatively, the at least one work product may comprise a materials list defining the pipeline components, accessories and equipment to be used during implementation of the final design for the operational procedure. Optionally, the at least one work product may comprise a plurality of lay table diagrams, each lay table diagram comprising: an indication of a pipeline configuration that may be generated during one or more of the plurality of operational processes; and an associated indication of whether the pipeline configuration would enable the corresponding one or more operational processes to be successfully performed. Additionally, or alternatively, the at least one work product may comprise a plurality of sea state tables, each sea state table comprising an indication of wave movement in a location of one of the plurality of operational processes that would enable the corresponding operational process to be successfully performed. Optionally, the at least one work product may comprise a set of instructions defining a workflow to be followed when implementing each of the plurality of operational processes in the final design for the operational procedure. Optionally, the at least one work product may be configured to be output to a third-party service provider who will be performing the operational procedure. In some instances, the method may further comprise determining if the received input data contains new information, and if so, to updating a database to include the new information in the received input data. In such instances, each of the plurality of pipeline components and equipment may have an associated identifier, and determining if the received input data contains new information comprises: comparing a first identifier received in the input data for each of the plurality of pipeline components and equipment with a second identifier stored in the database in association with a stored set of pipeline components and equipment; and if the first and second identifiers do not match, determining that the input data contains the new information. Optionally, the method may further comprise retrieving stored data from a database, the stored data comprising information relating to use of one or more of the plurality of pipeline components and equipment during at least one previous operational procedure; and calculating at least one of the one or more sets of properties based on the retrieved stored data. In such instances, the method may further comprise receiving, at predefined intervals, one or more data updates comprising information about use of one or more of the plurality of pipeline components and equipment during the at least one previous operational procedure. The method may also comprise updating the stored data in the database based on the data updates. Optionally, receiving the one or more data updates may comprise one or more of the following: receiving instructions and / or advice from engineers relating to the at least one previous operational procedure; receiving changes to the predefined criterion; or receiving changes to one or more of the plurality of operational parameters. The method may further comprise displaying, via the interactive user interface: a visual representation of the pipeline composition that will form part of the proposed design for the pipeline operational procedure; and one or more user-selectable icons that, upon interaction by the user, alter at least one property of the visual representation. The method may further comprise, upon interaction by the user, updating (i) the visual representation to take into account the alteration of the at least one property, and (ii) the proposed design for the operational procedure. Optionally, the at least one property of the visual representation may comprise any one or more of the following: (i) an order of the plurality of pipeline components and equipment for implementation in the proposed design for the pipeline operational procedure; or (ii) a type, identity or number of the plurality of pipeline components and equipment. According to a further aspect of the invention, there are provided computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the methods as set out above. To summarise, a design tool and corresponding method are provided to design an operational procedure for a subsea pipeline. The design tool is configured to receive input data from a user relating to the operational procedure and to output to the user at least one work product relating to implementation of a final operational procedure design. The design tool is configured to generate a proposed design for the subsea pipeline and for the operational procedure; and to calculate one or more sets of properties of the proposed design for the subsea pipeline and / or the operational procedure. For each of the one or more sets of properties, the processor is further configured to: determine whether the set of properties meets a predefined criterion for one or more of the plurality of operational processes to be successfully performed. In dependence on the predefined criterion not being met, the processor is configured to (i) request updated input data from the user, and (ii) generate an updated proposed design for the subsea pipeline and / or for the operational procedure based on the received updated input data. In dependence on the predefined criteria being met, the processor is configured to (i) determine the final operational procedure design based on the updated proposed design for the subsea pipeline and for the operational procedure, and (ii) generate the at least one work product. In order that the invention may be more readily understood, reference will now be made, by way of example, to the accompanying drawings in which: Figure 1 is a schematic illustration of a computing system for implementing a design tool for pipeline operations according to aspects of the invention; Figure 2 illustrates a workflow that is performed by a user of the design tool of Figure 1; and Figure 3 illustrates an example interactive graphical user interface (GUI) provided as part of the design tool of Figure 1; Figures 4 and 5 illustrate example interactive interfaces provided as part of the design tool in relation to the ‘Project Inputs’ icon and the ‘Project Diagram’ icon respectively of Figure 3; Figures 6 and 7 illustrate example interactive interfaces provided as part of the design tool in relation to the ‘Second End Pull In’ icon of Figure 3; Figures 8 and 9 illustrate example interactive interfaces provided as part of the design tool in relation to the ‘Catenary Loads’ icon of Figure 3; Figures 10 and 11 illustrate example interactive interfaces provided as part of the design tool in relation to the ‘Tensioners Settings’ icon of Figure 3; Figure 12 illustrates an example work product output by the design tool in relation to the ‘Installation Diagram’ icon of Figure 3; Figure 13 illustrates an example work product output by the design tool in relation to the ‘Procedure Text icon of Figure 3; and Figure 14 illustrates an example work product output by the design tool in relation to the ‘Schedule’ of Figure 3. Figure 1 shows a computing architecture arranged to provide a computing system 100 for implementing an automated pipeline operation design (and modelling) tool according to aspects of the present invention. In its most general sense, the computing system 100 is configured to receive input data relating to various properties and requirements of a pipeline operation project that is planned for a future time. The computing system is further configured to perform (engineering) calculations and modelling relating to the implementation of various aspects of the pipeline operation. More particularly, the computing system is configured to determine a desired design of a pipeline composition; and to determine a desired design of the operational procedure that will make use of the pipeline composition. More specifically, the pipeline composition comprises the components, equipment and accessories that will be used during the pipeline operation. The operational procedure comprises a desired set of operational processes that will be implemented as part of the overall operational procedure, each process having a corresponding set of pipeline operational configurations, timescales and schedules that will be adopted during implementation of the pipeline operation. A proposed (final) design for the pipeline operation as a whole - including the desired pipeline composition design and the operational procedure design is therefore modelled and analysed by the computing system 100. The computing system 100 is further configured to, in dependence upon the results of the calculations and modelling performed, produce output data for use in implementation of the pipeline operation. This output data may include a plurality of work products that contain information and instructions governing how the proposed design of the pipeline operation is to be implemented. For example, the work products may include an operational schedule, task list, materials list, and / or list of procedures to be followed during the operation. As will be described in greater detail subsequently, as a result of the processing that is implemented and the outputs that are generated, the computing system 100 is able to improve the efficiency, speed and accuracy with which pipeline operations can be designed, modelled and subsequently implemented. In more detail, the computing system 100 comprises at least one processor 102 and at least one memory or database 104 in operative communication with the processor 102. The memory 104 stores instructions and rules 105 that are configured to cause the processor 102 to implement the automated operational design and modelling functionality that is achieved by the design tool. The computing system 100 further comprises at least one user (communication) interface 106 that is configured to enable a user 108 to communicate with the computing system 100 and thereby implement the design tool functionality. The user interface 106 is configured to enable two-way communication of data between the user 108 and the computing system 100. Data input by the user 108 to the user interface 106 is used by the processor 102 to implement aspects of the design tool functionality. The processor 102 may in turn generate data that is output to (displayed to) the user 108 via the user interface 106. As such, the user interface 106 may correspond to a display unit, such as a graphical user interface (GUI). The user interface 106 may also therefore be configured to display a plurality of interactive icons or buttons 110 (only one of which is shown in Figure 1 for simplicity) that the user 108 may interact with to provide their input to the computing system 100 and make use of its functionality. Interactions of the user 108 with the GUI user interface 106 will be described in more detail subsequently with reference to Figures 3 to 10. To summarise, the user 106 may input a variety of data to the user interface 106 (e.g., data obtained from documentation available to the user relating to the operational procedure that is undergoing design, and / or to previous operational procedures). The user 106 may carry out this data input as part of an initial set-up phase, and / or in an ongoing manner as and when may be required. Furthermore, the user may also interact with the user interface 106 during the design process and input data on an ad-hoc basis when interacting with the icons 110. Any or all this input data may be stored in the database 104. The computing system 100 may be implemented as a distributed server system, whereby different aspects of the computing system functionality are implemented by multiple (different) computing devices or systems. As one example, it is envisaged that the user interface may be implemented on and accessible via one or more user computing devices, with the main processing functionality implemented on a different (central and remote) system or server. In addition to receiving data via the user interface 106, the computing system 100 is also configured to receive information from a plurality of data sources 112a, 112b, 112c. The data received from these sources is used by the computing system 100 to compile one or more lists or databases 114a, 114b of information relating to the pipeline operational processes. The databases 114a, 114b may be stored by the memory 104, and accessed by the processor 102 to implement the automated design tool functionality. Although two databases 114a, 114b are shown in Figure 1, in practice there may be more or fewer databases provided. For example, the databases 114a, 114b may contain properties and parameters relating to pipeline operational components that can be used by the processor 102 as inputs when performing the necessary (engineering) calculations to generate the desired outputs. The processing and rules governing these calculations may be comprised within the instructions 105 stored by the memory 104, or may be stored (and updated) separately. In their most general sense, the data sources 112a, 112b, 112c may correspond to one or more computing systems or servers having data stores containing any one or more of the following sets of stored information from which information relevant for designing future pipeline operations can be extracted. For example, (i) information relating to previous pipeline operations; (ii) information relating to a set of possible pipeline operation locations; (iii) information relating to parameters and properties of components or equipment typically used during pipeline operations. In practice, for example, the data sources 112a, 112b, 112c may correspond to computing systems storing information about a plurality of vessels that are used to carry out pipeline operations, and more specifically information about the equipment available on each vessel, as well as information characterising vessel behaviour under different conditions, the types of operation that each vessel can perform, and the associated time taken for any given operation. For example, the instructions 105 governing the engineering calculations performed by the computing system 100 in relation to the input data may include but are not limited to programming that is configured to analyse input data regarding pipeline operational equipment (e.g., vessel(s), pipeline components and accessories). The programming is also configured to model and assess how this equipment will behave under a variety of physical and environmental conditions, such as different wave conditions. The underlying software that is configured to implement the instructions 105 and associated programming includes various pieces of off-the-shelf engineering calculation, analysis and visualisation software programs (e.g., OrcaFlex™ Solutions, AutoCAD™ software) as well as certain planning and scheduling software programs. The specific software functionality that will be utilised will vary depending on the type of pipeline operations that are being designed, since the requirements of different operations can vary significantly. Communications between the computing system 100 and the data sources 112a, 112b, 112c may be carried out via an input communications interface 116. It is envisaged that the computing system 100 may obtain a large amount of the necessary data from the data sources 112a, 112b, 112c prior to the user 108 interacting with the system to start planning a new operation. However, it is also envisaged that the computing system 100 may also periodically (regularly) update its memory 104 with new information and learnings obtained after any given operation is completed, for example to incorporate information and learnings gleaned during the operation. This allows the computing system 100 to continually improve its design and modelling functionality and provide the best possible support for the user 108. It should be appreciated that the interactions that may be carried out by the user 108 in relation to the user interface 106 can, in some instances, be essentially equivalent to the interactions of the external sources 112a, 112b, 112c with the computing system 100, in terms of the data that is provided. The computing system 100 further comprises at least one further (output) communications interface 118 that is configured to enable communication of one or more of the outputs (or output data) produced by the processor 102 to an external third-party server or system 120. In some cases, the third-party system 120 corresponds to a service provider for some or all of the pipeline operations; and the output data transmitted thereto correspond to information or material that the service provider needs access to in order to prepare for and carry out the operation. As noted above, the processor 102 is configured to utilise instructions 105 stored by the memory 104 to achieve the automated design tool functionality. For ease of understanding, this functionality can be thought of as being implemented via a plurality of functional modules 122a, 122b, 122c, 122d, 122e. Each functional module has associated with it, or has access to, the appropriate processing and memory of the computing system 100 to perform general functions, thereby allowing the user to break down the overall design and modelling process into a series of (sequential) tasks within an overall workflow. These modules and their corresponding functionality will be discussed in more detail subsequently with reference to specific implementation examples and Figures 3 to 14. However, in their most general sense, the plurality of functional modules comprise the following: (i) a ‘set up’ module 122a configured to allow definition of the high-level scope of the pipeline operation that is undergoing design; (ii) an ‘initialisation’ module 122b configured to define the detailed components and procedures that will be involved during the operation. For example, to define details of the pipeline composition and operational process data constituting the operational procedure; (iii) a ‘visualisation’ or display module 122c configured to allow for an interactive design and feedback functionality and the visualisation of a variety of aspects of the operation; (iv) one or more ‘calculation’ modules 122d configured to perform engineering calculations, analyses and modelling in relation to certain aspects of the operation; and (v) an ‘output and conclusions’ (consolidation) module 122e configured to consolidate the data generated by the other modules and to generate the output work products of the design tool for provision to the user 108 and / or the third-party system 120. It will be appreciated that each module may also comprise one or more sub-modules (not shown) that together provide the functionality associated with any one module. Additionally, although the modules are described as providing separate functionality, in practice there will typically be cross-communication and interaction between the various modules as well as with the pieces of information and programming stored in the memory 104 in order to ensure that the appropriate data is processed by each module. The functionality of these modules can be accessed by the user 108 via selection of, and interaction with, one or more of the icons 110 that are displayed using the user interface 106. An overview of an automated design tool workflow 200 implemented by the computer system 100 according to aspects of the invention will now be described with reference to Figure 2. The workflow 200 is primarily implemented via the user 108 interacting with the computer system 100, using the user interface 106, and the icons 110 displayed thereon. The workflow 200 begins with an initial ‘set-up’ phase A comprising two main steps 205 and 210 during which the user 108 provides, selects or inputs data relating to certain key initial variables, parameters and properties of the pipeline operation, this information is provided to the computing system 100 via the user interface 106. As such, this input data typically defines aspects of the desired pipeline composition, and also defines one or more of the operational processes which constitute the overall operational procedure. This input involves the user 108 interacting with various ones of the modules 122a to 122e via the icons 110. The workflow 200 continues with a series of steps 215a, 215b in which the user 108 is able to interactively and sequentially model, design and visualise - in other words, digitally ‘construct’ - the composition of the pipeline that will be handled during the operation. More specifically, in each step 215a, 215b, the user 108 is able to input data defining one or more of the components and equipment that will be used during the pipeline operation, along with their associated properties. As part of these steps 215a, 215b, the computing system 100 is configured to display a model or visualisation of the pipeline composition that is being digitally constructed by the user 108. The displayed model is continually and sequentially updated (in near real-time, and as the user 108 inputs the information) to reflect the information input and defined by the user 108 in relation to the pipeline components and equipment. Although only two steps are shown in Figure 2 for simplicity, it should be appreciated that additional steps can be present in the process, depending on the pipeline composition and hence the number of pipeline components that will need to be included in the pipeline. As mentioned previously, during a typical pipeline installation for example, there can be around fifty components and pieces of equipment that need to be taken into consideration, and the combined effects of which need to be analysed and modelled, to determine the optimum pipeline composition and set of operational processes to adopt. Subsequently, the workflow 200 involves implementation of a ‘calculation and analysis’ phase B during which at least one calculation step 220 is performed (only one is shown in Figure 2 for simplicity, but multiple steps are typically desired). During the or each calculation step 220, a variety of engineering calculations and modelling functions are performed by the computing system 100, based on the information input and analysed during the preceding steps 205 to 215, to determine the properties of the pipeline composition and operational procedure that would result from those preceding steps. Additional operational input information that is specific to the calculations being carried out may be requested from the user 108 during each of these calculation steps 220 in order to allow the corresponding calculations and modelling to take place. The ‘calculation and analysis’ phase B of the workflow 200 also comprises one or more analysis and modelling steps 225 (although again only one is shown for simplicity), during which certain pieces of information that were generated during the associated calculation step 220 are consolidated and communicated to the user 108. Each analysis step 225 involves the modelling of certain aspects of the pipeline operation (based on the information provided in the preceding steps), with the aim of guiding the user 108 as to whether one or more predefined criteria necessary to achieve a successful operational procedure have been met. This allows the user 108 to be made aware of whether they need to alter the pipeline composition and / or parameters of the operational processes that have been defined thus far (as part of a proposed pipeline and operation design) so as to achieve an improved result. Examples of how this may be implemented in practice, in the context of the example of the ‘Second End Pull-in’ modelling, are shown in Figure 6. As can be seen, the user 108 is informed that the engineering calculations performed in step 220 have determined that the transfer angle for the pull-in operation is higher than a predefined limit (itself determined based on geometric and load limitations of the pipeline components and equipment). The user is therefore informed that alterations to the design of the pipeline composition and / or the operational processes will likely need to be made, so as to avoid the potential for damage to the pipeline and / or the vessel and its operational equipment. If it is determined during the analysis step(s) 225 that certain properties or parameters relating to the pipeline composition and / or operational processes should be altered or improved (as in the example outlined above), the user 108 may repeat any one or more of the preceding steps 205 to 215. Doing so will result in the user 108 altering the input information, and then causing the computing system 100 to reperform the calculation step 220 and subsequent analysis step 225 to ascertain whether an improved result has been achieved that now meets the predefined criteria. In other words, steps 205 to 225 can be implemented as part of an iterative feedback-loop process whereby aspects of the pipeline composition are digitally added to the overall design in turn, and the resulting operational processes that will be implemented using this pipeline composition design are assessed and refined (by reperforming the calculations and modelling based on the updated input data as necessary) using the functionality provided via the (modules of the) computing system 100. The design tool workflow 200 therefore takes into account the fact that altering one or more aspects of the pipeline composition design can achieve specific results in relation to one or more operational processes using the specific aspects of the pipeline composition design. Finally, once it has been determined that an acceptable pipeline operation has been designed using the design tool, the workflow 200 terminates with a consolidation and output step 230. During this step, the afore-mentioned work product outputs (including but not limited to an operational diagram and schedule, task list, materials list, and list of actions or procedures to be followed during the operation) are generated and output to the user 108 and / or the third-party system 120. As part of this final step 230 (or as an optional additional step), the computing system 100 can also ensure that any learnings derived from the design procedure are updated within the databases 114a, 114b and / or the instructions 105 stored in the memory 104. The computing system 100 and design workflow 200 that constitute the design tool allow the design for a pipeline operational procedure to be simplified. In particular, the provision of the above-described interactive input and visualisation aspects of the design tool beneficially guide the user 108 in designing a pipeline composition having optimised configuration, properties and parameters for use in a plurality of operational processes. Moreover, the modular and interactive nature of the user interface 106 implemented by the computing system 100, in combination with the ability of the computing system 100 to store information regarding previous pipeline operations, reduces the amount of user (specialist) knowledge that is required during a given design project. This in turn means that the design tool simplifies the entire modelling and design process, and requires less experienced and / or fewer users, as well as less time being dedicated in total to this process. The quality of the results obtained are nevertheless maintained by the functionality of the design tool. As a result, the overall efficiency of the operational design process is improved, without sacrificing the quality of the end product. Additionally, the design tool is effectively ‘self-learning’ as it incorporates learnings / teachings, conclusions and updated information from previous projects and previous designs as a result of certain feedback aspects. The design tool therefore ensures that the most up-to-date information can be used during the operational design process, allowing the results to be generated with improved efficiency and accuracy. A robust database of stored pipeline composition data and operational process data is also built and maintained. As a result, the design tool essentially incorporates the knowledge, ability and skill of a large number of experienced engineers into its functionality. The design tool is therefore invaluable to both experienced engineers (saving them time during the design process), as well as to inexperienced engineers (reducing the learning curve required to take part in the design process). Figure 3 illustrates a snapshot of an example GUI display 300 that can be displayed via the user interface 106 - it shows an example implementation of the icons 110 that are used during the design workflow 200. It should be appreciated that the icons shown and described in relation to this figure (and subsequent figures), are merely one illustrative example of how the design tool functionality provided by the computing system 100 may be implemented. The scope of the current application should not be limited to this example implementation, and other implementation mechanisms (e.g., different types and groupings of icons) may be possible without altering the underlying functionality. A plurality of icons are shown on the display 300 and can be interacted with by the user 108. The majority of these icons can be categorised into three main groups based on their associated functionality: (1) an ‘Initial Inputs’ group 300a; (2) a ‘Calculation’ group 300b; and (3) an ‘Elaboration’ group 300c, as illustrated in Figure 3. The first ‘Initial Inputs’ group of icons 300a provides the overall functionality of receiving, storing and processing basic input data from the user 108: this includes both large-scale (global) properties of the pipeline operation that is undergoing design; as well as the more detailed information in relation to the pipeline composition and the operational processes that are to be performed. This input data defines the scope of the calculations, analyses and modelling that the computing system 100 carries out thereafter. The functionality provided via this group of icons corresponds primarily to the functionality of the ‘set up’ module 122a, the ‘initialisation’ module 122b, and the ‘visualisation’ module 122c as was described above. This first group of icons 300a includes an ‘Initial Data’ icon 302, a ‘Project Inputs’ icon 304, a ‘Project Diagram’ icon 306 and a ‘Platform Inputs’ icon 308. The user typically interacts with some or all of this group of icons during steps 205 and 210 in the ‘set-up’ phase A of the process 200. The user 108 primarily interacts with the ‘Initial Data’ icon 302, the ‘Project Inputs’ icon 304 and the ‘Platform Inputs’ icon 308 to provide general (basic) input parameters and properties about the desired pipeline operation. For example: the project name, contributors; permissions I accessibility; operational vessel type; the service provider who will be carrying out the operation; the type of platform to be used; and the type of operation that will be carried out. In steps 215a, 215b, the user 108 primarily interacts with the ‘Project Inputs’ icon 304 and the ‘Project Diagram’ icon 306 to input the additional detailed information required. This additional information includes but is not limited to the following: (a) The type of pipeline(s) being handled during the procedure: for example, a gas injection line, gas lift line, oil export line, production pipeline or umbilical. (b) The type of operational procedure: for example, installation, demobilization or some combination of the two. (c) The form of the pipeline being handled: for example, whether a lazy wave is desired, and if so the amount and type of buoyancy required (and how the buoys would be configured to achieve the desired pipeline shape); the number of portions of pipeline desired (quantity of pipe sections); the lengths of each of the pipe sections; physical properties of each of the pipe sections (weights, bending stiffness, friction factor with the soil). (d) The scope of the operations occurring at the two ends of the pipeline: for example, vertical connection or disconnection, pull-in, pull-out, abandonment, recovery, horizontal connection or disconnection; as well as defining what entities the pipeline will be connected to during the operation, e.g., a well or a platform; (e) Conditions at the operation location: for example, water depth; and (f) Details of each of the components that will be involved in the operational process and their associated properties: for example, the structures and accessories (such as stiffeners, end fittings, restrictors and anchorage collars) and / or pieces of equipment (e.g., vertical and horizontal connection modules VCM and HCM, in-line valves). An example of the interactions that the user 108 can carry out with the computing system 100 via the ‘Project Inputs’ icon 304 is shown in Figure 4, which illustrates the information that the GUI display 300 can request (and receive) from the user 108. The specific illustrated example relates to defining details of a particular piece of equipment (in this case, a VCM or Vertical Connection Module) that will be used during an installation operation. All the information that is input by the user 108 to the user interface 106 when interacting with the icon 304 is stored in the databases 114a, 114b in association with the particular pipeline operation that the user is designing, as well as in association with that component or piece of equipment. In such instances, a corresponding component or equipment identifier can additionally be defined and stored in association with each component or piece of equipment. This identifier can then be displayed to the user 108 via the user interface 106, and also be used to identify the appropriate information to be retrieved once selected by the user 108. In other words, the information associated with any component or piece of equipment can be stored, processed and retrieved in a modular fashion, with any given component or equipment corresponding to a ‘module’ or section of the overall pipeline that can be handled and managed separately from other sections. As noted in Figure 4, this enables an ‘Equipment Registry’ or directory of pipeline components, equipment and their properties to be built up within the databases 114a, 114b for subsequent retrieval. Thereafter, if the same component or piece of equipment having the same or similar properties is desired to be used in a different operation, the computing system 100 will be able to identify this component or piece of equipment (based on the identifier and the associated properties of the equipment as stored in the databases 114a, 114b). The computing system 100 will be able to retrieve and present this equipment to the user 108 via the GUI display 300 for selection and inclusion in the newly defined operation. The design tool therefore builds upon any and all data that has been stored by users when designing previous operations. This functionality minimises the additional time and effort for users when designing any given pipeline operation, as well as the amount of processing that needs to be performed by the computing system 100. The ‘Project Diagram’ icon 306 is able to provide interactive visualisation functionality to the user 108 in relation to the overall pipeline composition design. This is illustrated in Figure 5 which shows the information 500 that can be displayed to the user 108 via the user interface 106 during interaction with this icon. As shown in Figure 5, a diagram 505 of a specific section of the overall pipeline composition that is proposed for an installation operation is displayed, along with the constituent components, accessories and pieces of equipment making up and associated with that specific section. These components, accessories and equipment are displayed in the diagram 505 in the specific sequence and location that was defined by the user as described above. In the illustrated example, the specific section corresponds to one of a plurality of pipe sections that will make up the overall pipeline composition. A corresponding list 510 of the plurality of individual pipe sections is also displayed to the user in an interactive manner. The user 108 can alter which pipe section is displayed in the diagram 505 by selecting a different one of the pipe sections in the list 510. For each pipe section in the list 510, three additional corresponding lists 515, 520, 525 are also displayed: a first list 515 (shown on the left-hand side) illustrating the connectors associated with that pipe section; a second list 520 (shown in the middle) illustrating the accessories associated with that pipe section; and a third list 525 (shown on the righthand side) illustrating the equipment associated with that pipe section. The user 108 can edit any or all of the displayed lists 510, 515, 520, 525 in an interactive manner to alter the properties of the individual components or equipment, and / or to change the order of these components or equipment within the pipeline composition design. The data associated with the lists 510, 515, 520, 525 are then used by the computing system 100 to generate the pipeline composition diagram 505. As such, edits to the lists 510, 515, 520, 525 will cause the corresponding pipeline composition diagram 505 to update accordingly (in realtime) to reflect these changes as they are made by the user 108. The combination of the functionalities provided by this set of icons 300a - involving the initial receipt, processing and visualisation of pipeline related information I data - creates an easily understandable and user-friendly interface that allows for a seamless and efficient pipeline operation design process. The user 108 is also able to make their changes directly by inputting information to the user interface 106, and then can immediately visualise the physical effects that their changes have upon the final pipeline composition design. Additionally, the visualisation functionality allows the user 108 to see the appropriate data for each component when in its intended implementation context. This in turn means that the user 108 can identify issues that might arise in the intended implementation context; they might otherwise miss these issues when merely looking at raw data or assessing any given component or pipe section in isolation. Moreover, if it is determined that some information associated with one of the components is incorrect, or that that component has been defined in an inappropriate location within the overall pipeline composition design, the above-described interactive editing functionality for any given component means that the user 108 does not need to repeat all the data entry steps for other components of the pipeline to make the necessary corrections and alter the final result. Turning now to the second ‘Calculation’ group of icons 300b, user-interaction with this icon group achieves overall functionality relating to analysis of input information regarding the pipeline operational process design. Additional functionality is achieved, based on the application of engineering modelling and calculations, relating to provision of information to the user 108 regarding the suitability of the proposed pipeline composition design as well as the proposed operational process design. The functionality provided via this group of icons 300b corresponds primarily to the functionality of the ‘visualisation’ module 122c and the ‘calculation’ module 122d. This group of icons 300b includes a ‘Catenary Loads' icon 310, a ‘Torque’ icon 311, a ‘Tensioners Settings’ icon 312, an ‘Inserts’ icon 313, an ‘Anchorage’ icon 314, a ‘Sea State’ icon 315, and the ‘Second End Pull-in’ icon 316. The user typically interacts with this group of icons during the calculation and analysis phase B in steps 220 and 225 of the workflow 200. Prior to using these icons, the user 108 will typically have been able to define the scope of the operational procedure. As noted above, this will have involved the user 108 interacting with the ‘Initial Inputs’ group of icons 300a - usually at least the ‘Project Inputs’ icon 304, the ‘Project Diagram’ icon 206 and the ‘Platform Inputs’ icon 308 (if appropriate) - to define the operational processes that will be implemented in relation to the first and second ends of the pipeline. Figures 6 and 7 illustrate interactive interfaces 600, 700 which are displayed by the user interface 106 when the user 108 interacts with the ‘Second End Pull-in’ icon 316. For context, as the skilled person will be aware, a ‘Second End Pull-in’ is an operational process that occurs towards the end of a pipeline installation, and specifically occurs when the installation involves an FPSO (Floating Production, Storage and Offloading) vessel or platform. In this process, the second end of the pipeline (i.e., the end that is not attached at the seabed) is ‘pulled in’ to the FPSO using a winch, and connected to the FPSO so as to transfer pipeline fluids to the FPSO. In more detail, as shown in the GUI display 600 of Figure 6, examples of certain pieces of operational input data 602 relating to properties of the (FPSO) platform and the winch implementing the pull-in process are requested from the user 108. The received operational input data 602 are combined, by the computing system 100, with other pieces of (stored) data relating to the pipeline composition itself (e.g., received during the earlier steps 205 to 215 of the workflow). This combined data is analysed by the calculation module 122d, and engineering modelling and calculations are carried out to determine output parameters defining the pull-in process (e.g., how much pipeline to pull in and over what timescales; what angles and tension should be achieved). In order to implement the necessary calculations, the calculation module 122d may itself call one or more functional modules that are pre-programmed with the necessary functions and equations to perform the calculations. As noted previously, these functional modules may include software solutions provided by existing software providers, such as the OrcaFlex™ software solutions. When providing the input to the functional modules, the computing system 100 may need to reformat and / or rearrange the received data into a form that is compatible with the existing software solutions. As shown in Figure 7, guidance outputs 702, 704 can be provided to the user 108 by the computing system 100, as part of the analysis step 225 and following interaction with the GUI display 600 described above. Specifically, automated lay tables can be generated and displayed to the user 108 via the user interface 106 - an example GUI display 700 shows these lay tables. The skilled person will be aware of what lay tables are in the context of second end pull-in operations. To summarise: various pipeline configurations are modelled by the computing system 100 to determine the range of top tension values within which the pipeline operation can proceed, and the displayed lay tables 702, 704 illustrate a range of possible pipeline configurations that are determined as a result of the modelling (and in which acceptable and unacceptable cases can be indicated). In other words, the lay tables essentially encompass a set of processes or instructions, that would be provided to the FPSO during the operation, and include actions that are to be taken by the FPSO (e.g., pay out or take in X amount of pipeline length at Y water depth). The object of this modelling using the lay tables is to identify certain pipeline configurations (and hence the corresponding instructions that would result in such configurations) that meet one or more predefined restrictions or criteria. These criteria are defined such that certain physical conditions or properties of the pipeline are maintained during the course of the operational process(es) - for example, as noted above, ensuring that a transfer angle is within an appropriate range and outputting an alert 604 if it is determined that this is not the case. As a result, consequential breakages and fatigue of the pipeline and equipment can be avoided during the actual operation. The generation of the lay tables (displayed in an interactive manner via the GUI display 700) enables the modelled pipeline configurations to be automatically assessed against the one or more predefined criteria, and the subset of acceptable pipeline configurations to be presented to the user 108 for visual confirmation. The user 108 can therefore more easily identify and approve acceptable pipeline operational configurations, making the design process more efficient and streamlined: a result that would usually take an experienced engineer several days to model and analyse now takes just minutes or hours. Now turning to Figures 8 and 9, these illustrate interactive GUI displays 800, 900 which are displayed by the user interface 106 when the user 108 interacts with the ‘Catenary Loads’ icon 310. In more detail, as shown in Figure 8, a plurality of individual steps 802a, 802b that take place within the overall pipeline operation are displayed to the user 108 via the GUI display 800. In this example, the operation is a pipeline installation and each of these steps 802a, 802b corresponds to the launching or laying of a specific portion of the pipeline composition (e.g., a pipe section). Each step therefore has associated with it certain physical properties and parameters that correspond to that specific portion of the pipeline composition (e.g., pipe section length, laying equipment, water depth, launched length, launching angle etc) that need to be assessed for implementation. Based on those steps 802a, 802b and their associated information, the calculation and visualisation modules 122c, 122d of the computing system 100 can model and output information to the user 108 (via the graphical user interface 106). More specifically, information relating to the resulting pipeline catenary that will be generated following each step 802a, 802b can be output. Examples of these are shown in Figure 9 as interactive catenary load visualisations. As the skilled person will be aware, the catenary load visualisations relate to angles and loads that result from the paying out of the pipeline, combined with movements of the vessel, during the operational procedure. As shown in Figure 9, catenary loads corresponding to each step 802a, 802b are output via an interactive visualisation mechanism on the GUI display 900a. The display 900a shows individual steps 902 involved in the operational procedure, each step 902 corresponding to one of the steps 802a, 802b that were shown in the GUI display 800. Via the GUI display 900a, the user 108 can select any single step 902 or combination of steps, and interactively determine the catenary loads and angle / declination (and other properties) associated with that step or steps 902. These details are also interactively displayed to the user on the GUI display 900a via an information box 904 having contents that change depending on the step(s) that is I are selected. Based on the information that is derived from these interactions in relation to the displayed step 902 in the GUI display 900a, the user 108 may consider alterations that should be made to a corresponding one or more steps 802a, 802b from the GUI display 800. These alterations would be intended to optimise the resulting catenary loads and / or to avoid undesirable loads being placed upon sections of the pipeline. Figure 9 shows an alternative GUI display 900b that can be implemented which displays information in relation to a double catenary configuration. As the skilled person will be aware, in a single catenary configuration (such as that shown in the GUI display 900a), only one end of the pipeline catenary is attached at the surface and the other end remains along the seabed. By contrast, a double catenary configuration involves both ends of the pipeline being attached at the surface (e.g., to a vessel and an FPSO). As discussed above in relation to the GUI display 900a, the catenary loads and declination associated with any given operational step or steps 802a, 802b (defined in GUI display 800) can be displayed in the GUI display 900b. However, additional functionality is associated with the visualisation of the double catenary in the GUI display 900b in view of the increased number of potential issues that may need to be addressed in the context of double catenary installation: as both ends of the pipeline are attached to surface equipment, the corresponding curvature I bending of the pipeline can cause more extreme loading on certain pipeline sections. More specifically, any potentially undesirable loading or bending resulting from the defined steps can be identified by the computing system 100. A variety of pipeline configurations 910 created as a result of the operational processes are visualised in the GUI display 900b, and a corresponding alert 915 is output to the user 108 where it is necessary to indicate to the user 108 that there are issues arising from the pipeline configuration(s) which may be detrimental to the pipeline installation. More specifically, as shown in the GUI display 900b, the computing system 100 provides indications 920 that is has detected the presence of some connections between components located in the sag bend portion of the catenary. The computing system 100 has also identified that this configuration can lead to issues with the curvature of the pipeline, as potentially undesirable tensions or forces may be placed on certain components in the pipeline causing them to be at or beyond their design tolerance. The computing system 100 has therefore output a warning in the alert section 915 of the GUI display 900b. It is beneficial to avoid these undesirable tensions or forces being generated to avoid unnecessarily fatiguing the pipeline, which would in turn reduce the working lifetime of the pipeline. In extreme cases, it may cause damage to the pipeline and its associated equipment. The functionality provided by the computing system 100 (e.g., via the ‘Catenary Loads’ icon 310 and the functional modules 122c, 122d) is therefore of great technical advantage, since it allows undesirable pipeline configurations to be quickly and clearly identified. The computing system 100 also automatically provides a proposed solution as part of its alert section 915 such that the user 108 is guided in taking appropriate action to address the issues which have been detected (e.g., via altering the information input or defined via the GUI display 800). The proposed solutions may be at least partially derived from data that has been received or generated by the computing system 100 during previous operational design projects: the computing system 100 may have learnt that certain configurations lead to undesirable results and that certain alterations can address this. As such, the design tool simplifies the design process, whilst also making it more robust as it reduces the potential for human error. One or more predefined criteria associated with properties of the pipeline composition can be defined to govern this process; and it is envisaged that eventually the computing system 100 may even automatically take certain actions on its own without requiring specific input from the user 108. The computing system 100 is also configured to generate one or more operational state files for output and display to the user 108. For example, the computing system 100 may generate a ‘sea state table’, in relation to the different steps 802a, 802b, which includes critical conditions applicable to each of the steps. As the skilled person will be aware, the loads placed upon a pipeline during operations are dependent upon the movement of the vessel to which the pipeline is connected during the operations. The vessel movements are in turn determined by the wave movements in the geographical location of the operation. Sea state tables are an industry-standardised mechanism for characterising wave movements in a particular location, and typically include information relating to a statistical average of (expected) wave movements in that location. As such, sea state tables contain information that allow a subsea engineer to ascertain the maximum allowable sea state ranges within which a particular operation can be performed. These ranges will typically correspond to sea states in which critical parameters of the pipeline (e.g., loads and bending of the pipeline) still remain within acceptable ranges or tolerances. Such acceptable ranges or tolerances will be dependent upon many factors, including the vessel’s reaction to the wave movements, the type of operation, the pipeline composition (pipeline components and equipment used), and the pipeline configurations that will be generated as a result of the operational processes performed. In some instances, once the sea state tables are generated, their contents may be analysed by the computing system 100 and compared with the expected conditions at the desired operational location. Furthermore, based on this comparison, automatic outcomes (e.g., ‘Go’ or ‘No Go’) can be output to the operational team at the location (e.g., directly via the interface 118, or indirectly via the user interface 106). The design tool therefore provides automatic modelling, assessment and action in relation to clearing operational procedures to be performed, in addition to the substantive operational procedure design described above. In some cases, in view of the differing wave conditions in different geographical locations, the computing system 100 may be configured to model the sea state according to a variety of underlying sea models and parameters. The information required for this modelling will be preprogrammed into the computing system 100 (e.g., into the instructions 105 and / or the databases 114a, 114b). The sea state determination and the subsequent output of the sea state tables can be accessed as part of one of the existing icons 110 in the user interface 16 (e.g., via the ‘Catenary loads’ icon 310). Alternatively, the corresponding functionality can be accessed via user interaction with a separate icon displayed directly on the GUI display 300 - for example, the ‘Sea State’ icon 315. Turning to Figures 10 and 11, these illustrate example interactive GUI displays 1000, 1100 which are displayed by the user interface 106 when the user 108 interacts with the ‘Tensioners Settings’ icon 312. As the skilled person will be aware, tensioners are typically used on board pipelaying vessels to maintain tension in the pipeline, and primarily during a pipeline installation process. In more detail, tensioners comprise tracks that apply pressure to the pipeline, holding the pipeline in place via the use of frictional forces. The tensioner settings can be altered to adjust the amount of pressure applied, and thereby control whether the pipeline can be paid out (and if so, the rate at which this occurs). A delicate balance must be maintained in relation to the tensioner pressure settings: sufficient pressure is required to control the pipeline and the rate at which it is paid out; however, too much pressure may potentially damage or fatigue the pipeline, with the attendant negative consequences for the operation and the pipeline lifetime. It is therefore important to ensure that the appropriate tensioner settings are determined in relation to each section of the pipeline and each stage of the operational procedure. The GUI display 1000 in Figure 10 shows detailed information defining the tensioner properties and requirements for each portion of the pipeline (e.g., in relation to each component or piece of equipment associated with the individual pipe sections). A series of operational inputs 1005, 1010, 1015 that are used to calculate the tensioner requirements can be input and defined by the user 108 via the GUI display 1000. Interactive columns 1020, 1025 are provided that, when selected, can provide the user 108 with additional information about the intended tensioner settings, and indicate whether any issues are expected to arise as a result. The GUI display 1100 in Figure 11 shows an example breakdown of the tensioner settings that have been calculated for each section of the pipeline (effectively an expansion of the columns 1020, 1025 in the GUI display 1000), along with an indication of any issues that may arise based on the settings and operational inputs that were provided. As illustrated in Figure 11, the settings which have been derived based on the information input to the interface 1000 all appear to result in an acceptable outcome for the pipeline. Specifically, the rightmost column 1105 indicates that all of the settings are acceptable (an ‘OK’ in that column), whilst the other columns 1110, 1115, 1120 provide context for why this result has been derived. More specifically, the leftmost column 1110 indicates a tensioner setting, the next column 1115 indicates the derived or defined value selected for that setting, and the subsequent column 1120 indicates how that value compares against one or more predefined criteria that will allow the resulting tensioner setting to fall within a range of acceptable values. As noted above, the outputs in this interface 1100 are calculated based on the input data provided via the GUI display 1000. The outputs may also take into account stored data that has been retrieved from the databases 114a, 114b relating to the operation and the pipeline, and processed and analysed using the instructions 105. A brief description of the ‘Torque’ icon 311, the ‘Inserts’ icons 313 and the ‘Anchorage’ icon 314 will also now be provided. The functionality associated with the ‘Torque’ icon is accessed in instances where it is desirable to perform flanged connections between adjacent pipe sections in the pipeline composition. In those instances, the ‘Torque’ icon 311 can be used to determine the required pressure in certain torque tools that will be used to perform the connections. A torque value and a (amount of a) lubricant to be applied in the pipe can be input when utilising this icon and can be taken into account when determined the required pressure. With regard to the ‘Inserts’ icon 313, the associated functionality is accessed in instances where it is desired to utilise hang-off (steel) structures that will be used to support pipe sections at a vessel working table. More specifically, the software associated with the ‘Inserts’ icon 313 is configured to utilise input data, regarding dimensions of pipe connectors and allowable design loads, to design these hang-off structures. Examples where such functionality may be desired include operational procedures where the crew of the vessel need to work on the extremities of the pipe section (e.g., for accessory and / or equipment installation) or perform flanged connections between the pipe sections. The databases 114a, 114b may contain appropriate information relating to the components that are utilised in these calculations and designs. The databases 114a, 114b may be updated as required to ensure that information contained therein is up-to-date and accurate (e.g., updates may be carried out when new accessory I equipment items are manufactured). The functionality associated with the ‘Anchorage’ icon 314 is accessed in instances where the pipeline is being ‘pulled in’ to an FPSO vessel or platform. The functionality relates to anchorage features of the seabed end of the pipeline, and specifically to the interplay between the anchorage and the pulling in of the other end of the pipeline. The ‘Anchorage’ icon 314 can be used to determine, for example, whether the modelled pipe angle (relative to the vessel) during the pulling in process needs to be changed; and / or if additional steps need to be taken in relation to the anchorage itself to compensate for the movement of the other end of the pipeline. For example, whether it is necessary to implement additional securing anchors at various points to prevent the pipeline from moving substantively on the seabed. In order to access the functionality of this icon 314, as with the other icons in this group, input data is received by the computing system 100 from the user 108 via the user interface 106. This data may include, for example, details of the pipeline, its intended movement and intended anchorage mechanism. The functionality of the calculation module 122c is then utilised, which in turn can draw upon functional modules of preprogrammed software solutions (e.g., OrcaFlex™) as necessary. A brief description of the third group of ‘Elaboration’ icons 300c will now be provided, with reference to Figures 12 to 14. User-interaction with this icon group 300c achieves the overall functionality of: (i) consolidating all of the information that has been input by the user 108 thus far to the design tool, with the information that has been calculated and modelled by the design tool; and (ii) outputting a plurality of work products defining the implementation of a finalised pipeline operational procedure design. The functionality provided via this group of icons 300c corresponds primarily to the functionality of the ‘visualisation’ module 122c and the ‘output and conclusions’ module 122e. This third group of icons includes a ‘Schedule’ icon 318, a ‘Task Plan’ icon 320, a ‘Material List icon 322, a ‘Procedure text icon 324 and an ‘Installation Diagram’ icon 326. The user typically interacts with this group of icons during the final step 230 of the pipeline operation design workflow 200. The plurality of work products that are generated and output via interaction with the ‘Elaboration’ group of icons 300c consolidate key results of the calculations that have been performed thus far by the computing system 100 during the design process. These work products are provided to the user 108 and / or the third-party service provider remote server 120. As illustrated in Figure 12, an ‘Operational Diagram’ 1200 is generated and output to the user 108 following interaction with the ‘Installation Diagram’ icon 326. This ‘Operational Diagram’ comprises an overall summary portion 1205 and a visualisation portion 1210, relating to certain aspects of the final pipeline operational procedure design. The GUI display 300 presents this icon specifically in relation to installation operations, but it should be understood that the functionality of this icon can be generalised for application to all types of pipeline operations (and may also therefore be renamed accordingly as appropriate). The summary portion 1205 includes an indication of the final pipeline composition design. It comprises a detailed (written) breakdown of all of the components, structures and accessories that will form part of the pipeline and the equipment that will be used during the operation, along with the associated properties and parameters of each component and piece of equipment. The summary portion 1205 also comprises information relating to the operation that would typically need to be communicated to the deck crew of the operation vessel(s). It therefore includes specific information about which components are to be connected together and how (e.g., fasteners and pressures used; and test parameters to be used to test the robustness of the connections). On-deck installation information and instructions can also be provided as part of the summary portion 1205. For example, as shown in Figure 12, the information provided in the summary portion 1205 includes but is not limited to: physical parameters (e.g. weight) of each component; torques for flanged connectors; the maximum loads for each section of the pipeline; tensioner settings for each section of the pipeline; lubricants and test pressures to be used. One or more diagrams I visualisations of the corresponding final design for (a portion of) the pipeline composition are also generated and can be displayed in the visualisation portion 1210. These diagrams include an indication of the modular breakdown of the components that will constitute (that portion of) the final pipeline composition. This is illustrated in Figure 12, where details of one of the pipe sections is shown. The ‘Operational Diagram’ 1200 as a whole may be colour coded in a manner that allows for the correct information breakdown in the summary portion 1205 to be associated with the correct component displayed in the visualisation portion 1210 - i.e., the detailed information for each component is presented with a colour coding that matches the corresponding component in the diagram - and thereby improves accessibility of the information contained therein. The information used to generate the ‘Operational Diagram’ 1200 is derived from the input data from the user, in combination with the subsequent analyses and modelling carried out by the computing system 100 using the instructions 105; and optionally, utilising stored data from previous operations. These instructions 105 are programmed to associate specific actions, modules and combinations of pipeline components and equipment, and their corresponding properties and parameters, with one another; and to assess all of this information against one or more sets of predefined criteria. These criteria are themselves defined based on feedback and knowledge from corresponding data stored in relation to similar operations implemented previously. The creation and output of the ‘Operational Diagram’ 1200 and its constituent information is therefore advantageous from an efficiency point of view: such information would typically require many engineers working for multiple days to generate, but can now be produced in a matter of hours by just one or two engineers using the functionality embodied by the design tool. Moreover, the fact that this information is generated automatically based on predefined rules and criteria eliminates (or at least minimises) human input and error. The instructions 105 and criteria can also be periodically updated to take into account learnings from any given completed operation for future use. An accompanying breakdown list of the materials that will be required to produce the final pipeline composition design is also generated following user interaction with the ‘Materials List icon 322. The list is generated based on the components that have been determined to constitute the final pipeline composition design. In order to generate this list of materials, the databases 114a, 114b and instructions 105 are preprogrammed to store each pipeline component and piece of equipment in association with the appropriate accessories that are needed to physically construct the pipeline. The defined combinations of components and accessories used to derive the pipeline composition are identified and retrieved by the computing system 100, and this data is consolidated into a ‘Materials List’ by the consolidation module 122e. Some or all of this stored data can be received from the data sources 112a, 112b, 112c which may correspond to the third-party system 120 who may be the operational service provider. Information contained in the ‘Materials List’ breakdown includes but is not limited to the following: details of the fasteners that will be required (e.g., studs, bolts); details of any accessory materials (e.g., lubricant, sealing rings); as well as information regarding the equipment and components defining the overall pipeline composition. The information in the ‘Materials List’ breakdown may be displayed to the user via the graphical user interface 106; and may additionally also be provided to the third-party system 120 so that they can prepare appropriately for the pipeline operation. Moreover, the ‘Materials List’ that is generated can be formatted appropriately and transmitted to the third-party system 120 in a form that can be easily read by a corresponding service provider computing system, for example via an API. This formatting and transmission may be programmed to occur automatically. A ‘Procedure Text’ document 1300 comprising a detailed breakdown of all of the steps and processes that will need to be implemented during the pipeline operation can also be generated by the computing system 100, following user interaction with the ‘Procedure Text icon 324. Information contained in the Procedure Text includes but is not limited to the following: (i) the scope of work that will be involved in implementing the final pipeline operational processes design; (ii) a breakdown of each of the components (pipe sections), connectors and accessories that will be included in the final pipeline composition design; and (iii) an accompanying set of characterising properties and parameters associated with each component, connector and accessory. An example of this latter piece of information (iii) is illustrated in Figure 13 for one component of a riser pipeline. A corresponding page of such information will be generated for every component forming the final pipeline composition design. Figure 14 illustrates an example of a ‘Schedule’ work product 1400 that is generated and output to the user 108 following interaction with the ‘Schedule’ icon 318. This work product 1400 sets out a logical sequence of high-level tasks 1405 that are required to implement various stages of the pipeline operation, from start to finish, with each high level task 1405 being broken down further into individual sub-tasks 1410 corresponding to individual operational steps, processes or actions. For example, in the case of pipeline installation, each sub-task may correspond to a step of installing one or more accessories, preparing for a first-end pull-in etc. Additionally, the ‘Schedule’ 1400 includes an associated indication of the approximate duration 1415 for implementation of the sub-task in question. Finally, although not shown, a ‘Task Plan’ document comprising a breakdown of the tasks that will need to be carried out in order to implement the final pipeline operational procedure design can also be generated by the computing system 100, following user interaction with the ‘Task Plan’ icon 320. The information contained in the ‘Task Plan’ includes but is not limited to: a step-by-step breakdown of all of the tasks that needs to be completed; and an indication of where responsibilities lie for completing each of the tasks. Text that is generated in relation to each of the above-described work products can be stored (as separate text strings) in the databases 114a, 114b. These text strings can be combined as desired to generate the various components of each work product using preprogrammed rules based on the instructions 105. These rules ensure that the correct combination of components, tasks, instructions and timings (if appropriate) are consolidated and output in each work product. The data sources 112a, 112b, 112c were arranged to provide at least some of this information to the computing system; and may therefore correspond to experienced engineers or third-party service providers who have maintained or developed this stored text data based on the information and learnings gleaned from experience with past pipeline operations. An initial bank of text data may therefore be stored (in databases 114a, 114b) as part of a setup or initialisation phase of the workflow 200 by the computing system 100, in communication with any or all of the data sources 112a, 112b, 112c. The stored text data may thereafter be updated periodically and on-demand, where the stored data is added to or altered based on new learnings or updates in more recent operations. Advice derived based on practical experience in operational design and implementation can also be stored in the databases 114a, 114b, in association with certain aspects of the pipeline design. This allows the real-world experience of subsea engineers to be made automatically and centrally available to subsequent users of the design tool. The tool itself can also automatically make use of this experience and advice when implementing the calculation, modelling and consolidation functionalities. In summary, the automatically generated work products of the design tool encompass all of the information that would be needed to practically plan and implement any given operation. The computing system 100 therefore minimises the amount of human input that is required to generate these results / products, and hence not only is the efficiency of the work product generation increased but the possibility of human error being introduced is also decreased. As such, the results can be quickly and confidently implemented in a real-world operational scenario. Once the user 108 has designed an operational procedure ‘plan’ using the computing system 100 to implement the design tool and its corresponding workflow, this ‘plan’ can then be implemented to enable a ‘real-world’ operational procedure (e.g., a pipeline installation operation) to be carried out. This real-world implementation of the plan may make use of the above-described plurality of work products that are generated, and include practical implementation actions that should be taken. For example, actions that may be required prior to implementation of the plan may be carried out: e.g., sourcing and obtaining any and all of the components, accessories and equipment necessary as defined by the work products; constructing any portions or sections of the final pipeline composition design that may be required; and loading all portions, sections, components, accessories and equipment onto the vessel(s) to be carried to the operational location. The real-world implementation of the plan may also involve, once the vessel(s) are at the operational location, implementing the operational procedure according to the plan, and using the work products that have been generated as descried hereinabove. This final ‘real-world’ implementation may correspond to an extension of the workflow 200 of Figure 2. Some or all of this process of using the designed plan may be carried out by the third-party service provider 120. Many other variations are possible within the inventive concept. For example, it is noted that during pipeline demobilisation operations, the icon that is used may be labelled differently. Specifically, the ‘Second End Pull-in’ icon 316 may instead be relabelled as a ‘Pull-out icon. The functionality of this icon may also be altered to be directed towards the specifics of how to handle a pull-out operation - where the pipeline is disconnected from an FPSO and winched away back to the vessel - rather than a pull-in operation (where the opposite action is taken).

Claims

1. A computer-implemented design tool arranged to design an operational procedure for a subsea pipeline, the design tool comprising:at least one input configured to receive input data from a user relating to the operational procedure, the input data comprising:(i) pipeline composition data defining a plurality of pipeline components forming the subsea pipeline and associated equipment for use in the operational procedure; and(ii) operational process data comprising a plurality of operational parameters defining a plurality of operational processes carried out to implement the operational procedure;at least one processor and an operatively coupled memory, the memory being programmed with instructions that when executed cause the at least one processor to:generate a proposed design for the subsea pipeline and for the operational procedure based on the received pipeline composition data and operational process data;calculate one or more sets of properties of the proposed design for the subsea pipeline and / or the operational procedure;for each of the one or more sets of properties:determine whether the set of properties meets a predefined criterion for one or more of the plurality of operational processes to be successfully performed;display, via an interactive user interface to the user, the set of properties, in association with an indication of whether the set of properties meets the predefined criterion;in dependence on the predefined criterion not being met, (i) request updated input pipeline composition data and / or operational process data from the user, (ii) generate an updated proposed design for the subsea pipeline and / or for the operational procedure based on the received updated input data, and (iii) re-perform the preceding calculation, determination and display functions until the predefined criterion is met; andin dependence on the predefined criteria being met, (i) determine a final operational procedure design based on the updated proposed design for the subsea pipeline and for the operational procedure, and (ii) generate at least one work product relating to implementation of the final operational procedure design; andat least one output configured to output, to the user, the at least one work product.

2. The design tool according to claim 1, wherein the operational procedure corresponds to a pipeline installation and / or a pipeline demobilisation.

3. The design tool of claim 1 or claim 2, wherein the subsea pipeline is flexible.

4. The design tool of any preceding claim, wherein the predefined criterioncorresponds to whether the set of properties lies within an acceptable range of values that avoids causing fatigue and / or damage to the subsea pipeline during the operational procedure.

5. The design tool of any preceding claim, wherein the plurality of operational processes comprise any one or more of the following processes occurring at first and / or second ends of the subsea pipeline during the course of the operational procedure: a vertical connection or disconnection, a pull-in, a pull-out, an abandonment, a recovery, a horizontal connection or disconnection; a connection or disconnection to a well and / or seabed storage; or a connection or disconnection to a surface platform and / or vessel.

6. The design tool of any preceding claim, wherein the plurality of operational parameters define any combination of the following: (i) water depth at a location of the operational procedure; (ii) water movement at the location of the operational procedure; (iii) properties of a vessel to be used during the operational procedure; or (iv) actions to be taken during one of the plurality of operational processes.

7. The design tool of any preceding claim, wherein the pipeline composition data comprises any one or more of the following: (i) a type of the subsea pipeline; (ii) a proposed form of the subsea pipeline to be achieved during the operational procedure; (iii) properties of one or more accessories and / or pieces of equipment that will form part of the subsea pipeline or be used during the operational procedure.

8. The design tool of any preceding claim, wherein the request for updated input pipeline composition data and / or operational process data from the user comprises: (a) information that enables the user to determine why the predefined criterion has not been met, and / or (b) instructions for the user to update the pipeline composition data and / or operational process data to ensure the predefined criterion is met.

9. The design tool of any preceding claim, wherein the one or more sets of properties relate to any of the following: (i) loads on a pipeline catenary during the operational procedure; (ii) pressure exerted by one or more tensioners during the operational procedure; (iii) wave movements experienced during the operational procedure; or (iv) a transfer angle of the subsea pipeline during the operational procedure.

10. The design tool of any preceding claim, wherein the at least one work product comprises an operational diagram comprising information and instructions about the pipeline composition and the plurality of operational processes associated with the final design for the pipeline operational procedure.

11. The design tool of any preceding claim, wherein the at least one work productcomprises a materials list defining the pipeline components, accessories and equipment to be used during implementation of the final design for the operational procedure.

12. The design tool of any preceding claim, wherein the at least one work product comprises a plurality of lay table diagrams, each lay table diagram comprising:an indication of a pipeline configuration that may be generated during one or more of the plurality of operational processes; andan associated indication of whether the pipeline configuration would enable the corresponding one or more operational processes to be successfully performed.

13. The design tool of any preceding claim, wherein the at least one work product comprises a plurality of sea state tables, each sea state table comprising an indication of wave movement in a location of one of the plurality of operational processes that would enable the corresponding operational process to be successfully performed.

14. The design tool of any preceding claim, wherein the at least one work product comprises a set of instructions defining a workflow to be followed when implementing each of the plurality of operational processes in the final design for the operational procedure.

15. The design tool of any preceding claim, wherein the at least one work product is configured to be output to a third-party service provider who will be performing the operational procedure.

16. The design tool of any preceding claim, wherein the memory is further programmed with instructions that when executed cause the at least one processor to: determine if the received input data contains new information, and if so, to update a database to include the new information in the received input data.

17. The design tool of claim 16, wherein each of the plurality of pipeline components and equipment has an associated identifier, and wherein the memory is further programmed with instructions that when executed cause the at least one processor to determine if the received input data contains new information by:comparing a first identifier received in the input data for each of the plurality of pipeline components and equipment with a second identifier stored in the database in association with a stored set of pipeline components and equipment; andif the first and second identifiers do not match, determining that the input data contains the new information.

18. The design tool of any preceding claim, wherein the memory is further programmed with instructions that when executed cause the at least one processor to: retrieve stored data from a database, the stored data comprising information relating to use of one or more of the plurality of pipeline components and equipment during at least one previous operational procedure; andcalculate at least one of the one or more sets of properties based on the retrieved stored data.

19. The design tool of claim 18, wherein:the input is configured to, at predefined intervals, receive one or more data updates comprising information about use of one or more of the plurality of pipeline components and equipment during the at least one previous operational procedure; andthe memory is further programmed with instructions that when executed cause the at least one processor to update the stored data in the database based on the data updates.

20. The design tool of claim 19, wherein the one or more data updates comprise one or more of the following: instructions and / or advice from engineers relating to the at least one previous operational procedure; changes to the predefined criterion; and changes to one or more of the plurality of operational parameters.

21. The design tool of any preceding claim, wherein the memory is further programmed with instructions that when executed cause the at least one processor to display, via the interactive user interface:a visual representation of the pipeline composition that will form part of the proposed design for the pipeline operational procedure; andone or more user-selectable icons that, upon interaction by the user, alter at least one property of the visual representation;wherein the instructions when executed further cause the at least one processor to, upon interaction by the user, update (i) the visual representation to take into account the alteration of the at least one property, and (ii) the proposed design for the operational procedure.

22. The design tool of claim 21, wherein the at least one property of the visual representation comprises any one or more of the following: (i) an order of the plurality of pipeline components and equipment for implementation in the proposed design for the pipeline operational procedure; or (ii) a type, identity or number of the plurality of pipeline components and equipment23. A computer-implemented method arranged to design an operational procedure for a subsea pipeline, the method comprising:receiving, from a user, input data relating to the operational procedure, the input data comprising:(i) pipeline composition data defining a plurality of pipeline components forming the subsea pipeline and associated equipment for use in the operational procedure; and(ii) operational process data comprising a plurality of operational parameters defining a plurality of operational processes carried out to implement the operational procedure;generating a proposed design for the subsea pipeline and for the operational procedure based on the received pipeline composition data and operational process data;calculating one or more sets of properties of the proposed design for the subsea pipeline and / or the operational procedure;for each of the one or more sets of properties:determining whether the set of properties meets a predefinedcriterion for one or more of the plurality of operational processes to be successfully performed;displaying, via an interactive user interface to the user, the set of properties, in association with an indication of whether the set of properties meets the predefined criterion;in dependence on the predefined criterion not being met, (i)5 requesting updated input pipeline composition data and / or operationalprocess data from the user, (ii) generating an updated proposed design for the subsea pipeline and / or for the operational procedure based on the received updated input data, and (iii) re-performing the preceding calculation, determination and display functions until the predefined10 criterion is met; andin dependence on the predefined criterion being met, (i) determining a final operational procedure design based on the updated proposed design for the subsea pipeline and for the operational procedure, and (ii) generating at least one work product relating to implementation of the final15 operational procedure design; andoutputting, to the user, the at least one work product.

Images