See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/332495000

Blockchain Reference Model and Use Case for Supply Chains within
Enterprise Architecture

Article · March 2019

CITATIONS READS

0 780

3 authors:

Tumennast Erdenebold Jae Jeung Rho

Korea Advanced Institute of Science and Technology Korea Advanced Institute of Science and Technology
5 PUBLICATIONS   4 CITATIONS    4 PUBLICATIONS   28 CITATIONS   

SEE PROFILE SEE PROFILE

Yoon Min Hwang

Korea Advanced Institute of Science and Technology
3 PUBLICATIONS   25 CITATIONS   

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

KAIST GCORE Project View project

All content following this page was uploaded by Tumennast Erdenebold on 18 April 2019.

The user has requested enhancement of the downloaded file.

Journal of Information Technology and Architecture
Vol. 16. No. 1, March 2019, Pages 1-10

Blockchain Reference Model and Use Case for Supply Chains

within Enterprise Architecture
Tumennast Erdenebold1, Jae Jeung Rho2, and Yoon Min Hwang3,*
1
Global Center for Open Research with Enterprise (GCORE), KAIST
2
School of Business and Technology Management, KAIST
3
School of Business, Chungbuk National University

(Received March 6, 2019; Revised March 17, 2019; Accepted March 18, 2019)

Abstract: Blockchain Technology is disrupting in many industries, introducing a decentralized business

model over peer-to-peer network. Moreover, many researchers believe that blockchain technology will
modernize the global supply chain network, making it more efficient and economical. In order to achieve
complex IT solutions like Blockchain with change management for business and IT models, enterprise
architecture (EA) is a suitable approach holistically. However, there is a research gap from the blockchain
study perspective for the enterprise architecture approach, more deeply inefficient supply chain issues
of interoperability, data integration, use of common data, and track and trace issues along with different
stakeholders existing in the enterprise domain. Thus, the main goal of this paper is to fill the unexplored
research gap academically, more specifically, to solve supply chain issues with Blockchain Enterprise
Architecture. As a result of this study, we developed a conceptual new Blockchain Enterprise Architecture
(BEA) reference model for the supply chain. We expect our constructed model will be a guide for new
business developers, architect designers, and scholars in the supply chain area, and specifically will assist
them to trial reference models for new business development in the inception stage. Practically, we
demonstrated the BEA reference model for the Pharmaceutical Industry supply chain as a use case.
Keywords: Blockchain, Enterprise architecture, Reference model, Supply chain, Use case

1. Introduction change management with the latest and innovative

The history of supply chain management started
from early of 1900s, and was created to reengineer
whole supply chains from the manufacturer worker’s
process to end consumers with latest technologies
and innovations. There are many challenges in supply
chain areas such as multiple stakeholders involved
in data transfer and information exchange, high
administrative costs, lack of technological interoper-
ability, and distributed management efficiency [15].
To overcome the above complex issues, research
and development required to reflect both manage-
ment and technology related issues holistically
within enterprise organizations, therefore Enterprise
Architecture helps to achieve whole-business process
technologies. Furthermore, enterprise architecture
in supply chains need more efficient and real-time
data, because of there are multi-parties with differ-
ent organizational sizes, systems, standards, and
issues such as interoperability issues, data integra-
tion issues, use of common data, track and trace
issues, and expensive systems for the integration
issue, exist [6].
Another hand, Blockchain technology is one of the
key technologies under the Fourth Industrial Revo-
lution, and is considered an emerging disruptive
technology to many industries including supply
chain. Many developers [1], scholars, and leading
tech companies are highly focused on concept devel-
opment, pilot and trial adoption and implementation

*Corresponding Author: ymhwang@cbnu.ac.kr

1
Tumennast Erdenebold, Jae Jeung Rho, and Yoon Min Hwang
of Blockchain technology into their back-end busi-
ness operations for increasing benefit [8]. Moreover,
Blockchain is latest technology, which promises to
change businesses and technical models of current
existing centralized systems to decentralized, and is
one of the major industries to benefit the supply
chain area to solve its complexity. But there are lack
of studies exist to investigate holistically, including
both change management and technology using
Enterprise Architecture, more specifically in the sup-
ply chain domain [8].
For that reason, the goal of this study is to fill the
research gap in the supply chain domain using an
enterprise architecture approach. The objectives are
firstly to explore the Blockchain potential for the
enterprise perspective in the supply chain, and
develop a Blockchain Enterprise Architecture refer-
ence model for the supply chain domain with Block-
chain technology. Then secondly, to apply an
example use case in the supply chain of the phar-
maceutical industry for a newly developed reference
model, practically.
The research scope is focused on the following
areas the Enterprise Architecture for supply chain
industry using the Blockhcain technology as a ref-
erence model. Besides, the example case used for the
pharmaceutical industry supply chain using block-
chain technology.
Then, for the research method, we selected Enter-
prise Architecture as a baseline architecture domain
for reference model design and generation, and we
used with design approach for EA development
based on the Consolidated Reference Model (CRM) of
the Federal Enterprise Architecture Framework. In
addition, we applied a use case testing method with
example case to demonstrate our developed reference
model, practically.
Finally, the importance of this study is to contrib-
ute conceptual Blockchain Enterprise Architecture
reference model development for supply chains ind-
ustry, theoretically. Besides, we applied developing a
Blockchain Enterprise Architecture (BEA) reference
model, and demonstrating it to the pharmaceutical
supply chain as a use case.
2 Journal of Information Technology and Architecture
2. Literature Review
2.1 Enterprise Architecture and Reference
Model
Enterprise architecture (EA) is “a well-defined
practice for conducting enterprise analysis, design,
planning, and implementation, using a comprehen-
sive approach at all times, for the successful devel-
opment and execution of strategy. Enterprise
architecture applies architectural principles and
practices to guide organizations through the busi-
ness, information, process, and technology changes
necessary to execute their strategies. These practices
utilize the various aspects of an enterprise to iden-
tify, motivate, and achieve these changes” [9].
In addition, An Enterprise Architecture frame-
work (EA framework) defines how to create and use
an enterprise architecture. An architecture frame-
work provides principles and practices for creating
and using the architectural description of a system.
It structures architects' thinking by dividing the
architecture description into domains, layers, or
views, and offers models - typically matrices and dia-
grams - for documenting each view. This allows for
making systemic design decisions on all the compo-
nents of the system and making long-term decisions
around new design requirements, sustainability, and
support [10].
Furthermore, key benefits of enterprise architec-
ture include cost reduction, advanced IT alignment,
the reduction of system cycle times, improved of risk
management, the enhancement of interoperability,
and improved system integration within enterprise
holistically [11].
For the Enterprise Architecture Reference models
in systems, enterprise, and software engineering are
an abstract framework or domain-specific ontology
consists of an interlinked set of clearly defined con-
cepts produced by an expert or body of experts in
order to encourage clear communication. A reference
model can represent the component parts of any con-
sistent idea, from business functions to system com-
ponents, as long as it represents a complete set [7].
While, reference architectures in the field of software
 Blockchain Reference Model and Use Case for Supply Chains within Enterprise Architecture
architecture or enterprise architecture provides a
template solution for a particular domain. They also
provide a common vocabulary with which to discuss
implementations, often with the aim of stressing
commonality [8].
In addition, supply chain is a cooperative system
and it exists on the dynamics of its group members.
Moreover, supply chains manage coordinated infor-
mation, material flows, operations, and logistics
through a set of policies, standards, and performance
metrics throughout its process between distributed
members. This cooperative system requires distrib-
uted complex problem solving among members. In
order to solve this issue among members, it is made
easier to use an enterprise architecture framework
system into the supply chain [15].
2.2 Blockchain Technology, Applications and
Benefits
The Blockchain is an electronic ledger (database)
which is based on distributed ledger technology
(DLT), and can hold any information on transactions,
ownership, records etc. [2]. Blockchain contains peer-
to-peer networks and cryptographic techniques and
is based on a consensus algorithm to solve distrib-
uted ledger synchronization issues. Blockchain tech-
nology has several key characteristics:
• Peer-to-peer network based
• Decentralized
• Distributed ledger recorded chronically
• Immutable and tamper-proof records
• Elimination of intermediaries
Moreover, there are various industries where
Blockchain technology will potentially be applicable
as defined by the IBM corporation (2017), including
finance (trade, finance, cross currency payments,
mortgages), the public sector (asset registration, cit-
izen identity, medical records, medicine supply
chains), retail (supply chains, loyalty programs,
information sharing), insurance (claims processing,
risk provenance, asset usage histories, claims files)
and manufacturing (supply chains, products, parts,
maintenance tracking). Overall, there are three
types of categories of Blockchain networks: public,
private, and federated/consortium (permissioned)
[18].
• A public blockchain was first introduced by Bit-
coin where the network is standard and open to
all and there is no centralized management.
• A private Blockchain is a closed system, which is
owned by individual or enterprise.
• A federated/consortium Blockchain is a permis-
sioned and group-owned solution for groups of
organizations or individuals.
In addition, there are several startup companies,
scholars, and initiatives defined Blockchain technol-
ogy’s promising benefits in supply chain systems as
time savings, security improvements, more reliable
and trusted data management, increased auditabil-
ity, enhanced trust and transparency, enhance oper-
ational efficiency, efficient tracking and traceability,
and cost savings for data management [6]. Further-
more, according to a Deloitte report, Blockchain tech-
nology is useful when shared data exist, multiple
parties are involved, low trust exists, as well as for
auditability, disinter-mediation, and transaction
interactions needs.
3. Methodology
First all, the reason why we select Enterprise
Architecture (EA) as a baseline for this research and
development, even though there are many Supply
chain management (SCM) architectures exists is
that Enterprise Architecture in supply chain area
used for the complicated set of demands [20]. More
specifically, traditional SCM information systems
had challenges to solve efficient interoperability, but
EA possibility to extend embedded multiple domains
for critical concern in the implementation and out-
lining the interoperability [21]. Therefore, this study
selected EA rather than SCM systems concerned for
our research objectives and scopes for interoperabil-
ity and decentralization demands using Blockchain
technology.
There are variety of Enterprise Architecture
frameworks such as the Zachman Framework (ZF),
The Open Group Architecture Framework (TOGAF),
the Federal Enterprise Architecture Framework
Journal of Information Technology and Architecture 3
Tumennast Erdenebold, Jae Jeung Rho, and Yoon Min Hwang
(FEAF), [11], which are considered for use in
research and related issues where the scope is gen-
eralized or narrowed. Applying firms should select
the best match for their needs [6, 11]. Thus, in our
study, we selected the Federal Enterprise Architec-
ture Framework (FEAF) as our architecture design
foundation, after considering its high-level abstrac-
tions, ontology-based view domains, and a variety of
reference components.
The FEAF was initially introduced by the United
States government in 1999, and provides enduring
standards and guidelines for the development and
documentation of models and architecture descrip-
tions among multi-organizational functional seg-
ments. It consists of eight components and four
architecture models: business, data, applications,
and technology. One of the key component reference
guides is used for supporting the effective flow of
information, shared business processes, and technol-
ogy across the architecture as shown in Figure 1.
Moreover, the FEAF equipped version 2 reference
model is called the Consolidated Reference Model
(CRM) and it consists of a set of interrelated layers
of reference models, which were selected to facilitate
designing collective elements among inter-organiza-
tions.
It has five major reference models: Performance
Reference Model (PRM), Business Reference Model
(BRM), Application Reference Model (ARM), and
Infrastructure Reference Model (IRM) [16]. Firstly,
the Performance Reference Model (PRM) is used for
Figure 1. FEAF main components [16]
4 Journal of Information Technology and Architecture
performance measurement, and it enables better
management of enterprise business at strategic and
planning level. The main goal of this reference
framework leads to [19]:
• Help produce enhanced performance information
to improve strategic and daily decision-making
• Improve the alignment and better articulate the
contribution of inputs to outputs, thereby creat-
ing a clear “line of sight” to desired results
• Identify performance improvement opportunities
that span traditional organizational structures
and boundaries
Secondly, the Business Reference Model (BRM) is
providing facilitation of a functional view, including
its daily operations and services for customers. It’s
structured into a tired field of business main function
[19]. Then, the Data Reference Model (DRM) enables
understanding the meaning of data in the organi-
zation, how to support data performance, how to
access and manage on it for performance result [19].
Next, the Application Reference Model (ARM) is
categorizing the enterprise system application related
technologies and standards that facilitate the deliv-
ery of service capabilities, allowing organizations to
use common application solution [19]. Finally, the
Infrastructure Reference Model (IRM) supports the
network/cloud infra related norms and technologies
to enable delivery of IT services components and
capabilities [19].
In conclusion, our method for the development new
reference model is based on the Consolidated Ref-
erence Model (CRM) of the FEAF, and we constructed
a Blockchain Enterprise Architecture (BEA) refer-
ence model. This model, including blockchain tech-
nology-related components consisted from the supply
chain perspective as follows by each domain with
components.
4. Conceptual Architecture: BEA
In order to develop new conceptual architecture for
Blockchain EA reference model, we adopted all the
domains from consolidated reference model (CRM).
Moreover, we need to define and select components
for each domain: Performance, Business, Data,
 Blockchain Reference Model and Use Case for Supply Chains within Enterprise Architecture
Application, Infrastructure reference models based
on the CRM guideline [22].
4.1 Development of Performance Reference
Model
For the Performance Reference Model (PRM), we
followed guideline components as defined in CRM, it
links organizational strategy, internal business com-
ponents, cross-agency and inter-agency goals and
objectives, and performance indicators [22]. The PRM
has three main areas including goal, measurement-
area, and measurement category [22]. Firstly, the
goal enables identification of common performance
across activities, and future enables cross-platform
[22], thus in our study we adopt and defined as the
purpose of the system including the system strategy
and objectives. Secondly, the measurement area
applied by a goal, in which performance area is used
for activity support [22], and we applied as this com-
ponent under the name of area or field to use plat-
form. More specifically, we defined the type of
industry to use system under the performance goal.
Thirdly, the measurement category refines measure-
ment area, and any measurement category may
apply to the goal [22], thus we adopt this component
and defined as detailed two components those are
scope, and blockchain use. Then the scope component
described system coverage area, while blockchain
use component defined the detailed sub-sector of use
dedicated for blockchain enabled application.
4.2 Development of Business Reference Model
For the Business Reference Model (BRM), we fol-
lowed guideline components as defined in CRM, it is
a classification of taxonomy used to describe the
types of business services and functions performed
by applying organization [22]. The BRM has three-
layer hierarchy representing the mission sector,
business service and function. First, the mission sec-
tor identifies the business area of the organization in
the common approach to EA [22], therefore we
adopted and modified for the branch business needs
and demand for mission sector. Mostly focused on the
Blockchain needs for the mission sector. Second,
Business services describe what the organization
does at s secondary component level of service [22],
and we implemented this component named the sup-
ply chain service item, specific services involved in
the stakeholders of the supply chain. Finally, the
business function identifies the organization function
agreed level [22], therefore we used with modifica-
tion as scalability, because of this function defines
one of the key functions measured in transactions
per second (TPS) for the blockchain business.
4.3 Development of Data Reference Model
For the Data Reference Model (DRM), we followed
tutoring components as defined in CRM, and its
main purpose is business focused data standardiza-
tion, and information and data exchange among
cross organizations [22]. The DRM has three layers
indicating domain, subject and topic for data related
elements [22]. In our research and development, we
used four main data management items from block-
chain related data. The first item is data or asset on
blockchain, and it defined what type of data or asset
on the blockchain as data storage. It can be original
data or asset or transaction records, etc. Second, we
implemented a proof of existence (PoE) item, which
is strong data validation finger print function [23].
Thirdly, we inserted data decentralized storage sys-
tems from third party (3P) such as Storj, Sia, File-
coin, Swarm, IPFS, etc. [23]. Final item is data
related standards [22], those able to use any type of
data related standards for system requirements.
4.4 Development of Application Reference
Model
For the Application Reference Model (ARM), we
followed as defined in CRM, and it is to provide the
basis for application categorization, and their soft-
ware components, including websites, databases,
email, and other supporting software [22]. The ARM
has different types of system software, application
component and interface [22]. In our research and
development, we used five items from blockchain
Journal of Information Technology and Architecture 5
Tumennast Erdenebold, Jae Jeung Rho, and Yoon Min Hwang

related application and supporting software. The the authorities those have access permissions. Also,
first item is Smart contract that is basically com- it can be mixed such as some parts private, some
puter software that can automatically execute the parts public we called hybrid systems. The second,
terms of contract [23]. Another hand, it’s called chain Blockchain Platform design depends on the block-
code for other systems. Second, we applied item chain main network itself or based on the other exist-
adopted from blockchain called Decentralized Appli- ing blockchain platform, we called sidechains. The
cations (Dapps) is decentralized application, and finally, Network and Facility component defines type
Decentralized Autonomous Organization (DAO) is a of blockchain network on peer-to-peer usage, cloud
software-based governance structure over decentral- based, and virtualized containers used or not, etc.
ized network. Third, we used Consensus mechanism The development of all the components summarized
item that is distributed ledger on blockchain is ver- as the design shows in Table 1.
ified by consensus mechanism of a majority of the We designed a new Blockchain EA with 5 major
participants in the network system [23]. There are domains, and each of domain introduced new items
variety types of consensus algorithms such as ERC20 such as the PRM constructed with four new compo-
Ethereum network based, Proof of Work (PoW)-a nents, the BRM constructed with three new items,
node generating a block needs to prove that it has the DRM designed with four new elements, the ARM
enough computing power to solve cryptographic and
mathematical puzzle, while Proof of Stake (PoS) Table 1. Designed Blockchain Enterprise Architecture
selects node that has more wealth [23], and other (BEA) reference model
Delegated Proof of Stake (DPoS) for nodes those Constructed Constructed Constructed
Reference Reference Components Description
worked on selected master nodes, Proof of Consensus
Model Model
(PoC) that doesn’t involve mining service, etc. Next,
Components
we added mining service use to blockchain block cre- Performance • Goal: Purpose of system, and
ation incentive. Finally, we added other features for Reference objectives, strategy
the application components that ability to use con- Model (PRM) • Area / Field: Type of industry use
vergence application technologies for the system • Blockchain Detailed sub-sector use
use:
such as Artificial Intelligence (AI), Big data, Internet
• Scope: System coverage sites
of Things (IoT), etc. and area
Business • Supply Service involved
4.5 Development of Infrastructure Reference Reference Chain Services: stakeholders
Model Model (BRM) • Scalability: Blockchain Transaction
Per Second (TPS)
• Needs / Blockchain use demand,
For the Infrastructure Reference Model (IRM), we Demand: why is it needed?
followed as defined in CRM, and it is the taxonomy Data • Data /Asset What type of data /asset
based for categorizing IT infrastructure, hardware Reference on Blockchain: on Blockchain as data
providing functionality, and hosting, data center, Model (DRM) (original data/assets,
transaction records, etc.)
cloud, virtualization related network, platform and
• Validation Proof of Existence (PoE),
facility components considered in this domain [22]. Data (PoE): data existence validation
We used three components under infrastructure check function
from blockchain facilities, network and platform • Blockchain Third Party Data Storage
type. The first, Blockchain type defines the platform Storage (3P): Blockchain use (such as
Storj, Sia, FileCoin,
design. It consists of Public blockchain – all the
Swarm, IPFS, etc.)
records are transparent, Private blockchain – only • Data file System data related
among private nodes will store and access to the standardizatio standards
records, and permissioned blockchain – only allowed n:

6 Journal of Information Technology and Architecture

 Blockchain Reference Model and Use Case for Supply Chains within Enterprise Architecture

Table 1. Designed Blockchain Enterprise Architecture

(BEA) reference model (continued)
Constructed Constructed Constructed
Reference Reference Components Description
Model Model
Components
Application • Smart Using Smart contract/
Reference Contract: Chaincode for automated
Model (ARM) action
• Dapps/DAO: Using Decentralized
Applications (Dapps) or
Decentralized
Autonomous
Organization (DAO)
Figure 2. Counterfeit Drug Detection Supply chain system
• Consensus Using type of consensus
using Blockchain [24]
Mechanism: algorithms such as:
• ERC20 based (ETH)
• Proof of Work (PoW)
• Proof of Stake (PoS) supply chain market, and detect and eliminate fake
• Delegated Proof of medicines from the market. This will lead to saving
Stake (DPoS) thousands of lives, as well as economical contribu-
• Proof of Consensus
tions to drug manufacturers and consumers [17].
(PoC)
• Other Other application Therefore, we selected “Counterfeit medicine detec-
features: technologies convergence tion using Blockchain and AI” project ongoing in
with Blockchain such as Mongolia, and to demonstrate and apply it to our
Artificial Intelligence developed BEA reference model as a use case. Our
(AI), Big data, Internet of
selected use case the example supply chain consists
Things (IoT), etc.
• Mining Information about
from Manufactures of drugs to end-user customers
Service use: mining service, Intensive through warehouse, distribution channel, hospital or
to mining nodes or not pharmacies. Each of the supply chain stakeholders
Infrastructur • Blockchain Type of Blockchain such should be checked through the blockchain based
e Reference Type: as Public/Private/
counterfeit medicine detection system. Supply chain
Model (IRM) Permissioned or Hybrid
• Blockchain Main network/ side chain
shown in Figure 2.
Platform: Based on the interview method and feasibility
• Network and Type of Blockchain study documents with Mongolian “Counterfeit med-
Facilities: network on Peer-to-Peer: icine detection using Blockchain and AI” project part-
Public/Private node,
ner company and experts, we applied as an example
Clouds, Virtualized
containers, etc.
use case for supply chain on our developed Block-
chain Enterprise Architecture in each domain as fol-
lows.
developed with five measures, and the IRM created Firstly, in the Performance Model, the goal of the
with three new components as shown in Table 1. project is to detect counterfeit drugs from the global
supply chain network starts from the Mongolia. The
5. Use Case: Pharmaceutical Supply Chain project area is the pharmaceutical industry, and the
blockchain technology used for record interoperabil-
Among the potential applications of Blockchain in ity, track and trace, inspect originality of drugs in
the supply chain domain, it looks promising for manufacturing supply chain. The project scope is
tracking counterfeit drugs in the global and domestic strategically global, and start from piloting from

Journal of Information Technology and Architecture 7

Tumennast Erdenebold, Jae Jeung Rho, and Yoon Min Hwang

Mongolia. Table 2. Applied pharmaceutical supply chain case for the

Secondly, in the Business Model, case project Blockchain Enterprise Architecture

applied supply chain services stakeholders are gov- Performance • Goal: Detect counterfeit drugs
Model • Area/Field: Pharmaceutical
ernment, pharmaceutical related manufacturer,
• Blockchain use: Manufacturing
warehouse, distributor companies, hospital and supply chain
pharmacy retailers. And business function for block- • Scope/site: Global/Mongolia
chain scalability would be 10,000 transactions per Business • Supply Chain Services:
second, and main purpose and demand for using Model Government, pharmaceutical companies,
hospitals, and pharmacy retailers.
blockchain is to check originality, increase trust,
• Scalability: 10,000 TPS
auditability of drug records, keeping immutable his- • Needs: Trust-Originality, auditability,
tory of medicines, increase interoperability efficiency, an immutable history, efficiency, cost
providing security from the counterfeit, and cost sav- savings, security
ings among supply chain. Data • Data/Asset on Blockchain:
Model Transaction data
Thirdly, in the Data Model, this use case project
• Validation Data (PoE): Yes
drugs transmitted transaction record data stored in • Blockchain Storage (3P): No
blockchain. In addition, the system will use the drug • Data File Standardization: Falsified
data proof of existence, and system will not use third- Medicine Database, and Drug
party decentralized storage. Moreover, from the serialization at origin
Application • Smart Contract: Yes, (Automated
manufacturer drug serialization at origin, they used
Model reporting, ERC20 compliant)
falsified medicine database standard. • Dapps/ DAO: Not using
Next, in the Application Model, an example use • Consensus Mechanism: ERC20
case project used Smart contract for automated based/ PoS
reporting of drugs transmission throughout the sup- • Other features: Big data analysis,
Artificial Intelligence, Application
ply chain. It will not use any decentralized applica-
programming interface.
tions (Dapps), and Decentralized Autonomous • Mining Service use: No
Organization (DAO). For the consensus mechanism, Infrastructure • Blockchain Type: Hybrid (Private
and it will use Ethereum ERC20 compliant standard Model plus Public/
with Proof of Stake (PoS) consensus algorithm. In Permissioned)
• Blockchain Platform: Ethereum-
addition, this case project is not using the mining
based side chain
service for creating a blockchain, and other applica- • Network and Facilities: Peer-to-Peer
tion features including Artificial Intelligence (AI), big on Cloud
data analysis, and to provide interoperability the
Application programming Interface (API) is used.
Finally, in the Infrastructure Model, example proj- chain Enterprise Architecture (BEA) with reference
ect defined hybrid blockchain type, including private models in the supply chain field based on Consoli-
and public, permissioned systems based on the led- dated Refence Model domains of the FEAF. It has five
ger record requirements. The blockchain platform is reference domains models: performance, business,
Ethereum based sidechain, and the blockchain net- data, applications, and infrastructure, and for each
work uses Peer-to-Peer network based on the cloud domain we newly introduced three to five reference
computing system. The summary of use case example components for Blockchain-based systems in the sup-
potted by each domain as a result shown in Table 2. ply chain.
This study is important because we constructed a
6. Discussion and Conclusion new Blockchain Enterprise Architecture (BEA) in the
supply chain and practically demonstrated its use in
Through this study, we designed a novel Block- the pharmaceutical supply chain to detect counter-

8 Journal of Information Technology and Architecture

 Blockchain Reference Model and Use Case for Supply Chains within Enterprise Architecture
feit drugs using Blockchain technology. Moreover, the
Blockchain Enterprise Architecture (BEA) approach
will contribute to practitioners when mapping their
complex blockchain based strategy implementation
use of ontology view IT business, management and
technical alignment holistically.
The limitations of this research are that we selected,
designed, and demonstrated our supply chain domain
in the case of the pharmaceutical industry.
Further studies should involve different industries
in the supply chain and extend the reference item
options of Blockchain, as well as employ different
Enterprise Architecture points of view such as
TOGAF. Finally, this study reference model needs
more expert’s empirical validation for the further
development.
Acknowledgements
This work was supported by the KAIST GCORE
(Global Center for Open Research with Enterprise)
grant funded by the Ministry of Science and ICT
(Project# N11190116), and a partnership with TG
Consulting Company.
References
[1] Tasca, P. and Widmann, S., “The challenges faced by
blockchain technologies - Part 1,” Journal of Digital
Banking, Vol. 2, No. 2, pp. 132-147, 2017.
[2] Federation of EA Professional Organizations, “Common
Perspectives on Enterprise Architecture”, in Architec-
ture and Governance Magazine, Issue 9-4, November
2013.
[3] Condos, J., Sorrell, W. H., and Donegan, S. L. “Block-
chain technology: Opportunities and risks.” Vermont,
January, 15, 2016.
[4] Biggs, J., Hinish, S. R., Natale, M. A., and Patronick,
M. “Blockchain: Revolutionizing the global supply chain
by building trust and transparency,” 2017.
[5] Chichoni, J. and Webb, S. “The digital global supply
chain: The growing case for blockchain technology
expansion within global supply chain,” Marriott Stu-
dent Review, Vol. 2, No. 2, Article 5, 2018.
[6] Singh, P. M., van Sinderen, M. J., and Wieringa, R. J.
Smart logistics: An enterprise architecture perspective.
In CAiSE Forum. 29th CAiSE Conference, pp. 9-16,
2017.
[7] L. Candela, G. Athanasopoulos, D. Castelli, K. El Raheb,
P. Innocenti, Y. Ioannidis, A. Katifori, A. Nika, G. Vullo,
S. Ross: The Digital Library Reference Model, April,
2011.
[8] Clements, Paul, Felix Bachmann, Len Bass, David
Garlan, James Ivers, Reed Little, Paulo Merson; Robert
Nord, Judith Stafford. Documenting Software Archi-
tectures: Views and Beyond, Second Edition. Boston:
Addison-Wesley, 2010. ISBN 0-321-55268-7.
[9] Federation of EA Professional Organizations, “Com-
mon Perspectives on Enterprise Architecture,” Archi-
tecture and Governance Magazine, Issue 9-4, Novem-
ber, 2013.
[10] The Chief Information Officers Council. Federal Enter-
prise Architecture Framework Version 1.1, at the Way-
back Machine. September, 1999.
[11] Tumennast.E, “A Smart Government EA Framework
for m-Services in Mongolia: Case Study Based App-
roach,” LAP LAMBERT Academic Publishing. ISBN:
978-3330086326, May, 2017.
[12] Urbaczewski, L. and Mrdalj, S. “A comparison of enter-
prise architecture frameworks,” Issues in Information
Systems, Vol. 7, No. 2, pp. 18-23, 2006.
[13] Roger Sessions, “Comparision of the top four Enterprise
Architecture methodologies”, May 2007. Retrieved on
Dec 2018 from http://www3.cis.gsu.edu/dtruex/courses/
CIS8090/2013Articles/A%20Comparison%20of%20the
%20Top%20Four%20Enterprise-Architecture%20Meth
odologies.html
[14] Tian, F. An agri-food supply chain traceability system
for China based on RFID & blockchain technology. In
Service Systems and Service Management (ICSSSM),
2016 13th International Conference on IEEE, pp. 1-6,
June, 2016.
[15] Chandra, C. and Kumar, S. “Enterprise architectural
framework for supply-chain integration,” Industrial
Management & Data Systems, Vol. 101, No. 6, pp. 290-
304, 2001.
[16] Chief Information Officer Council. A Practical Guide to
Federal Enterprise Architecture Archived 2008-10-10
at the Wayback Machine. February, 2001.
[17] The OECD report, World Government Summit. “Emb-
racing Innovation in Government: Global Trends 2019,”
Counterfeit Medicine Detection Using Blockchain and
AI (Mongolia) case, pp. 118-122, 2019.
[18] Xsolus. Different Types of Blockchain Networks, Ret-
rieved from https://blog.xsolus.com/different-types-of-
blockchain-networks, on 22 February 2019.
[19] Consolidated Refernce Model, FEAF v 2, Retrieved
from https://eapad.dk/gov/us/feaf2/consolidated-refer-
Journal of Information Technology and Architecture 9
 Tumennast Erdenebold, Jae Jeung Rho, and Yoon Min Hwang

ence-model/, on 23 February 2019. ved on February 2019 from https://www.gao.gov/assets/

[20] Tambo, T. and Koch, C. Enterprise architecture in the
supply chain. In 2010 IEEE/ACIS 9th International
Conference on Computer and Information Science.
IEEE. pp. 881-886, August 2010
[21] Chen, D., Doumeingts, G., and Vernadat, F. “Architec-
tures for enterprise integration and interoperability:
Past, present and future,” Computers in industry, Vol.
59, No. 7, pp. 647-659, 2008.
[22] Chief Information Officer Council. “A Practical Guide
to Federal Enterprise Architecture” version 1.0, Retrie-
590/588407.pdf
[23] Crosby, M., Pattanayak, P., Verma, S., and Kalyanar-
aman, V. “Blockchain technology: Beyond bitcoin,”
Applied Innovation, Vol. 2, No. 6-10, 71, 2016.
[24] The OECD-Observatory of Public Sector Innovation
“Counterfeit Medicine Detection Using Blockchain and
AI”, retrieved on Feb 2019 from https://oecd-opsi.org/
innovations/counterfeit-medicine-detection-using-block
chain-and-ai/

Dr. Tumennast Erdenebold

Bs.Cs in Computer Hardware & Software Engineering (Dual major) - Mongolian University of
Science and Technology, M.A & Ph.D. (Management of Information & Telecommunication Tech-
nology) –Korea Advanced Institute of Science and Technology (KAIST). Post-Doctoral
Researcher: Korea Advanced Institute of Science and Technology (KAIST).

Prof. Jae-Jeung Rho

B.S. – Dept. of Mechanical Engineering, Seoul National University (SNU), M.S. – Dept. of
Mechanical Engineering, Texas A&M University, Ph.D. – Dept. of Industrial Engineering, Uni-
versity of Houston. Professor of School of Business and Technology Management & Director
of Global Information and Telecommunications Technology Program (ITTP) at Korea Advanced
Institute of Science and Technology (KAIST).

Prof. Yoon Min Hwang

B.A in Management & Economics (Dual Major), Computer Science (Sub-Major) - Han-Dong Uni-
versity. M.A & Ph. D. (Business & Technology Management) - Korea Advanced Institute of Sci-
ence and Technology (KAIST). Assistant Professor of School of Business at Chungbuk National
University (CBNU).

10 Journal of Information Technology and Architecture

View publication stats