• Save
Guidelines for preparation of a RFP for e governance projects
Upcoming SlideShare
Loading in...5
×
 

Guidelines for preparation of a RFP for e governance projects

on

  • 2,621 views

This presentation constains guidelines that may be considered by Government Departments that wish to prepare RFP's for IT / e-Governance projects

This presentation constains guidelines that may be considered by Government Departments that wish to prepare RFP's for IT / e-Governance projects

Statistics

Views

Total Views
2,621
Views on SlideShare
2,552
Embed Views
69

Actions

Likes
1
Downloads
0
Comments
0

7 Embeds 69

http://www.egovindia.in 33
http://egovkarnataka.blogspot.in 13
http://www.linkedin.com 12
http://egovkarnataka.blogspot.com 6
http://www.docshut.com 2
https://www.linkedin.com 2
http://www.slideshare.net 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Guidelines for preparation of a RFP for e governance projects Guidelines for preparation of a RFP for e governance projects Presentation Transcript

  • Experience sharing on RFP preparation Anirban Mukerji [email_address] 0-98455 18520
  • Challenges
    • Selection process should be deemed to be fair
      • Should follow CVC guidelines
    • Selection can be challenged in court
      • This can delay implementation
    • Most work complex unlike Public Works project
      • Most projects one off not repeatable
      • Limited understanding of Government Staff
        • Open standards vs. Open source, free software vs. open source
      • Vendors extremely savvy
      • Subtle changes in Tender documents can lead to certain vendors being favored
  • RFP writing process
    • Initial brief note on the project
      • What outcomes need to be achieved
    • Evaluation of technology choices
      • Centralised Architecture vs. Client Server
      • Thin Clients vs. PC’s
      • Wireless connectivity vs. Wired connectivity
      • Open source vs. proprietary software
    • Each has implication on costs and technical performance and are not comparable
    • Combination of outcome orientation vs. detailed specification of each subcomponents
      • Bangalore One – Service delivery metrics have been fixed , however hardware sizing has been left to vendor
    • However if specs are not provided how will vendor achieve desired outcomes
  • Risk Factors
    • Risk Factors should be articulated for each project
    • Some Sample Risk factors could be as following
      • For e.g. for Akshaya Project of Govt. of Kerala
        • The internet centre initially may be unviable and hence kiosk operator may not open the centre for most days
        • Kiosk operator may be untrained on use of computers
        • If Linux is specified as O/S not many people may know how to operate the system
        • In case e-Governance services are delivered from a portal connectivity may not be available for some time duration
        • Power issues
        • Ladies may feel unsafe in Kiosk as the centre is used as a club house for boys of the village
        • Inadequate support and hand holding for the kiosk operator
  • Risk Factors Contd..
    • Appointment of Consultancy organisation
      • Consultants may not be placed in a timely manner
      • Risk Mitigation Strategy
        • Penalty for delay in placement of consultants
      • Time and Material project
        • Consultancy organisation can show 2 months work for only one month work has been carried out.
      • Risk Mitigation Strategy
        • Have consultants work from defined government premises
  • Risk Factors Contd..
    • Appointment of Technical support engineers in District headquarters for Land Records computerisation project
      • Rapid turnover of Engineers whenever they get a permanent job in Bangalore
      • Risk Mitigation Strategy
        • Charge Rs. 50,000 from agency for turnover of Staff
    • Huge Risk of Bankruptcy of the Organisation during the Project Period
    • Technology Obsolescence – X Department purchased a Unix varient O/S which does not have widespread OEM hardware support
    • Software performance may degrade in 2-3 years time
  • Costing
    • Have detailed realistic cost estimates
      • Hardware
      • Software Licenses – Most licenses are processor based hence cost will increase when hardware is upgraded
      • Software development
      • Implementation
      • Data digitisation
      • Development of facilities ( front offices)
      • Manpower
      • Overheads
    • Should be compared with Commercial bid and reasons for variance + ve or – ve ascertained
  • Components of RFP
    • Scope of Work
      • Needs to be as detailed as possible
      • Vendor will take advantage of vagueness in their favour
      • Vagueness in defining SOW may lead to good organizations thinking the project to be too risky and not participating
      • Winning party may have made a miscalculation and may delay delivery
      • Prepare the Scope of Work such that even if the most inelegible vendor wins the contract the work will be executed satisfactorily
  • Timelines for Delivery
    • Milestone wise timelines with penalties for delay in each component example of an existing project
    Sl No Milestone Time for Completion Penalty for delay 1 Signing of PPP agreement with successful bidder
    • T1
    - 2 Handing over of site
    • T1+8 weeks
    3 Development of Application Software T1+14 weeks Rs X lakhs per every week of delay 4 Establishment of Centers, including Networking
    • T1+14 Weeks
    Rs N lakhs per every week of delay 5 Testing & Certification of Software Solution T1+16 Weeks Rs M lakhs per every week of delay 6 Training T1+18 Weeks Rs Z lakh per every week of delay 7 System ready for launch (XX No. of Services at YYY No. Service Centers) T1+20 Weeks Rs Y lakhs per every week of delay
  • Payment Types
    • Transaction wise payment
      • Per Driving license
      • Per bill payment
    • Paid by
      • Citizen
      • Government
    • Ultimately every thing is paid by the Government
  • Payment Models
    • Lumpsum payment models
    • Deferred payment models
      • Milestone based payment
      • Quarterly Guaranteed Revenue payment
    • Each type has its advantages and disadvantages and relevant for particular types of work
    • Bangalore One
      • Payment per transaction, incentive for the vendor to increase the number of transactions from the Bangalore One Centres
      • Disadvantage
        • Low transaction services that are in public interest may not be provided by the Vendor
  • Duration of Contract
    • Conscious decision needs to be taken
    • Very short term contracts
      • 1 year development , 1 year implementation + 2 year support and maintenance
      • will lead to again going to market after 4 years
    • Most probably Government staff will extend contract on same terms and conditions
    • Long contracts 10 years, 15 years – Risk of technology obsolescence
  • Responsibilities
    • Responsibilities of the various stakeholders need to defined in great detail
      • Government
      • Vendor ( The Scope of Work would be the definition of the responsibilities of the Vendor)
    • Responsibilities of other stake holders
      • Both private and public involved in the project.
      • Bangalore One Project promoted by the e-Governance department but dependencies on many other Government Departments
        • Electricity
        • Water
  • SLA’s
    • SLA – Service Level Agreement
    • Against each deliverable of the vendor
      • SLA during Implementation
      • SLA during Operation
      • Timeline and Quality of service needs to be mentioned
      • Penalty for not meeting SLA
      • Penalty for egregious breach of SLA
      • Termination of Agreement in case of continued breach of some SLA’s
  • SLA’s need to be SMART
    • Objective – Reach office 95% of days prior to 9.00 AM for January to December 2008
    • vs
    • Come to Office on time
    S Specific Yes M Measurable Can be measured through electronic attendance monitoring system A Achievable Since it is 95% , probably can be achieved R Relevant Punctuality will improve the environment of the department T Timely Definition of time period Jan – Dec 2008
  • . Sample SLA Placement of required no. of HD1 counter operators as per specifications S No. Item Details 1 Definition of Service or additional explanation Counter operators will have the required qualifications, experience, training and will have qualified the test set by Dir. EDCS 2 Certifying authority Chairman HD1 CMC 3 Penalty for breach Rs. 250/- per day for shortfall of every operator 4 Material Breach Placement of less than 75% of the required operator strength even after 60 days of the timeline 5 Stipulated period for mitigating material breach conditions 30 days 6 Enhanced Penalty during stipulated period Rs. 500/- per day per operator 7 Remedial performance required for mitigating material breach conditions for non termination before the end of the stipulated period Placement of atleast 90% of the operators within stipulated period
  • RFP Components
    • Pre qualification or eligibility criteria
      • Financial capability
      • Prior similar project experience
      • Should have adequate justification why certain eligibility criteria is being proposed
      • Should follow CVC guidelines
      • Difficulty in formulating eligibility criteria when novel projects are being implemented
  • CVC Guidelines
    • Guidelines were prescribed in this office OM of even number dated
    • 17/12/2002, on the above-cited subject to ensure that the pre-qualification criteria specified in the tender document should neither be made very stringent nor very lax to restrict/facilitate the entry of bidders. It is clarified that the guidelines issued are illustrative and the organizations may suitably modify these guidelines for specialized jobs/works, if considered necessary. However, it should be ensured that the PQ criteria are exhaustive, yet specific and there is fair competition. It should also be ensured that the PQ criteria is clearly stipulated in unambiguous terms in the bid documents.
    • Examples of Eligibility Criteria not meeting above guidelines
      • MNC Brands for computers
      • Turnover much higher than the required
    • For giving International services, only private airlines with more than 5 years track record were considered – Thus only JET airways qualified
  • Analysis of an IT tender The Content Service Provider (CSP) should have an established office in the State. Needed because close cooperation is required The CSP should be a financially sound registered company/society in India having minimum annual turnover of Rs. 2 Crore during any two of the last three financial years Should be linked to project cost The CSP should have minimum experience of 5 years in providing Content Development Services for websites/ portals /electronic publishing (CSP to provide documentary support). May be unnecessary because many new companies have come up that can provide good service
    • The CSP should have executed minimum two projects with entire scope of work as per clause 3. CSP to furnish detailed information on both the projects as per Annexure-V along with work orders.
    Required as we want experienced parties
    • The CSP should have relevant experience and understanding of the information and services of Government Domain.
    How is this defined
    • CSP should have skilled/experienced Content Writers on its payroll (CSP to provide details as per Annexure III)
    How many Content writers, what skill level
  • Expression of Interest/ Request For Qualification
    • Helpful to know number of parties interested in the project
    • RFQ can help in shortlisting of firms
    • Prospective bidders can know their competition and can give a serious bid
    • Evaluation of Prequalification norms takes 15 days or so, hence EOI or RFQ can be the first stage of the tender
    • As prospective bidders will know the competition, the bid price may be higher
  • Consortium bidding
    • Required when diverse skills are needed
    • Bangalore One Project
      • Implementation of Citizen Centres
      • Software Development
    • Disadvantages
      • Mostly ineligible firms team up with eligible firms.
      • Work is executed by the smaller firm
      • Issues in management of Consortium
        • Over long duration of project, partners may fall out
        • Consortium partners may ask for replacement of one or more partners due to non performance
        • Responsibility needs to be fixed on Prime Partner
  • EMD / PBG
    • Earnest Money Deposit
      • Should be kept at 1-2% of estimated project value
      • Transparent mechanism for refund of EMD to unsuccessful bidders
    • Performance Bank Guarantee
      • PBG format should be included in the RFP
      • Successful bidder should submit PBG within x period of award of contract
  • Bid Evaluation
    • Technical Evaluation is used only for qualifying & final decision is on commercial
    • Quality cum Cost basis with weightage for both Technical and Commercial
    • Technical Bid
      • Needs to be as detailed as possible
      • Evaluation should be objective
  • Technical Bid
    • Should consist of the following
      • Previous experience of the bidder
      • Specific competencies that the Bidder will deploy for successful outcome of the project
        • Additional Manpower
        • Specific technical competency
    • Technical bid should form part of deliverables of the successful bidder
    • Risk factors
      • In many technical bid, the bidders give CV’s of personnel, but when bid is awarded claim that the personnel have left the firm.
  • Evaluation
    • Unambiguous evaluation
    • Intricacies
      • In case of QCBS will normalization of Technical and Commercial bid be followed
  • Supporting Infrastructure
    • Project Management Office
      • The task of the PMO is to manage the project post awarding of contract
    • IIIrd party auditors
      • To check compliance of the vendor to the RFP
  • Pre bid Conference
    • Important for interested parties to meet the department
    • Put forth their suggestion, queries regarding the tender document
    • Ask bidders to submit questions in advance
    • Pre bid queries need to be answered atleast 15 days prior to last date of submission of bid
  • Award of Work
    • Definition to be clarified
      • Letter of Intent
      • Government Order
      • Master Service Agreement with the successful bidder
  • Master Service agreement
    • MSA or contract with successful bidder
      • All NISG RFP’s contain draft contracts
      • Most bidders don’t raise questions on MSA during pre bid but ask for changes once they win the contract.
      • MSA should incorporate
        • Scope of Work from RFP
        • Technical bid of the successful bidder
  • Summary
    • RFP / Tender is like a plan
    • Needs to be prepared with care
    • Will guide project implementation
    • In case of change of Project Implementation Staff , the only document that will guide successors
    • NISG has been a leader in preparing RFP’s for many government projects, hence these RFP’s can be used as template
    • Copy with PRIDE