<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Implementation Framework for Hyperloop Decision-Making Ecosystem</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Aleksejs</forename><surname>Vesjolijs</surname></persName>
							<email>vesjolijs.a@tsi.lv</email>
							<affiliation key="aff0">
								<orgName type="department">Transport and Telecommunication Institute</orgName>
								<address>
									<addrLine>Lauvas 2</addrLine>
									<postCode>LV-1019</postCode>
									<settlement>Riga</settlement>
									<country key="LV">Latvia</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Accenture</orgName>
								<address>
									<addrLine>1 Grand Canal Square</addrLine>
									<postCode>D04 EE70</postCode>
									<settlement>Dublin</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Implementation Framework for Hyperloop Decision-Making Ecosystem</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">0646C24EA7B10A621EC19F1B310295F2</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T16:53+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Hyperloop</term>
					<term>software ecosystem</term>
					<term>data engineering</term>
					<term>dataops</term>
					<term>decision-making</term>
					<term>digital transformation 1</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><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></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><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) <ref type="bibr" target="#b0">[1]</ref>. Technology initially is envisioned as ultra-high speed transportation mode which is able to transfer passengers and cargo on supersonic speed overcoming Kantrowitz limit <ref type="bibr" target="#b1">[2]</ref>. 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 <ref type="bibr" target="#b2">[3]</ref>.</p><p>The technology is currently at a low maturity level from engineering, operational, and cost perspectives <ref type="bibr" target="#b3">[4]</ref>. 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. Q1. What are the key components necessary for developing and deploying a digital decision-making ecosystem specifically designed for Hyperloop technology projects?</p><p>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. 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. O5. Conduct framework approbation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Research Methodology</head><p>The research methodology for the development of implementation framework for Hyperloop decision-making ecosystem is shown in Figure <ref type="figure" target="#fig_0">1</ref>. The state-of-the-art contains a problem definition, literature analysis to define research gap, ecosystem definition. 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">State-of-the-Art</head><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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Problem Definition</head><p>Due to technology complexity <ref type="bibr" target="#b2">[3]</ref>, dynamic nature of Hyperloop project <ref type="bibr" target="#b4">[5]</ref>, challenged decisions <ref type="bibr" target="#b5">[6]</ref>, the Hyperloop is still in TRL 5 according to Horizon 2020 standards <ref type="bibr" target="#b7">[7]</ref>. 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 <ref type="bibr" target="#b8">[8]</ref>. 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Hyperloop Decision-Making Ecosystem</head><p>To address the research gap, the study proposes the concept of the Hyperloop Decision-Making 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. 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Design</head><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 Extract-Transform-Load approach <ref type="bibr" target="#b9">[9]</ref>, enhanced with Generative AI (GenAI), namely Extract-Generate-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 <ref type="figure" target="#fig_3">3</ref> 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 <ref type="figure" target="#fig_2">2</ref>).  <ref type="table" target="#tab_0">1</ref>. 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Implementation Framework</head><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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Vensim</head><p>System modelling core that will be used for visualization in COM22.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>COM22 Dashboard visualization</head><p>Power BI Creates interactive dashboards for data analysis and reporting.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1.">Framework Overview</head><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 <ref type="table">2</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 2</head><p>Software development methods adopted in the framework</p><p>The framework is presented in Figure <ref type="figure" target="#fig_4">4</ref>. 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) <ref type="bibr" target="#b17">[17]</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Method</head><p>Features selected for framework Source DevOps Continuous integration/deployment, automated testing, collaboration.</p><p>[10]</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Lean</head><p>Value stream mapping, continuous improvement.</p><p>[11] DataOps Collaboration, rapid data delivery, integration, automation.</p><p>[12] RAD Prototyping, user feedback, iterative.</p><p>[13] PRINCE2</p><p>Roles-responsibility model, control, stage-based process.</p><p>[14] Data mesh Data as a product, decentralized data ownership, federal computational governance.</p><p>[15]</p><p>Six Sigma Data-driven approach, control, quality improvement. <ref type="bibr" target="#b16">[16]</ref> 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 <ref type="figure" target="#fig_3">3, COM7-9</ref>).</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 <ref type="table" target="#tab_0">1</ref>) 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 <ref type="bibr" target="#b18">[18]</ref>. Therefore, each component of ecosystem must answer regional data protection policies, such as General Data Protection Regulation (GDPR) <ref type="bibr" target="#b19">[19]</ref> in EU and incorporate best software development practices in mitigating cybersecurity risks. Further, pursuit to comply with European strategy for data <ref type="bibr" target="#b20">[20]</ref> principles must be considered as summarized in Figure <ref type="figure" target="#fig_5">5</ref>. 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2.">Framework Approbation</head><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). 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 <ref type="figure" target="#fig_6">6</ref>, 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Conclusions</head><p>The research goal is completed by proposing a framework (Figure <ref type="figure" target="#fig_4">4</ref>) for implementing a digital decision-making ecosystem designed specifically for Hyperloop projects (Figure <ref type="figure" target="#fig_3">3</ref>). The framework integrates ETL process enhanced with Generative AI envisioned in solution components (COM1-COM22, Table <ref type="table" target="#tab_0">1</ref>). Structured technical solution blueprint is based on FBD (Figure <ref type="figure" target="#fig_2">2</ref>) 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 <ref type="table">2</ref>) and can be adopted to other digital systems with similar parameters. The approbation is conducted using unit tests on synthetic data (Figure <ref type="figure" target="#fig_6">6</ref>), 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 <ref type="bibr">[21]</ref> by enabling digital transformation of businesses and European strategy for data <ref type="bibr" target="#b20">[20]</ref>. 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. 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 <ref type="bibr" target="#b22">[22]</ref>.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Research methodology overview.</figDesc><graphic coords="2,96.23,607.97,402.55,75.14" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>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).</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Hyperloop decision-making ecosystem functional block diagram.</figDesc><graphic coords="4,86.38,284.46,422.16,221.90" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Hyperloop decision-making ecosystem technical solution blueprint. Data load stages are presented in green colour and component codes are highlighted in blue colour.</figDesc><graphic coords="5,85.05,156.79,425.35,236.25" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Hyperloop decision-making ecosystem implementation framework.</figDesc><graphic coords="7,88.65,503.85,417.70,179.84" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: European strategy of data for Hyperloop decision-making ecosystem [20].</figDesc><graphic coords="8,88.08,369.58,418.85,65.25" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Figure 6 :</head><label>6</label><figDesc>Figure 6: Implementation framework validation using unit testing strategy and results.</figDesc><graphic coords="9,87.50,85.05,419.95,78.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc>Hyperloop decision-making ecosystem components</figDesc><table><row><cell>Component</cell><cell>Name</cell><cell cols="3">Technology Description</cell><cell></cell><cell></cell><cell></cell></row><row><cell>COM1</cell><cell cols="6">Data extraction ChatGPT 4 Extracts from GenAI knowledge base.</cell><cell></cell></row><row><cell>COM2</cell><cell>API connector</cell><cell>Python</cell><cell cols="5">Connects to external APIs to fetch data</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="5">directly into the system from various</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="3">Internet of Things devices.</cell><cell></cell><cell></cell></row><row><cell>COM3</cell><cell>Web crawler</cell><cell>Python</cell><cell cols="5">Gathers data from various online sources</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="4">to be processed and analysed.</cell><cell></cell></row><row><cell>COM4</cell><cell>External data</cell><cell cols="6">PostgreSQL External data collected from various</cell></row><row><cell></cell><cell>source</cell><cell></cell><cell cols="3">sources for processing.</cell><cell></cell><cell></cell></row><row><cell>COM5</cell><cell>Data transfer</cell><cell cols="6">Snowflake Transfers extracted data into Snowflake</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="4">for centralized data handling.</cell><cell></cell></row><row><cell>COM6</cell><cell cols="6">Database backup Snowflake Provides backup services for data.</cell><cell></cell></row><row><cell>COM7</cell><cell cols="7">Data enrichment ChatGPT 4 Enhances data quality by adding missing</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="4">information or correcting errors.</cell><cell></cell></row><row><cell>COM8</cell><cell>Synthetic data</cell><cell>Python</cell><cell cols="5">Generates artificial data based on</cell></row><row><cell></cell><cell>generation</cell><cell></cell><cell cols="4">patterns learned from real data.</cell><cell></cell></row><row><cell>COM9</cell><cell>Data cleanup</cell><cell cols="6">ChatGPT 4 Cleans and prepares data for analysis,</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="4">removing errors and inconsistencies.</cell><cell></cell></row><row><cell>COM10</cell><cell>Python</cell><cell>Python</cell><cell cols="5">Application built in Python to process</cell></row><row><cell></cell><cell>application</cell><cell></cell><cell cols="3">and handle data operations.</cell><cell></cell><cell></cell></row><row><cell>COM11</cell><cell>Data transfer</cell><cell>Python</cell><cell cols="5">Facilitates the movement of processed</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="4">data to different parts of the system.</cell><cell></cell></row><row><cell>COM12</cell><cell>Data analytics</cell><cell cols="6">Snowflake Component that analyses big data,</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="5">applies machine learning and advanced</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="2">analytics</cell><cell></cell><cell></cell><cell></cell></row><row><cell>COM13</cell><cell>Data processing,</cell><cell cols="6">Snowflake Processes and further transforms data</cell></row><row><cell></cell><cell>transformations</cell><cell></cell><cell cols="3">applying business logic.</cell><cell></cell><cell></cell></row><row><cell>COM14</cell><cell cols="6">Database backup Snowflake Provides backup services for data.</cell><cell></cell></row><row><cell>COM15</cell><cell cols="7">Simulation data ChatGPT 4 Uses advanced models to simulate data</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="4">scenarios for further analysis.</cell><cell></cell></row><row><cell>COM16</cell><cell cols="4">Database backup Snowflake Snowflake</cell><cell>database</cell><cell cols="2">containing</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="5">production data gathered in all previous</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="2">steps.</cell><cell></cell><cell></cell><cell></cell></row><row><cell>COM17</cell><cell cols="7">API enrichment ChatGPT 4 Uses APIs to enrich data with additional</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="3">external insights.</cell><cell></cell><cell></cell></row><row><cell>COM18</cell><cell cols="7">Data enrichment ChatGPT 4 Further enriches data post-transfer with</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="4">additional context and information.</cell><cell></cell></row><row><cell>COM19</cell><cell cols="6">Database backup Snowflake Provides backup services for data.</cell><cell></cell></row><row><cell>COM20</cell><cell>Application</cell><cell>Streamlit</cell><cell>A</cell><cell>bridge</cell><cell>between</cell><cell>data</cell><cell>and</cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="2">visualizations.</cell><cell></cell><cell></cell><cell></cell></row><row><cell>COM21</cell><cell>System</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell>modelling</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgements</head><p>Research supervisor -Professor Dr.Sc.Ing Mihails Savrasovs, Transport and Telecommunication Institute.</p></div>
			</div>

			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>A. Online Resources</head><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></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Hyperloop Alpha</title>
		<author>
			<persName><forename type="first">E</forename><surname>Musk</surname></persName>
		</author>
		<ptr target="https://www.tesla.com/sites/default/files/blog_images/hyperloop-alpha.pdf" />
		<imprint>
			<date type="published" when="2013-01">2013. 01-Mar-2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Aerodynamic study of a Hyperloop pod equipped with compressor to overcome the Kantrowitz limit</title>
		<author>
			<persName><forename type="first">M</forename><surname>Bizzozero</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Sato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Sayed</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.jweia.2021.104784</idno>
		<ptr target="https://doi.org/10.1016/j.jweia.2021.104784" />
	</analytic>
	<monogr>
		<title level="j">Journal of Wind Engineering and Industrial Aerodynamics</title>
		<imprint>
			<biblScope unit="volume">218</biblScope>
			<biblScope unit="page">104784</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Prospects and Challenges of the Hyperloop Transportation System: A Systematic Technology Review</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">K</forename><surname>Noland</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACCESS.2021.3057788</idno>
		<ptr target="https://doi.org/10.1109/ACCESS.2021.3057788" />
	</analytic>
	<monogr>
		<title level="j">IEEE Access</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="page" from="28439" to="28458" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Hyperloop Concept Technological and Operational Review: The Potential to Fill Rail Niche Markets</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">C</forename><surname>Barbosa</surname></persName>
		</author>
		<idno type="DOI">10.1115/JRC2020-8033</idno>
		<ptr target="https://doi.org/10.1115/JRC2020-8033" />
	</analytic>
	<monogr>
		<title level="m">2020 Joint Rail Conference</title>
				<meeting><address><addrLine>St. Louis, Missouri, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="page" from="V001T" to="3A" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Elon Musk abandons Hyperloop project months after ramping up testing</title>
		<author>
			<persName><forename type="first">M</forename><surname>Turner</surname></persName>
		</author>
		<ptr target="https://www.cityam.com/elon-musk-abandons-hyperloop-project-months-after-ramping-up-testing/" />
		<imprint>
			<date type="published" when="2022-12">2022. 12-May-2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Hyperloop One to Shut Down After Failing to Reinvent Transit</title>
		<author>
			<persName><surname>Bloomberg</surname></persName>
		</author>
		<ptr target="https://www.bloomberg.com/news/articles/2023-12-" />
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">/hyperloop-one-to-shut-down-after-raising-millions-to-reinvent-transit</title>
		<imprint>
			<date type="published" when="2024-01">-Jan-2024</date>
			<biblScope unit="page">28</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<ptr target="https://ec.europa.eu/research/participants/data/ref/h2020/wp/2014_2015/annexes/h2020-wp1415-annex-g-trl_en.pdf" />
		<title level="m">Technology Readiness Levels (TRL)</title>
				<imprint>
			<publisher>European Commission</publisher>
			<date type="published" when="2014-12">2014. 12-May-2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Overview of Factors and Methods for Analysis of Hyperloop Project</title>
		<author>
			<persName><forename type="first">A</forename><surname>Vesjolijs</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-031-53598-7_25</idno>
		<ptr target="https://doi.org/10.1007/978-3-031-53598-7_25" />
	</analytic>
	<monogr>
		<title level="m">Reliability and Statistics in Transportation and Communication</title>
				<editor>
			<persName><forename type="first">I</forename><surname>Kabashkin</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">I</forename><surname>Yatskiv</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">O</forename><surname>Prentkovskis</surname></persName>
		</editor>
		<meeting><address><addrLine>Switzerland; Cham</addrLine></address></meeting>
		<imprint>
			<publisher>Springer Nature</publisher>
			<date type="published" when="2024">2024</date>
			<biblScope unit="page" from="281" to="291" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Conceptual modeling for ETL processes</title>
		<author>
			<persName><forename type="first">P</forename><surname>Vassiliadis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Simitsis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Skiadopoulos</surname></persName>
		</author>
		<idno type="DOI">10.1145/583890.583893</idno>
		<ptr target="https://doi.org/10.1145/583890.583893" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 5th ACM International Workshop on Data Warehousing and OLAP</title>
				<meeting>the 5th ACM International Workshop on Data Warehousing and OLAP</meeting>
		<imprint>
			<date type="published" when="2002">2002</date>
			<biblScope unit="page" from="14" to="21" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">Leading DevOps Practice and Principle Adoption</title>
		<author>
			<persName><forename type="first">K</forename><surname>Maroukian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">R</forename><surname>Gulliver</surname></persName>
		</author>
		<idno type="DOI">10.48550/ARXIV.2008.10515</idno>
		<ptr target="https://doi.org/10.48550/ARXIV.2008.10515" />
		<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Lean Software Development</title>
		<author>
			<persName><forename type="first">M</forename><surname>Poppendieck</surname></persName>
		</author>
		<idno type="DOI">10.1109/ICSECOMPANION.2007.46</idno>
		<ptr target="https://doi.org/10.1109/ICSECOMPANION.2007.46" />
	</analytic>
	<monogr>
		<title level="m">29th International Conference on Software Engineering (ICSE&apos;07 Companion)</title>
				<meeting><address><addrLine>MN, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="165" to="166" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Good practices for the adoption of DataOps in the software industry</title>
		<author>
			<persName><forename type="first">M</forename><surname>Rodriguez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">J P</forename><surname>De Araújo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Mazzara</surname></persName>
		</author>
		<idno type="DOI">10.1088/1742-6596/1694/1/012032</idno>
		<ptr target="https://doi.org/10.1088/1742-6596/1694/1/012032" />
	</analytic>
	<monogr>
		<title level="j">J. Phys.: Conf. Ser</title>
		<imprint>
			<biblScope unit="volume">1694</biblScope>
			<biblScope unit="page">12032</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Rapid application development (RAD): an empirical review</title>
		<author>
			<persName><forename type="first">P</forename><surname>Beynon-Davies</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Carne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Mackay</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Tudhope</surname></persName>
		</author>
		<idno type="DOI">10.1057/palgrave.ejis.3000325</idno>
		<ptr target="https://doi.org/10.1057/palgrave.ejis.3000325" />
	</analytic>
	<monogr>
		<title level="j">European Journal of Information Systems</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="page" from="211" to="223" />
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Managing a software development project complying with PRINCE2 standard</title>
		<author>
			<persName><forename type="first">S.-D</forename><surname>Axinte</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Petrica</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I.-D</forename><surname>Barbu</surname></persName>
		</author>
		<idno type="DOI">10.1109/ECAI.2017.8166435</idno>
		<ptr target="https://doi.org/10.1109/ECAI.2017.8166435" />
	</analytic>
	<monogr>
		<title level="m">2017 9th International Conference on Electronics, Computers and Artificial Intelligence (ECAI), IEEE</title>
				<meeting><address><addrLine>Targoviste</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="1" to="6" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Data Mesh: Concepts and Principles of a Paradigm Shift in Data Architectures</title>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">A</forename><surname>Machado</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Costa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">Y</forename><surname>Santos</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.procs.2021.12.013</idno>
		<ptr target="https://doi.org/10.1016/j.procs.2021.12.013" />
	</analytic>
	<monogr>
		<title level="j">Procedia Computer Science</title>
		<imprint>
			<biblScope unit="volume">196</biblScope>
			<biblScope unit="page" from="263" to="271" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Benefits, obstacles, and future of six sigma approach</title>
		<author>
			<persName><forename type="first">Y</forename><forename type="middle">H</forename><surname>Kwak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">T</forename><surname>Anbari</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.technovation.2004.10.003</idno>
		<ptr target="https://doi.org/10.1016/j.technovation.2004.10.003" />
	</analytic>
	<monogr>
		<title level="j">Technovation</title>
		<imprint>
			<biblScope unit="volume">26</biblScope>
			<biblScope unit="page" from="708" to="715" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">The maturity of maturity model research: A systematic mapping study</title>
		<author>
			<persName><forename type="first">R</forename><surname>Wendler</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.infsof.2012.07.007</idno>
		<ptr target="https://doi.org/10.1016/j.infsof.2012.07.007" />
	</analytic>
	<monogr>
		<title level="j">Information and Software Technology</title>
		<imprint>
			<biblScope unit="volume">54</biblScope>
			<biblScope unit="page" from="1317" to="1339" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Cybersecurity in Digital Transformation</title>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">P F</forename><surname>Möller</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-031-26845-8_1</idno>
		<ptr target="https://doi.org/10.1007/978-3-031-26845-8_1" />
	</analytic>
	<monogr>
		<title level="j">Advances in Information Security</title>
		<imprint>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="page" from="1" to="70" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<author>
			<persName><surname>Gdpr-Info</surname></persName>
		</author>
		<ptr target="https://gdpr-info.eu" />
		<title level="m">General Data Protection Regulation (GDPR)</title>
				<imprint>
			<date type="published" when="2016-02-27">2016. 27-Feb-2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<monogr>
		<title level="m" type="main">A European strategy for data</title>
		<ptr target="https://digital-strategy.ec.europa.eu/en/policies/strategy-data" />
		<imprint>
			<date type="published" when="2023-05-27">2023. 27-May-2024</date>
			<publisher>European Commission</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<monogr>
		<title level="m" type="main">Europe&apos;s digital decade: digital targets for 2030</title>
		<ptr target="https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/europes-digital-decade-digital-targets-2030_en" />
		<imprint>
			<date type="published" when="2023-05-27">2023. 27-May-2024</date>
		</imprint>
		<respStmt>
			<orgName>European Commission</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<monogr>
		<ptr target="https://transport.ec.europa.eu/transport-themes/mobility-strategy_en" />
		<title level="m">Mobility Strategy</title>
				<imprint>
			<publisher>European Commission</publisher>
			<date type="published" when="2024-03-14">2024. 14-Mar-2024</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
