Configuration Management System. Contractor shall maintain accurate, thorough and current records throughout the performance of the Work. A single Configuration Management system shall apply to all material furnished irrespective of its origin. All Technical Documentation shall be identified by title, number, issue, revision and date. All documents shall carry a configuration identity. The Configuration Management system shall include: (a) Identification of and documentation of the physical and functional characteristics of components and systems as defined by technical information including functional schematics, physical schematics, applicable standards, software flow diagrams, software architecture, software source code, drawings, layouts, plans, specifications, specification control drawings, and both maintenance and operating manuals; (b) A means to search out associated documents, including next higher and lower levels, assembly level, specifications, software, and documents; (c) Drawing trees for all major systems and subsystems, with drawing identities reserved by groups; (d) Specification and process trees for all major systems and subsystems, with engineering unit description identities reserved by groups; (e) Change control procedures, wherein the approval status of any document can be determined; (f) Identification of completed incorporated changes; (g) Posting of pending changes against any document; and (h) Identification of the effect on manufacturing for any changed document. The following principles shall be incorporated in the Configuration Management system:
Appears in 2 contracts
Sources: General Provisions Agreement, California High Speed Train Project Agreement
Configuration Management System. β Contractor shall maintain accurate, thorough and current records throughout the performance of the Work. A single Configuration Management system System shall apply to all material furnished irrespective of its origin. All Technical Documentation shall be identified by title, number, issue, revision and date. All documents shall carry a configuration identity. The Configuration Management system System shall include:
(a) Identification of and documentation of the physical and functional characteristics of components and systems Systems as defined by technical information including functional schematics, physical schematics, applicable standards, software flow diagrams, software architecture, software source code, drawings, layouts, plans, specifications, specification control drawings, and both maintenance and operating manuals;
(b) A means to search out associated documents, including next higher and lower levels, assembly level, specifications, software, and documents;
(c) Drawing trees for all major systems Systems and subsystemsSubsystems, with drawing identities reserved by groups;
(d) Specification and process trees for all major systems Systems and subsystemsSubsystems, with engineering unit description identities reserved by groups;
(e) Change control procedures, wherein the approval status of any document can be determined;
(f) Identification of completed incorporated changes;
(g) Posting of pending changes against any document; and
(h) Identification of the effect on manufacturing for any changed document. The following principles shall be incorporated in the Configuration Management systemSystem:
Appears in 1 contract
Sources: Trainset Agreement