Online Transaction Processing System

1. INTRODUCTION With a view to take the benefits of Information Technology to the common man, as a part of its e-Governance initiative, the Government of Andhra Pradesh, India embarked on a number of IT Projects that seek to redefine public service CARD (Computer-aided Administration of Registration Department)-digital registration of legal deeds, TWINS (Twin Cities Network Services) one-stop citizen service centers, MPHS (Multi-Purpose Hosehold Survey) IT at the grassroots level of mandals. These IT projects focus on the common man. The objective of MPHS is to provide to the citizens of the State, selected services and information of revenue department in an efficient, reliable, transparent and integrated manner on a sustained basis through easy access to a chain of Citizen Information Counters (CICs) set up at the 1125 mandal offices. The MPHS project has been implemented in a phased manner with 1 server and 2 clients established at each mandal office, with the software and databases relating to citizen data and land records data. It is now proposed to take up a pilot project that encompasses all departments and agencies of the Government at the mandal level through an OLTP (Online Transaction Processing System) with the mandal office as the focal point or hub. 2. SALIENT FEATURES OF MPHS PROJECT The MPHS project has been implemented at 1125 mandals in 3 phases during the period 1997 2000. The system has been designed to manage the socio-economic data of 30,000 to 70,000 citizens of the mandal and the land records data of the 30 to 50 revenue villages of the mandal. The systems and the databases are distributed and are not networked either vertically along the hierarchy of the revenue department or horizontally across the departments and agencies of the Government at the mandal level. Employees of the Revenue department, trained initially, manage the systems. The systems are installed in a small LAN on the Citizen Information Counters designed uniformly and erected in all mandal offices.

3. SERVICES PROVIDED THROUGH MPHS AT PRESENT Applications of revenue department listed below have been made fully operational as part of the MPHS project.

3.1 MPHS & HDS Data 1. Caste-Nativity certificates to citizens

2. Socio-economic data of households ( HDS Data) 3.2 Land Records 1. Database of land records 2. Extracts of land title & Occupancy 3. Record of Rights 4. Details of Crops grown on each holding 5. Revenue and Irrigation - Demand Collection and Balance 3.3 Public Distribution System 1. Registration & Licensing of Fairprice Shop Dealers 2. Allotments of essential commodities to FPS dealers 3. Registration of households for issue of ration cards 4. Monitoring distribution of ration to the households 3.4 Others 1. Employee Payrolls 2. Land Acquisition 4. THE MPHS TECHNOLOGY The MPHS project is architected using the Client-Server technology 4.1 Hardware & Software 1 PIII Database Server Windows NT network Oracle database server Forms 4.5 front-end 2 KVA UPS 2 clients and 2 printers 4.2 Design & Implementation The MPHS software has been designed and developed by two organizations- the MPHS portion by the AP Technology Services and the Land records portion and other applications by National Informatics Centre. The implementation has been undertaken by the CCLA ( Chief Commissioner of Land Administration)

5. CURRENT STATUS OF MPHS Project Currently MPHS project is being used primarily for issuing Caste-and-Nativity Certificates. So far about 75,000 certificates were issued cumulatively in all the mandals. The systems are being used to update and integrate the MPHS, HDS and Land records databases. It is assessed that the full potential of the project can be realized only when the MPHS systems are integrated with the systems of

other related departments and networked through an appropriate architecture. Hence the current proposal has been designed. 6. REQUEST FOR PROPOSAL (RFP) 6.1 Objectives The present proposal is to take up a Pilot Project involving design, develop and implement an OLTP system that achieves the following basic objectives : Integrates all the Government offices at the mandal level horizontally Achieves vertical integration of all Government data Creates OLTP capabilities for as many departmental application systems as needed Creates an architecture that permits sharing of data across departments Ensures automatic updating of core data, especially of citizens and land, by automating all the processes that impact on or depend on such core data Integrates seamlessly with the legacy systems in place already especially the MPHS, CARD, subtreasury, TWINS and any other systems that may become operational during the period of implementation of the Pilot. Creates a model that is replicable - technologically and commercially Provides a cost-effective method of networking horizontally and vertically across departments and across mandal, district and state levels. Conforms to the highest standards of security of systems, transactions and data Provides a web-based interface to the citizens and businesses intending to transact with the Govt agencies. Is compatible with the overall IT Architecture defined by the Government of Andhra Pradesh

6.2 Pilot Mandal Bhongir Mandal of Nalgonda District has been selected as the pilot area considering factors such as proximity to Hyderabad, availability of representative offices of most of the departments, being a small municipality etc. The pilot should network all the mandal level institutions, district level institutions and the state level offices of the selected departments. 6.3 Implementation model Since it is a pilot involving lot of original work and experimentation, the total cost of the pilot will be borne by the Government ( IT&C) department. The commercial model evolved during the pilot will be used to replicate the system in all the mandals of the state using the Publc-Private-Partnership model announced by the Government through GOMs 23 IT&C department dated 293-2001 (available on www.ap-it.com) . The developer selected through this

RFP Process will implement the pilot on a turn-key basis, within the scope defined in Clause xx of this RFP. 6.4 Basic responsibility of the developer The developer shall design, develop all the component systems, install required hardware, software and other equipment and maintain the same for a period of one year from the date of acceptance, as per the details mentioned in this document. They shall develop and build the complete system subject to the conditions prescribed in this document, in the time frame prescribed and operate the system, at their expense, till the expiry of one year from the date of acceptance. 6.4 Implementation time The developer shall implement the Pilot project in 16 weeks from the date of award. Timely execution of the project and maintaining the required uptime of all the systems to ensure provision of quality services to the citizens are the main ingredients of the proposal. 6.5 Other specifications The GOAP makes available the space in all the Govt. departments/ agencies participating in the OLTP pilot project The Computerized systems will be operated by the personnel drafted from the Govt. department /agencies participating in the OLTP pilot project.

7.PREQUALIFICATION OF BIDDERS Entrepreneurs desirous of bidding for the pilot project shall have the following qualifications : a. The bidder shall have experience in implementing Information Technology Projects of comparable size and complexity preferably in the area of OLTP systems. b. The Turnover of the bidder in installation and maintenance of hardware, development of software, installation and maintenance of complex Wide Area Networks and OLTP systems, shall exceed Rupees One Crore in each of the proceeding two years ( FY 1999-2000 & 2000-01) c. The bidder should have employed at least 50 I.T Professionals as on 31-3-2001. For this purpose, the term IT professional means a person with a graduate degree or a higher qualification in computer or communication areas from a recognized university. d. The bidder can partner with another person (firm or company) subject to the following conditions.

1. A maximum of one partner will be allowed for each bidder, otherwise called the principal bidder. 2. The principal bidder shall disclose full particulars of the partner in the prescribed format while submitting the tender and enclose with it a copy of the agreement between them in relation to this tender. 3. The contractual agreement of GOAP will be with the successful principal bidder(s) and their partner(s). The bidder and the partner are jointly and severally responsible for discharging the contractual obligations with GOAP. 4. The turnover of the partner in the areas specified in clause (iii) above, shall be counted towards the pre-qualifying turnover of the principal bidder and the IT professionals employed by the partner as on 31-3-2001 shall be counted towards the prequalifying requirement mentioned in clause (iv). 8. SCOPE OF WORK COVERED BY THE RFP The Scope of work covered by this RFP includes the following (i) Design and development of an OLTP software solution to achieve the objectives set forth in Clause 6.1, adopting open, interoperable standards and scalable, state-of-the-art architecture, in the most costeffective manner. The scalability shall take into consideration the horizontal and vertical scaling which is the essence of the Pilot. (ii) Procurement and installation of hardware of servers and clients required for achieving the basic objectives (iii) Networking the different component systems and the backend servers of the associated departments and agencies, (iv) Implementation of the solution, (v) Training of GOAP personnel in running of the applications (vi) Maintenance of the systems on a turn key basis including supply of consumables, stationery and media, and any other material required essentially to provide the services for a period of one year from the date of acceptance of the entire system by GOAP. (vii) Integration of the applications relating to various departments and agencies as specified in this document and future applications of like nature, to be specified by the GOAP, to achieve the overall objectives of the pilot. (viii) Ensuring that the response-times in accessing the servers and provision of counter services shall be as specified in clause 14 at all times during the currency of the arrangement.

Provision of some of services implemented in the Pilot, to the citizens on the Internet, as may be specified by the GOAP. 9. REQUIREMENTS OF THE SOLUTION 9.1 ARCHITECTURE OF THE SOLUTION: a) The architecture of the solution should be based on open, inter-operable standards and shall not be based on any proprietary systems or packages. More specifically, the operating systems, the system software and RDBMS packages, the networking operating systems, the protocols, the APIs, shall conform to open standards and shall be proven to be supported at least by three vendors. The architecture should be proven to be highly scalable and capable of delivering high-performance in varied field conditions. b) The architecture should be able to interface with the existing applications of various participating departments/agencies, with marginal customizations where required. In other words, the user-interface in respect of each application / service shall be identical, as defined by the respective department or agency, for all operators and for all modes of access i.e at the departmental counters or on the Internet. c) To the extent permitted by the over-all architecture, Internet technologies may be deployed for easy scalability, replicability and cost-effectiveness. d) The architectural and design features shall enable adoption of multiple delivery channels at the customer end including Pilot counters, Internet kiosks etc. e) A representative functional architecture is shown in Annexure I. The developer may adopt a more elegant architecture that is technologically superior and more cost-effective. 9.2 APPLICATION SOFTWARE a) The developer shall adopt the structures of the databases of the respective participating departments and agencies of the Government. No basic change can be made in any of the databases of the participating departments / agencies to accommodate particular demands necessitated by the architecture chosen by a bidder. In exceptional cases the department may consider adopting and modifying marginally its processes and information organization to suit the solution. b) The user interfaces shall be uniform to the extent practicable and as approved by the GOAP c) The application software shall produce the output reports, receipts, certificates as prescribed by the respective department / agency. The illustrative list outputs can be obtained by prospective bidders from the GOAP, for this purpose. f) The software solution shall be capable of handling all categories of electronic payments i.e., through internet, Credit card or debit card, ATM,

(ix)

etc. The solution should be based on latest state-of-the-art technology and practices such as web-enabled solutions etc. g) The software solution shall provide for the facility of the networking across the Pilot centers for all information and filing services. In other words a citizen should be able to avail the services at any counter of the pilot project, established in the pilot area, irrespective of his place of residence. h) The operator shall carry out the modification of software as required from time to time, depending upon the amendments made by the Government to laws, rules and procedures in connection with the administration of these services. The design features of the software should be, to this extent, based on master codes and follow the best principles of software development. i) The developer should develop the application software for future additional services as and when required. The GOAP reserves the right to install and run some of the other applications, developed by departments and agencies of the Government, on the OLTP pilot facilities. Addition of any such applications or services in future should not degrade the performance of the system. If any augmentation in configuration is needed to meet the performance, the operator shall install the same. j) The following information relating to the existing application software of legacy systems will be made available to the developer at his option. o o o o o Data base structure and description of fields and tables. Data flow diagrams, entity-relationship diagrams. Procedures, Functions, Triggers and interface details. Source code, where essential. Report formats.

9.3 HARDWARE, NETWORKING AND ANCILLARY EQUIPMENT a) The hardware to be used by the developer shall be new and shall be capable of delivering high performance during the currency of the pilot project. The hardware shall be inspected by a team of technical experts to ensure compliance of this requirement. b) The solution should incorporate reliable network architecture, communication technology and equipment. Suitable redundancy shall be provided in the communication networks and topology. The communication systems need not be of only one type but could be different such as, leased lines of different types, dialup lines, OFC, satellite and wireless communications etc. c) The system may have to operate in heterogeneous environment wherein the back end implementations could vary. This aspect shall be firmly kept in view.

d) Off Line System - The developer shall provide required interface to the applications so as to enable conducting the transactions even when the LAN/ WAN is down. The system should update the backend servers automatically, whenever the network connectivity is restored h) UPS : The operator shall provide UPS backup of required capacity at each critical location to ensure running of business-critical processes and transactions even when there is a shut-down of power.

10. SECURITY OF THE SYSTEMS & DATA 1) The software solution shall contain all suitable security features and Firewalls using the latest features to protect and secure the databases used by the proposed system, data in transit etc. All databases, which are required to be accessed and updated on a continuous basis, shall be mirrored at the cost of the developer. The developer shall also be responsible for overall consistency and integrity of such mirrored databases. A penalty of Rs 1000 will be levied for each day when any inconsistency is noticed till the same is rectified to the satisfaction of the GOAP. 2) The developer shall maintain a log of the transactions at each center in a database. 3) Access Controls a) Access Controls shall be provided to ensure that the departmental databases are not tampered/altered/modified/deleted/ by the systemoperators, except updating the records as a part of the transaction with a citizen. Periodic surprise checks will be conducted by the GOAP officials to ensure the security and reliability of the system b) All the technical people associated with the Pilot shall be allotted passwords to monitor any modifications to the database, application software and changes to the departmental master data. c) The employees shall be allotted login user-id and password to fix up accountability for transactions carried out from any component system. d) Arrangements shall be made to prevent any unauthorized access to Servers, hardware and the network equipment. 4) While the developer is responsible for the functioning and operation of the component systems, the backend databases will be owned and maintained by the departments themselves. Government will be the owner of all data, transactions in any form kept at the centres either in electronic form or physical form such as paper etc.

11. DEPARTMENTS/ APPLICATIONS/ SERVICES TO BE COVERED 11.1 The details of departments/ applications/ services proposed to be covered in the Pilot project are given below: Department 1.Revenue Existing or New MPHS data updation Existing Land Records data Existing updation Registration of births Existing Application/ Service Value addition expected of the Developer Conversion to OLTP system Conversion to OLTP system Conversion to OLTP system; Integration with Family Welfare system of PHC Conversion to OLTP system Conversion to OLTP system Conversion to OLTP system Conversion to OLTP system Conversion to OLTP system Conversion to OLTP system Conversion to OLTP system Conversion to OLTP system Integration with subtreasury system Integration with CARD system; Integration with death registration system Integration with Irrigation & Agriculture systems Development of system; Integration with MPHS Integration with land records Integration with Cooperative Societies / banks Integration with Local Body; Integration with MRO Integration with Local Body Integration with MPHS; Integration with local body Integration with MPHS

Registration of Existing deaths Birth certificates Existing Death Certificates Existing Record of Rights Existing HDS data updation Existing FPS dealer master Existing Monitoring PDS Existing Ration Cards Existing Payroll Existing Mutations New

Record of crops

New

2.MDO 3.Sub-registrar

Benefits to BPL New families Registration of Deeds Existing Encumbrance certificates Property Valuation Transfer Duty Family Welfare Births & Deaths
9

Existing Existing Existing Existing Existing

4.PHC 5.Local Body

Department 6.Agriculture 7.Irrigation 8.Police

Property taxes New Application/ Service Existing or New Crop & Irrigation New details Crop & Irrigation New details FIR registration Existing system Caste verification of New students Crop Loans & MT New loans

9.Educational Institutions 10.Agricultural Cooperative Society 11.APTRANSCO 12.Commercial Taxes 13.Excise 14.Market yard

Integration with CARD Value addition expected of the Developer Integration with MRO & irrigation Integration with MRO & Agriculture Integration with MRO System; Integration with Court Integration with MPHS system Integration with subregistrar & MRO systems Networking vertically with their line agencies Networking vertically with their line agencies Networking vertically with their line agencies Networking vertically with their line agencies

11.2

11.3

The proposed pilot shall, in addition to providing the linkages and integration specified above, ensure that all the mandal-level offices mentioned above shall be connected to their respective supervisory offices at the district and state level appropriately, in the most costeffective manner. The nature of connectivity between different units could be dial-up, leased line, OFC, wireless or satellite or a combination of the same. The architecture should provide for Internet connectivity to all the participating departments at mandal level.

12 . FACILITIES MANAGEMENT SERVICES: The developer shall be responsible for the over all management of network and OLTP Systems which includes administration of Servers, PCs, Networking & UPS and the applications running on them and other services added from time to time. The responsibilities include the following but at the same time not limited to them. (i) Network Administration: Network Administration & Management consists the following activities but not limited to them:

10

1) Administering User IDS 2) User level help in logging on to the Network and other related activities. 3) Helping Users to use common resources on Network etc. 4) Network analysis and performance tuning. 5) Continuous monitoring & management of network during the working hours on each working day & restoration of breakdown within prescribed time limits. (ii) Systems Support: Systems Support consists of the following: a) Taking System Back Ups (Daily back ups for Database servers and Web servers). b) Installation and Reload Support on Desktop OS like Win 95/98, NT, Office 97/2000, IE etc. c) Installation and Reload Support for Server OS like Windows NT Server, SCO UNIX etc. d) Installation and Reload Support for Application software e) Rectification of system software problems due to crashing or malfunctioning of the OS; RDBMS or front end, within the time limits prescribed. f) Installation of upgrades of system software namely, OS, RDBMS, and front end g) Guarding the systems against virus infections using the latest anti-virus tools . h) To support and maintain the proprietary applications of different departments on the mutually agreed terms. (iii) Maintenance Services (for equipment not covered under parts Warranty) The Maintenance, Upkeep and Physical Security of the systems shall be the responsibility of the developer. The maintenance services of systems include: a) Preventive maintenance and includes carrying out the necessary repairs and fitting of replacement parts wherever applicable. Preventive maintenance shall not be attended during working hours.

11

b) The operator shall arrange to hold training/software workshops for improving the skills of the employees in proper usage of the hardware and its day-to-day maintenance. The workshops shall cover all the users at least once in 6 months. The first batch of such workshops shall be conducted within 45 days of the commencement of the agreement period. iv)Supply of consumables : (a) Making available all the consumables and any other goods or articles required from time to time for functional operations of pilot, which include i. Ribbons for Dot Matrix Printers ii. Cartridges for Laser Printers iii. Pre-Printed Computer stationery applications and certificates

required

for

various

(b) The stationery used for all statutory certificates shall be security paper, to prevent duplication. (c)If any doubt arises, whether any item or article can be categorized as required for functional operations or not, or with regard to the quantities used, the decision of the GOAP shall be final. (d) The developer shall maintain an inventory adequate for one months operations at each site.

13. PERFORMANCE LEVELS IN TERMS OF AVAILABILITY OF SYSTEMS Since the CITIZEN services cannot be stopped during specified service hours, the solution should consider reliability, redundancy in hardware configuration and fail safe design. No data loss is permitted and any recovery procedures should take into consideration this factor. Uptime : The overall uptime of the systems shall be 99% computed on a monthly basis for each site aggregated for the pilot area. The uptime shall be computed as per the following procedure. The working shall be based on 30/ 31 working days per month The uptime shall be computed in terms of the available working days (minus) the days of downtime using the following formula. Uptime in terms of working days during the month Available working days in the month Downtime: A downtime exceeding 1 hour on a working day shall be counted as a full day for the purpose of computation.

12

A site will be considered to be down in the following circumstances: a) When the work at any site is conducted manually on account of problems related to hardware and or /system software and/or network. b) When the systems at any site falls below the Minimum Expected Configuration (MEC) specified even though the work might be carried on with the available systems. c) The MEC is specified below for each site 90 % of the sites meant for handling governmentcitizen transactions shall be fully operational The operator shall deploy a suitable Network Management Software that maintains, inter alia, a log of all the events at all the sites in the pilot.

15. PENALTIES 15.1 Penalty for delay in launching of the Project The developer shall adhere to the time schedule indicated in Tender notification for completion of the Pilot Project. He shall complete installation and commencement within specified period from the date of handing over the site. In case of delay in execution of the project, a penalty calculated at the rate of Rs. One Thousand per every day of delay for each such site shall be levied. 15.2 Penalty for shortfall in performance levels: The prescribed uptime of the systems shall be 99% computed on a monthly basis as specified in clause 13. A down time exceeding 1 office hour on a working day, computed on a cumulative basis for each day, shall be considered as a full day of down time. For shortfall of every 0.1% of uptime below 99% a penalty of Rs 1000 will be levied. 16. TRAINING GOAP PERSONNEL 16.1 Personnel belonging to Government departments/organizations will be providing the actual services relating to the departments and agencies of the Government, by operating the systems. The developer shall train such personnel on running the applications and providing citizen services. The training shall be for a minimum period of 4 weeks and may be extended for a further period as may be required to impart the required degree of proficiency to the satisfaction of GOAP.

13

The Developer shall also be responsible for retraining the counter operators whenever changes are made in the software. The number of employees to be trained will be arrived at through the following formula, which takes care of 25 % reserve. Number of employees to be trained = (Number of PCs in the system) * 2.5 16.3 The developer should engage the data base administrators or any other technical staff required at his expense and maintain the system for a period of one year from the date of acceptance.

17. RESPONSIBILITIES OF THE DEVELOPER a) The Developer shall bear the responsibility for installation of hardware, software and all other equipment required and its maintenance for a period of one year from the date of acceptance. b) The developer shall incorporate all such features as required by the OLTP system for its information and management. These could be in the form of accounting, transaction files, log files and any other statistical reports. c) The developer shall install the Hardware or any other equipment of very high quality and it shall be new and be of standard brands. The hardware equipment, software and any other system installed should get the approval of evaluation committee before the test run is declared to have been satisfactorily completed. The developer shall replace immediately the hardware equipment or software which is found to be of inferior quality or does not suit the requirements. 18. RESPONSIBILITIES OF GOAP a) GOAP will facilitate securing permissions required for providing the OLTP system with access to the databases of the associated departments as needed. (The responsibility of networking will be that of the developer) b) GOAP undertakes the responsibility for completion of Civil works including General Electrical work and provision of furniture required at all the sites of the Pilot. However laying cable net work required for installing computers, providing electrical fittings of all types, fax, printers and Xerox machine, Air-Conditioning equipment, electronic equipment and UPS shall be the responsibility of the developer. He shall furnish a design of cable network required for all the aforementioned equipment so that an arrangement can be made by

14

GOAP for providing ducts for all such cables while executing civil works. 19. RESPONSIBILITIES OF ASSOCIATED DEPARTMENTS a) Associated departments will computerize their respective APPLICATIONS and maintain the databases. b) The servers of the departments shall be up during the period when the OLTP systems are scheduled to operate. c) The participating departments and agencies shall be responsible to take all such security measures including setting up firewalls , as are required to prevent unauthorized access to their databases. 20. NON EXCLUSIVITY, LICENSE FEE, IPR (i) The Government reserves the unrestricted right to deploy the solution developed for OLTP by any other developer or agency at locations outside the pilot area. IPR : The Intellectual Property Rights will be owned exclusively by the Government of Andhra Pradesh. The architecture, application software of the solution may be deployed by GOAP outside its own requirement, any of the Public Sector Undertakings of AP or statutory bodies under its control. The Government may come up with a portal, in the joint sector, to provide some or all of the services covered by the OLTP system.

(ii)

(iii)

21. TWO- STAGE BID PROCEDURE : The bidding will be in two stages. At the end of the evaluation in Stage I, a maximum of 3 bidders will be short-listed and they will participate in Stage II bidding. A comprehensive evaluation of the proof of concept will be made at this stage and one bidder will be selected finally. 22. STAGE I BIDDING : a) The bids in Stage I shall be in the format shown in Annexure II . The bidders shall furnish all the information sought through the formats. In case any of the columns are left blank by the bidders in the formats, the Committee will assign a zero weightage to that item. b) EMD for Stage I : An EMD of Rs 2 lakhs shall be enclosed to the bid document at Stage I. The EMD shall be in the form of a DD or pay order in favour of MD APTS. c) All the valid bids received in Stage I will be evaluated using the criteria defined below :

Criteria for evaluation of Stage I bids

Points

15

(A) ORGANIZATIONAL STRENGTHS OF THE BIDDER (WEIGHTAGE 70) (i) Turnover and financial performance, manpower & quality certification1 (ii) Experience and track record of the Bidder in the last 2 years 25 relevant technical expertise and skill-sets experience in developing enterprise-wide solutions for large organizations experience (including international experience) in providing solutions for complex citizen service systems involving OLTP systems 25

(iii)

Qualifications/competence of the key staff committed for the assignment Project Management Expert(s)

15

Systems Analyst(s) Expert(s) in e-Commerce & Internet Network & Hardware Specialist(s) Security Expert(s) Database Design & Administration & OLTP experts
Domain Expert(s) in governmental systems & procedures 5

(iv)

Local presence

Criteria for evaluation of Stage I bids

(B) SOLUTION PROPOSED (weightage 30)

Points

At this stage the bidder is expected to give a brief approach paper and an outline of the solution proposed. These are expected to provide information for evaluation based on the following criteria: (i) Understanding of the issues and project requirements 10

ISO 9000 (for software development), SEI CMM Level 3 or above, TQM, six sigma or equivalent.

16

Understanding of the project requirements, important issues and associated risks for the OLTP system. Suggested modifications and improvements to the functional requirements, architecture and other aspects in the existing legacy systems. (ii)Outline of proposed solution Proposed architecture of the solution covering Technology model Architecture of application software Networking model Security model Internet Transaction Model OLTP model Openness & Inter-operability of solution Scalability of the solution 15

The bidders are expected to propose the outline of their solution in respect of each of the above areas, with illustrations to explain the features of each of the above models and also indicate the names of the software package options and preferences.

(v)

Methodology

The bidders are expected to indicate the following in their implementation methodology: Software development model considered appropriate for OLTP project Manpower deployment plan Time frame, elaborating how the bidder plans to execute the project within the time frame of 4 months indicated in this document

Total points assigned for evaluation in Stage I

100

d) A maximum of 3 bidders will be short-listed at the end of the evaluation process in Stage I

17

e) The bidders will be permitted to visit the facilities at MPHS, CARD and TWINS project sites, and interact with the key staff by prior appointment. f) The pre-qualified bidders are required to enclose a technical approach paper to the bid document and to make a presentation to the Tender Committee, with a view to bring out the bidders appreciation of the requirements of the OLTP project, the architecture of the proposed solution, the practicability of the proposed solution and the costeffectiveness thereof. 23. STAGE II BIDDING a) A maximum of 3 bidders will be short-listed for Stage II. The Stage I EMD of all other bidders will be returned thereafter. b) Stage II EMD : The bidders short-listed for Stage II shall submit an additional EMD of Rs 2 lakhs . c) The bids in Stage II shall be in the formats at Annexure III and Annexure IV d) The Stage II bid shall consist of 2 parts namely, Technical Bid ( Annexure III) and Commercial Bid ( Annexure IV). e) Each offer should be placed in a separate envelope superscribed: Technical bid or Financial bid, as the case may be, followed by the title mentioned above against tender call: Name of the bidder and contact address should also be written on the envelope.

24. TECHNICAL BID (STAGE II) ( Annexure III) The Technical bid in Stage II shall contain the software solution offered by him in detail. He shall mention the architecture and the strategy he intends to follow to network and interface with the databases of different departments and to create an OLTP system. The bidder shall also demonstrate the proof of concept of the solution proposed by developing a prototype of registration of birth and how it updates the databases at mandal/ district and state levels, using the architecture suggested. The prototype may simulate the systems at the mandal/ district and state levels for the demo. The solution shall aim at Compatibility with the existing software of the participating departments. Should be scalable and secure. The software solution may also mention the cases where similar software solution is already in operation. Should be cost-effective It shall also include o a detailed technical documentation, reference to various industry standards to which the products included in

18

vendors offer conform, and literature concerning the proposed solution. In particular, the vendors should identify areas in which their solution conforms to open standards and areas that are proprietary in nature. Justification about proprietary components in terms of functionality and performance should be given. o A statement about appropriateness of the solution plan for operating conditions in AP, including physical infrastructure and human resources. o The facilities for training the staff and the strategy he intends to adopt for maintaining the sites for one year.

25 . FINANCIAL BIDS ( STAGE II) ( Annexure IV) (a) The financial bid should contain a Quotation for the rates for the components mentioned below in the format given in the bid document. 1) Development of application software 2) Hardware required to be installed at various sites in the participating departments 3) System Software required to be installed at various sites in the participating departments 4) Networking devices 5) Installation costs 6) Training of employees 7) Maintenance of the system and solution for 1 year 8) Miscellaneous costs 9) TOTAL COST (b) The rates quoted shall be valid for any new applications that may be introduced in future in Govt. departments as a result of the detailed study undertaken by the developer. (d) No enhancement of the rates quoted in the Commercial bid and finally approved by the Evaluation committee will be allowed during the currency of the arrangement. (e) The rates quoted shall be inclusive of all taxes, duties and statutory payments incident upon the operator.

26. BID EVALUATION PROCEDURE: OPENING OF BIDS: Immediately after the closing time, GOAP contact person shall open the technical bids and list them for further evaluation. The financial bid covers shall be listed

19

and put into a bag sealed according to GOAP procedure. The sealed bag of financial bids shall be in custody of a designated officer and the financial bids will not be opened till the completion of evaluation of technical bids. Any participating bidders may depute a representative to witness these processes. BID EVALUATION: The bidders are required to make a detailed presentation on the proposed solution and the prototype developed. The technical bids will be evaluated on the following criteria.
(A) TECHNICAL ELEGANCE & SUITABILITY OF THE SOLUTION (60 POINTS)

1. ARCHITECTURE
OPENNESS

OF THE PROPOSED SYSTEM INCLUDING SCALABILITY

&

2. Software development and implementation plans including timeframe, milestones and deliverables at various stages of implementation 3. 4. 5. 6. 7. Structure and design of the Application Prototype Technology model of the OLTP solution Design of Internet-based services Networking / routing Plans SECURITY PLAN

8. TRAINING PLANS 9. TECHNICAL STANDARDS PROPOSED TO BE ADOPTED 10. TESTING AND QUALITY CONTROL PROCESSES COMMERCIAL BID Cost-effectiveness of the solution will carry 40 points on a relative basis.

Points will be assigned to different vendors on a relative basis using the following formula L1*40 / L(x) Where L1 is the lowest commercial bid and L(x) is the bid under evaluation. GOAP may ask vendor(s) for additional information visit vendors site and/or ask for technical presentation and may arrange discussion with their professional, technical faculties to verify claims made in technical bid documentation. 27. EVALAUTION COMMITTEE

20

a) The tenders shall be evaluated by the Tender Committee constituted by the Government. b)The Tender Committee may choose to conduct negotiation or discussion with any or all the bidders. c)If there be any changes in the terms in the terms and conditions of the tender pursuant to the negotiations during the evaluation of the technical bids, which are likely to impact on the financial bids, it shall be competent for the Tender Committee, to seek revised commercial bids in sealed covers ONLY from those tenders cleared technically by the committee. While seeking such revised financial bids, the committee shall give reasons justifying the need for such a course of action. d) The decision of the Tender Committee in the evaluation of the Technical and Commercial bids shall be final. No correspondence will be entertained outside the process of negotiation/ discussion with the Committee. 28. PAYMENT TO THE OPERATOR The GOAP shall pay to the operator the consideration, fixed as per terms of the agreement with the successful bidder(s). The broad terms of payment are indicated below : Delivery of SRS Installation of hardware Installation of beta version of the entire system Testing , implementation and acceptance On successful completion of 1 year of running the system 15 % 20% 20 % 25 % 20 %

21

Annexure I Indicative Architecture of OLTP system

Internet

State Information Exchange

HOD 1 HOD 2 APSWAN

District Information Exchange

Dt Office 1 Dt Office 2

OFC Link

Mandal Information Exchange

Mandal Office ( MPHS)

PHC

Re gis

Police

Irrigation

Other Offices ..
Su b
APTRANSCO

MDO

22

ANNEXURE II FORMAT OF STAGE I BID (Pl see clause 22) I. GENERAL INFORMATION OF THE PRINCIPAL BIDDER 1. Name of the bidder (company / firm) :

2. Address 3.Telephone Nos FAX e-mail web-site : : : :

4.Legal Status Public Limited Company / Private ltd co / Partnership firm 5.Date of establishment II. GENERAL INFORMATION OF THE PARTNER 1. Name of the partner (company / firm) :

2. Address 3.Telephone Nos FAX e-mail web-site : : : :

4.Legal Status Public Limited Company / Private ltd co / Partnership firm 5. Date of establishment ============================================================= III . PREQUALIFICATION CRITERIA

1. EMD enclosed : Amount : DD/ Pay order No & date : Bank & branch : 2. Particulars of turnover ( as per audited accounts) in Rupees Crores ( 2 decimals)

23

Item of turnover (1) Principal bidder Software development Hardware maintenance Networking TOTAL (2) Partner Software development Hardware maintenance Networking TOTAL GRAND TOTAL

Turnover in 1999-00

Turnover in 2000-01

3. IT Professionals employed on 31-3-2001 Principal Bidder Partner : :

============================================================= IV) EVALUATION CRITERIA ( ORGANIZATIONAL STRENGTHS) 4. Experience & Track Record in last 2 years a) Describe how your company / firm and together with your partner, has the right competency & skill set required to implement the TWINS project ( 100 words)

24

b) Pl give details of enterprise-wide projects, OLTP projects and customer service projects implemented during last 2 years Name of Organization Period Value in Brief description of the Project crores nature of customer services and number of customers served per year

============================================================= 5. Details of key staff to be committed to this project: Sl Name No Designation Qualifications Length Service of total with service bidder Projects implemented

7 . Local Presence : Company / Branch address : Turnover effected by Branch in AP : Number of IT Professional Staff employed in AP : ============================================================= V SOLUTION PROPOSED 1.Enclose a detailed technical solution covering Your understanding of the issues and requirements of TWINS project Outline of the proposed solution Methodology of implementation 2. The approach paper shall specifically address all the points mentioned in Clause 22 of the bid document , with illustrations and names of software packages proposed to be used, diagrams to explain the architecture and any other information require to elucidate the solution.

25

3.The bidders shall, if so required, make a presentation to the tender committee on the proposed architecture of the solution. 4.The bidders may develop and demonstrate the proof of concept of the proposed solution.

Signature of the bidder Name Designation

Signature of the Partner Name Designation

26

ANNEXURE III TECHNICAL BID ( PHASE II) ( See Clauses 23 & 24)

I. GENERAL INFORMATION OF THE PRINCIPAL BIDDER 1. Name of the bidder (company / firm) 2. Address 3.Telephone Nos FAX e-mail web-site : : : : : :

II. GENERAL INFORMATION OF THE PARTNER 1. Name of the PARTNER (company / firm) 2. Address 3.Telephone Nos FAX e-mail web-site III : TECHNICAL SOLUTION A comprehensive technical solution should be enclosed covering the aspects mentioned in clause 24. The bidders shall have to show the proof of concept at this stage. They shall also state all the technology products to be used by them and the standards proposed to be adopted. : : : : : :

Signature of the bidder Name Designation Signature of the Partner Name Designation

27

ANNEXURE IV FINANCIAL BID STAGE II ( To be submitted in a separate sealed cover) (see Clause 25) I. GENERAL INFORMATION OF THE PRINCIPAL BIDDER 1. Name of the bidder (company / firm) : 2. Address : 3.Telephone Nos : FAX : e-mail : web-site : II. GENERAL INFORMATION OF THE PARTNER 1. Name of the PARTNER (company / firm) : 2. Address : 3.Telephone Nos : FAX : e-mail : web-site : III.PRICE QUOTED FOR THE PILOT PROJECT ITEM Rate quoted (Rs in Lakhs) Development of application software Hardware required to be installed at various sites in the participating departments System Software required to be installed at various sites in the participating departments Networking devices Installation costs Training of employees Maintanance of the system and solution for 1 year Miscellaneous costs TOTAL COST QUOTED Total Cost quoted in words IV. TOTAL VALUE OF ASSETS TO BE CREATED BY BIDDER:

Signature of the Partner Name Designation

Signature of the bidder Name Designation

28

29