Dgs is 020 r0 Custody Metering Systems

TAKREER DESIGN GENERAL SPECIFICATION (DGS)

DGS-IS-020

CUSTODY METERING SYSTEMS

REV

DATE

0

MAR 2006

DESCRIPTION

BY

REVIEWED ENDORSED

APPROVED

Base Reference – Project 5601 ABU DHABI OIL REFINING COMPANY

DOCUMENT NUMBER: DGS-IS-020

Rev: 0

Date:

March 2006


Page 1 of 29

TABLE OF CONTENTS

1.0

2.0 3.0 4.0 5.0 6.0 7.0 8.0 9.0

10.0

11.0

12.0

13.0

GENERAL....... ........................................... ............................................ .............................................. ...4 ... 4 1.1 INTRODUCTION.........................................................................................................................4 1.2 PURPOSE......................................................................................................................................4 1.3 DEFINITIONS DEFINITIONS ..................................... ........................................... ........................................... ...4 ... 4 1.4 EXCEPTIONS...............................................................................................................................4 CODES AND STANDARD STANDARDS S ........................................... ........................................... ............................ 4 REFERENCE DOCUMENTS.................................................................................................................5 DOCUMENT PRECEDENCE ......................................... ........................................... ............................ 6 SPECIFICATION SPECIFICATION DEVIATION/CONCES DEVIATION/CONCESSION SION CONTROL ..................................... ........................... 6 QUALITY ASSURANCE/QUALITY ASSURANCE/QUALITY CONTROL....................................... CONTROL ....................................... .......................................... 6 DOCUMENTA DOCUMENTATION .......................................... ........................................... .......................................... 6 SUBCONTRACTORS/SUBVENDORS.................................................................................................7 HANDLING.............................................................................................................................................8 9.1 PACKAGING ACKAGING AND AND SHIPPING...................................................... ........................................ ...... 8 9.2 PRESERV PRESERVATION AND STORAGE. STORAGE............................................. ............................................ ....................................... .......... 8 DESIGN...................................................................................................................................................8 10.1 CUSTODY CUSTODY TRANSFER TRANSFER METERING DESCRIPTION........................ DESCRIPTION........................ ....................................... 8 10.2 METERING SYSTEM BASIC REQUIREMENTS REQUIREMENTS ...................................... ............................. 11 10.3 FUNCTIONAL FUNCTIONAL REQUIREMENTS........ ............................................ ........................................ 13 10.4 SYSTEM ARCHITECTURE ARCHITECTURE .................................... ............................................ ...................... 14 10.5 EXTENT OF SUPPLY SUPPLY ........................................... ............................................ ......................... 14 10.6 ENVIRONMENT ENVIRONMENTAL CONDITIONS........................................ CONDITIONS........................................ .......................................... ........ 14 10.7 SYSTEM LIFE AND AVAILABILITY AILABILITY ...................................... ........................................ ........ 14 10.8 SYSTEM HARDWARE HARDWARE DESIGN CRITERIA-GENERAL.. CRITERIA-GENERAL........................................... ......................................... ............ 14 10.9 SYSTEM HARDWARE..............................................................................................................15 10.10 INTERFACES INTERFACES ...................................... ........................................... ........................................... . 17 10.11 SOFTWARE SOFTWARE DESIGN DESIGN CRITERIA ...................................... ............................................... ........ 18 10.12 ALARMS .......................................... ............................................. ............................................ . 19 DETAILED DETAILED DESIGN DOCUMENT DOCUMENTA ATION .......................................... ........................................... .... 20 11.1 FUNCTIONAL FUNCTIONAL DESIGN DESIGN SPECIFICA SPECIFICATION TION .................................. ........................................ .... 20 11.2 DESIGN DRAWINGS DRAWINGS ........................................... ........................................... .......................... 20 11.3 DETAILS DETAILS AND DAT DATA SHEETS............................ ........................................ ............................. 21 11.4 OPERATION OPERATION AND MAINTENANCE MAINTENANCE MANUALS....................... ............................................ 21 11.5 APPLICATION APPLICATION SOFTWARE SOFTWARE DESCRIPTIONS DESCRIPTIONS ........................................ ................................ 22 11.6 SYSTEM LOG ....................................... ........................................... ......................................... . 22 INSPECTION AND TESTING ........................................ ........................................... .......................... 22 12.1 TESTING GENERAL.................................................................................................................22 12.2 PRE-FACTOR PRE-FACTORY Y ACCEPTANCE ACCEPTANCE TEST (PRE-FA (PRE-FAT)...................................... ............................. 23 12.3 FACTORY ACTORY ACCEPTANCE ACCEPTANCE TEST (FA (FAT)................................................... T)........ ........................................... ................................. 23 12.4 SHOP INSPECTION...................................................................................................................24 12.5 CERTIFICA CERTIFICATES TES OF ACCEPTANCE ACCEPTANCE ...................................... ........................................... ........ 24 12.6 SERVICES SERVICES SUPPLIED SUPPLIED BY THE VENDOR VENDOR ...................................... ........................................ 24 INSTALLA INSTALLATION TION AND PRECOMMISSIONING PRECOMMISSIONING ......................................... ........................................ 24 13.1 INSTALLA INSTALLATION TION OF EQUIPMENT........................................ ....................................... ............ 24 13.2 PRECOMMISSIONING PROCEDURE.....................................................................................24

ABU DHABI OIL REFINING COMPANY


Rev: 0

Date:

March 2006


Page 2 of 29

14.0 SPARE PARTS AND CONSUMABLES............................................... ............................................ .... 25 14.1 PHILOSOPHY ..................................... ........................................ .............................................. . 25 14.2 START-UP AND COMMISSIONING SPARES.................................... ..................................... 25 14.3 OPERATIONAL SPARES................................................. ........................................... ............... 25 14.4 VENDOR MAINTENANCE AND GUARANTEE............................................................ ........ 26 14.5 CONSUMABLES ........................................... ........................................... ................................. 26 15.0 TESTING AND CALIBRATION EQUIPMENT .......................................... ........................................ 26 15.1 EQUIPMENT PHILOSOPHY ........................................ ......................................... ................... 26 15.2 EQUIPMENT SCOPE.................................................................................................................27 16.0 PROJECT ADMINISTRATION............................................................................................................27 16.1 PROJECT PERSONNEL .......................................... ............................................ ...................... 27 16.2 PROJECT SCHEDULE...............................................................................................................27 16.3 PROGRESS REPORTING..........................................................................................................28 16.4 COORDINATION MEETINGS..................................................................................................28 17.0 TRAINING .......................................... ........................................... ............................................... ........ 28 17.1 TRAINING PHILOSOPHY ...................................... .......................................... ........................ 28 17.2 TRAINING COURSE DOCUMENTATION............................................. ................................. 28 17.3 OPERATOR TRAINING COURSE....................................................... ..................................... 28 17.4 MAINTENANCE TRAINING COURSE...................................................................................28 17.5 SYSTEM CONFIGURATION COURSE .................................... ....................................... ........ 28 17.6 TRAINING AIDS........................................................................................................................29 18.0 WARRANTY.........................................................................................................................................29 19.0 MAINTENANCE ....................................... ............................................ ........................................... .... 29 19.1 MAINTENANCE DURING WARRANTY................................................................................29 19.2 MAINTENANCE AFTER WARRANTY...................................................................................29



Rev: 0

Date:

March 2006


Page 3 of 29

1.0

GENERAL

1.1

INTRODUCTION

This specification describes the minimum requirements for the design, manufacturing, testing and application of a custody transfer metering system at the Umm Al Nar and Ruwais Refineries of Abu Dhabi Oil Refining Company (COMPANY). The metering system will track commodity and communicate with the skid’s independent microprocessor which is linked to the DCS. The custody transfer metering system will consist of metering skids and provers. 1.2

PURPOSE

This specification covers the minimum requirements for the design, materials, fabrication, inspection, testing and commissioning of the system. It is the COMPANY’s intent to utilize an independent microprocessor for each custody transfer metering system to provide quantity control, computing, and communication in a single integrated system. The independent microprocessor shall communicate with the DCS. 1.3

DEFINITIONS

For the purposes of this specification, the following definitions shall apply: CONCESSION REQUEST — A deviation requested by the SUBCONTRACTOR or VENDOR, usually after receiving the contract package or purchase order. Often, it refers to an authorization to use, repair, recondition, reclaim, or release materials, components or equipment already in progress or completely manufactured but which does not meet or comply with COMPANY requirements. A CONCESSION REQUEST is subject to COMPANY approval. DCS - Distributed Control System. SHALL — Indicates a mandatory requirement. SHOULD — The use of the word “should” indicates a strong recommendation to comply with the requirements of this document. 1.4

EXCEPTIONS

The VENDOR must adhere to the functional requirements, design criteria and system configuration contained in this document. Where there is a conflict between the requirements of this specification and the VENDOR’S current standard system/technology, this must be clearly defined in writing as an exception. This specification defines the minimum performance levels required. The VENDOR may propose alternative improved modules. 2.0

CODES AND STANDARDS

It shall be the VENDOR’S responsibility to be, or to become, knowledgeable of the requirements of the referenced Codes and Standards. The following codes and standards shall, to the extent specified herein, form a part of this specification. The latest edition in force shall apply.



Rev: 0

Date:

March 2006


Page 4 of 29

National Electrical Code (NEC) Factory Mutual (FM) International Electrical Commission (IEC) Underwriters Laboratories, Inc. (UL) National Electrical Manufacturer’s Association (NEMA) American National Standard Institute, Inc. (ANSI) Instrument Society of America (ISA) Institute of Electrical and Electronic Engineers (IEEE) International Organization for Standardization (ISO) ISO 9001-2000

Quality Management System Requirements

ISO 9004-2000

Quality Management Guidelines for Performance Improvement System

ISO 9011

Quality Management Guidelines for Performance Improvement System

American Institute of Steel Construction (AISC) 3.0

REFERENCE DOCUMENTS Project Specifications:

DGS-CU-002

Structural Engineering Design Criteria

DGS-CU-020

Material General Specification Structural Steel Fabrication

DGS-EE-012

Materials General Specification for Instrumentation and Thermocouple Cable

DGS-IE-001

Flow Instruments Specification

DGS-IS-001

Distributed Control System

DGS-IS-003

Fire and Gas Detection System

DGS-IS-010

Public Address and Intercom Systems

DGS-IS-014

Marshaling Cabinets

DGS-IS-015

System Cables

DGS-IU-001

General Instrument Specification

DGS-IU-007

Instruments Furnished with Package Units

DGS-MU-002

Preservation and Export Packing

DGS-PU-003

Material General Specification



Rev: 0

Date:

March 2006


Page 5 of 29

4.0

DOCUMENT PRECEDENCE

The VENDOR shall notify the CONTRACTOR of any apparent conflict between this specification, equipment or software functional detailed specifications/drawings, the Codes and Standards and any other specifications noted herein. The VENDOR is to prepare a tabulated list of discrepancies between any of these documents for review with CONTRACTOR. Resolution and/or interpretation precedence shall be obtained from the CONTRACTOR in writing before proceeding with the design/manufacture. In case of conflict, the order of precedence shall be stated in the AGREEMENT or other PROJECT documents as applicable. 5.0

SPECIFICATION DEVIATION/CONCESSION CONTROL

Any technical deviations to this specification and its attachments shall be sought by the VENDOR only through CONCESSION REQUEST format. CONCESSION REQUESTS require CONTRACTOR’S and COMPANY’S review/approval, prior to the implementation of proposed technical changes. Technical changes implemented prior to approval are subject to rejection. 6.0

QUALITY ASSURANCE/QUALITY CONTROL

The VENDOR shall have in effect at all times, a QA/QC program which clearly establishes the authority and responsibility of those responsible for the quality system. Persons performing quality functions shall have sufficient and well defined authority to enforce quality requirements to initiate, identify, recommend and provide solutions to quality problems and verify the effectiveness of the corrective action. VENDOR’S proposed quality shall fully satisfy all the elements of ISO 9001 - 2000 and ISO 9004 - 2000. The quality system shall provide for the planned and systematic control of all qualityrelated activities performed during all phases. Implementation of the system shall be in accordance with the VENDOR’S Quality Manual and Project Specific Quality Plan, which shall both together with all related/referenced procedures, be submitted to the COMPANY for review, comment and approval. The VENDOR shall identify in purchase documents to its SUBCONTRACTORS all applicable QA/QC requirements imposed by the COMPANY, and shall ensure compliance thereto. On request, VENDOR shall provide objective evidence of its QA/QC surveillance of its SUBCONTRACTORS activities. If selected SUBCONTRACTORS have ISO 9001-2000 or ISO 9002 certification, as required for contracted scope, then copies of these certifications are to be provided for COMPANY review. The COMPANY and CONTRACTOR may elect to waive their audits in favor of ISO 9001-2000 register audits. Any contracted service not covered and not having ISO 9000 certification will be subject to COMPANY and CONTRACTOR audit requirements. 7.0

DOCUMENTATION

VENDOR shall submit the type and quantity of drawings and documentation for CONTRACTOR'S authorization or information as listed in the individual Purchase Orders. Refer to section 11.0 for a description of the minimum detailed design documentation that is required to be supplied by the VENDOR.



Rev: 0

Date:

March 2006


Page 6 of 29

Mutual agreement on scheduled submittal of drawings and engineering data shall be an integral part of any formal Purchase Order. Comments made by CONTRACTOR on drawing submittal shall not relieve VENDOR or SUBVENDORS of any responsibility in meeting the requirements of the specifications. Such comments shall not be construed as permission to deviate from requirements of the Purchase Order unless specific and mutual agreement is reached and confirmed in writing. Each drawing shall be provided with a title block in the bottom right-hand corner incorporating the following information: •

Official trade name of the vendor.

•

VENDOR'S drawing number.

•

Drawing title giving the description of contents whereby the drawing can be identified.

•

A symbol or letter indicating the l atest issue or revision.

•

PO number and item tag numbers.

•

TAKREER Logo.

Revisions to drawings shall be identified with symbols adjacent to the alterations. A brief description in tabular form of each revision shall be given, and if applicable, the and date of the revision shall be listed. The term "Latest Revision" shall not be used. Additionally, all final system design documentation shall be provided in electronic format. All project specific system design drawings shall be provided in AUTOCAD file format. All project specific design specifications produced shall be provided in Microsoft Word format. All project database information shall be provided in Microsoft Access format. Additionally, it is desired to have as much system documentation as possible available on CD-ROM with search and retrieval capabilities. Documentation specifically developed for the Project shall be provided in CD-ROM read/write format while vendor standard documentation may be provided in read only format. VENDOR shall advise the extent of provided hardware and operating software covered by documentation in this manner. 8.0

SUBCONTRACTORS/SUBVENDORS

The VENDOR shall assume unit responsibility and overall guarantee for the equipment package and associated equipment. The VENDOR shall transmit all relevant Purchase Order documents including specifications to his SUBVENDORS and SUBCONTRACTORS. It is the VENDOR'S responsibility to enforce all Purchase Order and Specification requirements on his SUBVENDORS and SUBCONTRACTORS. The VENDOR shall submit all relevant SUBVENDOR and SUBCONTRACTOR drawings and engineering data to the CONTRACTOR. The VENDOR shall obtain and transmit all SUBVENDOR and SUBCONTRACTOR warranties to the CONTRACTOR/COMPANY, in addition to the system warranty.



Rev: 0

Date:

March 2006


Page 7 of 29

9.0

HANDLING

9.1

PACKAGING AND SHIPPING

Preparation for shipment shall be in accordance with the VENDOR'S standards and as noted herein. VENDOR shall be solely responsible for the adequacy of the preparation for shipment provisions with respect to materials and application, and to provide equipment at th e destination in ex-works condition when handled by commercial carriers. Adequate protection shall be provided to prevent mechanical damage and atmospheric corrosion in transit and at the job site. Preparation for shipment and packing will be subject to inspection and rejection by COMPANY'S/CONTRACTOR'S inspectors. All costs occasioned by such rejection shall be to the account of the VENDOR. Equipment shall be packed, securely anchored, and skid mounted when required. Bracing, supports, and rigging connections shall be provided to prevent damage during transit, lifting, or unloading. Separate, loose, and spare parts shall be completely boxed. Pieces of equipment and spare parts shall be identified by item number and service and marked with CONTRACTOR'S order number, tag number, and weight, both inside and outside of each individual package or container. A bill of material shall be enclosed in each package o r container of parts. One complete set of the installation, operation, and maintenance instructions shall be packed in the boxes or crates with equipment. This is in addition to the number called for in the Purchase Order. 9.2

PRESERVATION AND STORAGE

Equipment and materials shall be protected to withstand ocean transit and extended period of storage at the job site for a minimum period of 18 months. Equipment shall be protected to safeguard against all adverse environments, such as: humidity, moisture, rain, dust, dirt, sand, mud, salt air, salt spray, and sea water. All equipment and material shall be preserved and export packed in accordance with Project Preservation Specification, DGS-MU-002. 10.0

DESIGN

10.1

CUSTODY TRANSFER METERING DESCRIPTION

The custody transfer metering system shall be considered as two major sub-systems. They are: •

The field mounted skid including the master meter proving equipment

•

The microprocessor based control system flow computer/prover control

The metering system shall provide measurement accuracy for accounting purposes for mass and volumetric quantities and the flow rates of product. It shall incorporate sufficient parallel meter runs to enable the maximum and minimum flow rates to be measured at the specified accuracy.



Rev: 0

Date:

March 2006


Page 8 of 29

Each metering skid operates as an independent unit with a microprocessor based control system flow computer/prover control communicating with the DCS. The skid flow computer/prover control will be located in the nearest Satellite Instrument Shelter (SIS) or control building. For earthing purposes, skids shall be provided with two (2) M10 bolts. These shall be located diagonally at opposite corners. 10.1.1

Metering Overview Each custody transfer metering system shall have an inlet valve, filter, straightening vanes dual pulse flow meter, electronic smart pressure and temperature transmitters, stream flow control valve, isolation valve, and a thermal relief valve. The flow meter is the primary element in the metering system. The pulses generated by the flow through the meter will be logged in the skid microprocessor. The pressure, density and temperature of the fluid will also be logged in the skid microprocessor. The isolation valves on each unit are motorized to enable product routing. A filter and straighten vanes shall be provided at the inlet of the flow meters as required by the VENDOR. The flow control valve at the outlet of the skid will control the quantity of product released. There will be two types of meter proving systems; loop prover for custody transfer outside of the COMPANY’S affiliates and “Master Me tering” for within the COMPANY’s affiliates. The loop prover shall be a bi-directional mechanical displacement meter prover or a compact volume prover. The master meter system consisting of a “Master flowmeter” verifies the custody transfer calibration. The master flow meter must be proved by a conventional pipe prover or by using a gravimetric prover in a laboratory at periodic intervals. The inlet and outlet valves for both meter proving systems shall have open and closed position switches for remote indication. There will be a common loop prover/master meter for each skid.

10.1.2

Custody Transfer Metering Operation For general metering operations, the DCS shall download the flow rate to the skid microprocessor based flow computer/prover control. The DCS shall issue a signal to indicate that the downloaded rate was confirmed. The skid flow computer/prover control shall adjust the outlet flow control valve accordingly.

10.1.2.1

Custody Transfer Batch loading The following is a general outline of requirements for batch loading. The CONTRACTOR shall customize the details as required. The DCS issues a "Reset Permissive" command which allows the flow computer/prover control to reset the registers, including the flow control system manual loader to zero and to accept reset figures for the batch totals.



Rev: 0

Date:

March 2006


Page 9 of 29

The DCS issues an "Inlet Valve Open" command which indicates to flow computer/prover control whether the "Batting" or "Bypass" mode has been selected. The flow computer/prover control then relays the "Valve Open" signal to the appropriate valve and awaits confirmation of the valve status switches, before continuing the sequence. In the batch mode, the sequence continu es as follows: The DCS downloads to the flow computer/prover control, the following batch parameters: •

Initial quantity

•

Normal quantity

•

Top-off quantity

•

Initial flow rate

•

Normal flow rate

•

Top-off flow rate

•

Ramp-up rate

•

Ramp-down rate

The DCS shall issue a signal to indicate that the downloaded parameters are confirmed. The flow computer/prover control then: Relays a "Valve Open" signal to the stream isolation valve and awaits confirmation of valve status from the valve status switches, before continuing the sequence, and simultaneously relays a "Valve Open" signal to the stream outlet valve and awaits confirmation of valve status from the valve status switches, before continuing the sequence. The flow computer/prover control issues a "Batch Ready to Start" signal to the DCS, indicating that all valves are correctly aligned and that the system is held by control valve(s) awaiting instruction. At the operator's discretion, the DCS then issues a "Batch Start" command initiating the batch sequence. During the running of this sequence the flow computer/prover control issues a signal to the DCS indicating if flow has exceeded the set flow rate. The flow computer/prover control will automatically "temporarily" stop or pause the batch when the Total Top-off Quantity is reached. At the Operator's discretion, the DCS issues a "Batch Continue" command which indicates to the flow computer/prover control to continue loading at the previously set top-off rate until a further "Pause" or "Batch Stop" command is issued by t he DCS. 10.1.2.2

Meter proving operation When the flowing conditions demand, the meter proving sequence commences. This happens either automatically or on operator authorization dependent on whether the authorization to prove is in "auto" or "manual" mode . It then waits for keypad or DCS authorization. A proving sequence interlock system initiates an adjustable timer which is set to allow for the completion of valve travel.



Rev: 0

Date:

March 2006


Page 10 of 29

If the movement completion is not confirmed by the valve position switches within the set time period, an alarm is raised and any further commands to move other valves in the set sequence is inhibited. Irrespective of the selected proving mode, the proving sequence is inhibited until stabilization of the flow, temperature and pressure has been established. Proving functions proceed automatically, controlled by the flow computer/prover control microprocessor which also initiates the sphere launching, by controlling the position of the fourway diverter valve and the sequencing of the proof runs. A maximum of ten proving runs will be undertaken, automatically stopping after five successful runs. Unstable conditions or the initiation of any relevant alarm automatically aborts the proving cy cle. In all cases control valves have been installed in the discharge header to provide the necessary back-pressure for the correct operation of the meters and prover, they also control the overall through-put of the metering skid. These valves are controlled by the skid microprocessors. The setpoint signal for the overall flow control can be received from DCS via a redundant serial link. 10.2

10.2.1

METERING SYSTEM BASIC REQUIREMENTS

The system shall be capable of monitoring the metering operation and shall be simple to operate and maintain. All functions defined in this specification shall be performed in an integrated cohesive manner. The architecture of the system must accommodate both functional and geographical distribution of the hardware and the software. The VENDOR shall clearly identify any design which is nonstandard or does not have a history of at least one working installation of at least 10,000 hours of life. The systems shall include only completed, tested and operational programs that are fully documented and described clearly.

10.2.2

The microprocessor flow computer/prover control shall be specially designed to meet international standards for fiscal metering and be engineered for the highest standards of reliability and capable of interfacing with primary devices to provide readout of meter run parameters and data in the units prescribed in this specification. As a minimum the microprocessor shall be capable of performing the following functions: •

•

•

Receive dual pulse train signals from its associated meter and with the use of the “K” factor, calculate the run flowrate and total in accordance with industry standards. Receive line temperature, pressure and header density, with which it will calculate mass flow rates, mass totals and correct the volume flow rates and totals to standard conditions. Monitor for pulse discrepancy and provide transmission integrity in accordance with API Manual of Petroleum Measurement Standards, Chapter 5 Section 5 Level A and initiate an error counter and alarm on receipt of impaired pulses.



Rev: 0

Date:

March 2006


Page 11 of 29

10.2.3

The flow meter shall conform to the following requirements: Linearity of each meter shall be better than + 0.25% over a 10:1 flow range at the specified operating viscosity. The meter shall be calibrated initially by an independent authority. Viscosity performance shall be established when the meters are in operation. The repeatability under stable conditions shall be better than + 0.05% of the mean pulse count. This shall be checked for several different flow rates within the specified 10:1 range.

10.2.4

The prover connection shall be downstream of the flow meters. The number of meter pulses generated over calibrated volume shall be not less than 10,000 pulses. For the loop provers, the resolution of the detector and sphere system shall be compatible with this requirement. The sphere velocity shall not exceed 3 m/s. The length between detector switches (or round trip length for bi-directional provers) shall be at least 10,000 times the detector repeatability.

10.2.5

The custody transfer metering instrumentation and piping shall adhere to the General Instrument Specification, DGS-IU-001, the general specification for Instrumentation Furnished with Packaged Units, DGS-IU-007 and the material and rating requirements of the piping line class in accordance with the Material General Specification, DGS-PU-003.

10.2.6

All field mounted electrical/electronic instruments installed in hazardous areas shall be certified for use in such locations.

10.2.7

Electric motor operated valves shall comply with the electrical area classification, integral reversing start, open and close limit switches geared to the valve stem drive mechanism, integral control transformer, open close, and stop push butto ns, open and close indicator light, hand-offauto switch, and interposing control relay. Mechanical valve position indicator shall be provided on motor operated flow control valves.

10.2.8

If required, each filter shall have a differential pressure gauge with local indication and an electronic transmitter for a remote alarm. The CONTRACTOR shall determine the necessity of the filters and shall proceed with COMPANY approval.

10.2.9

If straightening vanes are required, minimum upstream and downstream run lengths shall be 10D and 5D respectively, where D is the inside di ameter of the run. The CONTRACTOR shall determine the necessity of straightening vanes and s hall proceed with COMPANY approval.

10.2.10

The pressure drop value shall include all items of equipment in the system between the two terminal piping flanges. The VENDOR shall provide written data in the form of a calculation sheet, detailing the components of the system to substantiate compliance.

10.2.11

All instruments and piping components shall be accessible for operation and maintenance as per project specification DGS-IU-001 General Instrument Specification, Instrument Access and Visibility Table. The skid shall be fitted with lifting lugs, which will be clearly marked, and sling attachments. Certified slings and spreader beams shall be included.



Rev: 0

Date:

March 2006


Page 12 of 29

The VENDOR shall define the “skid datum point: to which all dimensions on the skid, its pipe work and all accessories shall be referred. Spool pieces shall be included in the pipe work to facilitate inspection and removal of equipment as required. Spool pieces shall be provided for replacement of in-line instruments during pipe flushing pressure testing. Drip trays shall be installed under all metering runs and under the working areas of the master meter loop which are likely to see spillage. 10.2.12

Structural steel work design shall be in accordance with AISC and Project Specification DGS-CU-002. Steelwork detailing and fabrication shall comply with Project Specification DGS-CU-020.

10.3

FUNCTIONAL REQUIREMENTS

10.3.1

The custody transfer metering system shall provide the following functions •

•

•

•

•

•

•

•

10.3.2

Security: Provide password protection to control level of access for operator, shift supervisor, and clerical staff. Access Control: Control operators’ access to the prover control. Operator Interface: Provide clear and easy to use CRT/keyboard based operator interface. Receive and act on keyboard commands. Provide overview of metering systems and details on flow Supervisor Interface: Provide clear and easy to use CRT/keyboard based interface. Allow addition, deletion, and modification of data related to loading. Transaction Recording: Record all product movement. For example; record when and how much product was moved and why. Flow metering: The microprocessor shall provide mass and volume based flow control. The flow (quantity) control shall be 0.1% accurate or better. The DCS shall supervise the flow computer/prover control and load the flow quantities. Database management: Compile data in an agreed format and feed it to a dedicated printer either at specified times or on demand from the operator. Form a database of selected alarms, measured and calculated variables. Fallback/redundancy: All critical components shall be redundant.

Si units of measurement shall be used for the metering system. MEASURED VARIABLE

UNIT

Pressure

kg/m2

Temperature

°C

Density

kg/m3

Flowrate - Normal

Nm3/hr

Flowrate

m /hr

Flowrate (Mass)

Tons/hr

3



Rev: 0

Date:

March 2006


Page 13 of 29

10.4

SYSTEM ARCHITECTURE

The system architecture shall be in accordance with the DCS specification, DGS-IS-001. 10.5

EXTENT OF SUPPLY

The VENDOR must provide the custody transfer metering system hardware, system software, application software, and services required to make the system functional. When applicable, the vendor shall interface with the DCS vendor to arrange the data links and protocol necessary for monitoring of the metering systems. The VENDOR shall, at all stages, inform the CONTRACTOR immediately if there is doubt on the specified requirements. 10.6

ENVIRONMENTAL CONDITIONS

All system components shall be able to be stored at the site ambient (noncondensing) conditions without adverse effect. 10.7

SYSTEM LIFE AND AVAILABILITY

The custody metering control will be part of the DCS. Refer to the corresponding section in the DCS specification, DGS-IS-001. 10.8

SYSTEM HARDWARE DESIGN CRITERIA-GENERAL

10.8.1

System shall incorporate precious metal plating of component lead wiring, connectors, etc. System construction shall not use techniques which are particularly prone to damage by corrosive atmospheric pollutants, e.g., wire wrapping. The hardware shall be tropicalized .

10.8.2

System status display selection capability and continuous system alarm monitoring shall be provided on the operator console.

10.8.3

System shall be simple and flexible with regard to reconfiguration of loop connection and display formats to suit changes in operational requirements. The system must have the capability to be totally reconfigured on-site with the hardware and software system supplied. System software security, including database configuration and controller loop tuning parameters, is preferred to be accessible by keylock. However, a system of password access is acceptable if a keylock scheme is not practical.

10.8.4

System shall be able to support, and VENDOR shall be able to supply, and warrant all requested peripheral devices.

10.8.5

Systems shall be subject to rigorous quality assurance and testing programs at all stages of manufacture. This shall include a full function test of the complete system prior to acceptance testing. Quality assurance and testing shall be designed to simulate as closely as possible local conditions, and shall preferably conform to ISO 9000 QA/QC procedures.



Rev: 0

Date:

March 2006


Page 14 of 29

10.8.6

Redundant communication data links, where specified, shall be provided between devices on the highway. Both data links shall be continuously monitored and failures alarmed as a system alarm. Changeover from one data link to the other in case of failure of one shall be automatic and shall not interrupt terminal operation.

10.9

SYSTEM HARDWARE

For all system hardware shall be in accordance with the DCS specification, DGS-IS-001, unless specified in this specification. 10.9.1

Microprocessor flow computer/prover control The flow computer/prover shall as a minimum provide the following functions: Input/output channels for the flow meter, control valves, temperature and pressure transmitters, etc. 15% spare input/output channels for each type of I/O. A function keypad or push buttons for START, PAUSE, RESUME, and STOP functions. An alphanumeric display with 4 lines of 40 characters (or more) to display instructions and status information to the operator. Loading interlock logic and flow control. Interface with the DCS system. Display valve status and selected parameters. Display an index of all the commands and functions available to the operator. Permanently display metering skid mass flow with sufficient digits to accumulate three month’s maximum design flow without roll-over. Display on demand the station daily totalized flow. The flow computer/prover control shall have the capability of being configured and tuned from any console, or from a local configuration unit. Each module shall have on board diagnostics, with on board LED indicators, defining status. Upon malfunction of flowmeter, it shall stop loading operation. Upon malfunction of flow control valve in open position, the DCS shall trip (stop) the loading pumps and require operator to manually override the trip before resetting the trip. The configuration loaded into the microprocessor shall be held in non-volatile memory to maintain critical parameters for at least 30 days on failure of the AC power supply. An integral battery back-up with “low charge” alarm to provide this facility is acceptable.



Rev: 0

Date:

March 2006


Page 15 of 29

10.9.2

Network Interface The custody transfer metering system shall provide hardware and software for interfacing and communicating with the following devices through computer network(s). •

10.9.3

10.9.4

Distributed Control Systems

Field Instrument Wiring a.

Wiring shall be in accordance with the Materials General Specification for Instrumentation and Thermocouple Cable (DGS-EE-012).

b.

All signal wire shields shall be drained to a heavy earth bus (isolated earth) at the power supply side.

c.

All wire ends shall be identified with permanently attached (shrink on tubing) tags showing wire identification and loop number, and terminal details.

d.

Field cables to rack-mounted equipment shall enter from the bottom in such a manner so as not to block service or maintenance.

e.

Digital inputs shall have individual indicator fuses at the terminal strips or on the I/O Modules.

f.

Each terminal shall hold only one wire. Jumper straps especially designed for the block must be used if more than one wire requires connection to a common point. Raceways shall be designed to segregate input/output signals of different voltage levels, and must accommodate all cables without overflow.

g.

The equipment will normally be installed so that terminals and all electronic equipment are accessible from the front of the cabinet. A plan drawing showing accessibility to all system and marshaling cabinets will be furnished to the VENDOR by CONTRACTOR.

h.

VENDOR’S standard internal wiring conductor identification method shall be submitted for CONTRACTOR approval.

Data Communications The system shall be furnished with a reliable data communications system. The following features shall be provided as a minimum: a.

Communications diagnostics are to be continuous such that a failure is alarmed in the minimum time.

b.

Each node shall have message checking capability; detection and alarm of node failure shall be within one second.

c.

“Software” points shall be capable of being passed no de to node.

d.

Failure of one or more node(s) will not degrade the communication.

e.

Positive acknowledgment of all messages transmitted.

f.

Any measured or calculated variable in one part of the system shall be available to any other node in the system without hardwiring.



Rev: 0

Date:

March 2006


Page 16 of 29

10.9.5

Communication Efficiency An industry standard open communications protocol (such as TCP/IP) shall be used. A diagnostic routine shall be included to monitor the highway performance and log, on request the accumulated number of errors over a specified time period. VENDOR shall fully document data protocols and diagnostics.

10.10

INTERFACES

10.10.1

DCS Interface Communication with the DCS shall be through a dual redundant multidrop configured bidirectional serial data interface utilizing modbus RTU protocol. Data transmission to DCS shall be a combination of b oth single and double precision format.

10.10.2

Operator Interface and Displays The operator interface shall be provided by workstations which permit the operator to control and monitor the metering system. From the operator’s workstation it shall be possible to view all the information required to control the metering system and to change all parameters except those specifically reserved for engineering/ programming change, such as alarm set points, controller tuning, etc. Engineers shall be able to configure the system, develop graphics, monitor the system, and load/save I/O points to related databases. All data entry and operator commands shall be subject to two steps of operating action so as not to cause any inadvertent actions. The operator workstation shall provide screens for individual metering loading overview. The workstation shall provide detail point display capability to show all the relevant information for one point on the screen. The workstation shall provide capabilities for real time and historical trends as follows: a.

Real time trend: The real time trend shall be for a minimum of 1 hour at a sampling rate of 1 second.

b.

Historical trend: The historical trend shall be for a minimum period of 120 hours. Historical data shall be stored on a nonvolatile memory device such as hard disk. It shall be able to be archived and subsequently recalled.

When an analog variable exceeds an alarm limits or a digital variable signal is in an abnormal status, there shall be an alarm indication on the screen. The sequence shall comply with ISA S 18.1A codes. The operator workstation shall provide an alarm list. The alarm list shall store the latest 100 terminal alarms and alarm resets. Alarms shall be associated with a predefined alarm priority level which ranges from 1 to 4 and shall be presented on the screen according to this priority basis. By pressing one key, the operator shall be able to go directly to the relevant screen/page (predefined) or to the screen which handles the alarms of hi ghest priority.



Rev: 0

Date:

March 2006


Page 17 of 29

The alarms shall be systematically printed by one of the dedicated printers. Each screen and printout shall show the time (hours, minutes, seconds) when the alarm and the alarm reset occurred, the type of alarm (high, low, etc.), the description, the alarm group and the operating group with which the alarm is associated. The workstations shall be capable of displaying the system diagnostics. 10.11

SOFTWARE DESIGN CRITERIA

10.11.1

General The VENDOR shall provide the necessary software system which will enable integration with the system hardware, be easy to configure and reconfigure by nonspecialist personnel and shall be considered as “part of the system” for system availability calculations. Software system shall include operating system(s), communication software and database management and interfaces with the DCS.

10.11.2

Database The database is expected to store information related to customers, tankers, schedule, custody transfer transactions, inventory, and alarms/events. The VENDOR shall discuss metering operations in detail with the COMPANY prior to finalizing database definition. The database definition shall be normalized. Table indexes and relations between tables shall be set up to speed database queries and report generation. Data validation rules shall be defined as part of database definition as much as possible. Database access shall be efficient with small or large sizes of various database tab le. As a minimum, the database shall calculate and/or indicate on the front display of the microprocessor flow computer/prover control, the applicable parameters and totals listed below. Calculation shall be in accordance with the API Manual of Petroleum Measurement Standards. •

Liquid Volume Total

•

Standard Liquid Volume Total

•

Standard Liquid Volume Flow rate

•

Liquid Volume Flow Rate

•

Liquid Volume Flow Rate Hi Limit

•

Liquid Volume Flow Rate Low Limit

•

Temperature

•

Pressure

•

Density

•

Density Hi Limit

•

Density Low Limit

•

K Factor

•

Proved Flow Rate



Rev: 0

Date:

March 2006


Page 18 of 29

10.11.3

Application Programming The base application program should already be developed, documented, tested, and deployed. It may need to be configured or may need minor modifications to meet the requirements of this specification. The database table fields, relations, indexes, and business rules should be defined within the database engine or database front end tools as much as possible. The database model should be well documented. The database reports should be configured. The access application program files (including database definition, data entry screen design, report design, etc.) shall be password controlled.

10.11.4

Control Functionality The flow computer/prover control shall provide capabilities for regulatory control, discrete control, and batch/sequence control. The metering points shall be able to be connected to other points in the system through software configuration tools. The following software functi ons are a minimum for regulatory control:

10.11.5

•

Input Monitoring.

•

PID control.

•

ON/OFF control.

•

Totalizing/integration.

•

Multiplication/division, common and natural logarithms.

•

Boolean functions: AND, OR, NAND, NOR, XOR and NXOR.

•

Logic functions: switch, compare, bi-directional delay, on/off, etc.

•

Valve control.

•

User defined algorithms.

Sequence Programming The custody transfer metering system must have provision to develop sequences and must be capable of being programmed directly from logic flowcharts using an operator-oriented language. It must have the following minimum features:

10.12

•

Be programmable from logic diagrams, ladder logic, Boolean, etc.

•

Have internal (software) timers and counters.

•

Be capable of continuous monitoring of program execution.

ALARMS

The custody transfer metering system shall comply with the corresponding section in the DCS specification, DGS-IS-001.



Rev: 0

Date:

March 2006


Page 19 of 29

10.12.1

Report Generation The metering systems shall be capable of producing hard copy reports. All the current metering information required for these reports shall be available, on demand, for transmission or automatically transmitted via a serial link, to the DCS to enable hard copies to be produced in the control room as required. Each metering flow computer/prover control system shall be capable of downloading current metering and alarm data which is held in memory via the serial link, to the DCS. This information shall be available in the memory until overwritten by new data from any future runs or periods irrespective of whether the information has been requested by the DCS or not. The following is a list of available reports: •

Loading report.

•

Batch transfer report.

•

Daily metering skid report.

•

Interim skid reports.

•

Metering proving reports.

•

Alarm report.

•

Current daily status report.

•

Seven day mass totals.

•

Parameter reports.

11.0

DETAILED DESIGN DOCUMENTATION

11.1

FUNCTIONAL DESIGN SPECIFICATION

Following the purchase order, the VENDOR shall respond to this specification with a Functional Design Specification, detailing his interpretation of the custody transfer metering specification and describing complete functional operation of the system. It shall include architecture block diagrams and operations flowcharts. This document will be analyzed by the CONTRACTOR. Technical review meetings will be held to resolve outstanding testing installation and commissioning issues on the custody transfer metering system. 11.2

DESIGN DRAWINGS

All system drawings shall be prepared and submitted in accordance with recognized standards. Every effort shall be made to minimize the total number of drawings prepared by use of common drawings, where practical, without loss of clarity. 11.2.1

Drawings for Approval Prior to the start of manufacture, the VENDOR shall submit all drawings for CONTRACTOR approval.



Rev: 0

Date:

March 2006


Page 20 of 29

11.2.2

As Built Drawings Before completion of the final Site Acceptance tests, the VENDOR shall issue a complete set of updated drawings incorporating all modifications, additions or other changes that have taken place during manufacture and site precommissioning. Each drawing shall be clearly marked “as-built” and dated.

11.3

DETAILS AND DATA SHEETS

The VENDOR shall also supply the following document. •

Lists of all equipment items giving ty pe, manufacturer, etc.

•

Equipment layout drawings.

•

Cabling, wiring and interconnection drawings.

•

Interface specifications and input/output summaries.

•

Communications requirements.

•

Definition of operation procedures, lists of commands, pages and printouts.

•

Lists of all applications modules (descriptions and basic flowcharts).

•

List of all spare parts, tools, test equipment and installation materials.

•

List of preliminary maintenance requirements.

•

•

11.4

The packing and transportation specification with preliminary quantities, dimensions and weights. Recommended routine maintenance schedule.

OPERATION AND MAINTENANCE MANUALS

A Project Manual shall be provided which shall include, but not be limited to the following documents: •

VENDOR’S standard manuals for operation, configuration, installation, and maintenance as applicable to the system.

•

The approved COMPANY supplied Project Specification(s).

•

Drawings and schematics sufficiently detailed to permit diagnostics.

The suggested Project Manual structure and arrangement is as follows: •

Operating Procedures

•

System Hardware Description

•

System Software Description

•

Repair, Test and Maintenance for:

•

Spare parts, Tools, and Test Equipment for:

•

Drawings

•

System Software Documentation

•

Training



Rev: 0

Date:

March 2006


Page 21 of 29

NOTE: The VENDOR shall follow his standard practice provided this meets the intent of the above requirements. “As-built” revisions for each volume shall be prepared and final issue submitted not more than four weeks after completion of th e factory acceptance tests. Any information/data revised during Site Acceptance testing or precommissioning shall be provided at the completion of the availability test. 11.5

APPLICATION SOFTWARE DESCRIPTIONS

The system Software Descriptions shall be complete and follow the format given below: 11.5.1

Program Description For every software module a full written description of its objectives and functions shall be provided. It shall be in sufficient detail to allow a person with no prior knowledge of the system to determine the function of each module.

11.5.2

General Flow Diagrams This shall provide, in standard symbols, flow diagrams for the total system, indicating the flow of information between the various software modules and all external devices.

11.5.3

Basic Equations A full description of the basic equation and calculation procedures (where applicable) used in the system shall be provided. This shall be cross referenced to the modules in which the equations are used and the calculations carried out.

11.5.4

System Editing The VENDOR shall provide all information required to carry out editing and loading of configuration information into system libraries. A full description shall be provided in the techniques required to amend existing configuration and replace old versions in the system. A separate list of editing feature (adding/deleting for points, CRT pages, microprocessor configuration, etc.) shall be included, defining what can be done on line, on the Operator Console, and what must be developed off line on the Engineering Workstation.

11.6

SYSTEM LOG

A system log shall be maintained with the syste m by COMPANY/VENDOR from the time system integration starts, through the Factory Acceptance Test, through the Site Acceptance Tests and on the through the warranty period. The system log notes the date of occurrence of the problem, who reported the problem, summary of the problem, problem reports number, and action taken to correct the problem, kept in chronological order. 12.0

INSPECTION AND TESTING

12.1

TESTING GENERAL

The section defines the responsibilities of the VENDOR in performing the inspection and testing of the system.



Rev: 0

Date:

March 2006


Page 22 of 29

The VENDOR shall be responsible for inspection and quality assurance of the materials and standard of workmanship furnished. Testing will be carried out and witnessed by the CONTRACTOR and COMPANY representatives at various stages as the custody transfer metering system equipment is manufactured and assembled, at locations detailed below. a.

Pre-Factory Acceptance - conducted at the manufacturing facility of the custody transfer metering system VENDOR.

b.

Factory Acceptance Test - as below.

c.

Staging Acceptance Test - conducted at the staging facility nominated by the VENDOR, and approved by COMPANY.

d.

Site Acceptance Test - conducted at the job site.

All formal testing will be conducted in accordance with a written test procedure. The test procedures will be furnished by the VENDOR to the CONTRACTOR at least 2 months prior to the Factory Acceptance Test for approval. Each formal acceptance test must be signed by VENDOR, CONTRACTOR and COMPANY representative at the successful completion of the test(s). 12.2

PRE-FACTORY ACCEPTANCE TEST (PRE-FAT)

The standard vendor procedures for thermal cycling of parts of the system shall be provided in the VENDOR’S proposal. The system equipment will be inspected by the COMPANY representative prior to Pre- Factory Acceptance Test for satisfactory quality and workmanship. The entire Pre-Factory Acceptance Test (Pre-FAT) procedure must have been successfully exercised on the system by the VENDOR prior to the FAT. 12.3

FACTORY ACCEPTANCE TEST (FAT)

The FAT will include the testing and acceptance of both hardware and software systems. All system programs must be complete and resident in the digital system prior to the start of FAT. All listings must be free of penciled (patched) corrections. The system must be free of patches. All hardware diagnostic programs will be run at the start of FAT. These must be the diagnostic programs which have been used for processing the system in the VENDOR’S factory. VENDOR shall be responsible for generating the FAT procedures that shall include “pass/fail” criteria. Diagnostic programs which are tested during FAT will be shipped to the staging area with the system. During FAT the system shall be made available to COMPANY for sufficient periods to verify satisfactory performance. COMPANY and CONTRACTOR representative will witness the entire FAT. The FAT procedure will be signed off by the VENDOR, CONTRACTOR and COMPANY representative at the successful conclusion of testing.



Rev: 0

Date:

March 2006


Page 23 of 29

All process inputs and outputs must be simulated during the FAT. The purpose of this simulation is to provide a facsimile of the production process, with all points of an individual loop or interconnected loops hooked up for test simultaneously. A copy of the signed off FAT procedures and related printouts shall be furnished to COMPANY representative. The VENDOR shall be required to submit FAT procedures for approval prior to the test. These shall cover, but not be limited to: •

Hardware/software tests.

•

System response tests with all I/O simulated at worst l oading conditions.

•

12.4

Power supply test (single feeder failure, momentary power loss, individual unit power supply loss, etc.).

SHOP INSPECTION

CONTRACTOR representative will periodically visit the VENDOR’S shop facilities and inspect system progress from a hardware and software perspective. 12.5

CERTIFICATES OF ACCEPTANCE

At the satisfactory conclusion of the FAT, a factory Certificate of Acceptance shall be provided by the VENDOR for signature by the CONTRACTOR. At the satisfactory conclusion of the SAT (Site Acceptance Test) a final Certificate of Acceptance shall be prepared by the VENDOR. Attached shall be all test records, receipt for documentation and spare parts plus any other pertinent records regarding the vendor’s delivery. The document becomes a Certificate of Final Site Acceptance which COMPANY shall review and app rove. 12.6

SERVICES SUPPLIED BY THE VENDOR

The VENDOR shall supply supervision, specialist personnel and all necessary materials to support the inspection and shop/site testing as defined above, including all the equipment and signal generation adequate to simulate all inputs simultaneously on a loop containing multiple input. 13.0

INSTALLATION AND PRECOMMISSIONING

13.1

INSTALLATION OF EQUIPMENT

Installation will be carried out by the CONTRACTOR with assistance from the VENDOR. Any special tools required for installation will be provided by the VENDOR. 13.2

PRECOMMISSIONING PROCEDURE

Precommissioning shall include, but is not limited to, the following: a.

An audit and inspection of equipment received. A deficiency report shall be written and appropriate action taken to rectify any problems.



Rev: 0

Date:

March 2006


Page 24 of 29

b.

Each system shall be powered up and functionally tested with appropriate test equipment.

c.

The microprocessors and peripherals shall be powered up and tested with diagnostic routines.

d.

Communications shall be established between all components of the system and tested using test equipment defined in Section 12.0.

e.

All alarm status, analog and pulse inputs, and controlled end devices shall be disconnected by means of isolating terminals. All alarm status, analog and pulse inputs, control outputs of each RTU shall be checked with simulated in puts and outputs loads.

f.

Each analog device shall be calibrated and the system function verified by closing the terminal isolators and interrogating each analog point and operating each final control element the Site Acceptance Test.

14.0

SPARE PARTS AND CONSUMABLES

14.1

PHILOSOPHY

Any spare parts for the custody transfer metering system or any integrated systems used during the Warranty Period shall be replenished at the VENDOR’S expense. The time scale and procedure for repair and/or replacement of parts shall be stated in the VENDOR’S bid. The VENDOR shall provide ordering information to order consumables and spare parts as required. Information required is:

14.2

•

Description of item.

•

VENDOR’S reference and part number.

•

Standard quantities recommended for start-up and normal operation.

START-UP AND COMMISSIONING SPARES

The VENDOR shall supply start-up spares, as required in order to avoid using any of the recommended spares. The cost of start-up spares shall be quoted separately. The time scales and procedure for repair and/or replacement of parts shall be stated in the VENDOR’S bid. 14.3

OPERATIONAL SPARES

The VENDOR shall review the equipment (including tools, testing and calibration equipment) offered in his proposal and shall include a comprehensive recommended spare parts list sufficient for two (2) years continuous operation of the equip ment. The costs of the recommended spares shall be quoted separately, by part. Two year spares, one year consumables, commissioning and start-up spares and consumables for basic and optional works.



Rev: 0

Date:

March 2006


Page 25 of 29

CONTRACTOR shall provide order preparation services for spare parts and consumables during the warranty period and for 2 years’ operation. This cost assumes that the procurement service will be executed within a period such that the order to the suppliers are placed before the corresponding SAT. COMPANY will place the order directly to the VENDOR. All cost of material, packing, shipping, clearing, and custom duties shall be included. If applicable, delivery to site will be paid directly by COMPANY. 14.4

VENDOR MAINTENANCE AND GUARANTEE

VENDOR confirms that warranty services are included in the unit pricing structure sum for scope. The spare part lists shall detail: •

Identifying model and/or figure number of the main equipment being quoted.

•

Part number and identification name.

•

Drawing or sketch number.

•

•

•

•

•

•

Source of the part. When a part is not manufactured by the VENDOR, the original supplier’s identification must be given. Price of spare parts. The lead time for supplying additional spares shall be quoted, (e.g., extra stock, 30 days, subject to quotation, etc.). The VENDOR shall indicate whether complete units or modules are recommended for the peripheral equipment. For all units, spare fuses and consumable items shall be provided as individual packages. All spare parts shall be clearly marked and identified using a concise tag number. Original spare parts shall be guaranteed available for a period of 15 years from the date of delivery and equivalent spare parts guaranteed available for a further 20 year period.

Spare parts shall be adequately protected and packaged to prevent deterioration of components and contact surfaces during prolonged storage under condition set forth in DGS-MU-002, Project Preservation specification. 14.5

CONSUMABLES

VENDOR shall ship, with the hardware, a six month supply of consumables, except printer paper. 15.0

TESTING AND CALIBRATION EQUIPMENT

15.1

EQUIPMENT PHILOSOPHY

The VENDOR shall provide the equipment required to test calibrate, service and generally maintain the system equipment to its maximum reliability and accuracy.



Rev: 0

Date:

March 2006


Page 26 of 29

15.2

EQUIPMENT SCOPE

15.2.1

Standard and Special Tools, Test and Calibration Equipment The VENDOR shall supply all standard and special tools, test and calibration equipment necessary for site installation, pre-commissioning and SAT.

15.2.2

Special Test Equipment The VENDOR shall provide his standard items of test equipment to perform the following functions: a.

Microprocessor emulator to test the proper operation of the input and output point functions. This unit shall be portable for l ocal testing of I/O cards or microprocessor controllers.

b.

Multimeters, signal generators and any other equipment recommended by the vendor. The VENDOR shall use the above equipment in the course of the precommissioning and the SAT. At the completion of these activities the equipment will be handed over to COMPANY in good condition. This equipment will be receipt acknowledged.

16.0

PROJECT ADMINISTRATION

16.1

PROJECT PERSONNEL

The VENDOR shall insure that sufficient qualified personnel are at all times allocated to the project. The VENDOR shall utilize a p roject team structure to achieve continuity and accuracy of implementation. The VENDOR shall submit for contractors approval the résumés of all personnel engaged in the project. It is anticipated that the project team shall comprise at least the following disciplines (one person may cover more than one discipline): •

16.2

Project Manager (Commercial/Technical) (shall be n ominated representative of the VENDOR with responsibility and authority to fully implement the project with technical correctness, on schedule and within the budget).

•

Senior System Designer (Technical).

•

Hardware Designer (Technical Hardware).

•

Software Designer (Technical Software).

•

Test Technician (Technical Testing).

•

Site Engineer (Installation/Commissioning).

PROJECT SCHEDULE

The VENDOR shall include with his quotation, a detailed Project Schedule showing the VENDOR’S best estimate of the achievable major schedule milestones. The Project schedule shall be used as the main progress control document during the implementation of the project. The Project Schedule shall clearly show any “float” or “slack” time available together with any freeze dates required by the VENDOR and major milestones for equipment design, manufacture and delivery. The schedule shall clearly indicate required dates for each of COMPANY supplied design data.



Rev: 0

Date:

March 2006


Page 27 of 29

The VENDOR may include in the proposal any additional material which clarifies the procedure for implementing the Project Schedule. 16.3

PROGRESS REPORTING

The Project Schedule shall be used as the basis for monthly progress reporting, schedule controlling, and schedule forecasting. At regular intervals, the VENDOR shall revise the Project Schedule to include the effect of changes and to reflect actual Project Progress. 16.4

COORDINATION MEETINGS

Coordination meetings shall be held as required between COMPANY, CONTRACTOR and VENDOR. The agenda for each coordination meeting will be prepared by the VENDOR prior to each meeting. Detailed meeting minutes will be taken by the VENDOR and submitted to COMPANY and CONTRACTOR for approval. An “action item” log shall be prepared and continuously updated by the VENDOR. Coordination meetings, shall be held either in Abu Dhabi or at CONTRACTOR’S office and will be a part of the purchase order scope. 17.0

TRAINING

17.1

TRAINING PHILOSOPHY

VENDOR shall provide formal training both on site and at the VENDOR facility for COMPANY personnel. 17.2

TRAINING COURSE DOCUMENTATION

For each trainee who will attend a training course, a copy of the complete training course, notes, and drawings shall be provided to COMPANY eight weeks prior to the commencement of the training course. The copies shall be retained by the trainees on completion of the training course and shall be the property of COMPANY. In addition, five copies of the training course documentation shall be available on site prior to the installation and pre commissioning for reference purposes. 17.3

OPERATOR TRAINING COURSE

A syllabus shall be prepared and provided, and a location recommended. Operator manuals shall be made available to COMPANY prior to this course. 17.4

MAINTENANCE TRAINING COURSE

The purpose of the course is to train technicians for first line fault diagnosis, and repair by replacement. A syllabus shall be prepared and provided, and a location recommended. Maintenance manuals shall be made available to COMPANY prior to this course. 17.5

SYSTEM CONFIGURATION COURSE

The purpose of this course is to enable COMPANY Engineers to be able to modify system configuration control and sequencing and to modify and build new graphics.



Rev: 0

Date:

March 2006


Page 28 of 29

•

Basic System Introduction.

•

Peripherals.

•

Operator Consoles.

•

Database Reports and Data Entry.

The VENDOR shall recommend the location for this training. 17.6

TRAINING AIDS

The VENDOR shall list training aids required for above courses. 18.0

WARRANTY

VENDOR shall provide warranty support for a period of two years, commencing on the date of COMPANY written acceptance of the system following the site acceptance test. Warranty shall apply to defective material workmanship and facility design, and/or facility software. Warranty work shall be done at COMPANY local facilities. The cost of diagnostics and/or correction of any warranty items shall be borne by the VENDOR and the CONTRACTOR. The VENDOR will not be required to provide resident maintenance personnel during the warranty period, but shall have competent technical personnel available from the local facility within 24 hours, if so required by COMPANY. The VENDOR shall guarantee availability of spare parts for the system for a minimum period of 15 years from the date of acceptance of the system. The VENDOR shall guarantee that the software to be supplied shall be free from errors; i.e. software/firmware failure to perform function(s) as specified in this specification or COMPANY documentation. 19.0

MAINTENANCE

The VENDOR shall detail in the proposal the maintenance services provided during the following phases of the project: 19.1

MAINTENANCE DURING WARRANTY

The warranty period for this contract shall be twelve (12) months, following the issuance of the Provisional Acceptance Certificate. During this period the VENDOR shall provide service personnel for periodic preventative maintenance, fault finding, repair and replacement of all equipment, firmware and software, supplied in accordance with this specification. The VENDOR may utilize the recommended spare parts to maintain the system. The VENDOR shall replace all such spare parts used, at no cost to COMPANY. 19.2

MAINTENANCE AFTER WARRANTY

The proposal shall include the detai ls and costs of all standard maintenance services available from the VENDOR which are suitable for the proposed system (hardware, firmware and software). COMPANY shall be under no obligation to select all or any of the agreements detailed and shall be free to negotiate a unique maintenance agreement with the VENDOR.



Rev: 0

Date:

March 2006


Page 29 of 29

Dgs is 020 r0 Custody Metering Systems

Recommend Documents