Archived System CR 30623 Detail |
| Title: On time jeopardy notification improvements. | |||||
| CR Number |
Current Status Date |
Level of Effort |
Interface/ Release No. |
Area Impacted |
Products Impacted |
|
|
|||||
| 30623 |
Completed 7/18/2002 |
5500 - 8000 | 3/10 | IMA | All Products |
| Originator: Thompson, Jeff |
| Originator Company Name: Qwest Corporation |
| Owner: Winston, Connie |
| Director: |
| CR PM: Routh, Mark |
| Description Of Change |
|
Implements additional automated jeopardy notifications, to a total of 45 types of jeopardy conditions. This CR is related to the Jeopardy Notice Interval and Timely Jeopardy Notices Performance Indicator Definition (PIDs PO8 and PO9). Colorado Docket 01I-041T. PID definitions can be found at http://www.nrri.ohio-state.edu/oss/master/perform/perform.htm.
The current Jeopardy Notice process is manually intensive. Problem: The current process for sending Jepardy Notices and then calculating the timeliness of Jeopardy Notices is manually intensive. personnel in the Interconnect Service Center (ISC), manually send a notice using FAX, email or online IMA functionality. Then, the ISC will manually record the fact that the notice was sent in a database to be used by the algorithm that calculates the P08/P09 measures.
Resulting Business Need: Automate the creation of Jepardy Notices, the sending of Jeopardy Notices, and the recording of statistics about when the Jeopardy Notice was sent. This goal can be achieved with some enhancements to the existing IMA architecture. The existing architecture allows Network systems to be interrogated to determine the Jeopardys on wholesale service orders. Jeopardys are then recorded and make available to IMA. Today, IMA does not create a Jeopardy Notice or set the LSR status to Jeopardy. However, if an the ISC manually uses online IMA functionality to send a Jeopardy Notice to the CLEC, then the IMA LSR status is set to Jeopardy. The new business requirement will ask that IMA automatically do what it does today in response to a person in the ISC using the online IMA Jepardy screen: set the IMA LSR status to Jeopardy, send a Jeopardy Notice to the CLEC, and record the Jeopardy information. The Jeopardy data will then be available to produce the data for PIDs P08 and P09 .
LSRs that are Faxed to Qwest do not reside in IMA. Problem: The only requests that are in IMA are requests that originated in IMA. Consequently, requests that do not originate in IMA (such as requests that come in via FAX or IIS) cannot have their Jeopardy Notices automatically sent by IMA.
Resulting Business Need: Create a mechanism to alert personnel in the ISC when a Jeopardy is detected on a non-IMA request. Allow ISC to manually record the date/time when they manually send the Jeopardy notice. The ISC will still have to manually FAX the Jeopardy Notice for LSRs that do not originate in IMA.
Not all Jeopardys should result in Jeopardy Notices. Problem: IMA systems currently detect all jeopardies that are in the Network systems for wholesale service orders. Some of these jeopardies are ‘internal’ and should not result in Jeopardy Notices being sent to the CLECs. Resulting Business Need: Qwest systems will filter out internal Jeopardys.
Project Objectives a) Automate the generation of Jeopardy Notices for IMA-originated LSRs. b) Create an automated mechanism to alert personnel in the ISC when Jeopardys exist on non-IMA LSRs. c) Allow manual entry into Qwest systems to indicate when a Jeopardy Notice is sent. This functionality will be used for LSRs that do not originate in IMA. d) Filter out the ‘internal’ Jeopartys so that they are not recorded in IMA.
|
Status History |
| Date | Action | Description |
| 10/18/2001 | CR Submitted | CR was submitted at the October Monthly CMP Meeting by Qwest. |
| 10/18/2001 | Discussed at Monthly CMP Meeting | CR was presented at the October CMP Meeting. |
| 10/18/2001 | Clarification Meeting Held | CR was clarified by Jeff Thompson at the October Monthly meeting |
| 10/31/2001 | Release Ranking | Ranking for Release 10.0; 30623 is "Above the Line" |
| 1/17/2002 | Discussed at Monthly CMP Meeting | CR # 30623 discussed during 10.0 Packaging Presentation |
| 1/17/2002 | Status Changed | CR # 30623 status updated to 'Packaged' for 10.0 |
| 3/13/2002 | Status Changed | Status updated from 'Packaged' to 'Development' |
| 3/21/2002 | Discussed at Monthly CMP Meeting | 30623 discussed at March Systems CMP Monthly meeting during IMA Release 10.0 Commitment Discussion (Attachment I) |
| 4/18/2002 | Discussed at Monthly CMP Meeting | 30623 discussed at April Systems CMP Monthly meeting; please see Systems CMP Distribution Package April CMP - Walk On |
| 6/20/2002 | Discussed at Monthly CMP Meeting | 30623 discussed at June Systems CMP Monthly meeting; please see Systems CMP Distribution Package June CMP -- Attachment N |
| 6/25/2002 | Status Changed | Status set to CLEC Test |
| 7/18/2002 | Discussed at Monthly CMP Meeting | 30623 discussed at July Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment G |
| 7/18/2002 | Status Changed | Status updated to Completed |
Project Meetings |
|
|
CenturyLink Response |
| Qwest is concerned that there is no CR Type that clearly encompasses these CRs. Qwest believes these CRs are most closely aligned with the Regulatory Change CR type. Qwest proposes to address this concern during the next Redesign Working Session.
|
Information Current as of 1/11/2021