BECHTEL CORPORATION OGC GLOBAL BUSINESS UNIT - ENGINEERING CONTROL SYSTEMS
ENGINEERING DESIGN GUIDE INSTRUMENT DATABASE USING INtools 3DG-J21D-00013, Revision 001, 06 December 2004 Prepared by: J.C. Yang/M. Parker Checked by: W. Wong Approved by: A. Vakamudi Reason for issue: Revised for Use
INTRODUCTION
INtools is the approved Bechtel Standard Application Program for managing instrument database for OG&C projects. This design guide defines key requirements for the configuration and implementation of an Instrument Database using INtools by Control Systems on projects. Control Systems Engineering Group Supervisors (CSEGS) shall follow this design guide to define all INtools setup/configuration requirements for a given project and issue a Project Work Instruction (PWI). This design guide shall be the basis for the PWI and shall include all deviations and changes made to customize for meeting the project requirements. Each project shall submit the INtools Project Work Instruction for the Chief Engineer’s review and approval prior to proceeding with configuration and set up of INtools. Each CSEGS shall review the information in this guide before any work is begun on the INtools database.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
This document shall be used for the setup and the implementation of INtools on Projects. It provides an overview of INtools features and functions. It documents the information needed to set up and configure the INtools database system and also documents how Control Systems use INtools. The data in the database will be used for generating the project deliverables such as the instrument index, instrument data sheets, loop diagrams, connection drawings, installation details, configuration data for DCS/PLC/SIS system, etc.
Acronyms:
BOM Bill of Material BPS Bechtel Procurement System BSAP Bechtel Standard Application Program CSEGS Control Systems Engineering Group Supervisor DBA Database Administrator DCS Distributed Control System EPC Engineering, Procurement and Construction FEED Front-End Engineering Design FEL Front End Loading IEE INtools External Editor (INtools utility for process data sheets) LDT Line Designation Table (generated from PPS) P&C Petroleum and Chemical P&ID Piping and Instrument Diagram PLC Programmable Logic Controller PPS Pressure Profile Suite (Project Engineering BSAP) PWI Project Work Instruction SIS Safety Instrumented System
Definitions:
INtools Project Coordinator: A project control systems engineer who coordinates all INtools automation activities/issues with the INtools BSAP support group.
INtools BSAP Support Group: A group of INtools super-users who provide the department wide INtools support.
INtools Administrator: any member of the INtools BSAP Support Group who sets up, configures, and manages the INtools database, including administration of the access right and the assigned privileges for the users.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
This design guide covers required setup/configuration information and preparation/use of the INtools database during engineering and design phase in support of Engineering, Procurement and Construction (EPC) on a project. This design guide covers the data requirements for INtools to produce deliverables, including data exchanges to other BSAPs. INtools shall be used for the FEL and FEED projects as well, unless a deviation is granted by the Chief Engineer and the Project Engineering Manager.
3.0 PROCEDURE
Control Systems is responsible for the initial set up, building, updating, issuing, and maintaining the INtools database. Since project execution varies depending on the type of contract, project organization, and offices involved there will be a need to define and document the ownership of INtools data for the various project deliverables. During initial phase of the project CSEGS should review the system setup/configuration checklist (see Appendix D) and select the appropriate options for the project (also see 5.0).
It is recognized that some unique requirements and Client preferences can affect the project deliverables. The INtools database has to be set up accordingly to satisfy any unique requirements of the project. Any deviations from this guide shall be reflected in the INtools Project Work Instruction.
3.1 Database
One database will be developed and maintained per project. In cases where there is work sharing with other offices (such as New Delhi), the desired solution is to work share via a Citrix server such that only one database is required.
If there is a need to exchange INtools databases (such as with a client or compressor vendor), this should be coordinated with the INtools BSAP support group.
3.1.1 Database access
All access to INtools shall be through the INtools security logon. It is the responsibility of the CSEGS or the INtools Project Coordinator to determine and approve all users requiring access and what access rights they shall have in INtools. The INtools Project Coordinator shall inform the INtools BSAP support group of these users & their rights. It shall be the responsibility of the INtools BSAP support group to setup and assign a unique user-id and initial password for each user. After initial logon, each user shall change the initially assigned password.
When a user no longer requires access to INtools, usually when leaving the project, CSEGS or delegate will inform the INtools BSAP support group. It shall be the
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
responsibility of the INtools BSAP support group to revoke the user’s access.
3.2 Abbreviations and Standardized Terms
The use of abbreviations and standardized terms, such as measurement units, equipment numbers, names and other descriptive words, shall be used consistently throughout the database. It is important to standardize the format of the data. A list of standard abbreviations & terms shall be established and issued at the beginning of each project by CSEGS. In general, ASME Y14.38a – 2002 should be used as a guideline for abbreviations (different guidelines may be developed for those projects not using the USA practices). Any deviations or additions to these abbreviations to meet the project specific needs should be documented and maintained in the INtools PWI and approved by the Chief Engineer’s office.
Note: ASME Y14.38a-2002 is an addendum to ASME Y14.38-1999, Abbreviations and Acronyms.
4.0 INTOOLS OVERVIEW
INtools is an Intergraph product that is licensed to Bechtel. It runs on Microsoft Windows and uses Oracle as the database engine. INtools helps to maintain all aspects of instrument and control systems data through multiple modules that share one common database. Custom interfaces (i.e. the INtools Adaptor) were developed and released to facilitate data exchange between INtools and other pertinent BSAPs such as BPS, SETROUTE, PPS and TEAMWorks. Appendix A (Integration Exchange Diagram) and Appendix B (Control Systems Automation using INtools and other BSAPs) show various modules of INtools and its interfaces with various other BSAPs.
Appendix C includes a work process flow diagram for “INtools Setup Work Flow”. This is a flow chart to determine the requirements for setting up and configuring INtools. It takes into consideration the possibility that the client may supply us a seed file and also the possibility that some of our sub-contractors/vendors may also use INtools where we need to supply a seed file for them. The ultimate goal of this flow chart is to show that the CSEGS is responsible for developing a PWI that will determine how the project control systems team will execute their work using INtools.
INtools includes the following modules to administer and perform a variety of engineering and design activities.
4.1 Administration
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
There are two mutually exclusive levels of administration: • System Administration
This is a higher level of administration to define and manage the database infrastructure, which includes creating and defining the working environment, creating the list of users including the Domain Administrator, setting up database security, managing user session on multi-user versions, etc.
• Domain Administration
This allows managing resources that have been defined in System Administration. Access privileges for users, defining loop naming convention, plant-area-unit hierarchy, user-defined fields, etc. can be granted here.
4.2 Browser This module provides with a wide-angle view of instrument index data and allows the users to browse through and modify the data from a single location in INtools.
4.3 Instrument Index This module is used to create, modify, and maintain a comprehensive database containing all of instrumentation components. This module offers tools for adding, editing, and deleting loops and tags. Other functions include item-oriented filtered, sorted, customized database viewing options.
4.4 Instrument Specifications This module generates instrument specification sheets (data sheets) for single-item and multiple-item lists.
4.5 Spec Binder This module allows maintaining and controlling sets of instrumentation documents. At present this module does not satisfy Bechtel material requisition forms and requirements and is not approved for use on Bechtel projects.
4.6 Wiring
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
This module provides the means to define and manage the connections and routing of all interconnecting devices for instrument signals. Cable lists can be obtained with final associations to both the field device and system I/O.
4.7 Loop Drawings This module generates schematic SmartLoops, SmartSketch, AutoCad, or MicroStation drawings based on loop data from the Instrument Index and loop drawing blocks based on wiring and other selected data.
4.8 Hook-Ups This module provides the ability to generate installation detail drawings (hook-ups). This module covers various aspects of hook-ups, such as instrument installation, Bill of material data, etc.
4.9 Process Data This module defines process conditions for all active devices in the system. Process conditions may be modified for individual components or determined from existing conditions in the line and other associated component.
4.10 Calculation This module contains four sub-modules: • Flow Meter calculation • Control Valve calculation • Relief Valve calculation • Thermowell calculation See Section 8.2 for the further descriptions.
4.11 Other Modules INtools offers other modules such as Maintenance, Calibration, Spare Parts, and Construction, etc. Additional licensing fees are required for the use of these modules. Furthermore these modules have not fully matured and proven and are not directly related to the engineering and design functions, therefore, they are not recommended for project use.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
To successfully set up and implement INtools, close coordination is required between the CSEGS and the INtools Administrator. During the initial phase of the project CSEGS should review the system setup/configuration checklist (see Appendix D) and select the appropriate options for the project. INtools has the capability of being installed using one of several commercial databases. The Bechtel standard database system is Oracle. The Oracle database to be used by the project shall be installed/setup by an Oracle DBA. It shall then be the responsibility of the INtools Administrator to initialize the database and create the initial project domain.
5.1 Domain Initialization and Definition The Control Systems INtools seed file shall be used to initialize the domain. The seed file needs to be reviewed and agreed upon by the INtools support group and CSEGS prior to usage. This seed file normally contains default support tables, instrument-wiring profiles, default cables, default panels, and hook-up drawings. CSEGS shall be responsible for reviewing the seed file defaults and modifying them to be project specific as required. When creating the project domain, the INtools administrator shall be responsible for determining the domain name, domain login name and domain login password. In general, since the domain login name is the Oracle account name for the domain and is a read and write account, the domain login password should not be shared with other users. Since there are times when users need read-only direct access to the Oracle database, the INtools Administrator shall coordinate with the Oracle DBA to create a domain guest account that has read-only privileges. The following information needs to be provided to the INtools Administrator prior to setup and initialization:
• Project Number - The job number and sub-job number, such as 24954-100 • Project Description - The approved project title/name, such as EG LNG Train 1
Project • Naming Convention Type - The “Flexible” naming convention will be normally
used for the projec5t.
5.2 Owner-Plant-Area-Unit Data Entry
• Owner Name -The approved owner name
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
• Plant Name - The plant name defined by the project • Area Name(s) - The area name(s) shall be defined for a given project • Unit Name(s) and Number(s)
The unit names and numbers shall be defined for a given project, for example:
10 – General 11 – Inlet Separ/NGL Recovery 12 – Acid Gas Removal/Amine Regen 13 – Dehyd & Mercury Removal 14 – Propane Refrigeration 14V- Propane Compressor 15 – Ethylene Refrigeration 15V- Ethylene Compressor 16 – Liquef & Meth Compression 16V- Liquef & Meth Compr 17 – Hvy Liq Removal/NGL Recov 19 – Flares & Incinerator 20 – Refrigerant Storage 21 – Miscellaneous Storage 22 – Fuel Gas System 24 – LNG Storage/Loading 29 – Effluent Treatment 31 – Power Generation 33 – Firewater System 34 – Hot Oil System 35 – Plant/Instr Air System 36 – Water System 39 – Nitrogen System 40 – Buildings
5.3 Tag Naming Conventions
5.3.1 Tag
For example: 1-ABCDE-23456FG
1-ABCDE-23456FG - Prefix for Train Number (1 numeric) 1-ABCDE-23456FG - Process Variable (1 alpha) 1-ABCDE-23456FG - Modifiers (1 to 4 alpha) 1-ABCDE-23456FG - Unit designator (2 numeric) as defined above.
1-ABCDE-23456FG - Loop Sequence Number (3 numeric)
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
5.3.2 LOOP For example: 1-A-23456FG 1-A-23456FG – Prefix for Train Number (1 numeric) 1-A-23456FG – Process Variable (1 alpha) 1-A-23456FG – Unit designator (2 numeric as defined above) 1-A-23456FG – Loop Sequence Number (3 numeric) 1-A-23456FG – Loop Suffix (2 alphanume4ic)
5.3.3 (INSTRUMENT) DEVICE PANEL - Generally the same format as the instrument tag
number 5.3.4 DEVICE CABLE - Generally the same format as the instrument tag number 5.3.5 CONTROL SYSTEMS (SOFTWARE) TAG - Generally the same format as the
instrument tag number with all spaces and dashes removed
5.4 Project Logo If there is no project specific logo the standard Bechtel logo will be used.
5.5 Unit of Measure Need to specify if Imperial or Metric units will be used. Additionally, all of the units should be reviewed to ensure meeting the project requirements.
5.6 Security Setup Any special security setup/access requirements need to be specified by CSEGS. INtools security/access is controlled through a combination of userids, user groups, type of INtools activity, and the domain/plant/unit hierarchy that has been setup. To gain access to any INtools database, a user must be assigned a valid INtools Userid/password. The current procedure requires that any user granted access to a project database requires first the approval of CSEGS. A user group is a means of grouping individual users together that require the same level of access/use of specific types of activities. For each of these user groups such
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
as Engineers, Designers, New Delhi Control Systems, etc., access to specific activities are assigned, e.g., Instrument Index Module, Specification Module, Browser Module, etc. For each of these modules, there are sub-rights that can be assigned as well, e.g., View Only, Add & Update Only, Add, Update & Delete, No access at all. All of the activity rights are further assigned/controlled by the Domain, Plant, and Unit hierarchy. For example, the New Delhi user group is restricted only to certain units, and no access to the proprietary units. The constraints on the current INtools security implementation are: - Cannot restrict access to specific columns/data attributes. For example, give
access to all fields in the Index Module except the model number field. - From within the same unit, restrict activities based on specific tags. For example,
give access to Unit 14 for data sheets except control valve tags. - Restriction of activities that INtools does not already have an identified right. For
example, there is no specific right to control printing. Any project confidentiality/proprietary issues need to be coordinated by the CSEGS with both project management and the Chief Engineer prior to the initial INtools security setup.
5.7 Supporting Tables There are a number of support tables that are used by INtools to either automate other tasks or for ensuring data integrity/validation. These should be all reviewed and defined. While none are explicitly required to be completed during the initial setup and initialization, there are a few highly recommended to be defined before setup. A full list of tables follows, with those that are recommended to be defined before setup indicated with an *: - Instrument Type * - General Process Function Sub-Category (currently not used) - Status * - System I/O Type * - Location - Equipment - P&ID Drawing Number - Line Numbers - Certification (currently not used) - Manufacturer - Model - Function Block (currently not used) - Measured Variable * - Loop Type * - Loop Function * - User-Defined Tables 1 through 16
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
Instrument types are very important in INtools. The importance of getting the instrument type table and the associated profiles correct before tags are added to the system cannot be overstated. Abbreviations and instrument types must conform to the project requirements. (Note: The control system tag is defined as part of the instrument type profile.) Instrument Profiles are set up as part of the instrument types. These profiles can generate default data for a number of the modules. For instance, pre-defined data sheet forms can be assigned to tags (for single tag data sheets only). As such, the configuration of these profiles can impact significantly the creation of data and should be reviewed in depth.
5.7.2 Status Table Instrument status is used to define the top-level purchase requirements such as: NEW – to be specific and purchased by Control Systems EXISTING – makes use of an existing instrument; no need to specify or purchase
5.7.3 System I/O Type Table The I/O Type supporting table is used to define various types of input and output that an instrument has. The following types are commonly defined in this table: AI: Analog Input AI-HART: Analog Input HART Device AI-R: Analog Input Redundant AI-R Smart: Analog Input Redundant Smart AI-Smart: Analog Input Smart AI-4-20 mA: Analog Input 4-20 mA AI-R-4-20 mA: Analog Input 4-20 mA Redundant AO: Analog Output AO-HART: Analog Output HART Communication AO-R: Analog Output Redundant DI-120VAC: Digital Input 120VAC DI-24VDC: Digital Input 24VDC DN: Device Net DO-120VAC: Digital Output 120VAC DO-24VDC: Digital Output 24VDC DO-R: 24 VDC Relay FIELDBUS: Fieldbus H1 REDUN: H1 Redundant KX-mV: KX-Millivolt Signal
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
NA: Not Applicable PI: Pulse Input RTD: Resistance Temperature Device SCADA: SCADA SERIAL PT: Serial Point SOFT: Software Input SOFTWARE: Software Tag TC: Thermocouple
5.7.4 Location Table The location table is to specify the general instrument location data. Some typical location designators are listed below: ANALYZER SHELTER CONT BLDG-CONSOLE CONT BLDG-I/O CAB CONT BLDG-INACCESS CONT BLDG-RACK COMPR BLDG-CONSOLE COMPR BLDG-CONT PANEL COMPR BLDG-I/O CAB COMPR BLDG-INACCESS COMPR BLDG-MCC COMPR BLDG-RACK MAIN SUB-CONT PANEL MAIN SUB-I/O CAB MAIN SUB-MCC MCC INTERPOSING RELAY CAB FIELD FIELD-EQUIPMENT FIELD-REMOTE FIELD-INLINE FIELD-OFFLINE FIELD-LOCAL PANEL FIELD-INTEGRAL MTD VENDOR NA
5.7.5 Equipment Table This table is used to specify the associated/related equipment for any given instrument.
5.7.6 P&ID Drawing Number Table
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
This table is used to specify which P&ID drawing any given instrument is located on. The table is normally populated via an import. Coordinate any imports with the INtools Administrator.
5.7.7 Line Numbers Table This table is used to specify which piping line number an instrument is associated with. This table is also used to store various physical data about the line, such as line size, material and pipe schedule, etc., holds all the line physical data, and is categorized according to line types. The table is normally populated via an import. Coordinate any imports with the INtools Administrator.
5.7.8 Manufacturer Table This table is used to specify the instrument manufacturer. This is normally done after an instrument supplier has been selected.
5.7.9 Model Table This table is used to specify the instrument model number for any given instrument. This is normally done after an instrument supplier has been selected.
5.7.10 Measured Variable Table
This table is used to specify the loop process variable, such as F for Flow, P for Pressure, T for Temperature, etc. This identifier is also used in both the tag and loop naming conventions. The measured variables used by the project should match what is defined on the P&ID Symbols and Legend sheet. These typically match ISA standard for tagging of instruments.
5.7.11 Loop Type Table This table is used to categorize the type of the loop. For example: LOCAL DCS SIS VENDOR NA
5.7.12 Loop Function Table This table is used to specify the purpose or function of the loop. For example: I – Indicating loop A – Alarm loop
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
5.7.13 User-Defined Table There are sixteen (16) user-defined tables. They are currently assigned as follows: (1) Commodity Code, example: JA01, JF01, JL01, etc. (2) System Type, example: DCS, SIS, PLC, MARK V, etc. (3) System Locator, example: AB, DG, HC, etc. (4) Estimating Code (5) Supply Responsibility, example BY OTHERS, BY VENDOR, BY VENDOR-SHIP LOOSE, BY ELECTRICAL, etc. (6) Alarm Priority Table 7 to 16, currently un-assigned
6.0 MASTER INSTRUMENT DATABASE
All of the tables established for the INtools system are collectively considered as part of the Master Instrument Database. The database is used through the life cycle of the Engineering, Procurement and Construction (EPC) project activities. INtools supports the various EPC phases by supporting the generation of instrument index, process data sheets, instrument specifications (data sheets), loop drawings, wiring/termination reports, hookup drawings (installation detail drawings), bulk material takeoffs (MTO), alarm summary, and engineering data to support DCS/SIS/PLC configuration. Through the use of the INtools Adaptor interfaces and DataBroker, the database can also support the exchange of data with other Bechtel BSAPs, including TEAMWorks and SETROUTE. While the Master Instrument Database contains a wide array of information, not all of the data is used directly on any given deliverable. There are a number of fields that are used by INtools to maintain the database integrity and provide for automation of various activities and modules. Likewise, there are a number of fields, including the user-defined fields that are used by engineering and design group to help managing and coordinating their work effort in support of generating project deliverables. Field references through the balance of this design guide are intended as minimum data requirements for the project deliverables to be generated by INtools.
7.0 INSTRUMENT DATA
7.1 Instrument Index The instrument index is developed and issued in conjunction with the P&ID’s. The index serves as the indices to each individual instrument (hard or soft tag) and supporting documents and drawings
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
The tags to be added to the database include: - All visible instrument tags on the P&ID, including soft tags - Implied instrument tags on the P&ID, based on project requirements - Vendor tags, based on project requirements - Control Systems tags, which are normally auto-generated by INtools The instrument tags can be added by “Tag”, “Loop”, or “Batch Loop Creation”. Properly defining the instrument profiles (including the wiring assignments) and typical instrument loop codes, prior to adding instruments to the index, can significantly minimize the amount of work required for wiring document, loop drawing, hook-up drawing (installation detail) and data sheet generation later. Adding the tags by the typical loop method is the preferred way. Exactly which fields to be included shall be determined by each project. However, the minimum required fields for the instrument index are: TAG Number - This field provides the alphanumeric identification of all instruments, including soft tags. See paragraph 6.3 for the tag naming conventions.
P&ID Number - This field indicates the P&ID drawing number reference for each instrument. The P&ID is selected from the P&ID Drawing support table.
Example: 24954-100-M6-1T19-00005 19 - Unit designator (2 numeric) 00005 - Sequential Drawing Number (5 numeric)
7.1.1 Loop Number This field indicates the tag’s associated loop identification number. It is initially assigned by INtools program when new tags are added. However, in cases where the auto-assignment is incorrect, it can be modified. It is important to get this association correct to facilitate correct loop generation.
Example: 1-T-11001 1 - Train Number Prefix (1 numeric) T - Process Variable, Temperature (1 alpha) 11 - Unit Designator 11 (2 numeric)
01 - Loop Sequence Number 001 (3 numeric)
Note: INtools allows for a tag to NOT have a Loop Number reference, such as pressure gauges. The primary reason for not having a reference for such instrument type is to prevent the INtools program from attempting to generate “un-desired” loop drawings. Whether to assign a loop drawing reference to every tag in the index or not should be decided up front by CSEGS and documented in a PWI.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
This field denotes the instrument type. Examples: PRESSURE TRANSMITTER, PRESSURE GAUGE, etc. It is automatically entered by INtools when a tag is added. The selection is done from the Instrument Type support table. Note: In INtools terminology, this is actually the Instrument Type Description. Instrument Type in INtools is the alpha portion of an instrument tag number, i.e., FE, FT, FIC, etc.
7.1.3 Service Description This field is used to define the overall use or service for an instrument. It is normally referenced on data sheets, nameplates, loop drawing titles, and the DCS configuration. It should contain information which is concise yet exactly defines what is the service of the instrument. If a tag is added by loop, it initially gets its service description of the loop as a default value. However, it can be edited as required.
7.1.4 Instrument Location
This field denotes the device’s general physical location and is selected from the Location support table. See 5.7.4 for the Location Table.
7.1.5 Line Number
This field denotes the Line Number on which the instrument is associated with. This number will generally match with line numbers from the LDT and is selected from the Line Number support table.
Examples: 2”-1FG-22108-A1-N-0 2”– Line size (2 inches) 1FG – Project phase and system 22 – Unit designator 108 – Line sequence number A1 – Pipe specification N – Insulation code 0 – Line section number
Note: The line number from LDT may include a line section number. For the exact interpretation of project line identification system designations, refer to “P&ID Overall Symbols and Legend Sheet”.
7.1.6 Commodity Code This field represents the commodity code for an instrument. This is based on the Bechtel Standard Component Numbering instruction. This code is used as part of the material requisition (MR) assignment process.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
As part of the initial INtools setup, the valid codes should have been pre-loaded into User Support Table 1 and are selected from this table. Examples: JF04 – for orifice plates JP02 – for pressure transmitters JV01 – for control valves User Support Table 1 is available in the instrument profile setup. As such, when an instrument type is defined, the appropriate commodity code should also be selected. This will then be auto-assigned when an instrument is added. Note: This field doesn’t always show up on the instrument index report depending on the report setup configuration.
7.1.7 System Locator Code This field represents the system locator code for where the instrument is being used in the plant. This code is based on the Bechtel Standard Component Numbering instruction. As part of the initial INtools setup, the valid codes should have been pre-loaded into User Support Table Number 3 and are selected from this table. Examples: AE – for Feedwater CRE – for Ethylene DK – for LNG FGM – for Main Fuel Gas While User Support Table 3 is available in the instrument profile setup, but it is difficult to pre-determine by instrument type what the appropriate system locator code should be. As such, it is not recommended to make a default selection for this in the instrument profile. Note: This field doesn’t always show up on the instrument index report depending on the report setup configuration.
7.1.8 Parent Tag This field represents the “parent” tag that an instrument is related to. For example, the parent tag for a limit switch 1-ZSO-14011 is the control valve that the limit switch is assembled to, 1-FV-14011. Data entry is made through user-defined field, UDF C41.
7.1.9 Area Locator Code This field represents the Area Locator Code for an instrument. This is normally the same as the construction planning area. Data entry is made through user-defined field, UDF C06.
7.1.10 Status This field is used to determine whether an instrument is new, existing, etc. This data is used to identify the status of the instrument. The status value is selected from the Status Support Table.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
A user-defined table (UDT 5) should be used to define the instrument supply responsibility such as: BY OTHERS, BY VENDOR, BY VENDOR-SHIP LOOSE, BY ELECTRICAL, etc.
7.1.12 MR Number This field denotes the instrument Material Requisition Number. After an instrument has been assigned to a MR in BPS, this field can be auto-populated through a data exchange with BPS. The format of this number shall be: Example. 24954-100-MRA-JV01-00001 24954-100 -represents Project job # and sub-job # MRA -represents Material Requisition document type
JV01 -represents instrument commodity type 00001 -represents MR sequence number
Prior to exchanging tags with BPS, the recommended format for the MR number that is filled in should not include the job and sub job number. This makes it easy to identify which tags have been assigned to a MR in BPS and which haven’t.
Note: Use P.O. field to enter the MR number. Do not use the “Requisition Number” field. 7.1.13 MR Item Number This field denotes the MR Item Number assignment. After an instrument has been
assigned to a MR and given an item number assignment in BPS, this field can be auto-populated through a data exchange with BPS. Data entry/import is through the field SPEC_CMPNT_PO_ITEM_NO.
7.1.14 Manufacturer
This field represents the Manufacturer of the instrument. This field is selected from the Manufacturer support table and is normally specified during the preparation of the instrument data sheets.
7.1.15 Model Number
This field represents the Model Number of the instrument. This field is selected from the Model support table and is normally selected during the preparation of the instrument data sheets.
7.1.16 Instrument Specification Sheet (Data Sheet) This field indicates the Instrument Data Sheet Number and it is assigned when preparing an instrument data sheet. While this field is listed as part of the instrument index, it is actually assigned and edited from the Specification Sheet module, not the Index module.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
Example: 24954100JVDJV0100001 24954100 -represents Project job # and sub-job # JVD -represents data sheet document type for control valves JV01 -represents instrument commodity type 00001 -represents data sheet sequence number
7.1.17 Location Drawing Number
This field indicates the Location Drawing Number for each field instrument. Data entry is made through the user-defined field, UDF C61.
7.1.18 Electrical Connection Detail This field indicates the Electrical Detail Drawing Number for each applicable field instrument. While this field is listed as part of the instrument index, it is actually assigned from the Hook-up module when assigning a tag to the hook-up.
7.1.19 Pneumatic Connection Detail This field indicates the Pneumatic Detail Drawing Number for each applicable field instrument. While this field is listed as part of the instrument index, it is actually assigned from the Hook-up module when assigning a tag to the hook-up.
7.1.20 Process Connection Detail This field indicates the Process Connection Detail Drawing Number for each applicable field instrument. While this field is listed as part of the instrument index, it is actually assigned from the Hook-up module when assigning a tag to the hook-up.
7.1.21 Heat Trace Connection Detail This field indicates the Heat Trace Detail Drawing Number for each applicable field instrument. While this field is listed as part of the instrument index, it is actually assigned from the Hook-up module when assigning a tag to the hook-up.
7.1.22 Support Detail Number This field indicates the Support Detail Drawing Number for each applicable field instrument. While this field is listed as part of the instrument index, it is actually assigned from the Hook-up module when assigning a tag to the hook-up.
7.1.23 Wiring Drawing Number This field indicates the Wiring Diagram/Report Number for each applicable instrument. Data entry is made through the user-defined field, UDF C63.
7.1.24 Loop Diagram Number
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
This field indicates the Loop Drawing Number for an instrument assigned to a loop that requires a loop drawing. While this field is listed as part of the instrument index, it is actually assigned from the Loop module when assigning a loop drawing to a loop. Any tag assigned to the loop inherits the loop drawing number assignment.
7.1.25 Piping Reference Drawing / Isometric
This field indicates the reference piping drawing or isometric drawing for each applicable instrument. Data entry is made through the user-defined field, UDF C67.
7.1.26 Notes / Remarks
This field is used by engineering or design to record miscellaneous information about an instrument. Before entering any construction specific information, this should be discussed with Construction to ensure a common understanding on the use of this field. Data entry is made through the REMARKS 1 field. This field is a 200-character wide field, however, care should be exercised on exactly how many characters are used due to the index report “spacing” constraints.
Note: The “NOTE” field in the index module. This field is a memo type field and is meant to record notes by engineering/design and retained and used internally, i.e. recommended not to be used on any reports or data exchanges.
7.2 DCS/SIS DATA DCS/SIS data are normally exported from INtools and modified into a format that is usable by the DCS/PLC/SIS configuration programs as an import file. Specific data fields from the instrument index required include: - Tag number - Loop number - Service description - Instrument type - P&ID drawing number - Instrument data sheet number Other data required by the DCS/PLC/SIS includes:
7.2.1 System I/O Type This field represents the type of signal to/from the instrument. It is automatically generated by INtools if the instrument type profile is set up correctly. The selection is from the System I/O Type support table. See 5.7.3 for typical entries.
7.2.2 Control System
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
This field represents the associated control system for an instrument. This is used to identify which tags belong with which control system. As part of the initial INtools setup, the control system values should have been pre-loaded into User Support Table Number 2 and are selected from this table. Examples: DCS – Distributed Control System, sometimes coded as JD01 PLC – Programmable Logic Controller, sometimes coded as JD02 ESD – Emergency Shutdown System, sometimes coded as JD03 1-SIS – Safety Instrumented System for Train 1 2-DCS – DCS for Train 2 User support table 2 is available in the instrument profile setup. As such, when an instrument type is defined, the appropriate system code could be pre-selected. This will then be auto-assigned when an instrument is added.
7.2.3 Control System Tag The control system tag can be auto created when an instrument tag is added to the index. This is controlled by a flag in the instrument profile. As such, there is normally a one to one relationship between a hard tag and a control system tag, which then becomes the basis for determining I/O counts.
7.2.4 Interlock Number This field is used to show the associated interlock number for applicable tags. Data entry is made through the user-defined field, UDF C35.
7.2.5 Complex Loop Document Number This field is used to show the assigned complex loop document number that describes the control scheme for a complex loop. Data entry is made through the user-defined field, UDF C36.
7.2.6 Ranges Process range information and engineering units are required to configure controllers, etc. correctly. This data is normally stored on the instrument data sheet for the field element instrument (versus the related transmitter).
7.3 Instrument Index Report The standard Instrument Index Report should include the following fields (the data attribute for the field shown in the parenthesis):
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
The instrument index report makes use of data that is available in the INtools to TEAMWorks DataBroker interface. Using MS Access, a link is made to this interface and an MS Access report form is used to print/generate the report. The INtools support team is responsible for installing the TEAMWorks DataBroker interface and the MS Access database.
A standard instrument index report (showing typical data) is depicted on Appendix F.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
Any deviations to the standard report format should be documented in the INtools PWI. Once approval is obtained, the project needs to co-ordinate with the INtools BSAP support team to implement the actual required changes/customization.
7.4 I/O Listing If practical the control system (such as DCS, SIS, PLC, etc.) should be defined as part of the instrument profile. The I/O type can also be auto-assigned when adding tags if it is already defined as part of the instrument profile. An I/O summary report (coordinated the format with the INtools Support Group) can be generated for the estimating purpose at the early stage of the project. Normally the following fields should be included on the I/O listing:
• AI, 4-20 mA
• AI, Smart
• AO, 4-20 mA
• T/C Input
• RTD Input
• DI, 24VDC
• DO, 24VDC SOLID STATE
• DO, 24 VDC RELAY
• DO, 120VAC RELAY
The I/O redundancy requirements should be noted to each type signal wherever applicable.
During the EPC phase the following data should be completed to support DCS/SIS engineering and configuration work:
• Tag Number
• Control System Tag Number (ID used for DCS, SIS, etc.)
• P&ID Number
• I/O Rack Location
• Field JB Number (preliminary – assigned by designers)
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
The DCS/SIS engineers will use the above information and feed back the following items back to support the design work:
• Control System Tag Number (real name)
• Control System (after check/verification)
• Controller Name (use a UDF to define)
• Controller Cabinet Number
• Rack/Box/Chassis Number
• Slot/Card Number
• Channel/Subslot Number
• Strip/FTA Card Name
Close coordination between the DCS/SIS engineering group and the design group during the EPC phase are essential. Some items listed above are also system dependent based on the vendor selection.
An I/O Summary Report is generated using the I/O listing data. The actual counts are done dynamically/automatically using a custom INtools database view. Using MS Access, a link is made to this view and an MS Access report form is used to print/generate the summary report. The INtools support team is responsible for installing the custom INtools database view and the MS Access database that contains the standard I/O Summary Report form.
A standard I/O Summary Report (showing typical data) is depicted on Appendix G.
Any deviations to the standard I/O Summary Report format should be documented in the INtools PWI. Once approval is obtained, the project needs to co-ordinate with the INtools support team to implement the actual required changes/customization.
7.5 MR Listing Once Tag Number, MR Number, and Type of Instrument have been entered to the Index Module a MR listing can be generated for the estimating purpose.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
7.6 Alarm Summary Alarm summary is a document to list all the tags with alarm set points. For DCS the alarms are normally resided with the controller tag and the indication tag. For SIS they should reside with the field input tag. For discrete switches such as PSH show the discrete tag PAH. The report format should have the following information:
• Tag Number
• Process Case Name (if applicable, optional)
• System Type (i.e., 1-DCS, 1-SIS, etc., optional)
• Low Range Limit
• High Range Limit
• Units of Measurement (engineering units for flow, pressure, temperature, and percent for level in general)
• HHH, HH, H, L, LL, LLL set points as required (HHH/LLL can be handled by a note)
• Alarm Priority
• Other Alarms (such as “Deviation Alarm”, “Rate-of-Change Alarm”, etc., optional)
• Notes
In general vendor supplied alarms should not be part of the summary if they don’t tie to the DCS or SIS unless requested by the Client.
The alarm summary report should be generated by the Browser Module.
Refer to “Engineering Design Guide for Alarm Summary Implementation” (3DG-J42F-00002) for details.
8.0 PROCESS DATA AND CALCULATIONS
8.1 Process Data
A work process utilizing the INtools External Editor (IEE) has been established to import process data information for in-line instrumentation (valves, flow elements, etc.) from the Project Engineering discipline to the “Process Data” module of INtools. This data is in turn made available to the Specification module when creating/editing instrument data sheets. Refer to Engineering Instruction, 3DI-G04F-00014, Interdiscipline Process Data Transfer for General Service Control Valves.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
The Calculation Module can be used to perform preliminary in-house sizing calculations for flow meters, control valves, thermowells and relief valves. However, the final calculations shall be performed using the vendor sizing programs or project-approved methods.
Bechtel is not using this module due to the reason that these calculations are not validated. If the project would validate the calculations this module can be used on a project level.
Warning: Fluid properties or other data entered in the Calculation Module and any subsequent calculation results will update the instrument data sheet. As such, caution should be exercised before using the Calculation module, since these updates may have un-intended results on the instrument data sheets.
9.0 WIRING MODULE
9.1 Instrument and Equipment Wiring
Within INtools the Control Systems Design Group will establish the interconnections between all wired instruments, and instrument equipment such as racks, panels, enclosures, and terminal boxes. The Control Systems Design Group will define and manage the creation of panels of different types and terminations of all the interconnecting devices for instrument signals. The concept of a device panel is used throughout the Wiring Module to represent devices to which wires are connected (such as instruments, junction boxes, racks, enclosures, cabinets, and instrument control panels). One of the most important functions of the Wiring Module is to create cables and to establish cable-wiring connections by identifying the wires and their "from-to" connection points. The wires and the entities to which they are connected are arranged hierarchically as cables, cable sets/cable pairs, wires, and panel-terminals or strip-terminals.
9.2 Wiring Module Managers Cable and panel naming conventions must be defined first before any cables or panels are created. The Wiring Module is divided into four managers: 1) Default cable manager 2) Plant cable manager 3) Default panel manager 4) Plant panel manager
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
Wiring Module managers enable access to all the wiring entities in the plant. As part of the domain setup an initialization from the master INtools seed file, default cables and panels are created. Default panels include junction boxes, marshalling cabinets, local panels, and system panels. Default cables include single pair and multi-pair cables. The default cable information includes cable codes, service levels, gland sizes and gland type. This information is needed for the wiring and loop modules to function properly and for downloading cables to SETROUTE using Data Broker. The Control Systems Design Group will use the default panels and cables as the basis of all plant cables and panels. Creation of new plant cables and panels are done within the plant cable manager and the plant panel manager. Once completed, the plant panel manager should contain all the panels, racks, enclosures, and junction boxes defined on the system block diagrams.
9.3 Instrument Wiring Profiles
After definition of the default cables, wiring profiles are assigned to existing instrument tag numbers. Normally, as new instrument tags are added to the Instrument Index Module, wiring profiles should be assigned to the instruments. The INtools support group may assign wiring profiles globally where there are a significant number of instruments of the same type. The Instrument Type profiles with the correct cable types should be defined before any tags are input into INtools. Do NOT add instrument tags through the wiring module. The Index module shall be used for all tag additions.
9.4 Wiring Interconnections
Once wiring profiles have been assigned to the “device panels” with their respective cables and plant panels defined, interconnecting wiring of the instruments to the plant panels can be completed.
9.5 Assignment of Instruments to Junction Boxes
Use the Browser Module to Pre-assign the junction boxes to the field instruments. The jnction boxes have to be created in the wiring module plant manager before they can be selected in the Pre-assignment Browser Module. Batch load the instruments to the junction boxes that have been pre-assigned.
9.6 Create Homerun Cables
Create the Home-Run cables using the default cables and connect from the junction box to the marshalling cabinet.
9.7 DCS/SIS System Cabinets
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
Create the DCS/SIS System cabinets using the drag & drop method from the default panels. Assign the Control System tags to the appropriate I/O card.
9.8 Cross Wiring
Use the Cross Wiring option to connect from the marshalling cabinet to the I/O modules in the DCS/SIS System cabinets. After all of the marshalling panel wiring has been completed, an appropriate cross-wiring report is created and issued to the panel vendor for them to do the cross wiring. This report is generated using the Cross-Wiring interface that is installed as part of the INtools Adaptor.
9.9 Wiring Reports
INtools provides a series of reports that can be generated such as loop reports, terminal strip reports, Fieldbus segment reports, continuity check reports, cable reports, and drawing reports. Document Control generally accepts a “.PDF” file for a deliverable from Control Systems. This should be coordinated with Document Control on each project.
9.10 Color Coding Wire color codes are listed here for reference: Analog Wiring for I/O - 4-20 mA & Smart: Signal (+) Black Signal (-) White T/C, Type K: Signal (+) Yellow (Per MC 96.1) Signal (-) Red RTD: Signal (+) Black Signal (-) Red Signal (-) White Digital Wiring for I/O – 24 VDC: Signal (+) Black Signal (-) White 120 VAC: Signal (+) Black Signal (-) Red DC Power Wiring – DC (+): Black DC (-): White Ground: Green
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
AC Power Wiring – Hot: Black Neutral: White Ground: Green Signal Wiring for Foundation Fieldbus – DC (+): Black DC (-): White Jacket: Black Others – Safety Ground: Green Master Reference Ground: Green w/Yellow stripe Note: The color-coding needs to match the color code in SETROUTE.
9.11 Work Flowchart for Wiring See Appendix E for the INtools wiring work flowchart.
10.0 LOOP MODULE
Enhanced Smart Loop is the preferred method for generating Loop Diagrams. The wiring has to be completed before the loop generation process. After generation of the loop, check the completeness of the wiring and view the loop for layout of graphics. Revise the loop and save the position of the graphics and database to the required format for the project. For instrumentation used as part of a fieldbus installation, segment drawings shall be generated using the INtools segment generation feature.
11.0 HOOK-UP MODULE
11.1 Instrument Installation Details and Material Take-off The Hook-Up Module (Installation Details) provides the means of creating, viewing, and editing, the physical installation detail drawings of instruments and the fittings that are required to connect them to piping. This module provides a means of assigning instrument types to hook-up types, maintaining user definable hook-up databases, and providing the total quantity of items for procurement. Specialized reports such as the hook-up item list, tag list, and the BOM can all be printed to satisfy the needs of engineering design and procurement.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
The Hook-Up Module supports creating and managing hook-up drawing details (i.e. installation detail drawings) where one of the main objectives is to generate a BOM. A relationship is set up by linking tag numbers from the “Instrument Index” module to user-defined hook-ups. These are in turn linked to a hook-up type (five Bechtel standard hookup types and one miscellaneous). The user determines the name of each hook-up drawing based on project design specific requirements. Each instrument type should be associated with each and every hook-up type, so you can place an “NA” or appropriate hook-up number against all instrument tags. When the Hook-Ups Module is initially opened, hook-up types are defined first, followed by hook-ups, and then tag numbers. (Note: While INtools will allow it, don’t assign a tag to more than one hookup type.) The Current Item library is created in the Hook-Ups Module using the Items Libraries dialog box. This library should be created with the name “Bechtel Stock Code”. This library is populated with Bechtel Stock Codes using the Bechtel Stock Code Query Utility. Coordinate with the INtools Support Group to get this utility loaded. The Bechtel Stock Code and the other details entered such as total quantities comprise the BOM. The Bechtel Stock Code provides the item number and material description of parts associated with each Hook-Up. A Stock Code Number is a Bechtel standard identifier assigned to a bulk commodity for the purpose of facilitating procurement, material management, supplier fabrication, and construction activities. Each Stock Code identifies a commodity with a unique set of alphanumeric values. The quality of the Stock Codes data is assured by following the "Instrument Piping Material Classes". A Material Take Off (MTO) is auto-generated through an INtools Adaptor interface and downloaded/transferred via Data Broker to BPS. BPS is then used to generate Bulk Material Requisitions.
11.3 Hook-up Drawing Generation
Microstation is the method for generating Hook-Up Drawings. Prior to generation, a graphic cell for each detail must be created. Also, a border cell to be used for all hook-ups must be created. A tag set has to be placed in the graphic cell so the detail will receive the material information from INtools. Fill in the revision block information prior to hook-up generation.
12.0 SPECIFICATION (DATA SHEET) MODULE
The Specification Module provides the means to generate detailed instrument data sheets. It also incorporates data from the Instrument Index, Process Data, and Calculations modules into generated documents.
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
INtools generates instrument data sheets by utilizing pre-defined data sheet templates (forms), with which component data is associated. When you first create a data sheet for an instrument, you have to specify the form number to create the association, unless already specified in the instrument type profile when the tag was added to the instrument index. Two types of data sheets can be generated: Single-tag and Multiple-tag (“Single” to deal with a single instrument item and “Multiple” to deal with two or more instruments). Methods of handling on instrument assemblies (such as control valve equipped with solenoid valve, I/P transducer, limit switch, etc.) shall be defined. Instrument data sheets for all instruments shall be produced in INtools. Exceptions to this such as using the vendor’s data sheets for control valves shall obtain an approval from Control Systems Chief Engineer. A set of master data sheets are tabulated below: Note: Those data sheet forms marked with * are still to be developed. Precaution: Before importing the data from the vendor the exchange procedures and mappings shall be tested and certified by INtools support group.
FORM #
FORM NAME
MULTI-TAG (M)
01001 Misc Analysis Instrument
01011 Combustible Gas Monitor M
*01021 Toxic Gas Monitor
*01031 Effluent Gas / CEMS
*01041 Specific Gravity or Density Analyzer
01051 Gas Chromatograph
*01061 Oxygen Analyzer
*01071 Mass Spectrometer
*01101 Cloud, Flash or Boiling Point
01111 PH, ORP, Dissolved O2
01121 Infrared / Ultraviolet Analyzer
*01131 Oil-in-Water / TOC
*01141 Specific Ion Analyzer
01161 Sulfur Analyzer
*01181 Turbidimeter Analyzer
*01201 Vapor Pressure
*01211 Viscometer Analyzer
01221 Moisture Analyzer
*01241 BTU / Wobbe
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
Before generating any Fieldbus documents the CSEGS shall consult with the DCS group to obtain their inputs. INtools provides the ability to design and maintain the fieldbus system of a plant, starting with the creation of fieldbus tag numbers in the Instrument Index module, generation of instrument data sheets in the Instrument Specifications module and the generation of segment maps and other deliverables at the end of the process.
The Fieldbus Segment Manager provides the creation and management of Fieldbus segments, association of instruments with the appropriate segments and the creation and management of virtual tags (multi-process variable instruments).
When creating new segments, the segments are associated to the required segment-
wide parameter profile. Once the segment has been created, instruments can be associated with the segment. A Fieldbus instrument can be associated only with one Fieldbus segment. However, one Fieldbus segment can take multiple tag numbers as defined by the project. The segment association of an instrument can be changed, if needed. Before making a new segment association, the instrument will have to be disassociated from its current segment.
The fieldbus feature in the Wiring module enables the installation of a Fieldbus network
wiring and attachment of the Fieldbus control devices. INtools differentiates home-run cables from regular cables, as home-run cables propagate and connect the individual device spurs to the DCS. INtools provides the facility of defining cables as home-run, enabling these cables to be associated to segments. Termination Blocks are added to junction boxes by creating the terminal blocks based on the configured termination blocks. Where internal terminations are used, ensure that the internal terminator check box has been selected.
At the end of the process, segment-wiring drawings can be generated. 14.0 DATA INTERFACE PROCESSES
INtools is an instrumentation design and engineering software suite that includes integrated modules for instrument index, data sheet, process data, wiring, loop drawing, hook-up drawing, etc. Data is exchanged between INtools and Bechtel’s standard programs (such as TEAMWorks, BPS, Stock Code Library, and SETROUTE) using DataBroker. One of the features of DataBroker is its ability to identify data differences between applications. This information is then used to resolve the data differences, resulting in data consistency between applications. INtools Adaptor is a collection of interfaces to the other Bechtel programs in the following ways:
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
14.1 INtools to TEAMWorks TEAMWorks use a set of database tables to identify and track items for which Construction has responsibility. One of these database tables is the Instrument Table. The data basis for this table is the instrument data from INtools and essentially the same fields that make up the instrument index plus other appropriate reference data. The data exchange is implemented using DataBroker and is a one-way exchange from INtools to TEAMWorks.
14.2 Bechtel Stock Code Library to INtools The Bechtel Stock Code Library contains Bechtel standard identifiers or stock code numbers which are assigned to non-tagged commodities or goods. These stock codes are used to facilitate procurement, material management, supplier fabrication, and construction activities. The INtools Adaptor provides a stand-alone query interface to allow the transfer of selected stock code data from Bechtel’s Stock code Library to INtools’ internal stock code table.
14.3 INtools to BPS Bulk Materials Since INtools does not have a bulk material requisition module, an INtools total bulk material take-off (MTO) will be exchanged with BPS. This MTO data will form the basis for creating bulk material requisitions in BPS. This exchange of data is implemented with DataBroker and is a one-way exchange, from INtools to BPS.
Notes: The MTO is not performed directly from INtools user interface or program. It is performed automatically by the Data Broker interface between INtools and BPS.
14.4 INtools to BPS Tagged Material Requisition A DataBroker interface has been implemented to transfer instrument tag and applicable instrument data, including the data sheet reference to BPS. BPS is then used by control systems engineering to generate the tagged material requisitions. An INtools import is then used to retrieve the assigned MR and MR item numbers back from BPS. These are updated to the INtools SPEC_CMPNT_ PO_NO and SPEC_CMPNT_PO_ITEM_NO fields.
14.5 INtools to SETROUTE Bechtel’s electrical discipline is responsible for engineering and designing the cable raceway system using SETROUTE. Bechtel’s Construction also uses SETROUTE to
Electronic documents, once printed, are uncontrolled and may become outdated. Refer to the electronic documents in eEngineering for current revisions.
status and to manage the installation of instrumentation cables and terminations. To support these needs, the cable and wiring data and other related data are transferred to SETROUTE through SRBroker (a DataBroker compliant interface).
15.0 REFERENCES
3DG-J21-00004, Engineering Design Guide for Instrument Index
3DG-J42F-00002, Engineering Design Guide for Alarm Summary Implementation
3DI-G04F-00014, Engineering Design Instruction for Interdiscipline Process Data Transfer for General Service Control Valves
![[PPT]SmartPlant Instrumentation - Houston SPI LTUFspi-ltuf.org/20150805/SPI 2016 RoadMap.ppsx · Web viewDiscontinue INtools 6 INtools version 6 and versions before that will be discontinued](https://static.documents.pub/doc/80x56/5aa4596e7f8b9a7c1a8c0532/pptsmartplant-instrumentation-houston-spi-ltufspi-ltuforg20150805spi-2016.jpg)
