Anda di halaman 1dari 10

ROS

Release Implementation Plan - ROS 2006.0F (X908R)


PREPARED BY Dick Unkenholz RELEASE 2006.0F DATE 5/19/06

Description
ROS Release 2006.0F will implement 9 new features, 30 Edits (3910’s), and the correction of 10
production defects.
The Change Management Work Order to install the ROS features, edits & production defects is #
588437.

ROS Features

Feature Description
New Window for TAC Promos - This add-only folder will display information about the
60879 customer’s current TAC, TACT, and TACC promotion(s) and allow the user to select an available
promotion to be added to the service order.
60897 Correct CLS for ME BCOS
Updates to ME for Mid-Band Copper - This feature will provide additional support for Metro
61370
Ethernet (ME) by including service ordering capability for Mid-Band Ethernet (MBE) on Copper.
Appt code for BTFAA - This enhancement will modify existing severe ROS edit 0226 for invalid
appointment code to no longer display when the Toll Free Dialing USOC(s) are I action coded on
61460
the service order.

BellSouth Centrex - This enhancement will modify ROS to support Centrex Simultaneous Ring
61528
(SIMRING) on BellSouth Centrex service in the EWSD switch.
Modify List of DCR Codes - This enhancement will modify the list of Disconnect Reason (DCR)
codes displayed on the Account / Disconnect folder by removing codes that should no longer be
61636
used and adding new codes.

Decommission New Orleans Servers - This request includes decommissioning 2 ROS servers
61696 in New Orleans. The office the servers exist in will be removed from ROS Office and SOCS ID
information.
Modify ISAFA Recapping Logic - This change will bring ROS recapping behavior in line with
61702 the ISAFA high level business requirements for the scenario where an account is being changed
from ISAFA to POTS.
61710 Create USOC Pop Guide for TIRKS Term USOCs – Modify USOC Population Guide Table.

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 1 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)

Edits (3910’s)

Feature Description
THE COU DATA TEAMS HAVE REQUESTED SOME CHANGES TO DISCONNECT
REASON CODES TO PROVIDE BETTER TRACKING INFORMATION.
F-61644
ADD THE FOLLOWING NEW CODESETS TO EDIT 008:
BX - BELLSOUTH TO WIRELESS -NON-PORTING
DS - DOWNSIZING
An exception is needed to the FID ZBDI so that edit 009 is not performed when the bundle
USOC is the same on a C and T action coded USOC logical line
F-61667
NOTE: This edit is not performed when the same BUN++ USOC appears on a C and T
action coded paired USOC logical line
F-61680 Add USOC NLMCX to edit
RTG FLX REQUIRED IF SNID'S LAST CHARACTER IS C!

ON N, T, C, D, F, R OR X ORDERS WHEN THE FID SNID (SONET NETWORK


IDENTIFIER) APPEARS IN THE S&E AND THE LAST CHARACTER OF DATA IS "C",
F-61689
THE RTG FID MUST APPEAR WITH THE CODESET OF FLX, UNLESS THE ORDER IS
IN HC STATUS OR WAS INITIALLY ENTERED IN CP STATUS (ORDER IS CURRENTLY
CP AND HAS NEVER BEEN AO, PD, PF OR MA) THEN THE FID RTG WITH DATA OF
FLX MUST NOT APPEAR IN THE IDENT SECTION.
IC MUST APPEAR ON NON-CABS N, T, C ORDERS WHEN THE RECAPPED OR
INWARD (I) ACTION CODED FID TAC OR TACT APPEARS IN THE BILL SECTION
F-61692 WITH A CODESET OF ZWN2, ZWN4, OR ZWN6, THE FID IC MUST APPEAR ON
EVERY INWARD (I) ACTION CODED USOC LOGICAL LINE EXCEPT THE ONES
LISTED BELOW AND MAY NOT APPEAR ON THE ONES LISTED BELOW:
CHANGE 007 TO: INVALID VPI DATA FORMAT!
WHEN VPI APPEARS IT MUST APPEAR IN THE FOLLOWING FORMAT:

/ VPI 250, VCI 32


F-61693
WHERE 250 = VIRTUAL PATH IDENTIFIER (1-3 NUMERICS FROM 0-255 FOLLOWED
BY A COMMA AND A SPACE)
WHERE VCI 32 = VIRTUAL CHANNEL IDENTIFIER (3 ALPHAS OF VCI FOLLOWED BY
A SPACE AND 1 NUMERIC OF 0 OR 2-4 NUMERICS OF 32-1023), (OPTIONAL)
CHANGE TO: EQ# OF USOCS MUST APPEAR! (3)

F-61697 IF AN INWARD (I) ACTION CODED UREWO USOC APPEARS AN EQUAL NUMBER OF
THE FOLLOWING USOCS MUST APPEAR INWARD (I,E,X)ACTION CODED OR
RECAPPED.
ADD: SSM REQUIRED!

ON NON-CABS ORDERS, WHEN THE FID ZDSL APPEARS ON A CATEGORY D OR


F-61610 SAFAL USOC LOGICAL LINE AND THE FID CLS APPEARS ON ONE OF THE
FOLLOWING INWARD (I,E,T) ACTION CODED USOC LOGICAL LINES AND THE DATA
FOLLOWING THE ZDSL FID AND THE CLS FID IS THE SAME, THEN THE FID SSM
MUST APPEAR ON THE CATEGORY D OR SAFAL USOC LOGICAL LINE.

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 2 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)
Feature Description
ADD NOTE 5 - CHG 015 TO: ZLTD MUST APPEAR!

ON NON-CABS ORDERS IN FLORIDA AND IN CENTURY, FLORIDA, (NPA NXX OF 850


F-61698
M15, 850 Z35, 850 256, 850 366) WHEN ONE OF THE FOLLOWING USOCS APPEAR
OUTWARD (O, C, D) ACTION CODED, THE FID ZLTD MUST APPEAR ON AN INWARD
( I, E, T, X) ACTION CODED 9LM USOC LOGICAL LINE.
CHG TO: ZDDD MUST APPEAR!

F-61699 ON NON-CABS N AND T ORDERS IN FLORIDA AND IN ALABAMA FOR CENTURY,


FLORIDA (NPA NXXX 850 256) WITH ONE OF THE SERVICE CODES LISTED BELOW,
THE FID ZDDD MUST APPEAR IN THE IDNT SECTION.
This change will allow outward activity when the FID RAF3 appears on the FIDCLS. Also
change the edit to apply to both SB and SBC.
F-61703
Add the FID RAF3 to CLS edit 023 and remove the “SB” from the edit.
PRN – PROJECT NUMBER – IDNT

ADD EDIT 014


F-61706 ON NON-CABS N AND C ORDERS WITH A BASIC CLASS OF SERVICE SHOWN
BELOW WHEN THE USOC ODO APPEARS
INWARD (I,E,T,X) ACTION CODED IN THE S&E, THE FID PRN WITH THE LAST FOUR
DATA CHARACTERS OF DWDM IS REQUIRED IN THE IDNT.
CHANGE TO: USOC REQUIRED! (3)

F-61707 ON NON-CABS C ORDERS WITH A BASIC CLASS OF SERVICE OF CEN++, WHEN


THE FID TC APPEARS RECAPPED IN THE TRAFFIC SECTION, ONE OF THE
FOLLOWING USOCS MUST APPEAR INWARD (I) ACTION CODED IN THE S&E:
ADD 012: PCN NOT ALLOWED!
F-61708
ON NON-CABS ORDERS IN ALABAMA AND NORTH CAROLINA, THE FID PCN IS NOT
ALLOWED INWARD ACTION CODED.
DELETE FMT EDIT 1527. EDITING IS BEING DONE IN ROS AND EDIT IS CAUSING
F-61711
PROBLEMS IN SOCS
An exception is needed on RTE edit 029 to allow the FID RTE to appear
on orders issued by the Wireless Center.
F-61715
Add a note to: This edit is not performed when the FID CENT with data of
IW0 appears in the IDENT Section.
ADD SCB SITE IDENTIFIER CODES TO EDIT 007:
1 = ALABAMA
4 = KENTUCKY
F-61716
5 = LOUISIANA
6 = MISSISSIPPI
9 = TENNESSEE

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 3 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)
Feature Description
TTRA MUST APPEAR! (3)

ON NON-CABS ORDERS, WHEN A CATEGORY D USOC APPEARS INWARD (I,E,T,X)


F-61719 ACTION CODED OR RECAPPED AND ONE OF THE CONDITIONS BELOW EXIST,
THE FID TTRA MUST APPEAR INWARD (I) ACTION CODED OR RECAPPED IN THE
IDENT SECTION AND MUST APPEAR ON THE INWARD (I,E,T,X) ACTION CODED OR
RECAPPED CATEGORY D USOC LOGICAL LINE.
WHEN SAFAL IS BEING DISCONNECTED AND CHANGED TO A NEW CLASS OF
SERVICE C AND T ACTION CODES WILL BE USED AND END USER LINE CHARGES
SHOULD APPLY TO THE NEW CLASS OF SERVICE. MODIFY FMT 0203 SO THAT
F-61720
WHEN THE FID CS APPEARS OUTWARD ACTION CODED IN THE IDNT WITH DATA
OF SAFAL THEN A T ACTION CODED CATEGORY D USOC SHOULD BE USED FOR
PURPOSES OF BALANCING CAT D’S AND END USER LINE CHARGES.
WHEN SAFAL IS BEING DISCONNECTED AND CHANGED TO A NEW CLASS OF
SERVICE C AND T ACTION CODES WILL BE USED AND END USER LINE CHARGES
SHOULD APPLY TO THE NEW CLASS OF SERVICE. MODIFY FMT 0208 SO THAT
F-61721
WHEN THE FID CS APPEARS OUTWARD ACTION CODED IN THE IDNT WITH DATA
OF SAFAL THEN A T ACTION CODED CATEGORY D USOC SHOULD BE USED FOR
PURPOSES OF BALANCING CAT D’S AND END USER LINE CHARGES.
WHEN SAFAL IS BEING DISCONNECTED AND CHANGED TO A NEW CLASS OF
SERVICE C AND T ACTION CODES WILL BE USED AND END USER LINE CHARGES
SHOULD APPLY TO THE NEW CLASS OF SERVICE. MODIFY FMT 0762 SO THAT
F-61722
WHEN THE FID CS APPEARS OUTWARD ACTION CODED IN THE IDNT WITH DATA
OF SAFAL THEN A T ACTION CODED CATEGORY D USOC SHOULD BE USED FOR
PURPOSES OF BALANCING CAT D’S AND END USER LINE CHARGES.
WHEN SAFAL IS BEING DISCONNECTED AND CHANGED TO A NEW CLASS OF
SERVICE C AND T ACTION CODES WILL BE USED AND END USER LINE CHARGES
SHOULD APPLY TO THE NEW CLASS OF SERVICE. MODIFY FMT 0360 SO THAT
F-61723
WHEN THE FID CS APPEARS OUTWARD ACTION CODED IN THE IDNT WITH DATA
OF SAFAL THEN A T ACTION CODED CATEGORY D USOC SHOULD BE USED FOR
PURPOSES OF BALANCING CAT D’S AND END USER LINE CHARGES.
WHEN SAFAL IS BEING DISCONNECTED AND CHANGED TO A NEW CLASS OF
SERVICE C AND T ACTION CODES WILL BE USED AND END USER LINE CHARGES
SHOULD APPLY TO THE NEW CLASS OF SERVICE. MODIFY FMT 0361 SO THAT
F-61724 WHEN THE FID CS APPEARS OUTWARD ACTION CODED IN THE IDNT WITH DATA
OF SAFAL THEN A T ACTION CODED CATEGORY D USOC SHOULD BE USED FOR
PURPOSES OF BALANCING CAT D’S AND END USER LINE CHARGES.

THE PURPOSE OF THIS REQUEST IS TO ALLOW THE FIRST CHARACTER OF A


HOUSE NUMBER ON THE SERVICE ADDRESS TO BE A 0. THIS EDIT WAS
CHANGED TO DISALLOW THE 0 AS THE FIRST CHARACTER IN SEPTEMBER, 2005.
SINCE THEN AREAS HAVE BEEN IDENTIFIED THAT HAVE VALID HOUSE NUMBERS
F-61725
WITH A LEADING ZERO. INTRADO HAS ATTEMPTED TO GET THE COUNTIES TO
RENUMBER THE ADDRESS; HOWEVER, THEY HAVE REFUSED TO DO SO.

PLEASE CHANGE EDIT 13. ALLOW A HOUSE NUMBER TO BEGIN WITH 0.

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 4 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)
Feature Description
ADD 011
ON NON-CABS ORDERS, WHEN THE FID ZDSL APPEARS ON A CATEGORY D OR
SAFAL USOC LOGICAL LINE AND THE FID ZDSL APPEARS ON ONE OF THE
F-61726
FOLLOWING INWARD (I,E,T) ACTION CODED USOC LOGICAL LINES AND THE DATA
FOLLOWING THE ZDSL FIDS IS THE SAME, THEN THE FID SSM MUST APPEAR ON
THE CATEGORY D OR SAFAL USOC LOGICAL LINE.
A SECOND LINE (CATEGORY D) COULD BE ADDED THAT WOULD BE I ACTION
F-61734
CODED. REVISE THE EDIT TO ALSO INCLUDE I ACTION CODED CATEGORY D
A SECOND LINE (CATEGORY D) COULD BE ADDED THAT WOULD BE I ACTION
F-61735
CODED. REVISE THE EDIT TO ALSO INCLUDE I ACTION CODED CATEGORY D
A SECOND LINE (CATEGORY D) COULD BE ADDED THAT WOULD BE I ACTION
F-61736
CODED. REVISE THE EDIT TO ALSO INCLUDE I ACTION CODED CATEGORY D
A SECOND LINE (CATEGORY D) COULD BE ADDED THAT WOULD BE I ACTION
F-61737
CODED. REVISE THE EDIT TO ALSO INCLUDE I ACTION CODED CATEGORY D
A SECOND LINE (CATEGORY D) COULD BE ADDED THAT WOULD BE I ACTION
F-61738
CODED. REVISE THE EDIT TO ALSO INCLUDE 1 ACTION CODED CATEGORY D

Production Defects Corrected

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 5 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)

Defect Description

D-34049 FORMAT_0105 is firing incorrectly


D-35149 Seq field on Unfielded Ident doesn't retain comma
D-35226 TTYP S&E 010 not displaying in ROS
D-35971 DM-g7236082 auto core defect core.k2026013.Mar17.15.14
D-36055 ROS 0145 Firing in Error
D-36103 Ab Term Search for address
D-36220 S&E gets recapped in error
D-36582 Account not found even though it is in CRIS
D-36605 Address Key data is incorrectly displayed as all upper case
D-36615 ROS Abnormal Termination on SO Search & Replace

ESD Services/CCF Releases Tested with the ROS 2006.0F release

Release Content Shipped to Production


None

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 6 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)

Implementation Contact List

Contact Role Contact Information


Dick Unkenholz ROS April Release Manager 205-733-5806 Pager: dickunkenholz
Gary Scott PRM Ordering Group Lead 404-927-6390 Pager: garyscott
BellSouth Business Customer Care – Manager, ROS
Marshall Canant 205-298-6710 Pager: mcanant
Support
BellSouth Business Customer Care – Director, ROS
Melaine Hardwick 404-995-7800 Pager: mhardwick
Support
Jim Norris ROS Prime Integrator 404-829-7682 Pager: jnorris
Bob Bates BTG Delivery SR Director 404-927-8893 Pager: bbates2

Implementation Approach

Goals and objectives:

1. Deploy the release in four Soak sites on Tuesday, 6/13/06, and in all remaining sites on Friday, 6/16/06.

Processes and Procedures:

1) Publish Release Implementation Plan with Release Notes


2) Submit Change Control Request to EDS
3) Build Release packages for User Acceptance Testing
4) Conduct Scheduled Deployment activities
5) Conduct SOAK Roll-Out Verification Tests
6) Conduct Production Roll-Out Verification Tests

Tools:
CCC Harvest: For Configuration Management

Soak/Production Sites:
1. Test in Soak sites on Tuesday, 6/13/06:
Small Business – Louisville, KY
BellSouth Business – Charlotte, NC
Consumer Services – Louisville, KY
LCSC – Fleming Island, FL
2. Production Full Deployment in all remaining sites on Friday, 6/16/06.

Implementation Requirements
Release 2006.0F software changes will be installed on all ROS production servers on Friday, 6/16/06.

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 7 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)

Training Requirements
Communicated to the field by BellSouth ROS Training Team

Communication Plan

Date/Time Communication Audience


EST
ROS SCCB meeting scheduled to review the Product Test and UAT
6/12
test summaries and the IOT results. A Go/No Go decision will be SCCB
2:00 p.m.
made as to the deployment of the April release to the soak sites.
6/12 SMS Advertisement to SOAK PCs begins. PC GUI Server DDS Soak
Accenture
8:00 p.m. Install begins.
6/13
Pager notification that ROS soak verification has begun. Accenture
5:00 a.m.
By 5:15 a.m. Pager notification that first test order has completed. Accenture
A Go/No Go decision is communicated via pager for soak site
6:00 a.m. Accenture
implementation.
BTG Delivery, CIO, Accenture,
7:00 a.m. A release implementation page with release status is sent out.
Business Unit management
BTG Delivery, CIO, Accenture,
9:00 a.m. Email notification with release contents is sent out.
Business Unit management
ROS SCCB meeting scheduled to review any issues from the soak
6/15
sites. A Go/No Go decision will be made as to the deployment of the SCCB
12:00 p.m.
release to remaining production sites.
ROS release is deployed to the remaining production sites. Roll-out
6/16 verification activities will be performed to ensure the stability of the Accenture
release.
5:00 a.m. Pager notification that ROS roll-out verification testing has begun. Accenture
Pager notification that first test order has completed.
By 5:15 a.m. Accenture
A Go/No Go decision is communicated via pager for implementation
6:00 a.m. Accenture
to remaining sites.
BTG Delivery, CIO, Accenture,
7:00 a.m. A release implementation page with release status is sent out.
Business Unit management
Email notification with release contents is sent out if any changes BTG Delivery, CIO, Accenture,
9:00 a.m.
required from the SOAK release. Business Unit management

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 8 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 9 10/14/yy 14:57 A10/P10
ROS
Release Implementation Plan - ROS 2006.0F (X908R)
Back Out Plan/Procedure for April Release

In the event the Release must be recalled, the procedure for backing out the software is documented in the ROS
DDS_SMS Backout Plan.doc at: U:\wrkctr\PCGUI Prod Support\Back-Out Plans.

Roll-Out Verification Testing

Soak Sites:

6/13: Functional testing will be executed by the IDC product test team on a subset of application servers within
each soak site and on an application server within a non-soak site.

Full Deployment:

6/16: Functional testing will be executed by the IDC product test team on a subset of application servers
throughout the region.

Note: The specific steps for the new connect scenarios are located on the ROS shared drive in:

X:\Summaries\Rollout Verification\Soak Verification Test Plan.doc


X:\Summaries\Rollout Verification\Rollout Verification Test Plan.doc

Test User IDs will be used to access production application servers for soak and full deployment testing. There will
be no verification of the client software on the production PCs.

PRIVATE/PROPRIETARY
NO DISCLOSURE OUTSIDE BELLSOUTH AND BELLSOUTH ACCENTURE SOURCING ARRANGEMENT
EXCEPT BY WRITTEN AGREEMENT.
X908R.doc v1.0 Page 10 10/14/yy 14:57 A10/P10