<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article  PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">OJBM</journal-id>
      <journal-title-group>
        <journal-title>Open Journal of Business and Management</journal-title>
      </journal-title-group>
      <issn pub-type="epub">2329-3284</issn>
      <publisher>
        <publisher-name>Scientific Research Publishing</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.4236/ojbm.2021.92051</article-id>
      <article-id pub-id-type="publisher-id">OJBM-108188</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Articles</subject>
        </subj-group>
        <subj-group subj-group-type="Discipline-v2">
          <subject>Business&amp;Economics</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>


          Multiperspective Assessment of Enterprise Data Storage Systems: The Use of Expert Judgment Quantification and Constant Sum Pairwise Comparison in Finding Criteria Weights

        </article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author" xlink:type="simple">
          <name name-style="western">
            <surname>Luja</surname>
            <given-names>Shrestha</given-names>
          </name>
          <xref ref-type="aff" rid="aff1">
            <sup>1</sup>
          </xref>
        </contrib>
        <contrib contrib-type="author" xlink:type="simple">
          <name name-style="western">
            <surname>Nasir</surname>
            <given-names>Jamil Sheikh</given-names>
          </name>
          <xref ref-type="aff" rid="aff1">
            <sup>1</sup>
          </xref>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <addr-line>Department of Technology Management, University of Bridgeport, Bridgeport, USA</addr-line>
      </aff>
      <pub-date pub-type="epub">
        <day>22</day>
        <month>02</month>
        <year>2021</year>
      </pub-date>
      <volume>09</volume>
      <issue>02</issue>
      <fpage>955</fpage>
      <lpage>980</lpage>
      <history>
        <date date-type="received">
          <day>19,</day>
          <month>February</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>28,</day>
          <month>March</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>31,</day>
          <month>March</month>
          <year>2021</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>&#169; Copyright  2014 by authors and Scientific Research Publishing Inc. </copyright-statement>
        <copyright-year>2014</copyright-year>
        <license>
          <license-p>This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/</license-p>
        </license>
      </permissions>
      <abstract>
        <p>


          Digital transformation has taken center stage in every IT organization. Data is being created at various sources: edge, core, and cloud at an unprecedented rate. For enterprise IT infrastructure, this means more places to store data and more ways to store them. Storage solutions can be broadly categorized as Direct Attached Storage (DAS), Storage Area Network (SAN), Network Attached Storage (NAS), Hyperconverged Infrastructure (HCI), and Public Cloud Storage, each with its advantages and potential drawbacks. Besides computing and networking, storage is one of the core physical components of an IT infrastructure. Application performance and availability depend strongly on their underlying storage. As such, the selection of storage systems is one of the critical decisions for IT executives. Assessment of Enterprise Data Storage Systems (EDSS) for selecting the one that provides a comprehensive solution requires not only the consideration of technical performance and economic feasibility but also other perspectives such as strategic, operational, and regulatory. An assessment model with multiple perspectives and related criteria will serve as a valuable reference in the decision-making process. This study uses expert judgment to validate an assessment model covering Strategic, Technological, Operational, Regulatory, and Economic (STORE) perspectives and their related criteria. Expert judgment is also used to calculate the criteria weights using the constant sum pairwise comparison method. The results can be used for the evaluation of various storage alternatives under consideration. It is anticipated that the STORE assessment model and criteria weights will be valid for IT organizations in their long-term strategic decision-making.

        </p>
      </abstract>
      <kwd-group>
        <kwd>Enterprise Data Storage Systems</kwd>
        <kwd> EDSS</kwd>
        <kwd> STORE Assessment Model</kwd>
        <kwd> Multi-Criteria Decision Making (MCDM)</kwd>
        <kwd> Expert Judgment Quantification</kwd>
        <kwd> Constant Sum Pairwise Comparison</kwd>
        <kwd> Criteria Weights</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="s1">
      <title>1. Introduction</title>
      <p>
        The source of unprecedented data growth in recent years is many and varied. International Data Corporation (IDC) estimated that the Global Datasphere, a measure of all new data collected, created, and replicated in a year across the globe, will grow from 33 Zettabytes (10<sup>21</sup> bytes) in 2018 to 175 by 2025 (Reinsel et al., 2018). A zettabyte is a trillion Gigabytes.
      </p>
      <p>In May 2020, IDC published an update. The estimated growth of data for the year 2020 alone was 59 Zettabytes with a forecast of continued growth through 2024 with a five-year compound annual growth rate (CAGR) of 26%. The COVID-19 pandemic contributes to this figure by causing an abrupt increase in the number of work-from-home employees and rapid digitization (IDC, 2020).</p>
      <p>
        A vast majority of this data is transmitted, processed, and stored at enterprise data centers. The remarkably high rate of new data creation means there need to be more storage systems in the enterprise data centers. These days, enterprise IT infrastructure consists of tens of thousands of physical and virtual servers and their associated hardware like servers, network equipment, and storage systems spread across geographies. The amount of data stored in each data center is in multiple Petabytes (10<sup>15</sup> bytes).
      </p>
      <p>Storage systems consist of dedicated servers, storage media, and related software to obtain a high-performance, high availability, and efficiently managed system. The main types of storage media used in data centers are tape drives, magnetic hard drives, and solid-state drives. Enterprise-grade hardware is meant to run continuously, twenty-four hours a day, seven days a week.</p>
      <p>Storage systems have developed over decades, improving performance, cutting cost, and, most importantly, enabling modern computing needs by supporting the new types of workloads. The recent industry trend in IT infrastructure management emphasizes automation of the daily repetitive tasks through various commercially available software or homegrown scripts. Another trend in enterprise IT is to leverage public cloud storage for offloading some or most management responsibilities to a third party.</p>
      <p>Enterprise data storage systems go through hardware refresh every three to five years to take advantage of newly available features and reduce risks due to aging hardware. These are multi-million-dollar decisions involving implementation and data migration plans that span months to years.</p>
      <p>Technology assessment is the evaluation and estimation of the nature, quality, or ability of the technology. It started as a form of public policy research to examine various short and long-term consequences of technology use. Such analysis requires consideration of multiple perspectives and criteria.</p>
      <p>Multiple Criteria Decision Making (MCDM) is one of the most widely used decision methodologies in various fields that aim to satisfy the multitude of conflicting objectives in the best possible way. We derive measurements by directly comparing objects. Thomas L. Saaty established that direct comparisons are necessary to establish measurements for intangible properties with no scales of measurement (Saaty, 2008). Methods based on pairwise comparison form a significant part of multiple criteria decision making.</p>
      <p>Decision-makers need models that are updated, capturing all significant perspectives and criteria. IT executives in the decision-making positions often supplement their knowledge with advice from experts in the field. This study discusses the use of expert judgment in the assessment of enterprise data storage systems. Expert judgment can be defined as an expert opinion given in the context of a specific decision problem. Expert judgment is a recognized, mature research methodology suitable for assessing emerging technology where benchmarks have not been established or no objective data is available. Expert judgment quantification utilizes rating instruments in the form of a questionnaire to convert informed estimates from the experts to numeric values. This study uses a constant sum pairwise comparison to record one criterion or perspective’s importance versus another. The information that the experts provide becomes data. Conclusions are drawn by combining expert judgments as an aggregation of quantitative estimates.</p>
      <p>In this study, we map the process of expert judgment to validate the STORE assessment model for assessing enterprise data storage systems (Shrestha &amp; Sheikh, n.d.). We also used quantification of expert judgment in finding the criteria weights. This study speaks primarily to the decision-makers who fill one of these roles:</p>
      <p>&#183; Senior Executives responsible for leadership and technology purchase decisions</p>
      <p>&#183; Storage Managers responsible for providing the storage services</p>
      <p>&#183; Storage Architects responsible for the design of storage solutions</p>
      <p>&#183; Storage Engineers engaged in the implementation of storage solutions</p>
      <p>&#183; IT Operations Staff responsible for the daily operations</p>
    </sec>
    <sec id="s2">
      <title>2. Literature Review</title>
      <p>
        We performed a literature review to understand and develop a scholarly base for the three related research areas: Enterprise IT, Data Storage, and Technology Assessment as shown in <xref ref-type="fig" rid="fig1">Figure 1</xref> (Shrestha &amp; Sheikh, n.d.).
      </p>
      <p>The review enabled identifying gaps in prior research, specifically, the lack of a comprehensive decision model, covering Strategic, Technological, Operational, Regulatory, and Economic (STORE) perspectives. Each of the STORE perspectives was subjectively categorized and considered a preferentially orthogonal dimension. Preferentially orthogonal perspectives are the independent dimensions. The combined dimensions are then deemed to be comprehensive for the assessment of EDSS.</p>
      <p>Strategic perspective considers high and low level, short- and long-term goals of the organization. Technological perspective considers various criteria that relate to the capability and efficiency of the storage system. The operational perspective considers how the product will affect the day-to-day operations of the IT function. The regulatory perspective considers the legal aspects of technology implementation. The economic perspective considers the financial aspects of the solution. We derived twenty criteria by grouping the related concepts and categorized them under the five STORE perspectives.</p>
      <p>This study expands our literature review to expert judgment quantification and constant sum pairwise comparison in finding criteria weights for multiple criteria decision making. We explore the recent use of these methods in the information technology domain.</p>
      <p>Multiple criteria decision making refers to all methods that help designate a preferred alternative and rank alternatives based on subjective preferences, where there is more than one criterion (Ho, 2008). Some authors (Zimmermann, 1991; Chen &amp; Hwang, 1992) categorized MCDM into two categories: 1) Multi-Attribute Decision Making (MADM) problems, where the number of alternatives is predetermined, and 2) Multi-Objective Decision Making (MODM), where they are not.</p>
      <p>MCDM has been used in the study of cloud service selection (Rehman et al., 2011), IT infrastructure selection for smart grid (Rezagholizadehl et al., 2013), big data storage selection (Kachaoui &amp; Belangour, 2019), IT disaster recovery site selection (Yang et al., 2015) and justification of IT investments (Borenstein &amp; Betencourt, 2005).</p>
      <p>Expert judgment quantification adds substantial value in analyzing complex problems when there are no universally accepted scientific laws or extensive data available. Keeney &amp; Von Winterfeldt (1989) stressed the value of quantifying expert judgments to complement the expert’s qualitative thinking and reasoning. They also highlighted the need for explicit judgments to avoid misinterpretations and misuse.</p>
      <p>Expert judgment has been studied in various fields, including cybersecurity (Holm et al., 2014), web development projects (Torrecilla-Salinas et al., 2019), regression models of software effort estimation (Tsunoda et al., 2012), the potential of blockchain in supply chain management (Kopyto et al., 2020) and addressing uncertainty in high technology system design (Chytka et al., 2006).</p>
      <p>The constant sum pairwise comparison method is used in the scientific study of preferences, attitudes, and requirements engineering. It reflects the importance or priority attached by a respondent to one entity compared to another. The number of independent pairwise comparisons for n number of entities is n(n − 1)/2. In multiperspective hierarchical decision making, criteria are the lower-level entities to perspectives in the hierarchy. Constant sum pairwise comparison has a relative orientation providing more decision context than binary choices. It is unavoidably more complex than a binary or discrete choice task, resulting in inattention or higher drop-out rates (Skedgel &amp; Regier, 2015).</p>
      <p>Pairwise comparison has been used in various fields, including IT infrastructure refresh planning for enterprises (Daim et al., 2011), engineering design (Dym et al., 2002), document ranking algorithms in information retrieval systems (Ozbey &amp; Dincsoy, 2020), intelligent transportation recommendation systems (Borodinov et al., 2020), and image quality assessment (Zhang et al., 2017).</p>
    </sec>
    <sec id="s3">
      <title>3. Development of Assessment Model</title>
      <p>
        <xref ref-type="fig" rid="fig2">Figure 2</xref> shows the STORE assessment model with five perspectives and twenty criteria in a hierarchy (Shrestha &amp; Sheikh, n.d.). Note that certain aspects of a criterion are covered by others in the model. For example, technical aspects of data security under regulatory perspective are considered in technology features under technological perspective.
      </p>
      <p>Short definitions of the perspectives and criteria:</p>
      <p>Strategic Perspective: Strategic perspective considers high and low level, short- and long-term goals of the organization.</p>
      <p>Technological Perspective: Technological perspective considers various criteria that relate to the storage system’s capability and efficiency.</p>
      <p>Operational Perspective: Operational perspective considers how the product will affect the day-to-day operations of the IT function.</p>
      <p>Regulatory Perspective: Regulatory perspective considers the legal compliance aspects of technology implementation. Note that some regulations like GDPR cover more than one criterion in the STORE regulatory perspective.</p>
      <p>Economic Perspective: Economic perspective considers the financial aspects of the solution.</p>
      <p>Business Strategy: Business strategy is a set of guiding principles that aim to achieve business objectives like service enablement, revenue growth, and cost-saving.</p>
      <p>Technology Strategy: Technology strategy explains how we should utilize technology as part of an organization’s business strategy.</p>
      <p>Organizational Readiness: Organizational readiness refers to the availability of a skilled workforce and defined processes for technology implementation and operations.</p>
      <p>Technology Feature: Technology features of storage systems include policy-based provisioning, orchestration, storage snapshot, and replication.</p>
      <p>System Performance: System performance of storage systems includes throughput in IOPS and latency.</p>
      <p>System Reliability: The system reliability of a storage system is a measure of performing consistently well. It contributes directly to the high availability of applications supported by the system.</p>
      <p>Capacity Management: Capacity management refers to the ease with which capacity is expanded when needed. Capacity management is aided by data reduction techniques like compression and deduplication.</p>
      <p>Technological Complexity: Technological complexity refers to a difficulty understanding the storage system and its interaction with other IT components.</p>
      <p>Storage Implementation: Storage implementation for an application involves setting up the physical hardware and cables, configuring the device, testing, and migrating data.</p>
      <p>Storage Administration: Storage administration tasks include provisioning storage, creating storage units, and performing cleanups.</p>
      <p>System Monitoring: System monitoring is essential for the fine-tuning of storage systems and identifying performance bottlenecks.</p>
      <p>System Reporting: System reporting is essential for keeping track of how well the system fulfills the needs. It also helps in making decisions related to capacity expansion and others.</p>
      <p>Vendor Support: Vendor support is characterized by the ease of creating service requests, communicating with support engineers, and a clear escalation path.</p>
      <p>Data Privacy: Data privacy relates to the protection of consumer data. Examples of the regulations that might be applicable are European Union General Data Protection Regulation (GDPR), California Consumer Privacy Act (CCPA), and others.</p>
      <p>Data Security: Data security refers to the prevention of unauthorized access. Laws like the Cybersecurity Information Sharing Act (CISA) equip organizations to secure the data from the latest cyber threats.</p>
      <p>Data Retention: Data retention means the safe keeping of data for future access. Examples of regulations that might be applicable are the Sarbanes Oxley Act (SOX) and Health Insurance Portability and Accountability Act (HIPPA).</p>
      <p>Data Transfer: Data transfer refers to the mobility of data. An example of data transfer regulation is cross-border data transfers under GDPR.</p>
      <p>Capital Expense: Capital expenses (CAPEX) consist of purchasing equipment or services towards fixed assets that the company will use beyond the current year.</p>
      <p>Operating Expense: Operating expenses (OPEX) refers to the ongoing expenses for the operation and maintenance, including the cost of power, space, and cooling in the data center.</p>
      <p>Total Cost of Ownership: Total cost of ownership (TCO) is a holistic view of the enterprise’s expenses over time.</p>
    </sec>
    <sec id="s4">
      <title>4. Expert Judgment Process</title>
      <p>
        <xref ref-type="fig" rid="fig3">Figure 3</xref> shows the process of expert judgment quantification used in this research study. It involved five steps: Define Decision Problem, Recruit Experts, Design Research Instruments, Collect Expert Judgment, and Analyze Expert Judgment.
      </p>
      <sec id="s4_1">
        <title>4.1. Define Decision Problem</title>
        <p>Data storage systems are essential components of enterprise IT operations. Application performances depend heavily on the underlying data storage systems. Storage system implementation and data migration can take years of coordinated effort and tens of millions of dollars in investment. A successful storage implementation can bring new IT capabilities, and a bad case can jeopardize entire enterprise IT stability. Performance issues in the storage systems or a total failure can cause costly service outages. Therefore, the selection of EDSS is a critical decision for IT executives.</p>
        <p>In enterprise IT infrastructure, hardware refresh takes place every three to five years. The supplier’s continual development in computer hardware and software technologies provides new features, but it also introduces more variables for the decision-making process. The availability of more options further complicates the process.</p>
        <p>IT executives need to assess various storage systems and select the best alternative to fulfill the business needs. Evaluation of an EDSS needs careful consideration of all related perspectives and criteria. A hierarchical model with criteria weights allows decision-makers to apply numeric methods. A multi-criteria decision model to assess the storage systems must be developed for a comprehensive approach to this problem. Experts are needed to validate the assessment model and assign weights subjectively.</p>
      </sec>
      <sec id="s4_2">
        <title>4.2. Recruit Experts</title>
        <p>The potential participants, experts in EDSS, were contacted initially through email, telephone calls, and in-person interviews to introduce them to the research. Their potential value was determined by expertise on the research topic and ability to answer related questions. All selected experts have demonstrated experience through vocation, education, or both with a minimum of ten years of related experience.</p>
        <p>We selected the experts based on their years of related experience working with leading information technology organizations. We formed six panels from the twenty-six participants—one for calculating the perspective weights and one each for criteria weights in the five STORE perspectives. Based on work experience, an expert could be included in more than one panel. Participation was voluntary and, we did not provide any financial incentives for participation.</p>
        <sec id="s4_2_1">
          <title>4.2.1. Expert Qualification</title>
          <p>
            <xref ref-type="table" rid="table1">Table 1</xref> shows the expert’s experience in years—total IT experience, and experience in each of the STORE perspectives related to EDSS. An asterisk (*) indicates the experience of fewer than ten years.
          </p>
          <table-wrap id="table1" >
            <label>
              <xref ref-type="table" rid="table1">Table 1</xref>
            </label>
            <caption>
              <title> Work experience of experts in years</title>
            </caption>
            <table>
              <tbody>
                <thead>
                  <tr>
                    <th align="center" valign="middle"  rowspan="2"  ></th>
                    <th align="center" valign="middle"  rowspan="2"  >Current Job Title</th>
                    <th align="center" valign="middle"  rowspan="2"  >Total IT Experience (Panel 1)</th>
                    <th align="center" valign="middle"  colspan="5"  >Experience with STORE perspectives</th>
                  </tr>
                </thead>
                <tr>
                  <td align="center" valign="middle" >Strategic (Panel 2)</td>
                  <td align="center" valign="middle" >Technological (Panel 3)</td>
                  <td align="center" valign="middle" >Operational (Panel 4)</td>
                  <td align="center" valign="middle" >Regulatory (Panel 5)</td>
                  <td align="center" valign="middle" >Economic (Panel 6)</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 1</td>
                  <td align="center" valign="middle" >Storage Engineer</td>
                  <td align="center" valign="middle" >18</td>
                  <td align="center" valign="middle" >5*</td>
                  <td align="center" valign="middle" >16</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >13</td>
                  <td align="center" valign="middle" >3*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 2</td>
                  <td align="center" valign="middle" >Systems Engineer</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >14</td>
                  <td align="center" valign="middle" >14</td>
                  <td align="center" valign="middle" >14</td>
                  <td align="center" valign="middle" >14</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 3</td>
                  <td align="center" valign="middle" >Systems Engineer</td>
                  <td align="center" valign="middle" >28</td>
                  <td align="center" valign="middle" >5*</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >5*</td>
                  <td align="center" valign="middle" >5*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 4</td>
                  <td align="center" valign="middle" >Senior Engineer</td>
                  <td align="center" valign="middle" >36</td>
                  <td align="center" valign="middle" >14</td>
                  <td align="center" valign="middle" >21</td>
                  <td align="center" valign="middle" >21</td>
                  <td align="center" valign="middle" >14</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 5</td>
                  <td align="center" valign="middle" >Backup and Storage Engineer</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >5*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 6</td>
                  <td align="center" valign="middle" >Systems Engineer</td>
                  <td align="center" valign="middle" >22</td>
                  <td align="center" valign="middle" >16</td>
                  <td align="center" valign="middle" >16</td>
                  <td align="center" valign="middle" >16</td>
                  <td align="center" valign="middle" >16</td>
                  <td align="center" valign="middle" >16</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 7</td>
                  <td align="center" valign="middle" >Vice President of Engineering</td>
                  <td align="center" valign="middle" >29</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >20</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 8</td>
                  <td align="center" valign="middle" >Sr. Systems Analyst</td>
                  <td align="center" valign="middle" >16</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >16</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >12</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 9</td>
                  <td align="center" valign="middle" >Solutions Architect</td>
                  <td align="center" valign="middle" >13</td>
                  <td align="center" valign="middle" >8*</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >8*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 10</td>
                  <td align="center" valign="middle" >IT Director</td>
                  <td align="center" valign="middle" >37</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >5*</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 11</td>
                  <td align="center" valign="middle" >Systems Engineer II</td>
                  <td align="center" valign="middle" >25</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >15</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 12</td>
                  <td align="center" valign="middle" >Database Architect</td>
                  <td align="center" valign="middle" >31</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 13</td>
                  <td align="center" valign="middle" >Storage Engineer</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >14</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >8*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 14</td>
                  <td align="center" valign="middle" >Manager of Backup Engineering</td>
                  <td align="center" valign="middle" >29</td>
                  <td align="center" valign="middle" >22</td>
                  <td align="center" valign="middle" >22</td>
                  <td align="center" valign="middle" >23</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >21</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 15</td>
                  <td align="center" valign="middle" >Sr. IT Engineer</td>
                  <td align="center" valign="middle" >30</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >25</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 16</td>
                  <td align="center" valign="middle" >Sr. Backup Engineer</td>
                  <td align="center" valign="middle" >35</td>
                  <td align="center" valign="middle" >7*</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >3*</td>
                  <td align="center" valign="middle" >3*</td>
                  <td align="center" valign="middle" >3*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 17</td>
                  <td align="center" valign="middle" >Systems Engineer II</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >6*</td>
                  <td align="center" valign="middle" >6*</td>
                  <td align="center" valign="middle" >6*</td>
                  <td align="center" valign="middle" >5*</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 18</td>
                  <td align="center" valign="middle" >Systems Engineer</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >4*</td>
                  <td align="center" valign="middle" >8*</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >6*</td>
                  <td align="center" valign="middle" >4*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 19</td>
                  <td align="center" valign="middle" >Capacity Planner</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >8*</td>
                  <td align="center" valign="middle" >8*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 20</td>
                  <td align="center" valign="middle" >Storage Engineer</td>
                  <td align="center" valign="middle" >25</td>
                  <td align="center" valign="middle" >25</td>
                  <td align="center" valign="middle" >25</td>
                  <td align="center" valign="middle" >25</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >15</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 21</td>
                  <td align="center" valign="middle" >Principal Storage Engineer</td>
                  <td align="center" valign="middle" >24</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >24</td>
                  <td align="center" valign="middle" >24</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >12</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 22</td>
                  <td align="center" valign="middle" >Advisory Engineer</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >9*</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >6*</td>
                  <td align="center" valign="middle" >9*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 23</td>
                  <td align="center" valign="middle" >Storage Engineer</td>
                  <td align="center" valign="middle" >21</td>
                  <td align="center" valign="middle" >12</td>
                  <td align="center" valign="middle" >18</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 24</td>
                  <td align="center" valign="middle" >Systems Engineer III</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 25</td>
                  <td align="center" valign="middle" >IT Director</td>
                  <td align="center" valign="middle" >11</td>
                  <td align="center" valign="middle" >4*</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >6*</td>
                  <td align="center" valign="middle" >4*</td>
                  <td align="center" valign="middle" >4*</td>
                </tr>
                <tr>
                  <td align="center" valign="middle" >Expert 26</td>
                  <td align="center" valign="middle" >Systems Engineer III</td>
                  <td align="center" valign="middle" >30</td>
                  <td align="center" valign="middle" >15</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >20</td>
                  <td align="center" valign="middle" >10</td>
                  <td align="center" valign="middle" >10</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec id="s4_2_2">
          <title>4.2.2. Formation of Expert Panels</title>
          <p>
            From the expert’s pool (<xref ref-type="table" rid="table1">Table 1</xref>), we formed six panels—one for calculating perspective weights and one each for criteria weights under the five STORE perspectives. Experts with at least ten years of experience in all five perspectives are included in panel 1. Panels 2 through 6 include experts with at least ten years of experience in the related perspectives.
          </p>
          <p>An expert can be included in more than one panel.</p>
          <p>Panel 1: Experts in all five STORE perspectives (14 experts).</p>
          <p>Expert 2, 4, 6, 7, 8, 11, 12, 14, 15, 20, 21, 23, 24, 26.</p>
          <p>Panel 2: Experts in Strategic Perspectives (18 experts).</p>
          <p>Expert 2, 4, 5, 6, 7, 8, 10, 11, 12, 13, 14, 15, 19, 20, 21, 23, 24, 26.</p>
          <p>Panel 3: Experts in Technological Perspectives (24 experts).</p>
          <p>Expert 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 19, 20, 21, 22, 23, 24, 25, 26.</p>
          <p>Panel 4: Experts in Operational Perspectives (22 experts).</p>
          <p>Expert 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13, 14, 15, 18, 19, 20, 21, 22, 23, 24, 26.</p>
          <p>Panel 5: Experts in Regulatory Perspectives (19 experts).</p>
          <p>Expert 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 20, 21, 23, 24, 26.</p>
          <p>Panel 6: Experts in Economic Perspectives (16 experts).</p>
          <p>Expert 2, 4, 6, 7, 8, 10, 11, 12, 14, 15, 17, 20, 21, 23, 24, 26.</p>
        </sec>
      </sec>
      <sec id="s4_3">
        <title>4.3. Design Research Instruments</title>
        <p>Pairwise comparison is a process in which experts rate a set of criteria, perspectives, or alternatives only two at a time. While this method is time-consuming to elicit all possible combinations and only provides relative data relations, recent research shows that people make better relative judgments than direct estimates (Benini et al., 2017). This study adopts the pairwise comparison method with seven stepped levels to assess solar photovoltaic technologies (Sheikh, 2013).</p>
        <p>We selected an elicitation situation of individual experts instead of interactive group or Delphi to avoid potential bias from group dynamics. We chose a web-based form as the mode of communication to capture encoded expert judgments. There were two questionnaires for the experts—the first questionnaire (Appendix A) validated the assessment model, and the second established criteria weights (Appendix B).</p>
      </sec>
      <sec id="s4_4">
        <title>4.4. Collect Expert Judgment</title>
        <p>We met with each expert through a video chat to explain the research study and question format through screen share. The sessions took about 20 minutes each. We then sent the web link to the experts with the following greeting message:</p>
        <p>“This research study aims to develop a comprehensive assessment model to evaluate Enterprise Data Storage Systems (EDSS). EDSS represents the servers, storage media, or appliance used for storing digital data. Some examples of EDSS are Storage Area Network (SAN), Network Attached Storage (NAS), Direct Attached Storage (DAS), Hyperconverged Infrastructure (HCI), and Public Cloud Storage.</p>
        <p>You are being asked to participate in this research study because of your EDSS expertise. Your experience working with the leading information technology organizations makes you uniquely valuable to this research.</p>
        <p>The questionnaire (I) relates to the validation of the STORE assessment model. Questionnaire (II) has a total of 42 pairwise comparison questions with multiple-choice answers. Questions are not specific to any job, organization, or vendor but EDSS in general. These questionnaires should not take more than 30 minutes.</p>
        <p>Informed Consent: Participation in this research activity is voluntary. The participants may withdraw at any time without penalty or loss of benefits. The questionnaires are anonymous. Please do not enter any personally identifiable information.”</p>
      </sec>
      <sec id="s4_5">
        <title>4.5. Analyze Expert Judgment</title>
        <p>After collecting the expert judgment, we used a quantification scale described below with a constant sum of 100.</p>
        <p>Attribute A is four times as important as Attribute B; A = 80 and B = 20</p>
        <p>Attribute A is three times as important as Attribute B; A = 75 and B = 25</p>
        <p>Attribute A is two times as important as Attribute B; A = 67 and B = 33</p>
        <p>Attribute A is equally important as Attribute B; A = 50 and B = 50</p>
        <p>Attribute A is one-half times important as Attribute B; A = 33 and B = 67</p>
        <p>Attribute A is one-third times important as Attribute B; A = 25 and B = 75</p>
        <p>Attribute A is one-fourth times important as Attribute B; A = 20 and B = 80</p>
        <p>A score of zero is entered for both A and B when experts do not qualify for the panel. In the next steps, we aggregated the scores to obtain combined values.</p>
        <sec id="s4_5_1">
          <title>4.5.1. Panel 1: Perspective Weights</title>
          <p>
            <xref ref-type="table" rid="table2">Table 2</xref> shows the quantified expert judgment on questions 1 through 10 (Appendix B) using the method explained in Section 4.5.
          </p>
          <p>Sum of perspective scores from all pairwise comparisons:</p>
          <p>Strategic Perspective = 845 + 789 + 662 + 713 = 3,009</p>
          <p>Technological Perspective = 555 + 843 + 696 + 763 = 2,857</p>
          <p>Operational Perspective = 611 + 557 + 717 + 777 = 2,662</p>
          <p>Regulatory Perspective = 738 + 704 + 683 + 860 = 2,985</p>
          <p>Economic Perspective = 687 + 637 + 623 + 540 = 2,487</p>
          <p>Total Score = 3,009 + 2,857 + 2,662 + 2,985 + 2,487 = 14,000</p>
        </sec>
        <sec id="s4_5_2">
          <title>4.5.2. Panel 2: Strategic Perspective</title>
          <p>
            <xref ref-type="table" rid="table3">Table 3</xref> shows the quantified expert judgment on questions 11 through 13 (Appendix B) using the method explained in Section 4.5.
          </p>
          <p>Sum of criterion scores from all pairwise comparisons:</p>
          <p>Business Strategy = 956 + 875 = 1,831</p>
          <p>Technology Strategy = 844 + 1,056 = 1,900</p>
          <p>Organizational Readiness = 875 + 744 = 1,696</p>
          <p>Total Score = 1,831 + 1,900 + 1,696 = 5,400</p>
        </sec>
        <sec id="s4_5_3">
          <title>4.5.3. Panel 3: Technological Perspective</title>
          <p>
            <xref ref-type="table" rid="table4">Table 4</xref> shows the quantified expert judgment on questions 14 through 23 (Appendix B) using the method explained in Section 4.5.
          </p>
          <p>Sum of criterion scores from all pairwise comparisons:</p>
          <p>Technology Features = 1,177 + 1,048 + 1,267 + 1,252 = 4,744</p>
          <p>System Performance = 1,223 + 1,158 + 1,471 + 1,461 = 5,313</p>
          <p>System Reliability = 1,352 + 1,242 + 1,491 + 1,571 = 5,656</p>
          <p>Capacity Management = 1,133 + 929 + 909 + 1,437 = 4,408</p>
          <p>Technological Complexity = 1,148 + 939 + 829 + 963 = 3,879</p>
          <p>Total Score = 4,744 + 5,313 + 5,656 + 4,408 + 3,879 = 24,000</p>
        </sec>
        <sec id="s4_5_4">
          <title>4.5.4. Panel 4: Operational Perspective</title>
          <p>
            <xref ref-type="table" rid="table5">Table 5</xref> shows the quantified expert judgment on questions 24 through 33 (Appendix B) using the method explained in Section 4.5.
          </p>
          <p>Sum of criterion scores from all pairwise comparisons:</p>
          <p>Storage Implementation = 1,020 + 1,011 + 1,091 + 988 = 4,110</p>
          <p>Storage Administration = 1,180 + 1,269 + 1,353 + 1,057 = 4,859</p>
          <p>System Monitoring = 1,189 + 931 + 1,214 + 1,091 = 4,425</p>
          <p>System Reporting = 1,109 + 847 + 986 + 940 = 3,882</p>
          <p>Vendor Support = 1,212 + 1,143 + 1,109 + 1,260 = 4,724</p>
          <p>Total Score = 4,110 + 4,859 + 4,425 + 3,882 + 4,724 = 22,000</p>
        </sec>
        <sec id="s4_5_5">
          <title>4.5.5. Panel 5: Regulatory Perspective</title>
          <p>
            <xref ref-type="table" rid="table6">Table 6</xref> shows the quantified expert judgment on questions 34 through 39 (Appendix B) using the method explained in Section 4.5.
          </p>
          <p>Sum of criterion scores from all pairwise comparisons:</p>
          <p>Data Privacy = 937 + 1,080 + 1,068 = 3,085</p>
          <p>Data Security = 963 + 1,246 + 1,154 = 3,363</p>
          <p>Data Transfer = 820 + 654 + 917 = 2,391</p>
          <p>Data Retention = 832 + 746 + 983 = 2,561</p>
          <p>Total Score = 3,085 + 3,363 + 2,391 + 2,561 = 11,400</p>
        </sec>
        <sec id="s4_5_6">
          <title>4.5.6. Panel 6: Economic Perspective</title>
          <p>
            <xref ref-type="table" rid="table7">Table 7</xref> shows the quantified expert judgment on questions 40 through 42 (Appendix B) using the method explained in Section 4.5.
          </p>
          <p>Sum of criterion scores from all pairwise comparisons:</p>
          <p>Capital Expense = 1,011 + 838 = 1,849</p>
          <p>Operating Expense = 589 + 860 = 1,449</p>
          <p>Total Cost of Ownership = 762 + 740 = 1,502</p>
          <p>Total Score = 4,800</p>
          </sec>
        </sec>
        </sec>
          </body>
            
          <back>
            <ref-list>
              <title>References</title>
              <ref id="scirp.108188-ref1">
                <label>1</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Benini, A., Chataigner, P., Noumri, N., Parham, N., Sweeney, J., &amp; Tax, L. (2017). Expert Judgment: The Use of Expert Judgment in Humanitarian Analysis: Theory, Methods and Applications. Geneva: Assessment Capacities Project.
                  https://www.acaps.org/sites/acaps/files/resources/files/acaps_expert_judgment_-_full_study_august_2017.pdf
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref2">
                <label>2</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Borenstein, D., &amp; Betencourt, P. R. B. (2005). A Multi-Criteria Model for the Justification of IT Investments. Information Systems and Operational Research, 43, 1-21.
                  https://doi.org/10.1080/03155986.2005.11732711
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref3">
                <label>3</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Borodinov, A., Agafonov, A., &amp; Myasnikov, V. (2020). A Method of Preference and Utility Elicitation by Pairwise Comparisons and Its Application to Intelligent Transportation Recommendation Systems. 10th International Conference on Information Science and Technology, Bath, London, and Plymouth, 9-15 September 2020, 77-85.
                  https://doi.org/10.1109/ICIST49303.2020.9201952
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref4">
                <label>4</label>
                <mixed-citation publication-type="other" xlink:type="simple">Chen, S.-J., &amp; Hwang, C.-L. (1992). Fuzzy Multiple Attribute Decision Making Methods (pp. 289-486). Berlin, Heidelberg: Springer. https://doi.org/10.1007/978-3-642-46768-4</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref5">
                <label>5</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Chytka, T. M., Conway, B. A., &amp; Unal, R. (2006). An Expert Judgment Approach for Addressing Uncertainty in High Technology System Design. Portland International Conference on Management of Engineering and Technology, 1, 444–449.
                  https://doi.org/10.1109/PICMET.2006.296590
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref6">
                <label>6</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Daim, T. U., Letts, M., Krampits, M., Khamis, R., Dash, P., Monalisa, M., &amp; Justice, J. (2011). IT Infrastructure Refresh Planning for Enterprises: A Business Process Perspective. Business Process Management Journal, 17, 510-525.
                  https://doi.org/10.1108/14637151111136397
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref7">
                <label>7</label>
                <mixed-citation publication-type="other" xlink:type="simple">Dym, C. L., Wood, W. H., &amp; Scott, M. J. (2002). Rank Ordering Engineering Designs: Pairwise Comparison Charts and Borda Counts. Research in Engineering Design, 13, 236-242. https://doi.org/10.1007/s00163-002-0019-8</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref8">
                <label>8</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Ho, W. (2008). Integrated Analytic Hierarchy Process and Its Applications—A Literature Review. European Journal of Operational Research, 186, 211-228.
                  https://doi.org/10.1016/j.ejor.2007.01.004
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref9">
                <label>9</label>
                <mixed-citation publication-type="other" xlink:type="simple">Holm, H., Sommestad, T., Ekstedt, M., &amp; Honeth, N. (2014). Indicators of Expert Judgement and Their Significance: An Empirical Investigation in the Area of Cyber Security. Expert Systems, 31, 299-318. https://doi.org/10.1111/exsy.12039</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref10">
                <label>10</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  International Data Corporation (IDC) (2020). Worldwide Global DataSphere IoT Device and Data Forecast, 2020-2024.
                  https://www.idc.com/getdoc.jsp?containerId=US46718220
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref11">
                <label>11</label>
                <mixed-citation publication-type="book" xlink:type="simple">
                  Kachaoui, J., &amp; Belangour, A. (2019). A Multi-Criteria Group Decision Making Method for Big Data Storage Selection. In M. Atig, &amp; A. Schwarzmann (Eds.), NETYS 2019: Networked Systems (pp. 381-386). Cham: Springer.
                  https://doi.org/10.1007/978-3-030-31277-0_25
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref12">
                <label>12</label>
                <mixed-citation publication-type="other" xlink:type="simple">Zimmermann, H. J. (1991). Fuzzy Set Theory—And Its Applications. Dordrecht: Springer.</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref13">
                <label>13</label>
                <mixed-citation publication-type="other" xlink:type="simple">Zhang, Z., Zhau, J., Liu, N., Gu, X., &amp; Zhang, Y. (2017). An Improved Pairwise Comparison Scaling Method for Subjective Image Quality Assessment. 2017 IEEE International Symposium on Broadband Multimedia Systems and Broadcasting, Cagliari, 7-9 June 2017, 1-6. https://doi.org/10.1109/BMSB.2017.7986235</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref14">
                <label>14</label>
                <mixed-citation publication-type="other" xlink:type="simple">Yang, C. L., Yuan, B. J. C., &amp; Huang, C. Y. (2015). Key Determinant Derivations for Information Technology Disaster Recovery Site Selection by the Multi-Criterion Decision Making Method. Sustainability, 7, 6149-6188. https://doi.org/10.3390/su7056149</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref15">
                <label>15</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Tsunoda, M., Monden, A., Keung, J., &amp; Matsumoto, K. (2012). Incorporating Expert Judgment into Regression Models of Software Effort Estimation. 2012 19th Asia-Pacific Software Engineering Conference, Hong Kong, 4-7 December 2012, 374-379.
                  https://doi.org/10.1109/APSEC.2012.58
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref16">
                <label>16</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Torrecilla-Salinas, C. J., De Troyer, O., Escalona, M. J., &amp; Mejías, M. (2019). A Delphi-Based Expert Judgment Method Applied to the Validation of a Mature Agile Framework for Web Development Projects. Information Technology and Management, 20, 9-40.
                  https://doi.org/10.1007/s10799-018-0290-7
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref17">
                <label>17</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Skedgel, C., &amp; Regier, D. A. (2015). Constant-Sum Paired Comparisons for Eliciting Stated Preferences: A Tutorial. Patient, 8, 155-163.
                  https://doi.org/10.1007/s40271-014-0077-9
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref18">
                <label>18</label>
                <mixed-citation publication-type="other" xlink:type="simple">Shrestha, L., &amp; Sheikh, N. J. (n.d.). Multiperspective Assessment of Enterprise Data Storage Systems: Literature Review. Portland International Conference on Management of Engineering and Technology (PICMET).</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref19">
                <label>19</label>
                <mixed-citation publication-type="other" xlink:type="simple">Sheikh, N. J. (2013). Assessment of Solar Photovoltaic Technologies Using Multiple Perspectives and Hierarchical Decision Modeling. Ph.D. Theses, Portland, OR: Portland State University.</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref20">
                <label>20</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Saaty, T. L. (2008). Relative Measurement and Its Generalization in Decision Making Why Pairwise Comparisons Are Central in Mathematics for the Measurement of Intangible Factors The Analytic Hierarchy/Network Process (To the Memory of my Beloved Friend Professor Sixto Rios Garcia). Revista de la Real Academia de Ciencias Exactas, Fisicas y Naturales. Serie A. Matematicas, 102, 251-318.
                  https://doi.org/10.1007/BF03191825
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref21">
                <label>21</label>
                <mixed-citation publication-type="other" xlink:type="simple">Rezagholizadehl, M., Mehrannii, P., Barzegar, A., Fereidunian, A., Moshiri, B., &amp; Lesani, H. (2013). A Probabilistic Partial Order Theory Approach to IT Infrastructure Selection for Smart Grid. International Conference on Control, Automation and Systems, Gwangju, 20-23 October 2013, 488-493. https://doi.org/10.1109/ICCAS.2013.6703983</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref22">
                <label>22</label>
                <mixed-citation publication-type="other" xlink:type="simple">Reinsel, D., Gantz, J., &amp; Rydning, J. (2018). The Digitization of the World from Edge to Core. Framingham, MA: International Data Corporation.</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref23">
                <label>23</label>
                <mixed-citation publication-type="other" xlink:type="simple">Rehman, Z. U., Hussain, F. K., &amp; Hussain, O. K. (2011). Towards Multi-Criteria Cloud Service Selection. Proceedings of 2011 5th International Conference on Innovative Mobile and Internet Services in Ubiquitous Computing, Seoul, 30 June-2 July 2011, 44-48. https://doi.org/10.1109/IMIS.2011.99</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref24">
                <label>24</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Ozbey, C., &amp; Dincsoy, O. (2020). An Efficient Pairwise Comparison Scheme for Document Ranking. 2020 28th Signal Processing and Communications Applications Conference, Gaziantep, 5-7 October 2020, 1-4.
                  https://doi.org/10.1109/SIU49456.2020.9302078
                </mixed-citation>
              </ref>
              <ref id="scirp.108188-ref25">
                <label>25</label>
                <mixed-citation publication-type="other" xlink:type="simple">Kopyto, M., Lechler, S., von der Gracht, H. A., &amp; Hartmann, E. (2020). Potentials of Blockchain Technology in Supply Chain Management: Long-Term Judgments of an International Expert Panel. Technological Forecasting and Social Change, 161, Article ID: 120330. https://doi.org/10.1016/j.techfore.2020.120330</mixed-citation>
              </ref>
              <ref id="scirp.108188-ref26">
                <label>26</label>
                <mixed-citation publication-type="other" xlink:type="simple">
                  Keeney, R. L., &amp; Von Winterfeldt, D. (1989). On the Uses of Expert Judgment on Complex Technical Problems. IEEE Transactions on Engineering Management, 36, 83-86.
                  https://doi.org/10.1109/17.18821
                </mixed-citation>
              </ref>
            </ref-list>
          </back>
</article>