Appointment of Third Party Auditor (TPA)

Transcription

1 Request for Proposal (RFP) for Appointment of Third Party Auditor (TPA) for Madhya Pradesh State Wide Area Network (MPSWAN) Tender No. : MPSEDC/ADCGM/MPSWAN/404 Madhya Pradesh State Electronics Development Corporation Ltd. 147, Zone 1, M P Nagar, Bhopal Phone , Fax No Page 1 of 48

2 TERMS AND DEFINITIONS 1. Authorized Representative shall mean any person authorized by either of the parties. 2. Bidder means any firm offering the solution(s), service(s) and /or materials required in the RFP. The word Bidder when used in the pre award period shall be synonymous with Bidder, and when used after award of the Contract shall mean the successful Bidder or Vendor with whom MPSEDC signs the agreement for rendering of services for MPSWAN. 3. BHQ shall mean Block Head Quarter 4. BOOT model means Build Own Operate and Transfer (BOOT) model. 5. BoM shall mean Bill of Materials 6. CHQ shall mean Commissionery Head Quarter 7. Contract is used synonymously with Agreement. 8. Default Notice shall mean the written notice of Default of the Agreement issued by one Party to the other in terms hereof. 9. DHQ shall mean District Head Quarter 10. Final Acceptance Test (FAT) means the acceptance testing of the network including equipment at SHQ, all DHQs, all SDHQs/ BLOCKs and all co-located & remote offices. 11. Fraudulent Practice means a misrepresentation of facts in order to influence a procurement process or the execution of a Contract and includes collusive practice among Bidders (prior to or after Bid submission) designed to establish Bid prices at artificial non-competitive levels and to deprive MPSEDC of the benefits of free and open competition. 12. GoI shall stand for the Government of India. 13. GoMP shall stand for the Government of Madhya Pradesh. 14. Implementation Period shall mean the period from the date of signing of the Agreement and up to the completion of time period of contract. 15. ITIL means Information Technology Infrastructure Library (ITIL) 16. "Law" shall mean any Act, notification, bye law, rules and regulations, directive, ordinance, order or instruction having the force of law enacted or issued by the Central Government and/ or the Government of Madhya Pradesh or any other Government or regulatory authority or political subdivision of government agency. 17. LoI means Letter of Intent which shall constitute the intention of the Tenderer to place the Purchase Order with the successful bidder. 18. MPSEDC means Madhya Pradesh State Electronics Development Corporation Ltd. the implementing agency for MPSWAN. 19. MP shall mean the state of Madhya Pradesh. 20. MPSWAN shall mean Madhya Pradesh State Wide Area Network. 21. Partial Acceptance Test (PAT) means the provisional acceptance testing of SHQ, CHQ, DHQ and all BHQs. 22. "Party" means MPSEDC or Bidder, individually and Parties mean MPSEDC and Bidder, collectively. 23. PoP refers to Point of Presence with respect to MPSWAN setup in State. 24. Remote Office means the office located at a distance of more than 1Km from the respective Centre. 25. Request for Proposal (RFP), means this detailed notification seeking a set of solution(s), services(s), materials and/or any combination of them. 26. Requirements shall mean and include schedules, details, description, statement of technical data, performance characteristics, standards (Indian as well as International) as applicable and specified in the RFP. 27. "Service" means provision of Contracted service as per this RFP. 28. Site shall mean the location(s) for which the Contract has been issued and where the service shall be provided as per agreement. 29. STPI means Software Technology Parks of India, the consultant for MPSWAN 30. SHQ shall mean State Head Quarter 31. "Third Party Agency" means the successful bidder, appointed by MPSEDC for monitoring MPSWAN during commissioning and operation. 32. Termination Notice means the written notice of termination of the Agreement issued by one Party to the other in terms hereof. 33. TULIP Tulip Telecom Ltd. is the vendor for MPSWAN Page 2 of 48

3 I Introduction About MPSWAN Scheme The National e-governance Plan (NeGP) of Government of India has a clear focus on improving delivery of government services to citizens, e-governance is noted to play a very active role in this endeavor. NeGP recognizes that creation of basic IT and service delivery infrastructure by the States is essential for effective and cost efficient deployment of e- Governance, with this view, NeGP recognizes to undertake three core projects of State Wide Area Network (SWAN), State Data Centre (SDC) and Common Service Center (CSC) are being established in every State. Department of Information Technology, Government of India is providing support for these projects to the state. SWAN (State Wide Area Network) is envisaged as the converged backbone network for data, voice and video communications throughout the State and is expected to cater to the information communication requirements of all the departments. Key focus of the SWAN project is on high service delivery. As per SWAN policy, all States/UTs are implementing SWAN under two Options. Under the first Option, the State is to select a suitable Public Private Partnership (PPP) model and get the SWAN commissioned and operated for 5 years by a private Network Operator. In the second Option, the SWAN for the States/UTs would be set up and operated for 5 years by the National Informatics Centre (NIC). In either of the Options a Third Party Auditor (TPA) is required. SWAN is planned to be a high speed, high capacity, reliable intra-state and inter-state network planned to deliver G2G, G2B and G2C services. The network would have minimum bandwidth 2 Mbps connectivity between the states head quarters and the district head quarters, the network would provide high uptime, redundancy, backup etc. Strict Service Levels agreements are signed between the stakeholders to ensure that the service levels are maintained. Moreover the design of SWAN is to ensure Standardization & Interoperability as well as security of the networks. The SWAN deployment takes place both vertically and horizontally, the main backbone of SWAN connects the State Head quarters PoP with the PoPs at Commissioner Head Quarters (CHQ) which in turn are connected to the respective PoPs at District HQs. The DHQ PoPs are connected to Sub district/ block level headquarters (BHQ). Moreover the various state offices are also proposed to be connected horizontally with the closest respective PoPs. Typical equipment to be deployed at these PoPs and to be maintained by the implementing agency includes routers, switches, modem, racks, RAS, AAA, NMS, Servers, VoIP Phone, Desktops, UPS, Generators, Air Conditioners etc. Page 3 of 48

4 II THIRD PARTY AUDITOR (TPA) TPA is required to provide dedicated Man power for entire contract period with MPSEDC. It is expected at least one person need to be deployed at the SHQ location and further a team shall be required to undertake the site visits as per the requirements of the RFP. Arranging access to NMS and related systems shall be MPSEDC s responsibility. Further, MPSEDC shall provide office space at the SHQ location with facilities like furniture, power connection, telephone/fax connection etc. The equipment for TPA s team (like laptop/workstation, printer etc.) shall be TPA s responsibility. All the PoP equipment shall be under purview of this TPA contract. The details list of the same shall be provided. For any additional equipment to be monitored within the existing PoPs, the TPA charges shall be calculated proportionally as per the proportional increase in cost compared to the total cost of the equipments as per list given in this document. 1. TPA - Scope of Work Third Party Audit shall include monitoring the performance of MPSWAN with a view to ensure desired Quality of Service (QoS) by the Network Operator and bandwidth service provider, as defined in the respective SLA s, signed between MPSEDC, Bandwidth Service Provider and Network Operator. These Guidelines define the broad areas of work, which TPA shall perform for a period of five years from the date of final acceptance test of the network. However, the TPA shall be appointed immediately, preferably before the acceptance testing and commissioning of MPSWAN. 2. To understand the project, TPA would be required to a) Study the contract signed between the GoMP and the Network Operator and Bandwidth Service Provider. b) Study the network architecture & design and the services envisaged. c) Review communication process among the stakeholders (Government of Madhya Pradesh, Madhya Pradesh State Electronics Development Corporation Ltd., Tulip Telecom Ltd., Bandwidth service providers and DIT-GoI). d) Create frameworks and procedures for audit. e) Study the functionality of the Network Monitoring System (NMS) installed in the SWAN and identify the gaps, if any, required for TPA scope of work. The additional module/tool including hardware/software required for the same will be procured by the respective State and TPA would assist the state with the procurement process for the same. f) Review of the escalation mechanisms being followed to resolve any issues between MPSEDC and Tulip related to MPSWAN. 3. Acceptance Test (PAT, FAT) a. TPA shall review the detailed acceptance test plan in consultation with MPSEDC after taking into account any comments/suggestions of DIT. b. TPA would also conduct audit of the process, plan and results of the Acceptance Test carried out by Tulip. TPA shall verify availability of all the defined services as per the contract signed between Tulip and MPSEDC. Tulip shall be required to demonstrate all the services/features/ functionalities as mentioned in the agreement. Page 4 of 48

5 4. Inventory a. TPA audit would include verification of completeness of bill of material for each PoP. b. TPA audit would include review that all hardware and software items have been installed at the sites as per the contract. c. TPA audit would include maintenance of an inventory register to have PoP wise equipment list, including hardware and software. TPA audit would also include updating inventory registry in event of any changes in the inventory. Inventory Audit is to be performed annually and the relevant changes in the year of the audit shall be recorded. Inventory Details shall be provided by the State and TPA shall maintain a record at its end, which shall be updated by TPA based on information provided by the State. Also, the verification will be done through tools and through site visits as explained in RFP. These exercises would include review of documentation, physical verification on a sample basis. The sample size to be decided mutually between MPSEDC and TPA and reports generated using NMS. 5. SLA Monitoring Audit SLA monitoring would include audit of the performance of network. Network includes the components provided and operated by Tulip and bandwidth provisioned by the bandwidth service provider. Subsequently, TPA would carry out the following tasks: a. TPA audit would include preparation of templates for reports to be submitted by Tulip to TPA/State and report to be submitted by the TPA to the State. TPA shall also tabulate measurable parameters as defined in the respective SLA s with Tulip and bandwidth service provider. b. TPA shall review the configuration/deployment parameters of the NMS and the process followed to ensure that the reports generated are authentic. c. TPA would proactively convey to the stakeholders any concerns based on the information generated using NMS. d. TPA would provide quarterly certification of network availability and perform penalty computation for the calculation of QGR to be paid to Tulip as per the SLA and payment conditions mentioned in the agreement between Tulip and MPSEDC (on Quarterly basis). e. TPA would also undertake proactive monitoring of the links provided by the bandwidth service provider based on the SLA signed by the bandwidth service provider. The Agency shall submit reports on the same to the government who would use these reports for making the payments to the bandwidth service provider. f. TPA audit would also include site inspection to verify those parameters of the SLA, which cannot be monitored using NMS. These site visits would be done for atleast 5% of the sites (at each network tier) per quarter. 6. Usage Audit a. TPA would appraise MPSEDC about the health of the network through reports indicating the bandwidth utilization, scalability requirements as per the current and envisaged State level applications etc. Page 5 of 48

6 b. Only the overall Recommendation for Expansion is covered under the purview of this contract. For detailed activities like designing, BoM, specifications etc. MPSEDC is expected to engage an Agency separately. 7. Security Audit a. TPA would perform security audit of MPSWAN as per the Guidelines issued by the Department of IT, Govt. of India and submit recommendations to MPSEDC indicating the risk elements in the network operations. b. TPA would perform the penetration testing and vulnerability testing on the SWAN network. c. TPA would review the rules and policies for network components such as firewall, IDS etc. d. TPA would review the network security policy of the GoMP and suggest recommendations if any. e. TPA would review the policy of granting access to the SWAN network. f. TPA would conduct the Security Audit half yearly. 8. Helpdesk & User feedback a. TPA audit would include review of the helpdesk setup by the Network Operator and would submit a Quarterly Report with recommendations to the MPSEDC. b. TPA would review the mechanism of obtaining user feedback on quality of service & post analysis of the same, and would submit a report with recommendations to MPSEDC. This task would be done on a yearly basis. 9. Exit Process Support This role is envisaged with the objective of ensuring preparedness of MPSEDC at all the time for any eventuality resulting in termination of contract. TPA audit includes support/ advice in the event of exit of the SWAN operator. The Agency would: a. Review the exit process as per the contract. b. Advise the State on documentation, process and procedures necessary for taking over the network from the SWAN operator. c. Provide advisory support during the transition period from the current SWAN operator to the new operator. d. Conduct audit readiness of the State for such an eventuality on a Yearly basis. MPSEDC in consultation with DIT, GoI and the GoMP, would institute a separate audit by an Agency at a National level which would carry out risk based sample audit of the methodology, process and documentation adopted by the TPA in order to ensure that the processes adopted by the Agency is of international standard. TPA would undergo one such audit in a year. However, this would be decided by Dept. of IT, GoI and notified separately to GoMP. Page 6 of 48

7 10. TPA Deliverables Key deliverables of the TPA for the project includes: Sl. No Deliverables Periodicity 1 Review/Study of completion report for SHQ, DHQ, BHQ and colocated Once & remote offices after Final Acceptance Test (FAT) depending on the project plan defined in the RFP/contract. 2 Assessment Framework for Performance Audit incorporating Once following: Assessment parameters based on GoMP s policies and guidelines regarding networking, security IP addressing schemes, migration strategy, and GoI s interoperability and security standards. Tabulation of measurable parameters for SWAN infrastructure (network and other elements). Formulation of scripts and schedules. Map the SLA conditions and limits onto NMS. Review of processes of interaction between Tulip, MPSEDC and bandwidth provider. Template for reports to be submitted by Tulip to TPA on a regular basis. Also make sure that NMS reports are not modified. 3 Performance Audit reports of MPSWAN Weekly, Monthly and Quarterly 4 Report on network availability and other SLA conditions with Quarterly final recommendations for release of QGR after penalty computations 5 MIS reports relating to uptime, downtime of the network etc to Quarterly measure the health of the network based on PoP, Network components etc. 6 Security Audit Report Half yearly 7 Exit Readiness Report Yearly 8 User Satisfaction Survey Yearly Page 7 of 48

8 11. Roles and Responsibilities Matrix Sl. No. Activity MPSEDC Consultant, STPI 1. Installation and Commissioning of MPSWAN 2. Monitoring the Installation and Commissioning of MPSWAN 3. Provision of office space at SHQ and authorization for monitoring, visiting MPSWAN PoPs 4. Fulfillment of GAP in NMS specifications vis a vis the requirements intimated by TPA Network Operator, Tulip 5. Acceptance Test TPA 6. Onsite Inspection and Verification of Acceptance Tests 7. Issue of Final Acceptance Test Certificate 8. Operation, Management and Maintenance of MPSWAN 9. Centralized Monitoring from NOC (24x7) 10. Supervision of the Monitoring of MPSWAN 11. Periodical Generation of NMS report 12. Verification of the NMS Report 13. Approval of NMS Report 14. Periodical Auditing of MPSWAN 15. Submission of the Audited Report of MPSWAN Page 8 of 48

9 III Madhya Pradesh SWAN Details INTRODUCTION Government Of India while formulating guidelines for extending Technical and Financial support to various State Government for State Area Network (SWAN), entrusted upon augmenting present infrastructure available (If any) with State Governments for the purpose of achieving desired objective of providing seamless flow of information amongst various government departments offices located all over the states. There are tentatively 51 Numbers of State Government Departments, 09 Public enterprises and 41 Organizations in Madhya Pradesh and which may use SWAN for their e-governance projects. 1. Madhya Pradesh SWAN Architecture As per the proposed Network Architecture of SWAN, POPs are divided into four groups: Tier-1 POP--NMC at Bhopal.: 01 Tier-2 POP -- all Divisional HQ: 09 (Excluding State HQ) Tier-3 POP -- all District HQ: 40 Tier-4 POP -- at Block/Tehsil HQ: 310 Apart from this the proposed SWAN network will be divided into two parts namely:- SWAN Backbone User Departments Connectivity SWAN Backbone will be through conventional lease lines and all MPSWAN backbone lease lines will be terminated on the Routers placed at every SWAN POPs. Lease lines required for the SWAN network will be ordered directly by MPSEDC, However coordination and commissioning schedule of the same will be done by TULIP. 2. Network Architecture Network is divided into 4 tiers i.e.tier1, Tier2, Tier3 & Tier4 with each layer representing following segments: Tier1=State NMC having Core Routers, Switches & other G/w level devices Tier2=Distribution/Access Routers & other devices at Divisional HQ POP s. Tier3=Distribution/Access Routers & other devices at District HQ POP s. Tier4=Access Routers & other devices at Block Level POP s The state NMC will be located at Bhopal the Madhya Pradesh state capital. Tiered Network Architecture Design Motives Establishing State wide inter-connectivity Vertical Offices-State NMC, 9 Divisional HQ, 40 District HQ, 310 Tehsils/Blocks Horizontal Offices-Various departments/offices at NMC, CHQ, DHQ, BHQ. Creating a multi-service network for Voice, Video and Data High-availability and resiliency of network is essential Integrated network security for all layers including horizontal offices Scalable and High-performance network solution Efficient Network management Page 9 of 48

10 3. MPSWAN Network Diagram The overall schematic network diagram of MPSWAN is shown in the figure below: The above diagram shows the schematic connectivity of various Tiers in MPSWAN. The Internet connectivity for MPSWAN will be taken at NMC and terminated on the Gateway Router which can be any mid-level router capable of handling 4-8 Mbps data transfer rate and supports BGP configuration. Whole Internal MPSWAN traffic will converge at the core router/switch at State NMC. Leased lines of variable capacity to be used for connectivity between various Tiers as per the details below:- Connectivity from Divisional POP to NMC will be of 2Mbps Initially and will be up gradable to 16 Mbps Connectivity from District to Divisional POP will be of 2 Mbps initially and will be up gradable to 6 Mbps. Connectivity from Block to District POP will be of 2 Mbps initially and will be up gradable to 4 Mbps. PRI/BRI connectivity at all levels for RAS. Page 10 of 48

11 In addition to above router, a mid-level router will also be located at State NMC for terminating the Internet bandwidth and running BGP as the inter-domain routing protocol. In addition to this a Central Call Manager/ Call server catering to entire MPSWAN VoIP traffic will also be located here forming a Hub and Spoke topology. Also a central Video Conferencing MCU will also be located at State NMC catering to the entire MPSWAN Video Conferencing traffic forming a Hub and Spoke topology. An Intrusion Prevention System (IPS) will be located at State NMC taking care of securing the entire traffic to and fro from Internet to MPSWAN. The Central Servers to be located at State NMC are:- Their will be Five servers in NMC. For following applications one server each will be used: AAA Server Web Server DNS Server Proxy server Server NMS/ EMS Overview of different applications to be run: Proxy Servers Proxy Server shall provide high performance web caching, application layer inspection firewall solution allowing for controlled and monitored web access as well as advanced protection network protection firewall AAA Server The Remote Authentication Dial-in User Service (RADIUS) server should Page 11 of 48

12 support managing user authentication and authorization. It should support authentication, authorization, and accounting for network access. Web Server The Web Server should accept http/https requests. The Web Server should deliver delivers high reliability and performance. The web server should be configured for maximum security by default. Server: server will be used for providing services to users. It is planned that users will be able to access this using WWW as well as POP3. A mail server with capacity to handle mail traffic of 5000 users via POP3 / IMAP / HTTP access, of which concurrent user load may be of 500 users DNS server: Domain Name resolution Server (DNS) will be available for all internet users in the SWAN network. NMS Servers: Central NMS servers will be located at state NMC for NMS, monitoring al the SNMP Supporting devices deployed in MPSWAN including Servers Routers, Switches, Power Supplies, Call Manager, Leased line CSU/DSU s, Wireless Broadband Base Stations and CPE s etc. 4. Divisional POP Architecture As shown in the above diagram each divisional POP will have one E1 coming from state NMC, it will be up gradable to 16 Mbps. Also the horizontal connectivity to various departments and offices will be provided via copper/optical cables and broadband wireless radio on unlicensed band, depending on the feasibility w.r.t. distance and bandwidth requirements In addition to this VoIP phone and Desktop camera for Video conferencing will also be kept at Divisional level POP s Page 12 of 48

13 5. District POP Architecture As shown in the diagram below each district POP will have one E1 coming from Divisional HQ POP s. PRI/BRI connectivity for RAS. In addition to this multiple serial links would be going to different blocks. Also the horizontal connectivity to various departments and offices will be provided via copper/optical cables and broadband wireless radio on unlicensed band, depending on the feasibility w.r.t. distance and bandwidth requirements In addition to this VoIP phone and Desktop camera for Video conferencing will also be kept at District level POP s Page 13 of 48

14 6. Block POP Architecture: As shown in the above diagram each block level POP will have one E1 s link coming from respective district POP. PRI/BRI connectivity for RAS. Also the horizontal connectivity to various departments and offices will be provided via copper/optical cables and broadband wireless radio on unlicensed band, depending on the feasibility w.r.t. distance and bandwidth requirements In addition to this VoIP phone and Desktop camera for Video conferencing will also be kept at all block level POP s. 7. IP Network Design Considerations It is proposed to take IP connectivity from two different ISP s. One Class C IP block to be taken from APNIC for assigning to all Internet Servers in NMC. One AS number for running BGP will be taken from APNIC. Very Small membership will be required to be taken from APNIC for these. Private IP address ranges to be used for the rest of the inter-network. BGP to use as the EGP at the gateway router for peering with 2 ISP s for Internet route exchanges. Routing Protocol Considerations The following points should be taken into account while implementing routing protocol in the network. Page 14 of 48

15 Hierarchy Scalability Optimization Simplicity and Low Overhead Robustness and Stability, Rapid Convergence, Flexibility and Scalability. Standards based Keeping in view the above discussed features and parameters in a routing protocol it is recommended to choose hierarchically scalable hybrid open standard-based OSPF (Open Shortest Path First Standards Based) for Madhya Pradesh State Wide Area Network (MPSWAN). OSPF Design Considerations For better scalability of the network, TULIP will design and implement hierarchical IP Schema with scope for future growth. OSPF will be limited to Distribution layer. Core routers and Router VLAN formed on Core switches will form Area 0. All Divisional HQ with respective districts will form independent areas other than area zero. All links between State HQ, Division and Districts connected to that division will form independent non zero area. Access Layer (Tehsil/Block level) routers will have default static routes pointing towards Distribution router (District). Redistribution of static networks for Tehsil s will take place at Distribution Routers (District Routers). Route summarization will happen at Distribution layer. District routers will do route summarization for all connected Tehsil networks. All Routers at Division and District level will behave as Area Border Routers. Redundant links will be utilized to load balance the traffic towards the Core. Network Management Software Considerations The Network Management software being an integral part of the NMC must provide following capabilities:- To give accurate report of Hardware & Software deployed on the network. To give comprehensive report of Hardware & Software configuration of network equipments. To view the details of the response time, availability, reloads, protocols and interface status. To isolate the network error condition and suggest probable cause. To monitor traffic utilization w.r.t. hourly/daily/monthly/yearly graphs. To provide Downtime/ Uptime reports w.r.t various Network elements as per SLA. To provide one Interface to state monitoring agency for monitoring all SLA s and network status. IP Telephony/ Telephony Solution The centralized architecture based solution is proposed for MPSWAN. This model consists of call processing engine or Soft Switch or Call Manager at the central site, IP telephone users spread across the network. The IP telephones should be connected to the Soft Switch either using LAN if the user is located in the LAN or WAN if the users are located remotely. The WAN network to be built for Data traffic can be used to connect the IP phones located in the remote sites. The same IP WAN can also carry call control signaling between the central site and the remote sites. Centralized system will also support termination of PSTN lines, call processing of both Page 15 of 48

16 PSTN and VoIP calls will be done using call manger. The centralized Soft Switch will control the entire IP telephony network. It will perform the major tasks such as Call Processing, Controlling, Switching, etc. In this model the remote sites rely on the centralized Soft Switch to handle their call processing. Routers that reside at the WAN edges require quality of service (QoS) mechanisms, such as priority queuing and traffic shaping, to protect the voice traffic from the bursty data traffic across the WAN. The primary advantage of this model is Centralized call processing that reduces the equipment required at the remote sites and facilitates to have Unified Dial plan across the network. Solution Description: The above diagram depicts the IP telephony setup for MPSWAN. The Proposed architecture is centralized in nature. All the call processing engine & Soft Switch is located at the State Center, while IP telephone users are spread across the LAN and WAN. Call server/ call manager will be used as IP PBX and will do the Call processing and Call control Functionality. IP Phone is proposed for the Office communication. For VoIP service capacity planned is of minimum 5000 users and maximum of 25,000 users plus with min simultaneous sessions. For Unified messaging solution the capacity planned is maximum of 500 users with min. 20 simultaneous sessions. Remote Site IP Telephony Details The above diagram shows MPSWAN IP Telephony setup at remote offices. IP phones will be connected to the Ethernet switch. External power adapter/poe switches will be used to supply the power to the Phone each IP phones will be assigned unique IP address. And all these phones will be registered with IP PBX at the Central office. Remote offices will be connecting to the Central office through IPWAN. And each phone will be assigned Unique Directory Number (DN) for identifying the phone in the IP telephony network. Unified Messaging System overview Page 16 of 48

17 Unified messaging enables the people occupying critical positions to be contacted to their phones all the time, it make sure that all the critical calls are answered in time avoiding, time loss & delayed follow ups. Other benefits are to interface, text to speech conversions, and voice mail and fax retrievals. Voice Gateway overview The State Head quarter need to connect to the outside voice telephone network and the voice gateway router should supports the widest range of packet telephony-based voice interfaces and signaling protocols within the industry, providing connectivity to public switched telephone network (PSTN) and PBX. The voice gateway router enables users to immediately deploy an end-to-end IP telephony network architecture or gradually shift voice traffic from traditional circuit-switched networks to a single infrastructure carrying data, voice, and video over packet networks. Remote Access Services (RAS) The SWAN network will be used by some remote offices/ villages, where these locations may be used infrequently and wireless connection is not feasible, in such cases they will get connected using either normal telephone (analog) or ISDN services, depends on the availability of services in those locations. This option can also be used as redundancy measure for some offices for avoiding blackout of the service. At state NMC (T1) one dedicated RAS equipment with 30 async. And 30 PRI ports will be taken supported by a RADIUS/TACACS Server for AAA (Authentication, Authorization and Accounting) requirement. At Divisions (T2), district (T3) and blocks (T4) BRI and Async. Ports will be taken in the available router. For AAA requirement RADIUS/TACACS server in NMC will be used. Helpdesk Their will be helpdesk at state NMC for providing support services to entire SWAN network users. Helpdesk will have following components: Helpdesk management module of NMS. Ten desktop machines. Two 50 LCD Monitors. One Laser printer. Network Security Design Considerations Following security features have been considered in the network: URL filtering Gateway Antivirus Intrusion Prevention and Detection System Firewall Firewall Services module is to be implemented either internally or externally alongwith L3 Switch for managing MZ s and DMZ s at NMC Tulip has to follow the Security/Interoperability Guidelines given in Chapter 12 of the RFP for MPSWAN (RFP No. MPSEDC/MPSWAN/ /01. In addition Tulip has to comply with the security and other guidelines issued by DIT/NIC from time to time Passive component/ Cabling Setup Passive cabling at all locations will be as shown in the diagram shown below and should be as per accepted international standards: The SWAN network also involves the passive cabling at NMC, Div HQ, District HQ and Block level. All the passive components will be of the same make across the entire network to ensure standardization and ease of Certification from the Page 17 of 48

18 manufacturers. Network Operator will get certification of cabling from the manufacturer. UTP Cable UTP Cable UTP Cable Crimped on Patch Panel 3 Fts Patch Cord Jack Pane Switch UTP Cable Crimped on I/O I/O Box I/O Box 7 Fts Patch Cord 7 Fts Patch Cord Rack PC PC UTP Cabling Details Horizontal Office Connectivity The user deptt. Can use low-end router with/without modem at department with 24/128 Kbps link at departments and 2 Mbps channelized link will be procured at the SWAN POP. Please refer the diagram shown. Single 2 Mbps link will be able to take care of 30 nos. of 64 kbps links. In this case a single modem is required at the Block/DHQ/Div site which increases the ease of management. Dynamic routing can be enabled effectively as the Block/DHQ/Div routers are already configured for dynamic routing. This improves the performance of the total routing in the network. The security policies can be deployed effectively because when the user from the department tries to access any application or server at DHQ/DIV he has to pass through Perimeter security device (FW+IPS) and when he tries to access the application at State NMC the Core firewall and IPS will check its authenticity Page 18 of 48

19 8. PoP Details POPs CONFIGURATION: Tier-1 POP at Bhopal (NMC) Routers and Switches as per specifications. Ethernet terminations for Servers, VC, VoIP, NMC, LAN and wireless. UPS and DG as per specifications. As majority government departments have HQs at Bhopal, connectivity from user departments through Leased line/wireless etc should be present. Estimated users at Bhopal NMC, which like to take connectivity, could be 200 in next 05 years. Extending connectivity to these locations can be combination of wired, wireless and dial-ups as the case may be. Interconnectivity between SWAN POPs will be terminated directly on Routers and user department connectivity to SWAN will be through layer-3 switch i.e. Ethernet (user department connected through wireless point to multipoint system will give us Ethernet connectivity which can be directly connected to switch and connectivity through cu wire will be converted to router through channelised E1. Point-to-Multipoint wireless system HDSL Modems. Remote Access Server Firewall, IP Exchange, Master VC equipment. DNS, Mail server. Network Management Software (NMS). Fire Protection. Network security. VoIP Phone Type 1 Provision for connecting MPSWAN with NIC gateway, State Data center and SWAN of other state should be made at NMC. Call server for call centre with 10 PSTN connections RAS Page 19 of 48

20 Tier-2 POP at Divisional HQs Routers and Switches as per specifications. Ethernet connectivity for LAN and wireless UPS and DG as per specifications AC as per specifications Some of the government departments have HQ at these divisional HQ like Commercial Tax, Land records etc, connectivity from these departments through Leased line/wireless should be present. We may take 150 user departments in next 05 years. Extending connectivity to these locations can be combination of wired and wireless. Interconnectivity between SWAN POPs will be terminated directly on Routers and user department connectivity to SWAN will be through layer-3 switch i.e. Ethernet (user department connected through wireless point to multipoint system will give us Ethernet connectivity which can be directly connected to switch and connectivity through cu wire will be converted to router through channelised E1. Point-to-Multipoint wireless system HDSL Modems. Fire Protection. Network security. VoIP Phone Type 1 01 PSTN connection Tier-3 POP at District HQs Routers and Switches as per specifications. Ethernet connectivity for LAN and wireless. UPS and DG as per specifications AC as per specifications District offices of government would like to take connectivity and we may take 150 user departments in next 05 years. Extending connectivity to these locations can be combination of wired and wireless. Interconnectivity between SWAN POPs will be terminated directly on Routers and user department connectivity to SWAN will be through layer-3 switch i.e. Ethernet (user department connected through wireless point to multipoint system will give us Ethernet connectivity which can be directly connected to switch and connectivity through cu wire will be converted to router through channelized E1. Point-to-Multipoint wireless system HDSL Modems. G703/V.35 Converter Fire Protection. Network security. VoIP Phone Type 1 Tier-4 POP at Block/Tehsil Routers and Switches as per specifications Ethernet connectivity for LAN and wireless. UPS and DG as per specifications AC as per specifications Solar system. Majority of government offices in a given block would be connected to SWAN through wireless and numbered up to 150 in next 05 years. Interconnectivity between SWAN POPs will be terminated directly on Routers and user department connectivity to SWAN will be through layer-3 switch i.e. Ethernet (user department connected through wireless point to multipoint system will give us Ethernet connectivity which can be directly connected to switch and connectivity through cu wire will be converted to router through channelized E1. Point-to-Multipoint wireless system HDSL Modems. Page 20 of 48

21 Network security. VoIP Phone. Type 1 9. Project Timelines and Current Status The implementation of the Project is under process and the complete network is expected to be commissioned by June, Bill of Material The Bill of Material (BOM) as finalized with the operator is attached at Annexure NMS Details The details of the Network Monitoring System (NMS) to be deployed for the SWAN alongwith Product details, modules, sub-modules etc is attached at Annexure Bidding Details The bidding details shall be as per the following table: Description Details 1. RFP Issuing authority Madhya Pradesh State Electronics Development Corpn. Ltd., 147, Zone 1, M P Nagar, Bhopal Correspondence address Addl. Chief General Manager, Madhya Pradesh State Electronics Development Corpn. Ltd., 147, Zone 1, M P Nagar, Bhopal RFP Name Appointment of Third Party Auditors (TPAs) for Independent Audit and Performance Monitoring of SWAN 4. RFP reference Tender No. MPSEDC/MPSWAN/404 no. 5. Date of pre-bid 16 th April, 2010 at MPSEDC Office at 03:00 p.m. conference 6. Last date for submission of Bids 27 th April, 2010 by 03:00 p.m. The envelope should be addressed to : Addl. Chief General Manager M P State Electronics Dev. Corpn. Ltd. 147, Zone-1 M P Nagar Bhopal Late proposals shall be summarily rejected 7. Date for bid opening 27 th April, 2010 at 04:00 p.m. 8. Details to be submitted Sealed bids shall be submitted by the bidder under Two Envelope System. All the documents along with signed copy of the RFP document and EMD except Financial Bid shall be sealed in one Envelope called the Technical Bid. The Financial Bid shall be sealed in a separate envelope and submitted along with Technical Bid in a larger sealed Envelope. The bid shall comprise of the following: a. Checklist as provided in the Annexure 1. b. Cover letter in the format as given in Annexure 2 c. Proof (Board resolution/ Power of attorney) stating that the person signing the bid is an authorized representative of the bidder. d. EMD. e. Undertaking stating that the bidder is not the state SWAN operator/network equipment OEM or any Consortium member/any partner of network equipment OEM Page 21 of 48

22 f. Key resources proposed and resource deployment plan g. Sealed Financial bid in the format as given in this document 9. Envelope heading The financial proposal should be clearly marked and should contain a label stating Financial Proposal To be Opened in presence of the SWAN TPA Evaluation Committee. The overall bid envelope shall contain a label stating Bid for for MPSWAN alongwith the Tender No. and due date. The name and address of the bidder should be written on the envelope along with the address of the RFP issuing authority. 10. Language of proposal Proposals shall be submitted in English. The original proposal shall be prepared in indelible ink. It shall contain no inter-lineation or overwriting, except as necessary to correct errors made by the bidder itself. Any such corrections must be initialed by the person (or persons) who sign(s) the proposals. An authorized representative of the bidder shall initial all pages of the proposal. The representative s authorization should be confirmed by a written letter of authorization accompanying the bid. 11. EMD details The Bidders shall furnish, Earnest Money Deposit (EMD) of Rs Lakhs (Rupees Two Lakhs Only) in the form of demand draft/banker s cheque, from a Scheduled Bank, drawn in favour of MPSEDC Ltd., payable at Bhopal. The demand draft/banker s cheque should be valid for 6 months. The bidder would be disqualified in the pre-qualification process if the EMD is not submitted along with the Bid. Unsuccessful Bidder s EMD (bid security) will be returned as promptly as possible but not later than 60 days after the award of the contract to the successful bidder. No interest will be payable by MPSEDC on the amount of the Bid Security. 12. Key resource details The bid security may be forfeited: 1 If the Bidder modifies or withdraws his Bid or change his quoted price during the period of bid validity or its extended period without the explicit consent of MPSEDC, if any; or 2 In the case of a successful Bidder, if it fails within the specified time limit to: a Sign the Agreement or, b Furnish the required Performance Bank Guarantee a. The bidder must provide the detailed CVs of the key resource for project proposed. The Profiles of the Core team members should match with those furnished in the Technical Proposal for empanelment in the bid process conducted by DIT, GoI for empanelment of consultants. The CVs should be provided in the format as given in Annexure 5. b. Besides, the bidder must also provide the number of the other resources it proposes to deploy for the project and their profile. c. Bidder should also provide the resource deployment plan for the duration of the project. The resource deployment plan should give the number of man months of the core resources and other resources proposed. 13. Financial Bid No changes in the financial bid would be allowed post submission of the bid. The currency for the financial bid should be Indian Rupees. Bidders shall quote for the entire Project on a single responsibility basis on the following lines: Page 22 of 48

23 i. Bidders intending for commercial bid should necessarily give the commercial details in the format given in Annexure 3 only in accordance to the details and terms and conditions as mentioned in the RFP. ii. The bid should be comprehensive and inclusive for all the services to be provided by the bidder as per scope of his work. The payments would be made to selected bidder on the basis of the bid and further negotiations between MPSEDC and the bidder only. No separate payment shall be made for services that are to be delivered by the Bidder as part of his scope of work for this project other then the fixed payment for certain deliverables as detailed in the scope of work and the payment terms of the bidder. iii. The prices quoted shall be inclusive of all taxes, duties and statutory payments incident upon the bidder and it shall be a fixed price bid. Once the prices have been tendered, no change/modification will be entertained for any cause whatsoever (including changes in regulation, tax and duty structure etc.) The prices once provided by the bidder will be valid for the entire period of validity of the bid as defined in the bid document. Further negotiations between MPSEDC and bidder may lead to change in the quoted prices. iv. Any revision in the rates of taxes, duties, charges and levies at a later date and during the tenure of the bid will be to the account of the bidder. v. The Bidder shall be responsible for the costs towards travel/stay, daily allowance or any other allowances with respect to their staff deployed with respect to the execution of this project before or after the award of the contract. 13. Bid Evaluation process and Award of Contract The Evaluation Committee constituted by MPSEDC shall evaluate the bids submitted by the bidders for compliance. The evaluation of the bids shall be carried out as detailed below 14. Preliminary Evaluation The bid documentation furnished by the bidder shall be examined prima facie, to ensure that the bid has been properly sealed and signed and accompanied by relevant documents criteria (covering letter, EMD, authorization/power of Attorney in favour of bid signatory, other requisite details like resource deployment plan and CVs etc.) to substantiate the compliance with the criteria as explained in this RFP. Only the bids qualifying the Preliminary Evaluation would be considered for further evaluation. 15. Technical Evaluation The evaluation committee shall evaluate the bids further (subsequent to qualification in preliminary evaluation), based on the documents submitted including the proposed approach and methodology, proposed timelines and proposed resources. Each bidder would be essentially required to make a presentation for the same to the evaluation committee. Page 23 of 48

24 The scoring pattern for the required presentation would be as per the following table Sl.No. Parameter Score 1 Understanding the State-specific SWAN 50 and corresponding TPA requirements 2 State Specific Approach and Work Plan 50 3 State Specific Resource Plan and CVs 50 Total (Max) Score Financial evaluation The financial evaluation shall be done based on the details submitted by the bidder as per the format provided in Annexure 3. The calculation for financial evaluation shall be for the entire duration of 5 years of the project. 17. Award of Contract The methodology for award of contract is detailed in Annexure 4. The award of contract would be decided on the basis of i. Weighted Score (15%) for the normalized score as per the marks awarded by DIT, GoI during empanelment process. ii. Weighted Score (15%) for the normalized score as per the marks obtained by the bidder in the presentation at State level as per the table above. iii. Weighted Score (70%) for the normalized score as per the financial bids After evaluation of all accepted proposals by the evaluation committee, the contract may be awarded to the most responsive bidder (having the highest overall score T, as explained in Annexure 4) meeting all the requirements as per RFP. 18. Notification of Award The acceptance of a tender, subject to contract, will be communicated in writing at the address supplied by the bidder in the bid document. Any change of address of the Bidder, should therefore be promptly notified to the State. 19. Signing of Contract The Most Responsive Bidder shall be required to enter into a contract, including any agreements reached during the negotiation process, if any with MPSEDC, within 15days of the award of the contract or within such extended period, as may be specified by MPSEDC. This contract shall be on the basis of this document, the Bid of the Bidder, the letter of intent and such other terms and conditions as may be determined by MPSEDC to be necessary for the due performance of the work, as envisaged herein and in accordance with the Bid and the acceptance thereof. Note: a. MPSEDC reserves the right to accept or reject any Bid, and to annul the bidding process and reject all Bids at any time prior to award of Contract, without thereby incurring any liability to the affected Bidder or Bidders or any obligation to inform the affected Bidder or Bidders of the grounds for department s action. b. Failure to agree with the Terms & Conditions of the RFP/Contract: Failure of the successful Bidder to agree with the Terms & Conditions of the RFP/Contract shall constitute sufficient grounds for the annulment of the award, in which event MPSEDC may make the award to the next Best Value Bidder or call for new Bids. Page 24 of 48

25 V General Terms and Conditions The terms and conditions given in the RFP and subsequent corrigendum released by Department of Information Technology, Government of India for empanelment of consultants for Third Party Audit of MPSWAN shall apply. The main clauses are as follows: 1. One Proposal per Bidder Each bidder shall submit only one Proposal. The bidder who submits or participates in more than one Proposal will be disqualified. 2. Cost of Proposal The bidder shall bear all costs associated with the preparation and submission of its Proposal, including site visits, and MPSEDC will in no case be responsible or liable for those costs, regardless of the conduct or outcome of the proposal process. 3. Amendment of RFP Documents At any time prior to the deadline for submission of Proposal, MPSEDC may amend the RFP document by issuing suitable Addenda. Any addenda/corrigenda thus issued shall be part of the RFP document, and shall be uploaded only on MPSEDC website No claim will be entertained or accepted regarding non-receipt of addendum/corrigendum. To give bidders reasonable time in which to take an Addendum into account in preparing their Proposals, MPSEDC shall extend if necessary, the deadline for submission of Proposals. 4. Limits on Promotion The bidder will not make any reference to MPSEDC or this procurement or resulting contract in any literature, promotional material, brochures, sales presentation or the like without the express prior written consent of the authorized representative of MPSEDC. The bidder shall not perform any kind of promotion, publicity or advertising etc. at MPSEDC field offices through any kinds of hoardings, banners or the like without the express prior written consent of the same. 5. Use & Release of Bidder Submissions MPSEDC is not liable for any cost incurred by the bidder in the preparation and production of the Proposal, the preparation or execution of any benchmark demonstrations, simulation or training service or for any work performed prior to the execution of a formal contract. All materials submitted become the property of MPSEDC and may be returned at its sole discretion. The content of each bidder s Proposal will be held in strict confidence during the evaluation process, and details of the Proposals will not be discussed outside the evaluation process. 6. Deadline for submission of proposals Proposals must be received by MPSEDC at the address specified in the RFP no later than the time and date stipulated in the RFP. MPSEDC may, in exceptional circumstances and at its discretion, extend the deadline for submission of Proposals by issuing an Addendum/Corrigendum on the website. MPSEDC may also intimate all bidders who have been provided the Proposal Documents, by . In this case, all rights and obligations of MPSEDC and the bidders previously subject to the original deadline will thereafter be subject to the deadline as extended. Page 25 of 48