
Resource added for the Supply Chain Management program 101821.
There's a great book on this topic from the first dot com age. Necessary but not Sufficient (https://www.amazon.com/Necessary-But-Sufficient-Eliyahu-Gold...). The idea being you can adopt a tool but if you don't understand the mental models that go along with that tool then you won't fully reap the benefits.
As a company, this is still our responsibility. The best products educate as well as enable.
Ludwig von Bertalanffy
https://www.amazon.com/s/ref=dp_byline_sr_ebooks_1?text=Ludw...
John Seddon
Theory of Constraints
https://www.amazon.com/dp/B002LHRM2O The Goal / Eli Goldratt
https://www.amazon.com/dp/B00KYW1L66 Necessary but Not Sufficient / Eli Goldratt
https://www.amazon.com/dp/0884271137 It's Not Luck / Eli Goldratt
https://www.amazon.com/dp/B00408ALES Isn't it Obvious? / Eli Goldratt
https://www.amazon.com/dp/B002LHRM2E Critical Chain / Eli Goldratt
https://www.amazon.com/dp/B004THZ9VK Be Fast or Be Gone / Andreas Scherer
https://www.amazon.com/dp/1499660901 Hanging Fire / Jeff Cox
https://www.amazon.com/dp/1439158932 Velocity / Dee Jacob
https://www.amazon.com/dp/B00XKX1FEO Epiphanized / Bob Sproull & Bruce Nelson
https://www.amazon.com/dp/B0185JFYEO Focus and Leverage / Bob Sproull & Bruce Nelson
A full list of books on ToC here http://www.tocico.org/?page=toc_books
Russell L. Ackoff
https://www.amazon.com/s/ref=dp_byline_sr_book_1?search-alia...
Gerald M. Weinberg
https://www.amazon.com/Gerald-M.-Weinberg/e/B00459FFAC/
Philip B. Crosby
https://www.amazon.com/Philip-B.-Crosby/e/B001HD360A
Peter M. Senge
https://www.amazon.com/Peter-M.-Senge/e/B000AQ8R86/
And many more, most of which are mentioned by the above in their work.
I was also looking at ERP after working in the field for a number of years. I was planning on coming from a very different angle. Hosting a very configurable system that required little or no manual intervention. Aiming at small business for a $20 per month per user fee.
Then I discovered I hate running a business, not just dis-like but hate so much I never want to do it again :-(
I think your idea could take off but the software has to be malleable, this is in contrast to nearly every piece of software written to this day which is brittle. I was looking at this as just a way to predict how software will be written in the future.
First off read a couple of books to understand better where I'm coming from :-
Necessary But Not Sufficient by Eliyahu M. Goldratt
Naked Objects by Richard Pawson
From a business perspective I want a group of classes that mirror real world items e.g. Order, Invoice, Address, Amount, Price, Date etc. Then I want another group of classes that handle business actions e.g. Enter Order, Print invoice. Lastly a group of classes that handle business process e.g. Process Order, Calculate invoice etc.The above would give you a group of objects that you can model the business with and forget about technical details.
Then the underlying system could be built e.g. fully temporal, fully redundant etc. etc.
The idea being that you could focus on business processes without thinking about implementation details. In true naked object style the UI would be automatically generated from the business action/process classes.
To make what you are thinking about work _ALL_ design has to be KISS and DRY. Also, the more you can generate the better you'd be.
I was thinking of using Lisp or SmallTalk to gain an advantage, must use a VM to be able to separate business from technical. I want to my software running 24/7 with zero downtime including during upgrades, automatic rudundancy, load balancing etc.
If you are thinking of something along these lines then drop me a line and I'd love to help.
If you just want to re-implement the current paradigm don't bother contacting me. The current paradigm is so broken it's not even funny.