transnet capital projects - etenders.gov.za · transnet capital projects ... 4.1 information...

Transnet Capital Projects

Historian Functional Design Specification

Note: Check Aconex system for latest revision

2684358-P-A00-IN-SP-002 of 15

Table of Contents

Acronyms ........................................................................................................................................ 3

1. Introduction .............................................................................................................................. 4

1.1 Purpose of Document ....................................................................................................... 4 1.2 Scope of this Document ................................................................................................... 4

2. Exclusions ................................................................................................................................ 4

3. Background .............................................................................................................................. 4

4. References ............................................................................................................................... 6

4.1 Information References .................................................................................................... 6

5. Functional Requirements ....................................................................................................... 7

5.1 Architecture ...................................................................................................................... 7 5.2 Availability ......................................................................................................................... 8 5.3 System Functionality ........................................................................................................ 9

5.3.1 Data Acquisition and Archiving ............................................................................. 9 5.3.2 Security ............................................................................................................... 10 5.3.3 Data Backup ....................................................................................................... 10 5.3.4 Client Tools ......................................................................................................... 10

5.4 Data Collection and Archiving Interfaces ....................................................................... 12 5.5 Data Retrieval Interfaces ................................................................................................ 13 5.6 Diagnostics ..................................................................................................................... 13 5.7 Licensing ........................................................................................................................ 14 5.8 Archive configuration ...................................................................................................... 14 5.9 Performance ................................................................................................................... 14




2684358-P-A00-IN-SP-002 of 15

Acronyms

Abbreviation Definition

API Application Programming Interface

ASCII American Standard Code for Information Interchange

CN Control Narrative

CO Co-ordinating Officer

DDS Detail Design Specification

DJP Durban-Johannesburg Pipeline

DOL Direct-On-Line

EDS Engineering Design Specification

F&G Fire and Gas

FC Flow Computer

FDS Functional Design Specification

GIS Geographic Information System

HTP (PS3) Hilltop

HVAC Heating, Ventilation and Air Conditioning System

I/O Input/Output

IN Inland Network

IVW (TM1) Coastal Terminal (Island View)

JMP (TM2) Jameson Park – Inland Terminal

LDAP Lightweight Directory Access Protocol

MBT (PS5) Mnambithi

MBV Motorised Block Valve

MCC Master Control Centre

MPP Multi-Product Pipeline

NMPP New Multi-Product Pipeline

NOC National Operations Centre (MCC)

OLE Object Linking and Embedding

OPC OLE for Process Control

PCS Process Control System

PL1 Pipeline One (IVW to JMP - 24” MPP Pipeline)

PLC Programmable Logic Controller

PLMS Pipeline Monitoring System

PSx Pump Station x

RPP Refined Products Pipeline

SCADA Supervisory Control and Data Acquisition

SCC Secondary Control Centre

SO Station Operator

STM 1 Synchronous Transport Module level-1

TBA To be advised

TBC To be confirmed

TBD To be defined

TCP Transmission Control Protocol

TGS Tank Gauging System

TNI (PS1) Twini

VLR (PS8) Villiers

VSD Variable Speed Drive

WDN (PS7) Warden




2684358-P-A00-IN-SP-002 of 15

1. Introduction

1.1 Purpose of Document

This document formulates the functional design specification for the procurement and detail design of a real time data historian for Transnet Pipelines (TPL), to support all TPL process control system operations.

1.2 Scope of this Document

This document records the requirements for the procurement and detail design of a real time data historian for Transnet Pipelines (TPL). The following are addressed:

1. The functional and system requirements for the real time data historian

2. The interface requirements to the following systems:

Process Control System (PCS)

Tank Gauging System via PCS

Product Custody Metering System

2. Exclusions

Excluded from the scope of this are interfaces to the following operational systems:

The Pipeline Monitoring System (PLMS) – Contains a dedicated historian

Geographic Information System

Security and Situation Management System

3. Background

TPL operates the following pipelines:

A 24” MPP line consisting of two storage facilities at each end, Island view in Durban and

Jameson Park in Johannesburg with three pump stations and various automated

segmentation valves and metering points along the pipeline.

A multiproduct inland network consisting of various pipelines.

Crude oil pipeline, for crude oil from Durban to Sasolburg, Secunda and Kendal with various

pump stations, segmentation valves and metering points along the line.

RPP pipeline, multiproduct from Durban to Johannesburg with various pump stations,

delivery stations, segmentation valves and metering points along the pipeline.

AVTUR pipeline, AVTUR from NATREF to OR Tambo Airport with various pump stations,

and a delivery station at OR Tambo.

The pipelines and the product transfer between delivery stations are controlled from the

National Operations Centre (NOC) in Pinetown. Product deliveries and transfers at the

delivery depots is controlled locally on site with monitoring from the NOC.

TPL also monitors pipelines operated by others:




2684358-P-A00-IN-SP-002 of 15

Gas line

Below is an illustration of the TPL pipeline network.

Figure 1: TPL Pipeline Network

Control and monitoring of the respective pipelines and associated stations rely on data communication networking infrastructure.

The 24” MPP line is provided with Ethernet at each of the control centres, terminals and pump stations, via a dedicated fibre optic infrastructure with a backup facility provided by a STM16 link from Johannesburg to Durban effectively making the communications backbone a ring topology between Johannesburg and Durban.

The Inland pipeline network is provided with STM 1 infrastructure either via a fibre optic link from Johannesburg or a microwave link from the nearest site linked with fibre optics. These are all single links with no redundancy.

The Crude, RPP and AVTUR lines are provided with a mixture of frame relay networking and STM1 infrastructure provided by Microwave links.

Systems used to operate the pipelines include:

PLC / SCADA System for pipeline control and monitoring




2684358-P-A00-IN-SP-002 of 15

Product Custody Metering System for measuring product quantities for custody transfer and non-custody transfer

Tank Gauging Systems for measuring product volumes at storage facilities

Machine Monitoring Systems for monitoring condition of the major product pumps at the pump stations depots and terminals

Pipeline Monitoring System for batch tracking and leak detection

4. References

4.1 Information References

No. Doc Number Revision

[1] Process Control User Requirements

Specification

2684358-J-SCO-CS-SP-002

C

[2] MIS User Requirements Specification 2684358-P-A00-SY-SP-001

03

Note: When this document is issued to the Contractor for engineering, in each instance where an applicable reference’s revision is stated as ‘Latest approved’, the specific revision of such applicable references will be declared to the Contractor.




2684358-P-A00-IN-SP-002 of 15

5. Functional Requirements

5.1 Architecture

A functional architecture of the historian system is indicated below.

Figure 2: System Functional Architecture

Sites

(Autonomous)

ERP

NOC

Process

Control

Servers

Process Control

View ClientHistorian

Data

Collector

with Store/

Forward

TGS

MMS

Historian

Data

Client

Process

Control

Servers

(LWC)

Process

Control View

Client

Historian

Data

Collector

with Store/

Forward

Historian

Data

ClientHistorian

Data Archive

(Process, Alarm,

Event,

Aggregated

Data)

(Redundant

partner in NOC)

MIS

Reporting

Clients

Reporting

Clients

Historian

Data

Client

Legend Historian

MES

Metering




2684358-P-A00-IN-SP-002 of 15

The system shall be expandable to all TPL assets including to the Crude line, RPP line, AVTUR line, 24” MPP line and the 24” MPP inland network. Thus the system shall be scalable to accommodate at least 50 sites with an average of 1500 archived tags per site (assume 80% real values).

Sites shall operate autonomously with respect to data collection functions, in the case of a network failure to the NOC, i.e. it shall not be dependent on any services provided in the NOC or offsite to perform its normal data collection functions.

During a connectivity loss to the NOC, Updates to the Reporting and historian client are not required at remote sites.

Other reduced functionality shall be clearly identified by the systems provider and submitted to TGC and client for acceptance.

The system shall automatically upload data from the data collector to the historian data archive following network recovery (after loss thereof).

Preference will be given to solutions that are independent of operating system, or alternatively, to non-Windows based systems.

5.2 Availability

The following availabilities for the various functions shall apply:

o Data Collection – 99.9%

o Data Archive - 99.9%

o Central historian node for reporting – 99.9%

The period for which data is stored on site in the event of a network failure to the data archive/s shall not be less than 7 days.

The system shall auto recover from any communication loss and withstand communication degradation.

The system shall allow the online addition, deletion and reconfiguration of tags without interrupting the operation of the system data collector or data archive.

There shall be no single point of failure in the system for data collection and data archiving functions.

Where redundancy can be provided on other levels, it should be indicated by the system provider to TGC for consideration.

It shall be possible to do system upgrades, updates and migrations online in parts, which does not require an entire system shutdown.




2684358-P-A00-IN-SP-002 of 15

5.3 System Functionality

The system shall provide the following functionality:

5.3.1 Data Acquisition and Archiving

Auto and manual acquisition of data. Manual entered values to be enterable against a operator selectable time.

Support archiving for:

o Digital values

o Integer values (8, 16, 32 and 64 bit)

o Real values (32 and 64 bit)

o String values (To a max of 255 characters)

o Alarms (With state changes (active, not active, acknowledged) and associated timestamps)

o Events (With state changes (active, not active) and associated timestamps)

Compression - Data shall be compressed and stored:

o On delta (with time and/or value dead-bands); or

o Cyclically.

Differing storage methods and rates shall be configurable on a per tag basis.

Support the structuring of variables in hierarchical structure, independent of the PCS with at least two hierarchies, configured as a functional and physical hierarchy.

Calculation of derived values. The system shall support the following:

o Calculation of derived values as a result of an expression on archived values

o Calculation of derived values upon the following triggers:

Configurable time based triggers

Configurable event (value changes) based triggers

Custom rule based triggers

It shall be possible to calculate rolled up derived values using the hierarchical structures defined.

It shall be possible to configure the system to either archive or not to archive the result of a derived value calculation and calculate when requested.

Support for time stamping at data source, archive or at data collector.




2684358-P-A00-IN-SP-002 of 15

5.3.2 Security

User authentication levels for the following:

o Administrator (Ability to change user configuration)

o Technician (Ability to configure system and reports, change values and view)

o Operator (Ability to enter manual values and view)

o View only (Ability to view all data)

The system should be able to integrate into a LDAP (or similar) central managed user management directory service e.g. Active Directory, Open LDAP.

The system shall not be dependent on the directory service being available at all times to perform any of the functionality required by this specification. The system should cache credentials as required.

If LDAP Microsoft active directory is not used, the system shall provide its own central user configuration, authentication and authorisation functionality.

5.3.3 Data Backup

The following system functions shall be provided:

An automatic and manual data backup function to backup the historian data archive onto external storage. Auto backup function to support time based and size based triggers.

A manual data restore function to restore a backup of the historian data archive from external storage.

5.3.4 Client Tools

Historical data viewing in tabular and graphical (trend) format with:

o Operator selectable time ranges

o Predefined time ranges relative to current time

o Operator selectable on/off for auto refresh to current time

o Support for at least 20 pens (trends), each with a different operator selectable colour

o Combined Tabular/Graphical view with the tabular view displaying the times and values of graphical view at a specified time, specified via a operator movable line/ruler

o Ability to save a configured view per system user

o Auto scaling

o Support for multiple ranges on one trend display (multiple Y-axis)

o Zoom and pan functionally

o A tag search facility which can accept wildcards




2684358-P-A00-IN-SP-002 of 15

Viewing of historical data via a web interface with same functionality as above

Export of historical data in text and ASCII (delimited) format for:

o A selectable time range

o The viewed graphic

The Historian Client tools shall provide native functionality to manually enter and alter values in the Historian archive.

Event log for manually entered and corrected values recording the originator (user), time and an operator entered comment.




2684358-P-A00-IN-SP-002 of 15

5.4 Data Collection and Archiving Interfaces

The system shall support the following interfaces for data collection and archiving:

Table 1: Data Collection and Archiving Interfaces

Type Comment

PCS:

Siemens PCS7 system with redundant OS server pair (v8 and later)

OPC DA 2.0

OPC A&E 2.0

Read of process data, alarms & events from PCS

Read of process data from PCS

Read of alarms & events from PCS

OPC UA Future

SAP MII(latest) Future

.Net Remoting Future

Direct SQL Future, including PowerTech IST ecWIN for Electrical Metering System

Emerson Floboss S600+ Flow computer interface

Future




2684358-P-A00-IN-SP-002 of 15

5.5 Data Retrieval Interfaces

The system shall provide the following interfacing mechanisms for third party applications to query the Real Time Data Historian archives:

Table 2: Data Retrieval Interfaces

Type Comment

Web Services

SAP MII Future

.Net Remoting Future

Direct SQL Future

API A documented API interface

OLEDB and ODBC providers

5.6 Diagnostics

The following minimum system events shall be logged and accessible to the user for debugging:

o Archiving start / stop

o Configuration changes

o Disk space warnings

The following minimum system errors shall be logged and accessible to the user for debugging:

o Communication failure between data collector / historian

o Loss of redundancy and system errors

o Archiving errors

o Data collection errors between data source and data collector

o Tag read / write failures

o Configuration errors




2684358-P-A00-IN-SP-002 of 15

5.7 Licensing

Licensing shall be a once-off licence without any time based renewal.

Licensing for web clients/views, if required, should be floating and concurrent. i.e. first come first serve.

5.8 Archive configuration

Where available the following values shall be archived as a minimum:

Process variables, e.g. Flow, Pressure, Temperature, Levels

Analysers

Volumes (compensated and non-compensated)

Equipment (DOL, VSD and valve) statuses

Sequence states

Instrument status/failures.

Alarms (With state changes (active, not active, acknowledged) and associated timestamps)

Events (With state changes (active, not active) and associated timestamps)

Details of what is logged for each typical to be developed in the DDS.

5.9 Performance

Limitations:

Networking performance to be assumed:

o 60 Mbps available bandwidth for STM1 and 24” MPP sites and 128 Kbps for Frame Relay sites, shared with PCS

o Latencies up to 150ms per end to end link

System performance to be no less than:

Process value data collection rate of 1000 tags per second per site (assume 80% real values)

Process value archiving rate should support archiving of site data, specified in section 5.1, within a period of 10 seconds. (assume 80% real values)

Forwarding of site collected data after loss of communications shall occur within a 24 hour period

Alarm and event archiving to handle burst of 3000 messages in 4 seconds per site

Data retrieval rates shall support displaying of 20 tag values for a 24 hour period at a resolution of 10 second intervals in no more than 1 second on a trend display on the high bandwidth sites (60 Mbps)




2684358-P-A00-IN-SP-002 of 15

Data retrieval rates shall support displaying of 20 tag values for a 24 hour period at a resolution of 10 second intervals in no more than 3 second on a trend display on the low bandwidth sites (128 Kbps)

The above will be measured on the standard trend interface for multiple tags (pens)

Data storage capacity of 2 years with automated longer term archive.

Mechanisms to achieve the performance to be included and documented in the design. Any restrictions or concession on the performance to be declared and accepted by TGC and client.

transnet capital projects - etenders.gov.za · transnet capital projects ... 4.1 information...

Documents