GOST34 - the main standard for the design of automated control systems

GOST34 - the main standard for the design of automated control systems

Description of the list of documentation according to the requirements of GOST 34.201.89

Since any production, to one degree or another, is associated with a risk to the environment or equipment, human life or health, the list of actions to create process automation is regulated by GOST. This documentation is simply called - GOST34

Below, the APCS documentation is presented for the organization of design work on the creation and maintenance of systems. Requirements for automated process control systems are laid down in these documents to determine the purpose of systems and their degree of safety. This list is a standard in the design of automation systems for oil refineries

1. System-Wide Solutions

P2. Explanatory note

P3. Description of automated functions

PM. Test program and methodology

PS. Passport

TP. Project sheet

FO. ED form. Statement of operational documents

2. Organizational support
I3. User guide

PV, SO. Description and organizational chart

3. Information Support
IN 1. List of DCS input and output signals

IN 2. List of input and output signals of the ESD system

AT 7. Database directory

I4. Instructions for the formation and maintenance of the database

P5. Description of the information support of the system

P6. Description of the infobase organization

P7. Description of classification and coding systems

P8. Description of historical data arrays (archives)

C9. Album of documents and video frames

4. Technical support
C4,C5. Connection diagrams for external wiring

C6. cable magazine

AT 4. Hardware Specification

IN. general view drawings of system cabinets and installation of technical equipment

IE. Instructions for use and maintenance of KTS

P9. Description of the complex of technical means

C1. Structural diagram of a complex of technical means

C7. APCS equipment layout plan at the facility

C8. Layout plan of equipment and wiring in the control room

5. Standard software
PA. Description of standard software

6. Application software
PB. Description of control algorithms and emergency protection

C12, C13. Block diagrams of DCS and ESD algorithms

C12. Block diagram of DCS system algorithms

SZ. Functional diagrams of automation

You can ask me for a sample of any of these documents.

How these standards work in practice:

When developing documentation for public and serious private customers, we usually have no choice - compliance with standards is included in the requirements for documenting technical specifications. In practice, I had to deal with various examples of misunderstanding of the structure of standards, what should be in the documents and why these documents are needed. As a result, such pearls sometimes come out from the pen of technical writers, analysts and specialists, that it is not clear in what state of consciousness they were written. But in fact, everything is quite simple. A search on Habr did not return links to more or less complete material on this topic, so I propose to fill in this annoying gap.

Taken from habrhabr:
In the 34 series in question, there are only 3 main standards for documentation:

GOST 34.602-89 Terms of reference for the creation of an automated system

The most beloved and popular standard for the development of technical specifications. The only thing you should not forget is that it is closely related to other standards of the series, and if you have received a technical specification made according to this standard, it is highly desirable to adhere to other standards, even if there are no direct requirements for this. At least in terms of a general ideology (which is discussed below)

GOST 34.201-89 Types, completeness and designations of documents when creating automated systems

This is a basic document that provides a complete list of GOST 34 documentation, recommendations for coding documents, which stages of the project the documents belong to (the stages are described in GOST 34.601-90), and also how they can be combined with each other.

In fact, this standard is a large table with comments. It can be driven into Excel for ease of use.

RD 50-34.698-90 Automated systems. Requirements for the content of documents

A voluminous standard describing the content of project documents with varying degrees of detail. The above-mentioned GOST 34.201-89 is used as an index.

There are many questions and interpretations of its provisions to the RD 50-34.698-90 standard, which, due to their vagueness, are often understood differently by the customer and the contractor or even members of the project team. But, unfortunately, we don't have anything more specific.