WO2012006679A1 - Engineering quality system - Google Patents

Abstract

An engineering quality system comprising: a database module to hold at least one database; a computational module to perform a comparison of data in the database against at least one set of quality requirements and a communications module to communicate the results of the comparison.

Description

ENGINEERING QUALITY SYSTEM

Background of the invention:

Currently the completions management processes that are implemented during the construction and commissioning phases of a construction project are paper based systems in which inspection test records and functional test records are used to verify installation quality and plant completion and identify, record and manage noncompliances for either rectification or agreed handover. A completions management system usually allows for completed paper based records to be scanned in and stored in a central repository and thereby allows tracking of the completion process by indicating which inspections and tests have been performed and which activities are outstanding. All plant equipment is subject to these inspections, from tanks, piping and structural items to electrical equipment such as motors, beacons, instruments and control system components.

The current process involves inspecting plant equipment throughout various stages of the project. For example on equipment delivery and receipt to site (or in many cases inspected at various levels at the suppliers sites - i.e. Factory Acceptance Tests) initial inspections are performed to ensure the correct items have been supplied and are in acceptable condition. The items are then stored and await installation by the construction team, who will then build the plant to the engineered design Following construction of plant items mechanical completions inspections are conducted, to verify compliance and quality to the engineering standards specified for the project. During the completion of these records, inspections and testing is performed in the field against various project documents, drawings and information by personnel qualified in the appropriate disciplines. The forms or inspection sheets are filled in by inspectors and technicians and then signed off by approved signatories such as supervisors and client representatives or construction managers. These inspections are used as a mechanism to identify flaws in design, implementation, configuration and installation quality. Punch- listing is a general result of inspections and is a mechanism used to record noncompliances where applicable. The item being inspected is compared against engineering drawings, documents and other information, which must be manually obtained and compiled prior to conducting the inspection work.

On successful physical verification that all the equipment is compliant and installed correctly - or mechanically complete, the equipment is energised and pre- commissioned. This involves powering up or starting equipment and conducting further inspection and verification activities often performed by a new group of people from the commissioning team. The overall inspection and verification process is critical in all usual industrial projects to ensure safe and successful commissioning, start-up and turn-key operation of the asset.

During this verification process there are several activities conducted in terms of testing and configuration, where field test equipment is used to check and verify correct operation of plant equipment. For example field communicators, network analysers, pressure or temperature simulators, multi-meters, special simulators or software applications are taken to the field to conduct functional tests or pre-commissioning activities. For example field communicators are used to connect to instruments, where on-screen parameterisation can be performed to view and change software settings within the instrument and therefore set it up correctly. The results for the functional testing and verification are again hand-written onto inspection forms, and scanned into the completions database signifying a completed verification task.

The current system presents many challenges during mechanical completion and pre- commissioning phases which heavily impact project schedule and in turn lead to a lower quality result. An example disadvantage with the current paper based systems is that the information recorded is not used any further other than as a record of the activities performed and a record of the results that were obtained. The inspection sheets are simply scanned in to a database, with no means of extracting information obtained for use during or after the project completion. Therefore, as databases are not up dated with new information, equipment details are written and re-written for each inspection activity. Additionally the information recorded on the sheets is susceptible to inaccuracy or error and often requires calculations and input from relevant project documents. To properly perform the field inspection, all the appropriate documents and drawings (of the most recent revision) are required, which takes an enormous amount of manually managing, arranging and compiling. Further to this, it is difficult to design test and inspection forms that are both simple and straightforward while still attempting to capture all of the flaws and instances of non-compliance that the client has determined critical for successful and safe start-up of the plant. It is also not uncommon for the inspection workforce to be completely new to the site (having been brought in specifically for this task) and often also new to the particular client's specification criteria and methods of verification. The inspection criteria is often misunderstood, incorrectly challenged or ignored, and workforce capabilities vary with competencies and skills. On larger projects, the most common challenge faced by the quality assurance effort is in keeping quality assurance records consistent and correct, where inspection forms and records are being interpreted differently or incorrectly by a large workforce, and the results are that the biggest problem faced by inspectors is not normally the technical or quality assurance aspects of their work, but rather how it is reported using the supplied documentation / records.

Instrumentation and electrical products and devices used in today's industrial plants and refineries are complex devices that offer many times the capability of conventional units and required technological devices to set up and configure them. With this comes the critical requirement to ensure devices are configured correctly so that their response to certain process conditions, faults and events are precisely as per engineering and design, and in accordance with the device manufacturer's specifications and guidelines. Where equipment is implemented for safety shutdown systems and responsible for the plant operating safely and effectively, it is crucial that the settings that govern their response and behaviour is as per design. Current systems rely on the field technicians to make decisions and change settings to the devices, with very little interaction from engineering or supervisors to ensure this is correct. It is not until commissioning phases that the plant has a view of these configurations, when the instrumentation is brought on-line to plant control and safety systems. During this phase however, there is no real allocation of the right technical resources to investigate the configurations in detail. The current situation is not performed satisfactorily, even on very large projects that are relying on a flawless approach to start-up to achieve schedule and turn-key results and have invested heavily to ensure a high quality result from engineering through to completions and start-up. The current process also has an unacceptably high risk of an incorrect device configuration or its un-suitability being discovered during pre- commissioning and in the commissioning phase. The correct configuration queries can be managed and tracked from a much earlier phase, rather than during a very complex and time-restrictive project phase such as commissioning. Where a lot of engineering effort is placed in designing the installation and determining equipment configuration, the verification process is relied upon to ensure the implementation is correct and it could be said that this process has too many deficiencies and inefficiencies for such a critical project requirement. Essentially current systems rely on a signed inspection record to signify that the work was done correctly. Many industry equipment incidents result from equipment failure related to identifiable aspects that sought to be captured in the completions process. Both the physical configurations and the software configurations of these devices are critical in determining the correct response and behaviours of these critical plant components and the end client or operator relies on the fact that the inspection / verification process is used effectively to guarantee this.

The reference to any prior art in this specification is not, and should not be taken as, an acknowledgement or any form of suggestion that the prior art forms part of the common general knowledge.

Summary of the invention:

According to one aspect of the invention, there is provided an engineering quality system comprising: a database module to hold at least one database; a computational module to perform a comparison of data in the database against at least one set of quality requirements; a first communications module to communicate the results of the comparison and optionally, a second communications module to assist communication of information from an information source.

According to another aspect of the invention, there is provided an engineering quality testing method comprising: comparing data in a database against at least one set of quality requirement, communicating the results of the comparison.

The database module may comprise any suitable number and types of database. For example, in some embodiments the database module comprises an engineering database to store engineering information (for example equipment specifications or other requirements). In some embodiments, there is a completions database to store information which will be useful for a completions process. In some embodiments there is provided a client requirements database to store data about requirements that a client organisation has in relation to one or more aspects of an engineering project. Such information may comprise any suitable form, for example drawings, text, measurements, inspection methods, tests to be performed, formatting, reporting guidelines, other data and so on. In some embodiments there is provided an interface equipment database to store information in relation to one or more tools which may be required for testing or assessment in relation to an engineering project.

In some embodiments, the interface is definable, for example so that the form or interface may be built to the client specification. Thus for example it may provide a customised form that integrates hardware, networks, etc.

The computational module may be of any suitable type provided that it can adequately perform the functions required according to the present invention. The computational module may perform other functions, such as setting authorities for sign off and other processes needed.

The first communication module may communicate test results in any suitable form. Thus, it may on a display screen on a computer, in a written document, in a field in a database, one or more units of data transmitted and so on. In some embodiments there is further provided a second communication module to assist communication of information from an information source. The information may be communicated in any suitable way and may for example be communicated into one or more databases in the database module. Information may be of any suitable type. For example, information sources may comprise one or more of:

• Engineering Data, such as data supplied by an engineering phase that describe the equipment, identify it, and associate it with the project.

• Functionality Requirements, such as how the equipment should be set up and operate for the particular installation and application.

• Performance Criteria, for example defining how the equipment is expected to perform under certain conditions, how it interacts with a control or safety system, analysis associated with signal quality and how the equipment is expected to perform in terms of accuracy, stability, etc.

• Ex Specifications, for example relating to specific hazardous area data and information that is specified during project engineering phase, and relate to equipment that has been designed to be used in a potentially hazardous (or explosive) atmosphere.

• Standards - for example national standards, industry standards, codes of practice and specific installation or operation standards for the equipment.

• Specifications, for example specifications that have evolved from industry experience, lessons learned and engineering.

• Guidelines, for example Practices and methods that have been generated using a combination of standards and specifications.

• Client Specifications, for example the specific requirements as set out by the client for installation, configuration, setup, etc. and the Client Requirements that have been developed by the client for acceptable handover in the form of inspection sheets and lists.

• Manufacturers Information, for example information provided by the manufacturer that may be specific to the equipment and describes installation, configuration, operation and commissioning instructions and information.

• Site Safety Information, for example Safety Regulations which are the industry and national safety standards and Site Safety Requirements which are specific safety considerations and management of safety on site for the project (including permit and hazard analysis systems, etc.)

The communication modules may communicate by any suitable means. For example, HART, Foundation Fieldbus, Profibus. Zigbee, WiFi. Bluetooth, ASI Bus, F S Bus, IEEE 488 or any other suitable and / or proprietary type or variations or combinations of such communications protocols.

In some embodiments, the computational module may communicate with one or more items of test equipment in relation to one or more tests to be perfomned, for example on one or more items Of engineering equipment. Thus for example, in some embodiments, the computational module facilitates a communication which causes an item of test equipment to test an item of engineering equipment and report the results of the test. In some embodiments at least one of the test results may cause one or more additions in one of the databases. Thus for example, a more up to date record of the status of an item of equipment may be created, or a diagram may be marked up with changes, and so on. In some embodiments adapted for completions processes, the test results are used to generate a set of non compliances which may for example be useful for following up on items to be redressed in terms of quality.

In another aspect of the invention there is provided an engineering quality system comprising a computational module and a database comprising at least one interactive element wherein the at least one interactive element corresponds to an item of engineering equipment and the interactive element is operable to cause the computational module to undertake one or more operations in relation to the engineering equipment selected from but not limited to: design a quality test, conduct a quality test, record information relating to a result of a quality test and / or update a database comprising information relating to the engineering equipment. In some embodiments, the system comprises an interface to enable easy operation of the at least one interactive element. In some embodiments, the interface comprises a form. However, the interactive element may take any suitable form. In some embodiments, interactivity is created by a hyperlink or another selectable item which, when clicked actions one or more of the operations.

By implementing a system as described in this invention, the aim is to achieve a very high level of inspection quality by providing correct, relevant information access, automate and supervise inspection and verification processes by hardware and software technology integration, implement an electronic version of the inspection and verification document and achieve data as a result that can be put to highly valuable uses to further gain assurance that a plant is truly ready for start-up. Real time tracking and access to data is realized as a result of performing these tasks using such a system.

Much of the requirement for the invention comes from observing the typical unacceptable methods and behaviours in the current completions workforce and the challenge that projects face by reliance on the inspection workforce to achieve the quality result the client requires. Often the inspection activities are poorly supported in terms of information and training and the project relying on a completed record to prove compliance is insufficient. In addition to this, the transient nature of the workforce often attracts a level of carelessness and lack of passion about achieving a high level of compliance and quality, as the workforce is brought in to perform the work late in the project and then usually relieved before actual start-up and plant operation at full capacity. This in addition to the fact that with the large amount of work and abundance of projects and work at present in various countries around the world, it is becoming increasingly difficult for the construction contractor, completions contractor or end client to source good people to perform the inspection work that verifies their plant assets. While several methods are implemented to try to obtain this high level result, very rarely is it achieved and there seems to be no single solution in gaining certainty in the inspection and verification process. Challenges with the current industry practices are that if more detailed inspection forms are implemented the result seems to be a confused and careless inspection workforce. Also if the inspection criteria are simplified, the result is a simplified inspection and inspection points are overlooked. Heavy training and education of inspectors is difficult due to the transient nature of the workforce, and requires close monitoring and auditing to ensure the right results. Inspectors are rarely engineers and therefore often do not understand the consequences of an installation that is not to specification The system of the invention incorporates, integrates and communicates with the complete process, from low level hardware communications to everyday computing applications. In addition to performing inspections and entering inspection activities into a computer based inspection tool (which could include a regular PC), the system of the invention does so but also communicates with devices and test equipment, integrates clients inspection criteria Into the process and manages results and data to provide a new layer of deliverables and efficiency.

According to the present invention, the overall inspection effort is provided for by one 'tool' including connectivity to electronic test equipment and plant components. Integration to this level justifies the dedicated use of the technology and the system to perform the work, further enhancing the possible implementation of the system by encouraging extended integration to other existing processes and consistent use for many tasks during the project life-cycle. By performing a range of activities using the invention, further integration of information and data with the project can be realised. None of the available prior art systems involve an integration that specifically provides a dedicated, overall solution for conducting completions work, where it is realised this is lacking in today's level of quality assurance requirements.

In one embodiment, the invention integrates field equipment and project information into an electronic Inspection form, which is presented on a computing device to conduct inspection and verification activities. The computing device may be of any suitable type, including a computer, a handheld computer, a mobile communications device such as a phone, and so on. The device optionally has connectivity to a wireless system which enables information transfer from and to the field to relevant databases as required for example via a purpose built system and to manage and work in new ways with the collected data.

Using field equipment that can communicate with instrumentation and electrical devices under inspection, the device data is collected and utilised on the live electronic interface as well as back-populating completions databases with information for future use and population of upcoming forms. In some embodiments one or more items of certified field test equipment may also have connectivity to the field inspection computing device. In such embodiments, control of the equipment may be initiated from the interface to perform tests, and results are displayed directly onto the electronic forms.

In some embodiments, the system includes the management of field device configuration and verification information to enable preparatory work to be conducted in collecting relevant certification and information for upcoming inspections and preparation of handover dossiers, tracking and enable reporting on device type and setup information and to enable engineering review of work being conducted.

In some embodiments, the system allows ah interface or forms to be used that are "smart" and are accompanied with tips and guidelines and allows access to dynamic information that may be required to perform the work. Using an electronic interface allows the system to be built to the specific client requirements to provide guidance and result in comprehensive inspections. Using allied technology, the system can be further utilised at the clients request to unlock new processes and means of performing the work, for example barcode reading or RFID, GPS technology, instant messaging (communications between the field and engineering, supervisors or other technicians), safety and site information broadcast, etc.

Throughout this specification (including any claims which follow), unless the context , requires otherwise, the word 'comprise', and variations such as 'comprises' and 'comprising', will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps.

Brief description of the drawings:

Figures 1a and 1b depict an overview process flow of an example completions process

Figure 2a and 2b depicts a process flow for an overview of one example embodiment of the invention

Figure 3 depicts details of an Interface Equipment integration example.

Figure 4a depicts a process workflow overview - Page 1

Figure 4b depicts a process workflow overview - Page 2

Figure 4c depicts a process workflow overview - Page 3

Figure 4d depicts a process workflow overview - Page 4

Figure 4e depicts a process workflow overview - Page 5

Figure 5a depicts a process flow of a Safety Analysis Integration Example - Page 1

Figure 5b depicts a process flow of a Safety Analysis Integration Example - Page 2

Figure 6 depicts a process flow of a Conventional Equipment Integration Example - Valve Timing

Figure 7 depicts a process flow of an Equipment Management Integration Example

Figure 8a depicts a process flow of an Instrument Function Check Example - Temperature Transmitter - Page 1

Figure 8b depicts a process flow of an Instrument Function Check Example - Temperature Transmitter- Page 2

Figure 8c depicts a process fow of an Instrument Function Check Example - Temperature Transmitter- Page 3

Figure 8d depicts a process flow of an Instrument Function Check Example - Temperature Transmitter- Page 4

Figure 8e depicts a process flow of an Instrument Function Check Example - Temperature Transmitter- Page 5

Figure 8f depicts a process flow of an Instrument Function Check Example - Temperature Transmitter- Page 6

Detailed description of exemplary embodiments:

It is convenient to describe the invention herein in relation to particularly preferred embodiments. However, the invention is applicable to a wide range of situations and it is to be appreciated that other constructions and arrangements are also considered as falling within the scope of the invention. Various modifications, alterations, variations and or additions to the construction and arrangements described herein are also considered as falling within the ambit and scope of the present invention. Figure 1a is a simplified generalisation of a standard completions system according to the invention. It should be appreciated that there are many variations to its implementation.

It can be seen that the Inspection 21 , and in particular Inspection Sheet 22 is at the centre of the system representation. Essentially the drawing represents the Equipment Item 29 (a device such as an instrument or other piece of plant equipment) under Inspection 21 with relation to Information 10. The various items shown in the group Equipment Item 29 show examples of the inspectable components that could be associated with a piece of equipment. To inspect the Equipment Item 29, Information 10 is referred to, which generally includes information sources consisting of:

• Engineering Data 11 - the data supplied by the project engineering phase that describe the equipment, identify it, and associate it with the project.

• Functionality Requirements 12 - how the equipment should be set up and operate for the particular installation and application.

• Performance Criteria 13 - defining how the equipment is expected to perform under certain conditions, how it interacts with a control or safety system, analysis associated with signal quality and how the equipment is expected to perform in terms of accuracy, stability, etc.

• Ex Specifications 14 - relating to specific hazardous area data and information that is specified during project engineering phase, and relate to equipment that has been designed to be used in a potentially hazardous (explosive) atmosphere.

• Standards 15 - national standards, industry standards, specific installation or operation standards for the equipment.

• Specifications 16 - Specifications that have evolved from industry experience, lessons learned and engineering.

• Guidelines 17 - Practices and methods that have been generated using a combination of standards and specifications.

• Client Specifications 18 - the specific requirements as set out by the client for installation, configuration/ setup, etc. and the Client Requirements 3 that have been developed by the client for acceptable handover in the form of inspection sheets and lists.

• Manufacturers Information 19 - information provided by the manufacturer that may be specific to the equipment and describes installation, configuration, operation and commissioning instructions and information.

• Site Safety Information 20 - include Safety Regulations 4 which are the industry and national safety standards and Site Safety Requirements 5 which are specific safety considerations and management of safety on site for the project (including permit and hazard analysis systems, etc.)

The information that is used to perform the inspection is derived from these relevant sources, but in particular the engineering effort that is engaged during the project design phase. The information sources shown in this example and represented simply as Project & Engineering Specifications, Documents, Drawings and Standards 8 stands for the project specific information resulting from the front end engineering and design as well as the information derived from all external sources such as standards and manufacturers, provided across a suite of documents and drawings for the project. Project & Engineering Specifications, Documents, Drawings and Standards 8 is shown connected to the Engineering Database 7. which represents the fact that the engineering effort placed during project design phase has ultimately supplied the information and controls the relative associations and in general manage the engineering data and information provided for the project as a whole. A change in engineering data at any point in the project can affect several Project & Engineering Specifications, Documents, Drawings and Standards 8.

Also being shown on Figure 1a is the connection of the Engineering Database 7 to the Completions Database 41. This connection represents data flow that is required to setup the Completions Database 41 and holds basic information on all the plant equipment, the association of each piece of equipment with cables, connections, loops, junction boxes, etc. and allocations in terms of plant system, subsystem and associations with drawing and document numbers. It is based on this connection of data that the Completions Database 41 can define its hierarchies and groups and allocates particular inspection requirements to equipment items such as the Equipment Item 29.

While the Engineering Database 7 is providing all the engineering information on the equipment in the project, the Client Requirements 3 in the drawings represents the client specification in terms of how the equipment should be inspected, what tests and results are necessary and how the form should be formatted and how it should read. The client defines a set of test and inspection records which cover all the inspection and verification requirements for the project, and these are supplied to the Completions Database 41. The Completions Database 41 can then provide these inspection forms for all the inspectable equipment items and populate certain engineering information to the individual forms, such as tag, description, system and drawing numbers. These forms are represented as Inspection Sheets 22 in Figure 1a and are stored in the Completions Database 41 until required by the project.

At the appropriate phase in the project when the equipment becomes ready for inspection, the Inspection Sheet 22 is deployed for the field Inspection 10 to the appropriate discipline inspector.

The Interface Equipment 25 components shown in Figure 1 represent the tools that may be required to perform particular inspection / verification activities. The Communications 26 interface would be required to connect to and communicate with certain equipment. This could be but would not be limited to, HART, Foundation Fieldbus, Profibus, Wireless, etc. or other proprietary type communications protocols for example. A functional test or calibration check of the Equipment Item 29 would most usually require communication hardware, as most modern equipment use software configurable settings rather than hardware settings such as DIP switches or jumpers as used in the past to configure the equipment. The Test & Calibration 27 equipment represents any simulation, measurement or test equipment that is used to perform functional testing on the Equipment Item 29 for example, pressure source and measurement equipment or temperature simulation equipment. The Analysis 28 equipment are devices that are used to check other performance properties of the equipment installation, for example network communications analysis, scope-meter readings of transducer operation, current and voltage load readings, etc. All the Interface Equipment 25 types and models used in the current method are read and used by the inspection technician and results written into the Inspection Form 22 with comparison to the Information 10 that is provided.

The inspection or verification may be performed as a manual exercise, where simply observations and decisions on compliance are comparisons between the data observed during the inspection and information provided or available at the time of inspection. The Inspection Form 22 is simply a prompt and a record to show that the steps required for a particular inspection or verification were performed and any results that were obtained. The components of the Equipment Item 29 items 33 through to 40 represent the corresponding inspectable aspects of the Equipment Item 29 that are being assessed against Information 10 components.

Resulting from an Inspection 21. are three representations:

• Recorded Inspection & Verification Results 23 represents the completed Inspection Sheet 22 which shows the information and data collected during the inspection and completed checks.

• Marked up Drawings & Documents 24 represents any documents used during the Inspection 21 process that required alteration or comments.

• Non Compliances 42 represents a standard vehicle for reporting on and recording any items which failed the inspection process, commonly referred to as punch-lists or outstanding work. All Non Compliances 42 that are a result from an inspection activity are managed by the Completions Database 4 if they cannot be rectified at the time of inspection. These non conformances are usually submitted using a paper based system, recording a description and date and are assigned a classification which relates to their criticality in affecting successful handover or start-up of the Equipment Item 29.

Referring now to Figure 1b where the separate elements are more broadly shown, the Approval Process 16 represents the return of forms to the Completions Database 9. This process is a defined authorisation method where the Inspection Sheet 15 is usually signed off by the inspector, the discipline supervisor and then perhaps a client representative or administrator in some cases. The successful completion of an Inspection Sheet 15 represents a compliant piece of plant equipment for the particular inspection moment and captures any associations of punch-list entries where applicable.

Also shown on Figure 1b connected to the Completions Database 9 are various Deliverables 1 examples that a usual completions management system provides. The application of the completions system is to report Progress 3 of the equipment, systems and ultimately the whole project. The Completions Handover Dossier 4 represents the successful completion of the plant and is being compiled directly using the completions management system by filing and representing completed inspection and verification tasks and demonstrating the completion of all of those tasks. The Ex Dossier 5 shows that the Completions Database 9 has an input to the successful compilation of this dossier by providing completed Ex related Inspection Sheets 15 that will become an important element in demonstrating that the plant complies with Ex requirements. The Punchlist 6 are the non-compliances that are recorded as both a result of the Inspection 14 process and entered generally throughout the project.

Figure 1 b demonstrates the fact the Observations 13 are performed to provide Inspection Sheet 15 results between Information 12 and the Equipment Item 21. Also, Observations 19 are performed to access and control Interface Equipment 18 to provide Inspection Sheet 15 results between Information 12 and the Equipment Item 21. A Document Control Process 11 is used to add to the Marked up drawings and documents 2 deliverable. Finally, also shown on Figure 1 b is the ITR Handling Process 22 which represents the process of providing paper based Inspection Sheet 15 for the Inspection 14 and the Punchlist entry Process 23 to provide non-compliance recording to the Completions Database 9.

EXAMPLE TICS IMPLEMENTATION

During, the examples given, the engineering quality system discussed is referred to TICS, standing for Technically Integrated Completions System, which relates to the system of the invention.

The process is made available to the end client by means of customisation, where the clients own check-sheet set and specific requirements are implemented into their completions system early in the project development stages as is currently with the completions management system process. This enables the client specification to become the basis of the inspection or verification activities, and defines the operability of the^'electronic smart forms that will be used in the system. Working with the client, the appropriate guidelines, document links, equipment integration requirements, communication requirements and data manipulation advantages are defined to implement as a superior system. The TICS system is providing the integration and offers technology based solutions, but the client completely specifies the inspection criteria and methods to their specific project requirements and determines the extent to which the invention is utilised.

THE TICS INTERFACE / FORM

Referring now to Figure 2a of the drawings, the TICS interface 30 (which may for example be an online form but could also be any other suitable type) comprises of the Electronic Inspection Sheet 31 which contains the comparator blocks 32, 33, 34, 35, 36 and 37. This represents the integration of Information 11 components and Interface Equipment 38 components to the TICS interface 30 where comparison can be made directly from the interface itself. The drawings demonstrates the process as being electronic where the data and information is being brought into the interface rather than the components being separate items referenced in a manual process when completing the inspection or verification activity. The TICS interface Technically Integrates Completions System components by making all Information 11 available electronically, providing electronic transfer of results and data collected and making Interface Equipment 38 controllable and readable from the Electronic Inspection Sheet 31. In achieving this, it is possible to improve the depth and accuracy of Information 11 used during the inspection but also unlock new potential in terms of automation and electronic assistance while conducting the work. The comparator blocks 32, 33, 34, 35, 36 and 37 with associated Results 24, 25, 26, 27, 28 and 29 demonstrate the new possibilities of providing a system where various sources of data provided on the Equipment Item 42 can be compared to actual data sources from within the Equipment Item 42 and Interface Equipment 38 and provide new deliverables by using this data and storing it. Also, whereas the prior art systems did not provide any further use for the information collected (being hand written on paper forms), the present invention provides new ways to use this data and provide methods for creating interactive "smart" interfaces / forms. INFORMATION

Figure 2a shows the Completions Database 2 providing the Electronic Inspection Sheet for use, but via the TICS Platform 22. This represents the fact that the TICS system provides a better mechanism to conduct the work and capture information by working with the interface in new ways.

Information 11 is acquired / raised from the Electronic Inspection Sheet 31 using hyperlinks or other selectable means built into the form. The primary document number information is built into the interface as a known parameter, as this has been defined and provided by the Completions Database 2 using data provided initially by the Engineering Database 8 early in the existing implementation process. This information is currently printed onto the paper based form, whereas the TICS process utilises the fact that a field PC (be it a PDA, tablet, laptop or otherwise) is being used to complete the interface and therefore a simple link to the required documentation is a basic implementation that provides almost instant electronic access to the primary documents required to complete the inspection. This automated access to documentation means that there is now no longer the requirement to source up-to-date documents and compile them in preparation for an inspection or verification activity. Also, by accessing a central repository, the documentation being accessed is controlled and up-to-date, ensuring an old copy is not mistakenly used to perform the inspection. The Information 11 link through the TICS Platform 22 can be achievable in the field by use of wireless, telephone network technology for example (or any other communication technologies as appropriate for the particular site or availability).

For the purpose of simplicity, Figure 2a shows the connection of the Engineering Database 8 to the information components provided as Information 11. In reality, the flow of information to the interface is via the Completions Database 2 for basic engineering data that is normally used to populate the inspection forms. Whereas in the case of more specific engineering data, as shown in Figure 2a as Engineering Data 12, Functionality Requirements 13, Performance Criteria 14 and Ex Specifications 15, the information is actually provided by the Engineering Database 8 through to the TICS Platform 22 (this will actually be via the TICS Database 23 component but shown as direct links for simplicity) and thus allows for automated and / or integrated comparison of Engineering 12 information with actual device information represented by Configuration Parameters & Settings 43 for example. To demonstrate the data origin and ultimate controller of data and drawings, the Engineering Database 8 has been shown as the link to this information in the drawing. The actual implementation could be that the Completions Database 2 is actually used to link the information across to the TICS system.

The current process involves only retrieval, assembling and referring to general documentation that is expected to be critical in performing the inspection or verification. An advantage of the TICS process is that enabling electronic access to all project documentation means such that the inspector has access to all additional information requirements that may be realised during the activity. Currently these additional information requirements mean the inspector must leave the field and return to offices, drawing rooms or their supervisor to request additional material to ensure the inspected item complies with the inspection requirements. By assembling information external to the project information, such as manufacturer's manuals, industry information, client specifications, etc. and electronically filing this information, the inspector has access to virtually all the information that may be required, making TICS a very powerful information integration tool for use in the field. The result of making a comprehensive and instant portal to information sources for field inspections available, results in efficient, quality inspection activities. Whereas there might be tendencies to not "go the extra mile" in sourcing and confirming the inspectable item against information, the TICS system encourages detailed, intelligent inspection activities.

EQUIPMENT DATA COLLECTION

A useful aspect of the TICS implementation is the early gathering of particular information on plant items such as EX information, device make, device model and device serial number information.

As an example for Ex information, the current system performs these particular inspections quite late in the project but prior to pre-commissioning, and involves a lot of effort to verify that electrical equipment complies with the engineered design of the plant with respect to hazardous area use. The implementation of an electronic data system such as TICS provides all recorded information in an electronic format, which unlocks enormous potential in terms of assembling dossiers, such as the large Ex dossier requirement on oil and gas projects for example. While equipment is inspected using the TICS process at early project stages, the collection of Ex information from electrical equipment means that the project has early access to specific information. This allows for desk based verification activities to be performed by engineers that have access to this data in an electronic manageable format. It also allows for the collection of external information progressively through the project Instead of at the back end, for example by collecting and assembling manufacturer ex certification documents which are required for an Ex dossier and must be available during an Ex inspection. Instead of sourcing this sort of information just prior to or during inspections, this work can be progressively engaged and be ready for the ex inspection phase. The TICS process of recording and collecting data electronically means that that all data can be used instead of its only use being as a record as is with the current system.

In the same respect any data or information collected on electronic forms becomes usable instead of a static record. This data becomes available for upcoming inspection activities and for compiling and using within the project in new ways. Integral to this advantage is the collection of electronic configurations, settings and device information which is not currently performed or the advantages of doing so realised.

INTERFACE EQUIPMENT - COMMUNICATIONS

Still referring to Figure 2a of the drawings, direct communications to the Equipment Item 42 is achieved using the Communications 39 component of the Interface Equipment 38 group in the TICS process. This connectivity into the TICS interface 30 is represented in Figure 2a of the drawings by a direct link, as the integration of device information and data is an electronic process as compared to being a manual process in Figure 1b where details are observed on a separate device and certain information transferred to the form. This integration of actual Configuration Parameters & Settings 43 may be achieved by means of the appropriate communications devices that are selected and proven during the development process and integrated into the TICS system forms. This could be but would not be limited to, HART, Foundation Fieldbus, Profibus, etc. type communications protocols. The Communications 39 equipment may be interfaced by the TICS interface 30 on a field PC (be it PDA, tablet PC, laptop or otherwise) by using hard-wired or Bluetooth or similar wireless technology. The current testing has proven HART technology on a Bluetooth wireless link successfully integrated to the field PC. The integration of a live Equipment Item 42 configuration and software settings to the TICS interface 30 is achieved by use of simple integration software, where the required parameters are accessed and displayed on the interface and commands sent from the interface to perform configuration and diagnostics tests as required. The integration of Configuration Parameters & Settings 43 into the TICS interface 30 means that one tool is being utilised for the inspection or verification activity, in terms of reading, recording data and configuration, and the advantages of doing so mean that the TICS interface 30 is automatically populating required information and able to present parameters and settings to compare against the integrated Engineering Data 12. This method is far superior to a manual effort, where in this system the interface itself is supervising the correct application and comparison of engineered data to the "as left" result in the field equipment. Where there are differences in the two data sets, the appropriate measures can be taken, whether it be changes made to the Equipment Item 42 in the interface of configuration adjustments or the Information 11 sources in the interface of document mark-ups and engineering data adjustments. During the consultation process with the client to determine inspection and verification requirements the depth of automatic comparison is determined with regard to equipment parameterisation and identified critical configuration settings requirements. The interface integration level can be modified to automatically seek and compare data from the Equipment Item 42 and the Engineering Data 12 by means of identifying common terminology used in Alarm Range and Trip Schedules and Datasheet documents from engineering and allocating against common communications protocol terminology as read and accessed by communications hardware / software. This electronic integration also provides a suite of benefits, such as the acquisition of the full parameter listing from the equipment for upload into the TICS Database 23. This acquisition of data can be utilised for a range of purposes, in particular to provide a database of device configuration and parameter data, which can be sorted, filtered and searched thus allowing engineering supervision, parameter searches (i.e. how many Device X Hardware Revision Y are there in the project) and eventually to compliment project handover deliverables in terms of actual equipment configuration information.

INTERFACE EQUIPMENT - TEST. CALIBRATION AND ANALYSIS

Also illustrated in Figure 2a is the integration of Interface Equipment 38 to access Functionality 44 and Performance 45 aspects of the Equipment Item 42. This connectivity is realised using Test and Calibration 40 equipment and Analysis 41 equipment that has also been specifically selected and implemented which allows for remote control and dynamic data flow to and from the TICS interface 30. The existing tests have utilised equipment that uses Serial RS232 and USB type connectivity solutions (for example). This equipment may be further controlled and interfaced using hard-wired or Bluetooth or similar technology to provide a wireless, hands free solution. The existing tests have utilised Bluetooth technology to provide the wireless interface between equipment and the field PC to control and read the equipment remotely. This means that not only is the one tool being utilised to control the test, calibration or verification procedure but also to read the real values. This data is displayed in the appropriate field on the Electronic Inspection Sheet 31 whereas previously this information was manually read by the technician and hand written into the paper based inspection sheet. The integration of Interface Equipment 38 allows for a simpler, streamlined and controllable procedure that records real values as experienced during testing. It also allows for an interface on the field PC that has defined test processes and requirements, meaning that the interface itself can set up the test equipment to prepare for test procedures and define the conditions. Additionally, results achieved can be calculated into percentage accuracies, graphs, converted to alternative units, or in fact manipulated in almost any way to result in various pass / fail criteria, record statistics, or otherwise. By doing so the TICS interface 30 is now assisting (and in fact supervising to a degree) in ascertaining the compliance of test results, and can alert the user to specific non-compliances that are identified during the test process. Previous methods would involve manually setting and driving the test equipment and writing results as read from that equipment onto the paper based record, as well as manually recording all the information on the equipment used and its validity information.

The specific Analysis 41 component represents higher level analysis of the installation that generally is not allowed for in current processes. As an example, this aspect can be utilised to capture network performance details, transducer or equipment component performance or operation details, electrical parameters, vibration readings, etc. where currently the same approach is used in taking readings from external test equipment and recording on forms, or simply recording the fact that results were satisfactory against some pre-defined specification. The integration of such measurements is only limited by the availability of integrate-able tools and the clients overall requirements.

The Interface Equipment 38 integration into the TICS interface 30 involves defining, setting up and proving standardised equipment types for use with the TICS system. At present these integration options are being explored and have been proven at various levels, but in essence the process involves selection of equipment that allows the capability of dynamically reading parameters and writing commands perform testing, communicate and analyse from within the TICS interface 30. The current tests have utilised a Fluke 725 multifunction calibrator and Visual Basic code for integration (both read and write) into Microsoft Excel work-sheets to demonstrate the inspection form. The integration involves building special add-ons and configuration that allow read / write capability to a virtual communications port that is being used for Bluetooth connectivity with the Bluetooth enabled equipment. A preferred application for the eventual forms may be a Microsoft application document or an Adobe Livecycles form or similar. In the case of Communications 39 this may be achieved by building on existing software that is designed for equipment communications using manufacturer device libraries, but in addition it may allow for parameter read / write access through the TICS system forms. To achieve the desired result there are options to develop new applications or software, or have existing software adjusted to suit.

Additionally, the initial consultations with the client may involve determination of testing requirements, which in turn define the equipment requirements for the TICS process on the particular project. These determinations are made in early project phases and are based on information provided by engineering, for example instrument or equipment ranges, types, communication protocols being used, etc. As an example, for instrumentation calibration and function testing the project Range, Alarm and Trip schedule or Instalment Index would be referenced to determine the pressure simulation range requirements for the particular project as a whole and the equipment assembled to satisfy these complete requirements. In effect, although the TICS process standardises on equipment makes and models that achieve the integrated result, the specific project requirements further define the equipment capabilities to suit.

INTERFACE EQUIPMENT MORE DETAILED DESCRIPTION Referring now to Figure 3 of the drawings, a demonstration of interface equipment implementation is shown, with the concept specifics of the invention, equipment integration aspect. This drawing has been shown with the Equipment Item 27 as a HART instrument, for demonstration purposes whereas the concept is not limited to this one particular type of plant equipment type or communications protocol.

As a representation, the main components of a modern day HART instrument - the Equipment Item 27 under demonstration- have been shown as Transducer 30 which measures the analogue process parameter (i.e. temperature, pressure, flow, etc.) and which is converted from an Analogue to Digital 33 signal and passed through to the device Processor 34. Accessing Configuration Parameters & Settings 28 and Memory 31 (as a simple representation) the Processor 34 can provide a proportional or scaled Output 29 signal via a Digital to Analogue 32 conversion process, which in this case is a scaled DC Current 25 signal. The Interface Equipment 17 item, Multifunction Calibrator 22 has accurate inbuilt current measurement electronics that may measure the true DC current readings. As shown in Figure 3 the Multifunction Calibrator 22 is also being utilised to produce the Process Simulation 24 signal to perform the simulation (e.g. temperature, pressure or otherwise). The Multifunction Calibrator 22 is a device that has been certified as correct and approved for use to test equipment in this way, as part of a normal field verification or calibration activity. In this example however, the Multifunction Calibrator 22 has connectivity options that allow the unit to be controlled and read remotely. The connection represented as item 17 through to the RS232 - Bluetooth 21 converter has been achieved using an RS232 standard protocol and application of existing technology to convert the serial signal to a standard Bluetooth 20, wireless connection. The RS232 - Bluetooth 21 device is paired wirelessly to the Serial Interface Software 15 using industry standard means, where a Virtual Com Port 16 is implemented to replicate the functionality of a standard serial communications port and allow software applications to communicate to the Multifunction Calibrator 22 as if it was hard-wired using an RS232 physical layer. In order to use the data read by the Multifunction Calibrator 22 (in this case to read the digital representation of the analogue DC Current 25 measurement) from within the TICS interface 6 an application possibly in the form of a Visual Basic program (or similar) is required to poll the communications port for updated readings. This function is simply represented as the Serial Interface Software 15, which is ultimately controlled from the Equipment Data / Commands 11 component of the TICS interface 6 to send read requests and command. In this way, the reading from the accurate calibration device (Multifunction Calibrator 22) is presented to the user, directly into the electronic form.

Using the same mechanism as was used to access the Current Meter 23 parameter of the Multifunction Calibrator 22, but as a data send command instead of a read command, the Multifunction Calibrator 22 receives instructions from the TICS interface 6 to produce Simulation 26 values required during the test. Additionally, the data commands are used to initially set up the Multifunction Calibrator 22 to the correct Process Simulation 24 requirements. This activity is expected to be implemented as an automated process, where the system knows the test requirements and therefore can place the Multifunction Calibrator 22 into the correct mode and calculate the desired values of simulation for each step in the verification process. In other words where the verification requires testing at 25% intervals from 0% through to 100%, the system automatically calculates these intervals and places the. Multifunction Calibrator 22 to the appropriate values during the test procedure.

This integrated method enables the results recorded in the TICS interface 6 to be real and accurate, and simplifies the activity as the user does not have to switch between calibration activities and recording information on a form. Additionally, the communications link between the Multifunction Calibrator 22 and the TICS interface 6 automatically identifies the Interface Equipment 17 by serial number and records the details within the record instead of being done manually. The process also ensures the appropriate equipment is utilised. Further refinement of the above process can realise even further benefits, by analysing ihe information sent to and from the Multifunction Calibrator 22 and making determinations on the results. At essentially a basic level, using this method the system has the advantage of proofing the results achieved against the expected functionality requirements that have been provided by the engineering effort, represented as Engineering Data 4 in the drawing, thus assisting to eliminate human error and mistakes. In essence the interface itself is supervising the results achieved and identifying flaws in either the device itself or the engineering data, therefore automatically capturing inconsistencies on the spot.

The Equipment Item 27 communications link through to the TICS interface 6 is achieved in the (HART instrument) demonstration in Figure 3 using HART Modem 19 equipment. This currently available equipment item uses industry standard means of interpreting the Bell 202 11 signal that is superimposed on the DC Current 25 signal. This signal is used to send and receive commands to the Equipment Item 27 to configure, calibrate and read parameters and settings from the equipment. The most likely setup for the Interface Equipment 17 Is one in which the individual hardware components are integrated into one "test kit" (i.e. in one box or case). Another preferred embodiment is where the equipment is requested to be manufactured to provide an integrated solution, by aligning with a current manufacturer of test equipment solutions. For current testing the individual components may be compiled into a "test kit" form, using an equipment case and internal wiring, etc. such that there are only two wires required to connect to the instrument under test which provided supply power and output measurements and communication. In a similar way to the Multifunction Calibrator 22 connection to the Serial Interface Software 15, the use of Virtual Com Port 14 and HART Interface Software 13 is implemented to carry the read and write commands through to the TICS interface 6. On the interface itself, parameters can be read and commands sent as represented by the component Device Data / Commands 7.

Also shown in Figure 3 is the component Full Configuration 8 and the comparator block item 9 which is used to demonstrate that the complete software configuration of the Equipment Item 27 is acquired and transferred to the TICS Database 3 and comparable to the Engineering Data 4 which is accessible also through the TICS Database 3. This connectivity from the TICS interface 6 has been suggested as being via a Wireless Link 5 between the field PC standard Wireless Adapter 10 and a Wireless LAN 2. The Wireless LAN 2- a Local Area Network in field - is achieved by using industry standard technology that has been sourced to allow a field based solution for the particular project site requirements. This LA could also be implemented using the digital phone network (i.e. 3G) system.

By accessing the Equipment Item 27 Configuration Parameters & Settings 28 and Processor 34 parameters from within the TICS interface 6, a very large suite of advantages and automated processes become available that were previously unavailable in an un-integrated system and the device configurations as a direct result of simply communicating with an Equipment Item 27 under inspection are acquired.

BACK POPULATING OF I FORMATION An often poorly conducted process during plant completions and commissioning is the "as building" and document "mark-ups" that are required to correct engineering drawings and documents to match what has actually been implemented in the plant build and configuration changes to control systems and devices. The verification, correction or adjustments to these documents is crucial in providing an accurate documentation reference for further start-up activities and eventual handover of the plant to the end client. Figure 2b shows the electronic link between the TICS interface 22 and the general Information 19 component of the process. In addition to accessing documentation / drawings from the field PC tool, the ability now exists to mark up documents and adjust data using the field PC and submitting for review and approval. The advantage that is realised is that the project has almost immediate access to these modifications to drawings, documents and data, and the mark-ups and corrections are virtually made instantly available for future inspections, engineering action or when referenced by other parties on the project. As part of the inspection or verification activity the TICS interface may present the applicable primary drawings for attention and only by accepting acknowledgment of compliance of this information is the inspector able to submit the results for approval. At present, the manual paper based system relies on a large manual effort to ensure that all mark-ups are captured let alone available to the project and any additional upcoming inspections. Quite often the situation evolves into there being several copies of the same document or drawing in several locations, even off-site, and this leads to a whole range of problems if not managed correctly. By submitting marked up documents electronically, this single process can be greatly improved and automated to a large degree to electronically govern access and filing of document copies and adjustments. Engineering efforts can be implemented which monitor, review and eventually back-draft the modifications progressively throughout the project and address any issues as they are identified and reported on.

Also, quite often a change that is made to a device, document, drawing or control system affects other documents. A typical example of this is where a change is implemented to a measurement range on an instrument during the project commissioning phase. The measurement range alteration may be altered in the device and the control system, then this alteration may need to be updated on the control system narrative documents, the instrument index document, the range/alarm/trip schedule document, the cause and effect document, the process and instrument diagrams, the instrument datasheets and also possibly affect the calibration record for the instrument and any configuration saves that were previously made. Where such a change is made, the process of manually ensuring these documents are all updated to reflect the new information is enormous, without mentioning any existing hard-copies that may be in existence and are being referred to for use (uncontrolled copies). By enabling a central system to highlight all changes, it is possible to back-load data and make electronic connections to pre-defined associations such as which documents or drawings may be affected and require addressing. The concept extends back to the engineering methods initially used to design the plant, which rely on data associations to initially create drawings and documents, where a single change shall be implemented across all related documents and drawings created. Unfortunately, these systems are rarely used during the construction and commissioning phases of the plant build, an even if they were, there needs to be a system of highlighting these changes and presenting to the engineering application that a change requires implementation for population of all associated documentation and drawings. Where front end engineering provides the means of spreading the same information across several documents, the same automated human-error-free approach should be implemented for the back end of the project. By working from the "ground up" so to speak, TICS aims to provide a mechanism to allow this same level of fluency during the back end of the project cycle also.

ADDITIONAL DELIVERABLES AND ACHIEVEMENTS

As part of the supervision requirement of inspection and verification activities, it is very common to reject forms that are incomplete or incorrectly filled out. By using a system according to the current invention, this problem is removed, as the system itself is performing the supervisory task of ensuring the job is complete before being able to submit the results. This point alone may save time by no longer becoming part of the process.

By implementing a system such as that of the present invention, there are many add-on benefits that can be explored and realised that were not previously readily available using a conventional paper based system (Figure 2.2).

Of primary importance, the Notes and Field Information 6 that are made in the field can be used in the system instead of becoming a stagnant note on a paper based test / inspection sheet or communicated from the technician to engineering or supervision. Using the system of the invention, one can electronically attach notes or additional information that now becomes readily accessible by the project, whether it be directed to a particular department, alerted for review during the authorisation process of an inspection completion, directed to engineering personnel for assistance or review or perhaps made available to each and every future inspection activity by being attached to the tag. This benefit can be used very effectively to communicate information between separate inspectors and even disciplines in the project, where the next inspection activity that is occurring has access to a note or additional information recorded by the previous inspector or otherwise. The purpose can be safety, technical or query based for example, and can become a very powerful mechanism for addressing flaws, notable situations, equipment passwords or other special information that could otherwise be overlooked or lost. In some embodiments, the invention provides for level of communication and information flow. For example, built into a field inspection field PC may be the additional technological tools including a camera, for instance, that allow for comprehensive reporting for notes and punch-listing, or in fact even queries that are instantly delivered to the appropriate personnel (on or off site) before an inspection can be properly completed. By providing the electronic mechanism the system of the invention allows for a seamless connection between the field and appropriate personnel, which actually encourages queries and clarification and provides the immediate tools to do so effectively.

Figure 2b shows Notes and Field Information 6 as a deliverable from the TICS Database 21. While this information is very usable throughout the project, the additional end deliverable accessed is for Operations Handover 3 at the completion of the project, where the client and operators may also acquire any notes and information that have been made during the project completion / commissioning. The field notes can be realised as vital pieces of information that were recognised and identified and are otherwise lost once the project is completed. A "file" is essentially provided to hand over that contains information on that one tag that the client can access through a simple database system or networked folder access. The implementation of this concept of the invention can be as simple as a selection that provides access to a designated directory that is progressively being built upon and contains folders with particular information being assembled as a result of field inspections and prior preparatory activities such as assigning manufacturer manual, ex certificates, etc, A database solution may prove more advantageous, but the concept is the same - accessibility of information and providing a vehicle for collecting information during the project process.

Other examples also included in these additional deliverables shown as Operations Handover 3 are Configuration Results 4 which are actual "as-left" configuration records of the equipment that was part of the TICS process. Since TICS accesses and uses that information during the project, an offline copy of the details for each piece of equipment can be included in the equipment file. This information is an additional deliverable that is not currently available by the existing process, and enables data manipulation such as filtering and sorting during the project and as a handover deliverable to the client as a record of equipment configurations and settings, where future failed equipment can be set up exactly as per a documented configuration record.

Similarly, the Calibration Results 5 for calibration verification activities are in an electronic record format that can also be sorted or filtered by the project or end client and embedded in this advantage is the fact that last know calibration verification dates are discoverable. This information from a handover perspective can be utilised to incorporate into the client or operators maintenance management system. P

Performance Data 7 is another example, that involves providing a base-line data set to the client that represents the performance of digital networks, loads or valve signatures for example (any performance related data) that the end client can use to reference as a snap shot or "normal" condition that was observed during acceptance testing of the equipment during commissioning.

Management based deliverable examples shown in Figure 2b, Statistics 8, Supervision 9 and , Lessons Learned 10 are examples of TICS database potential that can be realised with respect to delivering new, additional information as a result of its implementation. By intelligently using the technology and manipulating data it is possible to allow for new information to result that was not previously easily accessible or automatic. By automating some form of analysis of the activities, it is possible to identify how long activities take, for example, for analysing and forecasting project schedule or to use on another project plan. It is possible to automatically report on not only how the inspection and verification process is performing, but identify who is performing what and how long it is taking (i.e. Supervision 9 and Statistics 8). Also embedded in this Is that lessons learned 10 information is being created through the process, because all information is now in an electronic format, thereby enabling automatic compilation of the data in a "lessons learned" fashion. For example, data used to make punchrlist entries can be evaluated to produce valuable lessons learned for the current and upcoming projects. In addition to this, lessons learned information that is identified during the project can be made available and communicated across the project, of course using photos and notes to assist.

PUNCHLISTING

Figure 1b shows the completions component Punchlist 6 which represents the management of non-compliances and outstanding work that has been identified during the project and as a result of inspection and verification activities. This is important in managing and recording information for rectification and handover agreements between project phases. As indicated in Figure 1b of the drawings, the Punchlist 6 component is managed by the Completions Database 9 and the data entered is accessible and able to be filtered in any way, for example by tag, system or subsystem. What lacks is consistency throughout the entries. The current process usually involves a noncompliance or outstanding work being identified and submitted on a punch list entry form, a handwritten entry by an inspector or other project person. The information on the entry form is entered into the Completions Database 9 by an administrator, perhaps after being approved by a discipline supervisor or manager. This information originally noted by the inspectors is often misunderstood or misinterpreted due the lack of technical background or information available. Due to the fact that the TICS process is using electronic forms, more regimented punch-list entries can be implemented by using drop down boxes and queries that define punch list items in standard ways. The result is punch list items are more standardised and can be used for reporting and end of project handover for future projects. The client can access the information and identify where to focus efforts for an upcoming project (or the remainder of the existing project) to reduce the non-compliances, etc. The current system also often results in vague items pooling at the completion of a project that have not been able to be solved simply due to the vagueness or inaccuracy of the entry that was processed. By consulting with the client and setting up standardised methods of identifying non-confomnances early in the project, the results and use of the punch-list can be improved by allowing defined selections against selected non-confomnances. For example an entry that is made due to "earthing and bonding" not being correct, may automatically present drop down lists or options that force the inspector to clarify exactly which of the pre-defined areas where this inspection point could be deemed not acceptable. This creates consistency and clarity in the punch listed entries, which enable the entries to be filtered and sorted properly. This benefit is realised also when compiling lessons learned information, to demonstrate where groups of issues are identified across a project and can therefore be addressed or compliment the lessons learned database for the company and upcoming projects.

Additionally it is common in the current environment for punch -listing to occur that is outside the scope of the client and project requirements due to certain opinions of individual inspectors and team members. By using the TICS processes, clear guidance can be implemented that helps identify real non-compliances, perhaps even requesting that the applicable reference in the documents be noted where the non-compliance is relative. As the inspector has instant access to the client specifications and other specifications, they are also more equipped to make good decisions on punch-listing requirements. Since the entries are submitted electronically, it is possible to gain instant approval / submission abilities so that the project sees the entry much faster than the existing system. The particular non-oonformances may be directed to different teams or personnel for review or rectification (i.e. construction teams).

INTERFACE EQUIPMENT MANAGEMENT

The Interface Equipment 25 shown in Figure 2b has a link to the TICS Database 21. This link represents the implementation of the TICS system controlling the management of equipment in terms of use, calibration details, make, model and serial number, etc. and prompts the project when certain equipment may be due for attention such as a calibration or verification requirement. The TICS system is also able to identify the exact equipment used to performed in inspection and verification activities, such that responsibility is assigned to users and also instant identification of equipment that was tested using particular equipment in situations where this may be of importance. One example may be an equipment item that was later identified to have an accuracy issue, and the data being instantly available as to what that equipment was used to test. To further clarify, this could relate to calibration gas bottles that were found to be contaminated or incorrect, and therefore one could easily search the data to determine what equipment was tested or calibrated using that particular product. This ability just does not exist currently using a paper-based system.

It is envisaged that the Interface Equipment 25 components are labelled by use of a barcode system or otherwise to uniquely identify each piece of equipment used on the project and thereby enable the TICS interface 22 to automatically populate the record of equipment use on the form. Additionally, the interface ensures the calibration date and validity of equipment use is correct. This way. unauthorised equipment is not able to be used and also the correct type that is required for the particular test type and range is supervised automatically thus removing human error or carelessness. It is also envisaged that kits would be supplied for the project where each inspector or technician had access to their own equipment, thus ensuring a consistent work-flow and built in responsibility when it comes to managing and caring for assets of this type. Also, the field PC and equipment would have been proved as a pair which far increases the reliability certainty.

EQUIPMENT MANAGEMENT INTEGRATION EXAMPLE

Referring to the drawings, in particular Figure 7, an example process of integrating the equipment management into TICS for a project is demonstrated. An Equipment Item 26 is acquired for use during the project and integrated into the TICS process. The Supervisor 9, Inspects Equipment 10 to begin the process. The Add Equipment Details to Database 1 1 activity represents applying all the relevant equipment details into the TICS Database 4, such as Make, Model, Serial Number, Range, etc. and also the Supplier 27 information. This information is entered once and allocated and identifiable by the TICS system, to automatically populate forms and for the equipment management process. The Supervisor 9 then Adds Calibration Validity Information to Database 12 which logs the calibration expiry information, also for recording on forms and to track the upcoming calibration requirements for all equipment, which can be implemented to automatically alert the Supervisor 9 and also disable the Equipment Item 26 from being used for inspections and verification in the TICS system if calibration requirements are not valid. The Supervisor 9 then Stores Calibration Certificate 13 and Stores Manual Λ ο the Network Storage 1 where that information can be accessed by all parties, especially the Inspector 17 as required. Since the TICS system is PC based, the Inspector 17 has almost instant access to these documents as required, particularly in the field. This method enables quality results and dramatically improves efficiency. It also means that the documents are managed in a controlled fashion, where revision changes and amendments are added.

The Supervisor 9 then uses a barcode label or other identification means (i.e. RFID) which has been provided by the TICS system once the equipment item is added, to use for identification purposes throughout the project. The Labelled Equipment Item 24 is now in Storage 23 and ready for use, after having scanned the barcode to identify to the TICS Database 4 of this action.

An Inspector 17 requiring the use of a Labelled Equipment Item 24 can check Equipment Availability 18 using the TICS Platform (field PC) to access the Equipment Status List 5 which represents the data accessed from the TICS Database 4 that shows the last scanned location and user. The Labelled Equipment Item 24 location may be shown and availability presented. The Inspector 17 then collects the Labelled Equipment Item 24 from its location and scans the barcode to effectively Check-out Equipment 19. This action of Barcode Scanned 8, updates the status in the TICS Database 4 to log the event that the particular inspector checked out a particular equipment item on a specific date and time. ^' The Equipment Status List 5 data would reflect this information and mark the Labelled Equipment Item 24 availability as "out" or "in use" for other inspectors information. This advantage is realised when trying to locate equipment required and determining when it might become available, and also to dramatically improve efficiency where a lot of time is currently wasted on site trying to locate equipment or determine who used it last This also incorporates a level of responsibility to the users, as they would be aware that they are logged as being the last user if the equipment is damaged and not reported for repair, etc.

The Inspector 17 may then Perform a Bump Test 20 using the certified workshop equipment (also integrated to the TIGS system) where the bump test results are stored and passed to the TICS Database 4 for additional tracking purposes. A bump test is a simple functional test that validates the accuracy against more accurate measurement equipment.

The Inspector 17 proceeds to use the equipment, which is an integrated process in itself, and tracked by the TICS process in the form of data records and data collection.

Where Equipment 25 items are in the consumable form, such as calibration gases or liquids, the Inspector 17 has the opportunity to identify when this Consumable expired 30 has occurred, using the TICS form, resulting in an Alert 16 to the Supervisor 9 to rectify this. Where the Supplier 27 information exists in the TICS Database 4, the supervisor can easily re-order the consumable or forward the information to the appropriate personnel. The Equipment Status List 5 reflects all activities, conditions and locations for the equipment management integrations of the TICS process.

The current systems used are normally a completely manual activity, and where there are no tracking methods or centralised documentation systems used. This implementation improves efficiency, responsibility, accuracy and traceability of the inspection and verification process even further.

WORKFLOW OVERVIEW EXAMPLE

Figure 4a through to Figure 4e detail an overview of how the workflow may be achieved using a system of the invention such as TICS. The charts show the integration and relationship between Engineering, CMS (Completions Management System), Network Storage, Supervisor, TICS platform (TICS system, database, network and PC's), Inspection activities and Device & Test Equipment (the actual device under inspection plus the equipment used to test the device in the field). It should be mentioned that the use of the word "List" throughout the examples represents only the fact that data from a data matrix is being accessed to identify listed data, and in reality the development of the TICS product may use database structures and data transfer to perform the functions discussed.

The primary path for the drawings mentioned are shown in Figure 4a as the Inspection 28 path, where the symbol Start Work 29 shows the initiation of the inspector's duties in performing an inspection and function check.

Figure 4a shows Engineering 1 column containing the Engineering Data 2 feeding through a CMS Integration Process where the agreed data fields and associations are provided as the CMS Engineering Data 4 package for CMS Database 9 integration. This currently existing process is used to provide the completions database with information required to set up the hierarchies and associations in order to structure and build the completions management system. Shown under the CMS 5 responsibility group, the Client Forms 6 which essentially define the exact requirements and format of the inspection forms are integrated also into the CMS Database 9 via the Interface Integration Process 7. These processes are only simply represented to show their relationship in preparation for providing the upcoming inspection criteria, information and allocations to the plant.

Shown on the drawing also, is the Equipment Management Process 25 which is identified early to represent the fact that the test and calibration equipment that is required to perform work is sourced and managed by site supervisors and engineers prior to work being conducted. Therefore the Supervisor 16 who is responsible for ensuring this first ensures the systems are in place to ensure the workforce has access to correctly suited, functional equipment to perform the work - Equipment Ready 17. When the Construction Completed 33 flag is received for a particular inspectable item, as represented as the Construction Complete list 1 , the Supervisor 16 can Determine Work 19 to be performed as per normal. By referencing the Punchlist Report 12 (managed by the CMS Database 9) the supervisor can ensure that there are no critical outstanding work issues currently identified and proceed to assign work to have the item inspected. To do so, they check ITR Ready 21 which is performed by examining a storage location where the ITR 3 has been stored due to the Generate ITR 8 process. If the ITR 13 does not exist, an ITR Required 14 notification is sent to the CMS Database 9 administrator (or in reality, the supervisor has access to generate the interface themselves, into the correct network storage repository). A confirmed ITR Ready 21 status may result in the ITR Status List 26 being updated to show the blank ITR is available. Once confirming this, the Supervisor 16 may Assign job to Inspector 23 which updates the Job List 27. The Inspector 28 uses this list to receive work and would then proceed to check the ITR Status List 26 to verify the existence of the ITR 13. The Inspector 28 would address their Supervisor 16 where the ITR was not ready, who may need to action 22 this and resolve prior to the inspector continuing with this particular assigned work task. The assigning of work, confirming punchlist status and confirming ITR status tasks mentioned are automated and electronic, whereas the existing system relies on manual handling and verification of readiness in a cumbersome manner. Using this system, the work is electronically assigned to the inspector, with no manual handling of sheets or status indexes. Effectively, the supervisor and inspector have not even required physical communication at this point, even where there where issues in the assignment. Additionally, the Network Storage 10 implementation is utilised to make the information available (perhaps with varying privileges) to many parties, both on and off site.

Referring now to page 2 of the workflow overview example, Figure 4b it can be seen that the Inspector 20 now performs the task to Retrieve ITR 21. The Stored ITR 10 (a reproduced copy from the network storage location) is downloaded to the TICS PC. This activity also triggers an update of the ITR Status List 26 which now may indicate that the ITR is "checked out". This may disable another inspector or party attempt to perform the same inspection for any particular reason. The existing system resulted in this problem, as the paper-based printouts of inspection forms were often produced more than once and resulted in doubling up of inspections across the project.

The Inspector 20 now checks to verify the primary information is ready to perform the work, which involves accessing the Information Ready List 18 which shows the information provided by the Supervisor 13 who has checked Information Ready 14 by observing the documentation status for the particular equipment under inspection, located on the Network Storage 9. Primary Documents & Drawings 2 provided by Engineering 1 are stored on the Network Storage 9. The CMS 6 process of integrating data provided by Engineering 1 involves allocation of drawing and document numbers to project equipment tags, such that ITRs and forms are printed automatically showing the assigned details. By accessing this information and confirming the required information files exist, the Supervisor 13 can ultimately confirm that the Information Ready 22 component of the Inspector 20 activities shall be achieved.

Once this is confirmed (or most likely as the same activity) the Inspector 20 is able to retrieve the engineering Drawings & Documents 11 to prepare for the inspection, all electronically. The existing process relies on paper based copies of the drawings being provided, which often result in many copies of the same drawing in existence, and therefore no control over the use of those drawings especially where engineering changes are made to the master copies. Additionally, the TICS system advantage is that the revision number of drawings and documents downloaded is a recorded parameter, so that if there was a major engineering revision or important change, all inspections that were performed using a specific revision of a document or drawing can be identified with a simple database search.

During the process of retrieving information for the inspection task, any Supervisor Additional Information 15, or Engineering Additional Information 3 is retrieved, which may be in the form of notes, manufacturer manuals, specifications, typical drawings or instructions as the case may be. In fact the Inspector 20 would be provided access to the equipment specific "file" which would include all collected data and information as previously acquired and / or defined as being made available. Additionally an essential part of the TICS process is for the collection of parameters and information which may be built into the inspection process that allows for high level inspection activities and automated processes, specific to the TICS process. This data is used on the TICS interface to perform automatic and manual comparisons between the engineering data and the equipment software settings and test equipment readings. This data is represented as TICS Specific Engineering Data 5 as provided via an integration process (providing the required data in a specified format) represented as TICS Engineering Data Integration Process 4.

The Inspector 20 assesses the data available. Where not appropriate, they would discuss with the Supervisor 13 as a Review Required 16. Where satisfactory, the inspection process continues back on to drawing Figure 4a as shown. To Assemble Test Equipment 34 the inspector relies on the TICS Platform 24 which identifies, manages and provides access to the selected equipment inventory provided for the project. This system is simply represented by the Equipment Management Process 25 which is ultimately overseen by the Supervisor 16. The Inspector 28 would collect the required equipment to perform the inspection, as decided using the information provided on the TICS ITR interface also referencing the information retrieved earlier. A suitably trained discipline inspector conducts this task painlessly, with the assistance of the Equipment Management Process 25 (defined more clearly in later sections). The Inspector 28 then prepares the equipment for use by checking its functionality, batteries, and certification and checks the equipment out by use of barcode scanner system. A "bump" test or equipment verification process may be implemented, where the field equipment is verified against laboratory or workshop standards as a daily performance check. In the case where conventional (non electronic) tools and equipment are used (i.e. torque wrenches, calibration / test gases, etc.) the process would be similar, with results entered into the TICS System manually. Referring now to Figure 4c of the drawings, the Inspector 15 conducts a Safety Analysis 16 and where OK to proceed 17 (as detailed in later sections regarding safety implementations example) the Inspector 15 is able to begin the inspection and Perform visual inspection 24 to ensure no obvious issues are present that would prevent them continuing. In the case that there were obvious reasons that the inspection should not continue, the Supervisor 6 is required to take the appropriate action to rectify and address associated information repositories and make a note against the item in the TICS implemented note system. Where the inspection is to proceed, the next step for the inspector is to now Retrieve Device Data to interface 19 which involves the integrated communication mechanisms to collect the appropriate information from the equipment and insert into the designated sections on the TICS form. Once again, this process is flexible and the information transfer requirements are defined in the development phase to the client's requirements. The process is detailed further in later sections of this invention proposal. For simplicity, the drawings show that the appropriate data is transferred at this point.

The Save Configuration 20 action is performed, where the full device data download is performed using the TICS hardware integration equipment and sent to the TICS Platform 11 (Server based) via the TICS LAN. The items As Found Settings 14, Configuration Log/Audit Trail and As Left Settings 12 represent the process of providing the TICS Platform 11 with settings from the original download, subsequent downloads and then the final download (on job completion) which enables tracking of configuration changes made during the activity. By simply comparing the two configurations at any future moment, it is possible to identify what changes were made during the particular inspection process. The data would be "stamped" with the inspection ID details, which all the activity to be classified to that particular inspection point by the TICS Database 10 and the saved configuration plus additional data and determinations stored on the Network Storage 3 for access capabilities. These capabilities are represented simply by the Information Read Access Portal 4 which is shown as providing access to Engineering 1 and Supervisor 6 in this particular example.

Shown now on Figure 4d of the drawings, a Configuration Review 17 is performed as a combined manual and automated process, where the Pre-defined Engineering Device Data 14 is compared against the actual device configuration (as represented by the links back to Figure 4c, item Device Data 23) and any Configuration Changes 18 are assessed and implemented. The process involves identifying key parameter requirements and referencing engineering information to ensure equipment is configured correctly and software configurations represent the appropriate equipment capabilities and conditions as specified.

To prepare for functional checks, the activity Retrieve Equipment Data To interface 24 is conducted, where the test / verification equipment communications established and details uploaded to the test form. During this process, the equipment ID and suitability is verified automatically, against the defined test parameters that were acquired during the engineering data and device data acquisition. This process intelligently assesses the suitability of the test conditions and equipment used against pre-defined determinations.

Shown next is the step Perform Inspection / Verification 19 to represent the actual inspection activities associated with the particular inspection moment. This is representing the actual inspection work performed, and function checking the equipment. The process is detailed further in later sections, but shown simply in this drawing to identify the activity as. part of the overall workflow. During this step, the physical observations are made and recorded on the form, against drawings, documents and information provided as shown by Physical Installation Check 26. Also, there are several observations made during this step, based on quality and operability, some of which are specific to the level of experience held by the particular inspector. The TICS system aids in these determinations by providing links on the interface to project documents and standards, and provides the inspector clear guidance and assistance. The Functionality Check 25 uses communications methods (detailed elsewhere in this invention specification) to access Equipment Data 23 and Device Data (item 23 on Figure 4c) to input test results to the form. Also embedded in this process is automatic determinations and criteria that assesses results obtained. The resultant interface may provide the same information (plus additional) as conventional paper- based systems, or as per the clients specification, however all data is collected in a manageable and usable electronic format, as well as being provided as an electronic record to satisfy existing processes and inspection techniques.

Non-compliances 20 deals with inspection items that result in a non-conformance with the relation to the inspection / verification criteria specified on the inspection form, and which could not be addressed or resolved immediately. These non-conformances 20 eventuate into Punchlist Entries 8 having first been assessed and approved by the Supervisor 9. Only then can the non-compliance 20 be processed by the CMS 2 administrators and enter the Official Project Punchlist 3, and be provided in a CMS Punchlist Report 7 requested by project groups or members. Punchlist items are to be addressed prior to handover or accepted at time of handover and are a critical part of achieving a successful start-up and quality result.

Following the activity of identifying any non-compliances 20 the Inspector 16 would then proceed to re-review and Mark up Drawings & Documents 21 as required. The TICS field system would present this requirement to the Inspector 16 as a mandatory activity prior to being able to submit the inspection results. This additional advantage of the TICS process ensures that the inspector is addressing all relevant documentation in the field, and the corrections are made prior to the inspection being completed.

Referring now to Figure 4e of the drawings, the step Review all Information 23 is shown to represent the process by which the Inspector 22 would review the complete task once completed, Label Device as activity complete 29 (commonly a tag or sticker on the device itself) and prepare to submit the information as shown in the subsequent steps Submit ITR 25 and Submit Marked Up Drawings & Documents 26. During this process, the TICS Platform 17 takes the submitted interface and Extracts New Data 19 which is a process of assembling new and modified information from the interface into the TICS Database 18. This information is once again defined to the clients requirements, but in essence the fact that data acquired during the inspection (for example equipment information stored in the software configuration, like model number, serial number, hardware revision, software revision, etc. etc.). is now updated into the TICS Database 18 where one can have the ability to back-load the information to the CMS Tag Database 7 as an option for further populating this data source as well. This helps to provide more information to any upcoming inspection forms, as well as maintain a detailed and highly databases with intelligent and useful information. Previously this was not achievable with paper-based inspection and verification systems. Once again the Supervisor 13 is responsible for overseeing and reviewing the work performed and once Approved 15 the information enters Network Storage 9 locations where it is accessible by the project, and in particular the CMS Tag Database 7 which ultimately controls and reports on the completions progress of the project, and by doing so marks the inspection activity as completed once Approved 8. It is envisaged that an Update Drawing & Document Status 6 process is engaged to identify to the Engineering Database 2 (or responsible persons) that the documentation mark-ups are available for review and addition to the project. The drawings and documents edited would be available via Network Storage 9 and a system of labelling used to identify their position in the process (i.e. against a particular inspection). These items are then available to the project in an immediate fashion, and very importantly to upcoming inspections. The engineering drawings and documents are progressively Back-drafted 4 by engineering and the files updated and managed by Engineering 1 and old revisions deleted and replaced as required. This back-drafting process does not inhibit the project from accessing previously identified mark-ups and changes. A well thought out implementation of this process can provide dramatic improvements on and off site, where the drawing and document management process is difficult to control, manage and address.

Where the Supervisor 13 has Approved 15 the submitted inspection and verification results, the interface Status List 21 is updated to reflect this step in the process as does the CMS 5 approval process. The Inspector 22 Monitors Acceptance 26 of this progress in an ongoing fashion via the Status List 21 until the inspection is Accepted 27 and thus no longer identified on the Job Status List 31. At this point the Job is complete 30, or if either approval process was denied the Review Required 16 step is initiated, where the Inspector 22 would be required to consult with the Supervisor 13 to identify issues and resolve them where possible. This may or may not involve repeating the activity. At all stages, where documents are transferred to the Network Storage 9 and have not passed approval processes, the relevant submitting parties still have primary access rights and control of the information and data.

CONVENTIONAL EQUIPMENT FUNCTION CHECK EXAMPLE

The following example is used to demonstrate the integration of test equipment with regard to simple devices (those not containing processor based electronics and memory) which could be in the form of electrical, mechanical or pneumatic equipment for example. The example demonstrates the integration of test and calibration equipment into the TICS forms and TICS system to allow the concept to be considered across various applications, even where plant equipment is not "smart" or software configurable. Once again, the extent of this type of implementation is dependent on the project / clients requirements, and the TICS process aims to only offer this sort of integration once proven and demonstrate-able. The example shown uses a shut-down valve timing analysis, but the concept is that suited hardware in the form of test and calibration equipment is integrated with a field PC (TICS platform) to enable accurate and real results to be recorded for an existing process during plant equipment inspection and verification activities. The example shows representations only, and simplifies certain processes to provide an overview of the concept rather than every component aspect. Some details of simplified processes and excluded information is included elsewhere in this invention proposal.

Referring now to the drawings, in particular Figure 6, the drawing component Engineering Data 2 is represented as having defined Valve Timing Data that was specified during the plant engineering and design phases. Via the TICS Engineering Data Integration Process 3 the information is made available to the TICS Database 8 as a data package shown as TICS specific Engineering Data 4. This data may contain specific Tag, Timing Criteria (e.g. Minimum Time to Close, Minimum Time to Open values), and Timing Units (e.g. Seconds). The information is held and kept synchronised on the Network Storage 7. Ultimately, this information is accessed by the TICS interface 19 by the field Inspector 20.

When this particular activity is required, the process starts by an Energise Solenoid 21 action that is initiated by the Inspector 20 when appropriate. This action applies energy to the Solenoid 27 which may cause the Valve Action 28 to occur. Simultaneously the Energise Detected 12 flag is activated on the TICS Platform 11 which could be via voltage threshold detection using the integrated equipment, and being broadcast to the TICS Platform 11 using communications methods as discussed elsewhere in this invention proposal. When this action is detected, the Record Current Time 3 event is performed, which as an example would capture the real time on the TICS Platform 11 PC equipment. Following this data acquisition, the possibility to also record the measured voltage (for example) across said Solenoid 27 is available which shows the working voltage used during the test. Almost instantaneously (or possibly in parallel), the Monitor Limit Switch 15 event is active which in the example is monitoring the Limit Switch 29 contacts either by resistance measurement or using a source voltage or current connected to the same interfaced test equipment. When the Limit Switch 29 signal becomes Closed 16 the TICS Platform 11 then Records Current Time 17. It would also be possible to record the measured resistance, voltage or current signal for example at this point in the same way that the Solenoid 27 measurement was taken earlier.

Providing the Solenoid 27, Valve Action 28 and Limit Switch 29 components were functional and correct as expected and designed, the process would provide test results as shown by Display Valve Timing Result 22. This would be the automatic calculation of the difference between Record Current Time 17 and Record Current Time 13. This simple process has provided an automated, accurate and real result (not simply an estimation or "normal" figure) for the valve timing test, with additional diagnostic data such as the solenoid and limit switch measurements.

To fully realise the benefits of a system such as TICS, the Compare Results 23 evaluation which is to compare the engineered timing specification against the acquired result and automate data evaluation would occur, resulting in a Pass 24 evaluation. Where the timing criteria and results obtained were not satisfactory, the Inspector 20 would need to rectify the issues, which could mean adjusting the valve hardware and ancillaries to achieve the desired result, or consult with a supervisor or engineer to gain guidance on the conditions identified. Where the criteria and results are acceptable, the TICS interface 19 which contains all the data, information and results obtained (including the inspection results performed outside of this example) are submitted as part of the process as defined elsewhere in this document. To demonstrate the particular data transfer for this process, the TICS Database 8 component is shown to receive the test results from the form, as well as compile Valve Timing Datasets 9 with this information, available as data (and manipulation as required) by Engineering Review 5 and Supervisor Review 31 who have access to this reported information on the Network Storage 7.

SMART TEMPERATURE INSTRUMENT FUNCTION CHECK EXAMPLE

The following example demonstrates the functionality verification of a usual temperature transmitter instrument that would be commonly encountered on industrial plants. For simplicity not all components of the drawings, Figures 8a through to Figure 8f have been labelled or discussed. Referring to Figure 8a an overview of the general process is shown. Engineering Data 1 represents information that is being referenced from engineering data sources from within the TICS platform. Field Device 3 represents information being sourced from within the actual instrument and Test Equipment 4 represents information being sourced from within the test equipment. The TICS interface 2 represents the activities and tasks being performed from the field PC.

The process involves using Engineering Data tables 5 to find Tag Specific Engineering Data 6 against ttie tag information that has been collected previous to retrieving the sheet (use of barcode on instrument and sheet download). The Device Data 7 is retrieved from the Field Device 3 and configuration review and changes implemented as required. Next, the Equipment Data 8 is retrieved from the Test Equipment 4, and the Setup Test 9 performed where the Equipment Setup 10 information is sent to the Test Equipment 4. When the interface performs a Run Test 13 the automated process is performed which, through communications to the Test Equipment 4 enables the interface to retrieve and record Test Data 12 and Populate Results 13 to the TICS interface 2.

As previously mentioned and detailed further in Figure 8b, the Device 3 data is compared and documented against Compiled Engineering Data where key elements are examined and confirmed, with specific relation to the particular test - in this case a functional test of this field device. In addition to performing such comparisons and verifications, the full device download is performed to capture the configuration at that particular time. Shown on Figure 8b are only some of such parameters and settings that may be of interest during the functional test example.

Figure 8c demonstrates the TICS interface 2 using the information collected so far to define the test setup, where with the user input or project specification, the number of Rising Steps 4 and Falling Steps 5 are defined. From this information, the TICS interface 2 may determine the test setup values, reading expectations and use Compiled Engineering Data 1 once again, to determine the Accuracy Specification for this particular inspection moment.

During the process, the test equipment requirements are determined to allow the selection of appropriate and available test equipment. Referring to Figure 8d of the drawings, the TICS interface 1 retrieves the Equipment Status List 2 and compares the Test Equipment Criteria 3 with a Lookup Table 4 to identify suitable equipment and show their availability. Once this is determined, the user would then Check out the selected equipment 5 which in turn would adjust the Equipment Status List 2 to reflect this action. The details of this equipment is then loaded onto the TICS interface 1 in preparation for the upcoming functional test.

In the field, the inspector would proceed to locate the device and establish communications as described above, and then continue on with the inspection as per the TICS interface process. When the stage for the functional test arrives, the system would proceed as demonstrated simply in Figure 8e. Here the TICS interface 1 establishes communication with the Test Equipment 2 after which it can Request ID 3 from the Test Equipment 2. When this occurs the device serial number is loaded into the TICS interface and by accessing this device information located in the equipment management system, in particular the Equipment Status List as previously mentioned, the interface can re-check the suitability and selection of this equipment to confirm it is correct and within validation, This check confirms that the correct equipment was physically selected and is to be used. The TICS interface 1 may then be able to proceed and set up the Test Equipment 2 by arranging the specific input and output requirements as previously determined by the system. When this has been achieved, the inspector must then physically connect the Test Equipment 2 to the field device under test and at which point the TICS interface 1 may instruct to do so. Also at this point the Equipment Hook-up instructions for test type 4 is made available to guide the inspector for use of the particular equipment connection details and any other special information (previously determined and attached to this equipment, equipment type or type of test).

During the actual function test as shown now on Figure 8f, the test is initiated by the user and the TICS interface 1 may Set output 3 on the Test Equipment 2. The Test Equipment 2 may be instructed to re-present this figure to the TICS interface 1 with a Read Output 4 instruction. This figure is recorded by the system. Then the TICS interface 1 may Read Input 5 of the Test Equipment 2 which now reports back the current reading of the instrument under test. This figure is also recorded by the system. It would be usual also to confirm the plant control system reading so at this point the inspector can communicate with the appropriate console operator / engineer to have the result reported back and manually enter this data to the form. The test would continue in this fashion until all the TICS defined test steps are performed.

On completion of the test, the TICS interface 1 would then calculate the results measured, and check the tabulated information against Test accuracy limits 7 as previously acquired from the engineering data, to then present the Pass or Fail information and an evaluation of the test. Where the results are not satisfactory, the TICS interface 1 would request the appropriate action is taken to correct the situation and / or repeat the test at which point there would be a selection of pre-defined options available to the inspector.

INTERCONNECTIVITY TO PLANT SYSTEMS AND EXAMPLE IMPLEMENTATIONS

Use of a system such as TICS can be expanded to cover a multitude of application advantages. Few Examples of such implementations are discussed below.

PC Access

An ever increasing need is present in today's inspection and verification regime for computer access, whether it be to create forms, access completions databases or search for and locate information, certificates and manuals. Where this normally becomes only available through a supervisor or spare computer on site, the TICS system allows each inspector the access to their own PC. This advantage can be realised by allowing inspector access to the Completions Database 23 which has its own system of user privileges and access rights, and the inspector can access information on punch-lists, plant and equipment status and inspection progress. This enables the inspector to access the live punch-list when assessing the addition of a new entry (to determine if the Non Compliance 31 has been already identified) and also see the status if inspection points related to their inspection task (have the cable, tubing, interfaces, etc. been checked) for example prior to commissioning tasks. It is generally one of the first questions on a "B" type (pre-commissioning type) inspection and verification form - "have all the "A" sheets been completed and punch-list items cleared". Enabling access to the inspector, they can identify this requirement themselves. This step is critical in situations where a pre-commissioning check is performed, only to be later invalidated when a prior punch-list item requires major rework to the installation and causes the need for a revisit inspection / verification. Where this process falls over is when the completions system does not identify that the re-work has invalidated inspection work, it just sees a completed form.

Cause and Effect testing and other project test scenarios

The implantation of TICS could extend further to be used during other test situations commonly used on projects. Such an example of this could be cause and effect testing where the plant safety systems are verified systematically. This could involve the use of "remote access sessions" or across multiplexer arrangements where the engineer performing the test has access to either the field TICS unit connected to the appropriate process input device and/or across a multiplexer arrangement. In this situation, the engineer can initiate the "cause" while another technician or group of technicians are at the location of each "effect". Similar implementations could be added for commissioning test procedures on plant systems and mechanical skids or modules.

Remote access possibilities

Through the PC platform in use, it is possible to enable "remote access" sessions, perhaps where a technician required assistance or input from a remote supervisor, fellow technician or engineer. Once again this would benefit the project a lot in terms of a quality result (where the situation is more likely to be dealt with rather than "ignored" by the field technician) and efficiency. This possibility could extend to off-site if the appropriate arrangements are made to support this. In addition to this, using the correct networking methods, it would also be possible for data transfer between control systems and remote stations (say the console operator or engineer) and perhaps data transfer in terms of control system actions such as "over-ride" or inhibit enabled.

Leak testing

During the process of leak testing a pipeline or subsystem, the barcode system already implemented could be utilised by the inspector simply scanning all devices exposed to the leak test, to document the test conditions. Compiling such a list can assist in confirming the full process line-up and verification, whereas previously a list or drawing would be used and marked off. Performing such a test with a TICS field PC would simply be a matter of scanning a barcode, automatically updating the test information.

GPS overlays

Using the TICS PC with GPS functionality, it would be possible to provide a layout drawing overlay which would assist technicians locating plant equipment to as close as a 5 meter accuracy in an outdoor plant location or where the technology permits. Inspectors that are usually new to site (not involved with the construction process) possibly waste as much as a third of their day just locating the devices that are to be inspected. Using layout drawings, it would be possible to set up the plant layout and provide at least a two dimensional map of the plant equipment.

3D model access

Due to the fact once again that the TICS system is PC based, it would be possible to allo access to the plant 3D model. This would enable considerable benefits when locating equipment and determining installation correctness.

Cable data analysis

In situations where cable lengths and physical properties are used in engineering calculations (i.e. digital networks and Ex validation) it would be possible also to use cable analyser equipment connected to the TICS PC platform to include these measurements in the test and inspection process.

Safety analysis compliance and new contributions

The user has the ability to complete Job Safety Analysis forms and create permit applications themselves, using the TICS PC. There is abilit to implement mandatory task safety assessments prior to each inspection activity being performed using the TICS system, and safety alerts and special information can be applied to tasks where this is required. Safety assessment is an increasing requirement for projects, and it is possible to allow for a system where generalised or indeed very specific assessments that are made for tasks are applied automatically to activities that are issued and performed using the TICS interface 25. An example may be an inspection on a level instrument that resides on top of a tank, where the application of specific hazard analysis for that task has been attached to the inspection task and is presented to the user to confirm the hazards are known. Once again, being in a regimented, standardised format from the field PC, the information that is utilised during these processes can be compiled and used for reporting, with access to the site Health and Safety manager.

Referring to the drawings and in particular to figures 5a and 5b, an example of implementing a safety aspect into the versatile TICS system is demonstrated. The basic workflow with relation to the safety implementation is shown only.

In this drawing, HSE department 1 creates HSE related documents such as a Hazard Analysis Checklist 7 template. It is envisaged for the system to be implemented simply, a copy of this template is assigned to each job, stored on the Network Storage 5. Both the HSE Department 1 and Supervisor 9 (for example) are able to add to these forms and customise for a particular task or job activity, and also add notes on a specific Hazard Analysis Checklist 7 prior to the job being performed. An example of this may be where a job is in a particularly dangerous location. As represented by Assign job to inspector 11 the Job List 16 is updated by the supervisor when a particular inspection is ready to be performed. The Inspector 19 accesses this list and in turn Retrieves Job 20. The associated tasks Retrieve ITR 21 and Retrieve JHA information represent the fact that the appropriate files are retrieved to the TICS PC platform. At this stage the Inspector 19 would complete the job hazard analysis and submit the form for supervisory review, all done electronically by uploading the file to the supervisor. When the form is Approved 13 the file is stored on the Network Storage 5 in the designated location allocated for all Completed JSA Files 8. When the form is approved, the Inspector 19 receives JSA Approved Notification 18. The next task is to perform a "Step back 5X5" which is widely used throughout industry to further engage the worker to step back and spend five minutes to assess the work location on the job at hand before starting work. In this example the TICS Platform 12 is requesting that this is also done prior to starting work. In the usual process, this activity may or may not be performed prior to beginning work, and the TICS system is merely insisting this is done before allowing the inspector to proceed. As is represented in Figure 5b, the Authorise Start Work - Issue ITR 15 step has used automated means of ensuring that the JSA Approved 8 information is received , but also that the Step-back 5X5 performed 13 step is satisfied before allowing the Inspector to Perform Work 23. This implementation, not ensures that the inspection team is performing the required safety analysis tasks in the correct order and for each job, but also enables the system to automatically upload the forms and results. As shown in Review 11 step, the information from the activity is transferred to the Supervisor 8 who can then check the results and send to the Network Storage 4 location. Additionally, the statistics on safety performance are an automated result, as is the information collected on the cards themselves. Due to the implementation of an electronic system such as TICS, the information can be further sorted and categorized. The HSE Audit Process 2 demonstrates that the HSE department could then access the stored data and identify common issues and findings quite easily. This may assist with say providing additional protective equipment, running an awareness campaign or inspecting in the field further to address a high number of reportable hazards.

At present, systems for safety analysis are difficult to monitor and the data received requires full time data entry activities to transfer to electronic systems. Using the TICS system already enables the field personnel with the tools to enter the data electronically. It also ensures that work can't begin prior to the adequate safety tasks being performed. Using the system enables automatic monitoring of individual inspectors compliance with these requirements, and makes use of the data acquired. In conjunction with these advantages, the inspector has the ability to take photos using the PC based equipment (where in-built camera is present) and report directly to appropriate people by using the device. The implementation of automatic reminders to input further safety observations (as is commonly required on projects) can also be achieved quite easily on the system as could the ability to "broadcast" certain safety announcements and pre-start information. A site "news" page can be used to offer the site pre-start report to the users of the TICS system. In summary, being able to identify and report on safety observations on the spot is important when expecting a general level of reporting for the workforce. Effectively, it could be said that the users on site of the TICS system would have the best chance of remaining compliant and adding value to the HSE management system due to the inbuilt supervision and ease of access.

Arranging special requirements

Where there are special requirements or requests, the implementation could extend to being used for placing these requests on site through the PC and local network. For example, where an inspection task required scaffold or a scissor lift in order to be performed, the inspector could make this request using the field PC, which in turn is directed to the appropriate department on site as a "booking" so to speak. Where an inspection cannot take place, the team supervisor is made aware of the fact immediately (via email or instant messaging) instead of at the end of the day or earliest convenience. Additionally while message forwarding is alone efficient, the inspector's information can be forwarded directly to the responsible parties where applicable.

Claims

Claims

1. An engineering quality system comprising: a database module to hold at least one database; a computational module to perform a comparison of data in the database against at least one set of quality requirements and a communications module to communicate the results of the comparison.

2. An engineering quality testing method comprising: comparing data in a database against at least one set of quality requirement and communicating the results of the comparison.

3. A system or method according to either claim 1 or claim 2 wherein the database comprises optionally one or more of: an engineering database; a completions database; a client requirements database; and / or an interface equipment database.

4. A system or method according to claim 3 wherein the interface is definable.

5. A system or method according to claim 1 or claim 2 comprising a second communication module to assist communication of information from an information source which optionally may comprise one or more of:

a. Engineering Data

b. Functionality Requirements

c. Performance Criteria

d. Ex Specifications

e. Standards

f. Specifications

g. Guidelines

h. Client Specifications

i. Manufacturers Information

j. Site Safety Information

6. A system or method according to claim 1 or claim 2 wherein the computational module communicates with one or more items of test equipment in relation to one or more tests to be performed.

7. A system or method according to claim 1 or claim 2 wherein a test result causes one or more additions in one of the databases.

8. An engineering quality system or method comprising a computational module and a database comprising at least one interactive element wherein the at least one interactive element corresponds to an item of engineering equipment and the interactive element is operable to cause the computational module to undertake one or more operations in relation to the engineering equipment and wherein the operation is optionally selected from: design a quality test, conduct a quality test, record information relating to a result of a quality test arid / or update a database comprising information relating to the engineering equipment.

9. A system or method according to claim 1, claim 2 or claim 8 wherein field equipment and project information are integrated into an electronic inspection form, which is presented o a computing device to conduct inspection and verification activities.

10. A system or method according to claim 1, claim 2 or claim 8 comprising management of field device configuration and verification information to enable preparatory work to be conducted in collecting relevant certification and information for upcoming inspections and preparation of handover dossiers, tracking and enable reporting on device type and setup information and to enable engineering review of work being conducted.