Materials System Specification

23-SAMSS-071 3 December 2014

Data Validation and Reconciliation Software
Document Responsibility: Process Optimization Solutions 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.......................................................... 7
6 Functionalities............................................. 10
7 Management/Administration........................ 20
8 Reliability and Performance........................ 20
9 Searching.................................................... 20
10 Security....................................................... 20
11 Inspection and Testing................................ 21
12 Documentation............................................ 22

Appendices......................................................... 23

Previous Issue: 7 August 2012 Next Planned Update: 7 August 2017

Revised paragraphs are indicated in the right margin Page 1 of 30
Primary contact: Alsuezi, Amein Muhammad on 966-3- 8801587

Copyright©Saudi Aramco 2014. All rights reserved.

Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

1 Scope

1.1 This specification defines the functional and system requirements of the Data
Validation and Reconciliation Software (DVRS) to be deployed in all Saudi
Aramco Facilities including but not limited to GOSP, gas Plants, Refineries and
Petrochemical. The specification shall identify the specific requirements as per
the following categories:

1.1.1 [MUST] is the requirement that define the mandatory requirements to

be provided for all bid packages for capital projects for new facilities
or automation initiatives for existing facilities.

1.1.2 [WILL] is the requirements that define the preferential requirements to

be provided for all bid packages for capital projects for new facilities
or automation initiatives for existing facilities requirements.

1.1.3 [MAY] is the requirements that define the evolving DVRS technology
road map to be provided for the future offering of DVRS Vendor(s) as
well as the updates and upgrades of their official current releases.

1.2 This specification covers the requirements of Unit Reconciliation and Plant
Wide Reconciliation with emphasis on the following:

1.2.1 Salient functionalities of the solution requirements that are represented

under the Functionalities section (section 6) including: data filtering
and measurements bounds, gross errors detection and elimination,
mass and heat balances, thermodynamic libraries, model and GUI
configuration, solver, KPIs generation and calculation engine,
reporting, unit reconciliation, and plant-wide reconciliation whereas
each major category of other system requirements is represented under
separate sections as shown in the table of contents.

1.2.2 Unit reconciliation and plant-wide reconciliation data, system, and

platform integration with other essential Decision Support System
(DSS) applications such as long term data archiving, lab management,
inventory management, oil movement, etc. in addition to the Standard
Interfaces requirements.

1.2.3 Unit reconciliation and plant-wide reconciliation preferential

integration with other essential modeling applications such as APC,
dynamic modeling, optimization and energy KPI's, etc.

1.3 This specification utilizes the Yourdon-DeMarco structured analysis as part of

the ISA-95.05 requirements to define the DVRS model functionalities.
Therefore, it provides the DVRS data models that cover DVRS main and sub-

Page 2 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

functionalities and defines the data flow among them (see the document's
appendixes)

2 Conflicts and Deviations

2.1 Any conflicts between this specification and other applicable Saudi Aramco
Materials Systems Specifications (SAMSS), Saudi Aramco Engineering
Standards (SAES), Saudi Aramco Standard Drawings (SASD), or industry
standards, codes, and forms shall be resolved in writing by the Company or
Buyer Representative through the Manager, Process and Control Systems
Department, Saudi Aramco, Dhahran.

2.2 Direct all requests to deviate from this specification in writing to the Company
or Buyer Representative, who shall follow internal Company Engineering
Procedure SAEP-302 and forward such requests to the Manager, Process and
Control Systems Department, Saudi Aramco, Dhahran.

3 References

Specific sections of the following documents are referenced within the body of the
document. Material or equipment supplied to this specification, shall comply with the
referenced sections of the latest edition of these specifications. Where specific sections
are not referenced, the system shall comply with the entire referenced document.

3.1 Saudi Aramco Documents

Saudi Aramco Engineering Procedures

SAEP-302 Instructions for Obtaining a Waiver of a Mandatory
Saudi Aramco Engineering Requirement

3.2 Industry Codes and Standards

American Society for Testing and Materials

ASTM D86 Standard Test Method for Distillation of Petroleum
Products

OPC Foundation
OPC-DA & OPC-HDA Specifications of OPC Data Access and Historian
Data Access -for the interfaces between a
historian and any client/server OPC
combatable software system

Page 3 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

The Instrumentation, Systems, and Automation Society (ISA)

ISA-95.05 International Standard for the Integration of
Enterprise and Control Systems: B2M
Transactions (Part 05 of ISA-95: “Business to
Manufacturing Transactions”)

4 Definitions

This section contains definitions for acronyms, abbreviations, words, and terms as they
are used in this document. For definitions not listed, the latest issue of the
“Comprehensive Dictionary of Measurement and Control”, International Society for
Measurement and Control, shall apply.

4.1 Acronyms and Abbreviations

APC Advanced Process Control
ASTM American Standards for Testing Materials
ATG Automated Tank Gauging
API American Petroleum Institute
API Application Programming Interface
CDU Crude Distillation Unit
COTS Commercial-off-the-Shelf
DA Data Access
DBMS Database Management System
DSS Decision Support System
DCS Distributed Control System
DVR Data Validation and Reconciliation
FAT Factory Acceptance Test
FSD Functional Specification Document
GC Gas Chromatography (an analysis performed in the laboratory)
GOSP Gas-Oil Separation Plant
GUI Graphical User Interface
HDA Historical Data Access
ISS Instrument Specifications Sheet
LAN Local Area Network

Page 4 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

LC Liquid Chromatography (an analysis performed in the laboratory)

LIMS Laboratory Information Management System
ODBC Open Database Connectivity
OLE DB Object Linking and Embedding for Database
OMS Oil Movement System
OLE Object Linking and Embedding
OPC OLE for (or Open) Process Control
OR&GPI Oil Refining and Gas Processing Industry
P&CSD Process and Control Systems Department
PC Personal Computer
PI-UDS Plant Information Universal Data Server (from OSIsoft Inc.)
PMMS Products Movement Management System (in-house Oil
Movement Application)
RDBMS Relational Database Management System
SDK Software Development Kit
SQL Structure Query Language
SQP Sequential Quadratic Programming
SQP-IP Sequential Quadratic Programming with Interior Point method
TBP True Boiling Point
WAN Wide Area Network

4.2 Words and Terms

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.

Configuration: The physical installation of hardware modules to satisfy system

requirements; or the selection of software options to satisfy system requirements.

Data Validation and Reconciliation (DVR): The process of validating,

adjusting and reconciling the process measurements to obtain more accurate
estimates those are consistent with material, energy, and other balances. Its main
objective is to provide rectified data with higher quality that is utilized to improve
results and decisions once exploited by other applications and analysis tools.

Page 5 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Data Validation and Reconciliation Software (DVRS): The computer

application that performs all functional requirements for data validation and
reconciliation.

Decision Support System (DSS): A comprehensive solution that is

implemented at an operating facility in order to systemize and improve the
decision making process. The solution consists of main applications
components that include but not limited to data historian, data validation and
reconciliation, expert and automated advisories, lab management, planning and
scheduling, safety and incidents tracking, asset management, root cause and
fault identification, reliability analysis, operational and performance KPI's, and
oil movement systems.

End User PC: The personal computer used by an operator/user to perform the
functions required to monitor and control his assigned tasks.

Field Proven: A system shall be considered to be field proven when it has been
installed, commissioned, and operational in a customer facility for a period of
six months or longer (excluding beta test periods). It shall be possible for Saudi
Aramco to verify the field proven status.

Gross (Systematic and Non-Random) Error: is the error generated from non-
random events such as malefactions, not adequately compensated meters,
incorrect calibration of instruments or poor sampling and it is larger than the
random error. Types of such error include: process related errors (i.e., leaks,
emissions, evaporation), measurement related errors (i.e., malfunctioning
instruments, bias errors, physical property changes, errors in meter factor
calculations), or modeling related errors (i.e., wrong assumptions).

Interior Point (IP) method: A class of algorithms utilized to solve linear and
nonlinear convex optimization problems. The basic element of the method
consists of a self-concordant barrier function used to encode the convex set. It
reaches the optimal peak by traversing the interior of the feasible region.

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.

Point/measurement: A process variable derived from an input or resulted in a

process calculation.

Random Error: is the uncertainty error which arises by chance and will
diminish when the greater the number of readings is made. Random
measurement errors are small errors due to the normal fluctuation of the process

Page 6 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

and/or the random variation inherent in any instrument operation. The errors are
usually considered independent and normally distributed with zero mean.
Fluctuation and irreproducibility of measurements could be the result of power
supply fluctuations, network transmission and signal, conversion noise, analog
input filtering, and/or changes in ambient conditions.

Reliability: The capability of a system or component to perform its intended

function for a specified period of time.

Reconciled Measurement Penalty: is a numerical value that represents the

amount of correction applied to a specific measurement and the contribution of
this correction on the overall optimization function of the problem. It is
calculated by talking the second power of the total amount of the difference
between the raw and reconciled values divided by the accuracy (level of
confidence) of that measurement.

Sequential quadratic programming (SQP): is a generalization algorithm of

Newton's method for unconstrained optimization in that it finds a step away
from the current point by minimizing a quadratic model of the problem. In its
purest form, the SQP algorithm replaces the objective function with its quadratic
approximation.

Sequential quadratic programming with Interior Point (SQP-IP): is a novel

approach that utilizes the IP method within SQP for the data validation and
reconciliation problem solver. The solver with SQP-IP is proven to provide
optimum solutions for some NLP and general large scale problems that SQP
alone can't solve.

Tag: A collection of attributes that specify a control loop, a process variable, a

measured input, a calculated value, or some combination of these with all
associated control and output algorithms. Each tag is unique.

True Boiling Point: the temperature point at which the liquid is transformed to
gas under the standard conditions of pressure and density could be suppressed.

5 General

5.1 Use of Standard Products

5.1.1 The DVRS MUST be ready to be installed and run on standard

hardware, standard vendor software –if needed-, and be configured to
meet the stated requirements of hardware and software by Saudi
Aramco.

5.1.2 A vendor's software MUST be commercial-off-the-shelf (COTS) not

Page 7 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

requiring any modifications to meet any of Saudi Aramco's

requirements.

5.1.3 The DVRS WILL use standard interfaces/adaptors in order to acquire

plant row data and sending it back as reconciled data.

5.1.4 The DVRS MUST have an acceptable standard data repository.

5.1.5 The DVRS application WILL allow access to its inbuilt data repository
through standard interfaces like Open Database Connectivity (ODBC),
Object Linking and Embedding for Databases (OLE DB), and/or Data
Access Objects (DAO).

5.1.6 All software components provided by the vendor as part of the system
WILL be commercially available and supported at the time of contract
or purchase order, whichever is the later.

5.1.7 The DVRS MUST have the ability to operate in a tiered Client/Server
mode.

5.1.8 The DVRS MUST be field proven and has a minimum of three
installations at three different OR&GPI customers.

5.2 Software Revision

Interfaces/adaptors to the system, databases, and any system internal

components WILL not require any additional modifications in order for the
application to run. It is acceptable if the interface/adaptor is provided with the
new release(s) by the vendor.

5.3 System Support

The DVRS Vendor MUST provide Saudi Aramco with an efficient hotline
support oriented not only in solving software problems/bugs but, also in helping
the system administrator(s) to correctly troubleshoot and configure the models
of their processes in order for the model to run, converge, and give the expected
results.

5.4 Standard Interfaces

5.4.1 The DVRS MUST provide Bi-directional interface with OSIsoft's real-
time data historian: PI-UDS version 3.3 and later.

5.4.2 The DVRS MUST provide unidirectional interface to automate the

capture of raw (non-reconciled) data from relational databases, i.e., MS
SQL and Oracle RDBMS and write back the reconciled results.

Page 8 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

5.4.3 The DVRS WILL provide unidirectional interface that complies with
the OPC-DA & OPC-HDA specifications.

5.5 System, Data and Platform Integration

5.5.1 The DVRS MUST run on Windows platform.

5.5.2 The DVRS MUST support distributed architecture (product

components can be installed on single/different machines).

5.5.3 The DVRS WILL be accessible from any location within the Saudi
Aramco network.

5.5.4 The DVRS MUST provide seamless integration with data sources such
as DCS, real-time data historians, oil movement systems, etc.

5.5.5 The DVRS WILL be able to simultaneously collect raw data and
retrieve multiple variables from different and more than one source
(i.e., data historian, lab data, relational data bases, tables, manual entry,
ASCII files -, and/or COM & DCOM.

5.5.6 The DVRS WILL support different data types that include but not
limited to (Real, Text, Tag, Tag IDs, Tag attributes, integer, float,
double, strings, long, picture, byte, Boolean).

5.5.7 The DVRS MUST be able to retrieve datasets and operational data
based on specific date and time instances and intervals.

5.5.8 The DVRS WILL provide API and/or SDK in order to extract data
from DVRS to other systems and vice versa.

5.5.9 The DVRS MUST be developed employing prevailing Microsoft

technologies and the Intel platform, as these are predominantly used
within Saudi Aramco.

5.5.10 The Vendor MUST provide Saudi Aramco with an illustration of the
recommended systems architecture, depicting the tiers, the hardware
platform, and software (operating system, web server, 3rd party
applications and DVRS related applications).

5.5.11 The Vendor WILL provide an explanation of his data repository

architecture and the underlying technology, highlighting the methods
available to query the data repository from within other standard
reporting applications, like Excel, etc.

Page 9 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

6 Functionalities

6.1 Data Validation

6.1.1 Measurements Bounds

6.1.1.1 The DVRS MUST allow user defined rules to handle

measurement bounds, i.e., avoiding the calculation of
negative flows or unrealistic readings.

6.1.1.2 The DVRS MUST provide a data filtering tool/procedure to

pre-process the raw measurements, i.e., measurements out of
range in order to ensure best convergence results.

6.1.1.3 The DVRS filtering tool/procedure MUST be able to

substitute the filtered measurements either: by a default value,
the minimal, the maximal value of the measurement interval,
last good value, average of the boundaries, average of a
specific number of readings or interval, higher bound, lower
bound, any specific user defined values, or by deactivating
the measurement.

6.1.1.4 There WILL be at least one level of bounds (upper and lower)
for each provided measurement in order to be considered for
filtering.

6.1.2 Measurements Accuracies

6.1.2.1 The DVRS filtering tool/procedure WILL have the capability

to adapt the accuracy of the filtered measurement based on
default procedures or on user definition.

6.1.2.2 The DVRS MUST provide the ability to

manually/automatically assign confidence factors to
measurements which contributes to its reconciled values.

6.1.2.3 The DVRS WILL provide capabilities to assign default

confidence factors of measurements based on their types if
there is no enough information to assign a certain factors.

6.1.3 Flow Compensation

The DVRS MUST be able to calculate the compensated readings of

flows provided that needed information to implement the
compensation is available -unless compensated flows are provided
directly from one or more data source.

Page 10 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

6.1.4 Data Conditioning

6.1.4.1 The combination of bounds and accuracy WILL drive the

reconciled data and its new accuracy factors.

6.1.4.2 The DVRS WILL be capable of calculating the reconciled

values based on input measurements (Flow, Pressure,
Temperature, Density, etc.) assuming that they are normally
distributed.

6.1.5 Event Analysis

6.1.5.1 The DVRS MUST be capable of detecting steady state

operations of the process unit or plant being reconciled.

6.1.5.2 The DVRS WILL be easily (preferably automatically)

reconfigurable according to process modes and operational
state.

6.1.5.3 The DDVR component MAY be able to adjust the model

according to the state/mode of the operation automatically.

6.1.5.4 The DDVR component MAY allow users standard

procedures to implement the data and rules of
different/possible operating conditions.

6.2 Model Configuration

6.2.1 Unit/Plant Model

6.2.1.1 General

6.2.1.1.1 The DVRS application MUST have an acceptable

object oriented graphical user interface (GUI) with
a built-in library of objects required to model
units, storages and external facilities in the
OR&GPI.

6.2.1.1.2 The DVRS MUST be able to integrate unit

reconciliation model(s) and their results with the
plant-wide model(s).

6.2.1.1.3 The DVRS WILL provide modeling tools and

rules to identify routing and dispositions of
process streams between the plants and the
different types of tanks, number and type of crude

Page 11 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

switches, and different model layers based on

changing plant physical configuration and
operation modes.

6.2.1.1.4 The DVRS GUI WILL allow for assigning data

(reconciled readings, KPIs, confidence factors and
accuracies, un-reconciled real-time and historical
data, and any other model related information) on
the model GUI.

6.2.1.1.5 The DVRS WILL allow for applying API standard

volume calculations and converting volumetric
flow to mass flow and vice versa.

6.2.1.2 Unit Reconciliation Model

6.2.1.2.1 The DVRS MUST allow for modeling and thus

reconciling any general or specific unit related
envelope of processes where the minimum
redundancy is achieved.

6.2.1.2.2 The DVRS MUST help to identify the operation

logic and perform unit production balancing based
on open and closed transactions and the unit input
and output with regard to tanks or other
units/steams.

6.2.1.2.3 The DVRS WILL provide any possible unit

related KPIs based on the reconciled data.

6.2.1.2.4 The possible units to be modeled by DVRS WILL

include but not limited to: CDU, Utilities, H2,
Vacuum Distillation Unit, Fluid Catalytic
Cracking, Hydrocracker, Crude Stabilization
Facility, Gas Treating Unit, Gas Condensation
Unit, Natural Gas Liquid, Platformer, or/and
Viscosity Breaker (Vis-Breaker).

6.2.1.3 Plant-Wide Reconciliation Model

6.2.1.3.1 The DVRS plant wide model MUST provide

means for selecting the mass balance loop based
on crude switches and operation scenarios, and
identifying open and closed transactions (when

Page 12 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

there is a change in level status of tanks or

operation of pumps).

6.2.1.3.2 The DVRS plant wide model MUST balance the

input, output and inventories of the receipts,
charge, processing, intermediate products, and
final products.

6.2.1.3.3 The DVRS plant wide model WILL provide

allocation technique(s) to perform the mass
balancing based on the feed, charge, and products
specifics.

6.2.1.3.4 The DVRS MUST be capable of manually

allocating tanks when a service change occurs.

6.2.2 Thermodynamics Libraries

6.2.2.1 The DVRS MUST have an intrinsic collective library of

thermodynamic methods and properties of pure compounds
as well as pseudo-compounds for crude assays –
producing/using True Boiling Points (TBP)-, etc., and utilizes
the techniques for vapor-liquid equilibrium to represent
relevant thermodynamic aspects of the processes in the
OR&GPI.

6.2.2.2 The DVRS thermodynamic libraries MUST allow for

defining all process data including but not limited to
temperatures, pressure, LC & GC, Density, ASTM D86, TBP,
etc.).

6.2.3 Mass and Heat Balances

6.2.3.1 The DVRS MUST provide the capability to combine mass,

heat, and component balances as well as the thermodynamic
equilibrium information into one single optimization
problem.

6.2.3.2 The DVRS MUST be able to perform major balances of

mass, volume, heat (energy), and component, with
thermodynamic equilibrium on separate and simultaneous
runs -that will create redundancies and increase the accuracy
of reconciled measurements.

6.2.3.3 The DVRS WILL provide estimation with accuracy for

missing compositions by calculating the average mass weight

Page 13 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

based on component mass balance and the thermodynamic

libraries implementation.

6.2.3.4 The DVRS MUST identify/estimate values for unmeasured

process variables and values of missing instruments -if
existing redundancies allow- and store them.

6.2.4 Pressure and Molecular Balances

The DVRS MUST provide methods that are able to utilize the
techniques for vapor-liquid equilibrium and calculate pressure and
molecular balances.

6.2.5 Redundancy Level

6.2.5.1 The DVRS MUST supply the functionalities required to

reconcile process data by providing additional redundancies
within the developed plant models to overcome the lack or
inaccuracy in some measurements.

6.2.5.2 The DVRS WILL provide the user with the redundancy level
while considering the level of the redundancy as a factor in
determining the healthiness and level of trust on the results of
the model.

6.2.5.3 The DVRS WILL utilize each available piece of information

to support the level of redundancy for the DVRS model.

6.2.5.4 The DVRS WILL allow for a tool/method to initially identify

the minimum required level of redundancy for a specific
model envelope to allow for model convergence.

6.2.6 Chemical Reactions

The DVRS MUST be capable of modeling reactions on the basis of

atomic balances and/or user defined equations.

6.2.7 ASTM D86

The DVRS MUST handle the measurement validation of systems with

multi components by transferring the ASTM D86 distillation curves to
True Boiling Point Curves.

6.2.8 Model Rules and Conditions

The DVRS MUST provide the capabilities to set rules and implement

Page 14 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

general and/or special conditions, i.e., setting a pump off if the flow is
below certain limit or activating some bounds or streams based on
some readings/conditions.

6.3 Model Solver

6.3.1 SQP/SQP-IP Solver

6.3.1.1 The DVRS MUST provide a solver capable of utilizing the

sequential quadratic programming algorithm or any proven
state-of-the-art method to solve the reconciliation problem.

6.3.1.2 The DVRS WILL provide a solver capable of solving

rigorous modeling using simultaneous mass and heat balances
and capable of converging large models in time intervals that
are less than ten minutes per run.

6.3.1.3 The DRS Solver WILL have the capability to allow user
defined rules to handle measurement bounds.

6.3.1.4 The DVRS solver WILL allow for simultaneous mass and
volumetric balance.

6.3.1.5 The DVRS Solver WILL have the capability to resolve

problems with inequality constraints.

6.3.1.6 The DVRS solver WILL employ advanced methods, i.e.,

SQP-IP to solve the reconciliation problem.

6.3.2 Model Solution

6.3.2.1 The DVRS model MUST allow terminating the application

run if the convergence is not achieved within a configurable
number of iterations.

6.3.2.2 The DVRS model MUST utilize all model configurations/

information, solver, thermodynamics and equations, gross error
detection and elimination, bounds, redundancies to reconcile
the model and produce validated and reconciled data.

6.3.3 Error Detection

6.3.3.1 The DVRS MUST provide a proven technique to enable

detecting the presence of gross errors in the sets of
measurements.

Page 15 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

6.3.3.2 The DVRS WILL provide improved solver technology in

terms of gross error detection and elimination, convergence
and speed.

6.3.3.3 The statistical confidence level of gross error technique

WILL be configurable and WILL be possible to be set at 95%
by default.

6.3.3.4 The gross error technique WILL provide a numerical

measurement to represent the confidence (certainty) level of
the reconciled values and the possibility of gross error
existence.

6.3.3.5 The DVRS WILL flag all measurements that are outside a
confidence interval corresponding to a defined level of
confidence.

6.3.3.6 The DVRS WILL utilize a standard statistical method to

distribute random errors over measurements depending on the
identified confidence factors.

6.3.4 Error Elimination

6.3.4.1 The DVRS SHALL allow the option of enabling and

disabling the gross error elimination.

6.3.4.2 The DVRS SHALL provide the capability to remove

measurements with suspected gross errors by the following:

6.3.4.2.1 Giving the priority to remove measurements with

larger magnitude of corrections.

6.3.4.2.2 Giving the priority to remove measurements with

highest impact on the total sum of reconciliation
run penalty.

6.3.5 Solution with Solver Boundaries

6.3.5.1 The DVRS WILL provide a proven technique –depending on

the used solver- to implement solver bounds (manually or by
default) for each measurement to make sure solver will
provide acceptable and realistic reconciled measurements.

6.3.5.2 The DVRS WILL continuously check the model result

against the solver boundaries and update the solver
simultaneously.

Page 16 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

6.3.6 KPI's and Un-measured Values

6.3.6.1 The DVRS MUST provide capabilities to estimate KPIs that

are related but not limited to loss identification, oil
accounting, performance monitoring, etc.

6.3.6.2 The DVRS MUST provide estimations of the unmeasured

and/or corrupted with gross error readings based on the
redundancies available at the DVRS model.

6.3.6.3 The DVRS MUST allow for user-defined KPIs development

that include but not limited to:

6.3.6.3.1 Loss Management (LM): LM KPIs shall calculate

on-line the amount of losses on unit or plant level.

6.3.6.3.2 Reliability Index [reconciled / theoretical yield

variable]

6.3.6.3.3 Performance based KPIs including but not limited

to:
a) Fouling of heat exchangers.
b) Efficiency of heaters, Compressors, pumps,
tubes, fractionation.
c) Fractionation overlaps.

6.3.6.3.4 Performance Index (for more valued products) [1-

reconciled losses]/ [1- un-reconciled losses]

6.3.6.4 The DVRS MUST provide a calculation engine to cover any

required calculations and KPI generation related to the model.

6.3.6.5 The DVRS calculation engine WILL utilize user friendly

tools, i.e., simple GUI and basic programming language to
implement calculations, and WILL not require any advanced
programming experience.

6.4 Sensitivity Analysis

6.4.1 Measurements Analysis

6.4.1.1 The DVRS WILL produce reconciled measurements with

their validated accuracies/precision.

Page 17 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

6.4.1.2 The DVRS WILL provide readings to help user identify the
major measurements that contribute to the validated accuracy
as well as the measurements that are improved by the DVRS
solution.

6.4.1.3 The DVRS WILL quantify the contribution of the reconciled

measurements to the overall penalty of the reconciliation
problem.

6.4.2 KPI's Analysis

The DVRS WILL provide any KPIs calculated based on the reconciled
measurements with the error contributed/resulted from each input data
used to calculate that KPI. The error propagation needs to be clear and
easy to be identified.

6.4.3 Measurements Covariance Analysis

6.4.3.1 The DVRS WILL provide a tool to calculate the interactions

between different measurements.

6.4.3.2 The DVRS WILL allow the user the level of dependency of
different measurements.

6.4.4 KPI's Covariance Analysis

6.4.4.1 The DVRS WILL provide a tool to calculate the interactions

between KPIs and/or measurements.

6.4.4.2 The DVRS WILL provide computed accuracies of each KPI

–calculated based on the reconciled measurements- and
provide covariance calculations for all variables affecting that
KPI.

6.5 Reporting Results

6.5.1 Reconciliation Quality

The DVRS WILL provide a measure to estimate the quality of the

reconciled model based on the used assumptions, level of
redundancies, and conditions of the available measurements.

6.5.2 Reconciled Measurements with accuracy

The DVRS MUST provide a tool to report the reconciled

measurements with their reconciled accuracies.

Page 18 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

6.5.3 Estimated Measurements with accuracy

The DVRS MUST provide a tool to report the estimated readings

resulted from the reconciliation model with their computed accuracies.

6.5.4 KPI's with accuracy

The DVRS MUST provide a tool to report the KPIs resulted from the
reconciliation model with their computed accuracies.

6.5.5 Flagged and suspected Measurements

The DVRS WILL be able to flag and identify suspected and out-of-
range readings.

6.5.6 Customized Reports

6.5.6.1 The DVRS MUST have a proprietary or a standard report

building tool (i.e., Crystal reports or MS Excel Add-in).

6.5.6.2 The DVRS WILL allow users to print reports and/or export
them to excel, word, PDF in both Native and Raw Data
Format.

6.5.6.3 The DVRS WILL allow users to generate integrated reporting

including but not limited to the following:
a) Yield and Loss Accounting, i.e., charge/feed balancing.
b) Environmental compliance of API drainage, tank
vaporizations, % of Unaccountable losses, and % of
Accountable losses.
c) Performance Monitoring.
d) Model and Data Analysis.

6.5.6.4 The DVRS WILL provide the capability to sort

measurements by decreasing penalty allowing for easy
identification of where the biggest corrections have been
applied.

6.5.6.5 The DVRS WILL allow flagging different alarming colors for
significant unaccountable losses, faulty, or/and suspected
readings and reconciled measurements.

Page 19 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

7 Management/Administration

7.1 The DVRS MUST include a scheduling system allowing automatic sequencing
of DVRS tasks (data retrieval, filtering, data reconciliation, reporting, and data
storage). A manual mode MUST be enabled to test the correct operation of the
system.

7.2 The DVRS MUST provide an administration tool to administrate models, online
scheduling, system security, tags, interfaces, databases, and users of the system.

7.3 The DVRS MUST allow both storing the results on its own databases and
exporting them to external systems databases, i.e., PI-UDS.

7.4 The DVRS MUST have backup and recovery features and procedures.

7.5 The DVRS WILL be able to track model changes by saving different versions of
the model with each modification performed.

8 Reliability and Performance

The DVRS MUST have capability to handle model runs to generate and populate
results every hour at minimum.

9 Searching

The DVRS WILL have capability to search and sort the input/output data of
tags/measurements by name, description, value, or penalty.

10 Security

10.1 The DVRS WILL have capability to integrate with Windows Active Directory
and Sun Directory Server (LDAP).

10.2 The DVRS WILL have the capability to be integrated with other security rules
of other products such as Microsoft SQL and Oracle DBMS.

10.3 The DVRS MUST be compatible with anti-virus software.

10.4 The DVRS MUST have its own security rules, and central management of
model content and configuration.

10.5 The DVRS MUST use fixed TCP-IP ports for its client-server and interfacing
communications.

Page 20 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

11 Inspection and Testing

11.1 Standard Software

Any acquired license of the software MUST be tested and verified. Numbers of
licensed tags, users, and other software components shall be matched with the
software license request. Testing shall be in accordance with the standard test
procedures for software diagnostics.

11.2 Integrated Systems

Factory Acceptance Test (FAT) and Site Acceptance Test (SAT) criteria MUST
meet the Saudi Aramco established criteria below.
A) Factory Acceptance Testing (FAT)
1) A detail Model Configuration report to include the following:
a) Presence or lack of Redundancies listed by Streams for each
area.
b) Explanation of each customized object used.
c) Listing of measurement defaults, bounds and filters employed.
d) Listing of Key Performance Indices (KPIs) provided.
2) Model verification with acceptable convergence defined as:

Acceptable number of iterations and data quality as defined by the

software using 10 suggested data sets (daily runs) covering the
following scenarios:
a) Different Operation Modes [Naphtha, Kero, etc.].
b) Turnaround and Inspection [Plant(s) Shutdown, Reduced
throughput, etc.].
c) Emergency Situations.
3) A detail Model Exception report to include the following:
a) Explanation of any convergence issue(s).
b) Listing of Gross Error(s) eliminated in order of impact.
B) Site Acceptance Test (SAT)
1) Approval shall be contingent upon achieving 80% convergence in 30
contiguous on-line daily runs in the case of plant-wide material

Page 21 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

balance model. And 720 contiguous hourly runs in the case of mass
and energy balance model.
2) A Site Acceptance Test (SAT) document that provide updates on the
following FAT reports:
a) Model Configuration.
b) Model Exception.

12 Documentation

12.1 The DVRS MUST be well equipped with a comprehensive set of application
manuals. The DVRS MUST provide online and context sensitive help within
the application suite itself.

12.2 The following documentation MUST be supplied by the vendor as part of the
project deliverables:

12.2.1 Model Development and Execution Plan that reflects the project FSD
by Saudi Aramco Project team.

12.2.2 Preliminary Acceptance Test Plan.

12.2.3 Factory Acceptance Test Plan.

12.2.4 Site Acceptance Test Plan.

12.2.5 Installation Instructions.

12.2.6 Operating Manuals (user, advanced user, and administrator).

12.2.7 Model Manuals that include special components, inputs, outputs, and
assumptions of the deployed model.

12.2.8 Post Audit and Benefit Identification Report.

12.3 All documentation MUST be in English using the US dictionary.

12.4 Word processor or text files of all application software documentation MUST be
provided on removable electronic media or attached to an official email to the
Saudi Aramco project leader.

Revision Summary
7 August 2012 Revised the “Next Planned Update.” Reaffirmed the content of the document, and reissued
with editorial changes.
3 December 2014 Editorial revision to transfer responsibility from Process Control to Process Optimization
Solutions Stds. Committee.

Page 22 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendices

Appendix I – DVRS External Description Diagram

DVRS External Description Diagram

Users / Reports

DVR Application
Applications ERP / SAP
Functions

Data Sources

Page 23 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendix II – DVRS Functional Data Model

DVRS Functional Data Model

APC &
Real-Time Maintenance
Plant Energy Optimization Yield
Management Accounting

Reliability Optimization
Hydrocarbon
Optimum
Models Management
PM Recon.
EPIs
C F & Life Production
Cycle
Data Validation &
Reconciliation
Application
User Configuration
Engineer
Reconciled
Parameters
Values
Aggregated Data

Data
Historian

LIMS DCS OMS

Page 24 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendix III – DVRS Functional Architecture (General)

DVRS Functional Architecture: Functionalities (6.0)

Administrator
Se

Configure
pa t ents
,
re ra uipm
gu m
s, eq stream
s P&IDs
nfi ete nit
Co s r U rs, &
Model m ete
Model Solver Validated model
Configuration
(6.3.0) Eliminate/activate readings/rules
(6.2.0)
Re

Te
s

co

m
lyse

p,
Val
nc

Pr
ile
ana

ida

es
dm

s
ted

ur
e

od

e,
erat

Ac

dat
el

flo
tiv ate

w,
Gen

a
if n
at- atio bo

lev
Wh figur un
ds/

el,
con rul
es Data

De
Sensitivity

ns
re
gu Validation

it
Analysis nfi

y,
co rules T, P

D-
(6.4.0) Re
- ds & (6.1.0) ,

86
F, D
boun ing ,
Set leve
Acc ad l, D
re - 86
Cov uracy ge
Analyze

aria an
nce fr Data Sources (PI
to
Ou KPI’
, D’, leve
l’, D-86’, -OMS-LIMS-ISS)
Reporting T’, P’, F’
Process Engineer Recon
.p
Readin rocess
g & KP
I Results
Reco
dy
to ts
(6.5.0) n
m ea .
surem
s
cu en ents Applications
Production

n. m
eco sure
Recon.

R ea
m

Accounting
Planner

Page 25 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendix IV – DVRS Functional Architecture

DVRS Functional Architecture: Data Validation (6.1.0)

Flow
Compensations
Model Solver (6.1.3)
(6.3.0) Model
d)
ate Configuration

Fc (
ns
Ac

(6.2.0)
pe

6.co
tiv
at

m
e

.co

data

m
bo

ated
(6

pen
Valid
un

Fc
ds

sate
/ru

T,
P,
le
s

F,
d)
Data Measurements & D
Conditionings Accuracies
T, P
(6.1.4) ds & rule
s (6.1.2) , F, D
Set boun , leve
l, D
-86
Process Engineer Ac Data Sources (PI
Analy

tiv
ate
-OMS-LIMS-ISS)
Mode

bo
ze

un
ds
readin
detec

Set
boun
ds &
tion

rules
g

gs
din
rea
ge
ran

Event Analysis Measurements

t of

(6.1.5) Bounds (6.1.1)

Ou

nge
f ra
O ut o
Reporting nge rea
ding
Out of ra
Results
(6.5.0)

Page 26 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendix V – DVRS Functional Architecture

DVRS Functional Architecture: Unit/Plant Model (6.2.0)

Administrator Set param

et ers P&IDs
Set pa
ram ete
rs Model Rules Chemical s
am
& Conditions Reactions st
re
&
(6.2.8) (6.2.6) er
s,
et

s
,m

on
ts
Def

ati
en

qu

ine
ine
i pm
de qu

Def
,e
Ad

ts
ASTM D-86 ni
Mass & Heat
Model Solver U
To TBP Curve Balances
(6.3.0) Elimina e
te/activ
ate reading
(6.2.7) E De
fi n (6.2.3)
s/rules mb
ed
Valida D86
ted mo
del Unit/Plant Data Sources (PI
-OMS-LIMS-ISS)
Utilize

Model Temp, pressure, flow, level, & density

TD

n nt
(6.2.1)
nfiguratio De
Sensitivity What-if co pla on fi n
to rati e
Analysis ap u
M nfig
(6.4.0) Thermo- Co Pressure
dynamic & Molecular
Re quir
re
du em

Libraries Balances
ns
nd en

atio
an ts

(6.2.2) (6.2.4)
cy

equ
ded

Va
Ad

Va
lid

lid
at

at
Redundancy
ed

ed
e

da
ur

da
Level
fig

ta

ta
on

(6.2.5) Data
-c
Re

Validation
Process Engineer
(6.1.0)

Page 27 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendix VI – DVRS Functional Architecture

DVRS Functional Architecture: Model Solution (6.3.0)

Administrator
Solution
Error
with Solver
Elimination re
Sensitivity Boundaries nfi
gu
(6.3.4) Co
Analysis (6.3.5)
Ch

Eli
(6.4.0) Gen
ec

m
Solv

erate ina

Identifie
readings
k

analy te/
ses ac
er ty

Ge tiv
ne ate
ra
pe

rea

d
te din
an
aly Model gs
/ru
s les
es Solution Validated
model
uc
e (6.3.2) H
Model
od im ighe
Pr pa st Eliminate/ac
KPIs & ct
/p
tivate readin
gs/rules Configuration
en
Un-Measured al
ty
(6.2.0)
Variables Error
Perform run

(6.3.6)
Select

Detection
(6.3.3)
el
od
Ac

m
tiv

d el
ate

c ile od
on m
bo

d
ec le
un

R ci
Solver
ds

on
ec
/ru

R
SQP/SQPIP
les

Reporting
(6.3.1)
Results Data
(6.5.0) Validation
(6.1.0)

Page 28 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendix VII – DVRS Functional Architecture

DVRS Functional Architecture: Sensitivity Analysis (6.4.0)

Model Solver
Ge
ne (6.3.0)
Process Engineer ra
te
ze

an
aly

aly
KPIs s
An

Measurements es
Covariance
Covariance
ze

Analysis
aly

Analysis(6.4.3)
An

(6.4.4)
s

va
gain/penalty
Relative
ie

lid
ac

at
ur

ed
c
ac

ac
ed

cur
at

ac
lid

ie
va

KPI Relative
Measurements
Analysis gain/penalty Analysis
Ac W
cu (6.4.2) (6.4.1) ha
ra t-i
cy fc
/p on
en fig
al Wh ur
ty at- at
if c ion
Reporting onf
igu
rati
Results on
Model
(6.5.0)
Configuration
(6.2.0)

Page 29 of 30
Document Responsibility: Process Optimization Solutions Standards Committee 23-SAMSS-071
Issue Date: 3 December 2014
Next Planned Update: 7 August 2017 Data Validation and Reconciliation Software

Appendix VIII – DVRS Functional Architecture

DVRS Functional Architecture: Reporting Results (6.5.0)

Data
Reconciled Validation
Meas. With (6.1.0)
Estimated
Accuracy
Meas. With

e
Model Solver (6.5.2)

din ang
Re Accuracy

rea t of r
(6.3.0) c

g
mo oncil (6.5.3)
del ed

Ou
Ca
lcu

Calc
lat
e T’, P’, F’,
Recon. Data Sources (PI

ulate
D’, level’,
Quality D-86’, KPI’ -OMS-LIMS-ISS)

(6.5.1) Re
Sensitivity Acc me con.
Cov uracy KPIs as
ure
Analysis aria
nce with Accuracy
me
nts
(6.4.0) Re
(6.5.4)
Config

-c
al
cu
Applications
la
te
ure

Rec
Rea on. pr re
gu
din oces nfi
g& s Co
KPI
Customized
Process Engineer Reports (6.5.6) Flagged
& Suspected on.
ure Rec uction
nfig Meas. (6.5.5) Pro
d
Co
Recon. custody Planner
Administrator measurements

Accounting

Page 30 of 30