Saep 1624

Engineering Procedure
SAEP-1624 6 February 2013

Preparation of System Design Documents
Document Responsibility: Process Control Standards Committee
Saudi Aramco DeskTop Standards

Table of Contents
1 Scope............................................................. 2
2 Conflicts and Deviations................................. 3
3 Applicable Documents,
Acronyms and Definitions....................... 3
4 Instructions..................................................... 5
5 Responsibilities.............................................. 5
Appendix 1 – System Design

Document Contents................................ 7
Previous Issue: 16 September 2009 Next Planned Update: 6 February 2018

Revised paragraphs are indicated in the right margin Page 1 of 26
Primary contact: Kinsley, John Arthur on +966-3-8801831
Copyright©Saudi Aramco 2013. All rights reserved.

Document Responsibility: Process Control Standards Committee SAEP-1624
Issue Date: 6 February 2013
Next Planned Update: 6 February 2018 Preparation of System Design Documents
1 Scope
1.1 Application
This Saudi Aramco Engineering Procedure (SAEP) provides instructions for the
development and approval of a System Design Document (SDD) for both new
and major expansion of process control and automation systems.
Any Process Automation System (PAS), Process Control Systems (PCS),

Distributed Control Systems (DCS), Supervisory Control & Data Acquisition
Systems (SCADA), Emergency Shutdown System (ESD), Terminal
Management Systems (TMS), Auxiliary Control System and any combination of
these items shall fall under the scope of this SAEP, provided that SAEP-16
governs the execution of the project. These systems shall be referred to
henceforth as a PAS in this document.
SAEP-16 is applicable for projects in which:

(a) a PAS is included, and
(b) overall cost of the PAS is $1,000,000 or greater.
1.2 Purpose
The System Design Document (SDD) documents the design basis of the Process
Automation System (PAS). It is a project-specific engineering document which
addresses the system design aspects and supplements design considerations that
are project specific normally not covered by Vendor’s standard engineering and
maintenance manuals.
This document defines the design basis of the architecture, configuration, data
bases, hardware, software and communication (both internal and external)
aspects of the PAS. It shall provide the basis for the detailed design and
integration of the PAS.
The SDD is typically prepared by the Vendor and/or Integrator. It may also be
authored by the design engineering contractor if he acts as the integrator.
1.3 Approval and Timing
The SDD is part of the 601 and 602 series of NMRs (Non-Material Requirements)
as described in SAEP-16.
The initial draft of the document shall be issued prior to delivery of NMR 601’s.
It shall be updated throughout the life of the project as further details become
available.
Page 2 of 26
This document must be approved by Saudi Aramco prior to any configuration,

software development and assembly of equipment.
It shall be updated prior to mechanical completion as an “as-built” document as

a key reference for system and control engineers. It shall provide accurate and
sufficient detail as the key document for future modifications and expansions.
2 Conflicts and Deviations
2.1 Any conflicts between this Procedure and other applicable Saudi Aramco
Engineering Procedures (SAEPs), Saudi Aramco Engineering Standards
(SAESs), Saudi Aramco Materials System Specifications (SAMSSs), Saudi
Aramco 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 Procedure 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 Applicable Documents
All referenced Procedures, Standards, Specifications, Codes, Forms, Drawings, and

similar material or equipment supplied shall be considered part of this Procedure to the
extent specified herein and shall be of the latest issue (including all revisions, addenda,
and supplements) unless stated otherwise.
 Saudi Aramco Engineering Procedures

SAEP-16 Project Execution Guide for Process Automation Systems
SAEP-302 Instructions for Obtaining a Waiver of a Mandatory
SAEP-368 Alarm System Management
SAEP-1626 Configuration and Graphics Guidelines
 Saudi Aramco Engineering Standards

SAES-J-003 Instrumentation - Basic Design Criteria
SAES-J-904 FOUNDATION™ Fieldbus (FF) Systems
SAES-J-905 Instrument Asset Management Systems (IAMS)
SAES-Z-001 Process Control Systems
Page 3 of 26
SAES-Z-003 Pipelines Leak Detection Systems

SAES-Z-004 Supervisory Control and Data Acquisition Systems
SAES-Z-010 Process Automation Networks
 Saudi Aramco Materials System Specifications

23-SAMSS-010 Distributed Control Systems
23-SAMSS-020 Supervisory Control and Data Acquisition Systems
23-SAMSS-050 Terminal Management Systems
4 Acronyms and Definitions
4.1 Definitions
In general, the definition sections of 23-SAMSS-010 and SAES-Z-001 apply.
Auxiliary System: A control and/or monitoring system that is stand-alone,

performs a specialized task, and communicates to the main control system for
monitoring and operator control. Examples are Compressor Control,
Programmable Logic Controllers, Rotating Machinery protection, process
analyzers network.
Operating Organization: The department responsible for operating the

facility, usually referred to as the “Proponent”.
4.2 Acronyms
DCS Distributed Control System

DCN Distributed Control Network
ESD Emergency Shutdown System
FSD Functional Specification Document
LAN Local Area Network
MIS Management Information System
NMR Non-Material Requirements
P&CSD Process and Control Systems Department
PAS Process Automation System
PAN Plant Automation Network
SAEP Saudi Aramco Engineering Procedure
Page 4 of 26
SAMSS Saudi Aramco Material System Specification

SAPMT Saudi Aramco Project Management Team
SCADA Supervisory Control and Data Acquisition
5 Instructions
4.1 The System Design Document (SDD) contains essential design considerations.
It is intended as a high level design document to establish the overall design
philosophy of the PAS. It is also intended to be an important reference
document for Plant engineers to use in maintaining and modifying the system
after the project completion.
4.2 The SDD shall consist of the sections shown in Appendix 1. State “Not
Applicable” if a section does not apply to the system in question. All drawings,
calculations and supporting detailed discussions and documents shall be
included as appendices.
4.3 The SDD shall contain both the design philosophy and actual system design for
those sections listed in Appendix 1. Placeholders shall be inserted where details
are not available during the initial SDD review. Actual design details shall be
inserted as the system design progresses.
4.4 The SDD shall be continuously updated as required during detailed design to
show the correct and latest design guidelines and to incorporate additional data
not available during the initial development of the SDD.
5 Responsibilities
This section defines the responsibilities of the parties involved in the development of an
SDD for a PAS that is governed by SAEP-16.
5.1 Saudi Aramco Project Management Team

a. Maintain overall responsibility for the SDD.
b. Initiate and coordinate the formal review of the SDD.
c. Review and approve the SDD document.
5.2 Operating Organization

a. Assign one responsible engineer to supply the detailed information required
for the SDD.
b. Review and approve the SDD document.
Page 5 of 26
5.3 Process and Control Systems Department
Provide technical consulting as requested to the Operating Organization and

SAPMT.
5.4 Vendor/Contractor
It is the Vendor/Contractor’s sole responsibility to prepare the SDD and ensure

compliance with all applicable Functional Specification Documents (FSD),
Saudi Aramco Engineering Standards (SAES) and Saudi Aramco Materials
System Specifications (SAMSS).
Revision Summary
6 February 2013 Revised the “Next Planned Update.” Reaffirmed the content of the document, and reissued
with minor revision.
Page 6 of 26
Appendix 1 - System Design Document Contents
1. INTRODUCTION
1.1 Purpose
The purpose of this Procedure together with the referenced Saudi Aramco
Standards, Specifications, and project documents is to describe the guidelines
for the Process Control System (PCS) VENDOR to prepare a System Design
Document (SDD) for the PCS.
Any conflict between this document and any other project specification, or
Saudi Aramco standards/specification, shall be brought to attention of the
COMPANY for resolution.
1.2 Scope
1.2.1 Immediately after placement of the purchase order PCS VENDOR

shall develop the SDD, using this document as the basis for design.
In addition, PCS VENDOR shall ensure that standard, sound and
consistent engineering practices are followed throughout the design
and hence are at liberty to propose suggestions or alternatives.
1.2.2 SDD shall be reviewed and approved by CONTRACTOR(s) and

COMPANY during SDD Review Meeting.
1.2.3 The SDD shall be continuously updated as required during detailed

design through the Factory Acceptance Testing to show the correct and
latest design guidelines and to incorporate additional data not available
during the initial development of the SDD. Updates shall be distributed
to CONTRACTOR(s) and COMPANY as part of the NMR review
cycle.
1.2.4 The SDD shall contain details specific for the selected PCS hardware,
system architecture, and configuration used for the PCS system.
1.2.5 SDD shall describe in details PCS configuration as defined in this

document and details defined in Appendix 1 of SAEP-1624. Additional
sections may be added as required by PCS VENDOR.
1.2.6 SDD shall describe all aspects the PCS system architecture, control
network design, plant automation network design, hardware and
software design, console design and cabinet design, and power supply
and grounding design.
Page 7 of 26
1.2.7 SDD shall describe in detail the arrangement and distribution of

installed and uninstalled spares capacity for each cabinet.
1.2.8 SDD shall describe all aspects of the PCS software design, including
but not limited to I/O configuration, FF device configuration, control
strategy configuration, auxiliary systems interface configuration,
graphics configuration and system security.
1.2.9 The SDD shall describe in detail PCS VENDOR’s configuration

philosophy and control strategies for all elements of the PCS.
1.2.10 SDD shall describe in details Graphics Displays requirements and

develop display guidelines which will be reviewed by
CONTRACTOR(s) and COMPANY before starting the display
development activity.
1.2.11 SDD shall describe in details PCS system security and access control
which will be reviewed by CONTRACTOR(s) and COMPANY during
the detail design.
1.2.12 SDD shall describe in details PCS alarm management requirements

which will be reviewed by CONTRACTOR(s) and COMPANY during
the detail design.
1.2.13 PCS VENDOR shall include full details of the auxiliary

equipment/systems design and configuration as a part of the SDD.
1.3 Reference Documents
See Section 3 of this document for a list of applicable documents.
1.4 Definitions and Acronyms
1.4.1 See Section 3 of this document for acronyms and definition of terms
used in this document.
1.4.2 When used in this or referenced documents the following words are
used in the manner described below:
 ‘Shall’ and ‘must’ are used in the imperative sense
 ‘Will’ is used in the preferred sense
 ‘May’ is used in a permissive sense to state authority or permission
to do the act prescribed or provide the function being defined in the
prescribed manner, and the words ‘no person may….’ Or ‘a person
may not….’ mean that no person is required, authorized, permitted
Page 8 of 26
to do the act prescribed, and the words ‘a… may not ….’ mean that
the item being described is not required, authorized, or permitted in
the prescribed manner
 ‘Includes’ means ‘includes but not limited to’.
2. GENERAL
The following sections and details listed in each section shall be included in the SDD as
a minimum.
3. PCS OVERVIEW
This section provides a brief overview of the overall PCS to be supplied. The following
are to be included:
a) A general description of the overall PCS.
b) The overall control and operating philosophy.
c) A listing of each of the Operating Areas, Operator Consoles, and Risk areas
including the physical location of each.
d) A listing of each of the subsystems which comprise the overall PCS to be
provided including vendor name, product name and product version number.
Commentary Note:
The product version number may not be known at the initial writing of the SDD
since it is prior to PDR / CDR. The anticipated version number should be listed and
the section updated after CDR to reflect the actual version numbers used.
4. PROCESS CONTROL SYSTEM (PCS) ARCHITECTURE
4.1 Station Naming Conventions
This section shall describe the naming convention used for naming of
workstations, consoles, and cabinets provided as part of the PCS.
4.2 Consoles
This section shall provide details on each console provided as part of the PCS.
The following shall be provided as a minimum:
a) A listing of all consoles to be provided.
b) A typical layout drawing for an operator console in the CCR and a
maintenance console in the PIB.
c) A listing of workstations and workstation identification / tags to be
included in each console.
Page 9 of 26
d) The designation of process units to operator consoles (i.e., A listing of

which process units are allowed to be controlled from each console.)
4.3 Risk Area Segregation
This section shall provide details including design and layout for how
segregation between risk areas shall be provided. Segregation shall address all
PCS components including Marshaling Cabinets, I/O, Controllers, Consoles, and
Auxiliary Systems interfaces.
4.4 DCS Control Network (DCN) Architecture
This section shall provide details on the architecture of the DCN. The following
shall be included as a minimum:
a) An overall DCS System Architecture Drawing.
b) An overall description of the DCS Control Network (DCN) (including
architecture, redundancy, throughput, etc.).
c) A typical layout drawing for each operating area DCN.
d) Node naming or numbering conventions.
e) The number of nodes connected to the DCN and any limitations and
allowances for future expansion.
f) Details of IP Addresses of all Nodes connected to the DCN.
g) Details of any communications interface devices used to connect Nodes to
the DCN.
h) Details of any bridges, switches, routers or media converters used in the
DCN with their part numbers, physical locations, physical description and
functional description.
i) Details of any interconnections between the DCN and the Plant
Automation Network or other networks.
4.5 Plant Automation Network (PAN) Architecture
This section shall provide details on the architecture of the networks provided as
part of the PCS used for Plant Information. The following shall be provided as a
minimum:
a) A typical layout drawing for each network provided.
b) Details of any hardware devices used for the PAN including bridges,
switches, routers and firewalls.
c) The naming convention, number of nodes and IP addressing for all nodes
Page 10 of 26
connected to the PAN.

d) Details of redundancy if provided.
3) Details of any Firewall / DMZ implemented with the system.
4.6 Data Flow
This section shall provide a conceptual data flow diagram for data being
transmitted on either the DCN or PIN. A separate data flow diagram showing
source and sink connections for each system listed below shall be provided:
a) Sequence-of-Events data collection and reporting.
b) Diagnostic data collected by the Instrument Assent Management System.
c) Communications between the ADS and its appropriate control subsystem
for all Auxiliary systems.
d) Alarm Management System data collection and reporting.
e) PI data transfer and collection.
f) Any data communication transfer using OPC protocol.
5. POWER SUPPLY AND DISTRIBUTION
This section shall describe in detail the layout of the power supply and distribution
system for all subsystems which comprise the PCS. The following shall be included as
a minimum:
5.1 Typical layout for power distribution with System Cabinets.
5.2 Typical layout for DC power supplies used for instrument loop power.
5.3 Detailed description of the redundancy scheme used for all power supplies
installed in redundant fashion.
5.4 Power consumption calculations for each circuit connected to the power supply
system.
Commentary Note:
Details on power consumption calculations can be inserted later during the detail
design phase.
5.5 Sizing details of relays or fuses used to provide short circuit protection.
6. GROUNDING
This section shall provide details on the design of the grounding system for various
Page 11 of 26
subsystems which comprise the PCS. Description of the grounding philosophy for the
following subsystems shall be included as a minimum:
a) AC Power Grounding
b) DC / Instrument Loop Grounding.
7. CONTROLLER DESIGN
This section shall include details on the following:
7.1 Naming Conventions
Describe the convention used for naming of controllers.
7.2 Controller Sizing Guidelines
The following shall be included:

a) I/O type and quantity limitations including maximum number of I/O cards
per controller.
b) Memory limitations, available memory and philosophy for maintaining
available spare memory.
c) Communications limitations.
d) Processing limitations.
e) Control processor sizing spreadsheet for calculating the controller load.
7.3 Configuration Guidelines
List default values used for controllers such as controller scan time, addressing,
etc.
8. DATA ACQUISITION AND I/O
8.1 General
8.1.1 SDD shall describe data acquisition for all I/Os in the DCS via
hardwiring, digital communications, internal computation, or manual
keyboard input. A description of each type of I/O module shall be
provided.
8.1.2 SDD shall describe each type of I/O module used in the DCS.
SDD shall describe all interfaces with package equipments that are fully
controlled by DCS including any necessary sequential function (i.e.,
Reverse Osmosis, Instrument Air Compressors and Dryers etc.).
Page 12 of 26
8.2 I/O Design
This section shall provide details on the following:

a) Description of the naming, numbering or addressing convention used for
I/O modules.
b) Grouping of I/O cards belonging to a particular process area or module
within a risk area.
c) Details of how the I/O layout will limit the failure of single I/O card,
connector or I/O cable to one process equipment, primary or backup, for
parallel process equipment.
d) Details on how similarity in design and layout of I/O assignments and
configuration will be achieved for parallel process equipment.
8.3 Tagging Conventions
This section shall describe in details the tagging conventions that will be used
and shall cover as a minimum the following:
a) The format and structure of the tagging convention for each type of block
used.
b) Details on how this naming convention can be used for any tag throughout
the PCS, including auxiliary systems tags, without duplication of tags.
c) A listing of typical parameters for each tag type (i.e., PV, SP, MV for PID
blocks).
d) Details of any tag name conversions (if required) between the DCS and
auxiliary systems tag names.
e) System device tagging for diagnostic purposes.
8.4 I/O Cards
8.4.1 For each I/O card type it shall be explained as to how it meets the loop
and system requirement, the design considerations in engineering and
configuration, etc. SDD shall describe as a minimum the following I/O
and types whenever used in the PCS system in detail:
a) 4-20 mA DC redundant and non-redundant analog input and
output cards.
b) Thermocouple input cards.
c) RTD input cards.
d) 0-20 mA DC input cards.
Page 13 of 26
e) 24 V DC discrete I/O cards.

f) 120 V AC discrete I/O cards.
g) HART or other Smart I/O cards.
h) Modbus or other communications interface I/O cards.
i) FOUNDATION™ Fieldbus (FF) I/O cards.
j) Any other type of I/O card used.
8.4.2 SDD shall describe the loading guidelines of I/O cards inside PCS
cabinets as well as the space requirements for cards, redundancy
requirements, the arrangement of cards within a controller cabinet, and
consistency from cabinet to cabinet.
8.4.3 SDD shall describe in detail the signal separation based on the I/O type
(analog or discrete) and current/voltage levels.
8.4.4 SDD shall describe in detail the arrangement and distribution of

installed and uninstalled spares capacity for each cabinet.
8.4.5 SDD shall describe the project philosophy for implemented redundant
IO cards.
8.5 Signal Conversion and Scaling
This section provides details on the philosophy for signal conversion and
scaling. The following shall be included as a minimum:
a) Details on how scaling of raw values to engineering unit values will be
performed including locations and scale factors (if applicable).
b) Location of square root extraction either in the transmitter or the device.
c) Philosophy for low-flow cutoff and where this will take place.
d) Details on digital input filtering.
e) Details on analog input filtering including location of filter.
f) Details on any deadbands used with the default setting.
8.6 Engineering Units
This section shall list the engineering units used for each type of tag.
The following shall be included as a minimum:
Page 14 of 26
Property Fluid Units

Flow Water (Process/BFW/FW/CW) GPM
Flow Process oils, inc. gas condensate BPD or MBPD
Flow Glycol/DGA/Liquid utilities/Lube Oil GPM
Flow Steam LB/HR or MLB/HR
Flow Steam Condensate GPM
Flow Process/Fuel gases and vapors SCFD or MMSCFD
Flow Utility gasses (Air/N2/etc.) SCFM
Level Liquids and interfaces % (of Range)
Pressure All PSIG
Diff. Press All PSI or IN. H2O
Vacuum All IN.HG
Temperature All DEF.F
Vibration Displacement MILS
Vibration Velocity MILS/S
Vibration Acceleration G (gravity)
Specific Gravity Liquids SG
Specific Gravity Gasses SG
Concentration Any % MOLE or % PPM
Concentration HC Gas in Air % LEL
Viscosity All CP (Centipoise)
Density All LB/FT3
8.7 Analog Input
This section shall describe in detail the following for analog input signals:
a) Transmitter fault handling whenever the transmitter output exceeds its
saturation limit or transmitter output falls below minimum limit.
b) Signal isolation for externally powered signals.
c) Characterization and linearization required for various signal types.
d) Analog input rate of change limiting to filter out spikes.
e) Thermocouple burnout and RTD open circuit detection and alarming.
f) Extended engineering unit range shall not exceed ±7% of the range.
Page 15 of 26
8.8 Analog Output

a) Direct/reverse function.
b) Non-linear output characterization.
c) Initialization.
d) Output status and value for a failure condition.
e) Alarming for rate of change (where applicable).
f) Clamping of output value (where applicable).
g) Anti-reset windup (where applicable).
h) Standardization of the operator action to set “0%” for closing the valve and
100% for opening of a valve (irrespective of the valve action).
8.9 Digital Inputs

a) Nuisance alarm handling due to contact bounce.
b) Enabling, disabling, and inhibition of alarm condition.
c) Momentary digital input handling (such as from push/pull buttons).
d) Up/down accumulation and count of digital input point transition for motor
RUN/STOP status inputs, and watt hour measurement discrete input.
e) Start, stop and reset commands to control the count, target value for the
count, and the alarm or message generated when the target value is reached.
f) Details of any digital signal inversions done in the PCS.
8.10 Discrete Outputs
8.10.1 Outputs shall be configured to provide closed contacts for energizing a

field device and an open contact for de-energizing a field device. In the
case of certain motors, a closed contact may be required for tripping.
8.10.2 Outputs shall be configured as direct. (output is a closed contact when

the logic driving the output is “ON”).
8.10.3 Details on the following shall be included.

 Outputs requiring momentary contact.
 Leakage current (if any) of the output cards and the impact of this
Page 16 of 26
leakage on field devices.

 Diode requirements
8.11 FOUNDATION™ Fieldbus (FF) I/O
This section shall include the following as a minimum. FF system design and
configuration shall be as per Saudi Aramco Engineering Standard SAES-J-904.
8.11.1 FF Segment Design
This section shall provide details on the philosophy for FF segment

design. The following shall be included as a minimum:
 Philosophy for FF Segment topology or architecture.
 The maximum number of control elements per segment.
 The maximum number of indication only inputs per segment.
 Location of the Backup Link Active Scheduler.
 Philosophy for ensuring spare capacity on a segment.
8.11.2 Default Configuration Parameters
This section shall provide details on the philosophy used to define

default values for the following FF device parameters:
 Universal Parameters
o TAG_DESC
o STRATEGY
 Resource Block Parameters
o MODE_BLK.TARGET
o MODE_BLK.NORMAL
o RS_STATE
o RESTART
o FEATURE_SEL
o WRITE_LOCK
o WRITE_PRI
 AI/AO Block Parameters
o XD_SCALE
Page 17 of 26
8.11.3 Details on Transmitter parameters which are accessible to the PCS

operator or maintenance workstation. These shall include but not
limited to the following:
 Upper and lower range values.
 Damping.
 PV source (manually entered value or auto from the transmitter).
 PV type (raw value, linearized and/or compensated, square root
extracted, etc.).
 Communication configuration variables.
 Status of the transmitter.
9. CONTROL STRATEGY CONFIGURATION
9.1 Scan times
This section shall list the default loop scan times used for each loop type.
9.2 Initialization
This section shall describe the strategy for initialization of control loops.
a) Initial values for various controller parameters before processing is started
or restarted.
b) Value PV for Inputs when a point becomes active, a controller undergoes a
warm or cold start, or when a point recovers from “BAD” status.
c) Value of Initial Value sent to field (OUT) for Outputs when a point
becomes active, a controller undergoes a warm or cold start, or when a
point recovers from “BAD” status.
d) The Mode to which blocks will initialize for each block type. Mote: I/O
blocks typically initialize in Auto and Control blocks initialize to manual).
e) Philosophy for ensuring bumpless initialization for primary and secondary
controllers in cascade control scheme during initialization.
9.3 Bad PV
This section shall describe the philosophy for alarming and handling of BAD PV.
Page 18 of 26
9.4 Tracking
This section shall describe in detail the control configuration required to ensure
bumpless and balanceless transfer between various control modes.
9.5 Controller Action
This section shall describe the default configuration for controller action for
both direct and reverse acting controllers.
9.6 PID Tuning Parameters
This section shall describe the default tuning parameters to be used for various
loop types. The table below shall be populated with the actual values used.
Commentary Note:
The values shown below are suggested default values. The actual values used
may be adjusted during startup due to individual loop and/or process conditions.
Definitions:
Gain = 100% / Proportional Band = K
Integral = Resets per minute / repeat = T1
Derivative = Derivative time in minutes = T2
Scan = Point Processing cycle in seconds
LOOP TYPE GAIN INT DER SCAN

FLOW (gas/liquid) 0.25 0.4 None 1.0
PRESS (liquid) 0.25 0.4 None 1.0
PRESS (gas) 1.0 1.0 None 1.0
LEVEL 1.0 5.0 None 1.0
TEMPERATURE 2.00 10.0 0.2 1.0
ANALYZER (Chromatograph) 0.25 20.0 None 1.0
9.7 FF Control in the field Design
This section shall provide details on the philosophy for implementation of

Regulatory Control using FF. The following should be addressed where
PID control is implemented in the field devices:
 What criteria is used to determine where the primary PID control will be
implemented?
Page 19 of 26
 How cascade control be implemented using FF.

 How controllers will react on loss of communications with the Host System.
9.8 Control Loop Templates
This section shall provide details for each loop type (control loop typical) which
will be used. For each control typical, a written description of the Operating
Philosophy and Basic Design Criteria used and a Control Strategy Template for
the control loop typical shall be provided. Further details for specific loop types
are described below.
9.8.1 Flow Control.
9.8.2 Level Control.
9.8.3 Cascade Control.
9.8.4 Split Range Control.
9.8.5 Motor Control.
9.8.6 Interlocks.
9.8.7 Permissives.
9.8.8 ESD Bypasses.
9.8.9 H2S/LEL Detection.
9.8.10 Fire Detection.
9.8.11 Advanced Control
This section shall provide details for any advanced control strategies
implemented in the PCS. Details such as control narratives and
overview control strategy function blocks should be included.
9.8.12 GC Analyzer Loops
This section shall also define the philosophy for ensuring stale values
are detected and alarmed to the operator.
9.8.13 Composite Tags
This section shall describe configuration for composite tags such as
ZVs, MOVs, etc. The following shall be provided:
a) The device control point’s permissives and overrides to issue
open/close/reset/start/stop commands where required.
Page 20 of 26
For example, the local/remote switch input for a MOV shall be

used as a permissive for open/close/stop commands.
b) Mismatch alarms when the command and the status feedback
are conflicting.
c) Time specified (set equal to the valve travel time) to inhibit a
mismatch alarm during the valve travel.
d) Failure and initialization status for each of the I/Os.
e) Closing Alarm for all MOV & ZV.
f) Each equipment to have Stop Alarm to differentiate between
field and Control room operator stop commands.
9.8.14 Flow Compensations and Totalizations
This section shall provide details on flow compensation and flow
totalization loops. The following shall be described:
a) Compensations of flow measurement for variations in
temperature, absolute pressure, specific gravity or molecular
weight.
b) Steam flow measurement compensation for steam quality and
compressibility.
c) The quality check on each of the measured values used in the
flow compensation and the subsequent action, alarm and
display configured.
d) Totalization showing the time scaled accumulation of a flow
measurement.
e) Totalization of a pulse input or transmitter input or MODBUS
register input, and the time scale in seconds, minutes, hours or
day.
f) Operator action configured to start, stop and reset the totalized
value from the console.
g) Value of flow cut-off limit to prevent accumulation of negative
flow values.
h) Bad quality input detection and return to normal sequence.
10 AUXILIARY SYSTEMS INTERFACE
This section shall describe the various interfaces to third party auxiliary systems.
Page 21 of 26
10.1 Details of the following subsystems shall be included:

10.1.1 Emergency Shutdown Systems (ESD).
10.1.2 Rotating Machinery Protection Systems (RMPS).
10.1.3 Compressor Control Systems (CCS).
10.1.4 Condition Monitoring Systems (CMS).
10.1.5 Power Systems Automation (PSA).
10.1.6 Programmable Logic Controllers (PLC).
10.1.7 Tank Gauging Systems.
10.1.8 Custody Metering Systems.
10.1.9 Interface to SAP (Terminal Management Systems).
10.1.10 Other third party systems interfaced to the PCS.
10.2 For each interface, the following details shall be provided:

10.2.1 Design Philosophy.
10.2.2 Communication Interface definition.
10.2.3 Interface Loading considerations and status monitoring.
10.2.4 Tagging Conventions.
10.2.5 Interface configuration philosophy.
10.2.6 Sub-system requirements and configuration.
11 TIME SYNCRONIZATION
This section shall provide detailed description of the various components used to
provide time synchronization of various sub-systems of the PCS. Details on the
following subsystems shall be provided:
11.1 DCS Time Synchronization.
11.2 ESD Time Synchronization.
11.3 CCS Time Synchronization.
11.4 RMPS Time Synchronization.
Page 22 of 26
12 GRAPHICS DESIGN AND NAVIGATION
This section shall describe the operational philosophy for the display sub-system.
a) Display Hierarchy. Description of which actions are possible from the different
types of displays (i.e., overview, process graphics, control overlays, equipment
startup and shutdown displays, etc.).
b) Display Navigation. Definition of the philosophy for navigation through displays.
c) Access Control. Definition of the mechanisms which will be used to limit access
control to particular consoles and/or user.
13 SECURITY AND ACCESS PROTECTION
This section shall provide details on the security and access protection for the PCS.
a) Definition of the philosophy for limiting access to users based on their authorization
level.
b) Definition of the User Roles which will be implemented for the project.
c) Definition of the User Environments which will be implemented for the project.
d) Definition of the password complexity and aging requirements which will be
implemented for the project.
e) Definition of the network security measures which will be implemented to prevent
and detect intrusion.
14 HISTORIZATION AND DATA COLLECTION
This section shall provide details on the configuration of data collection and
historization for trending and reporting. The following shall be provided as a minimum:
14.1 System Description
This section shall describe the various components of the system, both hardware
and software, used to collect and store real-time and alarm message data.
14.2 Historian Configuration
The following shall be specified:

 Configuration of data collection rates for various types of tags.
 Configuration of data retention time for various types of tags.
 Configuration of historical deadbands (if applicable).
Page 23 of 26
14.3 Data archiving
This section shall describe procedures used to archive historical data to offline
media (if applicable).
15 REPORTING
This section shall provide details on the various components and operation of the
reporting system. The following shall be provided as a minimum:
a) Description of any software licenses required.
b) Description and example of each of the various types of reports which are provided.
c) Description of the various components, both hardware and software, which are
used in the reporting system.
d) Operation of the reports including scheduling and on-demand execution.
e) Description of the report archiving and mechanism used to retrieve past reports.
16 SEQUENCE OF EVENTS
This section shall describe the configuration and operation of the Sequence of Events
(SOE) messaging and reporting system.
17 PI SYSTEM AND INTERFACE
This section shall describe the hardware and software components which make up both
the “interface to” and the actual OSI-PI system. The following shall be included as a
minimum:
a) Description of system components (both hardware and software).
b) Description and quantity of software licenses which will be supplied.
c) The location, configuration and operation of the interface to the OSI-PI system.
d) The configuration of the OSI-PI server including OSI-PI data collectors and server
software packages, data collection update rates, and other configuration details.
e) The location, configuration and operation of any OSI-PI client software.
18 SYSTEM DIAGNOSTICS AND EQUIPMENT STATUS DISPLAYS
This section shall provide details on the system diagnostic subsystem.
18.1 System Diagnostics
Page 24 of 26
 Description of components used for the system diagnostics.

 The location of monitoring programs and alarm destinations for stations
monitored by the system diagnostics.
 Description of the operation of the system diagnostics package.
18.2 Equipment Status Displays
This section shall provide details on the layout and status information available
on equipment status displays for third party systems which are connected to the
PCS. Typical Layouts for each type shall be provided.
19 PROJECT SPECIFIC APPLICATIONS
This section shall provide a detailed description of any project specific or custom software
applications implemented on the system. The following shall be included as a minimum:
a) Design narrative describing the function and operation of the application.
b) Details on program data flow charts and decision tables.
c) Details on internal and input/output data structures used.
d) Details on programming languages, compilers (with version) and source code listings.
e) Resource utilization (e.g., memory, computational time).
f) Application requirements such as any protocols required (i.e., TCP/IP, OLE DB, etc.).
20 ALARM MANAGEMENT
20.1 Alarm Management System Description
This section shall contain a description of the components, both hardware and
software, which comprise the Alarm Management System. A conceptual data
flow diagram showing the source and destination for all alarms collected by the
system shall be provided.
20.2 Alarm Design Guidelines
This section shall contain the Alarm System Philosophy Document as described
in Section 6 of SAEP-368, Alarm Systems Management, and shall describe how
the alarm management system will meet the requirements specified in the Alarm
Management System Functional Specification document.
21 INSTRUMENT ASSET MANAGEMENT SYSTEM (IAMS)
This section shall describe the design, configuration and operation of the IAMS.
Details on the following shall be provided as a minimum:
Page 25 of 26
a) Description of the physical interfaces, from signals connected directly to DCS I/O
cards and from third party systems through HART multiplexors, for the IAMS.
b) Definition of the structure/hierarchy used to categorize instruments (i.e., by plant
area, instrument vendor, instrument type, process service, etc.)
c) Definition of what data will be stored in the IAMS (i.e., Instrument specification
sheets, maintenance manuals, exploded views, etc.)
d) Philosophy for categorization and annunciation of diagnostic alarms from smart
devices.
e) Details on the interface to Smart Valve Positioners, including diagnostic
capabilities, philosophy for storage of valve signature data, definition of alarm and
error codes, and other important information.
22 BACKUP AND RESTORE PROCEDURES
This section shall describe the philosophy for backup and restore of critical data from
the PCS. The following shall be included as a minimum:
a) Backup and restore for DCS System configuration data, graphics (if applicable)
and Control Application configuration database.
b) Backup and restore for IAMS database.
c) Backup and restore for ESD application logic.
d) Backup and restore for CCS application program.
23 SOFTWARE LICENSES
This section shall list all software licenses with license codes supplied with the PCS.
Commentary Note:
Actual license codes can be added later in the detail design phase.
Page 26 of 26

Saep 1624

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

Saep 1624

Uploaded by

Copyright:

Available Formats

Engineering Procedure

SAEP-1624 6 February 2013

Saudi Aramco DeskTop Standards

Appendix 1 – System Design

Previous Issue: 16 September 2009 Next Planned Update: 6 February 2018

Copyright©Saudi Aramco 2013. All rights reserved.

Any Process Automation System (PAS), Process Control Systems (PCS),

SAEP-16 is applicable for projects in which:

1.3 Approval and Timing

This document must be approved by Saudi Aramco prior to any configuration,

It shall be updated prior to mechanical completion as an “as-built” document as

2 Conflicts and Deviations

All referenced Procedures, Standards, Specifications, Codes, Forms, Drawings, and

 Saudi Aramco Engineering Procedures

 Saudi Aramco Engineering Standards

SAES-Z-003 Pipelines Leak Detection Systems

 Saudi Aramco Materials System Specifications

4 Acronyms and Definitions

In general, the definition sections of 23-SAMSS-010 and SAES-Z-001 apply.

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

Operating Organization: The department responsible for operating the

DCS Distributed Control System

SAMSS Saudi Aramco Material System Specification

5.1 Saudi Aramco Project Management Team

5.2 Operating Organization

5.3 Process and Control Systems Department

Provide technical consulting as requested to the Operating Organization and

It is the Vendor/Contractor’s sole responsibility to prepare the SDD and ensure

Appendix 1 - System Design Document Contents

1.2.1 Immediately after placement of the purchase order PCS VENDOR

1.2.2 SDD shall be reviewed and approved by CONTRACTOR(s) and

1.2.3 The SDD shall be continuously updated as required during detailed

1.2.5 SDD shall describe in details PCS configuration as defined in this

1.2.7 SDD shall describe in detail the arrangement and distribution of

1.2.9 The SDD shall describe in detail PCS VENDOR’s configuration

1.2.10 SDD shall describe in details Graphics Displays requirements and

1.2.12 SDD shall describe in details PCS alarm management requirements

1.2.13 PCS VENDOR shall include full details of the auxiliary

1.3 Reference Documents

See Section 3 of this document for a list of applicable documents.

1.4 Definitions and Acronyms

4. PROCESS CONTROL SYSTEM (PCS) ARCHITECTURE

4.1 Station Naming Conventions

d) The designation of process units to operator consoles (i.e., A listing of

4.3 Risk Area Segregation

4.4 DCS Control Network (DCN) Architecture

4.5 Plant Automation Network (PAN) Architecture

connected to the PAN.

4.6 Data Flow

5. POWER SUPPLY AND DISTRIBUTION

5.1 Typical layout for power distribution with System Cabinets.

This section shall include details on the following:

7.1 Naming Conventions

Describe the convention used for naming of controllers.

7.2 Controller Sizing Guidelines

The following shall be included:

7.3 Configuration Guidelines

8. DATA ACQUISITION AND I/O

8.2 I/O Design

This section shall provide details on the following:

8.3 Tagging Conventions

8.4 I/O Cards

e) 24 V DC discrete I/O cards.