Common use of Configuration Management Reporting Clause in Contracts

Configuration Management Reporting. Service Provider’s responsibilities include: 1. Provide a monthly report on configuration Changes made to the infrastructure, Equipment, and Software. 2. Provide a monthly report in a format agreed by DIR, to include: 2.1. Number and classification of configuration Changes made. 2.2. Trend analysis of the configuration Changes made during the thirteen (13) most recent months. 3. Provide a report within ten (10) Business Days of completion of a validation effort, as part of the Configuration Management Validation Plan, covering at a minimum: 3.1. Number of differences between the records and validation effort findings. 3.2. Number of occasions on which a configuration was found to be unauthorized. 3.3. Recommended corrective actions to Resolve any process deficiencies or failures identified. 3.4. Number of occasions on which a recorded CI could not be located. 3.5. Statistical information about the structure and composition of the Equipment and Software. 4. Provide monthly exception reports which articulate the following: 4.1. Number of instances where configuration information in the CMS / CMDB was discovered to be incorrect (e.g. when being used to execute support and delivery activities, and activities of other processes). 4.2. Details of the Exception Reports created as a result of the configuration validation. 4.3. Details regarding instances in which configuration policies and procedures have been violated. 5. Provide reports regarding Configuration Items and configurations as requested by DIR and DIR Customers. 6. Provide Portal access to the CMS / CMDB for authorized DIR and DIR Customer ad hoc reporting, including access to the data dictionary and user documentation.

Configuration Management Reporting. Service Provider’s Provider responsibilities include: 1. Provide a monthly report on configuration Changes made to the infrastructure, Equipment, and Software. 2. Provide a monthly report in a format agreed by DIR, to include: 2.1. Number and classification of configuration Changes made. 2.2. Trend analysis of the configuration Changes made during the thirteen (13) most recent months. 3. Provide a report within ten (10) Business Days of completion of a validation effort, as part of the Configuration Management Validation Plan, covering at a minimum: 3.1. Number of differences between the records and validation effort findings. 3.2. Number of occasions on which a configuration was found to be unauthorized. 3.3. Recommended corrective actions to Resolve resolve any process deficiencies or failures identified. 3.4. Number of occasions on which a recorded CI could not be located. 3.5. Statistical information about the structure and composition of the Equipment and Software. 4. Provide monthly exception reports which articulate the following: 4.1. Number of instances where configuration information in the CMS / CMDB was discovered to be incorrect (e.g. when being used to execute support and delivery activities, and activities of other processes). 4.2. Details of the Exception Reports created as a result of the configuration validation. 4.3. Details regarding instances in which configuration policies and procedures have been violated. 5. Provide reports regarding Configuration Items CIs and configurations as requested by DIR and DIR Customers. 6. Provide Portal access to Enable reporting capability from the CMS / CMDB MSI with reasonably current data (and with unrestricted query length and depth) for authorized DIR and DIR Customer ad hoc reportinguse by Authorized Users in the generation of sophisticated, including access to the data dictionary and user documentationcustom reports.