Hyperloop Systems Aspects - Reference Architecture

This work item specifies the reference architecture for a hyperloop system. It will specify the functions of each (sub)system to define the purpose of each block, its different possible implementations, and will highlight how the (sub)systems support each other.
The interfaces of the transportation system will be listed, whether it be internal interfaces or exterior interfaces. The characterization considers the technical as well as operational features of the transport service.

Hyperloop-Systemaspekte - Referenzbauweise

Dieses Dokument legt die Referenzarchitektur für ein Hyperloop-System fest. Es legt die Funktionen jedes (Teil-)Systems fest, um den Zweck jedes Blocks und dessen verschiedene mögliche Implementierungen zu defi
nieren, und zeigt auf, wie sich die (Teil-)Systeme gegenseitig unterstützen.
Die Schnittstellen des Transportsystems werden aufgelistet, seien es interne oder externe Schnittstellen. Die Charakterisierung berücksichtigt sowohl die technischen als auch die betrieblichen Merkmale der Transport
dienstleistung.

Aspects des systèmes Hyperloop - Architecture de référence

Le présent document spécifie l’architecture de référence pour un système Hyperloop. Il spécifie les fonctions de chaque (sous-)système pour définir l’objectif de chaque bloc, ses différentes mises en oeuvre possibles, et met en évidence la manière dont les (sous-)systèmes se soutiennent mutuellement.
Les interfaces du système de transport sont énumérées, qu’il s’agisse d’interfaces intérieures ou extérieures. La caractérisation tient compte des caractéristiques techniques, mais également opérationnelles, du service de transport.

Vidiki sistemov Hyperloop - Referenčna arhitektura

General Information

Status
Not Published
Public Enquiry End Date
22-Feb-2023
Technical Committee
Current Stage
4020 - Public enquire (PE) (Adopted Project)
Start Date
08-Dec-2022
Due Date
27-Apr-2023
Completion Date
19-Apr-2023

Buy Standard

Draft
prEN 17930:2023
English language
16 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
oSIST prEN 17930:2023
01-februar-2023
Vidiki sistemov Hyperloop - Referenčna arhitektura
Hyperloop Systems Aspects - Reference Architecture
Hyperloop-Systemaspekte - Referenzbauweise
Aspects des systèmes Hyperloop - Architecture de référence
Ta slovenski standard je istoveten z: prEN 17930
ICS:
03.220.99 Druge oblike transporta Other forms of transport
55.020 Pakiranje in distribucija blaga Packaging and distribution of
na splošno goods in general
oSIST prEN 17930:2023 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN 17930:2023

---------------------- Page: 2 ----------------------
oSIST prEN 17930:2023


EUROPEAN STANDARD DRAFT
prEN 17930
NORME EUROPÉENNE

EUROPÄISCHE NORM

December 2022
ICS 03.220.99; 55.020

English version

Hyperloop Systems Aspects - Reference Architecture
Aspects des systèmes Hyperloop - Architecture de Hyperloop-Systemaspekte - Referenzbauweise
référence
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/CLC/JTC 20.

If this draft becomes a European Standard, CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal
Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any
alteration.

This draft European Standard was established by CEN and CENELEC in three official versions (English, French, German). A
version in any other language made by translation under the responsibility of a CEN and CENELEC member into its own language
and notified to the CEN-CENELEC Management Centre has the same status as the official versions.

CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and United Kingdom.

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.Recipients of this draft are invited to submit, with their comments, notification
of any relevant patent rights of which they are aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
















CEN-CENELEC Management Centre:
Rue de la Science 23, B-1040 Brussels
© 2022 CEN/CENELEC All rights of exploitation in any form and by any means
Ref. No. prEN 17930:2022 E
reserved worldwide for CEN national Members and for
CENELEC Members.

---------------------- Page: 3 ----------------------
oSIST prEN 17930:2023
prEN 17930:2022 (E)
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Hyperloop system . 6
5 Methodology . 6
6 Key hyperloop system functions . 6
7 Reference architecture - Building Blocks. 7
8 Functions related to the infrastructure . 10
8.1 Infrastructure structure and enclosure (F1) . 10
8.2 Low-Pressure Environment Control (F2) . 10
8.3 Station, hub and related infrastructure (F3) . 10
8.4 Infrastructure Maintenance (F4) . 11
9 Functions related to the Vehicle . 11
9.1 Vehicle structure and body/fuselage (F5) . 11
9.2 Vehicle Internal Environment (F6) . 11
9.3 Vehicle Maintenance and Storage (F7) . 11
10 Functions relative to the Operating system . 12
10.1 Longitudinal forcing between vehicle and infrastructure (F8) . 12
10.2 Transverse forcing between vehicle and infrastructure (F9) . 12
10.3 Energy Management (F10) . 12
10.4 Command, Control, Communication and Signalling (F11) . 13
10.5 Emergency prevention and evacuation management (F12) . 13
11 Functions related to multiple systems - Introduction of the interfaces. 14
11.1 Context . 14
Annex A (informative) Characterization of the interfaces . 15
Annex B (informative) Classification of the interfaces . 16

2

---------------------- Page: 4 ----------------------
oSIST prEN 17930:2023
prEN 17930:2022 (E)
European foreword
This document (prEN 17930:2022) has been prepared by Technical Committee CEN-CLC/JTC 20
“Hyperloop system”, the secretariat of which is held by NEN.
This document is submitted to the CEN Enquiry.
3
Interne

---------------------- Page: 5 ----------------------
oSIST prEN 17930:2023
prEN 17930:2022 (E)
Introduction
This document defines the reference architecture of the hyperloop system, its subsystems and interfaces.
The main purpose is to develop an architecture for this novel mode of transportation that can be used by
any parties participating in the development of the different aspects of a hyperloop system.
4

---------------------- Page: 6 ----------------------
oSIST prEN 17930:2023
prEN 17930:2022 (E)
1 Scope
This document specifies the reference architecture for a hyperloop system. It specifies the functions of
each (sub)system to define the purpose of each block, its different possible implementations, and
highlights how the (sub)systems support each other.
The interfaces of the transportation system are listed, whether it be internal interfaces or exterior
interfaces. The characterization considers the technical as well as operational features of the transport
service.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp/
— IEC Electropedia: available at https://www.electropedia.org/
3.1
hyperloop system
mode of land transportation capable of high speed and driverless operations, in which a vehicle is guided
through a low-pressure tube or system of tubes, for passengers and/or cargo
3.2
payload
total mass of the passengers, luggage and goods
[SOURCE: IEC 60050, definition 811-03-05, modified – “in the train” deleted]
3.3
internal environment within the vehicle
Environment within the vehicle accommodating the passengers and cargo which could include, but is not
limited to, air pressure, air quality, temperature, gas composition and humidity
3.4
internal environment within the tube
Environment within the tube accommodating the vehicle travels which could include, but is not limited
to, air pressure
3.5
interface
shared boundary between two functional units, defined by various characteristics pertaining to the
functions, physical interconnections, signal exchanges, and other characteristics of the units, as
appropriate
[SOURCE: ISO/IEC 2382:2015]
5
Interne

---------------------- Page: 7 ----------------------
oSIST prEN 17930:2023
prEN 17930:2022 (E)
4 Hyperloop system
The hyperloop is an electrically powered mode of land transportation with vehicles travelling through a
network of low-pressure tubes, capable of high-speed and driverless operations, offering continuous
service for transporting passengers and cargo towards their destinations.
The hyperloop system uses electro-magnetic forces for levitation, guidance and propulsion. Magnetic
levitation is one the key features of the hyperloop system. This eliminates the direct contact between the
moving and static parts of the system. The pressurized hyperloop vehicles operate inside a low-pressure
tube. The low-pressure environment reduces both air resistance and energy consumption. The body of
the tube lowers noise emissions towards the direct environment.
The hyperloop linear infrastructure enables controlled traffic flow of vehicles through a low-pressure
tube or system of tubes that are either elevated on columns above the ground, at ground level, or go
underground/underwater. The spatial constraints need to be taken into account when designing the
hyperloop transport service.
5 Methodology
The reference architecture of the hyperloop system can be determined in various ways depending on the
perspective taken. It can be defined in terms of physical elements of the final system as well as in terms
of functions to be performed by the hyperloop system.
In this document a systems engineering methodology is used relying on the functional breakdown of the
system. Through this methodology, a high-level architecture is defined. The high-level systems
architecture provides a frame of reference for the functional view of the main functional blocks and
associated functions of the hyperloop.
This architecture represents the topology of the hyperloop high level functional blocks at the system level
and the hyperloop functional blocks at the sub-system level. For each of the functional blocks, a set of key
functions is identified. When applicable and necessary, these key functions are associated with physical
parts of the hyperloop system.
Each of the functional blocks has several interactions with a set of other functional blocks. These
interactions are identified as interfaces.
The description of the hyperloop system through the high-level systems architecture relying on the
functions allows for various implementations, while still providing clear guidelines to the hyperloop
product developers.
6 Key hyperloop system functions
The main function of the hyperloop system is to transfer passengers and cargo in a low-pressure tube or
system of tubes through on driverless vehicles.
Subsequently, in order to achieve this functionality, the hyperloop system will have to provide the
following subsequent functions:
— To provide a pressure-controlled pathway for vehicles connecting multiple locations
— To handle cargo loading/unloading and passengers boarding/disembarking
— To move and position the vehicle within the infrastructure
— To coordinate the vehicles and infrastructure operations
— To transport passengers and/or cargo in a pressurized environment
— To ensure system availability, safety, reliability and maintainability
6

---------------------- Page: 8 ----------------------
oSIST prEN 17930:2023
prEN 17930:2022 (E)
These high-level functions are grouped into three high level functional blocks namely: the infrastructure,
the operating system and the vehicle.
— Infrastructure
— To provide a pressure-controlled pathway for vehicles connecting multiple locations
— To handle cargo loading/unloading and passengers boarding/disembarking
— Operating system
— To move and position the vehicle within the infrastructure
— To coordinate the vehicles and infrastructure operations
— Vehicle
— To transport passengers and/or cargo in a pressurized environment
The choice for the three high level functional blocks is made in order to reflect and provide the
relationship to the main physical entities of the hyperloop: Infrastructure, Operating System and Vehicle.
The presentation of the high-level functional blocks is depicted in a topological view of the Figure 1.

Figure 1 — High level functional block of the Hyperloop System
7 Reference architecture - Building Blocks
The reference architecture is structured as a multi tiers approach including 3 levels:
— tier 1: High level functional blocks
— tier 2: Functional blocks
— tier 3: Functions
The tier 1 is composed of the high-level functional blocks as depicted in Figure 2. This functional
structure, implementation independent, is organized further into functional blocks at tier 2 level, as
shown in Figure 2. The functional blocks are each specified by a set of different functions at tier 3 level.
7
Interne

---------------------- Page: 9 ----------------------
oSIST prEN 17930:2023
prEN 17930:2022 (E)

Figure 2 — Hyperloop system’s functional structure
The generic description of the functional blocks of the hyperloop system (tier 2) is summarized below.
a) Infrastructure
— F1 -
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.