Materials System Specification

23-SAMSS-072 17 September 2013

Data Acquisition and Historization System (DAHS)
Document Responsibility: Process Control Standards Committee

Saudi Aramco DeskTop Standards

Table of Contents

1 Scope............................................................. 2
2 Conflicts and Deviations................................ 2
3 References..................................................... 2
4 Definitions....................................................... 2
5 General........................................................... 6
6 Platform Support............................................ 6
7 Data Archives................................................. 6
8 Data Compression.......................................... 8
9 Interfaces........................................................ 8
10 Database Connectivity................................. 10
11 Asset-Centric Database…………………..…. 10
12 Calculations.................................................. 10
13 Maintenance and Performance Monitoring.. 11
14 Client Utilities................................................ 12
15 Security........................................................ 13
16 Documentation............................................. 14

Previous Issue: 24 October 2009 Planned Update: 17 September 2018

Revised paragraphs are indicated in the right margin Page 1 of 14
Primary contact: Kokolu, Prabhakar Rao on +966-13-8801589

Copyright©Saudi Aramco 2013. All rights reserved.

Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

1 Scope

1.1 This specification defines the minimum mandatory functional design,

architecture and functionalities necessary for Data Acquisition and Historization
System (DAHS) for capturing, management and use of real-time process data.

1.2 This specification applies to DAHS including the software and hardware
components required to integrate Oil & Gas applications.

1.3 Additional requirements might be included in Company's FSD, in which case

both this document and the FSD requirements shall be met.

2 Conflicts and Deviations

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

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

3 References

Material or equipment supplied to this specification shall comply with the latest edition
of the references listed below, unless otherwise noted.

 Saudi Aramco References

Saudi Aramco Engineering Procedure

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

Saudi Aramco Best Practice

SABP-Z-001 Plant Information System Data Compression

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

Page 2 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

“Comprehensive Dictionary of Measurement and Control”, International Society for

Measurement and Control, shall apply.

4.1 Acronyms and Abbreviations

API Application Program Interface
DAHS Data Acquisition and Historization System
DMZ Demilitarized Zone
ERP Enterprise Resource Planning
FSD Functional Specification Document
KPI Key Performance Indices
MES Manufacturing execution system
ODBC Open Database Connectivity
OLEDB Object Linking and Embedding Database
PLC Programmable Logic Controllers
SQL Structured Query Language

4.2 Words and Terms

Application Programming Interfacing (API): A set of library functions to be

made available by DAHS that allows programmatic access to the DAHS both
for data archiving and for retrieval.

COM Connectors: are used as intermediary to interact with data in external

data systems. A separate COM connector is required to communicate with each
specific foreign data system.

Data Compression: is a storage methodology that uses the predicted behavior

of a process parameter to reduce the actual raw data values to a data subset,
which can then be later expanded and interpolated or decompressed to produce a
representation of the original data accurate to within the data tolerance level
specified.

Data Filtering: Interface send data from an instrument data source to historian
only after it is evaluated and found to be significant. During the evaluation, the
current value is compared to the previously sent value. It would be sent to
historian if it is different.

Fault-tolerant: is a method for designing a system so it will continue to

operate, possibly at a reduced level (also known as graceful degradation), rather
than failing completely, when some part of the system fails.

Page 3 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

Instrumentation Data Sources: Most common instrumentation data sources

are Distributed Control Systems (DCS), Programmable Logic Controllers
(PLCs), Remote Terminal Units (RTUs), Lab Systems, HMI/SCADA.

Interfaces: are software modules for collecting data from any computing
device with measurements that change over time. Typical data sources can be
DCS, PLCs, Lab systems and process models.

ODBC Drivers: are used to access DAHS archives as well as Database in a

relational database format.

OPC: is a standard established by the OPC Foundation task force to allow

applications to access process data from the plant floor in a consistent manner.
Current OPC versions of OPC Data Access (DA); OPC Historical Data Access
(HDA and OPC Unified Architecture (UA) shall be used.

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

Real-time Performance Management (RPM): is the ability to utilize real-time

costing information to improve economic performance. For manufacturing
centric operations, plant automation and information systems already collect,
process, and store thousands of real-time measurements that can provide the
basis for real-time costing calculations.

This approach allows companies to monitor the performance of every process

unit along with the entire plant in real-time, while production is happening.
Performance values derived in real-time can be used by process operators to
improve current performance of the plant and passed to higher level enterprise
planning systems to improve future resource allocation decisions.

Robust Data buffering: Input data continue to accumulate in the interface

node's buffer, even as its communication with the historian is interrupted.
The empty data sectors in the historian are then automatically repopulated once
the communication is restored.

Robust I/O Interface: The ability of the software interfaces between DAHS
and other software components to remain on-line and as functional as possible in
the face of software errors.

Scheduling features: The scheduling feature determines when a calculation

will be carried out. There are two types of scheduling, Time based and Event
based. With Time based scheduling, calculation is evaluated at fixed intervals.

Page 4 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

Event based scheduling means a calculation is evaluated whenever one of its

trigger tags has received a new event.

Software Development Kit (SDK): is a set of tools used to develop

applications for a particular platform. An SDK typically contains a compiler,
linker, and debugger. It may also contain supporting code libraries and
documentation for APIs.

SQL Subsystem: is software module that processes SQL statements, including

those submitted by ODBC drivers.

Swinging door compression: discards values that fall on a line connecting

values that are recorded in the Archive. When a new value is received by the
process historian, the previous value is recorded only if any of the values since
the last recorded value do not fall within the compression deviation blanket.
The deviation blanket is a parallelogram extending between the last recorded
value and the new value with a width equal to twice the compression deviation
specification. When a new data point is received, the previous data is recorded
and held in Archive if it falls outside the compression deviation blanket.

Please refer “Swinging Door Trending: Adaptive Trend Recording” by E. H.

Bristol for further studies.

Temporal Archives: Temporal Archives are special format of database

which was developed to store and retrieve sets of time-sequenced data.
Temporal database is not a flat file or a relational database. It's a repository for
automatically collected data. This data, also called temporal or time series data,
consists of two components: a recorded value of a user determined type, and a
time stamp. The input/output (I/O) point identifies organized data in data stream
series. This format makes it possible to archive, retrieve, and organize data with
minimal demand on system resources.

Time-series data: is a stream of data identified by its tag identifier, and by

time, not by its internal data value. All data types are handled, like text, integer,
floating point, time and currency. Time Sequenced data set primarily handles
Time, Variable values and quality of the data. Data accuracy is most often
based on sensors/detector measured in percentage, variance, +/- bands or
significant digits.

Demilitarized Zone (DMZ): In computer security, a DMZ is a physical or

logical subnetwork that contains and exposes an organization's external-facing
services to a larger untrusted network, usually the Internet. The purpose of a
DMZ is to add an additional layer of security to an organization's local area
network (LAN).

Page 5 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

5 General

5.1 The application and database architecture of DAHS shall provide efficient storage
and retrieval of plant data over unlimited period of time. Hardware should be the
only limitation.

5.2 DAHS shall provide real-time storage for process and plant data that also
provides flexible user defined calculations, aggregations (mean, max, min, etc.)
over multiple user defined time periods.

5.3 DAHS shall provide easy-to-use tools to build, deploy and manage the historian.

5.4 DAHS shall allow programming of complex calculations and shall provide
various scheduling features: Time based, Event based, Event, Equation
Ordering, etc.

5.5 DAHS vendors shall demonstrate that the required functionality is provided and
that the system is robust. This testing shall be performed against an agreed test
specification prepared by the vendor, witnessed and approved by Saudi Aramco.

6 Platform Support

6.1 DAHS shall be scalable on available open standard operating systems such as
Microsoft Windows multi-tasking operating systems. The data files, archives
and configuration files used by DAHS shall be stored in a format that is portable
to all the platforms.

6.2 DAHS shall be compatible with latest microprocessors architecture and also
backward compatible. DAHS shall be easily migrated from older versions
(32-bit, etc.) to current architectures.

6.3 DAHS shall provide high availability features to configure alternate source to
store time-series data (i.e., redundant servers that act as independent storage and
a source for time-series data) so that data is highly available. The architecture
shall have built-in features that address the issues of data availability during
planned and unplanned downtime.

6.4 DAHS shall have the ability to conduct online backups without the need to bring
down the DAHS or disconnect clients.

7 Data Archives

7.1 DAHS shall have a temporal archive system where multiple time-series data
points are stored. Archive real-time data with precise time synchronization, so
that any operation or occurrence can be recreated and analyzed at any time.

Page 6 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

It shall have the ability to archive and retrieve minimum 80000 events per sec.
Time-Series resolution should be fine (one millisecond) and should be
synchronized across all archived elements.

7.2 DAHS shall be scalable to support large databases without compromising

performance, over and above 10 million tags, limited only by hardware capacity.
Archive speeds should be minimum 80000 events per sec.

7.3 DAHS archives shall support simultaneous archiving of thousands of data points
per second (80000 events/sec minimum). It should record only those data that
exceed an acceptable range of values (user determined) and should reduce the
required amount of stored data points, while increasing their accuracy and
resolution. DAHS shall be able to record the data according to a lossless
compression algorithm. The compression type and parameters should be
configurable. Compression can be turned off completely for a specific data
point when needed.

7.4 DAHS shall use temporal database technology for inputting data to, and
retrieving data from, the historian. Apply linearity while data points are
sampled to ensure linearity and only diverging points stored the values between
the stored points can then be interpolated giving high data fidelity with little
impact to storage.

7.5 DAHS shall be capable of storing and accessing on-line data up to minimum
5 years worth of plant wide data, time stamped at its natural frequency, for
immediate use on demand.

7.6 DAHS shall be scalable to unlimited number of archives, limited only by the
physical space available on the archive media.

7.7 DAHS shall have the capability of on-line monitoring (register or un-register) an
archive without disturbing the normal DAHS archiving functionality.

7.8 DAHS shall have all the conventional functions like creating new archives,
moving archives, combining a number of archives, dividing big archives into
smaller archives, recovering a corrupted archive, conversion of archives from
one version to another.

7.9 DAHS shall use latest techniques for backfilling data that comes in to the
archive out of sequence. It should have both abilities, i.e., to backfill data with
compression and without compression.

Page 7 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

8 Data Compression

DAHS shall follow industry standard data compression methodologies. Factors needed to
be considered while evaluating a DAHS compression methods are, data storage efficiency,
precision of the captured data, the ability to accurately recreate the raw input data and the
speed at which data can be written to / accessed from the archives. It is recommended that
the data compression parameters be according to SABP-Z-001 document.

8.1 DAHS shall have an efficient data storage module to evaluate events to
determine if it is significant. A significant event is one that is essential for
recreating the original data. Events that are not significant should be discarded.
Insignificant events can be discarded with no loss of information.

8.2 DAHS shall follow the “Swinging Door” algorithm(s) for data compression or
any other future industry proven compression method.

8.3 DAHS shall provide enough configurations to adjust the compression

parameters to produce efficient archive storage without losing significant data.

8.4 DAHS shall provide adequate protection against data loss in the event of failure
of the archive system due to a surge of process data from process or temporary
CPU overloading of the computer running the historian or other upsets.
When the Archive is able to recover from the cause of the upset, the events on
disk should be retrieved and placed back in memory for processing and storing
them in archive. There should be no fixed time limit that an Archive can be
off-line before data is lost. The amount of free space on the disk should be the
only limitation on the length of the queue.

8.5 DAHS interfaces shall provide exception reporting features. Exception reporting
is another kind of filtering the incoming data. Interfaces poll the equipment on a
regular basis and report new events to historian only after these events are
evaluated and found to be significant.

9 Interfaces

The DAHS System shall be an open system. It should provide industry standard
interfaces that allow other vendor products to be connected to DAHS.

9.1 DAHS shall provide a wide range of interfaces to popular control systems (DCS,
PLCs, SCADA) and SAP.

9.2 DAHS shall provide ODBC and OLEDB standard public interfaces that allow a
user to connect any client that supports the ODBC or OLEDB standard.

9.3 DAHS shall provide OPC foundation DA interface for bi-directional data

Page 8 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

transfer. It shall operate with any third party OPC DA server.

9.4 DAHS shall provide OPC foundation HDA interface for bi-directional data
transfer. It shall operate with any third party OPC HDA server.

9.5 DAHS shall provide OPC foundation Unified Architecture (UA) interface for
bi-directional data transfer. It shall operate on any service-oriented architecture
(SOA) with any third party OPC UA server.

9.6 DAHS shall provide OPC DA/HDA/UA Server which can interoperate with any
third party OPC client that is complaint with one or more OPC standards, to
allow the user to read data from DAHS, insert data into DAHS, or delete data
from DAHS.

9.7 DAHS shall provide data access via web services clients. It shall allow web
services clients to access DAHS system data via SOAP and also writing data to
DAHS.

9.8 DAHS shall have Robust I/O interface and Robust Data Buffering. It shall have
high speed interfaces (50000 events/sec) which deliver real-time, fault-tolerant
data.

9.9 DAHS shall provide interfaces to all Instrumentation Data Sources and Laboratory
Systems. It should provide manual data entry interface. All interfaces should have
data filtering facilities.

9.10 DAHS shall provide Application Programming Interfacing (API) and Software
Development Kit (SDK) libraries that allow a developer to write code that
connects to the historian both for data archiving and for retrieval.

9.11 DAHS shall support multiple historians. History for a specific parameter can be
collected on multiple servers, providing historical backup capability.

9.12 DAHS shall provide server-to-server interface to distribute data from one
historian to another so that a centralized administration for all remote tags can
be accomplished.

9.13 DAHS shall provide interface to allow bi-directional transfer of data between
the DAHS and any Relational Database Management System (RDBMS) that
supports Open DataBase Connectivity (ODBC) drivers. The RDBMS like
Oracle, MS SQL Server shall be supported.

9.14 DAHS OPC interfaces shall have a single port access via firewalls for secure bi-
directional path to plant networks.

Page 9 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

10 Database Connectivity

10.1 DAHS shall support standard SQL querying functionality. The basic SQL
functionality shall include querying data, alarm & events, system and
administrative information from the DAHS.

10.2 DAHS shall provide ODBC driver interface to enable programmatic access by a
third-party applications.

10.3 DAHS shall provide OLE DB Provider to integrate with third party applications
like Oracle, Microsoft SQL Server.

10.4 Open access for ERP and MES applications

10.5 Application integration via OLE DB, .net API, SDK, and OPC HDA

10.6 Highly compatible with third-party solutions

11 Asset-Centric Database

11.1 DAHS shall support building standard asset-centric databases and maintain user-
centric objects called plant assets or processes.

11.2 DAHS shall support asset models to build and organize DAHS data and other
data according to physical objects in the plants (meters, compressors, heaters,
etc.).

11.3 DAHS asset models shall be flexible to develop hierarchical models and ability
to span other such asset models.

11.4 DAHS shall provide analytics features to configure alerts and notifications that
can access asset centric database models.

12 Calculations

12.1 DAHS shall provide an integrated calculation engine which can be used to
develop calculations ranging from simple, equation-based calculations to
complex, scripted calculations. DAHS shall provide totalizer functions
(mathematical calculations which include totals, averages, minimum and
maximum values, ranges, medians and standard deviations).

12.2 DAHS shall provide a library of large array of pre-built calculations and
functions, including statistical, chemical, and mechanical engineering libraries.
DAHS shall provide a means to configure and store user defined functions in a
function library. The DAHS calculation engine shall provide features which
will allow data to be retrieved from and send results to DAHS tags.

Page 10 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

12.3 DAHS Calculation Engine shall support VB/.NET scripting technology or any
other standard scripting language. DAHS calculation engine shall allow
programmers to develop complex data manipulation calculations and KPIs.

12.4 DAHS Calculation Engine shall provide scheduling features where by the user
developed calculations can be executed. The calculations shall be configurable
to execute as time or event driven calculation and can easily be scalable to
multiple set of tags.

12.5 DAHS Calculation Engine shall provide the ability to call COM and .NET
objects and a library of user-written functions.

12.6 DAHS Calculation Engine shall provide the ability to test and debug equations.

12.7 DAHS Calculation Engine shall provide the ability to migrate the equations to
later releases of DAHS.

12.8 DAHS Calculation Engine shall have a re-calculation engine which will enable
users to re-run a calculation from any configurable start and end time against the
history of values and update the stored results.

13 Maintenance and Performance Monitoring

13.1 DAHS shall provide system management tools to inspect key health indicators.
These tools shall provide message logs, abnormal messages, system metrics
(such as I/O rates) and abnormal performance indicators for smooth and reliable
operation of DAHS.

13.2 DAHS shall provide robust system management tools to monitor the system.
Some of the critical areas shall be as follows;
 Monitor DAHS backup status
 Check for unusual events from system message logs
 Monitor status of client connections to DAHS
 Does the archive data for a reference tag look normal?
 Does the archive data flow normal?
 Check interface logs for unusual events
 Check interface health (verify I/O rates and timestamps)

13.3 DAHS shall provide a web based Real-time Performance Management platform.

13.4 The DAHS Performance Management module shall publish key performance
counters to windows. These performance counter statistics shall be viewed
using Microsoft's Performance Monitor Utility.

Page 11 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

13.5 The DAHS performance Management module shall publish key performance
counters on tag information, archives, interface I/O events, message statistics,
SQL I/Os, Totalizer statistics, network connection statistics, calculations, local
host as well as session statistics.

13.6 The DAHS performance counters shall contain information about the DAHS as
well as the machine that runs it. The performance counters for the machine shall
be useful in determining resource problems of the machine that runs DAHS
Server. The DAHS performance counters are useful in determining how well
the DAHS Server is performing.

13.7 The DAHS shall provide real-time information portal to visualize DAHS
process data using Microsoft Internet Explorer web browser. It shall be fully
secure, customizable and have search facilities.

13.8 DAHS shall have a messaging module to report historian status, errors, change
notifications to clients and monitor historian health.

13.9 DAHS shall have Rich Systems Diagnostics like Fault tolerant architecture,
Support for Microsoft Cluster Server, redundant data collectors, enhanced data
security.

14 Client Utilities

14.1 DAHS shall provide client tools to perform essential tasks as mentioned in
below points.

14.2 DAHS client tools shall be based on API library of routines that provide a
standard way of interfacing and be scalable on Microsoft Windows multi-
tasking operating systems.

14.3 DAHS shall provide a real-time graphics package to develop process graphics.
Drawing functions like values, bars and trends which update dynamically shall
be provided. Complete graphics tools and library. Support for ODBC access
features and programming language is mandatory.

14.4 DAHS shall provide an Excel based reporting and analysis tool. It should have
add-in for Microsoft Excel to allow DAHS data to be retrieved directly from
within the spreadsheet program. The add-in to have features to download;
 Current value
 Value at a specific time
 Tag attributes
 Evenly spaced (sampled) data

Page 12 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

 Sampled data while a given expression is true

 Compressed (archived) data
 Compressed data while a given expression is true
 Sampled data for a user specified array of timestamps
 Totals, minima, maxima, standard deviations, ranges, averages, counts and
means for DAHS tags and expressions

14.5 DAHS shall have an application to log data into the historian, which cannot be
collected automatically from instrumentation and control systems. Data sent to
DAHS should be automatically time stamped.

14.6 DAHS shall have native ODBC driver to bring process data from the historian
into any ODBC complaint client application.

14.7 DAHS shall provide tool to view alarms from the historian and detect behavioral
alarm patterns over a period of time. Tools which allow users to browse
displays of historian data on the Internet are an added benefit.

14.8 DAHS shall provide easy to use Web visualization to users with near-instant
ability to see and respond to problems or perform in-depth analyses on Historian
information.

14.9 DAHS shall provide a web-based tool for accessing, analyzing and visualizing
production information with sophisticated trending and reporting capabilities.

15 Security

In Saudi Aramco, DAHS are used in production systems where secure, correct, and
reliable operation is required.

15.1 DAHS shall provide windows integrated security to manage Historian Server
authentication through Windows and Microsoft Active Directory (AD).
This new security model improves historian server security, reduces
management workload, and provides users a single-sign on experience.

15.2 DAHS shall provide adequate security mechanism to protect against tampering
with the system. Shall provide provision to define user accounts, groups and
assign users to groups. Assign user groups to various databases, archive system.

15.3 DAHS shall provide mechanism to define role based access permissions to
groups. Using these groups, security shall be maintained over access to DAHS.

15.4 DAHS shall employ Microsoft Operating System security features to manage
users with common workplace roles.

Page 13 of 14
Document Responsibility: Process Control Standards Committee 23-SAMSS-072
Issue Date: 17 September 2013
Next Planned Update: 17 September 2018 Data Acquisition and Historization System (DAHS)

15.5 DAHS shall provide security features while accessing via API or SDK calls.

15.6 DAHS shall have features to control access from other historian servers or client
machines, i.e., point-to-point connection trusts.

15.7 DAHS shall have Database features to configure for user and group security.

15.8 DAHS shall be compatible to “single sign-on” or SSO approach. Enterprise and
control can be separated by a “DMZ” network.

16 Documentation

Extensive documentation shall be provided as listed below to ensure that the DAHS is
engineered and configured in a consistent manner.

16.1 DAHS Standard documentation shall be provided in CD-ROM or other

electronic format approved by the Saudi Aramco.

16.2 DAHS shall provide detailed documents on technical capabilities and design of
the application architecture.

16.3 DAHS shall deliver the following manuals as part of the system documentation
package: Installation Guide, Administration Guide, System management
Manual, User Operators Manual, API Manual and all other Manuals based on
vendor application.

16.4 DAHS shall make available On-line electronic documentation including text
search option.

Revision Summary
17 September 2013 Revised the "Next Planned Update." Reaffirmed the content of the document, and
reissued with minor revisions.

Page 14 of 14