Saes Z 008

Engineering Standard
SAES-Z-008 7 July 2015

Terminal Management Systems
Document Responsibility: Process Control Standards Committee
Saudi Aramco DeskTop Standards

Table of Contents
1 Scope.............................................................. 2
2 Conflicts and Deviations................................. 3
3 References..................................................... 3
4 Definitions....................................................... 4
5 General Requirements.................................. 10
6 TMS Operation............................................. 12
7 TMS Facility Monitoring and Control............. 18
8 TMS Components......................................... 22
9 Environmental Conditions............................. 29
10 Operation Centers........................................ 29
Appendix A - Typical Product Tank Allocation.... 30

Appendix B - Typical Tank Truck Unloading....... 31
Appendix C - Typical Tank Truck Loading
(No Queue)................................... 33
Appendix D - Typical Queue Algorithm............... 36
Appendix E - Typical Tank Truck Loading
(with Queue)................................. 41
Appendix F - Typical Pipeline Meter Proving...... 45
Appendix G - Typical Bulk Plant Automation
Overview....................................... 46
Appendix H - TMS Components by Process....... 47
Previous Issue: New Next Planned Update: 7 July 2018
Primary contact: Zahir, Hussain Ali (zahiha0a) on +966-013-8801838
Copyright©Saudi Aramco 2015. All rights reserved.

Document Responsibility: Process Control Standards Committee SAES-Z-008
Issue Date: 7 July 2015
Next Planned Update: 7 July 2018 Terminal Management Systems
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 typical Saudi Aramco Bulk Plants. Parties involved in the
design and commissioning of TMS systems are required to comply with this
standard.
1.2 Typical Saudi Aramco Bulk Plant Operations:

a) Pipeline Product Receipt
b) Pipeline Product Delivery (Shipping)
c) Pipeline Meter Proving
d) Road (Tank Truck) Loading and Unloading
e) Rail Car Loading
f) Liquefied Petroleum Gas (LPG) Loading
g) Refined products (Diesel, Gasoline, Jet Fuel, and Kerosene),
Sulphur, Crude Oil, Liquid Chemicals, and Asphalt Loading
h) Tank gauge and Inventory Management
i) Product Reconciliation
j) MOV Operation
k) Pump Operation
l) Vapor Recovery
1.3 TMS Components functionalities:

a) TMS Control Application
b) TMS Business Application
c) Driver Verification System (DVS)
d) Order Information System (OIS)
e) Truck Identification System (TIS)
f) Preset Controller
g) Driver Interface Device (DID)
h) Queue Monitoring System (QMS)
i) Weighscale Electronics
j) Bill of Lading (BoL)
Page 2 of 47
k) Terminal Servers (TS)

l) Custody Pipeline Metering and Proving Control Systems (MSC)
m) Automatic Tank Gauging (ATG)
n) ESD system
o) VMS (RMPS)
Appendix H provides a matrix for TMS components by process.

Note: Some of the listed TMS components are not within the scope of this standard.
1.4 This entire standard may be attached to and made a part of purchase orders.
2 Conflicts and Deviations
2.1 Any conflicts between this standard and other applicable Saudi Aramco
Engineering Standards (SAESs), related Materials System Specifications
(SAMSSs), Standard Drawings (SASDs), or other mandatory Saudi Aramco
Engineering Requirements (MSAER) shall be resolved in writing by the
Company or Buyer Representative through the Manager, Process & Control
Systems Department of Saudi Aramco, Dhahran.
2.2 Direct all requests to deviate from this standard in writing to the Company or
Buyer Representative, who shall follow internal company procedure SAEP-302
and forward such requests to the Manager, Process & Control Systems
Department of Saudi Aramco, Dhahran.
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.
3.1 Saudi Aramco References
Saudi Aramco Engineering Procedures

SAEP-99 Process Automation Networks and Systems Security
SAEP-302 Instructions for Obtaining a Waiver of a Mandatory
Saudi Aramco Engineering Requirement
SAEP-368 Alarm System Management
Page 3 of 47
Saudi Aramco Engineering Standards

SAES-B-014 Safety Requirements for Plant and Operations
Support Buildings
SAES-B-070 Fire and Safety Requirements for Bulk Plants, Air
Fueling Terminals and Sulfur Handling Facilities
SAES-J-601 Emergency Shutdown and Isolation Systems
SAES-J-902 Electrical Wiring for Instrumentation
SAES-T-566 Plant Demilitarized Zone (DMZ) Architecture
SAES-Y-103 Royalty/Custody Metering of Hydrocarbon Liquids
SAES-Y-301 Royalty Custody Measurement of Hydrocarbon
Liquids using Radar Tank Gauging Systems
SAES-Z-001 Process Control Systems
SAES-Z-010 Process Automation Networks
Saudi Aramco Materials System Specifications

23-SAMSS-010 Distributed Control Systems
23-SAMSS-050 Terminal Management Systems
34-SAMSS-180 Truck Weigh Scale System
34-SAMSS-318 Automatic Tank Gauging Equipment
34-SAMSS-847 Preset Controller for Truck Loading and Unloading
Systems
Saudi Aramco Best Practice

SABP-Z-021 Terminal Management System – SAP Interface
Specifications
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
Page 4 of 47
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
OIS Order Information System
PIN Plant information Network
PLC Programmable Logic Controller
SAEP Saudi Aramco Engineering Procedures
SAES Saudi Aramco Engineering Standards
SAMSS Saudi Aramco Material System Specifications
SAP Systems, Applications and Products.
SQL Structured Query Language
TCP/IP Transmission Control Protocol/Internet Protocol
TIS Truck Identification System
TMS Terminal Management System
UPS Uninterruptible Power Supply
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.
Page 5 of 47
Algorithm: A prescribed set of well-defined rules or processes for the solution

of a problem in a finite number of steps. (See also control algorithm).
Auxiliary System: A control and/or monitoring system that is stand-alone,

performs a specialized task, and communicates with the TMS.
Availability: The amount of time a device is actually working as a percentage

of total time it should be operating.
Batch Management System: A TMS Batch Management System provides

automatic product receipt operation which allows, among others:
 Semi-automatic routing of product from pipeline to tank.
 Valve sequencing on tanks and manifolds dependent on product routing to
prevent cross product contamination.
 Diversion of the flow based on the product density value received from the
densitometers or product zero count-down volume.
 Customizable to meet user requirements.
 Supports MES.
 Provides Safety Protection.
 Connects to commercial systems such as ERP.
Batch Manager: A batch Manager is usually the Shift Supervisor or Shift

Coordinator.
Bulk Plant: A terminal or depot that receives, stores, and dispenses refined
hydrocarbon product via tank trucks, pipeline or marine vessels. Typical Bulk
Plant loads multiple products such as gasoline, diesel, jet fuel, via multiple
loading bays.
Cabinet: A general term describing any enclosure which contains process

control equipment. The requirements for cabinets vary depending on the type of
equipment enclosed in the cabinet.
Control Algorithm: A mathematical representation of the control action to be

performed.
Controller: A microprocessor-based device used primarily to perform

regulatory control functions.
Control Room Rack: A framework, constructed of rails or steel members, for

mounting an assembly of electronic modules or components of the TMS.
Page 6 of 47
Custom Application Software: The software written specifically to perform

functional requirements for an individual plant when standard software packages
cannot be configured to meet the requirements. Custom Application Software
works with the standard operating software; it does not modify any standard
software.
Distributed Control System (DCS): A process control system that is composed

of distinct modules. These modules may be physically and functionally
distributed over the plant area. The distributed control system contains all the
modules and associated software required to accomplish the regulatory control
and monitoring of a process plant, excluding field instruments, remote terminal
units, auxiliary control systems and Plant information systems.
Emergency Shutdown System (ESD): A system composed of sensors, logic

solvers, and final control elements for the purpose of taking the process, or
specific equipment in the process to a safe state when predetermined conditions
are violated. The system is designed to isolate, de-energize, shutdown or
depressure equipment in a process unit. Another term commonly used
throughout the hydrocarbon and petrochemical industry is a Safety Instrumented
System (SIS)
Estimated Time of Arrival (ETA): The Estimated Time of Arrival when the
product switch occurs on multiproduct pipeline.
Hardware: Physical components used within a Terminal Management System

such as: Controllers, I/O cards, power supplies, network devices, workstations
and servers.
Loading Rack: A framework, constructed of pipes, instruments, mechanical

components, and support structure for the loading bays.
Logs: Files or printouts of information in chronological order.
Mode: Control block operational condition, such as manual, automatic, or cascade.
Module: An assembly of interconnected components that constitutes an

identifiable device, instrument, or piece of equipment. A module can be
disconnected, removed as a unit, and replaced with a spare. It has definable
performance characteristics that permit it to be tested as a unit.
Operational Data: The statistical data such as alarm limits, tuning parameters,
and clamping values, as opposed to process data such as input values, output
values, and set-points.
Operator Console: A console used by an operator to perform the functions
Page 7 of 47
required to monitor and control his assigned units.
Operating System: Software that runs on a computer for the purpose of

managing computer hardware and providing common services for the execution
of application software.
Pipeline Receiving Station: The station where hydrocarbon products are

received via pipeline for distribution at the bulk plant and/or for further shipping
to other bulk plants via pipelines.
Preset Controller: An electronic metering device used in an industrial

environment to provide totaling volumes, correcting volumes to reference
conditions, and controlling the loading operation at the rack (batch loading).
Process Controller: A digitally operating electronic system designed for use in

an industrial environment, which is used to control and automate a sequence of
operation. The Process Controller could be Programmable Logic Controller
(PLC) subsystem or conventional controller provided by Distributed Control
System (DCS).
Process Control System: The integrated system which is used to automate,

monitor and/or control an operating facility (e.g., plant process units). The TMS
consists of operating area Distributed Control Systems and their related auxiliary
systems which are connected together at the Process Control Network and
Process Automation Network level to form a single integrated system.
Programmable Logic Controller: A digitally operating electronic system,

designed for use in an industrial environment, which uses a programmable
memory for the internal storage of user-oriented instructions for implementing
specific functions such as logic, sequencing, timing, counting and arithmetic, to
control, through digital or analog inputs and outputs, various types of machines
or processes.
Rebrand: The reclassification of a product that includes transfer between

product tanks, the sale of one product as another, and transfer of product
classification on a standing tank.
Recovered Product: The amount of products that are recovered as a result of

tank reconciliation calculation.
Redundant Configuration: A configuration that provides automatic

switchover, in the event of a failure, without loss of a system function.
Regulatory Control: The functions of regulating certain process measurement

via manipulation of final element. The regulatory control includes fetching
Page 8 of 47
process measurement, control algorithm execution, and final control device

manipulation.
Reliability: The probability that a system will provide correct outputs up till
some given time.
Semi-Automatic: Semi-Automatic control is the use of automation and control

systems for operating processes and equipment in bulk plants with partial human
intervention.
Software: Software shall be considered programming code, computer

instructions or data that can be stored electronically. The storage devices and
display devices are hardware. Software is often divided into two categories:
 Systems Software: Includes the operating system and all the utilities that
enable the computer to function.
 Applications Software: Includes programs that do real work for users.
For example, word processors, spreadsheets, and database management
systems fall under the category of applications software.
 System Access Restriction: Means of controlling and regulating access to
computing resources and information such as by.
 System Alarm: The collection of hardware and software that detects an
alarm state, communicates the indication of that state to the operator, and
records changes in the alarm state.
Tag: A collection of attributes that specify either a control loop or a process

variable, or a measured input, or a calculated value, or some combination of
these, and all associated control and output algorithms. Each tag is unique.
Tag ID: The unique alphanumeric code assigned to inputs, outputs, equipment
items, and control blocks. The tag ID might include the plant area identifier.
Tank Reconciliation: Tank Reconciliation tracks all the fuel that enters or exits
in each tanks, regardless of delivery or dispensing activity. Then, automatically
collects metered sales information from electronic and mechanical dispensers and
gives you accurate delivery and reconciliation reports on a shift-by-shift basis.
Terminal Management System: A process automation system comprised of a

Distributed Control System, an Emergency Shutdown System, a Terminal
Management System Business Server and related subsystems which are utilized
to control the loading, unloading, delivery and receipts of petroleum products as
well as to manage the executing product delivery orders to customers that
initiated from Saudi Aramco Enterprise Resource Planning System such as SAP.
Page 9 of 47
TMS Control Application: Application which monitors and controls bulk plant
terminal operation using DCS and ESD.
TMS Business Application: Application which handles and process business

data such as Driver, Truck, and Order data.
Transaction: An input message to a computer system that must be dealt with as

a single unit of work. A transaction typically includes data such as date, time,
quantity, source and destination of an order request or action taken.
Workstation: Is a computer dedicated to a user or group of user engaged in

business or professional work. It includes one or more high resolution displays,
processor, keyboard (s), storage (s) peripheral (s) and associated pointing device (s).
5 General Requirements
5.1 The TMS shall meet all requirements defined in SAES-Z-001 Process Control
Systems.
5.2 Emergency Shutdown Systems provided as part of an integrated TMS, shall meet
all requirements defined in SAES-J-601, Emergency Shutdown and Isolation
Systems.
5.3 TMS shall support the alarm rationalization process for all configured alarms as
per SAEP-368 and Section 12 of SAES-Z-001, to assign the priorities in order to
ensure that the plant operator is not flooded with irrelevant alarms, etc.
5.4 DCS and ESD components of the TMS shall be installed indoors.
5.5 The TMS shall be configured to monitor safety interlocks.
5.6 The TMS shall be capable of interfacing with sampling systems.
5.7 The TMS shall be configured to initiate shutdown through ESD in the event of
an emergency.
5.8 The TMS shall be configured to upload transactions to the SAP/host computer.
5.9 System shall be designed using redundant architecture to meet the fault tolerant
functionality.
5.10 The TMS shall be designed to be a tightly integrated components, subsystems,

and field control devices.
5.11 TMS software packages shall be vendor's standard Commercial Off-The-Shelf

(COTS) offering.
Page 10 of 47
5.12 TMS software packages shall be configurable to meet job-specific requirements.

Modification of source code to meet specification requirements is not allowed.
5.13 The TMS System shall be designed to achieve 3 second maximum response time
for any transaction. For example, verification of data entered into Preset
Controller such as Driver Name, Order and Truck numbers as well as applicable
alarms and error messages shall be verified by TMS and displayed back on
Preset Controller console within this time frame.
5.14 The TMS shall be configured to permit the completion of a single

loading/unloading operation at more than one bay, if needed, in case
loading/unloading operation was not possible to be completed at the assigned bay.
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.17 The TMS shall be configured to automatically upload/download flow meter

factors using restricted access level.
5.18 The TMS shall be configured to monitor and control the Oily Water collection
and treatment equipment.
5.19 The TMS shall be configured to perform automatic and/or manual order matching.
Operator shall be promoted to acknowledge the manual order matching.
5.20 The TMS shall be configured to record the tanker arrival time stamp and truck
number.
5.21 TMS should be governed by a Domain Controller that is provided as part of the
system preferably in redundant configuration. Domain Controller shall be used to
control device connectivity on the Plant Network and User Account
Management.
5.22 TMS shall be hardened in accordance with SAEP-99 and the latest vendor
recommendations.
5.23 TMS shall be configured to accept manually entered order details from
authorized site personnel.
5.24 TMS shall be configurable to meet Vapor Recovery Unit (VRU) requirement or
TMS shall have to interface with VRU system for monitoring capability.
5.25 The TMS shall be configured to have the capability, at supervisor access level, to
Page 11 of 47
manually perform validation of driver, tank truck and order details.
5.26 ll events and logs shall be viewed and recorded in a single database where
tracking and reporting can be done using unique field such as order number or
equipment number.
6 TMS Operation
6.1 Pipeline Product Receipt
6.1.1 The TMS shall be configured to monitor and control product receipt.
6.1.2 The TMS shall be configured to automate tank allocation (as per
product being received). Refer to Appendix A flow chart.
6.1.3 The TMS shall be configured to monitor product tank.
6.1.4 The TMS shall be configured for semiautomatic routing of product

from Pipeline Receiving Station to the Tank Farm such that the TMS
will allow manual routing where applicable.
6.1.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.
6.1.6 The TMS shall be configured to allow the operator to line up valves
from the Pipeline Receiving Station to the tank based on the tank
allocation table.
6.1.7 The TMS shall be configured to allow the operator to switch valves
proactively based on the process measurements.
6.1.8 The TMS shall be configured to allow the operator to prevent the
dead-heading of a line during valve switching.
6.1.9 The TMS shall be configured to allow the operator to prevent cross
product contamination using interlocking valves.
6.1.10 The TMS shall be configured to allow the operator to manually operate
pipeline product receipt.
6.2 Batch Management System
6.2.1 The Batch Management System shall be designed to provide Manifold

MOV routing and switching.
6.2.2 The Batch Management System shall be designed to provide Tank
Page 12 of 47
MOV switching.
6.2.3 The Batch Management System shall be designed to provide

interlocking of MOV valves dependent on product routing to prevent
cross product contamination.
6.2.4 The Batch Management System shall be designed to provide manual

entry screens to allow allocation of tanks to products.
6.2.5 The Batch Management System shall be designed to provide switching

of product to allocated tanks.
6.2.6 The Batch Management System shall be designed to provide alarms/

messages for all events and incidents such as tanks not allocated and
batch under allocation.
6.2.7 The Batch Management System shall be designed to provide alarms

related to unclosed valves, unselected tanks, loading, and shipping.
6.2.8 The TMS should be configured to follow the typical operation

workflow shown in Appendix A for a typical Product Tank Allocation
Check, unless specified otherwise in the project specifications.
6.3 Pipeline Product Delivery (Shipping)
If specified in the project specification, the TMS shall be configured to monitor

and control the following equipment as a minimum:
 Shipper pumps (in service and on standby).
 Booster pumps (in service and on standby).
 Associated custody transfer metering and proving.
 Control valve station.
 Associated instrumentation and MOV's.
 Transfer from Automatic Tank Gauging.
 Safety interlocks.
 Pump operation.
 Product contamination equipment such as density meter or online analyzers.
 TMS shall have the capability to interface with Supervisory Metering Systems.
6.4 Tank Truck Loading / Unloading
6.4.1 The TMS shall be configured to view tank truck loading/unloading

operation with the following minimum functionality:
Page 13 of 47
 Automatic, semi-automatic, and manual identification and

verification of Driver, Tank Truck, and Order.
 Process control and monitoring.
 Transaction data processing.
 Transaction ticket printing.
 Preset controller monitoring.
 Proving operation.
 Data transfer to/from host computer system of orders.
 Display of status of all elements on the TMS HMI.
 Safety interlock monitoring.
 Ability to shutdown in the event of an emergency.
 Automatically update business system, BOL, and tank information
based on DCS tank status.
 Depiction of the status of all metering elements on the TMS HMI.
 The TMS shall be configured to verify the Driver, Tank Truck and
Order numbers at each loading/unloading bay.
 The TMS shall be configured to monitor the loading/unloading
totalized flow and shall graphically display in real-time the volume
transferred.
 The TMS shall be configured to manually override checking for driver,
tank truck and order by operations personnel with privileged access.
6.4.2 The TMS shall have a provision to allow operator to enter comments
when they manually update transactions/order details.
6.4.3 TMS should be configured to follow the typical operation workflow for
tank truck unloading as shown in Appendix B.
6.4.4 TMS should be configured to follow the typical operation workflow for
tank truck loading as shown in Appendix C.
6.4.5 The TMS shall be configured to prevent the simultaneous

loading/unloading of a product from a single tank.
6.4.6 The TMS shall be configured to download/upload meter factors and

density in automatic or semi-automatic.
Page 14 of 47
6.5 Inventory Management
6.5.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.5.2 The TMS shall be configured to perform product receipt using data
transmitted from an Automatic Tank Gauging (ATG) system to
determine the quantity transferred by calculating the difference in tank
level.
6.5.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.5.4 The TMS shall be configured to automatically print tank reconciliation

report when Tank status is changed in DCS (TMS Control Server).
6.5.5 The TMS shall be configured to re-brand products,

i.e., the re-classification of a product that include:
 Transfer between product tanks.
 Transfer of product classification on a standing tank.
6.5.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.5.7 The TMS shall be configured to allow the operator to select the
destination for re-branding of transferred product.
6.5.8 The TMS shall be configured to automatically reconcile inventory

changes from Re-branding operations.
6.5.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.6 LPG, Sulphur, Crude Oil, Asphalt and Vacuum Bottoms Loading
6.6.1 The TMS shall measure the weight of loaded Sulphur, Crude Oil,
Page 15 of 47
Asphalt and Vacuum Bottoms Loading based on weighing the truck by

difference when it enters and leaves the facility.
6.6.2 The TMS shall be able to interface to other applicable type of

measurements, (e.g., Coriolis Mass Flow Meters / Mass Flow
Controllers, for Liquids and Gases).
6.6.3 The weighscale building shall house an interface for drivers to enter
their driver, tank truck and order numbers for identification.
6.6.4 The TMS shall be configured to allow the operator to display quantities
measured in units of volume and mass.
6.6.5 The TMS shall communicate to weighscale electronics via redundant

Modbus or OPC protocols.
6.6.6 The TMS design shall include preset controller or DID at the bay that
would allow only pre-weighted trucks.
6.7 Rail Car Loading
The TMS shall be configurable to control the product delivery through Rail Car
Loading operations. This shall include such functions as:
 Product loading and meter monitoring.
 Uploading of meter data to the host computer.
6.8 Product Reconciliation
6.8.1 The TMS shall be configured to calculate and auto-print product

inventory balance using information from product receipts, transfers,
deliveries, inventory, plant diesel and gasoline usage and re-brands.
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
Page 16 of 47
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.
6.8.6 The TMS shall be configured with the following inventory

reconciliation functionality:
 Graphic presentation of equipment and related variables.
 Entry for adjusting individual transfer quantities.
 Highlighted losses/gains.
 Interactive report configuration to store or modify reporting
parameters.
 Routing reports to other users and printers as needed.
 Error-log summary for all the errors encountered.
 View of the balances, together with raw measurements, and
reconciled data.
 Any operator changes for inventory reconciliation shall be logged
and documented by an audit trail.
6.9 Pipeline Meter Proving
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 based on a configurable
metered quantity.
6.9.3 The TMS shall be configured to continuously receive the metering

system and prover status and process variables.
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.
Page 17 of 47
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.
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 TMS Facility Monitoring and Control
7.1 Engineering Units
The TMS shall be configurable to use the applicable measurement system as

provided in Section 5.1 of SAES-Y-103.
7.2 Valve Operation
7.2.1 The TMS shall be programmable to configure all PID controllers for
control valves including MOV's, ZV, PCV's, and FCV's.
7.2.2 The TMS shall be configured for the operator to have a valve graphical
symbol per valve with open, close and stop push buttons as follows:
a) Digital output:
o Open (Momentary)
o Close (Momentary)
o Stop (Momentary)
Page 18 of 47
b) Digital input:
o Opened
o Closed
o Not-in-Remote/ Power Failure.
7.2.3 The TMS shall be configured to allow operator to operate valve in

manual from operator workstation as well as field whenever required.
Pumps shall be interlocked with suction and discharge ZV’s (isolation
valves) such that pumps shall stop automatically if the valve in closed
position.
7.2.4 In addition, pumps shall be configured with manual override of this

interlock, by authorized role on the system. If an override is to be
bypassed then it should be logged automatically in the Alarm
Management System.
7.2.5 The TMS shall be configured to provide alarms for MOV fault
conditions including when:
 Time to change from Open/Close exceeds a configurable delay.
 Travel time exceeds a configurable delay.
 A command action did not occur within the above travel time.
7.2.6 The TMS shall be configured to annunciate the ESD MOV discrepancy
alarm separately from a normal operation discrepancy alarm.
7.2.7 MOVs used in an ESD sequence should be of a type that will fail to a
predetermined position when the electrical supply is disconnected.
7.3 Pump Configuration
The following are required as minimum:
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.
 Discrete input: Remote/ Local.
Page 19 of 47
7.3.3 The TMS shall be configured to allow TMS local operation of a pump
through a remote/local field switch terminated in the system.
 The TMS shall control the pump when the field switch in remote
(energized state).
7.3.4 The TMS shall be configured to allow the operation of a pump in

manual through a software selector switch.
7.3.5 The TMS shall be configured to generate an alarm if the following fault
conditions occur when the pump is switched to remote:
 A Pump is requested to start and the running signal is not energized
within 5 seconds.
 A Pump is requested to stop and the running signal is not
de-energized within a 5 seconds.
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.7 Discrepancy alarms shall be configured in the TMS and shall be

automatically disabled in the event of an ESD pump shutdown.
7.3.8 The TMS shall be configured to provide ESD discrepancy checking in

the event of an ESD shutdown of a pump. This discrepancy alarm shall
be annunciated separately from a normal operation discrepancy alarm
within 2 seconds of an ESD shutdown of a pump.
7.3.9 The TMS shall be configured to automatically start/stop product

loading/unloading pumps based on product demand and pump capacity
data tables.
7.3.10 The TMS controller shall be configured to start a pump when the
instantaneous demand is greater than the sum of the capacity of all
running pumps.
7.3.11 The controller shall be configured to reduce the loading/unloading rates

when all pumps are running and are unable to maintain the demand rate.
7.3.12 The controller shall be configured to automatically start a parallel pump

in the event of a pump fails to start.
7.3.13 The TMS controller shall be configured to stop a pump when no

demand or no flow.
Page 20 of 47
7.3.14 The TMS shall be capable to configure recycle flow control valves for
loading pumps.
7.3.15 The TMS shall be configured to allow an MOV to be controlled from

the field and TMS through a remote/local field switch.
 The TMS shall be configured to control a MOV when the field
switch is in remote (energized state).
7.4 Equipment Monitoring
The TMS shall be configured to retain and display historical data for the
following parameters at a minimum:
 Process Pumps: Total running hours
 Custody Transfer and Tank Truck Loading/unloading Meters: Total net
volume throughput.
 The TMS controller shall generate an alarm for UPS fault condition.
 The TMS controller shall generate an alarm for low fire water tank level.
7.5 TMS to Vibration Monitoring System (VMS) interface
The TMS shall provide interface to VMS for bulk plants pumps where required
in accordance with Section 15.4 of SAES-Z-001.
7.6 Interface to Long-term Data Acquisition and Historization System (DAHS)
The TMS shall provide interface to DAHS, where required, in accordance with
Section 15.6 of SAES-Z-001.
7.7 TMS to PLC and 3rd Party Packages Interface
The TMS shall provide interface to PLC and Thrid Party Packages, where
required, in accordance with Section 15.7 of SAES-Z-001.
7.8 TMS to Laboratory Information Management System (LIMS) interface
7.8.1 The TMS shall provide interface to Laboratory Information

Management System (LIMS) via OPC or Modbus communication.
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.
Page 21 of 47
7.9 Interface to Electrical Substation Equipment
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.
7.10 TMS to SAP interface specifications
7.10.1 The TMS shall be configured to process transactions initiated locally

and shall be processed in the same manner as transaction received from
Saudi Aramco SAP system.
7.10.2 The TMS-SAP interface shall be configured based on TMS-SAP

Interface specification “SABP-Z-012”.
8 TMS Components
8.1 TMS Business Server
8.1.1 TMS business server shall host a single database in either SQL or
Oracle and connect to SAP with the matching SQL or Oracle plugin.
8.1.2 The TMS Business Servers (Database Server) shall be designed to be

redundant with no data loss when one server failed. The failover to
standby server shall not require any user intervention. Alarming shall be
displayed when there is an automatic change over from main to standby.
Database on backup server shall be automatically synchronized with
active server on real time without manual intervention.
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 TMS Control Server
8.2.1 The TMS shall be configured to provide alarms, alerts and process
event logs as defined SAES-Z-001 Section 12.
8.2.2 TMS shall alarm operator and provide a message to the driver to
contact operator after three failed attempts.
Page 22 of 47
8.3 Driver Verification System (DVS)
8.3.1 The TMS shall be configured to verify a truck driver’s identity via eye
scan or biometric DVS technology for fingerprint scanning, card reader
or barcode reader.
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 DVS can use barcode and card reader technology to identify the driver
only when truck’s entry is registered. For bar/card reader PIN is an
additional authentication along with truck identification.
8.3.7 The DVS shall be configured to display meaningful messages to driver

to take correct actions.
8.4 Order Information System (OIS)
8.4.1 The OIS shall be configured to verify order information via barcode
scanning technology.
8.4.2 The OIS can be integrated with the DVS.
8.4.3 The OIS shall be configured to allow manual data through an integrated
keypad. Manual entry shall be controlled by the TMS.
8.5 Truck Identification System (TIS)
8.5.1 The TIS shall be provided at the loading/unloading bays.
8.5.2 The TIS tag reader shall be configured to communicate with the TMS
via TCP/IP or serial communications.
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.
Page 23 of 47
8.5.5 Tanker tag and reader shall be configurable to communicate via

wireless technology.
8.5.6 TIS shall be configured to deactivate tanker tag device which is

installed on truck if it is tampered or mishandled.
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 download the tanker number to the
tanker tag.
8.5.10 The TMS shall be configured to enter a truck number via DID or TIS.
8.6 Preset Controller
8.6.1 TMS shall be configured to monitor and control loading/unloading

operations and provide data storage utilizing data from the preset
controller.
8.6.2 The TMS shall be configured to exchange preset controller information

such as driver number, tank truck number, order number,
loading/unloading parameters and process parameter from the Preset
Controller, at each loading/unloading bay. This data shall be used for
driver, tank truck and order verification. Driver messages shall be
displayed on the Preset Controller in meaningful way.
8.6.3 In case of communication failure between TMS and Preset Controller,

the Preset will continue loading/unloading at the bay until the batch is
completed and TMS shall not allow the loading/unloading of a new
batch from the same bay in auto mode. The bay can allow
loading/unloading batches in manual if Operator selects a bay in
Manual. The TMS shall be configured to upload manually completed
orders when communication is re-established. All events shall be
logged and alarmed as required.
8.6.4 The TMS shall be configured to upload and download the configuration
details of the Preset Controller including density of product and meter
factor of flowmeters.
8.6.5 The TMS shall verify data entered by the driver prior to permitting the
loading/unloading process.
Page 24 of 47
8.6.6 The TMS shall be configured to utilize the Preset Controller for the
entry of transaction data as the loading/unloading interface.
8.6.7 Multiple Preset |Controllers installed (for different products) in a single

loading bay shall have the ability to work with one TIS.
8.6.8 TMS shall be configured to monitor and store the following

information from the Preset Controller at a minimum:
 Configuration and diagnostics.
 Keypad entry.
 Ready, operating, or end of operating data available status.
 Fault status.
 Automatic or manual mode status.
 All I/O status.
 All driver and operator actions for a particular loading/unloading
order.
 System configuration/ diagnostics data.
 Driver Identification.
 Tanker Identification.
 Order/Transaction Number.
 Opening Meter Reading (Liters).
 Closing Meter Reading (Liters).
 Indicated Volume Delivered (Liters).
 Gross Volume Delivered (Liters).
 Gross Standard Volume at 15C Delivered (Liters).
 Average Temperature (0C).
 Density at 15C (kg/m³).
 Average Flow Rate (L/min.).
 Average Meter Factor.
 Manual entry for batch quantity.
8.6.9 The TMS shall be configured to upload/download and display the

following information on the Preset Controller at a minimum:
 Configuration to preset controller.
 Display text message on preset controller display.
 Driver/operator prompts.
Page 25 of 47
 Driver/order/transaction data.
 Total Gross Standard Volume at 15C Delivered.
 Next channel load size to loading Preset Controller or next unload
size to unloading Preset Controller.
 Product Density and Meter Factor.
8.7 Driver Interface Device (DID)
8.7.1 DID shall be configured to communicate to the TMS via point-to-point

serial protocols or via networked interface using TCP/IP.
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.8 Queue Monitoring
8.8.1 The queue monitoring shall be a minimum 42” size flat LCD/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.3 Queue monitoring shall display all pending orders on the active screen,
pending orders more than two days shall not be displayed.
8.8.4 The TMS shall be configured to permit truck, order and driver
information verification after the truck has passed inspection.
8.8.5 The TMS shall be configured to display loading/unloading queue

monitoring in the truck driver waiting area.
8.8.6 The TMS queue monitoring system shall display the operation status
and location.
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 current
status.
Page 26 of 47
8.8.9 The TMS should be configurable to follow the driver queue workflow
as shown in Appendix D and Appendix E.
8.9 Weighscale Interface
8.9.1 The TMS shall be configured to interface with weighscale electronics

via Modbus communications, wherever required.
8.9.2 All order data shall be exchanged with TMS similar to preset controller.
8.9.3 Authentication shall be followed to ensure the safety and reliability

similar to preset controller loading operation.
8.10 Bill of Lading
8.10.1 The TMS shall be configured to print Bills of Lading (BOL).
8.10.2 The TMS design shall include centralized and redundant BOL printers.
8.10.3 A minimum of two BOL/ delivery receipt printers shall be installed per
BOL building.
8.10.4 BOL shall be industrial grade printer and shall be able to withstand in
harsh environment and 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.10.6 If required by Company, E-BOL technology requirements shall be

implemented. E-BOL is an electronic bill of lading which is sent through
electronically to user either email or SMS format. In case of drive
through BOL cabinets, these shall be of the vendor specific design.
8.11 Terminal Servers
8.11.1 Terminal servers shall be configured to utilize only the active serial
ports connected to the system.
8.11.2 Terminal Servers shall be able to automatically reconnect after

communication timeout is reestablished.
8.11.3 Multi-port serial interface servers shall be provided to interface

between the LAN and the following field devices:
 Loading and unloading preset controllers.
Page 27 of 47
 Weigh-scale electronics.
 Custody pipeline metering and proving control systems.
 Truck identification systems.
 Driver interface devices.
 Other serial communication devices which provide data to TMS.
8.11.4 TMS shall be supplied with redundant multi-port serial interface

terminal servers.
8.11.5 Each field device shall have its own serial communication link to the
TMS via a dedicated terminal server port for field side.
8.11.6 Terminal servers shall be mounted in a cabinet preferably in the

network cabinet.
8.11.7 Auxiliary systems shall not be daisy chained while interfacing with
terminal server.
8.11.8 Terminal Servers shall have a single port connection to Preset Controllers.
8.12 Custody Pipeline Metering and Proving Control Systems (MSC)
The TMS shall be configured to interface to the MSC via Modbus or OPC
whatever required.
8.13 Automatic Tank Gauging (ATG) Inventory System
8.13.1 ATG inventory calculation shall be an integral part of TMS or the TMS
shall be configured to interface to the ATG via Modbus or OPC to
exchange realtime data between them, whatever required.
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.
8.13.3 The TMS shall be configured with manual data entry capability for
tanks without a ATG or in case of ATG malfunction. Minimum tank
information entry parameters are as follows:
 Level.
 Temperature measurement.
 Volume.
 Tank contents by type (Product).
Page 28 of 47
 Tank leak detection (detection of unexpected level changes).

 Actual available capacity.
 product density
8.14 Fire Detection and Alarm System
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.
8.14.2 TMS shall be interfaced to the FACP via Modbus or TCP/IP

communications. All alarms and other status information available in
the FACP shall be configured and displayed in the TMS.
8.15 Firewater System
The TMS shall be configured to monitor the Firewater system through hardwired
signals to the TMS controllers. The minimum signals are as follows:
 Tank level.
 Water suction and discharge pressures.
 Pump Flow.
 Running and fault status indication of the firewater pumps.
 Firewater diesel engine.
 Jockey pump.
9 Environmental Conditions
TMS equipment shall meet the environmental requirements defined in Section 5 of

23-SAMSS-010.
10 Operation Centers
Bulk Plant operation centers design shall be per SAES-B-014.
Revision Summary
7 July 2015 New Saudi Aramco Engineering Standard.
Page 29 of 47
Appendix A - Typical Product Tank Allocation
Figure 1 - Product Tank Allocation
Page 30 of 47
Appendix B - Typical Tank Truck Unloading
Figure 2 - Tank Truck Unloading Procedure
Page 31 of 47
B C
Driver disconnects and

stows unloading hose
Driver disconnects
ground plug
Can the driver Can problem

Operators Driver walks to printer
A Yes unload at a No be fixed
alerted building
different bay? immediately?
Yes
Driver enters driver

Timeout?
No number
Yes
Driver instructed to Transaction

leave site No complete
No
Driver to check all TMS prints
bay closed Fix problem hoses are delivery receipt
correctly stowed
Operations print
release note or Driver retrieves
Are the
delivery receipt as Operator instructs delivery receipt and
traffic lights
appropriate driver to exit returns to his
on green?
tanker
Security checks
Driver exits
Release note/
unloading bay
delivery receipt
Driver exits site
Figure 3 - Tank Truck Unloading Procedure
Page 32 of 47
Appendix C - Typical Tank Truck Loading (No Queue)
Tank truck arrives at Driver denied access

security gate to site
No
Driver's ID card Driver

examined by security admitted to
personnel site?
Yes
Has driver
Yes got host
order?
No
Driver parks in vacant

parking space
Driver drives to Driver walks to

appropriate rack operations room
Driver enters driver, Operator makes

Tank order and tank truck appointment/ order if
truck Yes
numbers available
database
table
TMS checks driver,

Driver Appointment/
order tank truck and No
database order given?
arrival time are valid
table
Yes Order
database Driver referred to
Details valid? No
table sales staff
Yes
Operations print
release note or
Ready to start loading Problem BOL as
procedure
Yes
resolved?
No B
appropriate
No
Problem
resolved?
Driver referred to
sales staff
Driver parks in
vacant parking C
space
Figure 4 - Tank Truck Loading Procedure (No Queuing System)
Page 33 of 47
Driver connects
A ground plug to
tank truck
Driver to intercom
Operators Tank truck
to operations No
alerted OK?
staff
Yes
Driver connects
driver told to Operator resolves
No loading and
exit rack? problem
vapour hoses
Tank TMS downloads

Order quantity to preset
truck
database controller
database
table
table
Yes
Driver presses
Driver disconnects
start button on
ground plug
preset controller
D E F
Page 34 of 47
Page 35 of 47
Appendix D - Typical Queue Algorithm
Start
Enter driver
Driver enters driver
number
Yes number A
again?
TMS checks that

Driver the driver No
database number is valid
table
Error! Driver
Is the driver number
No No
number valid? incorrect or not
valid
Yes
Enter order
number
TMS checks that Enter order

Order the order Yes number
database number is valid again?
table
Error! order
Is the order number
No Valid order
number valid? incorrect or not
valid
Yes
TMS checks that

Enter tank Order
the appointment
truck number database
time is within limits
table
Yes
TMS calculates new

Tank TMS checks that Enter tank
Is the driver appointment time.
truck the tank truck Yes truck number Yes
late? Time = (old time) +
database number is valid again?
(minutes late * f)
table
No
Error! tank
Is the tank TMS displays
truck number TMS allocates new
truck number No appointment
incorrect or appointment time
valid? time
not valid
Figure 7 - Waiting Room Data Entry Procedure
Page 36 of 47
B Fix device
Yes
Problem with Operator enters

Report to Can the
the driver driver, tanker,
A Operations (Sales
interface
Yes problem be No
order details in the
office) fixed?
device? TMS
No
Driver without Order issued/

No
appointment revised?
Yes Tank
truck
database
table
Operations (Sales
office) revise/ make Order TMS checks details
order database
table
Driver
database
table
Operator enters
TMS allocates an
order details in
appointment
the TMS
TMS allocates TMS site

TMS allocates an
queue position by
appointment
appointment time.
TMS prints FAN Driver not allowed

to load
Figure 8 - Waiting Room Data entry Procedure
Page 37 of 47
Enable
Change
tank
Start tank truck Start
truck
status
loading
Driver
presses start
Tank truck
No Waiting button on No Waiting
identified?
preset
controller
Yes Yes
Look at first tank Look at first tank

truck in bay truck in bay
queue queue
Look at next tank Look at next tank

truck in bay truck in bay
queue queue
No No
Does
identified
End of bay Does status = End of bay
tank truck No No
queue? 'AT BAY'? queue?
match the
record
Yes Yes
Set tank truck (t) Set tank truck (t)

status = 'AT BAY' status = 'LOADING'
Start tank truck (t) Start tank truck (t)

'AT BAY' timer 'LOADING' timer
Yes Yes
Stop tank truck (t) Display Stop tank truck (t)

'QUEUING' timer status 'AT BAY' timer
Enable tank truck

Display status
(t) loading
Alarm. tank
Alarm. tank truck
truck not in bay
not in bay queue
queue
Figure 9 - TMS Queue Management
Page 38 of 47
Add Remove
tank tank truck
Start Start
truck to from
queue queue
Number of
tank trucks in
bay (n) traffic
the queue less
No Waiting lights switch No Waiting
than the
to green?
maximum.
(z < x)?
Yes
Yes
Look at first tank Look at first tank

truck in TMS truck in bay
site queue queue
Look at next tank Look at next tank

truck in TMS site truck in bay
queue Yes queue
No No
Can the tank

truck be End of TMS Does status = End of bay
No No
loaded at bay site queue? 'LOADING'? queue?
(n)?
Yes Yes
Reserve record, add

tank truck (t) to the Reserve record and
end of bay (n) queue delete from bay
and delete from site queue
queue
Set tank truck (t) status Stop tank truck (t)

= 'JOIN QUEUE' 'LOADING' timer Yes
Remove one tank

Add one tank truck
truck from the
to the queue length.
queue length. Set z
Set z = z + 1
= z-1
Start tank truck (t) Display Alarm. tank truck

'QUEUING' timer status not in bay queue
Page 39 of 47
Yes
Check tank
Tank truck (t)
truck Look at first tank End of
Start 'QUEUING' No
'Queuing' truck in the queue queue?
timeout?
timeout
Yes
Alarm. Tank
Look at next tank truck
truck 'QUEUING'
timeout
No
Yes
Check
tank Tank truck (t)
Look at first tank End of
truck 'At Start 'AT BAY' No
truck in the queue queue?
bay' timeout?
timeout
Yes
Alarm. Tank
Look at next tank
truck 'AT BAY'
truck
timeout
No
Yes
Check tank
Tank truck (t)
truck Look at first tank End of
Start 'LOADING' No
'Loading' truck in the queue queue?
timeout?
timeout
Yes
Alarm. Tank
Look at next tank truck
truck 'LOADING'
timeout
No
Page 40 of 47
Appendix E - Typical Tank Truck Loading (with Queue)
Tanker arrives at Driver denied access

security gate to site
No
Driver's ID card Driver

examined by security admitted to
personnel site?
Yes
Driver parks in vacant

parking space
Has driver
Yes got host
order?
No
Driver walks to Driver walks to sales

waiting room room
Driver enters driver, Operator makes

order and tanker appointment/ order if
numbers available
Tanker
database
table
TMS checks driver,

Driver Appointment/
order and tanker are No
database order given?
valid
table
Order
database
table Driver, order
and tanker are No
Yes
valid?
Yes
TMS allocates loading Driver referred to

Problem
bay and queue Yes Operations (Sales
resolved?
position office)
No Operations print
Driver waits until his turn is release note or
displayed on the queue BOL as
monitor appropriate
B C D E
Figure 12 - Tank Truck Loading Procedure (Queuing System)
Page 41 of 47
Driver connects
A Yes ground plug to
tank truck
Driver enters
tank truck
number
TMS verifies
Tank tank truck
truck details and
database certification
table
Driver to intercom
Operators Tanker
to operations No
alerted OK?
staff
Yes
Operator Driver connects

driver told to
No resolves loading and
exit bay?
problem vapour hoses
Yes
Tank TMS downloads

Driver disconnects Order
truck quantity to preset
ground plug database
database controller
table
table
Driver presses start

button on preset
controller
F G H
Page 42 of 47
Page 43 of 47
B C D F
Driver parks in Driver instructed to

Driver returns to his tanker
vacant parking space return
J
Driver drives to allocated

loading bay and joins the queue
Has the bay

Yes
been closed?
No No
Is the bay
empty?
Yes
Driver parks in bay and enters

driver number at preset
TMS verifies correct bay and

queue position
E
Correct bay and

Yes No Operators alerted
queue position?
Operator re-assigns bay
Yes
Operator
Is order correct Driver to intercom to
decides to load Yes
for type of bay? operations staff
anyway?
No
No
Driver returns to
tanker
Security checks Driver exits loading

Driver exits site Release note/ BOL bay
K
Page 44 of 47
Appendix F - Typical Pipeline Meter Proving
Start
Proving
Is proving
operation Operator must wait Wait till proving is
Yes operation No
already in until it is complete complete
complete?
progress?
Yes
CPMPCS switches
No prover valves back to
pipeline operation
CPMPCS calculates and

Operator
records new meter
schedules proving
factors and transmits to
operation
TMS
Has interface Wait for interface Meter factor

point arrived at No to arrive at proving historical
proving tee tee display
Yes
Operator
Initiate CPMPCS proving accepts new TMS uploads new
Yes
cycle from TMS meter factor via meter factor data
TMS
CPMPCS commences
proving operation
No
Operator request from

Has interface Wait for interface TMS to CPMPCS to print
point arrived at No to arrive at meter proving report
manifold? manifold
Yes
TMS switches manifold

valves to accept new End
product
Figure 16 - Multi-Product Pipeline Meter Proving
Page 45 of 47
Appendix G - Typical Bulk Plant Automation Overview
Page 46 of 47
Appendix H - TMS Components by Process
Dedicated Receipt Pipeline
Product manifold/Pumps
Shipper/Booster Pumps
Marine Loading (Cargo)

Multi-Product Receipt
Road Tanker Loading
Raw/Potable Water
Rail Tanker Loading
Marine Unloading
Marine Bunkering
Delivery Pipeline
Road Unloading
Vapor Recovery
Sanitary Waste
Closed Drain
Fire Water
Tankage
Pipeline
TMS Control Application X X X X X X X X X X X X X X X X X
ESD System X X X X X X X X X X X
RMPS X X X
Batch Management X X X X X X X
TMS Business Application X X X X X X X X X
Driver Verification System (DVS) X X
Order Information System (OIS) X X
Truck Identification System (TIS) X X
Preset Controller X X X
Driver Interface Device (DID) X X
Queue Monitoring System (QMS) X
Weighscale Electronics X X X
Bill of Lading (BoL) X X X X
Terminal Servers (TS)
Custody Flow Metering X X X X X X
Automatic Tank Gauging X
Custody Radar Tank Gauging? X X
Quality Analysis X X X X X
Automatic Dewatering X
OID/Density Batch Interface X X
Product Autosampling X X X
Product Quality Analyzer X X
Page 47 of 47

Saes Z 008

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

Saes Z 008

Uploaded by

Copyright:

Available Formats

Engineering Standard

SAES-Z-008 7 July 2015

Saudi Aramco DeskTop Standards

Appendix A - Typical Product Tank Allocation.... 30

Previous Issue: New Next Planned Update: 7 July 2018

Primary contact: Zahir, Hussain Ali (zahiha0a) on +966-013-8801838

Copyright©Saudi Aramco 2015. All rights reserved.

1.2 Typical Saudi Aramco Bulk Plant Operations:

1.3 TMS Components functionalities:

k) Terminal Servers (TS)

Appendix H provides a matrix for TMS components by process.

2 Conflicts and Deviations

3.1 Saudi Aramco References

Saudi Aramco Engineering Procedures

Saudi Aramco Engineering Standards

Saudi Aramco Materials System Specifications

Saudi Aramco Best Practice

DVS Driver Verification System

Algorithm: A prescribed set of well-defined rules or processes for the solution

Auxiliary System: A control and/or monitoring system that is stand-alone,

Availability: The amount of time a device is actually working as a percentage

Batch Management System: A TMS Batch Management System provides

Batch Manager: A batch Manager is usually the Shift Supervisor or Shift

Cabinet: A general term describing any enclosure which contains process

Control Algorithm: A mathematical representation of the control action to be

Controller: A microprocessor-based device used primarily to perform

Control Room Rack: A framework, constructed of rails or steel members, for

Custom Application Software: The software written specifically to perform

Distributed Control System (DCS): A process control system that is composed

Emergency Shutdown System (ESD): A system composed of sensors, logic

Hardware: Physical components used within a Terminal Management System

Loading Rack: A framework, constructed of pipes, instruments, mechanical

Logs: Files or printouts of information in chronological order.

Mode: Control block operational condition, such as manual, automatic, or cascade.

Module: An assembly of interconnected components that constitutes an

Operator Console: A console used by an operator to perform the functions

required to monitor and control his assigned units.

Operating System: Software that runs on a computer for the purpose of

Pipeline Receiving Station: The station where hydrocarbon products are

Preset Controller: An electronic metering device used in an industrial

Process Controller: A digitally operating electronic system designed for use in

Process Control System: The integrated system which is used to automate,

Programmable Logic Controller: A digitally operating electronic system,

Rebrand: The reclassification of a product that includes transfer between

Recovered Product: The amount of products that are recovered as a result of

Redundant Configuration: A configuration that provides automatic

Regulatory Control: The functions of regulating certain process measurement

process measurement, control algorithm execution, and final control device

Semi-Automatic: Semi-Automatic control is the use of automation and control

Software: Software shall be considered programming code, computer

Tag: A collection of attributes that specify either a control loop or a process

Terminal Management System: A process automation system comprised of a

TMS Business Application: Application which handles and process business

Transaction: An input message to a computer system that must be dealt with as

Workstation: Is a computer dedicated to a user or group of user engaged in

5.5 The TMS shall be configured to monitor safety interlocks.

5.6 The TMS shall be capable of interfacing with sampling systems.

5.10 The TMS shall be designed to be a tightly integrated components, subsystems,

5.11 TMS software packages shall be vendor's standard Commercial Off-The-Shelf

5.12 TMS software packages shall be configurable to meet job-specific requirements.

5.14 The TMS shall be configured to permit the completion of a single

5.17 The TMS shall be configured to automatically upload/download flow meter

manually perform validation of driver, tank truck and order details.