Process Control Narratives: NEORSD Design Standard

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 1

NEORSD Design Standard

Process Control Narratives

I. Introduction

A process control narrative, or PCN, is a functional statement describing how device-mounted


controls, panel mounted controls, PLCs, HMIs, and other processor-based process control system
components should be configured and programmed to control and monitor a particular process,
process area or facility. PCNs are sometimes referred to as control strategies, control narratives,
sequence descriptions, and by other similar names. A PCN is the essential link between process
design and control system design. It also forms an integral part of the final control system
documentation, providing in the most concise but descriptive form, a statement that ties together
process operation, process equipment, instrumentation, control philosophy, available control modes
and control loops, as well as documenting control logic settings such as setpoints, computed values,
alarm limits, normal operating limits, trips, interlocks, and other key parameters.

Process Control Narratives serve several purposes:

• During the Preliminary Design phase of a project PCNs are used to describe the process
control and monitoring concepts based on the conceptual process design. The PCNs
document preliminary equipment and operational requirements. At the start of this stage the
document may be a Process Narrative or Process Description. At the completion of the
Preliminary Design phase the document should be a well-developed Process Control
Narrative (PCN) that is about 90% complete.
• During the Detailed Design phase, PCNs are used to refine process control design
requirements such as:
o Selection and location of instrumentation and control devices
o Hardwired interlocks and permissives
o Data archiving and reporting requirements
o Trend parameters
o Alarm settings
o Operator prompts and messages
o Other functions and parameters associated with the process.
A PCN provides the instrumentation and control system engineer with a guideline for
development of the overall design.
• During construction and start-up, the PCNs, in conjunction with supporting drawings, control
system lists, equipment specifications and instrumenttion information, must be the controlling
documents used by integrators and programmers for developing the process control logic and
system configuration. The PCNs describe the system functionality that must be installed and
tested. Site and Factory Aceptance Test checklists can, in part, be developed from the
descriptive material in the PCNs.
• Following the construction testing phase, the as-built PCNs become key reference documents,
operation and maintenance manual components, and training materials to provide current,
updatable documentation for the technical and operations personnel at the facilities. The
design documents should require contractors and integrators to submit as-built documents in

You might also like