<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Implementation Framework for Hyperloop Decision-Making Ecosystem</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Aleksejs Vesjolijs</string-name>
          <email>vesjolijs.a@tsi.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Accenture</institution>
          ,
          <addr-line>1 Grand Canal Square, Dublin, D04 EE70</addr-line>
          ,
          <country country="IE">Ireland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Transport and Telecommunication Institute</institution>
          ,
          <addr-line>Lauvas 2, Riga, LV-1019</addr-line>
          ,
          <country country="LV">Latvia</country>
        </aff>
      </contrib-group>
      <fpage>116</fpage>
      <lpage>126</lpage>
      <abstract>
        <p>The Hyperloop technology is an ultra-high-speed transportation mode proposed and envisioned by Elon Musk in 2012 by reimagining vactrains. It leverages pods moving un supersonic speed in 3-m vacuum tubes using magnetic levitation for propulsion. Technology Readiness Level is TRL 5 according to HORIZON 2020 standards. At the end of 2023, the shutdown of Hyperloop ONE, one of the largest companies in the Hyperloop industry, emphasized significant challenges in the implementation of Hyperloop technology and revealed dynamic nature of Hyperloop project. This study identifies a research gap: the absence of digital decision-making systems specifically designed for Hyperloop projects. To address this gap, the research presents a six-stage implementation framework for an Hyperloop decision-making ecosystem. The study involves the creation of a functional block diagram, the design of a technical solution blueprint, and the proposal and validation of the implementation framework using a unit testing method on an Hyperloop project case. The proposed technical solution integrates several advanced technologies, including the Snowflake data warehouse, Streamlit, Vensim, Microsoft PowerBI, GPT-4, PostgreSQL, and custom Python applications. The framework's validation process involved iterative testing and refinement, resulting in an increase in the project maturity model from the level 'Defined' to the 'Capable'.</p>
      </abstract>
      <kwd-group>
        <kwd>Hyperloop</kwd>
        <kwd>software ecosystem</kwd>
        <kwd>data engineering</kwd>
        <kwd>dataops</kwd>
        <kwd>decision-making</kwd>
        <kwd>digital transformation 1</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Hyperloop marked revolution in transportation since its complex and innovative concept
was introduced by Elon Musk back in 2012 that was later documented in Hyperloop Alpha
Paper publication by Tesla (SpaceX) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Technology initially is envisioned as ultra-high
speed transportation mode which is able to transfer passengers and cargo on supersonic
speed overcoming Kantrowitz limit [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. According to Hyperloop Alpha Paper, a new
mobility solution proposed to use vacuum tubes of 3.3 m diameter and capsules with
frontal area up to 4 m2. These capsules are propelled and guided along a track, it was
designed with distributed acceleration points to minimize the infrastructure, only
requiring energy over a small fraction of the track. The Hyperloop transportation system
(HTS) is considered a promising alternative to short-haul flights, offering reduced travel
times and lower fuel consumption per passenger revenue kilometer [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        The technology is currently at a low maturity level from engineering, operational, and
cost perspectives [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Significant technological, regulatory, planning, financial, and
environmental issues must be resolved before HTS can achieve commercial viability. The
successful deployment of Hyperloop systems requires an integrated approach that
leverages advanced digital tools and technologies to stream-line decision-making
processes.
      </p>
      <p>Research aims to propose a structured approach for integrating various digital tools
and technologies to support decision-making processes in Hyperloop projects. The goal is
to design a framework for implementing Hyperloop decision-making ecosystem.</p>
      <p>Research questions.</p>
      <p>Q1. What are the key components necessary for developing and deploying a digital
decision-making ecosystem specifically designed for Hyperloop technology projects?
Q2. What strategy(s) can be adopted to implement decision-making ecosystem?
Q3. How does the proposed Hyperloop decision-making ecosystem improve project
maturity levels?</p>
      <p>Research tasks and objectives.</p>
      <p>O1. Review existing literature on Hyperloop projects, frameworks and best practices
in digital systems, particularly in the context of complex techno-logical projects and define
decision-making ecosystem.</p>
      <p>O2. Identify and define key components, technologies, and methodologies that are
relevant to the implementation of digital ecosystems.</p>
      <p>O3. Establish the relationships and interactions between Hyperloop decision-making
ecosystem components within the framework.</p>
      <p>O4. Develop an implementation framework.</p>
      <p>O5. Conduct framework approbation.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Research Methodology</title>
      <p>The research methodology for the development of implementation framework for
Hyperloop decision-making ecosystem is shown in Figure 1. The state-of-the-art contains
a problem definition, literature analysis to define research gap, ecosystem definition.</p>
      <p>The Functional Block Diagram (FBD) method is selected to map underlying ecosystem’s
processes in structured approach. It serves as a basis for the technical solution blueprint.
The design step involves identifying the key components and technologies necessary for
development and deployment of a digital decision-making ecosystem. Step 3 is the
development of implementation framework based on the conceptual model. It contains
framework design, integration and deployment strategy, and discussion on potential
challenges. Step 4 is framework approbation and conceptional adoption using Python
programming language unit testing method. The proposed research methodology is aimed
to achieve research goals, addressing the complex and multidisciplinary nature of
implementing digital decision-making ecosystems for Hyperloop projects.</p>
    </sec>
    <sec id="sec-3">
      <title>3. State-of-the-Art</title>
      <p>In this Section, research state-of-the-art is presented. Hyperloop decision-making
ecosystem is described, concept is discussed, and Functional Block diagram is de-signed. It
contributes to completing Research Objective 1 (O1).</p>
      <sec id="sec-3-1">
        <title>3.1. Problem Definition</title>
        <p>
          Due to technology complexity [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], dynamic nature of Hyperloop project [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], challenged
decisions [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], the Hyperloop is still in TRL 5 according to Horizon 2020 standards [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. The
implementation of Hyperloop systems present complex decision-making challenges that
underlines necessitate a robust ecosystem for effective management that answers the
following success factors: namely reliability, scalability, technical feasibility, quantum
factor, safety, regulatory approval, social acceptance, environmental sustainability,
infrastructure integration and usability factors [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Study has filtered out and analysed 95
papers in Scopus DB (keywords – hyperloop, hyperloop system(s), hyperloop project(s),
hyperloop decision-making, hyperloop challenges, et al) and identified research gap, that
currently there is no hyperloop decision-making ecosystem software that can
improve decision-making process for Hyperloop project, by assessing success factors of
Hyperloop implementation for specific case.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Hyperloop Decision-Making Ecosystem</title>
        <p>To address the research gap, the study proposes the concept of the Hyperloop
DecisionMaking Ecosystem and implementation framework for future product deployment. The
Hyperloop Decision-Making Ecosystem is a technology platform that applies the enhanced
ETL process with use of Generative AI. Research proposed refined ecosystem definition
for ecosystem specific for Hyperloop project based on literature analysis: a networked
community of actors (organisations, software products, individuals) supported by an
underpinning technological platform in the same environment that enables actors to process
multivariate data, produce knowledge, extract insights, foster innovation, create value, and
support decision-making.</p>
        <p>Ecosystem’s functional block diagram (FBD) is shown on Figure 2. Initial INPUT 1-7
correlates to multivariate input sources (1 – Generative AI model, 2 – external database(s),
3 – internal database(s), 4 - sensors, 5 – satellite data, 6 – industry reports, 7 – user input).</p>
        <p>The Hyperloop decision-making ecosystem is a software framework designed to
leverage big data for the efficient planning and implementation of Hyperloop project. As a
big data product, this ecosystem integrates diverse datasets, employing advanced
analytics, machine learning, and predictive modeling to facilitate informed
decisionmaking. The ecosystem is structured to handle the complexity and scale of data generated
by various actors (see INPUTS 1-7 above). By transforming raw data into actionable
insights, the ecosystem enables stakeholders to make data-driven decisions that enhance
safety, efficiency, and cost-effectiveness. Advanced analytics tools process data to identify
patterns, predict potential issues, and optimize performance. Ecosystem finite state is data
visualization and system modelling which accessed by end users of the system.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Design</title>
      <p>In this Section Hyperloop decision-making ecosystem technical solution blueprint is
prosed, and components are identified and defined. It contributes to the completion of
Research Objectives 2 and 3 (O2 and O3).</p>
      <p>
        As a big data product, Hyperloop decision-making ecosystem utilizes
ExtractTransform-Load approach [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], enhanced with Generative AI (GenAI), namely
ExtractGenerate-Transform-Load. The ecosystem’s adaptive structure promotes scalability,
flexibility, enabling continuous improvement and development in response to the evolving
needs of the Hyperloop industry.
      </p>
      <p>The technical solution presented in Figure 3 is a sophisticated system designed to
streamline the collection, processing, analysis, and visualisation of data pertinent to
decision-making in Hyperloop technology according to FBD (Figure 2).</p>
      <p>Detailed ecosystem’s components are presented in Table 1. The framework starts with
the ingestion of diverse datasets through external databases, web crawlers, and API
connectors. Once data is collected, a dedicated component utilising AI technology
interprets and extracts relevant information from various. This data is transferred to a
centralised data warehouse managed in Snowflake. In the next phase, data is cleaned and
enriched to improve its quality with the help of AI. To supplement decision-making in
cases when data is missing, synthetic data is generated based on existing statistical
patterns using Generative AI. The architecture emphasises data resilience through
multiple backups within Snowflake.</p>
      <p>System dynamics models used to simulate various scenarios, thereby aiding in the
prediction of outcomes based on different Hyperloop design and operational strategies.
The final stage is data visualization using PowerBI interactive dashboards, built on top of
Streamlit applications.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Implementation Framework</title>
      <p>In this Section Implementation framework is proposed, implementation challenges are
discussed, and framework approbation is conducted. It contributes to the completion of
Research Objectives 3, 4 and 5 (O3, O4, O5).</p>
      <sec id="sec-5-1">
        <title>Component</title>
      </sec>
      <sec id="sec-5-2">
        <title>Hyperloop decision-making ecosystem components</title>
      </sec>
      <sec id="sec-5-3">
        <title>Name Data extraction API connector</title>
      </sec>
      <sec id="sec-5-4">
        <title>Web crawler</title>
      </sec>
      <sec id="sec-5-5">
        <title>External data source Data transfer</title>
      </sec>
      <sec id="sec-5-6">
        <title>Synthetic data generation Data cleanup</title>
      </sec>
      <sec id="sec-5-7">
        <title>Python application Data transfer</title>
      </sec>
      <sec id="sec-5-8">
        <title>Snowflake</title>
      </sec>
      <sec id="sec-5-9">
        <title>Python</title>
      </sec>
      <sec id="sec-5-10">
        <title>ChatGPT 4</title>
      </sec>
      <sec id="sec-5-11">
        <title>Python</title>
      </sec>
      <sec id="sec-5-12">
        <title>Python</title>
        <p>Database backup Snowflake
Data enrichment ChatGPT 4</p>
      </sec>
      <sec id="sec-5-13">
        <title>Data analytics</title>
      </sec>
      <sec id="sec-5-14">
        <title>Snowflake</title>
      </sec>
      <sec id="sec-5-15">
        <title>Data processing, Snowflake</title>
        <p>transformations
Database backup Snowflake
Simulation data ChatGPT 4</p>
      </sec>
      <sec id="sec-5-16">
        <title>Database backup Snowflake</title>
      </sec>
      <sec id="sec-5-17">
        <title>API enrichment</title>
      </sec>
      <sec id="sec-5-18">
        <title>ChatGPT 4</title>
      </sec>
      <sec id="sec-5-19">
        <title>Data enrichment ChatGPT 4</title>
      </sec>
      <sec id="sec-5-20">
        <title>Database backup Snowflake</title>
        <p>Application Streamlit</p>
      </sec>
      <sec id="sec-5-21">
        <title>System modelling Dashboard visualization</title>
      </sec>
      <sec id="sec-5-22">
        <title>Vensim</title>
      </sec>
      <sec id="sec-5-23">
        <title>Power BI COM1 COM2 COM3</title>
        <p>COM4
COM5
COM6
COM7
COM8
COM9
COM10
COM11
COM12
COM13
COM14
COM15
COM16
COM17
COM18
COM19
COM20
COM21
COM22</p>
      </sec>
      <sec id="sec-5-24">
        <title>Technology Description</title>
      </sec>
      <sec id="sec-5-25">
        <title>ChatGPT 4 Extracts from GenAI knowledge base. Python Connects to external APIs to fetch data directly into the system from various Internet of Things devices.</title>
        <p>Python Gathers data from various online sources
to be processed and analysed.</p>
        <p>PostgreSQL External data collected from various
sources for processing.</p>
      </sec>
      <sec id="sec-5-26">
        <title>Transfers extracted data into Snowflake</title>
        <p>for centralized data handling.</p>
        <p>Provides backup services for data.
Enhances data quality by adding missing
information or correcting errors.</p>
        <p>Generates artificial data based on
patterns learned from real data.</p>
      </sec>
      <sec id="sec-5-27">
        <title>Cleans and prepares data for analysis, removing errors and inconsistencies. Application built in Python to process and handle data operations.</title>
      </sec>
      <sec id="sec-5-28">
        <title>Facilitates the movement of processed</title>
        <p>data to different parts of the system.
Component that analyses big data,
applies machine learning and advanced
analytics
Processes and further transforms data
applying business logic.</p>
      </sec>
      <sec id="sec-5-29">
        <title>Provides backup services for data.</title>
        <p>Uses advanced models to simulate data
scenarios for further analysis.</p>
        <p>Snowflake database containing
production data gathered in all previous
steps.</p>
        <p>Uses APIs to enrich data with additional
external insights.</p>
        <p>Further enriches data post-transfer with
additional context and information.
Provides backup services for data.
A bridge between data and
visualizations.</p>
        <p>System modelling core that will be used
for visualization in COM22.</p>
      </sec>
      <sec id="sec-5-30">
        <title>Creates interactive dashboards for data analysis and reporting. 121</title>
        <sec id="sec-5-30-1">
          <title>5.1. Framework Overview</title>
          <p>Existing software development frameworks, methods, and paradigms are analysed. Agile
and Waterfall do not exactly fit given ecosystem, because they are mainly aimed at the
team’s approach to managing project tasks, rather specific digital system implementation
framework. They can be adopted to develop specific components of ecosystem as different
teams can be involved for their development. For example, COM6 and COM16 can be done
by one team using Waterfall method and COM1-COM4 can be implemented by another
team which adopted Agile. Proposed framework utilizes hybrid methodology adopting
selected methods features (Table 2).</p>
          <p>
            The framework is presented in Figure 4. It is purposed for evaluating and guiding the
deployment of Hyperloop decision-making ecosystem. At the end of each cycle project
maturity model is reevaluated according to Capability Maturity Model Integration (CMMI)
[
            <xref ref-type="bibr" rid="ref17">17</xref>
            ].
          </p>
          <p>Implementing a digital ecosystem for Hyperloop projects presents several challenges.
Integration of diverse and vast data sources can pose a challenge as Hyperloop systems
generate large amounts of data from various sensors, operational logs, and maintenance
records. Ensuring data quality and consistency across these different sources is crucial for
accurate analysis and decision-making, involving data cleaning, transformation, and
enrichment processes that can be resource-intensive and complex to manage, however
integrated in the ecosystem by design (Figure 3, COM7-9).</p>
          <p>
            Ecosystem and implementation framework can be considered as part of digital
transformation processes of the society and introduces shift to digital business system
from monolithic by its design. It incorporates such technologies as AI, Big Data, Data
Analytics, Internet of Things, Cloud Computing, Data Warehousing, and others (Table 1)
which are essential drivers of digital transformation. Digital transformation has an
influence on human lives, industrial processes, circular economy, various systems, and
their Key Performance Indicators. Data privacy and cybersecurity of ecosystem affect all
mentioned above impacts [
            <xref ref-type="bibr" rid="ref18">18</xref>
            ]. Therefore, each component of ecosystem must answer
regional data protection policies, such as General Data Protection Regulation (GDPR) [
            <xref ref-type="bibr" rid="ref19">19</xref>
            ]
in EU and incorporate best software development practices in mitigating cybersecurity
risks. Further, pursuit to comply with European strategy for data [
            <xref ref-type="bibr" rid="ref20">20</xref>
            ] principles must be
considered as summarized in Figure 5.
          </p>
          <p>Another challenge is the need for seamless collaboration among a wide range of
stakeholders, including engineers, regulatory bodies, investors, and business users. The
project leadership must provide transparent and accessible means for stakeholders to
monitor system performance, simulate scenarios, and make informed decisions. The
implementation process must address the scalability and flexibility of the ecosystem to
accommodate the evolving needs of the Hyperloop industry. To conclude, the success of
the Hyperloop decision-making ecosystem depends on effectively managing these
challenges to create a scalable, efficient, and reliable framework for data-driven
decisionmaking.</p>
        </sec>
        <sec id="sec-5-30-2">
          <title>5.2. Framework Approbation</title>
          <p>Framework approbation is conducted on hypothetical case of Hyperloop Baltics
implementation, for which synthetic data was generated and included in Python script
(Appendices A, files tests/unit/synthetic_data.py and
tests/unit/synthetic_maturity_data.py).</p>
          <p>Implementation framework approbation is conducted using unittest method in Python
programming language pytest library on synthetic data generated for Hyperloop Baltics
project. Unit testing strategy and results are presented in Figure 6, source code is publicly
available on GitHub, see Appendices A. In scope of tests, 43 unit tests were executed with
SUCCESS status. Project maturity level check indicates an increase of maturity model
CMMI metrics which include Hyperloop project success factors (Section 3.1). As a result,
project maturity model increased from defined to capable and each of underlying
contributing factors increased as well.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusions</title>
      <p>The research goal is completed by proposing a framework (Figure 4) for implementing a
digital decision-making ecosystem designed specifically for Hyperloop projects (Figure 3).
The framework integrates ETL process enhanced with Generative AI envisioned in
solution components (COM1-COM22, Table 1). Structured technical solution blueprint is
based on FBD (Figure 2) correlating to system inputs, outputs, and desired result which
contributes to completion of research aim. By unifying diverse data sources into a
centralized platform, the ecosystem facilitates informed decision-making, predictive
maintenance, and process optimization, providing knowledge and insights to end users.
Implementation framework guides ecosystem development and integration. It is scalable
and flexible as it incorporates selected features from seven software development
methods (Table 2) and can be adopted to other digital systems with similar parameters.
The approbation is conducted using unit tests on synthetic data (Figure 6), contributing to
implementation strategy adoption to given use case. The output of each implementation
cycle is revised project maturity model according to CMMI.</p>
      <p>
        Contribution. Research contributes to the field of telematics and logistics, data
engineering and project management, within the context of Hyperloop technology. It
supports EU digital targets 2030 [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] by enabling digital transformation of businesses and
European strategy for data [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. Framework is designed for use by Hyperloop project
stakeholders as guiding steps for digital system deployment and integration. It is
committed to increasing the Hyperloop technology project’s chances of success given the
dynamic and innovative nature of HTS and ability to adapt to scope changes.
      </p>
      <p>Limitations. Synthetic data is used for implementation framework approbation.</p>
      <p>
        Future steps. The next step involves further tests and framework approbation using
real world data for various real Hyperloop projects from different regions and using
different methods. It is planned to apply the given framework to the Hyperloop Baltics
startup project, aiming to implement Hyperloop technology for passenger and freight
transport in the Baltic and Nordic regions. This development will contribute to the green
and digital transformation aligned with the EU Mobility Strategy [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ].
      </p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgements</title>
      <sec id="sec-7-1">
        <title>Research supervisor – Professor Dr.Sc.Ing Telecommunication Institute.</title>
      </sec>
      <sec id="sec-7-2">
        <title>Mihails Savrasovs, Transport and</title>
        <p>The code for framework approbation can be accessed via public GitHub repository at
https://github.com/pirrencode/tsi_hl_framework_implementation/tree/main.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>E. Musk,</surname>
          </string-name>
          "Hyperloop Alpha,"
          <year>2013</year>
          . [Online]. Available: https://www.tesla.com/sites/default/files/blog_images/hyperloop-alpha.pdf. [Accessed:
          <fpage>01</fpage>
          -Mar-2024].
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bizzozero</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Sato</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Sayed</surname>
          </string-name>
          ,
          <article-title>"Aerodynamic study of a Hyperloop pod equipped with compressor to overcome the Kantrowitz limit,"</article-title>
          <source>Journal of Wind Engineering and Industrial Aerodynamics</source>
          , vol.
          <volume>218</volume>
          , p.
          <fpage>104784</fpage>
          ,
          <year>2021</year>
          . https://doi.org/10.1016/j.jweia.
          <year>2021</year>
          .
          <volume>104784</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>J. K.</given-names>
            <surname>Noland</surname>
          </string-name>
          ,
          <article-title>"Prospects and Challenges of the Hyperloop Transportation System: A Systematic Technology Review,"</article-title>
          <source>IEEE Access</source>
          , vol.
          <volume>9</volume>
          , pp.
          <fpage>28439</fpage>
          -
          <lpage>28458</lpage>
          ,
          <year>2021</year>
          . https://doi.org/10.1109/ACCESS.
          <year>2021</year>
          .
          <volume>3057788</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>F. C.</given-names>
            <surname>Barbosa</surname>
          </string-name>
          ,
          <article-title>"Hyperloop Concept Technological and Operational Review: The Potential to Fill Rail Niche Markets," in 2020 Joint Rail Conference</article-title>
          , St. Louis, Missouri, USA, p.
          <fpage>V001T03A004</fpage>
          ,
          <year>2020</year>
          . https://doi.org/10.1115/JRC2020-8033.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Turner</surname>
          </string-name>
          ,
          <article-title>"Elon Musk abandons Hyperloop project months after ramping up testing</article-title>
          ,"
          <year>2022</year>
          . [Online]. Available: https://www.cityam.
          <article-title>com/elon-musk-abandons-hyperloopproject-months-after-ramping-up-testing/</article-title>
          . [Accessed:
          <fpage>12</fpage>
          -May-2024].
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Bloomberg</surname>
          </string-name>
          ,
          <article-title>"Hyperloop One to Shut Down After Failing to Reinvent Transit,"</article-title>
          <year>2023</year>
          . [Online]. Available: https://www.bloomberg.com/news/articles/2023-12- 21/hyperloop-one
          <article-title>-to-shut-down-after-raising-millions-to-reinvent-transit</article-title>
          . [Accessed:
          <fpage>28</fpage>
          -Jan-2024].
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>European</given-names>
            <surname>Commission</surname>
          </string-name>
          ,
          <article-title>"Technology Readiness Levels (TRL</article-title>
          ),
          <year>" 2014</year>
          . [Online]. Available: https://ec.europa.eu/research/participants/data/ref/h2020/wp/2014_2015/annex es/h2020-wp1415
          <string-name>
            <surname>-</surname>
          </string-name>
          annex
          <article-title>-g-trl_en</article-title>
          .pdf. [Accessed:
          <fpage>12</fpage>
          -May-2024].
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>A.</given-names>
            <surname>Vesjolijs</surname>
          </string-name>
          ,
          <article-title>"Overview of Factors and Methods for Analysis of Hyperloop Project," in Reliability and Statistics in Transportation and Communication, I. Kabashkin, I. Yatskiv, and</article-title>
          <string-name>
            <given-names>O.</given-names>
            <surname>Prentkovskis</surname>
          </string-name>
          , Eds. Springer Nature Switzerland, Cham,
          <year>2024</year>
          , pp.
          <fpage>281</fpage>
          -
          <lpage>291</lpage>
          . https://doi.org/10.1007/978-3-
          <fpage>031</fpage>
          -53598-7_
          <fpage>25</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>P.</given-names>
            <surname>Vassiliadis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Simitsis</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Skiadopoulos</surname>
          </string-name>
          ,
          <article-title>"Conceptual modeling for ETL processes,"</article-title>
          <source>in Proceedings of the 5th ACM International Workshop on Data Warehousing and OLAP</source>
          , pp.
          <fpage>14</fpage>
          -
          <lpage>21</lpage>
          ,
          <year>2002</year>
          . https://doi.org/10.1145/583890.583893.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>K.</given-names>
            <surname>Maroukian</surname>
          </string-name>
          and
          <string-name>
            <given-names>S. R.</given-names>
            <surname>Gulliver</surname>
          </string-name>
          ,
          <article-title>"Leading DevOps Practice</article-title>
          and
          <string-name>
            <given-names>Principle</given-names>
            <surname>Adoption</surname>
          </string-name>
          ,"
          <year>2020</year>
          . https://doi.org/10.48550/ARXIV.
          <year>2008</year>
          .
          <volume>10515</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>M.</given-names>
            <surname>Poppendieck</surname>
          </string-name>
          ,
          <article-title>"</article-title>
          <source>Lean Software Development," in 29th International Conference on Software Engineering (ICSE'07 Companion)</source>
          , MN, USA, pp.
          <fpage>165</fpage>
          -
          <lpage>166</lpage>
          ,
          <year>2007</year>
          . https://doi.org/10.1109/ICSECOMPANION.
          <year>2007</year>
          .
          <volume>46</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>M.</given-names>
            <surname>Rodriguez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. J. P.</given-names>
            <surname>De Araújo</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Mazzara</surname>
          </string-name>
          ,
          <article-title>"Good practices for the adoption of DataOps in the software industry,"</article-title>
          <source>J. Phys.: Conf. Ser.</source>
          , vol.
          <volume>1694</volume>
          , p.
          <fpage>012032</fpage>
          ,
          <year>2020</year>
          . https://doi.org/10.1088/
          <fpage>1742</fpage>
          -6596/1694/1/012032.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>P.</given-names>
            <surname>Beynon-Davies</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Carne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Mackay</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Tudhope</surname>
          </string-name>
          ,
          <article-title>"Rapid application development (RAD): an empirical review,"</article-title>
          <source>European Journal of Information Systems</source>
          , vol.
          <volume>8</volume>
          , pp.
          <fpage>211</fpage>
          -
          <lpage>223</lpage>
          ,
          <year>1999</year>
          . https://doi.org/10.1057/palgrave.ejis.
          <volume>3000325</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>S.-D.</given-names>
            <surname>Axinte</surname>
          </string-name>
          , G. Petrica,
          <string-name>
            <given-names>and I.-D.</given-names>
            <surname>Barbu</surname>
          </string-name>
          ,
          <article-title>"Managing a software development project complying with PRINCE2 standard,"</article-title>
          <source>in 2017 9th International Conference on Electronics, Computers and Artificial Intelligence (ECAI)</source>
          , IEEE, Targoviste, pp.
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          ,
          <year>2017</year>
          . https://doi.org/10.1109/ECAI.
          <year>2017</year>
          .
          <volume>8166435</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>I. A.</given-names>
            <surname>Machado</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Costa</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M. Y.</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <article-title>"Data Mesh: Concepts and Principles of a Paradigm Shift in Data Architectures,"</article-title>
          <source>Procedia Computer Science</source>
          , vol.
          <volume>196</volume>
          , pp.
          <fpage>263</fpage>
          -
          <lpage>271</lpage>
          ,
          <year>2022</year>
          . https://doi.org/10.1016/j.procs.
          <year>2021</year>
          .
          <volume>12</volume>
          .013.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>Y. H.</given-names>
            <surname>Kwak</surname>
          </string-name>
          and
          <string-name>
            <given-names>F. T.</given-names>
            <surname>Anbari</surname>
          </string-name>
          ,
          <article-title>"Benefits, obstacles, and future of six sigma approach,"</article-title>
          <source>Technovation</source>
          , vol.
          <volume>26</volume>
          , pp.
          <fpage>708</fpage>
          -
          <lpage>715</lpage>
          ,
          <year>2006</year>
          . https://doi.org/10.1016/j.technovation.
          <year>2004</year>
          .
          <volume>10</volume>
          .003.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>R.</given-names>
            <surname>Wendler</surname>
          </string-name>
          ,
          <article-title>"The maturity of maturity model research: A systematic mapping study,"</article-title>
          <source>Information and Software Technology</source>
          , vol.
          <volume>54</volume>
          , pp.
          <fpage>1317</fpage>
          -
          <lpage>1339</lpage>
          ,
          <year>2012</year>
          . https://doi.org/10.1016/j.infsof.
          <year>2012</year>
          .
          <volume>07</volume>
          .007.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>D. P. F.</given-names>
            <surname>Möller</surname>
          </string-name>
          ,
          <article-title>"Cybersecurity in Digital Transformation,"</article-title>
          <source>Advances in Information Security</source>
          , vol.
          <volume>103</volume>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>70</lpage>
          ,
          <year>2023</year>
          . https://doi.org/10.1007/978-3-
          <fpage>031</fpage>
          -26845-
          <issue>8</issue>
          _
          <fpage>1</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <article-title>GDPR-info.eu, "General Data Protection Regulation (GDPR</article-title>
          ),
          <year>" 2016</year>
          . [Online]. Available: https://gdpr-info.eu. [Accessed:
          <fpage>27</fpage>
          -Feb-2024].
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <surname>European</surname>
            <given-names>Commission</given-names>
          </string-name>
          ,
          <article-title>"A European strategy for data,"</article-title>
          <year>2023</year>
          . [Online]. Available: https://digital-strategy.ec.europa.eu/en/policies/strategy-data. [Accessed:
          <fpage>27</fpage>
          -
          <lpage>May2024</lpage>
          ].
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>European</surname>
            <given-names>Commission</given-names>
          </string-name>
          ,
          <article-title>"Europe's digital decade: digital targets for</article-title>
          <year>2030</year>
          ,"
          <year>2023</year>
          . [Online]. Available: https://commission.europa.eu/strategy-and
          <article-title>-policy/priorities2019-2024/europe-fit-digital-age/europes-digital-decade-digital-targets-2030_en</article-title>
          . [Accessed:
          <fpage>27</fpage>
          -May-2024].
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <surname>European</surname>
            <given-names>Commission,</given-names>
          </string-name>
          "Mobility Strategy,"
          <year>2024</year>
          . [Online]. Available: https://transport.ec.europa.eu/transport-themes/mobility-strategy_en. [Accessed:
          <fpage>14</fpage>
          -Mar-2024].
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>