Some standard content:
GB/T19017
This standard is equivalent to the international standard ISO) 10007:1995 Quality and Management Technical Status Management Guide. This standard is a component of the GB/T19000 family of standards and is in full agreement with them. Appendix A of this standard is the standard appendix. Appendix B, Appendix C and Appendix D are all informative appendices. Considering that this standard is currently mainly used in the fields of industry and aerospace, where there are usually out-of-tolerance and no exemption, this standard translates "waiver" as "exceeding". This term is translated as "exclusive" in (iB/T6583 and other standards in the 1509000 family. The standard is proposed and managed by the National Technical Committee for Quality Management and Quality Assurance Standardization. This standard was drafted by the China Institute of Standardization and Information Classification and Coding. The participating units of this standard are: China National Accreditation Service for Quality Certification Bodies, the Seventh and Eighth Institute of China Aviation Industry Corporation, the China New Era Quality System Certification Center, and the China Institute of Electrical Technology Standardization. The main drafters of this standard are: Xu Yougang, Li Liang, Zhang Zhizhen, Cao Chun, Li Tienan, Zhengyan, and Xia Weidong. CB/T 19017—1997
ISO Preface
[ISO (International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of developing international standards is usually done by ISO technical committees. If a member body is interested in the work of a technical committee, it has the right to participate in the committee. International organizations (official or unofficial) that maintain ties with ISO may also participate in the work. In the field of electrotechnical standardization, ISO maintains a close cooperative relationship with the International Electrotechnical Commission (IEC). The draft international standards formally adopted by the technical committee are submitted to the member bodies for approval. International standards can only be formally adopted if they are approved by the member bodies with a voting rate of at least 75%. International Standard IS01000711S0/TC176/SC:2 Quality Management and Quality Assurance Technical Committee Quality System Branch has formulated this standard. Appendix A of this standard is an integral part of this standard: Appendix B, Appendix C and Appendix 1) are for reference only. GB/T 19017 This standard provides guidance on technical status management. Configuration management is a management discipline that applies to the entire life of a product to accurately describe the functional and physical characteristics of the product and provide corresponding control methods. The activities described in this standard are a means of meeting certain requirements of other standards in the ISO(9000) family. The purpose of this standard is to promote a common understanding of the discipline of configuration management and to promote the application of configuration management to transform their work: to standardize the configuration management methods throughout the industry and to promote national and international cooperation. 1 Scope
National Standard of the People's Republic of China
Quality management Configuration management Guide
Quality management Culdellnes For configuration manugement
GB/T 19017—1997
idt Is0 10007:1995
This standard provides guidance for the application of configuration management in industry and its interface with other management systems and procedures. This standard first gives a management overview (Chapter 4), and then describes the process, organization and detailed procedures. This standard applies to all activities that support product planning, design, development, procurement, production, installation, operation, maintenance and disposal. This standard details the technical status management elements in GH/T19004.1 (idl: IS0) 9001-1). Appendix B gives the corresponding relationship between this standard and GB/19 (I01 (idt1S09001), CB/T19002 (idtIS09002), G3/119003 (id11S09 (03) and GB/T19004.I (idtIS090011). The application of technical status management can be analyzed based on the scale, complexity and nature of the work. Tailored to suit specific daily requirements
Note 1 For guidance on special applications (e.g., hardware), see Appendix D for the relevant standards. 2 Cited standards
The following standards contain provisions that constitute the provisions of this standard through reference in this standard. When this standard was published, the versions shown were valid. All standards will be revised, and parties using this standard should explore the possibility of using the latest versions of the following standards. G3/6583--1994 Quality Management and Quality Assurance Terminology (idtIS08402:1994) GB/T1993 Quality System Audit Guide (idtISO10011-1:1990) GB/T 19021.2—93 Quality-based system audit guidelines Quality system auditor assessment criteria (idt IS (10011-2; 1991) GB/T19021.393 Quality system audit guidelines Audit management (idt IS) 10011-3: 1991) 3 Definitions
This standard adopts the definitions in GB/T6583 and the following definitions: 3.1 Technical status criteria
Product functional characteristics and physical characteristics specified in the technical documents and achieved in the product. 3-2 Technical status criteria Audit (Ca) Inspection to determine whether the technical status items conform to their technical status documents. 3.3 Technical status baseline The technical status of a product formally specified at a specific point in time, which is the reference for subsequent activities. 3.4 Technical status committee (B) A group composed of technical and management experts with the authority and responsibility to make decisions on the technical status and its management. Note 2 This group is usually called the technical status control committee (CCB). 3.5 Technical status control (cc) Activities carried out to control the changes to the technical status after the technical status document is formally confirmed. Approved by the State Administration of Technical Supervision on March 7, 1997 and implemented on August 1, 1997
GB/T 19017--1997
3 Control includes the evaluation, coordination, approval or disapproval of changes and the implementation of changes. 4 The implementation of changes includes engineering changes and the discussion of the deviations from the impact of the technical status on the product. 3.6 Technical status document configuration dncumeni: Documents necessary to determine the requirements, design, construction/production and verification of the technical status. NOTE 5 Documents may be in any form of media.
3.7 Technical status identification The activity of determining the product structure, selecting technical status items, documenting the physical and functional characteristics of the technical status items, as well as their interfaces and subsequent requirements, and assigning identifiers or codes to the technical status items and corresponding documents: 3.8 Technical status item configurationitrm(c) A collection of hardware, software, process materials, services or any of their individual parts that is designated for use in technical status management and treated as a single entity in the technical status management process.
3.9 Technical status management configurationirnrinnagenent (CM) Technical and management activities, including;
-Technical status identification;
Technical status control:
Technical status record;
Technical status audit
3.10 Technical status planranfiguratiuniainagcmcntplanCMP) The document that defines the organization and procedures for the technical status management of the product or item. 3.11 Technical status recordsLalusaccounting(CsA) The formal record report on the implementation status of the changes to the established technical status documents and the approved rescue. 3.12 Interfaceinterfac
The physical or functional relationship between technical status items at the interface. 4 Technical status management system, description and purpose 4.1 General
Technical status management is a management discipline that manages technical knowledge in the life cycle of product development, production and guarantee. This discipline can be applied to hardware, software, process materials, services and their related technical documents. Technical status management is an integral part of life cycle management (Appendix C gives a typical example). Other disciplines involved in the life cycle of a product (such as: document management, inspection and maintenance) contribute to the realization of the technical status management objectives. The main goal of technical status management is to fully reflect the current technical status of the product and its status in meeting physical and functional requirements and form documents. Another national standard for technical status management is the participation of research and development projects.The following clauses summarize the main elements of the technical status management system. 4.2 Overview 4.2.1 Technical status management process The technical status management process includes the following related activities: technical status identification; - technical status control; - technical status documentation; - technical status verification. This process is implemented in the fifth step to achieve the technical status management objectives required by GB/T 19017-1997. In order to achieve the technical status management objectives required by the company, a technical status management organization should be established, its responsibilities should be defined, and it should be given sufficient independence and limits.
These activities will be further described in Chapter 6. 4.2.3 Technical Condition Management Procedures and Technical Condition Management Plans Written procedures should be used to describe the company's policies, activities and practices related to the technical condition management process. In the technical condition management plan, the corresponding technical condition management policies, activities and practices to be used should be specified for specific programs or projects. The plan can refer to the company's standard technical condition management procedures. These activities will be further described in Chapter 7. 4.2.4 Technical Condition Management System Audits
To evaluate the compliance of the technical condition management system with the technical condition management procedures and plans, a technical condition management system audit should be carried out. These activities will be further described in Chapter 8. 5 Technical Condition Management System Audits
To evaluate the compliance of the technical condition management system with the technical condition management procedures and plans, a technical condition management system audit should be carried out. These activities will be further described in Chapter 8. Condition Management Process
5.1 General
The following describes the activities performed during the technical condition management process, which must be fully integrated for the process to be effective. Www.bzxZ.net
5.2 Technical Status Identification
Technical status identification includes the following activities:
5.2.1 Product structure and selection of technical status items The product structure shall describe the location of the technical status items and their relationships according to the decomposition of the product. During the decomposition of the product, the technical status items shall be selected using the technical status item selection guidelines (see 7.2.1): 5.2.2 Technical Status Prerequisites
All necessary functional and physical characteristics of the technical status item, including interfaces, changes, deviations and out-of-tolerances, shall be included. Clearly identified documents should be written. These documents are often classified as technical status documents. 5.2.3 Coding
The coding method should be specified and the technical status items and their components, parts and documents, interfaces, changes, deviations and out-of-tolerance traces should be identified. 5.2.4 Establishment of technical status baseline
The technical status baseline should be established at a specific point in time through formal agreement and will be used as the starting point for formal technical status control. The technical status baseline and the changes to it together constitute the current approved technical status. 5.3 Technical status control
All changes should be controlled after the technical status document is first issued. The impact of history, customer requirements and the affected technical status line will determine the extent of historical changes implemented and can serve as a basis for improvement. The basis of the classification/classification decomposition system. The following activities involved in the technical status control should be described in detail in the standard change control procedure document: - Document the changes and judge their correctness; - Evaluate the consequences of the changes; - Approve or disapprove the changes! - Implement and verify the changes; - Handle deviations and out-of-tolerances. To ensure the integrity of the technical status concept and provide a basis for political control, the technical status items, components and their documents should be kept under the following conditions: - Meet the required environmental conditions (such as the environmental conditions required by computer hardware, software, data, documents, drawings, etc.) to prevent unauthorized changes and private changes: - Provide methods for repairing damaged documents, GR/T 19017: 1997 - Be able to control the copies of the controlled originals of software, data, documents or drawings: - Ensure the consistency of the construction/production status of the technical status with the design status. 5.4 Technical Status Records
Technical status records should be made from the time when the technical status data is first generated. The technical status record should provide all technical status identification and information on deviations from the technical status baseline. Therefore, it can ensure the traceability of the technical status baseline changes.
Corresponding records and reports should be formed during the technical status identification and control activities. Redundant technical status records should be avoided. 5.5 Technical Status Audit
To ensure that the product meets the requirements of the contract and that the technical status document of the product accurately reflects the product, a technical status audit should be carried out before the technical status audit is approved (see requirements (). There are generally two types of technical status audits:
a) Functional technical status audit: a formal inspection to verify that the technical status item has achieved the performance and functional sustainability specified in the technical status document;
b) Physical technical status audit: a formal inspection to verify whether the manufacturing/production technical status of the technical status item is sufficient to comply with its product technical status document.
A technical status audit may be required for the formal acceptance of a certain technical status item. 6 Technical Status Management Organization
6.1 General
The technical status management period should be organized to maintain its impartiality, independence and integrity and achieve the specified technical status management objectives. 6.2 Structure of Technical Status Management
To ensure effective technical status management, its organizational structure should be specified. The organizational structure should usually be established according to the needs of the specific project and different life cycle stages. The structure should define the relationship between the various activities directly involved in the technical status management process, and should also include the technical status management function, interface organization, design, procurement and contract management departments, data management and manufacturing, quality assurance and other disciplines involved, including necessary subcontractors and vendors. The organizational structure of technical status management should ensure the coordination of technical status management activities with other activities and allocate authority and responsibilities for all technical status management activities appropriately.
The authority to approve the technical status baseline and any changes should be defined within a project organization (usually implemented by the "Technical Status Committee").
For small projects, the technical status management responsibility can be assigned by the project manager to specific personnel in the project. 7 Technical Status Management Procedures
7.1 General
This clause describes the procedures that constitute an effective technical status management system. The organization's technical status management system should be documented as a procedure referenced by the technical status management plan. The technical status management plan should define the procedures and levels of application related to the project during the product life cycle.
7.2 Technical Status Identification Procedure
7.2.1 Selection of Technical Status Items
Technical status items are selected through a decomposition process. This top-down process decomposes the entire product structure into logically related and subordinate hardware, components, process materials, services or their combined contents for technical status management. The selection of higher-level technical status items should be carried out in the initial stages of the project (such as feasibility analysis and definition stages). The selection of lower-level technical status items should be completed in the early development stage.
GB/T 19017—1997
The technical status items should be selected using the corresponding guidance criteria. Too many technical status items will affect the overall understanding of the product, hinder management and increase costs; too few technical status items or insufficient decomposition of the product will increase logistics, maintenance and management difficulties. The primary criterion is to select technical status items whose performance parameters and physical characteristics can be individually processed to achieve their final performance. Other selection criteria that should be used are:
Importance in terms of high risk, safety, mission effectiveness, etc.;
New or modified technology, design or development, interface with other technical status items:
-Procurement conditions;
-Logistics and maintenance conditions.
7.2.2 Technical status item documentation
All physical and functional characteristics necessary to determine the technical status item throughout its life cycle shall be documented.
Type of document - generally includes; specifications, design documents, checklists, software data and user and maintenance manuals. The documentation required for the technical status item depends on the level of control required, however all documents should include information on changes and traceability
7.2.3 Coding method
A coding method should be specified and used to identify technical status items, technical status documents and changes to parts and components. The coding method should take into account the organization's or supplier's existing coding procedures. However, the identification code must be unique. The coding method or other information management system should be able to manage: - the hierarchical relationship or affiliation between technical status items within the product structure; - the hierarchical affiliation of basic components in each technical status item - the difference between technical status items and documents; - the relationship between document changes; - the structure of the document; - other requirements. 7.2. 4 Technical,Technical Status Baseline
The Technical Status Baseline consists of all approved documents that define the product at a specific point in time. During the product life cycle, when it is necessary to define a technical status concept as a reference starting point for further development, a Technical Status Baseline should be established.
The level of detail specified in the product status baseline depends on the level of control required. For example, a functional technical status baseline may consist of only one document, while a production technical status baseline may include a complete set of documents, including documentation of tools and processes. 7.3 Status Committee
The project manager may establish a status committee with specific authority to review and approve/disapprove the status management plan, the status management procedures, the selection of status items, the status baseline and changes to the status line, including deviations and out-of-tolerances. The members of the Technical Status Committee are usually appointed by the Project Manager. The Technical Status Committee should include representatives of all necessary professional departments. The Technical Status Committee should be chaired by the Project Manager or his agent. The Technical Status Management Committee may include different levels of authority. If the customer is required to participate in the Technical Status Management process according to the contract requirements, the customer may also establish a Technical Status Committee. The functions of the Technical Status Committee are to verify that: - the Technical Status Committee has appropriate authority over the relevant Technical Status Baseline: - changes are necessary; - the results are acceptable; - the changes have been properly documented and classified; and - the implementation plan for the document, hardware and/or software changes is satisfactory. 7.4 Technical Status Control Procedure
7.4.1 Determine the need for changes and document them. Change proposals can be made by the organization, customers, subcontractors or suppliers. All change proposals should be documented before being submitted to the Technical Status Committee, usually including the following information: 1. The name of the technical status item to be changed and the revision status of the relevant document; 2. The name, organization and date of the person proposing the change; 3. The reason for the change; 4. The urgency of the change. It is recommended to fill in the above information on a standard form and use this form as the basis for the change process. In order to facilitate traceability and identification, it is recommended to assign a unique identification code to each change proposal from the beginning. The status of the change process and the decisions and treatments… may include other information such as classification and priority to explain the change process. 7.4.2 Evaluation of Changes
The proposed change should be evaluated and documented as follows: Technical advantages of the proposed change,
Impact on versatility, connectivity, and the need for reconfirmation;
Impact on contracts, schedules, and costs;
Impact on manufacturing, testing, and inspection methods;
Impact on procurement and inventory;
Impact on maintenance, user schedules, and parts and spare parts manuals. The above evaluation criteria may be tailored to the complexity of the product. 7.4.3 Approval of Changes
After the change is evaluated, a team of authorized personnel shall review the documented evaluation results and make a decision on who to approve/not approve.
The change procedure shall define the authority and mode of operation of the relevant personnel. The authority to approve/not approve the change may vary, depending on the importance of the change. The decision on approval/disapproval shall be documented and communicated to the relevant areas. 7.4.4 Implementation and verification of changes
The implementation and verification of an approved change shall normally include the following steps: Changes to the technical status identification shall be approved by the official; The affected department shall take appropriate corresponding measures: Conformity verification shall be carried out (design test, design, etc.). 7.5 Technical status documentation procedure
7.5.1 General
Appropriate identification and change control are the prerequisites for correct technical status documentation. The technical status documentation reports the management points of the technical status management process and related activities. It starts with the first technical status document and continues throughout the life cycle of the product. 7.5.2 Records
During the technical status identification and control process, the technical status documentation records selected information. The technical status record provides visibility and traceability for the effective management of the technical status progress process. The following types of information should usually be reported: identification
(component file)
GB/T 19017-1997
Development and/or specification sequence
Development status
Implementation status
(design, rapid progress and production reliability)
|Separation and benefits
Technical status basis
-Technical status items
In order to provide the required report, the above information should be recorded in a way that can be referenced to reflect their mutual relationship. 7.5.3 Reports
For management needs, different types of reports should be issued regularly. Reports usually include:
- List of technical status baseline documents;
- List of technical status items and their baselines;
- Current technical status (such as "designed\or\built/produced"); - Status reports of changes, deviations and deviations: Status reports of change implementation and verification.
The above reports can be issued for technical status items or the entire product. Reports can be made manually or by computer systems. 7.6 Technical Status Review Procedure
Technical status reviews should be carried out according to a documented and agreed procedure, including the required recording and reporting methods. Functional technical status audit is to identify the various functions and performance requirements of the technical status items in the functional technical status line, and confirm that these requirements have been met by checking the evaluation documents, inspection and test records. Physical technical status audit is to check the "built, produced, and tested products" according to the product's technical status documents to ensure their compliance. This review (together with the functional technical status audit) confirms that the product (as defined by the technical status documents) meets the functional and physical requirements. Usually, each technical status is audited once, or it can be audited level by level (see Appendix ( ), the technical status management plan shall not replace other forms of review, testing or inspection for the conformity or delivery delay of the project. 7.7 Technical status management plan
The organization shall formulate a technical status management plan for the project or cooperation. The technical status management plan provides each subcontractor with the technical status management procedures to be used and specifies who will perform these procedures and when. In the case of multiple layers, the main contractor's technical status management plan is usually a plan, and each subcontractor shall formulate its own plan. These plans may be issued as independent documents or included in the main contractor's technical status management plan. The customer should also prepare a configuration management plan to describe the customer's participation in the contractor's configuration management work. The basic requirement for the configuration management plan is that all plans should be compatible and they should together describe the configuration management system that will serve as the basis for configuration management practices in subsequent stages of the project.
The configuration management plan can be a management document required by the contract and should itself be subject to a document control procedure. To keep the plan simple and avoid duplication, the organization should use existing procedures to prepare the plan whenever possible. Appendix A Recommended technical status management system audits are given. Technical status management system audits
GB/T19017—1997
Organizations should conduct technical status management system audits according to documented procedures to: verify that the technical status management system is effective and meets the specified requirements; determine the compliance of the technical status management practices with the procedures in the corresponding technical status management plan. The audit can be initiated by the quality assurance department, the customer or the technical status department, depending on the specific contract situation. Principles of annual audit of the technical status management system.The recommendation and implementation shall comply with the relevant requirements of GB/T 19021 (IDIS) 10011). 41 Introduction
GB/T 19017—1997
(Annex to the standard)
The recommended structure and content of the technical condition management plan should generally give the following basic information: Description of the system or technical condition items to which the plan applies Provide a time schedule for important technical condition management activities: 1. The purpose and scope of the technical condition management plan; 2. Related documents (such as the technical condition management plans of suppliers and contractors, which are closely related to the relevant technical condition management plan):
1. Applicable documents and their implementation procedures
A2 Policy and procedures
This chapter should include the technical condition management requirements agreed with the customer or subcontractor and the implementation process. These elements provide the basis for the technical condition management activities within the scope of the contract. Its contents include: 1. The policy and relevant management system of technical status management practice; 2. The responsibilities of the technical and status management organization and the technical status committee, committee members, small correction or supplier consultants and other relevant organizations; 3. The agreed selection criteria of technical status items; 4. The frequency, distribution and control of internal reports and reports provided by customers; 5. The agreed terminology.
A3 Technical Status Identification
The technical chapter should include:
The relationship tree of technical status, specifications and other top-level documents; 6. The coding method used for the current specifications, diagrams and changes! 7. The established technical status test line, progress and referenced document types; 8. The use and allocation of series codes or other traceable identification: 9. The issuance sequence.
A4 Technical Status Control
This competition shall include
The organization, composition and charter of the technical status committee and the relationship with the technical status committee organized by the customer or subcontractor
Establish a change control procedure before the technical status line is established according to the contract: the procedure for handling changes, which involves the process from the submission of the technical status item content to the confirmation after the implementation of the change (including changes proposed by the customer, also including changes proposed by the organization or suppliers] A5 Technical Status Record
This competition shall create evidence
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.