Guidelines for standardization—Part 8:Establishing principles and guidelines for use of stage code system
Some standard content:
ICS 01.120
National Standard of the People's Republic of China
GB/T 20000.8—2014
Guidelines for standardization-Part 8: Establishing principles and guidelines for use of stage code system[ISO Guide 69:I999, FHarmonized Stage Code system(Editian 2)-Principles and guidelines for use, MOD2014-12-31 Issued
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Standardization Administration of China
2015-06-01 Implementation
1 Scope
2 General principles of the phase code systembZxz.net
3 Structure of the phase code matrix
1 Guidelines for the use of the phase code system
5 Internal code development based on the phase code matrix Appendix A (Normative Appendix)
References·
Phase code system matrix
GB/T 20000.8—2014
GB/T 20000.8-2014
GB/T 20000 Guide to Standardization Work, GB/T 10000 Guide to Standardization Work, GB/T 10000 Guide to Standardization Work GB/T20001 "Rules for the preparation of standards", GB/T20002 "Drafting of specific contents in standards" and GB/T20003 "Special procedures for the formulation of standards" together constitute a basic series of national standards to support the formulation and revision of standards. GB/T20000 "Guide to standardization" is planned to be divided into the following parts: - Part 1: General terms for standardization and related activities; - Part 2: Adoption of international standards; - Part 3: Reference documents; - Part 4: General principles for the translation of national standards into English; - Part 5: General expressions for the English translation of national standards; - Part 6: Code of good practice for standardization; - Part 7 Demonstration and formulation of management system standards; - Part 8: Principles and guidelines for the use of the stage code system; - Part 9: Adoption of other international standardization documents. This part is Part 8 of GB/T20000. This part is in accordance with GB/T 1.1-2009. This part is revised and adopted the IS0 Guide 69:1999 Harmonized Phase Code System (2nd Edition) Principles and Guides for Use by the redrafting method.
This part is consistent with ISO Guide 69:1999 in structure I:. The main technical differences between this part and ISO Guide 69:1999 and their reasons are as follows: This part deletes the description of the principles of use of the phase code framework in international, regional and other national standard organizations in 2.3 of ISO Guide 69:1999, because this part only involves the principles and guidelines for the use of the coordinated phase codes in my country; - This part deletes the management content of the coordinated phase codes in 2.10 and Chapter 6 of ISO Guide 69:1999, because this part does not involve the relevant management provisions of standardization; This part deletes 5.8 of ISO Guide 69:1999 on the principles for the use of international, regional and other national organization code identification, because this part only involves the principles and guidelines for the use of the coordinated phase codes in my country. This part is under the jurisdiction of the National Technical Committee on Standardization Principles and Methods of Standardization (SAC/TC286). Drafting organizations of this part: China National Institute of Standardization, Metallurgical Industry Information Standards Research Institute, Mechanical Industry Instrumentation and Metering Comprehensive Technical and Economic Research Institute, China Quality Inspection Press (China Standards Press), Shenzhen Huace Testing Technology Co., Ltd., China Electronics Technology Standardization Research Institute.
Main drafters of this part: Wu Xuejing, Feng Zhenghu, Bai Dianyi, Zhang Ningchun, Ouyang Jinsong, Bai Demei, Liu Shenzhai, Lu Xilin, Zhu Ping, Xue Haining.
GB/T20000.8--2014
The standardization process consists of several clear steps or stages, which are used to describe the standardization and revision procedures or to indicate the stage of a standard plan. In general, the methods used by different standardization organizations to develop and publish standards through formal standardization procedures are very similar. Therefore, the standardization organizations can reach a consensus on the standardization procedures and the setting of each stage at a high level. However, the standards formulation and revision procedures of various standard organizations are different, which requires them to develop a stage system suitable for themselves. The development of so many systems can easily confuse standard users, so ISD has developed a coordinated stage code system (HSC) that all organizations can understand and use.
The establishment principles and matrix structure of the coordinated sequence code provided in this part can serve as the basis for various standard organizations in my country to establish their own program codes, develop standard project databases and publish standard formulation information to the outside. GB/T1.2 "Guidelines for Standardization Work Part 2: Standard Formulation Procedure" defines the stage division and code of the standard formulation procedure. This standard refers to the establishment principles and matrix structure of the program code in this part. It is based on the establishment principles and matrix structure of the program code specified in this part, and is a detailed arrangement made according to the situation of standard formulation in my country. It is mainly used for the information management of national standard formulation and revision. 1 Scope
Guidelines for Standardization
Part 8: Principles and guidelines for the use of phase code systems GB/T20000.8—2014
This part of GB/T20000 specifies the principles and guidelines for the use of a harmonized phase code system for a wide range of standards and databases. This part applies to standards bodies that use databases to track standard development projects and to exchange information between standards bodies on standard projects. 2 General principles of phase code systems
2.1 The purpose of establishing a harmonized phase code system is to provide a common framework for the transfer of core data between different standards bodies. Each standards body can establish its own phase system based on the core matrix of the harmonized phase code system. 2.2 Different users have different needs for the phase code system. Standards organizations need to establish a detailed system to properly monitor, analyze and control the entire standardization process. The general public should have an overview of the system in order to understand standardization work. The harmonized phase code system meets the needs of all parties by providing a matrix framework for the standardization process while allowing the details of standardization work to be integrated into it. 2.3 A common procedural framework for phase codes provides a matrix of coordinated phase code systems, see Appendix A. Phase code systems can be established on the basis of this framework, or new phase code systems can be established around this framework. 2.4 The phase code matrix organizes both items and decisions in the matrix, with some items having independent sub-items and some not. This organization is determined by the characteristics of the standard setting process, as each stage of the standard setting process involves decisions made during or after the activity. This eliminates the need to design separate fields to store decision information, and some information such as project status should be stored in other database fields.
2.5 Only designated codes in the framework can be used for effective data transmission. Other codes are for internal use only (see Chapter 5) and should not be transmitted to other organizations as database extracts.
2.6 Only certain nodes in the phase code matrix can occur. Those nodes that cannot occur are marked with a "-" in Appendix A. 2.7 The phase code system allows the development of specific projects to be tracked in the same way in databases at the international, regional and national levels. Therefore, the adoption of a standard at one level as an item at another level can be incorporated into the overall sequence of event codes, such as the adoption of an international standard as a national standard or the adoption of a regional standard as a national standard. 2.8 The framework of the phase code system given in Appendix A can be adapted to new procedures developed in the future. The overall process for developing standards is similar for each standards organization, so any changes to the existing process are likely to be the same. The code matrix can easily adapt to new requirements and even to the restructuring of the standard development process.
3 Structure of the phase code matrix
3.1 The matrix establishes a series of "phase" codes that represent the sequence of the standards development process to describe the main stages of the standards development process. Note: These "phases" are shared by different standards organizations. 3.2 Within each "phase\code", a series of\item\codes are established using a consistent logical concept system. The terms "phase" and "item" represent the vertical and horizontal axes of the matrix coordinates respectively. 3.3 The main phase codes and item codes are each coded with two digits from 00 to 90 in increments of 10. The standards organization may use the second non-zero digit to code possible sub-phases and sub-items in the standards development process. There are many insertions in the matrix of Appendix A using a second non-zero digit. Only items that do not end with the number "\" and have not yet been designated can be used freely. GB/T 20000.8-2014
3.4 Each cell in the matrix is coded with a four-digit number consisting of the coordinates of the phase and item, separated by a dot. For example, Table 10.20: Phase 10, Item 20. 3.5 All "Phase\" codes used in the technology are reserved for future use to allow the insertion of new phases that may be identified. 3.6 Item codes 10.30, 40, 50 and 80 are reserved for future use to allow the insertion of new items that may be identified. Item codes 30, 40 and 50 exist between the main activity items xx.20 and xx.60: - Some internal activities and/or nodes may be required between xx.20 and xx.60. Therefore, users may use item codes 30, 40 and 50 as internal codes for convenience. If these codes are needed in the main matrix in the future, users should modify their internal systems. If the activities between standards organizations become more consistent, there may be a requirement to modify internal systems.
3.7 Every standards development process contains a number of important nodes. These important nodes are key links in the standards development process. There are a number of common important nodes in the harmonized stage code matrix system that all standards bodies should identify. Other nodes can be used in the standards development process of individual standards bodies. The commonly used important nodes are 00.0010.00.20.00.40.20, 40.60, 50.20, 50.60.55.60, 60.60, 65.60, 90.20. These commonly used important nodes are marked as \M in the matrix. After the review stage, other commonly used important nodes are 90.60.91.60, 92.60.99.60. These nodes are marked as "m" in the matrix. Although other commonly used important nodes are also important nodes, they are optional like other nodes and do not need to be recorded if they are not applicable to the working methods of a certain standards organization. 4. Guidelines for the use of the phase code system
4.1 The commonly used phase codes given in Appendix A have a common meaning. Each standard Quasi-organizations can clearly identify the corresponding standard-setting procedures within their own organizations through the same phase codes. Therefore, as long as the semantics of the terms used internally by the standards organization are the same as the general meaning, the standards organization can rename the phase codes.
4.2 For different standards organizations, important phases and matters are different, so each standards organization is free to adopt phases and matters that are only applicable to itself.
4.3 Each phase code represents a standardization work, which may be the beginning or end of a standardization activity, or it may be a decision made based on a certain aspect of the standardization activity. Some codes can be regarded as important nodes in the entire formulation and revision cycle of the standard item.
4.4 Its related information (such as documents The source or document type should be recorded separately in other database fields and should not be reflected in the phase code.
4.5 Do not use subcodes to indicate that items are suspended at any particular stage. It is recommended that other database fields be used to handle this issue. 4.6 A coordinated phase code system takes into account the cyclical nature of the standards development process and also takes into account the possibility of repeating the current or earlier phases. Repeated items in the standard project development and revision cycle are recorded by repeating the same phase code. For example, if a decision is made to repeat a procedure due to an error in the operation of the procedure, item code xx.93 should be used; if a decision is made to redraft a document due to incorrectness, item code xx.92 should be used. Tracking phases should be recorded in other separate database numeric fields. 4.7 The return and suspension of standard items is a local operational issue of the phase code system. Item codes xx.92 and xx.93 are usually used to indicate the return of an item to any other point in the system; the suspension of a project is indicated by the phase code of the project or item code xx.91. Other codes may be used locally, and attention should be paid to the code once it is transferred. Information on suspended standard items should be recorded in other separate database fields.
4.8 The coordinated phase code system does not involve target and actual dates for the completion of a certain point. Other database fields should be used to record the target and/or actual dates associated with specific points. Each standards body should decide at which point to retain and maintain this information. 4.9 Once a project in the \00: New Project Proposal\ phase has begun, it should not be returned to the suspended state unless preparation is made for a complete re-evaluation of the project. 4.10 There is a distinction between work item types coded 20 to 60 (or 70) and decision items coded 90, because in practice the two can be clearly distinguished in time.
4.11 Only item code xx.60 indicates the end of the main work, and other item codes should not be used to indicate this meaning. However, in some stages, it is necessary to carry out some follow-up work after the main work is completed, such as distributing results. Item code xx.70 can be used to record this situation. - If the standard item is carried out to item xx.60 and (or) xx.70, the next item may be one of items 91 to 99, or it may be to enter the next appropriate stage. At any time, only one decision of item xx.90 can be selected. 4.12 "60: Publication phase" refers to the phase in which the standards body prepares for publication of the standard. "65: Implementation phase" refers to the phase in which the standards body implements the application of the standard by other standards bodies other than the standards body. 4.13 The use of item xx.90 is different from other items and requires a choice of decisions, so this item has a different design. If items xx.92 or xx.91 are used, it is generally considered that the next item should be xx.99. Note that the use of item xx.90 is optional for all other items.
4.14 The titles of the decisions selected in item xx.90 are usually as follows: -xx91 Decision to return the project;
--xx92 Decision to return to an earlier stage;
Decision to repeat this stage;
-. - xx.93
--xx.94 Decision to omit one or more stages: ---xx.95 (unassigned):
-xx.96 unassigned);
-xx.97 Decision to merge or split items; -xx.98 Decision to abandon items;
xx,99 Decision to register as the next applicable stage. The specific titles of different stages may vary slightly. 4.15 Matter *xx.94, decision to omit one or more stages" can be used to indicate a special process for items that have been determined. The actual process should be recorded in other database fields.
4.16 Stage 90: Review stage \ is associated with \91: Confirmation stage" *92: Revision stage \ *95: Glue withdrawal procedure \ and *99: Abolition stage \. Whether to use stage 91.92 or 95 (or 99) depends on the decision made in stage 90. Standards bodies with clear abolition procedures can use stages 95 and or) 99.
4.17 Records that have been cancelled or are no longer valid for some reason (relative to standards items) are retained in the database system. Separate database fields are usually used to record this information. If users wish to use a harmonized phase code to record this information, the special code 99.98 should be used, following the principles of item xx.98. Code 99.98 is not used for items that are formally postponed, cancelled or otherwise suspended (such items should be recorded using one of the other valid items xx.90). S Internal code development based on the phase code matrix 5.1 The harmonized phase code system is designed primarily for data transfer between standards bodies, but it can also be used internally by individual standards bodies.
5.2 If each body adds codes for internal use and uses the same code to mean different things, there may be disagreements between different standards bodies, but the impact of this will be minimal. The harmonized phase code matrix ensures that the main codes always have the same meaning and only the internal codes can have different meanings. The previous situation is that the same code can mean different phases in two standards bodies. 5.3 All standards organizations using the phase code matrix (including internal codes) should be aware that the coordinated phase code system may change in the future, and the internal codes should also change.
5.4 Individual organizations may add additional numbers for internal procedures that are not related to external units. One of the following two methods should be used: a) Expand some codes to the right to XX,XX,YY,Here YY is just an internal code; b) Use new items between xx.21 and xx.59, and items 30, 40 and 50 may be used (these items are not currently used and occur between the start and end of each stage of the main work). Note that the additional digital codes can only be used as internal codes and are not publicized. If these reserved codes are used for specific items in the future, the user should modify their internal system accordingly. 5.5 The use of codes between items xx20 and xx.60 or specific organization codes helps to incorporate the activities of professional organizations (such as working groups) into the system. Each standard organization can determine its internal code as needed, but it is not appropriate to set up specific stages for working group activities. 5.6 Try not to use reserved items (such as 80 learning stages) to represent various activities (such as editing). The items used by each standard organization in the future are used as internal codes. However, if these reserved codes are used for specific items in the future, the standard organization should modify its internal system accordingly.
5.7 Multi-agency projects (i.e. projects driven by more than one standards body, such as international standards bodies, regional and national standards bodies) should be recorded as either separate projects or as branches of the same project. In either case, they are separate entities and their own data sets and phase codes should be treated separately. It is not possible to track multi-agency projects with a single phase code (or other specific attribute) and keep records for all the agencies involved. 5.8 The harmonized phase code system is designed for sub-processes of the main phases and is not designed for specific tasks that occur at multiple points. These tasks include transmitting text, obtaining drafts, preparing tables, etc. These tasks occur between xx20 and xx60 and are part of a phase. Sub-items at these points can be defined as agency-specific codes and it is usually recommended that separate fields be created to store this information.
5.9 It is common for users of the harmonized phase code system to find it difficult to convert their own internal codes to the harmonized phase code system or to transfer harmonized phase codes to another system. When converting internal codes to a harmonized phase code system, it should be remembered that the vast majority of codes used by an organization are for internal use only. It is not necessary for users and other organizations to know those codes. Once this is recognized, it becomes easy to adapt the main codes to the matrix and develop nodes that are only used internally between the main activities xx20 to xx.60. Similarly, it is usually impossible to convert the core matrix back to the individual systems. Systems cannot be invalidated in this way. Remember that the purpose of establishing a harmonized phase code system is to facilitate the transfer of core data, not every detail. 4
The phase code system matrix is shown in Table A.1.
New project construction
00—*
Project proposal evaluation
Other stakeholders' evaluation
Drafting stage
Main work begins
Proposal begins
Distribute project proposals
Distribute evaluation proposals
Drafting begins
Appendix A
(Normative Appendix)
Phase code system matrix Matrix
Table A,1 Phase code system matrix
Work to be done! Further work
Proposal discussion
Evaluation completed
Evaluation results
Working group discussion
Draft completed
Work completed
Evaluation results
Evaluation results
GB/T20000.8—2014
100,91Decision to push back the project
1 00.92 -
00.93 Decision to redefine the project date
CO.97 Decision to merge or split the project
00.98 Decision to abandon the project
C0.99 Decision to register as the next applicable stage10.91 Decision to postpone the project
10.92 Decision to re-define the project date
10.94 Decision to omit one or more stages
10.97 Decision to merge or split the project
10.98 Decision to postpone, modify or abandon the project
10.99 Decision to register as the next applicable stage15.91 Decision to postpone the project
15.92 Decision to redefine the project
15.94 Decision to omit one or more stages
15.97 Decision to merge or split the project
15.98 Quick decision to abandon the project
15.99 Decision to register as the next application stage 20.91 Decision to postpone the project date
20.92 Decision to redefine the project
20.93 Decision to postpone the redrafting of the document
20.91 Decision to omit one or more price segments
20.97 Quick decision to split the project
20.98 Decision to abandon the project
20.99 Decision to register as the next application stage 5
GB/T 20000.8—2014
Soliciting opinions
Second round of soliciting
Review stage
Approval stage
Release stage
(Registration
Main work begins
Soliciting opinions begins
Soliciting opinions begins
Distributing review draft
Distributing formal approval draft
Distributing approval documents
Table A.1 (continued)
Main work
Progress work
Soliciting opinions and issuing opinions
Soliciting opinions 1 Distributing opinions
Review is over! Distributing results
Approval is over
Approval is over
Condensing results
30.91 Decision to postpone a project
30.92 Decision to return to the drafting stage or to redefine the project
30,91 Decision to omit one or more stages
30.97 Decision to postpone, merge or split a project
30,98 Decision to abandon a project
1 30,99 Decision to mark the project as the next applicable stage35.91 Decision to postpone a project
135.92 Decision to return to the drafting stage
35.94 Decision to omit one or more stages
135,97 Decision to merge or split a project
135,98 Decision to postpone the project
35,99 Decision to register as the next applicable stage
40.91 Decision to postpone the project
40.92 Decision to return to the draft stage or redefine the project
40.93 Decision to re-examine
40.91 Decision to omit one or more stages
40,97 Decision to merge or split the project
40.98 Decision to abandon the project
40.99 Decision to register as the next applicable stage50.91 Decision to withdraw the project
50,92 Decision to return to the draft stage
50.93 Decision to redistribute the formal approval documents50.94
50.98 Decision to abandon the project
50.99 Decision to register as the next applicable stage55.91
55,93
55,99 decided to enter the review stage7 For multi-agency projects (i.e. projects driven by more than one standards body, such as international standards bodies, regional and national standards bodies, etc.), these should be recorded as either separate projects or as branches of the same project. In either case, they are in fact separate entities and their own data sets and phase codes should be treated separately. It is not possible to track multi-agency projects with a single phase code (or other specific attribute) and keep records for all the agencies involved. 5.8 The harmonized phase code system is designed for sub-procedures of the main phases and is not designed for specific tasks that occur at multiple points. These tasks include transmitting text, obtaining drafts, preparing tables, etc. These tasks occur between xx20 and xx60 and are part of a phase. Sub-items of these points can be defined as agency-specific codes and it is usually recommended that separate fields be created to store this information.
5.9 It is common for users of the harmonized phase code system to find it difficult to convert their own internal codes to the harmonized phase code system or to transfer the harmonized phase codes to another system. When converting internal codes to a harmonized phase code system, it should be remembered that the vast majority of codes used by an organization are for internal use only. It is not necessary for users and other organizations to know those codes. Once this is recognized, it becomes easy to adapt the main codes to the matrix and develop nodes that are only used internally between the main activities xx20 to xx.60. Similarly, it is usually impossible to convert the core matrix back to the individual systems. Systems cannot be invalidated in this way. Remember that the purpose of establishing a harmonized phase code system is to facilitate the transfer of core data, not every detail. 4
The phase code system matrix is shown in Table A.1.
New project construction
00—*
Project proposal evaluation
Other stakeholders' evaluation
Drafting stage
Main work begins
Proposal begins
Distribute project proposals
Distribute evaluation proposals
Drafting begins
Appendix A
(Normative Appendix)
Phase code system matrix Matrix
Table A,1 Phase code system matrix
Work to be done! Further work
Proposal discussion
Evaluation completed
Evaluation results
Working group discussion
Draft completed
Work completed
Evaluation results
Evaluation results
GB/T20000.8—2014
100,91Decision to push back the project
1 00.92 -
00.93 Decision to redefine the project date
CO.97 Decision to merge or split the project
00.98 Decision to abandon the project
C0.99 Decision to register as the next applicable stage10.91 Decision to postpone the project
10.92 Decision to re-define the project date
10.94 Decision to omit one or more stages
10.97 Decision to merge or split the project
10.98 Decision to postpone, modify or abandon the project
10.99 Decision to register as the next applicable stage15.91 Decision to postpone the project
15.92 Decision to redefine the project
15.94 Decision to omit one or more stages
15.97 Decision to merge or split the project
15.98 Quick decision to abandon the project
15.99 Decision to register as the next application stage 20.91 Decision to postpone the project date
20.92 Decision to redefine the project
20.93 Decision to postpone the redrafting of the document
20.91 Decision to omit one or more price segments
20.97 Quick decision to split the project
20.98 Decision to abandon the project
20.99 Decision to register as the next application stage 5
GB/T 20000.8—2014
Soliciting opinions
Second round of soliciting
Review stage
Approval stage
Release stage
(Registration
Main work begins
Soliciting opinions begins
Soliciting opinions begins
Distributing review draft
Distributing formal approval draft
Distributing approval documents
Table A.1 (continued)
Main work
Progress work
Soliciting opinions and issuing opinions
Soliciting opinions 1 Distributing opinions
Review is over! Distributing results
Approval is over
Approval is over
Condensing results
30.91 Decision to postpone a project
30.92 Decision to return to the drafting stage or to redefine the project
30,91 Decision to omit one or more stages
30.97 Decision to postpone, merge or split a project
30,98 Decision to abandon a project
1 30,99 Decision to mark the project as the next applicable stage35.91 Decision to postpone a project
135.92 Decision to return to the drafting stage
35.94 Decision to omit one or more stages
135,97 Decision to merge or split a project
135,98 Decision to postpone the project
35,99 Decision to register as the next applicable stage
40.91 Decision to postpone the project
40.92 Decision to return to the draft stage or redefine the project
40.93 Decision to review
40.91 Decision to omit one or more stages
40,97 Decision to merge or split the project
40.98 Decision to abandon the project
40.99 Decision to register as the next applicable stage50.91 Decision to withdraw the project
50,92 Decision to return to the draft stage
50.93 Decision to redistribute the formal approval documents50.94
50.98 Decision to abandon the project
50.99 Decision to register as the next applicable stage55.91
55,93
55,99 decided to enter the review stage7 For multi-agency projects (i.e. projects driven by more than one standards body, such as international standards bodies, regional and national standards bodies, etc.), these should be recorded as either separate projects or as branches of the same project. In either case, they are in fact separate entities and their own data sets and phase codes should be treated separately. It is not possible to track multi-agency projects with a single phase code (or other specific attribute) and keep records for all the agencies involved. 5.8 The harmonized phase code system is designed for sub-procedures of the main phases and is not designed for specific tasks that occur at multiple points. These tasks include transmitting text, obtaining drafts, preparing tables, etc. These tasks occur between xx20 and xx60 and are part of a phase. Sub-items of these points can be defined as agency-specific codes and it is usually recommended that separate fields be created to store this information.
5.9 It is common for users of the harmonized phase code system to find it difficult to convert their own internal codes to the harmonized phase code system or to transfer the harmonized phase codes to another system. When converting internal codes to a harmonized phase code system, it should be remembered that the vast majority of codes used by an organization are for internal use only. It is not necessary for users and other organizations to know those codes. Once this is recognized, it becomes easy to adapt the main codes to the matrix and develop nodes that are only used internally between the main activities xx20 to xx.60. Similarly, it is usually impossible to convert the core matrix back to the individual systems. Systems cannot be invalidated in this way. Remember that the purpose of establishing a harmonized phase code system is to facilitate the transfer of core data, not every detail. 4
The phase code system matrix is shown in Table A.1.
New project construction
00—*
Project proposal evaluation
Other stakeholders' evaluation
Drafting stage
Main work begins
Proposal begins
Distribute project proposals
Distribute evaluation proposals
Drafting begins
Appendix A
(Normative Appendix)
Phase code system matrix Matrix
Table A,1 Phase code system matrix
Work to be done! Further work
Proposal discussion
Evaluation completed
Evaluation results
Working group discussion
Draft completed
Work completed
Evaluation results
Evaluation results
GB/T20000.8—2014
100,91Decision to push back the project
1 00.92 -
00.93 Decision to redefine the project date
CO.97 Decision to merge or split the project
00.98 Decision to abandon the project
C0.99 Decision to register as the next applicable stage10.91 Decision to postpone the project
10.92 Decision to re-define the project date
10.94 Decision to omit one or more stages
10.97 Decision to merge or split the project
10.98 Decision to postpone, modify or abandon the project
10.99 Decision to register as the next applicable stage15.91 Decision to postpone the project
15.92 Decision to redefine the project
15.94 Decision to omit one or more stages
15.97 Decision to merge or split the project
15.98 Quick decision to abandon the project
15.99 Decision to register as the next application stage 20.91 Decision to postpone the project date
20.92 Decision to redefine the project
20.93 Decision to postpone the redrafting of the document
20.91 Decision to omit one or more price segments
20.97 Quick decision to split the project
20.98 Decision to abandon the project
20.99 Decision to register as the next application stage 5
GB/T 20000.8—2014
Soliciting opinions
Second round of soliciting
Review stage
Approval stage
Release stage
(Registration
Main work begins
Soliciting opinions begins
Soliciting opinions begins
Distributing review draft
Distributing formal approval draft
Distributing approval documents
Table A.1 (continued)
Main work
Progress work
Soliciting opinions and issuing opinions
Soliciting opinions 1 Distributing opinions
Review is over! Distributing results
Approval is over
Approval is over
Condensing results
30.91 Decision to postpone a project
30.92 Decision to return to the drafting stage or to redefine the project
30,91 Decision to omit one or more stages
30.97 Decision to postpone, merge or split a project
30,98 Decision to abandon a project
1 30,99 Decision to mark the project as the next applicable stage35.91 Decision to postpone a project
135.92 Decision to return to the drafting stage
35.94 Decision to omit one or more stages
135,97 Decision to merge or split a project
135,98 Decision to postpone the project
35,99 Decision to register as the next applicable stage
40.91 Decision to postpone the project
40.92 Decision to return to the draft stage or redefine the project
40.93 Decision to review
40.91 Decision to omit one or more stages
40,97 Decision to merge or split the project
40.98 Decision to abandon the project
40.99 Decision to register as the next applicable stage50.91 Decision to withdraw the project
50,92 Decision to return to the draft stage
50.93 Decision to redistribute the formal approval documents50.94
50.98 Decision to abandon the project
50.99 Decision to register as the next applicable stage55.91
55,93
55,99 decided to enter the review stage99 Decision to register as the next applicable stage 10.91 Decision to postpone the project
10.92 Decision to redefine the project date
10.94 Decision to omit one or more stages
10.97 Decision to merge or split the project date
10.98 Decision to delay, modify or abandon the project
10,99 Decision to register as the next applicable stage 15.91 Decision to postpone the project
15,92 Decision to redefine the project
15.94 Decision to omit one or more stages
15,97 Decision to merge or split the project
15,98 Quick decision to abandon the project
15.99 Decision to register as the next application stage 20.91 Decision to postpone the project date
20.92 Decision to redefine the project
20.93 Decision to postpone the redrafting of the document
20.91 Decision to omit one or more price segments
20.97 Quick decision to split the project
20.98 Decision to abandon the project
20.99 Decision to register as the next application stage 5
GB/T 20000.8—2014
Soliciting opinions
Second round of soliciting
Review stage
Approval stage
Release stage
(Registration
Main work begins
Soliciting opinions begins
Soliciting opinions begins
Distributing review draft
Distributing formal approval draft
Distributing approval documents
Table A.1 (continued)
Main work
Progress work
Soliciting opinions and issuing opinions
Soliciting opinions 1 Distributing opinions
Review is over! Distributing results
Approval is over
Approval is over
Condensing results
30.91 Decision to postpone a project
30.92 Decision to return to the drafting stage or to redefine the project
30,91 Decision to omit one or more stages
30.97 Decision to postpone, merge or split a project
30,98 Decision to abandon a project
1 30,99 Decision to mark the project as the next applicable stage35.91 Decision to postpone a project
135.92 Decision to return to the drafting stage
35.94 Decision to omit one or more stages
135,97 Decision to merge or split a project
135,98 Decision to postpone the project
35,99 Decision to register as the next applicable stage
40.91 Decision to postpone the project
40.92 Decision to return to the draft stage or redefine the project
40.93 Decision to re-examine
40.91 Decision to omit one or more stages
40,97 Decision to merge or split the project
40.98 Decision to abandon the project
40.99 Decision to register as the next applicable stage50.91 Decision to withdraw the project
50,92 Decision to return to the draft stage
50.93 Decision to redistribute the formal approval documents50.94
50.98 Decision to abandon the project
50.99 Decision to register as the next applicable stage55.91
55,93
55,99 decided to enter the review stage99 Decision to register as the next applicable stage 10.91 Decision to postpone the project
10.92 Decision to redefine the project date
10.94 Decision to omit one or more stages
10.97 Decision to merge or split the project date
10.98 Decision to delay, modify or abandon the project
10,99 Decision to register as the next applicable stage 15.91 Decision to postpone the project
15,92 Decision to redefine the project
15.94 Decision to omit one or more stages
15,97 Decision to merge or split the project
15,98 Quick decision to abandon the project
15.99 Decision to register as the next application stage 20.91 Decision to postpone the project date
20.92 Decision to redefine the project
20.93 Decision to postpone the redrafting of the document
20.91 Decision to omit one or more price segments
20.97 Quick decision to split the project
20.98 Decision to abandon the project
20.99 Decision to register as the next application stage 5
GB/T 20000.8—2014
Soliciting opinions
Second round of soliciting
Review stage
Approval stage
Release stage
(Registration
Main work begins
Soliciting opinions begins
Soliciting opinions begins
Distributing review draft
Distributing formal approval draft
Distributing approval documents
Table A.1 (continued)
Main work
Progress work
Soliciting opinions and issuing opinions
Soliciting opinions 1 Distributing opinions
Review ends! Distributing results
Approval ends
Approval ends
Condensing results
30.91 Decision to postpone a project
30.92 Decision to return to the drafting stage or to redefine the project
30,91 Decision to omit one or more stages
30.97 Decision to postpone, merge or split a project
30,98 Decision to abandon a project
1 30,99 Decision to mark the project as the next applicable stage35.91 Decision to postpone a project
135.92 Decision to return to the drafting stage
35.94 Decision to omit one or more stages
135,97 Decision to merge or split a project
135,98 Decision to postpone the project
35,99 Decision to register as the next applicable stage
40.91 Decision to postpone the project
40.92 Decision to return to the draft stage or redefine the project
40.93 Decision to review
40.91 Decision to omit one or more stages
40,97 Decision to merge or split the project
40.98 Decision to abandon the project
40.99 Decision to register as the next applicable stage50.91 Decision to withdraw the project
50,92 Decision to return to the draft stage
50.93 Decision to redistribute the formal approval documents50.94
50.98 Decision to abandon the project
50.99 Decision to register as the next applicable stage55.91
55,93
55,99 decided to enter the review stage
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.