e-Gov solutions Re-usability

I have worked for Railways for over 7 years and now I am working in e-Governance domain after pursuing my MBA. I also had experienced a small e-Gov experience while working on e-District UP project; on behalf of 3i-Infotech as a Summer Trainee. As moving ahead my career in e-Gov domain, I have came across a few confusions in my mind, which I would like anyone having vast experience to clear.

Since e-Gov projects(India) like e-District, e-Panchayati Raj, etc. are proposed for all the states. And they widely cover all citizen centric services like Ration Cards, Pension, various Certificates, etc. Now, many of the states have already started working on these projects. (for example, UP e-District is all set to start delivering its services and state is now ready to cover all districts). All states widely cover similar/same services in first phase. All states hire agencies for similar role-out. My question now is that if similar services are to be covered and an e-enabled model has to be implemented after some re-engineering of existing processes; then why do we invest heavily in re-defining the processes for each state (correct me, if we re-use the above said) ? Why isn't a model, say, which is developed in UP is replicated to other states; harnessing the common backbone and program code OR making the process a GENERIC solution ? Making the processes widely acceptable or modeling on the lines of "Best Practices". I actually wanted to explore, if there is a way in which the IT majors, who partner for e-Gov service/product delivery with the govt can join hands for developing a common model for e-gov for the whole country. This way, we not only can develop a widely accepted model, we will also save on costs incurred and replication always saves time. This way, we can easily make our gov system, a truly e-Gov system. Please do correct me, if I am wrong at any part. I would be great full to all who contribute towards my understanding.