Track and Trace Future, Present, and Past Product and Money Flows with a Resource-Event-Agent Model

Laurier, Wim; Poels, Geert

doi:10.1080/10580530.2012.662102

Cited by 11 publications

(11 citation statements)

References 47 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Another limitation is that only a descriptive evaluation of the presented conceptual modeling grammar was presented here. Another type of descriptive evaluation has been presented in (Laurier and Poels, 2012), where a conceptual modeling script for traceability is presented as a proof of concept for this conceptual modeling grammar.…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

An Enterprise-ontology based Conceptual-modeling Grammar for Representing Value Chain and Supply Chain Scripts

Laurier

2013

Proceedings of the 15th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

In business modeling the focus is shifting from the enterprise to the supply chain as the prime context. Contemporary business modeling grammars should allow each enterprise taking part in a supply chain to develop its own information system and at the same time support the creation of system interoperability and information sharing amongst business partners in the supply chain. This paper presents a conceptual modeling grammar for representing business scripts in a way that is observer-independent. That is, rather than presenting value chain information from the perspective of any partner in the supply chain (e.g., enterprise, supplier, customer, customer's customer, supplier's supplier) or from a completely neutral third party. This observer-independent conceptual-modeling grammar, which is given strength by grounding it in the mature Resource-Event-Agent model, is shown to represent information about business phenomena of diverse supply chain partners such that it can be integrated across enterprise boundaries.

show abstract

Section: Discussionmentioning

confidence: 99%

“…In the REA terminology, such a model of a production process is called a conversion model, as it represents the conversion of one or more inputs into one or more outputs. For a more detailed analysis of conversion models, we refer to (Laurier and Poels, 2012). 5 shows the main components of a conversion script.…”

Section: Archetypal Conceptual Modeling Scriptsmentioning

confidence: 99%

An Enterprise-ontology based Conceptual-modeling Grammar for Representing Value Chain and Supply Chain Scripts

Laurier

2013

Proceedings of the 15th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

“…The relevance would be tested by generating and testing a prototype in a commercial programming language (e.g., C#, Java, Python, Ethereum). The test scenarios of this initial prototype will also include tracking and tracing (Laurier and Poels, 2012). After testing this initial prototype, commitments, types and groups will be added to the prototype.…”

Section: Future Researchmentioning

confidence: 99%

“…Collaboration requires sharing information with trading-partners, whereas information sharing might hamper maximisation of earnings in a competitive environment (Letaifa, 2014). Meanwhile, third parties (such as governments, trusted third parties) request access to trade data so that they can process this information to reduce health and safety risks through food-traceability, e-customs, or in novel forms of business interactions such as blockchains (Laurier and Poels, 2012;Steiner and Baker, 2016;Tan et al, 2010). Traditional of the REA 2 formalisation, in which data available in ISO/IEC FDIS 15944-4 or a compatible viewindependent data format supports interoperability between the information systems of trading-partner sharing a collaboration space.…”

Section: Introductionmentioning

confidence: 99%

REA2: A unified formalisation of the Resource-Event-Agent ontology

Laurier

Kiehn²,

Polovina

2018

Self Cite

View full text Add to dashboard Cite

Abstract. Through a proof of concept in SWI-Prolog, this paper demonstrates a business transaction model by which the trading partners can derive their own, personal perspective from shared data. The demonstration is an innovative formalisation of the Resource-Event-Agent (REA) ontology as it allows for switching viewpoints in real-time between one trading-partner's perspective and that of a trading-partner with an opposing view (i.e., customer or supplier), or a trading-partner independent perspective (e.g. trusted third-party). The business transaction model is achieved by uniting REA with the Open-EDI Business Transaction Ontology (OeBTO). The resulting unified formalisation of the REA ontology (REA 2 ) also highlights implications for the future development of a) enterprise information systems (EIS) in the cloud, b) social-media-based EIS, c) blockchain EIS, and d) EIS interoperability across business paradigms. The EIS interoperability such as between traditional EIS (which typically uses a trading-partner perspective), and EIS for the collaborative economy (which typically uses a trading-partner independent perspective) is particularly highlighted as it becomes much more transparent than previously.

show abstract

“…They say the major strength of their proposed method is that it combines the multiple layers of REA and OeBTO to identify an entire enterprise-wide service portfolio on the business level that is well-enough defined to be transformed further to a system-centric e-service model. Laurier and Poels (2012a) used the ISO standard 15944-4 (ISO/IEC, 2007) to illustrate how one can track and trace product and monetary flows. Specifically, they show how one can track both intra-and interorganizational enterprise phenomena in a prototype application of a pizza bakery's supply chain from the farm to the customer to demonstrate the robustness of the REA ontology.…”

mentioning

confidence: 99%

Resources-Events-Agents Design Theory: A Revolutionary Approach to Accounting and Enterprise System Design

Dunn

Gerard²,

Grabski

2016

CAIS

View full text Add to dashboard Cite

Enterprise systems typically include constructs such as ledgers and journals with debit and credit entries as central pillars of the systems' architecture due in part to accountants and auditors who demand those constructs. At best, structuring systems with such constructs as base objects results in the storing the same data at multiple levels of aggregation, which creates inefficiencies in the database. At worst, basing systems on such constructs destroys details that are unnecessary for accounting but that may facilitate decision making by other enterprise functional areas. McCarthy (1982) proposed the resources-events-agents (REA) framework as an alternative structure for a shared data environment more than thirty years ago, and scholars have further developed it such that it is now a robust design theory. Despite this legacy, the broad IS community has not widely researched REA. In this paper, we discuss REA's genesis and primary constructs, provide a history of REA research, discuss REA's impact on practice, and speculate as to what the future may hold for REA-based enterprise systems. We invite IS researchers to consider integrating REA constructs with other theories and various emerging technologies to help advance the future of information systems and business research.

show abstract

Track and Trace Future, Present, and Past Product and Money Flows with a Resource-Event-Agent Model

Cited by 11 publications

References 47 publications

An Enterprise-ontology based Conceptual-modeling Grammar for Representing Value Chain and Supply Chain Scripts

An Enterprise-ontology based Conceptual-modeling Grammar for Representing Value Chain and Supply Chain Scripts

REA2: A unified formalisation of the Resource-Event-Agent ontology

Resources-Events-Agents Design Theory: A Revolutionary Approach to Accounting and Enterprise System Design

Contact Info

Product

Resources

About