Bright House Networks Information Services ... - AT&T Clec Online

Region Performance Metrics Change Management
Section 11: Change Management
CM-1: Timeliness of Change Management Notices
Definition
Measures whether CLECs receive required software release notices on time to prepare for AT&T interface/system changes so CLEC
interfaces are not impaired by change.
Exclusions
Changes to release dates for reasons outside AT&T control, such as the system software vendor changes. For example: a patch to
fix a software problem.
Type 6 Change Requests (Defects/Expedites), as defined by the Change Control Process (CCP)
Business Rules
This metric is designed to measure the percent of change management notices sent to the CLECs according to notification standards
and time frames set forth in the Change Control Process. The CCP is used by AT&T and the CLECs to manage requested changes to
the AT&T Local Interfaces.
The clock starts on the notification date. The clock stops on the software release date. When project events occur (scope changes,
analysis information, etc.), the software release date may change. A revised notification would be required and the clock would
restart. Based on release constraints for defects/expedites, notification may be less than the agreed upon interval in the CCP for new
features.
Calculation
Timeliness of Change Management Notices = (a / b) X 100
a = Total number of Change Management Notifications Sent Within Required Timeframes
b = Total Number of Change Management Notifications Sent
Report Structure
AT&T Aggregate
Data Retained
Report Period
Notice Date
Release Date
SQM Disaggregation - Analog/Benchmark
SQM Level of Disaggregation SQM Analog/Benchmark
Region 95% >= 30 Days of Release
SEEM Measure
Yes
SEEM Disaggregation - Analog/Benchmark
SEEM Measure
Tier I
Tier II X
SEEM Disaggregation SEEM Analog/Benchmark
Region 95% >= 30 Days of Release
Version 0.06 11-4 Issue Date: June 4, 2002
RGN-005-122101
CCCS 341 of 369