http://www.eng-tips.com/viewthread.cfm?qid=214330
PHILOSOPHIES
Design philosophies for the C&I of a project are produced in an early stage of the conceptual study. The philosophy documents are the basis for the prepa-
ration of the C&I requirements specifications. For a large offshore project, the following typical philosophy documents may be necessary:
• Overall control and instrumentation philosophy
• Field instrumentation philosophy
• Process control system philosophy
• Emergency shutdown system/blowdown/process shutdown philosophy
• Fire and gas philosophy
• Metering philosophy
• Mechanical/electrical packages control philosophy
In an integrated safety and automation system, the following philosophies
may be combined into one philosophy document:
• Process control system philosophy
• Emergency shutdown system/blowdown/process shutdown philosophy
• Fire and gas philosophy
• Mechanical/electrical control philosophy
It is also possible to include field instrumentation philosophy in the overall
control and instrumentation philosophy. A philosophy document will normally
consist of the following sections:
• Introduction. This section fulfills the following purposes:
(1) the intent and a general description of the system are stated;
(2) the objectives are explained;
(3) general system requirements are highlighted; and
(4) applicable standards and codes and a list of abbreviations and
terminology are included.
• General Philosophy. The important features of the system are itemized.
The stated overall features are the means and criteria to help achieve
the objectives outlined in the introduction. This section should not
extend beyond one page.
• Overall Design. Functional requirements (e.g., control, monitoring,
management, and engineering) are described, then system topology is
explained.
• System Components. Communication, operation, control, management,
and auxiliary facilities are indicated.
• System Interfaces. The method of interfacing various subsystems with
the main control system is included.
• System Reliability and Availability. A brief description of reliability
and availability requirements and how they will be achieved is
presented.
• References. A list of support documents, some figures, and diagrams is
provided.