Sabp y 856

Best Practice
SABP-Y-856 22 June 2016

Metering Supervisory Computer for
Custody Transfer Measurement of Hydrocarbon Gases
Document Responsibility: Custody Measurement Standards Committee
Contents
1 Scope and Purpose........................................ 2
2 Conflicts and Deviations................................. 2
3 References...................................................... 2
4 Definitions and Abbreviations......................... 3
5 General Requirements.................................... 5
6 General Design Requirements........................ 7
7 Operational Design Requirements................ 15
8 Security......................................................... 22
9 Diagnostics................................................... 23
10 Event Logs.................................................... 24
11 Trending........................................................ 25
12 Historical....................................................... 25
13 Testing…………………................................. 26
14 Documentation.............................................. 27
15 Shipping Requirements................................. 27
Appendix............................................................... 29
Previous Issue: New Next Planned Update: TBD

Page 1 of 38
Contact: Salim, Mohammed (salimx0b) on +966-13-8801371
©Saudi Aramco 2016. All rights reserved

Document Responsibility: Custody Measurement Standards Committee SABP-Y-856
Issue Date: 22 June 2016 Metering Supervisory Computer for
Next Planned Update: TBD Custody Transfer Measurement of Hydrocarbon Gases
1 Scope and Purpose
This SABP provides design guidelines and functional requirements for a Metering
Supervisory Computer (MSC) used in hydrocarbon gas Custody Metering Systems.
This SABP shall be followed in developing MSCs in all Saudi Aramco hydrocarbon gas
Custody Metering Systems.
This SABP is based on current experiences and lesson learned in developing, operating
and maintaining hydrocarbon gas Custody Metering Systems.
2 Conflicts and Deviations
Any conflicts between this SABP and any other Saudi Aramco Materials System
Specifications (SAMSSs), Engineering Standards (SAESs), Standard Drawings,
(SASDs), or industry standards, shall be resolved by Chairman of Custody
Measurement Standards Committee.
3 References
Material or equipment supplied to this specification shall comply with the latest edition
of the references listed below, unless otherwise noted.
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
Saudi Aramco Materials System Specification

34-SAMSS-846 Flow Computer for Custody Transfer Measurement
of Hydrocarbon Gases
Saudi Aramco Form and Data Sheet

Form NMR-7907 Nonmaterial Requirements for Instrumentation
(General)
3.2 Industry Codes and Standards
Electronic Industries Association

EIA/TIA-232-E Interface between Data Terminal Equipment and
Data Circuit-Terminating Equipment Employing
Serial Binary Data Interchange
Page 2 of 38
EIA RS-422-A Electrical Characteristics of Balanced Voltage

Digital Interface Circuits
EIA RS-485 Electrical Characteristics of Generators and
Receivers for use in Balanced Digital Multipoint
Systems
American National Standards Institute/Institute of Electrical & Electronics
Engineers
ANSI/IEEE 802.3 Supplement to ISO/IEC 8802-3, Local and
Metropolitan Area Networks Sections 13 & 14
International Electrotechnical Commission
IEC 61000-4-3 Radiated, Radio-Frequency, Electromagnetic Field
Immunity Test
IEC 61000-6-2 Electromagnetic Compatibility (EMC) - General
Standards - Immunity for Industrial Environments
National Fire Protection Association
NFPA 70 National Electrical Code (NEC)
API Manual of Petroleum Measurements Standards (MPMS)

Chapter 1 Vocabulary
Chapter 12 Calculation of Petroleum Quantities
Chapter 21 Flow Measurement Using Electronic Metering
Systems
4 Definitions and Abbreviations
4.1 Definitions
Configurable: The capability to select and connect standard hardware modules

to create a system, or the capability to change functionality or sizing of software
functions by changing parameters without having to modify or regenerate
software.
Commentary Note: A sub-paragraph that contains comments that are

explanatory or advisory in nature. These comments are not mandatory, except
to the extent that they explain mandatory requirements contained in this
standard.
Custody Transfer Measurement: A specialized form of measurement that

provides quantity and quality information used for the physical and fiscal
documentation of a change in ownership and/or responsibility of hydrocarbon
Page 3 of 38
commodities. This includes measurement of hydrocarbon liquid or gas

movements (deliveries or receipts) between Saudi Aramco and its customers,
suppliers, joint ventures and transport contractors including VELA ships.
Dead Band: The range through which an input signal may be varied without
initiating an action or observable change in output signal.
Delivery: A custody transfer from a Pipeline to a customer.
Display: Set of operator computer schematics that generated by the MSC to

show metering information or point status using predefine common schematics.
Field-Proven: Field proven is defined as successfully tested in operation at a

field installation for six (6) months or more. It shall be possible for Saudi
Aramco to verify the field proven status of the system.
Flow Computer: An electronic device designed for calculating and totaling

metered volumes, and/or calculating meter correction during a check for one or
more meters.
Graphics: Set of operator computer schematics that graphically represent a

section of metering system using graphics symbols and dynamics link to real
time metering data.
Meter Run: A single pipeline meter with associated inlet block valve, flow
conditioning sections, control valve, outlet block and instrumentation.
Meter Skid: The field portion of a metering system consisting of meters, flow
conditioning sections, block valves, control valves, piping, instruments,
electrical equipment, and associated structural steel.
Meter Station: A facility that is primarily dedicated to the measurement of the

quantity and quality of hydrocarbon gas.
Metering Supervisory Computer (MSC): Computer that performs supervisory

functions (data archiving, report generation, system integrity checks, alarm
logging, meter factors curves, validation, diagnostics, MF control charting, etc.
and operator interface) for a metering system.
Metering Control System (MCS): An integrated automation system that

performs supervisory and control functions (MSCs, flow computers, PLC,
printers) for a metering system.
Metering System: A complete assembly of equipment designed to measure

quantity and quality of a hydrocarbon liquid or gas. The metering system
Page 4 of 38
includes, but is not limited to, the meter skid (meters, strainers, flow
conditioning sections, valves), GC, sampler, and metering control system, etc.).
Receipt: A custody transfer to a customer.
Redundant Devices: Two identical devices that operate in an interchangeable

duty/standby arrangement in which the functions of the duty device are
duplicated in the standby and are automatically transferred to the standby if the
duty fails without the intervention of a third device.
Ticket: A document specifying the quantity and quality of hydrocarbon

measured using a meter.
Vendor: The party that supplies or sells integrated metering systems, metering
equipment, or components.
4.2 Abbreviations
API American Petroleum Institute
AGA American Gas Association
CBM Computer Bases Monitoring
FC Flow Computer
GUI Graphical User Interface
ISO International Organization for Standards
MCS Metering Control System
MSC Metering Supervisory Computer
PLC Programmable Logic Controller
SCADA Supervisory Control and Data Acquisition
5 General Requirements
5.1 Environmental Conditions
The Metering Supervisory Computer (MSC) shall be installed indoors and

designed to operate at an ambient temperature of 35°C and relative humidity of
20% to 80%, non-condensing
5.2 Electrical Requirements
Unless specified otherwise in the purchase order, the MSC shall be suitable for
operation within the specified voltage variations as given in Table 1.
Page 5 of 38
Table 1 – Supply Voltages
System/Device Supply Voltage

Nominal NEC Class
Tolerance
110-240 VAC, 110 – 126/
Power 1 or 3
50/60 Hz 220 - 240 VAC
Provision for grounding shall be available on the MSC.
5.3 Radiated Electromagnetic Susceptibility Test
A conformance certificate from an authorized agency stating the equipment is

immune to electromagnetic interference, electrostatic discharge, radio frequency
interference, surge and fast transients, voltage dips and interruptions at
Performance Level A in accordance with IEC 61000-6-2. The certificate must
confirm the equipment is immune to radiated, radio frequency and
electromagnetic emissions in accordance with IEC 61000-4-3 using Test Level 3.
5.4 Units of Measurement
The units of measure for the MSC shall be specified in the purchase order and
shall be either the U.S. Customary (USC) or metric (SI) system for the custody
transfer measurement:
Item Metric (SI) U.S. Customary (USC)
Volume M³ mmscf
Flow Rate M³/H mscfh, mmscfd
Temperature °C °F
Static Pressure KPa Psig
Differential Pressure Pad Inch WC
Density Kg/M³ Lb/scf
Heating Value J/M³ Btu/scf
Total Heating Value MJ mmBtu
5.5 Vendor Responsibility
The vendor shall guarantee to support all system hardware, firmware, and
software with spare parts and services for a period of five (5) years from the
system delivery date or as defined in the contract or purchase order.
This support shall not be contingent on the customer upgrading to later releases
of software or hardware unless this upgrade is supplied at no additional cost.
Page 6 of 38
6 General Design Requirements
6.1 General MSC Requirements

a) Latest standard of-the-shelf personal computer shall be used for MSC(s).
b) The application software shall run on standard operating systems.
The standard operating system software shall not be modified to meet any
Saudi Aramco's requirements.
c) Acceptable HMI packages shall be approved for system integrators during
their approval process or upon request to be used for MSC. The system
integrator shall provide engineering level training for maintaining the HMI.
d) All supplied hardware, firmware, and software shall be field tested product
prior to freeze date as defined for the MSC in the purchase order or the
contract.
e) Restart of the MSC after power failure shall be automatic and shall include
restart of all features, devices and programs including correct time from a
battery backed up calendar clock. The MSC shall synchronize all sub-
systems clocks. Totals and constants shall survive a power fail.
f) The MSC shall be designed with 50% additional spare capacity for its
processing and storage.
g) A color monitor display, a pointing device (touch screen, mouse, etc.),
and keyboard for alphanumeric entries shall be provided with each MSC.
The type of monitor may be either desk or panel mounted. If a desk type
monitor is provided, it shall be a LCD flat screen with a minimum size of
21 inches. If a panel-mounted type monitor is provided, its size shall be a
minimum of 19 inches. Both types of monitors shall provide a minimum
display resolution of 1280 * 1024 (non-interlaced and low radiation).
At the discretion of the operating organization, a KVM with a single
monitor maybe supplied.
h) The MSC shall provide connectivity to any standard laser printer (s)
configured on a network in which the MSC is connected.
i) The MSC shall be capable of communicating any I/O data (GC data, etc.) to
a higher level system.
j) The MSC shall be labeled using a tag with Plant No.- MSC- 001, 002, etc.
6.2 MSC Communications

a) The MSC shall as a minimum, support multiple EIA/RS-232, EIA/RS-422,
EIA/RS-485, or ANSI/IEEE 802.3 ports for communicating with external
Page 7 of 38
devices such as other metering supervisory computers, flow computers,

DCS, printers, etc.. Acceptable real-time data communications protocols
include Modbus/RTU, Modbus TCP/IP, and OPC. A fully networked
solution shall be preferred.
b) Single and double precision floating-point values transferred over the
communication links shall conform to the IEEE floating-point formats.
c) The MSC shall implement error check over its communication links
incorporating either Cyclical Redundancy Checking (CRC) or Longitudinal
Redundancy Checking (LRC) or Vendor's equivalent method, in
conjunction with bit parity checks, fail-safe transmission timer and message
error detection.
d) The MSC shall provide configurable, automatic communication retries for
any malfunction occurring during message transfers.
e) Recoverable and unrecoverable communications errors shall be recorded by
the MSC for each communications channel and stored in a history file.
f) Failure or planned shutdown of any device connected to the communication
network shall not affect the ability of the MSC to communicate with any
other device on the network or degrade its performance.
g) All devices connected to the communication network including redundant
equipment shall be monitored for failures. An alarm shall be generated in
the MSC for each failure detected. An overall graphical display showing
the status of all the devices and their communication links shall be
available.
h) Information available over the MSC communications links to sub-systems
shall include, but not be limited to:
 Any sub-system configuration programs
 All dynamic and static data (pulse totals, temperatures, pressures,
volumes, etc.)
 I/O & alarm status
 Reports listed in this documents
 Flow meters computer based monitoring package data
 Data input locally by the operator
i) The MSC shall maintain a data base with the ability to input and/or output
floating point, digital and alphanumeric data from the keyboard or via the
Page 8 of 38
communication links to any other sub-system connected to it. Such data

shall include, but not limited to:
 Set points and mode changes
 Meter ticket (ticket start/stop, etc.)
 GC data.
 Date and time
 Data entered Manually
 Meter factor calibration data for each meter (up to a maximum of 12)
 Meter data (serial number, nominal K factor, etc.)
 Master meter data for the check meter
6.3 MSC Application Software

a) Application software shall only require software patches modifications in
order to be able to run the same features under new releases of the MSC
operating system software.
b) Start/stop of application programs shall be provided under engineering
access control.
c) Full development application software shall be provided for any number of
MSCs provided on a given project.
d) No software or hardware locking mechanisms that restrict the user from
copying the software source code from the storage media shall be
employed. The ability to rebuild the complete application from source code
supplied by the vendor shall be provided. A detailed manual for guiding
user on full installation shall be provided as standard document.
e) The MSC shall have the capabilities to utilize Relational Databases such as
Oracle. It is acceptable if vendor provides a full Relational Database
interface tools such as ODBC, SQL, etc.
f) Data entries shall be validated by the MSC, e.g., that an entered input is
within the permissible parameter range. When an entry is invalid, an
advisory message shall appear indicating the error.
g) The operator dialogue shall be designed to avoid performing actions
unintentionally. The MSC shall give feedback to the operator that a
command has been registered, and that processing has started. The MSC
shall give failure message with reason if the command has been rejected.
Page 9 of 38
h) The MSC shall be designed to meet the following performance requirements:

 Operator command 5 seconds for acknowledgement of alarms on the
MSC (measured from operator action until acknowledgement is
observed on the display screen).
 Operator command 5 seconds from command to field action (measured
from operator action until output has been initiated).
 Any loop control max. 5 seconds from input to output initiation.
 Alarm display text 5 seconds from alarm limit being reached
 Graphical update max. 5 seconds to complete graphic call up for any
display containing 100 variables (dynamic objects).
 Historical data display updates shall occur within five seconds of call up.
6.4 MSC Application Configuration

a) An interactive editor for building and maintaining configuration database
shall be provided.
b) The MSC shall have the tools to perform global search and modifying on-
line databases. It shall be possible to add or delete points from the history
configuration on-line without shutting any of the history devices.
c) Configuration displays shall be provided to help in configuring new
displays in the MSC. These shall include displays to show:
 All tags in the system
 All parameters for each tag, including (as applicable) tag ID, tag
descriptor, the hardware address, algorithm relating to the tag, and
input/output details
 All configurable (or soft) keys and their function
d) Configuration changes shall automatically update all modules and tags
affected by the change.
g) The MSC shall include, but not limited to the following capabilities:
 Configuration of all metering system data (meter, check meter, sampler,
etc.) under appropriate security level.
 Sub-systems configuration programs (PLC, Flow Computer, GC).
These software packages shall also provide an electronic format (CD or
DVD) with instructions for installation and setup on the MSC.
 Flow meter (CBM) and GC diagnostics
Page 10 of 38
 On-line and/or off-line database generation

 Graphics and display generation and modification
 Control algorithm generation and modification
 Report generation and modification
 Symbols generation and modification.
 Trends generation and modification.
 System access configuration
 File access
 Diagnostics
 Communication links setup
 Backup and restore facility along with procedure
h) Single faceplates for control and indication of multi-state devices shall be
provided. For example, a MOV shall indicate open, closed, and travel.
i) The MSC shall provide the ability to download or upload any data base or
configuration data to all sub-systems in the metering control system.
j) Vendor shall provide standard packages for developing reports using a
conventional method with drop-in tags, etc. Software programming shall
not be required to generate any reports in the MSC. It shall be possible to
use any variable in the MSC within a report.
6.5 MSC Displays

a) All values shall be displayed on the GUI in the units specified for the
application. Decimal resolution on the MSC display shall be sufficient to
verify the requirements for calculation accuracy and shall be as defined in
the reports.
b) All text presentation, abbreviations, icons, symbols, numerical data, borders,
lines, arrowheads, size and shape, screens, etc., shall be clear and readable.
c) The operator displays shall be designed with consistent layout, appearance,
legible (look-and-feel) and required functionality.
d) Operators shall be able to access specific displays and graphics by pressing
dedicated (hard or soft) functions keys, selecting from a list of displays in
directories or menus, or by typing display or graphic names.
Page 11 of 38
e) It shall be possible to move between related displays and graphics of

different detail levels or of the same detail level with a maximum of two
operator actions.
f) It shall be possible to limit the number of opened displayed areas. It shall
be easy to navigate between displays. Direct jumping between displays
shall be possible. The MSC display shall have a return button to go back to
the previous display.
g) The capability to generate a hardcopy of any active display shall be
available. Generation of a hard copy shall not freeze the monitor display
for longer than 5 seconds.
h) All displays and graphics that show real time data shall be automatically
updated when the display or graphic is on a screen.
i) Display capability shall include “Page Forward” and “Page Back” for
viewing of listings longer than one display page.
j) Each display or graphic shall have a dedicated alarm zone which shall
display, as a minimum, the three most recent alarms.
k) The format of numeric data shall have the capabilities to display a single
digit to 8 digits (not including the sign or decimal place), and 0 to required
number of decimal places. The numeric formatting shall be configurable on
an individual basis. Data displayed in the GUIs shall meet the requirements
of API Chapter 21.1, Flow Measurement Using Electronic Metering
Systems.
l) Symbolic representation of data on the graphics shall be performed by
shape changes, color changes (foreground and background independently),
and flashing in any combination. The MSC shall have a help screen
showing all symbols and status codes used in any display.
m) All graphics shall include the following information in standard locations:
 Title
 Date and time
 Display name
 Screen/Display No.
 Tag number of the MSC
 Duty/standby status
n) GUI displays shall include, but not be limited to the following:
 Display Selection (summary of selectable displays)
Page 12 of 38
 System Overview (all main components)

 Meter Skid Display(s)
 Check Metering Set-up (when applicable)
 Check Metering Calculations (when applicable)
 Meter diagnostic screens
 GC Set-Up (when applicable)
 GC Status & Data (when applicable)1
 Measured Values2
 Report Selection
 Report Inputs
 Active Alarms
 Alarm History
 Trends
 System, Communications Status and Control
 Settings (Set-points, limits and default values)
 Meter Calibration Data
 Meter Data
 Flow Computer Data
o) Measured values screens shall be provided for each meter and the station,
and should include the following information from each flow computer:
Temperature, pressure; density; composition (if a gas chromatograph is
provided); gross, gross standard and mass flow rate; gross, gross standard
and mass quantities for current batch; gross, gross standard and mass
quantities for previous batch.
p) Total of three graphic displays shall be designed for comparison operation.
q) The first display shall be for inputting the configuration data of the meters
with password security at an engineering access level. This display shall
include, but not limited to, the following information:
 Comparison Volume Desired
 % Volume Deviation
 Comparison Duration
 Temperature Stabilization time
 Acceptable Temperature difference between Check and duty meter
Page 13 of 38
r) The second display shall have Check/Duty meters with indication of the
current meter being compared, meters volumes, previous historical meter
data, current temperature, pressure, flow rate, density, Meters MOVs status,
and control points shall be displayed. Operator control points shall be
provided for all MOV valves.
s) The third display shall have the results of the comparison operation as it is
shown in the Comparison Report.
t) The MSC shall in a large metering system to display the volume
differences, temperature, pressure, differential pressure, density, GC data
between the duty and standby flow computers in tabular and graphical
formats on a separate display.
u) When using fallback values from failed transmitters instead of the live
signals during a report interval, these values shall be visually identified on
the MSC display by an * and printed in any report in which this data is
used.
v) MSC HMI shall comply with project standard for graphics, text, color,
symbol, line, etc. The details shall be provided by proponent organization
as part of project documentation.
w) It should be possible to open the process page where alarm exist by pressing
one of the active alarm.
x) It shall be possible for an engineer to navigate directly from a mimic object
to configuration of the object without the need for textual searches.
y) The MSC shall capture from flow computer and display the following
diagnostic parameters on continuous basis from ultrasonic meter(s):
 UFM path AGC level
 Signal to noise ratio
 Paths transit times
 Flow velocity of each path
 Average axial flow velocity of the meter
 Speed of sound for each path
 Average speed of sound
 Velocity sampling interval
 Averaging time interval
 Percentage of accepted pulses for each path
 Status and/or measurement quality indicators
Page 14 of 38
 Alarms, path failures indicators, etc.
These parameters shall be displayed, trended and archived in the MSC

with ability to perform historical trending.
z) The MSC shall capture from flow computer and display the following
diagnostic parameters on continuous basis from Coriolis meter(s):
 Pick off voltage
 Drive gain
 Live zero
 Field verification zero
 Raw tube frequency
 Tube stiffness
 EPROM checksum error
 RAM or ROM test error
 Sensor failure
These parameters shall be displayed, trended, and archived in the MSC with
ability to perform historical trending.
7 Operational Design Requirements
7.1 Operation
7.1.1 The MSC shall have option under engineering access level to change the
fiscal day timing for continuous measurement to be, e.g., 00:00, etc.
7.1.2 The MSC shall not perform any calculation that can be performed at the
sub-system by the flow computers.
7.1.3 Normal operational commands and data input for a transfer shall include,
but not limited to:
 Terminate meter ticket
 Set flow control mode (auto/manual), set points, outputs
 Input GC composition
 Open/close/stop MOV
 Select meter and initiate Check Comparison
7.1.4 The MSC shall at a minimum provide a GUI for displaying up to

4 previous tickets/batches stored in the flow computer historical data
memory and generate reports for storage and printing.
Page 15 of 38
7.1.5 Normal commands associated with Check Comparison shall include, but
not limited to:
 Set Auto/Manual Check
 Set time for Auto Checking
 Input Lab GC Data
 Select meter to be Compared
 Line-up the meter for Comparison
 Initiate Comparison
 Abort a Comparison
 Set product density
7.1.6 The MSC shall in a large metering system read the following data from
the duty and standby flow computers for each meter: 1) Actual volume,
2) Standard volume and 3) raw pulses during the batch. The MSC shall
calculate the percentage difference between the duty and standby
computers for each meter. The MSC shall set an alarm when the
percentage difference for a quantity exceeds a configurable limit.
7.1.7 At the conclusion of each ticket, the MSC shall in a large gas system
calculate the percentage difference between the end-of-ticket standard
volumes and energy from duty and standby flow computers for each
meter. If the percentage difference exceeds a configurable limit, the
MSC shall perform the following:
 Set an alarm
 Log the time, ticket number and percentage difference
 Store the following data from the duty and standby MSCs in a meter-
specific file:
1) Actual volumes,
2) Standard volumes,
3) Raw meter pulses.
7.1.8 The MSC shall provide the option for using the check meter as a back-up
to the normal duty meter(s).
7.1.9 The MSC shall generate all reports in the check meter when it is being
used as a duty that are associated with the normal duty meter.
7.2 Metering Control
7.2.1 If specified in the purchase order or project specifications, the MSC shall
Page 16 of 38
perform non-metering operations required to support metering activities.

These non-metering include but not limited to display and control of
Remotely Operable Isolation Valve, etc. The vendor must ensure
inclusion of non-metering operations will not impact metering operations.
7.2.2 The MSC shall not perform any valve control logic that is performed at
the sub-system level.
7.2.3 The MSC shall issue commands and verify status on Open/Stop/Close
logic with completion alarm timers, Remote/Local sensing, and have the
ability to issue reverse travel command before any current active
command is completed for each MOV in the control sub-system.
7.2.4 The MSC shall provide status of any interlock sequential control logic
for the metering system valves in the control sub-system. The logic
provided shall include, but not limited to provisions for preventing the
opening of more than one duty meter valve for comparison at a time, the
closing of a duty meter run prior to opening of the check meter inlet and
cross-over valve, valve timeout alarms, etc..
7.2.5 The MSC shall set an alarm flag for any MOV operated locally.
7.2.6 The MSC shall display refusal of a sequential operation (open meter run,
line-up meter for comparison) if any of the valves are in LOCAL
position and an alarm must be raised.
7.2.7 The MSC shall issue command to the control sub-system for an
operation upon an operator confirmation. At a minimum, these include
opening, closing and line-up of any meter run. Options shall be provided
to operate individual valves under technician access level.
7.2.8 Following a line-up request for comparison, the MSC shall perform the
sequence to open and close appropriate valves for performing the
Comparison check.
7.2.9 At the completion of the Comparison check, when requested by the

operator, the MSC shall issue a command to the control sub-system to
sequence the valves to place the duty meter in normal operation.
7.2.10 The MSC shall be able to perform all the basic monitoring and control
functions from graphic displays for the metering station. These
functions shall include, but not limited to, opening/closing meters,
Comparison check, daily tickets, changing process variables, alarm logs,
set-points, switching control modes, manually driving outputs, or
initiating maintenance bypasses for input points, reports.
Page 17 of 38
7.3 Meter Tickets

a) The MSC shall be capable of automatically terminating the daily delivery
on a meter at the end of the fiscal day or when requested manually by the
operator. The meter ticket shall be automatically printed and stored to the
meter’s storage area.
b) Each meter ticket shall have a distinct ticket number with all measurement
data present to enable verification and traceability as shown on the
templates in the attachments of this document. The ticket numbers are
generated by the flow computer.
c) Where a metering system has a GC installed, the MSC shall provide an
option to accept the GC reading or input lab data for the meter ticket and
comparison check.
7.4 Comparison Checking
7.4.1 The MSC shall allow line-up of any meter for Comparison operation
regardless of whether it is on delivery or not.
7.4.2 The meter flow rate during the Comparison shall remain the same as that
being supplied to the customer. The ability to change modes, enter a
percent (%) output and set points, shall be available through the MSC.
7.4.3 The MSC shall provide an abort option for the Comparison. Upon an
abort, the appropriate warning shall be alarmed. The failed Comparison
report shall be saved in the MSC failed report section for the meter.
7.4.4 Following an aborted Comparison, the MSC shall reset all conditions to
enable another Comparison to be requested. Any failed Comparison
shall be rejected and stored to the meter’s proof failed archive.
7.4.5 For a successful Comparison, a Comparison report shall be stored in a

distinct meter archive and printed automatically for the meter.
7.4.6 Each meter Comparison report shall have a distinct report number which
is generated by the MSC.
7.5 Reports
7.5.1 All reports format shall be per the templates provided in the attachments
of this document. The print shall be in Adobe PDF format.
7.5.2 The MSCs shall compile and archive as minimum the following reports:
 Comparison Report
Page 18 of 38
 Delivery Ticket
 Current status (Flow Computer)
 Hourly (Flow Computer)
 Configuration report (upon demand)
 Audit trail report (upon demand)
 Historical alarm report (upon demand)
 Snapshot report (upon demand)
 Meter calibration report (upon demand)
7.5.3 All reports data shall be in accordance with Appendix of this document
and aligned with 34-SAMSS-846, Flow Computer for Custody Transfer
Measurement of Hydrocarbon Gases.
7.5.4 The MSC shall have the capability to archive as a minimum previous
1000 reports of each type. Each meter must have its own set of distinct
reports (ticket, proving report, delivery/receipt summary report, failed
proofs, etc.) for easy reviewing and printing. The operator shall be able
to preview and print, if required, any report in the MSC archive.
7.5.5 It shall be possible for all reports to be displayed on an MSC screen as

well as print to a report printer.
7.5.6 Out-of-range and unknown status inputs shall be flagged by a special

character such as a question mark or other reserved symbol.
Numerical values shall not be used.
7.5.7 The MSC and/or printer shall queue the multi-printing request without
degrading the performance of the metering control system. It shall be
possible to dedicate printers for reports only with option for inhibiting
each printer.
7.5.8 The MSC shall output reports to the network attached laser printers.
Metering delivery tickets shall be printed at the termination of the
delivery. Delivery ticket shall be output to the printer at the conclusion
of the fiscal day. Comparison reports shall be printed upon completion
of the process for meters being compared.
7.5.9 It shall be possible to print the reports from the flow computer on the
network report printer.
7.5.10 Each MSC shall be capable of generating the following alarm/event reports:
 Active Alarm Summary
Page 19 of 38
 Ticket Alarm/Event Report (for each meter ticket)

 Comparison Alarms/Event Report (for each meter comparison
operation)
7.6 Alarms
7.6.1 The MSC shall provide separate displays for system alarms, process
alarms, and events to enable the operator to review these easily.
The MSC shall not generate any nuisance alarms at computer startup.
Any alarm generated by a sub-system of the MCS shall be displayed by
the MSC with timestamp. Alarms not generated by the sub-system such
as meter comparison failure, etc., shall be configurable at the MSC.
7.6.2 The MSC shall ensure that alarms requiring immediate operator action
are presented in a manner that supports rapid detection and
understanding by the operator under all alarm loading conditions.
Acknowledgment of flow computer alarm on the MSC shall also
acknowledge the alarms on the respective flow computer.
7.6.3 When viewing any MSC display screen, the operator must be able to
identify current alarm state, i.e., new, acknowledged, or cleared of recent
alarms.
7.6.4 The MSC shall continuously monitor and alarm on but not limited to the
following:
 Watch-dog timer timeout on any sub-system
 Memory error (RAM or ROM)
 Program errors
 I/O failures
 Sub-system communication failures
 Ticket start, end.
 Comparison success, failed, aborted, timeout, meter under
Comparison.
 Flow computer power failure
 Any user configured alarms
7.6.5 The GUI shall have a Display Selection Menu containing an overview of
selectable displays. Acknowledgment of alarms on one MSC shall cause
them to be acknowledged on any other MSC or any sub-system
generating the alarm.
Page 20 of 38
7.6.6 Alarms shall be categorized by at least four levels. The level shall be
configurable at the point database level.
7.6.7 To minimize analog input “chattering” (a point going in and out of an

alarm condition rapidly) there shall be configurable dead band
parameters, on a per tag basis.
7.6.8 For analog tags, the configurable triggers for process alarms shall include:
 Process variable high limit exceeded
 Process variable high high limit exceeded
 Process variable low limit exceeded
 Process variable low low limit exceeded
 Process variable rate-of-change limit
 Process variable deviation from set point
 Process variable invalid value
 Point is faulty as loss of communication, out of service, etc.
7.6.9 There shall be a summary display of active alarms. This display shall
show all currently active alarm conditions. An alarm indication shall not
be cleared unless the alarm has been acknowledged and the device has
returned to normal condition. Accessing this alarm summary display
from any other display or graphics shall require no more than one
operator action.
7.6.10 The alarm summary display shall list alarms in tabular format in order of
occurrence with the most recent alarm on top.
7.6.11 It shall be possible to display at least 100 alarms in an alarm summary.

Multi-page displays may be used. If so, it shall be possible to page
forward or backward and scroll up and down by a single operator action.
7.6.12 Alarms stay flashing even after they have returned to normal until they
are acknowledged. Acknowledged alarms return automatically to the
normal colors upon return to normal state. For graphics, the colors for
different types of alarms shall be configurable.
7.6.13 It shall be possible to manually inhibit alarms on a point-by-point or

group basis. This capability shall be protected by password control at
engineering access level. These actions shall be logged.
Page 21 of 38
8 Security
This section details the requirements for restricting access to MSC functions.
Four levels are required. It shall be possible to configure these levels with selectable
privileges. Each higher level shall include all the lower level privileges. The metering
system manufacturer/ integrator shall implement and provide system hardening
procedure for OS, application and communication per SAEP-99.
Level 0 View Only
It shall be possible to configure any MSC for “View Only” access.

This mode shall allow the viewing of all process values, configuration
data, process displays, system status displays, trends, and reports
configured in the system; but shall not allow the manipulation of any
data or parameters.
Level 1 Operator
This level shall allow normal operating functions to be performed.

These include but not limited to:
 Metering operations (meter run open/close, Comparison, ticket, etc.)
 Changing of FCVs set points.
 Changing of FCVs mode (auto/manual, etc.)
 Acknowledgment of process alarms/events
 Acknowledgment of system alarms/events
 Configuring and viewing trends
 Viewing/Requesting reports
 Viewing/Requesting logs
 Viewing of system diagnostic displays
 Manual selection of FCs for duty.
Level 2 Technician
This level shall allow restricted functions to be performed. These include:

 Individual MOV operations
 FCV operation
 Modifying alarm parameters
 Modifying tuning parameters
 Manual override of process input values
 Process variables calibrations
Page 22 of 38
Level 3 Engineer
This level shall allow engineering functions to be performed. These include

but limited to:
 Sub-system configurations
 Alarm disable/enable
 Building graphics, displays, reports, and symbols
 Software modification/development
 Configuring password and key lock access
 Database development/modification
 Changing/assigning passwords
 Set up and delete users
 Control passwords
 Restrict file accesses
 Setting file attributes
 Restricting any system resources
The MSC shall be secured by a password on the user level. Individual users shall be
granted access to display, graphics, and report based on the above listed privileges.
9 Diagnostics
9.1 Where Ultrasonic and Coriolis meters are used in the meter system, the
manufacturer’s full meter diagnostic package shall be embedded in the MSC
with analysis displays for simplifying the assessment of meter(s) health.
9.2 Diagnostics shall be provided to check the MSC (boot-up failure, application
start-up failure, hard-disk failure, etc.). These diagnostics shall be provided to
assist in MSC maintenance and troubleshooting.
9.3 MSC status displays shall be provided to indicate the status of the communications
links and any other devices on the network in the metering control system.
9.4 Standard displays shall show the operational status of the communication
network. The communication parameters of each device connected to the
communication network (on-line, off-line, failed, duty failed, standby failed)
shall be shown.
Page 23 of 38
10 Event Logs
10.1 An application software version number or configuration certificate shall be

accessible to enable changes in the application software to be identified.
10.2 Each event history file entry shall contain the time and date of occurrence, the
tag ID, Tag descriptor and value/state and the type of event.
10.3 Log entries shall be generated for tags going to an alarm state and for tags
returning to normal state.
10.4 A log shall be available for tracking operation and engineering actions or
changes. Actions shall be further divided into “Operation” or “Engineering.”
10.5 Operation actions include normal operator and technician actions that are to be
logged in history files including but not limited to:
a) Change made to the mode of a FCV,
b) Change made to the set point of a FCV,
c) Change made to the output of a FCV,
d) Responses to operator prompts,
e) Toggle of an alarm between inhibit and enable,
f) Change made to alarm limit,
g) Ticket termination, Comparison, etc.
h) Forcing member of a redundant pair on or off duty status
10.6 Engineer Actions consist of normal engineer actions that are to be logged in
history files, including but not limited to:
a) Change made to tuning parameters,
b) Download or modification of tag or module configuration
c) Modification to software used by the MSC
d) Placing devices on-line or off-line
e) Responses to engineer prompts
11 Trending
11.1 The MSC shall be capable of providing both real-time and historical trends.
11.2 The MSC shall support pan-and-zoom feature of any trend display.
11.3 Trends shall be provided in adjustable window size, which could be full, half
screen size, etc.
Page 24 of 38
11.4 Text accompanying the trend shall show the following for each tag: tag ID,
minimum scale value, maximum scale value, time scale, engineering units, and
current value.
11.5 The time periods and process value scales available for trend displays shall be
selectable.
11.6 It shall be possible to trend as a minimum of four different tags simultaneously

on one trend display. Each tag shall be represented by a different color.
11.7 It shall be possible for the technician to define and store the trend sets.
11.8 Real time trends shall be updated every two seconds with actual process data.
11.9 It shall be possible to configure scale and time span on trend displays for display
purposes. One minute average values for 4 days and five or six minute average
values for a month shall be provided as a minimum.
11.10 Consecutive trend data shall be connected by straight lines.
12 Historical
12.1 It shall be possible to store the value of any of the following parameters in
on-line history storage:
 process input/output values/status
 calculated value/state
 digital input/output states
 system events and alarms
12.2 Recoverable and unrecoverable communications errors shall be recorded by the

MSC for each communications channel and stored in a history file.
12.3 The historical data collection package shall be capable of storing the following
number of recent discrete events as a minimum:
Event Type Capacity

Process Alarms 6,000
System Alarms 2,000
Operator Actions 2,000
Engineering Actions 2,000
Page 25 of 38
12.5 It shall be possible to transfer historical data to removable media for long term
historical data storage.
12.6 It shall be possible to recall and display any data that has been stored on
removable media. It shall be possible to transfer archived data in a format that
can be displayed on a PC using word processing or spreadsheet software.
12.7 On-line historical data shall be stored for access via history trends, displayed
listings, and printed listings.
12.8 Historical data collection rates shall be configurable between 15 seconds and
1 hour, day, etc.
12.9 When an analog point is not available (point off scan, out of range, etc.) an
unavailable code shall be entered in the history.
13 Testing
13.1 Each MSC shall have as part of the purchase delivery a factory test certificate
verifying complete testing prior to leaving vendor site. This test shall ensure the
MSC meets all functional and operational requirements.
13.2 The tests shall include but not limited to self-check and self-diagnostics at cold
start, warm start and continuously during normal operation shall be part of the
factory test. The algorithms and fixed parameters important for accurate
computation of custody transfer quantities shall be verified as part of the factory
test.
13.3 Integrated systems that are staged at a vendor's facilities shall be tested
according to Factory Acceptance Test (FAT) procedures produced for each
metering control system project. The integrated test during FAT at vendor site
shall be conducted with maximum flow design capability of the metering system
to ensure data monitoring and reporting meets requirements.
13.4 FAT criteria shall be developed by the vendor and approved by Saudi Aramco.
13.5 The vendor shall supply a list of any required test tools.
14 Documentation
14.1 The vendor shall provide nonmaterial items as shown on Form NMR-7907.
14.2 In addition to documentation required in the purchase order, vendor shall furnish
the following additional documentation upon receipt of a purchase order:
Page 26 of 38
a) Operation Manual - describing metering control system operation and

calibration procedures allowing field personnel to start-up, operate, and
safely shut down the MSC.
b) Installation Manual - complete procedure for reloading all the setup
(operating system, application software, communication interfaces, etc.) for
the metering control system.
c) Trouble Shooting Manual - containing trouble shooting diagrams that allow
field personnel to identify a fault by means of a simple step-by-step
procedure.
d) Recommended list of spare parts.
14.3 On-line electronic documentation shall be available in the MSC and shall
include graphics and text string search.
14.4 Source code for all the applications written for the MSC shall be provided.
14.5 All application software shall be well documented. Text based files for all
application software documentation shall be provided.
14.6 All application software coding and documentation shall be in English.

The code syntax and comments in the source code for all software including
application system software shall be in English. All error messages from the
MSC shall be provided in English.
15 Shipping Requirements
15.1 All necessary repairs, replacements, or modifications to hardware, firmware, and

software, shall be completed by the vendor prior to shipment.
15.2 The Vendor shall be responsible for ensuring the equipment is properly prepared
for shipment, including, but not limited to, the requirements specified hereafter.
15.2.1 General
a) All equipment and internals being shipped shall be braced and
temporary supports shall be provided, if required, to prevent
damage during shipment.
b) Equipment shall be marked with water-soluble materials that will
not attack or damage the equipment at either ambient or operating
temperatures. Marking materials shall be free of lead, sulfur, zinc,
cadmium, mercury, chlorine and all other halogens.
Page 27 of 38
c) Markings for export shall conform to the requirements specified

on the purchase order.
15.2.2 Electronic and Electrical Equipment

a) The Vendor shall determine if electronics and instruments are
susceptible to damage from shock, weather or extremes of
temperature during shipment. If required, such items shall be
removed after the functional test and shipped separately.
b) Electronic equipment shall be prepared and protected for shipment
in accordance with the manufacturer's recommendations. As a
minimum, the equipment shall be fitted with a vapor phase
inhibitor emitter (CORTEC VCI-101, VCI-105, VCI-110 or
equivalent).
c) Electrical boxes shall be fitted with vapor phase inhibitor emitters
(CORTEC VCI-101, VCI-105, VCI-110 or equivalent).
Revision Summary
22 June 2016 New Saudi Aramco Best Practice provides design guidelines and functional requirements for a
Metering Supervisory Computer (MSC) used in hydrocarbon gas Custody Metering Systems.
Page 28 of 38
Appendix
Appendix 1A Delivery Ticket Format for Ultrasonic Metering Systems
Appendix 1B Delivery Ticket Format for Orifice Metering System
Appendix 1C Delivery Ticket Format for Coriolis Metering System
Appendix 1D Comparison Report for Ultrasonic Meters
Page 29 of 38
Appendix 1A: Daily Delivery Ticket Format for Ultrasonic Metering Systems
Saudi Arabian Oil Company (Saudi Aramco)
Station: AAAAAAAAA Delivery Date: MM/DD/YYYY
Ticket No.: XXXX Flow Computer Tag. No.: AAA-XXX Print Date/Time: MM/DD/YYYY/HH:MM
SERVICE GAS: AAAAAAAAA
Meter Data:
Tag No. AAA-XXX Model No.: AAA-XXX Serial No.: XXXXXX
Manufacturer: AAAAAAAAA Meter K-Factor: XXXX Pulses/CF
Pipe ID (in): XX.XXX USM ID (in):XX.XXX
1. Meter Closing (Date/Time) MM/DD/YYYY/HH:MM:SS
2. Meter Opening (Date/Time) MM/DD/YYYY/HH:MM:SS
3. Idle Time XX.XXX Hrs
4. Net Delivery Time XX.XXX Hrs
5. Meter Closing Reading (mmscf) XXX.XXX
6. Meter Opening Reading (mmscf) XXX.XXX
7. Total Volume (mmscf) XXX.XXX
8. Meter Closing Reading (mmBtu) XXXXXX
9. Meter Opening Reading (mmBtu) XXXXXX
10. Total Heating Value (mmBtu) XXXXXX
11. Average Flow Rate (mmscfd) XXX.XXX
12. Average Temperature (F) XXX.X
13. Average Pressure (PSIG) XXX
14. Average Density (lb/scf) XX.XX
15. Average Meter Factor X.XXXX
16. Daily Average Gas Velocities:
Chord A XX.XX FT/S Chord C XX.XX FT/S Meter Average Gas Velocity XX.XX FT/S
Chord B XX.XX FT/S Chord D XX.XX FT/S
17. Gas Composition:
C1 XX.XX
C2 XX.XX
C3 XX.XX
i C4 XX.XX
n C4 XX.XX
i C5 XX.XX
n C5 XX.XX
C6+ XX.XX
N2 XX.XX
CO2 XX.XX
H2S XX.XX
H2O XX.XX
Average Heating Value XXXX BTU/SCF
Specific Gravity X.XXXX
Non-Negotiable, Non-Transferable
Saudi Arabian Oil Company
Checked for Saudi Aramco by: __________________________ Date: ____________
Page 30 of 38
Explanation of Delivery Ticket for Systems with Ultrasonic Flow Meters

A new ticket shall be initiated upon delivery or receipt; automatically at midnight of each day; or when manually
initiated by the operator.
STATION - Alpha-numeric value entered in the metering system computer during initialization
METER TICKET NUMBER – Computer generated number plus an alpha character if applicable. Numbers for
each meter are consecutively assigned by the flow computer beginning with 12:00 midnight of the 1st day of each
year
FLOW COMPUTER TAG. NO. – The tag number of the flow computer used to calculate the total volume and
energy for the batch
DELIVERY DATE - Date of the delivery
PRINT DATE/TIME - Date and time when ticket is printed
SERVICE GAS – Alpha-numeric value entered in the metering flow computer during initialization (Natural Gas
or Ethane)
METER DATA (METER TAG NO, MANUFACTURER, MODEL NO. AND SERIAL NO., PIPE INSIDE
DIAMETER, ULTRASONIC METER DIAMETER AND METER K-FACTOR) - Alpha-numeric values entered
in the metering system computer during initialization
1. METER CLOSING (DATE/TIME): Date and time delivery stops as determined by flow computer
2. METER OPENING (DATE/TIME): Date and time delivery starts as determined by flow computer
3. IDLE TIME: Calculated by the flow computer
4. NET DELIVERY TIME: Calculated by flow computer = Item 1-Item 2-Item 3
5. METER CLOSING READING: Total accumulated volume reading at the time the delivery stops (mmscf).
6. METER OPENING READING: Total accumulated volume reading at the time the delivery starts (mmscf).
7. TOTAL VOLUME: Item 5-Item 6 (mmscf)
8. METER CLOSING READING: Total accumulated heating value reading at the time delivery stops (mmBtu)
9. METER OPENING READING: Total accumulated heating value reading at the time the delivery starts
(mmBtu)
10. TOTAL HEATING VALUE: Item 8-Item 9
11. AVERAGE FLOW RATE: Item 7*24/Item 4
12. FLOW WEIGHTED AVERAGE TEMPERATURE: Calculated by flow computer
13. FLOW WEIGHTED AVERAGE PRESSURE: Calculated by flow computer
14. FLOW WEIGHTED AVERAGE DENSITY: Calculated by the flow computer
15. FLOW WEIGHTED AVERAGE METER FACTOR: Calculated by the flow computer
16. AVERAGE GAS VELOCITY – The average gas velocity calculated by the ultrasonic meter processor and the
gas velocity for the individual paths
17. GAS COMPOSITION - Either the daily average of the data received from an on-line gas chromatograph or
entered manually.
AVERAGE HEATING VALUE – Calculated by the flow computer based on the gas composition
SPECIFIC GRAVITY: Calculated by the flow computer based on the gas composition
Page 31 of 38
Appendix 1B: Delivery Ticket Format for Orifice Metering System

Station: AAAAAAAAA Delivery Date: MM/DD/YYYY
Ticket No.: XXXX Flow Computer Tag. No.: AAA-XXX Print Date/Time: MM/DD/YYYY/HH:MM
Meter Data:
Tag No. AAA-XXX Model No.: AAA-XXX Serial No.: XXXXXX
Manufacturer: AAAAAAAAA
Pipe ID (in): XX.XXX Orifice Plate Diameter (in):XX.XXX
1. Meter Closing (Date/Time) MM/DD/YYYY/HH:MM:SS

2. Meter Opening (Date/Time) MM/DD/YYYY/HH:MM:SS
3. Idle Time XX.XXX Hrs
4. Net Delivery Time XX.XXX Hrs
5. Meter Closing Reading (mmscf) XXX.XXX
6. Meter Opening Reading (mmscf) XXX.XXX
7. Total Volume (mmscf) XXX.XXX
8. Meter Closing Reading (mmscf) XXXXXX
9. Meter Opening Reading (mmBtu) XXXXXX
10. Total Heating Value (mmBtu) XXXXXX
11. Average Flow Rate (mmscfd) XXX.XXX
12. Average Differential Pressure (Inch WC) XX.XX
13. Average Temperature (F) XXX.X
14. Average Static Pressure (PSIG) XXX
15. Average Density (lb/scf) XX.XX
16. Gas Composition:
C1 XX.XX
C2 XX.XX
C3 XX.XX
i C4 XX.XX
n C4 XX.XX
i C5 XX.XX
n C5 XX.XX
C6+ XX.XX
N2 XX.XX
CO2 XX.XX
H2S XX.XX
H2O XX.XX
Average Heating Value XXXX BTU/SCF
Specific Gravity X.XXXX
NON-NEGOTIABLE, NON-TRANSFERABLE
SAUDI ARABIAN OIL COMPANY
CHECKED FOR SAUDI ARAMCO BY: __________________________ DATE: ____________
Page 32 of 38
Explanation of Delivery Ticket for Systems with Orifice Meters

A new ticket shall be initiated upon delivery or receipt of a new batch; automatically at 12:00 midnight of each
day; or when manually initiated by the operator.
STATION - Alpha-numeric value entered in the metering system computer during initialization.
METER TICKET NUMBER – Computer generated number plus an alpha character if applicable. Numbers for
each meter are consecutively assigned by the flow computer beginning with 12:00 midnight of the 1st day of each
year
PRINT DATE/TIME - Date and time when ticket is printed.
SERVICE GAS – Alpha-numeric value entered in the metering flow computer during initialization (Natural Gas
or Ethane)
METER DATA (METER TAG NO, MANUFACTURER, MODEL NO. AND SERIAL NO, PIPE INSIDE
DIAMETER AND ORIFICE PLATE DIAMETER) - Alpha-numeric values entered in the metering system
computer during initialization
5. METER CLOSING READING: Total accumulated volume reading at the time delivery/receipt stops (mmscf)
6. METER OPENING READING: Total accumulated volume reading at the time delivery/receipt starts (mmscf)
7. TOTAL VOLUME: Item 5-Item 6
8. METER CLOSING READING: Total accumulated Heating value reading at the time the delivery/receipt
stops (mmBtu)
9. METER OPENING READING: Total accumulated Heating value reading at the time the delivery/receipt
starts (mmBtu)
10. TOTAL HEATING VALUE: Item 8-Item 9
11. AVERAGE FLOW RATE: Item 7*24/Item 4
12. FLOW WEIGHTED AVERAGE DIFFERENTIAL PRESSURE: Calculated by flow computer
13. FLOW WEIGHTED AVERAGE DIFFERENTIAL PRESSURE: Calculated by flow computer
14. FLOW WEIGHTED AVERAGE TEMPERATURE: Calculated by flow computer
15. FLOW WEIGHTED AVERAGE STATIC PRESSURE: Calculated by flow computer
17. GAS COMPOSITION: Either data received from an on-line gas chromatograph at every scan or entered
manually
AVERAGE HEATING VALUE: Calculated by the flow computer based on the gas composition
SPECIFIC GRAVITY: Calculated by the flow computer based on the gas composition
Page 33 of 38
Appendix 1C – Daily Delivery Ticket Format for Coriolis Metering Systems

STATION: AAAAAAAAA DELIVERY DATE: MM/DD/YYYY

PRINT DATE/TIME: MM/DD/YYYY/HH:MM
FLOW COMPUTER TAG. NO.: AAA-XXX
METER DATA:
TAG NO. AAA-XXX MODEL NO.: AAA-XXX SERIAL NO.: XXXXXX
MANUFACTURER: AAAAAAAAA METER K-FACTOR: XXXXX.XX Pulses/lb
PIPE ID (IN): XX.XXX CORIOLIS ID (IN):XX.XXX
1. METER CLOSING (DATE/TIME) MM/DD/YYYY/HH:MM:SS

2. METER OPENING (DATE/TIME) MM/DD/YYYY/HH:MM:SS
3. IDLE TIME XX.XXX HRS
4. NET DELIVERY TIME XX.XXX HRS
5. METER CLOSING READING (lb) XXX.XXX
6. METER OPENING READING (lb) XXX.XXX
7. TOTAL MASS (lb) XXX.XXX
8. TOTAL VOLUME (mmscf) XXX.XXX
9. METER CLOSING READING (mmBtu) XXXXXX
10. METER OPENING READING (mmBtu) XXXXXX
11. TOTAL HEATING VALUE (mmBtu) XXXXXX
12. AVERAGE MASS FLOW RATE (lb/d) XXX.XX
13. AVERAGE STD DENSITY (lb/cf) XX.XX
14. AVERAGE K-FACTOR (Pulses/lb) XXXXX.XX
15. GAS COMPOSITION:
Mole %
C1 XX.XX
C2 XX.XX
C3 XX.XX
i-C4 XX.XX
n-C4 XX.XX
i-C5 XX.XX
n-C5 XX.XX
C6+ XX.XX
N2 XX.XX
CO2 XX.XX
Average Heating Value XXXX Btu/scf
Average Specific Gravity X.XXXX
Non-Negotiable, Non-Transferable
Saudi Arabian Oil Company
Page 34 of 38
Explanation of Delivery Ticket for Systems with Coriolis Flow Meters

A new ticket shall be initiated upon delivery or receipt; automatically at midnight of each day; or when
manually initiated by the operator.
STATION - Alpha-numeric value entered in the metering system computer during initialization
METER TICKET NUMBER – Computer generated number plus an alpha character if applicable.
Numbers for each meter are consecutively assigned by the flow computer beginning with 12:00
midnight of the 1st day of each year
FLOW COMPUTER TAG. NO. – This will be the tag number of the flow computer used to calculate
the total volume and energy for the receipt or delivery.
PRINT DATE/TIME - Date and time when ticket is printed
SERVICE GAS – Alpha-numeric value entered in the metering flow computer during initialization
(Natural Gas or Ethane)
METER DATA (METER TAG NO., MANUFACTURER, MODEL NO. AND SERIAL NO., PIPE
INSIDE DIAMETER, CORIOLIS METER DIAMETER AND METER K-FACTOR) - Alpha-numeric
values entered in the metering system computer during initialization
5. METER CLOSING READING: Total accumulated volume reading at the time the delivery stops (lb).
6. METER OPENING READING: Total accumulated volume reading at the time the delivery starts (lb).
7. TOTAL VOLUME: Item 5-Item 6 (lb)
8. TOTAL VOLUME: Calculated by flow computer (mmscf)
9. METER CLOSING READING: Total accumulated heating value reading at the time the delivery
stops (mmBtu)
10. METER OPENING READING: Total accumulated heating value reading at the time the delivery
starts (mmBtu)
11. TOTAL Heating value: Item 8-Item 9
12. AVERAGE MASS FLOW RATE: The average mass flow rate calculated by flow computer
14. FLOW WEIGHTED AVERAGE K-FACTOR: Calculated by the flow computer
15. AVERAGE GAS COMPOSITION - Either the average gas composition data received from an on-
line gas chromatograph during the ticket period or entered manually
AVERAGE HEATING VALUE – Calculated by the flow computer based on the gas composition
AVERAGE SPECIFIC GRAVITY: Calculated by the flow computer based on the gas composition
Page 35 of 38
Appendix 1D: Comparison Report for Ultrasonic Meters

Station: AAAAAAAAA Print Date/Time: MM/DD/YYYY/HH:MM
Report No.: XXXX Comparison Start Date/Time: MM/DD/YYYY/HH:MM
SERVICE GAS: AAAAAAAAA Comparison Finish Date/Time: MM/DD/YYYY/HH:MM
Flow Computer Tag. No.: AAA-XXX
Operational Meter Data: Check Meter Data:
Tag No. AAA-XXX Tag No. AAA-XXX

Model No.: AAA-XXX Model No.: AAA-XXX
Serial No.: XXXXXX Serial No.: XXXXXX
Manufacturer: AAAAAAAAA Manufacturer: AAAAAAAAA
Meter K-Factor: XXXX Pulse/CF Meter K-Factor: XXXX Pulse/CF
USM ID (in): X.XXX USM ID (in): XX.XXX
Check Meter Readings:

1. Actual Volume mmscf XXX 2. Chord A XX.XX FT/S
3. Average Temperature °F XX.X 4. Chord B XX.XX FT/S
5. Average Pressure Psig XXX 6. Chord C XX.XX FT/S
7. Average Density lb/scf X.XXX 8. Chord D XX.XX FT/S
9. Average MF X.XXXX
10. Average Gas Velocity m/s XX.X 11. Meter Velocity XX.XX FT/S
12. Flow Rate macfh XXX
13. Standard Volume mmscf XXX
Operational Meter Readings:

14. Actual Volume mmacf XXX 15. Chord A XX.XX FT/S
16. Average Temperature °F XX.X 17. Chord B XX.XX FT/S
18. Average Pressure Psig XXX 19. Chord C XX.XX FT/S
20. Average Density lb/scf X.XXX 21. Chord D XX.XX FT/S
22. Average MF X.XXXX
23. Average Gas Velocity m/s XX.X 24. Meter Velocity XX.XX FT/S
25. Flow Rate macfh XXX
26. Standard Volume mmscf XXX
27. Vol. Deviation % X.XX
28. Duration of Comparison HH:MM:SS XX:XX:XX
Historical Records:
Date: MM/DD/YY MM/DD/YY MM/DD/YY MM/DD/YY MM/DD/YY MM/DD/YY MM/DD/YY
Flow Rate X.XXXX X.XXXX X.XXXX X.XXXX X.XXXX X.XXXX X.XXXX
Dev. % X.XX X.XX X.XX X.XX X.XX X.XX X.XX
Page 36 of 38
Explanation of Comparison Report for Ultrasonic Meters

A new master meter proving report shall be generated upon completion of the verification of the
operational meter(s) against the check meter.
STATION - Alpha-numeric value entered in the metering system computer during initialization.
REPORT NUMBER – Computer generated number plus an alpha character if applicable. Numbers for
each meter are consecutively assigned by the MSC every time a comparison is initiated
PRINT DATE/TIME - Date and time when comparison report is printed.
SERVICE GAS – Alpha-numeric value entered in the metering flow computer during initialization
(Natural Gas or Ethane)
COMPARISON START AND FINISH DATE/TIME: The date & time when the comparison was
actually started and completed
OPERATIONAL & CHECK METERS DATA (METER TAG NO, MANUFACTURER, MODEL
NO. AND SERIAL NO, K FACTOR & UFM INSIDE DIAMETER) - Alpha-numeric values entered in
the metering system computer during initialization
CHECK & OPERATIONAL METER READINGS: The following data are determined during each
run of the proving process based on measurement by the check & operational meters and their
associated instruments
1 & 14. ACTUAL VOLUME – The volume at flowing conditions for operational and check meters
2,4,6,8,11 AVERAGE GAS VELOCITY – The average gas velocity calculated by the ultrasonic meter
processor
15,17,19, and the gas velocity for the individual paths
21 and 24
3 & 16. AVERAGE TEMPERATURE – Flow weighted average temperature for operational and
check meters
5 & 18. AVERAGE PRESSURE – Flow weighted average pressure for operational and check
meters
7 & 20. AVERAGE DENSITY – Flow weighted average density for operational and check meters
9. & 22. AVERAGE MF – This applies only to the check meter and should reflect the average MF
during the proving
10 & 23. AVERAGE GAS VELOCITY – The average gas velocity for operational and check meters
12 & 25. FLOW RATE – The gas flow rate in the operational and check meters
13 & 6. STANDARD VOLUME – The volume at reference conditions for operational and check
meters
27. VOLUME DEVIATION – (Line 16 – Line 8)/Line 8 x 100%
28. DURATION OF COMPARISON – Total difference between the comparison finish and
start times. The comparison of gas volumes of the operational and check meters shall start
after reasonable period of lineup defined the supervisory computer to establish check meter
conditions similar to the operational meter.
Page 37 of 38
HISTORICAL RECORDS – The Date, Flow Rate and Deviation % of the previous 10 comparisons.
The Historical Record is updated each time a comparison is completed on the basis that oldest record
will be deleted.
Page 38 of 38

Sabp y 856

Uploaded by

Copyright:

Available Formats

You might also like

Sabp y 856

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

Sabp y 856

Uploaded by

Copyright:

Available Formats

Best Practice

SABP-Y-856 22 June 2016

Previous Issue: New Next Planned Update: TBD

©Saudi Aramco 2016. All rights reserved

1 Scope and Purpose

2 Conflicts and Deviations

3.1 Saudi Aramco References

Saudi Aramco Engineering Procedures

Saudi Aramco Materials System Specification

Saudi Aramco Form and Data Sheet

Electronic Industries Association

EIA RS-422-A Electrical Characteristics of Balanced Voltage

API Manual of Petroleum Measurements Standards (MPMS)

4 Definitions and Abbreviations

Configurable: The capability to select and connect standard hardware modules

Commentary Note: A sub-paragraph that contains comments that are

Custody Transfer Measurement: A specialized form of measurement that

commodities. This includes measurement of hydrocarbon liquid or gas

Delivery: A custody transfer from a Pipeline to a customer.

Display: Set of operator computer schematics that generated by the MSC to

Field-Proven: Field proven is defined as successfully tested in operation at a

Flow Computer: An electronic device designed for calculating and totaling

Graphics: Set of operator computer schematics that graphically represent a

Meter Station: A facility that is primarily dedicated to the measurement of the

Metering Supervisory Computer (MSC): Computer that performs supervisory

Metering Control System (MCS): An integrated automation system that

Metering System: A complete assembly of equipment designed to measure

Receipt: A custody transfer to a customer.

Redundant Devices: Two identical devices that operate in an interchangeable

Ticket: A document specifying the quantity and quality of hydrocarbon

5.1 Environmental Conditions

The Metering Supervisory Computer (MSC) shall be installed indoors and

5.2 Electrical Requirements

Table 1 – Supply Voltages

System/Device Supply Voltage

Provision for grounding shall be available on the MSC.

5.3 Radiated Electromagnetic Susceptibility Test

A conformance certificate from an authorized agency stating the equipment is

5.4 Units of Measurement

Item Metric (SI) U.S. Customary (USC)

5.5 Vendor Responsibility

6 General Design Requirements

6.1 General MSC Requirements

6.2 MSC Communications

devices such as other metering supervisory computers, flow computers,

communication links to any other sub-system connected to it. Such data

6.3 MSC Application Software

h) The MSC shall be designed to meet the following performance requirements:

6.4 MSC Application Configuration

 On-line and/or off-line database generation

6.5 MSC Displays

e) It shall be possible to move between related displays and graphics of

 System Overview (all main components)

 Alarms, path failures indicators, etc.

These parameters shall be displayed, trended and archived in the MSC

7 Operational Design Requirements

7.1.4 The MSC shall at a minimum provide a GUI for displaying up to

7.2 Metering Control

CHECKED FOR SAUDI ARAMCO BY: ______________ DATE:

Checked for Saudi Aramco by: ______________ Date: