WO2016027122A1 - Système de gestion de mise en service - Google Patents

Système de gestion de mise en service Download PDF

Info

Publication number
WO2016027122A1
WO2016027122A1 PCT/IB2014/003268 IB2014003268W WO2016027122A1 WO 2016027122 A1 WO2016027122 A1 WO 2016027122A1 IB 2014003268 W IB2014003268 W IB 2014003268W WO 2016027122 A1 WO2016027122 A1 WO 2016027122A1
Authority
WO
WIPO (PCT)
Prior art keywords
construction
parts
certificate
commissioner
status
Prior art date
Application number
PCT/IB2014/003268
Other languages
English (en)
Inventor
Paul Rushton
Original Assignee
Magma Products Group 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
Application filed by Magma Products Group Ltd. filed Critical Magma Products Group Ltd.
Priority to PCT/IB2014/003268 priority Critical patent/WO2016027122A1/fr
Publication of WO2016027122A1 publication Critical patent/WO2016027122A1/fr

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/02Agriculture; Fishing; Forestry; Mining
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311Scheduling, planning or task assignment for a person or group
    • G06Q10/063114Status monitoring or status determination for a person or group

Definitions

  • An oil platform which is also known as an oil rig, is a large structure to drill wells, to extract oil and gas, and to temporarily store the oil and gas until the oil and gas are brought to shore for refining and marketing.
  • the oil platform typically includes a multiple facilities for several purposes, such as drilling, processing, storing, and loading.
  • the oil platform is constructed with a large number of parts or elements that are may be manufactured by many different manufacturers and installed by several installers on the construction site.
  • the construction of the oil platform can thus be commissioned to ensure the operability and safety of the oil platform.
  • the commissioning process is designed to check, inspect, and test every operational component of the installation project from individual functions of the parts up to the operation of the entire platform.
  • As the construction of the oil platform is typically a complex and detailed project, ensuring that all parts have been properly installed and tested can be a difficult task, and a large amount of paperwork is often generated. Additionally, governmental and environmental regulations impose strict requirements, and failure to comply with such regulations can result in undesirable consequences.
  • this disclosure is directed to a commissioning management system.
  • the system operates to import a variety of certificates issued during the construction and commissioning processes and visualize the status of the construction.
  • Various aspects are described in this disclosure, which include, but are not limited to, the following aspects.
  • One aspect is a method of commissioning an oil platform.
  • the method includes identifying a first part in a drawing of at least a portion of the oil platform, receiving at least one certificate during construction process, the at least one certificate associated with the first part, and displaying a construction status of the first part on the system drawing using a computing device.
  • the system includes a processing device configured to control a commissioning management system, and a computer readable storage device storing software instructions that, when executed by the processing device, cause the commissioning management system to identify a first part in a system drawing, receive at least one certificate during construction process, the at least one certificate associated with the first part, and display a construction status of the first part on the system drawing.
  • Yet another aspect is a method of commissioning an oil platform.
  • the method includes identifying a first part and a second part in a system drawing, receiving at least one first certificate and at least one second certificate during construction process, the at least one first certificate associated with the first part, and the at least one second certificate associated with the second part, wherein the at least one first certificate is issued by a first vendor and the at least one second certificate is issued by a second vendor, the second vendor different from the first vendor, displaying construction status of the first part and the second part on the system drawing, generating a list of parts, the parts configured to be installed during the construction process, and displaying the construction status of the first part and the second part in the list of parts.
  • the construction status of the first part is represented with a first visual indicator in the system drawing and the list of parts when the first part is not installed during the construction process.
  • the construction status of the second part is represented with the first visual indicator in the system drawing and the list of parts when the second part is not installed during the construction process.
  • the construction status of the first part is displayed with a second visual indicator in the system drawing and the list of parts when the first part is installed during the construction process, and the construction status of the second part is displayed with the second visual indicator in the system drawing and the list of parts when the second part is installed during the construction process.
  • the construction status of the first part is displayed with a third visual indicator in the system drawing and the list of parts when the first part is installed and inspected during the construction process
  • the construction status of the second part is displayed with the third visual indicator in the system drawing and the list of parts when the second part is installed and inspected during the construction process.
  • FIG. 1 is an example construction system for an oil platform.
  • FIG. 2 illustrates an example oil platform of FIG. 1.
  • FIG. 3 illustrates an example method of implementing the construction system of FIG. 1 .
  • FIG. 4 illustrates an example diagram of implementing the construction system of FIG. 1.
  • FIG. 5 illustrates an example set of drawings and specifications.
  • FIG. 6 illustrates an example drawing.
  • FIG. 7 illustrates an example parts list.
  • FIG. 8 illustrates an example performance of a system designer.
  • FIG. 9 illustrates an example performance of a manufacturer.
  • FIG. 10 illustrates an exemplary architecture of a commissioner computing device.
  • FIG. 1 1 illustrates an example method of operating the commissioner computing device of FIG. 10.
  • FIG. 12 illustrates an example commissioner computing device including a commissioning management system.
  • FIG. 13 is an example method of operating a setup engine.
  • FIG. 14 is an example user interface for identifying drawing elements in the drawings.
  • FIG. 15 is an example user interface for tagging parts in the drawings.
  • FIG. 16 illustrates an example tagged item window.
  • FIG. 17 illustrates an example user interface for linking elements of a first drawing to a second drawing.
  • FIG. 1 8 illustrates an example commissioning engine.
  • FIG. 19 is a flowchart of an example method of operating a certificate management engine of the commissioning engine of FIG. 18.
  • FIG. 20 illustrates an example certificate.
  • FIG. 21 is a flowchart illustrating an example method of receiving certificates.
  • FIG. 22 is a flowchart illustrating an example method of updating the status of construction.
  • FIG. 23 illustrates an example user interface for tagging parts with certificates.
  • FIG. 24 illustrates an example method of performing the operation of updating the status of construction status with the certificates.
  • FIG. 25 illustrates an example drawing with the certificates updated.
  • FIG. 26 illustrates an example parts list with the certificates updated.
  • FIG. 27 is an example database table stored in the commissioner computing device.
  • FIG. 28 is a flowchart illustrating an example method of operating a checklist management engine of the commissioning engine of FIG. 18.
  • FIG. 29 illustrates an example client computing device.
  • FIG. 30 is a diagram of an example user interface of a client application.
  • FIG. 31 is a diagram of an example user interface of the client application of FIG. 30.
  • FIG. 32 is a diagram of an example user interface of the client application of FIG. 30.
  • FIG. 33 is a diagram of an example user interface of the client application of FIG. 30.
  • FIG. 34 illustrates an example commissioning system.
  • FIG. 35 illustrates an example commissioning management computing device.
  • FIG. 1 is an example construction system 100 for an oil platform 102.
  • the construction system 100 can include a system designer 104, one or more manufacturers 106, one or more installers 108 (including 108A and 108B), an inspector 1 10, a commissioner computing device 1 12 including a commissioning management system 1 14, and a client computing device 1 16.
  • the construction system 100 can communicate across a data communication network 122.
  • the installers 108 and the inspector 1 10 work at a construction site 134 for the oil platform 102.
  • the construction system 100 is directed primarily at constructing the oil platform 102.
  • the construction system 100 can be designed for any civil and/or industrial projects, such as chemical and petrochemical plants, metallurgical plants, paper and cellulose plants, coal handling plants, thermoelectric and hydroelectric plants, buildings, bridges, highways, and railroads.
  • the oil platform 102 includes several facilities with equipment to perform different operations to drill and service an oil well and extract oil and gas therefrom. An example operation of the oil platform 102 is illustrated and described with reference to FIG. 2.
  • the system designer 104 performs designing the oil platform 102 and producing drawings and specifications 126 for constructing the oil platform 102.
  • the system designer 104 can receive a design request 124 for the oil platform 102 from the client 120. Based upon the design request 124, the system designer 104 can prepare the drawings and specifications 126 for constructing the oil platform 102, and deliver the drawings and specifications 126 to several entities associated with the installation of the oil platform 102. Such entities include the manufacturers 106, the installers 108, the inspector 1 10, and the commissioner 1 18.
  • the system designer 104 can use one or more computing devices to receive the design request 124 and/or prepare the drawings and specifications 126.
  • An example of the drawings and specifications 126 is illustrated and described with reference to FIG. 6.
  • the one or more manufacturers 106 perform manufacturing parts 128 used in the installation of the oil platform 102.
  • the manufacturers 106 can receive the drawings and specifications 126 from the system designer 104 and refer to the drawings and specifications 126 to produce the parts 128.
  • the parts 128 can be delivered to the construction site 134 for the oil platform 102 so that the installers 108 install the parts 128 according to the installation requirements.
  • the manufacturers 106 can use one or more computing devices and/or manufacturing equipment to receive the drawings and specifications 126 and/or manufacture the parts 128.
  • An example performance of the manufacturers 106 is illustrated and described with reference to FIG. 8.
  • the one or more installers 108 are workers who perform the installation of the parts 128 to construct the oil platform 102 at the construction site 134.
  • the installers 108 can be employees of the commissioner 1 18 or independent contractors working under the supervision of the commissioner 1 18.
  • the installers 108 can include construction workers and field engineers.
  • the installers 108 can issue one or more installation certificates 130 for each part 128 that certify or guarantee the appropriate installation of the part 128.
  • the installation certificates 130 are delivered to the commissioner computing device 1 12 or the commissioner 1 18.
  • the inspector 1 10 performs inspection of the parts 128 to ensure that the parts 126 have been properly installed according to the installation requirements.
  • the inspection of the parts 126 includes testing of the operation of the parts 126 or an assembly of the parts 126.
  • the inspector 1 10 can issue one or more inspection certificates 132 that certify or guarantee the appropriate, safe operation of the associated part 128 or the associated assembly of the parts 128.
  • the inspection certificates 132 are delivered to the commissioner computing device 1 12 or the commissioner 1 18.
  • the installers 108 and the inspector 1 10 can be collectively referred to as vendors.
  • the commissioner computing device 1 12 operates to manage the commissioning activities or commissioning process, such as installation and inspection of the oil platform 102.
  • the commissioner computing device 1 12 is used to efficiently manage and monitor that all systems and components of the oil platform 102 are designed, installed, tested, inspected, and operated according to the operational requirements of the owner or client of the platform 102.
  • the commissioner computing device 1 12 is to effect the safe and orderly handover of the oil platform 102 from the commissioner 1 18 to the client 120, guaranteeing the operability of the oil platform 102 in terms of, for example, performance, reliability, safety and information traceability.
  • the commissioning process includes planning, execution, and control of a plurality of inspection and test activities on the construction of the oil platform 102, such as instruments, equipment, skids, modules, circuits, loops, subsystems, and systems.
  • the commissioning process typically involves a plurality of different certifications during installation and/or inspection.
  • the commissioner computing device 1 12 is configured to improve the commission process by visualizing the record of the certification information and permitting the commissioner 1 18 to manage a discipline checklist for the commissioning process. As described herein, the commissioner computing device 1 12 can be configured to monitor the installation status, and/or the inspection status, of the parts 128.
  • the commissioning management system 1 14 of the commissioner computing device 1 12 operates to visualize the construction status of the oil platform 102.
  • the commissioning management system 1 14 operates to receive the installation certificates 130 and the inspection certificates 132 and update the status of the installation and/or the inspection with visual indicators, thereby permitting the commissioner 1 18 to effectively monitor the commissioning process of the oil platform 102, which involves a large number of the parts 128 and the complex installation and/or inspection processes thereof.
  • An example commissioning management system 1 14 is illustrated and described with reference to FIG. 12.
  • the client computing device 1 16 provides an interface for the client 120 to access the commissioner computing device 1 12 and check the status of the commissioning process.
  • An example client computing device 1 16 is illustrated and described with reference to FIG. 29.
  • the commissioner 1 18 is a person or a business entity that operates the commissioner computing device 1 12.
  • the commissioner 1 18 can interact with the commissioning management system 1 14 to perform several commissioning activities or process as described herein.
  • the commissioner 1 18 can also communicate with the system designer 104, the manufacturers 106, the installers 108, the inspector 1 10, and/or the client 120, as necessary.
  • the client 120 is a person or a business entity that operates the oil platform 102 once the construction of the oil platform 102 is complete.
  • the client 120 can be an owner, or an operator, of the oil platform 102.
  • the operator of the oil platform 102 can be the owner of the oil platform 102.
  • the data communication network 122 communicates digital data between one or more computing devices, such as among the commissioner computing device 1 12 and the client computing device 1 16.
  • Examples of the network 122 include one or more of a local area network and a wide area network, such as the Internet.
  • the network 122 includes a wireless communication system, a wired communication system, or a combination of wireless and wired communication systems.
  • a wired communication system can transmit data using electrical or optical signals in various possible embodiments.
  • Wireless communication systems typically transmit signals via electromagnetic waves, such as in the form of optical signals or radio frequency (RF) signals.
  • a wireless communication system typically includes an optical or RF transmitter for transmitting optical or RF signals, and an optical or RF receiver for receiving optical or RF signals. Examples of wireless communication systems include Wi-Fi communication devices (such as devices utilizing wireless routers or wireless access points), cellular communication devices (such as devices utilizing one or more cellular base stations), and other wireless communication devices.
  • FIG. 2 illustrates an example oil platform 102.
  • the oil platform 102 can include a derrick 202, a turntable 204, a blowout preventer 206, a motor 210, a mud tank 212, an electric generator 214, a casing head 216, a drill string 218, a drill collar 220, and a drill bit 222.
  • the derrick 202 is a support structure configured to hold a drilling mechanism that operates to lower and raise the drill string 218 into and out of a wellbore 224.
  • the turntable 204 is part of the drilling mechanism and powered by the motor 210.
  • the turntable 204 is configured to rotate the drill string 21 8, the drill collar 220 and the drill bit 222.
  • the blowout preventer 206 is a device installed at a wellhead 226 to prevent fluids and gases from unintentionally escaping from the wellbore 224.
  • the blowout preventer 206 can include high-pressure valves configured to seal the high-pressure drill lines and relieve pressure when necessary to prevent a blowout of uncontrolled gush of gas or oil to the surface.
  • the power source 210 operates to provide the main source of power to the oil platform 102.
  • the power source 210 can include one or more diesel engines.
  • the mud tank 212 provides storage for storing drilling fluid or mud until it is required down the wellbore 224.
  • the drilling mud is used to lift rock cuttings from the drill bit 222 to the surface and can include a mixture of water, clay, weighting material and chemicals.
  • the mud tank 212 is part of a circulation mechanism that is configured to pump drilling mud under pressure through the turntable 204 and the wellbore 224.
  • the circulation mechanism can include a mud pump (not shown) configured to circulate the drilling fluid.
  • the electric generator 214 is powered by the power source 210 to provide electrical power to the components of the oil platform 102.
  • the casing head 216 is a concrete pipe that lines the wellbore 224, prevents the wellbore 224 from collapsing, and allows the drilling mud to circulate.
  • the casing head 216 is also used to support the surface equipment such as the blowout preventer 206.
  • the drill string 218 is an assembled collection of drill pipe, the drill collar 220 and other tools, which is run into the wellbore 224 to facilitate the drilling of the wellbore 224.
  • the drill pipe is a joint of hollow tubing used to connect the surface equipment to the bottom hole assembly (i.e., the lower part of the drill string 218 that extends from the drill bit 222 to the drill pipe) and acts as a conduit for the drilling mud.
  • the drill collar 220 is a pipe that fits around the drill pipe and configured to place weight on the drill bit 222.
  • the drill bit 222 is a device attached to the end of the drill string 218 and configured to break apart the rock being drilled.
  • the drill bit 222 can be configured in different shapes and/or materials depending on various drilling tasks and rock formations.
  • the oil platform 102 can further include storage or reservoir configured to temporarily store the gases and oil extracted from the wellbore 224 before the gases and oil are transported to shore.
  • FIG. 3 illustrates an example method 300 of implementing the construction system 100.
  • the method 300 includes a design phase 302, a manufacturing phase 304, a commissioning phase 306 including an installation phase 308 and an inspection phase 310, and a handover/operation phase 312.
  • the client 120 can request the system designer 104 to design the oil platform 102 for the client's use.
  • the client 120 can send the design request 124 to the system designer 104.
  • the system designer 104 creates the drawings and specifications 126 for constructing the oil platform 102.
  • the drawings and specifications 126 can be delivered to the manufacturers 106.
  • the manufacturers 106 can produce the parts 128 in accordance with the drawings and specifications 126.
  • the parts 128 are delivered to the installers 108 for installation at the construction site 134.
  • the commissioner 1 18 and/or the commissioner computing device 1 12 can perform several commissioning activities, such as monitoring the installation of the parts 128 and inspecting the parts when installed.
  • the commissioning activities can be performed both in the installation phase 308 and the inspection phase 310.
  • the commissioner computing device 1 12 is also used to update the status of the construction of the oil platform 102 during the installation and inspection processes.
  • the installers 108 install the parts 128, which have been received from the manufacturers 106, according to the drawings and specifications 126 at the construction site 134.
  • the installers 108 can issue the installation certificate 130 for each part 128 after the part 128 is installed properly.
  • the installation certificate 130 can be delivered to the commissioner 1 18 and/or the commissioner computing device 1 12 for further commissioning process.
  • the inspector 1 10 inspects the operability, and the safety, of the parts 128 that have been installed by the installers 108. For example, the inspector 1 10 can monitor the measurements and gauges applied to predetermined characteristics of the parts 128 or of one or more assemblies of the parts 128. The results can be compared to requirements and standards specified in the drawings and specifications 126 to determine whether the parts 128 and the assemblies of the parts 128 are appropriately operated as designed.
  • the inspector 1 10 can issue the inspection certificate 132 for each part 128 after the part 128 is inspected or tested.
  • the inspection certificate 132 can be delivered to the commissioner 1 18 and/or the commissioner computing device 1 12 for further commissioning process.
  • the oil platform 102 that has been constructed and inspected is handed over to the client 120.
  • the handover of the oil platform 102 is performed when the commissioner 1 18 completes all of the commissioning process to guarantee the operabi!ity (such as, performance, reliability, and safety) of the oil platform 102.
  • the operabi!ity such as, performance, reliability, and safety
  • FIG. 4 illustrates an example diagram 320 of implementing the construction system 100.
  • the diagram 320 includes operations 322, 324, 326, 328, 330, 332, 334, 336, and 338.
  • the system designer 104 sends the drawings and specifications 126 to the manufacturers 106, the installers 108, the inspector 1 10, and the commissioner 1 18 (or the commissioner computing device 1 12).
  • the manufacturers 106 produce the parts 128 that are to be used for constructing the oil platform 102.
  • the parts 128 are manufactured in accordance with the drawings and specifications 126 received from the system designer 102.
  • the manufacturers 106 then deliver the parts 128 to the installers 108.
  • the installers 108 install the parts 128 to construct the oil platform 102 at the construction site 134.
  • the installers 108 refer to the drawings and specifications 126 received from the system designer 102.
  • the installers 108 can issue the installation certificates 130 and send them to the commissioner 1 18 (and/or the commissioner computing device 1 12) when they install the parts 128.
  • different installers 108A and 108B can use different formats of installation certificates 130.
  • the installation certificates 130 are documents that certify the installation of the associated parts 128.
  • one installation certificate 130 is issued for each part 128.
  • more than on installation certificates 132 can be issued for each of at least some of the parts 128.
  • the installation certificates 130 can be prepared for a combination or assembly of a plurality of the parts 128.
  • the inspector 1 10 performs inspection of the installed parts 128.
  • the inspector 1 10 ensures that the parts 128 have been appropriately installed according to the drawings and specifications 126, and that the subsets of, and/or the entirety of, the oil platform 102 are safely operable in normal operation.
  • the inspection of the installed parts 128 can include testing of the parts 128 to ensure that the parts 128 meets the requirements and standards specified in the drawings and specifications 126.
  • the inspector 1 10 can issue the inspection certificates 132 and send them to the commissioner 1 18 (and/or the commissioner computing device 1 12).
  • the inspection certificates 132 are documents that certify the operability, such as performance, safety, and reliability, of the parts 128, the subset of the oil platform 102, and/or the whole oil platform 102.
  • the commissioner 1 18 and/or the commissioner computing device 1 12 can report the status of the construction of the oil platform 102 to the client 120 (and/or the client computing device 1 16).
  • the construction status of the oil platform 102 includes, for example, a list of the parts 128 that have been installed and/or inspected, and the percentage of the installed and inspected parts out of all of the parts 128.
  • the commissioner computing device 1 12 operates to permit the client computing device 1 16 to access the data or information about the commissioning process stored in the commissioner computing device 1 12.
  • the operations 326, 328, 330, 332, and 334 are repeated until the construction of the oil platform 102 is completed.
  • the commissioner 1 18 and/or the commissioner computing device 1 12 confirms the completion of the construction of the oil platform 102.
  • the construction of the oil platform 102 is considered to be complete when all of the parts 128 are installed and inspected and, therefore, all of the installation certificates 130 and the inspection certificates 132 are issued.
  • the commissioner 1 18 hands over the oil platform 102 to the client 120 once the completion of the construction (including the commissioning process) is confirmed.
  • FIG. 5 illustrates an example set of drawings and specifications 126.
  • the set of drawings and specifications 126 includes one or more drawings 340 and one or more specifications 342.
  • Each of the specifications 342 can include a parts list 344.
  • the drawings 340 are designed to show information about the parts 128, such as types, functions, and relationship of the parts 128.
  • An example drawing 340 is illustrated and described in more detail with reference to FIG. 6.
  • the specifications 342 contain a set of requirements and standards to be satisfied by the parts 128, the subsets of the oil platform 102, and/or the entire oil platform 102.
  • the requirements and standards can include, for example, materials, designs, products, services, safety requirements, and regulatory requirements.
  • the specifications 342 are used by several entities, such as the manufacturers 106, the installers 108, inspector 1 10, and the commissioner 1 1 8, in the construction system 100 to verify that all of the relevant requirements and standards are met.
  • the specifications 342 can contain material requirements (e.g., physical, mechanical, electrical, and chemical); acceptance testing requirements (e.g., performance testing); photographs or technical illustrations; certifications requirements; safety considerations and requirements; environmental considerations and requirements; quality control requirements, acceptance sampling, inspections, and acceptance criteria; person, office, or agency responsible for enforcement of the specification; completion and delivery requirements; and/or references and citations for which any instructions in the content may be required to fulfill the traceability and clarity of the document.
  • material requirements e.g., physical, mechanical, electrical, and chemical
  • acceptance testing requirements e.g., performance testing
  • photographs or technical illustrations e.g., certifications requirements; safety considerations and requirements; environmental considerations and requirements; quality control requirements, acceptance sampling, inspections, and acceptance criteria; person, office, or agency responsible for enforcement of the specification; completion and delivery requirements; and/or references and citations for which any instructions in the content may be required to fulfill the traceability and clarity of the document.
  • the parts list 344 contained in the specification 342 shows several pieces of information about the parts 128 used in the construction of the oil platform 102.
  • An example parts list 344 is illustrated and described in more detail with reference to FIG. 7.
  • FIG. 6 illustrates an example drawing 340.
  • the drawing 340 includes one or more part diagrams 346 (including 346A-E), one or more interconnection lines 348 (including 348A-E), and one or more continuation drawing signs 350.
  • the drawing 340 can be a piping and instrumentation diagram (P&1D), which shows the piping of the process flow, as well as the installed equipment and instrumentation used to control the process.
  • the drawing 340 can illustrate the physical sequence of equipment and systems and the interconnection of the systems.
  • the drawing 340 can also represent control and shutdown schemes, safety and regulatory requirements, and startup and operational information.
  • the part diagrams 346 can represent the parts 128, which include mechanical elements, components, apparatuses and/or pieces of equipment that constitute the oil platform 102.
  • the part diagrams 346 can also show valves, vents, drains, special fittings, sampling lines, reducers, increasers and swaggers.
  • the part diagrams 346 can accompany identifications or labels (e.g., names and numbers) thereof.
  • the interconnection lines 348 are configured to show the relationship among the part diagrams 346.
  • the interconnection lines 348 can accompany interconnections references, flow directions, and process piping, sizes and identifications.
  • the continuation drawing signs 350 is used to indicate that the associated part diagram (e.g., 364E) is connected to one or more components in another drawing 340 identified by the continuation drawing sign 350. As described herein, the continuation drawing sign 350 can be identified and linked to the other drawing 340.
  • FIG. 7 illustrates an example parts list 344.
  • the parts list 344 is configured as a table with a plurality of attributes.
  • the attributes of the parts list 344 can include part IDs, vendor tags, construction site IDs, project IDs, system IDs, subsystem IDs, drawing IDs, part descriptions, installation certification information, and inspection certification information. In other embodiments, however, the parts list 344 can be made in other formats.
  • the part IDs are configured to identify the parts 128.
  • the parts 128 are identified with their associated part numbers, and thus the part numbers are used as the part IDs.
  • the vendor tags are identifications used by vendors, such as the manufacturers 106. The vendor tags are particularly useful when the identifications used by the vendors are different from the part IDs used in the commissioning process.
  • the construction site IDs identify at which construction site 134 the associated part 128 is used.
  • Each of the construction sites can include one or more projects.
  • the project IDs identify for which project the associated part 128 is used.
  • the construction site 134 can be designed to construct multiple oil platforms 102, each of which is identified as one project.
  • each of the projects can include one or more systems.
  • Examples of the systems for the construction of the oil platform 102 include a fire and gas system (for detecting fire and gas leakage), an emergency shut-down system
  • a gas compression system for handling emergency conditions
  • a lighting system for handling emergency conditions
  • a deck system for handling emergency conditions
  • each of the systems can include one or more subsystems.
  • the subsystem of the gas compression system can b,e each of different compressors used in the gas compression system.
  • the project IDs, the system IDs, and the subsystem IDs are configured to categorize all of the parts 128 used at the construction site 134 with a hierarchy, thereby easing the management of the parts 128 during the commissioning process.
  • the subsystem IDs are the lowest rank in the hierarchy. In other embodiments, the subsystem IDs are identical to the part IDs.
  • the drawing IDs are configured to show which drawing 340 an associated part 128 belongs to. At least some of the parts 128 can be included in a plurality of the drawings 340.
  • the part descriptions contain any information about the associated part. Examples of the part descriptions include the function of the parts, the nature of the parts, and any other information that should be noted.
  • the installation certification information identifies the installation certificate 130 required for the associated part 128.
  • the inspection certification information identifies the inspection certificate 132 required for the associated part 128.
  • FIG. 8 illustrates an example performance 360 of the system designer 104.
  • the performance 360 includes steps 362, 364, 366 and 368.
  • the system designer 104 receives the design request or order
  • the design request 124 can include several pieces of information about the oil platform 102, such as functional or operational requirements, safety requirements, and regulatory requirements.
  • the system designer 104 designs the oil platform 102 based upon the design request 124.
  • the system designer 104 generates the drawings and specifications 126 as designed.
  • the system designer 104 sends or delivers the drawings and specifications 126 to relevant entities in the construction system 100, such as the manufacturers 106, the installers 108, the inspector 1 10, and the commissioner 1 18 (and/or the commissioner computing device 1 12).
  • the drawings and specifications 126 can be sent or delivered to the client 120 (and/or the client computing device 1 16) for the client's reference.
  • FIG. 9 illustrates an example performance 370 of the manufacturer 106.
  • the performance includes steps 372, 374 and 376.
  • the manufacturer 106 receives an order for one or more of the parts 128 from the client 120 or the system designer 104.
  • the order can include the drawings and specifications 126.
  • the manufacturer 106 manufactures one or more of the parts
  • the manufacturer 106 delivers the manufactured parts 128 to the client 120 or directly to the installers 108 at the construction site 134.
  • FIG. 10 illustrates an exemplary architecture of the commissioner computing device 1 12.
  • the architecture of the commissioner computing device 1 12 can also be similarly implemented in the client computing device 1 16, one or more computing devices for the system designer 104, and one or more computing devices for the manufacturer 106.
  • One or more computing devices, such as the type illustrated in FIG. 10, are used to execute the operating system, application programs, and software modules (including the software engines) described herein.
  • the computing device 156 includes, in at least some embodiments, at least one processing device 400, such as a central processing unit (CPU).
  • processing device 400 such as a central processing unit (CPU).
  • CPU central processing unit
  • a variety of processing devices are available from a variety of manufacturers, for example, Intel or Advanced Micro Devices.
  • the computing device 156 also includes a system memory 402, and a system bus 404 that couples various system components including the system memory 402 to the processing device 400.
  • the system bus 404 is one of any number of types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
  • Examples of computing devices suitable for the computing device 156 include a desktop computer, a laptop computer, a tablet computer, a mobile phone device such as a smart phone, or other devices configured to process digital instructions.
  • the system memory 402 includes read only memory 406 and random access memory 408.
  • the computing device 156 also includes a secondary storage device 412 in some embodiments, such as a hard disk drive, for storing digital data.
  • the secondary storage device 412 is connected to the system bus 404 by a secondary storage interface 414.
  • the secondary storage devices and their associated computer readable media provide nonvolatile storage of computer readable instructions (including 3268 application programs and program modules), data structures, and other data for the computing device 156.
  • exemplary environment described herein employs a hard disk drive as a secondary storage device
  • other types of computer readable storage media are used in other embodiments.
  • Examples of these other types of computer readable storage media include magnetic cassettes, flash memory or other solid state memory technology, digital video disks, Bernoulli cartridges, compact disc read only memories, digital versatile disk read only memories, random access memories, or read only memories.
  • Some embodiments include non-transitory media.
  • a number of program modules can be stored in secondary storage device 412 or memory 402, including an operating system 416, one or more application programs 418, other program modules 420, and program data 422.
  • the data used by the computing device 156 may be stored at any location in the memory 402, such as the program data 422, or at the secondary storage device 412.
  • computing device 156 includes input devices 424 to enable the caregiver to provide inputs to the computing device 156.
  • input devices 424 include a keyboard 426, pointer input device 428, microphone 430, and touch sensor 432.
  • a touch-sensitive display device is an example of a touch sensor.
  • Other embodiments include other input devices 424.
  • the input devices are often connected to the processing device 400 through an input/output interface 434 that is coupled to the system bus 404. These input devices 424 can be connected by any number of input/output interfaces, such as a parallel port, serial port, game port, or a universal serial bus.
  • Wireless communication between input devices 424 and interface 434 is possible as well, and includes infrared, BLUETOOTH® wireless technology, 802.1 l a/b/g/n, cellular or other radio frequency communication systems in some possible embodiments.
  • a touch sensitive display device 436 is also connected to the system bus 404 via an interface, such as a video adapter 438.
  • the display device 436 is a touch sensitive display device.
  • a touch sensitive display device includes sensor for receiving input from a user when the user touches the display or, in some embodiments, or gets close to touching the display.
  • sensors can be capacitive sensors, pressure sensors, optical sensors, or other touch sensors. The sensors not only detect contact with the display, but also the location of the contact and movement of the contact over time. For example, a user can move a finger or stylus across the screen or near the screen to provide written inputs. The written inputs are evaluated and, in some embodiments, converted into text inputs.
  • the computing device 156 can include various other peripheral devices (not shown), such as speakers or a printer.
  • the computing device 156 When used in a local area networking environment or a wide area networking environment (such as the Internet), the computing device 156 is typically connected to the network through a network interface, such as a wireless network interface 440. Other possible embodiments use other communication devices. For example, some embodiments of the computing device 156 include an Ethernet network interface, or a modem for communicating across the network.
  • the computing device 156 typically includes at least some form of computer-readable media.
  • Computer readable media includes any available media that can be accessed by the computing device 156.
  • Computer- readable media include computer readable storage media and computer readable communication media.
  • Computer readable storage media includes volatile and nonvolatile, removable and non-removable media implemented in any device configured to store information such as computer readable instructions, data structures, program modules, or other data.
  • Computer readable storage media includes, but is not limited to, random access memory, read only memory, electrically erasable programmable read only memory, flash memory or other memory technology, compact disc read only memory, digital versatile disks or other optical storage ⁇ magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the computing device 156.
  • Computer readable storage media is an example of a computer readable data storage device.
  • Computer readable communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
  • modulated data signal refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • computer readable communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.
  • the computing devices such as the commissioner computing device 1 12, the client computing device 1 16, the system designer computing device, and manufacturer computing device, do not include all of the elements illustrated in FIG. 10.
  • FIG. 1 1 illustrates an example method 500 of operating the commissioner computing device 1 12.
  • the method 450 includes a setup operation 502 and a commissioning operation 504.
  • the operations 502 and 504 of the method 500 can be performed by one or more processors (such as the processing device 400, as depicted in FIG. 10).
  • the setup operation 502 includes operations that are performed prior to the commissioning activities or processes in the commissioning operation 504. As described herein, the setup operation 502 can include preparation of the drawings 340 and the specifications 342 that are used during the commissioning of the oil platform 102.
  • the commissioning operation 504 includes several commissioning activities or processes, such as monitoring the installation of the parts 128 and inspecting the parts 128 when installed. As described herein, the commissioning operation 504 can include manage a plurality of certificates issued by the installers 108 and the inspector 1 10 at the construction site 134.
  • FIG. 12 illustrates an example commissioner computing device 1 12 including the commissioning management system 1 14.
  • the commissioning management system 1 14 can include a setup engine 512 and a commissioning engine 514.
  • the commissioning management system 1 14 of the commissioner computing device 1 12 operates to visualize the construction status and other pieces of information of the oil platform 102 so that the commissioner 1 18 effectively monitors the installation and inspection activities and conducts other commissioning 2014/003268 processes for the oil platform 102, which involves a large number of the parts 128 and the sophisticating installation and/or inspection of the parts 128.
  • the setup engine 512 is configured to perform the setup operation 502 as described herein. An example operation of the setup engine 512 is described and illustrated in more detail with reference to FIGS. 13-17.
  • the commissioning engine 514 is configured to perform the commissioning operation 504 as described herein. An example operation of the commissioning engine 514 is illustrated and described with reference to FIGS. 18-25.
  • FIG. 13 is an example method 520 of operating the setup engine 512.
  • the method 520 includes operations 522, 524, 526, 528 and 530.
  • the method 520 can be performed by one or more processors (such as the processing device 400, as depicted in FIG. 10).
  • the setup engine 512 operates to receive the drawings 340.
  • the setup engine 512 enables the commissioner 1 18 to import the drawings 340 to the commissioner computing device 1 12.
  • the commissioner 1 18 can interact with an application program or software module that is executed in the commissioner computing device 1 12 and provides a user interface for the commissioner 1 18 to add one or more new drawings 340 into the commissioning management system 1 14.
  • the setup engine 512 operates to receive the specification 342 including the parts list 344. Similarly to the operation 522, the setup engine 512 can enable the commissioner 1 18 to import the specifications 342 or the parts lists 344 thereof to the commissioner computing device 1 12. For example, the commissioner 1 18 can interact with the application program or software module to add the specifications 342 or the parts lists 344 into the commissioning management system 1 14.
  • the specifications 342 and/or the parts lists 344 can be converted to Microsoft Excel Worksheet files (.XLS or XLSX format) in order to be imported into the commissioning management system 1 14.
  • the specifications 342 and/or the parts lists 344 are required to include predetermined fields in a specified order.
  • the commissioning management system 1 14 requires the worksheets of the specifications 342 and/or the 2014/003268 parts lists 344 to be organized to have, for example, the part IDs, vendor tags, part descriptions, system IDs, and subsystem IDs in this order.
  • the setup engine 512 operates to identify the parts 128 in the drawings 340.
  • the setup engine 512 can enable the commissioner 1 18 to set boundaries for the parts 128 to identify them on the drawing 340.
  • the commissioner 1 18 can place labels 554 (FIG. 14) (such as part names and/or numbers) to desired locations to identify the parts 128.
  • FIG. 14 An example of the operation 526 is illustrated and described in more detail with reference to FIG. 14.
  • the setup engine 512 operates to tag the parts 128 in the drawings 340.
  • the setup engine 512 can enable the commissioner 1 18 to mark up the drawings 340.
  • the setup engine 512 allows the commissioner 1 18 to assign tags 572 (FIG. 15) to the parts 128 so that the tagged parts 128 are easily accessible during the commissioning process.
  • tags 572 FIG. 15
  • An example of the operation 528 is illustrated and described in more detail with reference to FIGS. 15 and 16.
  • the setup engine 512 operates to link the components or elements (e.g., the part diagrams 346, the interconnection lines 348, the continuation drawing signs 350, and labels 554 (FIG. 14)) illustrated in one of the drawings 340 to another drawing 340.
  • the setup engine 512 can permit the commissioner 1 18 to create links from the continuation drawing signs 350 to other drawings 340.
  • An example of the operation 530 is illustrated and described in more detail with reference to FIG. 17.
  • FIG. 14 is an example user interface 550, illustrating the operation 526 of FIG. 13, which is to identify the drawing elements (e.g., the part diagrams 346, the interconnection lines 348, the continuation drawing signs 350, and labels 554) in the drawings 340.
  • the user interface 550 can be displayed on a display screen of the commissioner computing device 1 12.
  • the user interface 550 is designed and arranged to display the drawing 340 thereon.
  • the drawing 340 can include one or more identification boundaries 552 (including 552A-G) and one or more labels 554 (including 554A-C).
  • the drawings 340 that have been received in electronic format need to be processed so that each of the drawing elements in the drawings 340 are recognized by the commissioning management system 1 14.
  • the commissioner computing device 1 12 can operate to identify the elements in the drawings 340. In other embodiments, any other computing device can be used to perform the identification of the elements in the drawings 340.
  • the identification boundaries 552 are used to identify the drawing elements (e.g., the part diagrams 346, the interconnection lines 348, and the continuation drawing signs 350) in the drawing 340. In at least one embodiment, the identification boundaries 552 are defined to incorporate the drawing elements that are intended to be identified. For example, where the part diagram 346A is to be identified, the commissioner 1 18 can place a cursor 560 at a first corner location 556 and select the first corner location 556 by clicking on. Then, the commissioner 1 18 drags the cursor 560 from the first corner location 556 to a second corner location 558 to delineate the boundary 552A, and clicks again to mark the second corner location 558. After that, the commissioner 1 18 can submit the defined boundary 552A by further interacting with the user interface 550 of the setup engine 512.
  • the commissioner 1 18 can submit the defined boundary 552A by further interacting with the user interface 550 of the setup engine 512.
  • the drawings 340 can be layered to identify and/or highlight individual identification boundaries 552.
  • the labels 554 are used to present the names and/or numbers of the parts 128 in the drawings 340.
  • the commissioner 1 18 can interact with the user interface 550 to create a label 554A and adjust the location of the label 554A.
  • the label 554A contains the name of the associated part 128 and is placed adjacent the part diagram 346A.
  • FIG. 15 is an example user interface 570, illustrating the operation 528 of
  • FIG. 13 which is to tag the parts 128 in the drawings 340.
  • the user interface 570 can be displayed on a display screen of the commissioner computing device 1 12.
  • the user interface 570 is designed and arranged to display the drawing 340 thereon.
  • the drawing 340 can include one or more tags 572 (including 572A-E).
  • the tags 572 operate as indexes for the associated part diagrams 346 and are configured to display various pieces of information about the associated part 128. For example, the tags 572 are linked to a new window 574 (FIG. 16) that shows the 3268 information about the parts 128 (FIG. 16).
  • the setup engine 512 is configured to enable the commissioner 1 18 to create the tags 572 and associate them with the parts 128, and adjust the locations of the tags 572 adjacent the part diagrams 346 through the user interface 570.
  • the setup engine 512 permits the commissioner 1 18 to interact with the user interface 570 and import a preexisting file that includes the information about one or more of the tags 572. When the file is imported, at least one of the part diagrams 346 can be automatically tagged with the tags 572 in accordance with the information contained in the file.
  • the setup engine 512 also permits the commissioner 1 18 to edit the tags 572 through the user interface 570.
  • the tags 572 can be associated with any drawing elements on the drawings 340, as well as the part diagrams 346.
  • the tags 572 can be connected to the labels 554 such as the part names and numbers.
  • FIG. 16 illustrates an example tagged item window 574.
  • the tagged item window 573 is a new window that presents several pieces of information about the selected part 128.
  • the tagged item window 573 displays the part name, the vendor tag, the part description, the system ID, the subsystem ID, the installation certification information, the inspection certification information, and additional files, which are associated with the selected part 128.
  • the tagged item window 573 pops up on the user interface 570 and shows the information about the associated part 128.
  • the tagged item window 573 can be configured to receive a user input to create a new tag 572 on the drawing 340.
  • the tagged item window 573 can also be configured to enable the commissioner 1 18 to edit the information displayed thereon.
  • the commissioner 1 18 can change or modify the information about the part name, the vendor tag, the part description, the system ID, and the subsystem ID.
  • the commissioner 1 18 can update or change the installation certification information and/or the inspection certification information.
  • the installation certificate 130 and/or the inspection certificate 132 associated with the selected part 128 can be uploaded or replaced through the tagged item window 573 that has been opened for that part 128.
  • the commissioner 1 18 can import a variety of files relevant to the selected part 128.
  • Examples of such additional files include photographs, video clips, and data sheets of the part 128.
  • the photographs and/or the video clips of the part 128 can be used to show the operability and safety of the part 128 when installed at the construction site 134.
  • FIG. 17 illustrates an example user interface 590, illustrating the operation 530 of FIG. 13, which is to link the elements of a first drawing 340A to a second drawing 340B.
  • the user interface 590 can be displayed on a display screen of the commissioner computing device 1 12.
  • the user interface 590 is designed and arranged to selectively display the drawings 340 (including 340A and 340B) thereon.
  • the drawing 340 can include one or more link regions 592.
  • the link regions 592 provide an interface for the commissioner 1 18 to load the linked drawing 340B, overlapping or replacing the original drawing 340A. For example, when the commissioner 1 1 8 selects and clicks on the link region 592 with the cursor 560, the original drawing 340A is replaced or overlapped with the linked drawing 340B and displayed on the user interface 590.
  • the link regions 592 are defined to incorporate the drawing elements that are intended to be linked to other drawings 340B.
  • the commissioner 1 18 can place a cursor 560 at a first corner location 594 and select the first corner location 596 by click-on. Then, the commissioner 1 18 drags the cursor 560 from the first corner location 594 to a second corner location 596 to delineate the link region 592, and clicks again to mark the second corner location 596.
  • the user interface 590 operates to provide an interface for the commissioner 1 18 to select a desired drawing 340B to be linked to the selected link region 592 on the original drawing 340A.
  • the commissioner 1 18 can submit the defined link region 592 by further interacting with the user interface 590 of the setup engine 512.
  • FIG. 18 illustrates an example commissioning engine 514.
  • the commissioning engine 514 includes a certificate management engine 702 and a checklist management engine 704.
  • the certificate management engine 702 operates to manage various certificates, such as installation certificates 130 and inspection certificates 132, during commissioning process. As described herein, the certificate management engine 702 operates to visualize the record of the certificates issued from the construction site 134, thereby permitting the commissioner 1 18 to easily perform and monitor the commissioning activities. An example operation of the certificate management engine 702 is described and illustrated in FIG. 19.
  • the checklist management engine 704 operates to manage various checklists during commissioning process.
  • the checklist management engine 704 provides an interface for the commissioner 1 18 to monitor, update, and manage the progress of the construction and/or commissioning of the oil platform 102.
  • An example operation of the checklist management engine 704 is described and illustrated in FIG. 28.
  • FIG. 19 is a flowchart of an example method 710 of operating the certificate management engine 702.
  • the method 710 includes operations 712, 714 and 716.
  • the operations 712, 714 and 716 of the method 710 can be performed by one or more processors (such as the processing device 400, as depicted in FIG. 10).
  • the certificate management engine 702 operates to receive one or more installation certificates 130.
  • the certificate management engine 702 can operate to store the received installation certificates 130 in the commissioner computing device 1 12.
  • the stored installation certificates 130 can be retrieved by the certificate management engine 702 when necessary.
  • the installation certificates 130 are issued by the installers 108 after the installers 108 perform the installation of the parts 128 for which they are responsible.
  • the certificate management engine 702 operates to receive one or more inspection certificates 132.
  • the certificate management engine 702 can operate to store the received inspection certificates 132 in the commissioner computing device 1 12.
  • the stored inspection certificates 132 can be retrieved by the certificate management engine 702 when necessary.
  • the inspection certificates 132 are issued by the inspector 1 10 when the operability and safety of the parts 128, the subsystem thereof, and/or the system thereof are ensured in accordance to the requirements and standards specified in the specifications 342.
  • An example certificate 130 and 132 is illustrated and described in more detail with reference to FIG. 20.
  • Example operations 712 and 714 are described and illustrated in more detail with reference to FIG. 21.
  • the certificate management engine 702 operates to update the construction status with the received certificates 130 and 132.
  • the construction status can represent how much the construction and inspection has progressed in terms of the percentage of the certificates completed.
  • An example operation 716 is illustrated and described with reference to FIGS. 22-26.
  • FIG. 20 illustrates an example certificate 720 (including 130 and 132).
  • the certificate 720 includes a subject information field 722, an inspection/installation list 724, and a verification field 726.
  • the subject information field 722 includes different pieces of information about the items (e.g., the parts 128) that are installed and/or inspected.
  • the information contained in the subject information field 722 can be used by the commissioner 1 18 to identify and categorize the subject part 128, for which the certificate 720 is issued.
  • the subject information field 722 can include the part ID, the part description, the system ID, the subsystem ID, the manufacturer, the vendor tag, the model number, the data sheet, and other pieces of information associated with the part 128.
  • the inspection/installation list 724 includes a list of inspection/installation descriptions that the installers 108 and/or the inspector 1 10 need to confirm during installation and/or commissioning process.
  • the installers 108 and/or the inspector 1 10 read the list of inspection/installation descriptions and make sure that all of the inspection/installation descriptions are satisfied.
  • the verification field 726 includes a signature box that is designed for the installers 108 and/or the inspector 1 10 to leave their signature once the inspection/installation descriptions are confirmed.
  • FIG. 21 is a flowchart illustrating an example method 730 of receiving the certificates 720 (including 130 and 132) (i.e., the operations 712 and 714).
  • the method 730 includes operations 732, 734, 736 and 738.
  • the operations 736 and 738 can be performed by one or more processors (such as the processing device 400, as depicted in FIG. 10).
  • the commissioner 1 18 or the commissioner computing device 1 12 receives the certificate 720.
  • the commissioner 1 18 can receive a hard copy of the certificate 720 from the installers 108 or the inspector 1 10. In other embodiments, the commissioner 1 18 can receive an electronic copy of the certificate 720.
  • the method 730 it is determined whether the received certificate 720 is in an electronic format. If the certificate 720 is not an electronic version (i.e., if a hard copy of the certificate 720 is received) ("NO" in the operation 734), then the method 730 continues to the operation 736. Otherwise (“YES” in the operation 734), then the method 730 continues to the operation 738.
  • the commissioner computing device 1 12 or any other computing device operates to convert the hard copy of the certificate 720 into an electronic format, such PDF and Microsoft Word files.
  • the commissioner 1 18 imports the electronic version of the certificate 720 into the commissioner computing device 1 12.
  • the method 730 considers that the commissioner 1 18 performs importing of the electronic version of the certificate 720 into the commissioner computing device 1 12, the electronic version of the certificate 720 can be transmitted directly from the installers 108 or the inspector 1 10 to the commissioner computing device 1 12 through the network 122.
  • FIG. 22 is a flowchart illustrating an example method 750 of updating the construction status (i.e., the operation 716).
  • the method 750 includes operations 752 and 754.
  • the operations 752 and 754 can be performed by one or more processors (such as the processing device 400, as depicted in FIG. 10).
  • the commissioner computing device 1 12 (i.e., the commissioning engine 514 or the certificate management engine 702 thereof) operates to tag the associated part 128 with the received certificate 720.
  • the part 128 is tagged with the certificate 720 through the tagged item window 573.
  • the commissioner 1 18 can open the tagged item window 573 by selecting the tag 572 associated with the part 128 on the user interface 570, and edit the information about the certificate 720 through the tagged item window 573.
  • the commissioner 1 18 can upload the electronic file of the certificate 720 through the tagged item window 573.
  • the part 128 is tagged with the certificate 720 in a different manner, which is illustrated and described with reference to FIG. 23.
  • the commissioner computing device 1 12 i.e., the commissioning engine 514 or the certificate management engine 702 thereof
  • the commissioner computing device 1 12 operates to update the construction status during the installation and inspection processes.
  • the information about the part 128 is updated with the certificate 720, and the drawings 340 and the item lists 344 are also updated with the certificate 720.
  • An example operation 754 is described and illustrated in more detail with reference to FIG. 24-34.
  • FIG. 23 illustrates an example user interface 770, illustrating the operation 752 of FIG. 22, which is to tag the part 128 with the certificate 720.
  • the user interface 770 can be displayed on a display screen of the commissioner computing device 1 12.
  • the user interface 770 is designed and arranged to display a certificate template 772.
  • the certificate template 772 can provide a table 774 including a part ID field 776, an installation certificates field 778, and an inspection certificates field 780.
  • the part ID field 776 lists the parts 128 that are selected under the criteria that the commissioner 1 18 has chosen. For example, the parts 128 that belong to a particular system or subsystem can be selected to be listed in the part ID field 776. Alternatively, all of the parts 128 that are selected from a particular project can be shown in the part ID field 776.
  • the installation certificates field 778 displays all of the installation certificates 130 that are available from the commissioner computing device 1 12. In at least one embodiment, the installation certificates field 778 lists all of the installation certificate files 782 (i.e., the electronic versions of the installation certificates 130) that have been imported at the operation 712.
  • the inspection certificates field 780 displays all of the inspection certificates 132 that are available from the commissioner computing device 1 12. In at least one embodiment, the inspection certificates field 780 lists all of the inspection certificate files 784 (i.e., the electronic versions of the inspection certificates 132) that have been imported at the operation 714.
  • each of the parts 128 listed in the part ID field 776 has a checkbox 786 under each of the installation and inspection certificate files 782 and 784.
  • the commissioner 1 18 can interact with the user interface 770 using the cursor 560 and select one or more of the certificate files 782 and 784 as appropriate by checking the associated checkbox 786. Accordingly, the parts 128 are tagged with the relevant certificates 130 and 132 (collectively, 720).
  • FIG. 24 illustrates an example method 800 of performing the operation 754 of FIG. 22, which is to update the construction status with the certificates 720.
  • the method 800 includes operations 802, 804, 806, 808, 810 and 812.
  • the operations of the method 800 can be performed by one or more processors (such as the processing device 400, as depicted in FIG. 10).
  • the commissioner computing device 1 12 i.e., the commissioning engine 514 or the certificate management engine 702 thereof
  • the commissioner computing device 1 12 operates to determine whether any certificate 720 is received and imported. If it is determined that the certificate 720 is not received or imported in the commissioner computing device 1 12 ("NO" at the operation 802), then the method 800 continues to the operation 804. If it is determined that the certificate 720 has been received and imported in the commissioner computing device 1 12 ("YES" at the operation 802), then the method 800 continues to the operation 806.
  • the commissioner computing device 1 12 i.e., the commissioning engine 514 or the certificate management engine 702 thereof
  • the commissioner computing device 1 12 operates to present the part 128, for which any certificate 720 is not received, with a first visual indicator 822.
  • the commissioner computing device 1 12 i.e., the commissioning engine 514 or the certificate management engine 702 thereof
  • the commissioner computing device 1 12 operates to determine whether the certificate 720 received is the installation certificate 130 or the inspection certificate 132. If it is determined that the installation certificate 130 is received ("Installation Certificate” at the operation 806), then the method 800 continues to the operation 808. If it is determined that the inspection certificate 132 is received ("Inspection Certificate” at the operation 806), then the method 800 continues to the operation 810.
  • the commissioner computing device 1 12 i.e., the commissioning engine 514 or the certificate management engine 702 thereof
  • the commissioner computing device 1 12 operates to present the part 128, for which the installation certificate 130 has been received, with a second visual indicator 824.
  • the commissioner computing device 1 12 i.e., the commissioning engine 514 or the certificate management engine 702 thereof
  • the method 800 continues to the operation 804. In this case, it is assumed that the inspection certificate 132 was received in error and the installation certificate 130 should be received first. If it is determined that there is no installation certificate 130 received prior to the inspection certificate 132 ("NO" at the operation 810), the method 800 continues to the operation 812.
  • the commissioner computing device 1 12 i.e., the commissioning engine 514 or the certificate management engine 702 thereof
  • the commissioner computing device 1 12 operates to present the part 128, for which both of the installation certificate 130 and the inspection certificate 132 have been received, with a third visual indicator 826.
  • the visual indicators can be of any type suitable for distinguishing the first, second and third visual indicators 822, 824 and 826. Examples of the visual indicators include color, shading, hatching, marks, and symbols.
  • FIG. 25 illustrates an example drawing 340 with the certificates 720 updated.
  • the drawing 340 is displayed on a user interface 830.
  • the user interface 830 can be displayed on a display screen of the commissioner computing device 1 12.
  • the user interface 830 is designed and arranged to display the drawing 340 thereon.
  • the tags 572 (including 572A-E) associated with the parts 128 are identified with different visual indicators 822, 824 and 826 (e.g., the first, second, and third colors) to represent the construction status of the parts 128.
  • the part diagrams 346C and 346 D are identified with the first visual indicator 822 to represent that the associated parts 128 (e.g., Parts 3 and 4) have not installed or inspected and thus no certificate 720 has been received.
  • the part diagrams 346A and 346E are identified with the second visual indicator 824 to represent that the associated parts 128 (e.g., Parts 1 and 5) have been installed, but not inspected, and thus the installation certificates 130 have been received, but the inspection certificates 132 have not been received.
  • the part diagram 346B is identified with the third visual indicator 826 to represent that the associated part 128 (e.g., Part 2) have been both installed and inspected and thus both of the installation certificate 130 and the inspection certificate 132 have been received.
  • FIG. 26 illustrates an example parts list 344 with the certificates 720 updated.
  • the parts list 344 is displayed on a user interface 840.
  • the user interface 840 can be displayed on a display screen of the commissioner computing device 1 12.
  • the user interface 840 is designed and arranged to display the parts list 344 thereon.
  • the parts list 344 are coded with the three visual indicators 822, 824 and 826 in the same manner as in the drawing 340 as illustrated in FIG. 25.
  • the third and fourth rows for the parts 128 are coded with the first visual indicator 822 to represent that the associated parts 128 (e.g., Parts 3 and 4) have not installed or inspected and thus no certificate 720 has been received.
  • the first and fifth rows for the parts 128 are coded with the second visual indicator 824 to represent that the associated parts 128 (e.g., Parts 1 and 5) have been installed, but not inspected, and thus the installation certificates 130 have been received, but the inspection certificates 132 have not been received.
  • the second row for the part 128 (e.g., Part 2) is coded with the third visual indicator 826 to represent that the associated part 128 (e.g., Part 2) have been both installed and inspected and thus both of the installation certificate 130 and the inspection certificate 132 have been received.
  • FIG. 27 is an example database table 850 stored in the commissioner computing device 1 12.
  • the database table 850 includes several fields suitable for identifying the construction status (including the installation status and the inspection status) of the oil platform 102 during installation and commissioning processes.
  • the database table 850 includes a part ID, a drawing ID, a construction site ID, a project ID, a system ID, a subsystem ID, a vendor tag, a construction status, a parts list, an installation certificate file, an inspection certificate file, a part description, and additional files.
  • the construction status field is identified in three different ways, such as neither installed nor inspected; installed but not inspected; and both installed and inspected.
  • the installation certificate file field and the inspection certificate file field can include unique identifications of the electronic files of the installation certificate 130 and the inspection certificate 132, if any, that have been imported into the commissioner computing device 1 12.
  • the additional files field can include unique identifications of the electronic files imported into the commissioner computing device 1 12. Examples of the additional files include photographs, video clips, data sheets of the part 128. Other fields have already been described and illustrated herein.
  • FIG. 28 is a flowchart illustrating an example method 870 of operating the checklist management engine 704.
  • the method 870 includes operations 872 and 874.
  • the operations of the method 870 can be performed by one or more processors (such as the processing device 400, as depicted in FIG. 10).
  • the checklist management engine 704 operates to manage various checklists during commissioning process.
  • the checklist management engine 704 provides an interface for the commissioner 1 18 to monitor, update, and manage the construction status, such as the installation status and the inspection status, during installation and inspection processes.
  • the checklist management engine 704 operates to receive a discipline checklist and import it into the commissioner computing device 1 12.
  • the checklist management engine 706 operates to update the construction status of the oil platform 102.
  • the checklist management engine 706 can update the construction status of the parts 128 with the three different visual indicators 822, 824 and 826 in the same manner as described with the certificate management engine 702.
  • FIG. 29 illustrates an example client computing device 1 16.
  • the client computing device 1 16 includes a client application 900.
  • the client application 900 operates to communicate with the commissioner computing device 1 12 and access the data stored in the commissioner computing device 1 12.
  • the client application 900 also operates to organize and display the data retrieved from the commissioner computing device 1 12.
  • the client application 900 provides a user interface for the client 120 to interact with the database of the commissioner computing device 1 12 and to view, monitor and/or manage the construction status of the oil platform 102.
  • the client application 900 is a Web-based application, which is accessed over the network 122 and run inside a Web browser.
  • FIGS. 30-33 illustrate an example user interface 910 of the client application 900.
  • FIG. 30 is a diagram of the user interface 910 of the client application 900 with PROJECTS tab selected.
  • the user interface 910 includes a drawing selection region 912, a filter setting 'region 914, a tabs region 916, and a content display region 91 8.
  • the drawing selection region 912 is designed to display different drawings
  • the drawing selection region 912 can display a plurality of the drawings 340 with additional information, such as project IDs.
  • the filter setting region 914 provides different criteria for filtering the search result.
  • the client 120 can set one or more of the filtering criteria to narrow down the search result from the entire database.
  • the filtering criteria include the drawing IDs, the construction site IDs, the project IDs, the system IDs, and the subsystem IDs.
  • the tabs region 916 allows the client 120 to navigate different pieces of information about the drawing 340 that the client 120 has selected.
  • the tabs region 916 provides a plurality of selectable tabs.
  • the tabs region 916 includes PROJECTS tab 920, TAG REGISTER tab 922, DRAWING tab 924; and REPORT tab 926.
  • the PROJECTS tab 920 is designed to show for which project the selected drawing 340 is used.
  • the PROJECTS tab 920 displays the information about the project name, the description of the project, the owner of the project, the construction site associated with the project, and the client of the project.
  • the content display region 918 provides a region on which a selected content is displayed.
  • FIG. 31 is a diagram of the user interface 910 of the client application 900 with the TAG REGISTER tab 922 selected.
  • the TAG REGISTER tab 922 is configured to show the parts list 344 associated with the selected drawing 340.
  • the parts list 344 also shows the construction status of each part 128 with three different color codes 822, 824 and 826.
  • FIG. 32 is a diagram of the user interface 910 of the client application 900 with the DRAWING tab 924 selected.
  • the DRAWING tab 924 is configured to show the selected drawing 340 on the content display region 918.
  • the drawing 340 also shows the construction status of each part 128 with three different color codes 822, 824 and 826.
  • FIG. 33 is a diagram of the user interface 910 of the client application 900 with the REPORT tab 926 selected.
  • the REPORT tab 926 is designed to display the summary of the construction status of the oil platform 102.
  • the REPORT tab 926 can show the total number of the parts 128 on the selected drawing 340, the number and/or percentage of the installation certificates 13 received, the number and/or percentage of the inspection certificates 132 received, and other information, such as the completion rate of the construction of the oil platform 102.
  • the client 120 can refer to the information displayed in the REPORT tab 926 to view the progress of the construction of the oil platform 102.
  • FIG. 34 illustrates an example commissioning system 1000.
  • the commissioning system 1000 includes a commissioning management computing device 1002, the commissioner computing device 1 12 operated by the commissioner 1 18, and tshe client computing device 1 16 operated by the client 120.
  • the commissioning management computing device 1002 can be configured to perform at least some of the operations that are implemented in the commissioner computing device 1 12, replacing the at least some of the operations of the commissioner computing device 1 12.
  • the commissioner computing device 1 12 and the client computing device 1 16 can communicate with the commissioning management computing device 1002 via the data communication network 122.
  • FIG. 35 illustrates an example commissioning management computing device 1002.
  • the commissioning management computing device 1002 includes a commissioning management engine 1004, a report engine 1006, a communication interface 1008, and a database 1010.
  • the commissioning management engine 1004 is configured to replace the commissioning management system 1 14 of the commissioner computing device 1 12 and performs the operations of the commissioning management system 1 14 of the commissioner computing device 1 12.
  • the setup operation 502 and the commissioning operation 504, as described herein, can be performed in connection with the commissioning management engine 1004, rather than the commissioning management system 1 14 of the commissioner computing device 1 12.
  • the report engine 1006 operates to send the summary of the construction status of the oil platform 102 to the client computing device 1 16.
  • the summary of the construction status can include the total number of the parts 128 on the selected drawing 340, the number and/or percentage of the installation certificates 130 received, the number and/or percentage of the inspection certificates 132 received, and other information, such as the completion rate of the construction of the oil platform 102.
  • the communication interface 1008 is configured to enable the commissioning management computing device 1002 to communicate with the commissioner computing device 1 12 and the client computing device 1 16 via the network 122.
  • the database 1010 is configured to store the data relevant to the setup operation 502 and the commissioning operation 504, such as the drawings 340, the specifications 342, and the parts lists 344.
  • the data can be stored in the database 1010 in the form of the database table 774.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Quality & Reliability (AREA)
  • Animal Husbandry (AREA)
  • Operations Research (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Agronomy & Crop Science (AREA)
  • Development Economics (AREA)
  • Marine Sciences & Fisheries (AREA)
  • Mining & Mineral Resources (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un système de gestion de mise en service et un procédé qui consiste à importer une variété de certificats émis lors de la construction et des procédés de mise en service et permettant de visualiser l'état de la construction.
PCT/IB2014/003268 2014-08-18 2014-08-18 Système de gestion de mise en service WO2016027122A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2014/003268 WO2016027122A1 (fr) 2014-08-18 2014-08-18 Système de gestion de mise en service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2014/003268 WO2016027122A1 (fr) 2014-08-18 2014-08-18 Système de gestion de mise en service

Publications (1)

Publication Number Publication Date
WO2016027122A1 true WO2016027122A1 (fr) 2016-02-25

Family

ID=53718039

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2014/003268 WO2016027122A1 (fr) 2014-08-18 2014-08-18 Système de gestion de mise en service

Country Status (1)

Country Link
WO (1) WO2016027122A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110555674A (zh) * 2019-08-29 2019-12-10 森诺科技有限公司 一种油气田钻井现场智能安全管控系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10225178A1 (de) * 2002-05-31 2003-12-24 Siemens Ag Systemarchitektur für die Steuerung und Veranschaulichung eines Projektablaufes
US20040088115A1 (en) * 2002-11-06 2004-05-06 Varco International, Inc. Method and apparatus for dynamic checking and reporting system health
US20120253540A1 (en) * 2011-04-01 2012-10-04 International Business Machines Corporation Energy grid device commissioning method and system
US20130179354A1 (en) * 2011-12-13 2013-07-11 Steven Gary Seat Automated System for Commissioning Verification, Progress Tracking and Punchlist Resolution of Oil and Gas Production Facilities

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10225178A1 (de) * 2002-05-31 2003-12-24 Siemens Ag Systemarchitektur für die Steuerung und Veranschaulichung eines Projektablaufes
US20040088115A1 (en) * 2002-11-06 2004-05-06 Varco International, Inc. Method and apparatus for dynamic checking and reporting system health
US20120253540A1 (en) * 2011-04-01 2012-10-04 International Business Machines Corporation Energy grid device commissioning method and system
US20130179354A1 (en) * 2011-12-13 2013-07-11 Steven Gary Seat Automated System for Commissioning Verification, Progress Tracking and Punchlist Resolution of Oil and Gas Production Facilities

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110555674A (zh) * 2019-08-29 2019-12-10 森诺科技有限公司 一种油气田钻井现场智能安全管控系统

Similar Documents

Publication Publication Date Title
Mochizuki et al. Real-time optimization: classification and assessment
Tabibzadeh et al. Applying the AcciMap methodology to investigate a major accident in offshore drilling: A systematic risk management framework for oil and gas industry
Jamal et al. Effective well management in Sabriyah intelligent digital oilfield
WO2016027122A1 (fr) Système de gestion de mise en service
US20040059510A1 (en) System and method of managing safety compliance data
Strutt et al. API 17N–Recommended Practise for Subsea Production System Reliability, Technical Risk & Integrity Management
Cramer et al. Less Footprints in the Snow for Salym Field in Western Siberia
Ahmad et al. Samarang Integrated Operations (IO)–Achieving Well Performance Monitoring, Surveillance & Optimization Through Data and Model Driven Workflows Automation
Anders et al. Well Integrity Operations at Prudhoe Bay, Alaska
AU2020203768A1 (en) Hazardous Area Information Development and Retrieval
DeBruijn et al. Improved oversight increases service quality for deepwater cementing operations
Elrefai et al. Inhouse design and implementation of well integrity database management system
Vij et al. The First Application of a Cloud-Based Well Engineering Solution in the Middle East Region
US20200272640A1 (en) Data authentication techniques using exploration and/or production data
NIZAR Digitalization and Data Automation: The Path for a More Efficient Well Integrity Data Management and Cost-Effective Responses
Mubashir Ahmad et al. Best Practices While Testing Sour GAS Wells
Barrilleaux et al. Downhole Flow Control for High Rate Water Injection Applications
Su A BIM-based visualization tool for facilities management: Fault detection through integrating real-time sensor data into BIM
Zahacy et al. Risk-ranking approach for thermal well integrity using readily available application, well and operational parameters
Al-Zaabi et al. Integrated Field Surveillance Leading Towards Operational Excellence and Efficiency Enhancement
Dervo et al. Comparison of quantitative blowout risk assessment approaches
Semwogerere et al. Digital and Automated Well Planning for Completions
Irwin et al. The Digitalization of Flow Assurance
Fatnani et al. Operations management dashboards: A production life cycle management study
Airlie et al. Intelligent asset management: Successful integration of modelling tools and workflow processes

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14880378

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14880378

Country of ref document: EP

Kind code of ref document: A1