1 / 12

Consult21 Systems Work Package

Consult21 Systems Work Package. John Bonell 21CN Systems. Objectives of the Session. To present the systems work package overview To illustrate how the industry informs our systems architecture and the timeline for deployment

zane-cameron
Download Presentation

Consult21 Systems Work Package

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Consult21 Systems Work Package John Bonell 21CN Systems

  2. Objectives of the Session • To present the systems work package overview • To illustrate how the industry informs our systems architecture and the timeline for deployment • To present our outline strategy for systems architecture proposed for 21CN • To define the business engagement model for: • Consulting on systems architecture strategy • Establishing 21CN requirements that impact the systems solution design and timeline for implementation • To present the overall timeline for the 21CN Programme

  3. Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Key Ofcom Milestone/Event Con. Doc. Concept 10 Jan - WG Proposal Committed Proposal Closure (& Method) Agreed SOR Systems Work Package Introduction • Scope • To explore the system requirements and implications so as to inform product working group discussions • Reach a shared understanding of: possible architectures and platform implications • Focus on Operational Support Systems in the Service Management area • Key Events driving Consultation Timeline • 21CN Systems Scope for Pathfinder and rollout need to be agreed by March 2005 • Will need product requirements • Method of Closure • Architectural discussion with industry reaching consensus on requirements • Systems implementation will be agreed product by product via the product projects

  4. What Influences the 21CN Systems Solution Design? Through direct consultation with our System Solution Designers Customers Systems Architecture Strategy Product Reqs Network Technology / Rollout Systems Solution Design • Through direct consultation via Consult 21 WPs on: • Products • Service Wrap • Systems Interfaces Operational Management Model

  5. The situation today Key Problems • Legacy assumed a vertically integrated company • BTR products are not explicitly built on SMP products. Legacy is not capable of supporting such propositions (i.e. product contains product) • Legacy systems assume a one-to-one mapping between the copper pair and the service. This results in security issues since all the assets are associated with the same DN and CSS does not support security partitioning on a DN. • The current interface from other SPs is based on a proliferation of product specific gateways wholesale products retail products credit vetting1 technical checks1 decomposition1 retail billing1 network1 progress events1 KCI1 Note 1: illustrative functions

  6. Existing B2B Services and OSS platforms • BT Wholesale offer a number of ‘B2B’ interfaces • B2B Channels are Product/Product Family specific (Stovepipes) • B2B Channels are supported by different transport protocols, e.g. ebXML, http(s), ftp • There is no consistent document definition for service request payloads • Difficult to use for multi/inter-related product service requests Current flows approximately: LLU - 1K per week, Broadband - 125K per week, WLR - 50K per week Note: schematic does not cover all processes

  7. Proposed Integration Framework Service Providers • Communication via standardised interfaces • Standardised business processes across all products • Identical message flows anddata formats used for allretailers • Choice of transport and format dependent on Customer Profile B2B protocols (ebXML, Rosettanet) email (SMTP) Web services(http,ftp, SOAP) BT SMP Customer Gateway Transport Management Customer B2B Profile XML(SOX schema) CSV, Tab delimited binary XML (XSD schema) Format & Translation Bt Internal XML (XSD schema) Process Management Bt Internal XML (XSD schema) SMP OSS

  8. Our proposed approach Potential Solution • All retailers use common SMP service management services • Customer, service, and network identifiers explicitly separated • Service-oriented architecture makes modular approach explicit • SMP service management uses shared platforms - no more standalone ‘wholesale product’ systems Today’s architecture 21C Target wholesale products retail products Integration Framework CRM Services Retailersservicemanagement Non-SMP Service Management credit vetting credit vetting1 decompose technical checks1 billing decomposition1 KCI retail billing1 network1 SMP ProductService Management tech checks progress events1 network KCI1 progress Note 1: illustrative functions

  9. Consulting on Systems Architecture Strategy Through direct consultation with our System Solution Designers Industry Customers Systems Architecture Strategy • Establish initial views today • Establish forum / model for receiving / sharing views Systems Solution Design

  10. Establishing 21CN Requirements • Strategic Architecture Realised in line with 21CN Programme releases • May require tactical solutions Industry Customers Product Reqs Analysis Systems Solution Design • Through direct consultation via Consult 21 WPs on: • Products • Service Wrap • Systems Interfaces 31/12 31/03 30/06 30/09 21C Systems Release

  11. Background to Pathfinder – High Level Plan 06/07 04/05 05/06 30/09/04 31/12/04 30/09/05 31/03/05 31/12/05 30/06/05 31/03/06 30/06/06 4.3 Support Trial 1 - PSTN Trunk Offload (01/10/04) Support Trial 2b – POTS for 1000 customers (01/01/05) (Plan & Build/Physical Inventory for Roll out) 4.4 Support Trial 2c – POTS for 1000 customers (01/04/05) (BB access over 2nd Generation DSLAMs & Combo Cards) 5.1 Capacity planning tools for Roll Out (01/07/05) 5.2 Releases Support FOA1 – “final” systems, network & processes for PSTN & new PC Products (01/10/05) 5.3 Support FOA2 – incl. 350k PSTN migration (PATHFINDER) (01/01/06) 5.4 Begin monthly rollout PSTN cutover & BB access, plus PC (new products) capability rolled out nationally (01/04/06) 6.1 6.2

  12. Your Views on Future Consultation

More Related