You are on page 1of 8

BackOffice Information Bulletin

2003

Dec

Jan

Feb

Mrt

Apr

May

Jun

Jul

Aug

Sep

May

Jun

Jul

Oct

Nov

on track
need extra attention
Off track

Roadmap:
Planned FOA
Expected GA date
Release
2.0
3.0
Videomail 6.0
4.0

Dec
2.0

2003
Jan
2.0

H3G Solution
Feb

Mar
Apr
3.0 + Vid

3.0+

Planned FOA
December 2002

Expected GA date
January 2003

March May 2003

May 2003

March May 2003

May 2003

August 2003

Tbd

Aug

4.0

Sep

Additional information:
By Emile Arens
1.0
Not in scope of the BackOffice
2.0
Solution 2.0 contains the following products:

WSB 3.0.2

CDS 1.0

GUA 1.1

SMSC 4.0 FP2B & 4.3

MMSC 1.1 -12

UC 5.2-7.3 -1

SVCC 1.0 -2

IP Backbone
* SAT Resolution plans including resolution dates have been defined. Problems to be resolved in the next three
months
* The software release of 28 October is considered final for 2.0 for escrow. For reaching customer acceptance
ASAP, all energy is directed to blocking issues and new interim software patches are made available with maximum
speed.
* Although role of BackOffice in Solution 2.0 is limited to ISD activities and BO on best effort basis, BO is fully in
the loop of ongoing issues.
* The GA date will be determined as a separate action. Estimate date: Jan 2003
3.0
Solution 3.0 has been re-instated and will be combined with Videomail. Ready for delivery 10 March 2003. The
following products are included:

SMSC 4.5

MMSC 1.2

UC 6.0 (LDAP schema 6.0, Notifier 6.0, Upower 6.0)

SVCC 1.0 -2
Videomail 6.0
This interim release is being scheduled. Ready for delivery 10 March 2003. SoW in progress at release
management.
GUA
Gua is seen by H3G as a separate product. The releases of GUA will coincide with maintenance releases
4.0
The following products are likely to be part of solution 4.0

SMSC 4.6

MMSC 2.0

UC 6.1

WSB 4.0
Maintenance releases
Maintenance releases will start to provide software for both 2.0 and 3.0 and GUA after implementation of 3.0

Delivery BackOffice

Ref: http://isis/

continue

Roadmap:
Planned FOA MMSC
Planned FOA MMSC
Exp. GA MMSC
Exp. GA MMSC

2002
May

MMSC
Jun

Jul

Aug

Sep

Planned FOA MMS


Planned FOA MMS
Exp. GA MMS
Exp. GA MMS
Release
Legacy Support
+MMStore
MMSC 1.1
MMS 1.1

Oct
Nov
Dec
1.1
1.2 (=1.1.1)
1.1
1.2
1.1

1.2

Expected GA date
-

Virgin (Compaq Smart inst)


November / December 2002
Virgin (Compaq Power inst)
Singtel (SUN Smart inst)
Singtel (SUN Power inst)
Optimus (Compaq Smart upgrade)
Optimus (Compaq Power upgrade)
MMSC 1.2 is delivered to the SICC
and will be part of Solution 3

MMSC 1.2
(was MMSC 1.1.1)

MMS 1.2
(Compaq only)
MMSC 2.0
Includes MMS
and iMMS

FOA candidate: No customer yet

13 December

t.b.d.

March 2003

(H3G delivery only)

Feb

1.2
1.1

Planned FOA
Ongoing (Telia)

2003
Jan

Additional information:
By Heino Wessels

MMSC 1.2 is again delivered to the sicc!!!!

MMSC 2.0 will include MMS, iMode mail and generic iMode adaptions.

Currently SUN manufacturing can only be guaranteed for EMEA

MMS 1.2 will only be applicable for Compaq!!!

The 1st release training for MMS 1.2 is planned for 16 December 2002. (so far: 19 subscriptions)
The 2nd release training for MMS 1.2 is planned in January 2003. (so far: 12 subscriptions)
Invitations to the managers have been send out.

Currently we are working on a overview of all tested ATPs

The Optimus upgrade is planned for week 3 in 2003

The Virgin (Compaq power) is re-installed for E-plus due to customer commitments.

All FOAs on SUN/Compaq; smart/power; installation/upgrade are closely planned and monitored by PM, CS, R&D and
BO.

For an MMSC upgrade (1.0/1.0.1 1.1) on a SUN power system 2 extra disk need to be ordered. You will be
informed by Product Management

Delivery BackOffice

Ref: http://isis/

continue

2002
May

Roadmap:
Planned FOA
Planned FOA
Expected GA date
Expected GA date

WSB
Jun

Jul

Aug

Sep

Oct

Nov
3.2

Dec

3.2

Release
3.2

3.2.1

3.3

4.0

Planned FOA
Ready for FOA (B release):
November 11, 2002
FOA candidate: Vodafone (CPQ)
FOA candidate: AT&T (SUN)
Ready for FOA: 13 January 2003
FOA candidate: M1 Singapore
Ready for FOA: 10 February 2003
FOA candidate: Telefonica
Ready for FOA: 1st April 2003
FOA candidate: No customer yet

2003
Jan
3.2.1

Feb
3.3
3.2.1

3.3

Expected GA date
2nd December 2002

1 February 2003
28 February 2003
1st May 2003

Additional information:
By Heino Wessels

WSB 3.2 is declared GA. Rollouts are currently only supported for CPQ single node, SUN dual node and SUN multi
node. All other installations need extra attention from all departments!!!

WSB 3.2 will only be rolled out / upgraded thriftily. This is upon decision of product management

Currently SUN manufacturing can only be guaranteed for EMEA

The initial scope for release 4.0 includes Backend/Frontend split where the Frontend will run on Linux (Redhat 7.3 personal)

Release 3.3 will focus on I-mode stability and performance. Target customers are: KPN group, Telefonica and
Vodafone

SMART installation (SIP) was planned to be verified for SUN and COMPAQ in WSB release 3.2.1. So far it seems
that this will not be finished on the 1st of January due to (not in time) hardware delivery at R&D. It will be shifted
to release 3.3

The WSB 4.0 will have changed STPs for all platforms. This release will have front end and back end nodes. Also
the SMART will be introduced replacing the Lite (Compaq) and single node (Compaq / SUN)

Delivery BackOffice

Ref: http://isis/

continue
SMSC
2003
Mrt

Roadmap:
Planned FOA
Expected GA date
Release
4.6

Apr

May

Jun

Jul

Aug

Sep

Dec

2003
Jan

Feb

4.6

Planned FOA
March 2003

Expected GA date
April 2003

Additional information:
By Michel Wilhelm
SMSC 4.6
This will be the next release after 4.3 and 4.5; its the merge between the 4.3 and 4.5 functionality added with
new functionality.
From this moment on there is one global SMSC release.
Upgrade path will be: 4.3 4.6 and 4.5 4.6.
The SOW (Statement Of Work) for this release is been made.
The PoA (Plan of Approach) has been made by Dev. and the scope is now clear.
This release only involves software changes, no hardware changes.
There are some interfaces changes but all interfaces are backwards compatible
The release-training is a two-day training. The dates are 17+18 Feb. 10+11 March and 31 March + 1 April. All
parties involved will be addressed to participate in the release-training.
RFOA March 2003.
SMSC STP changes (continuous)
Due to end-of-life issues new STPs SHOULD be defined.
At current the STPs will become end-of-life from 1-1-2003.
Beneath the scheme involving the Compaq systems :

The new DS15 will be released by Compaq from 1-7-2003.

The new DS25 is already released by Compaq.

The old DS10 will become end-of-life at 1-7-2003 (can be replaced by DS15).

The old DS20 will become end-of-life at 1-9-2003 (can be replaced by DS15 orDS25).

The old ES40 will become end-of-life at 1-4-2003 (can be replaced by DS25).
Due to these replacements we probably cant use the current VMS-version anymore. The VMS-version 7.3
needs to be used. This has a great impact on the defining the new STPs
At current we are investigating the alternatives and defining the impact and risks involved.
The proposed approach will be :

SMART : keep on DS10 but with VMS 7.3

Power : keep on DS20 but with VMS 7.3

Performance : New on DS25 with VMS 7.3

DSMSC : keep on DS20 but with VMS 7.3


Existing Hardware-configurations will be kept on VMS 7.2
SMSC Hercules / 5.0
This is the complete new SMSC concept with a redesign of the Hardware-configuration.
There will be only one STP. It will be a scalable multi-node system with Loadbalancer(s) and ITP(s). There is no
need anymore for the Signal transferring Point (STP).
The SMSC will be completely IP-based. No need anymore for SS7-hardware.
At current we are investigating the alternatives and defining the impact and risks involved.
We are also looking at the migration scenarios for the classic STPs to the new Hercules STP.
Planning :
New customers can order a Hercules system (GSM only) end Q1..
Existing customers can migrate to Hercules in the same period. Each migration will be treated as a special
project.

Delivery BackOffice

Ref: http://isis/

continue

Roadmap:
Planned first delivery

Feb

2.1.1

Expected GA date

Release
2.1.1
(maintenance)
2.2

GUA

2003
Jan

Mrt

April

May

June

July

Aug

Sept

Oct

2.2
2.1.1

Ready for Delivery


8th January 2003

(Expected) GA date
Feb. 2003 (after successful H3G-SAT)

31st January 2003

28th February 2003 (after successful H3G-SAT)

Additional information:
By Pierrette Koumans
General:
Naming of GUA has been changed in line with H3G GUA-Naming:
o
GUA 1.1.1 = GUA 2.1.1
o
GUA 1.2 = GUA 2.2
Release 2.1.1
GUA 2.1.1 is an enhanced release on GUA 2.1 (was 1.1) that was rolled out for H3G in September/November 2002.
On the 8th of January GUA 2.1.1. will be released to the SICC to be part of the Solution Maintenance release. In this GUA
release all outstanding FAT issues are to be solved plus some outstanding SPRs.
GUA 2.1.1 is also to be validated against SUN for GUA to be part of the UC platform. This combination was sold to H3G Austria
and Rome. Validation is jeopardized by lack of resources in the PDC.
This release is not intended for customers other than H3G.
GUA 2.1.1 was successfully validated against I-Planet.
Release 2.2
This Release concentrates on the added functionalities contractually required by H3G and described in the H3G Global Work
Package.
This release is intended also for non-H3G customers.
GUA 2.2 should perform on the H3G GUA platform, the UC platform (validated against Mirapoint and I-Planet). Added GUA
functionalities entail: communities of interest, e-mail and MMS, extended calendaring and GUA requirements for Videomail.

2002
Dec

Roadmap:
Planned FOA
Expected GA date
Release
2.0

Spam & Virus Control Center (SVCC)


2003
Jan

Feb
2.0

March

April

May

June

July

August

Sept

2.0

Ready for Delivery


14 February 2003

Expected GA date
March 2003

Additional information:
By Pierrette Koumans

SVCC 2.0 consists of an MTA, handling the e-mail (including MMS), and Brightmail, handling the virus & spam control
(incoming and outgoing mail). For SVCC release 2.0 the MTA can be placed separately in the DMZ. This involves a separate
STP for the MTA. SVCC 2.0 works with the MMSC, WSB and UC systems.
SVCC 2.0 will be installed for H3G, but will also be made available for non-H3G customers.
This release includes benchmarking for performance tests.
The STP platform on SUN will be upgradeable for existing customers (H3G!).
For new installations SVCC 2.0 will be delivered on the Veritascluster.
SICC and PDC can only test with Sun Netra front-ends, not with the now orderable (and ordered) Sunfires. Impact of the
difference between the two is estimated low, but is not verified.
The release training is scheduled for the 21th February 2003. Documentation and trainingsession will be developed and
organized by the Back-Office, supported by Development, Maastricht.

Delivery BackOffice

Ref: http://isis/

continue

2002
Dec
S1.1

Roadmap:
Planned FOA
Expected GA date
Planned FOA
Expected GA date
Release
1.1 SN-MART
1.2 SN-SMART
1.3 SN-SMART
1.3 DN-DS20

2003
Jan
S1.
1

Business Tools
Feb

March

1.2

May

June

July

Aug

Sept

1.3
1.2

April

1.3

Ready for Delivery


August 2002

Expected GA date
January 2003

February 2003 (Optimus)

Q1 2003

April 2003

May 2003

April 2003

May 2003

1.1 SMART = S1.1


Additional information:
By Pierrette Koumans
Release 1.1

The 1.1 SMART was successfully rolled out at MTS in Moscow, immediately resulting in a full acceptance by the
customer.

Mid January a trial and buy roll-out will start in Mexico by our colleagues of our South America Office. The BackOffice has agreed to give support during this roll-out to make it a success. Hopes are that Telefonica will decide on
implementing Business Tools at a larger scale.

At the end of January, after some delay, a 1.1 SMART will be implemented at Mobinil, Egypt.
Release 1.2

Business Tools 1.2 will be released on SMART STP only, and only for Optimus.

Release 1.2 will involve MMSC support and Customer Care. No Reporting is offered, nor was initially - requested by
Optimus.

Business Tools encountered some issues on MMSC logfiles during development. Now MMSC and BT development are
working together to solve this issue.

Release 1.2 will be ready for Delivery for Optimus in mid January 2003. Timelines are still shifting due to the customer.
Hopefully the customer will opt for the BT 1.3 release, which will be available in April 2003.
Release 1.3
The ES40 is end of life. Release 1.3 will be offered on DS20 and SMART.
This release will support among others: SMSC and MMSC, CC and Reporting and enhanced group monitoring.
Optimus has bought the 1.3 functionality. Roll-out is planned for April.

Delivery BackOffice

Ref: http://isis/

continue

2002
Dec
5.2

Roadmap:
Expected GA date
Planned FOA
Release
5.2 Power-STP
Videomail
H3G SR 6.0
Release 6.1

Unified Communications

2003
Jan

Feb

March
6.0

April

6.0

May
June
6.1
6.1

July

Ready for Delivery


August 2003 (for H3G)

Expected GA date
Q4, 2002 (for H3G)

H3G / 15th February 2003

First Delivery for testing purposes

April 2003

May 2003

Aug

Sep

Additional information:
By Pierrette Koumans
General:
Renaiming of releases and current scope of delivery:
UC 6.0 Videomail
UC 6.1 Former release number 6.0. Contains all the deliverables roadmapped for UC 6.0.
UC 5.2
Product Development / Sustaining is working hard on resolving outstanding SPR/IPRs on UC 5.2. This still takes up
much of their time. This is causing some additional resource pressure on the UC 6.0 and 6.1 development.
UC 6.0 Videomail Solution Release
Videomail was released to the SICC on the 13th of December 2002. SICC started installing Videomail. This is
ongoing and is quite successful. PDC, SICC and Back-Office are bundling knowledge and efforts resulting in a
Videomail system in the SICC. It is said to be a killer application.
The December release does not yet contain Billing. This will be included mid January 2003.
Downside is the unavailability of the Ericson Video Gateway (VIG) and handsets. This means that Videomail was
developed simulating the connections and data. After the VIG and handsets come available, this might mean
Videomail needs some adjustments.
At this time it appears Videomail (UC 6.0) will only be installed on one H3G testsite. There it will be integrated with
the VIG. In view of this, no official release-training will be provided. SICC, Back-Office and Richmond PDC will
support the roll-out of Videomail during pre-installation and on the testsite.
The opportunity has been offered to H3G-IS to have engineers trained on the job in the SICC and during
(pre)installation. If it appears that UC 6.0 Videomail will be rolled-out repetitively, a more formal training will be
organized.
Timelines are not defined by H3G yet. Planned delivery is the 15 th February 2003.
UC 6.1
Development and delivery of UC 6.1 is under high pressure due to sustaining UC 5.2 and development of UC 6.0.
Hopes are to push the delivery date further down next year. This has not been agreed/confirmed by H3G yet. As
till now, delivery is planned for the 15th of April 2003.
Product management and Development Richmond have started work for the UC 6.1 release. This product will contain
the following features, in compliance to the requirements in the H3G Global Work Package and the SBC customer
(America):
UC New services (Video mail; Calendaring; Voice activated calling; Voice portal services; conference calling
services)
UC Platform Features (Improved 5.2 with e.g.: MMS push; Support of DSP card, greetings management)
UC Uone Messaging Features (Improved 5.2 with e.g.: Hot List; TUI enhancements; Multi-Line mailboxes etc)
UC OA&M Features (Improved 5.2 with e.g.: COI Multiple Administrators; enhancements of log records;
Business Directory Support etc.)
UC Corporate Message Store Features (Forward/Copy to corporate message stores; POP or IMAP fetch from
CMS; Support of Multiple Email addresses; email alias for responding to emails.)
UC Universal Messaging (e.g. messaging to non-subscribers; VPIM feature to allow the UC platform to co-exist
in an account with embedded legacy systems)
UC Baseline Service Features (e.g.: Jumpstart, Release Migration from 5.2; Customized TUI).

Delivery BackOffice

Ref: http://isis/

continue

Roadmap:
Planned FOA
Expected GA date
Release
1.1
1.2 or 2.0

Messaging Broker

2002
Nov

Dec
1.1

2003
Jan
U1.1

Feb

March

April

May

June

July

August

I1.1

Ready for Delivery


5th December 2002

Expected GA date
March 2003

Unknown

Unknown

U1.1 = upgrade 1.1


I1.1 = installation 1.1
Additional information:
By Pierrette Koumans
Release 1.1
On the 6th of December 2002 the enhanced MB 1.1 was handed over to Product Management. The day after this, a project
started at SFR France. SFR had been encountering many issues with the MB 1.0-1 resulting in the customer not accepting
the system. As a resolution of these issues the SFR MB 1.0-1 system needed to be upgraded to the enhanced MB 1.1
release. This SFR project involved upgrading their test system first, and after that their production system. This needed
to be done before Christmas. Development and CS made this upgrade a success in a joined effort. The SFR acceptance
period is to end mid January 2003. SFR chose not to use the MB 1.1 new functionality, but is content with the systems
current performance and stability.
Dutchtone has bought a new MB 1.1 system. This project will start in January 2003. In this project Development and
Back-Office will verify install ability and ATPs.
Release 1.2

Assessment on the 1.2 Release project have started. Timelines have not been set yet.

2002
Dec

Roadmap:
Planned FOA
Expected GA date
Release
1.1 / H3G
2.0

Centralized Directory Server (CDS)


2003
Jan

Feb

March
2.0

April

May

June

July

August

Sept

2.0

Ready for Delivery


28 February 2003

Expected GA date
14th March 2003

March 2003

April 2003

Additional information:
By Pierrette Koumans

CDS 1.1 will resolve outstanding H3G CRs. Planned release date to SICC is the end of February 2003. The SICC will
release CDS 1.1 as part of the Solution Maintenance release on the 14 th of March 2003.
CDS 1.1 will only be installed for H3G, involving upgrades of the current systems and new installs (via ICE) of the new H3G
systems (Austria, Rome).
CDS 2.0 does target on non-H3G customers. CDS 2.0 is a major release, mainly due to a new STP. The CDS 2.0 is designed
for the Hercules SMSC-project.

Delivery BackOffice

Ref: http://isis/

You might also like