Billing systems are a nightmare for engineers
(1 of 2)<p>In the 00&#x27;s, I was part of an effort to get the State of Oregon to consider open source software.  A 40 million billing system debacle was part of what drove this effort.  The details are not important, save to say the ASA paid big to stall the legislation and that worked.  It was stalled, and word got out that future bills would be toxic.  So, that&#x27;s over, but a great idea remains!<p>I am putting it here, because someone, somewhere should do it.  Will save us all a lot of money and do a great public good.  And it&#x27;s likely to pay a fellowship of some kind very well over the next couple decades.  I&#x27;m on a different project and need to finish it, and I&#x27;m likely to be paid well on that, so...<p>Instead of paying the likes of Oracle, or some consulting firm to write and support the billing system, the State should do it.  So far, I&#x27;ve seen several bad contracts in my State where the State has a right to use the software, does not own the code, must pay for support, and on it goes.  This is quite expensive, and frankly, it didn&#x27;t work well.<p>Instead do this:<p>The State sets up an organization.  This org is public, and those who work there are public servants, or some similar arrangement.  The key thing is the billing system gets written on open code, uses open data, and the resulting software is owned by the public, through the State essentially.  This code gets published on Github under an appropriate open license.<p>Fund this org, paying respectable developer salaries, and get the system written, tested, deployed, whatever is required.  This funding comes from public tax dollars, and I would suggest the lottery as a primary source.<p>Once the initial system is complete, and let&#x27;s say it&#x27;s for water.  Once it&#x27;s complete, the system can be published and the whole thing becomes an export for the State that does it.<p>Any municipality anywhere can do one of a few basic things:<p>They can build and deploy the system and handle billing themselves.<p>They can hire the Org to help them do this, contact for support, whatever.<p>They can hire private entities to deploy the system.<p>Changes can come from anywhere, but the organization is best suited to implement them.  This can be on a contract basis, funded reasonably in any number of ways.<p>The organization continues on to develop other public works tools, each funded by public dollars, each displacing some expensive thing or other, and each saving the people quite a bit over the course of say a decade.<p>Wash, rinse, repeat.<p>The end product is a nice pile of public works software needed by tons of municipalities most all of whom are paying hard for it now and they pay hard for basically everything, and continue to do that.  The public could make these investments once and benefit for a very long time.<p>Perhaps more than one State wants to be a part of something like this, or whatever State gets going on it first, might want a few organizations, depending on what is to be done and the scope &#x2F; scale required.  Either way, the Organizations provide jobs and consulting &#x2F; support and basically own the public works they develop and are funded to maintain those software works.<p>An advantage over contracts and proprietary license is cost, particularly when the likes of Oracle are involved (and no judgement here and no calling out as I&#x27;m only saying Oracle as a well known example among many out there and I just feel the public works can be done without Oracle and the cost associated with similar entities).  Having the data be open is another advantage in that it can be used in all sorts of ways, and the public records can be made available to the public in simple, effective ways.<p>Mix in smart API&#x27;s and the whole thing becomes very high value and an attractive base target for all sorts of public software development having to do with the basic machinery of society.<p>None of this is particularly sexy, but it does pack a big punch in terms of modeling how a more modern, digital society could employ open code, open data to get the work we need done, done in a cost effective, efficient way.<p>And that&#x27;s it basically.<p>Over time, this first, or core organization will accumulate considerable domain knowledge.  And it would become the basis for a lot of other work.  Ideally, others started up in various places would all garner the knowledge needed by domain:<p>Utilities, water, power, internet (where it&#x27;s actually municipal, and we know that&#x27;s not popular with the big telecoms...), garbage, etc.<p>City functions, parking, various permits, anything that has a process that could be automated and or just performed on open code in simple, direct ways that are lean, consistent.<p>Vehicles:  Registration, and all that tends to be tied into these systems.  In my state, we&#x27;ve got vehicle registration, drivers licenses &#x2F; ID Cards that link to facial biometrics (I don&#x27;t like this, but that is another discussion), and it&#x27;s also voter information central with a signature, party affiliation, address, and everything needed to manage the voting rolls, and execute Vote By Mail nicely, and in a trustworthy fashion.  Oregon has done well on that front.  Citizenship records are in this pool of software too.<p>Health Care:  Right now, again in my State the Medicaid system insures people who are diabled, are poor, perhaps wards of the State.  This is currently on Oracle, and has been such a mess it&#x27;s ended up in court.  I don&#x27;t even know the state of it all right now, but it&#x27;s a lot of money and a lot of grief.