Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
SYSTEM, METHOD AND TOOL FOR MANAGING ACTIVITIES
Document Type and Number:
WIPO Patent Application WO/2011/014912
Kind Code:
A1
Abstract:
A system (2) for managing an activity, the system comprising a processing means and a storage means, the storage means having a software application stored thereon, whereby the processing means is operable, under control of the software application, to generate a user interface to facilitate operation of the system, display via the user interface a plurality of screens for displaying and/or for inputting of data relating to the activity, receive data relating to the activity inputted via the user interface, store the received inputted data in the storage means, and generate a report on the basis of the inputted data, to manage the activity.

Inventors:
WALKER BRETT MITCHELL (AU)
WHITE DAVID ALEXANDER (AU)
Application Number:
PCT/AU2010/000979
Publication Date:
February 10, 2011
Filing Date:
August 03, 2010
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
WALKER BRETT MITCHELL (AU)
WHITE DAVID ALEXANDER (AU)
International Classes:
E21B49/00; G06Q10/00; G06Q50/00; G06Q90/00
Domestic Patent References:
WO2004063949A22004-07-29
WO2009018450A12009-02-05
Foreign References:
US20070260373A12007-11-08
Other References:
DATABASE WPI Derwent World Patents Index; AN 2008-F40508
Attorney, Agent or Firm:
WRAYS (56 Ord StreetWest Perth, Western Australia 6005, AU)
Download PDF:
Claims:
The Claims Defining the Invention are as Follows:

1. A system for managing an activity, the system comprising a processing means and a storage means, the storage means having a software application stored thereon, whereby the processing means is operable, under control of the software application, to generate a user interface to facilitate operation of the system, display via the user interface a plurality of screens for displaying and/or for inputting of data relating to the activity, receive data relating to the activity inputted via the user interface, store the received inputted data in the storage means, and generate a report on the basis of the inputted data, to manage the activity.

2. The system of claim 1, wherein the processing means is operable, under control of the software application, to display or publish the report via the user interface.

3. The system of claim 1 or 2, wherein the user interface comprises a graphical user interface or human machine interface comprising a display or touch screen.

4. The system of any one of the preceding claims, wherein the processing means is operable, under control of the software application, to automatically generate the report. 5. The system of any one of the preceding claims, wherein a format of the generated report is customisable according to the inputted data.

6. The system of any one of the preceding claims, further comprising a sensor in data communication with the processing means, wherein the sensor is operably coupleable to a subject of the activity to detect subject data relating to the subject and to communicate the detected subject data to the processing means, and the processing means is operable, under control of the software application, to receive and store the received detected subject data in the storage means, and to generate the report on the basis of the detected subject data.

7. The system of any one of the preceding claims, wherein the activity comprises a plurality of tasks to be completed according to a procedure, and the plurality of screens display information relating to the tasks, and prompt the inputting of data relating to the tasks.

8. The system of claim 7, wherein the screens are sequentially generated to display the task information, and prompt the inputting of data, in a task screen order corresponding to that in which the tasks must be completed according to the procedure, to manage the activity.

9. The system of claim 8, wherein the processing means is operable, under control of the software application, to require data prompted to be inputted by a screen in the task screen order to be inputted before generating a subsequent screen in the task screen order. 10. The system of claim 8 or 9, wherein a screen in the task screen order relates to a Job Safety Analysis ("JSA"), and the processing means is operable, under control of the software application, to require data relating to the JSA to be inputted before generating a subsequent screen.

11. The system of any one of the preceding claims, wherein the processing means is operable, under control of the software application, to process the inputted data and/or the detected subject data before generating the report.

12. The system of claim 11 , wherein the processing comprises comparing the inputted data and/or the detected subject data against test criteria to generate a test result. 13. The system of claim 12, wherein the test result comprises whether the test criteria is satisfied (a pass) or not satisfied (a fail).

14. The system of claim 13, wherein the processing means is operable, under control of the software application, to display the test result via the user interface.

15. The system of claim 13 or 14, wherein the processing comprises determining a reason for the test result and the processing means is operable, under control of the software application, to display the reason for the test result via the user interface.

16. The system of any one of claims 12 to 15, wherein the processing means is operable, under control of the software application, to recommend the test criteria and display the recommendation via the user interface.

17. The system of any one of claims 12 to 16, wherein the inputted data includes the test criteria.

18. The system of any one of claims 11 to 17, wherein the processing comprises predicting whether the performance result is likely to satisfy the test criteria.

19. The system of claim 18, wherein the predicting comprises generating a trend on the basis of the inputted data and/or the detected subject data.

20. The system of claim 19, wherein, when the generated trend is an increasing trend the processor mean is operable, under control of the software application, to predict that the test result is unlikely to satisfy the test criteria, and when the generated trend is a decreasing trend the processing means is operable, under control of the software application, to predict that the performance result is likely to satisfy the test criteria.

21. The system of any one of claims 11 to 20, wherein the software application uses an algorithm to perform the processing.

22. The system of any one of claims 11 to 21 , wherein the test result comprises whether a prescribed condition has occurred, in which case the processing means is operable, under control of the software application, to execute a corresponding prescribed action.

23. The system of claim 22, wherein the corresponding prescribed action comprises generating and displaying via the user interface a notification regarding the prescribed condition, initiating a shut down procedure, and/or generating a visual, audible, and/or tactile alarm via the user interface.

24. The system of any one of the preceding claims, wherein the report relates to the performance of the subject.

25. The system of any one of the preceding claims, wherein the processing means is operable, under control of the software application, to generate and communicate a request for prescribed subject data to the sensor, and the sensor is operable to receive the request and to detect the prescribed subject data in response thereto and communicate the prescribed subject data to the processing means. 26. The system of any one of the preceding claims, wherein the system is operable to manage a plurality of activities, selected from a set of activities including: hydrostatic pressure testing; bolt tensioning; assembling bolted flanges; testing a bolt batch to destruction to determine or prove a grade thereof; verifying that a torque used translates to an expected tension in a bolt; torque up a pressure containing flanged joint; checking the cleanliness of a hydraulic fluid; pressure testing a flanged joint; tensile destructive testing with use of either hydraulic cylinder or torque tool (hydraulic, pneumatic or manual) and hollow/washer/donut load cell; operations management; field inspection; and work instructions. 27. The system of any one of the preceding claims, wherein the processing means is operable, under control of the software application, to link reports generated for a plurality of activities in a multiple activity report.

28. The system of any one of the preceding claims, wherein the displayed data comprises information including prescribed standards specifying requirements for the activity, the subject of the activity, and regarding components used in the activity. 29. The system of any one of the preceding claims, comprising visual recording or imaging means and/or audio recording means.

30. The system of claim 29, wherein the visual recording or imaging means comprises a camera integrated with or operably coupleable to the processing means and operable to record and store still and video images in the storage means.

31. The system of claim 29, wherein the audio recording means comprises a microphone and/or a hydrophone integrated with or operably coupleable to the processing means and operable to record and store sound in the storage means. 32. The system of any one of the preceding claims, comprising time determining means operable to determine a time that data is received, and the processing means is operable, under control of the software application, to store the determined time of receipt in association with the received data in the storage means. 33. The system of claim 32, wherein the processing means is operable, under control of the software application, to stamp the determined time of receipt in the report.

34. The system of any one of the preceding claims, wherein the report comprises a graph. 35. The system of claim 34, wherein the processing means is operable, under control of the software application to display the performance criteria in the graph.

36. The system of any one of the preceding claims, comprising location determining means operable to determine a location that data is received, and the processing means is operable, under control of the software application, to store the determined location of receipt in association with the received data in the storage means.

37. The system of claim 36, wherein the processing means is operable, under control of the software application, to stamp the determined location of receipt in the report.

38. The system of any one of the preceding claims, comprising modelling means for generating a representation related to the activity, and operable via the human machine interface.

39. The system of any one of the preceding claims, wherein the system is operable to communicate with a device.

40. The system of claim 39, wherein the communication is via the Internet or an Internet link and the system is operable to communicate received data and/or the report to the device.

41. A method for managing an activity, the method comprising accessing an activity management system comprising a processing means and a storage means, the storage means having a software application stored thereon, whereby the processing means is operable, under control of the software application, to generate a user interface to facilitate operation of the system, the method comprising viewing and inputting data relating to the activity via the user interface using a plurality of screens for displaying and/or for inputting of data relating to the activity, receiving data relating to the activity inputted via the user interface, storing the received inputted data in the storage means, and generating a report on the basis of the inputted data,, to manage the activity.

42. The method of claim 41 , comprising displaying or publishing the report via the user interface.

43. The method of claim 41 or 42, comprising automatically generating the report. 44. The method of any one of claims 41 to 43, comprising customising a format of the generated report according to the inputted data.

45. The method of any one of claims 41 to 44, comprising establishing data communication between a sensor and the processing means, operably coupling the sensor to a subject of the activity to detect subject data relating to the subject, communicating the detected subject data to the processing means, receiving and storing the received detected subject data in the storage means, and generating the report on the basis of the detected subject data.

46. The method of any one of claims 41 to 45, wherein the activity comprises a plurality of tasks to be completed according to a procedure, and the plurality of screens display information relating to the tasks, and prompt the inputting of data relating to the tasks.

47. The method of any one of claims 41 to 46, comprising sequentially generating the screens to display the task information, and prompt the inputting of data, in a task screen order corresponding to that in which the tasks must be completed according to the procedure, to manage the activity.

48. The method of claim 47, comprising requiring data prompted to be inputted by a screen in the task screen order to be inputted before generating a subsequent screen in the task screen order.

49. The method of claim 47 or 48, wherein a screen in the task screen order relates to a Job Safety Analysis ("JSA"), comprising requiring data relating to the JSA to be inputted before generating a subsequent screen.

50. The method of any one of claims 41 to 49, comprising processing the inputted data and/or the detected subject data before generating the' report.

51. The method of claim 50, wherein the processing comprises comparing the inputted data and/or the detected subject data against test criteria to generate a test result.

52. The method of claim 51 , wherein the test result comprises whether the test criteria is satisfied (a pass) or not satisfied (a fail).

53. The method of claim 52, comprising displaying the test result via the user interface.

54. The method of claim 52 or 53, wherein the processing comprises determining a reason for the test result and displaying the reason for the test result via the user interface.

55. The method of any one of claims 51 to 54, comprising recommending the test criteria and displaying the recommendation via the user interface.

56. The method of any one of claims 51 to 55, wherein the inputted data includes the test criteria. 57. The method of any one of claims 50 to 56, wherein the processing comprises predicting whether the performance result is likely to satisfy the test criteria.

58. The method of claim 57, wherein the predicting comprises generating a trend on the basis of the inputted data and/or the detected subject data. 59. The method of claim 58, wherein, when the generated trend is an increasing trend, predicting that the test result is unlikely to satisfy the test criteria, and when the generated trend is a decreasing trend predicting that the performance result is likely to satisfy the test criteria.

60. The method of any one of claims 50 to 57, comprising using an algorithm to perform the processing. 61. The method of any one of claims 51 to 60, comprising determining whether the test result comprises the occurrence of a prescribed condition and, if so, executing a corresponding prescribed action.

62. The method of claim 61 , wherein the corresponding prescribed action comprises generating and displaying via the user interface a notification regarding the prescribed condition, initiating a shut down procedure, and/or generating a visual, audible, and/or tactile alarm via the user interface.

63. The method of any one of claims 41 to 62, wherein the report relates to the performance of the subject.

64. The method of any one of claims 41 to 63, comprising generating and communicating a request for prescribed subject data to the sensor, receiving the request and detecting the prescribed subject data in response thereto and communicating the prescribed subject data to the processing means.

65. The method of any one of claims 41 to 64, comprising linking reports generated for a plurality of activities in a multiple activity report.

66. The method of any one of claims 41 to 65, wherein the displayed data comprises information including prescribed standards specifying requirements for the activity, the subject of the activity, and regarding components used in the activity. 67. The method of any one of claims 41 to 66, comprising recording and storing still and video images in the storage means.

68. The method of any one of claims 41 to 67, comprising recording and storing sound in the storage means.

69. The method of any one of claims 41 to 68, comprising determining a time that data is received and storing the determined time of receipt in association with the received data in the storage means.

70. The method of claim 69, comprising stamping the determined time of receipt in the report.

71. The method of any one of claims 41 to 70, comprising determining a location that data is received and storing the determined location of receipt in association with the received data in the storage means.

72. The method of claim 71 , comprising stamping the determined location of receipt in the report.

73. The method of any one of claims 41 to 72, comprising generating a representation related to the activity. 74. The method of any one of claims 41 to 73, comprising communicating with a device.

75. The method of claim 74, wherein the communication is via the Internet or an Internet link and the method comprises communicating received data and/or the report to the device. 76. A tool for managing an activity, the tool comprising a processing means and a storage means, the storage means having a software application and a database stored thereon, whereby the processing means is operable, under control of the software application, to generate a user interface to facilitate operation of the system, display via the user interface a plurality of screens for displaying and/or for inputting of data relating to the activity, receive data relating to the activity inputted via the user interface, store the received inputted data in the storage means, and to generate a report on the basis of the inputted data, to manage the activity. A method for managing an activity, the method comprising displaying data relating to the activity, receiving data relating to the activity, and generating a report on the basis of the received data, to manage the activity. 77. A computer-readable storage medium on which is stored instructions that, when executed by a computing means, causes the computing means to perform the method for managing an activity according to any one of claims 41 to 75 or 77.

78. A computing means programmed to carry out the method for managing an activity according to any one of claims 41 to 75 or 77.

79. A system for managing an activity substantially as hereinbefore described with reference to the accompanying drawings.

80. A method for managing an activity substantially as hereinbefore described with reference to the accompanying drawings.

Description:
System, Method and Tool for Managing Activities Field of the Invention

The present invention relates to a system, method and tool for managing activities, such as procedural operations including testing, data recording and analysing. Although the present invention will be described with particular reference to activities in the resource industry and particularly subsea construction and abandonments, such as hydrostatic pressure testing and hydraulic bolt tensioning and any hydraulic system that requires pressure and flow recording and analysing, it will be appreciated that the present invention may be used in respect of any activity in any industry or on any system that requires personnel and sensors to record data and generate a report. Embodiments of the present invention are applicable to any task where a repetitive set of instructions must be adhered to and a recorded result is desirable.

Throughout the specification, unless the context requires otherwise, the word "comprise" or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated integer or group of integers but not the exclusion of any other integer or group of integers.

Furthermore, throughout the specification, unless the context requires otherwise, the word "include" or variations such as "includes" or "including", will be understood to imply the inclusion of a stated integer or group of integers but not the exclusion of any other integer or group of integers.

Additionally, throughout the specification, unless the context requires otherwise, the words "substantially" or "about" will be understood to not be limited to the value for the range qualified by the terms.

Background Art

Each document, reference, patent application or patent cited in this text is expressly incorporated herein in their entirety by reference, which means that it should be read and considered by the reader as part of this text. That the document, reference, patent application, or patent cited in this text is not repeated in this text is merely for reasons of conciseness.

The following discussion of the background to the invention is intended to facilitate an understanding of the present invention only. It should be appreciated that the discussion is not an acknowledgement or admission that any of the material referred to was published, known or part of the common general knowledge of the person skilled in the art in any jurisdiction as at the priority date of the invention.

Often, for successful completion of an activity, a number of prescribed tasks must be completed to, or a subject performed at, a particular standard.

Two such activities in the resources industry are hydrostatic pressure testing and bolt tensioning.

In the case of a hydrostatic pressure testing activity, a number of tasks are required to be done to conduct the test on a subject piece of equipment, including determining the test criteria, logging data arising from the test, interpreting the logged data, and preparing a report thereon. Health and safety policies also often stipulate that a safety analysis be undertaken before the testing is conducted, and safety barriers established. Equipment typically used to log data arising from the testing include paper chart recorders, paperless chart recorders, hand held, panel mounted or mobile data loggers, and hand written notes based on operator interpretation.

A number of problems can arise in the completion of these tasks, including the following:

• Critical or important information on what the test was for may not be recorded, and if it is it may not be kept with a recording of the test results

(such as a paper chart), rendering the test results (chart) not meaningful.

Although the information to be recorded is critical/important, it is often of a repetitive and tedious nature. For example, information such as serial numbers, dates, identifiers and names, etc, may be supposed to be recorded for tests that can be repeated dozens of times a day for days on end. The monotony of such activity is one of the reasons why operators omit information with the good intention of completing recording of the information later.

• Often the test criteria are not understood by the operator, causing the operator to perform tests incorrectly and damaging equipment and or tests being not valid.

• Although a safety analysis is supposed to be completed prior to the testing commencing, in practice it may be done separately to the testing activity, at a different location, and/or on paperwork separate from any testing paperwork (and therefore separable therefrom).

• Test criteria's can be complex and results can require a reasonably high level of interpretation to determine whether it's a pass or fail, which may be beyond the skill of operators. For example, a pressure test with a requirement to be a decreasing leak trend is usually overlooked by operators and if not overlooked or misunderstood is very difficult to determine on a paper chart or graph on a paperless recorder.

• Often, testing equipment to a standard of a classification society requires a great deal of knowledge and can really only be undertaken by a person suitably qualified and experienced in the relevant field. In this regard, depending on the standard, a person must be truly qualified and experienced just to determine the criteria than is required to be tested to satisfy the standard. • The tasks may be completed inefficiently, with operators persisting in trying to get a test to pass when they are marginal, with closer inspection of the data showing that the system is leaking.

• Reports may be compiled after the tests have been completed and by a different person than whom performed the tests.

• Typical danger demarcation barrier tape may be left erected while no danger may be present, leading to it being ignored unless practice is closely managed and supervised. • Procedures for the activity may be produced on paper worksheets required to be manually completed by the operator and subsequently manually stored, which may result in them being misplaced and information lost.

An additional problem that may arise in a bolt tensioning activity is that human error in judgement may result in bolts not being done up in the correct order, too loosely or too tightly, and being damaged. The bolt material may also not meet mechanical requirements of it's grade.

Another activity is calibration of hydraulic equipment, which usually requires the equipment to be sent offsite for calibration.

Furthermore, the data recording techniques used involve devices that record data that then has to be downloaded to a separate computer and used to generate a report. In other cases data loggers may be used, which do nothing more than log an output measurement.

It is against this background that the present invention has been developed. Disclosure of the Invention The present invention seeks to overcome, or at least ameliorate, one or more of the deficiencies of the prior art mentioned above, or to provide the consumer with a useful or commercial choice.

Advantages of the present invention will become apparent from the following description, taken in connection with the accompanying drawings, wherein, by way of illustration and example, preferred embodiments of the present invention are disclosed. In accordance with a first broad aspect of the present invention, there is provided a system for managing an activity, the system comprising a processing means and a storage means, the storage means having a software application stored thereon, whereby the processing means is operable, under control of the software application, to generate a user interface to facilitate operation of the system, display via the user interface a plurality of screens for displaying and/or for inputting of data relating to the activity, receive data relating to the activity inputted via the user interface, store the received inputted data in the storage means, and generate a report on the basis of the inputted data, to manage the activity. Preferably, the processing means is operable, under control of the software application, to display or publish the report via the user interface.

Preferably, the user interface comprises a graphical user interface or human machine interface comprising a display or touch screen.

In a preferred form, the processing means is operable, under control of the software application, to automatically generate the report.

In a preferred form, a format of the generated report is customisable according to the inputted data.

Preferably, the system further comprises a sensor in data communication with the processing means, wherein the sensor is operably coupleable to a subject of the activity to detect subject data relating to the subject and to communicate the detected subject data to the processing means, and the processing means is operable, under control of the software application, to receive and store the received detected subject data in the storage means, and to generate the report on the basis of the detected subject data. Preferably, the activity comprises a plurality of tasks to be completed according to a procedure, and the plurality of screens display information relating to the tasks, and prompt the inputting of data relating to the tasks. Preferably, the screens are sequentially generated to display the task information, and prompt the inputting of data, in a task screen order corresponding to that in which the tasks must be completed according to the procedure, to manage the activity. In this manner, an electronic procedure or wizard is provided to step an operator through the process of performing the tasks of the procedure, which may comprise a pressure test or any other testing procedure. A wizard template may be provided that the same wizard template services all activities.

Preferably, the processing means is operable, under control of the software application, to require data prompted to be inputted by a screen in the task screen order to be inputted before generating a subsequent screen in the task screen order.

Preferably, a screen in the task screen order relates to a Job Safety Analysis ("JSA"), and the processing means is operable, under control of the software application, to require data relating to the JSA to be inputted before generating a subsequent screen.

Preferably, the processing means is operable, under control of the software application, to process the inputted data and/or the detected subject data before generating the report. Preferably, the processing comprises comparing the inputted data and/or the detected subject data against performance or test criteria to generate a performance result. The performance or test result may comprise whether the performance or test criteria is satisfied (a pass) or not satisfied (a fail). The processing means may then be operable, under control of the software application, to display the result via the user interface. The performance or test result may be for a task of the activity, and comprise a test or examination of the task. In this manner, no human interpretation of the inputted data or the detected subject data is required to determine whether the performance or test criteria is satisfied or not satisfied. The processing may further comprise determining a reason for the performance result. In such a case, the processing means may be further operable, under control of the software application, to display the reason for the result via the user interface. The reason may comprise why the performance or test criteria was not satisfied (such as failure to comply with a standard, for example).

The performance or test criteria may be in accordance with recognised standards. Furthermore, the processing means may be operable, under control of the software application, to recommend the performance or test criteria and display the recommendation via the user interface. The inputted data may include the performance criteria. In this manner, a user or client of the system may input (i.e. upload) their own or company testing criteria and store or save them to the storage means for subsequent users to access and use. The processing means may be operable, under control of the software application, to generate via the user interface a wizard to guide an operator through a classification society standard to determine performance or test criteria to be entered to satisfy that standard.

In the case of an activity related to flanges, the performance result may comprise a determination of a bolt of the flanges to be acted on next regardless of the number of bolts. In the case of a torque versus tension test activity, the performance result may comprise a determination of a relationship between torque and tension for a bolt and flange arrangement with a torque tool (hydraulic, pneumatic, or manual) and a load cell.

In a preferred form, the inputted data comprises notes or comments regarding the activity.

Preferably, the inputted data comprises data selected from data stored in the database. For example, the inputted data may comprise a torque versus tension test relationship factor from a previous test activity stored in the database. Preferably, the processing comprises predicting whether the performance result is likely to satisfy the performance criteria. The predicting may comprise generating a trend on the basis of the inputted data and/or the detected subject data. If the generated trend is an increasing trend then the processing means is operable, under control of the software application, to predict that the performance result is unlikely to satisfy the performance criteria. If the generated trend is a decreasing trend then the processing means is operable, under control of the software application, to predict that the performance result is likely to satisfy the performance criteria. Preferably, the software application uses an algorithm to perform the processing.

The performance result may comprise whether a prescribed condition has occurred, in which case the processing means is operable, under control of the software application, to execute a corresponding prescribed action. The corresponding prescribed action may comprise generating and displaying via the user interface a notification regarding the prescribed condition.

In the case of a hydrostatic pressure testing activity, the prescribed condition may comprise whether pressure is increasing.

The prescribed condition may comprise whether a safety value has been exceeded, such as, for example, an over pressure or rapid pressure drop. In such a case, the corresponding prescribed action may comprise a shut down procedure, and/or generating a visual, audible, and/or tactile alarm via the user interface.

Preferably, the report relates to the performance of the subject.

Preferably, the processing means is operable, under control of the software application, to generate and communicate a request for prescribed subject data to the sensor, and the sensor is operable to receive the request and to detect the prescribed subject data in response thereto and communicate the prescribed subject data to the processing means. Preferably, the system is operable to manage a plurality of activities, selected from a set of activities including: hydrostatic pressure testing; bolt tensioning; assembling bolted flanges; testing a bolt batch to destruction to determine or prove a grade thereof; verifying that a torque used translates to an expected tension in a bolt; torque up a pressure containing flanged joint; checking the cleanliness of a hydraulic fluid; pressure testing a flanged joint; tensile destructive testing with use of either hydraulic cylinder or torque tool (hydraulic, pneumatic or manual) and hollow/washer/donut load cell; operations management; field inspection; and work instructions. Furthermore, the system is operable to group more than one activity together, such as for than one flange that has been assembled in the same pressure test.

In a preferred form, the processing means is operable, under control of the software application, to link reports generated for a plurality of activities in a multiple activity report. Preferably, the displayed data comprises information including activity subject information. The activity subject information may be stored in an activity subject database and comprise prescribed standards specifying requirements for the activity, the subject of the activity, and regarding components used in the activity. These components may include bolts, bolt/stud sizes, hoses, flanges, pipes, valves, chokes, Blow-out Preventer ("BOP") valve packages, lubricants, materials, torque tools, and bolt tensioners in the case of a bolt tensioning activity. The prescribed standards may relate to recognised pressure bodies from recognised industry standards and/or company products.

Preferably, the system comprises visual recording or imaging means and/or audio recording means. The visual recording/imaging means may comprise a camera integrated with or operably coupleable to the processing means and operable to record and store still and video images in the storage means. The audio recording means may comprise a microphone and/or a hydrophone integrated with or operably coupleable to the processing means and operable to record and store sound in the storage means.

In a preferred form, the inputted data includes annotations for stored images and sounds. Preferably, the system comprises time determining means operable to determine a time that data is received, and the processing means is operable, under control of the software application, to store the determined time of receipt in association with the received data in the storage means. Preferably, the processing means is operable, under control of the software application, to stamp the determined time of receipt in the report. Preferably, the time determining means comprises a clock or a timer.

Preferably, the report comprises a graph. In a preferred form, the time determining means is operable to determine a time that an activity commenced. In such a case, the processing means is operable, under control of the software application, to store the determined commencement time in the storage means, and display the determined commencement time in the graph. The determined commencement time may be displayed by means of a vertical line, for example.

Preferably, the processing means is operable, under control of the software application, to display the performance criteria in the graph. In the case of a hydrostatic pressure testing activity, the performance criteria may comprise maximum and minimum pressure boundaries, and the processing means may be operable, under control of the software application, to display these as, for example, horizontal lines in the graph. In the case of a bolt tensioning activity, the pressure/tensioning of a bolt to do up a flange may be displayed in the graph. Preferably, the graph is operable to automatically zoom into a domain and range of the performance criteria. This makes viewing the stored data easier to understand and interpret without maximum and minimum boundaries of the domain and range being required to be manually inputted. Preferably, the system comprises location determining means operable to determine a location that data is received and the processing means is operable, under control of the software application, to store the determined location of receipt in association with the received data in the storage means. Preferably, the processing means is operable, under control of the software application, to stamp the determined location of receipt in the report. Preferably, the location determining means comprises a Global Positioning System ("GPS") integrated with or operably coupleable to the processing means.

Preferably, the application software comprises modelling means for generating a representation related to the activity, and operable via the human machine interface.

Preferably, the system is operable to communicate with a device. Preferably, the communication is via the Internet or an Internet link, in which case the device comprises an Internet enabled device. The device may comprise any mobile communication device, including a personal, notebook or tablet computer such as that marketed under the trade mark IPAD® by Apple Inc, or a smartphone such as that marketed under the trade mark IPHONE® by Apple Inc.

Preferably, the system is operable to communicate received data and/or the report to the device. In this manner, a client office, operating the device, is able to view tests performed in the field by the system.

In accordance with a second broad aspect of the present invention, there is provided a method for managing an activity, the method comprising accessing an activity management system comprising a processing means and a storage means, the storage means having a software application stored thereon, whereby the processing means is operable, under control of the software application, to generate a user interface to facilitate operation of the system, the method comprising viewing and inputting data relating to the activity via the user interface using a plurality of screens for displaying and/or for inputting of data relating to the activity, receiving data relating to the activity inputted via the user interface, storing the received inputted data in the storage means, and generating a report on the basis of the inputted data, to manage the activity.

Preferably, the method further comprises, displaying or publishing the report via the user interface. In accordance with a third broad aspect of the present invention, there is provided a tool for managing an activity, the tool comprising a processing means and a storage means, the storage means having a software application stored thereon, whereby the processing means is operable, under control of the software application, to generate a user interface to facilitate operation of the system, display via the user interface a plurality of screens for displaying and/or for inputting of data relating to the activity, receive data relating to the activity inputted via the user interface, store the received inputted data in the storage means, and to generate a report on the basis of the inputted data, to manage the activity.

Preferably, the processing means is operable, under control of the software application, to display or publish the report via the user interface.

Preferably, the method comprises displaying or publishing the report via the user interface.

Preferably, the method comprises automatically generating the report.

Preferably, the method comprises customising a format of the generated report according to the inputted data.

Preferably, the method comprises establishing data communication between a sensor and the processing means, operably coupling the sensor to a subject of the activity to detect subject data relating to the subject, communicating the detected subject data to the processing means, receiving and storing the received detected subject data in the storage means, and generating the report on the basis of the detected subject data. Preferably, the activity comprises a plurality of tasks to be completed according to a procedure, and the plurality of screens display information relating to the tasks, and prompt the inputting of data relating to the tasks.

Preferably, the method comprises sequentially generating the screens to display the task information, and prompt the inputting of data, in a task screen order corresponding to that in which the tasks must be completed according to the procedure, to manage the activity.

Preferably, the method comprises requiring data prompted to be inputted by a screen in the task screen order to be inputted before generating a subsequent screen in the task screen order.

Preferably, a screen in the task screen order relates to a Job Safety Analysis ("JSA"), comprising requiring data relating to the JSA to be inputted before generating a subsequent screen.

Preferably, the method comprises processing the inputted data and/or the detected subject data before generating the report.

Preferably, the processing comprises comparing the inputted data and/or the detected subject data against test criteria to generate a test result.

Preferably, the test result comprises whether the test criteria is satisfied (a pass) or not satisfied (a fail). Preferably, the method comprises displaying the test result via the user interface.

Preferably, the processing comprises determining a reason for the test result and displaying the reason for the test result via the user interface.

Preferably, the method comprises recommending the test criteria and displaying the recommendation via the user interface. Preferably, the inputted data includes the test criteria. Preferably, the processing comprises predicting whether the performance result is likely to satisfy the test criteria.

Preferably, the predicting comprises generating a trend on the basis of the inputted data and/or the detected subject data. Preferably, when the generated trend is an increasing trend, the method comprises predicting that the test result is unlikely to satisfy the test criteria, and when the generated trend is a decreasing trend the method comprises predicting that the performance result is likely to satisfy the test criteria.

Preferably, the method comprises using an algorithm to perform the processing. Preferably, the method comprises determining whether the test result comprises the occurrence of a prescribed condition and, if so, executing a corresponding prescribed action.

Preferably, the corresponding prescribed action comprises generating and displaying via the user interface a notification regarding the prescribed condition, initiating a shut down procedure, and/or generating a visual, audible, and/or tactile alarm via the user interface.

Preferably, the report relates to the performance of the subject.

Preferably, the method comprises generating and communicating a request for prescribed subject data to the sensor, receiving the request and detecting the prescribed subject data in response thereto and communicating the prescribed subject data to the processing means.

Preferably, the method comprises linking reports generated for a plurality of activities in a multiple activity report.

Preferably, the displayed data comprises information including prescribed standards specifying requirements for the activity, the subject of the activity, and regarding components used in the activity. Preferably, the method comprises recording and storing still and video images in the storage means.

Preferably, the method comprises recording and storing sound in the storage means. Preferably, the method comprises determining a time that data is received and storing the determined time of receipt in association with the received data in the storage means.

Preferably, the method comprises stamping the determined time of receipt in the report. Preferably, the method comprises determining a location that data is received and storing the determined location of receipt in association with the received data in the storage means.

Preferably, the method comprises stamping the determined location of receipt in the report. Preferably, the method comprises generating a representation related to the activity.

Preferably, the method comprises communicating with a device.

Preferably, the communication is via the Internet or an Internet link and the method comprises communicating received data and/or the report to the device. In accordance with a fourth broad aspect of the present invention, there is provided a method for managing an activity, the method comprising displaying data relating to the activity, receiving data relating to the activity, and generating a report on the basis of the received data, to manage the activity.

In accordance with a fifth broad aspect of the present invention, there is provided a computer-readable storage medium on which is stored instructions that, when executed by a computing means, causes the computing means to perform the method for managing an activity according to the second or fourth broad aspects of the present invention as hereinbefore described.

In accordance with a sixth broad aspect of the present invention, there is provided a computing means programmed to carry out the method for managing an activity according to the second or fourth broad aspects of the present invention as hereinbefore described.

Brief Description of the Drawings

The invention will now be described, by way of example only, with reference to the accompanying drawings, of which: Figure 1A depicts an illustration of a first embodiment of a management system in accordance with an aspect of the present invention in use in a hydrostatic pressure testing activity;

Figure 2 depicts a high level flow chart illustrating the procedural operation of the management system of Figure 1 to process data received from an operator and sensors to determine a result and publish the result to a report;

Figure 3 depicts an overview of a selection of possible applications relating to activities that can be managed via the management system of Figure 1 ;

Figure 1 B depicts an illustration of the management system of Figure 1 in use in a bolt tensioning activity; Figure 1C depicts an illustration of the management system of Figure 1 in use in a task comprising taking photographic evidence relating to a hydrostatic pressure testing activity;

Figure 4 depicts a table listing published standards that relate to pressure testing and their test criteria; Figure 5A depicts a screen shot of a test name or test details input page of the management system of Figure 1 ; Figure 5B depicts a screen shot of an alternative test name or test details input page of the management system of Figure 1 ;

Figure 6 depicts a screen shot of a test equipment input page of the management system of Figure 1 ; Figure 7 depicts a screen shot of a test photo input page of the management system of Figure 1 ;

Figure 8A depicts a screen shot of a comments/notes or summary input page of the management system of Figure 1 ;

Figure 8B depicts a screen shot of an alternative comments/notes input page of the management system of Figure 1 ;

Figure 9A depicts a screen shot of a test criteria input page of the management system of Figure 1 ;

Figure 9B depicts a screen shot of an alternative embodiment of a test criteria input page of the management system of Figure 1 ;Figure 10A depicts a screen shot of a Job Safety Analysis ("JSA") input page of the management system of Figure 1 ;

Figure 10B depicts a screen shot of an alternative embodiment of a Job Safety Analysis ("JSA") input page of the management system of Figure 1 ; Figures 11 A, 11B and 11C depict screen shots of pressure graphs generated by the management system of Figure 1 ;

Figures 12A, 12B and 12C depict screen shots of a display gauge generated by the management system of Figure 1 ;

Figure 13 depicts a screen shot of a report image page of the management system of Figure 1 ; Figures 14A to 14C depict flow charts of operation of a Human Machine Interface of the management system of Figure 1 during a hydrostatic pressure testing activity;

Figures 15A to 15H depict flow charts of the operational steps performed by a wizard of a test summary input page of the management system of Figure 1 ;

Figures 16A to 16D depict a test subject cross-section of a Wireline BOP valve package generated by the management system of Figure 1 ;

Figure 17 depicts a screen shot of a schematic selection screen of the management system of Figure 1 ; and Figure 18 depicts a test subject cross-section of a subsea tree generated by the management system of Figure 1.

Best Mode(s) for Carrying Out the Invention

In the drawings, like features have been referenced with like reference numbers.

In Figure 1A, there is shown a first embodiment of a management system 2 in accordance with an aspect of the present invention.

In the embodiment described, the management system 2 is used to manage activities comprising jobs that are required to be done in the resource industry, such as in oil and gas, construction, mining or in the hydraulic industry. The activities include: • Pressure Testing including Hydrostatic Pressure Testing;

• Bolt Tensioning;

• Flange Tensioning;

• Mechanical Joint Tensioning;

• Bolt Destructive Testing; • Torque/Pressure Vs Tension Confirmation;

• Confirmation of Dynamic Amplification Factor ("DAF") used for off-shore crane lifts; and

• Hydraulic Fluid Cleanliness Testing. For successful completion or performance of each activity a number of tasks must be carried out according to a prescribed procedure. Tasks include undertaking a physical action in respect of a subject, such as a piece of mechanical equipment, and gathering data or information about the subject or the physical action taken (data logging). The management system 2 is operable to guide a user or operator 4 through the tasks required according to the procedure for each activity, measure and/or record their successful completion, and generate a report thereon, thereby managing the activities.

It should be appreciated that the management system 2 is not limited to such activities, however, and alternative embodiments of the invention can be used to manage any activity in any environment, such as a personal exercise program, or a medical procedure.

The management system 2 comprises a wired or wireless management tool 3 in the form of a managing computer software application ("application") stored and run on a computer 6. In the embodiment described, the management tool is provided under the trade mark DART™ ("Data Acquisition and Reporting Tool") and allows various tests and procedures relating to the above mentioned activities to be performed from the one tool. The application may comprise a set of system and application software, with software within the set relating to each of the activities. The application can be written in any suitable language, and in the described embodiment is developed in Wonderware® within a Windows® XPΛ/ista platform as is well known to persons skilled in the art. In an alternative embodiment of the invention, the application runs from a Windows embedded or Windows CE platform, so that less power is required and for improved reliability. The application can be provided as a standalone application or via network depending on the system requirements.

The computer 6 can be of any suitable type, and in the embodiment described comprises a Trimble® Yuma™ tablet personal computer, and has all of the features and capabilities thereof including integrated WiFi®, Bluetooth®, Global

Positioning System ("GPS"), audio recorder, media player, and camera technologies, including a back or rear facing webcam. This is advantageous for work in the resource industry as it is robust, ruggedised, tolerant to water, vibration and dust, small and light weight, mobile/portable and may be hand held.

The computer 6 includes integrated control and display means in the form of a touchscreen display 8 providing a user interface comprising a Human or Man Machine Interface ("HMI") 10 to enable the user 4 to interact with the application. The computer 6 also includes processing or processor means such as a central processor and storage means such as a memory device for the storage and running of an operating system such as Windows®, and one or more software applications, including the application of the embodiment of the present invention. The use and operation of computers using software applications are well known to persons skilled in the art and need not be described in any further detail herein except as is relevant to the present invention.

The processing means is operable under control of the software applications to perform actions and operations as will be described in further detail below.

The operator 4, being a worker on a site in the resources industry in the embodiment described, of the application inputs data for interaction with and processing by the application via a graphical user interface of the HMI 10 displayed on the touchscreen display 8. The HMI 10 presents a graphical display to the operator 4 through which the operator 4 inputs and reads data therefrom. As described above, alternative embodiments of the invention can be used to manage any activity. Accordingly, in alternative embodiments of the invention the user or operator could be anyone required or wishing to undertake the managed activities of the embodiment.

The use of graphical user interfaces and the inputting and reading of data therefrom is well known to persons skilled in the art and need not be described in any further detail herein except as is relevant to the present invention.

The application presents to the operator 4 via the HMI 10 the means to select an activity and to receive data input from the user 4 relating to the selected activity.

The application is further operable, via the HMI 10, to step or guide the operator 4 through the multiple separate tasks required to be done to complete the activity, in an electronic procedure.

The system 2 further comprises a set of sensors, individual sensors within the set of sensors being in selectable data communication with the computer 6. Sensors within the set of sensors are relevant to each activity and operably coupleable to the subject associated with the activity to gather data thereon and communicate it to the computer 6 according to the task(s) of the activity. Sensors include pressure, flow, light, torque, acceleration, or ultrasonic transducers/transmitters, for example, as appropriate, and may be internally located within the computer 6 or provided externally. Any suitable communication protocol can be used to facilitate the communication between sensors within the set of sensors and the computer 6, including wired and wireless (preferably), as are well known to persons skilled in the art and need not be described in any further detail herein except as is relevant to the present invention.

Data received by the computer 6 (inputted by the operator 4 via the HMI 10 or from individual sensors within the set of sensors) is stored in a database coupled to the computer 6 and in data communication therewith in order to enable data to be read to and from the database, as is well known to persons skilled in the art. In the embodiment described herein, the database is an SQL database, although any suitable database structure can be used. The database can be provided locally as a component of the computer 6 (such as in the storage means) or remotely such as on a remote server. In this embodiment, several computers can be set up this way to have a network client-server application. There is one database of information for the application in the embodiment described and it is stored in the storage means of the computer 6. In alternative embodiments there may be more than one database of information.

The database also stores information relating to the activities.

The application is operable to process and interpret the data received and to generate or publish a report based on the interpretation made (i.e. the result of the processing). As it is interpreting the data it is operable to intuitively react to the data and prompt the operator 4 to perform certain tasks as it steps them through the pre-defined tailored procedure of the activity. The interpretation may comprise comparing and evaluating raw data received from the operator 4 (via the HMI 10) and/or sensors of the set of sensors against criteria to determine the result. It can be used to compare the raw data to a set of criteria/specifications set out by an employer company of the operator 4 or to classification society industry standards, such as International Organization for Standardization ("ISO") or American Petroleum Institute ("API") standards.

The application is operable to facilitate the printing of the report directly from the computer 6.

Figure 2 depicts a high level flow chart illustrating the procedural operation of application to process data received from the operator 4 and sensor(s) of the set of sensors to determine the result and publish the result to the report.

The application is further operable to provide a linked system for the activities to relate to one another via the one tool.

The above and other features and advantages of the embodiment of the invention will now be further described with reference to the system 2 in use. Upon execution, the application is operable to generate and present to the operator 4 via the HMI 10 a first or "Start'V'Main" application window or electronic page/screen on the touchscreen display 8. The Start page is operable to provide core functionality control and to enable the operator 4 to make choices regarding the activities.

Figure 3 depicts an overview of a selection of possible applications relating to each of the activities (from the above described set) that can be run or executed via the Start page.

Hydrostatic Pressure Testing Hydrostatic pressure testing is an activity undertaken to locate leaks in pressure vessels such as, but not limited to, pipelines and plumbing including hoses, pipes, manifolds, and bores, for example. It is necessary in all industries that rely on such vessels to transport or store hydraulic or pneumatic energy.

The operator 4 firstly takes the required action to prepare the subject equipment for the test, including connecting it to a pump 12 by a hose 14 to create a hydraulic circuit, connect a sensor 16 from the set of sensors to the test subject to sense/detect and gather test data related to the operation of the subject equipment during the test and communicate it to the computer 6, and taking any required or specified safety precautions. The required action may include using hydraulic isolation valves to isolate the test subject, and closing a needle valve after the pump and venting pressure from the pump 12 to ensure trapped pressure in the pump 12 is not feeding a leak in the subject system or a leaking pump giving a false indication of a test subject leaking. In the embodiment described the sensor 16 is a wireless pressure transmitter (such as Electrochem's PS 1 sensor) mechanically connected to the hydraulic circuit and in wireless data communication with the computer 6 so as to allow sensed data to be logged thereby without the use of a Programmable Logic Controller ("PLC"). The wireless pressure transmitter sensor 16 facilitates recording and viewing pressure activity in the hydraulic circuit as will be described in further detail below.

To manage hydrostatic pressure testing using the system 2, the operator 4 executes the application and the hydrostatic pressure testing activity application thereof via the Start page on the HMI 10. Upon execution of the hydrostatic pressure testing activity, the application is operable to generate and present via the HMI 10 a series or sequence of electronic procedures on application windows or electronic pages/screens that are gated to extract essential data or information from the operator 4 to identify the required test and to step or guide the operator 4 through a list of tasks required to be performed to complete a hydrostatic pressure test. In this way the operator 4 is provided with guide line instructions on how to perform the tasks of the activity. Progression through the pages by the operator 4 results in the application receiving and recording information relevant to the hydrostatic pressure test. Once all of the pages have been completed by the operator 4 the application is operable to automatically generate a report on the hydrostatic pressure test on the basis of the recorded information. The application is operable, via the pages, to capture and log the time and date at which the operator 4 accepts responsibility for performing the tasks set out by the electronic procedures, and to include and present the logged information in the automatically generated report.

The operator 4 is able to navigate the pages and select a particular page by touching or clicking on labelled tabs 18 associated with each page via the HMI 10. The tabs 18 are displayed so as to traverse sequentially from left to right across the touchscreen display 8 of the computer 6, starting at Page 1.

The application is operable, when first executed, to only make the first page, Page 1 , available for selection by the operator 4. An indication of the availability, or otherwise, of a page for selection is provided to the operator 4 by the application showing a page title appearing in the associated label tab 18 in a first colour (for example, black) when available for selection, and a second colour (such as grey) when not available for selection. The application is further operable to a present a Done/Next/OK ("Next") button at the bottom right hand side of each page, and to make the Next button available to the operator 4 for execution once they have completed all of the tasks on the corresponding page. Upon execution of the Next button, the application software is operable to progress the operator 4 to the next page in the sequence (displaying it via the HM! 10 and changing the page title appearing in the associated label tab 18 to the first colour), and perform other functions as will be described in further detail below. All buttons presented via the HMI 10 are large enough to be manipulated by a person wearing gloves, so that the operator 4 can comply with health and safety requirements when employing the system 2.

In embodiments of the invention, the application is also operable to present a "Previous" button at the bottom left hand side of each page. Upon execution of the Previous button, the application software is operable to return the operator 4 to the previous page in the sequence.

The electronic pages generated by the application, and their sequence, are as follows:

Page 1: File As described above, Page 1 is available at all times for selection by the operator 4. The application is operable to provide the following functionality via this page:

• New - execution of this function progresses the operator 4 directly to a second page of the sequence - Page 2: Details. If a test is already open the application is operable, via the HMI 10, to ask the user if they want to save details of the existing test first.

• Open - execution of this function opens and displays the contents of a partitioned hard disk drive of the storage means of the computer 6 within the page or a popup window enabling the operator 4 to open or retrieve a previous test report in a suitable file format (such as Portable Document Format - .pdf) or partially completed test that they wish to complete stored therein.

• Save - execution of this function saves a report of a hydrostatic pressure test in its present state in the storage means that can be re-opened and completed at another time. The application is operable to provide this functionality only once the Page 2: Details screen has been completed.

• Download - execution of this function enables the operator 4 to copy any or all of the test reports files stored in the storage means to an external Universal Serial Bus ("USB") Hybrid Hard Drive ("HHD"). In the embodiment described, the operator 4 is only able to access files contained in the partitioned hard disk drive of the storage means and any external USB HHD, and only the .pdf reports can be downloaded. Other files cannot be copied or removed from the computer 6.

• Pressure Testing Standards - execution of this function opens a popup window showing the table illustrated in Figure 4 of the drawings which lists published standards that relate to pressure testing and their test criteria. In an alternative embodiment of the invention, the application is operable to provide access to more industry recognised standards relevant to the activity.

Page 2: Name/Details

When Page 2 is selected the application, via the HMI 10, presents to the operator 4 an image in the form of a test name or test details input page 20, as illustrated in

Figure 5A of the drawings. The test details input page 20 requests information relevant to the hydrostatic pressure test to be conducted from the operator 4 via a set of pre-set or prompted questions. It includes a plurality of data entry fields into which the operator 4 can enter information such as answers in response to the questions posed. The information inputted by the user 4 is recorded in a file record for the test in the database and displayed in the test details input page 20, by operation of the application software. In the embodiment described, most of the data entry fields of the test details input page 20 (and the other pages generated by the application) are drop down boxes. The application is operable to populate the content of the drop down boxes such that they are composed of every prior entry with duplicates removed and are displayed in alphabetical order. The application is operable so that the displayed content is further narrowed as fieids/information/data are entered to display only relevant selections. This is advantageous as after a short duration of use in a company, the names of the relevant employee and all relevant equipment identifiers, etc, will be selectable under the drop down boxes - removing the requirement for repetitive typing or entering of data by the operator 4. Fields that are not drop down boxes, such as "Last names" are pre-populated by database queries that can be over written if needed. The application is operable to retain entries from the last use in the fields to increase the efficiency of performing repetitive tests. In this manner, the embodiment of the present invention is designed to capture or get optimal or maximal information with minimal effort from the operator 4. This set of pages, which may also be referred to as a wizard, is operable to gather a maximum amount of tedious data with a minimum amount of effort from the operator 4, thereby advantageously reducing the monotony of such action. The information collected via the test name or test details input page 20 includes: o Supervisor First Name

o Supervisor Last Name (the application is operable to prepopulate the edit box of this field depending on the Supervisor First Name selected. If it comprises a new selection, then the Supervisor Last Name can be entered manually by the operator 4, following which it will be saved by the application, so that it will only be required to be done once in the embodiment described) o Operator First Name

o Operator Last Name (the application is operable to populate this field similar to as described above in relation to the Supervisor Last Name)

o Client Company

o Client Company Representative (the application is operable to populate the edit box of this field with the last entered client company representative's name details once Client Company has been selected)

o Test Location

o Date

In an alternative test name or test details input page 20, depicted in Figure 5B, the information collected includes: o Operator Name

o Assistant Name

o Area Supervisor

o Location

o Client

o Project/Asset Name

o Project/Asset Number

o Item Number being tested

o Item Number

o Item Type: selectable via a down list (Hose, Pipe, Manifold, Bore

Test, Valve)

o Length

o Diameter

o Normal Operating Pressure

o Equipment Pressure Rating (maximum pressure rating of component with lowest maximum pressure rating) o Date (shown as Day(number)/Month(text)/Year(number) i.e.

09/July/2009, in the embodiment described)

o Test Number (automatically generated by the application and associated with the test, not determined or inputted by the operator 4). The Test Number references the test to the particular computer 6 that was used to manage it, the date that the test was undertaken, and the number of tests that the particular computer 6 has done. The Test Number comprises the date in reverse order i.e. 090612, the computer 6 is identified by an identifier comprising a three digit number starting at 001 , and the number of tests is a 5 digit number starting at 00001.

Accordingly, an example Test Number is 090612-001-00001. o Item Type. Activation of this button provides the functionality to selectively display the Pressure Testing Standards Table

(provided on Page 1 and illustrated in Figure 2) for each of a set of equipment types (such as a hose, a pipe, a pressure vessel, etc or other) to be the subject of the hydrostatic pressure test. The application is further operable, on selection of a particular equipment type from the set to automatically determine and present as a suggestion to the user 4 the pressure testing criteria, on Page 6 (described in further detail below), to comply with the industrial standard associated with the selected equipment type.

o Length.

o Diameter.

o Normal Operating Pressure.

o Maximum Pressure Rating.

The application is operable to automatically create or generate a file name for the test file record recorded in the database, and to update every time the operator 4 types in or otherwise changes the details inputted in response to the questions.

Once generated, the file name is displayed at the bottom of each page to the left of the Next button (bottom right hand corner). The file name is structured as follows: Test Number/Project-Asset Number/Item Number, for example F:/090612-001 -00001 -CJ0061 -0001. Once the operator 4 has entered the requested information into each field, thereby completing Page 2, they execute the Next button on Page 2 via the HMI 10. A popup window is then presented to the operator 4 via the HMI 10 displaying the generated file name for the test with the options of continuing or cancelling. If the operator 4 chooses to continue the test the application software then operates to save or store the inputted information details in a test file record recorded in the database and to progress the operator 4 to the next page in the sequence - Page 3. At any point after this the operator 4 can navigate the pages via the HMI 10 to return to Page 2 to view or change any of the inputted information details with the exception of those details used to create the file name (i.e. Test Number/Project-Asset Number/Item Number) of the test record, which the application will not permit to be changed so as to facilitate auditing. In an alternative embodiment of the invention, the application is operable to allow the operator 4 to change any of the inputted information details. In such a case, if they change the details that the file name is generated from then the application is operable to update the file name accordingly - the file name will change - it will not do a save as resulting in multiple files being created.

If the operator 4 chooses to cancel or discontinue the test, then a test file record is not created, the inputted information details are not recorded, and the popup window is removed, returning the operator 4 to the test details input page 20. The application prevents the operator 4 from accessing further pages until all of the requested information details are inputted and the option of continuing the test is selected.

By the above actions the management system 2 facilitates recording of critical information relevant to the activity in one place - a file for the activity in the storage means of the computer 6.

The application is operable to record any allowable information detail changes made following a return to Page 2 by execution of a similar continue/cancel procedure as described. The application is operable to determine and record the time and date at which the details are inputted by the operator in the file for presentation in the final report.

Page 3: Test Equipment When Page 3 is selected the application, via the HMI 10, presents to the operator 4 an image in the form of a test equipment input page 21 , as illustrated in Figure 6 of the drawings. The test equipment input page 21 requests information relevant to the test equipment from the operator 4 via a set of pre-set or prompted questions. It includes a plurality of data entry fields into which the operator 4 can enter information such as answers in response to the questions posed. The information inputted by the user 4 is recorded in a file record for the test in the database and displayed in the test equiment input page 21 , by operation of the application software.

The information collected via the test equipment input page 21 includes: o Equipment System Name. This could be, for example, a car or a bike. If car is entered or selected from the relevant drop down box by the operator 4 then the application is operable to automatically enter the serial number for or associated with car testing in to the next edit box "Equipment System Serial Number". Furthermore, all subsequent fields are populated by operation of the application to only show anything related to the equipment system name "Car" in the drop down boxes to help simplify the next selections.

o Equipment System Serial Number ("SN"). This edit box is automatically populated by operation of the application if it matches any of the parameters from the database query. If not it can be manually entered by the operator 4.

o Equipment System Component Name. This could be, for example, Cars - Brakes. The application is operable so that this drop down box will show only previous entries related to the "Equipment System Name" and "Equipment System SN".

o Equipment System Component SN. The application is operable to automatically populate this edit box if it matches any of the parameters from the database query. If not it can be manually entered by the operator 4.

o Equipment System Subcomponent Name. This could be, for example, the cars - brakes - left, front brake calliper. The application is operable so that this drop down box will show only previous entries related to the "Equipment System Name" and

"Equipment System SN" and "Equipment System Component Name" and "Equipment System Component SN".

Equipment System Subcomponent SN. This edit box is automatically populated by operation of the application if it matches any of the parameters from the database query. If not it can be manually entered by the operator 4. Once the operator 4 has entered the requested information into each field, thereby completing Page 3, they execute the Next button on Page 3 via the HMI 10.

The application software then operates to save or store the inputted information details in the test file record recorded in the database and to progress the- operator 4 to the next page in the sequence - Page 4.

Page 4: Photographs

The application is operable to provide the functionality to prompt and enable the operator 4 to take photographs and append individual comments to each photograph via this page. When Page 4 is selected the application, via the HMI 10, presents to the operator 4 an image in the form of a test photo input page 23 as depicted in Figure 7 of the drawings. The test photo input page 23 is provided with a Take Photo button (not shown). Selection of the Take Photo button executes an imaging software application enabling the operator 4 to take photographic evidence relevant to the test, such as of the subject equipment being tested, or the test set up, using the camera that is integrated into the computer 6 and record it in an associated image database of the storage means of the computer 6. Execution of the Take Photo button activates the GPS capabilities of the computer 6 so that the photographic evidence is time and GPS location stamped - Le. the time and GPS location that the test was performed is recorded. This is particularly useful for geographically significant locations as evidence of the action taken. Any suitable imaging software application can be used as are well known to persons skilled in the art.

Recording this evidence is advantageous as it assists in clarifying the test configuration and where it was performed, and is particularly useful in the testing of geographically significant assets such as oil and gas wells. The location stamping provides another means of verifying which test subject a particular test report refers to.

Once the photographs have been taken and the imaging software application closed, the application is operable to show the photographs in the image database as thumbnail images with associated text boxes in a photo table 25 on the test photo input page 23. Clicking or activating the thumbnail images via the HMI 10 opens a popup image window 27 with the photograph in it that fills all or a section of the page, facilitating enhanced viewing of the image only.

Clicking or activating the text box via the HMI 10 results in the application opening a keyboard in the HMI 10 touch screen enabling the operator 4 to add comments or notes including an identifier such as a name to each photograph and subsequently record the same in the image database in the storage means of the computer 6 associated with the relevant photograph. When an image is displayed in the image window 27, any associated comments or notes are displayed in a popup operator notes window 29. The comments or notes may include observations made by the operator 4 in the case it is thought more information is required than has been entered in the earlier fields/pages. Typical entries here may comprise visual inspections to compliment the associated photograph.

The image database is searchable. In this regard, activation of a first column 25A of the photo table 25 executes an image database query application enabling the operator 4 to enter, via the HMI 10, a database query. Images in the image database having associated comments or notes matching or corresponding to a database query are displayed in a second column 25B of the photo table 25. In the example depicted in Figure 7, the database query comprises "Griffin-System, Surface Tree - Component and Production Wing Valve - Subcomponent. The second column 25B displays all of the photos in the image database having associated comments or notes matching or corresponding to the database query in first column 25A.

In the event that the image database already contains photographic evidence relevant to the test, then it may not be necessary for the operator to take photographic evidence using the Take Photo button as hereinbefore described. Rather, the operator may select a suitable photograph from the images in the image database found using an appropriate database query.

An icon (such as a white cross inside a red square) is provided at the top right corner of each photograph. Clicking or activating the icon provides the operator 4 with the option of deleting the photograph from the storage means of the computer 6.

Once the operator 4 has recorded and annotated any desired photographic evidence, they execute the Next button on Page 4 via the HMI 10. The application then operates to progress the operator 4 to the next page in the sequence - Page 5.

At any point after this the operator 4 can navigate the pages via the HMI 10 to return to Page 4 to record additional photographic evidence as described above. Figure 1 C illustrates the operator 4 taking photographic evidence relating to a hydrostatic pressure testing activity using the management system 2.

Page 5: Summary/Comments/Notes

When Page 5 is selected the application, via the HMI 10, presents to the operator 4 an image in the form of a comments/notes or summary input page 22, examples of which are illustrated in Figures 8A and 8B of the drawings.

The application is operable to provide the functionality to open a dialogue box and keyboard on the HMI 10 touchscreen when the comments/notes/summary input page 22 is activated to enable the operator 4 to input comments or notes or provide a summary relevant to the test and subsequently record the same in the storage means of the computer 6. The summary may be a concatenation of information entered so far and be used to summarise the intended test. It may confirm critical criteria or values of the test, such as upper and lower pressure testing boundaries, the duration for which the test must satisfy specified criteria, and may reinforce a maximum pressure that the system or equipment being tested is allowed to see.

Material entered on this page is included in the report generated by the application at the completion of the activity.

Functionality for voice recording is also provided via this page, via which the operator 4 can take spoken notes or observations and record any unusual noises generated during the test in the database, for example.

Once the operator 4 has recorded any desired comments and notes or summary, the user 4 executes the Next button on Page 5 via the HMI 10. The application then operates to progress the user 5 to the next page in the sequence - Page 6. At any point after this the user 4 can navigate the pages via the HMI 10 to return to Page 4 to record additional comments or amend existing ones as described above. Page 6: Test Type

When Page 6 is selected the computer 6, via the HMI 10, presents to the user 4 an image in the form of a test type input page.

The test type input page requests information relevant to the hydrostatic pressure test to be conducted from the operator 4 via a set of executable buttons, each one representing a possible type of test, as follows: o Leak Test: verifies that the subject equipment being hydrostatically pressure tested is structurally sound and leak tight in accordance with identified standards. o Proof Test: verifies that the subject equipment being hydrostatically pressure tested is structurally sound in accordance with identified standards. It does not verify that the equipment is leak tight. o Pressure Graph: a pressure recording option with no test requirements.

The operator 4 selects the required type of test by activating the corresponding button, details of which are then recorded by the application in the storage means of the computer 6.

Once the required test has been selected, the operator 4 executes the Next button on Page 6 via the HMI 10. The application then operates to progress the operator 4 to the next page in the sequence - Page 7. Page 7: Test Criteria

When Page 7 is selected the application, via the HMI 10, presents to the operator 4 an image in the form of a test criteria input page 24, examples of which are illustrated in Figures 9A and 9B of the drawings.

The test criteria input page 24 requests information relevant to the hydrostatic pressure test to be conducted (and selected on Page 6) from the operator 4 via a set of pre-set or prompted questions. It includes a plurality of data entry fields into which the operator 4 can enter information such as answers in response to the questions posed.

The information collected via the embodiment of the test criteria input page 24 depicted in Figure 9A includes: o Equipment Rating. The application is operable to enable this value (number) to be selected from a dropdown box or manually typed in by the operator 4. This number is referenced by the tool 3 for monitoring and generation of over pressure alarms and safety systems, as will be described in further detail below.

o Target Test Pressure. The application is operable to enable this value (number) to be selected from a dropdown box or manually typed in by the operator 4. This number is referenced by the tool 3 for the operators 4 intended test pressure for the selected equipment.

o Test Hold (Minutes). The application is operable to enable this value (number) to be selected from a dropdown box or manually typed in by the operator 4. This number is referenced by the tool 3 for the operator intended test hold period for the selected equipment. This is the duration that the pressure test must satisfy all criteria.

o Test Pressure Tolerance (%).The application is operable to enable this value (number) to be selected from a dropdown box or manually typed in by the operator 4. This number is referenced by the tool 3 for the operators intended test pressure allowable deviation. For example, for a Test Pressure Tolerance of 10% the tool 3 is operable to accept pressures to within + or - 10% of the target test pressure. So for a 5000psi target test pressure with a test pressure tolerance of 10% the tool 3 will accept pressures between 4500psi and 5500psi. These two numbers set first or upper and second or lower acceptable testing boundaries. In this example, any pressure above 5500psi will trigger a response action in the tool 3. In the case where the tool 3 comprises emergency shut down means, described in further detail below, the response action may comprise generation of an overpressure alarm and automatic shut down of the test pump 12. The application is further operable to record this overpressure to the database and write the event to the report to identify that the equipment was over pressure. If the pressure drops below 4500psi the test will not satisfy the criteria and so will not start passing until the pressure is brought back above 4500psi.

o Allowable Loss (%).The application is operable to enable this value (number) to be selected from a dropdown box or manually typed in by the operator 4. This number is referenced by the tool 3 to quantify the amount of pressure that can be lost during the test hold period while the test pressure is within the Test Pressure Tolerance. For example, for a 10% Allowable Loss with the above example the tool 3 is operable to allow up to 500psi pressure loss during the prescribed hold period.

o Test Fluid Used. The application is operable to enable this value

(number) to be selected from a dropdown box or manually typed in by the operator 4. This is referenced by the tool 3 for inclusion in the test report. The owner of the equipment or system being tested will often be interested in this information as most fluids are not interchangeable.

o Test Fluid Cleanliness. The application is operable to enable this value (number) to be selected from a dropdown box or manually typed in by the operator 4. This is referenced by the tool 3 for inclusion in the test report. The owner of the equipment or system being tested will often be interested in this as most equipment has standards that hydraulic fluid must comply to. This cleanliness level can be tested and recorded by operation of the tool 3. This is an example of the benefit of the one tool 3 gathering all required certification information. In the test criteria input page 24 depicted in Figure 9B 1 the answers to the data entry fields are defaulted by the application to the pass criteria of the associated recognised standard that was displayed in Figure 4 when the operator 4 selected what Item Type the test was for. The operator 4 has the option to change these values. If the values are made more stringent than what the recognised standard requires then the application software is operable to state that the test criteria meets the recognised standard. If the operator 4 changes the values to less than the standard test criteria then the application software is operable to state that they do not meet the recognised standard. The information inputted by the operator 4 is recorded in the file record for the test in the database 14 and displayed in the test criteria input page 24, by operation of the application software.

The appearance of the test criteria input page 24 of the embodiment illustrated in Figure 9B, and the information collected thereby varies according to which test type was selected, as follows:

Leak Test Criteria

• Test Pressure (i.e. 1.5xWP) (this is defaulted to the value

associated with the standard that corresponds to the Item Type selected on Page 2: Details)

• Test Pressure Multiplication Factor (TP/WP) (this is defaulted to the value associated with the standard that corresponds to the Item Type selected on Page 2: Details)

• Hold Period minutes (this is defaulted 15 minutes) • Allowable Test Pressure percentage deviation (i.e. ±5%) ± % (this is defaulted to 5%)

• Max Pressure Boundary = psi (Test Pressure + Test Pressure x

Percentage Deviation)

• Min Pressure Boundary = psi (Test Pressure - Test Pressure x

Percentage Deviation)

• Allowable Pressure Drop Percentage (i.e. 1 %) (this is defaulted to

1 %)

• Allowable Pressure Drop = psi (Test pressure x Allowable Pressure Drop Percentage)

• Average pressure drop per minute = psi (Allowable Pressure

Drop/Hold Period)

• The Jest Pressure graph must finish with a decreasing trend.

• These Test Parameters comply with the following standard/s:

(the application is operable to identify if the Test

Parameters abide to any listed standards i.e. the standard that it defaulted to)

Test Notes

Test time starts once pressure is brought into the Test Pressure Boundaries and starts to decrease.

Test passes once it has held pressure between the Test Pressure Boundaries for the Hold Period and meets the leak criteria above. A vertical green line is drawn when the test starts and has passed. A vertical red line is drawn if and when it fails.

Proof Test Criteria • Test Pressure (i.e. 1.5xWP) = (this is defaulted to the value associated with the standard that corresponds to the Item Type selected in the Item Type selected on Page 2: Details)

• Test Pressure Multiplication Factor (TP/WP) (this is defaulted to the value associated with the standard that corresponds to the Item Type selected on Page 2: Details)

• Hold Period (minutes) (this is defaulted to the value associated with the standard that corresponds to the Item Type selected on Page 2:

Details)

• These Test Parameters comply with the following standard/s:

(the application is operable to identify if the Test

Parameters abide to any listed standards i.e. the standard that it defaulted to) Test Notes

Test time starts once pressure is brought above Test Pressure and starts to decrease. Test passes once it has held pressure above test pressure for the Hold Period. If Pressure drops below Test Pressure then test fails. A vertical green line is drawn when the test starts and has passed. A vertical red line is drawn if and when it fails.

Pressure Graph

Max Pressure of graph psi (this sets the pressure range of the graph) Time Period of graph minutes (this sets the time domain of the graph)

No Test Notes required.

The criteria information inputted by the user 4 is used by the application software to determine what is required for the subject equipment to successfully perform (i.e. "pass") the test during a data acquisition procedure, with the decision being made according to the Test Notes above, and as will be described in further detail below.

In practice, many companies have their own testing requirements that are different to recognised standards. The test criteria input page 24 enables the operator 4 to change them to meet any relevant company standards.

Once the requested criteria information details have been entered and recorded, the operator 4 executes the Next button on Page 7 via the HMI 10. The application then operates to progress the user 4 to the next page in the sequence - Page 8. Page 8: Job Safety Analysis

A Job Safety Analysis ("JSA") is a method that can be used to identify, analyse and record 1) the steps involved in performing a specific job, 2) the existing or potential safety and health hazards associated with each step, and 3) the recommended action(s)/procedure(s) that will eliminate or reduce these hazards and the risk of a workplace injury or illness.

On Page 8 the application, via the HMI 10, presents to the operator 4 an image in the form of a JSA input page 26, examples of which are illustrated in Figures 10A and 10B of the drawings. The JSA input page 26 requests information relevant to a JSA of the hydrostatic pressure test to be conducted (and selected on Page 6) from the operator 4 via a set of pre-set or prompted questions that require a tick box to be ticked by the user 4 to confirm that a required action has been taken. The application software is operable, when a box is ticked, to determine the time and date that the user ticked the box and accepted responsibility for completing that part of the JSA, and record details of the same, and the corresponding box ticked, in the file record for the test in the database. These details are included in the report generated by the application at the completion of the activity.

The questions asked on the JSA input page 22 may include, but are not limited to: 1. Have you completed a company JSA?

2. Are all hydraulic fittings rated to the maximum working pressure of ?/Are all fittings rated to XXXXXPSI? (the application is operable to identify and insert the required value to show the working pressure that the operator 4 inputted on Page 2. This is a safety precaution to ensure the components used to perform the test are safe. The actual pressure is updated by the application from the "Target Test Pressure x Test Pressure Tolerance" to ensure that the highest pressure likely to be seen by the equipment or system is considered for the testing components). 3. Are all of the hydraulic lines rated to the maximum working pressure of

? (the application is operable to identify and insert the required value to show the working pressure that the operator inputted on Page 2).

4. Is the test subject rated to the maximum working pressure of ? (the application is operable to identify and insert the required value to show the working pressure that the operator inputted on Page 2).

5. Is the area barricaded off?

6. Is there a physical barrier between the test area and personnel?/Do you have pressure testing barriers up? (this is an industry standard safety precaution to ensure bystanders are aware of the hazardous activity taking place. To add more meaning to and increase the effectiveness of the barriers, the management system 2 comprises safety means in the form of an active barrier light system as will be described in further detail below.

7. Have you connected the Pressure Transmitter to the hydraulic circuit?

8. Is all air bled from the test system? 9. Are the wireless (or wired) pressure alarm lights (where provided) positioned next to the test body and pump and are turned on? 10. Do you have a mechanical pressure gauge in the system? (this is a safety precaution to ensure plurality of the live pressure reading in the case there is a failure in the tool 3).

11. Company JSA? (most companies have a comprehensive safety policy for hazardous tasks such as pressure testing. Files including text detailing a relevant company JSA may be uploaded to the tool 3 and displayed in an edit box via the HMI 10).

12. I comply with and agree to the JSA text above? (this comprises confirmation by the operator 4 of the company JSA). Once all of the boxes have been ticked, the operator 4 executes the Next button on Page 6 via the HMI 10. The application then operates to progress the operator 4 to the next page in the sequence - Page 9.

In the event that the operator 4 presses the Next button before ticking all of the boxes, the application is operable to generate and present a popup window requesting the operator 4 to tick all boxes. This loops until all of the boxes are ticked. In embodiments of the invention, security is provided in the form of a password protected Management of Change ("Management of Change") function for the need of special circumstances where some conditions cannot be met. Typically, only management would be authorised to override this function and the application is operable to record such action and include it in the report.

In this manner the system provides a safety gate - as the operator 4 has to confirm that they have completed the JSA and assume responsibility for it before they are allowed to continue further with the activity.

When opening a partially completed test the JSA must be performed again prior to the system recording any more pressure (as described below). Any pressure that had been recorded prior to reopening the partially completed test will be shown in the report. Page 9 - Data Acquisition and Pressure Graph

Having completed the JSA the application is operable to open a pressure graph and begin to record pressure from the wireless pressure transmitter sensor 16. At this stage the computer 6 is operable to generate and send a signal to turn on warning lights 27 of an active barrier light system if provided, and discussed in further detail below. If at any point prior to this stage the wireless pressure transmitter sensor 16 senses any pressure above a predetermined amount that was considered dangerous (i.e. 10psi) then the lights 27 would have been signalled to turn on. The lights 27 will not turn off until the pressure transmitter pressure reading falls below the predetermined amount.

The lights 27 provide an active warning system to prevent personnel from coming close to the test area. This is much safer than always leaving lights on or relying on personnel to actively turn the lights on or off.

During the test, the wireless pressure transmitter sensor 16 measures the pressure in the hydraulic circuit and communicates the measured pressure information data to the computer 6. The application is operable to record the received data in the database in association with the file record for the test. The application is further operable to process and interpret the received data, along with the information previously inputted by the user 4, to generate a performance result on the basis thereof.

In the embodiment described, the processing comprising using an algorithm to analyse and predict test results and to interpret the test data to be a pass or fail performance result, and generating a pressure graph which is presented to the user on Page 9 of the sequence of electronic pages as an image in the form of a pressure graph page 28, examples of which are illustrated in Figures 11 A, 11B and 11C of the drawings. The application is operable to determine if the test is a pass or a fail and predict if the test is going to pass or fail by determining if the pressure decay is an increasing or decreasing trend.

Details of the analysis and pressure graph, for the embodiment described, are as follows:

Axis

The pressure graph is an x/y graph with pressure on the vertical axis and time on the horizontal axis.

The pressure graph samples the pressure x time at high frequencies (up to 400Hz in the embodiment described) and displays pressure x time, rate of pressure change, and rate of the rate of pressure change (pressure second derivative).

Generation of these additional rates facilitate determination of whether a test achieves a desired performance result or not (i.e. is a pass or a fail), particularly if specified to have a decreasing leak trend. Furthermore, generating and displaying the second derivative provides an indication early on in the test of whether the test is likely to pass or fail.

The left hand vertical scale is in pounds per square inch ("psi"), the right hand vertical scale is in psi/min.

Via the graph the application software is operable to display the current Δpsi/Δmin value and state if the trend is decreasing or increasing by its value being positive or negative. The graph may also plot the Δpsi/Δmin values as it does the psi/min.

The pressure range is initially from zero to the predetermined maximum pressure. This predetermined maximum pressure depends on the test type.

For Leak and Proof Tests the application is operable to identify when the test has started and only for Leak tests will it then automatically zoom between minimum and maximum test pressure boundaries. Further to this it can be manually zoomed by the operator 4 via the HMI 10.

Leak Test Range

• Pressure Range: o max pressure range = 2xWP+2xDeviation, wherein WP is the Maximum

Working Pressure. o min pressure range (for autozoom) = 2xWP-2xDeviation o min pressure range (for manual) = Opsi

• PSI/min scale: o min = 3xAverage Pressure Drop per minute o max = -Average Pressure Drop per minute. Proof Test Range

• Pressure: o max pressure range = Test Pressure + IOOOpsi o min pressure range (for autozoom) = does not zoom in once test time starts as it in Leak Test - it is always in manual zoom mode o min pressure range (for manual) = Opsi

Psi/min range assumes the default pressure decay rate of a Leak Test: o min = 3xAverage = 3xAllowable Pressure Drop/Hold Period = 3xTest Pressurexi %/1 δminutes = 0.002xTest Pressure o max = -Average = -Average Pressure Drop/Hold Period = -Test Pressurexi %/1 δminutes = -Test Pressure/1500

Pressure Graph Range • PSl: o max pressure range = Max Pressure of Graph o min pressure range (for autozoom) = does not zoom in as in Leak Test - it is always in manual zoom mode o min pressure range (for manual) = Opsi.

• Psi/min: o min = autozoom o max = autozoom

For Leak Test and Proof Test the time domain defaults to 2 x test duration however it can be manually scaled.

For Pressure Graph the time domain is equal to the value of the operator 4 inputted on Page 6: Criteria.

The time domain shows time and date (in 2400hrs) and time elapsed in hours: minutes. Trends

In the embodiment described, the application is operable to plot two trends: a pressure (psi) trend and a pressure versus time (psi/min) trend.

The pressure trend is represented by a thick pipe (grey gradient) with a blue line inside. The pressure versus time trend is a thinner line of different colour. Each labelled axis matches the colour of its trend. The psi trend is always on top of all other lines in the embodiment described.

Sampling rate is 2/sec.

Features

A horizontal line is drawn at the maximum and minimum test pressure boundaries. A vertical green line is drawn representing when the test first starts. The application software determines this from when the pressure starts to decrease within the upper and lower pressure boundaries. A second vertical green line will be drawn when the test meets the input test criteria and, on such event, the application software operates to generate a dialog box informing the user of the successful performance of the test - namely that the test has passed because the inputted test criteria have been satisfied.

The application is further operable to count what the pressure drop has been over the last test time period (for example, 10 minutes) and to display this information in a dialog box.

If at any stage during a leak test (i.e. after the first vertical green line) the pressure trend begins to decay with an increasing trend (this could be due to temperature change or leak) a vertical red line will be drawn indicating that the test has failed or the operator has increasing the pressure by means of turning the pump on again. When and if the trend changes to a decreasing trend and is still within the upper and lower test pressure boundaries another vertical green line will be drawn indicating the start time of a new test period.

If the application determines that the performance of the subject equipment was not satisfactory, namely that the test has failed because, for example, the inputted test criteria have not been met, it is operable to draw a vertical red line and generate a dialog box informing the user 4 that the test failed.

The vertical green and red lines are annotated so as to not require a legend.

A "Test Complete" button is provided on Page 8, upon activation of which the application is operable to end the data logging session, record the analysis in the database, and progress the user 4 to the next page in the sequence - Page 9.

In alternative embodiments of the invention, alternative processing and interpretation techniques are used according to the activity being managed. In an embodiment of the invention, the application is operable to display values of the received data, and the performance result on the basis of the processing and interpretation thereof, live and in real time via the HMI 10 in a graphical display comprising a set of gauges, examples of which are depicted in Figures 12A, 12B and 12C of the drawings. In the embodiment described, there are four gauges in the set of gauges - respectively Pressure, Test Timer, Allowable Loss, and Leak Trend.

The live values are displayed in a way that is designed to be very easy to read and understand. In this regard, the set of gauges comprise a centrally positioned dual dial pressure gauge 31 which makes small changes easy to notice. The gauge 31 has its full scale set at 1.5 x the required test pressure (i.e. set to 50% higher than the expected maximum pressure) to maximize displayed analogue movement, and an outer scale set to between 0-1000psi. This advantageously ensures that small pressure changes are more distinguishable and likely to be noticed by the operator 4. In this regard, on a typical IOOOOpsi gauge and chart recorder, conventionally used, it is very difficult to detect a 50psi change.

First and second vertical gauges 33A and 33B either side of the dual pressure gauge 31 display and compare pressure lost during the hold period to the remaining hold period. The two vertical gauges 33A and 33B are compared to each other while the test is within the specified pressure band.

The first vertical gauge 33A, also referred to as a Test Timer gauge, (positioned on the left of the gauge 31) displays the remaining hold period of the test and has its full scale set to whatever the required test hold period is, such as 15min for example. The second vertical gauge 33B, also referred to as a loss gauge, (positioned on the right of the gauge 31) displays the remaining allowable pressure loss and has its full scale set to the allowable pressure loss over the hold period, such as 40psi for example. Thus, in the first and second vertical gauges 33A and 33B the tool 3 magnifies the two main values required to determine the tests outcome (pressure loss over the given hold period). Allowable pressure loss is spread across the full scale of one gauge and the required hold period is spread across the full scale of another gauge.

Display of raw data in this manner makes it very easy for the operator 4 to compare the first and second vertical gauges 33A and 33B during the test by watching the two vertical gauges 33A and 33B falling together, to see how the test is performing as for the test to pass the hold period gauge needs to count down to 0 seconds before the maximum pressure loss gauge has reached Opsi. That is, if the Test Timer gauge 33A on the left reaches the bottom (i.e. expires or reaches 0) before the loss gauge on the right (i.e. before the maximum allowable pressure loss has been accrued) then essentially the test will pass providing it is of a decreasing leak trend. These gauges are the same size and when both set to full scale for any test are much clearer and easier to read and to compare side by side than on a typical paper chart, where a line representing pressure is drawn over the chart and the relevant horizontal and vertical increments are on such a small scale that even significant pressure changes are difficult to see. Other tests will require a leak trend to be decreasing. This is displayed graphically on a progress bar on the far right - representing a leak trend gauge 33C). This is a very clear graphical way to see how a test is performing, particularly if comparing this to a thick pen line on a finely graduated paper chart, as is conventionally done. The leak trend gauge 33C graphically quantifies whether the test is holding perfectly (i.e. no gain and no loss, a perfect flat line), has an increasing leak trend (the system is losing pressure at a steady or increasing rate), or has a decreasing leak trend (the system is losing pressure but is losing less pressure at each subsequent unit of time, i.e. the test is improving).

This information is critical as most test criteria specify that a test must have a decreasing leak trend. This means that if the system is losing pressure then it must be of an improving nature. The performance of a test can be predicted early on with this information. If the leak trend gauge 33C shows an increasing leak trend then there is no way the test will pass. Time will be wasted attempting to get a test with this characteristic so the sooner it is identified by the operator 4 the better, as appropriate action can be taken such as venting the system and investigating the leak source. By analysing and interpreting the data collected during the test in real time, and displaying the results thereof, human interpretation of typically difficult to read and interpret data is not required and removed from the process. Furthermore, providing an early indication of whether the test is likely to pass or fail results in efficiencies as it prompts the operator 4 to take corrective or remedial action in respect of the subject equipment sooner, avoiding time been wasted by the operator 4 persisting with a failing test.

Furthermore it is not the operator 4 determining whether the test passes or not. Success is determined by the tool 3 on the basis of the sensed data and the values entered by the operator 4 before the test started. The tool 3 will either pass or not pass the test; there is no grey area or room for discussion. The only way for the operator 4 to make a border line test that is failing to pass is to either fix the leak or change the testing criteria. The graphical display allows the operator to see how the test is performing, not influence the outcome.

The results are much easier for the operator 4 to view via the HMI 10 than on a paper chart as the axis can be scaled to zoom into the information making it easier to understand the recorded data.

Page 10: Report Once the testing has been completed the application is operable to automatically generate a report on the same and present the same to the operator 4 on Page 10 in a report image page 30. An example of this is illustrated in Figure 13 of the drawings. The report includes all of the information from Pages 1 to 9 (both inputted by the operator 4 and collected via the wireless pressure transmitter sensor 16).

For Leak Tests a graph on a front page of the report will only show the zoomed in section of the test passing or failing.

For Proof Tests a graph on the front page will only show the results (not zoomed), showing pass or fail results displayed on the graph at the point of passing or failing.

For Pressure Graph on the front page will only show the last lot of result showing when the testing was terminated.

An appendix of the report comprises a Test History showing the complete test history with both pressure and time scales set to default i.e. no auto-zooming or manual zooming. This may cover multiple pages.

Another appendix of the report comprises the photographic evidence.

The necessary information is gathered on the one tool (the management tool 3) by the one person (the operator 4) at the time of the actual test. This reduces the likelihood of data being lost or misplaced (such as photographic evidence, notes, details of how the test was performed, and the test results themselves).

In this manner it can be seen that the embodiment of the invention ensures that critical information regarding what the test was for is recorded in a central depository. In this way it overcomes problems of prior art methods for such testing utilising paper charts, paperless charts or dataloggers where critical information on what the test was for is often not recorded, or if it is it may not be kept with the pressure recordings, rendering the test pressure recordings useless. Page 11 : Finished

Once the report is generated, the application is operable to enable the operator 4 to navigate to and access the final page in the sequence - Page 11.

The application is operable to provide the following functionality via this page: o Repeat Test - execution of this function returns the operator 4 directly to Page 8: Job Safety Analysis with all inputted details regarding Test Details, Type and Criteria the same. o New Test (Same Project/Asset) - execution of this function returns the operator 4 directly to Page 2: Details with all Project/Asset related inputted details the same. o New Test - execution of this function returns the operator 4 directly to Page 2: Details with all details cleared.

This page increases the efficiency of doing repeated tests, for either a test that did not pass due to leaks, (following which the leak was fixed and retested), or for testing many of the same items that have the same or similar details.

Figures 14A to 14C of the drawings shows a flow chart of operation of the HMI 10 during a hydrostatic pressure testing activity.

Test Summary

In embodiments of the invention, the application, prior to allowing the operator 4 to access the JSA input page 26, is operable to present to the operator 4 an image in the form of a test summary input page via the HMI 10.

Testing equipment to a standard of a classification society requires a great deal of understanding of the standard and equipment to be used. Via the test summary input page, the application is operable to provide a wizard for testing to a classification society standard. This wizard is operable to ask particular questions in a particular order to determine the required test parameters to meet a particular standard.

The test summary input page requires the operator 4 to read through the critical values of the test to confirm they understand what is required, and to provide confirmation of the same, before access is granted to the JSA input page 26. Figures 15A to 15H of the drawings depict flow charts of the operational steps performed by the wizard in the case where the standard is the ISO 10423 Petroleum and natural gas industries - Drilling and production equipment - Wellhead and Christmas Tree Equipment.

Figure 15A is a high level flow diagram for the ISO 10423 wizard. From use of this wizard, the operator 4 can determine what the pressure testing requirements are (under the ISO 10423 standard) for the piece of equipment the operator 4 will be testing.

The steps involved include the following.

1 ) Select Equipment Execution of this facility by the operator via the HMI 10 gives access to a library of pieces of equipment that is covered by ISO 10423. This library not only includes the different types of equipment recognised by this standard but also all of the different sizes and pressure ratings that are recognised and covered by the standard. Examples of equipment include, but are not limited to: flanged end and outlet connections, casings, tubings, full bore valves, regular and venturi bore valves, check valves, choke valves, casing and tubing heads and hangers, tubing- head adaptors, tees and crosses, adaptors and spacer spools, actuators, packing mechanisms, top connectors, surface and underwater safety valves, bullplugs, valve-removal plugs, back-pressure valves, connectors and fittings, and Christmas trees.

2) Original Equipment Manufacturer ("OEM") The operator will have to select if the equipment is a newly assembled OEM piece of equipment or if it a refurbished item. For an newly assembled OEM item the software application then asks the operator 4 what the pressure rating of the equipment is and if it will be exposed to gas, and if that gas contains H 2 S. From these answers the software application is operable to determine and display to the operator 4 via the HMI 10 what the minimum Product Service Level ("PSL") Level requirement is for the equipment. The operator 4 can select higher, but not lower in order to be in accordance with ISO 10423. This selected PSL Level, along with the selected equipment type, determines the pressure testing requirements for the equipment. The software application is then operable to step the operator 4 through the procedures in order to achieve these minimum requirements and automatically document them.

3) Refurbished

For refurbished OEM equipment, first the operator 4 must select what the original OEM PSL Level was. After selecting this they must then select the Refurbishment

Level ("RL") Level. The RL can be equal to or less then the OEM PSL level, but not higher. This selected RL Level, along with the selected equipment type, determine the pressure testing requirements for the equipment. The software application is then operable to step the user through the procedures in order to achieve these minimum requirements and automatically document them.

Bolt Tensioning

To ensure that a fastener performs in its application as intended, it must be adequately tensioned. Bolt tensioning is an activity undertaken to achieve this.

Figure 1 B illustrates the management system 2 in use in a bolt tensioning activity. The management system 2 is operable, via an interactive electronic procedure, to step the operator 4 through a procedure of assembling and disassembling recognised bolt flanges or individual bolts according to specified tensioning requirements, recording each process or action taken and generating a report thereon.

The operator firstly takes the required action to prepare the subject equipment for tensioning, including identifying the subject flange or bolt, and operably connecting a hydraulic bolt tensioning jack or hydraulic torque tool 37, and pump 12 via lines 14 to create a hydraulic circuit and taking any required or specified safety precautions.

The operator 4 then operably couples a sensor 16 from the set of sensors to the subject equipment to sense and gather tensioning data related to the tension of the subject equipment during the tensioning activity and communicate it to the computer 6. In the embodiment described the sensor is a wireless pressure transmitter (such as Electrochem's PS 1 sensor) mechanically connected to the hydraulic circuit and in wireless data communication with the computer 6 so as to allow sensed data to be logged thereby. To manage bolt tensioning using the system 2, the operator 4 executes the application and the bolt tensioning activity thereof via the HMI 10. Upon execution of the bolt tensioning activity, the application is operable to generate and present via the HMI 10 a series or sequence of electronic procedures that are gated to step or guide the operator 4 through a list of tasks required to be performed to complete bolt tensioning. Progression through the pages by the operator 4 results in the application receiving and recording information relevant to the bolt tensioning. Once all of the pages have been completed by the operator 4 the application is operable to automatically generate a report on the bolt tensioning on the basis of the recorded information. As in the case of the hydrostatic pressure testing activity hereinbefore described, the operator 4 is able to navigate the pages and select a particular page by touching or clicking on labelled tabs associated with each page via the HMI 10. The tabs are displayed so as to traverse sequentially from left to right across the touchscreen display 8 of the computer 6, starting at bolt tensioning ("BT") Page 1. The user's navigation of and access to the BT pages operates in a corresponding manner to that of the pages for the hydrostatic pressure testing activity.

The electronic BT pages generated by the application, and their sequence, are as follows: BT Page 1: File

BT Page 1 operates in a similar manner, and provides similar functionality, as Page 1 of the hydrostatic pressure testing activity, with the differences being that the functions provided by BT Page 1 are in respect of tensioning rather than testing, and a Bolt Tensioning Standards function is provided (relating to standards for bolt tensioning), rather than a Pressure Testing Standards function.

BT Page 2: Name/Details

When BT Page 2 is selected the application, via the HMI 10, presents to the operator 4 an image in the form of a tensioning input page. The tensioning input page requests information or details relevant to the tensioning activity or job to be conducted from the operator 4 via a set of pre-set or prompted questions. It includes a plurality of data entry fields into which the operator 4 can enter information such as answers in response to the questions posed. The information inputted by the operator 4 is recorded in a file record for the tensioning activity in the database and displayed in the tensioning input page, by operation of the application software.

To assist the operator 4 in providing the requested information, a knowledge base software application is accessible by the operator 4 from BT Page 2. The knowledge base application provides an interactive library or repository of information regarding the activity topic (tensioning in this case). The library lists industry recognised flanges and bolts that the user 4 can select from, their specifications, and comprises information relevant or related to assembling flanges and bolts, including, for example, flanges, bolts, industry standards, hydraulic torque tools, hydraulic bolt tensioners βacks), lubricants and their associated friction coefficients, thread compounds, and gaskets.

The information collected via the tensioning input page includes: o Selection of flange/individual bolt/stud to be tensioned. o For flange, selection of what type of flange to be mated from a list of recognised flange types and sizes. o For bolt/stud, the application is operable to recommend what types of bolt/stud, for example diameter, pitch, strength/grade, standard, stainless or not, surface finish (Galvanized, Phosphated, Zinc, Chromated, polytetrafluoroethylene (PTFE), etc), thread type (Unified or

Metric), to use for a specific flange type, and to optionally allow the operator 4 to select a bolt/stud from a list that can be used for that type of flange in accordance with recognised standards. o Selection of hydraulic bolt tensioner. The application is operable to provide a list of all hydraulic bolt tensioning jacks and torque tools currently available on the market that are capable of pre-tensioning the selected bolts/flanges. o If a jack is selected the application is operable not to require information details regarding lubrication, coefficient of friction, or torque as they do not apply, and will proceed directly to a calculation of Pressure Vs

Tension, described below. The library contains and shows a pressure/pre-tension constant for all listed jacks. If the jack the operator 4 is using is not listed in the library to select from, the operator 4 can select an "other" option which will enable them to manually type in the pressure/tension constant, or type in the working pressure area, or inside diameter ("ID") and outside diameter ("OD") of working pressure, in which case the application is operable to calculate the corresponding pressure/tension constant therefrom. The area over which the pressure acts can be calculated by the equation A=π(OD 2 -ID 2 )/4. Force=P.A). o If a torque tool is selected, the application is operable to require information details regarding lubrication, coefficient of friction, and torque to be inputted. The library contains and shows a pressure/torque constant for all listed torque tools. If the torque tool the operator 4 is using is not listed in the library to select from, they can select an "other" option which will enable them to manually type in the pressure/torque constant. o For lubrication, the application is operable to recommend what type of lubrication to use, and to allow the operator 4 to optionally select the lubrication from a list of types available on the market. o For coefficient of friction, the application is operable to list the published coefficient of friction as a function of the flange, bolt & lubrication types. Functionality is provided to allow the operator 4 the option to manually change this.

After all of the requested information details have been entered (relating to assembling/disassembling a particular flange, for example) the application is operable to process, analyse and interpret the input data. In the embodiment described, this comprises determining or calculating what pressure the hydraulic bolt tensioning jack or hydraulic torque tool requires to tension the bolts in the flange to the correct amount. This is done as follows: o Torque: application is operable to calculate and inform the operator 4 (via the HMI 10) of the torque required to achieve a pre-tension. This is a function of the flange, bolt and lubrication types. o Pressure Vs Tension: the application is operable to determine and inform the operator 4 (via the HMI 10) of the relationship between pressure and tension. o Pressure: the application is operable to determine and inform the operator 4 (via the HMI 10) of the pressure required to achieve the desired bolt pre-tension. o Pre-Tension: the application is operable to determine and inform the operator 4 (via the HMI 10) of the bolt pre-tension required to mate the flange correctly in accordance with recognised standards.

The application is operable to automatically create or generate a file name for the tension file record recorded in the database, and to update it every time that the operator 4 types in or otherwise changes the details inputted in response to the questions. Once generated, the file name is displayed at the bottom of each page to the left of the Next button (bottom right hand corner).

Once the operator 4 has entered the requested information into each field, thereby completing BT Page 2, they execute the Next button on BT Page 2 via the HMI 10. A popup window is then presented to the operator 4 via the HMI 10 displaying the generated file name for the tensioning with the options of continuing or cancelling the tensioning.

If the operator 4 chooses to continue the tensioning the application software then operates to save or store the inputted information details in a tension file record recorded in the database and to progress the operator 4 to the next page in the sequence - BT Page 3. At any point after this the operator 4 can navigate the pages via the HMI 10 to return to BT Page 2 to view or change any of the inputted information details with the exception of those details used to create the file name which the application will not permit to be changed so as to facilitate auditing.

If the operator 4 chooses to cancel or discontinue the tensioning, then a test file record is not created, the inputted information details are not recorded, and the popup window is removed, returning the operator 4 to the tensioning details input page. The application prevents the operator 4 from accessing further pages until all of the requested information details are inputted and the option of continuing the tensioning is selected.

The application is operable to record any allowable information detail changes made following a return to BT Page 2 by execution of a similar continue/cancel procedure as described.

BT Page 3: Photographs

BT Page 3 operates in a similar manner, and provides similar functionality, as Page 4 of the hydrostatic pressure testing activity, with the difference being that the evidence to be recorded relates to the tensioning activity, such as the flange/bolt being assembled and the equipment being used, rather than pressure testing.

BT Page 4: Comments/Notes/Summary

BT Page 4 operates in a similar manner, and provides similar functionality, as page 5 of the hydrostatic pressure testing activity, with the difference being that the comments/notes to be recorded relate to the tensioning activity rather than testing.

BT Page 5: Job Safety Analysis

On BT Page 5 the application, via the HMI 10, presents to the operator 4 an image in the form of a JSA input page. The JSA input page requests information relevant to a JSA of the tensioning to be conducted (and selected on BT Page 2) from the operator 4 via a set of pre-set or prompted questions that require a tick box to be ticked by the operator 4 to confirm that a required action has been taken. The application software is operable, when a box is ticked, to determine the time and date that the operator 4 ticked the box and accepted responsibility for completing that part of the JSA, and record details of the same, and the corresponding box ticked, in the file record for the tensioning in the database. These details are included in the report generated by the application at the completion of the activity.

The questions asked on the JSA input page include, but are not limited to, ones related to setting up the equipment required for the activity, such as a hydraulic jack, pump, lines, wireless pressure transmitter, the bolts being tensioned, and nuts, flange, lubricant etc involved.

Once all of the boxes have been ticked, the operator 4 executes the Next button on BT Page 5 via the HMI 10. The application then operates to progress the operator 4 to the next page in the sequence - BT Page 6. In the event that the operator 4 presses the Next button before ticking all of the boxes, the application is operable to generate and present a popup window requesting the operator 4 to tick all boxes. This loops until all of the boxes are ticked.

In this manner the system provides a safety gate - as the operator 4 has to confirm that they have completed the JSA and assume responsibility for it before they are allowed to continue further with the activity.

When opening a partially completed bolt tensioning file the JSA must be performed again prior to the system continuing with any of the procedures.

BT Page 6: Procedure, Data Acquisition and Graph When BT Page 6 is activated the application, via the HMI 10, presents to the operator 4 an image in the form of a tensioning procedure page.

The application is operable, via this page, to step or guide the operator 4 through the procedure of assembling or disassembling the flange/bolt according to the activity. The procedure is in accordance with recognised published standards and an indication of conformation with these standards is included in the report generated by the application at the completion of the activity. The application is operable to generate to scale an animated drawing of the flange to assist in showing the operator 4 how to assemble or disassemble the flange in accordance with the procedure. The bolts in the animation are numbered and the procedure instructs the operator 4 to label the bolts the same. The procedure indicates via text and with the animated drawing the order in which to do the bolts/studs up and to what pressure to achieve the required bolt/stud pre-tension. Typically flange mating procedures require the bolts to be done up in a criss-cross pattern in loading increments of 30%, 60% and 100% of the defined final pre-tension. This allows the loads to be evenly distributed to minimise the danger of damaging the flange gasket and allows time for any creep/relaxation to have finished prior to the final load being applied.

Whilst the operator 4 carries out the steps of the activity according to the instructed procedure, the wireless or wired pressure transmitter sensor measures the pressure that the hydraulic bolt tensioner or torque tool is applying to the bolt/stud and communicates the measured pressure information data to the computer 6. The application is operable to record the received data in the database in association with the file record for the tensioning. The application is further operable to process, analyse and interpret the received data, along with the information previously entered by the operator 4, to generate a performance result based thereon.

In the embodiment described, the performance result comprises a graph, generated in real time, of the pressure, the theoretical torque and pre-tension that the hydraulic bolt tensioner or torque tool is applying to the bolt/stud.

The application is operable to display the graph to the operator 4 on the tensioning procedure page and inform them once the required pre-tension has been achieved via an alert, which may comprise a visual and/or audio alarm. It is further operable to automatically record and label such a graph for every bolt for all increments (i.e. 30%, 60%, and 100%). These are included in the report generated by the application at the completion of the activity. Every time the procedure instructs the operator 4 to apply pressure to the hydraulic torque tool or jack the computer 6 is operable to generate and send a signal to turn on the warning lights 27 of the active barrier light system if provided, and discussed in further detail below. If at any point prior to this stage the pressure transmitter sensor senses any pressure above a predetermined amount that is considered dangerous (i.e. 10psi) then the lights 27 would have been signalled to turn on regardless of the stage of the procedure. The lights 27 will not turn off until the pressure transmitter pressure reading falls below the predetermined amount. The lights provide an active warning system to prevent personnel from coming close to the test area. This is much safer than always leaving lights on or relying on personnel to actively turn the lights on or off.

The necessary information is gathered on the one tool (the computer 6) by the one person (the operator 4) at the time of the actual bolt tensioning activity. This reduces the likelihood of data being lost or misplaced.

In this manner it can be seen that the embodiment of the invention ensures that critical information regarding the tensioning is recorded in a central depository. In this way it overcomes problems of prior art methods which result in a paper trail where critical information is often not recorded, or if it is it may not be kept with the corresponding criteria information, rendering the recordings useless.

BT Page 7: Report

Once the tensioning activity has been completed the application is operable to automatically generate a report on the same and present the same to the operator 4 on BT Page 7 in a report image page. The report includes all of the information from BT Pages 1 to 6 (both the data inputted by the operator 4 and by the wireless or wired pressure transmitter sensor), including all steps taken and recorded during the process of assembling/disassembling the flange/bolt. The application is operable to save the report in pdf format in the database, and download the same onto an external device via USB on request, enabling the report to be viewed via the HMI 10 or on another device if downloaded thereto.

An appendix of the report comprises the photographic evidence and comments. BT Page 8: Finished

Once the report is generated, the application is operable to enable the operator 4 to navigate to and access the final page in the sequence - BT Page 8.

The application is operable to provide the following functionality via this page: o Repeat Tensioning - execution of this function returns the operator 4 directly to BT Page 5: Job Safety Analysis with all inputted details the same. o New Tensioning - execution of this function returns the operator 4 directly to BT Page 2: Details with all details cleared.

This page increases the efficiency of operations if there are multiples or a plurality of the same type of flange or bolt that are to be mated.

Calibration

In another embodiment of the invention, the system allows a calibration activity to be managed, guiding the operator through the tasks of the activity and a JSA, allowing on site calibration of hydraulic equipment such as gauges and pressure relief valves, and generating a detailed test report thereon.

This is advantageous as it avoids the equipment being required to be sent offsite for calibration.

Other Activities The management system 2 allows the further activities available on the Start application window to be similarly managed, guiding the operator 4 through the respective tasks of the activities and a JSA and generating a report thereon.

Safety Means As mentioned above, in an embodiment of the invention, the management system 2 further comprises safety means in the form of an active barrier light system. The barrier light system comprises a plurality of lighting devices in the form of warning lights 35 operably coupled to the computer 6 to receive control communications or signals therefrom and used as personnel safety barriers signalling the presence of danger.

In use, the lighting devices are placed by the operator 4 at the extremity of and any entry points to an area where a hazardous activity is being managed via the management system 2, and operable to display by means of illuminated green, orange or red lights an indication of the level of hazard or danger present in the area as follows: green - no unusual hazard; orange - hazardous activity recently completed or about to commence, red - hazard present.

The application is operable to process received data to determine the hazard present and send control signals to the lighting devices to light them accordingly. For example, in the case of a hydrostatic pressure testing activity, when the received data indicates that the subject system is pressurised (and hazardous), the application is operable to generate and send a wireless or wired signal to the lighting devices to illuminate red. When the received data indicates that the subject system has been vented, the application is operable to generate and send a wireless or wired signal to the lighting devices to illuminate orange, and subsequently green as time passes.

By actively providing an indication of the level of hazard present, the barrier light system is more likely to be heeded than passive barrier means, such as "danger" tape that is typically erected to demark a hazardous area. In other embodiments of the invention, the management system 2 further comprises remote inspection means, such as wireless inspection cameras and wireless hydrophones, operable to gather preferably live data or information relating to a subject that may be either hazardous itself (such as a hydraulic system under pressure) or in a hazardous or difficult to access area, and communicate the sensed data/information to the computer 6 for display to the operator 4 via the HMI 10. Functions of the remote inspections means (such as pan, tilt and zoom in the case of a camera) are controllable in real time by the operator 4 via the HMI 10. This is advantageous as it reduces the need for personnel to be physically near the subject and associated hazard. For example, typically operators inspect pressurised systems to find leaks as they are usually only visible or apparent when the system is pressurised. A series of wireless cameras can be placed in a pressure testing bay and used to inspect areas of known or suspected weakness without an operator being exposed to the dangers of a leaking pressurised system.

Hydrophones are underwater acoustic tools that are used in such an embodiment to listen to and record signature sounds emanating from or near a subject, such as underwater hydraulic and mechanical components. The application is operable to process, analyse and interpret the sounds, by comparison with a knowledge base of identified sounds, to determine what they may be indicative of (such as normal operation or imminent failure, for example) and display the results of the determination to the operator 4 via the HMI 10, who can then take appropriate action. It allows for inspection of subject equipment that may not be able to be visually inspected. For example, in the event that a visual indicator on a valve is damaged, it could facilitate its inspection by enabling the operator 4 to listen to it open and close.

In further embodiments of the present invention, the management system 2 may further comprise actuating means or control means coupled to the computer 6 to receive control communications or signals therefrom and operably coupled to the subject of the activity to act thereon in response to a received control communication or signal. Operation of the actuating or control means is facilitated by the operator 4 via the HMI 10. This allows extra functionality. For example the operator 4 may choose to shutdown or activate certain pieces of equipment allowing them perform certain tasks otherwise not possible. On the satisfaction of prescribed criteria, the application is operable to automatically control the actuating or control means and the subject equipment coupled thereto. This may comprise, for example, operating valves to turn a pump on and control it. In embodiments of the present invention, the management system 2 may further comprise safety means in the form of a "dead man switch" operably coupled to the computer 6 via wire or wirelessly. In such a case the application is operable to require the operator 4 to activate the switch and another operator to activate the equipment associated with the activity (such as a pump) for it to operate (such as a torque head in the case of a bolt tensioning activity). This may reduce accidents where personnel sustain injuries, such as serious hand injuries, as a consequence of confused communication.

An Emergency Shutdown Device ("ESD") (not shown) may be fitted before the power supply to the pump 12. If the application determines that a prescribed emergency event has occurred (such as, for example, the pressure has breached an upper pressure boundary) the application is operable to control actuating or control means to take an emergency action (such as, for example, closing the pumps supply solenoid to prevent further over pressurisation).

Another safety advantage provided by embodiments of the present invention is that any over pressures are recorded to the database and published to the final report. Conventionally, it is not unusual in a case where a test accidentally goes above the upper pressure boundary on a paper chart for that chart to be disposed of and a new one started. The likelihood of over pressures due to human error may be lessened with the knowledge by the operator that such an occurrence will be permanently recorded by the tool 3. Test Mimics and Schematics

"Test Mimic" is an expression used to describe a drawing that mimics the three dimensional physical representation of a hydraulic body showing where hydraulic fluid travels within the body. It is essentially a schematic that looks like the physical object instead of just lines and symbols. A "mimic" is indicative of the test whereas a "schematic" is an approved engineering representation of the circuit.

Schematics are quicker to create and quite often easier to understand and problem solve than mimics, although both are useful. Test mimics also provide a graphical view of what components saw, such as during a pressure test activity, for example.

As hereinbefore described in relation to management of the bolt tensioning activity, to assist the operator 4 in providing the requested information, a knowledge base software application is accessible from BT Page 2.

In embodiments of the invention, the knowledge base is expanded to be applicable to all activities available to be managed, and the application is operable to provide the functionality to enable the operator 4 to access files of it appropriate to the activity being undertaken. Furthermore, it is operable to provide a visual representation/schematic on the computer 6 via the HMI to assist the user 4 in conducting the intended procedure of the activity. In the case where a pressure test procedure activity is being performed it is operable to provide, and/or to enable the operator 4 to create a visual representation/schematic or model of the test arrangement of the subject equipment - as a test mimic or schematic.

This functionality can be accessed by the operator 4 via an additional page sequenced after Page 2: Details of the hydrostatic pressure testing activity as hereinbefore described. The application is operable to allow the operator 4 to select from a range of previously created mimics or schematics of the test arrangement of the subject equipment, create a new one, or choose not to include one in the test.

These visual representations are in the form of a cross-section/cutaway and/or transparent/glass type view of the subject equipment in the embodiment described, or simply a schematic of the equipment being tested. The application is operable to allow the operator 4 to activate items appearing in the mimic or schematic, such as opening and closing valves, to isolate where the pressure will be acting.

A library/database of test setups is available for the operator 4 to select, view and adapt to each situation. In addition to this the software provides the tools for the operator 4 to create their own schematic or mimic to represent what they are testing. Depending on the situation the computer 6 is operable to communicate the test subject position via the GPS unit and receive up to date instructions and visual representations of the test subject in question from the database. The library/database may include typical pressure testing scenarios and may be downloadable.

In the instance where hydraulic testing is being conducted, the library contains a variety of setups including but not limited to industry, valve type, hose, pipe, seal cavity, gasket joint, and bore with cascading sub test arrangements. The system provides an automated test arrangement library containing common valve packages relevant to the supplied industry that can be searched by the operator to find the package they desire. The selected valve package is automated and provides animated variations of the valve positions changeable by touching the desired valves on the screen and moving the test input and outputs by dragging on the HMI 10 until the desired test mimic is obtained.

In Figures 16A to 16D there is shown a test subject cross-section of a Wireline Blow-out Preventer ("BOP") valve package. The operator 4 can select test inputs on the diagrammatic representation by moving the test input and outputs by dragging them on the HMI 10 until the desired test scenario is obtained and an animated representation can then be generated according to the inputs selected as shown in Figure 16A to 16D. As is shown in these Figures the high pressure regions are shaded with each input variation. Further to this, indicators may be provided to the operator via the HMI 10 as to where to attach relevant test equipment and/or what tools need to be used or were used in the activity.

The selection of the Wireline BOP ram arrangements of the activity may be performed by the operator 4 via a test mimic selection screen, an example of which is illustrated in Figure 17 of the drawings. Although in the illustrated test mimic selection screen the buttons of the HMI 10 are labelled, in alternative embodiments of the invention thumbnail pictures of the relevant test mimics may be provided.

In some cases information may need to be provided to the operator or for the operator to input/record for correct analysis. In the case of testing a gate valve of a subsea tree as shown in Figure 18, for example, a transparent view of the tree is provided showing that there are two sides of the gate that are possible to extract test data from. In some circumstances only one side will require testing - that is, only one side needs to demonstrate proof of leak tightness, for example.

The application is operable to enable the operator 4 to change the gate valves on the subsea tree from the open to closed state by touching the valve image in the HMI 10. The application is operable to recognize where to fill the pressured regions represented by shading in this instance. Alternatively, the library stores an image of every possible test configuration for selection by the user 4.

The particular mimic shown represents a Production Master Valve ("PMV") being pressured from the underside as shaded. The test mimic shows that the Chemical Injection Non-Return Valve ("CIV-NRV") is also holding pressure.

This CIV-NRV holding pressure and effectively being proven in this test is typical of the data that would be missing from a paper test chart with only the information "PMV Test" labelled. Without the use of a photograph or printed marked up hydraulic schematic or representation (thereby containing all required data within the computer 6), an operator could mark a test chart up with all details but without specifying the side of the gate valve the test refers to. This is common and quite frequently renders the test chart meaningless and therefore the results cannot be interpreted. Trying to overcome this omission of information is usually not possible or even valid unless done at the time of the performed test.

Accordingly, visual representation on the computer 6 is advantageous to ensure that correct data is collected by prompting the user visually for input. Incorporating visual schematics into the computer 6 also ensures that the necessary data is collected, preventing necessary information from being omitted by prompting the operator visually.

Even with carefully planned procedures for individual tasks or test scenarios and operator training, other factors come into play on the operator's performance or collection of results. The state of mind of the operator can greatly affect the quality of work or results achieved. Furthermore certain factors associated with work environments can be distracting to workers, particularly oil rig or mine site environments. These factors include such factors as noise, close proximity to machinery and weather conditions to name a few. The HMI 10 helps keep the operator 4 focused regardless of distraction.

Embodiments of the invention provide a management tool that enables a job that would typically require multiple separate tasks to be performed by multiple personnel (JSA, chart record, identify if the test has passed or not, record procedures, and write report, for example) to all be managed by a single, portable, hand held device and a single operator. They ensure that information gathered is usable, thorough, traceable and complete and is originated together and kept together, and may therefore lead to increases in time efficiency and accuracy. They also ensure that information doesn't need to be repeated over and over. Once information such as serial numbers have been entered they can subsequently be selected easily from a drop down list. Furthermore, they guide the operator through all aspects of the data extraction and allow them to provide more efficient and higher quality reporting to engineers or supervisors.

Additionally, embodiments of the invention allow a linked system for the tests to relate to one another via the one too) - combining separate testing processes into one. For example, a bolt flange requiring making up may require a joint to be tensioned requiring:

1a- Confirmation that the bolts to be used are as per the required grade. Therefore a destructive test of the bolt will be advantageous. The bolt will be tensioned to failure and a report generated of the bolts performance.

This will confirm or otherwise the quality of that batch of bolts. The management tool will guide the operator through this procedure.

1b- The flange will then require tensioning as per a company or classification society standard. The management tool guides the operator through this process and generates a report on the completed task. The destructive test of the bolts used will be linked to this report by the management tool.

2a-This flanged joint may require pressure testing to confirm its integrity. The fluid used for the test may also require certification as to its cleanliness. The management tool will guide an operator through taking a fluid cleanliness test and record the results to a report and save in the database.

2b-The proven fluid will now be used to complete a pressure test of the flanged joint, and other flange joints in the same pressure body that have or have not been assembled by this management tool. The management tool will guide the operator through this procedure and generate a report.

An overall report of the tasks will then be generated by operation of the management tool to give evidence of all tasks required to tension the flanged joint. All required data has been collected on the one tool ensuring completeness of information.

3-The completed component may then be required to be lifted to a rig from a supply vessel. Typically an operational limit is given to a sea state for the purpose of not overloading the cranes due to high DAF. This is typically a disputed and undefined number. The management tool can be used to record via a load cell the maximum DAF seen over a given period of time, say 30min, and if below the operating limit of the crane then the transfer can continue, if not then the operation must cease until the sea state has reduced.

Embodiments of the invention provide an operator with guide line instructions on how to perform a particular task or activity to comply with a company standard or classification society standard. Embodiments also provide a company with the ability to communicate these standards to an operator while taking away the confusion of the operator's requirement to interpret the instructions and results of the test/task/activity.

Embodiments of the invention provide a safety gate as a JSA must be performed, and are able to intercept dangerous activity such as accidental over pressurization. As the tool will know what the maximum pressure intended for a system is based on the operator inputs, if it sees the pressure has passed this boundary it can alarm the operator and even close valves with simple Bluetooth or wired solenoid valves, for example. As hereinbefore described, it can also activate a barrier traffic light system to demark the presence of a dangerous operation taking place. These wired or wireless portable bollard type traffic lights can be placed at possible entrances to the working area.

Embodiments of the invention also advantageously take human interpretation of typically difficult to read data out of the process, thereby potentially avoiding accidents that may arise through misinterpretation of test results, such as whether a pressure test on an isolation cement plug to a reservoir has passed or failed. In this regard, there is generally very high pressure on the "Company Man" to keep a project moving forward and so his judgment can be biased. By using the tool, the company man can report forward that the tool (based on a pre-agreed test criteria) determined that a pressure test had passed or failed - he is not required to interpret a test result himself and basically can say that the "computer says yes or no".

Embodiments of the invention advantageously simplify data that the operator needs to view. Conventionally, an operator only sees raw data from sensors and is required to mentally process this to a large degree. For example, an operator looking at a graph (pressure x time) to determine if a subject under test has lost more pressure over its pre-determined hold period than is allowed requires quite a few mental deductions such as, working out the scale of the chart (time and pressure). These are usually extremely difficult to read due to very small unnumbered increments. Embodiments of the invention display information in the easiest way possible for an operator to view with anything requiring interpretation of raw data to be analysed by the tool and display the results in a comprehendible form such as yes or no or a traffic light system, red, green or yellow. It can also show the data in the same format as the conventional circular chart if required.

Additionally, all of the data and information captured and generated by the tool in embodiments of the invention is in digital format, facilitating integration and communication with devices via existing communications networks and systems, such as the Internet, including emailing, and uploading of data to a website for client access, for example.

Furthermore, embodiments of the invention allow the operator a means the recording of both visual and audio data allowing better analysis or troubleshooting of issues. The management tool can be used on any system that requires personnel to record data and automatically generate a report based on the recorded data.

Modifications and variations such as would be apparent to a skilled addressee are deemed to be within the scope of the present invention. Particularly, it should be appreciated by the person skilled in the art that the invention is not limited to the embodiments described. For example, the invention as described can include the following modifications and/or additions:

• Activities other than those described can be managed, including ultrasonic bolt tensioning, hydraulic pressure and flow recording and analyzing, pump flushing, and operations management, for example.

The activity may comprise wirelessly managing the use of a plurality of systems in accordance with aspects of the invention and associated personnel in real time as procedures are followed - thereby facilitating mobile real time logging of a project, such as an offshore campaign. For example, a set of offshore procedures for a particular campaign may be uploaded to the system. These would be managed from a master computer operated by an active operator, with other personnel involved in the campaign having read only computers displaying the status of the campaign networked with the master computer. For example, a member of a well testing team may be the initial active operator and once they have finished their section of work on the campaign they would hand the master computer over to a member of the team responsible for the next operation in the campaign, such as a subsea team to recover equipment from the seabed.

• A knowledge base of operator accessible safety and information files may be provided, comprising media files with short safety messages relevant to the activity, industry updates and news, and other industry related information. • Activity tasks may follow a standard template referred to as a wizard, questions for different tasks may change slightly but will be presented in a very similar way.

• Onsite/Field Inspections: o A typical report template can be created that steps the operator 4 through the steps required to complete an inspection activity. o The software is operable to prompt the operator 4 to take photos and/or videos with the camera that is integrated into the hand held computer 6. o The software is operable to automatically generate a report in a predefined template that includes all the steps the operator took to complete the inspection including the information they entered and the photos and videos they took with the hand held computer 6. o All events that took place to complete the tasks of the inspection are dated and timed and GPS stamped as to identify exactly when and where the inspection took place. o Sensors such as paint coating thickness meters, dry film thickness ("DFT") meters, ultrasonic wall thickness meters can be integrated in to this the same way the pressure transmitter sensor is in the embodiments hereinbefore described.

• Work Instructions: o A work instruction (electronic procedures) activity can be uploaded onto the hand held computer 6. The operator 4 can then follow the electronic procedures. The procedures may prompt for the operator 4 to take photos or videos with the camera that is integrated into the hand held computer 6. o All events that took place to complete the tasks of the instruction are dated and timed and GPS stamped as to identify exactly when and where the instructions were carried out.

• Onsite/Field/Project Procedures o Electronic procedures of onsite/field/project activities can be uploaded onto the hand held computer 6. An operator 4 can then follow the electronic procedures. The procedures may prompt for the operator to take photos or videos with the camera that is integrated into the hand held computer 6. o All events that took place to complete the tasks of the activities are dated and timed and GPS stamped as to identify exactly when and where the activities took place.

It should be further appreciated by the person skilled in the art that variations and combinations of features described above, not being alternatives or substitutes, can be combined to form yet further embodiments falling within the intended scope of the invention.