Archived System CR SCR092801-1 Detail |
Title: Release Addendum deadline date and Addendum submission requirements | |||||
CR Number |
Current Status Date |
Level of Effort |
Interface/ Release No. |
Area Impacted |
Products Impacted |
|
|||||
SCR092801-1 |
Completed 7/18/2002 |
- | 12/10 | N/A |
Originator: Sprague, Michelle |
Originator Company Name: McLeodUSA |
Owner: Henry, Karen |
Director: |
CR PM: Esquibel-Reed, Peggy |
Description Of Change |
McLeodUSA has two change requests in regards to release addendum’s. McLeodUSA is requesting a deadline date to be initiated for the submission of addendum’s pertaining to a IMA/EDI release. To our knowledge there is not currently a deadline date associated with addendum’s. We would request that all addendum’s be submitted by Qwest, within 30-days of the Disclosure document being published. McLeod would also like to put a requirement in place that would require that each addendum be reviewed and discussed with Qwest and the CLEC, to ensure that the CLEC’s will not be impacted with development changes (on the EDI side). If it is found that their will need to be changes to development for the CLEC to support the addendum, then the CLEC would have the right not to support the addendum until the following release. McLeodUSA has been faced with numerous last minute development changes, due to addendum’s being issued very close to our EDI release implementation dates.
|
Status History |
Date | Action | Description |
9/28/2001 | CR Submitted | CR was received in the System process and logged. |
10/8/2001 | Clarification Meeting Held | Clarification meeting held with McLeodUSA (see minutes) |
10/18/2001 | Discussed at Monthly CMP Meeting | Discussed at the October CMP Meeting. This is a systems documentation issue, no system change is needed so is not a candidate for 10.0. No questions from the CLEC community. Level of Effort is not applicable. |
10/29/2001 | Draft Response Issued | Draft response posted to CMP database |
10/31/2001 | Release Ranking | Ranking for Release 10.0 occurred at October, 2001 CMP Meeting. SCR092801-1 ranked 15 |
11/15/2001 | Discussed at Monthly CMP Meeting | Discussed at the November CMP Meeting; discussion to continue on this item through redesign; see November CMP meeting minutes; CR Status updated to On Hold pending outcome of discussion in Redesign |
12/1/2001 | Status Changed | Status changed to "On Hold" pending Re-Design resolution |
1/17/2002 | Discussed at Monthly CMP Meeting | CR # SCR092801-1 discussed during 10.0 Packaging Presentation |
1/17/2002 | Status Changed | CR # SCR092801-1 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 | SCR092801-1 discussed at March Systems CMP Monthly meeting during IMA Release 10.0 Commitment Discussion (Attachment I) |
6/20/2002 | Discussed at Monthly CMP Meeting | SCR092801-1 discussed at June Systems CMP Monthly meeting; please see Systems CMP Distribution Package June CMP -- Attachment N |
6/20/2002 | Discussed at Monthly CMP Meeting | SCR092801-1 discussed at June Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment G |
6/25/2002 | Status Changed | Status updated to CLEC Test based upon discussion at June Systems CMP Meeting and IMA 10.0 Deployment on June 17, 2002 |
7/18/2002 | Discussed at Monthly CMP Meeting | SCR092801-1 discussed at July Systems CMP Monthly meeting; please see Systems CMP Distribution Package July CMP -- Attachment G |
Project Meetings |
July 18, 2002 CMP Meeting Discussion: This CR was completed with the IMA 10.0 Release. No CMP participants disagreed with the proposal to update this CR to Completed. 11/15/01 November CMP Discussion: Jeff Thompson would like the proposed process agreed to at the the re-design meeting. Eschelon advised that McLeod does not participate in re-design. McLeod will be invited along with EDI vendors to the December or January re-design meeting. Eschelon asked if the proposal agrees with McLeod's request. Jeff advised that no it does not. McLeod does not want any addendums and addendums are necessary for corrections. NightFire wants an analysis of previous addendums. Jeff advised that he would provide addendum examples to use in the discussion, an analysis is too big of a job. Alignment/Clarification Meeting 10:00 a.m. (MDT) / Monday 8th October 2001 SC092801-1 Release Addendum Deadline Date and Addendum Submission Requirements Attendees Peggy Esquibel-Reed / Qwest Michelle Sprague / McLeod USA Joseph J. Bradley / Qwest Annelyn Aficial / Qwest Beth Foster / Qwest Dianne Friend / Qwest Tracy Gilford / Qwest Gerald Mohatt / Qwest Lynn Stecklein / Qwest 10-08-01: Received clarification from Michelle Sprague, there are not two change requests, this request is a two-fold request. Part 1) McLeod would like a deadline established for addendum’s. Part 2) McLeod would like 30 days to review the ‘draft addendum’ for EDI associated changes. If code changes are involved, the CLEC would like the right to have the change moved to another release. Michelle advised that there has been some instances where addendum’s have impacted CLEC’s due to code changes and not enough notice was given to the CLEC’s to make any system changes. One example when impacted was the 8.0 release involving a manual indicator. Qwest advised that a draft developer worksheet does go out a few months prior to a release, but is not a full disclosure document. Qwest advised that a process for addendum’s may exist and will research. Confirm Interfaces & Products Impacted: IMA / EDI
|
CenturyLink Response |
For Review by the CLEC Community and Discussion at November CMP Meeting DRAFT RESPONSE October 29, 2001 Michelle Sprague ILEC Relations Manager McLeodUSA CC: Jeffery Thompson Teresa Jacobs Joseph J. Bradley Beth King C This letter is in response to your CLEC Change Request Form, number SCR092801-1, dated September 28, 2001, CR Title: Release Addendum Deadline Date and Addendum Submission Requirements CR Description: McLeod USA has two change requests in regards to release addendum’s. McLeod USA is requesting a deadline date to be initiated for the submission of addendum’s pertaining to an IMA/EDI release. To McLeod’s knowledge there is not currently a deadline date associated with addendum’s. McLeod would request that all addendum’s be submitted by Qwest, within 30-days of the Disclosure document being published. McLeod would also like to put a requirement in place that would require that each addendum be reviewed and discussed with Qwest and the CLEC, to ensure that the CLEC’s will not be impacted with development changes (on the EDI side). If it is found that their will need to be changes to development for the CLEC to support the addendum, then the CLEC would have the right not to support the addendum until the following release. McLeodUSA has been faced with numerous last minute development changes, due to addendum’s being issued very close to our EDI release implementation dates. Additional clarification was received from Michelle in the Clarification Meeting that was held on Monday, October 8th and at the October CMP Forum. There are not two change requests; this request is a two-fold request. Part 1) McLeod would like a deadline established for addendum’s. Part 2) McLeod would like 30 days to review the ‘draft addendum’ for EDI associated changes. If code changes are involved, the CLEC would like the right to have the change moved to another release. Michelle advised that there has been some instances where addendum’s have impacted CLEC’s due to code changes and not enough notice was given to the CLEC’s to make any system changes. One example when impacted was the 8.0 release involving a manual indicator. Qwest advised that a draft developer worksheet does go out a few months prior to a release, but is not a full disclosure document. Qwest advised that a process for addendum’s may exist and will research. Qwest Response: An addendum to the IMA EDI Disclosure Document is required anytime any content of the disclosure document changes. The addendum will always include a change summary that will explain each change by chapter or appendix, location (ie. business description or field on developer worksheet), action taken (add, delete, change), and a concise summary of the change. Additionally, each chapter on the web page includes the date of update next to it's title. Following is a high level overview of the current disclosure, release and addendum process: * Draft Developer Worksheets -- 45 days prior to a release the draft Developer Worksheets are made available to the CLEC’s. * Final Disclosure - 5 weeks prior to a release the Final Disclosure documents, including I charts and developer worksheets are made available to the CLECs. * Release Day - On release day only those CLECs using the IMA GUI are required to cut over to the new release. * 1st Addendum - 2 weeks after the release the 1st addendum is sent to the CLECs. * Subsequent Addendum’s - Subsequent addendum’s are sent to the CLECs after the release as needed. There is no current process and timeline. * EDI CLECs - 6 months after the release those CLECs using EDI are required to cut over to the new release. CLECs are not required to support all new releases. Following is a high level overview of the proposed disclosure, release and addendum process. * Draft Disclosure -- 73 days prior to release the CLECs receive full draft disclosure. * Walk through & Review Disclosure - 68 days prior to release the CLECs and Qwest walk through and review the draft disclosure documents. * CLECs have a designated period of time to identify issues and discuss them with Qwest. Where appropriate Qwest will make changes to the release and the disclosure documents. * Final Disclosure Documents will be made available to the CLECs prior to the 5-week mark that is used in the current process. * SATE Test Environment -- 30 days prior to the release the CLECs will be given the opportunity to test interfaces in SATE environment. * Addendum’s - The 1st addendum will be published 2 weeks after the release. Subsequent addendum’s will be published as needed. Based on the information noted above, this CR would require changes to systems documentation. This request will not result in a system change, therefore a level of effort is not appropriate and this request is not eligible for a systems release. This issue is also being addressed in the re-design meetings. Sincerely, Karen Henry Information Technologies Sr. Director
|
Information Current as of 1/11/2021