Pain points in e-Governance - 2 : Vendor Locking
Vendor Locking
Government has involved many big/small IT companies for development and implementation of many technical project due to lack of its internal capacity. Most of the times companies quote unjustifiable low rate to get these contracts. Many projects are singed for a duration of 3-5 years, with provision for extension. Once the work start many fails to deliver in time. One of the main reason for this is failure is frequent change request in application, many times resulting change in scope of work. If the raised Change Request involves financial, then a committee will look in to the costing quoted by the company and then negotiation, renegotiation, walkout, threats of law suits/arbitration and finally every minor word in contract wake up, resulting in delay leading to service hampering resulting in public inconvenience.
Two questions arise out of it. One why government keep changing its requirement and other is why company must keep charging for additional requirement even after reading risk factors, assumptions etc., of the tender documents.
The answer for the first question lies in understanding the Government’s stake holders in the ecosystem. Unlike government, a company will have a very well defined stakeholder and they are in limited numbers. But in government everyone who resides/born in that area are stakeholders. Imagine the diversity of stakeholders, Rich/poor, Law abiding citizens/criminals, minority/majority etc., its complexity multi fold with addition of caste, language, region etc. With these diversity, it’s quite natural for any sensitive government to keep changing its requirements, it’s almost impossible to have fixed scope for any government application.
On the other hand, a company which has quoted low while bidding, faces crisis at the time of development, since it must deploy additional resource for this additional requirement. Hence to minimize the loss they quote high price at the time of change request. Usually most of the tender have predetermined man moths rate quotes. But the big question here will be duration for development/implementation of additional requirement.
In additional to these issues like timelines, SLA’s, delayed payments etc., create a situation where both the parties burn the bridges, resulting in vendor lock. In these situation, smaller companies just vanish form the scene, leaving behind absolute chaos and while big companies can afford to forgoes these cost, but they will not work beyond thresholds. Nothing moves on either side.
Very true sir. I also felt the same when I was working for ITBT department.
ReplyDeleteIf you wish, you can share your experience here.
DeleteVery aptly Said, the issue is after floting RFP, if you keep on changing the requirements, we need to rework on the entire architecture of the application. Better to have in house. But question remains who will monitor/ guide/ supervise them.
ReplyDeleteGovernment requirement keep changing, since it does not have fixed stakeholders. I strongly agree with you to have in house team, with regular monitor/supervision from external experts.
Delete101%True.
ReplyDeleteVery well touched the problem in e- governance..
ReplyDeletethank you
DeleteGood article!! From the solution point of view, yes, all the above specified three options are good & it’s viable.
ReplyDeleteAnd also, I believe, if we think from long term prospective, Ideally Government should have it’s own IT cell filled with potential Project Managers, developers, testers and others required resources which should capable of handling all government IT projects / requirements & delivery should happen with in defined SLA . It takes lot of time to build such a team but surely this will breakdown the dependence on the service companies which delays all the government projects for one or the other reasons.
Yes, i agree, Government should have its own team.
DeleteVery well thought and brilliantly written blog. Sir, I feel you have put all your experience with CeG in this blog.
ReplyDeleteOff course. Thank you for your support.
DeleteBro I feel by making a little tweak in notification n MOU there can be plug for high price/charges for additional changes. There should always be space n scope for additional changes/requirement/addendums in the product requested within package or as you said building a own desired skillful team is long sustaining viable option, though build it is a hectic process at initial stage.
ReplyDeleteYes, it is solvable issue with amendments. The problem here is approval cycle and criticality of enhancement, both with take its own time. Yes, having internal team is time consuming and hectic at initial phase, but i feel, that the only option now.
Delete