2010 FTTH Best Practices for Bundle Services
Upcoming SlideShare
Loading in...5
×
 

2010 FTTH Best Practices for Bundle Services

on

  • 1,909 views

FTTH has arisen as the most relevant access technology choice for service providers in North America to deliver next-generation services. With Google’s interest in FTTH, the National Broadband Plan ...

FTTH has arisen as the most relevant access technology choice for service providers in North America to deliver next-generation services. With Google’s interest in FTTH, the National Broadband Plan and the broadband stimulus efforts, FTTH is the future of connectivity across the continent. As deployment of FTTH networks reach a critical mass, service providers are looking to deliver new innovative service bundles over these networks in order to maximize their network infrastructure investments and gain the advantage over competitors in their serving areas. However, in order to bring these new services to market in the most efficient way, there is a key element of their operations infrastructure that must be highlighted.

Operational support systems (OSS) have always been a key element of service provider networks. Yet, as new services are introduced and service providers must balance managing their new FTTH network with existing DSL, wireless and possibly HFC networks, OSS service fulfillment becomes crucial to the success of a service provider.

This presentation will outline the best practices for OSS service fulfillment in managing a FTTH network itself, or in combination with a multi-network deployment.

Statistics

Views

Total Views
1,909
Views on SlideShare
1,907
Embed Views
2

Actions

Likes
0
Downloads
94
Comments
0

1 Embed 2

http://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Multiple products and levels: The product, in the eyes of end-users, is becoming an “experience” that is based on the delivery of voice, video, and data as an integrated package across mobile and fixed infrastructure which, deconstructed reveals multiple layers of hardware, software, and services. Current Product catalog offering have evolved from billing systems and suffer from lack of functionality, poor integration, and lack of inability to access service catalogs. Rapid technology innovation (and obsolescence): While convergence creates new opportunities for growth through innovation, competition is intense as companies race to gain first-mover advantage — which accelerates obsolescence at all levels. Diverse Product Supplier: Far from the days of the vertically-integrated monopoly of the past, today’s typical Telecom supply chain is a highly fragmented global operation where multiple enterprises (and supply chains) must collaborate to design, develop, and deliver a coordinated experience. Used to be 90% internal; 10% external interactions; this is shifting as NGOs need to up their competitive responsiveness; general trend to increase reliance on partners. i.e. Google Maps Allows for the validation of the services via geography, network Product catalogs are typically siloed to specific areas of the NGO; evolution from individual product offering and services

2010 FTTH Best Practices for Bundle Services 2010 FTTH Best Practices for Bundle Services Presentation Transcript

  •  
  • Best Practices to Deliver Innovative Service Bundles Kerbey Altmann Session: T-904-G Wednesday, 9 AM
  • Speaker Contact
    • Kerbey Altmann
    • Director, Solutions Architecture
    • Sigma Systems, Inc.
    • [email_address]
    • +1 650.401.3678
  • Why bundle?
    • ATTRACT: Price remains a key decision factor in choice of Service Provider, and so bundling offers key part of perceived value proposition
    • RETAIN: Selection/churn decisions are made across the bundle of services and not just one service
    • RETAIN: Creates stickiness for the service provider. Bundling seen as the main reason for 5yr+ loyalty
    • GROW: Provides a means to increase ARPU
  • Best Practices to Deliver
    • Products and Service Catalog Integration
    • Support for Multi-Technology Networks
    • BSS/OSS Order Management Integration
    • Service Transformation
  • Products and Services Catalog Integration
    • Dispersed and unsynchronized Product and Service information
    • No single view of products and services
    • No control over product design, creation or reuse
    • No standardized definition of products and services
      • Slow and costly time-to-market for new products
      • Inability to build triple / quad play offers
      • Little or no integration between systems
      • No performance analysis
    Product & Service Management Chaos
  • Issue: Application Silos VOICE VIDEO DATA
  • Present
  • Consistent Services
  • The Bundle
  • Service Reuse
  • Multi Device/Technology
  • Benefits of Converged Services Layer
    • True service layer abstraction
      • Change out of Device Provisioning without impact to upstream BSS layers
      • Support for multiple access technologies
      • Rapid rollout of new services on infrastructure
    • Support for both network and third party partner fulfillment
    • Rapid reuse of value added services across multiple access technologies
    • Repository of Subscriber-Service-Resource information
    • Automatic recognition of impacted subscriber services and reprovisioning on network/resource changes
      • Segmentation and congestion relief, etc
  • Service Fulfillment for the Bundle
    • Lies between Order Capture Systems and downstream systems
    • Provides overall control, management, status and orchestration of a customer order
    • Interacts with Product and Service Catalogs to process bundles
    • Flow Through Automation
  • Service Order Management
    • Complex orders found in the Bundle
    • Order management decomposes the bundle
    • Service Orchestration determines the correct flows
    Customer Profile & Other BSS Order Manager OSS/J API Order Entry Product Specification Service Activation Order Service Orchestration
  • Benefits
    • Reduce bundle processing costs
    • Improved order accuracy for complex bundles
    • Flow through automation virtually eliminates manual processing
    • Elimination of swivel chair processing
  • Service Layer Transformation
    • One OSS platform to support all service offerings; eliminate “silos”
    • Service portability and re-use to be delivered across any network
    • Standardized interfaces to enable extensible integration between BSS & OSS systems
    • Abstraction of the network layer to ease the process of new bundle introducution
    • Unifying the view of subscriber knowledge for usage, campaigns, up-sell, and targeted ads
  • Case Study 1 - Before
  • Case Study 1 - After
  • Case Study 2 - Before
  • Case Study 2 - After
  • Questions? Chart -