35 years of software development for major companies like Mobil, CBS and Intuit, worked on 3 commercial ERP systems and 2 supply chain management systems, e-commerce standards for ISO, UN/CEFACT, OASIS and W3C, open source software for food, timber, housing and open hardware networks.
- Main developer of Valueflows based on REA ontology, with Lynn
- Main developer, with Lynn of the first NRP-CAS in collaboration with Sensorica
From a post on hREA Discord
- I worked as a programmer on 3 big ERP systems, two for user companies, and once as a staff developer for the ERP software company. On that job, I was assigned to a skunkworks team to redesign ERP systems because they were too complicated. They had grown by awkwardly hacking together several older systems and had at least four (different) copies of each concept they were trying to implement.
- That project produced an app that the company could sell and they had new managers who were happy with what we had done and then killed the rest of the project. So I quit and spent a solid year looking for a new model, and found REA, which was perfect. It has a few main concepts - Resources, Events, and Agents and how they interact in Processes and Exchanges. And it can do everything that ERP software can do, plus also supply chain management which is an add-on for ERP software.
- I think REA is a minimal model. If you want to do what hREA wants to do, it is all that you need, but you need all of it.
- I can always be wrong, but I have developed several systems using REA for several contexts and have not found anything it can't do in the arena of production, distribution and exchange for economic networks or even community economic systems. REA also works fine for normal single companies.