Presentation on theme: "1 EBC Evolution Refresher 27 th May 2005 BT Wholesale 1, City Place, Gatwick."— Presentation transcript:
1 EBC Evolution Refresher 27 th May 2005 BT Wholesale 1, City Place, Gatwick
2 EBC Evolution Refresher Introduction and Welcome
3 Objectives of the day Understand the drivers behind EBC Evolution Understand EBC Evolution Understand where we are today and what you should do
4 Agenda 10.00Coffee and Registration 10.30Introduction & Welcome 10:40Brief history of EBC Why EBC Evolution ? EBC evolution - workshops with OfCom and Industry involvement What is EBC Evolution ? The importance of your Routing Plans The new EBC files Important next steps 11.45Questions 12.15Summary 12:25Introduction to a new BT Interconnect Telephony Tool – “SIMPLE” 12:40Lunch
5 Brief history of EBC 1/5 Before 1993 Conveyance charges based on retail model Consultation with the Industry System trialled by some Operators Distance component added in All Operator charges based on EBC methodology Charging scenarios catered for are: BT terminated geographic calls Transit calls BT originated IA,CPS,118DQ,NTS (CLI model).
6 Brief history of EBC 2/5 Based on least cost path principle Derived from network and number data Based on switches and distance Updated quarterly using network snapshot 1 month before the live date.
7 Brief history of EBC 3/5 Data is acted on by a set of rules based on Least cost path: Rule 1: LOWEST nos.of exchanges calls would pass through: derive Charge Band Local Exchange Segment Single Tandem & Single Tandem Transit If call would pass through more than one tandem switch:-
8 Brief history of EBC 4/5 For Double Plus Tandem & Double Plus Tandem Transit Rule 2: SHORTEST TOTAL distance from POC to Dest’n switch. Once shortest path is chosen then derive charge band. Use inter-tandem distance to determine:- <100km- Short 100km<200km- Medium 200+km- Long.
9 Brief history of EBC 5/5 There are three columns of information in the EBC matrix: Unique NNI (Network Node Identifier) for any POC (point where a call can enter the BT Network) The destination Number String reduced in length by “Number Retardation” 525 Three digit code represents the EBC Charge Band.
10 Why EBC Evolution? Large Complex Customer charging queries often received Uncontractual routeings shown Difficult to explain the different charging algorithms Result of many Industry workshops to address the above
11 What is EBC Evolution? 1/2 Removal of disallowed routing from EBC Instead of calculating where calls will exit the BT network, agreed EXIT POCs - as held in CP’s routing plans - will be used Creation of a new database to store routing plans Provide on-line access for updates to routing plans Provide two new files for CPs to use to decide where best to send and receive calls to BT
12 What is EBC Evolution? 2/2 No change to charging for BT-terminated traffic EBC Evolution will use Exit POCs shown in CP routing plans for IA, CPS, 118 and transit Least cost connectivity path to get to the agreed exit POC Changes to internal EBC systems, but not the use of EBC data
13 Importance of Routing Plans Use Routing Plans and DMAs (Data Management Amendments) The exit POC for a given origin will be that agreed to be in place when the EBC data goes live The Routing Plans will directly drive EBC Charge Bands via Exit POC These show BT Switches that will pass calls to OLOs by Number range Also show the “Catchment Area” of each such switch Include Dates for when submitted by CP, Agreed with TAM, DAM received and when DAM Implemented TAMs (Technical Account Managers) have loaded the existing routing plans into RPD (Routing Plan Database) and are now running in parallel with the excel files Direct access for CPs later this year (2005)
14 Importance of Routing Plans The information in your routeing plans will affect your invoice They should be reviewed regularly
15 The New EBC Files 1/5 Two New Files A new file to assist CPs receiving traffic from BT A new file to assist CPs delivering traffic to BT Standard EBC file format Standard naming convention Standard header and trailers Comma-separated format data records
16 The New EBC Files 2/5 File 1 – Receiving Traffic from BT A BT-switch-to-BT-switch matrix, with charge band Any traffic type Valid call routing scenarios E.g. a DLE origin would be shown against the following destinations: For BT-originated traffic, the DLE itself and all switches that could be Exit POCs For transit traffic, nothing Each data record will contain: origin exchange NNI, destination exchange NNI, EBC charge band Transit / Non-transit charge bands
17 The New EBC Files 3/5 File 1 – Benefits to CPs Transparency Trunk-to-trunk connectivity Routing plan applicability Mapping to catchment areas All possible points of connect covered
18 The New EBC Files 4/5 File 2 – Delivering Traffic to BT Point of connect to number block, with EBC charge band Full-length number blocks Valid call routing scenarios E.g. a WAT origin would be shown against the following destination number blocks: BT number blocks hosted on directly connected DLEs CP number blocks accepted at this WAT Each data record will contain: origin exchange NNI, destination number block (unretarded, charging level), EBC charge band
19 The New EBC Files 5/5 File 2 - Benefits to CPs Discrete number blocks Only valid routing shown Route Optimiser-friendly No need to expand out retarded number blocks Invalid routings will not be shown
20 Important Next Steps Next EBC matrix will use EBC Evolution You must review your routing plans as these will affect your bill When published run checks Open up new connections as necessary Use the two new files: Switch to switch file - where to receive calls POC to Number Block file - where to deliver calls to BT Talk to your TAMs
21 EBC Evolution Refresher - Summary Brief History of EBC Why EBC Evolution What is EBC Evolution Routing Plans New files Important next steps
22 EBC Evolution Refresher Any Questions?
23 EBC Evolution Refresher Thank you.
24 File 1 – DLE Example , , , ,521 … , , , , , ,525 … , , , , , , , ,525 … , , , , , , , ,525 … , ,521 Directly connected WATs WATs tandemed with directly connected WATs All SYSX DMSUs Itself Middleton Unit C (DLE) All NGS DMSUs Directly connected SYSX DLTEs Directly connected AXE10 DLTEs
25 File 1 – Trunk Example All SYSX DLEs and DLTEs All SYSX DMSUs All ASUs Ipswich Morganite (NGS DMSU) All NGS DMSUs … , , , , , , , ,523 … , , , , , ,529 … , , , , , ,525 … , , , , , ,529 … , , , , , ,525 … All AXE10 DLEs and DLTEs
26 File 2 – DLE Example , , , , , ,520 … , , , , , , , ,520 … , , , , , , , , , , , ,520 … , , , , , ,520 … , , , , , ,520 Unretarded BT number blocks hosted on DLE Ipswich Unit B (DLE)