RFP FOR SYSTEM INTEGRATOR IMPLEMENTATION OF HOLISTIC … FOR SI - VOULME 1.pdf · rfp for system...

RFP for Selection of System Integrator for GHMC – Vol - I

GHMC Page 1

RFP FOR SYSTEM INTEGRATOR IMPLEMENTATION OF HOLISTIC AND INTEGRATED GREATER HYDERABAD EGOVERNANCE SOLUTION (HIGH eGOV) GREATER HYDERABAD MUNICIPAL CORPORATION HYDERABAD, ANDHRA PRADESH VOLUME – I FUNCTIONAL AND TECHNICAL SPECIFICATIONS


GHMC Page 2

TABLE OF CONTENTS

1. DISCLAIMER ........................................................................................................................................................ 5

2. REQUEST FOR PROPOSAL DATA SHEET ................................................................................................... 6

3. DEFINITIONS ....................................................................................................................................................... 7

4. INTRODUCTION ................................................................................................................................................. 8

4.1 Project Background ......................................................................................................................................... 8

4.2 Goals of this RFP ............................................................................................................................................. 8

5. PROJECT OVERVIEW ....................................................................................................................................... 9

5.1 Need for the project ......................................................................................................................................... 9

5.2 Vision, Goals and Objective of the Project ..................................................................................................... 9

5.2.1 Vision ................................................................................................................................................................ 9

5.2.2 Goals of the Project ......................................................................................................................................... 9

5.2.3 Objectives of the Project ................................................................................................................................ 10

5.2.4 Stakeholders of Project .................................................................................................................................. 11

5.3 Roles &responsibilities of the stakeholders in the project implementation ................................................ 12

5.3.1 State level Nodal Agency (APUFIDC) .......................................................................................................... 12

5.3.2 Project Management Consultant .................................................................................................................. 12

5.3.3 System Integrator ........................................................................................................................................... 13

5.3.4 GHMC ............................................................................................................................................................. 13

5.3.5 Techno Financial Committee ........................................................................................................................ 14

5.3.6 Andhra Pradesh Technological Services ..................................................................................................... 14

6. GREATER HYDERABAD MUNICIPAL CORPORATION ............................................................................. 15

6.1 Background .................................................................................................................................................... 15

6.2 GHMC Vision, Goals & Objectives ............................................................................................................... 15

6.3 Organization Structure ................................................................................................................................... 15

6.4 Overview of Services for GHMC ................................................................................................................... 16

6.5 Existing e-Governance Initiatives in GHMC ................................................................................................. 18

7. SCOPE OF THE PROJECT ............................................................................................................................. 20

7.1 Configuration, Development and Integration of Integrated IT solution of GHMC ..................................... 22

7.1.1 System Study, Design, Application Development, and Integration ............................................................ 22

7.1.2 Application Development and Unit Testing .................................................................................................. 23

7.2 Infrastructure at the Client Side Locations.................................................................................................... 27

7.3 Network Connectivity ..................................................................................................................................... 28

7.4 IT Infrastructure at the Data Center and Disaster Recovery Center .......................................................... 28

7.5 Data Migration ................................................................................................................................................ 31

7.5.1 Data Migration ................................................................................................................................................ 31

7.5.2 Data Migration Requirements ....................................................................................................................... 31

7.5.3 Scope of Data migration ................................................................................................................................ 31

7.5.4 Methodology of Data Migration: .................................................................................................................... 32


GHMC Page 3

7.5.5 Additional Guidelines for Data Migration ...................................................................................................... 32

7.5.6 Data Quality .................................................................................................................................................... 33

7.6 Capacity Building and Training ..................................................................................................................... 33

7.6.1 Identification of Trainers (Internal) ................................................................................................................. 33

7.6.2 Identification of Trainees: ............................................................................................................................... 33

7.6.3 Develop Overall Training Plan ...................................................................................................................... 34

7.6.4 Develop Training Schedule and Curriculum ................................................................................................ 34

7.6.5 Develop Training Material ............................................................................................................................. 34

7.6.6 Deliver Training to End Users ....................................................................................................................... 35

7.6.7 Number of Trainees in each group on IT Enablement ................................................................................ 35

7.6.8 Training Effectiveness Evaluation ................................................................................................................. 35

7.6.9 Change management.................................................................................................................................... 35

7.6.10 Communication and Awareness .............................................................................................................. 36

7.6.11 Change Management Workshops ........................................................................................................... 36

7.7 Supply of Consumables ................................................................................................................................ 37

7.8 Manpower Services - Out sourced employees ........................................................................................... 37

7.9 Integration with Legacy Systems, State Level Solutions, SMS gateway, Payment gateway& other Databases .................................................................................................................................................................... 38

7.10 Mail & Messaging Services ........................................................................................................................... 38

7.11 SMS Services ................................................................................................................................................. 39

7.12 MIS Services .................................................................................................................................................. 39

7.13 Dash Board Services ..................................................................................................................................... 39

7.14 Proxy Services ............................................................................................................................................... 39

7.15 Antivirus & Anti-spam Services ..................................................................................................................... 39

7.16 Handholding Support ..................................................................................................................................... 40

7.17 Project Planning and Management .............................................................................................................. 40

7.18 Requirements Traceability Matrix ................................................................................................................. 41

7.19 Project Documentation .................................................................................................................................. 42

7.20 Post Implementation Support........................................................................................................................ 42

7.20.1 Resource Requirement ............................................................................................................................. 43

7.20.2 Warranty services ...................................................................................................................................... 43

7.20.3 ATS services .............................................................................................................................................. 44

7.20.4 Handholding services to provide Operations and maintenance support .............................................. 45

7.20.5 Handholding services to provide Centralized Helpdesk and Support ................................................... 45

7.20.6 Handholding services to provide software maintenance and support services .................................... 46

7.20.7 Handholding services to provide application functional support ............................................................ 47

7.20.8 Exit Management and Transition – Capacity Building at GHMC ........................................................... 47

8. TECHNOLOGY REQUIREMENT FOR APPLICATION DEVELOPMENT ................................................. 48

9. IMPLEMENTATION AND ROLL-OUT PLAN ................................................................................................. 56

9.1 List of Indicative Deliverables ........................................................................................................................ 56


GHMC Page 4

9.2 Implementation Plan ...................................................................................................................................... 56

9.3 Geographical Coverage ................................................................................................................................ 57

9.4 Service Coverage .......................................................................................................................................... 57

9.5 Outcomes ....................................................................................................................................................... 57

10. SERVICE LEVELS ........................................................................................................................................ 58

10.1 Definitions ....................................................................................................................................................... 58

10.2 Interpretations ................................................................................................................................................. 58

10.3 Implementation Phase SLAs ........................................................................................................................ 60

10.3.1 Delivery Related Service Level Agreement Criteria ............................................................................... 60

10.3.2 Violations and Associated Penalties ........................................................................................................ 61

10.4 Post Implementation Phase SLAs ................................................................................................................ 61

10.4.1 Primary DC/DR Infrastructure Systems, Application Availability & Performance ................................. 61

10.4.2 Client Site Infrastructure Systems (Critical Client Site Systems) ........................................................... 63

10.4.3 Handholding Support ................................................................................................................................ 64

11. TECHNICAL SPECIFICATIONS (INDICATIVE) ........................................................................................ 71

12. BILL OF QUANTITY ...................................................................................................................................... 97

13. FUNCTIONAL REQUIREMENT SPECIFICATIONS ................................................................................ 99

14. GOVERNANCE STRUCTURE .................................................................................................................. 156

ANNEXURE 1 - SOLUTION OVERVIEW FOR THE PROPOSED APPLICATION (INDICATIVE) ................. 158

ANNEXURE 2: TESTING AND QA REQUIREMENTS ........................................................................................ 177

ANNEXURE 3 – EXISTING IT INFRASTRUTURE AT GHMC ............................................................................ 184

ANNEXURE 4 – EXISTING IT MANPOWER AT GHMC HEAD QUARTERS ................................................... 193

ANNEXURE 5 – DETAILS OF OFFICE LOCATIONS ......................................................................................... 194


GHMC Page 5

1. DISCLAIMER All information contained in this Request for Proposal (RFP) is provided in good interest and faith. This is not an agreement and is not an offer or invitation to enter into an agreement of any kind with any party. Though adequate care has been taken in the preparation of this RFP document, the interested firms shall satisfy themselves that the document is complete in all respects. The information is not intended to be exhaustive. Interested parties are required to make their own enquiries wherever required. Intimation of discrepancy, if any, should be given to the specified office immediately. If no intimation is received by this office by the date mentioned in the document, it shall be deemed that the RFP document is complete in all respects and the participating firm is satisfied that the RFP Document is complete in all respects. The Managing Director, Andhra Pradesh technology Services, hereafter mentioned as MD APTS, / Commissioner, GHMC reserve the right to reject any or all of the applications submitted in response to this RFP document at any stage without assigning any reasons whatsoever. The APTS / GHMC also reserve the right to withhold or withdraw the process at any stage with intimation to all who submitted the RFP Application. APTS reserves the right to change/ modify/amend any or all of the provisions of this RFP document. Such changes would be posted on the websites www.ghmc.gov.in and www.apts.gov.in Neither the APTS / GHMC nor their employees and associates will have any liability to any prospective applicant interested to apply or any other person under the law of contract, the principles of restitution or unjust enrichment or otherwise for any loss, expense or damage which may arise from or be incurred or suffered in connection with anything contained in this RFP document, any matter deemed to form part of this RFP document, the award of the assignment, the information and any other information supplied by or on behalf of APTS / GHMC or their employees and Prime Bidder / Consortiums or otherwise arising in any way from the selection process for the Assignment. Information provided in this document or imparted to any respondent as part of the RFP process is confidential to APTS / GHMC and shall not be used by the respondent for any other purpose, distributed to, or shared with any other person or organization.


GHMC Page 6

2. REQUEST FOR PROPOSAL DATA SHEET

S. No Information Details 1 Publishing of RFP through e-tender 23.07.2012 2 RFP reference Number and Date APTS/CS/NMMP/APUFIDC/2012 3 Date, Place and time of pre-bid

meeting 31.07.2012 – 11.30 AM

4 Last date for submission of written queries for clarifications

02.08.2012 – 11.30 AM

5 Release of response to clarifications for the queries received on APTS and GHMC Websites

08.08.2012 – 5.00 PM

6 Last date (deadline) for receipt of proposals in response to RFP notice

18.08.2012 – 3.00 PM

7 Time and Date of submission of original copies of EMD(Physical Copies) and tender document fee to the O/o MD APTS

19.08.2012 – 12.00 Noon

8 Prequalification Bid opening date on e-procurement platform

21.08.2012 – 12.30 PM

9 Time and Date of opening of Technical Bids on e-Procurement platform

30.08.2012 – 3.00 PM

10 Time and Date Technical Presentation date

To be communicated to PQ qualified bidders through email.

11 Opening of financial Bid on e-Procurement platform

To be communicated to TQ qualified bidders through email.

12 Non Refundable Tender Cost Rs. 25,000/- (Rupees Twenty Five Thousand Only) 13 EMD Rs. 50,00,000 /- (Rupees Fifty Lakhs Only) through

valid DD/BG. 14 APTS Contact Person for queries General Manager T2, ,Andhra Pradesh

Technological Services, BRKR Bhavan, B Block, 4th Floor, Tank bund Road, Hyderabad, Andhra Pradesh, Phone: 040 23226970.Email: [email protected], [email protected]

15 Addressee and Address at which EMD / Tender document fee in response to RFP notice is to be submitted

Managing Director, ,Andhra Pradesh Technological Services, BRKR Bhavan, B Block, 4th Floor, Tank bund Road, Hyderabad, Andhra Pradesh, Phone: 040 23226970 Email: [email protected], [email protected]

16 Implementation cum Performance Guarantee Value & Validity Period

10 % of the total value of the bid. 90 days beyond contract period

17 Bid Validity Period 180 working days from the date of opening of the pre-qualification bids

18 Period for submission of implementation cum performance guarantee

Within 15 days of receipt of letter of notification of award

19 Location for Pre bid conference, opening of technical bids, presentations, financial bids

O/o Managing Director, Andhra Pradesh Technological Services , BRKR Bhavan, B Block, 4th Floor, Tank bund Road, Hyderabad, Andhra Pradesh, Phone: 040 23226970


GHMC Page 7

3. DEFINITIONS Unless the context otherwise requires, the following terms whenever used in this RFP and contract have the following meanings: a. “Proposals” means proposal submitted by bidders in response to the RFP

b. “Committee” means the Techno-Financial Committee constituted by the Government of Andhra Pradesh for evaluation of Technical and Commercial Proposals submitted by the bidders.

c. “Contract Price” means the price payable to the bidders under the Contract for the complete and proper performance of its contractual obligations.

d. “Contract” means the Contract signed by the parties (GHMC and Bidder) along with the entire documentation specified in the RFP.

e. “Day” means Calendar day

f. “Effective date” means the date on which an activity comes into force and effect.

g. “RFP” means Request for Proposals

h. “Personnel” means professional and support staff provided by the bidders assigned to perform services to execute an assignment and any part thereof.

i. “ToR” means Terms of Reference for the bidders

j. “Services” means the work to be performed by the bidders pursuant to the contract to be signed by the parties in pursuance of any specific assignment awarded

k. “Third Party” means any person or entity other than the GHMC and the bidders.

l. “Maintenance” shall mean and include implemented Application production support and small software modifications, bug fixing, enhancements, online and onsite help, support services and adaptation to changed environments

m. “Project” shall mean the Supply, Installation, services, Technical Requirements Specifications, Functional Requirements Specifications, testing, integration and commissioning of the Solution in accordance with the procedures, specifications and timelines set out in the Contract and Tender Document.

n. “Project Schedule” shall mean the schedule submitted by the Bidder together with the Statement of Work

o. “Vendor” shall mean the Prime Applicant (PA) (if bidding individually) and the Prime Applicant and the Consortium Partner (CP) in case of a consortium.

Single Point of Contact (SPOC): The Primary Bidder ( ) submitting the bid and undertaking the entire responsibility of successful completion of the entire project along with the AMC would be referred as the Single Point of Contact (SPOC).

p. System Integrator: An organization with experience which combines procedures from system engineering, system Management, product development for the purpose of developing and or implementation of large scale complex IT systems or products and may be based on existing or legacy system coupled with totally new requirements to add significant functionality


GHMC Page 8

4. INTRODUCTION 4.1 Project Background The National Mission Mode Project (NMMP) for e-Governance in Municipalities is one of the Mission Mode Projects that has significant citizen interaction as municipalities provide a large number of basic services for millions of citizens living in India's urban centers. Hence, there is a need for transformation to provide more “Efficient, Convenient & Transparent” services to the Citizens and Businesses. In light of this, there has been an increasing recognition of the role of ‘e-Governance’ in Government with implementation of Information & Communication Technologies (ICT). National e-Governance Plan (NeGP) by the Government of India (GoI) provides vision and impetus for successful implementation of ‘e-Governance’ and long-term growth of ‘e-Government’. It is envisaged that MMP for e-Governance in municipalities would provide a major fillip to the Government of India's Ministry of Urban Development's urban reform agenda. The vision for the National Mission Mode Project for e-Governance in Municipalities is to leverage the ICT opportunities for sustained improvement in efficiency and effectiveness of delivery of municipal service to citizens. In order to automate the departmental procedures & functionalities, and to leverage the advancements in Information Technology for effective administration, Greater Hyderabad Municipal Corporation (GHMC) has taken up several IT initiatives to computerize its business processes for improving the efficiency in administration and service delivery. GHMC intends to introduce automation and implementation of integrated framework for e-Governance by leveraging ICT with an aim to streamline, improve, and strengthen functioning of corporation and its service delivery to citizens. The Central Monitoring and Steering Committee (CSMC) under Urban Infrastructure & Governance (UIG), JNNURM has sanctioned budget for implementation of e-Governance in Greater Hyderabad Municipal Corporation on 1st July 2011. This project is intended to strengthen the Governance and broaden the public participation by leveraging the ICT for sustained improvement in service delivery. In this context, GHMC through Andhra Pradesh Technology Services (APTS) intends to select a System Integrator for Design Development and Maintenance of Software, Hardware and Network (LAN & WAN) and other components as mentioned in this document, in Greater Hyderabad Municipal Corporation, through this Request for Proposal (RFP) The SI shall be responsible for implementation of the Holistic and Integrated Greater Hyderabad e-Governance Solution (HIGH eGov) in GHMC for 5 years in consonance with the laid down strategies, policies and procedures of the GHMC. 4.2 Goals of this RFP The primary goal of this RFP is to solicit proposals from the interested bidders for selection as System Integrator (SI) for GHMC through a competitive bidding process. This volume of RFP intends to bring out all the details with respect to the solution and other requirements that are deemed necessary to share with the potential bidders. The goals of RFP are further elaborated below:

• To seek proposals from potential bidders for providing the “bundle of services” implementation of the Holistic and Integrated Greater Hyderabad e-Governance Solution (HIGH eGov) for GHMC


GHMC Page 9

• To understand from the bidders how they propose to meet the technical and operational requirements of GHMC.

• To ascertain how potential bidders propose to deliver the services and sustain the demand and growth in the requirements.

• To ascertain from bidders on how they will ensure scalability and upgradeability of the infrastructure and solution proposed to be deployed.

• To understand from the bidders as to how they intend to innovate further on this service delivery model.

APTS shall be the final authority with respect to qualifying a bidder through this RFP. Their decision with regard to the choice of the SI who qualifies through this RFP shall be final and APTS reserves the right to reject any or all the bids without assigning any reason. 5. PROJECT OVERVIEW 5.1 Need for the project There has been an increasing recognition of the role of ‘e-Governance’ in Government with implementation of Information & Communication Technologies (ICT). The National Mission Mode Project (NMMP) for e-Governance in municipalities as an effort to modernize the municipal services giving top priority to citizen services, information gathering, and its dissemination. A need has been felt to

• adopt a holistic approach to address the requirements of the citizens mainly with relation to functions in the corporation;

• to strengthen the citizen interfaces with the corporation; • to enhance the efficiency and effectiveness of the corporation • to provide better interface with various stakeholders involved with GHMC; • to provide integration with other departments and service providers; • Provide for information sharing and transparency; • Provide web-based services to the citizen etc.

In order to realize the benefits of e-Governance fully, it is essential that a holistic approach is adopted that includes re-engineering and standardizing key functions of the administration of the corporation and creating a sustainable and secure mechanism for sharing information. 5.2 Vision, Goals and Objective of the Project 5.2.1 Vision “To strengthen civic governance and broaden the public participation by leveraging ICT opportunities for sustained improvement” 5.2.2 Goals of the Project In line with its vision, the project has defined a number of Goals that include:

1. Corporation Facing:


GHMC Page 10

a. Bringing about improvements in efficiency and effectiveness of business processes/functions of the Corporation

b. Instituting a mechanism of result based monitoring and evaluation c. Ensuring economy (cost efficiency) in the design and implementation of the

project d. Improving the system for decision making with respect to planning and

delivery of municipal services to the citizen and within. e. Ensuring effective project management to track progress.

2. Citizen Facing:

a. Significantly improving the Quality of Service provided by the Corporation b. Transparent, effective and efficient service delivery to the Citizen c. More service delivery channels for hassle free service for Citizen d. Defined service level for timely delivery of services to the Citizen

5.2.3 Objectives of the Project To measure the objective of the project outcomes in terms of Specific, Measurable, Achievable, Realistic and Time bound (S.M.A.R.T), specific measure have been envisaged for the project. Table below summarizes the proposed measurable outcomes against the key objectives of the project: Objectives Key Measures Illustrative Targets Citizens (Quality of Service)

• Minimizing the number of customer visits

• Reducing the time required to request the service

• Reducing the time required to deliver a service

• Reducing the costs associated with a service

• Reducing the time spent by the customer to follow-up and track the progress of the requested service

• Annual independent citizen survey/ feedback for a period of five years from the time of go-live with maximum satisfaction level with respect to meeting specified service levels

• Providing the citizen services defined service level

Corporation (Process efficiency and effectiveness)

• Setting up new revenue streams • Reducing cost of processing • Transactions • Delivering intangible benefits • Enhancing existing revenues

• Hike in Corporation revenue year on year basis

• Paperless office in coming two years

• Integrated activities among departments

Policy makers (Decision making support system)

• Sharing the performance information with State and Central Governments.

• Periodical review about the policies

• Integrated Corporation Administration system

Service providers/ suppliers (M & E of Quality of Service

• Service Level Agreements (Internal & External)

• Deployment of a system for meeting the requirements for improved quality of services.

Programme Office (Progress tracking)

• %age of customers of each type using e-Governance services

• % of Corporation services transformed into e-Governance

• % of transactions of each service executed electronically

• increased % wise use of services by accessing various channels year on year from go-live

Additional Objectives are reckoned below:


GHMC Page 11

1. Provide better information and service delivery with speedy access. 2. Increase government transparency with systemized monitoring. 3. Reinforce political credibility and accountability 4. Ensure satisfied citizen interaction and corporation participation 5. Customers online, not in line. 6. Increase government staff productivity 7. Reduce overhead from fewer offices and less paper management 8. Facilitate the corporation to network with all zones and circles 9. Simplification and streamlining of the procedures of each department through

comprehensive process reengineering. 10. Bring the services of the Government closer to the door steps of citizens through

“One Click Interaction” 5.2.4 Stakeholders of Project It is an accepted paradigm that e-Governance interventions should bear its inception from the needs of the stakeholders. The major stakeholder in the department is the common citizen. As a result, all efforts of streamlining the processes of the department to improve the service standards through IT enablement should take due cognizance of the expectations of the stakeholders. The other dimension of e-Governance is the G2G element where the department aims to benefit from e-Governance by increasing its own efficiency and competency to elevate its service delivery standards. The objective behind introducing e-Governance is to effectively deliver services to the citizens in minimum time leveraging the use of ICT and concomitantly increase its own internal efficiencies. The purpose of stakeholder involvement analysis is therefore to assess the overall project environment and to help identify key persons, groups or institutions with an interest in the project or programme and assess how their interests may affect its success. The key stakeholders are identified and assessed the importance of key people, groups of people and institutions which are significantly influencing the public services, internal & external activities of GHMC. Therefore, the major stakeholders of GHMC are categorized as follows:

1. Citizens, General Public & Other primary beneficiaries, 2. Government & Ministries (Local / State / National), 3. Business Organizations (Vendors & Customers), 4. Employees (Corporation / Departments)

Primary Stakeholders Secondary Stakeholders External Stakeholders

1. State Government & Ministries

2. Elected representatives of the corporation

3. Citizens 4. Service Beneficiaries 5. Neighborhood Groups 6. Ward Committees 7. Ward Sabhas

1. Municipal Staff 2. Organized Labor 3. ICT Vendors & Businesses 4. Application Providers 5. Businessmen & Traders 6. Contractors & Vendors 7. Allied Departments 8. Society/Residential

Societies 9. Registered Planners

1. Service Pensioners of Corporation

2. Hospitals & Schools 3. Registered Planners 4. Media Groups 5. Experts & Analysts 6. Real Estate

Developers

Stakeholders Expectations The pain areas & expectations of the stake holders are captured in the below table:


GHMC Page 12

S. No. Stakeholder Pain Areas Expectations

1 Government • Unable to extract accurate information on time

• Tracking of arrears for collection • Minimal interdepartmental

interaction

• Real time accurate data access • Should be able track the demand

collection balances • Integration between departments • Information for taking strategic

decisions 2 Employees • Tracking of files

• Humongous volume of data • Large citizen interactions • Minimal storage for old records

• Efficient tracking mechanism • No duplication of process • Effective governance mechanism

3 Citizens • Delay in services • Lack of transparency • Less accountability

• Single point of contact • Speedy process • Greater accessibility

4 Contractors • Delay in payment • Less transparency • Large follow up for payment

release

• Faster release of payment • Minimal follow up of payment

5 Corporation • Large process with duplication • Monitoring the financial and

physical progress of the services

• Reengineer the process effectively

6 Elected Representatives

• Too many levels of file movement

• Tracking of fund utilization difficult

• Better governance mechanism

7 Supplier/Vendor

• Delay in payment • Less transparency • Large follow up for payment

release

• Faster release of payment • Minimal follow up of payment • Mechanism for informing the

requirement in advance 8 Traders • Delay in process

• Lack of transparency • Single point of contact • Speedy process • More assessable

9 Registered planners

• Delay in process • Lack of transparency

• Single point of contact • Speedy process • More assessable

10 Financial Institution

• Unable to extract accurate information on time

• Real time accurate data access

5.3 Roles &responsibilities of the stakeholders in the project implementation 5.3.1 State level Nodal Agency (APUFIDC) The State Level Nodal Agency (SLNA) at the state level that would serve as a channel for transfer of funds from GOI, State to GHMC for implementing the e-Governance project. Important roles of the SLNA are

• Timely transfer of funds received from GOI/GOAP to GHMC • Strict control on utilization of funds for intended purpose

5.3.2 Project Management Consultant Project Management Consultant is engaged to support the implementation of e-Governance in GHMC in the following areas:


GHMC Page 13

• Overall project planning and management in collaboration with GHMC includes planning, supervising the overall progress of the project, monitor conformance with the timelines, budgets and service levels.

• Review the scope and technical solutions covering all components provided by the SI • Acceptance testing and acceptance • Perform structured transition and rollout • Post-deployment reviews • Confirm and monitor service levels through the engagement with the SI through periodic

reviews • Monitor the implementation of the project according to the project plan and report to the

GHMC • Assess the progress of the implementation and recommend to GHMC on release of

funds to the SI 5.3.3 System Integrator GHMC adopts a “bundling of services” approach to implementation. Accordingly, all the implementation components at the state level are “bundled” and contracted out to a single Systems Integrator (SI) who would act as a single point of contact and accountability for the implementation, integration and performance of e-Governance project in GHMC. The bundle of services would include the following:

1. Program Planning and Management 2. The SI would customize and implement application 3. The SI would develop and deploy additional functionality that is scoped under the

project 4. Procurement, installation and commissioning of hardware (including PCs,

peripherals, etc.) at all the locations including site preparation 5. Procurement, deployment and commissioning of communications infrastructure

(Network, Wiring, Switches etc.) at all locations. APSWAN and AP State Data Center would be leveraged to the extent possible.

6. Capacity building a. Awareness and Sensitization of benefits of IT along with the

application level training b. Trainers Training c. System Administration and Support Training d. Handholding support to the all the offices of GHMC for 6 months

7. Change management 8. Procurement, configuration and commissioning of specialized infrastructure and

applications as necessary 9. Utilization Statements/ Progress Reports 10. Data Migration 11. Application, System and Network Maintenance 12. Helpdesk Support 13. Operations and Maintenance for 5 years

The SI would be held responsible for the outcomes of the program and their payments would be linked to the progress of the project as well as the outcomes of the program. The payment schedule will be based on achieving milestones of the Project as well as on accomplishing those milestones with predefined SLAs and Standard. 5.3.4 GHMC The Greater Hyderabad Municipal Cooperation is responsible for the following activities


GHMC Page 14

i. Reviewing the Request for proposal ii. Issue of the LOI to the successful bidder iii. Contract signing with selected bidder iv. Policy Directions and Guidance for successful execution of the Project, v. Creating a supporting environment for the success of the project vi. Timely Release of Payments to SI as per contract vii. Approval of BPR viii. Approval of various Project Components and Functionalities to be covered in the

Project ix. Review progress of the Project x. Ensure proper Training arrangements xi. Ensure deployment of appropriate handholding personnel xii. Other important policy and procedural issues

5.3.5 Techno Financial Committee

The techno financial committee of the Andhra Pradesh government is responsible for validating the RFP and accord the approval for the tendering process 5.3.6 Andhra Pradesh Technological Services Andhra Pradesh technological services (APTS) is responsible for the following activities

i. Convening meeting of TFC as and when required ii. Floating the Tender iii. Organizing the Pre-Bid Conference iv. Accepting the tenders v. Bid Evaluation vi. Identification of System Integrator through competitive bidding process and informing

the Commissioner, GHMC for further process


GHMC Page 15

6. GREATER HYDERABAD MUNICIPAL CORPORATION 6.1 Background The 625 Sq. KM area of Greater Hyderabad Municipal Corporation is divided into 5 Zones and 18 circles and 150 wards in and around areas of Hyderabad and extended areas of Hyderabad. Like all large E-Governance programs, GHMC project has been evolving and stabilizing towards better delivery of citizen services, which is the main aim of GHMC. GHMC has provided to the citizens a convenience in payment of their respective property tax, request for birth or death certificates, renewal of Trade Licenses, etc. through various additional windows e-Seva Centre’s, MeeSeva Centre’s, Citizen Service Centre’s, AP online, RajIV internet, etc. GHMC although a non-profit entity, earns its revenues by means of property tax, trade licenses, advertisements, administrative charges and fees for various services. The revenue earned along with the allocated funds from the government is used for providing citizen services like sanitation, roads, water drains, street lightening, water supply, health services, and city planning etc. 6.2 GHMC Vision, Goals & Objectives The Vision of GHMC’s e-Government initiative is user-centric, providing better government services to the end user. The goal is to build a common vision of success amongst all stakeholders and ensure the institutional and implementation arrangements support strategy. The aim of e-Governance in GHMC is to:

• Improve the quality, accessibility and effectiveness of government services for citizens and businesses

• Speed up processes and improve internal efficiency to provide more efficient delivery of public services

• Make processes more accountable and transparent • Encourage citizen participation in decision-making through effective use of ICT • Reduce costs and increase revenue

6.3 Organization Structure Organizational Structure of GHMC: The GHMC consist of deliberative/legislative wing and the executive wing. While the deliberative wing of the GHMC consists of elected members, the executive wing is headed by the Commissioner. The role of deliberative wing is mainly confined to governance of the GHMC and lying down of policies, guidelines, according approvals etc. for the various developmental Programmes. It is the executive wing, which is mainly responsible for the administration, regulatory and developmental activities being carried out by the civic body. The following is typical organizational structure of the executive body in GHMC.


GHMC Page 16

6.4 Overview of Services for GHMC The table below gives a detailed list of departments of the GHMC along with the services provided by each department and service category. Department Sl.No Services Health and Sanitation

1. Registration of Births and Deaths 2. Issuance of the Digitally Signed Certificates of Birth and Death 3. Issuance of the Ink Signed Certificates of Birth and Death 4. Procedure for issuing Non-availability certificates for the persons

whose names are not in the existing Database 5. Procedure for inclusion of Child Name in the Birth Register 6. Procedure for correction of entries in Births and Deaths records 7. Registration of Still Births 8. Procedure for issuing new trade license 9. Procedure for Renewal of Trade License 10. List of Dispensaries and the staff availability 11. Solid Waste Management System

Parks 12. Developing New Parks (Vacant Lands and Earmarked Areas) 13. Maintenance of Existing Parks and Green Areas

Estates 14. Allotment of properties for lease, mortgage or sale; and 15. Collect rents from the properties let out or leased

Veterinary 16. Issue of pet licenses and breeding dog licenses; 17. Issue of licenses to trades of non-vegetarian origin; 18. Details of Hot Spots, Animal Pounds, ABC and AR Vaccination

Sports 19. Organizing summer coaching camps, Organizing advance coaching camps and organizing tournaments to identify talents

20. Maintenance of sports and games facilities 21. Hiring and leasing of sports facilities 22. Procurement of equipment, infrastructure, manpower etc.,

Administration 23. Promotions of GHMC regular Employees 24. Transfers of GHMC Regular Employees 25. Sanction of Leaves, Petrol, Landline phone connections to officers,


GHMC Page 17

Department Sl.No Services Study permission, NoC for passport/Visa

26. Pay fixation in the promotion post to ministerial staff (HO) 27. Disciplinary Proceedings – Unauthorized absence, Bribery, Bigamy

cases of ministerial staff of GHMC employees only 28. Disciplinary Proceedings – Charge Memo 29. Disciplinary Proceedings – Regularization of Suspension period 30. Service Registers 31. Payroll 32. Pensions 33. Central Stationery 34. Unions 35. Library

Citizen Service Centers

36. Citizen Service Centres

Press and Media 37. Press Management System Secretary 38. Details of elected representatives of corporation

39. Standing Committee Area Sabha and Ward Committee meetings and Action taken reports

40. Allocation of Work through Ward Committee – Work Allocation process

41. Allocation of Work through Ward Committee 42. Creation of Master Data on the General Body Agenda / Minutes /

Notices 43. Creation of Master Data on Study tours , Honorariums paid

Taxation 44. Assessment of Un-Assessed Property & Under Assessed Property 45. New Assessment Property Tax 46. Mutation (title transfer / change of ownership) of the property 47. Collection of Property Tax through Handheld Devices 48. Vacancy Remission 49. Corrections in the property tax records 50. Exemption of Property Tax 51. Sub-division of Property 52. Amalgamation / Aggregation of Property Tax 53. Service Charges from Central Govt. on Properties of Central

Government 54. Deletion of Property Tax 55. Assessment of Property tax on Lands

Electricity 56. Procurement of agencies for Maintenance of Street Light 57. Procurement of Material for Street Lighting 58. Procurement of Contracts for execution of Maintenance works 59. Procurement of agencies for developing street lighting in new areas

Entomology 60. Database of epidemic and Communicable diseases 61. Action taken on the disease control

Advertisement 62. Issuance of Licenses 63. Collection of Advertisement Tax 64. Renewal of Advertisement Tax 65. Creation of database of Hoardings, Lollipops, Glow Signs, Etc.,

Engineering 66. Projects and Works Maintenance 67. Central Emergency, Quality Control, Stores

Information 68. Portal Management


GHMC Page 18

Department Sl.No Services Technology 69. Manage IT services

70. Project Management Information System Urban Community Development

71. Creation of Database of the schemes and activities 72. Integration with MEMPMA 73. Database of NGOs / SHGs / NAC etc., 74. Acceptance of application for schemes / trainings, etc.,

Town Planning 75. Issuance of Building Plan Approvals 76. Issuance of Layout approvals 77. Issuance of Permissions for erecting Cell phone towers 78. Creation of Database on the Heritage Buildings 79. Creation of Database on Dangerous Structures 80. Identification of unauthorized constructions and issuance of Notices 81. Sub Division of Plots 82. Road Widening, Land Acquisition, RDPs

Legal 83. Tracking and Monitoring of Legal Cases of GHMC Accounts 84. Financial Management Procurement 85. Integrated Procurement Management System for the departments in

the corporation Transport 86. Integrated Transport Management System for the corporation Dash Board 87. Dash board for the monitoring purpose MIS 88. Management Information System to generate reports for monitoring of

the GHMC activities 6.5 Existing e-Governance Initiatives in GHMC The GHMC applications have 16 modules designed for providing G2C and G2B services and 4 G2G modules for internal administration purposes. These modules assist the government in rendering specific set of services to the citizens. The table below details the various modules falling under specific departments of the GHMC along with the service category. S.No Module Technology Existing

Architecture Web Enabled Database Services provided by the

application

1. Property Tax Java J2EE, MVC Architecture Yes Oracle 9i

• Assessment of new property • Title Transfer of property • Sub-division of property

2. Vacant Land Java J2EE, MVC Architecture Yes Oracle 9i • Assessment of new property

3. Birth & Death ASP Client Sever (2 tier) Yes

Oracle 9i • Registration of Birth and Still Birth & Issue of Non Availability Certificate

• Death Registration and Issue of Non Availability Certificate

• Corrections in Registration • Requisition for Birth/Death

Certificate

4. D&O Trade Licenses

ASP Client Sever (2 tier) Yes Oracle 9i • Issuance of New License

• Renewal of License

5. HRMS/ Payroll

ASP Client Sever (2 tier) No Oracle 9i • Payroll Processing for

employees of GHMC

6. Works Java J2EE, MVC No Oracle 9i • Maintenance and tracking of works of GHMC

7. Town Planning

ASP Client Sever (2 tier) Yes Oracle 9i • Issuing Building Plan

Approvals 8. File ASP Client Sever No Oracle 9i • Digital movement of file from


GHMC Page 19

S.No Module Technology Existing Architecture

Web Enabled Database Services provided by the

application Monitoring (2 tier) each level of the hierarchy

• Enables tracking the status of file electronically

9. Transport ASP Client Sever (2 tier) No Oracle 9i • Transport management

10. Advertisement

ASP Client Sever (2 tier) Yes

Oracle 9i • Issuance of Licenses and Renewal

• Collection of Advertisement Tax

11. Electrical

ASP Client Sever (2 tier) Yes

Oracle 9i • Street light Management • Procurement and stock

maintenance of Material for Street Lights

12. OSRT Java J2EE, MVC Architecture Yes

MySQL • OSRT helps in monitoring the real time activities of the civic amenities

13. Court Cases Java J2EE, MVC Architecture No

Oracle 9i • Address legal cases which are filed by the employees against GHMC

• Address legal cases which are filed by the citizens against GHMC

• File cases on citizens on behalf of GHMC

14. Cell Phone Module ASP Client Sever

(2 tier) No Oracle 9i • Monitors the mobile number

and stock of the mobile phones in GHMC

15. Grievance Redressal Java J2EE, MVC

Architecture Yes

Oracle 9i • Filing and tracking of complaints by the public

• Assist the higher officials to track the status of closure of these complaints

16. Inventory .Net Client Server No Oracle 9i Maintains all the inventory of the GHMC


GHMC Page 20

7. SCOPE OF THE PROJECT The Greater Hyderabad Municipal Corporation divided into 5 Zones and 18 circles and 150 wards in and around areas of Hyderabad and extended areas of Hyderabad. Like all large e-Governance programs, GHMC has been evolving and stabilizing towards better delivery of citizen services, which is the main aim of GHMC. The primary scope of the project is to implement/roll out the software application across all offices of GHMC. The roll out would include installation and commissioning of hardware, connectivity, other infrastructure and all associated services as mentioned in the RFP. The scope of the “bundled services” to be offered by the SI includes the following: Category S. No Task/ Activity

I. Design, Develop, Deploy and Implement Software Application

Requirement Gathering, Preparation of SRS , HLD, LLD, SDD

1 The SI must clearly understand the requirements and propose a solution which helps in meeting the specific requirements of GHMC.

2 Carry out a Systems Study to prepare Systems Requirements Specification (SRS) document based on the Functional Requirements Specifications (FRS).

3 Creation of High Level Design (HLD), Low Level Design (LLD) documents, Software Design Documents (SDD)

Design of Solution

The selected SI shall develop on the Functional Requirement Specifications (indicative but not exclusive) provided in this RFP and prepare documents regarding each Process Flow. The SI shall perform the following tasks:

• Documents regarding each Process Flow • Design of Application • Design of Workflow with well-defined business rule for

the application • Design of Application Architecture , Network & Security

Architecture , overall IT Infrastructure , Logical and Deployment Architecture

• Design of Integration methodology • Design of Quality Assurance Plan & Methodology • Design of Security Policy • Design of Transition policy and Plan, during and at the

end of the tenure of the agreement or termination of the agreement

Development of Software 3

Development of the software solution, in accordance with frameworks and standards based on the specifications finalized through the Documents regarding each Process Flow and Solution design.

Software Testing, Go-Live and 3rd Party Certification

4 Integration Testing, System Testing (including Performance Testing, Load Testing), Functional Testing

5 User Acceptance Testing 6 STQC Certification for the application

7 Go-Live to a set of pilot users of GHMC including the Program Managing agency appointed by GHMC for intensive scenario based testing

Project Management for Application Development Services

8 Project Management Services and Preparation of Integrated Project Plan

9 Creation and maintenance of Requirements Traceability Matrix 10 End-to-end project documentation and creation of manuals


GHMC Page 21

Category S. No Task/ Activity

II. Supply, Install and Acceptance Test for H/W & N/W at all Circles, GHMC HQ and Data Centre

Hardware Procurement, Supply, Installation and acceptance test

1 Procurement of H/w and relevant software licenses, their installation and commissioning at all circles, zones and circle offices and the required infrastructure at Data Centre

Provision of Networking 2 Providing network connectivity between SDC and across Zones, Circles and Headquarters of GHMC using APSWAN

Site Preparation 3 Preparation of Interiors, Electrical Fittings, Other basic requirements at all the implementation locations of GHMC

III. Change Management, Capacity Building and Handholding Support

Training and Change Management Workshops

1

The Bidder is required to train/retrain the designated technical and end-user staff / vendors to enable them to effectively operate the system and shall undertake Change Management interventions as necessary to achieve project objectives. Departmental and Selected End-User Training. Training should also encompass “training the trainer”.

IV. Data Migration

Data Migration 2

The SI is also responsible for migrating the all the information/ data available in the existing applications to modified system. SI shall validate the data in the existing applications and migrate the data to the integrated GHMC application.

V. Integration with Legacy Systems, State Level Solutions and other Databases

Integration with GHMC Legacy System 1

Software application developed should provide the space for integration of the legacy Systems of GHMC like Oracle Financials based financial system, OSRT, Grievance System, Call Centre, etc.,

Scope for development of State Level Application

2

Software application should have a provision to scale up the application to implement in all the ULBS of the state. The application should also integrate with SSDG, SDC, UID,eSeva, Meeseva etc.,

Linkages to Other Databases 3

The application should be robust and should have an option to integrate with other databases of APCPDCL, UID, HMWSSB, civil supplies, etc…

VI. Operational Maintenance for S/W, H/W & N/W

Support & Handholding 1

Application Solution Management and Post Implementation Support Services

• For Application Software • For RDBMS / Application Server / Web Server at Data

Centre Annual Maintenance Support for 5 years 2 Infrastructure and Network Services Management at all offices of

GHMC, Data Centre, Call Centre and Citizen Facilitation Centre’sExit Management & Transition Services 3 Capacity Building – Plan and Implementation

Other Scope Apart from the above scope the System Integrator need to perform the following activities as an integral part of the project implementation VII. Supply of Consumables for GHMC officesSupply of photocopier 1 The Vendor shall maintain the existing operable photocopier


GHMC Page 22

machines machines and supply additional Photocopier machines required for GHMC operations on rental basis as per indent

Supply of Consumables required for GHMC for a period of 5 years

2 The vendor is required to supply the required toners / cartridges to GHMC on the need basis for 5 years as per indent

VIII. Manpower Services

Providing services for out sourced employees of GHMC

1

The System Integrator has to extend the services GHMC in providing data entry operators of GHMC as per indent (approximately 600-800 including the existing data entry operators).The selected vendor should follow the statutory requirements as per the GO No 3 of the finance department of GoAP as amended/ replaced from time to time.

In implementing the above, the SI shall strictly adhere to the standards set by the GHMC and State Government. The SI is required to study the key process requirements, the functional requirements and develop the required solution w.r.t the functional requirements, configuration and customization specific to GHMC processes, developing interfaces to integrate existing legacy systems to be interfaced with any additional specific module, required integration requirements with the other MMP applications such as SSDG, state portal etc. The detailed Functional Requirement Specifications, Non Functional Requirements and the specific customization requirements are detailed in section 13 of this volume of RFP The project will be managed out of Nodal Officer’s office (O/o Additional Commissioner (IT), GHMC) in GHMC. At all points in the execution of the project, key senior resources including the project manager must be based at Nodal Officer’s office in GHMC. Successful bidders are requested to note that any changes suggested by GHMC to the scope of work mentioned in the RFP (as per existing subjects handled by the GHMC and without the need for purchase of any additional COTS product) at a later date or time is deemed to be included into the overall scope of work. 7.1 Configuration, Development and Integration of Integrated IT solution of GHMC 7.1.1 System Study, Design, Application Development, and Integration The SI shall carry out a detailed systems study to refine the Functional Requirements Specifications provided as section 13 to this RFP and formulate the System Requirements Specifications (SRS) incorporating the functional specifications. The system study should also include different integration points with external agencies as per the requirement of GHMC. The SRS preparation shall take into account the BPR changes suggested by the GHMC.

a) Requirement Gathering: The SI shall understand the requirements and propose a solution which helps in meeting the specific requirements of GHMC. The SI must study the infrastructure needs of the project & visit the GHMC locations and gather the detailed requirement, understand the setup and perform the gap analysis.

b) Process Study: The SI should study the each process of the GHMC for the application development. GHMC will provide the relevant support, available reports and information required for completing the study

c) Preparation of SRS and Design of Solution: To prepare a System Requirement Specification (SRS) report –based on an independent assessment of the requirement of GHMC and the functional requirements as specified in this Tender document for e-enabling the services identified for implementation under the project.


GHMC Page 23

d) Review and Updating of FRS: To review and update the FRS based on the System Requirement Specification (SRS) report for e-enabling the services identified for implementation under the project.

e) High Level Design (HLD): Once the SRS is approved, the SI would create High Level Design (HLD). The SI would prepare the HLD and have it reviewed and approved by the GHMC Nodal Officer.

f) Detailed (Low Level) Design (LLD): The Low Level Design (LLD) would interpret the approved HLD to help application development and would include detailed service descriptions and specifications, application logic (including “pseudo code”) and UI design (screen design and navigation). The preparation of test cases will also be completed during this stage. GHMC Nodal officer will sign off on the LLD documents.

Deliverables

a) Process Study Report and Gap Analysis Report b) Preparation of SRS and Design of Solution c) Review and Updating of FRS d) High Level Design (HLD): e) Detailed (Low Level) Design (LLD)

7.1.2 Application Development and Unit Testing a. Application Development: The SI would develop the application in accordance with the approved requirements specifications and design specifications and according to the approved Project Plan; and carry out the Unit Testing of the application in accordance with the approved test plans. The SI shall also develop a Data Migration Utility/application for the additional functionalities with all the formats and tools to load the data into the state databases. This will migrate data from legacy based systems to the new databases. The user acceptance testing and fine-tuning of the application would be at GHMC Head Office. Also, the key senior resources would have to be based on site at GHMC Head Office. The SI would develop the solution based on the specifications finalized through the System Requirement Specifications (SRS) and solution design for the various GHMC departments. The following processes are identified for the application development of an Integrated solution: Department Sub –

Module Sl.No Services

Health and Sanitation

Birth and Death

1. Registration of Births and Deaths 2. Issuance of the Digitally Signed Certificates of Birth and

Death 3. Issuance of the Ink Signed Certificates of Birth and Death 4. Procedure for issuing Non-availability certificates for the

persons whose names are not in the existing Database 5. Procedure for inclusion of Child Name in the Birth Register6. Procedure for correction of entries in Births and Deaths

records 7. Registration of Still Births

D & O Trade Licenses

8. Procedure for issuing new trade license 9. Procedure for Renewal of Trade License


GHMC Page 24

Department Sub – Module

Sl.No Services

Dispensaries 10. List of Dispensaries and the staff availability SWM 11. Solid Waste Management System

Parks Parks 12. Developing New Parks (Vacant Lands and Earmarked Areas)

13. Maintenance of Existing Parks and Green Areas Estates Estates 14. Allotment of properties for lease, mortgage or sale; and

15. Collect rents from the properties let out or leased Veterinary Veterinary 16. Issue of pet licenses and breeding dog licenses;

17. Issue of licenses to trades of non-vegetarian origin; 18. Details of Hot Spots, Animal Pounds, ABC and AR

Vaccination Sports Sports 19. Organizing summer coaching camps, Organizing advance

coaching camps and organizing tournaments to identify talents

20. Maintenance of sports and games facilities 21. Hiring and leasing of sports facilities 22. Procurement of equipment, infrastructure, manpower etc.,

Administration Administration

23. Promotions of GHMC regular Employees 24. Transfers of GHMC Regular Employees 25. Sanction of Leaves, Petrol, Landline phone connections to

officers, Study permission, NoC for passport/Visa 26. Pay fixation in the promotion post to ministerial staff (HO) 27. Disciplinary Proceedings – Unauthorized absence,

Bribery, Bigamy cases of ministerial staff of GHMC employees only

28. Disciplinary Proceedings – Charge Memo 29. Disciplinary Proceedings – Regularization of Suspension

period 30. Service Registers 31. Payroll 32. Pensions 33. Central Stationery 34. Unions 35. Library

CSC Citizen Service Centre

36. Citizen Service Centers

Press and Media

Press Management

37. Press Management System

Secretary Council Management

38. Details of elected representatives of corporation 39. Master Data Creation on the Information of the Standing

Committee Area Sabha and Ward Committee meetings and Action taken reports

40. Allocation of Work through Ward Committee – Work Allocation process

41. Allocation of Work through Ward Committee 42. Creation of Master Data on the General Body Agenda /

Minutes / Notices 43. Creation of Master Data on Study tours , Honorariums

paid


GHMC Page 25


Sl.No Services

Taxation Taxation on Lands and Building

44. Assessment of Un-Assessed Property & Under Assessed Property

45. New Assessment Property Tax 46. Mutation (title transfer / change of ownership) of the

property 47. Collection of Property Tax through Handheld Devices 48. Vacancy Remission 49. Corrections in the property tax records 50. Exemption of Property Tax 51. Sub-division of Property 52. Amalgamation / Aggregation of Property Tax 53. Service Charges from Central Govt. on Properties of

Central Government 54. Deletion of Property Tax 55. Assessment of Property tax on Lands

Electricity Electricity 56. Procurement of agencies for Maintenance of Street Light 57. Procurement of Material for Street Lighting 58. Procurement of Contracts for execution of Maintenance

works59. Procurement of agencies for developing street lighting in

new areas Entomology Entomology 60. Database of epidemic and Communicable diseases

61. Action taken on the disease control Advertisement Advertisemen

t 62. Issuance of Licenses 63. Collection of Advertisement Tax 64. Renewal of Advertisement Tax 65. Creation of database of Hoardings, Lollipops, Glow Signs,

Etc., Engineering Works

Module 66. Projects and Works Maintenance 67. Central Emergency, Quality Control, Stores

Information Technology

IT Module 68. Portal Management 69. Manage IT services 70. Project Management Information System

Urban Community Development

Urban Community Development

71. Creation of Database of the schemes and activities 72. Integration with MEMPMA 73. Database of NGOs / SHGs / NAC etc., 74. Acceptance of application for schemes / trainings, etc.,

Town Planning Town Planning

75. Issuance of Building Plan Approvals 76. Issuance of Layout approvals 77. Issuance of Permissions for erecting Cell phone towers 78. Creation of Database on the Heritage Buildings 79. Creation of Database on Dangerous Structures 80. Identification of unauthorized constructions and issuance

of Notices 81. Sub Division of Plots 82. Road Widening, Land Acquisition, RDPs

Legal OLCMS 83. Tracking and Monitoring of Legal Cases of GHMC Accounts and Audit

Accounts and Audit

84. Integration with the existing ERP module


GHMC Page 26


Sl.No Services

Procurement Integrated Procurement Management System

85. Integrated Procurement Management System for the departments in the corporation

Transport Integrated Transport Management System

86. Integrated Transport Management System for the corporation

Dash Board Dash Board 87. Dash board for the monitoring purpose MIS Management

Information System

88. Management Information System to generate reports for monitoring of the GHMC activities

The SI will also be responsible for:

• Conducting System Study of all the existing applications available in GHMC • Preparation of System Requirements Specifications (SRS) and different integration

points with External Agencies. • Preparation of implementation document with respect to Configuration,

Customization and extensions as per the requirement of GHMC. • Preparation of the Solution Design. • Solution Development and/or Customization and/or Configuration and/or Extension

as required. • Development of reports. • Formulation of test plans and test cases for additional functionalities and different

integrations with external agencies • Preparation of Change/Reference document which will include all the changes or

deviations from the base version of the GHMC IT application • Testing of the configured solution and additional functionalities. • Integration requirements to various interfaces / SSDG shall also be incorporated in

the SRS and shall form the scope of work for the SI. Deliverables

• Solution Software, • Operational/ Technical manual, • Library files, • Setup programs etc., • Sign-off from GHMC

b. Software Testing, Go-Live and 3rdParty Certification by STQC

• To design Test Cases for the solution testing using the data, to be digitized

separately • To prepare the testing approach and plan • To perform the testing of the solution based on the approved test plan, document

the results and fixing of the bugs found during testing • Installation and Configuration of solution • Installation/integration of Operating System, Database, Application Server etc. • Configuration of Users, providing access as per roles defined • Updation of Installation Manuals with lessons learnt/identified Gaps • To implement the solution in all locations under GHMC – based on an independent


GHMC Page 27

assessment of the software, user acceptance and testing • To ensure that the software design and implementation takes care of necessary

security aspects such as data safety, access controls, integrity, back up measures and disaster recovery

• Incorporation of changes, if any, in the solution • Implementation and roll out of the solution at all the implementation locations • During the pilot implementation / parallel run the application should synchronized

with existing G2C applications which are in use without hampering the services (Testing and QA requirements are mentioned in the Annexure -2 Deliverables

• Quality Certification • Security Certification • IS audit certification from the APTS empanelled IS Audit agencies.

c. Site Preparation at all Offices in GHMC The SI is expected to prepare the client sites for setting up the necessary client site infrastructure. Site preparation at all locations of GHMC as specified in Annexure 5 will include but not limited to:

• Provision of Local area network (LAN cables, LAN ports) • Provision of power points in adequate numbers. • Earthing and electric cabling as required at the site.

Site Preparation shall cover all the activities necessary as mentioned above to enable the GHMC to setup the client side infrastructure and operate the application. Following are the total number of sites identified: Heads No. of Locations GHMC Head Quarters 1 Zonal Offices 5 Circle Offices 18 Ward Offices 150 Mahila Bhavans 18

Other Locations 14 (Dumping Yard, Transfer Stations/ Parking Lots, Buddha Bhawan, Harihar Kala Bhavan etc.)

Deliverables

• Signoff Certificates / Installation certificate from the concerned designated officer of

GHMC 7.2 Infrastructure at the Client Side Locations The premises for offices will be provided by GHMC. The list offices and other locations where the infrastructure is required to be installed/ provided are detailed at Annexure 5. SI shall procure the infrastructure required at these locations. At each such location the following shall be carried out.


GHMC Page 28

• Supply of the hardware, software, networking equipment’s, UPS, etc., as per the requirements

• Redundant Network Connectivity - Ensuring last mile connectivity and testing. • Installation, Testing and Commissioning of UPS etc. • Physical Installation of Desktops, Printer, Scanner, /MFD, Switch- Connecting

peripherals, devices, Plugging in etc. • Operating System Installation and Configuration. • Installation of Antivirus and other support software if any. • Configuring the security at the desktops, switch and broadband connection routers. • Network and browser Configuration. • Test accessibility and functionality of the application from the desktops. • Ensuring all the systems required are supplied, installed, configured, tested and

commissioned and declaring the site to be operational. GHMC application will be accessed and used at various access locations across the Jurisdiction of GHMC. The detailed list of ICT infrastructure at the proposed locations is as given in Annexure –5. No additional cost will be paid to System Integrator in case of any additional installations (except procurement of new hardware) required by GHMC at the office locations of GHMC Deliverables

• Signoff Certificates / Installation certificate from the designated officer of GHMC

7.3 Network Connectivity The WAN connectivity for the GHMC project will be provided by APSWAN through MPLS connectivity at selected offices, APSDC and VPN on Broadband for rest of the offices. Existing BSNL broadband connectivity will be used for backup. However, SI will be responsible for setting up and maintenance of LAN at the individual offices. Deliverables

• Signoff Certificates / Installation certificate from the designated officer of GHMC

7.4 IT Infrastructure at the Data Center and Disaster Recovery Center The SI shall provide system integration services to procure and commission the required hardware, software etc. at the Andhra Pradesh State Data Centre (APSDC) and Disaster Recovery Centre to deploy the GHMC application and integrate with external agencies as provided in the functional scope. The SI shall be completely responsible for the sourcing, installation, commissioning, testing and certification of the necessary software licenses and hardware required to deploy the application at the State Data Centre of Government of Andhra Pradesh and at the Disaster Recovery Centre (DRC). SI shall ensure that support and maintenance, performance and up-time levels are compliant with SLAs. SI shall coordinate with APSDC in isolating the issues between solution stack and common infrastructure provided by APSDC; and in ensuring that they are reported to concerned parties so that they are resolved in timely manner.


GHMC Page 29

To ensure redundancy requirements are met, SI shall ensure that infrastructure (hardware / software) procured by the SI has redundancy built in. SI shall also provide descriptive ‘Deployment Model, Diagrams and Details’ so that redundancy requirements for the common Data Center infrastructure can be addressed The SI is responsible for sizing the hardware to support the scalability and performance requirements of the solution. The SI shall ensure that the servers and storage are sized adequately and redundancy is built into the architecture that is required to meet the service levels mentioned in the RFP. In case of the Primary DR Centre is not ready GHMC will provide an alternate site for setting up the DR center to the System Integrator, as a temporary measure till permanent DR site is ready.. SI shall provide a Bill of Material that specifies all the hardware, software and any additional networking components of solution for the State Data Centre and DRC, in detail so as to facilitate sizing of common Data Centre and DRC infrastructure such as Racks, Power and Cooling, Bandwidth among other components. The common DC and DRC infrastructure will be provided by GHMC in consultation with GoAP. SI shall ensure that effective Remote Management features exist in the solution so that issues can be addressed by the SI in a timely and effective manner; and frequent visits to Data Centre /DRC can be avoided. After commissioning and testing of the entire system at State Data Center / DRC, the SI shall support GHMC in getting the system certified by a 3rdparty agency identified by GHMC. The following common Data Centre services will be available to the SI through the Data Centre Operator / Data Centre Service Provider:

• Suitable RACK Space • Power and Cooling • UPS, DG set power backup • Bandwidth and Connectivity • LAN • VPN • Firewall • Intrusion Protection System • Fire prevention • Physical security surveillance • Network Operation Centre • EMS and NMS Tools • Antivirus Software • Common Data Centre facility Maintenance and Support

The SI is responsible for providing the infrastructure as mentioned in the Bill of Material of the RFP at the Data Centre / DRC. The SI shall also deploy a backup software to periodically take backup all data and software. As a part of implementing the monitoring tool for GHMC IT Application, the bidders should extend the current EMS available in the Andhra Pradesh State Data Centre (APSDC) by procuring additional licenses of the existing SDC EMS modules. The existing modules at APSDC are Infrastructure Management, Database Performance, SPIM (Server Management), Access Control, Enterprise Log Management, Client Automation, Service Desk and IT Asset Manager. The bidder shall ensure proper, seamless and tight integration between the existing APSDC EMS and GHMC IT Application.


GHMC Page 30

The Application Performance Management tool is an essential requirement in this project and the same needs to be proposed as a part of the current offering. Specifications for the Application Performance Management requirement

a) Application Transaction Performance Monitoring System:

• The proposed solution must proactively monitor 100% of real user transactions; detect failed transactions; gather evidence necessary for triage and diagnosis of problems that affect user experiences and prevent completion of critical business processes

• The proposed solution must provide deeper end-to-end transaction visibility by monitoring at a transactional level and without deploying any software at end user desktop.

• The proposed solution must provide a single view that shows entire end-to-end real user transaction and breaks down times spent within the application components, SQL statements, backend systems and external 3rdparty systems.

• The proposed solution must be able to provide root-cause probability graphs for performance problems showing the most probable root-cause area within application infrastructure.

• The proposed solution must support any combination of operating platforms with a single methodology.

• The proposed solution must provide real-time performance metrics for leading application servers

• The proposed solution must allow monitoring granularity of no more than 15 seconds for all transactions.

• The proposed solution must be able to monitor application performance to all connected backend systems or any other external system from a single agent within the application, thus eliminating the need to install separate agents on all connected systems.

• The proposed solution must not necessitate any changes to application source code. • The proposed solution should provide out of the box monitoring of Web-services • The proposed solution should be seamlessly integrated with the existing

Infrastructure Management Solution out of the box.

b) End-User Experience Management System:

• The proposed solution should measure the end users' experiences based on transactions without the need to install agents on user desktops.

• Solution shall work based on the passive listening of the network traffic to and from the Web servers, and analyzes the transactions without affecting the performance or availability of the IT infrastructure in any way.

• The proposed system must be able to detect user impacting defects and anomalies and reports them in real-time:

o Slow Response Time o Fast Response time o Low Throughput o Partial Response o Missing component within transaction

• The proposed system must be able to pro-actively determine exactly which real users were impacted by transaction defects, their location and status.

• The licensing should be processor based and should not be dependent on the no. of transactions


GHMC Page 31

The indicative specifications for the servers and other components are provided in section 11 of this volume of RFP Deliverables: Signoff Certificates / Installation certificate from the designated officer of GHMC 7.5 Data Migration 7.5.1 Data Migration Migration of the data from the legacy systems to the new system will include identification of data migration requirements, collection and migration of user data, collection and migration of master data, collection and migration of documentary information, and migration of data from the legacy systems. The SI shall perform the migration from the existing systems / applications to the newly developed integrated application. The data migration to be performed by the SI shall be preceded by an appropriate data migration need assessment including data quality assessment. The data migration strategy and methodology shall be prepared by SI requires a formal approval from GHMC. However, it is the ultimate responsibility of SI to ensure that all the data sets which are required for operationalization of the agreed user requirements are migrated. Any corrections identified by GHMC or any appointed agency, during Data Quality Assessment and Review, in the data migrated by SI, shall be addressed by SI at no additional cost to GHMC. So far as the legacy data is concerned, they are either available as structured data in the IT systems that are currently used by GHMC for related work. Almost all of such data items relevant for GHMC Operations are maintained at all the head office of GHMC. 7.5.2 Data Migration Requirements Following requirement must be met by the vendor for Data Migration;

• Mapping should be done between the different data sources after the approval of GHMC, as there could be structural difference in the currently stored data.

• To carry out the migration of legacy electronic data to the New System. • To provide with the checklists of the migrated data to GHMC for validation, including

number of records, validations (where possible), other control/hash, and total highlighted errors, abnormalities and deviations.

• To incorporate corrections as proposed. • To get initial sign off from GHMC for migrated data. • At the end of migration, all the data for old applications must be available in the new

database. 7.5.3 Scope of Data migration The SI is also responsible for migrating the all the information/ data available in the existing applications of GHMC to the newly developed integrated system as part of the implementation in all the locations of GHMC. SI shall validate the data in the existing applications and migrate the data to the new system. The approximate volume of data that’s needs to be migrated is about 250 GB


GHMC Page 32

7.5.4 Methodology of Data Migration: Data migration methodology will comprise the following steps, explained as below. However this is just a guideline for data migration effort and the SI will be required to devise his own detailed methodology and get it approved by Nodal Officer of GHMC.

a. Analysis: Analysis of the legacy data and its creation, conversion, migration and transfer to the proposed new data base schema will be started during the scoping phase and shall take a parallel path during the design and development phase of the application. It will cover the following steps:

i. Analyze the existing procedures, policies, formats of data in lieu of the new proposed system to understand the amount of the data and the applicability

ii. Write a specification to create, transfer and migrate the data set iii. Document all exceptions, complex scenarios of the data iv. This phase will generate the specification for Data Take on routines.

b. Transformation: Transformation phase can be commenced after integration

testing phase. It will entail the following steps: i. Identify the fields, columns to be added/deleted from the existing system ii. Identify the default values to be populated for all ‘not null’ columns iii. Develop routines to create (Entry if any by data entry operators), migrate,

convert the data from hard copies, old database (if any), computer records to the new database

iv. Develop test programs to check the migrated data from old database to the new database

v. Test the migration programs using the snapshot of the production data vi. Tune the migration programs & iterate the Test cycle vii. Validate migrated data using the application by running all the test cases viii. Test the success of the data take-on by doing system test

c. Data Take-on: Take-on phase will be initiated when the proposed solution is

ready to be deployed. It will entail the following steps: i. Schedule data transfer of the computerized data that has been newly

created by the data entry operators based on the hard copy records. ii. Schedule data transfer of the existing digital data in the proposed new

format iii. Migrate the data from an old system (legacy) to the envisaged database iv. Test on the staging servers after the data take-on with testing routines v. Migrate from staging servers to production servers vi. Deploy and rollout the system as per the project plan

7.5.5 Additional Guidelines for Data Migration

i. SI shall formulate the “Data Migration Strategy document” which will also include internal quality assurance mechanism. This will be reviewed and signed off by GHMC prior to commencement of data migration.

ii. SI shall incorporate all comments and suggestions of GHMC in the Data Migration Strategy and process documents before obtaining signoff from GHMC

iii. SI shall perform mock data migration tests to validate the conversion programs. iv. SI shall ensure complete data cleaning and validation for all data migrated from the

legacy systems to the new application. v. SI shall validate the data before uploading the same to the production environment.


GHMC Page 33

vi. SI shall generate appropriate control reports before and after migration to ensure accuracy and completeness of the data.

vii. SI shall convey to GHMC in advance all the mandatory data fields required for functioning of the proposed solution and which are not available in the legacy systems and are required to be obtained by GHMC.

viii. In the event it is unable to obtain all the mandatory fields as conveyed by SI, SI shall suggest the most suitable workaround to GHMC. SI shall document the suggested workaround and sign-off will be obtained from GHMC for the suggested workaround.

ix. SI shall conduct the acceptance testing and verify the completeness and accuracy of the data migrated from the legacy systems to the proposed solution.

x. GHMC may, at its will, verify the test results provided by SI. xi. Historical logs should be maintained by the system

7.5.6 Data Quality The Agency shall perform the Data Quality Assessment for the Data migrated by SI to the system. The errors/gaps identified during the Data Quality Assessment shall be addressed by SI before moving the data into production environment, which is a key mile stone for Go-live of the solution. Deliverables

• Data Migration Strategy Report • Data Migration Report (after completion of the migration) for sign-off

7.6 Capacity Building and Training 7.6.1 Identification of Trainers (Internal) Greater Hyderabad Municipal Corporation shall identify qualified Trainers with relevant IT experience and training competency within each department who will be directly trained by the System Integrator and will be responsible for interfacing with the System Integrator for all the Capacity Building Initiatives. 7.6.2 Identification of Trainees: The System Integrator shall identify the trainees for the capacity building and change management activity with the help of the nodal officer of the GHMC. The trainees need to be identified in three categories as mentioned below. • Group I: Identify the key senior officers who are directly receiving/analyzing the reports

through the IT application. Role-based training will be carried out for these officers at GHMC Headquarters by the System Integrator

• Group II: Identify the key officers in charge of a zone/ circle and at head office who are directly reviewing the performance through GHMC IT Application, reviewing the reports generated by the system, carrying out the required analysis using application and providing the necessary guidance to the officers at the cutting edge. Role-based training will be carried out for these officers at GHMC Headquarters by the System Integrator

• Group III: Identify the key officers (below Deputy Commissioners) in the circles / Zones and Head Office who will use this application for service delivery and utilize the basic and advance search features to facilitate their transaction process. In addition to the computer awareness training, role-based training will be carried out for these officers at each circle and zone by the System Integrator. Refresher training can be carried out by the internal trainers subsequent to the System Integrator trainings


GHMC Page 34

The main challenges to be addressed effectively by the SI are wide variability in computer proficiency and minimal availability of time. The SI is responsible for creation of a detailed and effective training strategy, user groups and classifications, training plan and guidelines, detailed training material, training program designed their delivery to the target groups. The SI is responsible for preparation of training material, designing the training programs and their delivery to the target group. The SI shall be responsible for the following activities as part of the End User and Train the Trainer Training 7.6.3 Develop Overall Training Plan SI shall be responsible for finalizing a detailed Training Plan for the program in consultation with GHMC officials covering the training strategy, environment, training need analysis and role based training curriculum. SI shall own the overall Training plan working closely with the Training team. SI shall coordinate overall training effort. 7.6.4 Develop Training Schedule and Curriculum SI shall develop and manage the training schedule in consultation with GHMC, aligned with the overall implementation roadmap of the project and coordinate the same with all parties involved. Training schedule shall be solution based and shall be optimized to reduce business impact and effective utilization of Training infrastructure and capacities. The training curriculum for the training program should be organized by modules and these should be used to develop the training materials. The training curriculum shall outline the mode of delivery, module structure and outline, duration and target audience. These sessions should be conducted such that the users of the application/modules are trained by the time the application “goes-live” in the circles/ zones / head office with possibly not more than a week’s gap between completion of training and going live of modules. Continuous reporting (MIS) and assessment should be an integral function of training. 7.6.5 Develop Training Material Based on their needs and the objective, training programs could be organized under the following themes: 1. Basic IT skills and use of computers to creating awareness about the benefits of ICT and

basic computer skills 2. Role-based training on the application – Basic and Advanced. This training should be in

a role based, benchmarked and standardized format, multi-lingual and lead to learning completion and assessment. It should also allow for self-learning and retraining. Training would include mechanism for demonstration using audio/video/simulated/demo practice exercises and evaluation of trainees.

3. “Train the Trainer” programs, where members of the GHMC staff would be trained to enable them to conduct further training programs, thus helping build up scalability in the training program and also reducing the dependency on external vendors for training.

4. Design and development of the Training Manuals, User Manuals, Operational and Maintenance Manuals for the modules developed.

SI shall ensure that the training content meets all the objectives of the training course. The material shall be developed in English. SI shall also develop the training material for delivery through Computer Based Training, Instructor Led Training, Online User Material/Help Manuals and Job Aids.


GHMC Page 35

SI shall provide detailed training material providing step-by-step approach in soft and hard copies to all trainers for reference. 7.6.6 Deliver Training to End Users SI shall deliver training to the end users utilizing the infrastructure at GHMC. Training shall be an Instructor-Led Training (ILT) conducted by trained and qualified instructors in a classroom setting. To maintain consistency across trainings, standard templates should be used for each component of a module. An ILT course shall have the following components:

• Course Presentation (PowerPoint) • Instruction Demonstrations (Application training environment) • Hands-on Exercises (Application training environment) • Application Simulations: Miniature version of Application with dummy data providing

exposure to the real time scenario of post implementation) • Course Evaluations (Inquisition)

In addition to the ILT, a Computer Based Training (CBT) shall be organized for the modules. CBT should involve training delivered through computers with self-instructions, screenshots, and simulated process walkthrough and self-assessment modules. 7.6.7 Number of Trainees in each group on IT Enablement

Sl.No Group of Officers No. of Trainees1 Group I 50 2 Group II 200 3 Group III 1000 7.6.8 Training Effectiveness Evaluation

• SI shall evaluate the effectiveness of all end users trainings using feedback form • SI shall be responsible for analyzing the feedback and arrange for conducting

refresher training, wherever needed. • GHMC will periodically monitor the training effectiveness through the performance

metrics and Service levels and the SI shall comply with the same. • SI shall help the GHMC with complete Change Management exercise needed to

make this project a success. In fact Change Management will have to subsume ‘training’ as a key enabler for change. Following outlines the responsibilities of SI with respect to designing and implementation of change management plan for the Project.

7.6.9 Change management Stakeholder groups are categorized into following categories, based on their influence and role in managing the change and making the project successful: • Group I: Key senior officers (Zonal Commissioners and above) who are directly

receiving/analyzing the reports through the IT application. • Group II: Key officers in charge of a zone/ circle who are directly reviewing the

performance through GHMC IT Application, reviewing the reports generated by the system, carrying out the required analysis using application and providing the necessary guidance to the officers at the cutting edge.


GHMC Page 36

• Group III: Key officers (below Deputy Commissioners) in the circles / Zones and Head Office who will use this application for service delivery and utilize the basic and advance search features to facilitate their transaction process.

7.6.10 Communication and Awareness Communication & Awareness campaigns shall be conducted throughout the duration of the implementation of the project across the GHMC, at Project and Program level as well as for General awareness. SI shall work with the identified internal change agents (identified from all segments of GHMC) for all the Communication and Awareness Programs. SI shall utilize existing channels of communication and at the same time use innovative methods of communication for effectiveness. SI should ensure that the communication messages are consistent, continuous and easy to understand and wherever possible in multi lingual using all available channels. SI shall align communication content, timing and delivery to the deployment phases/plan of each solution. S. No Activities Details Frequency

1 Develop detailed communication plan

• SI shall prepare a detailed communication plan for the program in line with the implementation timelines of each solution

• SI shall ensure that all the impacted audience is covered in the communication plan and the most appropriate mode of communication is being used to deliver the messages to the target audience

Once

2 Develop Communication Content

• SI shall be responsible for developing the content for communication material in English, Hindi and vernacular language.

• • SI shall ensure that the communication is simple, continuous and consistent

Recurring Activity over the entire duration of the SI

3 Deliver Communication Events

• Prior to implementing the plan, the SI shall obtain the necessary sign-offs from GHMC on the Communication Strategy & plan and make necessary changes as recommended by GHMC.

• SI shall determine who needs to approve communications prior to dissemination, who is responsible for distributing the message, and who is responsible for Recurring Activity (once a month) over the entire duration of the SI ensuring that those accountable for specific elements of the plan follow through on their responsibilities.

• SI shall organize the communication events or interventions for the target audience.

• SI shall ensure consistency between messages delivered via different interventions, since the engagement of a key individual stakeholder or stakeholder group is an integrated effort, aiming at the same objective.

Recurring Activity (once a month) over the entire duration of the SI

7.6.11 Change Management Workshops SI shall conduct Change Management workshops build appreciation of change management and develop change leadership across the stakeholder groups detailed in para 7.6.9. SI shall design the necessary content (reading material, presentations) in English / Telugu / Urdu Language for the Change Management Workshops. SI shall conduct at least three Change Management Workshops (minimum of one-day) in the GHMC Headquarters and at least one


GHMC Page 37

Change Management Workshop (minimum of one-day) in each zone covering officers from each circle under the zone. The SI is required to conduct the Change Management Workshops for all the identified personnel in a phased manner in line with the overall implementation plan. These workshops shall be conducted at the locations provided by the GHMC. The workshop content & material shall be designed with specific focus on the requirements of the personnel. SI shall conduct workshops for each group of personnel in sync with the training plan and as part of the training module. SI is required to provide the necessary material for the workshops including presentations, training material etc. in both soft and hard copy formats. SI shall also associate and train the identified internal change agents (identified from the each circle / zone and head office) during these workshops so that subsequent workshops can be conducted by the internal change agents. Deliverables:

• Training need analysis report • Course curriculum • Stimulation assignments • Change Management Strategy • Presentations on Change Management • Evaluation Report on Change Management Workshops

7.7 Supply of Consumables

1. The Vendor shall be responsible for the supply the required Photocopier machines required

for GHMC operations on rental basis as per indent 2. The vendor shall be responsible for providing all consumables and any other goods or

articles required from time to time for operation of the project as per indent, which shall include (but not limited to)

• Cartridges and/or ribbons for printers. All the material purchased should be of true color and shall be purchased from an ISO certified manufacturer.

• Storage consumables for backup of data • Any other item which is required for the successful execution of the project.

The System Integrator should call for a competitive rate contract tender for all the consumables required by GHMC. GHMC will not pay any extra service charges. SI will be paid monthly as per the actual supply of consumables to GHMC. The SI shall maintain an inventory adequate for meeting the supply chain (preferably a quarter) for GHMC.

7.8 Manpower Services - Out sourced employees

GHMC is brining all the IT related out sourced staff (about 600-800 including presently working in head office, zones, circles) at different offices under the ambit of SI. The SI shall pay all the salaries including PF, ESI, and Service tax to these employees as per the pay structure provided by GHMC. GHMC will reimburse all these salaries to the SI on monthly basis. No additional charges will be paid to SI by GHMC for this service. This will be an extended service that the SI has to provide to GHMC as these Data Entry Operators/Programmers etc. facilitate the officials of the organization in delivery of citizen services. SI will be responsible for making timely payments to the outsourced staff, statutory payments to various institutions, periodic performance assessment and submission of reports in this regard.


GHMC Page 38

7.9 Integration with Legacy Systems, State Level Solutions, SMS gateway, Payment gateway& other Databases

The table below provides an indicative list of external applications and databases that are required to be interfaced with the Greater Hyderabad e Governance application. This external service may be added further during the implementation phase. No additional payment will be provided to the system integrator for the additional services that may be added during the implementation phase S.No Module Details

1. Works Developed on ASP using Oracle 9i database 2. OSRT Developed on Java Using MySQL database 3. "e" Procurement Application of Government of Andhra Pradesh is used 4. Call Centre / Grievance Module Application is being developed by independent vendor 5. Accounts and audit Running on oracle financials module

6. eSeva / MeeSeva / SSDG / CSCs Integration with eSeva / MeeSeva / SSDG / CSCs etc.

7. Bulk SMS Integration with Bulk SMS service of GHMC

8. MEPMA Should integrate with MEMPA for the services rendered by MEMPA for urban Population

9. Other Databases

The application should be robust and should have an option to integrate with other databases of APCPDCL, UID, HMWSSB, Civil Supplies, ESI, PF, Service Tax, IT etc…

10. State and National Gateways The application should also integrate with SSDG, SDC, UID

11. Payment Gateway Integrate with various banks payment gateway

12. GIS Platform (ARC GIS & Google Maps)

Should be able to display/process information on the GIS Platform from the various modules as per requirement

7.10 Mail & Messaging Services Centralized mailing facility shall be made available for all GHMC users (about 1500). It should have extensive security features to ensure privacy of users and the integrity of communication through user authentication, session encryption, and content filtering to help prevent spam and viruses, and mechanisms to monitor and enable regulatory compliance. It should support standard SMTP, IMAP and POP3 services. The Messaging system should provide a secure messaging and collaboration – email solution with standard features like calendaring, contacts and tasks, Archiving, Directory and LDAP address book, web based access to emails and support for data storage. Other features to be supported include – per-user filtering policies, user management, instant messaging, mailing list manager and synchronization. Mailbox Management Services should provide the facility to manage the mail store on the SAN. The actual mailboxes would reside on the SAN. Since the availability of this mailbox management service is critical, this server should be clustered for high availability. Any downtime of this server would affect all the users, and the communication would come to a stall. Following features are required:

• Cross platform support for Mailing Services (including synchronization of emails, contacts, tasks, calendar etc. on all platforms) by all OEMs and for this purpose


GHMC Page 39

bidder can give third party solution to support mailing services on cross platform with technical support, update, upgrade facility for five years.

• There should be a provision for centralized updates and upgrades from a Server instead of everyone having to access internet for this purpose.

• There should be a reasonable level of backend support for the System Integrator to handle problems, if any.

• Reports on usage of mail service etc. 7.11 SMS Services GHMC has identified a need to be able send an SMS to mobile phones of citizens/elected representatives/ employees/vendors etc., reminding them about dues/ tax/ salary/ alerts/reminders etc. Thus the system should have the facility to send SMSs wherever required and also integrate with existing SMS gateway to provide the above mentioned services. The bidder will also be responsible for the co-ordination with existing service provider. The payment for SMSs (as per actual) will be done by the GHMC directly to the existing service provider. 7.12 MIS Services The bidder would be responsible for development and Implementation of MIS solution for GHMC. The system should be able to generate reports as per the requirements of GHMC. The Solution should be able to Interface / Download / incorporate data from all application modules deployed by GHMC as listed in this RFP. The Solution should provide a user driven reporting tool capable of various multidimensional analysis across parameters, periods and dimensions. 7.13 Dash Board Services The bidder shall be responsible for incorporating the digital dashboards layer in the solution to enable the decision makers in GHMC to view information regarding various departments, projects or status of various service requests and non-conformance of defined timelines in the form of drill down dashboards. These should be available as information cubes with the information being presented in easy to understand charts and tables with drill down capabilities. The Dash Board should update dynamically by retrieving the data from various modules. 7.14 Proxy Services The Proxy services shall provide users the access mechanism to the intranet. The Proxy server web access shall provide web caching services for better performance and efficient utilization of intranet bandwidth. With proxy services the internet access should be controlled and monitored. 7.15 Antivirus & Anti-spam Services To keep the servers and application secure from the attack of virus, Trojans and spam an Antivirus and Anti-Spam service is required. A separate hardware server & software will be required for that. This may also help in scanning of emails coming in and going outside the GHMC network. Following features should be supported by the Anti-Virus solution

1. Should restrict e-mail bound Virus attacks in real time without compromising performance of the system.

2. Should be capable of providing multiple layers of defense


GHMC Page 40

3. Should be capable of installation on both the gateway as well as Mailing servers. 4. Inbound and outbound monitoring on all data transfer mechanisms and all e-mail

systems 5. Should be capable of detecting and cleaning virus infected attachments as well 6. Should support scanning for all common types of compressed file formats. 7. Should support online upgrade, where by most product upgrades and patches can be

performed without bringing messaging server off-line 8. Should use multiple scan engines during the scanning process 9. Should support in-memory scanning so as to minimize Disk IO 10. Should support Multi-threaded scanning. 11. Should support scanning of a single mailbox or a one off scan 12. Should support scanning by file type for attachments 13. Should support scanning of nested compressed files

7.16 Handholding Support The System Integrator will provide two qualified and trained persons per circle / head office for a period of 6 months, to handhold the staff in the GHMC offices and ensure that the staffs in these offices are able to use application on their own by the end of the handholding period. Handholding support would be required only after the successful commissioning of application and infrastructure in respective Offices. SI is expected to provide manuals and CD’s for handholding support. 7.17 Project Planning and Management This project is a geographically spread initiative involving multiple stakeholders. Its implementation is complex and though its ultimate success depends on all the stakeholders; the role of SI is key and hence SI is required to design and implement a comprehensive and effective project management methodology together with efficient & reliable tools. The SI will also be required to procure commission and maintain Project Management, Configuration management and Issue tracker tools at the GHMC Headquarters during the course of project implementation. The requirements are listed below:

a) Project Management Tool: The SI shall keep the project plan and all related artifacts up-to-date during the course of the project. In order to help with the project management, the SI shall use a suitable standard, proven off-the-shelf project management tool (preferably with unrestricted redistribution licenses). The SI shall install the project management software at GHMC premises right at the beginning of the project. The tool shall provide the dashboard view of the progress on project milestones by the Nodal Officer and other Supervisory Officers of GHMC.

b) Configuration Management Tool: The SI shall keep all project documents up-to date during the course of the project. In order to help with the version/configuration management for all documents (including source code and all other project artifacts), the SI shall use a suitable standard, proven off-the-shelf configuration management tool (preferably with unrestricted redistribution licenses). The SI shall install the configuration management software at GHMC premises right at the beginning of the project.

c) Issue Tracker: The SI shall employ a suitable and proven tool for tracking issues (preferably with unrestricted redistribution licenses) through the execution of the project. The SI shall install the Issue Tracking System at GHMC premises to enable users of GHMC to access and use the same.

The SI shall address at the minimum the following using PMIS:


GHMC Page 41

• Create an organized set of activities for the project • Establish and measure resource assignments and responsibilities • Construct a project plan schedule including milestones • Measure project deadlines, budget figures, and performance objectives • Communicate the project plan to stakeholders with meaningful reports • Provide facility for detecting problems and inconsistencies in the plan • During the project implementation the SI shall report to the Additional

Commissioner (IT), on following items: • Results accomplished during the period • Cumulative deviations to date from schedule of progress on milestones

as specified in this RFP read with the agreed and finalized Project Plan • Corrective actions to be taken to return to planned schedule of progress • Proposed revision to planned schedule provided such revision is

necessitated by reasons beyond the control of the SI • Other issues and outstanding problems, and actions proposed to be

taken • Progress reports on a weekly/fortnightly basis • Interventions which the SI expects to be made by the AC(IT) and/or actions to be

taken by the AC(IT) before the next reporting period; • Project quality assurance reports • As part of the project management activities, the SI shall also undertake:

• Issue Management to identify and track the issues that need attention and resolution from the GHMC.

• Scope Management to manage the scope and changes through a formal management and approval process

• Risk Management to identify and manage the risks that can hinder the project progress

The Project plan prepared by the SI would be reviewed by the Governance Structure in the GHMC as shown in section 14 and approved by the Committee on the advice of the Project Management Consultants. The SI would update and maintain the Project Plan throughout the duration of the engagement. All changes are to be reviewed and approved by the GHMC Core Group. The SI shall procure and commission the required infrastructure (software, servers) for Project Management Tool, Configuration Management Tool and Issue Tracker tool and maintain the same through the duration of the project. These tools along with the servers on which they are deployed will become property of the GHMC and will be used by GHMC even beyond the contract period. The SI would setup an online repository on PMIS / Configuration Management Tool for providing centralized access to all project documents including manuals and other materials. The online repository would be maintained by the SI through the engagement period. The SI should ensure that the repository is built on appropriate security features such as role- and necessity-based access to documents. 7.18 Requirements Traceability Matrix The SI would ensure that developed solution is fully compliant with the requirements and specifications provided in the RFP such as functional, non-functional and technical requirements. For ensuring this, the SI shall prepare a Requirements Traceability Matrix on the basis of Functional Requirements Specifications (FRS), Non Functional Requirements


GHMC Page 42

Specification, and Technical Requirements provided by GHMC (updated, expanded and fine-tuned by the SI as necessary) and the System Requirements Specifications (SRS) prepared by the SI. This matrix would keep track of the requirements and trace their compliance through different stages of the project including software design, coding, unit testing and acceptance testing. The Requirements Traceability Matrix would be a live document throughout the project, with the SI team updating the matrix at every stage to reflect the meeting of each specification at every stage. Through the duration of the project, the PMC will periodically review the Traceability Matrix. Governance Structure, GHMC would provide the final approval on the advice of the PMC once they are satisfied that all requirements are met. 7.19 Project Documentation The SI shall create and maintain all project documents that would be passed on to GHMC as Project documents as per the agreed project timelines. The documents created by the SI will be reviewed and approved by the GHMC. GHMC will provide required approvals for the Project documents submitted by the system Integrator Project documents include but are not limited to the following:

• Detailed Project Plan • Updated/vetted FRS • SRS document • HLD documents (including but not limited to):

o Application architecture documents o ER diagrams and other data modeling documents o Logical and physical database design o Data dictionary and data definitions o Application component design including component deployment views,

control flows, etc. • LLD documents (including but not limited to):

o Application flows and logic including pseudo code o GUI design (screen design, navigation, etc.)

• All Test Plans • Requirements Traceability Matrix • Change Management and Capacity Building Plans • SLA and Performance Monitoring Plan • Training and Knowledge Transfer Plans • Issue Logs

The SI shall submit project documents that they would submit based on the methodology they propose. The SI shall prepare the formats/templates for each of the documents upfront based upon industry standards and the same will be approved by GHMC prior to its use for documentation. All project documents are to be kept up-to-date during the course of the project. The SI shall maintain a log of the internal review of all the deliverables submitted. The logs shall be submitted to Nodal Officer on monthly basis. All project documentation shall conform to the highest standards of software engineering documentation. 7.20 Post Implementation Support


GHMC Page 43

As part of the post implementation services, the SI shall provide support for the software, hardware, and other infrastructure provided as part of this RFP. SI shall provide Five(5) years of comprehensive AMC that includes:

• Warranty support • Annual Technical Support (ATS) • Handholding Services

o Operations and maintenance services for the server and related infrastructure supplied and commissioned by the SI for the application at the Data Center and Disaster Recovery Center.

o Central Helpdesk. o Software maintenance and support services. o Application functional support services

7.20.1 Resource Requirement The services shall be rendered onsite from the GHMC premises. To provide the support for all the offices of GHMC where the software, hardware, and other infrastructure will be rolled out, SI is expected to provide experienced and skilled personnel at each location. The SI will also ensure that there is a Service Center available or setup at GHMC. The SI shall develop a work plan for the knowledge sharing as per scope defined in this RFP for use in future phases of the project. The Minimum number of resources to be placed at GHMC for day to day operations for the entire project duration is Sl.No Designation and Location No. of

Resources 1. Project Manager at GHMC Head quarter 1 2. System Administrator 2 3. Information Security Expert at GHMC Head quarter 1 4. IT infrastructure Specialist at GHMC Head quarter 1 5. Operations Manager(Techno Functional) at GHMC Head quarter 1 6. Database Administrator at GHMC Head quarter 2 7. GIS Specialist 1 8. Network Administrator at GHMC Head quarter 1 9. Hardware and Networking expert at GHMC headquarter (two) & one

at each zone of GHMC 7

10. Solution expert for application support at GHMC headquarter (two) & one at each zone of GHMC

7

7.20.2 Warranty services As part of the warranty services SI shall provide:

a. SI shall provide a comprehensive warranty and on-site free service warranty for 5 years from the date of Go Live.

b. SI shall obtain the five year product warranty and five year onsite free service warranty on all licensed software, computer hardware and peripherals, networking equipment and other equipment.

c. SI shall provide the comprehensive manufacturer's warranty in respect of proper design, quality and workmanship of all hardware, equipment, accessories etc. covered by the RFP. SI must warrant all hardware, equipment, accessories, spare parts, software etc. procured and implemented as per this RFP against any manufacturing defects during the warranty period.


GHMC Page 44

d. SI shall provide the performance warranty in respect of performance of the installed hardware and software to meet the performance requirements and service levels in the RFP.

e. SI is responsible for sizing and procuring the necessary hardware and software licenses as per the performance requirements provided in the RFP. During the warranty period SI shall replace or augment or procure higher-level new equipment or additional licenses at no additional cost to the GHMC in case the procured hardware or software is not adequate to meet the service levels.

f. Mean Time Between Failures (MTBF) - If during contract period, any equipment has a hardware failure on four or more occasions in a period of less than three months or six times in a period of less than twelve months, it shall be replaced by equivalent or higher-level new equipment by the SI at no cost to GHMC. However, if the new equipment supplied is priced lower than the price at which the original item was supplied, the differential cost should be refunded to GHMC for any delay in making available the replacement and repaired equipment for inspection, delivery of equipment or for commissioning of the systems or for acceptance tests / checks on per site basis, GHMC reserves the right to charge a penalty.

g. During the warranty period SI shall maintain the systems and repair / replace at the installed site, at no charge to GHMC, all defective components that are brought to the SI's notice.

h. The SI shall as far as possible repair the equipment at site. i. In case any hard disk drive of any server, SAN, or client machine is replaced during

warranty / AMC the unserviceable HDD will be property of GHMC and will not be returned to SI.

j. Warranty should not become void, if GHMC buys, any other supplemental hardware from a third party and installs it within these machines under intimation to the SI. However, the warranty will not apply to such supplemental hardware items installed.

k. The SI shall carry out Preventive Maintenance (PM), including cleaning of interior and exterior, of all hardware and testing for virus, if any, and should maintain proper records at each site for such PM. Failure to carry out such PM will be a breach of warranty and the warranty period will be extended by the period of delay in PM.

l. SI shall monitor warranties to check adherence to preventive and repair maintenance terms and conditions.

m. The SI shall ensure that the warranty complies with the agreed Technical Standards, Security Requirements, Operating Procedures, and Recovery Procedures.

n. SI shall have to stock and provide adequate onsite and offsite spare parts and spare component to ensure that the uptime commitment as per SLA is met.

o. Any component that is reported to be down on a given date should be either fully repaired or replaced by temporary substitute (of equivalent configuration) within the time frame indicated in the Service Level Agreement (SLA).

p. The SI shall develop and maintain an inventory database to include the registered hardware warranties.

7.20.3 ATS services As part of the ATS services SI shall provide:

a. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements and maintenance.

b. If the Operating System or additional copies of Operating System are required to be installed / reinstalled / de-installed, the same should be done as part of ATS.

c. SI should carry out any requisite adjustments / changes in the configuration for implementing different versions of Application Software.

d. Updates/Upgrades/New releases/New versions. The SI shall provide from time to time the Updates/Upgrades/New releases/New versions of the software and


GHMC Page 45

operating systems as required. The SI should provide free upgrades, updates & patches of the software and tools to GHMC as and when released by OEM.

e. SI shall provide patches to the licensed software including the software, operating system, databases and other applications.

f. The SI shall provide for software license management and control. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements, and maintenance.

g. SI shall provide complete manufacturer’s technical support for all the licensed software problems and/or questions, technical guidance, defect and non-defect related issues. SI shall provide a single-point-of-contact for software support and provide licensed software support including but not limited to problem tracking, problem source identification, problem impact (severity) determination, bypass and recovery support, problem resolution, and management reporting.

h. The manufacturer’s technical support shall at a minimum include online technical support and telephone support during the GHMC business hours (Business hours in GHMC all days (Mon-Sun)) with access for GHMC and SI to the manufacturer’s technical support staff to provide a maximum of 4 hour response turnaround time. There should not be any limits on the number of incidents reported to the manufacturer. GHMC shall have access to the online support and tools provided by the manufacturer. GHMC shall also have 24x7 accesses to a variety of technical resources including the manufacturer’s knowledge base with complete collections of technical articles.

7.20.4 Handholding services to provide Operations and maintenance support As part of the Handholding services to provide Operations and maintenance support for the server and related infrastructure supplied and commissioned by the SI for the application at the Data Center and Disaster Recovery Center SI shall provide:

• The scope of the services for overall IT infrastructure management as per ITIL framework shall include 365x24x7 on site Monitoring, Maintenance and Management of the server and related infrastructure supplied and commissioned by the SI for the application at the Data Center and Disaster Recovery Center

The SI shall provide the MIS reports for all the devices installed in the Data Center and Disaster Recovery Center in format and media as mutually agreed with the GHMC on a monthly basis. Whenever required by GHMC, SI should be able to provide additional reports in a pre-specified format. The indicative services as part of this support are as below:

• System Administration, Maintenance & Management Services • Application Monitoring Services • Network Management Services • Backend Services (Mail, messaging, etc.) • Storage Administration and Management Services • IT Security Administration Services and Services for ISO 27001 and ISO 20000

compliance • Backup and Restore Services

7.20.5 Handholding services to provide Centralized Helpdesk and Support As part of the Handholding services to provide Centralized Helpdesk and Support for end users at each location SI shall provide:


GHMC Page 46

• The help desk service that will serve as a single point of contact for all ICT related incidents and service requests. The service will provide a Single Point of Contact (SPOC) and also resolution of incidents. GHMC requires the SI to provide Help Desk services to track and route requests for service and to assist end users in answering questions and resolving problems related to the software application, network, Data Center, Disaster Recovery Center, Client side infrastructure, and operating systems at all locations. It becomes the central collection point for contact and control of the problem, change, and service management processes. This includes both incident management and service request management.

• SI shall provide a second level of support for application and technical support at all locations across the GHMC where the software, hardware, and other infrastructure will be rolled out.

• For all the services of GHMC within the scope of this RFP, SI shall provide the following integrated customer support and help.

o Establish 16X6 Help Desk facilities for reporting issues/ problems with the software, hardware and other infrastructure.

o SI shall maintain and support to all client side infrastructure including hardware, networking components, and other peripherals.

o SI shall provide maintenance of Hardware, including preventive, scheduled and predictive Hardware support, as well as repair and / or replacement activity after a problem has occurred.

o SI shall track and report observed Mean Time between Failures (MTBF) for Hardware.

o SI shall provide functional support on the application components to the end users.

o SI shall also provide system administration, maintenance and management services, LAN management services, and IT security administration services.

7.20.6 Handholding services to provide software maintenance and support services As part of the Handholding services to provide software maintenance and support services SI shall provide:

• The Software Maintenance and Support Services shall be provided for all software procured and implemented by the SI. The SI shall render both on-site and offsite maintenance and support services to the GHMC to all the designated locations. The Maintenance and Support Services will cover, all product upgrades, modifications, and enhancements.

• The SI will implement from time to time the Updates/Upgrades/New releases/New versions of the software and operating systems as required after necessary approvals from GHMC about the same.

• Tuning of application, databases, third party software’s and any other components provided as part of the solution to optimize the performance.

• The SI shall apply regular patches to the licensed software including the operating system and databases as released by the OEMs.

• Software Distribution. SI shall formulate a distribution plan prior to rollout and distribute/install the configured and tested software as per the plan.

• The SI shall provide for software license management and control. SI shall maintain data regarding entitlement for software upgrades, enhancements, refreshes, replacements, and maintenance. SI should perform periodic audits to measure license compliance against the number of valid End User software licenses consistent with the terms and conditions of site license agreements, volume purchase agreements, and other mutually agreed upon licensed software terms and


GHMC Page 47

conditions and report to GHMC on any exceptions to SI terms and conditions, to the extent such exceptions are discovered.

• The SI shall undertake regular preventive maintenance of the licensed software.

7.20.7 Handholding services to provide application functional support As part of the Handholding services to provide application functional support services SI shall provide:

• The Application Functional Support Services shall be provided for all software procured and implemented by the SI. The SI shall render both on-site maintenance and support services to GHMC from the development center in the GHMC

• SI shall incorporate technological changes, and provide enhancements as per the requests made by GHMC. SI shall perform minor changes, bug fixes, error resolutions and minor enhancements that are incidental to proper and complete working of the application.

• Routine functional changes that include user and access management, creating new report formats, and configuration of reports.

• SI shall provide user support in case of technical difficulties in use of the software, answering procedural questions, providing recovery and backup information, and any other requirement that may be incidental/ancillary to the complete usage of the application.

• The SI shall migrate all current functionality to the new / enhanced version at no additional cost to GHMC and any future upgrades, modifications or enhancements.

• The SI shall perform user ID and group management services. • The SI shall maintain access controls to protect and limit access to the authorized

end users of the GHMC. • The services shall include administrative support for user registration, creating and

maintaining user profiles, granting user access and authorization, providing ongoing user password support, announcing and providing networking services for users and providing administrative support for print, file, directory and e-mail servers.

7.20.8 Exit Management and Transition – Capacity Building at GHMC

• After the exit of the SI, GHMC shall take up the management of the Application. Therefore before the exit of the SI, GHMC must be strengthened and capacity must be developed for the GHMC to manage the application. The SI must plan the capacity building initiative to enable GHMC to manage the e-Governance application

• The SI shall create a detailed plan for Capacity Building (CB) required at GHMC to manage the application / IT infrastructure and a Transition Plan (implemented over a minimum period of three months) to affect the handover to GHMC; and implement the same in collaboration with the GHMC before the completion of their engagement.


GHMC Page 48

8. TECHNOLOGY REQUIREMENT FOR APPLICATION DEVELOPMENT The following section presents the future state desired by Greater Hyderabad Municipal Corporation (GHMC) with the implementation of the Holistic and Integrated Greater Hyderabad eGovernance solution. System Architecture The expected solution would be based on central and networked data processing architecture. The data processing would be carried out at State Data Center (SDC) with a set of servers to support the processing needs of the GHMC. The system shall be designed as to avoid the single point failure. This central location (SDC) would be connected to the various operational units (Circles / Zones / Head office) through APSWAN and different network components along with a disaster recovery site. 3-Tier/N-Tier Client Server Architecture: The 3-tier architecture will be employed for GHMC incorporating of three basic software components – front-end software, middleware and server software. The entire processing should take place in the following three layers:

a. Front-end software (client tier) shall be responsible for the presentation of information to GHMC user.

b. all business rules shall be defined in Middleware (application server tier) layer c. Server Software (database server tier) shall be responsible for the manipulation and

storage of data. Major Components of the solution architecture: The envisaged solution comprises of mainly four parts as described below:

• Client Layer: - Client layer would contain web browser for external as well as GHMC internal users. External user use internet to send request to access various services and GHMC internal users would connect via LAN/ Intranet or internet.

• Presentation Layer: - Web server and SMTP server would be hosted on the presentation layer.

• Application Layer: - Web portal shall be hosted at the application layer. Apart from web portal Payment gateway, Digital certification, Indexing and searching services shall hosted on the application layer.

• Database Layer: - All of the GHMC data shall reside on the Database layer. Apart from GHMC data User profile, content repository and Metadata shall also reside on the Database Layer.

The various components to be used in the proposed GHMC solution architecture are described below; Sr. No. Component / Service Description

1 Client Layer The Client layer of the GHMC portal would provide the internet/intranet browser that would initiate request to the GHMC web server and will display the results of requests.

2 Web Server GHMC web server would serve raw content or forward requests to the Portal Server

3 Case Management Services

The web server would deliver via the Http, both static web pages stored on the content manager and dynamically built web pages generated by the GHMC portal server.

4 Portal Server (Application Server)

Portal server would carry out the page aggregation, searching, indexing, integration to the various knowledge based managed


GHMC Page 49

Sr. No. Component / Service Description

backend system. This will provide an access to different stakeholders for day-to-day information.

5 User Authentication Services

These services will be used to register, authenticate and manage users and their security privileges. These services will authenticate the GHMC users and find out user specific privileges

6 GHMC User Profiles This will be the storage of the GHMC user’s authentication information and access capabilities.

7 Web Application Services

The Web Application Services would be a container to manage the presentation and application logic. It will provide transactional integrity, scalability and availability services. In addition it manages the session, the requests and responses to and from its clients and resources.

8 Application Logic This logic would encapsulate the business-level functions that can be used to satisfy a user’s requests.

9 Application Database Services

Services including Database Analysis and Design, Data Warehousing and Business Intelligence, Conversion.

10 Application Data Business specific data that the application would track or manage

11 Content Management Services

This would be a content Management Repository where different web pages, news, events, rules, regulations, schemes details, grant details, etc. safely reside with metadata contents.

12 Mailing & Messaging Server

This server would be used for sending the alerts as mail message to the registered users of the GHMC Portal.

13 Indexing and Searching

This tool would be used for indexing and searching all the repositories of knowledge repository maintained across the portal infrastructure.

The GHMC Portal will bring all of its services under one umbrella and provide a single point of access to the citizens, internal users and other intended users to avail the services. The proposed solution shall provide interfaces and formats for data transfer between external agencies and relevant stakeholders as per the requirements. The solution should support TCP/IP, HTTP and HTTPs for all traffic between the user screens and the application The bidder is expected to propose the solution and technology stack / platform that is based on the open standards, provide interoperability with other operating systems and application servers, guarantee portability of data and content and that best meets the specifications provided in the RFP. The solution should be based on shared and reusable architectures, that is, applications, systems and infrastructure are characterized as service oriented, component-based and reusable. The solution would be web based application and accessible over a standard browser. Application would be hosted centrally at APSDC and all the users will access the application over APSWAN or through Internet. The application tier would consist of two nodes clustered on a fail-over configuration. The database tier should also consist of two servers clustered to provide a highly scalable and available database solution for the proposed applications. Proposed solution should have adequate redundancies so as to have no single point of failure for the solution. On failure of the primary application server, the ‘fail-over’ server should take over processing. Similarly, on failure of a database server, the other active server should continue seamlessly, thus providing the desired availability. The solution landscape should be architected with following key drivers in mind:

• Based on Open Standards


GHMC Page 50

• High Availability • Scalability • Load Sharing • Performance Objectives • Optimization of Hardware • Usage Requirements • Integration Requirements • Maintainability • Platform Compatibility • Cost Implications

Standards The proposed GHMC system needs to be designed based on the latest DIT / GoAP standards, and in line with overall system requirement set out in this RFP, in order to have data standards, interoperability with multiple platforms and avoid any technology or technology provider lock-in. The list below is the minimum and is not to be treated as exhaustive. Portal development W3Cspecifications Information access/transfer protocols SOAP,HTTP/HTTPS Interoperability WebServices,Openstadards

Photograph JPEG(minimumresolutionof640x480 pixels) Scanned documents TIFF(Resolutionof600X 600dpi) Digital signature RSA standards Document encryption PKCS specifications Information Security ISO27001certified Operational integrity & security management ISO17799compliant IT Infrastructure management ITIL/EITM specifications Service Management ISO 20000 specifications

Project Documentation IEEE/ISO/CMMi (where applicable) specifications for documentation

Portal W3C standards Security: The security architecture proposed for the overall solution has to ensure complete confidentiality, authenticity and integrity of data and transactions. Access control procedures should cover all stages in the life-cycle of user access, from the initial registration of new users to the final de-registration of users who no longer require access to information systems and services. Special attention should be given, where appropriate, to the need to control the allocation of privileged access rights, which allow users to override system controls.

i. Security is the aspect of the service of providing confidentiality and non –repudiation by authenticating the parties involved, encrypting messages, and providing access control. The applications can have different approaches and levels of providing security, depending on the service requester.

ii. Security Process will include • Audit of Network, Server and Application security mechanisms


GHMC Page 51

• Assessment of authentication mechanism provided in the application/ components/modules

• Assessment of data encryption mechanism • Assessment of data access privileges, retention periods and archival

mechanisms • Final outcome of this process would be a comprehensive audit report

including all the Network, Server and Application security features incorporated in the GHMC Solution.

iii. The proposed solution shall follow the ISO 27001/BS 7799 standards. iv. User Access Management: Users should be granted access to information, data and

software on a "need to know" basis. Access should be restricted according to the user’s requirement to read, write, execute or delete information, data or software on the basis of least privilege to achieve the desired function.

General Requirements: Sl.No Description 1 The solution architecture should be platform and vendor independent. 2 The solution should facilitate centralized deployment of the application.

3 The solution should be interoperable in nature and design and development should be based on Service Oriented Architecture (SOA).

4 The solution is required to provide modularity (business function and process) that should support addition / removal of one more modules as and when required.

5 The solution architecture should allow infrastructure simplicity and Standardization.

6 The solution should result in low architectural diversity and should provide for multi-tiered architectures (at least 3-tiered with clear separation between the presentation logic, business logic, and data access logic).

7 The solution should provide application architectures that are highly granular and loosely coupled.

8 The solution should ensure data safety and integrity in the event of communication channels operation failures, software and hardware operability failures.

9 The solution should be designed to remove all single points of failure. The solution should provide the ability to recover from failures and should also provide clustering features, thus protecting against many multiple component failures

10

The solution should have the ability to scale up as and when the new business applications and services are added without compromising the performance of the overall solution. The architecture should be proven to be highly scalable and capable of delivering high performance as and when the transaction volumes increase

11 The solution should be designed in manner that operational data is not lost in case of any failure of equipment or communication network.

12 The solution should employ a common user access and authentication service to ensure Single-Sign on for the end-user.

13 The solution should support multi-tier authentication where ever and whenever required. 14 The solution should have a capability to assign activities to roles, and map roles to users.

15 The solution should restrict users from unauthorized access by allowing only the authorized users with valid profile/password to access only the allowed transaction

16

The solution should provide multi-level access management. The following should be provided:

• User identification; • Limitation of user rights to perform operations; • Data confidentiality provision;


GHMC Page 52

Sl.No Description • User actions audit and protocols;

17 The solution should support the following under user account management a. Unique user IDs b. Disabling of inactive user IDs

18 The solution should display an appropriate warning message upon user logon.

19 The solution should not store authentication credentials on client computers after a session terminates.

20 The framework should support plugging in of other authentication methods in the future. 21 The system should be developed to be deployed in a n-tier datacenter Architecture

22

The system should ensure high standards of security and access control through: a. Prevent cross-site scriptingb. Validate the incoming data / user requestc. Encode the incoming data / user requestd. Prevent SQL Injectione. Utilize parameterized queriesf. Sanitize the user-inputsg. Validate the data both at the client and serverh. Do not allow hard delete and perform only soft tagging the row for deletion

23 The solution must be capable of integration with a payment gateway for paid user services

24

The Solution should be capable of delivering the services through: a. Internet-based for providing services to citizen’s b. Intranet-based for employees of the Greater Hyderabad Municipal Corporation(GHMC) c. Extranet-based for external stakeholders such as and other government departments.

Technical Specifications for Solution Components The solution required for GHMC must be designed following open standards in order to provide for inter-operability with multiple platforms and avoid any technology or technology provider lock-in. The Solution architecture should be n-tiered and must include all necessary software components including but not limited to Web Servers, Application servers, Database and Operating system. The Solution architecture shall allow for future scalability and scope addition by way of defining new services. The bidder as part of their Technical Bid Response shall provide the detailed architecture and comprehensive Bill of Materials (stating the make & model for relevant component). The minimum specification requirements are as below: "The Software Platform Products’ and Versions proposed to be used in GHMC (Operating system of servers, DBMS, Database Server, Web server, application server or any other products proposed) should be the current released versions for that product, from the Software Manufacturer. The Products and Versions being offered for GHMC should have a well published and documented support roadmap – Mainstream support for at least 5 years from date of release. The Vendor should provide documentary proof to this effect, from the OEM for the core platform components of the solution " Application Server being critical component for overall solution the vendor should quote product that is listed in the Leader‘s quadrant in the latest Gartner for Enterprise Application Servers. The minimum required features for the core components are mentioned in the following tables


GHMC Page 53

Database: Sr. No Features

1 The database should address all the structured and un-structured data storage requirements of the proposed system

2 The RDBMS database should have a high tolerance of failure 3 The underlying database should support 24x7 high availability

4 The database should provide horizontal scalability, by adding additional servers for the same database without any downtime

5 The data scalability and manageability should be integral part functionality of the database.

6 The database should provide enterprise class web management tools for management and maintenance of databases even from remote places

7 The database should support native automated disaster recovery capability without any third party support with seamless switch over and switch back

8 between primary and disaster recovery sites

9 The database should be capable to support plug and play data transfer across platforms or operating systems

10 The database should be able to support various types of content like Texts, Images, Multi-media, Spatial and XML content natively

11

The database should ensure data synchronization between database servers on near real-time basis by capturing messages at the source database, stage messages in a queue, propagate messages from one queue at the source to another queue at the target and consuming messages

12 The database should support both way data synchronization across database servers in one-to-many and many-to-one situations and automatically detect data conflicts and resolve the same as per predefined conflict resolution algorithms

13 The database should support data synchronization across database servers in heterogeneous platforms

14 The database should be capable to deploy fine-grained access control, separation and segregation of duties and native encryption capabilities. The database should also prevent access to sensitive application data by highly privileged users.

15 The database should control access to the applications, databases and data with flexible security controls.

16 The solution should provide options or utility to encrypt/decrypt sensitive data

17 The solution should support data export and import facility to variety of databases and other software packages

18 The solution should provide backup (hot & cold) and recovery facility 19 The solution should be able to schedule a backup/restore task 20 The solution should be compatible with 3rd party system monitoring package. 21 The solution should support selective encryption of the stored data 22 The database should support a single unified data model hosted on a single database.

23 The database design & architecture should be in line with the functional and non-functional requirements of the proposed system

24 The database should be highly available with every processing node providing full view of data. This means, in case of failure of one server, each remaining server in the cluster should provide full access to all data at any point in time

25 It should support clustering exploiting rapidly emerging disk storage and interconnect technologies

26 Client-Server multi-tier support


GHMC Page 54

Sr. No Features

27 It should provide automated disaster recovery solution to maintain transaction consistency, providing an option of zero data loss where required

28 It should provide restrictive data access that enables different types of users to have secure, direct access to mission-critical data sharing

29 It should control data access down to the row-level (row-level security) so that multiple communities of users with varying access privileges can share data within the same database

30 It should provide encryption capabilities while transferring data over networks 31 It should possess ability to encrypt data stored in the database at the column level 32 It should provide Public Key Infrastructure (PKI) support 33 It should provide support for comprehensive auditing for ‘inserts’, ‘deletes’, 34 ‘updates’ and ‘selects’, and quickly spot and respond to security breaches 35 It should store XML content native to database

36 It should have the ability to index, search, and analyze text and documents stored in database

37 It should support different partitioning schemes to split large volumes of data into separate pieces or 'partitions' which can be managed independently.

38 It should provide to achieve the highest levels of scalability reliability, and uptime

39 It should be able to achieve database high availability using certified and supported high availability solutions

40 Should be able to meet Enterprise Scalability requirements to support future growth in users and data

41 Should be able to support Backup for hot backup and recovery at enterprise level and eliminate any risk of data loss.

42 Should be capable of Leveraging existing security infrastructures. 43 Should support database monitoring and administration

44 Should be capable of monitoring the health of databases and provide visibility into hot database activities

45 Should support partitioning to improve performance and simplify management of very large database environments

46 Should support Replication to improve scalability and performance of high-volume applications

47

Should have following features: • Support for distributed databases • Support for database replication • Support for web enabled applications • Support for data warehousing • Network support for a wide range of protocols • Portability of data through import/export procedures

Web Server

Sr. No. Description 1 The web server should be capable of supporting clustering.

2 All components of the web server should be based on standards and selected such as to provide ease of management and to avoid compatibility issues

3 All web server components must be maintainable with an ease such that corrective and preventive maintenance can be performed on the system without affecting the entire


GHMC Page 55

Sr. No. Description working of system.

4 All the web server components must be capable of being managed from a remote management station and provide information on performance parameters

5 Should support Single-Sign-On (SSO) 6 Should support user/role-based content management. 7 Should support Web Aggregation 8 Should support Fail-Over & Load Balancing features 9 Should support rules engine 10 Should have features like interoperability, secured transaction and reliability

11 Should have set of capabilities for discovering the existence, availability, health, performance, usage, as well as the control and configuration of a Web service within the Web services architecture

Application Server

Sr. No. Description

1 Application Server should be compliant to standards providing support for Web Services, SOAP, WSDL, UDDI, LDAP v3, SSL v3, XML 1.0 and equivalent standards

2 Provide comprehensive XML support compliant with the W3C XML standards and contain the basic building blocks to XML-enable applications - including reading, manipulating, transforming and viewing XML documents

3 Support developing, publishing and consuming web services 4 Support wireless enabled web sites and portals 5 The application server should be capable of supporting clustering.

6 All components of the application server should be based on standards and selected such as to provide ease of management and to avoid compatibility issues.

7 All application server components must be maintainable with an ease such that corrective and preventive maintenance can be performed on the system without affecting the entire working of system.

8 All the application server components must be capable of being managed from a remote management station and provide information on performance parameters


GHMC Page 56

9. IMPLEMENTATION AND ROLL-OUT PLAN SI shall prepare a detailed roll-out plan for each of the circles in the Phase and get the same approved by the GHMC. SI is also responsible for conducting workshops for the key officers GHMC for presenting the roll-out plan and gets the approval from the GHMC. The SI shall also provide the necessary assistance for the key officers of GHMC during the design and implementation of the project across all locations of GHMC. One of the important factors that would determine the success of the implementation in GHMC is the continuous availability of domain experts to the implementation team. SI shall put a domain expert with a minimum of 10 years of experience in the Municipal Department who will work on this project on a full time basis during the application development phase 9.1 List of Indicative Deliverables

1. Overall Project Plan 2. Application Development

a. Requirements Traceability Matrix b. Refined Functional Requirements Specification c. Systems Requirement Specification d. Design Document (High Level Design and Low Level Design) e. Test Plans f. Change / Reference Document documenting changes to the base version

3. Network Connectivity a. Network Architecture b. Network diagrams (LAN and WAN) for Zones / Circles/ other offices / HQ to

DC / DRC c. Network diagrams for connectivity between State DC / DRC and GHMC

locations 4. Data Migration Strategy and Methodology including Detailed Data Migration Plan 5. Change Management and Capacity Building

a. Overall Change Management Plan b. Content for Change Management including Awareness and Communications

Program c. Overall Capacity Building Plan and circle wise Training Schedule and

Curriculum d. Training Material

6. Circle-wise Roll-out / Implementation Plans

9.2 Implementation Plan The overall scope of the System Integrator would be to implement project through “Bundle of Services” which would be implemented in 9 months as detailed out in the table below

S.No Deliverables Completion Milestone

1. Award of Contract & Team Mobilization T0 (15 days from issue of LOI)

2. Systems Requirements Specification (SRS) and To-Be Documentation T0 + 6 weeks

3. High Level Design (HLD), Low Level Design (LLD) and Software Design Documents (SDD) T0+10 weeks

4. Site Preparation To+12 weeks


GHMC Page 57

S.No Deliverables Completion Milestone

5. Supply, Installation and Acceptance Certification by GHMC (for Server Side H/W, S/W & Circles) T0 + 12 weeks

6. Training Need Analysis Report and Training Modules T0 + 12 weeks 7. User Acceptance Test Report T0 + 20 weeks 8. End-to-end project documentation and creation of manuals T0 + 20 weeks9. Installation of Software and Go-Live T0 + 24 weeks 10. 3rd Party Certificate T0 + 28 weeks 11. Parallel Run and Data Migration Report T0 + 30 weeks 12. Successful Live Run (Implementation in 18 circles and SDC) T0 + 36 weeks 13. Implementation Completion Certificate by GHMC T0 + 40 weeks =T1

14. Annual Maintenance Contract (for 5 years after Implementation Completion Certificate by GHMC) T1 + 5 years

15. Man-month based supply of Programmer /System Analyst etc. T1 + 5 years 16. Other Reports 17. Results accomplished during the period Every 15 days 18. Cumulative deviations to date from schedule of progress on milestones Every 15 days

19. Corrective actions to be taken to return to planned schedule of progress

Every 15 days

20. Proposed revisions to planned schedule Every 15 days

21. Other issues and outstanding problems, and actions proposed to be taken

Every 15 days

9.3 Geographical Coverage The geographical coverage of the project comprises of all the offices under the GHMC (List of offices is attached in annexure –5. The roll out would include installation and commissioning of hardware, connectivity, other infrastructure and associated services (such as handholding). 9.4 Service Coverage The SI shall cover all the services mentioned in the scope of work in this RFP. 9.5 Outcomes

Activities Outcomes

Rollout in all locations of GHMC Implementation of Integrated IT Application of GHMC

Establishment of service levels pertaining to citizen services of GHMC

Accountability of services provided by the department

Digitization of historical data The historical data can be retrieved from the system through the Search feature

Integration with e-Seva / AP online Easy citizen service delivery Integration with External Interfaces (such as Hospitals, HMWSSB, APCPDCL, etc.) UID, SSDG

Seamless data transfer and enhanced service delivery


GHMC Page 58

10. SERVICE LEVELS This section describes the service levels to be established for the Services offered by the SI to the GHMC. The SI shall monitor and maintain the stated service levels to provide quality service to GHMC 10.1 Definitions

(a) “Scheduled Maintenance Time” shall mean the time that the System is not in service due to a scheduled activity as defined in this SLA. The scheduled maintenance time would not be during 16X6 timeframe. Further, scheduled maintenance time is planned downtime with the prior permission of GHMC.

(b) “Scheduled operation time” means the scheduled operating hours of the System for the month. All scheduled maintenance time on the system would be deducted from the total operation time for the month to give the scheduled operation time. The total operation time for the systems and applications within the Primary DC, DRC and critical client site infrastructure will be 24X7X365. The total operation time for the client site systems shall be 18 hours.

(c) “System or Application downtime” means accumulated time during which the System is totally inoperable within the Scheduled Operation Time but outside the scheduled maintenance time and measured from the time the GHMC and/or its employees log a call with the SI team of the failure or the failure is known to the SI from the availability measurement tools to the time when the System is returned to proper operation.

(d) “Availability” means the time for which the services and facilities are available for conducting operations on the system including application and associated infrastructure. Availability is defined as:

1. {(Scheduled Operation Time – System Downtime) / (Scheduled Operation Time)} * 100%

(e) “Helpdesk Support” shall mean the 16x6 basis support center which shall handle Fault reporting, Trouble Ticketing and related enquiries during this contract.

(f) “Incident” refers to any event / abnormalities in the functioning of the Data Centre Equipment / Services that may lead to disruption in normal operations of the Data Centre, System or Application services.

10.2 Interpretations

a. The business hours are 10.00 AM to 6.00 PM on all working days (Mon-Sat)

excluding Public Holidays or any other Holidays observed by the State of Andhra Pradesh. The SI however recognizes the fact that the offices will require to work beyond the business hours on need basis.

b. "Non-Business Hours" shall mean hours excluding “Business Hours”. c. If the operations at Primary DC are not switched to DRC within the stipulated

timeframe (Recovery Time Objective), it will be added to the system downtime. d. The availability for a cluster will be the average of availability computed across all the

servers in a cluster, rather than on individual servers. However, noncompliance with performance parameters for infrastructure and system / service degradation will be considered for downtime calculation.

e. The SLA parameters shall be monitored on a monthly basis as per the individual SLA parameter requirements. However, if the performance of the system/services is degraded significantly at any given point in time during the contract and if the immediate measures are not implemented and issues are not rectified to the complete satisfaction of the GHMC or an agency designated by them, then the


GHMC Page 59

GHMC will have the right to take appropriate disciplinary actions including termination of the contract.

f. A Service Level violation will occur if the SI fails to meet Minimum Service Levels, as measured on a half yearly basis, for a particular Service Level. Overall Availability and Performance Measurements will be on a monthly basis for the purpose of Service Level reporting. An “Availability and Performance Report” will be provided by the SI on monthly basis in the suggested format and a review shall be conducted based on this report. A monthly Availability and Performance Report shall be provided to GHMC at the end of every month containing the summary of all incidents reported and associated SI performance measurement for that period. The monthly Availability and Performance Report will be deemed to be accepted by the GHMC upon review and signoff by SI and the GHMC where required, some of the Service Levels will be assessed through audits or reports e.g. utilization reports, measurements reports, etc., as appropriate to be provided by the SI on a monthly basis, in the formats as required by the GHMC The tools to perform the audit will need to be provided by the SI. Audits will normally be done on regular basis or as required by the GHMC and will be performed by the GHMC or the GHMC appointed third party agencies.

g. EMS system as specified in this RFP shall play a critical role in monitoring the SLA compliance and hence will have to be customized accordingly. The 3rd party testing and audit of the system shall put sufficient emphasis on ensuring the capability of EMS system to capture SLA compliance correctly and as specified in this RFP. The selected System Integrator (SI) must deploy additional licenses of the existing SDC EMS modules tool and develop additional scripts (if required) for capturing the required data for SLA report generation in automated way. This tool should generate the SLA Monitoring report in the end of every month which is to be shared with the GHMC on a monthly basis. The tool should also be capable of generating SLA reports for a half-year. The GHMC will audit the tool and the scripts on a regular basis.

h. The Post Implementation SLAs will prevail from the start of the Operations and Maintenance Phase. However, SLAs will be subject to being redefined, to the extent necessitated by field experience at the GHMC offices and the developments of technology practices globally. The SLAs may be reviewed on an annual/bi-annual basis as the GHMC decides after taking the advice of the SI and other agencies. All the changes would be made by the GHMC in consultation with the SI.

i. The SI is expected to provide the following service levels. In case these service levels cannot be achieved at service levels defined in the tables below, it shall result in a breach of contract and invoke the penalty clause. Payments to the SI are linked to the compliance with the SLA metrics laid down in the tables below. The penalties will be computed and calculated as per the computation explained in this section. During the contract period, it is envisaged that there could be changes to the SLA, in terms of addition, alteration or deletion of certain parameters, based on mutual consent of both the parties i.e. the GHMC and SI.

Following tables outline the key service level requirements for the system, which needs be ensured by the SI during the operations and maintenance period. These requirements shall be strictly imposed and either the GHMC or a third party audit/certification agency shall be deployed for certifying the performance of the SI against the target performance metrics as outlined in the tables below.


GHMC Page 60

10.3 Implementation Phase SLAs 10.3.1 Delivery Related Service Level Agreement Criteria The deduction mentioned in this table shall be made from the next due payment to the vendor for services provided to GHMC

S.No Service metrics parameters

Baseline Low performance Violation of Service Level Agreement Basis of

measurement

Remarks Metric Metric Deducti

on Metric Deduction

1

Delivery of the reports / deliverables due for this session

As per the dates as mentioned in the contract

One week after the due date

Rs. 10,000

>1 week after the due date

Rs. 20,000 for every week of delay

Dates for delivery of reports as mentioned in the contract

2

Development, deployment and testing of application

7 months from the date of signing the contract

7-8 months

Rs. 100000 + No payment for the delayed period

More than 8 months

Rs.100000 per month delay

Months taken after beginning of the assignment Develop and test the application at the datacenter by the operator, not including the software audit by TPA

The centralized application should be tested for desired functionalities, security, and completeness as well as compliance with SLA, within the period

3

Supply, installation and commissioning of hardware at offices

3 months 3-4 months

For noncompliance at each point of deployment Rs. 30000

>4 months

For noncompliance at each point of deployment Rs. 45000

Months after taking over of the office site for project

The deduction shall be made per site basis. Where criterion is not satisfied

4

Supply, installation and commissioning of datacenter equipment

4 months from the date of signing of the contract

4-5 months

Rs.100000

More than 5 months

Rs. 100000 for every month of delay

Months taken after beginning of the assignment

GHMC may conduct independent audit to verify that the data centre is as per the specifications

5 Capacity building

At least 80 % of the training audience should give a rating of satisfactory or above

Less than 80 % and more than 60 % attendees find the training satisfactory

Rs. 15000/ training session

Less than 60 % of the attendees find the training satisfactory

Rs. 25,000/- per training session

Feedback survey to be provided to each attendee

The feedback of the attendees must be taken after every training session and this feedback should be leveraged for improving the feedback

6 Data Migration

Error rate in a batch during verification should

Error rate between 0.05 – 0.1 %

Rs. 5,000/- per batch and

Error rate of over 0.1 %

Rs. 10,0000 / per batch and the entire

Error rate in a batch during verification

Error rate is measured by percentage of the records with


GHMC Page 61

The deduction mentioned in this table shall be made from the next due payment to the vendor for services provided to GHMC

S.No Service metrics parameters

Baseline Low performance Violation of Service Level Agreement Basis of

measurement

Remarks Metric Metric Deducti

on Metric Deduction

be less than 0.05 %

correction of records

batch to be re-done

corrections marked by designated officials

7 Maintenance phase

All the issues reported regarding hardware, software, etc., should be resolved within 24 hours (less than 1 day)

Resolution of issues within 2 working days of reporting

Rs. 500

Resolution of the issue after 2 working days

Rs. 1000 for every day delay over and above beyond

Time and date of reporting of the issue

10.3.2 Violations and Associated Penalties The primary intent of Penalties is to ensure that the system performs in accordance with the defined service levels. Penalties are not meant to be punitive or, conversely, a vehicle for additional fees. Penalty Calculations - The framework for Penalties, as a result of not meeting the Service Level Targets is as follows:

1. Error rate in a batch during verification should be less than 0.5% as a baseline metric

and it is considered as lower performance if the error rate is between 0.5% to 1% and a violation of Service Level Agreement if it is above 1%.

2. The performance will be measured for each of the defined service level metric against the minimum / target service level requirements and the violations will be calculated accordingly.

3. The number of violations in the reporting period for each level of severity will be totaled and used for the calculation of Penalties.

4. Penalties applicable for each of the high severity violations are 0.1% of respective payment-period payment to the SI.

5. Penalties applicable for each of the medium severity violations are 0.05% of respective payment-period payment to the SI.

10.4 Post Implementation Phase SLAs 10.4.1 Primary DC/DR Infrastructure Systems, Application Availability & Performance a) Production Systems. - The failure or disruption has a direct impact on the GHMC’s

ability to service its other offices, ability to perform critical back-office functions or a direct impact on the organization. This includes but not limited to:

• Storage and related switches at Primary DC and DRC. • Web, Application, Database, and Backup Servers at Primary DC and

DRC.


GHMC Page 62

• Primary DC to DRC connectivity. • Primary DC and DRC network infrastructure. • Primary DC and DRC security infrastructure.

b) Non Production Systems (Development, QA, and Training): The failure or disruption

has no direct impact on the GHMC’s ability to serve its offices, or perform critical back-office functions. This includes but not limited to:

• Test, QA and Training Servers. • Helpdesk infrastructure & applications. • EMS Infrastructure.

c) GHMC Solution Components: The failure or disruption has a direct impact on the GHMC’s ability to service its offices, ability to perform critical back-office functions or a direct impact on the organization.

These service levels will be monitored on a monthly basis. The below tables gives details on the Service Levels the SI should maintain.

Particulars Measurement

Infrastructure Availability

Availability of production systems shall be at least 99%Severity of Violation: High

Availability over the six month period Violations for calculation of penalty

< 99% and >=98.5% 1 <98.5% and >=98% 2 <98% 3 In addition to the above, if the service level in any month in the six-month period falls below 98%, one (1) additional violation will be added for each such month to the overall violations for this service level.


Availability of nonproduction systems shall be at least 97% Severity of Violation: Medium


< 97% and >=96.5% 1 <96.5% and >=96% 2 <96% 3 In addition to the above, if the service level in any month in the six-month period falls below 96%, one (1) additional violation will be added for each such month to the overall violations for this service level.


• RTO shall be less than or equal to six (6) hours. • Severity of Violation: High • Each instance of non-meeting this service level will be treated

as one (1) violation.

Infrastructure Performance

• Sustained period of peak memory utilization of any server crossing 70% (with the exception of batch processing) shall be less than or equal to 30 minutes except during the 31st march of every year

• Severity of Violation: High • Each occurrence where the peak CPU utilization of any server crosses

70% (with the exception of batch processing) and stays above 70% for time more than 30 minutes will be treated as one (1) instance.

Number of instances over the six month period Violations for calculation of penalty

>0 and <=3 1 >3 2 • In addition to the above, if the number of instances in any month in the

six-month period exceeds 3, one (1) additional violation will be added for each such month to the overall violations for this service level.


GHMC Page 63

Particulars Measurement

Application Availability

• Availability of solution components measured within the Data Center shall be at least 99.9%

• Severity of Violation: High • The service shall be monitored on a monthly basis


<99.9% &>=99.5% 1 <99.5% &>99% 2 <99% 3 • In addition to the above, if the service level in any month in the six month

period falls below 99%, one (1) additional violation will be added for each such month to the overall violations for this service level.

Application Availability

• Availability of solution components measured within the Data Center shall be at least 97%

• Severity of Violation: Medium • The service shall be monitored on a monthly basis


<97% &>=96% 1 <96% 3 • In addition to the above, if the service level in any month in the six-month

period falls below 96%, one (1) additional violation will be added for each such month to the overall violations for this service level.

Application Performance

• Average application response time during peak usage hours as measured from a client terminal within the Data Center shall not exceed 4 seconds.

• Severity of Violation: High • The list of critical business functions and peak usage hours will be

identified by the GHMC during the Supply and System Integration Phase. • The service shall be monitored on a monthly basis

Average application response time over the six month period

Violations for calculation of penalty

> 4s &<= 5s 2 > 5s &<= 6s 4 > 6s 5 • In addition to the above, if the average turnaround time in any month in

the six-month period falls goes beyond 6s, one (1) additional violation will be added for each such month to the overall violations for this service level.

10.4.2 Client Site Infrastructure Systems (Critical Client Site Systems)

The failure or disruption results in inability of the GHMC to service its dependent offices or perform critical back-office functions. Critical client site infrastructure means the IT infrastructure at client site which are shared by multiple users i.e., Core Switch, Core Routers, etc. This service level will be measured on a monthly basis for each implementation site. The below tables gives details on the Service Levels the SI should maintain:

Service Level Description Measurement

Client Site Systems Availability

• Availability of the critical client site infrastructure components at all the implementation sites shall be at least 99% Severity of Violation: High

• This service level will be measured on a monthly basis for each implementation site.


GHMC Page 64

• If the availability in a month for an implementation site falls below the minimum service level, it will be treated as one (1) violation.

• The total number of violations for the six-month period will be the cumulative number of violations across all the months across all sites in the six-month period.

10.4.3 Handholding Support a. Client Site Support Level 1 Incidents - The incident has an immediate impact on the ability to service its offices, to perform critical back-office functions or has a direct impact on the organization. Level 2 Incidents - The incident has an impact on the GHMC’s ability to service its offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames. The severity of the individual incidents will be mutually determined by the GHMC and SI. The scheduled operation time for the client site systems shall be the business hours of the GHMC. This service level will be measured on a monthly basis for each implementation site. The tables on the following page give details of the Service Levels the SI is required to maintain:


Client Site Support Performance

• 80% of the Level 1 Incidents at each site should be resolved within 2 business hours from the time call is received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 8 business hours.

• Severity of Violation: Medium • This service level will be measured on a monthly basis for each

implementation site. • If the performance in a month for an implementation site falls below the

minimum service level, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months across all sites in the six-month period.

• Average number of instances per month = (Total number of instances for the six-month period) / 6

Average number of instances per month Violations for calculation of penalty > 0 &<= 4 1 > 4 &<= 8 2 > 8 &<= 12 3 >12 4


• 80% of the Level 2 Incidents at each site should be resolved within 6 business hours from the time call is received / logged whichever is earlier. The maximum resolution time for any incident of this nature shall not exceed 48 business hours.

• Severity of Violation: Medium • This service level will be measured on a monthly basis for each

implementation site. If the performance in a month for an implementation site falls below the minimum service level, it will be treated as one (1) instance. The total number of instances for the six-month period will be the cumulative number of instances across all the months across all sites in the six-month period.


GHMC Page 65


Average number of instances per month = (Total number of instances for the six-month period) / 6 Average number of instances per month Violations for calculation of penalty > 0 &<= 4 1 > 4 &<= 8 2 > 8 &<= 12 3 >12 4


Replacement of hardware equipment shall be done within 7days of notification by GHMC. These equipment’s would have failed on four or more occasions in a period of less than three months or six times in a period of less than twelve months. (Mean Time Between Failure Condition) Severity of Violation: High Each instance of non-meeting this service level will be treated as one (1) violation

b. Application Support

1. Level 1 Defects - The failure to fix has an immediate impact on the GHMC’s ability to service its offices, inability to perform critical back-office functions or a direct impact on the organization.

2. Level 2 Defects. The failure to fix has an impact on the GHMC’s ability to service its offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames.

3. Level 3 Defects. The failure to fix has no direct impact on the GHMC’s ability to serve its officers, or perform critical back-office functions.

The severity of the individual defects will be mutually determined by the GHMC and SI. This service level will be monitored on a monthly basis. The below tables gives details on the Service Levels the SI should maintain:


Application Support Performance

• 95% of the Level 1 defects shall be resolved within 4 businesshours from the time of reporting full details.

• Severity of Violation: High • This service level will be monitored on a monthly basis. Performance over the six month period


<95% &>=90% 1 <90% &>=85% 2 <85% 3 In addition to the above, if the service level in any month inthe six-month period falls below 85%, one (1) additionalviolation will be added for each such month to the overallviolations for this service level.

Application Support performance

• 95% of the Level 2 defects shall be resolved within 72 hours from the time of reporting full details.

• Severity of Violation: High • This service level will be monitored on a monthly basis. Performance over the six month period


<95% &>=90% 1 <90% &>=85% 2 <85% 3


GHMC Page 66

Service Level Description MeasurementIn addition to the above, if the service level in any month inthe six-month period falls below 85%, one (1) additionalviolation will be added for each such month to the overallviolations for this service level.


• 100% of the Level 3 defects shall be resolved within 120 hours from the time of reporting full details.

• Severity of Violation: High • This service level will be monitored on a monthly basis.

Performance over the six month period


<100% &>=90% 1 <90% &>=80% 2 <80% 3In addition to the above, if the service level in any month inthe six-month period falls below 80%, one (1) additionalviolation will be added for each such month to the overallviolations for this service level.


Up to date of the documentation of the design, modifications, enhancements, and defect-fixes in the half-yearly period. Severity of Violation: Medium This service level will be measured on a half-yearly basis.Each instance of non-meeting this service level will be treatedas one (1) violation.

c. Network Uptime Severity of violation: High This service level will be monitored on a monthly basis. The below tables gives details on the Service Levels the SI should maintain: Service Level Description Measurement

Network Uptime

• Availability of the network and all related components at allthe implementation sites shall be at least 99%

• Severity of Violation: High • This service level will be measured on a monthly basis for

each implementation site. • If the network availability in a month falls below the minimum

service level, it will be treated as one (1) violation. • The total number of violations for the six-month period will be

the cumulative number of violations across all the months across all sites in the six-month period.

d. Handholding Support: Helpdesk and Data Center Support

1. Level 1 Calls - The failure to fix has an immediate impact on the GHMC’s ability to service its offices, inability to perform critical back-office functions or a direct impact on the organization.

2. Level 2 Calls. The failure to fix has an impact on the GHMC’s ability to service its offices that while not immediate, can cause service to degrade if not resolved within reasonable time frames.

3. Level 3 Calls. The failure to fix has no direct impact on the GHMC’s ability to serve its offices, or perform critical back-office functions.


GHMC Page 67

This service level will be monitored on a monthly basis. The below tables gives details on the Service Levels the SI should maintain.


Helpdesk Performance

98% of the calls shall be answered within 45 seconds.Severity of Violation: High This service level will be monitored on a monthly basisPerformance over the six month period Violations for calculation of penalty <98% &>=90% 1 <90% &>=80% 2 <80% 3 In addition to the above, if the service level in any month inthe six-month period falls below 80%, one (1) additionalviolation will be added for each such month to the overallviolations for this service level.


• 98% of the incidents within helpdesk resolution capacity shall be resolved in a cycle time of 24 hours.

• Severity of Violation: High • This service level will be monitored on a monthly basis. Performance over the six month period Violations for calculation of penalty <98% &>=90% 1 <90% &>=80% 2 <80% 3 In addition to the above, if the service level in any month inthe six-month period falls below 80%, one (1) additionalviolation will be added for each such month to the overallviolations for this service level.


• 98% of the non SI supported incidents shall be routed to the appropriate service provider within 30 minute

• Severity of Violation: Medium • This service level will be monitored on a monthly basis.

Performance over the six month period Violations for calculation of penalty <98% &>=90% 1 <90% &>=80% 2 <80% 3 In addition to the above, if the service level in any month inthe six-month period falls below 80%, one (1) additionalviolation will be added for each such month to the overallviolations for this service level.


• 80% of the Level 1 calls shall be resolved within 2 hours fromcall received / logged whichever is earlier. The maximumresolution time for any incident of this nature shall not exceed8 business hours.

• Severity of Violation: High • This service level will be monitored on a monthly basis. Performance over the six month period Violations for calculation of penalty <80% &>=70% 1 <70% &>=60% 2 <60% 3


GHMC Page 68


In addition to the above, if the service level in any month inthe six-month period falls below 60%, one (1) additionalviolation will be added for each such month to the overallviolations for this service level.


• 80% of the Level 2 calls shall be resolved within 6 hours fromcall received / logged whichever is earlier. The maximumresolution time for any incident of this nature shall not exceed48 hours.


Performance over the six month period Violations for calculation of penalty



• 80% of the Level 3 calls shall be reported on status and actionto be communicated within 24 hours from call received /logged whichever is earlier. The maximum resolution time forany incident of this nature shall not exceed 72 hours.


Performance over the six month period Violations for calculation of penalty


Datacenter Support Performance

• Replacement of hardware equipment shall be done within 15days of notification by the GHMC. These equipment’s wouldhave failed on four or more occasions in a period of less thanthree months or six times in a period of less than twelvemonths. (Mean Time Between Failure Condition)

• Severity of Violation: High • Each instance of non-meeting this service level will be treated

as one (1) violation.

Datacenter Support Performance

• Up to date of the documentation of the design, modifications, enhancements, and fixes.

• Severity of Violation: Medium • This service level will be measured on a half-yearly basis.

Each instance of non-meeting this service level will be treatedas one (1) violation.

e. Reporting The below tables gives details on the Service Levels the SI should maintain:


GHMC Page 69


Availability and Performance Report

• Provide monthly SLA compliance reports, monitoring andmaintenance related MIS reports by the 5th of the followingmonth.

• Severity of Violation: Medium • This service level will be monitored on a monthly basis.

If the monthly SLA compliance report related to the servicelevel metrics is not provided in the given timeframe, it will betreated as one (1) instance.

• The total number of instances for the six-month period will bethe cumulative number of instances across all the months inthe six-month period.

Total number of instances over the six month period


>0 &<=3 1 >3 2

f. Credits for Successful Application Uptake

The below tables give details of the credits that can be gained by the SI for successful uptake of the application in GHMC. The credits will not be calculated for the first reporting period. Application Uptake Measurement

Application Uptake

The following metrics will be measured at the end of eachreporting period for each location that has been declared as“Go Live”: 1. Number of key transactions carried through internet (ex: Transactional

such as submitting an application for a no-objection certificate and Informational such a requesting the status of a case)

2. Number of active users profiles 3. Number of read-write transactions on GHMC system 4. Number of Searches carried out on data 5. Quality (regency and accuracy) of information available 6. Number of ad-hoc requests successfully responded to using

Application 7. Turnaround Time for submitting the monthly and annual reports 8. A credit will be gained for each of the above parameters if the

uptake for that parameter shows significant improvement 9. The following table applies for each of the above parameters:

% increase over the measurement in the last reporting period Credits provided

>5 &<=10% 2 >10 &<=15% 3 >15% 4

g. Violations and Associated Penalties

a) The primary intent of penalties is to ensure that the system performs in accordance

with the defined service levels. Penalties are not meant to be punitive or, conversely, a vehicle for additional fees.

b) A six monthly performance evaluation will be conducted using the six monthly reporting periods of that period.

c) Penalty calculations. The frameworks for penalties, as a result of not meeting the Service Level Targets are as follows:


GHMC Page 70

i. The performance will be measured for each of the defined service level metric against the minimum / target service level requirements and the violations will be calculated accordingly.

ii. The number of violations in the reporting period for each level of severity will be totaled and used for the calculation of penalties. a. If the total number of credits gained by the SI is lower than the total number of

high severity violations in the reporting period, the total number of credits will be subtracted from the total number of High Severity Violations in the reporting period for the calculation of Penalties.

b. If the total number of credits gained by the SI is higher than the total number of high severity violations in the reporting period, the resultant total number of high severity violations in the reporting period for calculation of penalties will be considered as zero (0).

iii. Penalties applicable for each of the high severity violations are two (2) % of respective half yearly payment to the SI.

iv. Penalties applicable for each of the medium severity violations are one (1%) of respective half yearly payment to the SI.

v. Penalties applicable for each of the low severity violations is half percentage (0.5%) of respective half yearly payment to the SI.

vi. Penalties applicable for not meeting a high (H) critical performance target in two consecutive half years on same criteria shall result in additional deduction of 5% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such high critical activity

vii. Penalties applicable for not meeting a medium (M) critical performance target in two consecutive half yearly periods on same criteria shall result in additional deduction of 3% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such medium critical activity

viii. Penalties applicable for not meeting a low (L) critical performance target in two consecutive half yearly periods on same criteria shall result in additional deduction of 2% of the respective half yearly payment to the SI. Penalty shall be applicable separately for each such medium critical activity

ix. It is to be noted that if the overall penalty applicable for any of the review period during the currency of the contract exceeds 25% or if the overall penalty applicable for any of the successive half year periods during the currency of the contract is above 15%; then the GHMC shall have the right to terminate the contract.


GHMC Page 71

11. TECHNICAL SPECIFICATIONS (INDICATIVE)

Database / Application Server

Sr. No

Database / Application Server Technical Specification

1 Processor / CPU

Latest 64 bit Server populated with 2 No. of Quad-Core processor, minimum 2.0 GHz clock speed or equivalent / subsequently better .The CPU should be of latest generation at the time of bidding i.e. Vendor should offer the highest clock speed and cache supported on the offered model with latest supported/ compatible server chipset. The Server should be scalable to 4 processors

2 Architecture RISC / EPIC as per OEM architecture

3 Operating System

Should support Industry-led operating system platforms including Windows Server Enterprise 2008, Red Hat Enterprise Linux, UNIX and Virtualization software, Sun Solaris with media and complete documentation for the system to be provided. Should be certified on the supplied OS Version.

4 Main Memory The system should be configured with minimum 128 GB RAM (ECC), scalable up-to 512 GB (ECC). Vendor should quote fastest available memory speed with the server being quoted.

5 Hard Disk 4X300 GB SAS 15K RPM SAS or better hot plug drives with RAID 1 with Disk Mirroring Features. Server Should have at least 2 HDD bays for future scalability.

6 Industry Benchmark

Should have published benchmarks for TPC-c or SAP or SPEC available. If no published benchmark result for the offered server & processor is available then the performance offered by the server will be estimated by linear extrapolation of a published result on a higher server model or a lower server model (with the same processor). If the OEM does not have particular benchmark on a specified server, the OEM can use an Internal benchmark to build the correlation between a benchmark and the proposed Server. The same has to be given in the OEM's letterhead and signed by an authorized person

7 Clustering Server should be configured to support for OS level clustering.

8 Network Interface Dual port 10/100/1000 Mbps Ethernet Adapter, with no single point of failure

9 HBA 2 No. dual ported 4 Gbps Fiber Channel Adapter with external fiber ports for redundant connectivity to external storage.

10 Removable drive One DVD-RW/CD-RW Combo drive per server. 11 Power Supply Dual Redundant Power Supply with cooling fans 12 All Items are to be Rack Mounted in Industry 13 Server Height Standard 4U (Rack mount) 14 Hot Swap components Hard Disk Drives, Drives, Power supplies and fans. 15 RAID Integrated RAID-0, 1

16 Server Management Firmware Update, Dynamic resource management & utilization capability, Real time System Monitoring

17 Warranty 5 years On-Site Comprehensive warranty and Maintenance


GHMC Page 72

Web Server /GIS Server

Sr. No

Web Server / GIS Server Technical Specification

1 Processor / CPU

Latest 64 bit server populated with 2 No. of Quad-Core processor, minimum 2.0 GHz clock speed or equivalent / subsequently better .The CPU should be of latest generation at the time of bidding i.e. Vendor should offer the highest clock speed and cache supported on the offered model with latest supported/ compatible server chipset. The Server should be scalable up to 4 Processors.

Cache Memory X86/RISC / EPIC as per OEM architecture

2 Operating System

Should support Industry-led operating system platforms including Windows/ Linux / enterprise class UNIX, and Virtualization software, Sun Solaris with media and complete documentation for the system to be provided. Should be certified on the supplied OS Version.


4 Hard Disk 4X300 GB SAS 15K RPM SAS or better hot plug drives with RAID 1 with Disk Mirroring Features. Server should have at least 2 HDD bays for future scalability.


Should have published benchmarks for TPC-c or SAP or SPEC available. If no published benchmark result for the offered server & processor is available then the performance offered by the server will be estimated by linear extrapolation of a published result on a higher server model or a lower server model (with the same processor). If the OEM does not have particular benchmark on a specified server, the OEM can use an Internal benchmark to build the correlation between a benchmark and the proposed Server .The same has to be given in the OEM's letterhead and signed by an authorized person


7 Network Interface Dual port 10/100/1000 Mbps Ethernet Adapter, with no single point of failure


9 Removable drive One DVD-RW/CD-RW Combo drive per server. 10 Power Supply Dual Redundant Power Supply with cooling fans 11 All Items are to be Rack Mounted in Industry 12 Server Height Standard 4U (Rack mount)

13 Hot Swap Components

Hard Disk Drives, Solid State Drives, Power supplies and fans.

14 RAID: Integrated RAID-0, 1

15 Server Management Firmware Update, Dynamic resource management & utilization capability, Real time System Monitoring

16 Warranty 5 years On-Site Comprehensive warranty and Maintenance


GHMC Page 73

Mail & Messaging, DNS/ DHCP, Anti-Virus / Anti-Spam, Document Management & Directory Server

Sl.No Mail & Messaging, DNS/ DHCP, Anti-Virus / Anti-Spam, Document Management and

Directory ServerTechnical Specification

1 Processor / CPU

Latest 64 bit Server populated with 1 No. of quad -Core processor, minimum 2.0 GHz clock speed or equivalent / subsequently better .The CPU should be of latest generation at the time of bidding i.e. Vendor should offer the highest clock speed and cache supported on the offered model with latest supported/ compatible server chipset. The Server should be scalable to 2 Processors.

2 Architecture X86/RISC / EPIC as per OEM architecture

3 Operating System

Should support Industry-led operating system platforms including Windows/ Linux / enterprise class UNIX and Virtualization software, Sun Solaris with media and complete documentation for the system to be provided. Server should be certified on the supplied OS Version.


5 Hard Disk 4X300 GB SAS 15K RPM SAS or better hot plug drives with RAID 1 with Disk Mirroring Features. Server Should have at least 2 HDD bays for future scalability.


Should have published benchmarks for TPC-c or SAP or SPEC available. If no published benchmark result for the offered server & processor is available then the performance offered by the server will be estimated by linear extrapolation of a published result on a higher server model or a lower server model (with the same processor). If the OEM does not have particular benchmark on a specified server, the OEM can use an Internal benchmark to build the correlation between a benchmark and the proposed Server .The same has to be given in the OEM's letterhead and signed by an authorized person


8 Network Interface

Dual port 10/100/1000 Mbps Ethernet Adapter, with no single point of failure


10 Removable drive

One DVD-RW/CD-RW Combo drive per server.

11 Power Supply Dual Redundant Power Supply with cooling fans 12 All Items are to be Rack Mounted in Industry 13 Server Height Standard 4U (Rack mount)

14 Hot Swap Components

Hard Disk Drives, Solid State Drives, Power supplies and fans.


16 Server Management

Firmware Update, Dynamic resource management & utilization capability, Real time System Monitoring

17 Warranty 5 years On-Site Comprehensive warranty and Maintenance Backup / Staging Server

Sl.No Backup / Staging Server Technical Specification

1 Processor / CPU

Latest Intel 7500 Chipset populated with at least one 2.4 GHz Quad -core processor with 16 MB cache per processor, expandable to 2 processor or equivalent / subsequently better .The CPU should be of latest generation at the time of bidding i.e. Vendor should offer the


GHMC Page 74

Sl.No Backup / Staging Server Technical Specification

highest clock speed and cache supported on the offered model with latest supported/ compatible server chipset.

2 Architecture X86/RISC / EPIC as per OEM architecture

3 Operating System

Should support Industry-led operating system platforms including Windows/ Linux/ Enterprise level UNIX, Virtualization software, Sun Solaris with media and complete documentation for the system to be provided. Server should be certified on the supplied OS Version.


5 Hard Disk 4X300 GB SAS 15K RPM SAS or better hot plug drives with RAID 1 with Disk Mirroring Features. Server should have at least 2 HDD bays for future scalability


7 Network Interface

Dual port 10/100/1000 Mbps Ethernet Adapter, with no single point of failure


9 Removable drive One DVD-RW/CD-RW Combo drive per server.

10 Power Supply Dual Redundant Power Supply with cooling fans 11 All Items are to be Rack Mounted in Industry 12 Server Height Standard 4U (Rack mount)

13 Hot Swap Components Hard Disk Drives, Solid State Drives, Power supplies and fans.


15 Server Management

Firmware Update, Dynamic resource management & utilization capability, Real time System Monitoring

17 Warranty 5 years On-Site Comprehensive warranty and Maintenance SAN Storage Sr. No

SAN Storage Technical Specification

1 RAID Level RAID Array supporting Raid Levels 0, 1, 0+1, 5, 10 or equivalent. The RAID Level should be Hardware based and should use dedicated Hardware for RAID Calculation.

2 Availability & Required Cache

Cache should be mirrored between Active-Active controllers on dedicated, redundant paths / links between the controllers. In case of power failure, the SAN array must be provided with cache protection mechanism to ensure no loss of data in cache by de- staging to disks, irrespective of duration of power outage, or for minimum 72 hrs. The Proposed SAN Array should be configured with at least 8GB usable data cache across dual RISC/ ASIC controllers with dual cache mirror interconnect paths.

3 Reliability

The Proposed SAN Array should be configured with No Single Point of Failure Architecture with Dual Controllers for redundancy and should support hot plug and hot swap of components online (including controllers, disks, power supplies, cooling fans etc.). Should have continuous system monitoring and shall support remote diagnostics / error reporting feature. It should also allow the recovery of data in transit in the event of failure.

4 Front End Connectivity

SAN Storage should be configured with at least 4 numbers of 4Gbps Fiber channel (FC) front end ports per controller (i.e. a total


GHMC Page 75

Sr. No

SAN Storage Technical Specification

of at least 8 x 4Gbps FC front end ports across Dual controllers) for front-end host connectivity.

5 Back End Connectivity

SAN Storage should be configured with at least 4 numbers of 4Gbps Fiber channel (FC) back end ports per controller (i.e. a total of at least 8 x 4Gbps FC back end ports across Dual controllers) for back-end disk-shelf connectivity.

6 Disk Drives

The SAN Array should be able to support a minimum of 95 disks in the array supplied from Day One and should be expandable to 200 disks in future with data in place upgrade. The SAN Array should support intermixing of FC & FATA/SATA‐II Disks of various capacities and speeds. It should support dual ported FC disks of 146GB, 300GB and 400GB or higher with speeds of 10K rpm & 15K rpm.

7 Required Disk space

The Proposed SAN Array should be configured with minimum 10TB Usable Capacity. Is required on RAID 10 (Strip and Mirror Everywhere) with 300GB, 15K RPM FC HDD (4Gbps, Dual Ported Drives) and with 1 hot spare per disk tray.

8 Self-Tuning The Storage System should provide ease of use capabilities – customer replaceable components, including non-disruptive replacement of disk drives, power supplies, fans and SFP optical transceivers.

9 Volume Expansion

The storage system should support dynamic online LUN/volume expansion and shrink through striping/ concatenation Or any equivalent means / feature, which can achieve similar functionality with supporting whitepaper validation documents from third party agencies

10 RAID Level Mixing

It should support a mix and match of RAID levels (including RAID 0, 1, 1/0, 5 ) within the same storage array serviced by a pair of controllers.If any of the above features are not supported by the bidder/OEM, then kindly propose equivalent features, with supporting whitepaper validation documents from third party agencies

11 No SPOF

Disk array should have no single point of failure (NSPOF) architecture, component and function level redundancy to provide high availability features. In addition it should support hot plug and hot swap of components online (including controllers, disks, power supplies, cooling fans etc.).

12 Volume Expansion

The SAN Management software should preferably be array- based, easy to use with secure web-based GUI administration interface for configuration, storage management.

13 Sparing Should have a pool of Global Hot Spare disks for the entire array, so that if a disk fails anywhere in the array, global hot spares can be invoked from the pool to reduce the risk of data loss.

14 OS support

Support for industry-leading Operating System platforms including but not limited to various flavors of LINUX, Microsoft Windows, UNIX (HP-UX, SUN Solaris, IBM-AIX) etc. As well as various High Availability cluster solutions. The detailed interoperability matrix should be available on the public domain.

15 IOPS I/O performance should be greater than or at least equal to 150,000 IOPS from Cache and should have a sustained sequential throughput of minimum 2000MB/sec.

16 Snapshots/ Full Copies

The array should provide for functionality for pointer based snapshot copies (which require a fraction of the space) as well as full physical copies. It should support Writeable space optimized snapshots. The Software for these copies should be licensed unlimited capacity.

17 Performance Monitoring

The storage should be provided with storage performance monitoring software. The performance monitoring software should provide graphical view of the through put, iops and other performance by host or by controllers

18 Advance functions

The storage should be provided with thin provisioning feature quality of service and SSD caching or tiering software should be provided


GHMC Page 76

SAN Switch

Sl.No SAN Switch

Technical Specification 1 Minimum 8 Active ports (each with minimum port speed 8Gbps) 2 Should have at least 4 numbers of 1Gbps ports for SAN extension over WAN 3 Should support FCIP protocol 4 All cable and accessories for connecting Servers /Devices to SAN 5 Should have capability of port trunking. 6 Should have optical transceivers for short wave and long wave 7 Should have dual Fans and Hot plug power supplies 8 Should have GUI based management software for administration and configuration

9 Should be possible to configure the switches with alerts based on threshold values for temperature, fan status and power supply status.

10 Should support zoning configuration, virtual SAN/ Virtual Fabric 11 Should support fabric routing to enable cross fabric connectivity 12 All other necessary fiber cables and racking accessory should be supplied

13 Should have inbuilt diagnostic features like Online Diagnostics, power on self-test, FC trace route and ping, FC Debug, Online Health System etc.

14 Should support RADIUS authentication or SSH Tape Library

Sr. No Tape Library

Technical Specifications

1 Offered Tape Library shall support Native data capacity of 6TB (uncompressed) expandable to 12 TB (compressed).

2 Tape Library shall provide web based remote monitoring capability. 3 The Tape Library unit shall be configured with latest FC / SAS LTO Gen5 Tape Drives.

4 Offered LTO5 drive in the Library shall conform to the Continuous and Data rate matching technique for higher reliability.

5 Offered LTO5 drive in the library shall offer optional WORM support and embedded AES 256 bit Encryption support.

6 Offered Library shall be provided with a hardware device like USB key, separate appliance etc. to keep all the encrypted keys in a redundant fashion.

7 Offered LTO5 drive shall have native speed of 120MB/sec and a compressed speed of 240 MB/sec for 2:1 compression.

8 Tape Library shall provide Fiber connectivity to SAN Environment.

9 For optimal Performance. Tape Library shall provide 8Gbps Native FC interface connectivity to SAN switches.

10 Tape Library shall be offered with minimum of 24 slots and barcode reader. 11 Tape library shall support removable magazine and mail slot.

KVM Switch

Sl.No KVM Switch 8 port & Console terminal with necessary cables


GHMC Page 77

Technical Specifications1 LEDs Bank and Active Port Display 2 Client/Host Connectors Keyboard: 6-pin Mini-DIN Female PS/2/USB 3 Mouse: 6-pin Mini-DIN Female PS/2/USB 4 Monitor: HDDB 15-pin Female VGA, SVGA, XGA, Multisync

5 Daisy-Chain connector Two 6-pin Mini-DIN + One 15-pin HDDB (Standard

KVM Cable minimum 12 feet) 6 Monitor Resolution Support: Up to 1920 x 1440 7 Display Data Channel: DDC1, DDC2B, DDC2AB 8 Keyboard State Saved and Restored 9 On Screen Display Yes; Password Protected10 PC Control Keyboard, Hot Key, Push Button 11 Switching Confirmation Buzzer 12 Daisy-Chain Level 8 13 Max. PC Control 64 14 Bandwidth 200MHz 15 Form Factor: Rack Mountable16 Dimension (LxWxH in): 16.14 x 6.5 x 1.85 17 Enclosure Material: Metal 18 Operating Temperature: 32°F ~ 104°F 19 Storage Temperature: 0°F ~140°F 20 Operating Humidity: 0% ~ 80 % RH non-condensing 21 Power Requirements: DC 12V, 1A22 Compliances: CE, FCC Class B, VCCI 23 Safety: UL 24 Warranty: 5 Years onsite warranty

Firewall with IPS

Sl.No Firewall with IPS Technical Specifications

1 Hardware Feature

The Firewalls should be Hardware based, Reliable, purpose-built security appliance with hardened operating system that eliminates the security risks associated with general-purpose operating systems with 6 No’s of 10/100/1000 Base Tx interfaces.The Appliance should be Full-featured, high-performance firewall, intrusion prevention system (IPS), and IP Security (IPSec) VPN technologies deliver robust application security, user- and application-based access control, worm and virus mitigation, and remote user/site connectivity. Should be redundant supporting Active/Active or Active/Standby Firewall for High Availability & Scalability Firewall Throughput of Up to 4Gbps Firewall + IPS services Throughput: Min. 2Gbps with real world HTTP Traffic VPN Throughput of Up to 800 Mbps Concurrent Sessions of at least 400,000IPSec VPN Peers of up to 2500 Virtual Interfaces (VLANs) support for at least 200 VLANs for forming Secure server Farms and DMZs Scalability through VPN clustering and load balancing

Software Features

2 Application Security Services

The Firewall should have Integrated specialized inspection engines for protocols like HTTP, FTP, ESMTP, DNS, SNMP, ICMP, SQL*Net, NFS, H.323 Versions 1-4, SIP, MGCP, RTSP, TAPI and JTAPI over CTIQBE protocol, GTP, LDAP, ILS, RPC etc.


GHMC Page 78


The Firewall should provide advanced inspection services to detect and optionally block instant messaging, peer-to-peer file sharing, and other applications tunneling through Web application ports Inspection of H.323, SIP based voice and multimedia streams that have been fragmented or segmented Support for foundational capabilities to assist in detecting protocol and application layer attacks To provide TCP stream reassembly and analysis services to help detect attacks that are spread across a series of packets

3 Intrusion Prevention Services

Advanced protection from known and unknown network and application layer attacks, DoS attacks, and malware, including worms/ network viruses. Analysis of network traffic accurately for these threats using a wide range of techniques, including stateful pattern recognition, protocol analysis, traffic anomaly detection, protocol anomaly detection, and Layer 2 analysis to detect man-in-the-middle attacks Specialized safeguards to prevent "detection evasion" attempts, including IP fragmentation reassembly and normalization, TCP stream reassembly and normalization, TCP evasion control, as well as IP anti-spoofing services Ensure malicious attacks are stopped without impacting legitimate traffic incorporating four elements (event severity, signature fidelity, asset value, and attack relevancy) to accurately determine the risk of an event, and then confidently performing administrator-specified mitigation action(s) Should support both "in-line" prevention of attacks. Should provide granular control over protocols, and provides custom regular expression matching tools for businesses to craft environment-specific signatures Should Incorporate a variety of technologies to defend from many popular forms of attacks, including DoS attacks, fragmented attacks, replay attacks, and malformed packet attacks Advanced attack protection features such as DNS Guard, Flood Guard, Frag Guard, Mail Guard, IP Verify, and TCP intercept to identify and stop a wide range of attacks Advanced TCP stream reassembly and traffic normalization services to assist in detecting hidden application and protocol layer attacks Should provide optional filtering of ActiveX and Java applets to prevent downloads of malware and the resulting damage malware can create.

4

Network Containment and Control Services

Inbound and outbound access control lists (ACLs) for interfaces, time-based ACLs, and per-user or -group policies for improved control over network and application usage Powerful reporting and troubleshooting capabilities that help enable collection of detailed statistics on which ACL entries are triggered by network traffic attempting to traverse a security appliance Grouping of network objects (such as devices, networks, and services) into logical groups to greatly simplify access control rule definition and maintenanceRich dynamic, static, and policy-based NAT and PAT services

5 Secure Connectivity Services

IPSec remote-access VPN services for up to hundreds of simultaneous remote software- or hardware-based VPN clients Should provide convenient method for authenticating VPN users through native integration with popular authentication services, including Microsoft Active Directory, Microsoft Windows Domains, LDAP, and RSA Secure ID. Support for Internet Key Exchange (IKE) and IPSec VPN standards


GHMC Page 79


with hub- and-spoke or meshed VPN configurations Ability to manually enroll into X.509 certificate authorities through support for Public Key Cryptography Standard (PKCS) #10 formatted certificate requests Support for DSA (Digital Signature Algorithm)-based X.509 certificates with key sizes ranging up to 1024 bits

6 High-Availability Services

Support for Active/Active & Active/Standby failover. Support for bidirectional state sharing between Active/Active failover pair members for support of advanced network environments with asymmetric routing topologies, allowing flows to enter through one Firewall appliance and exit through the other, if required Support for Synchronizing all security association state information and session key material between failover pair members Enable geographic separation of Security appliances in a failover pair by allowing failover information to be shared over a dedicated LAN connection between failover pair members Support to perform software maintenance release upgrades on the Firewall appliance failover pairs without affecting network uptime or connections

7 Intelligent Networking Services

Support for multiple virtual interfaces on a single physical interface through VLAN trunking and multiple VLAN trunks per appliance Comprehensive OSPF dynamic routing services. Improved network reliability through fast route convergence and secure, efficient route distribution. Secure routing solution in environments using NAT through tight integration with NAT services MD5-based OSPF authentication, in addition to plaintext OSPF authentication, to prevent route spoofing and various routing-based DoS attacks Route redistribution between OSPF processes, including OSPF, static, and connected routes. Load balancing across equal-cost multipath routes Secure integration in RIP based enterprise networks by learning routing updates for both versions 1 and 2 of the protocol. Protection against RIP-based reconnaissance activities and DoS attacks by supporting plaintext and keyed- MD5 authentication methods for RIPv2 Delivery of multimedia traffic in videoconferencing, collaborative computing, and mission-critical real-time enterprise applications through full PIM Sparse Mode Facilitate a wide range of multicast applications by including support for Internet Group Management Protocol (IGMPv2) and stub multicast routing, including NAT and PAT and the ability to build ACLs for multicast traffic Should deliver per-flow, policy-based QoS services, with support for LLQ and Traffic Policing for prioritizing latency-sensitive network traffic and limiting bandwidth usage of administrator-specified applications DHCP server services on one or more interfaces, allowing devices to obtain IPaddresses dynamically Capability to forward DHCP requests from internal devices to an administrator- specified DHCP server, helping enable centralized distribution, tracking, and maintenance of IP addresses Support for NTP to provide convenient method for synchronizing the clock on the firewall appliance with other devices on a network

8 Flexible Management

Support for Built-in Management Software for simple, secure remote management of the security appliances through integrated, Web-


GHMC Page 80

Sl.No Firewall with IPS Technical SpecificationsSolutions based GUI

Should provide a wide range of informative, real-time, and historical reports that give critical insight into usage trends, performance baselines, and security events Accessible through variety of methods, including console port, Telnet, and SSHv2 Strong authentication of users through the Firewall appliance through a local user database or through integration with enterprise databases, either directly using RADIUS and TACACS+ or indirectly with AAA Server

DMZ Switch

Sl.No DMZ Switch

Technical Specifications

1 Hardware Architecture

Multiple services (Data, voice, video)

Internal/ External Redundant Power Supply 1 x 24 Ports GE (10/100/1000Mbps) 1 x 2 Ports Gig Fiber High back plane speed minimum 48 Gbps Forwarding rate should be minimum 36 Mbps

2 L2 Features

Layer 2 switch ports and VLAN trunks IEEE 802.1Q VLAN encapsulation Support for at least 500 VLANs Dynamic Trunking Protocol (DTP) or equivalent VLAN Trunking Protocol or equivalent 802.1s 802.1w IGMP snooping v1 and v2

3 IP Routing Protocols

Static IP Routing OSPF RIP Hot Standby Routing Protocol/VRRP

L3 features ICMP support, IPv6 Support

4 Security

Standard and extended ACLs on all ports Dynamic Host Configuration Protocol (DHCP) snooping AAA and RADIUS authentication enable centralized control of the switch and restrict unauthorized users from altering the configuration. Secure Shell (SSH) Protocol and Simple Network Management Protocol Version 3 (SNMPv3) to provide network security by encrypting administrator traffic during Telnet and SNMP sessions.

5 Manageability & Up gradation

Switch needs to have console port / USB Console port for administration & management Must have support SNMP v1, v2, v3 Management using CLI, GUI using Web interface


GHMC Page 81

Sl.No DMZ Switch

Technical SpecificationsFTP/TFTP for upgrading the operating System TCP-MIB, UDP-MIB RFC1213-MIB (MIB-II), RFC1398-MIB (ETHERNET-MIB)

6 Standards

IEEE 802.1x support IEEE 802.3x full duplex on 10BASE-T and 100BASE-TX ports IEEE 802.1D Spanning-Tree Protocol IEEE 802.1p class-of-service (CoS) prioritization IEEE 802.1Q VLAN IEEE 802.3 10BASE-T specification IEEE 802.3u 100BASE-TX specification

7 Physical

19” Rack mountable All necessary power cords, adapters, data cables, connectors, CDs, manuals, brackets accessories, wire managers, etc. should be provided

Technical Specifications of HSM for PKI Security and Encryption Hardware Security module should be integrated with applications at Data Center in high availability mode and should be able to endure the security and integrity of the signing key, key management and multifactor authentication to access the key and most services significantly. It should be able to enhance the performance of the complete system by offloading the complete cryptography process to a dedicated appliance. Digital Certificates in addition to the HSM appliance may be used for further enhancing the security and integrity of the information.

Sl.No Functionality 1 Should support Windows,Linux,Solaris, 2 Should comply to standards like FIPS 140-2 Level-3, CC EAL4+,ROHS,FCC part 15 Class

B 3 Signing speed : 3000 S/S4 Remote PED Support for Authentication 5 Onboard key generation, Digital Signing & Verification process to be done inside the HSM

only for better performance and security 6 HSM should be integrated with the applications running inside the Data Center 7 Complete hardware based storage of key material for entire Life cycle

Laser Jet Printer Features Specifications1 Processor Min 300 Mhz 2 Print speed Up to 14 ppm A4 &letter 3 Resolution up to 600 x 600 dpi 4 Printing Features Manual duplex printing

Economic mode for toner savings 5 Memory 32 MB RAM 6

Paper Handling Tray 150-sheet adjustable main input tray, 100-sheet output bin, manual two-sided printing

7 Paper Size A4, A5,letter, legal, postcards, envelopes 8 Interfaces Hi-Speed USB 2.0 port, 9 operating systems

support Required Windows, Linux


GHMC Page 82

Desktop Computers Sl.No Item Description1 Micro- processor Intel Core i5-2400 (3.10 GHz, 6 MB L3 cache) or higher 2 Mother Board / Chipset Intel H61 or better on Intel/OEM Motherboard 3 Memory 4GB DDR3 RAM

4 Graphics 256 MB PCI Express NVIDIA GeForce 7300LE Turbo Cache or subsequently equivalent/better

5 Multimedia Integrated Audio and Graphic Controller 6 Bays 2 internal and 1 external or better 7 Hard Disk Drive 320 GB SATA HDD or subsequently equivalent/better 8 Monitor 18.5" Color TFT Monitor 9 Key Board 105 keys key board 10 Mouse Two Button Optic Scroll Mouse or better with Anti-static pad 11 Network Card 10/100/1000 Network card with WOL

12 Wireless Card

1 Integrated internal antenna, Standards- 802.11g, 802.11b Radio Data Rate : 1, 2, 5.5, 6, 9, 11, 12, 18, 24, 36,48, and 54 Mbps (Auto Rate Sensing), Frequency :2.4GHz to 2.5GHz CCK and OFDM Modulation

13 Power Management Power supply shall be surge protected and should be able to operate in Indian power condition.

14 Intelligent Manageability features

Remote System Management & Administration. Pre failure warning on Hard Disk Drive / memory.

15 Operating System Latest Preloaded Operating system 16 Office suite Preloaded office Automation productivity suite with media 17 Anti-virus Preloaded (licensed version of Antivirus with 5 years validity) 18 Patch Cord CAT 6 cord Laptop S No Features Specifications

1. Processor Intel i5/ AMD Phenom II Processor, 2. Motherboard Compatible motherboard to support the processor and memory.

Motherboard from the original OEM. 3. Memory 4 GB DDR3 4. Hard Drive 320 GB SATA 5. Removable drive Integrated DVD R/W 6. LAN Network Integrated 10/100 Mbps Ethernet Adapter (RJ-45) 7. Wireless Support Integrated 802.11 b+g 54 MBPS Wireless LAN adapter 8. Display 14.1" with Integrated WEB CAMERA (1.3 MP) 9. Battery Min 6 Cell Li Ion Battery 10. OS Certification Microsoft Windows, Linux 11. OS Pre-loaded 12. Operating System Latest Preloaded Operating system13. Office suite Preloaded office Automation productivity suite with media 14. Anti-virus Preloaded (licensed version of Antivirus with 5 years validity)

Connection Module/Information Outlet

Sl.No Functionality

1 RJ45 connection module of Category 6, for the establishing of transmission channels of class E with up to 4 plugged connections, complies with Category 6 requirements of the standards ISO/IEC 11801:2002, EN 50173-1: May 2007, DIN EN 50173-1: Dec. 2007 as


GHMC Page 83

Sl.No Functionality well as ANSI/TIA/EIA 568-B.2-1, de-embedded tested in acc. with IEC 60603-7-4, interoperable and backwards compatible with Cat.5e and Cat.5.

2 Suitable for 10GBase-T applications in acc. with IEEE 802.3an up to 500 MHz and 55 m.

3 Parallel pair termination without crossover in acc. with EIA/TIA 568-A/B, gold-plated bronze contacts for >1000 mating cycles, IDC contacts with single-wire strain relief and >20 insertion cycles, contact resistance <50 m Ohm, dielectric strength >1000 Veff..

4 Maximum reliability through special contact design without internal transfer points.

5 Should have integral dust cover and integrated bend-limiting strain -relief unit for cable entry.

6 Should have IDC to hold conductor without using any tool for termination of cable.

7 Outlets should be of single metal piece design without any PCB to support the IDC / Contacts.

8 Should be reusable and tool less in design in terms of termination of solid wire installation cable AWG22-24 as well as stranded cables AWG 22/7 – 26/7

9 Should be made of halogen free material and should be certified by third party like 3P or Delta or GHMT.

Specification of Layer 2 Switch

Features Specifications

No of Switch Ports 24

MAC Address Table Size 8K

Switch Fabric 32Gbps Forwarding Capacity

Transmission Method Store-and-Forward

Diagnostic LEDs Per Unit: Power

Per Port: Activity/Link, Speed

Packet Buffer Memory 340KBytes Buffer Memory per Device

QoS 802.1p (4 Queues)

Interface Options

RJ-45 10BASE-T, 100BASE-TX, AND 1000BASE-T

Network Protocols and Standards

IEEE 802.3 Ethernet, 802.3u Fast Ethernet, 802.3x Flow Control, 802.3ab Gigabit Ethernet, 802.1p QoS, 802.1w, 802.1D, 802.1as, 802.1x,

Electric Cabling

Detailed Specifications

Make and Model Offered(To be filled by bidder)

Total 5 Electrical Points Including 3 Switches&3 Sockets in Each Point, (2 No. 5-Amps and 1 No. 15 Amps.) - Point wiring using ISI approved PVC Conduit / Casing Capping, 1.1 KV grade 2.5 square meter FRLS Cu flexible wire including supply of wire, switch, socket and GI Box. Including all necessary hardware & accessories complete, material and labor as per requirement of the GHMC.


GHMC Page 84

Detailed Specifications For point wiring having Average Point length is12 to 18 Meters.

UPS Electrical Cabling for Network Rack, Four Computer Points, separate cabling for Two Printers from main input and Generator set to UPS Including change-over, MCB and all other accessories as per requirement. 10 KVA UPS Systems

Detailed Specifications Technical Specifications Make & Model Offered Manufacturer ISO 9001 & ISO 14001 Certified TECHNOLOGY

IGBT based PWM Technology Microprocessor Controlled Digital Design Double Conversion True On-line UPS

Overall Efficiency (AC-AC) ≥ 85% INPUT Voltage range 160-260 at 100 % Frequency range 47 to 53 Hz Phase Single Phase with ground Power Factor >0.9 or better OUTPUT Voltage 220VAC-230VAC Voltage regulation +/-2% (or better) Frequency regulation 50 Hz +/- 0.1% (free Run Mode) Harmonic Distortion (THD) < 3% (linear load) Waveform Pure Sine wave Crest Factor 3:1 Load power factor 0.8 lag Galvanic Isolation Provided through Inbuilt transformer Battery Backup 1 Hour

Battery Type Sealed Lead Maintenance Free VRLA type(Lead Calcium SMF batteries NOT acceptable)

DC Bus Voltage ≥ 120 V Transfer Time 0 ms Battery Enclosure Powder Coated Cabinets matching with color of UPS.

Battery Brands Reputed & Reliable brands like Exide, Panasonic, Rocket, Hitachi, Quanta, Luminous, CSB

General Operating Temp. 0 to 40 Degree C Audible Noise <55 dB at 1 mtr distance

Alarms & Indications All necessary alarms & indications essential for performance monitoring of UPS like mains fail, low battery & fault detection

Bypass Automatic, Manual Bypass Switch Compatibility UPS to be compatible with DG Set supply Communication Interface Standard RS 232 port for software interface


GHMC Page 85

Detailed Specifications Technical Specifications Optional SNMP interface support Certifications For Safety & EMC as per international standards

IP Based Communication Server

IP Communication Server for 1200 Users

System Architecture

a The Switching system of the EPABX should be designed with IP at the core allowing fully distributed IP solutions across data networks. It should support IP, TDM or a hybrid of IP/TDM technologies.

b IP Communication Devices should sup[port wired and wireless phones c Software up gradation patches should be provided till the contract period.

d Legacy TDM communication devices (Digital and analog 2 Wire telephone instruments with or without caller-id (Both FSK and DTMF), Fax, modems etc.)

e Hybrid trunks Analog CO, E&M circuits, digital trunks (PRI &BRI), IP trunks (H.323 & SIP).

f E&M AND LOOP DIAL TRUNKS The system should support dial Pulse / DTMF protocols for the extension side & LD/OD/2W, 4W E&M/MFC/MFR2/CEPT protocols on the CO side.

g

The system should be server based, scalable, distributable and modular and the operating system shall be hardened LINUX. The architecture should be capable of seamless migration to its maximum capacity by simply adding peripheral cards on the set of control server without compromising on any functions/features of this system or any degradation of service

h The system should support WII, DECT, Cellular systems (GSM/CDMA). i The system should support third party clients/phones like IP, SIP, TDM.

j The IP Phones should be directly registered on high end commercially off the shelf servers (call servers). IP phone should not get registered through any IP card.

k Software’s based facilities for controlling call flow for bandwidth management on the WAN side.

l The Call Server should able to handle traffic minimum 5000 users with a single server.

m The voice and signaling frames should be marked [tagged] in order to be recognized. The standards of marking supported will be: Level 2: IEEE 802.1p/Q and Level 3: TOS / Diff Serv.

n The system should support for voice encoding the standards like G.711, G.729A, G.723.1

o The system should support Call Switching Matrix

p The System must support Network Time Protocol to synchronize the system data/time of network devices.


GHMC Page 86

s

System should support VOIP solutions as an integral part of the system. It should not involve any external gateways, routers etc.

i. The system should be fully compliant to VOIP standards like H.323 and SIP (Session Initiation Protocol). Vendor to give clear compliance for the requested standards.

ii. The system should be able to operate with any SIP compliant device. If required it should be able to inter operate with H.323/ SIP standard based external gatekeepers.

iii. The Session Integration Protocol (SIP) proxy, SIP registrar should support any SIP compliant hard phones or soft phones. The SIP server (internal/ external) should be configured and ready to use.

iv. System should support the QOS features for the VOIP implementation. It should be compliant with QOS standards (Layer 2 – 802.1 p/q) and Layer 3- Diffserv / TOS).

t The system should support external fax to email server. The feature should be installed and ready to use for all the users. Web access to voice and fax messages should be available.

v The system should support IP4 presently and in future, the system should be upgradable to support IPV6. The necessary up gradation will be carried out immediately by the vendor after the necessary hardware/software is available with the OEM.

System Security MEDIA ENCRYPTION FEATURES

a PERIMETER SECURITY: For perimeter security, the system should have features like firewall and VPN technology.

b

The IP as well as VOIP traffic should be encrypted (signaling and voice packet ) with a 128 bit AES or stronger algorithm. Preferably the encryption algorithm should not reduce the processing capability of the server. However if reduction is there then capabilities of the processors for utilization of the feature should be clearly specified.

d The signaling from the gateway for TDM and IP traffic should also be encrypted. e The wireless equipment devices should support 802.11i or better security.

f The system must support syslog services for both internal and external command and configuration control accounting with a minimum of 5 days history

g The call server must be provided with adequate protection from possible virus, worm and Trojan infestation points such as internal E-mail servers. The passwords and access control must include at least the following

i Media Gateways should not host services such as proxy, FTP, Telnet or local dynamic routing to prevent exploitation in Distributed Denial of Service attacks.

j IP Phones should not support direct, external initiated, connections via HTTP, telnet, FTP, TFTP or any other protocol as means to prevent distributed Denial of Service attack exploitation.

k IP Phones must support 802.1x (EAP-MD5 or better) for authentication and access control to the network, this mechanism must allow the user to be connected to the call server once he has passed the authentication process; not before.

System Management

a The system must include a dedicated management server/platform that will be based on the latest technologies, such as JAVA/JEE. This server should support a minimum of five or more clients having different access rights to the applications.

b The management platform must provide a single graphical client (Graphical User Interface GUI)

c The Management platform must provide web access allowing the administrator to manage the system to use any PC.

d The management platform should support redundancy and perform the following tasks: (required hardware and software for performance of following tasks to be specify by vendor)


GHMC Page 87

i. Configuration and programming of services, users, categories and all system parameters and features. This module must provide centralized management in local or remote environments of a single system or a network. The network manager should be able to quickly and easily edit, create or delete any network object by the use of import/export functions and multiple operations.

ii. Faults and Alarms management of all the incidents and fail reports generated by the system itself informing date, hour, severity level and action recommended to take. This module must be able to centralize the alarms and events of the system, and give colors according the severity level of the alarm, Notify an alarm depending to the severity level sending an e-mail or activating an script performing an specific action, Register and generate statistics for the alarms and events in the network in a daily scheme etc.

iii. Fault diagnosis Generate reports and graphics about the statistics of the alarms and its corresponding resolution time.

iv. Call metering and Accounting The log of local to local call and local to trunk call should be maintained in the exchange in both directions i.e. incoming and outgoing in the hard disk .This log should be available for all the subscribers and the trunks ab-initio.The will help to trace the malicious call. Details of all calls generated by the users including , date, hour must be provided by the system . Must provide different options to group the monitoring of the calls (cost center, extension number, trunk, user, city/area associated to dialed numbers). EPABX system should have buffer of last 30 days call details in case of Call billing system/ management system failed.

v. Integrated Directory It shall be possible to provide display equipped voice terminals with access to system directory on digital and IP phones. Also System shall support internal and external directory. Any internal user can use by browsing the URL link from his laptop/PC to see the directory and dial the required no. by selecting under LDAP directory. The LDAP communication should be secured by communicating in a SSL tunnel.

vi. Performance of trunk operators The system should report clearance of calls by trunk operators and evaluate the performance index of each operator

vii. Reports The management platform must allow the administrator to generate reports and graphics of the activity per period of time in terms of traffic, accounting and alarms and giving the possibility to generate statics of this analysis. The reports must be predefined but the option to personalize the reports must be available .These reports must be available in HTML, pdf, excel and LDAP formats.

viii. Network Topology: The management server should provide an application that offers a view of IP Extensions registration status of the telecommunication system.

ix. (xi) Monitoring module The system must give a detailed analysis of the usage of trunks .The report generated should give out the subscriber numbers, ,time of day, date , usage ,cost etc .The system manager should be able to set restrictions( thresholds) on the usage of various trunks according to the subscriber’s priority . Each subscriber can be set limits for usage of trunks /CO ports. The system should be programmable to send alerts to the subscribers and also to the administrator in case of thresholds crossings. The system should be able to monitor as which all subscribers are busy in a particular call. The feature should also be available for the operator console also i.e. operator should be able to see the numbers which are busy in a particular call.

e Data and Security features

(i) All management traffic between a remote console/session and the call server must be encrypted. (SSH for direct command line sessions, HTTPS(SSL) for web sessions, SFTP for file transfers, etc.)

(ii) To ensure security of IP voice packets, end to end media and signaling encryption must be supported. The encryption employed should be strong and standards based.

(iii) The system should support standard features like intercom, messaging (text), call history and billing status specifying the duration of calls.


GHMC Page 88

(iv) The management platform must provide account management to define specific function responsibility.

System Survivability

a

The system should offer maximum availability, with the switchover of call control processing functions to an alternate or redundant processor (or soft-switch control point) in the event of significant fault. The switch over between 2 redundant call control processors should not interrupt existing and established communications. In case of failure of the main Server (hardware or software), the standby Server must take over the control of communications instantaneously. There should be no restriction on number of endpoints being backed up in case of one server failure.

b The server must be redundant and in a hot-standby configuration, allowing them to be installed in two different geographically separated locations.

c

Media Gateways must have self-survival mechanisms that allow them to maintain 100% of the telephony services for their users, in case of failure in the LAN/WAN/IP links where the signaling with the call server drops. Each gateway should be configured with local survivability to support basic telephony features of that Media Gateway and enabled to start up automatically & work as an isolated small PBX in case complete failure between call servers.

d The management Platform must provide a backup mechanism for all critical system information in both a manual and an automatic/scheduled archival and a Disaster Recovery mechanism.

e The system must support Remote Location Units on IP.

f Replacement of cards without switching off exchange (Hot swappable) including the control cards and peripheral/interface cards.

g All the tone generation and tone detection should be local to the gateway.

h The media gateways and call servers must be highly reliable ensuring uptime of at least 99.99%.

i The system should be able to restart automatically without human intervention when the external ac power supply is resumed after complete power failure i.e. Even after the batteries are discharged

j LIFE CYCLE: The life cycle of the exchange should be min 10 years

k All server databases should be coherently maintained .In the event of a switch over (a) Calls already in progress should be maintained. (b) Calls being connected should not be lost .

l Separate chassis for Media gateways with CPU & Power Supply at all locations in order to make redundant CPU & power supply .Each media gateway should have two power supply modules /cards per rack.

Media Gateway Interface a Analog Subscriber Card: Minimum 16 ports with minimum 3000 ohm loop resistance b Digital Subscriber Card: 08 / 16 ports c CO (PSTN) Trunk Card: Minimum 08 ports with minimum 2000 ohm resistance d E1 Card e ISND PRI Card (30 Channel) f E&M 2W/4W: Minimum 04 port g LD Trunk (TWT): Minimum 04 port h ISDN BRI Extension Card: Minimum 08 ports i ISDN BRI Trunk Card: Minimum 08 ports j Digital Trunk - E1-R2MFC k IP Trunk l Analog Subscriber Card: Minimum 16 ports Physical


GHMC Page 89

a The cards and slots should be universal should be interchangeable without switching off the exchange or removing power supply from the shelf..

b System shall have backup batteries powering min for 4 hrs.

c

Environmental Conditions The equipment offered shall be capable of maintaining its guaranteed performance when operating continuously for 24 hours a day and 365 days a year under the following environmental conditions :- (i) Operational temperature: 0 to 45 Degree C. (iii) Humidity 20% to 80% without condensation

System Features

a Numbering scheme. The EPABX should be suitable for up to 8 digit extension numbering scheme. This numbering scheme should be flexible. System should also allow mixed numbering scheme

b System should provide different rings for internal calls, junction calls, auto call back, wake up service and emergency reporting service.

c

The system should support the attribution of an external number DDI or individual line or a bundle head to a trunk, a bundle, an attendant, a group of attendants, a subscriber, a group of subscribers or virtual equipment. The unanswered DDI communication can overflow, to Attendant or attendant group, Local subscriber, Network subscriber, Voice mailbox, automated attendant, abbreviated number, External number.

d

The system must have the option for allowing outside caller to access switch features by dialing a special telephone number. Without attendant assistance, it should permit remote access to the server and long distance facilities from off premise stations .For security, there should be option of turning off this feature.

e

System traffic reports Traffics statics should be provided for incoming and outgoing call trunks / trunk groups, attendant consoles, static hunt groups and individual stations. The information must include the number of calls; call duration .The bidder must describe the proposed systems traffic reporting capabilities.

f

The proposed system should support automatic route selection (ARS) and least hop routing (LHR) features to route the calls based on priorities related to user profile, tariff, and network availability, along the most cost- effective path. This service will be transparent for users and irrespective of the physical carrier connection

g The system should support digital telephones, direct inward dialing, direct outward dialing, caller line identification, data communication, PC based operator consoles, IP line and trunk interface, video conferencing, VOIP, interactive voice response system, call forwarding,

h Voice Prompts The user should be able to edit/modify/add the system voice prompts.

i Voice Guidance Voice guidance for telephone should be offered as standard at least 50 prompts should be provided.

j External holding tone /music The system should be able to store different music /tone / customized song in standard digitized format like MPEG ,wav etc and also accept external music from a PC or an audio CD player .

k

The system should support the following features on IP system from any terminal, call forwarding ,call hold ,call park, call pick up: pick up any call ringing on another extension, pick up a hunt group call ringing on another ringing on another extension, acquire call, call waiting, ignore the call waiting, disable call waiting, clear the current call and pick up the waiting call, place the current on hold and pick up the waiting call, suspend the current call into the specified call slot and pick up the waiting call, pass the call to voice mail ,send all calls to voice mails, clear call waiting ,dial on pick up ,handset dial by name, hold call waiting ,ring back when free, suspend call waiting.


GHMC Page 90

l

The system should also support features like ACCOUNT CODE: system should have the capability to track calls to a particular external subscriber. A particular code can be assigned to the external subscriber and any call to the subscriber is through the account code .To ensure that every call to this client is recorded, a user can be forced to use an account code when making an external call. Account codes can either be forced or voluntary but must be registered with the system. Analog phones cannot enter account codes. Conference calls, directory, distinctive paging, do not disturb, enhanced intrusion. MOBILE TWINNING :allows a user to twin their office desktop phone with an external device such as their mobile /cell phone, follow me hot transfer, toggle, twinning, login, monitor calls ,meet me conference, hunt groups, bridged appearance, call appearance, call barring, call coverage ,caller display, dial emergency, external control port, group paging, hold music, hot disking, remote hot disking, incoming call routing, intrusion warning tone, alternate route selection, programmable maximum call length, key and lamp operation, night service, Priority calling, privacy, trunk to trunk transfer restriction override .

m The system should provide the possibility to restrict the access to certain trunks depending on any time of day features like caller line identification restriction for internal calls, camp busy telephone /hunting group/voice mail, controlled private call by pin code and password.

n

Basic Telephone Features a. Abbreviated dialing / Appointment reminder b. Automatic call-back on busy trunk/bundle/network link c. Automatic DISA, user authentication d. Call forwarding unconditional on busy/no reply to extension, hunting group, Voice

mail, operator, paging, etc. e. Conditional external forwarding( busy or no reply) f. Immediate forwarding g. Call pick-up. Call parking .Call tracing h. Call waiting indication / voice prompt i. Calling line identification restriction for internal calls j. Camp on busy telephone/hunting group/voice mail k. Controlled private call by Pin code and password l. Do not disturb m. Internal/external music on hold n. Internal/external inquiry call o. Individual hold p. Instrument locking to prevent the outgoing q. Last internal/external number redial r. Personal code modification s. Priority call. Priority cut in t. Store and redial external number u. Transfer in conversation on free/busy telephone v. Voice prompts on/off per telephone w. Voice message deposit on forwarded telephone x. Appointment reminders per extensions y. Boss Secretary Feature: One touch key for Boss and Secretary, Screening through

Secretary, Boss & Secretary busy indication Reminder, 32 party conference calls within subscribers of main exchange.

System Network Support

a The system should support international telephone standards such as QSIG (BC and GF), H.323 and SIM enabling interconnection with other 3rd party systems. The system should be Q-sig ready.

c The system should have options to network over any of IP, ISDN, Frame Relay technologies.

d

The system must support the following external telephony interface signaling: (i) E1 CCS PRI (VN3-4-6-7 /ETSI) (ii) E1 CAS (R2, Q421, Q23, Decadic) (iii) T1 CCS generic


GHMC Page 91

(iv) E&M (v) T0 ISDN BRI(VN 3-4-6-7 ETSI) (vi ) T1 CAS (vii) T0 ISDN BRI (VN3-4-6-7 / ETSI) (viii ) Analog Loop Start and Ground Start.

Server Based CPU Controller (Duplicated) a Format U rack mount - fixed rails kit included with server b Processor Xeon 4 core or equivalent c Number of processors : 1/2 d Cache memory : Minimum 8 MB per processor socket e Memory - Min 8 GB DDR-3

f Minimum 3 hard disks supporting RAID 5 configuration. Each hard disk of 500 GB min (hot swappable)

g DVD-ROM / CDRW slim line DVD. h Hot swappable and redundant fans i Minimum three gigabit (10/100/1000 Base) -T Ethernet ports j Should run on open source secure Linux operating system k Redundant power supply l USB ports 6 * USB 2.0 ports standard (2 front, 4 rear). m PS/2 ports (mini-DIN) 2 (mouse, keyboard). Card Details Analog Subscriber card a Should support 16 ports. b Each port should support CLIP features Digital Subscriber card a Should support 16 ports. b Each port should support CLIP features d Provide digital ports for connecting digital telephones, attendant consoles etc. Trunk Cards a

CO Trunks (i) Should accept/extend CLIP features (ii) Should be able to capture CLIP from PSTN network.

b

E1 Trunks (i) Should be able to take on E1-CCS & CAS : ISDN (PRI), Q-SIG and DPNSS (ii) Should have one or more ports.

c

E&M Trunks (i) Should support E (RON) / M (TRON) in 2- or 4-wire circuits (ii) Accept signaling on 2280 Hz (or 3000 Hz) (iii) Protocol Selection The choice of protocol should be selectable by board straps/jumpers (line signaling) or by software (for R2 or Q23 (DTMF) type signaling). (iv) Should support 4 or more circuits per board/card

Audio Conference (Required Hardware and Software For Performance of Following Tasks To Be Specify By Vendor)


GHMC Page 92

a

The collaboration suite must include self-service audio conferencing capabilities. These capabilities must be accessed by the user through the web interface including:

i. Ad-Hoc/On Demand Conferences, allowing the users to start an audio conference at any time by just aggregating the participants from the buddy list or by calling them at any telephone number (internal or external) without access codes.

ii. Reservation less Conferences (conference rooms), that the user can create by himself that include a "number to call" and an "access code" that can be used at any time to establish a conference call. Participants just dial the number and access code, and the conference is established.

iii. (iii) Scheduled Conferences that the user can schedule through the application user interface. The conference is scheduled for a specific date, time and duration. The application must generate an access code, a URL for this conference and provide a dial in number. Participants can join the conference by dialing the number and entering the access code.

b If enabled participants must be able to ask the application to call them to join the conference by clicking on the URL provided by the application.

c Scheduled conferences must include recurrence (daily, weekly or monthly).

d The audio conferencing bridge must allow dial-in as well as perform dial-out tasks to join the participants in the conferences.

e Users must have the option to specify access codes for a conference or have them generated automatically by the application.

f The application must generate different access codes for participants and leaders. g Users must have the option to create either leader required or leaderless conferences. h

Conference leader must be able to: (i) Mute participants (ii) Add/drop participants via the web UI (iii) Initiate web presentations, share their desktop and provide remote control

Automated Fault Registration system GENERAL: The automated Fault Registration is a special service extended to help all users of to register their complaint about faulty telephone lines/instruments etc. through a multi modal system (Landline/ SMS/ Web). a Features

i. Any caller from their work area or from any other telephone exchange should be able to access the services

ii. The services of Tele-Fault should also allow technicians/linemen and other Service personnel access to all the complaints lodged in by the users.

iii. TELE-FAULT should have various levels of Interaction. iv. Callers should be able to register their complaint from any exchange (Local/ RLU) or Web. v. The system should be able to issue a complaint number against every new complaint. vi. The technicians should be able to listen to all complaints or to a particular complaint lodged in

the by the caller. vii. The technicians should be able to report the action taken on a complaint by calling into the

system from an extension number / through dial –up options/ LAN or by physically keying in the actions taken.

viii. Alerts should be sent to the administrator concerned through email or an auto- dial- notification.

ix. It should support Security and logging (User wise options). x. It should generate complaint numbers. xi. All technicians should have a password to access the system. xii. It should provide GUI interface for changing and recording of prompts for different levels xiii. The system should be able to generate various reports for management and control

purposes. These can be configured to meet the user requirements. These may include statistical reports of various types as indicated below.

xiv. Reports indicating total number of complaints registered and rectified during a specific period viz. daily, monthly or annually.

xv. The supervisory end should be able to maintain logs on the system access.


GHMC Page 93

b Telephonic Registration The Proposed Call Flow and Voice prompts will be designed and approved by the customer is advance. Four telephone lines from the any of the EPABX or direct exchange will be terminated on the Complaint Management System. c Web- Based Registration All the users who are on LAN with the web server should be able to access a web page on the LAN and should be able to register their complaints. All the users who are on LAN should be able to access a Complaint Management web page on the LAN and should be able to register their complaints. A docket number should be generated by the system and given to the user through a POP window. Through the user web page, the user should be providing information on the mode of notification. d Notification through E-mail As and when a complaint is rectified the user should be able to get an e-mail notifying the user on the status of the complaint PROCESSOR FOR UNIFIED COMMUNICATION SERVER ( a) Format U rack mount - fixed rails kit included with server (b) Processor Xeon 4 core or equivalent (d) Cache memory : Minimum 8 MB per processor socket (e) Memory - min 8 GB DDR-3

(f) Minimum 3 hard disks supporting RAID 5 configuration. Each hard disk of 500 GB min (hot swappable)

(g) DVD-ROM / CDRW slim line DVD. (h) Hot swappable and redundant fans (i) Minimum three gigabit (10/100/1000) Base -T Ethernet ports (k) redundant power supply (l) USB ports 6 * USB 2.0 ports standard (2 front, 4 rear). (m) PS/2 ports (mini-DIN) 2 (mouse, keyboard). (n) PCI/PCI-X slots availability (Min. 2) UNIFIED MESSAGING/COMMUNICATION for 200 Users (a) PS/2 ports (mini-DIN) 2 (mouse, keyboard).

(b) Unified messaging must be able to handle various types of messages and at least Voice, fax and e-mail messages.

(c) Voice and fax messages must be directly stored on the e-mail server as e-mail messages with adequate attachments files (ex : .wav for Voice).

(d) The Unified Messaging application must provide a unique inbox for e-mail, voice mail and faxes messages.

(e) The Unified Messaging application must be able to identify messages by their type (e-mail, voice, and fax).

The Unified Messaging application must have a unified directory that allows the user to identify, send, reply, forward, call their correspondents. This unified directory must be able to search information from following directories:- (i) IP PBX directory. (ii) Corporate Directories (LDAP directories - v2 or v3 protocol). (iii) Microsoft Outlook or IBM Lotus Notes personal contacts.

(f) (iv) Any other personal phonebook.

(g) Unified Messaging application must be accessible by Graphical user interface from various devices: Web browser, PDA, Application/business phone.

(h)

The Unified Messaging application must also be accessible from dedicated function buttons integrated into e-mail clients. The user must at least be able to manage the listening of the voice messages and if possible give the user Unified Communication features such as make calls and access to the IP PBX services.


GHMC Page 94

(j)

When accessing messages by Telephone User Interface (TUI) the following services must be available : (i) Addressing messaging by name (call by name). (ii) Send a voice message to any e-mail address.

(k)

When accessing messages by Graphical User Interface (GUI) the following services must be available : (i) Message classification by type. (ii) Call sender on voice message. (iii) Call sender on email message. (iv) Forward messages. (v) Save messages.

(l)

In addition to Unified Messaging specific features, the application must provide classical Voice mail system features:- (i) Message Listening facilities. (ii) Messaging facilities. (iii) Recording facilities. (iv) Notification facilities. (v) Personal settings facilities

(m)

The Unified Messaging application must provide several different ways to listen to messages: (i) On declared Business phone. (ii) On alternate phone (ex GSM when out of office). (iii) Opening attached files with PC Multi Media player. (iv) Through direct embedded Unified messaging Functions (Play, pause).

(n) The Unified Messaging application must allow to record, send, reply, forward Voice messages.

(o) Ability to record live conversation. (p)

It must be possible to record and to activate different type of greetings. (i) Standard greeting. (ii) Busy greeting. (iii) Internal greeting. (iv) Alternate greeting. (v) Extended absence greeting.

(q) Recording name. (r) Setting passwords.

(t) Local, Remote and mobile users must be able to access their fax messages from a Web interface or from any telephonic station using a TUI (Telephone User Interface) based on VxML providing the option to print, save, forward or re-send the fax.

(u) The Unified Messaging application must be able to integrate third party Fax Servers. (Vendor Needs To Provide Necessary Support)

(v) Notification facilities must be applicable for any kind of message (voice mail, e-mail, fax). (w)

Destination of notification must include: (i) e-mail. (ii) Message Waiting Indicator (MWI) LED on the Business phone. (iii) Mobile phone (by SMS).

(y) Users accessing the application from PC must be authenticated using a strong authentication mechanism such as RADIUS

(z) The application must support secured protocols (LDAPS, HTTPS,…) (aa) Application sessions must close automatically after an inactivity period.

(ab)

The unified messaging application must include an efficient user management system that allows:- (i) Retrieval of users from various origins. (ii) From PBX phonebook. (iii) From LDAP directories (email server, corporate directory,...) (iv) Easy User Configuration (create, delete, restrict, define services, etc) (v) Mass provisioning.


GHMC Page 95

(ac) The administration tool must be Web based (ad)

The administration tool must include the following facilities: (i) Monitoring of the application and service status, traffic and service control. (ii) Management of the licensing. (iii) Backup and restore. (iv) Generation of log and trace files.

(ae) The Unified Messaging application must use standard and state of the art technologies such as SIP, XML, SOAP and WSDL at the core to manage the IP flows and messages.

(af) The Unified Messaging must provide Web services interface to ease integration with existing business applications.

(ah) The Unified Messaging application must be able to be integrated with e-mail servers Web/Thick client based Advanced Softphone

(a) The advanced softphone user must have access to Rich telephony services as any other user of the IP PBX.

(b)

The advanced Softphone must be able to propose efficient call possibilities. (i) Call by name (ii) Call by number (iii) Call from directories (iv) Call from call logs

(c )

From the softphone interface it must be possible to:- (i) Take call. (ii) Clear call. (iii) Transfer calls. (iv) Dial DTMF tones. (v) Record conversation. (vi) Redial the last number. (vii) Send a call back request. (viii) Put in conference. (ix) Put on hold. (x) Request Call back.

(d) The soft phone must be able to handle Multi-lines. (e) The soft phone must provide direct Voice mail access. (f) The soft phone must also provide Message Waiting indicator (MWI). (g) To manage the voice flow, the Advanced Soft phone must be able to use:

(i) Any IP and Analog phone set (ii) VoIP using the multimedia resources on the PC

(h) The Advanced Soft Phone must be able to handle headsets and handsets. Advanced features of Soft phone

(a)

The advanced soft phone must have an unified directory that allows the user to call by name and identify their correspondents. This unified directory must be able to search information from following directories:- (i) IP PBX directory (including personal entries from the users). (ii) Corporate Directories (LDAP directories - v2 or v3 protocol). (iii) Microsoft Outlook or IBM Lotus Notes personal contacts.

(b) The advanced soft phone must manage several call logs.

(c ) A call log with the answered, unanswered and outgoing calls, allowing click to call functions over the callers information

(e) When connected to the Intranet of the enterprise, Remote users must be able to use their soft phone to access regular telephony services.

(f)

Remote usage must be compatible with:-(ii) Thick Client (iii) In remote conditions, a call initiated with the advanced soft phone, must be seen by the calling party as a call initiated by the user itself.

Management facilities on Soft phone. (a) General Features


GHMC Page 96

(i) Inbound fax routing methods supported: DNIS, CSID, ANI (ii) Notification to one or several email addresses to one or several printers

(b)

Fax archiving (i) Archiving of all inbound & outbound faxes in central system database (ii) Auto-Deletion (configurable retention time) in the fax archive.

(c)

Faxing facilities (i) Coversheet are automatically filled with available sender & transaction information (if the corresponding variable was put on the coversheet)

Presence and Instant Messaging

(a) The Instant Messaging System must be secure, auditable and provide the ability for users to store IM threads locally.

(b) The instant messaging application must have a friendly, intuitive and easy to use graphical interface that informs in real time the multiple states of presence using the buddy list created by the user.

(c) The presence must use icons and colors and must include at least:- (i) On-Line Presence. (ii) Telephony Presence when calls are initiated through the conference bridge. (v) User-Choice Presence, (Busy, Be right back, Away, Out to lunch and Appear off-line).

(d) The instant messaging application must allow instant messaging (chat) sessions between members of the buddy list and perform actions as:- (i) Generate a call between buddy list contacts. (iii) Invite someone else to the conversation (iv) Share an application. (v) Launch an ad-hoc conference.

(e) The instant messaging application must include a log of all Instant Messaging sessions by a conversation history list on the interface indicating date, hour, contacts, content.

(f) The Instant Messaging service must be available during the audio conference sessions. Voice Mail Features

(a)

General The system should be equipped with server based voice mail system. The voice mail server to be provided by the vendor and should have specifications similar to or higher than the call server .The server should be external to the call server. The voice mail system should be available even if the primary server fails and secondary takes over. The voice mail must work as a centralized resource in case remotes are connected to the main exchange.

(b) Service Availability (The name of services given below may change as per different make & model of different exchanges but functionality listed below should be complied with)

(i) Voice messaging features That allow the owner of a mail box to send messages to other mail users whether they are part of the same system or remote users.

(c ) Voice and Fax applications to present company information (opening times, description of departments [e.g., marketing], product catalogs, etc.) and to provide automation of tasks like questionnaires, fax-on-demand, or fax overflow.

(d) E messaging service Should allow subscribers to access their voice mail from a remote PC (e-mail client) via the IP network.

Mailboxes and Access Control (a) Number of mailboxes >1500 (b) Recording time >100 Hours (c ) Simultaneous accesses >15 ports Voice Messaging System (a) Call answering or call/record answering function with time stamp. (b) Customization of an announcement (c ) Call forwarding to the voice mail


GHMC Page 97

(d) Message notification via message indicator LED or voice prompts. Web Administration i Secure admin access through username/password challenge.

ii Monitor Fax Status (search, view fax content, view fax detailed information, forward, reroute, retry now, resubmit and Cancel)

iii Monitor channels activity. iv User management Move add & change of personal information, password, fax profile v Manage Fax profiles (Fax, Notification, Permissions & Coversheet options) vi Customize notification templates vii Create and modify coversheets through Windows Coversheet authoring tool viii Configure dial Peer, signaling protocol supported (SIP), channel mode, inbound CSID ix Configure the inbound routing table (users, emails and printers) and misrouted faxes ii Support for faxing from web interface. iii Secure user access through username/password challenge. i Submit faxes from any SMTP based messaging system ii Outlook fax extension through Outlook forms iii E-mail notifications to confirm sent/failed outbound faxes iv Email notification for inbound faxes

v Notifications, outlook forms and Notes forms localized in 6 languages (French, English, Italian, Spanish, German and Portuguese)

vii Notification to one or several email addresses or to one or several printers i Support SIP/T38 (SIP stateless and state full proxies) 12. BILL OF QUANTITY IT Infrastructure at the Data Centre and Disaster Recovery Centre

Sl.No Component Quantity

Required for DC

Quantity Required for DR

1 Database Server (2 for General Database + 1 for existing ERP) 3 2

2 Web Server 2 1

3 Application Server (2 for General Database + 1 for existing ERP) 3 2

4 Mail & Messaging Server 1 1 5 DNS & DHCP Sever 1 1 6 Anti-Virus & Anti-Spam Server 1 1 7 Directory Server 1 1 8 Backup Server 1 1 9 Staging server 1 0 10 GIS Server 1 1 11 Document Management Server 1 1 12 Business Rules Specifications 1 1 12 SAN Switch 2 1 13 SAN Storages 1 1 14 Tape Library (with Media for project period) 1 1 15 Internal Firewall 1 1 16 DMZ Switch 2 1


GHMC Page 98

17 KVM Switch 2 1 18 HSM 1 0

Software Licenses: The bidder is required to meet the licensing requirements of the proposed solution so that all the requirements and expected outcome of the project are completely fulfilled IT Infrastructure at all Offices

Item Total Quantity RequiredDesktop 800 Duplex Laser Printer 300 UPS for 120min backup (10 KVA) 25 Bio-Metric Attendance System 25 IP Based Communication server for 1200 Users across offices of GHMC 1 Layer 2 Switches 100 Laptops 136 Note:

1. As per the data provided in the existing infrastructure section, the bidder is required to buyback the condemned material / machines as per the details mentioned in the RFP in Annexure – 3 and he may factor the receivable amount in the bid.

2. The quantity of the servers / desktop / printers / other systems may increase during the implementation. GHMC at its discretion may buy them from open market / bidder through competitive bidding with lifetime AMC and payment for this will be made on the actual supply as per the unit rate. The bidder will have to ensure proper security/ connectivity to the network for the additional systems.

3. Locations for supply and quantity to be supplied for each location will be informed to the successful bidder during the procurement stage

Site preparation

Item No. of Locations Total Quantity required

Electrical Cabling () for UPS 30 200 Bundles Structured LAN cabling () 30 150 Bundles LAN Nodes for all Locations 30 1500


GHMC Page 99

13. FUNCTIONAL REQUIREMENT SPECIFICATIONS This section of the RFP provides high level indicative functional requirement specifications for developing the solution for GHMC. However these functional requirements needs to validated, modified to suit the GHMC integrated application during the SRS development stage of the Project. Property Tax User Authentication 1. To query the database - user-id table and the password for the given user id is compared. If

appropriate menu is displayed, otherwise error message is displayed. 2. Usage of Biometric Authentication Methods such as Finger Print Technology for authentication

or PKI Architecture Inclusion of New Assesse 3. Ability for entering/adding the applicant details for new assessment and also facilitates in

modifying an existing record and deleting an existing record. 4. Ability to generate a new assessment application acknowledgment receipt through the system

either online /offline. 5. Ability to facilitate entering/adding of the field verification details for new assessment and also

facilitating in modifying an existing record and deleting an existing record. 6. Ability to generate a new assessment application acknowledgment receipt through the system

either online /offline. 7. Ability to generate field verification checklist report for the particular date, which is given as

input. 8. Ability to facilitate entering/adding of the field verification details for new assessment and also

facilitating in modifying an existing record and deleting an existing record. 9. Ability to facilitate in generating the special notice to the assesse indicating the amount of tax

to be paid. 10. Ability to enter the revision petition application into the system. If the assesses does not agree

with the tax levied, he can apply for revision within 15 days of service of special notice. 11. Ability to generate acknowledgement for the revision petition application received. 12. Ability to facilitate entering of the revision petition hearing date into the system. 13. Ability to facilitate entering of the revision petition hearing details into the system. 14. Ability to generate endorsement for the revision petition after the hearing is done and the tax is

either confirmed or revised by the commissioner. 15. Ability to facilitate in entering the appeal petition application into the system. If the assesses

does not agree with the tax levied in the revision petition hearing, he can apply for appeal of revision petition orders.

16. Ability to generate the acknowledgement for the appeal petition application received. 17. Ability to generate the acknowledgement for the appeal petition application received. 18. Ability to facilitate in entering the appeal petition hearing date into the system. 19. Ability to facilitate in generating the appeal petition hearing date information report. The

assesse is intimated about the appeal petition hearing date on which the hearing is held. 20. Ability to facilitate in entering the appeal petition hearing details into the system. 21. Ability to generate the endorsement for the appeal petition after the hearing is done and the tax

is either confirmed or revised by the commissioner. 22. Ability to facilitate in generating the court cases details for the Assessment. Change of Ownership 23. Ability to facilitate in entering/adding the application details for title transfer of property and also

facilitates in modifying an existing record and deleting an existing record. 24. Ability to facilitate in issuing an acknowledgement for the application for title transfer property. 25. Ability to facilitate in generating the field verification checklist report for the bill collectors use. 26. Ability to facilitate in entering/adding the field verification details for title transfer property and

also facilitates in modifying an existing record and deleting an existing record 27. Ability enter/add the approval details for title transfer property and also facilitates in modifying

an existing record and deleting an existing record.28. Ability to enter/add the fee payment details for title transfer property and also facilitates in


GHMC Page 100

modifying an existing record and deleting an existing record. Ability to facilitate in generating the endorsement for the title transfer property after the property is transferred and the fees is paid

Assessment & Collection of Property Tax29. Ability to calculate the PT to be levied based on the building type, area, usage details etc. 30. Ability to change property tax computations and determine arrears/refunds etc. with proper

controls/Authorization. 31. Ability to enter/add the assessment details and property tax levied and also facilitates in

modifying an existing record and deleting an existing record. 32. Ability to enter/add the Arrear details and property tax levied for assessment and also

facilitates in modifying an existing record and deleting an existing record. 33. Ability to generate the demand registers for the specified period. This function facilitates

printing of demand notices for the half year. 34. Ability to generate the PT paid for the assessment. 35. Ability to generate advance PT receipt for the assessment. 36. Ability to generate enter/add the application details for exemption from property tax and also

facilitates in modifying an existing record and deleting an existing record.37. Ability to generate the field verification checklist report for exemption for Bill Collectors use.38. Ability to enter/add the field verification details for exemption and also facilitate in modifying an

existing record and deleting an existing record.39. Ability to enter/add the approval details for exemption and generating an exemption approval

details report and also facilitates in modifying an existing record and deleting an existing record.

40. Ability to enter/add the application details for vacancy remission from property tax and also facilitates in modifying an existing record and deleting an existing record.

41. Ability to issue an acknowledgement for the application for vacancy remission. 42. Ability to generate the field verification checklist report for Vacancy Remission for Bill

Collectors use. 43. Ability to facilitate in entering/adding the field verification details for vacancy Remission and

also facilitates in modifying an existing record and deleting an existing record. 44. Ability to facilitate in entering/adding the approval details for vacancy remission and generating

an vacancy remission approval details report and also facilitates in modifying an existing record and deleting an existing record.

45. Ability to facilitate in entering/adding the application details for write off from property tax and also facilitates in modifying an existing record and deleting an existing record.

46. Ability to facilitate in issuing an acknowledgement for the application for write off. 47. Ability to facilitate in generating the field verification checklist report for Write Off for

Bill Collectors use 48. Ability to enter/add the field verification details for write off and also facilitates in modifying an

existing record and deleting an existing record with proper controls/authorization. 49. Ability to facilitate in entering/adding the approval details for write off and generating a write off

approval details report and also facilitates in modifying an existing record and deleting an existing record with proper controls/authorization.

50. Ability to facilitate in generating the court cases details for the Assessment General Revision of Assessment 51. Ability to accept requests for Revision 52. Ability to accept the field verification details 53. Ability to update the Assessment database based on the field verification details 54. Ability to enter the property modification details 55. Ability to enter the penalties details 56. Ability to capture the approval details Collection of Service Charges for Central Government Properties57. Ability to maintain the list of Central Government properties 58. Ability to calculate the service charges for the said Central Government properties 59. Ability to generate demand notices for service changes payable 60. Ability to generate demand notices on non-payment of service charges SMS Facility 61. The system should able to capture / update the mobile number of the assesse


GHMC Page 101

62. The system should be able to send an alert to the property owner with the property tax details like amount to be paid, due date for payment, etc..

63. The system should be able to generate and send mobile acknowledgment when the tax is paid

64. The system should be able to send reminders if the assesse fails to pay the tax on time Payment Collection through Handheld Devices65. The system should able to push the date to the handheld device from the database and pull

the data from the handheld devices through GPRS 66. The system should be able to post the payment collection information to the database and

generate the acknowledgement for the payment 67. The system should be able to generate device wise payment details every day Creation of Masters 68. Ability to maintain the location details in the masters 69. Ability to maintain details of Revenue Zones( Addition/Modification/Search) 70. Ability to maintain details of Revenue Wards( Addition/Modification/Search) 71. Ability to maintain details of Revenue Blocks ( Addition/Modification/Search) 72. Ability to maintain details of Locations( Addition/Modification/Search) 73. Ability to maintain details of Locality( Addition/Modification/Search) 74. Ability to maintain details of Apartments/Complexes( Addition/Modification/Search) 75. Ability to maintain details of Nature of Use of the Buildings( Addition/Modification/ Search)76. Ability to maintain details of Building Classification Type( Addition/ Modification/ Search) 77. Ability to maintain details of Roof Type Master( Addition/Modification/Search) 78. Ability to maintain details of Wall Type Master( Addition/Modification/Search) 79. Ability to maintain details of Floor Types( Addition/Modification/Search) 80. Ability to maintain details of Unit Rates ( Addition/Modification/Search) 81. Ability to maintain details of tax Rates( Addition/Modification/Search)82. Ability to maintain details of Depreciation Rate( Addition/Modification/Search) 83. Ability to maintain details of Bill Collector Master( Addition/Modification/Search) 84. Ability to maintain details of Service Tax master( Addition/Modification/Search) 85. Ability to maintain details of Exemption details master( Addition/Modification/Search) 86. Ability to maintain occupier details( Addition/Modification/Search) 87. Ability to maintain details of Bank Master ( Addition/Modification/Search)88. Ability to maintain the list of all properties pertaining to Central Government

(Addition/Modification/Search) MIS & Reports 89. Field Verification Checklists 90. Special Notices 91. Demand Notices 92. Collections:

Bill Collectors Collection( Counter Collection, Direct bank remittance) Election Ward wise Collection Locality wise Collection Penalty on Late Payment Collection Penalty on Unauthorized Construction Revenue Block wise Collection Revenue Ward wise Collection Revenue Zone wise Collection Street wise Collection.

93. Registers Arrears Register Area Base Register DCB Register Exemption Details Register PT Register Register of Appeals for the Year Register of Distrait Register of Warrants Remittance/Daily Col Register Receipts/Payments Register of PT for the Year


GHMC Page 102

True Extract of PT Demand Register Vacancy Remission Register Write Off Register.

94. Certificates Ownership Certificate Valuation Certificate.

95. Other Notices Final Notice Warrant Notice

96. Apartment Details, Complex Details, Group Housing Details, Row Housing Detail 97. Building Age wise Assessment List 98. Monthly List of Buildings Requiring Levy of PT or Revision of PT 99. Occupiers Notice Details 100. Occupiers Other Than Owners 101. Tax Section Circle No. (Property details by the owner)102. Customized Reports as required by GHMC Advertisement Creation of Master Data

1.

The system should be able to create all the reusable data required for the issuing the advertisement license and collection advertisement tax like advertisement types , permission / encroachment fee as per the government scheduled rates, recording hoarding sites localities, Recording penalty fee details etc…

User Authentication 2. The system should authenticate the user with a user name and login to all users like

Commissioner, Town Planning Officer, Town Planning users Building Inspector etc… as required for department

Registration for license

3. System should be able to record all the fields of Advertisers license application / renewal of the application form through online and other modes

4. The system should generate application number automatically. Data is to be updated into both Advertisers database and Collection databases.

5. An Acknowledgement is to be issued to the applicant once the application is submitted 6. The system should record status of application of advertiser license

7. The system should provide option to record the details pertaining to the lease of advertisement hoardings

Payment 8. The system should record all types of collections made for fresh advertisement application

and renewal of advertisement application 9. The system should provide option for the security deposit in case of fresh application for

advertisement 10. The system should provide option to record the mode of payment made by the applicant 11. The system should generate the receipt for all the payments made by the applicants 12. The system should generate the details pertaining to the realization of cheque

Field verification 13. The system should enable to record the field verification details furnished by the Town

Planning Supervisor after the verification with all the measurements and location Generation of Advertiser License

14. The system should send a message to the concerned applicant about the status of the application

15. The system should generate the fresh license based on the payment received from the applicant if the application is approved

16. The system should generate the renewal of license based on the payment status 17. System should support recording closed / deleted Advertising Agent details. 18. The system should support to provide alert on the status of the license to the applicant 19. The system should be able to send the advertisement license on line to the applicant

Generation of Demand 20. The system maintain the database of the list of advertisers within a Municipality


GHMC Page 103

21. The system should support generation of Demand Notices to traders 22. Advertising Agents for their renewal, 23. Unauthorized advertisements 24. Advertisement tax and rent (Permission/encroachment fee) if any 25. Lessees for half-yearly collection with respect to tendered hoarding: 26. Recording details of served demand notices issued to lessees of hoarding 27. The system should generate the status of the demand served and support to send SMS to

all the licensees mention the amount to be paid 28. The system should generate the list of closed or deleted advertisers at any particular point

of time 29. The system should maintain the details of refunds in respect of security deposit refunded

after considered all fine amounts and due amounts till then 30. The system should generate the Advertiser Settlement Document where advertiser sought

for refund of security deposit; advertiser closed his advertiser license, rejection of renewal of advertiser license and cancellation of advertiser license at any time.

Tax Collection 31. The system should capture all the payment details like mode of payment, amount

collected etc… 32. New/Renewal advertisement tax details are to be updated into Advertisement Tax

Database. 33. System should generate an acknowledgement after receipt of payment for advertisement

tax 34. Unauthorized advertisements 35. System should be able to record all the details of unauthorized advertisement erected at

regular intervals. 36. System be able to record details of advertisements closed/deleted in case of non-

compliance to the served notice for the renewal as well as unauthorized advertisementsReports

37. Generation of displayed Advertisements details (added/renewed/closed) 38. Generation of current Advertisement Permit Register 39. List of Demand Notices generated 40. Generation of list of details of all leaseholders per advertising agent 41. Generation of list of defaulters with respect to tendered hoarding agency-wise 42. Recording details of settlement of lease closure

Details of Advertisement Agencies for Collection of Taxes43. The system should maintain the details and reports on registered advertisement agencies

in the GHMC area for tax collection. 44. Sites allotted to agency for outdoor display zone wise for collection of taxes 45. The system should have a provision to update real time collection details from the

agencies SMS Facility

46. The system should able to capture / update the mobile number of the assesse 47. The system should be able to send an alert to the property owner with the property tax

details like amount to be paid, due date for payment, etc.. 48. The system should be able to generate and send mobile acknowledgment when the tax is

paid 49. The system should be able to send reminders if the assesse fails to pay the tax on time

Payment Collection through Handheld Devices 50. The system should able to push the date to the handheld device from the database and

pull the data from the handheld devices through GPRS 51. The system should be able to post the payment collection information to the database and

generate the acknowledgement for the payment 52. The system should be able to generate device wise payment details every day

Parks


GHMC Page 104

User Authentication

1. To query the database - User-ID table and the password for the given User ID is compared. If appropriate menu is displayed, otherwise error message is displayed.

2. Single sign-on should be provided to the application. Creation of Masters

3. Details of parks & Open Spaces 4. Details of wayside views 5. Details of major traffic islands 6. Details of urban forestry belts 7. Other Sports facilities (Indoor, complexes) 8. List of sports and games available under each sports/games facility

9. List of contractors who have executed and are executing the work for GHMC (Developing new parks and maintaining existing parks). This information should be provided park-wise or facility-wise

10. Details of Colony Welfare Associations (CWAs) in GHMC jurisdiction 11. Inventory of parks equipment and other materials available at each facility 12. Facility-wise details of regular and contractual staff

Developing New Parks and Green Areas13. The system should have a facility to register a contractor in a prescribed format

14. The system should have the facility to apply through online through GHMC website, eSeva, Citizen Facilitation Centre’s and AP-online centre.

15. The system should give a provision to select the park/green space/wayside view etc., while applying/bidding. This is required when more than 1 tender is floated for developing new parks.

16. The system should have the facility to generate an acknowledgement and other filled in details.

17. The system should have a provision to send an SMS or an email automatically to the contractor.

18. The system should also have a facility to edit, modify and delete the record by the user. 19. The system should facilitate easy payment option through payment gateway

Maintenance of Existing Parks & Open Spaces20. The system should have a facility to register a contractor in a prescribed format

21. The system should have the facility to apply through online through GHMC website, eSeva, Citizen Facilitation centre and AP-online centre.

22. The system should give a provision to select the park/green space/wayside view etc., while applying/bidding. This is required when more than 1 park is projected for maintenance.

23. The system should have the facility to generate an acknowledgement and other filled in details.

24. The system should have a provision to send an SMS or an email automatically to the applicant.

25. The system should also have a facility to edit, modify and delete the record by the user. 26. The system should facilitate easy payment option through payment gateway.

27. The system should have a facility to send alerts on maintenance contracts that are nearing termination

Reports 28. Report on total number of new parks development contracts issued for the given year 29. Report on total number of maintenance contracts presently undertaken in the current year 30. Report on maintenance contracts that are nearing completion or termination 31. Report on total number of facilities owned, hired and leased by GHMC 32. Report on total procurement details of the department year-wise for the last 5 years

Information to be placed on GHMC Website

33. The website should have all the details of the parks/green spaces/wayside views/urban forestry corridors etc., owned, hired, leased by GHMC

34. The website should have all the details pertaining to contractors and CWAs presently executing contracts for the GHMC parks department

35. The websites should have details of dates notified for new contracts or termination of existing contracts

36. The website should have details of maintenance staff for each park along with contact details


GHMC Page 105

Secretary User Authentication

1. To query the database - user-id table and the password for the given user id is compared. If appropriate menu is displayed, otherwise error message is displayed.

2. Usage of Biometric Authentication Methods using PKI Technology. Master

3. Ward committee details 4. Area Sabha Details 5. Members of each Ward Committee 6. Members of Standing Committee 7. Members of the General Body of the corporation 8. Information of the Ward Secretaries9. Details of the ward committee and Area Sabha Offices 10. List of ward committee chairman

Standing Committee 11. The system should provide interface to enter the agenda and send the information to all the

members added in the master through email, SMS , Fax and generate print forms 12. The system should have an ability to archive the agenda of the meetings for future use 13. Ability to add /search the agenda at a future date 14. System should have ability to capture the details of the person who prepared and distributed

the agenda of the meeting through digital signature 15. The system should provide an interface for entering the resolutions online and circulate to

all the members of the standing committee by various modes like mail / fax / print 16. The system should have an ability to archive the resolutions of the meetings for future use 17. Ability to add /search the resolutions at a future date 18. The system should have an ability to enter the action taken on the resolutions passed by the

standing committee by the secretary 19. The system should have an ability to enter the details on the action taken on the resolutions

by the concerned authorities of the corporation General Body Meeting

20. The system should provide interface to enter the agenda and send the information to all the members of the corporation added in the master through email, SMS , Fax and generate print forms

21. The system should have an ability to archive the agenda of the meetings for future use 22. Ability to add /search the agenda at a future date 23. System should have ability to capture the details of the person who prepared and distributed

the agenda of the meeting through digital signature24. The system should provide an interface for entering the resolutions online and circulate to


standing committee by the secretary The system should have an ability to enter the details on the action taken on the resolutions

by the concerned authorities of the corporation Ward Committee

28. The system should provide interface to enter the agenda and send the information to all the members of the ward committee and area sabha representatives corporation added in the master through email, SMS , Fax and generate print forms

29. The system should be able to capture the attendance of the ward committee representatives

30. The system should have an ability to archive the agenda of the meetings for future use 31. Ability to add /search the agenda at a future date 32. System should have ability to capture the details of the person who prepared and distributed

the agenda of the meeting through digital signature 33. The system should provide an interface for entering the resolutions online and circulate to


GHMC Page 106


standing committee by the secretary 37. The system should have an ability to enter the details on the action taken on the resolutions

by the concerned authorities of the corporation Allocation of Work through Ward Sabha

38. System should an ability to send the Information to the stakeholders through various means including SMS and Email

39. Ability to send the resolutions of the works to the respective Deputy Commissioners 40. The system should have an ability to verify of the resolutions and passing it to the

concerned zonal commissioners 41. The system should have an ability for passing the resolution to the concerned HoD for

preparation of Administrative sanctions 42. System should have an ability to prepare the Administrative Sanctions 43. System should have an ability for approving and sending the administrative Sanction for

Budget Approval as per the requirements 44. The system should have an ability to capture the work details once the work is allocated to

the contractor 45. The system should have an ability to take the submitted reports by the contractor and send

it to the Zonal Commissioner and Ward Secretary on the work accomplished 46. System should have an ability to generate the bill by the engineer based on the input given

and pass it to the finance department for release of payment General Features

47. The system should have the inbuilt workflow for each service under this module 48. The system should provide PKI enablement for digital signatures 49. The system should provide the definite service levels and escalation workflow

Reports 50. Various reports on the works allocated to each ward 51. Reports on the status of the work 52. Assembly and Parliament Constituency wise report on the works 53. Report on the value of projects 54. Reports on the Ward Committee Members 55. Reports on Area Sabha Members

Electricity User Authentication


2. Single sign-on should be provided to the application. General Features

3. Details of all packages under street lighting maintenance contracts under GHMC 4. Details pertaining to all street lights package-wise under GHMC area.5. Details pertaining to various vendors from whom electrical materials are procured 6. System Should be able to generate a GIS id when the electrical pole is erected

7. System to capture the actual coordinates of the centre of the electrical pole in the lat and long fields provided in the field visit report

8. System should allow editing of latitude and longitude on a later date Maintenance of street lights

9. The system should have a provision to track the number of complaints received for street light maintenance

10. The system should have a provision for package-wise street light maintenance responses and Redressal

11. The system should have a provision to tract the material used for maintenance of street lights which will act as an input for additional procurement

Procurement if material for street light maintenance


GHMC Page 107

12. The system should have details pertaining to all types of material procured for maintaining street lights. Details like type of material, make, manufacture, name if the company, number procured etc., should be visible in the system.

13. The system should have a provision for maintaining warranties and guaranties of products procured

14. Details pertaining to vendors from whom the materials have been procured should be maintained.

15. Details of tenders along with other details if any like rate contracts etc., should be maintained by the system

Procurement of agencies for maintaining street lights

16. The system should provide details pertaining to the agencies/companies procured to maintain the street lights. These details have to be provided package-wise along with details of the staff under each package

Execution of new works (street lights)

17. The system should have a provision to record details pertaining to new areas and localities that have newly provided with street lighting

Payment of Power Bills for Street Lighting

18. The system should have a provision to details pertaining to the bills generated for street lighting

19. The system should provide for package-wise power bill generation details

20. The system should have a provision to record details pertaining to key officers who need to be contacted with regard to power supply and power bills

Reports 21. Weekly report on number of street lights maintenance work attended to by each package

22. Weekly report of number of complaints received on street light maintenance/mal-functioning of street lights (Package-wise)


23. The website should have all the details pertaining to all the packages along with names of agencies maintaining them with their contact information.

Estates User Authentication


2. Single sign-on should be provided to the application.Creation of Masters

3. Details of Assets and estates owned by GHMC 4. Details of the Plots along with the GIS Image of the plot 5. Details of Assets and estates leased by GHMC 6. Details of Assets and estates let out by GHMC 7. Details of all markets and shopping complexes owned by GHMC8. Details of heritage building and other cultural properties with historical significance 9. Details of open lands of GHMC 10. Details of parking areas allocated in the GHMC area

11. Details pertaining to the documents under the custody of the estates department pertaining to estates (sale deeds, rental and lease agreements, etc.)

12. Details of regular and contractual staff Allotment of Rent, Lease or Sale of GHMC properties

13. The system should have a facility to register a bidder in a prescribed format.

14. The system should have the facility to generate an acknowledgement for applications received.

15. The system should have a provision to maintain the data pertaining to lease, rent or sale of a GHMC asset

Collection of Rent, Lease on the Properties

16. The system should have a form to fill in the details pertaining to the properties that have been leased or let out by GHMC

17. The system should identify each property with a unique ID for navigation


GHMC Page 108

18. The system should also have a facility to edit, modify and delete the record by the user

19. The system should have a provision to map the person/party to whom the property has been leased or let out against each property.

20. The system should have provision to map details like address, email, mobile number etc., of the person/party/tenant along with all transaction pertaining to the property

21. The system should have a provision to generate reminders for non-payment of rent against each property

22. The system should have a provision to send alerts to the user in case a rental or lease agreement is nearing termination or completion

Parking

23. The system should have a provision to maintain the details pertaining to various parking areas in the GHMC area

24. The system should have a provision to maintain the details pertaining to various parking contracts issued to vendors

25. The system should have a provision to display the parking rate contracts in implementation Reports

26. Report on total number of properties sold by GHMC year-wise for the last 5 years 27. Report on total number of properties leased to persons/parties year-wise for the last 5 years 28. Report on rent/lease collected on an annual basis from properties leased out. 29. Report on property-wise details pertaining to lease and rent 30. Report on total procurement details of the department year-wise for the last 5 years

Information to be placed on GHMC Website31. The website should have all the details pertaining to the assets of the GHMC

32. The website should have property-wise details pertaining tenants currently on GHMC properties

33. The website should have zone-wise details pertaining to GHMC parking areas and to who it has been leased

34. The websites should have details pertaining to historical and heritage building in the GHMC area

Sports User Authentication



3. Details of Stadiums/Playgrounds/Other Sports facilities 4. Details of Playgrounds 5. Other Sports facilities (Indoor, complexes) 6. Details of Coaches 7. List of sports and games available under each sports/games facility 8. List of sports federations and associations in the state 9. Details of schools and colleges in GHMC jurisdiction

10. Inventory of sports equipment and other materials available at each facility 11. Facility-wise details of regular and contractual staff

Processes Organizing Coaching Camp

10. The system should have a facility to register an applicant in a prescribed format.

11. The system should have the facility to apply through online through GHMC website, eSeva, Citizen Facilitation centre and AP-online centre.

12. The system should have the facility to generate an acknowledgement along with the photograph and other filled in details.

13. The system should have a provision to send an SMS or an email automatically to the applicant.

14. The system should display the fee structure to the applicant once he/she selects the desired option.

15. The system should also have a facility to edit, modify and delete the record by the user.


GHMC Page 109

16. The system should give a provision to select the type of sport/game type and location of the facility

17. The system should facilitate easy payment option through payment gateway

18. The system should provide a facility to update the details of the short-listed candidates selected through the summer camps

Advanced Training Programmes

19. The system should have a flag or a provision to display candidates selected for advanced training programme

Organizing Tournaments

20. The system should have the facility to apply through online through GHMC website, eSeva, Citizen Facilitation centres and AP-online centres

21. The system should have the facility to generate an acknowledgement along with the photograph and other filled in details

22. The system should display the fee structure to the applicant once he/she selects the desired option

23. The system should display the fee structure to the applicant once he/she selects the desired option

24. The system should also have a facility to edit, modify and delete the record by the user

25. The system should have a provision to send an SMS or an email automatically to the applicant

Reports

26. Report on total number of enrollments into summer camps for the year-wise for the last 5 years

27. Report on total number of enrollments for advanced training programme for the last 5 years 28. Report on results pertaining to the tournaments organized in GHMC jurisdiction last 5 years 29. Report on total number of facilities owned, hired and leased by GHMC 30. Report on total procurement details of the department year-wise for the last 5 years


31. The website should have all the details of the sorts/games facilities owned, hired, leased by GHMC

32. The website should have all the details pertaining to shortlisted candidates 33. The website should have all the reports should be shown above on the GHMC portal 34. The websites should have details of dates notified for summer camps 35. The website should have details of dates of tournaments organized in the GHMC for year 36. The website should have details of all the sports and games federation in the state 37. The website should have details of facility-wise the coaches honorary and permanent 38. The website should have facility-wise details of house-keeping contracts issued

Town Planning Department

Sl.No Functionalities 1. Provision should be made for plan submission at any time, any day from any place.

Allow municipal officials to access/download the same for verification of particulars 2. System should enable the officer in-charge or the applicant to add/update the

information pertaining to name, address, license category, details of surveyor/ licensed architect and other required information

3. Generate application reference for Building Plan Application/ Layout Application for the applicant and facilitate online tracking of the status of the application.

4. Facilitate checking of the physical documents submitted by the applicant for building plan approval.

5. An acknowledgement should be generated and given to the applicant 6. Provision should be made available to receive building permit renewal application7. online 8. System should provide search facility to find out the old application by giving permit

number or owner details 9. System should permit architect to view the permit online10. System should generate automatically the fee for renewal11. System should allow the authority to approve the renewal of permit by using digital

signature


GHMC Page 110

12. Applicant should be able to take a print out of digitally signed renewed permit online13. System should allow overseer to record his field visit details in connection with

renewal of permit 14. List of all mistakes should be displayed in a single step. Applicant should receive the

status of his drawing in a maximum of 8 hrs. in a working day 15. Enable staff to enter required documents for building permission based on the height

of the proposed structure. Various categories based on the height should be allowed to be entered

16. Correction and resubmission of plan is should be allowed at a very quick and easy method. Facility should be provided for an applicant to correct and upload the revised drawing online in case of any modifications

17. No manipulation should be possible and the system should generate the dimensions, Area Statement, Margins based on Bird Eye View, FAR etc, automatically,

18. Facilitate checking and assessing the fee charges for an applicant and calculate the total amount to be paid.

19. Facility to be provided for an applicant to view the current status and movement of the file from the website

20. Auto generation of reports regarding expiry of building permit application should be made available in the application

21. Ability to track arrears due to the ULB and the robustness of the system needs to be maintained

22. All the rules should be verified with submitted plan by the system itself or to generate the complete objection list. All Violations need to detected with the system

23. Facilitate entering of the inspection and scrutiny details for the building plan permission such as the Site Inspection Report (fields such as application no., applied for, application date, applicant details, usage, building category, inspector details, date of inspection, etc.), Fee & Charges Calculations, and Certificate and Document Verification Report. Further system should facilitate generation of an endorsement or building permission order to the applicant, based on the scrutiny.

24. Facility to store all drawings stored in the web based server which can be retrieved at any point of time.

Technical Scrutiny of Layouts & Drawings25. The approved latest GHMC regulations are to be automated including by-laws for fire-

fighting. The aim of this automation being: 26. The architect/ client's plan in soft copy in CAD format (DWG) is to be mapped with the

rules of the GHMC. An automated scrutiny report indicating the required/ permissible parameters and the proposed parameters is to be tabled. These reports to be sent to higher authorities for approval.

27. Architect/ client's line drawing in AutoCAD should be read and area calculation sheet is to be system generated to eliminate the human errors. The required tables like area statement, FAR table per building, summary of FAR calculations, coverage table, opening schedules, parking calculations, area for plot, area of block diagram with dimensions, required margin regions, coverage per building etc. to be generated by the system and should be automatically updated in the drawing.

28. An automated scrutiny report indicating the required/permissible parameters and the proposed parameters is to be tabled including status of each rule whether passed or failed.

29. 5) There should be system generated list highlighting the entities on which the plan is failing, thereby enabling GHMC to prepare objection list and inform the client to take necessary actions.

30. The software should be able to scrutinize building plans of all types of layouts and buildings i.e. Residential, Residential standard designs, Group housing, Industrial, Commercial, Commercial standard design/controls, Institutional (bay sites/standard designs/zoning governed)

31. The software should include scrutiny and finalization of compounding cases with respect to GHMC Compounding Policy in case of Commercial, Residential, Institutional and Industrial.

32. The software shall have provision to scrutinize revised Building plans with compoundable violations shown on the plan,

33. A detailed check, should also be made with respect to the following provisions:


GHMC Page 111

a ZONING REGULATIONS. 1) Setbacks 2) Site plan configuration.

i. Plinth level ii. Front road level iii. Surrounding area levels – Coverage, direction and Surrounding roads.

b AREAS / DENSITY / FAR / FIRE SAFETY: In all cases the following parameter checks should be possible with respect to rules applicable:

• FAR (Floor Area Ration) • Total built up area • Density • Open organized space • Number of units. • Fire safety provision :Underground water tank, Overhead tank, Fire ducts,

Fire escape, Fire detection system, Fire alarms, Hydrants c ARCHITECTURAL SCRUTINY Individual checks of Areas/Light/Ventilation/Height required with respect to applicable

rules for the following: Checks for following designations should be possible in respect of Residential housing/ Group housing:-

• Individual name of rooms: Drawing/Dining/Living , Kitchen, Bed room, Lobby, Store, Dress, Toilet, Study room, Pooja room , Loft , Terrace, Alcove , Plinth , Verandah

• Check no. of floors, • Check heights • Sections • Projections (on various sides and at various heights.): Plinth level, Roof level,

Parapet level /height, Ducts, Cutouts, Wall thicknesses • Openings w.r.t. height/ventilation • Joinery details • Door-Window sills, Lintel levels • Plumbing details and specifications. • Electrical wiring / main distribution box and their capacities • Basement areas and heights

In addition to the above list additional items are possible as per detailed requirements to be finalized during SRS.

D PUBLIC HEALTH CHECKS • Sewerage lines - location/ flow • Water lines Location/ flow • Traps location / types • Connection to main services.

e PROVISIONS FOR THE HANDICAPPED. The software should be able to ensure the checks required for provision of facilities for the handicapped in all buildings, wherever necessary, as per rules.

F COMPOUNDING The software should be able to scrutinize & finalize cases of compounding for:-

i) Revised plans ii) Completion cases.

g SINGLE WINDOW OPERATION The software should be able to make documents check with respect to the following:-

• No dues • Firefighting certificate • Reqd. Documents - Affidavits • Copies of allotment • Possession. • All required forms prescribed by GHMC • Identity check of owner, Architect, Structural Engineer, Plumber,


GHMC Page 112

Electrician, Contractor

34. Provision shall be made in the software for updating the forms periodically 35. Use of digital signature for approval of application at different levels should be

incorporated in the application system 36. Enable integration of the module with the following module to facilitate exchange of

data: Various NOCs, Property Tax, Vacant Land Tax, Water Tax, File Movement, Grievance Redressal, Court Cases, Financial Accounting, Assets & Inventory, Advertisement Tax, Trade Licenses, Project/ward works, and schemes.

37. System should integrate with the payment gateway system in such a way that payments pertaining to building permits can be made online

38. System to provide an option for print to payment details along with id as well as continue

39. System should define the service levels and the escalation matrix to officials regarding time limit for processing an application

40. Track delays in approval steps and maintain an audit log of the approval process steps.

41. System to generate an alert against each application when it nears the time limit for disposing it

42. The System should support the Mobile Governance for sending SMS to the applicant regarding receipt of application, receipt of payment, payment notice, field visit, renewal of permit, payment of extra fee etc.

43. System should be able to capture the preferred option of the applicant in getting information from the Town Planning Department

44. System should send SMS to the applicant regarding receipt of application, receipt of payment, payment notice, field visit, renewal of permit, payment of extra fee etc.,

45. System should generate a memo to be sent to applicant regarding the above requirement if the applicant do not possess email and mobile phone

46. System Should provide facility to print the memo in batch process 47. Online help should be available to the user for each system function. Topics covered

in the user manual shall also be available through the online help 48. Generate list of permits for which completion certificate has not been received after

the expiry of permits Reports

49. A comprehensive dashboard for Town Planning Authorities to monitor all the KPIs (Key Performance Indicators of the Department)

50. Generate report on total number of applications for building permit received during specified period

51. Generate report on total number of applications in which building permit was issued and or refused

52. Generate report on details of applications in which decision was not taken within the stipulated time as the case may be, from the date of receipt and the reasons therefore

53. Generate report on total number of applications received for regularization of unauthorized or deviated construction constructions

54. Generate report on total number of applications for regularization disposed of specifying the number of applications sanctioned and or refused, if refused, details of further action taken

55. Generate report on number of applications for regularization pending disposal 56. Generate other ad-hoc reports as and when required by the authorities.

GIS features 57. System should be able to generate a GIS id when the application is filed for building

permit, or regularization of building permit 58. System to capture the actual coordinates of the centre of the proposed building in the

lat and long fields provided in the field visit report 59. System should allow editing of latitude and longitude on a later date


GHMC Page 113

Notifications Contextual 60. System to enable printing of reminder alerts to permit holders in the above report list

of records if no e-mail or mobile number is available 61. System should send SMS or email to the permit holders if either the mobile number or

e-mail is available 62. System to provide the facility to update the details of notifications as follows: 63. System should allow attachment of digital photos (any number of photos with chosen

name) when occupancy certificate is given 64. System should allow viewing of digital photos for al! buildings for which occupancy

certificate is given 65. System to receive a completion certificate online 66. System should facilitate the architect to attach required documents and submit

completion plan as mandated 67. Facility to download all attached documents and plan as it is done in the permit

application 68. System should permit the overseer to input details of field visit by providing a check

list and to input his comment regarding the field visit and conforms that the submitted completion plan is ok?

69. System should allow to update the status of approval or rejection of the application for occupancy certificate

70. Facility to inform about the approvals or rejection status to the application by SMS 71. System to calculate the extra plinth area in the submitted plan and calculate the

additional fee for extra area. System to generate an SMS or print out for informing the architect regarding the extra fee payment and to permit the architect to remit extra fee if any for getting the occupancy certificate

72. System to generate an occupancy certificate as per the rules when the formalities are completed and allow the appropriate authority to digitally sign the occupancy certificate

73. System to permit the architect to download the digitally signed occupancy certificate 74. System should send the occupancy certificate along with details of completed building

(completion plan, area etc.) to other concerned departments? 75. If the applicant submits an application in a survey number which has been restricted,

can the system provide a warning? 76. If such warning is generated, system to allow the concerned authority to bypass the

warning by inputting the details of NOC / special sanction/ Government Order for construction

77. System to enable ail the officers dealing with permits to see such warning in their console

78. System should stop processing application when construction permissions are sought in restricted areas

79. Facility to system to accept application for regularization of unauthorized construction online

80. System should be enabled to check the violations in the building construction? 81. System to generate fee for regularization, if regularization has been ordered 82. System should allow overseer/concerned engineer input field visit details? 83. System should allow generation of regularization order 84. System should allow sending SMS and printing communication regarding field visit by

staff 85. System should able to accept input regarding refusal of application for regularization

of unauthorized construction 86. System should able to record the further action taken on refusal of application for

regularization 87. The system be able to interface with the property tax module to ensure the delete or

add the assessment


GHMC Page 114

Legal Case Management System

Sl. No Features

1 The implementation of Legal Cell Management System covers the following features: 2 Maintenance of Masters

a. Court Type b. Courts c. Standing Counsel/Lawyer d. Petition Type e. Case Category

3 Registration of Case a Once the case is received by the GHMC, the system should facilitate the legal cell to

enter the details in the LCMS system. The following details are to be entered by the user • Case • Petitioner (multiple) • Respondent (multiple) • Lawyer (can be changed during the life of the case) • Department

4 Allocation of case a The system should facilitate the legal department to assign case to Lawyers b The system should facilitate the legal department to assign the case to the concerned

department c The system should be able to calculate and enter the fees payable to the standing

counsel / Advocate based on the GHMC rates per case. d The system to have a facility to attach various documents related to the case 5 Details on Case hearing a The system should be able to enter the date of hearing b The system should be able to send alert to the officers w.r.t hearing date c The system should be able to enter the hearing details d The system should be able to Capture of judgment details e The system should be able to Linkage to the departmental data , Departmental Modules

to capture the information pertaining to the case f The system should have the provision to enter/modify the hearings and enter the next

hearing date. g The system should be able to update the hearing details after the hearing has taken

place 6 Filing Counter Affidavit. a The system should be able to capture the para wise remarks pertaining to the case b The system should be able to give alerts to the concerned officers to provide para wise

remarks online c The system should be able to send the material required to the advocate for filing the

counter affidavit 7 Interim Orders a The system should be able to capture all the details pertaining to the interim orders

issued by the court b The system should be able to capture all the instances like admission stage, hearing

(can be 1st, 2nd and so on) and after the Counter Affidavit is filed. c The system should be able to capture multiple Interim Orders till judgment state


GHMC Page 115

d The system should be able to capture the Interim Order type with the following values 1) Notice Order 2) Stay 3) Stay on Condition 4) Stay Made Absolute 5) Report File

8 Record Judgment a The system should be able to record the judgment of the case along with the final

judgment, the final installment is payable to the Standing Counsel. b The system should be able to capture the details of the arbitrators and fee payable to the

arbitrator in case of the judgment goes for arbitration c The system should be able to capture the details of the judgment type like

• Dismissal (in favor of corporation) • Opportunity (Enquiry by Commissioner) • Allowed (in favor of petitioner), • Arbitration (final order is treated as arbitration award), • Ex-parte order

9 Judgment Implementation a If the judgment requires some implementation on behalf of the GHMC, the same needs

to be captured by the application including the date of compliance and the compliance report.

10 Contempt a If compliance report is not submitted on time, then a contempt petition may be filed by

the respondent. Then the system should be able to capture the details of the contempt. 11 Appeals a The system should be able to capture the appeals filed by the GHMC if the decision is

not in favor of the GHMC. b The system should be able to capture the details pertaining to the acceptance or

rejection of the appeal. 12 Search Case a The system should allow to search the cases. b The search results should be based on the

a. View Case b. Edit Case a. Entering Interim Order details b. Enter Hearings c. Enter Judgment d. Enter Implementation e. Enter Disposal

13 View Case a The system should allow the viewers to view the complete case details of the case and

performing actions on the case. b The complete existing details of the case would be displayed. The user can choose the

following actions: a. Edit Case b. Print

c If the case is filed for an appeal and has a previous case number, then all the related case numbers(going up the case chain) will be shown as links.

14 Fee Module a The fee module will allow the Legal cell to view the fees payable/paid to the Standing

Counsel. b The system should allow to enter all legal Case fees which are paid for each case. c The system should have a provision to enter the additional fee paid along with the

reason for the additional fees d The system should allow entering the retainer fees automatically added to Fees payable

for each lawyer each month by a background process.


GHMC Page 116

e If the Standing counsel is deactivated from the system, then the Retainer fees and Legal case fees will no longer be generated from that time onwards.

15 Tracking Case a The system should be able to track the case based on the

a. Vakalat b. Filing of Counter Affidavits c. Interim Orders d. Hearings e. Judgment f. Implementation g. Closure

16 Reports a List of reports

1. List of cases department wise, zone wise and circle wise 2. List of cases category wise and zone wise and circle wise 3. Due reports - list of cases where PWR is due (sort by Zone circle,

Department) 4. Cases where Counter affidavit is due 5. Cases where judgment is to be implemented 6. List of cases where Government is the respondent 7. List of cases requiring personal appearance of Commissioner in

Contempt cases 8. Cases where enquiry has been ordered 9. Cases where Senior Advocate is engaged 10. Cases where payments made to Advocate 11. Cases where Stay is granted 12. Cases pending report filing 13. Cases pending judgment 14. Hearing list – weekly, monthly for zone, department and Standing

Counsel 15. List of appeal and contempt cases 16. List of time bound direction cases (tracked by implementation due date) 17. Judgment Information System – Judgment details zone wise, circle

wise, year wise, case category wise

17 Interfaces a The system should have a facility to have an interface with the SMS gateway to provide

notification to the parties on due dates b The system should interface with Finance System to capture the payment details of

appointed Municipal counsels c All departments should have access to this module to update/edit their respective case

details Works Module User Authentication



3. Details of Assets and estates owned by GHMC4. Details of Assets and estates leased by GHMC 5. Details of Assets and estates let out by GHMC 6. Details of all markets and shopping complexes owned by GHMC

7. Details of town planning and buildings and other cultural properties with historical significance


GHMC Page 117

8. Details of open lands of GHMC 9. Details of parking areas allocated in the GHMC area and jurisdiction

10. Details pertaining to the documents under the custody of the GHMC pertaining to town planning and buildings

11. Details of regular and contractual staff in Engineering Section 12. Creation, sanctions, approvals of budget online 13. Allocation of budget to concerned departments online

Tendering 14. The system should have a facility to register a bidder in a prescribed format online

15. The system should have the facility to receive and evaluate bids received and price discovery

16. The system should have a provision to maintain the database for contract monitoring and payments based on milestones accomplished

Reports 17. Report on total number of properties acquired by GHMC year-wise for the last 5 years

18. Report on total number of properties taken on leased to persons/parties year-wise for the last 5 years

19. Report on rent/lease collected on an annual basis from properties leased out. 20. Report on property-wise details pertaining to lease and rent 21. Report on total procurement details of the department year-wise for the last 5 years 22. Report on contracts executed 23. Report on progress of the project 24. Report on payments made to the contractors

Information to be placed on GHMC Website25. The website should have all the details pertaining to the contracts/works of the GHMC 26. The website should have property-wise details pertaining acquisition of properties 27. The website should have zone-wise details pertaining to GHMC development activities 28. The websites should have details pertaining to requests received and works implemented

Birth and Death Module User Authentication


2. Usage of Biometric Authentication Methods using PKI Technology. Creation of Master – Birth

3. Ability to maintain Hospital details (Addition/Modification/Deletion/ Search). 4. Ability to maintain Registrar details (Addition/Modification/Deletion/ Search). 5. Ability to maintain Birth Delivery details (Addition/Modification/Deletion/ Search). 6. Ability to maintain Birth Attention details (Addition/Modification/Deletion/ Search). 7. Ability to maintain details of Fees (Addition/Modification/Deletion/ Search).

Creation of Master – Death 8. Ability to maintain Hospital details (Addition/Modification/Deletion/Search). 9. Ability to maintain Cause of Death details (Addition/Modification/Deletion/Search). 10. Ability to maintain Attention Details (Addition/Modification/Deletion/Search). 11. Ability to maintain Registrar Details (Addition/Modification/Deletion/Search). 12. Ability to maintain details of Fees (Addition/Modification/Deletion/Search).

Creation of Master – Still Birth 13. Ability to maintain Hospital details (Addition/Modification/Deletion/ Search). 14. Ability to maintain Registrar details (Addition/Modification/Deletion/ Search). 15. Ability to maintain Birth Delivery details (Addition/Modification/Deletion/ Search). 16. Ability to maintain Birth Attention details (Addition/Modification/Deletion/ Search). 17. Ability to maintain details of Fees (Addition/Modification/Deletion/ Search).

Birth Registration 18. The system should provide interface to hospital / citizen facilitation centre for registering the

birth details 19. Ability to add/modify delete/Search the Birth details. The following details needs to be

captured and stored in the system. The following key fields needs to be captured:


GHMC Page 118

- Registration No - Registration Date - Sex of the Child (Male/Female) - Date of Birth - Name of the Child - Place of Birth - Permanent Address - Residential Address - Medical Attention - Hospital/Institution Name - Hospital/Institution Details - Order of Birth - Father’s Name - Father’s Occupation - Father’s Nationality - Mother’s Name - Mother’s Occupation - Mother’s Nationality - Birth Marks.

20. System should have ability to capture the informer details for both the birth and death registration and still birth registration

21. Ability to generate the Birth Registration Slip. It may contain the following fields: - Registration No. - Registration Date - Name - Date of Birth - Sex - Father Name - Mother Name - Address - Hospital/Non-hospital - Birth Marks.

22. System should make provision for payment to be made by the applicant and generate the receipt for the payment made

23. System should allow the operator of the facilitation centre / Hospital / Applicant to mark the documents that were submitted and allow to attach the documents against the application

24. On submitting the birth report the system should route the application as per the work flow and generate the alerts to the concerned officers

Death Registration 25. The system should provide interface to hospital / citizen facilitation centre for registering the

Death details 26. The system should be able to capture the informer details in the data base 27. The system should have ability to add/modify delete/Search the death details. The following

details needs to be captured and stored in the system. The following key fields needs to be captured:

- Registration No - Registration Date - Date of Death - Name - Place of Death - Permanent Address - Residential Address - Hospital/Institution Name - Hospital/Institution Details - Cause of Death

28. Ability to generate the Death Registration Slip. It may contain the following fields: - Registration No. - Registration Date - Name - Date of Death


GHMC Page 119

- Sex - Address - Hospital/Non-hospital - Remarks



Issuance of Birth and Death Certificate31. Ability to facilitate the capture the request for Registration certificate and retrieve details of

the applicant based on the Registration Number 32. System should have an ability to generate the digitally signed certificate for the registrations

already available in the database 33. System should be able to accept the application form from the citizens through multiple

delivery channels 34. System should able to accept the payment required for issuance of the birth and death

certificate 35. System should have an ability to query Birth Registration database based on the data

provided by the applicants and generate Birth Certificate. The certificate may have the following fields Name Sex (Male/Female) Name of the Father Name of the Mother Registration Number Registration Date Address Place of Birth, Date of birth and Birth Certificate No. in case of birth certificate Details of the mother and father Details of the hospital Date of Death, hospital details in case of death certificate

Still Birth Registration 36. The system should provide interface to hospital / citizen facilitation centre for registering the

still birth details 37. Ability to add/modify delete/Search the Birth details. The following details needs to be

captured and stored in the system. The following key fields needs to be captured: - Registration No - Registration Date - Sex of the Child (Male/Female) - Date of still Birth - Place of Birth - Permanent Address - Residential Address - Medical Attention - Hospital/Institution Name - Hospital/Institution Details - Order of Birth - Father’s Name - Father’s Occupation - Father’s Nationality - Mother’s Name - Mother’s Occupation - Mother’s Nationality

38. System should have ability to capture the informer details for both the birth and death registration and still birth registration

39. Ability to generate the Still Birth Registration Slip. It may contain the following fields: - Registration No and Registration Date - Name - Date of Birth - Sex


GHMC Page 120

- Father Name - Mother Name - Address - Hospital/Non-hospital



42. On submitting the birth report the system should route the application as per the work flow and generate the alerts to the concerned officers

Inclusion of Name at a later Date in the Birth Certificate43. The system should allow the operator to upload the request for inclusion of Child Name in

the Birth Register 44. The system should allow the operator / citizen to upload the relevant documents like

Signed Declaration by both the father and mother about the name of the child, Ration Card or any other address proof or Notarized affidavit on Rs.10/- Non-Judicial Stamp paper;

45. The system should allow to collect the required transaction fee and update the database real time

46. The system should able to generate the acknowledgement to the applicant on submission of the application;

47. On logging in, the concerned officer should view the details of the application status in the main screen

48. The system should provide alerts to the concerned officer for field verification and subsequently to the concerned higher official as agreed on escalation time

49. The system should capture the date and time of field visit 50. The system should able to send an SMS to the applicant informing the inclusion of the

name in the certificate Corrections of in the Birth and Death

51. The system should have ability to submit the application requesting for corrections in the Birth and Death Certificates

52. System should have ability to upload the relevant documents and required fee from the citizen

53. The system should have ability to enter of the applicant’s request and issue the acknowledgement to the submitted application

54. The system should have the ability to transfer the application along with enclosures, to the concerned Registrar of Births & Deaths of GHMC online

55. The system should prompt the concerned officer for field verification 56. The system should allow the concerned officer to sign the certificate digitally 57. The system should have ability to sending SMS message to the applicant informing that the

Non-availability certificate has been handed over to representative of the centre 58. The system should have ability to generate the digitally signed certificate and print

Issue of Non Availability Certificate59. System should have ability to upload the relevant documents and required fee from the

citizen 60. The system should have ability to enter of the applicant’s request and issue the

acknowledgement to the submitted application 61. The system should have the ability to transfer the application along with enclosures, to the

concerned Registrar of Births & Deaths of GHMC online 62. The system should prompt the concerned officer for field verification 63. The system should allow the concerned officer to sign the certificate digitally 64. The system should have ability to sending SMS message to the applicant informing that the

Non-availability certificate has been handed over to representative of the centre General Features

65. The system should have the inbuilt workflow for each service under this module 66. The system should provide PKI enablement for digital signatures 67. The system should provide the definite service levels and escalation workflow 68. The system should have an ability to generate unique barcode to each certificate issued

Immunization Alerts69. The system should able to maintain the immunization schedule and capture the details of


GHMC Page 121

infants due for immunization from the database 70. The system should be able to send an alert to the registered mobile number on the

immunization due date SMS Alerts

71. The system should be able to send SMS to the citizen at every stage of the service 72. The system should be able to provide the status tracking through SMS by retrieving the data

from the database Reports

73. Various reports information of Birth registrations based on Registration No, Registration, Date, Date of Birth, Issues , Non-Issues Month & Year –Wise

74. Reports births Sex Wise in a particular year 75. Reports on Father’s Literacy wise in a particular year 76. Reports on Father’s Occupation wise in a particular year 77. Reports on Mother’s Literacy wise in a particular year 78. Reports on Mother’s Occupation wise in a particular year 79. Reports on Year-Wise Issues 80. Various reports can be generated Year of Death-wise based on Date and Cause of death 81. Reports of Deaths based on Occupation-wise in particular year 82. Reports of Deaths based on Sex-wise in particular year 83. Reports of Deaths based on Cause of death-wise in particular year 84. Reports of Deaths based on Issued and not issued between two specified applied dates

D & O Trade License User Authentication


2. Usage of Biometric Authentication Methods using PKI Technology. Request for New/Renewal License

3. The system should capture the following fields in the application for New application and Renewal of Application form

4. The system should capture the License Category 5. The system should capture elements license, installation of machinery, property tax

details, plan details, purpose of license 6. System should allow attaching the supporting documents 7. If License type is 'New' can the system mandate all fields in the application form 8. Based on the License Type and License Category the system should display the Fee

details 9. If the license type is renewal the system display the fee based on date of renewal? For

example, if the date of renewal is prior to1 month of date of expiry, then no additional fee will be charged. If the date of renewal is during the last month of expiry then additional fee will be charged.

10. For Renewal of License the system should fetch the previous year's license application by entering the license number

11. System should allow editing the license application only after the date of issue of Renewal Notice

12. Based on the type and category of license can the system display if an NOC is required or not in the 'NOC' field

13. On entering the building number the system should fetch the building details, the taxes paid and other relevant information by integrating with accounts/revenue module?

14. On submitting the application the system should route the application to the concerned officer for verification of documents?

15. The system should have ability to facilitate for printing the acknowledgement capturing after submitting the application form for fresh license or renewal license

16. On submitting the application the system should have an ability to update the status of the application as 'Officer Allocated' and follow the work flow

Planning Field Visits


GHMC Page 122

17. On logging in, can the concerned officer view the details in the main screen like list of new requests pending for verification , List of New request , Pending for authorization , List of grievances to be addressed, List of alerts to be viewed , Consolidated list of requests handled

18. The system should have an ability to capture the date and time of field visit 19. System should have an ability to send an alert to the concerned supervisor when a

field visit is planned by an officer? 20. The system should have an ability to pop a reminder/email with the date and time of

the field visit 1 day prior to the visit and on the day of the visit Verification

21. Ability to fetch the license application by entering the application Number 22. Ability to display the list of license applications pending for verification in the main

screen of the concerned official 23. Ability to open the application by clicking on the application number on the list

available 24. Ability to capture the verification report in the remarks field in the application? 25. On approval the system should have an ability to update the status of the application

as approved 26. Once the field verification is approved the system should facilitate to send an

email/SMS alert to the applicant 27. Ability to send email/SMS alert on the application status, fee to be paid, officer to meet,

location to pay fee to the applicant 28. System should have an ability to update the status of the application as

'Communication Sent' after Notice/SMS/email is sent? Payment

29. System should populate a new window to make payment 30. Ability to accept the payment from different modes and different channels 31. System should display the fee and/or additional fee amount on the payment screen

with the payment options like cash, DD or Card 32. The system provide an option to print the receipt from the generated receipt screen 33. System should allow to issue the license only when payment status reflects as 'Paid'

Issue of Certificates 34. Once the payment is made the system should have an ability to route the application

for field verification 35. Once the field verification report is updated can the system route the application to the

AMOH / ALO/ AD(veterinary) for approval 36. The system should have an ability to send the application in the work flow to all the

concerned officer like Deputy Commissioner of the Circle / Zonal commissioner of the Zone

37. Once the concerned officer approves the request the system should allow to generate the digitally signed license certificate with unique license number

38. In case of rejection, the system should have an ability to generate a rejection certificate if the license request is rejected

39. Once the license is digitally signed the system send an alert to the applicant and ESeva / Me eSeva/ CSC for disbursement

Notice Generation 40. On login the system should display the list of license renewal notices to be sent on a

day with the following fields like Application Number , License Number, License Expiry Date, Date of Renewal of License

41. The system should have ability to generate bulk reminder notices 42. System should facilitate to send customized renewal notices to an applicant/a trader

who is conducting business without license 43. The system should facilitate to send the renewal notice through email/SMS to the

applicant 44. System should have an ability allow to issue a notice to the traders who are running

the trade without license


GHMC Page 123

45. System should have an ability to generate notice for defaulters to register trade SMS Facility

46. The system should able to capture / update the mobile number of the assesse 47. The system should be able to send an alert to the property owner with the

Advertisement tax details like amount to be paid, due date for payment, etc.. 48. The system should be able to generate and send mobile acknowledgment when the

tax is paid 49. The system should be able to send reminders if the assesse fails to pay the tax on

time Payment Collection through Handheld Devices

50. The system should able to push the date to the handheld device from the database and pull the data from the handheld devices through GPRS

51. The system should be able to post the payment collection information to the database and generate the acknowledgement for the payment

52. The system should be able to generate device wise payment details every day GIS

53. System Should be able to generate a GIS id of the advertisement hoarding 54. System to capture the actual coordinates of the centre of the electrical pole in the lat

and long fields provided in the field visit report 55. System should allow editing of latitude and longitude on a later date

Reports 56. Can the system generate reports for the following

• License Type • License Category • License Year, • Defaulters List, • Number of Applications Received • Number of Rejected Applications • Number of Certificates Issued • Number of Cancelled licenses • Location wise list of trade licenses • List of Notices Served • List of Pending Authorization, Pending Verification, • Planned Field Visits on the day/ week • Demand Collection & Balance, Integration Requirements

Veterinary User Authentication



3. Details of Dog and other animal pounds in the GHMC area 4. Details of Non-vegetarian trades in the GHMC area 5. Details of slaughter houses maintained by GHMC 6. Details of regular and contractual staff 7. Details pertaining to veterinary hospitals in the city

Issue of Pet Licenses to Pets 8. The system should also have a facility to edit, modify and delete the record by the user

9. The system should have a provision for maintaining information pertaining to number of pet licenses issued.

10 The system should have a form for recording information pertaining to pets licenses Other Information

11The system should have provision for recording number of complaints received and redressed on each issue namely: • Dog Menace


GHMC Page 124

• Monkey Menace • Pig Menace • Stray Cattle Menace

12 The system should have provision to record information on Animal Birth Control and Anti-Rabies vaccination activities conducted in dog pounds

13 The system should have provision to record information on number of animal brought into the pound and the number of animals released

14 The system should have provision to record information on the number of vaccinations undertaken in the in the animal pounds.

15 The system should have a provision to record details pertaining to anti-mortem and post-mortem reports from slaughter houses

16 The system should have a provision to generate reminders for non-payment of rent against each property

17 The system should have a provision to send alerts to the user in case a rental or lease agreement is nearing termination or completion

Reports 18 Report on total vaccinations done in dog pounds for the last 5 years 19 Details pertaining to total number of ABC and AR activities done for the last 5 years 20 Report on the hot spots identified on animal menace in the city 21 Report on total number of complaints received and redressed for the last 5 years

Information to be placed on GHMC Website22 The website should have all the details pertaining to slaughter houses of GHMC 23 The website should have details pertaining to dog and animal pounds in the city 24 The website should have zone-wise details of people to be contacted

Entomology User Authentication



3. Details of hospitals treating communicable diseases in the GHMC area 4. Details pertaining to chemicals and equipment procured

Information Disease Control (Epidemiological Inputs)

5. The system should provide form for the hospitals to send the details of the diseases in terms of cases received (suspected and confirmed)

6.

System should have a provision to send alerts to the officers on incidence of diseases (suspected and confirmed cases) – Field Assistant, Asst. Entomologist (Circle), Senior Entomologist (Zonal), AMOH of the concerned circle, Deputy Commissioner of the circle and Zonal Commissioner of the Zone

7. System should have a provision to record on disease incidence for the following diseases – Malaria, Filariasis, Japanese encephalitis and Dengue

8. The system should have a provision to upload the action taken report with parameters, time lag and gap between receipt of complaint and action taken (SMS based system)

Mosquito Control (Entomological Inputs)

9. The system should have provision for recording details pertaining to sentinel sites both fixed and random

10. The system should have provision for recording details pertaining to mosquito menace hot spots

11. The system should have provision for generating report on hot spots based on sentinel sites, entomological indices and trend analysis

12. The system should have provision for generating weekly report on larvae and adult mosquitoes for the following categories of mosquitoes namely, Anopheles, Culex, Ades, Mansonia and Armegeris.

Public Interface 13. The system should provide for daily news feeds on disease incidence and mosquito menace


GHMC Page 125

from news on the internet using key words

14. The system should have a provision for feedback form that can be received from Ward members and citizens.

Reports

15. Weekly report on hot spots based on sentinel sites, entomological indices and trend analysis

16. Weekly report on larvae and adult mosquitoes for the following categories of mosquitoes namely, Anopheles, Culex, Ades, Mansonia and Armegeris.

17. Weekly Report on the disease hot spots in the GHMC area 18. Weekly Report on the Mosquito hot spots in the GHMC area

19. Weekly action taken report with parameters, time lag and gap between receipt of complaint and action taken

Information to be placed on GHMC Website20. The website should have all the details pertaining to disease and mosquito hot spots 21. Information pertaining to hospitals treating communicable diseases

22. Information pertaining to officers who can be contacted for controlling mosquitoes in all circles

23. Information pertaining to key activities of the department including fogging and spraying operations

Solid Waste and Transport

• The system should link with the ISWM project of GHMC • The system should generate the GPS reports

Other Services under Health & Sanitation Department Dispensaries

1. The website should have all the details pertaining to disease and mosquito hot spots 2. Information pertaining to hospitals treating communicable diseases 3. List of staff available in the dispensaries 4. System should be able to capture No. of cases treated in the dispensaries

Public Toilets

5.

The system should be able to record the information of the public toilets in the public toilet masters

• Public toilet Code • Location Code • Maintained By • Number of seats • Scheme name • Facilities available like power and water

6. The system should able to capture the information pertaining to visits of sanitary inspectors

7. The system should be able to capture the contract details like Contract period, Contract amount, contractor name

8. System should be able to capture the staff maintaining these public toilets Sweeping

9. The system should have provision to record details pertaining to all the contractual and regular staff of the department

10. The system should have the details pertaining to various sweeping packages in the GHMC area

11. The system should have details of all contractors and agencies hired for sweeping GHMC roads

12. The system should track the attendance of all the staff pertaining to sweeping department 13. The system should capture the mobility plan of the sweeping packages

Festival Duty Allocation 14. The system should maintain a calendar of all major festivals where GHMC involves its staff 15. The system should maintain the details of in-charge officers allocated to these festivals 16. The system should capture all details of expenditure and receipts if any during the festival


GHMC Page 126

activities Information Technology – Portal Management General Specification

1. The solution should be compliant with • NIC website development guidelines issued by DoPT • UN Guidelines for Websites (UN eReadiness Report 2007)

2. The system should run on multiple browsers (IE 6.0 and above, Firefox 2.0 and above,etc.)

3. The system should be designed for access through browser-based systems and must impose minimal requirements on the client device of different operating systems including mobile phone/ handheld interfaces.

4. The system should be designed to have satisfactory performance even in connected on low-bandwidth (28 kpbs)

5. The system should be designed in manner that operational data is not lost in case of any failure of equipment or communication network.

6. The solution should be able to integrate with Statistical Tools and Reporting Tools 7. The solution should maintain a database of frequently asked questions (FAQ)

8. The solution should provide data dictionary along with the description of the objects, fields, and field types

9. Upgrades of the solution (fixing of defects or adding new enhancements or releasing new versions) should have zero/minimal impact to the installed system and should not affect the current version adversely

10.

The solution should support front-end modification for the following items: • Look and Feel(e.g. color, font size, font style) • Logos • Display Language

11. All applications must be fully integrated including enhancements and updates – no duplicate data entry at any level

12. The system should exist in an open environment providing enough flexibility in selecting the hardware as well as operating environment

13. The system must be capable of presenting usages service wise in a tabular and graphical form for easy understanding and analytical purposes

14.

The system should be modular in nature. Each activity must be handled by a specific module so that it could help in gradual

implementation of the system. Each module should have the capability of running as a standalone as well as an

integrated environment if other modules are installed and implemented

15. The system should operate in a full on-line / interactive environment with instant reflections of the missing or erroneous input

16. The system should be able to recover with rollback capability to the data in case of any system or communication failure (visualize last transaction)

17. System shall provide for ad-hoc spreadsheet and database functions or support the import and export of spreadsheets and databases, such as MS Excel and MS Access and others as defined

18. On-line maintenance is posted “real time” and immediately reflected in information provided by the system

19. System shall provide the ability to scan images and documents and make them available by item number for review

20. System should be user friendly with ease of navigation through various systems modules

21. Applications should be consistent in format and screen design Function keys should be consistent within and across applications for maintenance and

screen switching

22. Full editing and validation for data entry must be standard. In case of data in error a descriptive message with corrective action is displayed

23. Provides abbreviations or wild card characters in search mode 24. Provides help functions at the screen and field level for all screens and menus 25. Screens are capable of reverse as well as forward scrolling 26. Purging, backups, restores, etc. are performed at System Administrator level not at user level


GHMC Page 127

27. The system must be fully documented to reflect the latest software revisions and provides future update information. Whatever functionalities are tweaked / created by the SI will have to be updated in the user manual or in the Help pages or both

28. List of error code information and messages must be present 29. Must generate full audit trails

30. System must provide the ability to generate user-defined / adhoc reports using a report generation tool that directly accesses the business system data to develop executive level reports. Users must be able to save such queries with unique names for future use.

31. Facility to access the application should be role based

32.

Application must support Digital Signatures of any of the Certifying Authorities registered under the Controller of Certifying Authorities, and must be modifiable as per the changes made by the respective Certifying Authorities on the structure of the Digital Signatures issued by them. The Digital Signatures used in the application must provide the Time Stamping of the act

of Digitally Signing a document as mandated by the IT Act The Smart Card reader or the USB Token, carrying the Private/Secret Key, must be

activated by Biometric identification instead of a PIN / Password based system User Management

33. Citizens should be able to register with unique user name and password to access all the applications as per access rights

34. System should have the functionality to define users of the portal. 35. Portal should offer single entry point for stakeholders and applications relevant to them.

36. Portal should have a Scheduling module for all the users and facility to keep record of meeting notes, MoMs etc., viewable to respective attendees and notified over email and SMS

37. Scheduler should have facility to edit/update the schedule and accordingly the notification should be sent to the attendees via email and SMS

38.

Users should be mapped to the applications relevant to them. The portal will provide single sign on feature so that the end user need not individually logon to separate applications. Users can be categorized into following categories: Employees Management Vendors Citizens Government Agencies

Login related Functional Requirement Specification

39. Should allow only the authentic users to login to the system through the use of: User id and Password combination

40. Should display the login page as the first page when the user enters the application. 41. Should give a welcome message once the user is able to successfully login to the application.

42. Should give an error message once the user provides wrong login information and ask the user to re log in.

43. System should have the functionality to define users of the portal. 44. Portal should offer single entry point for stakeholders and applications relevant to them

45.

Users should be mapped to the applications relevant to them. The portal will provide single sign on feature so that the end user need not individually logon to separate applications. Users can be categorized into following categories: Employees Management Vendors Citizens Government Agencies

User ID and Password Combination

46.

The user login and password both should be a combination of following: Alphabets Symbols Numeric

47. The user name and password should have a minimum defined characters – Suggestive is eight

48. Should not create duplicate user ids


GHMC Page 128

49. Should not allow the user to have the same password for more than 30 days 50. Should generate alerts for password expiry from five days of actual expiry 51. Should not allow same user id and password 52. Should not allow blank spaces while setting user id or password 53. Should notify the user in case the Caps Lock is on 54. Should notify the use if Num Lock is on 55. Should generate user id based on the criteria of – Rank, etc. 56. Should allow a user who forgets password to access the password retrieval mechanism

57. Should allow only the machines whose match id is registered with the application enter the application

58. Should block the user to enter into the application if he puts in wrong login info continuously thrice. Account lock out problems will be sorted out by a designated Administrator. Hence, this feature is to be provided Administration module.

Monitoring and Reporting related Functional Requirement Specification

59. The defined user should be able to use the application to query the Departmental Databases using the name or other details of the applicant.

60. Should allow the application to retrieve various information from the individual databases and aggregate it

61. The application should support the monitoring in both the occurrence, when an event or time driven activity is triggered.

62. Should be able to automatically generate the defined reports to the concerned authorities at regular time interval.

63. Should be able to generate Process Report on a regular time interval. This report should include process wise the number of service requests initiated, number of requests completed, number of requests pending and the number of requests under process.

64. Should be able to generate SLA Report on regular time interval, this report should give information related to centre wise details of no. of SLA met and user wise details of no. of SLA breached.

65. Should be able to generate Performance Report on regular time interval, this report should give information related to user wise, details of no of service processed against the no of service received.

66. Should be able to generate Attendance Report on regular time interval, this report should give information related to user attendance.

67. Should provide a search option to the authorized users so that he can search the information which should be sorted according to Date, Primary keys (such as date range, Service type, etc.)

68. Should allow the stakeholder to review the progress report and give his comments online. 69. Should provide the facility to print and e-mail the report. 70. Should provide a printer – friendly version automatically for all pages. Search Facility

71. The functionality will help the in searching (Quick & Advanced) for all the services provided by GHMC

72. Application shall provide all the functionalities mentioned in RFP Access Rights Management

73. The Access to the databases, which will store all the information related to the applications, the verified details, and the digitally signed deliverables, should be tightly governed and monitored. The integrity and security of these databases is of paramount importance.

74. These databases will be accessed by various stakeholders at different stages of processes. The access parameters are defined based on the Create Read Update and Delete (CURD) Model for access management.

Notification System ( Alerts, Important Events, Reminders and Activity Calendar or Tasks Service) 75. Application shall provide all the functionalities mentioned in GHMC RFP.

76. In case of a new event, the system shall automatically generate alert in advance to all concerned offices for all applications.

77. The system should provide for creation and sending user alerts/events/reminders to identified group/subscribed users/offices

78. The system should provide for scheduling the activities and maintaining calendars with reminders


GHMC Page 129

79. The system should provide for sending the alerts/events/reminders either to the respective officer handling the department or in charge

80. The system should provide for sending alerts/events/reminders in the form of an email, or SMS to the registered phone or as an alert in the application once the user logs into the system or all available modes

81. The system should provide the officers to view the tasks that he/she had set in calendar like court appointments, and administrative related tasks

82. In case of new event, system shall automatically generate alert in advance to all concerned officers for all Applications

email / Messaging System

83.

The system should provide the Messaging system as a role based communication system. It should provide the general mailbox features such as: Address book Send / receive mail with attachments Creation / deletion of folders Moving mail to folders Spell check Mail filters Calendar Rich text editor Auto responders Signatures Server side mail filters Spam filters Support the mail protocols (IMAP and SMTP)

84. The system should provide the entire above general mailbox features in email systems 85. The system should enable the user to create or import the organizational hierarchy 86. The system should allow the selection of the user list from the organization hierarchy 87. The system should enable the user to create personal address books, personal groups 88. The system should allow the user to send messages to groups

89. Template creation and selection for message standardization should be provided by the system

90. The system should provide the user to select the option for read receipt 91. The system should provide for encrypting the message 92. The system should enable the user to print the message in printer friendly format

93. Searching of messages from archive based on message subject and between two dates should be provided by the system

94. Cell phone alerts subscription on receipt of new email in inbox should be provided by the system

95. Usage statistics at all levels and departments should be provided by the system Knowledge Management

96. System should provide for submitting learning documents to the knowledge management system; digital versions of archived documents should be incorporated into the system

97. System shall allow user to view data in logical sections in the KM related to tagging 98. System shall allow user to search documents using multiple search criteria 99. System shall present results in order of relevance 100. System shall allow storing of document (Image & Metadata)

101. System shall support for viewing a large number of file formats without the need of having the parent application. The system should support all commonly used file formats as MSOffice, Acrobat, TIF, JPEG, GIF, BMP, etc.

102. System shall provision to edit the document Metadata 103. System shall provide versioning of the document 104. System shall provision for marking comments 105. System shall allow role based access to the documents 106. System shall allow users to view and participate in forums Employee Grievances Functionality


GHMC Page 130

1. System shall allow for role based access to users

2. System shall auto escalate the case to higher officials, if the defined service levels are not adhered by the concerned stakeholders

3. System shall allow the user to file the grievances 4. Each grievances shall be assigned the unique no (ATN) for further tracking 5. There shall be separate email id to file the grievances

6. Senior officers shall decide To initiate the enquiry process To direct the concerned branch to redress the grievance

7. For option (vi-a), system shall allow the senior officer to appoint the independent adjudicator System shall allow to capture the details of the verdict of the adjudicator

8. For option (vi-b), system shall allow the senior officer to assign to the concerned branch officer for further action & Redressal

9. System shall allow the employee to trace the status grievances based on ATN 10. System shall allow the adjudicator to upload the final verdict 11. System shall notify the Sr. Officer regarding the final verdict. 12. System shall allow the user to upload the final action taken report 13. System shall auto update the status, if any, based on the workflow defined

14.

There shall be facility to search the details based on following fields: Date ( from – to ) Application No (from – to) Pending Grievances Employee Name

15.

There shall be facility to generate the report based on: Date Range (from – to) Pending Grievances (Office wise) Registered Grievances Action Taken Report

16. The system shall allow the user to download/save or print the reports or searched records 17. System shall be compatible to electronic/ digital pen

Citizen Grievances User Authentication


2. Single sign-on should be provided to the application. Functionality

3. System shall allow for role based access to users 4. System shall allow the applicant following option 5. To fill the Grievances online Through personal visit GHMC 6. Citizen shall also download & print the filled form and submit to the GHMC

7. System shall allow the operator ( if applicant submits the written application) To fill online web based form

8. To download / save/ print the form in pdf or word format 9. To upload the filled offline form into the system

10. System shall capture the personal detail of the applicant and each application shall be assigned the unique no (ATN) for tracking

11. System shall allow the applicant to track the application based on the ATN 12. There shall be separate email id to file the grievances

13. Senior officers shall decide To initiate the enquiry process To direct the concerned branch to redress the grievance

14. For option (vii-a), system shall allow the senior officer to appoint the IO

15. System shall allow the user to capture the details of the investigation by IO. It shall also allow to upload the supporting document, if any

16. System shall allow the Senior Officer to verify the report for further action

17. For option (vii-b), system shall allow the senior officer to assign to the concerned branch officer for further action & Redressal of grievances


GHMC Page 131

18. System shall allow to capture the applicant feedback (satisfied or dissatisfied) In case of dissatisfaction the relevant details shall be captured

19. System shall auto escalate the case to higher officials, if the defined service levels are not adhered by the concerned stakeholders

20. System shall allow the complainant to trace the status of grievances based on ATN 21. System shall have the provision for status tracking through SMS 22. System shall auto update the status, if any, based on the workflow defined

23.

There shall be facility to search the details based on following fields: Date ( from – to ) Application No (from – to) Pending Grievances Applicant Name

24. The system shall allow the user to download/save or print the reports or searched records

25. System shall be compatible to electronic/ digital pen Reports 26. Report on total number of grievances received by GHMC month-wise 27. Report on action taken on total number of grievances resolved by GHMC month-wise

28. Report on Pending grievances with SLA violation and officers list with whom the grievance is pending

29. Report on Zone wise Pending and resolved complaints Information to be Placed on GHMC Website30. The website should have all the details pertaining to the complaints/grievances lodged 31. The website provision to query on various parameters pertaining to grievances 32. The website should have provision to know the status of the grievance

33. The websites should have facility to send reminders to concerned officers in form of SMS/emails

34. The websites should have facility to send SMS/email to the Citizen whenever there is a change is status of his/her grievance submitted

Right to Information Functionality 1. System shall allow for role based access to users 2. System shall allow the applicant following option

To fill the Grievances online Through personal visit GHMC Citizen shall also download & print the filled form and submit to the GHMC office

3. System shall allow the Operator ( if applicant submits the written application) To fill online web based form To download / save/ print the form in pdf or word format To upload the filled offline form into the system

4. For option (ii-a) system shall accept the online payment through credit card / net banking / DD / treasury deposit etc. If the payment is other than credit card / Net banking, system shall generate the receipt

based on this the payment is done at CFC The system shall allow the CFC to check the receipt no to accept the payment for online

RTI request (if payment is done through Treasury deposit / DD etc.) 5. System shall capture the personal detail of the applicant and each application shall be

assigned the unique no (ATN) for tracking 6. System shall allow the applicant to track the application based on the ATN 7. System shall allow the PIO to approve / reject the request based on the information sought

If rejected / approved the applicant shall be informed via SMS or email 8. System shall allow the PIO to send the request to different departments / internal branched for

information Information available Information not available

9. For option (viii-a), if the no of pages are more than as per the charges inform the applicant for additional payment and submit the report


GHMC Page 132

10. For option (viii-b) the PIO shall inform the applicant and provide the reason for the non-availability of information

11. System shall allow the APIO to receive alert regarding the requested information from the PIO 12. System shall allow the APIO to upload the necessary information and forward the same to the

PIO 13. System shall auto escalate the case to higher officials, if the defined service levels are not

adhered by the concerned stakeholders 14. System shall auto update the status, if any, based on the workflow defined

There shall be facility to search the details based on the field like Date ( from – to ) Application No (from – to) and Pending RTI

15. There shall be facility to generate the report on Total RTI registered Total RTI pending

16. The system shall allow the user to download/save or print the reports or searched records 17. System shall be compatible to electronic/ digital pen

Payment Options High level functionality 1. All requests for the online payment directed by the citizen should go through this module 2. The system should be able to track success/failures of all requests that go through this

module. 3. It should provide an unified interface to the external payment gateway interface 4. It should handle the response received from payment gateway and forward the same to the

collection module. 5. It should handle response parameters that comes after the payment transaction has been

completed by the external payment gateway, and update status of the transaction based on the response

6. Display success/failure message to the Citizen. 7. It should keep a record of all transactions that go through it. It should also keep a record of all

successes and failures. 8. Reports ( transactions list )- date wise and status wise should be provided 9. Reconciliation between Payment Gateway and Collection Module should be addressed

Dependencies 10. This Module would be dependent on the following: 11. External payment gateway 12. GHMC Collection Module (online interface)

System Overview 13. From the GHMC (www.ghmc.gov.in) website, the citizen selects the service for which the

payment is to be done. Following the details entered (e.g. bill number), the citizen is presented with his bill details. When the citizen chooses the ‘Payment’ option, the following process flow is initiated: The citizen is re-directed to the Payment Gateway. On the gateway, the citizen is provided the various options, along with the transaction fee

for each option. 14. The citizen selects an option and proceeds with the transaction. Possible options are:

Credit Card Debit Card Direct Bank Debit

15. Based on the selected option, the citizen is re-directed to the relevant payment site (e.g. the bank website) to complete the transaction.

16. On successful login, the payment details (including transaction charges) are auto-populated on the payment site.

17. On successful completion of the transaction (e.g. the credit card processing, direct bank debit etc.,), a unique transaction ID is generated and passed back to the Payment Gateway payment gateway.

18. 19. The gateway, in turn, passes it to GHMC module where the transaction receipt is generated. This receipt includes the transaction-ID from gateway for future reference and reconciliation.


GHMC Page 133

Payment request forwarding 20. The collection module will send the request with the payment information to the payment

gateway 21. Once the request is received from the collections online interface, payment gateway calculates

the Transaction fee and displays the same to the user. The user is shown an option to proceed with the payment or go back to the collections module. The following is the process description.

22. Collections will add the following parameters in the request Transaction ID Transaction Number Revenue head Transaction amount (Bill amount) Return URL (Collection Module) Transaction amount (Bill amount for payment gateway to calculate transaction fee)

23. The request parameter should also have valid characters as desired by Payment Gateway24. Once the request parameter is formed for payment gateway, control is directed to the specified

URL of the payment gateway. 25. All the above parameters are sent as hidden parameters and a request is sent (post) to the

gateway URL Payment updation 26. Once the transaction has been completed by Payment Gateway, a response is sent back to

the Collections module. The process description is as follows. 27. The payment gateway will send the following parameters in as response

Transaction ID Transaction Number Transaction amount (Bill amount) Bank id Bank merchant id Transaction type Currency name Transaction date Authorization Status Revenue head

28. Payment gateway should Receive and Read the Payment Response message at the Return URL

29. Generate the ‘Sum value’ using the received in payment response and validate it with the ‘sum value’ received in the payment response.

30. If they match, proceed to the next step else should display a payment rejection message to citizen

31. If ‘sum value’ matches, online collections should update original record in its system based on the status received in the payment response

32. The status for that transaction is updated in the Collections Module.Error code 33. A system should display messages as follows.

Success Invalid Authentication at Bank Invalid Input in the Request message Payment Gateway is waiting for Response from Bank Error at Payment Gateway

Reports 34. There would be a need to view all the transactions

Date wise Week wise Service wise Month wise Quarterly Half yearly Annual

Status Tracking


GHMC Page 134

35. User would select any date range and the status (All/success/failure) as input. Output would be list of transactions that should appear in the following format: Transaction reference number Revenue head Bill number Amount Transaction fee Total amount Date

Refund file updation 36. Once the reconciliation between Payment Gateway and Collections Module is done, for all

those transactions where customer pays but has not come through to collections due to various reasons (one of it being internet connection loss), a refund should be provided for the same.

37. The data should be sent in a refund format that is in the following manner: 38. All such refund records are stored in a refund file which is named in a specific format and is

uploaded to Payment Gateway at the specified location. Payments 39. Citizen has to avail the service by utilizing the bill payment facility offered by their

bank/institution. 40. Once registered for such services, Payment Gateway will get bill data on a regular basis for

registered citizens and the same comes across in the bank’s website (e.g. SBI website) 41. At the bank website, the citizen chooses the service (e.g. Property Tax), enters Bill number

following which he will be presented with bill details. 42. When citizen chooses “Payment” option, he is directed to Payment Gateway 43. Payment Gateway will show payment options and the transaction amount along with

transaction fees for payment. 44. Citizen confirms payment and is directed to payment site 45. Once the payment transaction is completed, the transaction reference from payment site is

passed on to Payment Gateway which then passes it to the citizen at the bank website (e.g. SBI website) for future reference.

46. End of Day, Payment Gateway sends the transactions to collections where receipts are generated for each successful transaction.

47. Once receipts are generated at collections, billing system is updated. 48. Once billing system is updated, the citizen gets an SMS message saying that payment has

been received and receipt can be seen/obtained at Chennai corporation website 49. The citizen has to then log on to Chennai corporation website to see and print the receipt. He

can do so by entering his property id or bill number at the Property tax facility in the corporation website

50. Batch updation of transactions received from Payment Gateway to collections is covered in Collections requirement specifications

File Monitoring System

Record File 1. The system should be able to capture the following fields in the ‘Record File’ Screen

File No. (Will be system generated on submitting the file) Inward No. (Will be system generated on submitting the file) Outward No. (Will be system generated on submitting the file) File Type Concerned Department Service Concerned Officer File Submission Date (Generated on submission) File Submission Time (Generated on Submission) Remarks Priority File Creation Department (Generated on Saving) File Creation Office (Generated on Saving)


GHMC Page 135

Attach Supporting Documents

2. The system should pop an alert to the concerned officer before submission of the file 3. The concerned officer should be able to edit the file after it is save 4. On submission the system to route the file to the superintended for approval? 5. Once the concerned officer approves the file the system to route the file to the concerned

officer in the hierarchy 6. Once the concerned officer submits the file the system generate an alert to whom the file is

sent Track Files 7. On login can the system display the following,

New Files Received New Files Pending for Approval Priority Files Files Pending for Submission Files Pending for Modification

8. The user should be able to choose any of the above to open the list 9. System should allow the user to fetch a file by entering the file number 10. System should allow the user to search and fetch a file using the File No. , Inward No.,

Outward No., File Type, Department, Section, Officer-in-charge , Date of Creation, Date of Movement, Mode Received, Priority Status, etc. options

11. The user should be able to view the movement of the file with the File No., Inward No, Outward No., File Type, Created date, Mode of Received, Departments Moved, Sections Moved, Officer Handled, Date of Movement, Time of Movement, Status Priority, Remarks and Supporting Documents

12. Can the system pop an alert to the concerned officer for file disposal based on the file type? 13. Can the system allow for individual/bulk disposal of files? 14. When the concerned officer chooses a file to dispose can the system send an alert to the

concerned superintendent of the department in-charge of the file?15. Can the system mandate approval from the concerned officials for disposal of files? 16. On choosing disposal of file, can the system update the status of the file as 'Disposed'? 17. On disposal can the system generate an alert to the approving authority for file disposal and

the concerned department superintendent in-charge of the file? Reports 18. Can the system generate reports for file movement using the File No. , Inward No., Outward

No., Department Section, Officer In charge, Date of Creation, Date of Movement, Mode of Received, Priority Status, Period parameters

Masters 19. Can the system allow to maintain/view/edit the following masters

File Master File Number Sequencing Inward Number Sequencing Outward Number Sequencing

Administration Functionality – Employee Information System


GHMC Page 136

1. The system should have a provision to maintain the details pertaining to the employees under following heads Employee’s data like name, DoB, qualification, work experience, date of joining, date

of retirement, salary structure, employee grade, bank account details, leave, transfer, loan, promotion, training details, Conferences/Courses attended/on Job qualification added etc.

Employee postings, current department, email ID, Mobile phone number, Immediate Superior details and HOD details etc.

Annual Confidential Report (ACR) of employees Property returns filed by employees Attendance details and balance leaves of employees

2. The system should have a provision to assign a unique employee identification no # to each employee

3. The system should have a provision to track and store Bio-Data of all employees 4. The system should have a provision to allow respective cadre controlling authorities to

update the personal information and resume details of their employees online 5. The system should have a provision to notify the employee on updation of his/her details

via email/SMS/letter 6. The system should have a provision to allow employees to view their salary structure,

GPF, Rent, ACR etc. details 7. The system should have a provision to apply/approve/reject the leave application online

Interface 8. The system should interface with Finance System (ERP) to update the details about the

salary, loan, PPF, advances etc. 9. The system should also interface with Land and Estate Dept. for SLF for Municipal

accommodation allotted to employees. The system should interface with the GHMC ERP & web portal for updation of personal details

10. The system should be able to interface with the messaging system for sending notification or any communication to the employees via email/SMS/letter

11. The system should capture the attendance of all employees through Biometric device and interface with Finance System for salary and leave calculations.

Recruitment – In case of compassionate appointment cases (As applicable) 12. The system should maintain the details/report on vacant posts available, Category and

Cadre wise of various department. Reason for vacancy (death, VRS, etc.,) 13. The system should maintain the details/report status of requests sent to APPSC and

Government for recruitments14. The system should maintain the details/report short listed applicants’ list from APPSC,

Employment Exchange, Family members, etc., for recruitments 15. The system should maintain the details/report on Bio-Datas and applicant files received

from APPSC, Family member of the deceased/Nominee and Employment Exchange (Privacy to be maintained)

16. The system should maintain the details on selected applicants’ list from the recruiting agencies

17. The system should allow departments to place the online resource request (Online recruitment form). This is applicable for all types viz., permanent, daily wagers, contractor etc.

18. The system should assign unique identification no# for each application received for recruitment

19. The system should display vacancy, job details etc. on GHMC Portal. 20. The system should have the facility to apply online for any vacant post available with due

details 21. The system should a facility to generate the consolidated list of resource requirement

grade wise, post and department wise 22. The system should a facility to generate and print online offer, and medical letter for

selected candidate signed off digitally 23. The system should have the facility to upload all required document for recruitment like

RR, applicant file received from APPSC etc. RR will be linked against the post while applicant file will be linked against individual resume or application

24. Change the status of applicant to regular employee/daily wager/adhoc contractor


GHMC Page 137

(whichever is applicable) on successful completion of medical, vigilance and police verification

Interface 25. The system should interface with the GHMC web portal and display and accept online

application against vacant post 26. The system should be able to interface with the messaging system for sending notification

or any communication to applicants or employees via email/SMS/letter 27. The system should interface with vigilance system to get the details of employees, who

apply for jobs internally. Promotions, Transfers, Leaves, Deputation and Resignation

28. The system should maintain the details pertaining to promotion of employees with their name, date of promotion, new salary structure, department, grade etc.

29. The system should maintain the details pertaining to leave and transfer information of an employee

30. The system should maintain the details pertaining to vigilance case that are pending against any employee

31. The system should maintain the details pertaining to deputation and resignation details of employees

32. The system should maintain the details pertaining to aid in decision support for promotion, transfer of personnel against the available vacancies

33. The system should maintain the details pertaining to aid in decision support for allowing the employees to proceed for deputation

34. The system should allow employees or authorized person to place online request for transfer, promotion or deputation for themselves and their subordinates

35. The system should allow proper category selection (in case of transfer), like on rotation, administration grounds, in consonance with the existing policy, if any.

36. The system should allow auto generation of list of personnel due for promotion / retirement etc. on set days, prior to actual dates

37. The system should allow Establishment department to initiate transfer, deputation and promotion of personnel online. System should refer to the vacancy list available across organization

38. The system should allow updation of the personnel details, if individual is transferred, promoted, proceed on deputation or study leave.

39. The system should have the facility to generate transfer and promotion letter online based on the criteria

40. The system should allow to process and sanction leave/deputation request online. Employees should be able to apply for leave/ deputation online

41. The system should allow the concerned authority to relieve the employee in case of resignation/ transfer/ promotion/deputation/study leave etc. System should check all the required documents and NOC, in case of something missing, the same should alert the official at the time of relieving

42. The system should have the proper workflow management and should allow respective authority of concerned department to provide NOC during processing of Terminal Benefit and Resignation request

43. The system should notify the concerned person and authority regarding promotion, transfer, leave sanction, resignation acceptance, deputation etc. via email/SMS/letter

44. The system should allow the concerned authority to create and update the ACR for each employee. It should fetch common information directly from Employee personal details like qualification, work experience, date of joining etc.

Interface 45. The system should interface with the GHMC web portal display and accept online request

for transfer, promotion, resignation, deputation etc. 46. The system should be able to interface with the messaging system for sending notification

or any communication employees via email/SMS/letter 47. The system should interface with the vigilance department system to get NOC for

promotion, transfer etc. 48. All departments should have access for this module to perform intra-department transfers/

postings Salary Processing


GHMC Page 138

49. The system should maintain the details about TDS, GPF, salary disbursed etc. for each employee along with his/her nominee for receiving the due payments

50. The system should maintain the details about statutory report relating to Income tax, PF etc.

51. The system should aid in auto calculation of salary of employees (all type) based on category and grade of employees. It should consider the leave, loan installment, rent details, TDS, GPF, Attendance etc. while calculation

52. The system should calculate and disburse terminal benefits to employees or their legal heirs

53. The system should have a provision for auto update the entry in general ledger against the salary paid to employees

54. The system should have the facility to generate and print salary slip and same should be sent to employees’ email /SMS/letter

55. The system should provide a facility for the employee to search, view and print their salary slip online for past months also

Interface 56. The system should interface with Finance System (ERP) for details like loan, GPF, salary

structure etc. 57. The system should interface with Land and Estate for SLF details 58. The system should be able to interface with the messaging system for sending notification

or any communication to the employee via email/SMS/letter59. The system should interface with Biometric based attendance system for salary

calculations. 60. The system should interface with leave management system for salary calculation

Performance Appraisal 61. The system should maintain the details about the employees position, tenure of posting,

their reporting/reviewing and accepting authorities (wherever applicable) names, designation, place of posting and their tenure.

62. The system should maintain the details about assigned/ expected task to be detailed through self-appraisal or otherwise in prescribed Performa by respective employees which is to be reported upon and reviewed by concerned officers

63. The system should notify the employee whose appraisal is due and allow them to do self-appraisal and same should be sent to concerned officer for reporting and reviewing via email/SMS/letter. On approval, the same should be sent to Establishment department for further necessary action and records

64. The system should capture the details/status(yes or no) of property returns filed by the employees

65. The system should capture the vigilance status, Currency of Punishment etc. Interface

66. The system should interface with Vigilance department, property section 67. The system should be able to interface with the messaging system for sending notification

or any communication to the employee via email/SMS/letter Training & Development

68. The system should maintain the details about various agencies and experts in various fields imparting training for sharpening skills and professional development

69. The system should have the facility of online application and approval for group of the employees for the various training to be imparted to them

70. The system should have the facility for the department to update the calendar of trainings and brief description of training, venue and imparting agency

Interface 71. All departments should have an access of this module 72. The system should interface with the messaging system for sending notification or any

communication to the employees via email/SMS/letter 73. The system should interface with the Inventory Management System for tracking existing

infrastructure in office Recruitment Rules

74. The system should maintain the details about job profile of various positions of various categories for various cadres

75. The system should maintain the details about job evaluation, essential qualifications and


GHMC Page 139

experience for performing the job 76. The system should maintain the details about existing number of post of various

categories of various cadres with pay scale 77. The system should maintain the details about anticipated creation of vacancies and

revision of qualification, experience, pay scale 78. The system should maintain the details about organizational promotional hierarchy with

defined feeder grade 79. The system should have the facility for existing posts and anticipated creation of

vacancies 80. The system should have the facility to define and manage organizational promotional

hierarchy 81. The system should generate the report and format to share with APPSC & GoAP

Interface 82. All departments should have an access of this module for requirements and updation of

existing RRs or framing of new RRs Sanctions of Petrol, Landline phone connection to officers, Study permission, NoC for passport/Visa

83. The system should maintain the details about vehicles allotted, vehicles used, Phone numbers, educations details etc. for each employee

84. The system should maintain the details about statutory report relating to monthly utilization, Income tax, PF etc.

85. The system should aid in auto calculation of expenditure of employees (all type) based on category and grade of employees

86. The system should calculate and disburse terminal benefits to employees along with their salaries/reimbursement

87. The system should auto update the entry in general ledger against the payments paid to employees

88. The system should have the facility to generate and print salary slip and same should be sent to employees’ email /SMS/letter

The system should provide a facility for the employee to search, view and print their details slip online for past months also

Interface 89. The system should interface with Finance System (ERP) for details, salary structure &

other benefits etc. 90. The system should be able to interface with the messaging system for sending notification

or any communication to the employee via email/SMS/letter 91. The system should interface with Biometric based attendance system for salary & other

reimbursements calculations. 92. The system should intra department interface with other departments for various levels of

approvals. Disciplinary Proceedings – Unauthorized Absence/Bribery/Bigamy cases of ministerial staff of GHMC

93. The system should maintain the details about employee’s data like name, DoB, qualification, work experience, date of joining, date of retirement, salary structure, employee grade, bank account details, leave, transfer, loan, promotion, training details, Conferences/Courses attended/on Job qualification added etc.

94. The system should maintain the details about employee postings, current department, email ID, Mobile phone number, Immediate Superior details and HOD details etc.

95. The system should maintain the details about Annual Confidential Report (ACR) of employees

96. The system should maintain the details about attendance details and balance leaves of employees

97. The system should track and store attendance of all employees 98. The system should allow respective cadre controlling authorities to update the personal

information of their employees online 99. The system should notify the employee on updation of his/her details via email/SMS/letter

100. The system should allow employees to view their records for disciplinary proceedings and action taken

101. The system should have the facility to apply/approve/reject the leave explanation online


GHMC Page 140

Interface 102. The system should interface with Finance System (ERP) to update the details about the

salary, loan, PPF, advances , deductions, etc. 103. The system should also interface with Land and Estate Dept. for SLF for Municipal

accommodation allotted to employees. The system should interface with the GHMC ERP & web portal for updation of personal details

104. The system should be able to interface with the messaging system for sending notification or any communication to the employees via email/SMS/letter

105. The system should capture the attendance of all employees through Biometric device and interface with Finance System for salary and leave calculations.

106. The system should be able to notify all the actions initiated and capture explanations submitted by the employee

Out Sourced Employee Information SystemEmployee Details

107. The system should maintain the details about Job profile of various positions of various categories for various cadres

108. The system should maintain the details about Job evaluation, essential qualifications and experience for performing the job

109. The system should maintain the details about Existing number of post of various categories of various cadres with pay scale

110. The system should maintain the details about Employee’s data like name, qualification, work experience, date of joining, salary structure, employee grade, bank account details, leave, etc.,

111. The system should maintain the details about Employee postings, current department, Immediate Superior details and HOD details etc.

112. The system should maintain the details about attendance details and balance leaves of employees

113. The system should Assign unique employee identification number to each employee 114. The system should Track and store resumes of all employees 115. The system should Allow respective cadre controlling authorities to update the personal

information and resume details of their employees online 116. The system should Notify the employee on updation of his/her details via email/SMS/letter117. The system should Allow employees to view their salary structure , PF, etc., details 118. The system should Have the facility to apply/approve/reject the leave application online

Recruitment 119. The system should maintain the details/report about, Outsource agency Details like

Registration details, Service Tax registration, EPF Registration Details, ESI registration details, PAN Details

120. The system should maintain the details/report about, • Vacant posts available, Category and Cadre wise of various department • Resume and applicant file received from Outsourced agency • Selected applicants’ list from the recruiting agencies

121. The system should allow departments to place the online resource request (Online recruitment form).

122. The system should Generate the consolidated list of resource requirement department wise

Transfer, Leave, and Resignation 123. The system should maintain the details/report about Leave and transfer information 124. The system should allow employees or authorized person to place online request for

transfer, 125. The system should allow Establishment department to initiate transfer of personnel

online. System should refer to the vacancy list available across organization 126. The system should have the facility to generate transfer letter online. 127. The system should allow to process and sanction leave, Employees should be able to

apply for leave 128. Allow the concerned authority to relieve the employee in case of resignation, System

should check all the required documents and NOC, in case of something missing, the same should alert the official at the time of relieving

Salary Processing


GHMC Page 141

129. The system should maintain the details about PF, ESI, salary disbursed etc., for each employee along with his/her nominee for receiving the due payments , Statutory report relating to Income tax, PF etc.

130. The system should, • Aid in auto calculation of salary of employees (all type) based on category and

grade of employees. It should consider the leave, TDS, GPF, Attendance etc. while calculation

• Auto update the entry in general ledger against the salary paid to employees through Outsourced agency

• Have the facility to generate and print salary slip and same should be sent to employees’ email /SMS/letter through outsourced agency

• Provide facility for the employee to search, view and print their salary slip online for past months also

Performance Appraisal 131. The system should maintain the details about the employees position, tenure of posting,

their reporting/reviewing and accepting authorities (wherever applicable) names, designation, place of posting and their tenure.

132. The system should maintain the details about assigned/ expected task to be detailed through self-appraisal or otherwise in prescribed Performa by respective employees which is to be reported upon and reviewed by concerned officers

133. The system should maintain the details about the system should notify the employee whose appraisal is due and allow them to do self-appraisal and same should be sent to concerned officer for reporting and reviewing via email/SMS/letter. On approval, the same should be sent to Establishment department for further necessary action and records

Interface 134. The system should interface with Finance System to update the details about the

loan, PF, ESI 135. The system should be able to interface with the messaging system for sending

notification or any communication to the employee via email/SMS/letter 136. The system should capture the attendance of all employees through Biometric device

and interface with Finance System for salary and leave calculations. 137. All departments should have access for this module to perform intra-department

transfers/ postings Media Information Management System

1. The CPRO should have a separate email id for corresponding with media offices, media persons, GHMC officials and sending news clippings to GHMC officials, political functionaries etc.

2. The CPRO should have separate micro website for display of information like Press Releases, News clippings related to GHMC, Audio-Video Clippings, advertisements etc.

3. The CPRO should have facility to upload / delete the content of its micro website. 4. The CPRO is the nodal point for release of advertisements on behalf of all the

departments, offices, zones, divisions of GHMC. It should have a system which takes care of the entire process right from receiving the advertisement material from the issuing department, till the final payment for insertion of advertisement in media.

5. The system should have facility for formal request and text from the advertisement issuing department

6. The system should have facility for receipt of budget for publication/ broadcasting/telecasting of advertisement

7. The system should have facility for availability of budget for the above 8. The system should have facility to release advertisement to empanelled advertising

agencies 9. The system should have facility to routine advertisement to be issued on turn to

advertising agency 10. The system should have facility to invite for submission of design 11. The system should have facility to invite all agencies for submission of designs 12. The system should have facility to submit bills for publication and processing thereof 13. The system should maintain the details about the empanelled agencies 14. The system should maintain the Work allotted to the empanelled agencies


GHMC Page 142

15. The system should maintain the Advertisement, NIT, brochures, booklets etc. published for which departments, allotted agency etc.

16. The system should maintain the bills submitted by the agencies like bill date, work done, Amount etc.

17. The system should maintain the pending dues to the agency and by the agency 18. The system should maintain the budget received from the department and availability of

funds 19. The system should maintain the insertion of advertisements newspaper clipping, radio or

TV spot Print and Stationery Requisition Management System Sl.No Functionality

1. The system should maintain the details/reports about types of stationery and print 2. The system should maintain the details/reports about Department wise requisition details 3. The system should maintain the details/reports about Daily total production for every

departments 4. The system should maintain the details/reports about Details about printed information like

language, quantity, department etc., 5. The system should maintain the details/reports about Details about the dispatch like date,

time, quantity, item details, department etc., 6. The system should maintain the details/reports about Pending jobs like item details, date

of requisition, quantity pending, assigned to, reason etc., 7. The system should maintain the details/reports about Vendors like name, address, items

deals in, ordered qty, date of order, items ordered etc., 8. The system should Allow all departments to place the requisition for stationery and printing

online 9. The system should Have the facility to consolidate the requisition, item wise ( separate for

stationery and printing) 10. The system should Have the facility of setting and assigning jobs for printing as per the

priority 11. The system should Maintain the requisition details department wise 12. The system should Assign unique requisition id for each new requisition. The further

tracking will be based on this unique id 13. The system should Allow the P&S department to edit the requisition placed by respective

departments 14. The system should Notify the respective departments on editing of requisition placed by

them 15. The system should Allow department to track the status of their requisition 16. The system should Allow P & S department to place demand to respective departments for

budget against print and stationery requisition

17. The system should Capture the details about the bills submitted by the agencies like bill date, work done, Amount etc.

Stores Management System Maintenance of Masters (Stores System)

1. Stores Definition, including Bin Locations Item and Item Types Details Supplier Details Item and Item type details Supplier Details Unit of measurement and unit of measurement category details.

2. Material Indent (Requisition): Raised by any department/user within GHMC on the Stores for material

3. Material Receipt Receipt of items against a PO Physical Stock Taking


GHMC Page 143

4. The system should have a provision to issue is against a material Indent for the following purposes. Issue for consumption Repairs and maintenance Capital work in progress Issue to contracts Inter Store transfer Sale Written-off Returns of materials

5. Purchase Journal Voucher Creation of Bills against material received

Reports 6. Stores Ledger report 7. Material Receipt 8. Material Issue 9. Goods returns register 10. Integration with the e-Procurement Platform. 11. The Inventory Management System will be integrated with the following modules:

Financial Accounting System Asset Management System Works Management System

Stores Details 12. Material Indent 13. Material Indent Issue 14. Receipt of Material (Material Receipt Note):

Receipt against a PO Stock Adjustment

15. Receipt of Assets (Asset Receipt Note) 16. Purchase Journal Voucher (Supplier Bill) 17. Integration with Asset Management System for tracking of asset-wise consumption of materials.

Integrated Procurement Management System User authentication

1. System should be able to provide access to only register users of GHMC 2. The system should support user authentication and support user authorization

Creation of Master 3. System should create masters for the following 4. List of items required on day to basis 5. User departments 6. List of authorized staff for placing the procurement order 7. List of vendors and 8. List of scheduled rates

Request for order placing 9. The system should be a Web-based and the GHMC users should be able to access it

from anywhere at any time 10. The system should be self-explanatory while placing the request and minimizes data entry

of the operations and selecting the items 11. The Software should guide the officers through the procurement planning process 12. The system should be able to submit the procurement request to the procurement officer 13. The system should assist in monitoring of the procurement process by the designated

GHMC officials 14. The system should be able to send the request to the concerned officer for approval in

case of high value procurements Budget Management


GHMC Page 144

15. The system should maintain a library of scheduled items along with their description and rate. Items can be further classified into works and heads. Additionally it should be possible to break down items into sub items up to any level.

16. The system should facilitate analysis of rates of an item based on the coefficient of units consumed by unit quantity of an item.

17. Then system should facilitate high level estimates of a targeted works to be used primarily for budgeting purpose.

18. The system should enables preparation of yearly and supplementary budgets considering major, minor, sub-minor budget heads and schemes

Procurement Management Pre Tendering

19. The system should map the proposal initiation to approval process 20. The system should map administrative process resulting in financial approval 21. The system should map the proposal initiation process and workflow with a view to their

approval 22. The system should enable the calculation of the probable cost of a product, program, or

project, computed on the basis of available information Tendering

23. The system should facilitate the preparation of draft tender papers with standard and specific terms of reference with associated workflow for the approval of the requirement

24. The system should capture information on the Rate of the item procured in the past, Bill of Materials, Current schedule of rates (SOR) items, rate, specifications etc.

25. The system should facilitate publishing of e-tenders with external interfaces, acceptance tender online and off live along with tender price, EMD through ECS and link the same.

26. The system should be able to generate report for placing the advertisement 27. System should facilitate preparation of evaluation statement (comparative statement) and

parametric analysis based on possible quantity variation and other criteria. Post Tendering

28. 1. Issue of purchase order 2. The system should facilitate award of Contracts including issue of work order with

system generated contract serial number and other compliance requirements like EMD etc.

3. Document number: The ‘document number’ for the ‘Purchase Order ‘can be automatically generated or filled out manually if required

4. Order Reference: An external reference number of the Supplier can be displayed in this field for reference purposes.

5. Price List: Per ‘Purchase Order’ a specific ‘Pricelist’ can be selected for the Supplier that will apply to all lines on that ‘Purchase Order’.

6. Document Status: Different statuses can be selected to indicate in what phase of Procurement the Purchase Order currently is. Examples of document statuses are ‘Draft’, ‘Not Accepted’, ‘Underway’, ‘Completed’, ‘Closed’, etc.

7. Form of Payment: Different ‘Forms of Payment’ can be selected to indicate the invoice payment.

8. Payment terms: ‘Payment terms’ is defined to indicate when an invoice needs to be paid

9. Apart from the above attributes the ‘Purchase Order’ also specifies many other attributes like:

• what goods need to be purchased • the name of the Supplier • ordered quantity • prices of the goods • when the products were ordered • when they are promised to be delivered • which warehouse the products must be received in • who and where the invoice needs to be received • what tax needs to be applied


GHMC Page 145

• Which department the products are required for

29. The ‘Purchase Order’ indicates the ‘Summed Line Amount‘(the sum of the amounts on the Sales Order without taxes being added) and the ‘Grand Total Amount’ (the sum of the amounts on the Sales Order including taxes).

Goods Receipt 30. A ‘Purchase Invoice’ can be generated automatically from a ‘Goods Receipt’. 31. Movement Date: Indicates the date when the product moved into inventory, as a result of

a receipt of the ‘Purchase Order’ from the Supplier. 32. Storage: The location in the GHMC where the product that was received from the Supplier

will be stored. 33. When the ‘Goods Receipt’ document is generated and completed, the stocked quantity of

the product is updated. 34. The system should maintain inventory of assets 35. The system should be able process monthly cash accounting system. This should include

preparation of vouchers, Statutory Register and Expenditure Monitoring. Purchase Invoice

36. A ‘Purchase invoice’ should be generated once the inventory is fed into the system. 37. The system should generate the purchase invoice automatically. The automatic method

can generate a ‘Purchase Invoice’ based on a ‘Purchase Order’ or a ‘Goods Receipt’. 38. ‘Goods receipt’ can be automatically generated from a ‘Purchase Invoice’.

Reports 39. The application should provide industry standard reporting functionalities including

dashboards, scorecards and other static reports including but not limited to: 1. Budget Request Report. 2. Budget Sanction report. 3. Budget Request vs. Sanction Report. 4. Budget Sanction vs. Expenditures Report. 5. Vendor Payment Abstract Repot 6. Vendor Payment Detail Report. 7. Abstract Cost Overrun Report 8. Detail Cost Overrun Report.

40. Stage Wise Work Status :(AA (Administrative Approval),TS (Technical Sanction),Tender Publish , Work Order, Completed, Abandoned, Not Required) etc.

Content & document management module:

1. The application must provide best of breed content and document management functionality which would be used by GHMC (B&R) for storing, searching, retrieving, security, collaboration, versioning and traceability of documents covering all processes. It should also significantly enhance the compliance requirements of GHMC's processes. Some of the key functionalities in the application would be as under:

2. The system shall provide both a web-enabled interface (thin client) and user access interface via Windows Explorer (thick client)

Interface 3. Must support standard browser like Internet Explorer, Firefox including providing multiple

views of the folder and document content according to user preference and IT permission sets.

4. Must support drag and drop to move documents from one folder to another folder 5. Must provide the capability to automatically collect / upload document files from specific

file directory 6. The automatic file collection must provide flexibility in defining rules of what files get

uploaded Content Types

7. The user can upload more than one document files for a document object


GHMC Page 146

8. For the multiple file document, the user can download each individual document file or download all of the document files

9. Features for annotation must be provided for image files. Must allow ability to seamlessly view the image file content in its native form using a built-in viewer

10. For the multiple page TIF files, the image viewer must be able download a particular page at a time to reduce time taken to download image files with many pages

Image Annotation 11. The security model must allow to separate access rights to content from access right to

annotations. 12. Must provide capability to display the audit trail on who has done what to each of the

annotation object 13. The user can add as many annotation to the various pages of the image file

Document Handling14. Must support content reuse through management of links as pointers to a single

document

15. Must support filing of a document into multiple folders

16. Shall allow the users to link different documents as compound document. The document relationship can be pointing to a latest major version, latest minor version or a specific version of the document

17. When editing, the document must be checked-out from the repository (locked) preventing other users from making changes at the same time

18. Users must be able to continue viewing the document when a document is checked out. The GUI (user interface) must provide a visible symbol indicating the checkout and an attribute to indicate who checked out the document

19. Shall provide offline capabilities allowing users to check out a document offline and then check in the documents with the repository when online

20. Must support de-duplication, in which only 1 copy of the document file will be saved, in the situation that the user file into a duplicate copy of the exact document. Must support DITA publishing standard

21. Must provide capability to annotate PDF documents without requiring any additional license

Architecture 22. Must provide a common integrated repository to handle all types of enterprise

content management, including documents, web content, digital assets, collaborative content, document images, records etc.

23. System must provide the ability for content files to be stored in standard file systems and meta data in industry standard RDBMS

24. Must have built-in fault tolerance, load balancing and high availability

25. System must provide support for both Java, .NET and XML Web Services API

26. System must provide support for CMIS standard

27. The system shall have the capability to manage pervasive information types and process rich media format information (audio, video), common formats (PDF, Word, PowerPoint etc) and electronic records

Retrieval and search facility: 28. Content in the repository should be indexed by object properties and/or full text 29. Should use wildcard in specifying the document search criteria30. Search must be able to be conducted across folders and distributed repositories 31. Can specify whether to search for documents filed in a folder and / or its sub-folder 32. indexing and retrieval based on metadata must be provided for all file formats and

document types 33. Users can save queries for reuse or sharing as required.

Security And Auditing 34. Users should be able to assign rights to objects. Users should be able to assign rights to

individual users or groups of users


GHMC Page 147

35. If documents are secured, the presence of documents should not be visible when a user without access rights undertakes any searches on the document store

36. Must provide the flexibility to define if the user can download the document 37. Must provide the flexibility to define whether the user has the right to file documents into a

folder 38. Must provide the flexibility to define if the user can create sub-folder in the folder 39. Ability to authenticate user against LDAP (Lightweight Directory Access Protocol)

directory services 40. Must provide ability to capture all operations on documents in a audit trail

Platform And Industry Standards 41. Provide out-of-the-box integration with market-leading application servers and portals.

List the App Server and Portals supported 42. Should support inbuilt application server and database for Document management 43. Provide support for J2EE,,NET, XML and Web Services44. Must provide CMIS and REST support

ER Features 45. Content Manager should support multi-level versioning, folders and sub folders 46. Security has to object level even on the annotations 47. Content Manager should have in built image applet viewer which can open electronic and

image file formats 48. Content Manager should have web 2.0 based Ul with drag and drop features of adding

docs to the content repository 49. Web based Ul to access document management system 50. Content duplication to be checked at the content repository level

Management Information System Sl.No Features

1. The application should provide MIS Solution which meets MIS Requirements of GHMC 2. The system should be able to capture all the MIS requirements of the 3. The system should be able to generate customized reports and populate the same to the

officers of the GHMC by mail 4. Besides, Reports / Information / Data are being generated at Head Office, the system should

also be able to add more reports to the application as per the requirements during the course of time

5. The Solution should provide tools for capturing data already resident in the systems of the GHMC

6. The Solution should be able to Interface / Download / incorporate data from any of the Systems / Solutions deployed by the GHMC

7. The system should support with facility for data entry manually, verification thereof with maker-checker facility.

8. The Solution should populate database gaps at the point of entry / origination 9. The Solution should be web based with all User Friendly and Security Features viz. 10. , Access Control, Password Control, and Report Extraction Control etc. 11. The Solution should provide BI (Business Intelligence) Tool, capable of various

multidimensional analysis across parameters, periods and dimensions as may be user defined.

12. The Solution should facilitate drill down / drill-up functionalities to enable user to analyze the reports

13. The Solution should provide Users in Head Office Departments, and all other offices, dashboard to view and generate MIS Reports in line with the requirements at various levels. The Solution should provide information in forms - combination of numerical and / or graphical forms through dashboard, as the user may desire.


GHMC Page 148

14. The Solution should provide a Reporting tool to facilitate report design, generation, distribution and archiving.

15. The Solution should support Backup of Data / Information / Reports etc. 16. There should be ETL tools to extract and upload data from the existing Systems 17. The Solution should facilitate users to generate their own Reports through queries. 18. The system should be web-based on-screen user interface should be through an information

portal, with standard features such as a search engine, input screens and option to generate reports / output in various formats by the Users.

19. The system should also support generation of reports centrally at scheduled intervals and printouts distributable in various File Formats viz. Text, Excel; PDF etc.

Reporting & Analytics Module (DASH BOARD) The desired reporting and analytics functionality of the Application must include its ability to monitor progress, understand trends, provide management insights and decision support at all points in the life cycle. These capabilities must encompass all the modules of the application Role based views of Reports must be possible It must deliver the following capabilities: (a) Ad hoc query, (b) Managed Reporting, (c) analysis, (d) Dash-boarding, (e) Alerting. All functionality related to the creation and consumption or reports, dashboards, scorecards, alerts, ad hoc query and analysis should be available entirely over the web

REPORTING 1. Needs to support the following report creation process: an end user can create and save

a report/query using the ad hoc query interface and then pass it on to a professional report author for enhancement and subsequent publication. The professional author should be able to open the saved report/query and enhance it using the professional report authoring interface

2. Needs to be able to generate report output in various formats such as Microsoft Excel, Adobe® PDF, XML, HTML, and CSV.

3. Needs to have the ability to embed 81 content into office productivity tools like MS Word, MS Excel and MS PowerPoint and the ability to refresh this data using secure access to the CIW

4. Multi-Channel Report Publishing Capability: Should provide a scalable reporting server capable of generating richly formatted reports from multiple sources, in multiple formats (MS Excel, PDF, XML, HTML) published on multiple channels - specifically by email, to portals, and to mobile devices.

5. Should make it possible to deliver the very same reports that are published on the web to be delivered to mobile devices without the need for report rewrites

6. Should offer the ability to easily create multiple page - multi query reports e.g. where data on the second page uses a completely independent query from a different data source and has independent prompts

7. Should integrate with a mapping solution, or have one of its own, to show data conditions on Indian maps. It should be possible to define custom (i.e. customer specific) zones/areas on the map and associate these with zones/areas in the data

8. Needs to support graphical views in the form of chart types such as line, column, pie, radar, Pareto, quadrant, gauges etc. These should be available for report creation as well as dashboard creation

9. End users should be able to add comments/remarks on a report and other users should be able to view the comments history, including the user id and timestamp of comment creation

10 Should offer the ability to circumvent the intuitive interface to use SQL commands and MDX directly (for authorized IT or power users)

11. Should have the capability to schedule reports on the basis of a time calendar i.e. by hour, day, week, month, etc.

12. Should have the capability to schedule reports on the basis of a trigger or an occurrence,


GHMC Page 149

such as an email, database refresh, etc. 13. Should come with a search facility to perform an advanced search on all content,

including the data content of reports Citizen Service Centers Sl.No Functionality

1. Application should have provision for and allow the Citizen Service Centre Operator(CSC operator) to login in to the GHMC application after following defined authentication check –

using User Login and password 2. Operator should log into the application through the GHMC portal using valid user name and

password 3. The application should have provision of a database for Citizen Service Centre with the

following details – Unique CSC ID Location of CSC

4. The application should have provision of a database for operators of Citizen Facilitation Centre with the following details –

User name and password Employee ID

5. The application should have provision of a database for all operations / transaction performed by Citizen Service Centre with the following details –

transaction ID for service request unique CSC ID details of operator date and time of transaction

6. The application should have separate section for CSC Operator for logging into the application

7. The application should have the provision for CSC Operator to update records (add, delete and modify) as mentioned in point (3)

the Updation function should be allowed only through prescribed authentication mechanism through login by user name and password

confirmation of Updation should happen only through transaction ID and password

final submission of Updation request should happen only though signing by digital signature of CSC operator

all such transaction done by CSC operator should be saved and stored by GHMC application

8. GHMC application should not allow the CSC operator to modify the system login password through their user ID and password

9. GHMC application should have mandatory provision for changing of CSC operator password every 30 working days by the CSC operator

the GHMC application should send reminders for change in password from the 25th day of password setting

last 3 password should not be used alphanumeric codification should be made mandatory with minimum of 8

characters 10. GHMC application should block the system login in case of wrong user ID and password

provided for login for 3 consecutive attempts the system should allow the CSC operator to reset the password for such

instances where login is blocked and re-activate the login once the password has been reset

11. the system should allow CSC operator to access the online application form, download it and fill the details in the form on behalf of citizen at the e district application

12. The system should allow CSC operator to submit the form on behalf of citizen at the e district


GHMC Page 150

Sl.No Functionality

application only by using transaction ID and password assigned for the purpose 13. The system should allow CSC operator to issue the acknowledgement receipt generated by

the e district application on successful service request registration 14. The system should allow CSC operator to log in to the e district application to track the status

of service request application whether the application has been accepted, rejected or sent for verification

15. The system should allow CSC operator to view timely alerts generated against the service request in case of any clarifications required or in the case of delay in the service delivery

16. The system should allow the CSC operator to provide final service delivery at the CSC to the applicant against the service request made

17. The system should allow the CSC operator to access the GHMC portal and help citizen obtain information on various aspects related to services offered at the CSC.

18. The system should allow the CSC operator to generate a daily transaction record at the end of the day and print it if required

19. The system should allow the CSC operator to generate a periodical money deposition report against the money collection at the centre

20. The system should allow the CSC operator to generate a periodical money deposition report against the money collection

21. The system should not allow the CSC operator to make any changes in the service request / delivery against the service request at any point after the service request has been successfully registered with the system

any changes in the service request any changes in the service output any changes which comes in conflict with FIFO (First – In- First Out) logic any other changes which is deemed unlawful on the part of CSC operator (CSC

operator) 22. The system should not allow the CSC operator to enter / view the departmental database or

make any changes in the same at any point of time 23. The system should have a provision for making service complaint request by the CSC

operator in case any module of the GHMC application is not working properly the system should route such request to system administrator defined for the

GHMC application 24. The system should automatically log of the CSC operator from the GHMC application in case

of ‘inactivity’ for more than 30 minutes. 25. The system should maintain all the transaction record session wise for all the Citizen

Facilitation Centre under the GHMC application 26. The system should have a provision to store all ‘Machine ID’ with the GHMC application and

should allow the CSC operator to enter the application only through the registered machine with the defined ‘Machine ID’ the system should allow the CSC operator to register the Machine ID on the GHMC application the system should save the ‘Machine ID’ entered by the CSC operator only after providing the digital signature for the purpose

Integrated Transport Management System

Sl. No Features User Authentication

1. The system should create a authentication to the designated users of the ULB Masters

2. The System should provide interface for a. Details of various vehicles showing the vehicle Number, Type, Make and Age


GHMC Page 151

Sl. No Features b. Details of vehicles attached to the departments within GHMC c. Details of vehicles attached to the concerned officers of the GHMC (Employee

attachment) d. Details of the vehicles with status of ownership (owned/hired/leased) e. Details of Drivers against each vehicle f. Recording of maintenance sheds and garages owned and visited by GHMC g. Details of vendors from whom vehicle parts are procured h. Details of vendors who have hired and leased vehicles to GHMC i. Details of vehicle parts and peripherals (Inventory) j. Details of Petrol Bunks used by GHMC for fuel usage

Vehicle Scheduling and Movement3. The system should provide interface to capture the availability of vehicles 4. The system should provide a facility to track the mobility of the vehicles (Both those

attached to the officers as well as those moving on a specific tasks and official duties) 5. The system should track and provide the daily running of the vehicle with details in

running kilometers 6. The system should have a facility to track the vehicles in various shifts (Shift-wise

details) 7. System should allow to capture the start kilometer and end kilometer of the vehicles

used in a single day (Details to be keyed by the driver/Officer who is driving/using the vehicle)

8. The system should have a provision for the officer to generate petrol/diesel/gas vouchers for the vehicles (Fuel-wise details have to be captured against each vehicle)

9. The system should have a provision to generate report on the visits to garage/shed for repairs

10. The system should have details pertaining to the repairs undertaken on a vehicle on a monthly basis to assess the life of the vehicle

Daily Reports

11. System should facilitate to display the break up cost and total cost incurred for the day at the end of the daily report. For example, Cost of hired vehicles, Cost of equipment, cost of daily laborers and Sum total of all costs

12. System should facilitate concerned officer to submit the daily report on the scheduling and movement of vehicles

13. The system should automatically send the daily reports to the higher officers in the workflow

14. System should allow the sanctioning officer to approve the total cost incurred for fuel/maintenance/other repairs etc.

15. On approving the total cost incurred the system to auto update the accounts management module

Emergencies and On-Demand Work16. The system should facilitate to search for available vehicles to schedule on

demand/emergency work?

17. The system should allow the concerned officer to create a schedule 18. If a hired vehicle is chosen to carry out the emergency work, the system should facilitate

to trigger an SMS to the supplier to send the vehicle 19. On completion of the work the system should allow the concerned officer to submit the

daily report Planning Field Visits

20. The system should facilitate to view the demand field work requests and list of planned visits


GHMC Page 152

Sl. No Features 21. The system should prioritize the request based on the date of redressal for on demand

work 22. If field visit is not completed 1 week prior to date of redressal can the system pop a

reminder to the concerned officer 23. The system should capture the date and time of field visit 24. On submitting the request for field visit the system should route the request for approval 25. The system should send an alert to the concerned higher official when a field visit is

planned by an officer 26. The system should pop a reminder/email with the date and time of the field visit a day

prior to the visit 27. The system allow the officer to modify the date and time of the field visit prior to the

authorization 28. The system should send an alert to the concerned higher official when a modification is

made to the field visit 29. The system should allow raising a cancellation request for a planned field visit 30. The system should route the cancellation request to the higher official for approval 31. If the cancellation request is approved /rejected can the system pop an alert to the

concerned official MIS & Reports

32. Reports should be generated for the quantity of waste dumped on a daily, weekly, bi-weekly, monthly, yearly based on Route No, Employee No/Employee name, Schedules, Equipment Details Vehicle Details, Quantity of garbage collected, On demand work, Emergency work, Fine collected, Period, Area of fine collection, Allowance

Integration Requirements 33. The module should integrate with the following modules,

a. Personal Information System, Accounts Management System, Revenue Management System, File Monitoring , Grievances Redressal, Assets and Inventory and Court Cases

34. Integration with handheld devices to fetch payments recorded Urban Community Development (Schemes) Sl. No Features

1. Mastersa. Recording of geographical Details b. Recording of Registrar Details c. Recording of Occupation Details d. Recording of Literacy Details e. Recording of Bank Details f. Recording of Location Details g. Recording of Religion Details h. Recording of Community Details i. Recording of Caste Details j. Recording of Work Details / Scheme Details / Sub Scheme Details k. Recording of Training and training institute Details l. Recording of Population Details m. Recording SHG / NH Group Details n. Recording Member Details o. Recording Implementing Agency Details


GHMC Page 153

Sl. No Features p. Recording Meeting Details q. Recording Group Saving Details

Application Registration 2. The system should capture the following fields when a new application request is

submitted 3. The system should mandate Member Id, Ration Card Number and Scheme Details while

entering the application details 4. Can the system generate a unique application number on successful updating the

applicants information 5. The system should facilitate to forward the application to the concerned authority in the

hierarchy 6. The system should capture the approval/ rejection of the application by the sanctioning

authority 7. The system should capture whether the application requires to be forwarded to the bank 8. The system should generate a message for the user to confirm the status to be updated

to forwarded to bank if the application requires to be forwarded to the bank 9. The system should update the sanction/ rejection of the loan by the bank 10. The system should update the status of the application to sanctioned by bank on

sanctioning of loan by bank 11. The system should capture allotment date for all approved applications at every stage of

the component availed 12. The system should retrieve the application status on inputting the Application Number

New Beneficiary request 13. The system should capture the New Family Beneficiary Request application form field

like Applicant Details , Neighborhood Details, Below Poverty Line ( Yes/ No), Monthly Family income , Property Details, Religion , Caste, Scheduled Caste/ Scheduled Tribe, Bank Details, Support Documents, Family Details, Additional Family Members, House Condition, Benefits Availed by Members, etc…

14. The system should generate a unique application number on successful saving of request

15. The system should generate a message on successful/ Failure on submitting the request 16. Can the system generate unique member id's and a family id on successful saving of

request 17. Can the system upload support documents and family photograph 18. The system should ensure the ration card numbers and the voter id number is not a

duplication of numbers already present in the database 19. The system should generate a card with the members name, age, member id and family

id 20. Can the system print the member ship card which is handed over to the citizen

New Member Request 21. The system should capture the New Family Beneficiary Request application form field

like Applicant Details , Neighborhood Details, Below Poverty Line ( Yes/ No), Monthly Family income , Property Details, Religion , Caste, Scheduled Caste/ Scheduled Tribe, Bank Details, Support Documents, Family Details, Additional Family Members, House Condition, Benefits Availed by Members, etc…

22. The system should generate a unique application number on successful saving of request

23. The system should generate a message on successful/ Failure on submitting the request


GHMC Page 154

Sl. No Features 24. Can the system generate unique member id's and a family id on successful saving of

request 25. Can the system upload support documents and family photograph 26. The system should ensure the ration card numbers and the voter id number is not a

duplication of numbers already present in the database 27. The system should generate a card with the members name, age, member id and family

id 28. Can the system print the member ship card which is handed over to the citizen

New Beneficiary Group Request 29. The system should capture the details of the new beneficiary group in the ULB with all

fields in the application like Group Id, Group Name, Group President, Group Secretary, Member Id, Member Name, Date of Joining Group, etc...

30. The system should generate a message on successful saving of request 31. The system should generate an error message on failure in saving the request

Create New Scheme 32. The system should facilitate to capture the following fields 33. Scheme Name, Scheme Id, Scheme Type ( Housing, Skill Training, Sanitation…),

Allotment Amount, officer in-charge, project details, etc.. 34. Can the system provide for adding required number of projects and components and the

respective details Scheme Progress Tracker

35. The system should capture the details of the scheme at each allotment stage depending on the type of the scheme

36. The system should allow the user to add the required number of attendees and beneficiaries

37. The system should update the benefits availed by the member on successful saving of data

Scheme Monitoring 38. The system should facilitate to allow user to edit/ delete the beneficiary details, schemes

details , project details, 39. The system should facilitate to generate forms required for schemes monitoring 40. The system set service levels to each project at each level and allow the user to update

the status of the scheme Scheme Repayment

41. The system should maintain the details of the loan schemes sanctioned to each beneficiary

42. The system should facilitate to capture the repayment details , foreclosure amount details

43. The system to update the status of the loan with remarks of the officer Escalation Management

44. The system should facilitate to notify the Project Officer when the application exceeds the time limit set for that level

45. The system maintain and auto escalate based to the higher officers based on Application delays, Allotment Delays, Bank Response Delays

MIS & Reports 46. Can the system generate and print the following reports 47. Year wise/ month wise/ category wise beneficiary list per scheme(s)


GHMC Page 155

Sl. No Features 48. Bank wise target, application forwarded, rejected, loans( number/ amount) sanctioned,

loans(number / amount) disbursed, subsidy, number of beneficiaries 49. Report on group formation with category, location etc. wise heads 50. Reports on activities at the activities level on finances, categories etc. 51. Statement of accounts with year wise, head wise etc. details 52. Reports on stage wise fund release under schemes 53. Reports on period wise utilization progress of scheme funds 54. Reports on activities completed and to be performed on daily, monthly, yearly basis

Integration Requirements 55. File Management System , Accounts Management System , Grievance Management

System 56. The System should integrate with the MEPMA schemes


GHMC Page 156

14. GOVERNANCE STRUCTURE This section proposes setting up an APEX Committee and a Project Committee, to lead and guide the implementation with their visions and recommendations. Also, the project management arrangements comprising of members from System Integrator, Program Management Consultancy (PMC) and Corporation Officials for the implementation management at various levels. Further, it covers Contracting arrangements i.e. details of the contract entered by GHMC with the various vendors for the O&M responsibilities along with SLAs for compliance. Monitoring will be done during project development, roll-out and post implementation as well. The team will be responsible for monitoring of the project and evaluation of the outcomes of the project. Project monitoring will be done through the PMC during the development & roll-out phases of the project. Project development and rollout can be monitored through the reports like, Software development schedule adherence report and rollout progress reports. Performance levels as expected from the application software under typical working load must be mentioned in the contract awarded for application software development. Adherence to defined performance levels shall be dealt with in accordance to the terms defined in the contract. The evaluation study can be conducted by the team or can be outsourced to an independent evaluation agency. The output will be measured against the goals for assessing the effectiveness of the project. Measurement of output(s) can be done through reports generated through the developed system as well as feedback from the citizens. Reports such as those providing details of adherence to charter, demographics of the beneficiaries etc. can be used for estimating the effectiveness of the project. On the other hand, feedback of the citizens, gathered through survey can help judge the satisfaction level achieved by the project. The evaluation results will be made available to all the stakeholders of the project, especially the decision makers (senior functionaries of the government) and the citizens. For the deviations such as those in the schedule or effectiveness of the project, root-cause analysis must be performed. If the reason(s) is(are) among the risks already identified during project conceptualization, defined mitigation plan(s) in light of the changed circumstances must be adopted. In case, the cause of the problem is one which is not anticipated early on, cost-benefit analysis must be performed for the measure and decision must be taken accordingly. To reduce the impact of unforeseen reason(s) of deviation, frequent and periodic reporting of parameters indicating the schedule adherence and project effectiveness is suggested. Review and Monitoring Framework The project would require a close supervision and appropriate project control for successfully meeting the objectives and its timely completion. The individual projects would be executed in the GHMC administered by a Project Manager (preferably the Additional Commissioner), under the supervision of the Apex Committee. The following structures are proposed for overall implementation and monitoring of the project Apex Committee An Apex Committee will be set up to provide overall vision, broad policy direction and guidance. This committee will meet once in a month to oversee the progress of the project and to provide guidance for the implementation of the project. The composition of the committee is as follows:


GHMC Page 157

Sl No Designation Role 1 Commissioner GHMC Chairman 2 Special Commissioner, GHMC Vice- Chairman 3 AC(IT), GHMC Convener 4 Additional Commissioners of Finance, Health and Sanitation,

Administration, Planning, Parks and Sports, Electrical, all Zonal Commissioners and ENC

Members

Project Committee The Committee will play a major role in monitoring and review for implementation of the project drawing out the requirements for implementation of the project. This committee will meet once in a week to oversee the progress of the project and handle day to day issues of the project during the implementation. The composition of the committee is as follows: Sl No Designation Role 1 Special Commissioner GHMC Chairman 2 Additional Commissioner (IT) GHMC Convener 3 Representatives of PMC Member 4 Representatives of SI Member 5 Other Members as decided by Commissioner Member


GHMC Page 158

ANNEXURE 1 - SOLUTION OVERVIEW FOR THE PROPOSED APPLICATION (INDICATIVE) The Overview of the solution provided in this section is an indicative solution. The Bidder is advised to design a suitable solution as per the requirements mentioned in the RFP and present the same in the technical proposal. Overview of the Technical Architecture Proposed The proposed GHMC portal shall be web-enabled and based on n-tier service oriented architecture. Highlights of the portal should be,

• Industry standard web browser as the thin client • Intranets/secured Internet to provide secure access to Circle users • Extranets/intranets to provide access to other Circles and service providers to enable

G2G and G2C transactions. • Internet to provide managed access by citizens and other interested parties.

Proposed GHMC portal shall be based on Service Oriented Architecture (SOA). Service Oriented Architecture (SOA) may be defined as a group of services that communicate with each other through either simple data-passing or two or more services coordinating some activity. The application solution deployed for the Circles are required to interface with various other external/internal applications like Property Tax, Online Building Plan Approval, Town Planning, etc., for data exchange. The services should be integrated to citizen service centers for exchange of circle data and business logic. The design of the proposed technology solution in GHMC portal is,

• Allow internal, external and associated agencies access to the online GHMC portal • Allow Citizen and CSC to access services through a ‘Single Window’ interface • Services should be made available using IVRS, GPRS, SMS and Help Desk • Facilitating services through CSC's enabling implementation of GHMC portal,

middleware project infrastructure are to be hosted in the State Data Center of GoAP • Re-use existing and proposed circle infrastructure in service delivery by integrating

suitable existing department initiatives

Proposed Architecture The Solution is envisaged to be based on centralized and networked data processing architecture. The data processing would be carried out at a central location with a set of servers to support the processing needs of the GHMC. The system shall be designed on “no-single point failure” concept. The proposed GHMC architecture gives an overview to finalization of technology architecture, identification of service delivery channels and identification of departments to be integrated for back-end operations. The overview of solution architecture is given below, where the entire architecture has been divided in following 4 pillars:

GHMC Proposed Solution Overview The figure below depicts the solution overview proposed for GHMC IT application


GHMC Page 159

Fig: GHMC Proposed Solution Overview The architecture & design of GHMC web portal shall be such that it can be easily modified to respond quickly to the changing business needs, as well as to the rapidly evolving information technologies available to support business & IT needs of the GHMC & its constituents. The proposed solution shall be designed using the industry’s best practices as well as using the experiences from similar initiatives executed successfully within the country by Ministry of Urban development (MoUD), GoI. GHMC Portal will be based on n-tier service oriented architecture. Highlights of the portal shall include,

• Industry standard web browser as the thin client • Intranets/secured Internet to provide secure access to Circle users • Extranets/intranets to provide access to other circles and service providers to enable

G2G and G2C transactions. • Internet to provide managed access by citizens and other interested parties.

Functional Architecture of GHMC Web Portal GHMC provides the end to end services to the Citizens and Departmental Users. GHMC Portal services shall be made available Government to Citizen (G2C) and Government to Government (G2G). The proposed Functional Architecture for GHMC application is depicted below. It describes the functional components and the associated sub functions.


GHMC Page 160

Fig: GHMC Functional Architecture Contextual View of GHMC Web Portal GHMC Web Portal shall enable the electronic delivery of Services provided by Government Departments, Government Bodies as shown in contextual view diagram below. The proposed GHMC Web Portal solution envisages integration with existing Government Departments as well as any upcoming initiatives.

Fig: GHMC Online Architecture GHMC Web portal is important in allowing citizens and department users to access government information easily and to avail one-stop Corporation services. The portal will complement and enhance customer-focused service delivery channels which may already exist in a government. It shall allow departments to present information, applications and services in a single consolidated browser view. It shall provide a secure and individualized view of multiple online resources and interactive services. It shall offer a single access point to critical information and the primary applications necessary for an individual to avail the services. In this sense, a portal shall become an interface between the government and the citizens.


GHMC Page 161

GHMC web portal will act as front end interface to e-Governance initiatives and services. A User would typically come to GHMC portal to find information / avail any service through Internet. GHMC Portal would be connected to various departments through intranet / Internet and would be accessible to internal departments for information update and to various services delivery channels like for citizen/user access. Key Features Proposed for GHMC Integrated Portal

• Can be accessed via a variety of established channels, including Internet, e-Seva, AP Online etc.,

• GHMC web application will be single window to the G2B, G2E and G2C services. The service delivery would happen in integrated fashion

• Standardization of the content framework based on National Portal and Website design as per Indian Government Website design guidelines

• Integration of the GHMC Integrated portal with the State Portal / SSDG • GHMC web application will provide information about MIS, Engineering, Town

Planning, Grievance Redressal, government departments and web links to these departments

• The portal would primarily be available in English and Telugu • GHMC Web application will be available 24 hours a day, 7 days a week, and

accessible from anywhere in the world via the internet. • Content personalization and content management. • Search functionality shall be able to query both structured and unstructured

content by keywords • Consistent, easy-to-use interface: GHMC Web Portal typically shall have a

consistent interface which flows from the home page down through every area of the portal. The interface proposed to be designed specifically to make using the portal very easy.

• Aggregation: Provision for pulling links and content together into a single place so that to help users know where to go if they are looking for information. Aggregation shall allow a user to interact with several systems from one single user interface.

• Alerts: Provision for a service so that user(s) can sign up for e-mail notification when the information that they are interested changes. This can include both key performance indicator changes and changes in information within documents.

• Self - service: GHMC portal shall be a home for a variety of self-service applications, which allow citizens, employees, and others to take care of their own needs.

• Personalization: Provision of the feature for groups and individual users to customize the way that the information is displayed. Filtering content to the information that a group is interested in and shall be able to change the location of the information on the screen so as to make it user-friendly.

Integration Components The e-Governance Integration components (IC), with a common set of specifications shall act as hub for all the interactions between service seekers (the citizen and businesses) and the various service providers (GHMC Departments). Acting as nerve center, the IC would handle large number of transactions across the entire network provide a common set of specifications and a single point access. The gateway achieves integration amongst diverse set of applications built on varying platforms through compliance with a set of e-Governance Specifications- based on open standards.


GHMC Page 162

Business Rules Specifications

1. Ability to define rules based on - Logical conditions, Mathematical Computations , Combination of Conditions, like OR, Combination of above.

2. The application should have a simulation environment for testing the rules defined in the rules engine using:

3. Simulation Scenario Building 4. Unit and regression testing of the Rules engine 5. Ability to manage rules from a single interface and repository including single plat

form for modeling, coding, debugging and deploying. 6. Ease of Use: Ability to write rules in a rule language that is aligned to the natural

business language. 7. The application should provide inbuilt assistance for rule creation. eg: Templates

point and click editor. 8. The application should provide syntactical error checking facilities for defined rules. 9. The application should provide rules consistency validation tools, (e.g. checks for

logical errors, infinite loops) 10. The application should have the ability to diagnose rules over lapping and subsuming

the business rules. 11. The application should provide a flexible mechanism to define and control the life

cycle of the business rules from creation through validation and deployment. 12. Ability to configure the rule life cycle management by defining role capabilities and

permission associated with each rule. Design Considerations for Proposed Technology Solution It is proposed to co-locate the GHMC Servers, Storage and associated IT Infrastructure in the Andhra Pradesh State Data Center (APSDC). The design considerations for the proposed technology solution, detail the requirements that the proposed technology solution should meet in order to fulfill the objectives. The design considerations for the proposed technology solution in the GHMC Web Application are:

• High Availability • Scalability • Interoperability • Portability • Performance • Extendibility • Maintainability • Multi-lingual Support • Security

The following section details out each of these design considerations with respect to the project and the proposed technology solution. High Availability: It is an ability to withstand failure or individual components. Considering the priority of making department service information accessible through CSCs, the system requires high level of availability. From the perspective of GHMC Web Portal, following applications are of high importance:

• Work Flow Management for all services (transaction and workflow based services)

• GHMC Web Application • Grievance Management System


GHMC Page 163

• Certificates The proposed architecture shall address these requirements through the use of clustering, load balancing and redundancy. Cluster environment shall be built for critical applications with fail-over and fail back features. Redundancy and Load balancing features shall be built in Application Server, Web Server and Database Server to achieve the High Availability. System may return error occasionally, but it will respond in a normal manner on retry after reasonable amount of time, typically few seconds. Scalability: Scalability refers to ability to service significant increase in load or page request, without noticeable degradation of performance by means of deploying additional hardware without making any changes to existing code. It is envisaged that the number of Citizens /department users will increase with more Services joining the GHMC application initiative. To address the scalability challenge, the proposed architecture is built around the Service Oriented Architecture (SOA) paradigm. Interactions among the various services and integration with the existing application are proposed to be achieved using open standards. There has to be a clear cut demarcation between data and business and enterprise applications. There shall be provision to plug in new applications and new features at any point of time to address the application level scalability requirements. There must be well defined capacity management plan at the time of design phase to clearly define hardware changes to be done for servicing increasing load. Interoperability: There shall be a provision for the flow of information among the heterogeneous applications (e.g. GIS & Building Approval applications are built on different technology platforms) and across Corporation departments. The proposed architecture is built around the web services standard and adopts open standards for interacting with various applications to address the interoperability requirement. Portability: GHMC Web application should be portable. It should address the following requirements,

• Implementation should be portable • Any COTS products used should provide tools for exporting & importing data

using open standards • Developed source code should conform to open standards

Performance: Performance is defined as the responsiveness of GHMC Web application. It should manage the user load and response time. GHMC Integrated portal shall be capable of addressing the performance requirements as more and more citizens take part in GHMC Web initiative and volume of data grows. The performance of the portal must not deteriorate with increase in volume of data or number of end users. The proposed architecture shall take care of the application level performance requirement by load balancing and caching technique. The performance is taken care of by restricting the number of users to consume various services by defining an access control mechanism. However, regular performance tuning initiatives like purging and archiving of data are to be adopted to be ensured by the selected vendor for optimum performance.


GHMC Page 164

Extensibility: Extensibility refers the ability to add new functionality without requiring major changes to the existing code. GHMC Web application should be extendible to adopt following of changes with minimal or no changes to existing code

• Providing new content processing, content management system • Significant growth of the content • Providing new functionality or feature or service

Maintainability: All the applications shall have

• Ease of replacement of modular units • Visible or audio indicators to indicate operational status i.e. Alarm, Non

Operational & Operational Multi lingual support: At GHMC Web application, repository content management system is to be created in English for disseminating information to Citizens. For providing access to citizen’s information it is also recommended to make this information available in Telugu also. Security: Majority of the services is G2C services, and most of the information is in public domain. The security requirements should address data privacy, confidentiality and access control mechanism. In addition, the security should address the following features,

a. DMZ policy b. Encryption c. Authentication d. Authorization e. Digital Signature

Database Features: The Database Features that are required for the application are discussed in section - 8 Technology Requirement for Application Development Logical Architecture of Web Portal GHMC Web application is the set up at the GHMC Jurisdiction level, wherein data and information would be collected, stored, retrieved, used and exchanged in an efficient manner at all levels. The services to be delivered would require automated work flow, data Migration, and involve significant process redesign. GHMC Web application portal is proposed to be built based on Open standard technology, shall support N-tier architecture (thin/thick client) namely, Service Oriented Architecture (SOA). It shall run on multiple operating systems and various databases. The diagram below represents the important logical pieces of GHMC Web application that would result from overall SOA transformation. The following are the various layers for GHMC proposed for deployment using SOA. This diagram captures the abstract view of GHMC SOA layers, important components of each layer. Layered architecture means decomposition of services such that most interactions occur between adjacent layers. The diagram below represents the important logical pieces that would result in from overall SOA transformation.


GHMC Page 165

Fig: GHMC Portal – Layered Architecture

EIS Layer: This layer (Enterprise Information Service) consists of packaged, custom, applications, Content Management Systems and GHMC/Department databases that are essential and contributing directly or indirectly to the GHMC web system.

• Enterprise databases will hold both the application and service data. • GHMC application Database, Standard RDBMS used for storing GHMC specific

transactional data • Content Management, Open source product for GHMC specific content

repository. • Workflow database to store transactional data for workflow management like

scanned documents, certificates, licenses etc. • Meta Data Repository, stores the meta data about the various department

databases • Directory Server, stores Citizen Credentials. It needs to store Employee details

including digital signature. • Ability to capture electronic data and integrate into backend systems

Integration Layer or Service Mediation Layer: This layer shall consist of service infrastructure components for departmental integration, service registry, service repository. Integration Service will carry the service invocation payloads/messages between consumers and providers. Integration components will have all the intelligence as to how to route each request to the respective departmental Server offering the service. For ex: Land Usage request by the citizen is routed to Planning department and Grievance submitted by the citizen is routed to Grievance section of the administration and coordination department. Each Department will have a Departmental Interface Connector (DIS) installed on a server. The response from these servers will be returned to the GHMC Portal. The other important functions expected out of integrated components are message routing, tracking and security of each transaction.


GHMC Page 166

• Integration Channel de-links the backend from the front end of the departments. This helps to deliver e-service to the citizens

• Integration Channel route the SOAP message is routed to GHMC application. Message can also be routed to the department servers based on information registered in the gateway.

• Captures audit logs & time stamping of transactions going through it. • Integration Channel will not open/read the contents of the payload i.e. Submitted

e-form • Management and Configuration component facilitates interoperability between

client layer and the various department services using XML standards. Business Services Layer: These are typically the intermediate services Layer and represent Shared Business Process Services. At GHMC Level, these Services are Admin Services, Grievance Services, and File Management Services etc.

• Business Application represents all the business related applications and related components like Accounting, Administration, Unique Id Management, and licensing etc.

• Enterprise Application - The Enterprise application represents all the Enterprise related applications and related components such as payment gateway, Workflow management etc.,

• Business Data Services - Business data services encapsulate business data, typically providing Create, Read, Update and Delete (CRUD) type of functionality. They access data from data layer using data access components.

• Data access components are responsible for exposing the data stored in the database to the business data components. Data Access Object (DAO) pattern is used by these components to encapsulate all access to the data sources, which manages the connection with data sources.

Operational or infrastructure services:

• This encompasses generic services across all applications such as logging, auditing, notification, exception handling etc. This would also include device specific services. These are very specific to accessing some devices in general through application or service interfaces like printer, fax machine, scanner, plotter etc.

• Session Management enables user session management at the server. • Audit and logging enables logging of the events / Transactions at the server.

These events would then be used to generate security alerts and notifications. • Input validation enables validation of the raw data uploaded by the end user

before saving into the database. • Caching Management would cache frequently used resources for faster

response. For example, caching of frequently visited web pages for faster delivery at local machine is proposed.

Presentation Layer: Presentation Layer handles the GHMC application Services. It addresses, Personalization Services, Presentation Framework Services and Information retrieval service on top of content management services. Channel Layer: This consists of various devices like IVRS, Mobiles, e-Sava, Meeseva, CSCs, and AP Online to access GHMC application. Also, various browsers form the channel layers, through which users can access the GHMC Web application.


GHMC Page 167

Client Layer: This designates the different types of users accessing the GHMC Web application. Type of user typically would be an important factor in determine the level of access to applications.

• Thin Client refers to the web browser component installed on the end users machines. All services would be accessed through the browser and the proposed system would be capable of delivering the services through all the standard browsers like Internet Explorer, Mozilla, Firefox, Opera etc.

Security Services Layer: These are essential for all SOA layers. Features to be implemented are Authentication, Authorization & SSO (single-sign-on), and Privacy, Confidentiality, encryption, digital signature and access control.

• Authentication based on an LDAPV3compliant system allows end users to enter GHMC application. The parameters for this authentication would be user Id and password.

• Authorization is a single repository of access control for all users at GHMC level. This component would be responsible for defining access to various functionalities based on the access control defined in the system.

Management & Monitoring Services Layer: This layer contains management and monitoring components for GHMC Web application and its infrastructure. This layer cut across all layers of applications to manage/maintain the quality of service requirements of GHMC Web application. Migration Strategy There is a need to migrate the GHMC related data from the legacy systems to the proposed system in a planned manner. The data is available with GHMC in different formats and hence there is a mandate for the Migration Strategy with well-defined framework which is explained below: Data migration Overview: Data migration shall involve the movement of the data from legacy systems to packaged applications, data consolidations, data quality improvements and creation of data warehouses and data marts. The following objectives will be met with less effort by using the framework

• Avoid risk of the reliability of data after migration using the Audit and Verification process

• Identify minimum software and hardware standards for effectively running the migration task

• Perform the migration task in a shorter period of time and there by ensure time to market

• Provides option to evaluate synchronization mechanism by between various sets of data and ensures the reliability

• Provides list of tools that can help in the data migration activities

Data Migration Framework overview: The data migration framework shall consist of the following:

• Data Profiling • Data Conversion • Data Audit and verification • Data synchronization

Deployment Architecture of GHMC Web Portal


GHMC Page 168

The proposed solution would consist of a GHMC Portal and identified Services connected to the GHMC portal using Integration Channel. This architecture shall be flexible to accommodate department level variations. The GHMC Portal system would leverage on the various existing applications and provide a common service interface to the citizens and various other stakeholders. There would be service based interaction between end-users, existing applications and external systems. Citizens and Business Users would interact with the GHMC portal via standard service interface. The model shall effectively encapsulate all legacy system and external system interfaces. There shall be provision for authenticating any given user before the access to the application is made available. The users shall request for service and deliver services interfacing with the applications hosted or connected through the GHMC Portal. The GHMC Portal would host all the GHMC Services to the citizens through a common service gateway. The model is built around multi-layer request response model. As GHMC Portal application is built under the Centralized Architecture specification, with provision for High Availability solution at the web server, application server and database server level to avoid complete failures of services, which are delivered through GHMC application. Highly available deployment indicative architecture for GHMC Portal application is shown in Figure below.

Fig: GHMC Deployment Architecture

The architecture uses an active/active cluster technology for high availability solution at data tier and application tier. In Active-Active Configuration, in normal circumstances, both the nodes (hardware servers) configured in a cluster continuously provide the services to users, so both the nodes are utilized in online enquiries, transactions, etc. while running the same application. When one node goes down, the entire load of the application switches over to the second node.


GHMC Page 169

Overall Networking & Server Architecture The GHMC will be leveraging the APSWAN for addressing its connectivity requirements. All the Circles will be connected to the APSWAN backbone which shall provide access to the various Departmental applications. Centralized application shall be hosted at the State Data Center for implementing the solution. All the circles will be accessing the application from one secure central location (State Data Center). The State Data Center will be having its own Disaster Recovery Site for disaster fall back and other emergency conditions. The following diagram illustrates the network architecture of the GHMC Web Portal.

Fig: GHMC Network Architecture

The applications and database will be hosted centrally; the field units will access it over secure intranet (APSWAN). Citizens will access the information over internet. The GHMC Portal application will be developed in a Centralized environment. Information Security Measures: The System Integrator shall be responsible for GHMC application security initiatives which shall include DMZ Policy, encryption, authentication, authorization and digital signature. It should take the appropriate measures for the data privacy, confidentiality and access control. GHMC application portal will comply with all IT security features assured by implementing the security at the following levels,

• Component level (Operating system, switches etc.) security (ISO 15408) • Application level (Basic application for access control, authentication and audit trail

etc.) security • System level (Physical security, communication and operation management,

business continuity management etc.) security (ISO 27001)


GHMC Page 170

Single Sign-On: Single Sign-On allows the user to sign-in only once, after which the user is directed to the GHMC portal and will not be prompted for the user id and/or password when accessing services of any other department of GHMC. Authentication: There shall be a provision for Authentication (validation of a user’s identity (ID/password). Lightweight Directory Access Protocol (LDAP) is an internet standard protocol which is commonly used for authentication.

1. Allowing only authenticated users to access system resources protects those resources from inappropriate access.

2. Authenticating users are the basis for providing accountability. Authorization: Authorization will be performed in application tier. Authorization of the user is done by verifying his credentials at the database. Audit Trail and Logging: Logger service component will provide the functionality of logging system activity and audit trail information. Other application components communicate with logger through logger client component. Logger client component communicates with logger service by sending JMS messages. Logger service reads JMS messages and saves into database. It will use Log4J library. Logger service should be deployed on all nodes of application cluster. Application objects running on a node will use local logger service and should not access logger service deployed on other nodes of the cluster. Directory Server: Directory Server of GHMC Portal shall contain profile information of Citizens, Employees, Roles, application level ACLs (access control lists), service level access control list etc. This directory server should be made accessible using LDAP v3 compliant Conformance to Technology Standards The following key technology standards shall be provisioned by the System Integrator, in the solution

• GHMC Business Rules should be easily modifiable and should support changes in business rules

• It should be highly scalable • It should support any combination of user interfaces (e.g. graphical, web browser, and

telephone interfaces) • Implement business rules as discrete executable components or services • Data is created and used by business processes. In GHMC Portal, data must be

created, used by, and managed by the application component that automates the business processes

• Circle should not focus on where application components will execute (i.e., where they will be deployed) or what platforms they will execute on

• Applications and their components require the following management functions - Software distribution - Start-up, shutdown, and restart of components - Starting multiple instances of a component. - Configuration of components - Logging of component operations - Communication of errors, exceptions, and unexpected events

Proposed Architecture of GHMC Data Centre


GHMC Page 171

The existing Data Centre is hosted in GHMC Head Office. It is proposed to co-locate the Servers, Storage and associated IT Infrastructure in the AP State Data Centre. The following are some of the aspects considered:

• Redundancy of Computing equipment’s, active networking component including

Wide Area Network & Local Area Network. • Redundancy & scalability with Security infrastructure. • Domain controller & DHCP services introduction & integration. • Revised Architecture for Wide Area Network & Local Area Network. • Cabling infrastructure, Logical & physical connectivity. • Disaster Recovery Center.

Wide Area Network for Intranet & Internet: This State Data Center is being used for online services from all offices of GHMC & from internet public access for the users across the state. In the current scenario the core router is connected by a channelized STM1 connectivity to the offices at GHMC by 2 Mbps connectivity to each location without the redundant link. It is proposed to have primary WAN Connectivity in place along with a backup/redundant link of the existing connectivity. The following diagram depicts the proposed Wide Area Network Diagram integration with APSWAN

It is proposed to co locate the GHMC Servers in State Data Center (SDC). The SDC is connected to the APSWAN via 155 Mbps link.

Guiding principles of Technical Architecture & Standards for Proposed Solution The Components along with the key guiding principles and benefits are explained below: 1. Applications Architecture

a. Guiding Principles

i. Design applications to support N-Tier architecture ii. Design applications to be highly granular and loosely coupled iii. Plan for extensibility, interoperability and scalability


GHMC Page 172

iv. Design application to reuse components v. Select tools based on application architecture vi. Design applications to operate in a resilient manner within a fault tolerant

environment vii. Document architecture

b. Architecture and Technology

i. Adoption of n-tier architecture ii. Electronic service delivery raises expectations and technology needs to be

fast and robust iii. Electronic services must be, and must be seen to be, suitably secure iv. Object-oriented components should encapsulate both the business logic and

the data accessed by the business logic. v. System should be potential to become intelligent, self-managing entities,

allowing for more simplified management.

c. Data Architecture

i. Designing the enterprise Data Architecture so it increases and facilitates the sharing of data across the enterprise.

ii. Designing the enterprise Data Architecture so it is business driven, as opposed to technology driven, and aligned with the Application Architecture.

iii. Separate the data sources for online transaction processing (OLTP) data and online analytical processing (OLAP) information

d. Metadata

• Centralized Metadata

i. Common data elements should be defined consistently even when they are stored in multiple databases and data can be shared between applications

ii. The data is to be described in the same way in each table where it is defined iii. Definitions should include traits such as name of the field, length, number

format, data format, and the values it can have iv. The data should be defined in the same format for easier exchange data

across system and organizational boundaries

e. Metadata - State Service Broker

• State Service Broker

i. Shared data is accessed through reusable services called by each application that needs access to the common data elements

ii. Data can be shared through an interface, such as the State Service Broker (SSB)

iii. To access the data, each application sends a request to the SSB iv. The SSB executes the service and returns a response to the application v. This model protects the data and ensures that the data retrieved is accurate

and consistent since it is being retrieved by proven application code


GHMC Page 173

• Centralized Metadata

i. Use and actively maintain the Centralized Metadata Repository to store Centralized Metadata definitions

ii. When designing or modifying a database, review the Centralized Metadata Repository for existing standard and proposed data elements before implementing a new database to ensure data elements are defined according to standards

iii. Define existing databases in the Centralized Metadata Repository iv. Identify authoritative sources for Centralized Metadata v. Use Centralized Metadata Exchange Standards when exchanging data

across departments

f. Data Modeling

i. Determine the initial business requirements using terms and tools that are familiar to business users

ii. Take the Entity-Relation (ER) model to the third normal form, then de-normalize where necessary for performance

iii. In a dimensional model, use a star schema whenever possible iv. Restrict free form data entry where possible v. Setup indexes and form relationships carefully vi. Design the data model to allow for growth and/or change vii. Each department should standardize on a common data modeling tool for

designing and maintaining all new database instances

g. Database Management System

i. When using object oriented programming languages, use a relational database management system (RDBMS)

ii. When using a relational database with object-oriented programming, design the relational data model first

iii. Replicate stable data, based on business and performance requirements

h. Data Access Middleware

i. Provide centralized administration for data access middleware through central IT staff

ii. Implement a server-based OLE DB or JDBC solution as opposed to a workstation-based OLE DB, ODBC, or JDBC implementation

iii. Use domain name system (DNS) alias names when accessing databases through OLE DB and JDBC

i. Middleware Architecture

i. Using application communication middleware is required in a heterogeneous, distributed environment

ii. Minimize the use of distributed units of work iii. Do not use database middleware for application communication iv. Using a broker facilitates reuse and shortens development cycles v. Precede selection of application development tools with an application

communication middleware strategy vi. Select third-party middleware rather than middleware supplied with a

development tool


GHMC Page 174

vii. Document application programming interfaces (APIs) and interface definition language (IDL)

2. Integration Architecture

i. Enable inter-operation of multiple technologies into a single integrated network

ii. Integration Architecture should be based on middle service tiers such as interface engines, database gateways, messaging, integration services, XML and third party tools

iii. Should minimize the impact to existing application systems iv. Application Integration shall provide the following services

• Data translation and mapping (translates communications and data between applications)

• Transaction explosion (one transaction is spawned into multiple transactions in remote applications)

• Front ending other applications (a single front end for multiple applications)

a. Data Access Integration

i. Data access is the accessing and sharing of data between legacy, new, and packaged applications

ii. Techniques shall include

• Data Extraction(Data is extracted and transferred to destination application at desired frequencies)

• Data replication (A copy of data is made using replication features of the database, this is often used to support distributed users who need local copies of data for processing)

• Data Sharing (Same data is shared by more than one application allowing them to view most current data, always)

b. XML

v. XML is a standard for exchange of structured data between applications vi. XML shall constitute number of components, the key ones are:

• DTD/Schemas - define structure of data • DOM- document object model contains information about document

contents and allows parsing and generation of XML documents • Namespaces - resolves ambiguity in using tags • XSL - is used for presenting XML data in various formats and enables

separation of data from presentation. vii. Key tools necessary for implementing XML :

• Parsers - check the XML document • Repositories - store DTD/Schemas of documents • Authoring tools - necessary for creating large number of documents

3. Networking Architecture a. Local Area Network (LAN)

i. Applications located in the field units (Central, Zones, Circles, etc.) • Document management application • Office automation


GHMC Page 175

• Groupware application • Calendars and schedules • File and Print server • Mail server • Proxy server

ii. At certain locations LAN may need to support standard and high-speed workgroups

b. Wide Area Network (WAN)

i. Web browser will be used by departmental users to access the applications located centrally

ii. On-line access to all departmental applications which will be located centrally iii. Highly secure, reliable and fast communication link must be available from all

field units iv. High bandwidth requirements would be required to support data, voice and

video transmissions over the network

4. Government Users Access to Internet

i. Application layer firewall protected access to the Internet is core • Single Application Layer Firewall for outbound traffic along with other

tools like: • Policy Compliance • Directory • Encryption • PKI • VPN

ii. Use proxy server with appropriate security to access internet over LAN iii. The GHMC should have separate external and internal DNSs iv. All Internet access points shall be configured with the identical set of

technologies v. Network-based dial-out is to be avoided vi. Dial-out service will only be provided by department managed communication

servers vii. Application layer Internet firewalls will be used for access to all external IP

networks 5. External Business Partner Connectivity

i. The GHMC must support different levels of connectivity with its external business partners

• Partner may be treated as a part of the infrastructure • Partner and the GHMC determine an agreed upon interface and

intermediary for transferring information (e.g., VAN, Internet, Switched Services)

ii. Business partners will have access to GHMC resources through a secure communication link

iii. Connections to business partners should be secured via direct line or VPN iv. Secured authentication techniques will be used for authentication and a

“DMZ” which allows access to designated resources through a second firewall should be implemented for all partners

6. Platform Architecture


GHMC Page 176

i. Server Platforms o Departmental server (File, Print, Mail, Proxy, etc.)

• Standardize on an Operating System based on requirements Unix , Windows 2008 or Linux

• Directory Services (e.g., LDAP) integration with OS recommended • Should have Symmetric Multi-Processing (SMP) capabilities using

Cross-Bar Switch or CC-NUMA techniques o Enterprise Server (Web server, application server, database server)

• Choose an operating system based on the requirements • Unix, Windows 2008 • Needs of the extent of Scalability, Availability, Performance etc. should

be considered before choosing the platform/vendor ii. Mobile and Desktop Computers

• Windows 7/ XP or Open standard • OS should have tight integration with the internet using XML schemas

& file system to store XML objects • Implement mobile computing using DHCP, PPP and IMAP 4 standards • The hardware configuration should adhere to System Design

Guidelines laid down by IETF iii. Workstations

• RISC / Intel based Unix / windows OS based WS • Tighter OS/hardware integration

• Multiprocessing • High-performance memory subsystems

• Intel based Windows /Linux based WS to be used in • Less floating-point intensive applications • Situations where performance can be sacrificed on cost

iv. Primary Storage: • Hard Disk Drives are the most commonly used mass storage devices

because of their low cost, high speed, and large storage capacity • Interface: SCSI(declining), FC-AL( emerging as de-facto

standard), IEEE1394(emerging) • RAID with fault tolerance to be underlying design method for

storage systems v. Using Storage Arrays & Optical Juke Boxes carrying the HDDs vi. Secondary Storage:

• Tapes is still the primary media for data backup and archiving • CD-ROMs, DVD-ROMs and DVD-RAMs usage

vii. At the system level • Use SAN at

• The State-wide Data Center (Clustered environment with server farms requiring centralized automated tape backup for multiple servers with heterogeneous OS)

• For all Enterprise-class applications requiring data consolidation

• Use NAS at • Workgroup and departmental levels • For web data access, inter-enterprise application development

and when data is positioned to be accessed primarily via Ethernet or Internet connectivity

viii. Backup S/W to be decided on the ability for data protection, availability and storage resource management


GHMC Page 177

ANNEXURE 2: TESTING AND QA REQUIREMENTS Inspections Factory Inspections: Bidder shall provide the factory inspection report for quality assurance as per prevailing industry standards and practices for each type of item. The goods will be accepted only after verifying the factory inspection report by GHMC. Inspections following delivery: GHMC will conduct a thorough physical inspection of all the products delivered to ensure that they arrive at the sites in good condition and are free from physical damage including but not limited to crush or broken equipment’s, missing seals, opened packages and incomplete shipments. GHMC reserves the right to return the products to the bidder at the bidder’s expense.

Physical inspection of hardware will also include physical checking, unpacking and counting of the delivered equipment by GHMC staff in presence of the bidder. This equipment will only be acceptable as correct when each received item corresponds with the checklist that will be prepared by the bidder prior to shipment. Any shortfalls in terms of number of items received may render the delivered equipment’s incomplete. Pre-Commissioning Tests In addition to the Supplier’s standard check-out and set-up tests, the Supplier (with the assistance of GHMC) must perform the following tests on the System and its Subsystems before Installation will be deemed to have occurred and the GHMC will issue the Installation Certificate(s). Testing is an important part of the delivery process at GHMC. GHMC requires thorough and well-managed tests to be conducted. The bidder MUST build up an overall plan for testing and acceptance of system, in which specific methods and steps should be clearly indicated and approved by GHMC. The acceptance test of hardware and software will be defined by the bidder, agreed and approved by GHMC and include all the necessary steps to ensure complete functionality, operation and performance of the system. Testing will be conducted at the installation sites. Testing of hardware and software MUST demonstrate that the new systems:

• Perform according to detail functional requirements • Meet the basic system concepts • Satisfy the operational and technical performance criteria • Fit with GHMC operations i.e. provide right information to each user group or provide

the efficient system navigation to process various queries or process transactions • Convert data from the existing system • Interfaces with the existing systems and new systems, as and when they are

installed. • Upload data from various source

It is bidder’s responsibility during the tests to evaluate and recommend any further changes to the infrastructure. Any recommendations for change will be discussed with GHMC. Testing Methodology/Techniques


GHMC Page 178

• The bidder MUST outline the methodology that will be used for testing the software and hardware.

• The bidder MUST define the various levels or types of testing that will be performed for software and hardware.

• The bidder MUST provide necessary checklist/documentation that will be required for testing the software and hardware

• The bidder MUST describe any technique that will be used for testing for software and hardware.

• The bidder MUST describe how the testing methodology will confirm to requirements of each functional area.

• The bidder MUST indicate how one will demonstrate to GHMC that all applications installed in the system have been tested.

Operational Acceptance Tests GHMC (with the assistance of the bidder) will perform the following tests on the System and its Subsystems following Installation to determine whether the System and the Subsystems meet all the requirements mandated for Operational Acceptance. Testing Methodology/Techniques Please refer the above section for testing methodology/techniques. Successful completion of the contract will be gauged through a series of formal acceptance tests performed on all aspects of the system/sub systems as mentioned below Testing Requirement Description

Database Test • Verify complete and correct installation of Database Management System

• Data Integrity Testing • Data Sampling • Database Back-up & Recovery Testing • Query Testing • Database Connection Test (Determine if the database server will be

able to sustain the expected number of connections) • etc.

Functionality Test • Test that the functional requirements specified in all the modules are met.

• All functions MUST be tested when user provide inputs with correct and incorrect inputs

• Testing of Formats • etc.

Unit Test • Each module or Component should to be fully tested independently before integration

• etc. System Test • All specified functionality should exist. This testing verifies the as-

built program's functionality and performance with respect to the requirements for the software product.

• All System functions that are accessed through menus should be tested

• Defect test: Test software defects before implementation • House Keeping functions like archiving • Easy to use: Graphical user interface as per requirement

specification • Server, Storage system etc. shutdown and power up test


GHMC Page 179

Testing Requirement Description

• System backup and restoration test • etc.

Security • Attempt to break the password • Time out facility on dormant menu/screen. To continue using the

open screens the user MUST re-login. • Reviewing and Evaluating the Security Controls • etc.

Stress Test • Finding errors that will show themselves under certain combinations of events or data values

• Heavy repeating of certain actions or inputs • Time Test – To determine if individual business transactions run to

completion in a reasonable amount of time, etc… Reliability Testing • Testing the system for prolonged use at varying levels, or, possibly,

constant value at peak level, etc… Performance Testing • Testing to probe the system against prescribed timing, etc…

• etc. Consistency Testing • Test the consistency of data and results across the applications

• etc. Recovery Testing • Testing the response of the system to failures of all sorts including

but not limited to power failure, etc… Audit Trail • Tracking critical transactions

• Logging all critical errors, etc… Multi-User Capability • Test that the application system can support several users, etc… Help Information Testing

• Testing for help information that will be verified for detail and presentation, etc…

Limit Testing • Test as to how the system reacts to data which is maximal or minimal in the sense of attaining limit

• The system will be tested beyond the limits specified to verify whether sufficient margins have been built in, etc…

Volume Test • Test to submit the system to large volumes of data • Etc.

System Integration Test

• Testing Components and Component Integration • Testing System Interfaces • After each system has been fully integrated to create a larger

system, each module or sub-system MUST have a defined interface which will be used to call another program component

• Parameter interface: Data and function references are passed from one component to another.

• Procedure interface: One sub-system encapsulates a set of procedure which is called by other sub-system

• Message passing interface: One sub-system request a service from another sub-system.

• Validation (Completeness) • Robustness Testing • Testing for 24x7 availability • Error Detection & Recovery Testing • Measuring response time, throughput and availability • Monitoring Resource Utilization • Data Conversion, • Etc…

Compatibility and Configuration Testing

• Operating System and Data Base Compatibility • Hardware and Network Compatibility • Checking Compliance with Standards • Test the compatibility of data to the higher version, as and when

applicable


GHMC Page 180


• etc. Storage Testing • Testing to detect instances when the system exceed the specified

limits (e.g. processing or supplying large volume of data) • etc.

Installation Testing • The ease of installation will be checked • Where installation counts are applicable, the number of installations

specified will be tested. The system will be checked for a higher number of installations than specified, also to uninstalled to check if the installation count is reduced

• etc. Environment Testing • The application will be tested whether it works under different

environments e.g. application will be tested on different networks Graphical User Interface (GUI) Test

The system will be tested for GUI which will include but will not be limited to: • Menus • Message Boxes • Keyboard Interface • Cursor Management • Visual Design • etc.

Manual Procedures Testing

• If the system works only with manual aid, an archive utility that requires the manual loading of tapes or a system requiring manual switching of remote devices during processing

• etc. User Information Testing

• The user documents will be reviewed for clarity, ease of use, details of all required system facilities, and details of all system error messages together with sufficient information to allow the replications of errors

• etc. Maintainability • Reviewing and Evaluating Maintainability

• etc. Documentation Test procedures, test data, and test results should be documented in a

manner permitting objective pass/fail decisions to be reached. They should also be suitable for review and objective decision making subsequent to running the test, and they should be suitable for use in any subsequent regression testing. Errors detected during testing should be logged, classified, reviewed, and resolved prior to release of the software. Software error data that is collected and analyzed during a development life cycle may be used to determine the suitability of the software product for release for installation. Test reports should comply with the requirements of the corresponding test plans. The acceptance tests shall demonstrate that the bidder has met each and every requirement specified within the contract and has delivered an effective operational system.

Complete System Acceptance (UAT)

At the end of the System Acceptance period, GHMC will acknowledge complete system acceptance in writing to the bidder upon completion of the following:

• All required activities as defined in the bid document including all changes agreed by GHMC and delivered by the bidder and accepted by GHMC

• All required system functionality as defined in the bid document including all changes agreed by GHMC and delivered by the bidder and accepted by GHMC

• All required documentation as defined in this bid document including all changes agreed by GHMC and delivered by the bidder and accepted by GHMC

• All required training as defined in this bid document including all


GHMC Page 181


changes agreed by GHMC and delivered by the bidder and accepted by GHMC

• All identified shortcomings/defects in the systems have been addressed to GHMC’s complete satisfaction

The bidder MUST agree to above criteria for complete system acceptance and further agree that: In order to accept the system, GHMC MUST be satisfied that all of the work has been completed and delivered to GHMC’s complete satisfaction and that all aspects of the system perform acceptably. The functional/logical acceptance of the system will only be certified when the proposed system is installed and configured at the sites according to the design and that all the detailed procedures of operating them have been carried out by the bidder in the presence of GHMC staff NOTE: The acceptance test of the application system will be conducted with the live/actual data. 3RD Party Acceptance Testing, Audit and Certification by STQC The primary goal of Acceptance Testing, Audit & Certification is to ensure that the system meets requirements, standards, and specifications as set out in this RFP and as needed to achieve the desired outcomes. The basic approach for this will be ensuring that the following are associated with clear and quantifiable metrics for accountability:

• Functional requirements • Test cases and Requirements Mapping • Infrastructure Compliance Review • Availability of Services in the defined locations • Performance and Scalability • Security / Digital Signatures • Manageability and Interoperability • SLA Reporting System • Project Documentation • Data Quality Review

As part of acceptance testing, audit and certification, performed through a third party agency, GHMC shall review all aspects of project development and implementation covering software, hardware and networking including the processes relating to the design of solution architecture, design of systems and sub-systems, coding, testing, business process description, documentation, version control, change management, security, service oriented architecture, performance in relation to defined requirements, interoperability, scalability, availability and compliance with all the technical and functional requirements of the RFP and the agreement. GHMC will establish appropriate processes for notifying the SI of any deviations from defined requirements at the earliest instance after noticing the same to enable the SI to take corrective action. Such an involvement of the Acceptance Testing & Certification agencies, nominated by GHMC, will not, however, absolve the operator of the fundamental responsibility of designing, developing, installing, testing and commissioning the various components of the project to deliver the services in perfect conformity with the SLAs. Application audit is part of SI scope.


GHMC Page 182

Following sub sections discusses the acceptance criteria to be adopted for system as mentioned above: Functional Requirements Review: The system developed by SI shall be reviewed and verified by the agency against the Functional Requirements signed-off between GHMC and SI. Any gaps, identified as a severe or critical in nature, shall be addressed by SI immediately prior to Go-live of the system. One of the key inputs for this testing shall be the traceability matrix to be developed by the SI from system. Apart from Traceability Matrix, agency may develop its own testing plans for validation of compliance of system against the defined requirements. The acceptance testing w.r.t. the functional requirements shall be performed by both independent third party agency (external audit) as well as the select internal department users (i.e. User Acceptance Testing). Infrastructure Compliance Review: Third party agency shall perform the Infrastructure Compliance Review to verify the conformity of the Infrastructure supplied by the SI against the requirements and specifications provided in the RFP and/or as proposed in the proposal submitted by SI. Compliance review shall not absolve SI from ensuring that proposed infrastructure meets the SLA requirements. Security Review: The software developed for system shall be audited by the agency from a security & controls perspective. Such audit shall also include the IT infrastructure and network deployed for system. Following are the broad activities to be performed by the Agency as part of Security Review. The security review shall subject the system for the following activities:

• Audit of Network, Server and Application security mechanisms • Assessment of authentication mechanism provided in the application /components/

modules • Assessment of data encryption mechanisms implemented for the solution • Assessment of data access privileges, retention periods and archival mechanisms • Server and Application security features incorporated etc.

Performance: Performance is another key requirement for system and agency shall review the performance of the deployed solution against certain key parameters defined in SLA described in this RFP and/or agreement between GHMC and SI. Such parameters include request-response time, work-flow processing time, concurrent sessions supported by the system, Time for recovery from failure, Disaster Recovery drill etc. The performance review also includes verification of scalability provisioned in the system for catering to the requirements of application volume growth in future. Availability: The system should be designed to remove all single point failures. Appropriate redundancy shall be built into all the critical components to provide the ability to recover from failures. The agency shall perform various tests including network, server, security, DC/DR fail-over tests to verify the availability of the services in case of component/location failures. The agency shall also verify the availability of services to all the users in the defined locations. Manageability Review: The agency shall verify the manageability of the system and its supporting infrastructure deployed using the Enterprise Management System (EMS) proposed by the SI. The manageability requirements such as remote monitoring, administration, configuration, inventory management, fault identification etc. shall have to be tested out.


GHMC Page 183

SLA Reporting System: SI shall design, implement/customize the Enterprise Management System (EMS) and shall develop any additional tools required to monitor the performance indicators listed under SLA prescribed in this RFP. The Acceptance Testing & Certification agency shall verify the accuracy and completeness of the information captured by the SLA monitoring system implemented by the SI and shall certify the same. The EMS deployed for system, based on SLAs, shall be configured to calculate the monthly transaction-based payout by GHMC to SI. Project Documentation: The Agency shall review the project documents developed by SI including requirements, design, source code, installation, training and administration manuals, version control etc. Any issues/gaps identified by the Agency, in any of the above areas, shall be addressed to the complete satisfaction of GHMC. Data Quality: The Agency shall perform the Data Quality Assessment for the Data / migrated by SI to the system. The errors/gaps identified during the Data Quality Assessment shall be addressed by SI before moving the data into production environment, which is a key mile stone for Go-live of the solution.


GHMC Page 184

ANNEXURE 3 – EXISTING IT INFRASTRUTURE AT GHMC Existing Servers at Data Centre of GHMC The following table depicts the list of servers available at various locations of GHMC Equipment Type Usage Remarks To Buyback To retainServers IBM E-Series 232 Free Server Not In Use Yes - IBM E-Series 232 Free Server Not In Use Yes IBM E-Series 232 Free Server Not In Use Yes RS 6000 F80 AIX Server Not In Use Yes Dell Work Station Webserver1 2007 Yes Dell Work Station Webserver2 2007 Yes IBM E-Series 232 Not In Use IBM E- Series 220 Free Server Not In Use Yes

IBM E- Series 220 (4 Servers)

Located at Khairtabad, Abids, Secunderabad, Charminar circles

Not in Use Yes

Dell Work Station Mail server 2007 Yes Dell Work Station Development (Web)

Server 2007 Yes

Desktop System Proxy server Windows 2007 Yes Desktop System Proxy server Linux 2005 Yes

Desktop System Instaxx server(Messages) 2005 Yes

Desktop System Antivirus Server 2007 Yes Dell work Station DB Test server 2007 Yes IBM P-4 Series – 2 No’s (RAC) Model- 630 Data Base Servers 2005 Yes

IBM P-4 Series – 2 No’s Model –615 Application servers 2005 Yes

IBM P-5 Server Model-550 ERP Database server 2007 Yes IBM P-5 Server Model-550 ERP Application Server 2007 Yes IBM P-5 Server Model-510 ERP Development

Server 2007 Yes

IBM P-6 Server Model-520 Hyperion server 2008 Yes HP Proliant DL380 Rack server KM Atom Server 2011 Yes

Desktop system Antivirus Server 2010 Yes Desktop system GPF application 2010 Yes Desktop system LRS application 2005 Yes Dell Workstation BPS application 2007 Yes Dell Workstation Lampex PTHHD server 2007 Yes Dell Workstation Visiontek PTHHD server 2007 Yes Dell Workstation Visiontek PTHHD test

server 2007 Yes

Desktop System Grievance server 2011 Yes Desktop System Kasaya Monitoring

server 2011 Yes

Desktop System Fileserver 2007 Yes HP Proliant ML 350 GIS database server 2006 Yes Dell Workstation GIS Application server 2007 Yes All 2007 & older systems are to be condemned.


GHMC Page 185

Other Equipment at Data Centre The table below outlines the storage and other equipment’s currently available at various location of GHMC Equipment Type Description Remarks To Buyback To retain

Auto Tape Loader 6 Cartridges Model 3581-L23 Ultrim tape

Yes

SAN Switch 2 Numbers Model 3534-F08 / 2005

Yes

Cisco Gigabit switch 2 Numbers 2010 Yes Storage Devices

Ds4300 – 1 TB Raw Raid 1 with 2 Hot spares 2005 Yes

Exp-810 -1.6 TB Raw Raid 1 and Raid 5 with 1 hot spare

2007 Yes

Ds3400 -2.1 TB Raw Raid 5 with 1 Hot spare 2009 December Yes

Available Network Equipment at GHMC

Location Device Name Date of Purchase

To Buyback To retain

Head Office CISCO 7606 Router 17-04-2011 Yes Head Office Cisco catalyst 4503E 17-04-2011 Yes Head Office Cisco 3641 Router 2004 Yes Head Office Cisco catalyst 3750(DMZ) 2006 Yes Head Office Cisco 2811 Router(ISP) 2010 Yes Head Office NetAsq f200 firewall (Database) 08-04-2006 Yes Head Office NetAsq f200 firewall (Internet) 08-04-2006 Yes Head Office Sonicwall Pro2040 (VSNL Internet) 27-02-2007 Yes Head office Netasq MFiltro200 Antispam Device 2011 Yes CIRCLE OFFICE Abids Cisco 2610 Router 2006 Yes Secunderabad Cisco 2611 Router 2006 Yes Khirthabad Cisco 2610 Router 2006 Yes Charminar Cisco 2610 Router 2006 Yes Kukatpally Cisco 1841 Router 17-04-2011 Yes Serilingampally-1 Cisco 1841 Router 17-04-2011 Yes Kapra Cisco 1841 Router 17-04-2011 Yes Uppal Cisco 1841 Router 17-04-2011 Yes Malkajgiri Cisco 1841 Router 17-04-2011 Yes LBnagar Cisco 1841 Router 17-04-2011 Yes Gaddiannaram Cisco 1841 Router 17-04-2011 Yes Rajendranagar Cisco 1841 Router 17-04-2011 Yes Alwal Cisco 1841 Router 17-04-2011 Yes Qutubullapur Cisco 1841 Router 17-04-2011 Yes Rcpuram Cisco 1841 Router 17-04-2011 Yes Patancheruvu Cisco 1841 Router 17-04-2011 Yes Serilingampally-2 Cisco 1841 Router 17-04-2011 Yes H.O - Northzone Cisco Aironet 1300 Yes Sec bad-zonal Cisco Aironet 1300 Yes H.O Indira Park) Cisco Aironet 1300 Yes Indira Park Cisco Aironet 1300 Yes


GHMC Page 186

Location Device Name Date of Purchase

To Buyback To retain

H.O side (CMTC) Cisco Aironet 1300 Yes CMTC Cisco Aironet 1300 Yes Existing Software Licenses in GHMC The following table provides information on the software licenses available at GHMC Details of Software licenses available with GHMC at various locations

S.No Software / Tool Name Current Where Available (Central

Data Centre / Zonal / Circle)

Current Version

No. of Licenses

Operating Systems 1. IBM Aix 5.2 8 Data Centre 2. IBM Aix \Hyperion 6.0 1 Data Centre

3. Windows 2000 Advanced Server Service Pack 4 9

Data Centre – 5 Zonal Offices – 4

4. Windows 2003 Service Pack 2 2 Data Centre

5. Red Hat Enterprise Linux 5 5.0 Data Centre 6. Linux Fedora 9.0 Free Data Centre 7. Red Hat Linux 4.2 Data Centre Database Software 8. Oracle 9i 9.2.0.8 Data Centre 9. Oracle 10g 10.2 Data Centre 10. SQL Server 2000 - HO (Town Planning) 11. MS Access 2000 - Head Office (Election Dept.) Anti-Virus

12. Kaspersky 6.0.3 1200 DC & HO ,ZO, Circles and cooperators

Application Software 13. ASP 3.0 - Data Centre 14. Oracle Developer 2000 6.0 - Data Centre 15. RGS Server 9.2 1 Data Centre The selected system integrator has the option to either extend the AMC for the existing licenses or provide new software’s with required licenses to GHMC based on the solution proposed by the system Integrator as per the RFP. UPS Available at GHMC The following table provides the availability of UPS in various locations of GHMC offices Location Existing UPS

Capacity Remarks To Buyback To retain

Ground Floor 6 KVA 2011 Yes First floor 6 KVA Before 2005 Yes

Second Floor 10 KVA, 6 KVA, 15 KVA &15 KVA

10 KVA & 6KVA before 2005 &15 KVA in 2007

Yes

Third Floor 6 KVA Before 2005 Yes Fourth Floor 10 KVA 2010 Yes


GHMC Page 187

Location Existing UPS Capacity Remarks To Buyback To retain

Fifth Floor 6 KVA Before 2005 Yes Sixth floor 6 KVA Before 2005 Yes Charminar 10 KVA Before 2005 Yes Abids 3 KVA + 10

KVA Before 2005 (10KVA not in Use)

Yes

Secundrabad Circle 6 KVA Before 2005 Yes Khairatabad 3 KVA + 15

KVA 3 KVA Before 2005 / 15 KVA in 2008

Yes

Kapra 10 KVA Before formation of GHMC (2005)

Yes

LB Nagar 10 KVA Before formation of GHMC (2005)

Yes

Gaddi Annara 5 KVA Before formation of GHMC (2005)

Yes

Rajendranagar 10 KVA Before formation of GHMC (2005)

Yes

Serilingampally 10 KVA Before formation of GHMC (2005)

Yes

Serilingampally 10 KVA 2010 Yes Ramachandrapuram 3 KVA Before 2005 Yes Patancheru 3 KVA Before 2005 Yes Kukatpally 10 KVA Before formation of

GHMC (2005) Yes

Qutubdullahpu 10 KVA Before formation of GHMC (2005)

Yes

Alwal 10 KVA Before formation of GHMC (2005)

Yes

Malkajgiri 10 KVA Before formation of GHMC (2005)

Yes

Secundrabad ZO 10 KVA 2010 Yes GHMC have Existing 2 * 15kv Power ware UPS which is connected parallel to server room Data center. The total Load of Data center is 33% (each ups) Desktops Available at GHMC

Location

Year Of Purchase 2001 2004 2005 2006 2007 2008 2009 2010 2011 Total

Abids 14 5 15 7 22 63 Alwal 7 3 1 4 15 Circle 18 5 8 10 3 1 1 28 Circle 4 9 8 5 6 6 34 Circle 5 4 4 5 3 16 Gaddiannaram ZO 1 21 22 EZ Kapra -1 13 2 2 2 12 31 EZ LB Nagar - 3 9 11 3 1 10 34 EZ Uppal - 2 11 1 2 6 2 22 Head Office 1 123 48 14 108 6 6 40 346 K-Bad 35 11 17 2 10 6 81 Kukatpally 1 5 4 4 6 5 3 28 Malkajgiri 9 6 2 17 Patancheruvu 5 5 Quthubullapur 8 2 5 1 16


GHMC Page 188

Location

Year Of Purchase 2001 2004 2005 2006 2007 2008 2009 2010 2011 Total

Rajendra Nagar 13 3 6 4 4 30 RC Puram 1 5 4 4 6 5 3 28 Sec-bad Zone 1 9 13 23 Shelingampally - N 14 1 4 19 Shelingampally - S 4 4 15 3 2 11 1 40 IT Section – HO 35 35 ULB &Mahila Bhavan 92 92 Grand Total 1 2 276 108 70 228 15 142 113 1025 Note: All the desktops pertaining to 2007 & before are to be condemned and to be covered under Buy Back Option Printers Available at GHMC

Make and Model Year of Manufacturing 2006 2007 2008 2009 2010 2011 Grand Total

Canon 3108 B 28 28 Color 6110 6 1 7 Color HP2600 2 2 Fax machine 827 3 2 5 HP 1007 155 155 HP 1008 15 15 HP 1010 1 1 HP 1566 57 57 HP 1606 1 1 HP J 4580 1 1 HP LJ M 1213 MFP 17 21 38 HP1020 62 62 RICOH SP 232 SF COLOR 3 3 Samsung ML2010 18 18 XEROX - PE220 2 11 13 26 Xerox 3117 101 6 107 XEROX 3130 1 1 Grand Total 57 26 120 20 188 173 583 Note: All the printers pertaining to 2008 & before are to be condemned and to be covered under Buy Back Option As-Is Situation of Laptops Available at GHMC Make & Model Year of Manufacturing Total To Buyback To retainWipro 2008 45 Yes Compaq 420 2010 175 Yes Photo Copy Machines Available at GHMC


GHMC Page 189

Location Section Make Model To Buyback To retain

Second Floor Facility Center CANON I R C 3200 N Yes

Second Floor IT Work Center WC 7132 (Color)

Yes

Others Other HP 3390 Yes Fifth Floor SE-I Sharp AR 5120 Yes Fifth Floor ENC Sharp AR 5120 Yes Third Floor AC UCD Sharp AR 5020 Yes Fifth Floor ENC Canon 1 R 3530 Yes Fifth Floor TP Toshiba E Studio 16 Yes Fifth Floor HNC Canon G P 210 Yes Sixth Floor LAQ Konica Estudio 350 Yes Sixth Floor Audit Work center WC 245 yes Sixth Floor SE-ll Konica M 250 Yes Sixth Floor SE Project Sharp AR 5127 Yes Khairathabad EE Div 7 Sharp AR 5120 Yes Khairathabad UCD Cir 10 Toshiba E Studio 200 Yes

Sixth Floor Fire prevention Cell

Sharp AR 5120 Yes

Khairathabad Tax 10 Work center Xerox 5645 Yes Khairathabad Audit Work center Xerox 5645 Yes Khairathabad EE Div 8 Canon 1 R 2000 Yes Khairathabad EE Div 10 Canon 1 R 1600 Yes Khairathabad Tax 7 Canon 1 R 1600 Yes Secundrabad Circle ENGG-12 Konica Estudio 350 Yes

Others CMTC Canon 1 R 1600 Secundrabad Circle TP Work center Xerox 5225

Secundrabad Circle Election Toshiba E Studio 16 Yes

Secundrabad Circle ENGG-12 Sharp AR 5120 Yes

Secundrabad Zonel AUDIT Work center Xerox 5645 Yes

Secundrabad Zonel

Administration Konica Estudio 350 Yes

Secundrabad Zonel Electrical Konica Estudio 350 Yes

R.C Puram Computer Cell RICOH Mp 2000 le Yes

Serilingampalli-2 Computer RICOH Mp 2000 le Yes

Serilingampalli-1 Computer Section RICOH Mp 2000 le Yes

Patanchervu ENGG RICOH Mp 2000 le Yes Others Other HP 3390 Yes Serilingampalli-1 TPO RICOH Mp 2000 le Yes Abids Tax Cir 8 TOSHIBA E Studio 16 Yes Abids PD 5 SHARP AR 5320 Yes

Ground Floor CPRO Chamber CANON 1 R 1600 Yes

Fifth Floor DY CE KONICA KM 250 Yes Third Floor Dy sports SHARP AR 5120 Yes Third Floor UCD CANON 1 R 1600 Yes Third Floor UCD TOSHIBA E Studio 200 Yes


GHMC Page 190

Location Section Make Model To Buyback To retain

Third Floor Aasara WORK CENTER

WC 7345 (Color)

Yes

Third Floor Special Comm Sharp AR 5127 Yes

Third Floor LWS Sharp AR 5020 Yes Third Floor Legal Canon 1 R 3300 Yes Fourth Floor Electrical Sharp AR 5020 Yes Third Floor Election Work center WC 245 Yes

Third Floor General Admin Konica Estudio 350 Yes

Fourth Floor Veternary Canon 1 R 1600 Yes Fourth Floor CMOH Sharp AR 5320 Yes Fourth Floor AC Planing Sharp AR 5320 Yes Fourth Floor AC H&S Work center WC 245 Yes Second Floor AC Election Toshiba E Studio 16 Yes

Fourth Floor EE Electrical Sharp AR 5120 Yes

Serilingampalli-1 ZC Peshi Ricoh Mp 2000 le Yes Serilingampalli-1 Audit Work center WC 5645 Yes

Kukatpalli Computer Cell Toshiba E Studio 450 Yes

First Floor Secretary Canon 1 R 3300 Yes Charminar EE Div-3 Sharp AR 5120 Yes Ground Floor Vigilance Konica KM 210 Yes

First Floor Mayor Office Canon 1 R 3530 Yes

Others Other Xerox 5834 Yes Second Floor Central Tax Work center WC 245 Yes Second Floor FA Canon 1 R 3530 Yes Secunderabad Circle UCD Toshiba E Studio 200 Yes

Kukatpalli Dy. Comm Peshi Ricoh Mp 2000 le Yes

Kukatpalli Computer Cell Toshiba E Studio 450 Yes

Qutubullapur Tax Konica Estudio 350 Yes Others Other Hp 3390 Yes Charminar Tax 4 Sharp AR 5120 Yes Charminar Tax 4 Work center WC 5655 Yes Charminar TAX5 Canon 1 R 1600 Yes Charminar TAX5 Work center WC 5645 Yes Charminar ENG-DIV-1 Canon 1 R 1600

Charminar Zonal Commissioner

Work center WC 5645 Yes

Charminar UCD Cir 4 Toshiba E Studio 200 Yes Charminar ENG-DIV-2 Canon 1 R 1600 Yes Charminar EE Div-3 Sharp AR 5020 Yes Abids DMC Toshiba E Studio 16 Yes Abids Eng. Div 6 Sharp AR 5120 Yes Abids Eng. Div 6 Work Center WC 5655 Yes

Abids JNNURM (HYD) work Center WC 5655 Yes

Abids Tax Cir 9 Work center WC 5655 Yes Abids PD-3 Sharp AR 5120 Yes Abids PD-2 Canon 1 R 1600 Yes Khairathabad EE Div 9 Sharp AR 5320 Yes


GHMC Page 191

Location Section Make Model To Buyback To retainOthers CMTC Canon 1 R 2000 Yes Abids PD-1 Sharp AR 5020 Yes Secundrabad Circle QCC Div 1 Canon 1 R 1600 Yes

Abids EE Div-5 Sharp AR 5120 Yes Abids PD3 Sharp AR 5120 Yes Abids UCD-9 Toshiba E Studio 200 Yes Abids EE 4 Canon 1 R 1600 Yes Budda Bhavan H.L.W.B.M Canon 1 R 1600 Yes Alwal Computer Canon IR 2016 Yes L.B.Nagar Conunter Work center M 128 Yes Khairathabad ZC Work center WC 5745 Yes Kapra Computer Work center M 128 Yes Malakpet CTO Work center M 128 Yes

Third Floor Facility Center Work center WC 245 Yes

Gaddiannaram Zonal ZC Konica Estudio 350 Yes

Second Floor Facility Center Work center WC 245 Yes

Sixth Floor Facility Center Toshiba E Studio 230 Yes

Uppal Computer Cell Sharp AR 161 Yes

Uppal Computer Cell Canon 3180 I Yes

Uppal Computer Cell Canon 1 R 2000 Yes

Fifth Floor TP Canon 1 R 3530 Yes Budda Bhavan H.L.W.B.M Konica KM 210 Yes Others Other Xerox 5223 Yes

Fourth Floor Facility Center Work center WC 245 Yes

Budda Bhavan DMOH Toshiba E Studio 16 Yes Indira Park Office Toshiba E Studio 16 Yes Indira Park Office Sharp AR 5320 Yes Secundrabad Circle Tax Konica KM 250 Yes

First Floor Secreatary Toshiba Duplo Dp 460

Yes

Gaddiannaram Zonal AUDIT Sharp AR 161 Yes

Gaddiannaram Zonal Accounts Work center PRO 420 Yes

MalkajGiri Computer Sharp AR 161 Yes

First Floor Commissioner Office Work center 5020 Yes

Ground Floor Printing Press Ricoh DX 3440 Yes

Ground Floor Printing Press Ricoh DX 4542 Yes

Serilingampalli-1 Computer Section Konica Estudio 350 Yes

Abids JNNURM Canon 1 R 1600 Yes


GHMC Page 192

Connectivity Scenario at GHMC The following table depicts the various connectivity sources available at the GHMC head quarters Equipment Type Description Circle office connectivity to head office through leased lines 2 MBPS Head office intranet LAN 100mbps layer –II switch network. Circle office intranet LAN 100 mbps Switch network BSNL ISP 2 MBPS DSL (TATA) Broadband 4 Mbps (webhosting and proxy) DSL (TATA) Broadband 5 Mbps (Proxy) DSL (TATA) Broadband 1Mbps (For Test) E-Seva network AP Online network The following table depicts the various connectivity sources available at the GHMC Circle offices Location MLLN Provider Speed Circuit Number Billing Date Kukatpally BSNL 2Mbps 15597 March 31st Serlingam pally-1 BSNL 2Mbps 15603 March 31st Kapra BSNL 2Mbps 15600 March 31st Uppal BSNL 2Mbps 15602 March 31st Malkajgiri BSNL 2Mbps 15601 March 31st LB Nagar BSNL 2Mbps 15598 March 31st Gaddiannaram BSNL 2Mbps 15599 March 31st Rajendranagar BSNL 2Mbps 15604 March 31st Alwal BSNL 2Mbps 16764 March 31st Qutubullapur BSNL 2Mbps 16765 March 31st Patancheru BSNL 2Mbps 15595 March 31st Ramachandrapuram BSNL 2Mbps 15596 March 31st Serlingam pally-ii BSNL 2Mbps 17376 March 31st Kairthabad BSNL 2Mbps 13505 March 31st Secunderbad BSNL 2Mbps 13503 March 31st Abids BSNL 2Mbps 13502 March 31st Charminar BSNL 2Mbps 13504 March 31st The connectivity charges will be paid by GHMC directly to the service provider.


GHMC Page 193

ANNEXURE 4 – EXISTING IT MANPOWER AT GHMC HEAD QUARTERS

The following table shows the existing manpower who are presently working at the GHMC headquarters to manage the existing applications of GHMC

Designation No of Positions Project Leader 1 Team Leader 3 Senior System/Network Admin 1 Data Base Administrator 2 Jr System Administrator 2 Jr Network Administrator 2 Hardware Engineers 5 Web Content Manager 1 Senior Progarmmers 3 Junior Programmers 5 Trainee Programmers 2 SeniorGIS Analyst 3 Junior GIS Analyst 3 Administrative Officer 1 Total 34


GHMC Page 194

ANNEXURE 5 – DETAILS OF OFFICE LOCATIONS

1. GHMC Head Office, 2nd floor, GHMC complex, Tank bund road, Hyderabad -500063 2. O/o Deputy Municipal Commissioner, Kapra Circle, GHMC near ECIL X roads,

Ranga Reddy 3. O/o Deputy Municipal Commissioner. Uppal kalan, GHMC, Uppal kalan Municipality

,Uppal Cross Roads, Hyderabad – 500039 4. O/o Deputy Municipal Commissioner, LB Nagar Municipality, near MRO office,

Saroornagar, Venkateswara Nagar, Hyderabad – 500035 5. O/o Deputy Municipal Commissioner, (Gaddiannaram) H.No.23-30/1, Krishnaveni

nagar, Municiapl Office building, RR District, Hyderabad-500068 6. O/o Deputy Municipal Commissioner, Sardar mahal, Charminar, Hyderabad -

500002 7. O/o Deputy Municipal Commissioner. Executive Officer, Near BSNL office,

Rajendranagar, Hyderabad - 500032 8. O/o Deputy Municipal Commissioner., Khairatabad, near Shadan College,

Hyderabad-500004 9. O/o Deputy Municipal Commissioner., GHMC Parking Complex, 4th floor, Abids,

Hyderabad - 500001 10. O/o Deputy Municipal Commissioner., Sy.No.25a, Serilingampally, Municiapl Office

-1, Bombay Road, RR District, Hyderabad - 500032 11. O/o Deputy Municipal Commissioner. Municipal Office, Sy.No.25a, Serilingampally,

Municiapl Office-2, Bombay road, Near E-seva Centre, Old Bombay road, RR District, Hyderabad-500032

12. O/o Deputy Municipal Commissioner., GHMC Patancheru Circle, Near Post Office, Patancheru, Medak District - 502319

13. O/o Deputy Municipal Commissioner. GHMC ramachnadrapuram, Near Zilla Parishad High School, Ramachandrapuram, Hyd-500032

14. O/o Deputy Municipal Commissioner., Kukatpally, Janathanagar, Moosapet, Kukatpally Municiapl Office, Hyderabad

15. O/o Deputy Municipal Commissioner. Qutubullapur, HMt Road, Chintal Municipal Office, Hyderabad - 500055

16. O/o Deputy Municipal Commissioner. Alwal Municiaplity, Near Balaji temple, Secunderabad - 500010

17. O/o Deputy Municipal Commissioner. GHMC, malkajgiri, Near Ayyappa Swamy Temple, Geeta nagar, Hyderabad-500047

18. GHMC Malakpet Parking yard Office, Dy Executive Engineers, Dr.No.16-7-487, Jailgarden, Beside malakpet railway Station, Chaderghat, Hyderabad - 500024

19. GHMC Imlibun Transfer Station Office, Beside Imlibun Park, Opp.Shivaji Statue, on the Shivaji Bridge, Imlibun, Hyderabad

20. GHMC Khairatabad Parking yard Office, Beside MMTS railway Station, Khairtabad, Hyderabad-500004

21. GHMC Yousufguda Transfer Station Office, Near Krishnakanth Park, Yusufguda, Hyderabad

22. GHMC Kavadiguda Parking Yard, No.1-3-1026, Behind Marriot Hotel, Near Goshala, kavadiguda, Hyderabad

23. GHMC Tankbund Transfer Station Office, Beside Snow world lower tankbund Road, Hyderabad

24. GHMC Jawaharnagar Dumping Yard Office, Jawaharnagar, Shamirpet Mandal, Near Army Dental College, Jawahar nagar, Ranga Reddy District

25. GHMC Putlibowli Office, D.No.5-1-115, Putli Bowli, koti, Hyderabad - 500001 26. GHMC Indira Park Office, Opp: Ramakrishna Mutt, Near NTR Stadium, Lower Tank

Bund Road, Hyderabad


GHMC Page 195

27. GHMC Buddha Bhavan Office, Buddha Bhavan, 1st floor, beside Boats club, Secunderabad

28. GHMC City managers Training Centre, road No.12, Banjara Hills, Hyderabad 29. GHMC Zonal Office (North), Opp. Secunderabad Contonment Court West

Marredpally, Secunderabad - 500023 30. GHMC Engineering Stores , Door No.14-8-299, Begum Bazzar, Chudi Bazzar,

Hyderabad 31. Harihara Kala Bhavan, Secunderabad.

Date post:	23-May-2018
Category:	Documents
Upload:	tranphuc
View:	230 times
Download:	4 times