EXPRESSION OF INTEREST TO SHORT-LIST SOFTWARE DEVELOPMENT AGENCY (SDA) FOR CCTNS CORE APPLICATION SOFTWARE (CAS)

Transcription

1 E-GOVERNANCE MISSION MODE PROJECT (MMP) CRIME AND CRIMINAL TRACKING NETWORK SYSTEM (CCTNS) EXPRESSION OF INTEREST TO SHORT-LIST SOFTWARE DEVELOPMENT AGENCY (SDA) FOR CCTNS CORE APPLICATION SOFTWARE (CAS) NATIONAL CRIME RECORDS BUREAU (NCRB) MINISTRY OF HOME AFFIARS GOVERNMENT OF INDIA

2 DISCLAIMER Ministry of Home Affairs (MHA) is initiating a program called Crime and Criminals Tracking Network System (CCTNS) and the National Crime Records Bureau (NCRB) is the nodal agency at the National level on behalf of MHA. As part of CCTNS, NCRB intends to develop a CCTNS Core Application Software (CAS) through a Software Development Agency (SDA). This EOI is the first step in identifying the SDA. This document has been prepared on the basis of information that is presently available with MHA and NCRB and that which is publicly available. The sole objective of this document is to solicit Expression of Interest (EOI) from interested parties for taking part in the future process leading to selection of a Software Development Agency (SDA). While this document has been prepared in good faith, no representation or warranty, express or implied, is or will be made, and no responsibility or liability will be accepted by MHA, NCRB or any of their employees, advisors or agents as to or in relation to the accuracy or completeness of this document and any liability thereof is hereby expressly disclaimed. Interested Parties may carry out their own study/ analysis/ investigation as required before submitting the EOI. This document does not constitute an offer or invitation, or solicitation of an offer, nor does this document or anything contained herein, shall form a basis of any contract or commitment whatsoever. Some of the activities indicated to be carried out by MHA/NCRB subsequent to the receipt of the responses are indicative only. MHA/NCRB has the right to continue with these activities, modify the sequence of activities, add new activities or remove some of the activities, as dictated by the best interests of the project. 2

3 Table of Contents 1 Purpose of the EOI Background on CCTNS Introduction to CCTNS Implementation Model CCTNS Application Software Outline of Scope of Work Outline of Scope of Services around CAS (State) Outline of Scope of Services around CAS (Centre) Pre-qualification Criteria for the SDA Conditions to be met by the SDA Tentative Timelines Response requirements Appendix

4 1 Purpose of the EOI National Crime Records Bureau (NCRB), Ministry of Home Affairs (MHA), invites Expression of Interest from interested professional Software Development Agencies (SDA) for a turnkey project to: a) Develop, enhance and maintain the CCTNS Core Application Software to be deployed at the States (hereafter referred to as CAS). b) Develop, enhance and maintain the CCTNS Core Application Software to be deployed centrally at National Crime Records Bureau (hereafter referred to as CAS (Centre)) The selected SDA would be working under the guidance and supervision of National Crime Records Bureau (NCRB), MHA, NIC and DIT. NCRB will host the Project at the Central Government level on behalf of the MHA. The purpose of this EOI is to help NCRB determine the list of software development agencies that would be invited to respond to the RFP to be issued by NCRB on behalf of MHA. NCRB reserves the right to determine the list of software development agencies that would be invited to bid for the project. 2 Background on CCTNS A Common Integrated Police Application (CIPA) programme had been initiated in the year to bring about computerization and automation in the functioning at the police station with a view to bringing in efficiency and transparency in various processes and functions at the police station level. Over a period of time, it was felt that a stand-alone system of this nature would have limited utility, and there was a need to expand the functional application and build in networking capabilities in the system. This was required both from the angle of Management Information Systems (MIS) requirements and storage, collation, analysis and transmission/sharing of crime and criminals related information at the police station, District, State and Central levels. 4

5 2.1 Introduction to CCTNS The Ministry of Home Affairs has conceptualized the Crime & Criminals Tracking Network and Systems (CCTNS) project as a Mission Mode Project under the National e-governance Plan (NeGP). This is an effort of the Government of India to modernize the police force giving top priority to enhancing outcomes in the areas of Crime Investigation and Criminals Detection, in information gathering, and its dissemination among various police organizations and units across the country, and in enhancing Citizen Services. CCTNS aims at creating a comprehensive and integrated system for enhancing the efficiency and effective policing at all levels and especially at the Police Station level through adoption of principles of e-governance, and creation of a nationwide networked infrastructure for evolution of IT-enabled state-of-the-art tracking system with the following objectives: Goals and Objectives of CCTNS i. Provide Enhanced Tools for Investigation, Crime Prevention, Law & Order Maintenance and other functions like Traffic Management, Emergency Response, etc. a. Utilize IT for efficiency and effectiveness of core policing operations b. Provide information for easier and faster analysis ii. Increase Operational Efficiency by: a. Reducing the necessity to manually perform monotonous and repetitive tasks b. Improving the communication e.g. Police messaging, systems, etc. c. Automating back-office functions, and thereby release police staff for greater focus on core police functions iii. Create platforms at State and Central levels for sharing crime and criminal information/ databases across states and across the country. This would enable easy sharing of real-time information across police stations and districts at the State level and across states at the National level, there by resulting in: a. Improved investigation and crime prevention 5

6 b. Better tracking of criminals, suspects, accused, repeat offenders, etc. iv. Create a platform for sharing intelligence across the states, across the country and across other state-level and GOI-level agencies v. Improved service delivery to the public/ citizen/ stakeholders a. Access to police services in a citizen-friendly manner b. Provide alternate modes of service delivery such as internet (for general requests such as NOC, for following up on status c. Example ministry of external affairs, road transport The Scope of CCTNS The scope of CCTNS spans all 35 States and Union Territories and covers all police stations (approximately 14,000) and all higher police offices (approximately 6,000) in the country. The CCTNS project includes vertical connectivity of police units (linking police units at various levels within the States police stations, district police offices, state headquarters, SCRB and other police formations) as well as horizontal connectivity (linking police functions at State and Central level to external entities). CCTNS also provides for a citizen s interface to provide basic services to citizens. National Crime Records Bureau (NCRB) is the central nodal agency for CCTNS. The CCTNS project covers all 35 states and union territories. Within the states, the 14,000+ police stations and 6,000+ higher offices (including District HQ, Range Offices, Commissionerates, State HQ, etc.). The following are the suite of proposed solutions / modules for the Police Department (indicative): 1. Registration, Investigation, and Prosecution Solutions 2. Crime Prevention Solutions 3. Reporting Solutions 4. Collaboration Solutions 5. Emergency Response Management Solutions 6. Citizen and External Interfacing Solutions 7. Traffic Solutions 6

7 8. Law and Order Solutions The scheme would finance the following components under CCTNS: CCTNS application to address the police functionality under the scope of CCTNS, procurement and installation of hardware (including PCs and peripherals), connectivity infrastructure, state-level Data Centres, site preparation and commissioning, capacity building and handholding, digitization of historical data, data migration from legacy systems (if any) and specialized applications and infrastructure (that are approved under the CCTNS scheme). These components would be provided as a bundle of services to be executed by a Systems Integrator at state level. Funds would be released only against the procurement of the prescribed bundle of services and not against the procurement of individual components thereof. 2.2 Implementation Model The Implementation Strategy for CCTNS has been devised keeping in view the following considerations: NeGP frameworks of centralized planning and decentralized implementation Need for ownership of the State Governments of the overall program implementation, the infrastructure, application and the database; at the same time maintaining uniformity of information systems in order to facilitate information sharing and availability across states and at the national level Need to undertake the implementation of this large-scale project in a coordinated manner through experienced implementation agencies by entrusting them with the responsibility of end-to-end implementation with a clear set of deliverables. Need to synchronize the rollout of the hardware and network components with the rollout of other equally important soft components such as training, capacity building and change management. Accordingly, CCTNS 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 and performance of CCTNS. The bundle of services would include the following: 7

8 1. The SI would customize and implement CCTNS core application provided by NCRB 2. The SI would develop and deploy additional functionality that is scoped under CCTNS (for some of the additional functionality, the central nodal agency would provide the functional specifications to ensure standardization across states). 3. Procurement, installation and commissioning of hardware (including PCs, peripherals, etc.) at police stations and higher offices including site preparation 4. Procurement, deployment and commissioning of communications infrastructure at all police stations and higher offices; building and commissioning of state Data Center 5. Capacity building 6. Change management 7. Procurement, configuration and commissioning of specialized infrastructure and applications as necessary Each state would select a SI who would be selected by the state through a competitive bidding process. 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. 2.3 CCTNS Application Software On behalf of MHA, NCRB would provide all states with a CCTNS Core Application Software (CAS), which would be configured, customized, enhanced and deployed by the States. NCRB intends to engage the services of a professional software development agency (SDA) to develop CAS that would be provided to all States. The State level Systems Integrators (SI) would configure, customize and enhance CAS according to the unique requirements of the State before deploying it. The SDA would design and develop CAS based on the functional requirements specified by NCRB, and would also manage CAS. NCRB would select an SDA through a competitive bidding process, of which the first step is the short-listing of software development agencies who would be invited to bid for the development of CAS. The purpose of this EOI is to help in the short-listing software development agencies that would be invited to bid for CAS development. 8

9 3 Outline of Scope of Work The SDA that will be selected through this EOI and subsequent RFP is expected to design, develop, and provide the Core Application Software for the States. The SDA will be responsible for supporting the State Level System Integrator(s) for the final implementation of the developed Core Application Software. The Core Application Software for the States will provide the limited but core functionality that is required at the Police Station. The remaining functionality will be developed by the State Level System Integrator(s) on top of the Core Application Software. The scope of this project covers design, development, testing, enhancements, training, maintenance and user/technical support for the two main components of the CAS: i. CAS (State): CAS would be provided to States and Union Territories by NCRB, on behalf of MHA. The Systems Integrators (SI) selected by the States would configure, customize, extend and deploy the State CAS per the unique requirements of each State. The SDA would be required to design, develop, test, enhance and maintain CAS. The SDA would also be required to create all required documentation including operations manuals, technical manuals and user manuals. The SDA would be responsible for providing training content, user/technical support, and deployment support to the System Integrators at State Level for configuration and customization of the application. ii. CAS (Centre): This component is an application at the Central (GOI/NCRB) level that accepts/gathers/ collects data from States and processes/ organises the same. CAS (Centre) would be deployed at NCRB. Relevant input, output and report formats and processing requirements would be included as per the requirements of GOI/ GOI Agencies. The SDA would be required to design, develop, test, enhance and maintain CAS. The SDA would also be required to create all required documentation including operations manuals, technical manuals and user manuals. The SDA would be responsible for providing training content, user/technical support, and deployment support to NCRB for central deployment. 9

10 CCTNS Core Application Software (CAS) would be built as a platform to provide the basic framework to capture crime and criminal information, mainly at the police station, while providing the states with the flexibility to build their state specific applications around it and in addition to it. The SDA would build the CAS (State and Centre) based on the Functional Requirements Specifications (FRS) and Technical Architecture Guidelines provided by NCRB on behalf of MHA and its agencies. In doing so, the SDA would explore the option of leveraging to the extent possible, existing applications, including the applications at NCRB, State level applications or any other applications in this domain. Brief Functional Scope for the Core Application Software (State) The CAS (State) would focus on policing function at the State level and would be used at Police Stations, District and other Higher Offices and other police formations. It would be a web-based application designed to operate in low bandwidth and/or unreliable connectivity scenarios. CAS (State) would cover the following indicative functionality: a. Registration b. Investigation c. Prosecution d. Search/Query functionality e. Reporting and MIS f. Police messaging system In addition to the Core Application Software for the States, the SDA is expected to design, develop, and implement the Core Application Software for the Center. The Core Application Software (Center) will provide the required functionality to the NCRB for collating the information from the various states and provide the necessary reports to the NCRB. Brief Functional Scope for the Core Application Software (Center) This component is an application at the Central (GOI/MHA/NCRB) level that accepts/gathers/ collects data from States and processes/ organises the same. It analyses and reports on policing 10

11 information on a national scale, acts a hub for information exchange between states and with external agencies and serves the information, analysis and reporting needs of MHA. CAS (Centre) would be deployed at NCRB. Relevant input, output and report formats and processing requirements would be included as per the requirements of GOI/ GOI Agencies. CAS (Center) would cover the following indicative functionality: a. Interfaces with States to receive, gather, extract, collate and organize crime- and criminals-related data b. Carry out required analysis to serve the information, reporting and intelligence needs of MHA, other ministries and agencies, the Parliament and Citizens. CAS (Centre) would also share the results of their analysis with States and Union Territories. c. Interfaces with external entities such as Passports, Immigration to receive and share data with them. The CAS will be built for the GOI (with NCRB coordinating on behalf of MHA) for the minimum common functionality that is common across the States/ UTs and falls under the scope of CCTNS. The CAS shall be provided, along with its source code, to the States, for configuration, customization, enhancement and maintenance by the States (through the Systems Integrators to be chosen by the States). The CAS must be parameterized to accommodate the configurations required for each State with respect to the common functions. The CAS has to be built as a platformindependent application so that it is easily portable across platforms i.e. the application should be portable across hardware, operating systems, database systems, enterprise platforms etc. It is envisaged that CAS would be a web application based on hybrid architecture, designed to operate in low bandwidth and/or unreliable connectivity scenarios. It is further envisaged that the CAS would be based on a service-oriented architecture (SOA) to enable reuse of basic services. 3.1 Outline of Scope of Services around CAS (State) The following are the indicative primary functions that will be undertaken by the SDA: 1. Application Development of CAS (State) i. Conduct System Study/ Field Study for assessment and requirements gathering. 11

12 ii. Preparation of System Requirements Specifications (SRS) based on the Functional Requirements Specifications (FRS) provided by NCRB on behalf of MHA. iii. Preparation of design documents including High Level Design and Detailed Design documents iv. Development of CAS including User Interfaces v. Development of reports and forms. vi. Formulation of test plans. vii. Testing of the configured solution. viii. User Acceptance Testing and incorporating the feedback into the solution. ix. Final Testing of the solution including functional, stress, and load testing. x. Getting the solution certified through a third party agency identified by NCRB. xi. Project Management: the SDA would deliver CAS under the overall supervision of NCRB, MHA and DIT/ NIC. The SDA would be responsible for preparing and adhering to the detailed project plan, pre-determined timeliness and quality of the various modules of CAS. 2. Data Migration Methodology and Tools i. The SDA should prepare a Data migration plan identifying data migration requirements and specifications for migrating data from the legacy and manual systems in operation at the State level. 3. Professional Services and Implementation Support for Deployment of CAS (State) i. Provide access to interim and final releases, including code and related documentation ii. Provide installation instructions and instructions for general configuration of the system iii. Provide server sizing, configuration, tuning, and any additional guidelines required for the State Level System Integrator for proper commissioning of the system. iv. Provide training (online content, presentations, classroom training) on the installation, configuration and deployment of CAS v. Preparation of detailed and comprehensive documents including Operations manuals, Technical literature and training materials including training manuals, presentation decks and online materials. 12

13 vi. Provide details of Application Configuration parameters and instructions for configuration of the same vii. Maintenance (bug fixes, release management) of CAS. viii. Develop an online MIS and repository for providing centralized access to all documents, manuals, code, updates, training content, and help documents. ix. Incorporate feedback from States to enhance the CAS. x. The SDA would help NCRB in developing the internal competency to take over the management of State CAS within a period of approximately 3 years from the commencement of the engagement. 4. Application Management Services for State CAS i. The SDA would enhance and maintain (bug fixes, enhancements) the CAS for a period of approximately 3 years from the commencement of the engagement, after which NCRB would takeover the management of State CAS. ii. The SDA should work with NCRB in preparing an exit management plan. This must be reviewed and updated regularly till NCRB takes over the management of the application. 3.2 Outline of Scope of Services around CAS (Centre) The following are the indicative primary functions that will be undertaken by the SDA: 1. Application Development of CAS (Centre) i. Preparation of System Requirements Specifications (SRS) based on the Functional Requirements Specifications (FRS) provided by NCRB on behalf of MHA and after determining to what extent existing applications could be leveraged. ii. Preparation of design documents including High Level Design and Detailed Design documents iii. Development of CAS (Centre) iv. Development of reports and forms as required v. Formulation of test plans vi. Testing of the configured solution vii. User Acceptance Testing and incorporating the feedback into the solution. 13

14 viii. Final Testing of the solution including functional, stress, and load testing. ix. Getting the solution certified through a third party agency identified by NCRB. x. Project Management: the SDA would deliver CAS under the overall supervision of NCRB, MHA and DIT. They would be responsible for preparing and adhering to the detailed project plan and the timeliness and quality of the various modules of CAS. 2. Data Migration Services Data migration services for migrating the data from the legacy and manual systems in operation including: i. The SDA should prepare a Data migration plan identifying data migration requirements and specifications for migrating data from the legacy and manual systems in operation at the Centre. 3. Training Service for CAS (Centre) i. User training to different user groups at NCRB and SCRBs based on the nature of usage ii. The SDA would help NCRB in developing the internal competency to take over the management of Center CAS within a period of approximately 3 years from the commencement of the engagement. iii. Develop an online repository for providing centralized access to all documents, manuals, code, updates, training content, and help documents. iv. Provision of detailed and comprehensive documents for the above stages including Operations manuals, User manuals and Technical literature and training materials including training manuals, presentation decks and online materials. 4. Implementation Support for CAS (Centre) i. The SDA would provide NCRB and any other agencies involved with CAS (Centre) all the support necessary in deploying the application at NCRB. This support would include but is not limited to helping create and test the production environment at NCRB, deployment of CAS (Centre), integration testing and acceptance testing. 5. Application Management Services for CAS (Centre) 14

15 i. The SDA would enhance and maintain the CAS (Centre) for a period of up to 3 years from the commencement of the engagement, after which NCRB would takeover the management of CAS (Centre). ii. The SDA should work with NCRB in preparing an exit management plan. This must be reviewed and updated regularly till NCRB takes over the management of the application. 4 Pre-qualification Criteria for the SDA Participation is invited from Software Development Agencies (SDA) who meet all of the following criteria. 4.1 The participating Software Development Agency must be a single legal entity registered in India and must have a Registered Office in India. The company should have been operational in India for at least the last five financial years. 4.2 The SDA should have been profitable for at least three of the last five financial years. 4.3 The SDA must have a proven and consistent track record of successfully offering software development and related services. The SDA must have earned annual turnover of Rs. 250 Crores or more from software development services during the last two financial years. 4.4 The SDA must have been successfully assessed SEI CMMI Level 4 or above for IT Services and the certification must be currently held. 4.5 The SDA must have at least 300 employees as part of their software services group, including software developers, architects, project managers, professional integration services and business analysts (employees from sales and marketing, Human Resource, Finance, Administration and other corporate functions must not be counted). Please provide sample résumé of at least 15 people who would be working on this project if awarded. 15

16 4.6 The SDA must have designed, developed and maintained at least 2 applications/products each with a total software services value of Rs. 5 Crores during the last 5 years. These projects must satisfy the following additional requirements: The application/product must be web-based The application/product must have been deployed in at least 10 customers/sites with unique requirements, and must have successfully been configured, customized, enhanced and deployed to meet the unique requirements of each customer/deployment site The application/product must have been maintained for a minimum period of 1 year 4.7 The SDA must have prior experience of working on at least 1 software services project for Government of India, any of the State/UT governments or Public Sector Units. The project must be worth at least Rs. 1 Crore. 5 Conditions to be met by the SDA 5.1 Considering the sensitive nature of the domain of the project and the data involved, it is mandatory for all short-listed companies to be security-vetted by MHA. 5.2 The SDA must be able to commit to engaging with NCRB for at least 3 years. During this period, all senior members of the project must continue with CCTNS. 5.3 The SDA should agree to make presentations related to the information sought in the response to this EOI, if so requested by NCRB. This will not be a paid activity; the SDA must be ready to undertake this activity on its own. 5.4 The Software Development Agencies shortlisted on the basis of this EOI should agree to develop and demonstrate a proof of concept, with basic functionality, if so requested by NCRB. The demonstrations would be part of the technical evaluation during the technical/ financial bid process and will not be a paid activity. The SDA must be ready to undertake this activity on its own. 16

17 5.5 Participants declared by MHA to be ineligible to participate for unsatisfactory past performance, corrupt, fraudulent or any other unethical business practices shall not be eligible. 5.6 Breach of general or specific instructions for bidding, general and special conditions of contract with MHA or any of its other client organizations during the past 5 years may make a firm ineligible to participate in EOI bidding process. MHA reserves its right to subject the bidders to security clearances, as it deems necessary. 6 Tentative Timelines Tentative timelines for the SDA identification are as follows: Activity Publication of Expression of Interest Per EOI conference (If required) Last date for receipt of responses Timeline T T + 1 week T + 3 weeks T: Date of publication of EOI. NCRB reserves the right to modify these indicative timelines. 7 Response requirements Interested Software Development Agencies may furnish their Expression of Interest (EOI) by giving all the necessary documents in English as specified in the Response Formats for each of the abovementioned qualifying criteria as proof of having the minimum requirements. The Expression of Interest in a sealed cover along with an application duly signed by an authorized signatory must reach the following address on or before Aug by 1500 hours. Inspector General of Police (CCTNS) 17

18 National Crime Records Bureau East Block 7, R. K. Puram New Delhi Address: Phone: , NCRB reserves the right to withdraw this EOI if it is determined that such action is in the best interest of the Government of India. Short-listed SDAs would only be issued formal tender enquiry/request For Proposal inviting their technical and commercial bids at a later date. NCRB reserves the right to determine the shortlist of SDA based on the responses to this EOI. NCRB undertakes that all the information shared by the SDA will be held in strict confidence and will not be made public unless directed by court of law. Respondents are requested to submit their responses in the format given below. a. Covering Letter as per the format provided in Appendix I b. Requested information in the suggested formats along with the mandatory supporting documents for each of the criteria as provided in Appendix II For any queries related to this notice on Expression of Interest, an may be sent to projectcctns@ncrb.nic.in on or before July 27, [EOI Query] may be included in the subject line. 18

19 Appendix Appendix I: Covering letter from the Software Development Agency Company Letterhead [Date] Inspector General of Police CCTNS National Crime Records Bureau East Block 7, R. K. Puram, New Delhi Reference: Notice on Expression of interest to design, develop and maintain CCTNS Core Application Software Dear Sir, This is to notify you that our company intends to submit a proposal in response to the RFP for designing, developing and maintaining CCTNS Core Application Software. Primary and Secondary contacts for our company are: Name: Title: Company Name: Address: Phone: Mobile: Fax: Primary Contact Secondary Contact We confirm that the information contained in this response or any part thereof, including its exhibits, and other documents and instruments delivered or to be delivered to NCRB is true, accurate, verifiable and complete. This response includes all information necessary to ensure that the statements therein do not in whole or in part mislead the department in its short-listing process. We fully understand and agree to comply that on verification, if any of the information provided here is found to be misleading the short listing process or unduly favours our company in the short listing process, we are liable to be dismissed from the selection process or termination of the contract during the project, if selected to do so, for undertaking the design, development and maintenance of CCTNS Core Application Software. 19

20 Should we be shortlisted after the evaluation of this response, we agree to have security vetting done by MHA. We understand that we are liable to be dismissed from the selection process if any association is revealed that may give rise to conflict of interests. Should we be selected to execute this project, we agree to engage with this project for a minimum of 3 years. We also agree to ensure that the senior people staffed on this project would continue to be engaged with this project for a minimum of 3 years. We agree to abide by the conditions set forth in this EOI. It is hereby confirmed that I/We are entitled to act on behalf of our corporation/company/ firm/organization and empowered to sign this document as well as such other documents, which may be required in this connection. Dated this, Day of, 2009 (Signature) (In the capacity of) Duly authorized to sign the EoI Response for and on behalf of: Sincerely, [SOFTWARE DEVELOPMENT AGENCY S NAME] Name Title Signature Date (Name and Address of Company) Seal/Stamp of the SDA CERTIFICATE AS TO AUTHORISED SIGNATORIES I,, certify that I am of, and that who signed the above response is authorized to bind the corporation by authority of its governing body. (Seal here) Date 20

21 Appendix II: INDEX OF FORMATS & SUPPORTING DOCUMENTS If the responder is a single legal entity, they would be required to provide all relevant forms listed below. In case of a consortium, the lead participant firm would be required to provide all requested information. All participating firms would be required to furnish their Certificates of Incorporation issued by the Registrar of Companies. Criteria refers to paragraph Requested Information Form I: Details of the Organization 4.1 Mandatory Supporting Documents 1. Certificate of Incorporation from Registrar Of Companies (ROC) 2. Relevant sections of Memorandum of Association of the company or filings to the stock exchanges to indicate the nature of business of the company Form II: Financial Information 4.2 Mandatory Supporting Documents 1. Auditor Certified financial statements for the last five (5) financial years, i.e. from to (if the results of are not ready, provide information from to ). Please include only the sections on P&L and the assets, not the entire balance sheet. Form III: Information on Revenue from Software Services 4.3 Mandatory Supporting Documents 1. Certification by the company auditors supporting the revenue breakup for the last two financial years. 4.4 Form IV: CMM Level Assessment Mandatory Supporting Documents 1. Copies of the CMM LEVEL assessments for the last three years. 4.5 Form V: Employee Information Mandatory Supporting Documents 1. Attestation from the company auditor confirming the employee profile information. In case of consortium, attestations from auditors 21

22 of all participating firms are required. 2. Sample résumé of at least 15 people who would be allocated to this project of awarded. Form VI: Project Information (Web-based projects with multiple deployment instances) 4.6 Please use one form per project. Mandatory Supporting Documents 1. Details for the relevant project(s) Form VII: Project Information (Government Experience projects) 4.7 Please use one form per project. Mandatory Supporting Documents 1. Details for the relevant project(s) It is mandatory to provide all the information requested and failure to do so would be treated as noncompliance. NCRB undertakes that the information would be kept confidential until and unless mandated by the Court of Law. 22

23 Appendix III: Formats for Responses Form I: Details of the Organization Name Nature of the legal status in India Nature of business in India Date of Incorporation Date of Commencement of Business Address of the Headquarters Address of the Registered Office in India Other Relevant Information Form II: Financial Information Revenue (in INR Crores) Profit Before Tax (in INR Crores) FY FY FY FY FY Form III: Information on Revenue from Software Development Services Revenue from Software Development Services (in INR Crores) FY FY

24 Form IV: CMM Certification Information Level of CMM Certification Date of Assessment Units/Locations Assessed Name of the Assessing company and their contact coordinates Form V: Information of Employees and Skill Sets Employee Profile Total Project Managers Technical Architects Business Analysts Software developers with Database design experience Software developers with web-based service oriented application design experience Software developers Testing and Quality Assurance Experienced in Graphical User Interface design and Usability Professional Services Team for Integration and application deployment Total Supporting Documents 1. Certification by the company auditors supporting the employee information provided above 2. At least 15 résumé of people who would be working on this project if awarded. Other Relevant Information (if any): 24

25 Form VI: Information on Prior Experience in building web-based applications/products with multiple unique instances of deployment (one form for each project reference duly certified by authorized signatory) Client Information Name of the client Details of the Client s contact person for reference. Please include name, designation, postal address, contact phone, fax number and id Any relevant details about the client organization Project Details Nature of the Project Total Contract Value for Software Development Services part Please provide a description of the project including the goals of the project, scope of the project, roles of the team members involved, uniqueness of the project, complexity of the project, significant achievements and any other detail considered significant. Geographical Locations of Implementation Present status of the project Number of Locations/Units at which the project is implemented Peak project team size of the SDA during development Peak on-site (at the client location) project team size of the SDA post-implementation. Please provide the breakup into different teams Date of commencement of the project Date of successful completion of the project. If the project is not completed, please provide dates of key milestones already achieved and target dates for upcoming key milestones up to and including the expected date of completion. Scope of the SDA s Engagement (software development, infrastructure procurement, training, etc.) Duration of maintenance support Details of the Solution 25

26 Number of Instances of deployment of the solution Technical Details of the solution: (web-based deployment, nature of configurability of the solution) Relevance of the implementation to the current project Other Relevant Information Form VII: Information on Government Project Experience (one form for each project reference duly certified by authorized signatory) Client Information Name of client (Government Department) Country of Client/application deployment Details of the Client s contact person for reference. Please include name, designation, postal address, contact phone, fax number, id Any relevant details about the Client Total number of Employees of the client organization (department/ministry/psu) Project Details Nature of the Project including the government domain and nature of engagement Total Contract Value of the project Please provide a description of the project including the goals of the project, scope of the project, and any other detail considered significant. Present status of the project Date of commencement of the project Date of successful completion of the project. If the project is not completed, please provide dates of key milestones already achieved and target dates for upcoming key milestones up to and including the expected date of completion. 26