Configuration Management System Sample Clauses
The Configuration Management System clause establishes the requirement for maintaining a structured process to identify, control, and track changes to project deliverables and documentation. In practice, this involves using tools or procedures to record configuration items, manage version control, and ensure that all modifications are properly reviewed and authorized. The core function of this clause is to ensure consistency and traceability throughout the project lifecycle, reducing the risk of errors and miscommunication caused by uncontrolled changes.
POPULAR SAMPLE Copied 1 times
Configuration Management System. Service Provider’s responsibilities include:
1. Provide and maintain a CMS / CMDB that will serve as the single source of information regarding all Configuration Items for Service Provider Services, other Service Component Provider(s) Services, and designated Third Party Vendors.
1.1. Provide access to the CMS / CMDB to other Service Component Provider(s), DIR, DIR Customers, and authorized Third Party Vendors, which access shall include all appropriate and required licenses and/or interfaces.
2. Ensure that all Configuration data related to the Services resides in the CMS / CMDB.
3. Integrate the CMS / CMDB with other systems for Service Management, including Incident Management, Problem Management, Change Management, and Release Management.
4. Integrate the CMS / CMDB with the Configuration Management Systems of other Service Component Provider(s) and designated Third Party Vendors.
4.1. Integrate the CMDB with the Configuration Management Databases of other Service Component Provider(s), and designated Third Party Vendor(s), as directed by DIR.
4.2. Enable interfaces to integrate with the CMS / CMDB of other Service Component Provider(s), DIR, DIR Customers and authorized Third Party Vendors, as directed by DIR.
5. Limit access to the CMS / CMDB to the agreed levels (e.g. by DIR Customer) for the type of Authorized Users who require access to the systems.
6. Provide Service Provider personnel, other Service Component Provider(s) personnel, DIR, DIR Customers and authorized Third Party Vendors with appropriate training in using the CMS / CMDB.
7. Grant DIR and DIR Customers access to the database(s) of the CMS / CMDB, and allow DIR to monitor and view on an ongoing basis.
8. The CMS / CMDB shall at a minimum support the following:
8.1. Maintain the relationships between all service components and any related incidents, problems, known errors, change and release documentation.
8.2. Provide a customizable set of views for different stakeholders through the service lifecycle.
8.3. Consolidate data from several physical CMDBs as necessary, which together constitute a federated CMS.
8.4. Automate processes, discovery tools, inventory and validation tools, enterprise systems and network management tools, etc. to load and update the CMS / CMDB.
8.5. Mapping of logical information to physical assets (e.g. Applications, software, DR RTO/RPO, Billing Field, virtual server instance associations with physical hosts)
9. Maintain the CMS / CMDB to meet performance sta...
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:
Configuration Management System. Service Provider responsibilities include:
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 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 management and maintenance 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:
(a) Changes will not be initiated without affected party review;
(b) A change board will be established;
(c) A materials review board will be established;
(d) At the time of submittal of as-built drawings, incorporation of changes can be verified by inspection or demonstration; and
(e) Records of change assessment will be kept. Contractor shall keep history logs, including photographic progress records, for the Project and for all Principal Design Units. The history logs are to identify all the parts, the associated part, drawing, or identity, with change level applicable. History logs are to accompany items shipped for installation and be updated after installation and as as-built drawings. Contractor is required to close the history log with a set of as- built or as-installed documentation including all internal interfaces and those external interfaces affecting the Work. Once a history log is complete, Contractor shall submit the completed history log to Authority for review and acceptance.