Resource-Event-Agent Model: Difference between revisions
No edit summary |
|||
Line 72: | Line 72: | ||
"This application attempts to be a new frontend to existing 'Open Value Network' client / server apps." | "This application attempts to be a new frontend to existing 'Open Value Network' client / server apps." | ||
(https://github.com/django-rea/rea-app/wiki) | (https://github.com/django-rea/rea-app/wiki) | ||
=More information= | |||
* https://bitbucket.org/ccomb/rea/ (very early project to combine odoo/rea in the context of [[Coopaname]] | |||
Revision as of 08:34, 4 January 2018
= In the early 1980s Bill McCarthy first defines Resource-Event-Agent (REA) model for accounting systems and publishes many papers on the topic.
Description
Bob Haugen:
"REA is usually presented as an enterprise accounting model. But it can also be used for higher-level economic analyses, which can connect individual enterprises into larger economic formations. No other accounting model is so adaptable. In this context, it is apt to think of REA as a general-purpose economic ontology.
The REA Ontology quotes Ijiri as saying "...the economic activities of an entity are a sequence of exchanges of resources - the process of giving up some resources to obtain others." Those exchanges of resources do not stop at the boundaries of a single company. They extend across many individuals and organizations, across industries, regions or the whole planet. And they can be aggregated at higher levels: for example, all exchanges involving an economic resource or economic agent type.
...
REA economic exchanges can extend across companies, industries, nations, regions and the earth as a whole. REA economic resource and agent types can aggregate data at higher and higher levels.
Integration of REA data at higher levels could give enterprises and individuals views into their surrounding value systems, business clusters, regional economies and ecosystems.
Governmental and regional organizations could operate with current accurate aggregate data for economic analyses and future predictability.
Internet aggregators could follow the dependencies of economic events more deeply, beyond superficial text matches, into the ripple effects of wants and needs and potentials on all the related economic agents.
The signals of economic events, needs and potentials do now and will increasingly propagate through networks of economic relationships that will be forced to look a lot like REA. Those networks will become increasingly intelligent." (http://mikorizal.org/BeyondTheEnterprise.html)
Applications
Supply Chains and Value Systems
Bob Haugen:
"Supply chains, which have been modeled in REA terms several times, are composed of the chains of material suppliers to an individual manufacturing company. For example, the January 2000 REA, a semantic model for Internet supply chain collaboration and Supply Chain Modeling with REA which focuses a lot on transportation.
A value system is a broader concept, which consists of all the interconnected economic agents and resource inputs involved in bringing a product or service type to its end consumers.
Both supply chains and value systems are modeled in REA by chains of alternating conversion and exchange processes, connected by output-input stock flows. These chains will also be used in all of the other larger economic formations below, except the larger formations will use larger aggregate resource, agent and process types." (http://mikorizal.org/BeyondTheEnterprise.html)
Input-Output Graphs
"The Input-output model of economics uses a matrix representation of a nation's (or a region's) economy to predict the effect of changes in one industry on others and by consumers, government, and foreign suppliers on the economy. Wassily Leontief (1906-1999) is credited with the development of this analysis." ([1])
History
Bob Haugen:
- Mid 1990s: Bob Haugen commercially develops 'Quick Response Engine' & becomes interested in supply chain systems.
- 1995-2000: Bob discovers REA, he and Bill further develop REA as a semantic model for internet supply chain collaboration.
- 2000: Verna Allee coins the term "Value Network" to describe and model tangible & intangible economic value within organisations.
- 2002: ISO adopts REA as their economic and accounting ontology.
- 2005: Bob begins to write to the importance of expanding REA to cover ad-hoc networks of external economic entities.
- 2005-2011: Bob works closely with Lynn Foster under the name 'Mikorizal Software' on several open supply chain projects; targeting timber, food networks & fishing industries.
- 2012: Open hardware manufacturer Sensorica gets involved with REA and coins the term "Open Value Network" (OVN). They develop the Network Resource Planning (NRP) software in collaboration with Bob & Lynn. This is the first iteration of the software on which django-rea and its forks are based.
- NRP system architecture presentation (mandatory reading!)
- 2016: Bill expands upon the concept of an Open Value Network, building on his prior REA model.
- OVN / REA presentation slides
- Q1 2016: Sensorica's NRP software is forked by FreedomCoop and becomes OCP (Open Collaboration Platform). Many updates are made and integrations with economic networks (FairCoin) begin.
- Q3 2016: Another fork of NRP is made by GoPacifica and further development continues on that project.
- 2016-2017 Lynn and Bob join with others to continue work on developing the REA ontology, incorporating learnings from prior projects & concepts, including NRP & OVN, as well as others. The project name is genericised to "Value Flows" and becomes focused on working towards common standards.
- Dec 2016: Valueflows team members discuss and outline requirements for a modular & community-centered design process around OVN-compatible apps.
- Q1 2017: Members from GoPacifica, FreedomCoop, Sensorica & Mikorizal begin to collaborate on unifying the multiple forks of NRP to a single generic codebase so that development effort can be shared."
(https://github.com/django-rea/rea-app/wiki)
Example
REA Client Application Interface
"This application attempts to be a new frontend to existing 'Open Value Network' client / server apps." (https://github.com/django-rea/rea-app/wiki)
More information
- https://bitbucket.org/ccomb/rea/ (very early project to combine odoo/rea in the context of Coopaname