National Oil MIS Specification

NATIONAL OIL CORPORATION
GENERAL ENGINEERING SPECIFICATION
GES J.25
MANAGEMENT INFORMATION SYSTEMS
Rev Date Description Checked Approved

0 1999 Issued for Implementation DL
Compiled by Teknica (UK) Ltd

GENERAL ENGINEERING SPECIFICATION GES J.25
MANAGEMENT INFORMATION SYSTEMS Page 2 of 28
Rev 0 1999
INDEX
SEC TITLE PAGE
1.0 SCOPE OF SPECIFICATION 4
1.1 Introduction 4
1.2 Other NOC Specifications 4
2.0 DEFINITIONS 5
2.1 List of Abbreviations 5

2.2 Contractual 5
3.0 DESIGN 6
3.1 Codes and Standards 6

3.2 Functional Definition Specification 7
3.3 Design Studies 9
3.4 Data Links 11
3.5 MIS General Requirements 11
3.6 Application Software Requirements 12
3.7 Optimisation Simulation Package (Optional) 14
4.0 MATERIALS 15
4.1 Hardware 15
4.2 Software 16
4.3 Services 16
5.0 MANUFACTURE 17
5.1 Open Systems Requirements 17

5.2 Virtual Bulk Database Requirements 17
5.3 Electrical 18
6.0 PROJECT ACTIVITIES 19
6.1 Project Team 19

6.2 Planning 19
6.3 Quality Assurance 20
6.4 Software Quality Assurance 21
6.5 Software Costs 21
7.0 INSPECTION 21
8.0 TESTING 21
8.1 Statutory Tests 21

8.2 Test Procedures 22
8.3 Factory and Acceptance Testing 23
8.4 System Integration Testing 23
8.5 Site Acceptance Testing 24
8.6 Sustained Performance Test 24
Rev 0 1999
INDEX
SEC TITLE PAGE
9.0 DOCUMENTATION 24
9.1 Introduction 24
9.2 Schedules and Reports 25
9.3 Data and Calculations 26
9.4 Drawings 26
9.5 Final Records, Documents and Manuals 26
10.0 PRIOR TO SHIPMENT 26
10.1 Painting and Coatings 26

10.2 Spares 26
10.3 Packing and Storage 26
10.4 Shipping 27
10.5 Service Support 28
10.6 Warranty 28
DATA SHEET (1)

Rev 0 1999
1.0 SCOPE OF SPECIFICATION
1.1 Introduction
1.1.1 This specification covers the minimum requirements for the design, supply, inspection and testing for
Management Information Systems.
1.1.2 This specification applies to equipment for refineries, onshore oil and gas installations and processing
facilities.
1.1.3 In order to define the specific MIS requirements, is shall be necessary for the Vendor/Contractor to define
plant requirements, its operations, the interfaces and protocols required to link up the various sub-systems
and the information required by management. The services of a specialist Vendor/Contractor shall be
obtained in order to define the exact requirements of the MIS. The Vendor/Contractor shall have a proven
track record of undertaking such work and implementing petrochemical complex or refinery type MIS.
1.1.4 It is intended that this general specification will be developed further by the Vendor/Contractor by
incorporation of the Owner requirements into a Functional Definition Specification.
1.1.5 The Vendor/Contractor shall comply fully with the provisions laid down in this specification. Any
exception must be authorised in writing by the Owner.
1.1.6 In the event of any conflict between this specification or with any of the applicable codes and standards the
Vendor/Contractor shall inform the Owner in writing and receive written clarification before proceeding
with the work.
1.1.7 This General Engineering Specification will form part of the Purchase Order/Contract.
1.2 Other NOC Specifications
The following NOC Specifications are an integral part of this specification and any exceptions shall be
approved in advance by the Owner:
GES A.06 Site Data
GES C.54 Commissioning of Microprocessor Based Instrument Systems
GES J.16 Instrument Cable and Cabling
GES J.20 Distributed Control Systems
GES J.22 Field Automation (SCADA) Systems
GES J.26 Metering and Meter Proving Systems
GES J.27 In-Line Blending Systems
GES J.29 Centralised Tank Farm Monitoring Systems

Rev 0 1999
2.0 DEFINITIONS
2.1 List of Abbreviations
API Application Programming Interface

CAD Computer Aided Design
CCR Central Control Room
DBMS Data Base Management System
DCE Data Circuit Equipment
DCS Distributed Control System
DTE Data Terminal Equipment
FAT Factory Acceptance Testing
HDD Hard Disk Drive
IT Information Technology
LAN Local Area Network
MIS Management Information System
MMI Man Machine Interface
MV Measurement Value
ODBC Open Data Base Connectivity
OLE Object Linking and Embedding
OP Output
PLC Programmable Logic Controller
QA Quality Assurance
QC Quality Control
RAID Redundant Array of Inexpensive Drives
SAT Site Acceptance Testing
SIT System Integration Testing
SCADA Supervisory Control and Data Acquisition
SP Set Point
SQC Statistical Quality Control
SQL Structured Query Language
WAN Wide Area Network
2.2 Contractual
The commercial terms used in this specification are defined as follows:
Owner
The oil or gas company, an associate or subsidiary, who is the end user of the equipment and facilities.
Vendor
The company supplying the equipment and material.
Contractor
The main contractor for a defined piece of work.
Sub-Contractor
A company awarded a contract by a contractor to do part of the work awarded to the Contractor.
Rev 0 1999
Inspection Authority
The organisation representing the Owner or Vendor/Contractor that verifies that the equipment and facilities
have been designed, constructed, inspected and tested in accordance with the requirements of this specification
and the Purchase Order/Contract.
Inspector
A qualified individual representing the Owner, Vendor/Contractor or the assigned Inspection Authority, who
verifies that the equipment and facilities have been designed, constructed, inspected and tested in accordance
with the requirements of this specification and the Purchase Order/Contract.
3.0 DESIGN
3.1 Codes and Standards
The following codes and standards shall be considered part of this specification. All documentation shall be
the latest issues available.
British Standards Institution (BSI)
BS 4058 Specification for Data Processing Flow Chart Symbols, Rules and Conventions
BS 5515 Code of Practice for Documentation for Computer Based Systems
BS 5750 Quality Systems (All Parts) - Equivalent to ISO 9000 series
BS 5760 Reliability of Systems, Equipment and Components (All parts)
BS 5887 Code of Practice for Testing of Computer Based Systems
BS 6238 Code of Practice for Performance Monitoring of Computer-based Systems
BS 6488 Code of Practice for Configuration Management of Computer-based Systems
Electronic Industries Association (EIA)/CCITT Recommendations
V24/RS 232E Interface Between Data Terminal Equipment and Circuit Terminating Equipment
Employing Serial Binary Data Interchange
RS 422 Electrical Characteristics of Balanced Voltage Digital Interface Circuits
V28/RS 485 Electrical Characteristics for Generators and Receivers for use in Balanced Digital
Multipoint Systems
Institute of Electrical and Electronic Engineers (IEEE)
IEEE 802 Standards for Local and Metropolitan Area Networks Management - All Parts
Rev 0 1999
3.2 Functional Definition Specification
3.2.1 The Vendor/Contractor shall prepare a Functional Definition Specification for the MIS and issue for review
and approval by the Owner. The FDS shall incorporate the requirements of this section and the design studies
as determined in Section 3.3. The FDS shall be undertaken jointly with the Owner's Operations, Marketing,
Planning, Accounting, Maintenance and Information Technology departments.
3.2.2 The FDS detail the functions of the system to be supplied against this specification. It shall explain how each
of the packages function and its interaction with others. It shall detail all data requirements for the final system
and provide an initial description of all user interfaces. The content of this documentation shall be agreed by all
parties before the system development and building takes place. It shall be the first document to be produced.
3.2.3 Scope
In addition to the special requirements of the departments involved, the following general requirements shall
be incorporated into the FDS:
(a) Establish the process facilities operations and maintenance systems;
(b) Establish the process facilities production targets and objectives;
(c) Establish the facilities's past targets for performance and also analyse the feedback information
provided to adjust operations;
(d) Evaluate the capabilities of existing IT systems and interfaces to the process control system and to the
optimisation systems;
(e) Evaluate individual plant's information needs;
(f) Establish data flow requirements between different systems, sub-systems and users;
(g) Evaluate the method of dealing with redundant and conflicting information;
(h) Establish the need for a virtual bulk database and database programs;
(i) Evaluate methods to minimise costs and maximise efficiency.
3.2.4 Further Scope
(a) The FDS may address issues such as: planning, product yield prediction, scheduling, stock control,
product and feed stock movement, spares, production reporting, loss reporting, data reconciliation,
billing, salaries and costs and supervisory process control.
(b) The FDS may also address issues such as plant maintenance, environmental monitoring, permit
tracking and link to the CAD systems.
(c) It is assumed that local process unit control is carried out by a DCS. Optimisation utilising
multivariable control strategy may need to be applied for a typical refinery to such units as crude
distillation, hydrotreater, MTBE, hydrocracker, vacuum distillation etc. This level of
control/optimisation may be included in the FDS.
Rev 0 1999
3.2.5 Recommendations
(a) The FDS shall make recommendations with options on the following areas:
Improvements in selected areas of plant management.
Improvements in the existing plant IT systems.
Define overall requirements of the plant MIS.
Define data requirements.
Selection of DBMS package.
Information System planning including data set requirements.
Software recommendations.
Software package(s) selection.
Standardisation of hardware platform.
Level of hardware and software fault tolerance e.g. RAID drives, dual processor platforms,
data integrity.
Define facilities to be provided to guard against the failure of the main computer node.
Optimisation package(s) requirements.
Define priority applications.
Define enhancement applications.
Define System Integration requirements e.g. comm links, data transfer issues.
Implementation programme.
Software maintenance requirements and costs.
Cost benefit analysis of the proposed implemention.
(b) The final issue of the FDS shall take into account the Owner's comments and shall also include as a
minimum the following:
System overview diagram.
Data flow diagrams.
Functional specification of the proposed system.
Hardware architecture.
Software architecture.
Proposed data sets.
Proposed software implementation details .

Rev 0 1999
Proposed display sets.
Overall communication diagram.
Overall computer system integration block diagram.
QA/QC requirements.
Vendor/Contractor software proposals.
(c) The Vendor/Contractor shall list the sites, plant type details and plant size of the facilities where
similar MIS package have been successfully implemented.
(d) Vendor/Contractor shall also advise if the total system should be implemented under one project or if
an incremental implementation is preferable.
3.3 Design Studies
3.3.1 System Configuration Study
The Vendor/Contractor shall undertake to do an overall system configuration study summarising the main
facilities and functions that each of the sub-systems has to provide, and the way these shall all be integrated
together. This study shall include hardware, software, protocols, data formats and data displays. The purpose
of this study shall be to achieve the optimum overall system as defined in this specification. Any
incompatibilities, limitations and problematic areas between the different systems shall be identified and
solutions recommended. The study shall also address the following issues:
Accommodation of future changes;

Maximum use of standardised user friendly interfaces;
Implementation of system optimisation strategy;
Maximum utilisation of system resources;
Implementation of software guidelines.
3.3.2 Data Formats and Protocols Study
A study into the Data Format and Protocols required between each sub-system shall be undertaken by the
Vendor/Contractor with the following issues addressed as a minimum:
Compatibility/conformity;
Correctness of the information being transmitted;
Completeness;
Testability;
Standardisation;
Sufficiency of the information being transmitted;
Efficiency;
Speed/Loading;
Exception responses;
Action on responses;
Conversation structure;
Data structure.
3.3.3 System Sizing Study
(a) The Vendor/Contractor shall carry out a system hardware sizing/verification study. The purpose of
the study shall be to confirm that the selected hardware system has enough computing power and
memory to provide overall specific performance under steady state and under critical operating
Rev 0 1999
conditions.This study shall be updated at certain critical stages of the project. Basis of the sizing shall
be stated e.g. software and I/O limitations, bench marks, simulator studies, trade literature, existing
installations, number of users, other. In any event the processor and network loading shall be limited
to 40% under normal operating conditions and 50% under peak loading conditions. This
performance shall be guaranteed.
(b) System sizing study shall address all aspects of the response times and fault tolerance including the
transfer of database data, the base schedule of events, testing and maintenance.
3.3.4 Availability, Reliability, and Security Study
(a) The required level of availability shall be agreed with the Owner. The study shall address all elements
of the system i.e. processors, data links, network bridges, communication channels, routers, modems,
multiplexers, hard drives, etc. The methods used shall be agreed with the Owner. Only real life data
shall be used. All assumptions, sources of data and definitions shall be clearly stated. The study shall
include a failure mode and effects analysis.
(b) The study shall also include a sensitivity analysis, listing percentage sensitivities for various elements
in the path. The study shall also recommend any hardware or software additions, improvements, and
required redundancy in order to achieve the required level of availability.
(c) The Vendor/Contractor shall suggest and implement security measures to avoid the breach of security
when linking to any external system. This may mean utilising a particular method of data transfer e.g.
task to task rather than file transfer.
(d) Vendor/Contractor shall state in his bid the method by which he proposes to present these study
reports. Any software program used to carry out this study shall be approved by the Owner.
3.3.5 Man Machine Interface Study
The Vendor/Contractor in conjunction with the Owner shall produce a MMI Study which shall as a minimum
cover the following topics:
a) Screen layout;
b) Database (including field) details;
c) Colour schemes;
d) Graphic representation of dynamic and static symbols;
e) System and sub-system start-up procedures;
f) Menu bars;
g) Soft keys;
h) Overlays;
i) Page control/access;
j) System displays.
The Vendor/Contractor shall include for all graphics, mimics and static/dynamic objects based on the project
Piping and Instrumentation Diagram symbols.
The Vendor/Contractor shall agree with the Owner the MMI configuration including the database.
3.4 Data Links
3.4.1 The Vendor/Contractor shall produce a drawing showing all data link connections between systems.
3.4.2 Data will be received from different sources utilising various different communication interfaces and
protocols. Details of these interfaces shall be given using the typical "Data Interfaces and Protocols" Data
Sheet attached to this specification. The Vendor/Contractor shall complete the remaining information for each
interface/protocol. This document shall then form part of the configuration verification study.
Rev 0 1999
Communications with the plant DCS shall be via redundant fault tolerant data links. The Vendor/Contractor
shall provide details in his bid of all the successful links he has implemented to SCADA, DCS, PLC, flow
computers and analysers.
3.4.3 It shall be the responsibility of the Vendor/Contractor to implement successfully all links described above
without requiring the other Vendor/Contractors to modify their protocols.
3.4.4 Use shall be made of object embedding "point and click" data retrieve capability and live data links such as a
link to a spreadsheet.
3.5 MIS General Requirements
3.5.1 A Computer System Integration Block Diagram and the Data Flow Diagram shall be produced by the
Vendor/Contractor and approved by the Owner.
3.5.2 The MIS shall be a client-server architecture consisting of one or more central fault tolerant file servers in the
CCR Equipment Room or the computer room, connected via various communications links and using various
protocols to some or all of the following systems:
Plant DCS,
Fiscal metering systems,
Pipeline SCADA system,
Tank gauging SCADA systems,
In-line blending system,
Plant loading systems,
Laboratory systems.
In addition, there may be a requirement to connect the MIS to other plant control/monitoring systems. The
MIS client-server station shall receive data from all defined external systems and archive it without any
modification.
3.5.3 The central database server shall receive raw data from other systems and place this in a central database after
having checked the data for validity, limits violation, consistency, integrity, suspect values etc. Owner defined
operations shall be performed on this data the results of which shall then be stored and displayed on demand in
the pre-configured format by a number of users. The data transfer and display of data shall be done on a real
time basis and using a data historian programme such that the plant operational efficiency or profits may be
maximised. It shall be possible to mix or co-mingle live and historical data from different sources on the
displays.
3.5.4 A validation feature shall be incorporated in the package to check the incoming data for format,
reasonableness, validity, limits violation checks, integrity, suspect values, consistency and accuracy. These
checks shall be agreed with the Owner. Data not meeting these requirements shall be alarmed and the operator
shall be notified. Data quality shall be tagged.
Rev 0 1999
3.5.5 MMI shall be via graphics workstations and additional PC based workstations (as required). The displays may
be standard Vendor/Contractor displays subject to Owner's approval or these may be entirely defined by the
Owner. The MMI shall include definable levels of security access and provision for manually entering data
via the MMI screens. All manually entered data and comments shall be tagged as such and dated.
3.5.6 The MIS shall have the capability of being time synchronised with an accurate internal or external clock
source. It shall also incorporate a facility for setting this time on other external systems.
3.5.7 The Vendor/Contractor shall provide diagrams to illustrate the hardware/software architecture of the system.
Any interface software modules shall be separate from the above. The application software required to meet
the functional requirements shall be modular in design, be easy to configure and maintain and be capable of
unlimited future expansion.
3.5.8 It shall be the Vendor/Contractor's responsibility to include all hardware and software functions detailed in this
specification. Unless otherwise stated in the Vendor/Contractor's bid, it shall be assumed that he has included
for all hardware and software engineering and reports including configuration, testing and commissioning of
the same.
3.5.9 Output by the software shall be graphics, spreadsheets, alarms, events, calculated and predicted values reports.
These outputs shall be available to the operator for viewing or printing either locally or at a remote location.
Report generation may be manual or time based automatic activity.
3.6 Application Software Requirements
3.6.1 Server Application Software Platform
(a) At the time of writing, Window NT Advanced Server and Windows 98 are the preferred platforms.
Unix or OS.2 may be acceptable alternative to Windows NT Advanced Server subject to the Owner's
permission. Any other platforms shall be considered only if the Vendor/Contractor can clearly
demonstrate tangible benefits.
(b) Whichever platform is chosen, it shall be a true 32 bit version. If Microsoft operating system is
selected then the system shall support OLE, OLE Automation, OLE Scripting and the use of ODBC.
3.6.2 Server Data Historian
(a) The data historian shall be a real-time historical database, sized and designed such that data is
available on-line for at least 5 years from Purchase Order/Contract placement. All values at their
original resolution (quality and time) shall be recorded. The system shall have the capability to store
not less than 100,000 time tagged plant items. All items of data shall be stored once only. The
Vendor/Contractor shall provide full details of the data historian at the bid stage.
(b) The number of users that can be accommodated shall be agreed with the Owner, but in any event
shall not be less than 50. Any log in onto the host machine which require large bandwidth e.g. X
Windows into the Windows NT network shall be avoided altogether. Terminals, if used, shall be of
intelligent type with its own processor and hard drive and with local graphics capability.
(c) Data queuing facility shall be provided in order to guard against the failure of the main (or base)
mode. The Vendor/Contractor shall advise if continuous collection of data using fail-over, in the
event of a failure of a mode, is possible and desirable. This shall be agreed with the Owner.
Rev 0 1999
3.6.3 Server Standard Interfaces
(a) The Vendor/Contractor shall state in his bid which PLC, DCS, SCADA system, fiscal metering
system, tank gauging and other systems, protocol software drivers are standard and are included in
his bid. Any protocol functionalities that are excluded or require special programming to implement
or are not user configurable shall be detailed in the bid.
(b) The Vendor/Contractor shall provide details of the site at which these protocols are already in use.
Any protocol drivers which are yet to be developed or are under development shall be clearly
described as such in the bid.
3.6.4 Server Equation Library
A library of performance equations shall be supplied which shall allow the user to perform fluid properties
modelling related calculations. The sub modules shall include steam tables, compensated flow, calculations of
heat and mass balance, tank inventories, heat flow etc. It shall be possible to either create new equations and
add these to the library or to link any equation to any external function written in a high level language.
Examples of such language are C or FORTRAN, the latter being the preferred language. All language
compilers and licenses shall be included for in the bid. Vendor/Contractor shall state in his bid the standard
sub-modules included in the library. The Vendor/Contractor shall also provide optional prices for other
available sub-modules.
3.6.5 Server SQC Software
Vendor/Contractor shall state in his bid if SQC software is included for the plant studied. The SQC software
shall run in real time. Minimum functionalities shall include average, moving average, geometric average,
range, standard deviation and defective functions.
3.6.6 Server Alarm Software
The server alarm software module shall have the facility to raise alarms on any tag or selected group of tags.
Alarms may be low, high, deviation, rate of change, absence of data, bad data etc. Alarm message facilities
shall incorporate help information. It shall be possible to initiate an event such as report printing, message
routing or start an application on initiation of an alarm event. It shall be possible to log all or selected group of
alarm tags.
3.6.7 Server Batch Software
Batch software used to operate batch processes by initiating plant operating sequences and monitoring that the
correct actions have taken place shall be provided if required. The Vendor/Contractor, in conjunction with the
Owner, shall define the type of batch software required. The module shall have typically the following
facilities: batch creation, batch storage, batch selection, batch record/ID/Product unit etc. detail and support for
plant unit aliases. The latter shall allow retrieval of the data associated from the actual time period to the batch
run.
3.6.8 MMI Software
(a) The MMI shall be a full colour, graphical (Windows based) display. These could be standard
Vendor/Contractor's displays and Owner defined screens. The display shall have the ability to mix
live and historical data across different platforms. It shall be possible to combine, graphics, trends,
live dynamic `objects', statistical plots and spreadsheets. The MMI shall have single function key or
pointing device operation e.g. trackerball or mouse. The MMI shall incorporate at last 10 levels of
security access. Provision shall be made to manually enter data or comments which may be
unavailable due to equipment failure. Any such data shall be flagged as being manually entered data.
(b) The estimated number of screen displays shall be defined jointly by the Owner and the
Vendor/Contractor in the FDS. The Vendor/Contractor shall quote a unit price for implementing a
Rev 0 1999
screen display based on the maximum information that can be realistically displayed on the screen.
3.6.9 Report Generator Software
(a) The client report generator software shall allow the user to customise reports and print these either on
a local printer or on a remote printer on manual or periodic basis. It shall be possible to reuse or
redesign the report by the user easily and quickly.
(b) The Vendor/Contractor shall agree the number and format of the reports, in conjunction with the
Owner. The Vendor/Contractor shall include for this number of generated reports. The
Vendor/Contractor shall include for a minimum of 50 reports in his bid.
(c) The Vendor/Contractor shall quote a unit price for implementing reports based on the information
(number of fields) contained on a typical report.
3.6.10 Control Loop Performance Software
The Control Loop Performance software shall analyse the data on user selectable control loops pertaining to
their MV, SP, OP and ON/OFF control status flag. It shall report the time period during which the control is
functioning as designed, the loop stability, average valve position, average error and standard error for each
selected control loop. Those loops that deviate significantly from their normal pattern of behaviour shall be
linked automatically to a daily report for the maintenance department for action.
3.6.11 Batch Display Software
Facility shall be provided for the user to view selective batch data. The batch display software shall be part of
the MMI and as such, shall be user friendly employing dialogue boxes, menus and windows. The following
minimum information shall be user selectable: batch summary including start/end time/duration, batch change
marking. Trend alignment shall also be supported.
3.6.12 Statistical Quality Control Software
The SQC software shall also work in conjunction with the MMI allowing the user to select the SQC data and
trend it on his MMI. This module shall also support alarming and indication of upper and lower control limits
alarming and the user comments to these alarms.
3.6.13 Programming and Database Interfaces
The supplied data base shall support ANSI SQL calls as a minimum as well as the API calls. The
Vendor/Contractor shall detail fully in his bid the functionalities provided by the above interfaces.
3.7 Optimisation Simulation Package (Optional)
3.7.1 The optimisation package shall be user friendly. Configuration software shall not require end-user
programming expertise. It shall utilise sectional linear programming techniques to optimise a non-linear
mathematical model. It shall detect any movement of an optimum path from the optimum constraints. It shall
also be used offline for investigation into non-linear optimising problems.
Rev 0 1999
3.7.2 The program shall handle all inputs, outputs, logic, data handling, optimisation etc. The model shall employ
both primary convergence techniques and secondary convergence techniques, multi-unit capability, multiple
set of limits, adaptive linearity limits, move penalties, target constraints, dead zones, curtaining capability,
linear programming algorithm and error check. The Vendor/Contractor shall advise any additional features
that may be required or desirable.
3.7.3 The Vendor/Contractor shall include for the configuration and testing costs for properly formulating the
mathematical model and objective functions to be optimised or any programming routine to carry out any
complex mathematical routines not already included in the base package. The Vendor/Contractor shall also
include for the configuration and testing for a set of data, defining the initial values of model variables, limits
of model variables and the required logical control parameters. The number of loops shall be defined at the
Purchase Order/Contract stage.
3.7.4 It shall be possible to use the output to implement the desired control action timing. The Vendor/Contractor
shall provide for any interfacing to the process control software running on either the plant DCS or another
computer both of which are outside the MIS Vendor/Contractor's scope of supply.
3.7.5 The Vendor/Contractor shall also compile a short list of commercially available simulation packages that may
be suitable for the plant.
4.0 MATERIALS
4.1 Hardware
4.1.1 File Server
The following minimum hardware on a Client/Server File Server configuration shall be included for in the
Scope of Supply:
Fault tolerant processor cards with integral mathematical co-processors;
Cache memory;
UPS unit (minimum back-up battery time 2 hours);
Mirrored or RAID hard disc drive `hot' replaceable type. RAID level shall be defined by the
Vendor/Contractor. Storage size shall be agreed with the Owner;
Software loader (tape or CD ROM drive or both);
CD drive (read/write type);
Power supply unit;
All communication boards and associated external cables;
Equipment cabinet;
Workstation graphics cards;
Work stations (minimum screen size 21 inches);
Keyboard with integral tracker ball and mouse;
Colour and monochrome laser printers;

Rev 0 1999
All power leads and external cables.
4.1.2 Other hardware to be included in the scope of supply shall include the following:
All workstations with accessories at various locations;
Communication cards for workstations;
Gateways, bridges, routers and brouters;
Modems (normal or fibre-optic), multiplexers, line drivers, protocol converters;
Communications/fibre optic system and interconnecting cables and accessories;
Any other items including software/hardware test and utility items that are required for a fully
functional system.
4.2 Software
The Vendor/Contractor shall supply all software and firmware necessary for the system to perform the
specified functions. This shall include but not be limited to:
Project specific software;
Vendor/Contractor's standard software;
Operating system software;
Network software including protocols;
All application software;
Software maintenance tools;
Programming languages software and tools;
Software used for configuration, tests, maintenance and modification of the database, common links
and operator display;
All licences.
4.3 Services
4.3.1 All hardware, software and communication systems, operator displays, logs and reports and data bases shall be
supplied fully configured.
4.3.2 The Vendor/Contractor shall be supplied with a copy of the facilities Instrument Index after Purchase
Order/Contract placement. This document shall be used by the Vendor/Contractor to develop the MIS
database. The contents of the MIS database shall be approved by the Owner. The Instrument Index is a
database derived document which evolves throughout the life-time of the plant. It is expected that the
instrument index shall be revised a number of times during the life time of the project. The Vendor/Contractor
shall include for his database to be updated a number of times during the project.
5.0 MANUFACTURE
5.1 Open Systems Requirements

Rev 0 1999
5.1.1 Proprietary technology shall be avoided wherever possible. Hardware platforms and operating
system/network software shall be de-facto industry standard open systems. Industry standard readily available,
interoperable plug and play hardware modules and application software shall be used wherever possible.
5.1.2 Configuration techniques shall be used wherever possible. Programming shall be kept to a minimum. Database
development work shall be done using 4th Generation Programming Language wherever possible. The
Vendor/Contractor shall advise what case tools he intends to use in order to facilitate easier configuration
implementation.
5.1.3 The table below gives a list of typical equipment and software products available in the market at the time of
preparation of this specification. Unix based products are not preferred.
Table 1 - Preferred Suppliers
Equipment and Software Suppliers

Server - PC based (Preferred) Compaq, HP, IBM
Server - Unix HP Compaq, IBM,

Workstation - PC based Compaq, HP, Others
Workstation - Unix HP, Sun, Compaq

Routers/Bridges
Optical Drives Panasonic, HP, Sony
Server DBMS Software MicroSoft, Oracle, Informix,
Server (PC based) OS Windows NT Advanced Server, OS.2, Unix

MMI terminals Wyse, HP, Compaq
User Interface MicroSoft Windows, X Windows,
5.2 Virtual Bulk Database Requirements
5.2.1 All functionalities of the database software shall be defined in the FDS by the Vendor/Contractor. The
Vendor/Contractor shall list similar sites where the proposed virtual database concept has been successfully
employed to create a facility wide MIS.
5.2.2 A software system which can be shown to be used effectively and successfully on similar plants may be used
subject to the Owner's written permission.
5.2.3 Third party database programs may be used to integrate the software systems using proprietary MIS with a
large user base and based on Open System concepts.
5.2.4 Selected database programs shall be suitable for accessing data from both business information (staged data)
and from on line analytical processing i.e. from live data sources such as the DCS, PLCs etc.
5.2.5 The design of the selected system shall allow it to deal with issues such as protocol connections, server
management, SQL resolution, query governing, query routing, security, audit and data quality management as
a minimum. Its application shall be scalable from point to point single tool and distributed database
applications. Client server tools shall be suitable for use by a non-database expert but a computer literate
person. No programming skills shall be required. The facilities shall include easy selection, conditioning,
transformation, decoding, summarisation, roll up, manipulation and display of data on a desktop PC in a
distributed computing environment.
Rev 0 1999
5.2.6 Database and MMI
A graphical (Windows) based pre-defined but modifiable rule base copy management shall be provided which
shall allow the scheduled extraction and transportation of data for scheduled update processing. These shall
utilise the concept of data about data or metadata. Statistics of frequently used data shall be captured and data
priorities established. The Vendor/Contractor shall state how the proposed software can meet efficiently the
requirements of the ODBC concept.
5.2.7 Expert System
The Vendor/Contractor shall also include expert system technology software for capturing employees
expertise and knowledge for future decision making and to enhance efficiency. Any such system shall make
use of object oriented programming technology in order to minimise software development and
implementation time and costs.
5.2.8 Development
The users scope and the type of virtual database shall be defined. A bottom-up or outside-in approach to the
virtual database shall be adopted. This shall be done in consultation with the Owner, analysing the issues
involved, data access and security and access needs. The aim shall be to develop robust and flexible working
system. It shall be possible to build a virtual database as an ongoing process. It shall also be possible to amend
the virtual database once the data requirements are finalised for the project. The development and the
modification of the data requirements shall be possible with minimum additional costs and retraining. The
Vendor/Contractor shall also include for any software tools required to analyse data usage frequency and to
stop the system from becoming overloaded.
5.3 Electrical
5.3.1 Electrical Supply Requirements
(a) Electrical supply details shall be specified on project specific basis. The Owner shall specify all
requirements such as voltage levels, frequency, total harmonic distortion (ripple) and applicable
tolerances.
(b) The Vendor/Contractor shall confirm the compatibility of the proposed equipment with the power
supply.
5.3.2 Earthing Requirements
(a) The Vendor/Contractor shall comply with the project earthing philosophy and shall advise any
specific earthing requirements of his equipment.
(b) Any inter-system earthing or screening requirements or any requirements resulting form the different
geographical locations shall also be clearly identified by the Vendor/Contractor in the FDS.
(c) The Vendor/Contractor shall advise if isolation or protection is required to eliminate the effects of
lighting, raised earth potential due to earth faults and switching transients.
5.3.3 Electromagnetic Interference
All Vendor/Contractor's equipment shall be designed such that a high degree of immunity to radio interference
in the 27 to 500 MHz band with a field strength of 10V/m. The equipment shall continue to operate without
fault when a hand held communicator is keyed at 1.5 feet (0.5m) distance from the equipment with the doors
open. The Vendor/Contractor shall identify any equipment which does not have this immunity.
5.3.4 Signal Cabling Requirements

Rev 0 1999
(a) All wiring between various system network devices and peripherals, and between system cabinets
shall be carried out using prefabricated cables incorporating strain relief, proper earth and drain wires
and earth shields to reduce cross talk. Cable connectors shall also incorporate screw locking to
prevent accidental disconnection.
(b) Multiway plugs and sockets shall be used to terminate the interconnecting cables and shall be
complete with screw locking to prevent accidental disconnection. Connectors shall be standard RS
232E/CCITT V24, 25 or 8 pin, RS 422 or RS 485 interfaces. If the full complement of signal wiring
is not utilised, the Vendor/Contractor shall, show in the instruction manuals using diagrams, which
subsets are used for each type of cable.
(c) Cabling shall be kept to a minimum and the use of 'interface boxes' shall be avoided. However the
Vendor/Contractor may utilise proprietary adaptors.
(d) The Owner shall provide access to the plant telephone lines only, where it is required. All other
equipment such as network cabling and accessories and services shall be provided by the
Vendor/Contractor.
(e) The installation requirements of GES C.54 and GES J.16 shall apply.
6.0 PROJECT ACTIVITIES
6.1 Project Team
6.1.1 The Vendor/Contractor shall provide a project team for the full duration of the contract. Team members shall
be suitably qualified and experienced. The team shall be co-ordinated by an experienced project manager. The
Vendor/Contractor shall submit curriculum vitae of prospective project manager, project lead engineer, quality
control manager and other key personnel together with a proposed organogram with the bid.
6.1.2 The Owner reserves the right to interview and approve any prospective senior staff joining or leaving the
project. The Vendor/Contractor shall ensure the continuity of senior staff on the project.
6.2 Planning
6.2.1 Following Purchase Order/Contract placement, the Vendor/Contractor shall submit, within a period of four
weeks, a programme of engineering activities. Each activity shall include description, early and late freeze
dates of activities, float, deliverables, pre-requisites and information requirements. Key milestones shall be
highlighted.
6.2.2 The Vendor/Contractor shall provide monthly progress reports. The format of the monthly report shall be
agreed with the Owner.
Monthly reports shall include:
Activities undertaken/completed during the month;
Activities scheduled for the next month;
Information required from the Owner for the next month;
Problem areas;
Revised activity chart.
6.2.3 Meetings shall be convened to discuss progress, information flow and outstanding activities on a scheduled
Rev 0 1999
basis, with an average of one per month and additional meetings may be requested (if required) by either party.
The Vendor/Contractor shall prepare and issue minutes of these meetings within 5 working days of the
meeting.
6.2.4 All Vendor/Contractor communications to third parties shall be via the Owner. Direct communication shall be
only with the prior permission of the Owner. Where direct communication is allowed, it shall be for that time
basis only. The discussion shall be limited to information exchanges. The Owner shall be informed via phone
within one day of the discussion content and via fax of the minutes of the meeting within 3 working days.
6.3 Quality Assurance
6.3.1 The Vendor/Contractor shall have ISO 9000 registration. The Vendor/Contractor shall provide a copy of his
Quality Manual with the bid.
6.3.2 Following Purchase Order/Contract award the Vendor/Contractor shall submit a Quality Plan for the Owner's
approval. This plan shall include, but not be limited to, the quality plan, software design and documentation
proposals, test, installation and commissioning procedure. Documentation examples shall be submitted. The
plan shall also include witness/hold points where required. Witness/hold points shall be subject to agreement
with the Owner.
6.3.3 The Vendor/Contractor shall provide a project schedule showing all major activities with major dates for each
activity and the project critical path. Where the Vendor/Contractor considers that certain activities are the
responsibilities of the Owner, then these too shall be defined. Reasonable and sufficient time shall be given for
the Owner to review and agree the project schedule.
6.3.4 The carrying out of the quality control shall be the Vendor/Contractor's responsibility. However the Owner
reserves the right to ensure that the approved procedures are being followed. The Vendor/Contractor shall be
submitted to internal random audits by the Owner to ensure that an efficient QA programme is established and
complied with and that any non-conformance discovered during audits is promptly corrected.
6.3.5 The person in the Vendor/Contractor's organisation responsible for the Quality Assurance aspects of the
project shall be from the quality management team and independent from the rest of the project team.
6.3.6 The Vendor/Contractor shall provide a list of documents that he requires from the Owner and from sub-
contractors in order to fulfil his quality assurance obligations.
6.3.7 Sub-Contractors shall be asked in their quality plans to provide separate sections on software/communications
quality assurance. Copies of these sections shall be provided to Vendor/Contractor for review and comments.
6.3.8 The Vendor/Contractor shall have the responsibility to make sure that his sub-contractors carry out these plans
to the project standards. The Vendor/Contractor shall carry out Quality Assurance audits/monitoring of all sub-
contractors such that the QA Procedure/Plan is followed.
6.3.9 The number of audits/monitoring periods is not fixed, the Vendor/Contractor shall agree with the Owner the
frequency of these audits prior to Purchase Order/Contract placement.
6.4 Software Quality Assurance
6.4.1 All software packages shall be identified by revision and date. All software loadings and changes from the
commencement of the project shall only be from such identified software and all activities shall be entered in a
Project Log Book and signed and dated.
6.4.2 Security copies of the software shall be kept of all formal issues of the software including current and previous
issues.
6.4.3 The Vendor/Contractor shall place the commissioned master copy of his software in an escrow, the details of
which shall be agreed with the Owner.
Rev 0 1999
6.4.4 The various databases shall be stored using an agreed database package. Any text file or any drawing file
supplied shall use an Owner agreed file format.
6.5 Software Costs
All configuration costs associated with building, configuring the system (including all sub-systems),
implementing all communication links, development of all system databases, development of all reports,
development of all screens, system start-up support, commissioning the software system and any other effort
required to provide a fully functional system shall be detailed separately in the Vendor/Contractor's bid.
7.0 INSPECTION
An inventory check shall be carried to verify the correct supply of all parts, hardware and software modules,
interface equipment, cables and other associated equipment against the Purchase Order/Contract.
8.0 TESTING
8.1 Statutory Tests
8.1.1 The system equipment and software shall undergo formal testing at the following points.
FAT at the Vendor/Contractor's works.
SIT at site.
SAT and a sustained performance test at site.
8.1.2 Acceptance testing shall be carried out in stages i.e. FAT, SIT, SAT. At each stage the Vendor/Contractor shall
provide a detailed list of procedures to be followed during these tests. These tests shall test the functionalities
of individual parts of applications software and the complete packages. The tests shall demonstrate that the
requirements specified in this specification have been met. It shall be the Vendor/Contractor's responsibility to
ensure that the application software is fit for acceptance testing.
8.1.3 Testing shall be carried out by the Vendor/Contractor prior to FAT to ensure that all modules, hardware and
software comprising the total system comply with the specifications.
8.1.4 The Owner may accept test certificates specifying the tests conducted and the results obtained. However, the
Owner reserves the right to witness any test.
8.1.5 If as a result of testing, software changes are necessary, the Owner reserves the right to re-start the system test
period.
8.1.6 The Vendor/Contractor shall include in his bid, the cost of supplying all simulation packages and the relevant
hardware platforms, simulation software packages and cables for FAT and SIT (if required). The simulators
shall include all the necessary functions to test the full functionalities of all links. The hardware platform
machines selected shall be fast enough to test the links at the required speed.
8.2 Test Procedures
8.2.1 The Vendor/Contractor shall submit for approval, detailed test procedures for testing the overall system and
the integrated system. The procedures shall contain details of testing the various interfaces using simulators or
PC based equipment. Test procedures shall incorporate sufficient tests to demonstrate that the equipment
complies with all specifications and documentation. Tests shall, as far as possible, demonstrate the correct
Rev 0 1999
functionality of individual systems databases and file transfers when integrated as an overall system.
8.2.2 Test procedures shall take into account the need to demonstrate the correct operation of every aspect of the
sub-systems under conditions as close to operating conditions as practicable. As a minimum the tests shall
include basic link operation, verification, resilience, database consistency, performance and test for fault
tolerance where implemented. Tests shall verify the system response to power failures and auto restart. Tests
shall also demonstrate that the communication system will handle the maximum system load and fault
tolerance. The procedures shall define how this is to be demonstrated.
8.2.3 The procedures shall include all system simulation tests to be carried out, how the tests are performed, list test
apparatus and test equipment suppliers and documentation required.
8.2.4 Test procedures shall include detailed information on communication port settings, communication card switch
settings, communication cable wiring and software status flags.
8.2.5 Tests procedures shall include simulation and testing of system monitoring and security features. Test shall
also include component failures, cable breaks and power failures.
8.2.6 Each test contained in the test procedure shall include the following minimum information:
Test number and title;

Test objective;
Test procedure;
Check list;
Comments;
Fault report;
Reservations/further action;
Time and date;
Space for various witnesses signatures;
Reference to Test Equipment/Certification Documentation.
8.2.7 The procedures to be followed during the various stages of testing shall be approved by the Owner before the
start of each test. Procedures shall be submitted to the Owner for approval not less than 8 weeks before the
scheduled date for the commencement of testing.
8.2.8 System software and hardware documentation, including any diagrams or drawings as well as operator,
maintenance and system manuals shall be approved by the Owner, prior to the start of FAT. FAT shall not
commence until all documentation is submitted.
8.2.9 Provision shall be made within the test documentation to sign off or comment on each test. The completed
document shall be used as the basis for issuing test certificates.
8.2.10 If a fault or a deviation is identified during testing, then the test may be suspended at the Owner's discretion
until the Vendor/Contractor has rectified the fault or eliminated the deviation. Any retest shall be carried out at
no additional cost to the Owner. Retest may include all or parts of the tests already completed.
8.2.11 The above procedures shall apply to all stages of testing.
8.3 Factory Acceptance Testing
8.3.1 The capabilities of all operator interfaces shall be demonstrated during testing.
8.3.2 All database configuration, displays and features shall be tested for operation in accordance with the
specification.
8.3.3 Testing shall include testing of all spare parts and spare modules.
Rev 0 1999
8.3.4 A power supply test shall be included to verify the ability of the system to compensate for input power
variations as detailed in the specification.
8.3.5 A 90 day power up of all equipment to eliminate infant mortality failures shall be included.
8.3.6 Tests shall include fault tolerant tests to verify the operation of redundant processors, PSUs, I/Os, cables,
communication lists, bridges, routers, storage devices and operator interfaces such as VDU, printers and other
peripherals.
8.3.7 A check shall be carried out to verify that the system start-up procedure using the Vendor/Contractor start-up
procedure.
8.3.8 A separate log of all faults starting from the commencement of FAT up to site delivery shall be maintained and
shall become part of the test documentation.
8.3.9 The Vendor/Contractor shall issue revised documentation and drawings to cover any changes made as a result
of testing and as such their documentation and drawing shall show them in the "As delivered" state.
8.4 System Integration Testing
8.4.1 SIT shall be conducted after site installation of the equipment and satisfactory testing of individual units.
Rev 0 1999
8.4.2 Tests shall include testing all data links indicated on the Computer System Integration Diagram. Proper
functioning of all communication links and information transfer between various databases shall be verified.
As a minimum verification of analogue and digital signal transmission shall be carried out. The test procedure
shall be approved by the Owner. Additional tests related to the DCS, SCADA Systems and PLC interfacing
may be included by the Owner.
8.5 Site Acceptance Testing
8.5.1 SAT shall include verification of the correct system operation of the systems under varying communication
conditions for both the normal and standby links.
8.5.2 Proper operation of all application oriented functions shall be verified in the real environment, including
system response times and system loading performance.
8.6 Sustained Performance Test
8.6.1 After SAT a sustained performance test shall be carried out. Successful completion of this test shall be defined
as 1,000 hours of operation without any fault.
8.6.2 If faults or malfunctions occur during SIT, SAT or the sustained performance test, the Owner reserves the right
to demand such changes as may be necessary to eliminate the fault or malfunction at the Vendor/Contractor's
expense, who shall make the necessary repairs of any fault or malfunction which may occur until final
acceptance of the system.
8.6.3 If a fault occurs necessitating hardware or software design changes, the Owner reserves the right to restart the
sustained performance test after implementation of the changes.
9.0 DOCUMENTATION
9.1 Introduction
9.1.1 This section covers the documentation required for the design, selection, fabrication, inspection and testing for
all the MIS equipment, components and services to be provided against this specification.
9.1.2 The detailed list of documents that are required is attached to the Purchase Order/Contract. However, as a
minimum, the following listed documents shall be provided by the Vendor/Contractor.
Functional Definition Specification;

Design Studies;
System configuration and verification report;
Completed configuration sheets;
Protocol verification and data format verification report;
Printout report of displays;
MIS Database;
FAT Procedures;
Test dossier including Test Certificates;
SIT and SAT procedures;
System user manuals (for use by the system engineer);
Operator's user manual;
System reference manuals;
Software documentation;
Application software listings;
Hardware documentation;
Cable wiring diagrams;
Operating System documentation;
QA/QC Manual;
Rev 0 1999
As Built documentation;
Spare parts list.
9.1.3 Detail documentation shall be submitted in accordance with the schedule specified in the Purchase
Order/Contract to confirm compliance with the relevant specifications, and to allow a full and continued
appraisal to be made of the on-going design and development.
9.1.4 Any production or procurement or services undertaken prior to the relevant documentation being submitted
and reviewed by the Owner is at the Vendor/Contractor's risk.
9.1.5 On all documentation the Purchase Order/Contract number, equipment title, equipment number and project
name shall be quoted.
9.1.6 The Vendor/Contractor shall comply with the standards detailed in the QA/QC programme.
9.1.7 Documents shall be of the stand alone type. Excessive use of cross references shall be avoided.
9.1.8 An index of all Vendor/Contractor's documentation shall be kept and strict control of the documentation
revisions shall be maintained.
9.1.9 The final "As Built" documentation shall consist of all previously submitted documentation updated to reflect
any changes made during testing and final system installation and commissioning.
9.1.10 System manuals shall be an overview to those manuals provided by sub-contractors and shall include a
complete schematic of the installed sub-system and integrational aspects.
Brief summary of each sub-system and its functions as related to the overall system.
Index of reference documentation, contract personnel, companies, help information.
Any information not contained in the standard manuals.
9.1.11 The system reference manual shall include explanation of system operation, database structure and system
maintenance functions. The reference manual shall be for the use of system engineer. The manual shall include
details of the MIS software packages and shall contain sufficient details for ongoing system maintenance. The
contents of this manual shall reflect the licence agreement. The topics covered in the manual shall include but
not be limited to:
Fundamentals of the operation of the various software modules;

Description of the various MIS interfaces;
Documentation of the database;
Site-specific installation information such as data file names and similar information;
Documentation of system maintenance utility programmes.
9.1.12 Software documentation shall include all operating systems, languages compilers, interpreters, utilities,
applications, network and other documentation.
9.2 Schedules and Reports
9.2.1 The Vendor/Contractor shall submit with his bid a preliminary Quality Control Plan.
9.2.2 The Vendor/Contractor shall incorporate any revisions agreed with the Owner during the enquiry review stage
and submit revised tender documentation for approval.
9.2.3 Monthly reports shall be submitted by the Vendor/Contractor detailing design, procurement, production and
documentation activities. The format of the monthly report shall be agreed with the Owner.
Rev 0 1999
9.3 Data and Calculations
9.3.1 Project specific instructions shall be issued with the Purchase Order/Contract, which describes the data and
calculations to be submitted, and the methods of submission.
9.3.2 All calculations shall be carried out in clear and logical manner. Where conditions involve the use of formulae
or methods not specified in the Purchase Order/Contract, the source of these formulae or methods shall be
clearly referenced.
9.3.3 Computer calculations will only be acceptable if all inputs are shown together with the calculated values of
intermediate terms and factors and options chosen, as well as the final calculated value and the computer
program has been validated to the satisfaction of the Owner.
9.4 Drawings
The drawings listed with the Purchase Order/Contract shall be sent by the Vendor/Contractor to the Owner for
review and approval. Drawings shall be certified final upon the commissioning of the MIS system.
9.5 Final Records, Documents and Manuals
9.5.1 The Vendor/Contractor shall supply two (2) sets of Data Books and six (6) sets of the installation, operation
and maintenance manuals.
9.5.2 The software shall be certified final by the Vendor/Contractor upon acceptance of the MIS system by the
Owner.
10.0 PRIOR TO SHIPMENT
10.1 Painting and Coatings
10.1.1 Painting and protective coatings shall take into account the methods of transport to be used.
10.1.2 Surface preparation, painting and painting materials shall be in accordance with GES X.06.
10.1.3 The Vendor/Contractor's standard painting and coating systems may be acceptable subject to Owner's
approval, provided they are equal to or better than the Owner's standards specified in GES X.06 and are
equally suitable for the site environmental conditions specified in GES A.06.
10.2 Spares
The Vendor/Contractor shall submit with his proposal a priced list of recommended spares for start-up and two
year's operation for review by Owner.
10.3 Packing and Storage
10.3.1 This section describes the minimum requirements for the preservation and protection of the MIS equipment
during the sea and land transportation and storage prior to installation.
10.3.2 The probable storage period will be specified in the order/enquiry and will extend from the time to despatch to
the time of unpacking at site. If the storage period is not stated, a minimum period of 24 months shall be
assumed. Packing to be suitable for sea freight.
10.3.3 The cabinets and cabinet components shall be securely packaged such that they are protected against external
damage during transit.
Rev 0 1999
10.3.4 Cabinets or panels shall be crafted in moisture-proof sealed crates containing a desiccant for seagoing
shipment.
10.3.5 All components with moving or sensitive parts shall be removed from the cabinet prior to shipping, and shall
be suitably packed and shipped separately from the cabinet.
10.3.6 All loose electronic circuit boards and components shall be packaged in sealed, moisture-proof bags. If any of
the electronic circuit boards contain electrostatic sensitive components they shall be packed in conductive bags
with warning labels.
10.3.7 All modules shall be removed from swing frames and shall be suitably packed and shipped separately from the
cabinet.
10.3.8 Swing frames shall be secured so as to prevent their accidental opening, due to vibration, etc. during transit.
10.3.9 The Vendor/Contractor shall ensure that heavy items of equipment, e.g. power supplies, which are adequately
supported during transit.
10.3.10 All loose cables, tubing, etc., which are disconnected for ease of shipment shall be securely tied back and
identified.
10.3.11 Where multiple crates or packages are used, then each shall be individually numbered and the number clearly
marked on the outside of the crate or package. a packing list relating the crate or package number to the
contents shall accompany the consignment.
10.3.12 All open cable entry parts shall be protected by plastic plugs.
10.3.13 The equipment shall be crated to allow movement by forklift, rollers, crane slings, or skidding. The packing or
crating shall provide proper equipment protection, with consideration given to the site environmental
conditions. The Vendor/Contractor's own recommendations shall be considered in this respect.
10.3.14 The crates shall be clearly marked by a warning label together with appropriate symbol indicating the nature of
the contents and balance points. The crates shall be marked to indicate the balance point. The weight of each
crate shall be marked on at least two sides both, in killogrammes and pounds, in painted numerals at least 3
inches (75mm) in height.
10.4 Shipping
The panels shall not leave the Vendor's/Contractor's works for shipment until the release has been signed by
the Owner's Inspector.
Rev 0 1999
10.5 Service Support
10.5.1 The Vendor/Contractor shall identify in his bid the recommended maintenance and service organisation
nearest the installation site and shall provide details of suitable support related personnel services available at
that location.
10.5.2 The Vendor/Contractor shall also detail in his bid training courses available (at site or at Vendor/Contractor's
works) and their location for personnel who will operate and maintain the MIS system at site.
10.5.3 The Vendor/Contractor shall provide compatible spares for at least 10 years from product withdrawal. The
Vendor/Contractor shall notify in writing of any product withdrawal at least six months prior to date of
withdrawal.
10.6 Warranty
10.6.1 The Vendor/Contractor shall warrant all materials and services supplied, against any defect, for a minimum
period of 12 months after commissioning or 24 months from the date of delivery to the site, whichever is the
shorter period, or for the period stipulated in the Purchase Order/Contract.
10.6.2 Should any item be found defective, the Vendor/Contractor shall be responsible for all costs associated with
restoring the equipment to the standard specified in the Purchase Order/Contract. The Vendor/Contractor shall
undertake to carry out the repair or replacement in an expeditious manner.
10.6.3 The terms and conditions of this Warranty shall be additional to any other requirements specified in the
Purchase Order/Contract.
10.6.4 Hardware and software warranty shall be provided for a period of one year after successful completion of the
SAT and sustained performance test or 2 years from delivery to site whichever is sooner.
10.6.5 Any software remedial action during the normal warranty period shall carry a further one year warranty.
However, the total period shall not exceed a period of three years from takeover.
10.6.5 Acceptance of the system by the Owner shall not release the Vendor/Contractor of any warranties,
responsibilities or obligations to furnish equipment and materials in accordance with this specification.
10.6.6 The Vendor/Contractor shall state in his bid if the warranty is valid for direct purchase only or whether it can
be transferred to the Owner.
10.6.7 The Vendor/Contractor shall state the warranty coverage period if it is other than 24 hours all year around
basis.
10.6.8 Notwithstanding any maintenance or license agreement between the Vendor/Contractor and the Owner, the
Vendor/Contractor shall make available to the Owner a secure copy of all source codes for the lifetime of the
plant. The source code shall be kept in a safe at the Vendor/Contractor's offices and in the event of the failure
the Vendor/Contractor shall be expected to supply this to the Owner free of charge.
10.6.9 The Vendor/Contractor shall provide a quotation for an extended on-site warranty/on-site maintenance
contract.
DATA SHEET No.
DATA INTERFACES AND PROTOCOL

P.O. / CONTRACT No.
CLIENT
PLANT LOCATION SHEET 1 of 1
SERVICE ITEM No. No. of UNITS
1 VENDOR / CONTRACTOR
2
3 Interface Data Remarks
4 Data source device
5 Model number
6 Data destination device
7 Model number
8 Data base I.D.
9 Protocol / synchronous / asynchronous
10 Version No.
11 Protocol commands / functions
12 Electrical connections RS 232 / 422 / 485 etc.
13 Single / multi-drop
14 Master slave / peer to peer
15 Transmission media
16 Copper / Co-axial / fibre optic
17 Baud rate
18 Number of data bits
19 Number of start bits
20 Number of stop bits
21 Parity type / method
22 Address of source device
23 Comms board / port device
24 Comms board / port number
25 Maximum distances between devices
26 Buffer size
27 Length of message
28 Type of handshake
29 Comms card switches
30 Comms cable wiring diagram
31 Double buffering required
32 Source / target registers
33 Specific protocol requirements e.g. set flags for new data etc.
34 after reading, 16 or 32 bit
35 data, single / double precision
36 IEEE 64 bit floating point etc.
37 Data blocking details
38 Link master
39 Level of redundancy
40 Protocol deficiency / limitations
41 Remarks / comments
42
43
44
45
Revision No./Date
Prepared by/Date
Authorised by/Date
Purpose
(C) 1999 NATIONAL OIL CORPORATION. The information on this sheet may be used only for the purpose for which it is supplied by NOC.
K:\nocspecs\SPECIFICATIONS\j-series\j-25\dj2501r0.xls Sheet1

National Oil MIS Specification

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

National Oil MIS Specification

Uploaded by

Copyright:

Available Formats

NATIONAL OIL CORPORATION

GENERAL ENGINEERING SPECIFICATION

MANAGEMENT INFORMATION SYSTEMS

Rev Date Description Checked Approved

Compiled by Teknica (UK) Ltd

1.0 SCOPE OF SPECIFICATION 4

2.1 List of Abbreviations 5

3.1 Codes and Standards 6

5.1 Open Systems Requirements 17

6.0 PROJECT ACTIVITIES 19

6.1 Project Team 19

8.1 Statutory Tests 21

10.0 PRIOR TO SHIPMENT 26

10.1 Painting and Coatings 26

DATA SHEET (1)

1.2 Other NOC Specifications

GES A.06 Site Data

GES C.54 Commissioning of Microprocessor Based Instrument Systems

GES J.16 Instrument Cable and Cabling

GES J.20 Distributed Control Systems

GES J.22 Field Automation (SCADA) Systems

GES J.26 Metering and Meter Proving Systems

GES J.27 In-Line Blending Systems

GES J.29 Centralised Tank Farm Monitoring Systems

2.1 List of Abbreviations

API Application Programming Interface

The commercial terms used in this specification are defined as follows:

The company supplying the equipment and material.

The main contractor for a defined piece of work.

3.1 Codes and Standards

British Standards Institution (BSI)

BS 5515 Code of Practice for Documentation for Computer Based Systems

BS 5750 Quality Systems (All Parts) - Equivalent to ISO 9000 series

BS 5760 Reliability of Systems, Equipment and Components (All parts)

BS 5887 Code of Practice for Testing of Computer Based Systems

BS 6238 Code of Practice for Performance Monitoring of Computer-based Systems

BS 6488 Code of Practice for Configuration Management of Computer-based Systems

Electronic Industries Association (EIA)/CCITT Recommendations

RS 422 Electrical Characteristics of Balanced Voltage Digital Interface Circuits

Institute of Electrical and Electronic Engineers (IEEE)

(a) Establish the process facilities operations and maintenance systems;

(b) Establish the process facilities production targets and objectives;

(e) Evaluate individual plant's information needs;

(i) Evaluate methods to minimise costs and maximise efficiency.

3.2.4 Further Scope

Improvements in selected areas of plant management.

Improvements in the existing plant IT systems.

Define overall requirements of the plant MIS.

Define data requirements.

Selection of DBMS package.

Information System planning including data set requirements.

Software package(s) selection.

Standardisation of hardware platform.

Optimisation package(s) requirements.

Define priority applications.

Define enhancement applications.

Software maintenance requirements and costs.

Cost benefit analysis of the proposed implemention.

System overview diagram.

Data flow diagrams.

Functional specification of the proposed system.

Proposed data sets.

Proposed software implementation details .