2. Agenda
1. Project evolution
2. Product selection
3. Product evaluation
4. Current functionalities
5. Current architecture
6. Challenges
Sensitivity : "Unrestricted", "Internal Use Only" or "Confidential" 10/2/2012 Slide 2
3. Project : evolution
2001 : selection of technology
2003 : launch B2C portal as replacement of Broadvision
Self servicing for Telco customer
Evolution in Portal characterized by
1. Usability needs
2. Evolution services : from billing to self management
3. Evolution products :
1. standalone products > combined products
2. shorten life cycle of products
4. Convergence of brands : from fixed line to fixed&mobile
4. Multiple products , configuration, brands
Sensitivity : "Unrestricted", "Internal Use Only" or "Confidential" 10/2/2012 Slide 4
5. Product selection (I)
history – evaluation – future
Main criteria
- Tool :
- Best integration framework (technology / open )
- Interact with best of broad:
- Select best CMS on the market : Interwoven
- Select best webanalytics : Webtrends
- Select best authorization system : Tivoli Access manager
- Partner
- Select based on vision / strategy roadmap / business stability
- Select on base of technological potential.
6. Product selection (II)
Web at 2002 was ‘more technology ’
• E- was limited business critical
• Lower SLA
• Limited interactions with backend systems
• Integration frameworks have a low maturity
• Best of breed was best approach
• Lot of players on the market
• No online customer
• No products for which the web is critical
• Limited social online interactions
• Limited multi- channel / device
Sensitivity : "Unrestricted", "Internal Use Only" or "Confidential" 10/2/2012 Slide 6
7. Product evaluation in 2009
Interwoven
• High number of projects realized
• Technology acceptance / support of software partners
Tivoli Access Manager
• Continuation to Federated Identity Management as priority
• handled partially the portal responsibility
IBM Websphere Portal
• Heavy framework to learn / support
• No leverage on integration pattern : own pattern.
Conclusion : still positive evaluation because
• Technology patterns in new versions considered as promising
• Cost of rebuild was higher than cost of continuation
• Portal still answered on question (like governance, integration)
13. Current architecture (I)
Delivery of an One Telco roadmap
Portal & Identity Provider
FIM
Solution incl tool to manage attributes of the different ‘identities’
TAM WebSEAL
Portal Skynet NGP
Web Login
Bgc E-Services apps Prx E-Services apps
www.belgacom.be TV services www.skynet.be
confidential 02/10/2012
14. Current architecture (II)
Portal & Content management system
Content management system • Navigation
www.belgacom.be • Design – ocss Portal
https://admit.belgacom.be/
Livesite Bgc E-Services apps
Product catologue
Design elements Prx E-Services apps
Configuration
Teamsite Own developed Cms.
16. Current architecture :
Integration pattern
Portlets in portal application
• Monolithic approach
• Central team delivery
• JSR286 linked with Websphere 7; JSR186 too limited – no distributed model
I-frame integration
• Easy integration
• Design guidelines/approach strictly followed
• Behind same authentication system.
• Multiple domains
• Different teams delivery
17. Challenges
products – business roadmap
? Evolve to more personalized website
? Personalisation on public website >< self service on secure environment
? Support multi device websites (incl TV ?)
? Delivery of Apps
• How do we control support/maintenance cost in growing market
? Integration Ordering (Siebel integration )
? Sales channels positioning
? Packs selling – fast changing product offers
? Differentiated self service environment (coorperate >< residential )
? Telco added value services evolution (ex. FON, TV, …)
? Social networks/social interactions
18. Challenges
products – technology roadmap
? Technology– strategy ?
• Build further on own integration pattern for webtooling >< Tool driven
• How to handle more complex integration >< higher availabilty
• Is online e2e integration still possible
• Evolve to limited framework >< complex build product
• Competence building/maintaining > choice of offshore
? Ibm websphere portal 8 (the product we expected to had 3 y ago?)
• Mature package ? It’s an integration of different packages > do we need also all the different skills example for
operations ?
• Evolve from best of breed to package
• ROI investments
• Time to market >< business roadmap >< current ongoing investments
• Stronger business value proposition > how to translate this ?
20. Implemented architecture
- 2008 – upgraded at 2012
Loadbalancer
Webseal Webseal Reserve
Webseal Webseal Proxy
webserver
applicationserver
3 WAS clones for Portal 3 WAS clones for Portal
2 in reserve 2 in reserve
4 CPU 4 CPU
12 cpu 12 cpu
ITD “Profile” DB 02/10/2012 20
Portal DB
Ldap “Content” DB
21. Web Portal roadmap
Areas of interest
Access Access Access
One Web Single Sign-On
Management Management Management
Multichannel / Multi-
Integrate navigation Navigation Navigation Navigation
device capabilities Links
Integration with external parties
Specific Web unified Content
Contents Content Content Content
Applications Management System
Search Search Search
Common Components ONE Search
Engine Engine Engine
Web Portal Application aggregation standards Apps Applications Applications Applications
Web metrics Web metrics Web metrics
One Web metrics & profiling
& profiling & profiling & profiling
Enterprise Integration Foundation
Integration Integration Integration
EAI-BPM-BAM Roadmap
FLS MCS Skynet
Targeted Advertising
e-Services e-Services NextSlide 21
Gen
02/10/2012
portal portal PortalSlide 21
22. What : where do we are
0 10
0
0 10
0
0 10
0
0 10
0
Belgacom confidential
Made by Bart Van Vlierberghe 2006, November
23. Business is KEY
A sponsor on director level is key to facilate the implementation
• Organization of future budgetting & controle enhancements
• Auditing & follow-up of objectives
• Support & find the good concept of introduction
Relation with design team during the project is key to deliver a winning product
• The tools offers aid to designers & developers to be able to talk the same language
Strong business analysis is need to determine to correct needs & finding the good concept
Accent on Webreporting & feedback cycle !!!
ITD 02/10/2012 23
24. Implementation takes time
Good relations with vendor of the software is essential
• Decent knowledge is difficult to find – certainly in your business context
• Buyer of the software remains responsible to take the correct decision over his environment
• WIN-WIN relation
Portal is a technology : it must not be used everywhere; only where it make sense : define your own criteria & concept
Internal developers needs to be supported to learn/grow the tool
• Put the correct contract in place
• Work iterative : do not deliver a shock for business & own teams
Installation; sizing; development concepts; integration & performance tuning !!! Buffers in the projectplan mainly in
installation & stabilization/warranty
ITD 02/10/2012 24
