[go: up one dir, main page]

WO2003089837A1 - Systeme de gestion de controle et interface utilisateur graphique associee - Google Patents

Systeme de gestion de controle et interface utilisateur graphique associee Download PDF

Info

Publication number
WO2003089837A1
WO2003089837A1 PCT/AU2003/000472 AU0300472W WO03089837A1 WO 2003089837 A1 WO2003089837 A1 WO 2003089837A1 AU 0300472 W AU0300472 W AU 0300472W WO 03089837 A1 WO03089837 A1 WO 03089837A1
Authority
WO
WIPO (PCT)
Prior art keywords
inspection
entity
management system
user interface
inspected
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/AU2003/000472
Other languages
English (en)
Inventor
Neal Pennison
Byron Geneve
Reto Meier
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SURESPEK ISS Pty Ltd
Original Assignee
SURESPEK ISS Pty Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from AUPS1792A external-priority patent/AUPS179202A0/en
Priority claimed from AUPS1804A external-priority patent/AUPS180402A0/en
Application filed by SURESPEK ISS Pty Ltd filed Critical SURESPEK ISS Pty Ltd
Priority to AU2003227096A priority Critical patent/AU2003227096A1/en
Publication of WO2003089837A1 publication Critical patent/WO2003089837A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0267—Fault communication, e.g. human machine interface [HMI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q9/00—Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
    • H04Q9/02—Automatically-operated arrangements

Definitions

  • the present invention relates to an inspection management system and graphical user interface therefor.
  • the invention is particularly useful in the administration of inspections of sub-sea offshore oil and gas facilities such as pipelines.
  • Inspections are performed to ensure the continued integrity of assets.
  • the integrity of assets is essential to guarantee the continued safety of personnel and conservation of the surrounding environment, as well as, in some cases, ensuring that optimal production levels are maintained.
  • One aspect of the present invention relates to an inspection management system having a user interface whereby the user interface displays:
  • each glyph representative of a task or incident at a location relative to the visual representation of the entity being inspected, where the location of the glyph relative to the visual representation of the entity being inspected substantially corresponds to the physical location of the task or incident relative to the physical location of the entity being inspected.
  • the size of the glyph displayed by the user interface relative to the size of the visual representation of the entity being inspected substantially corresponds to the physical size of the task or incident represented by the glyph relative to the physical size of the entity being inspected.
  • the user interface displays information regarding the task or incident the glyph represents.
  • the information displayed can be modified.
  • only one glyph can be activated at a time.
  • the user interface updates the visual representation of the entity being inspected and the glyphs based on the recorded position of an inspecting entity.
  • the user interface displays glyphs created while an inspection is being conducted at positions in front of or behind the inspecting entity.
  • the inspecting entity is a remotely-operated vehicle.
  • the inspecting entity is equipped with at least one of the following inspection tools: Corrosion Protection; Alternating Current Frequency Modulation; and Flooded Member Detection.
  • the user interface distinguishes glyphs representing current event tasks or incidents from glyphs representing historical event tasks or incidents.
  • the method of distinguishing glyphs representing current event tasks or incidents from glyphs representing historical event tasks or incidents is to render partially transparent glyphs representing historical event tasks or incidents.
  • the user interface distinguishes glyphs representing anomalous event tasks or incidents from glyphs representing other event tasks or incidents.
  • the user interface displays a list of incidents identified during an inspection.
  • the inspection management system further comprises automatic information gathering means in data communication with an input device for obtaining information automatically about event tasks or incidents.
  • the automatic information gathering means is also in control communication with the input device.
  • the input device is at least one of the following: digital video disc recorder; video cassette recorder, survey computer.
  • the inspection management system further comprises audio recording means for recording commentary dictated by an inspector in respect of the inspection.
  • the audio recording means records commentary dictated by an inspector in respect of the inspection on a first audio track and the automatic information gathering means records commentary on the inspection on a second audio track.
  • the visual representation of the entity being inspected is derived from live-video feed of the entity.
  • the visual representation of the entity being inspected is displayed in stereo or three dimensional format.
  • the inspection management system further comprises target definition means for defining inspection targets, each inspection target representative of an entity to be inspected.
  • the inspection management system further comprises hierarchical means for defining a hierarchical relationship between inspection targets.
  • the inspection management system further comprises task definition means for defining inspection tasks.
  • the step of defining an inspection task includes defining data to be recorded in respect of the inspection task and a range of acceptable values for such data.
  • the inspection management system further comprises task allocation means for assigning inspection tasks to inspection targets.
  • the inspection management system further comprises span means for calculating the span of the entity being inspected.
  • the inspection management system further comprises scour means for calculating the scour of the entity being inspected.
  • the inspection management system further comprises time estimation means for estimating the time necessary to complete an inspection task.
  • the inspection management system further comprises report generation means for generating a report on the inspection.
  • a glyph representative of a task or incident at a location relative to the visual representation of the entity being inspected wherein the location of the glyph relative to the visual representation of the entity being inspected substantially corresponds to the physical location of the task or incident relative to the physical location of the entity being inspected.
  • the size of the glyph displayed by the user interface relative to the size of the visual representation of the entity being inspected substantially corresponds to the physical size of the task or incident represented by the glyph relative to the physical size of the entity being inspected.
  • the user interface displays information regarding the task or incident the glyph represents.
  • the information displayed can be modified.
  • only one glyph can be activated at a time.
  • the user interface updates the visual representation of the entity being inspected and the glyphs based on the recorded position of an inspecting entity.
  • the user interface displays glyphs created while an inspection is being conducted at positions in front of or behind the inspection entity.
  • glyphs representing current event tasks or incidents are distinguished from glyphs representing historical event tasks or incidents.
  • the method of distinguishing glyphs representing current event tasks or incidents from glyphs representing historical event tasks or incidents is to render partially transparent glyphs representing historical event tasks or incidents.
  • glyphs representing anomalous event tasks or incidents are distinguished from glyphs representing other event tasks or incidents.
  • the user interface further displays a list of incidents identified during an inspection.
  • the visual representation of the entity inspected is derived from live- video feed of the entity.
  • the visual representation of the entity being inspected is displayed in stereo or three dimensional format.
  • the step of displaying a glyph representative of a task or incident further comprises the step of adjusting the size of the glyph displayed by the user interface such that the size of the glyph relative to the size of the visual representation of the entity being inspected substantially corresponds to the physical size of the task or incident represented by the glyph relative to the physical size of the entity being inspected.
  • the method of presenting information further comprises the step of displaying information on the user interface regarding a task or incident represented by a glyph upon activation of that glyph.
  • the method of presenting information further comprises the step of updating the visual representation of the entity being inspected and the glyphs based on the recorded position of an inspecting entity. More preferably, the method of presenting information further comprises the step of displaying on the user interface glyphs created while an inspection is being conducted at positions in front of or behind the inspecting entity.
  • the method of presenting information further comprises the step of distinguishing glyphs representing current event tasks or incidents from glyphs representing historical tasks or incidents.
  • the step of distinguishing glyphs further includes the step of rendering glyphs representing historical event tasks or incidents partially transparent.
  • the method of presenting information further comprises the step of distinguishing glyphs representing anomalous event tasks or incidents from glyphs representing other event tasks or incidents.
  • the method of presenting information further comprises the step of displaying a list of incidents identified during an inspection on the user interface.
  • the method of presenting information further comprises the steps of:
  • the step of displaying a visual representation of the entity being inspected further comprises the step of rendering the visual representation of the entity into a stereo or three dimensional format.
  • Figure 1 is a schematic diagram of the inspection management system and its external interfaces.
  • Figure 2 is a first illustration of the user interface during an inspection displaying the structure being inspected.
  • Figure 3 is a second illustration of the user interface during an inspection displaying the tasks to be performed and the anomalies encountered during the inspection.
  • Figure 4 is a block diagram showing the general data structure.
  • Figures 5a - 5f are block diagram depictions of the automated inspection-video voice annotation function of the inspection management system.
  • Figure 6 is a block diagram depiction of the automated span, burial and scour profiling function of the inspection management system.
  • Figure 7 is a block diagram depiction of the structure navigation with recording interface function of the inspection management system.
  • Figure 8 is a block diagram depiction of the fully integrated reporting function of the inspection management system.
  • Figures 9a and 9b are block diagram depictions of the real-time visualisation and inspection interaction functions of the inspection management system.
  • the present invention relates to an inspection management system 10 having a graphical user interface 12.
  • the inspection management system 10 described hereafter has been particularly adapted for use in the inspection of sub-sea offshore oil and gas facilities, such as pipelines.
  • the inspection management system 10 is in data communication with a survey computer 14 and an inspection tool computer 16.
  • the inspection management system 10 is in data and control communication with an image recording device 18, in this case a video cassette recorder.
  • the inspection management system 10 also has a database 17. As shown in Figure 4, database 17 is in reciprocal communication with non-visual module 15.
  • Non visual module 15 contains information relating to the various components and objects of the system.
  • Non-visual module 15 is made up of data module 13 and I/O module 19.
  • Data module 13 contains information relating to the various data structures used in the inspection management system 10 and their implementation.
  • Data module 13 is made up of incident module 11 and generic module 25.
  • Incident module 11 contains information relating to the customised data structures obtained for event tasks and incidents and is further made up of recorded data module 23 and data definitions module 21.
  • Recorded data module 23 stores information entered in by a user during the course of an inspection.
  • Data definitions module 21 stores the user-defined data structures relating to the various event tasks and incidents.
  • Generic module 25 stores the data structures for the generic components used in the information management system 10 and other generic data structures.
  • Non-visual module 15 is also in reciprocal communication with the user interface 12.
  • the inspection tool computer 16 is in data and control communication with inspection tools 20 installed on a remotely operated vehicle ("ROV") 22 through I/O module 19.
  • the survey computer 14 is also in data communication with the inspection tools 20 installed on the ROV 22 through I/O module 19.
  • the inspection tools 20 may include such components as Corrosion Protection, Alternating Current Frequency Modulation (crack detection and sizing) and Flooded Member Detection in addition to a video camera 24.
  • the video camera 24 provides raw video footage to monitors 26.
  • the image recording device 18 are connected to monitors 26 in such a manner that the raw video footage provided to the monitors 26 can be recorded by the image recording device 18.
  • the inspection management system 10 operates as follows. The following description should be read in conjunction with Figure 5 through Figure 9 which graphically illustrate some of the features described.
  • An inspector 28 defines inspection targets 30 in a workpack preparation stage.
  • the inspection targets 30 are identified by diagrams produced by the owner of the facility being inspected. Details relating to each inspection target 30 are also defined. Typically, these details include:
  • the inspector 28 then generates an inspection hierarchy by defining parent-child relationships between the inspection targets 30.
  • the inspection hierarchy is stored in database 17.
  • the inspector 28 defines the inspection tasks 32.
  • the process of defining the inspection tasks 32 includes specifying the data that is to be recorded against the inspection task 32 and the method by which that data is to be recorded. A range of acceptable values for each item of data must also be specified by the inspector 28, where appropriate.
  • the inspector 28 must choose a glyph 34 that will identify the inspection task 32 when displayed on the graphical user interface 12.
  • the inspector 28 must also specify the expected estimated time to complete each inspection task 32.
  • the expected estimated time is compared with the efficiency factor that relates to that inspection target 30, if any, to produce a revised expected estimated time.
  • the revised expected estimated time is obtained by multiplying the efficiency factor for the inspection target 30 by the expected estimated time. In this manner, the efficiency factor should take into consideration such issues as water current and accessibility.
  • the total estimated time for an inspection can be obtained by summing the revised expected estimated times for each inspection target 30 in the inspection hierarchy.
  • the inspection tasks 32 are grouped within data definitions module 21 into logical categories to provide a fast and intuitive way of finding them during an inspection. Thereafter, the inspector 28 traverses each inspection target 30 in the inspection hierarchy allocating inspection tasks 32 as required. The inspector 28 may then commence the inspection at any time.
  • an inspection is commenced by initiating a dive.
  • the inspection management system 10 sets up the graphical user interface's 12 display and executes a sound file that announces the dive name and its status (ie. started).
  • the graphical user interface's 12 display contains a series of toolbars 34 and windows 36.
  • a visual representation 38 of the inspection target 30, defined as paramount in the inspection hierarchy is displayed as determined by the inspection target's 30 type.
  • the toolbars 34 and windows 36 are displayed close to the edges of the graphical user interface 12 so as not to obscure the visual representation 38 of the inspection target 30.
  • the visual representation 38 of the inspection target 30 is displayed in three- dimensional format.
  • the x-y plane 40 of the visual representation 38 is represented as a grid.
  • the x-axis 42 represents the transverse distance to the inspection target 30.
  • the y-axis 44 represents the length of or distance travelled along the inspection target 30.
  • Inspection tasks 32 allocated to the inspection target 30 are also displayed on the graphical user interface 12 by their glyphs 52.
  • the position of the glyphs 52 are determined with reference to the actual or expected physical location recorded for the inspection task 32 as related to the x- and y-axes 42, 44.
  • each glyph 52 is shown on the graphical user interface 12 at a position relative to the visual representation 38 that substantially corresponds with the actual or expected physical location of the inspection task 32 relative to the physical location of the inspection target 30. Incidents are displayed in the same manner.
  • the inspector 28 also has the option of viewing historical inspection tasks 32 and incidents.
  • glyphs 54 representing historical inspection tasks 32 and incidents relating to the inspection target 30 and stored in the database are displayed in the same manner as glyphs 52 representing current inspection tasks 32 and incidents.
  • Glyphs 54 representing historical inspection tasks 32 and incidents are distinguished from glyphs 52 representing current inspection tasks 32 and incidents by their partial transparency. Glyphs 54 representing historical inspection tasks 32 and incidents can not be activated (discussed below).
  • Toolbar 34a is the incident toolbar.
  • the glyphs displayed in the incident toolbar 34a vary according to the type of inspection target 30.
  • Toolbar 34b is the menu bar. From toolbar 34b the inspector 28 can take a frame or video capture, initiate an anomaly, and enter a text comment into the video log. Toolbar 34c allows the inspector to control the status of the inspection. Toolbar 34c also allows the inspector 28 to specify the current video number and its length, as well as entering operational log details.
  • Window 36a shows a visual representation 56 of the distance between the inspection target 30, being a pipeline in this instance, and the seabed. If the inspection target 30 is buried in the seabed, a visual representation 56 of how deep the inspection target 30 is buried in comparison to the seabed is shown. The calculations that provide this visual representation 56 are discussed in more detail below.
  • Window 36b displays the current time counter of the image recording device 18.
  • Window 36c displays a list of the last user-definable incidents and tasks.
  • the inspector 28 can select a task or incident from this list and the details relating thereto are displayed in window 36d.
  • Window 36d is joined to window 36c.
  • Window 36c shows information recorded against an incident or task. This information can be modified.
  • Window 36e displays information regarding the inspection target 30 or special instructions relating to the inspection target 30, depending on what tab 46 has been pressed.
  • the position of an inspecting entity is displayed on the user interface 12 as line 50.
  • line 50 starts from the bottom of the user interface 12.
  • line 50 moves up the user interface 12 until it reaches a position representing a line of symmetry on the x-y plane 40 as displayed.
  • line 50 moves downwards from this position until it again reaches the bottom of the user interface 12 (signalling that ROV 22 has reached the end of inspection target 30).
  • a second survey computer 14 feeds information relating to the ROV's 22 position to the inspection management system 10. This new positioning information is then used to update the visual representation 18 of the inspection target 32 and its associated glyphs 52, 54 in the following manner.
  • the ROV's 22 new position is compared to its old position for changes in distance travelled along the inspection target 32. These changes, if any, are then replicated to each glyph 52, 54 currently displayed, such that those glyphs 52, 54 below line 50 are moved even closer to the bottom of the user interface 12 and glyphs 52, 54 above the line 50 are moved even closer to line 50. If an event task 32 or incident, as a result of the change in position of the ROV 22, is no longer within the y-axis 44 range of the user interface 12, it's representative glyph 52, 54 is no longer displayed.
  • the inspection management system 10 generates a list of incidents. This list includes details of the incident type and position. A sub-set of this list is then displayed in window 36c. Also displayed in window 36c is a list of ongoing and planned incidents, including their type and their start time.
  • the inspector 28 also has the option of stopping an ongoing incident by double- clicking it or pressing the appropriate button on the ongoing incidents toolbar (not shown). Once the ongoing incident is stopped, a sound file is generated and executed announcing the incident type and the length of time that the incident has been ongoing.
  • the inspector 28 can activate any of the glyphs 52 currently displayed on the user interface 12, with the exception of historical glyphs 54.
  • the method of activation can vary ranging from double or single clicking the glyph 52 with a mouse or activating a hot-key associated with the glyph 52.
  • details of the inspection task 32 or incident associated with the glyph 52 is displayed in window 36d.
  • a sound file is also generated and executed that announces the chosen glyph's 52 full name.
  • the inspector 28 may then enter in information relating to the inspection task 32 or incident based on the visual feed displayed on monitors 26. This information is stored in related data module 23.
  • the inspector 28 enters information related to an inspection task 32 or incident that falls outside of the range of acceptable values defined for that field, the inspector 28 is informed of this fact. The inspector 28 is then asked to confirm that the value is correct and, if so, the inspection task 32 or incident is designated an anomaly and added to the anomaly collection. When next updated, the user interface 12 indicates that the glyph 52 representing the inspection task now represents an anomaly. Details of the anomaly, including its position, are then generated as a sound file and announced.
  • Only one incident or event task can be displayed in window 36d at any one time. This assists in providing an uncluttered user interface 12 to the inspector 28.
  • the inspector 28 chooses the appropriate incident glyph 52 from toolbar 34a.
  • the inspector 28 can then place the incident glyph 52 at a position on the user interface 12 such that the position of the new incident glyph 52 relative to the visual representation 38 of the inspection target 30 substantially corresponds to the position of the incident relative to the inspection target 30.
  • the method used to position and size the incident glyph 52 is the "click and drag" method commonly known to the person skilled in the art.
  • the position of the new incident is calculated according to the position of its glyph 52 on the user interface 12 relative to the position of the ROV 22 and the visual representation 38 of the inspection target 30.
  • the new incident is then added to the incident collection and a sound file generated and executed that announces the position and type of incident identified.
  • Information displayed in window 36d is then replaced with information relating to the new incident (default values being displayed) as defined for that type in generic module 25.
  • the inspector 28 may also identify a need for additional inspection tasks 32.
  • New inspection tasks 32 can be created regardless of the position of the ROV 22. Accordingly, inspection tasks 32 can be created either before or after the position of the ROV 22.
  • New inspection tasks 32 are created and defined in the same manner as described above and stored in data definitions module 21. Once created, the user interface 12 is updated to include the new inspection tasks 32 and information pertaining to the new inspection task 32 is displayed in window 36d.
  • the system also generates a seabed profile that is displayed in window 36a.
  • the seabed profile is generated by taking an image of the seabed profile from monitors 26 via image recording device 18 every predetermined number of seconds.
  • the captured image is then processed to determine the depth of spanning or depth of burial of the pipeline.
  • the degree of scour, if any, on each side of the pipeline can also be determined during the image processing procedure.
  • the position of the seabed profile is obtained via survey computer 14.
  • the inspection management system 10 checks the length of the span over successive captured images. If the length of the span, as determined by these successive captured images, is greater than a preset incident limit, the span is recorded as an anomaly and processed accordingly.
  • the inspector 28 may use the inspection management system 10 to record part of the live video feed sent to monitors 26 by issuing a record command to the image recording device 18. Typically this is done to allow video images to be incorporated in reports generated by the inspection management system 10. Recording stops when a stop command is issued to the image recording device 18. If desired, the inspector may view the recording or pause the recording by issuing a play or pause command, as appropriate, to the image recording device 18. In each case, as a command is issued to the image recording device 18 a sound file is created and executed announcing the command given. Images and video recorded by the image recording device 18 can be used in subsequent reports. During an inspection of an inspection target 30, a glyph (not shown) representing an additional inspection target 30 may be displayed. The inspector 28 may then inspect this additional inspection target 30 by activating this glyph as described above. The user interface 12 is then updated to represent the new inspection target 30 and the event tasks 32 and incidents associated with the new inspection target 32.
  • the inspector 28 may stop the dive at any time by activating the 'stop' button in window 34C.
  • a sound file is generated and executed that announces the dive name and is status.
  • the inspector 28 may generate a report on the inspection as a whole or on a particular inspection target 30.
  • the report may also be limited according to particular inspection tasks 32 or incidents.
  • the report can be generated in either Word or Excel format and video or still taken from video recorded by the image recording device 18 may be included therein.
  • the audio produced by the announcement of the various sound files is also directed towards an audio channel separate from the audio channel the inspector 28 uses for his/her commentary.
  • the audio directed towards this separate audio channel is recorded and can be used by the inspector 28 when reviewing the dive to verify aspects of the inspection that may not have been commented on as part of his /her audio commentary.
  • the visual representation 38 of the inspection target 30 is derived from direct video feed of the inspection target 30 during the inspection.
  • the visual representation 38 of the inspection target 30 is presented in stereo vision format.
  • historical glyphs may be activated.

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un système de gestion de contrôle (10) pourvu d'une interface utilisateur (12), affichant une représentation visuelle (38) d'une entité à contrôler, et au moins un glyphe (52), chaque glyphe (52) étant représentatif d'une tâche ou d'un incident, à un emplacement relatif à la représentation visuelle (38) de l'entité à contrôler, l'emplacement de ce glyphe (52) relatif à la représentation visuelle (38) de l'entité à contrôler correspondant sensiblement à l'emplacement physique de la tâche ou de l'incident relatif à l'emplacement physique de l'entité à contrôler.
PCT/AU2003/000472 2002-04-17 2003-04-17 Systeme de gestion de controle et interface utilisateur graphique associee Ceased WO2003089837A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003227096A AU2003227096A1 (en) 2002-04-17 2003-04-17 Inspection management system and graphical user interface therefor

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
AUPS1792 2002-04-17
AUPS1792A AUPS179202A0 (en) 2002-04-17 2002-04-17 Inspection management system and graphical user interface therefor
AUPS1804A AUPS180402A0 (en) 2002-04-18 2002-04-18 Inspection management system and graphical user interface therefor
AUPS1804 2002-04-18

Publications (1)

Publication Number Publication Date
WO2003089837A1 true WO2003089837A1 (fr) 2003-10-30

Family

ID=29251548

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2003/000472 Ceased WO2003089837A1 (fr) 2002-04-17 2003-04-17 Systeme de gestion de controle et interface utilisateur graphique associee

Country Status (1)

Country Link
WO (1) WO2003089837A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015106340A1 (fr) * 2014-01-16 2015-07-23 Msp Resourcing Canada Inc. Suivi des attributs d'inspection dans des installations de tuyauterie

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5272769A (en) * 1991-11-05 1993-12-21 Environmental Systems Product Inc. Emission system component inspection system
WO1997008652A2 (fr) * 1995-08-15 1997-03-06 Diffracto, Ltd. Systeme et procede pour l'acquisition, le stockage et la recherche de donnees-image
US6031566A (en) * 1996-12-27 2000-02-29 Olympus America Inc. Method and device for providing a multiple source display and a remote visual inspection system specially adapted for use with the device
US6097998A (en) * 1998-09-11 2000-08-01 Alliedsignal Truck Brake Systems Co. Method and apparatus for graphically monitoring and controlling a vehicle anti-lock braking system
JP2001265432A (ja) * 2000-03-15 2001-09-28 Central Uni Co Ltd 集中監視方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5272769A (en) * 1991-11-05 1993-12-21 Environmental Systems Product Inc. Emission system component inspection system
WO1997008652A2 (fr) * 1995-08-15 1997-03-06 Diffracto, Ltd. Systeme et procede pour l'acquisition, le stockage et la recherche de donnees-image
US6031566A (en) * 1996-12-27 2000-02-29 Olympus America Inc. Method and device for providing a multiple source display and a remote visual inspection system specially adapted for use with the device
US6097998A (en) * 1998-09-11 2000-08-01 Alliedsignal Truck Brake Systems Co. Method and apparatus for graphically monitoring and controlling a vehicle anti-lock braking system
JP2001265432A (ja) * 2000-03-15 2001-09-28 Central Uni Co Ltd 集中監視方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015106340A1 (fr) * 2014-01-16 2015-07-23 Msp Resourcing Canada Inc. Suivi des attributs d'inspection dans des installations de tuyauterie

Similar Documents

Publication Publication Date Title
US20210097770A1 (en) Methods for augmented reality applications
US8553039B1 (en) System and method for computer visualization of project timelines
CA2680958C (fr) Enchainement de gestion de reservoir
CN105474049A (zh) 井作业条形图
US9013573B2 (en) Knowledge capture and sharing for exploration and production tool sessions
US20050183028A1 (en) System and method for acquisition and analysis of time and location-specific data
EP3161412A2 (fr) Procédé et système d'indexation
CN116720242A (zh) 一种高压电缆隧道数字孪生全景监测系统
US20190003920A1 (en) Visualization of multi-pipe inspection results
Naticchia et al. Mixed reality approach for the management of building maintenance and operation
Kayely et al. A Revolutionary Digital Twin of Autonomous Hydraulic Simulation on Largest and Most Complex Pipeline Network in Indonesia (Case Studies in Rokan Block)
WO2003089837A1 (fr) Systeme de gestion de controle et interface utilisateur graphique associee
JP2006139163A (ja) 保安作業訓練システム
Oxstrand et al. Design Guidance for Computer-Based Procedures for Field Workers
CN113063843A (zh) 一种管道缺陷识别方法、装置及存储介质
US9557432B2 (en) Seismic interpretation system and method
CN111208582A (zh) 地下管网系统
Khorrami Shad et al. Augmented Reality Applications for the Excavation Industry: Locating and Protecting Underground Utilities
CN117764776A (zh) 一种基于bim的智慧工地管理平台
Fenzl Opportunities of augmented reality applications in tunnel construction
CN119417373B (en) Multi-party cooperation and intelligent decision support digital sand table system based on UE
Paramitha et al. The Role of Geomatics Discipline to Support Langsa Complex Restoration Program: 3D Visualization of Subsurface and Existing Subsea Facilities Geospatial Data
Raulino et al. From Data to Action: Leveraging Dynamic Operating Envelopes to Optimize the Production of Wells
CN117933922A (zh) 一种基于bim+ar的市政水厂工程预留预埋现场管理方法
CN117611130A (zh) 一种基于增强现实技术（ar）的石油设备检修系统及方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP