Saes Z 008
Saes Z 008
Contents
1 Scope ................................................................ 2
2 Conflicts and Deviations ................................... 4
3 References........................................................ 4
4 Definitions ......................................................... 5
5 Tms General Requirements ............................ 10
6 Operation Specific Requirements for TMS ...... 12
7 Tms Control Layer Configuration .................... 19
8 Tms Components Configuration ..................... 24
9 Electrical and Environmental Conditions ......... 32
10 Operation Centers........................................... 32
Appendix A - Typical Product Tank Allocation ........ 33
Appendix B - Typical Tank Truck Unloading ........... 34
Appendix C - Typical Tank Truck Loading
(No Queue) ........................................ 36
Appendix D - Typical Queue Algorithm ................... 39
Appendix E - Typical Tank Truck
Loading (with Queue) ........................ 44
Appendix F - Typical Pipeline Meter Proving .......... 48
Appendix G - Typical Bulk Plant
Automation Overview ........................ 49
1 Scope
1.1 This document prescribes the minimum mandatory requirements and guidelines
governing the engineering, design and installation of Terminal Management
Systems (TMS) in a Saudi Aramco Bulk Plants Terminal automation. The TMS
is used to automate the bulk plant or other plants operations where product is
loaded (shipped) and unloaded (received) through road truck, rail car, ship
vessel and pipeline.
1.3 Below table provides a matrix for TMS components use by process.
Authentication System
Truck Identification
Gauging/Inventory
Driver Verification
Queue Monitoring
Order Information
Preset Controller
Automatic Tank
System (DVS)
System (OIS)
Management
System (TIS)
(DID/DVS/OIS)
ESD System
Weighscale
Application
Application
Business
Control
Process↓ X Component→
Note: Some of the listed TMS components are not within the scope of this standard.
Saudi Aramco: Company General Use
Page 3 of 49
Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 2 May 2019
Next Planned Update: 11 October 2021 Design of Terminal Management Systems
1.4 This entire standard may be attached to and made a part of purchase orders.
Any conflicts between this document and other applicable Mandatory Saudi Aramco
Engineering Requirements (MSAERs) shall be addressed to the EK&RD Coordinator.
Any deviation from the requirements herein shall follow internal company procedure
SAEP-302.
3 References
Specific sections of the documents listed below are referenced within the body of this
standard. Material or equipment supplied to this standard shall comply with the
referenced section of the latest edition of these documents. Where specific sections are
not referenced, the equipment or material shall comply with the entire referenced
document.
International standards
ANSI/ISA-88 Batch Control
ANSI/ISA-95 Enterprise-Control System Integration
4 Definitions
4.1 Abbreviations
ATG Automatic Tank Gauging
BOL Bill of Lading
MSC Metering Supervisory Computer
DCS Distributed Control System
DID Driver Interface Device
DVS Driver Verification System
ESD Emergency Shutdown Systems
ERP Enterprise Resource Planning
FACP Fire Alarm Control Panel
HMI Human Machine Interface
I/O Input / Output
LAN Local Area Network
LIMS Laboratory Information Management System
MES Manufacturing Execution System
MOV Motor Operated Valve
OLE Object Linking and Embedding
OPC OLE for Process Control
4.2 Definitions
In this standard, the terms “must”, “shall”, “should” and “can” are used.
When “must” or “shall” are used, the item is a mandatory requirement.
When “should” is used, the item is strongly recommended but not mandatory.
When “can” is used, compliance may further enhance the system functionality
but is optional.
Estimated Time of Arrival (ETA): The Estimated Time of Arrival when the
product switch occurs on multiproduct pipeline.
Operational Data: The statistical data such as process values and alarm limits,
tuning parameters, etc.
Reliability: The probability that a system will provide correct outputs up till
some given time.
Restricted Access Level: The TMS system access authority level where users
has right to perform critical and key business processes. Normally, these
authorization are given to system administrator, plant superintendent, and plant
manager.
Tag ID: The unique alphanumeric code assigned to inputs, outputs, equipment
items, and control blocks. The tag ID might include the plant area identifier and
unique throughout the plant.
Tank Reconciliation: Tank Reconciliation tracks all the fuel that enters or exits
in each tanks, regardless of delivery or dispensing activity. The reconciliation
reports can generate on a shift, daily, weekly, etc., basis to provide the current
state of product, quality and delivery/receipt quantity.
5.1 The TMS shall meet the Sections 5 to 20 requirements defined in SAES-Z-001.
5.3 TMS shall have capability to implement alarm rationalization process for all
configured alarms as per SAEP-368 and Section 12 of SAES-Z-001.
5.4 The TMS shall be designed and configured to for safety functions using the
SAES-J-601, SAES-B-014 and SAES-B-070 . The ESD system shall initiate
shutdown in the event of an emergency and abnormal operation to protect the
peoples, assets and environment.
5.5 TMS shall designed and configured to meet SAEP-99 requirement and the latest
vendor recommendations.
5.6 TMS shall be designed using Domain Controller to control device connectivity
on the Plant Network and User Account Management.
5.7 TMS System shall be designed using redundant architecture to meet the fault
tolerant functionality.
5.8 The TMS shall be designed using integrated approach with components,
subsystems, and field devices to ensure reliable communication.
5.9 The TMS shall configure to display the health of all components and facility.
The TMS system overall status shall be displayed dynamically on HMI same as
system architecture drawing. The system shall have the ability to switchover
manually to standby device as well as enable /disable the communication of a
device from the graphics object itself.
5.8 The TMS shall be configured to implement the functions of Oily water,
Sampling, blending and VRU sub-system applications or able to interface with
these sub-systems through standard protocol such as MOD bus, OPC etc.
5.10 Control layer (PCS) and ESD components of the TMS are allowed to install in
outdoor if components approved by Saudi Aramco for outdoor application and
the design improves the CAPEX and OPEX. The outdoor design shall be
reviewed and approved by all stake holders.
5.11 The TMS shall be configured to record all business actions / transactions with
time stamp e.q. the tanker entry, loading starting.
5.12 The TMS System shall be designed to achieve 5 seconds or less response time to
any transaction action. For example, confirmation or error message shall
display on Preset within 5 seconds or less after data entered into Preset
Controller.
5.13 The TMS shall be configured to have the capability to enter data manually and
perform the validation of driver, tank truck and order details.
5.14 The TMS shall be configured to upload / download the transactions to the
Enterprise Resource Planning System/host computer in auto and manual mode.
5.15 The TMS shall be configured to allow manual entry of product density for mass
and volume calculations.
5.16 The TMS shall be configured to automatically upload/download the online and
offline product density using restricted access level.
5.18 The TMS shall be configured to perform automatic and/or manual order matching
task. The operator shall be promoted to acknowledge the auto order matching.
5.19 TMS shall be configured to allow to create emergency orders as well as accept
manually entered order details from authorized site personnel.
5.21 The TMS shall be configured have the capability to schedule the trucks / batches
in auto or manual mode.
5.22 The TMS shall configure the rules for queuing and assigning the bay. The rules
shall be based on arrival time and priority driven weightage method. The
weightage calculation shall be real time on the basis of current time and its
priority.
5.23 The TMS shall have the capability to show the details of orders (product receipt,
dispatch and transfer) in a GANT Chart and shall have predefined reports.
5.24 The TMS shall provide process and deviation alarms / advisory messages for all
events and incidents to alert operator with correct expected action message. The
message example “Enough tanks are not allocated to meet the batch under
allocation”.
5.25 All events and logs shall be recorded in a single database where viewing and
tracking can be done using unique field such as order or equipment number.
6.1.3 The TMS shall not allow to change the details of orders which are
loaded into auto mode.
6.1.4 The TMS shall have a provision to allow operator to enter comments
when they manually update transactions/order details.
6.1.7 The TMS shall be configured to allow operator to reassign the bay to
already assigned bay to a truck.
6.1.8 The TMS shall be configured to allow operator to stop the loading
operation intermediate in case of unsafe or abnormal situation.
6.2 LPG, Sulphur, Crude Oil, Asphalt and Vacuum Bottoms Loading
6.2.1 The TMS shall measure the weight of loaded Product using weighing
scale and shall calculate net weight of loaded product in the truck or
rail tanker using initial and final weight.
6.2.2 If required, the TMS shall configured meet Section 6.1 few or all
functionalities for LPG, Sulphur, Crude Oil, Asphalt and Vacuum
Bottoms Loading operation
6.2.3 The weigh scale building shall house an interface for drivers to enter
their driver, tank truck and order numbers for identification.
6.2.4 The TMS shall be configured to allow the operator to display quantities
measured in units of volume and mass.
6.2.6 The TMS design shall include preset controller or DID at the bay to
identify and allow only pre-weighted and authorized trucks to load.
6.3.1 The TMS shall be configure to control the product transfer through
Rail Car movement operations.
6.3.2 If required, the TMS shall configured to meet Section 6.1 and Section
6.2 few or all functionalities for Rail car Loading/unloading operation.
6.3.3 The TMS shall be configure to monitor and control all process and
interlocks of Rail Car movement operations.
6.4.1 The TMS shall be configured to monitor and control the product
receipt operation.
6.4.2 The TMS shall be configured to monitor product tank parameters and
take corrective actions if required to ensure safe operation.
6.4.3 The TMS shall be configured to automate tank allocation (per product
allocation table and current state) and auto line-up of product to
specified tank without contamination. Refer to Appendix A flow chart.
6.4.5 For each scheduled batch, the TMS shall be configured to allow the
operator to allocate a tank, or number of tanks to receive the batch and
lineup in auto or manual mode.
6.4.6 The TMS shall be configured to allow the operator to carry the
operation in manual, however, system shall provide advisory alert to
the operator during manual operation. Following are typical manual
operations to allowed:
The TMS shall be configured to monitor and control the following operation as
a minimum for pipeline product delivery:
Shipper pumps operation
Booster pumps operation.
Associated custody transfer metering and proving.
Control valve station.
Associated instrumentation and MOV's.
Transfer from Automatic Tank Gauging.
Safety interlocks.
Selecting correct channels to detect product contamination using density
meter or online analyzers.
TMS shall have the capability to interface with Supervisory Metering
Systems.
6.7.1 The TMS shall provide a complete inventory management package that
include tracking product receipt, deliveries, transfers, re-branding, and
tank's volume. Product inventory shall be logged on a continuous
basis.
6.7.2 The TMS shall be configured to perform product receipt using data
transmitted from an Automatic Tank Gauging (ATG) system designed
based on SAES-Y-301, to determine the quantity transferred by
calculating the difference in tank level.
6.7.3 The TMS shall monitor the tank conditions and to alert the operation
personnel at the control console in case of any deviation including
level, flow, temperature, density, pressure, unexpected movement or
movement in wrong direction, leak, flow start/stop and stop gauge.
6.7.5 The TMS shall be configured to re-brand products, i.e., the re-
classification of a product that include:
6.7.6 The TMS shall be configured to transfer between tanks and shall
include the following at a minimum:
Transfer of recovered product to product tank.
Transfer of gasoline rich product to product tank.
Transfer of diesel rich product to product tank.
Transfer of one product to another via a meter proving operation.
6.7.7 The TMS shall be configured to allow the operator to select the
destination for re-branding of transferred product.
6.7.9 The TMS shall be configured to allow the operator to select from a list
the allowable re-brand names for both sale and transfer.
6.7.9 TMS shall be configured to use tank High Level and High Level
signals to prevent overfill in the tanks.
6.8.2 The TMS shall be configured with manual data entry screens and
associated data storage for product receipts, transfers, deliveries,
inventory, own use and re-brands functions.
6.8.3 The TMS shall be configured to account for recovered product tank
inventory and calculate the quantity of recovered product transferred to
product storage.
6.8.4 The TMS shall be configured to reconcile inventory errors in the event
of loss of meter data, metering system inaccuracy or the removal of
product from a location where there is no metering.
6.8.5 The TMS shall be configured with a manual data entry screen to allow
losses to be accounted for by authorized personnel under password
access. Entry field shall be provided on the screen for recording the
reason for the loss.
Saudi Aramco: Company General Use
Page 17 of 49
Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 2 May 2019
Next Planned Update: 11 October 2021 Design of Terminal Management Systems
Note that- this operation may not require if the meter proving is carried using
standalone proving system.
6.9.1 The TMS shall be designed to interface with pipeline metering and
meter proving operations at each facility. The TMS shall perform the
following functions:
Retain meter transaction data.
Maintain meter factor database information for all meters.
Maintain information on volume readings during meter
proving and other maintenance activities.
6.9.2 The TMS shall be configured to initiate a pipeline proving operation
based on operator request, or automatically or manually.
6.9.4 The TMS shall be configured to receive and store new meter factors
from the Metering Supervisory Computer (MSC) upon completion of a
proving operation.
6.9.5 The TMS shall be configured to send a command for the MSC to print
a proving report with details for the new meter factors.
Saudi Aramco: Company General Use
©Saudi Aramco 2019. All rights reserved. Page 18 of 49
Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 2 May 2019
Next Planned Update: 11 October 2021 Design of Terminal Management Systems
6.9.6 The TMS shall be configured to accept or reject new meter factors on
the operator graphic based on the deviation from the previous meter
factors outlined in the proving report:
The TMS shall automatically upload accepted meter factors.
The TMS shall utilize existing meter factors when new meter
factors are rejected.
The TMS shall make the rejection of the meter factor based on
a pre-configured range (+/- “a” %) limit.
6.9.7 The TMS shall be configured to keep a read-only record with
timestamps of all meter factors downloaded from the MSC.
6.9.8 The TMS shall be configured to allow an operator to display and print
meter factors and meter history reports.
6.9.9 The TMS shall be configurable to follow a typical procedure for meter
proving such as the illustrated in Appendix F unless specified
otherwise in the project specifications.
7.2.4 The TMS shall be configured following IO types for ON/OFF valve:
Saudi Aramco: Company General Use
Page 19 of 49
Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 2 May 2019
Next Planned Update: 11 October 2021 Design of Terminal Management Systems
a) Digital output:
Open (Momentary)
Close (Momentary)
Stop (Momentary)
b) Digital input:
Opened
Closed
Not-in-Remote/ Power Failure.
c) Read back the actual percentage opening of control valves.
7.2.5 The TMS shall be configured to provide deviation alarms for ON- OFF
/control valves for fault conditions including when:
Time exceeds the configured delay time to change from
Open/Close state.
Travel time exceeds a configurable delay.
A command action did not occur within the specified time.
7.2.6 The TMS shall be configured ZV based on SAES-J-0601 requirement
and the ESD ZV / MOV discrepancy alarm shall be annunciated
separately from a normal operation discrepancy alarm.
7.2.7 ZVs used in an ESD sequence should be go to fail safe mode position
when the electrical (power) supply is disconnected.
7.3.1 The TMS HMI shall be configured to have a graphical symbol per
pump with start, stop, logic reset and auto/manual control
functionality.
7.3.2 The TMS shall be configured to have two discrete inputs and two
discrete outputs for motor/pump control as follows:
Discrete output: Start (Momentary).
Discrete output: Run/ Stop (Maintained).
Discrete input: Running.
7.3.6 The TMS shall be configured to require the discrepancy alarm fault
condition manually cleared and the pump logic reset by operations
prior to restart of a pump.
7.3.13 The TMS shall be capable to configure recycle flow control valves for
loading pumps.
Saudi Aramco: Company General Use
Page 21 of 49
Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 2 May 2019
Next Planned Update: 11 October 2021 Design of Terminal Management Systems
7.3.14 The TMS shall be configured to allow authorized user to override the
ESD interlock manually for a certain time. The TMS should be log all
override / bypasses and shall automatically alarm after set time time
lapse.
7.3.16 The TMS shall be configured to run all pumps when to reduce the
loading/unloading rates or unable to maintain the demand rate.
7.4.1 The TMS shall be configured to display and log the process,
equipment, field instrument, UPS and TMS component failure alarms
in the system.
7.4.2 The TMS shall be configured to display and log equipment, field
instrument, UPS and TMS component current health status.
7.4.3 TMS shall display and log the Server’s CPU and memory usage and
alarm if the usage is more than 50%.
7.4.4 The TMS shall be configured to log and display historical data of
following parameters at a minimum:
Process Pumps: Total running hours
Custody Transfer and Tank Truck Loading/unloading Meters:
Total net volume throughput.
TMS shall provide loading arm, flow, total loaded flow, grounding,
ESD condition, Knock Out Drum (KOD) level switch, vapor return
condition on HMI graphics.
7.4.4 The TMS shall be configured to lock the driver after three successive
wrong access attempts. The lock status alarm shall be generated to
inform to operator. Simultaneously, system shall provide a clear
message to the driver to contact operator to unlock or get more support.
Bay available
Bay locked
Rack fire alarm
Plant Fire alarm
Local Bay ESD
Plant ESD
Loading permissive
Earthing connection
Vapor return flow
KOD level
Truck Tanker level
Ramp up and down rate
Traffic light
Pump Demand.
Excess low Flowrate
High and low Pressure
The TMS shall provide interface to VMS for bulk plants pumps where required
in accordance with Section 15.4 of SAES-Z-001.
The TMS shall provide interface to PLC and Third Party Packages, where
required, in accordance with Section 15.7 of SAES-Z-001.
7.8.2 The interface shall be secured from a TMS control network intrusion
standpoint, and any LIMS to TMS write function shall not have impact
on the integrity of the TMS.
7.9.1 This requirements in this section apply to the interface between the TMS
and either a Power Monitoring System, a Substation Automation system,
and to individual motor control centers. These systems are collectively
referred to as ‘Electrical Substation Equipment’ within this standard.
7.9.2 The TMS shall provide interface to PLC and Third Party Packages,
where required, in accordance with Section 15.8 of SAES-Z-001.
The TMS shall provide interface to DAHS, where required, in accordance with
Section 15.6 of SAES-Z-001.
8.1.1 TMS business server shall host a single business transactional database
and connect to DMZ with the matching plugin.
8.1.3 TMS Business Server transactions data exchange shall not degrade the
performance of the monitoring and control functions in the process
control system.
8.2.2 The TMS shall be configured to provide alarms, alerts and process
event logs as defined SAES-Z-001 Section 12.
8.3.1 The TMS shall be configured to verify a truck driver’s identity via eye
scan or biometric technology (fingerprint scanning), card reader or
barcode reader. If card reader or barcode reader technology used then
additional authentication is required such as PIN or password.
8.3.2 The DVS shall be configured to allow manual data entry through an
integrated keypad. Manual Entry shall be controlled by the TMS.
8.3.3 The DVS shall be configured to communicate with the TMS via
TCP/IP Ethernet.
8.3.4 The DVS shall be installed at entry gate, waiting area, loading bays,
and BOL building.
8.3.5 The TMS shall be configured with standard maximum expiration time
(timeout) for entry.
8.3.6 The TMS shall be configured to use of DID as DVS in case of DVS
fails.
8.4.1 The OIS shall be configured to verify order information via barcode
scanning technology.
8.4.4 The TMS shall be configured to use of DID as OIS in case of OIS fails.
8.5.1 The TIS shall be provided at the entry gate, exit gate and
loading/unloading bays.
Saudi Aramco: Company General Use
Page 25 of 49
Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 2 May 2019
Next Planned Update: 11 October 2021 Design of Terminal Management Systems
8.5.2 The TMS shall be configured to enter a truck number via DID incase
TIS malfunction.
8.5.3 The TIS shall upload the truck information to the TMS System.
8.5.4 The TMS shall authenticate the tanker truck and send a
loading/unloading authorization command to the controller.
8.5.7 Communication between the truck tag and the tag reader shall be
encrypted.
8.5.8 The serial number of tanker tag device shall be programmed into the
device which shall be used for identification.
8.5.9 The TMS shall be configured to record the tanker number to the unique
tanker tag ID. This number is used to auto detect the truck.
8.5.10 The TIS tag reader shall be configured to communicate with the TMS
via TCP/IP or serial communications.
8.5.11 TIS shall have good line of sight and shall not interface with adjacent
bay trucks.
8.6.4 The TMS shall be configured to utilize the Preset Controller for the
entry of transaction data as the loading/unloading interface.
8.6.6 Preset and TMS shall be configured to upload, display and store the
following Preset Controller data on the TMS as a minimum:
Configuration
Alarms and diagnostics messages.
Keypad entry.
Ready, operating, or end of operating data available status.
Automatic or manual mode status.
All I/O status.
All driver and operator actions for a particular loading/unloading
order.
Identification and verification: Driver, Tanker and Order .
Meter Reading (Liters): Opening, Closing, Indicated Volume
Delivered, Gross Volume Delivered, Gross Standard Volume at
15C Delivered.
Average Temperature in C
Density at 15C (kg/m³).
Average Flow Rate (L/min.).
Average Meter Factor.
Total loaded quantity
Pressure
8.7.2 The TMS shall be configured to sequentially poll the devices to obtain
data.
8.7.3 A device driver shall be installed on the TMS Servers to obtain the
entered driver, tank truck and order numbers from the DID. The TMS
server shall be configured to process and verify these numbers against
a predefined database. If the driver information is not in the database,
the driver will be referred to Sales office or Operator, for assistance.
8.7.4 DID shall be configured to be use as DID, DVS and OIS incase
operator intend or auxiliary device fails.
8.8.1 The queue monitoring shall be a minimum 52” size flat LED monitor
with 1920x1080 resolutions at 60 Hz refresh rate.
8.8.2 The queue monitoring shall be mounted on a wall in the truck driver
waiting area with an adjustable bracket.
8.8.4 Allocating Bay and queueing sequence shall be based on the calculated
priority using the order/truck priority and arrival time of the truck.
8.8.6 The TMS queue monitoring system shall display the operation status of
each bay.
8.8.7 Queue monitoring shall be configurable for multiple pages and page
flip time. This is required if the open orders are more than one page.
8.8.8 Queue monitoring shall display all latest orders along with its status.
8.8.9 Queue monitoring shall display all pending orders on the active screen,
pending orders more than two days shall not be displayed.
8.8.10 The TMS should be configurable to follow the driver queue workflow
as shown in Appendix D and Appendix E.
8.9.2 All order data shall be exchanged with TMS and weigh scale similar to
preset controller exchange method.
8.9.3 Order, Driver and Truck authentication shall be followed to ensure the
safety and reliability similar to preset controller loading operation.
8.10.1 The TMS shall be configured for two Bills of Lading (BOL) printers
in redundant mode at Exit Gate.
8.10.2 The TMS design shall include centralized and redundant BOL printers
with auto switchover capability.
8.10.3 A minimum of two BOL/ delivery receipt printers shall be installed per
BOL building.
8.10.4 The BOL printer installed at Exit gate shall be industrial grade printer
and shall be able to withstand in harsh environment. The printer shall
handle minimum 800 print batches per day.
8.10.5 BOL shall communicate with the TMS device for automatic receipt
printout after verification of the transaction information received
through DID.
8.11.1 Terminal servers shall be configured to utilize only the active serial
ports connected to the system.
8.11.3 Single port Terminal Servers in redundant configuration shall use to all
device interface which has redundant connectivity (two ports in
redundant mode) including loading and unloading preset controllers,
Weigh-scale electronics, Custody pipeline metering and proving
control systems, TIS, OVS, DID etc.
8.11.4 Multi-port serial terminal servers are allowed only for simplex
interfaces where equipment is less critical and does not support
redundant communication.
8.11. 6 Auxiliary systems shall not be daisy chained while interfacing with
terminal server.
The TMS shall be configured to interface to the MSC via Modbus or OPC
whatever required.
8.13.1 ATG inventory calculation shall be an integral part of TMS shall meet
the SAES-Y-301 or the TMS shall be configured to interface to the
ATG via Modbus or OPC to exchange real-time data between them,
whatever required. Preferably, OPC set in TMS as OPC server.
8.13.2 The TMS shall automatically monitor the tanks conditions and to alert
the operation personnel at the control console in case of any deviation
in level, flow, temperature, density, and pressure as well as in case of
unexpected movement, wrong direction, leak, and flow start/stop.
Saudi Aramco: Company General Use
©Saudi Aramco 2019. All rights reserved. Page 30 of 49
Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 2 May 2019
Next Planned Update: 11 October 2021 Design of Terminal Management Systems
8.13.3 The TMS shall be configured with manual data entry capability for
tanks without an ATG or in case of ATG malfunction. Minimum tank
information entry parameters are as follows:
Level.
Temperature measurement.
Volume.
Tank contents by type (Product).
Tank leak detection (detection of unexpected level changes).
Actual available capacity.
product density
8.14.1 The TMS shall be configured to interface to the Fire Detection and
Alarm system through hardwired signals to the TMS controllers,
Signals definition shall be included in the project specifications.
The TMS shall configured for time synchronization based on SAES-Z-01. All
TMS subsystems shall configured to synchronize the time with TMS master
clock source and shall not exceed the allowance at any point of time.
TMS equipment shall meet the electrical requirement defined in SAES-J-902 and
environmental requirements defined in Section 5 of 23-SAMSS-010.
10 Operation Centers
Revision Summary
7 July 2015 New Saudi Aramco Engineering Standard.
11 October 2018 Major revision. Editorial and sections rearrangement.
2 May 2019 Editorial revision as part of content confirmation assessment
Summary of Change Form
No. Change Type Technical Change
Paragraph (New,
No. Modification,..)
B C
Driv er disconnects
ground plug
Y es
Y es
No
Driv er to check all TMS prints
bay closed Fix problem hoses are deliv ery receipt
correctly stowed
Operations print
release note or Driv er retriev es
Are the
deliv ery receipt as Operator instructs deliv ery receipt and
traf f ic lights
appropriate driv er to exit returns to his
on green?
tanker
Security checks
Driv er exits
Release note/
unloading bay
deliv ery receipt
No
Y es
H as driv er
Y es got host
order?
No
Y es Order
databas e D riv er ref erred to
D etails v alid? No
table sales staf f
Y es
Operations print
releas e note or
R eady to start loading Problem BOL as
proc edure
Y es
resolv ed?
No B
appropriate
No
Problem
resolv ed?
D riv er parks in
v acant park ing C
space
D riv er connects
A ground plug to
tank truck
D riv er to interc om
Operators Tank truc k
to operations No
alerted OK?
staf f
Y es
D riv er connects
driv er told to Operator resolv es
No loading and
ex it rack? problem
v apour hos es
D E F
Star t
Enter driv er
D riv er enters driv er
num ber
Y es num ber A
again?
Error! D riv er
Is the driv er num ber
No No
num ber v alid? incorrec t or not
v alid
Y es
Enter order
num ber
Error! order
Is the order num ber
No Valid order
num ber v alid? incorrec t or not
v alid
Y es
Y es
No
Error! tank
Is the tank TMS dis play s
truck number TMS alloc ates new
truck number No appointm ent
incorrec t or appointm ent tim e
v alid? tim e
not v alid
Y es
No
Y es Tank
truck
database
table
Operations (Sales
of f ice) rev ise/ m ake Order TMS checks details
order database
table
Driv er
database
table
Operator enters
TMS allocates an
order details in
appointm ent
the TMS
Enable
Change
tank
Start tank truck Start
truck
status
loading
Driv er
presses start
Tank truck
No W aiting button on No W aiting
identif ied?
preset
controller
Y es Y es
No No
Does
identif ied
End of bay Does status = End of bay
tank truck No No
queue? 'AT BAY '? queue?
m atch the
record
Y es Y es
Y es Y es
Alarm . tank
Alarm . tank truck
truck not in bay
not in bay queue
queue
Ad d R emo ve
tank tank truck
Start Start
truck to from
queue queue
N um ber of
tank truck s in
bay (n) traf f ic
the queue les s
No W aiting lights switch No W aiting
than the
to green?
m ax im um .
(z < x)?
Y es
Y es
No No
C an the tank
truck be End of TMS D oes status = End of bay
No No
loaded at bay site queue? 'LOAD IN G'? queue?
(n)?
Y es Y es
R em ov e one tank
Add one tank truck
truck f rom the
to the queue length.
queue length. Set z
Set z = z + 1
=z-1
Y es
Check tank
Tank truck (t)
truck Look at f irst tank End of
Start 'QUEUING' No
'Queu in g' truck in the queue queue?
tim eout?
timeout
Y es
Alarm . Tank
Look at next tank truck
truck 'QUEUING'
tim eout
No
Y es
Check
tank Tank truck (t)
Look at f irst tank End of
truck 'At Start 'AT BAY ' No
truck in the queue queue?
bay' tim eout?
timeout
Y es
Alarm . Tank
Look at next tank
truck 'AT BAY '
truck
tim eout
No
Y es
Check tank
Tank truck (t)
truck Look at f irst tank End of
Start 'LOAD ING' No
'Loadin g' truck in the queue queue?
tim eout?
timeout
Y es
Alarm . Tank
Look at next tank truck
truck 'LOAD ING'
tim eout
No
No
Y es
H as driv er
Y es got host
order?
No
Order
databas e
table D riv er, order
and tanker are No
Y es
v alid?
Y es
No Operations print
D riv er waits until his turn is releas e note or
display ed on the queue BOL as
m onitor appropriate
B C D E
D riv er c onnects
A Y es ground plug to
tank truck
D riv er enters
tank truck
num ber
D riv er to intercom
Operators Tanker
to operations No
alerted OK?
staf f
Y es
Y es
F G H
B C D F
H as the bay
Y es
been clos ed?
No No
Is the bay
em pty ?
Y es
Y es
Operator
Is order c orrec t D riv er to intercom to
decides to load Y es
f or ty pe of bay ? operations staf f
any way ?
No
No
D riv er returns to
tank er
Start
Prov ing
Is prov ing
operation Operator m us t wait W ait till prov ing is
Y es operation No
already in until it is com plete com plete
com plete?
progress?
Y es
Y es
Operator
Initiate C PMPC S prov ing ac cepts new TMS uploads new
Y es
cy cle f rom TMS m eter f ac tor v ia m eter f ac tor data
TMS
Y es
Page 49 of 49