Some standard content:
National Standard of the People's Republic of China
Network Planning Technology
General Rules for Representing Network Diagrams
Cenerale rule for representing non network planning techniques GB/T 13400.292
Network diagrams are the basis of network planning techniques. In practical applications, the logical relationships among many specific tasks and the tasks, i.e., the inter-connections and inter-constraints in terms of production and organization, are arranged in a sequential order according to the direction of the process and expressed visually with graphics. Provisions are made for the representation of network diagrams to facilitate their unified application. Subject Content and Applicable Examples
This standard specifies the general drawing and identification of network diagrams in network planning techniques. This standard applies to the preparation of network diagrams of network planning technology in planning management work 2 Reference standards
Network planning technology
CB/T 13400.1
3 Graphic drawing method
Common techniques
3.1 The basic form of graphic names and graphic symbols should comply with the provisions of Table 1. Table 1 Basic form of graphic symbols
Graphic name
Virtual energy line
Basic form of graphic symbols
The basic form of graphic symbols used in network diagrams is shown in Table 2. 3.2
Table 2 Basic forms and forms of graphic symbols used in network diagrams
Double code
Issued by the State Administration of Technical Supervision on February 26, 1992 Remarks
Circular is preferred
Horizontal orientation is preferred
Horizontal orientation is preferred
Single code
Implemented on December 1, 1992
Logical relationship
3.3 Identification of network diagrams
GB/T 13400.292
Continued Table 2
Double code
3.3.1 Identification may be determined according to application needs. The following 3.3.1.2 to 3.3.1.3 are for selection when making diagrams. 3.3.1.1 Graphic structure and graphic symbols
: Work and events (text description or letter code or digital number) b.
Predecessor work and or) subsequent work or starting point and completion event: logical relationship.
3.3.1.2 Time parameters
3. 3. 1. 3
Work duration DD
Earliest time of node ET: i, ET: F
Latest time of node LT-LT: +
Earliest start time ES; ES,
Earliest finish time EF..EF.t
Latest start time LS, -i+LS:
Latest finish time LF, LF,
Total time difference TF., TF.
Free time difference FF, -r+FF,.
Cost identification
Cost increase rate α
Resource intensity.
3.3.2 Identification with descriptive fonts. Identification with descriptive fonts should preferably be written in horizontal direction. If the arrow line is drawn vertically downward or vertically upward, the work name should be written on the left side of the arrow line, and the work duration should be written on the right side of the arrow line. 3.3.2.1 An example of double-code network diagram identification is shown in Figure 1. 3.3.2.2 An example of single-code network diagram identification is shown in Figure 2.3.4 Time coordinate drawing method
3.4.1 The time coordinate is a time length mark. The time unit in the time coordinate is determined according to needs before the network plan is prepared. It can be minutes, hours, days, weeks, months, quarters, years, etc. 3.4.2 The time coordinate should be marked at the top and bottom of the drawing; when the drawing is small, it is also allowed to mark only at the top. 3.4.3 For projects with a long period, the work duration should also be marked on the work arrow line of the time coordinate network diagram. 3.4.4 Examples of time coordinate drawing methods are shown in Table 3.
. Work name
Work duration
Node number
Work name
Work duration
Time (time unit)
Time (time unit)
3.5 Basic rules for network diagram drawing
GB/T13400.2—92
Table 3 Examples of time coordinate drawing methods
3.5.1 The diagram must be drawn according to the logical relationship of the work. It should be simple and easy to read and process technically. Work
Special example
Work duration
3.5.2 The network diagram must contain clear identification that can indicate basic information. Identification can be letter code or number. It is allowed to start a separate table to give a detailed description of the identification.
3.5.3 The letter code or digital number of the work or event shall not be repeated in the network diagram of the same task. 3.5.4 The network diagram is generally allowed to have only one starting node and one ending node. When a single-code network diagram has multiple starting and multiple ending tasks, a virtual task should be set at both ends of the network diagram as the starting node and the whole point node of the network diagram, as shown in Figure 3. Point
GB/T13400.2—92
3.5.5 The network diagram is directed. In the network diagram of the affirmative network plan, closed loops are not allowed. 3.5.6 The main direction of the network diagram is from the starting node to the ending node. When drawing the network diagram, the horizontal direction from left to right should be preferred.
The direction of the arrow line must give priority to the direction corresponding to the soil direction, or the direction perpendicular to the main direction. 3.5.7
3.5.8 When drawing a network diagram, try to avoid crossing with lines. When the crossing of screen lines is unavoidable, only the "bridge" drawing method or pointing drawing method is allowed, as shown in Figure 4.
Bridge drawing method
h Finger drawing method
GB/T13400.2—92
3.5.9 Except for the starting node and the end node, all other nodes must be connected by arrows or virtual arrows. 3.5.10 The arrow representing the work must have event nodes at both the beginning and the end. That is, there can only be one work between two event nodes. 3.5.11 If the same network diagram needs to be represented by more than two drawings, the connection of the disconnected parts should be indicated or explained at the connection point. 3.6 Simplified drawing method
3.6.1 Busbar method, as shown in Figure 5.
3.6.2 The time distance mark in the overlap network diagram is shown in Figure 6. STS3
3.7 Special marking
3.7.1 Marking of key lines. Key lines should be marked with special lines, as shown in Figure 7. Single number
Dual energy line
Black front line
Dual code
3.7.2 Marking of virtual work. When the virtual line is very short and difficult to represent in drawing, the arrow line with the duration of the work can be used as shown in Figure 8
GB/T 13400.2—92
3.7.3 Indication of special requirements, using the form of Figure 9 Single number
In non-ice conditions
3.7.4 Marking of actual conditions
Dual code
In non-ice conditions
Injection mixed load
For each work that has been started, its implementation status should be explained with obvious markings. For example, for the work that has been started, the nodes and arrows are painted with transparent colors.
3.8 Representation of logical relationships
The logical relationships in the network diagram should be as shown in Table 4. Table 4 Methods of expressing logical relations
Avoiding logical relations
After A is completed, proceed to B,
After B is completed, proceed to Cwww.bzxz.net
After A is completed, proceed to both
B and C at the same time
After both A and B are completed
Proceed to C
Both A and B are completed
Proceed to C and D at the same time
After A is completed, proceed to C,
After both A and B are completed, proceed
Double code expression method
Single code expression method
Avoiding logical relations
After both A and B are completed, proceed to
CB and D after the completion
After A is completed, proceed to C,
After both A and B are completed, proceed to D,
T After completion, proceed to E
A, B two works to be carried out successively, each divided into two sections
. A, after completion, proceed to AB. After completion of A., proceed to As, B2B1, proceed to Bz. After completion of As, Bz, proceed to GB/T13400.2—92
Continued Table 4
Double code representation method
3. 9 Supplementary drawing method for non-definitive logical relationship nodes, as shown in Table 5 and Table 6,As shown in Table 7, 3.9.1* and “relationship”
Table 5 ^and “relationship”
Working system
Input relationship
Output relationship
“OR” relationship
Input relationship
Output system
A, and A. After A is completed, B executes
After A is completed, B and B, and B, execute
Table 6 "OR" relationship
Operation relationship
A, or A. Or A, one of them is completed, B executes A after completion. Decision B, or B, executes single code expression method
3. 9. 3 "XOR" relationship
Input relationship
Output relationship
Additional instructions:
GB/T 13400. 292
Operation relationship
"XOR" relationship
A: With A, with A, one and only one of them is completed, B executes
After A is completed, decision H, There is one and only one implementation in B and C.
This standard is proposed by the State Administration of Technical Supervision and is under the jurisdiction of the China Institute of Standardization and Information Classification and Coding!
This standard is drafted by the Liaoning Provincial Standard Information Research Institute, the China Architecture Society Coordination Management Research Institute, and the China Institute of Standardization and Information Classification and Coding.
The main drafters of this standard are Ben Liwei, Gan Shaoxi, Li Xiaolin, Zhao Keling, and Tu Shuyang.
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.