1 / 24

Present status

Present status. CDR Portal for BSNL internal communication launched PO has been released -23 rd July Coordination meetings were held on 23/06/07, 26/06/07, 29/06/07 and 02.07.07. Site meetings were held on 22/06/07, 25/06/07, 30/06/07 and 03.07.07

albin
Télécharger la présentation

Present status

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. Present status • CDR Portal for BSNL internal communication launched • PO has been released-23rd July • Coordination meetings were held on 23/06/07, 26/06/07, 29/06/07 and 02.07.07. • Site meetings were held on 22/06/07, 25/06/07, 30/06/07 and 03.07.07 • Review meeting conducted at sites on 17/07/07,18/07/07,19/07/07, 20/07/07 • POC SSA’s requirement of equipment for placing POs have been discussed.

  2. SSA MPLS 1 MPLS 2 Ambala Ambala (B2) Chandigarh (A4) Chandigarh Chandigarh (A4) Jalandhar (A3) Dehradun Dehradun (B2) Haridwar Jammu Jammu (B1) Jalandhar (A3) Lucknow Lucknow (A3) Kanpur (B2) Merrut Meerut (B2) Ghaziabad (B2) Shimla Simla (B2) Chandigarh (A4) NIB Node Details

  3. S. No. Item Tender Qty Finalised Quantity Ordered Qty Ambala Chandi garh Dehra dun Jammu Luck now Meerut Shimla 1 Exchange Router 1075 10 16 5 11 17 12 13 90 2 Managed Ethernet Switch (24 Ports) 1075 6 16 5 13 23 6 4 80 3 Ethernet Extender (One Pair) 270 0 4 0 24 20 5 4 60 4 Remote Router 805 0 0 0 10 5 12 5 35 5 Ethernet Switch (Unmanaged, 16 Ports) 1075 4 5 2 16 15 8 9 65 6 Aggregation Router 127 2 2 2 2 1 2 11 7 Additional Module (4 ports E1) for AR 254 0 4 6 8 Additional Module (1 port E3) for AR 127 0 9 Central Router 23 1 1 1 1 4 10 Additional Module (4 ports E1) for CR 46 1 3 6 11 Additional Module (1 port E3) for CR 46 0 12 Additional Module (STM-1) for CR 23 2 2 2 2 2 2 14 Finalised Requirement of N/W Equpt for North Zone

  4. S. No. Item Tender Qty Finalised Quantity Ordered Qty Ambala Chand-igarh Dehra-dun Jammu Lucknow Meerut Shimla 1 MTE for E-10B 51 2 8 0 0 3 3 18 2 CES for C-DoT 431 7 0 1 8 1 4 11 35 3 IP Phones 766 20 15 10 10 22 20 10 112 4 Workstations (PCs) 1148 25 20 15 16 27 15 14 200 5 MS office 25 20 15 16 27 15 14 200 6 AntiVirus for Workstations 4290 25 20 15 16 27 15 14 200 Finalised Requirement of Other Equpt for North Zone

  5. Networking • Reliable Transmission Media is Required. • Maintenance of the transmission links Connecting Datacentre with MPLS shall be made over to the Concerned Regions • Existing maintenance incharges shall continue to maintain the links connecting the SSAs to the nearest MPLS node and the links connecting different exchanges

  6. Networking (Contd..) • Bandwidth between Aggregation Router to MPLS shall be E3/ STM1 • Backbone Routers in DC shall be connected to two MPLS nodes, each connectivity shall be 1Gb • This connectivity shall be extended through TWO nos. of STM16 rings – to connect to two nodes. • STM-16 equipment (CPE) with a provision to have 1Gb port should be installed at DCs • The entry and exit routes of OF cable within the DC premises should be different. • Internet Routers in DC shall be connected to two NIB nodes, each connectivity shall be E3/STM1

  7. Preparedness of switches • Readiness of the switches for 100% CDR generation for all the calls. • Availability of at least one week CDR storage capacity in the switches. • Availability of X.25 interface for pulling the CDR files. • Speed of data transfer of X.25 interface to be minimum 64 Kbps. • Conversion of all CDOT RAX switches and standalone CDOT SBM switches to ANRAX and RSUs. • Software upgradation of C-DoT MBMs to 2_2_1_9. • Standardization of the values of the Subscriber parameters.

  8. SSA SDCA CDOT SBM RAX Ambala Nil Nil Chandigarh Nil Nil Dehradun Chakotta Nil 3 (Koti, Tuni, Chillhar) Jammu Basoli Nil 3 (Bani (2), Mahanpur (1)) Jammu 1 (Trilokpur) Lucknow Malihavad Nil 12 (Manigunj, Gahdeo, Garhi, Kahela, Kasmandikala, Aalal, Kadhawara, Komharawan, Mall, Navioanah, Sansarpur, Dedaman Pending CDoT conversions Contd…

  9. SSA SDCA CDOT SBM RAX Merrut Nil Nil Shimla Shimla 1 (Drogra) Rampur 3 (Delath, Madhavani, Kangal) Rohru 2 (Dodragur, Dhamwari) Nimand 1 (Dalash) 2 (Binan, Kotasiri) Theog 4 (Majhauli, Pulbal, Gomma, Sainjakhad) Recongpeo 1 (Sangla) 2 (Purban, Raksham) Pooh 1 (Moorang) 5 (Chango, Yangthang, Gaibang, Namgia, Nesang) Kaza 6 (Kibber, Hurling, Losar, Tabo, Sagnam, Schling) Pending CDoT conversions (contd)

  10. POC SSAs – PCs & Antivirus status • All PCs should have Win XP or Win 2000; Should have a browser. • All SSAs should ensure valid and updated anti-virus running on PCs • If necessary old PCs may be replaced with New PCs of required config • All Dumb terminals working for DQ, FRS etc should be replaced with PCs • SSAs have to procure work station PCs for any newly planned CSCs • If any CDMs/Touch screens are provided in the SSAs, details about connectivity, configuration, Integration of software etc may be intimated.

  11. S. No. SSA Billing Commercial DQ FRS 1 AMBALA Trichur Integrated with Trichur COSS Integrated with Trichur 2 CHANDIGARH DOTSOFT DOTSOFT DOTSOFT DOTSOFT 3 DEHRADUN DOTSOFT DOTSOFT DOTSOFT/ Commandir Commandir 4 JAMMU DOTSOFT DOTSOFT DOTSOFT DOTSOFT 5 LUCKNOW Trichur COSS Commandir COSS 6 MEERUT DOTSOFT DOTSOFT DOTSOFT Commandir 7 SHIMLA Trichur CCMS CCMS CCMS POC SSAs – Existing Software Applications All India Status – Dotsoft in 183 SSAs; Trichur in 147 SSAs out of 334 SSAs

  12. POC SSAs – Data cleansing issues • Customer data across various systems such as Billing, Commercial, FRS and exchange data shall be cross checked to see that there is uniqueness in the data • Existing customer data shall be purified by removing duplicates etc. Customer categories shall be properly identified and mismatches corrected. • Finalisation of closed cases should be completed and Special drive should be taken to clear Outstanding cases by setting up HPCs

  13. POC SSAs – Data Collection items • All existing connections of a Customer (office, home, Mobile, LC shall be obtained as far as practicable for creation of unique customer ID • Group id can be a corporate id or family id • Corporate id/Family id shall be created for corporate groups/Families where in customer ids may be a subset. • Mobile (even if non-BSNL) and e-Mail of the customer should be taken for SMSing/ eMailing the customers any service related information/issues

  14. POC SSAs – Data related to provisioning • Exchange related information such as • Vacant numbers, • Date on which the no. became vacant, • NE numbers, • Catgegory specific port information for provisioning of PCO , ISDN or CLI cases, • Faulty NEs in both swiches and DLCs • DSLAM related information (spare ports, faulty ports) • should be prepared

  15. POC SSAs – Data related to FRS • MDF& OD information like • Vertical no., • NE No., • Cabinet details, • Pillar No., Pillar-in, Pillar-out, • DP No., DP Tag, • Block wiring details, • DLC and DSLAM details, • Staff no. contact nos. of the lineman/JTO/TTA/SDO/DE, shall be verified and updated.

  16. POC SSAs – Data migration issues • Migration of data of both closed and working customers • Installation address and billing address along with PIN code. • All unpaid bills and paid bills for the past 6 months. • Bank code and branch code for customers using ECS • Other data such as debits, credits, DEPOSITS, accessories and facilities.

  17. POC SSAs – Data migration issues • For a customer • Class code (Individual, Service, PCO, TAC etc.) • Category code • Rural/ Urban • Plan or Usage rate IDs • Billing schedule • RATING – Duration based or MCUs ?

  18. Basic Services Call Centres • Circlewise Call centres established at Uttaranchal and Haryana (Outsourced) • SSA wise / Cluster of SSAs wise call centres to migrate to Circlewise Call Centres

  19. S No SSA Circle/SSA Based On No of positions IVRS ports Equipment owned by 1 HP -- -- -- -- -- 2 HR =>Gurgaon Circle EPABX based 27 60 Outsourced 3 JK (**) 4 PB => Patiala (**) SSA EPABX based 17 240 5 UP(E) => Lucknow (**) Cluster of 8 SSAs Server based 8 190 6 UPW => Meerut Cluster of SSAs Server based 10 106 BSNL => Bareilly Cluster of SSAs Server based 10 106 BSNL => Noida Cluster of SSAs Server based 10 106 BSNL 7 UAL => Dehradun Circle EPABX based 16 30 98 838 Call Centres - Existing Status (as on 31.5.07) ** Tender evaluation under progress

  20. Call Centres in CDR Tender • Procuring the call centre equipment: • IP EPABX • IVRS • CTI • ACD • IP Phones • Circles to procure PCs for call centre positions (if required)

  21. Zone Existing Proposed Subscribers ( In Millions) 71.4 71.4 Agents 98 766 FAX Capability -- 16 faxes at any given time Minimum IVRS Port requirement including DR (Without FAX ports) 838 1547 IVRS Configuration

  22. Responsibility matrix • Zonal Coordinators: • Coordination with Civil and Electrical • Coordination with SIs • Coordination with NIB • Coordination with Telecom Regions • Coordination with other circle coordinators • Receipt and maintaining stores of Data centre

  23. Responsible matrix (Contd..) • Circle/SSA Coordinators: • Preparation of switches for CDR Project • Upgradation of PCs whereever required • Anti-virus • Making Available Transmission links for Project rollout • Maintenance of CSR and Switch (CDR) network • Maintenance of Call centre • Receipt and maintaining stores

  24. Status of Data Centre - Chandigarh • Site meetings were held on 27/06/07 and 17/07/07 • Some of the pending issues • Finalisation of Layout • Finalisation of Power requirement • Review of Civil and Electrical Works after finalisation of Layout and Power requirements • Review of transmission and network requirements

More Related