Italy - Revision history

Admin: Admin moved page Draft:Italy to Italy

2024-09-25T12:39:27Z

← Older revision	Revision as of 14:39, 25 September 2024
(No difference)

Anonymous: changed namespace

2024-09-25T12:24:01Z

changed namespace

← Older revision		Revision as of 14:24, 25 September 2024
Line 1:		Line 1:
			{{DISPLAYTITLE:Country:Italy}}

	= Overview in the National Level =		= Overview in the National Level =
Line 137:		Line 138:
	=== Outcome ===		=== Outcome ===
	To be completed.		To be completed.

			{{DEFAULTSORT:Country:Italy}}

Anasfou: /* Bolzano, STA (Südtiroler Transportstrukturen) */

2024-09-25T08:17:34Z

Bolzano, STA (Südtiroler Transportstrukturen)

← Older revision		Revision as of 10:17, 25 September 2024
Line 128:		Line 128:

	STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format. Considering the complex modelling that is needed to represent the physical environment of public transport, the complete standards NeTEx and SIRI were decided as more suitable.		STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format. Considering the complex modelling that is needed to represent the physical environment of public transport, the complete standards NeTEx and SIRI were decided as more suitable.
	[[File:STA 3.png\|center\|thumb\|500x500px\|Challenges]]Based on the new architecture, NeTEx - SIRI, and other relevant standards, are implemented for the exchange of planned and real time data between back end systems (like operational planning tool ticketing system, travel planner and others. This architecture and the introduction of those standards is seen as the sustainable solution that can accommodate future developments on for example MaaS and integrated ticketing systems. In particular this arcitecture was chosen to support also "LinkingAlps", one of the EU projects in which it is developed a decentralised network of travel information services. This network will be created by interlinking existing regional or national journey planner services from all neighbour countries, with focus on multimodal transport (public transport, railways, new modes) through a standardised exchange service. In this context, the exchange of complete and interoperable datasets is key.		[[File:STA 3.png\|center\|thumb\|500x500px\|Challenges]]Based on the new architecture, NeTEx - SIRI, and other relevant standards, are implemented for the exchange of planned and real time data between back end systems (like operational planning tool ticketing system, travel planner and others. This architecture and the introduction of those standards is seen as the sustainable solution that can accommodate future developments on for example MaaS and integrated ticketing systems.
	[[File:SA 1.png\|center\|thumb\|731x731px]]		[[File:SA 1.png\|center\|thumb\|731x731px]]
	[[File:SA 2.png\|center\|thumb\|500x500px]]		[[File:SA 2.png\|center\|thumb\|500x500px]]

			=== Implementation ===
			In particular this architecture was chosen to support also "LinkingAlps", one of the EU projects in which it is developed a decentralised network of travel information services. This network will be created by interlinking existing regional or national journey planner services from all neighbour countries, with focus on multimodal transport (public transport, railways, new modes) through a standardised exchange service. In this context, the exchange of complete and interoperable datasets is key.

	=== Outcome ===		=== Outcome ===
	To be completed.		To be completed.

Anonymous at 11:15, 17 September 2024

2024-09-17T11:15:07Z

← Older revision		Revision as of 13:15, 17 September 2024
Line 9:		Line 9:
	The Italian NeTEx profile is structured in 5 levels, with the minimum objective of being able to have a protocol useful to transport of all the data categories required by the Del. Reg. 1926. It is currently used by stakeholders, few of them implemented the whole stack.		The Italian NeTEx profile is structured in 5 levels, with the minimum objective of being able to have a protocol useful to transport of all the data categories required by the Del. Reg. 1926. It is currently used by stakeholders, few of them implemented the whole stack.
	[[File:NeTEx Italian Profile.png\|center\|thumb\|''Italian NeTEx Profile structure'']]		[[File:NeTEx Italian Profile.png\|center\|thumb\|''Italian NeTEx Profile structure'']]



	==== Passenger Information Profile (Level 1) ====		==== Passenger Information Profile (Level 1) ====

Anasfou at 13:15, 3 September 2024

2024-09-03T13:15:44Z

← Older revision		Revision as of 15:15, 3 September 2024
Line 127:		Line 127:
	[[File:STA 1.jpg\|center\|thumb\|500x500px]]		[[File:STA 1.jpg\|center\|thumb\|500x500px]]
	[[File:STA 2.png\|center\|thumb\|500x500px]]		[[File:STA 2.png\|center\|thumb\|500x500px]]
	== System Architecture ==		=== System Architecture ===

	STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format. Considering the complex modelling that is needed to represent the physical environment of public transport, the complete standards NeTEx and SIRI were decided as more suitable.		STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format. Considering the complex modelling that is needed to represent the physical environment of public transport, the complete standards NeTEx and SIRI were decided as more suitable.
Line 134:		Line 134:
	[[File:SA 2.png\|center\|thumb\|500x500px]]		[[File:SA 2.png\|center\|thumb\|500x500px]]

	== Outcome ==		=== Outcome ===
	To be completed.		To be completed.

Anasfou at 13:14, 3 September 2024

2024-09-03T13:14:56Z

← Older revision		Revision as of 15:14, 3 September 2024
Line 117:		Line 117:
	Implementation of this technical architecture implies also formalization through the signature of specific MOU, of relationships and responsibilities concerning data gathering and exchange of all stakeholders: PTOs, PTAs, Agencies and System Integrators		Implementation of this technical architecture implies also formalization through the signature of specific MOU, of relationships and responsibilities concerning data gathering and exchange of all stakeholders: PTOs, PTAs, Agencies and System Integrators

	= Bolzano, STA (Südtiroler Transportstrukturen)=		= Use cases =

			== Bolzano, STA (Südtiroler Transportstrukturen)==

	STA (Südtiroler Transportstrukturen), is the in-house company working on behalf of the Public Transport Authority in Bolzano.		STA (Südtiroler Transportstrukturen), is the in-house company working on behalf of the Public Transport Authority in Bolzano.

Anasfou: /* System Architecture */

2024-09-03T13:09:38Z

System Architecture

← Older revision		Revision as of 15:09, 3 September 2024
Line 121:		Line 121:
	STA (Südtiroler Transportstrukturen), is the in-house company working on behalf of the Public Transport Authority in Bolzano.		STA (Südtiroler Transportstrukturen), is the in-house company working on behalf of the Public Transport Authority in Bolzano.

	STA is positioned in a unique location, is part of Italy but very close to Austria and the majority of the people speaks German. This means that the travel information STA offers (such as bus stop names) has to be multilingual. Therefore, there were ~~needed~~ a standard which allows ~~then~~ to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity.		STA is positioned in a unique location, is part of Italy but very close to Austria and the majority of the people speaks German. This means that the travel information STA offers (such as bus stop names) has to be multilingual. Therefore, there were needing a standard which allows them to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity.

	STA is in the process of innovating their IT architecture. They opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format.

	~~== System Architecture ==~~

	~~STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format.~~
	[[File:STA 1.jpg\|center\|thumb\|500x500px]]		[[File:STA 1.jpg\|center\|thumb\|500x500px]]
	[[File:STA 2.png\|center\|thumb\|500x500px]]		[[File:STA 2.png\|center\|thumb\|500x500px]]
	~~[[File:STA 3.png\|center\|thumb\|500x500px\|Challenges]]~~		== System Architecture ==

	~~=== System Architecture ===~~		STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format. Considering the complex modelling that is needed to represent the physical environment of public transport, the complete standards NeTEx and SIRI were decided as more suitable.
	STA opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format.		[[File:STA 3.png\|center\|thumb\|500x500px\|Challenges]]Based on the new architecture, NeTEx - SIRI, and other relevant standards, are implemented for the exchange of planned and real time data between back end systems (like operational planning tool ticketing system, travel planner and others. This architecture and the introduction of those standards is seen as the sustainable solution that can accommodate future developments on for example MaaS and integrated ticketing systems. In particular this arcitecture was chosen to support also "LinkingAlps", one of the EU projects in which it is developed a decentralised network of travel information services. This network will be created by interlinking existing regional or national journey planner services from all neighbour countries, with focus on multimodal transport (public transport, railways, new modes) through a standardised exchange service. In this context, the exchange of complete and interoperable datasets is key.
	[[File:SA 1.png\|center\|thumb\|~~500x500px~~]]		[[File:SA 1.png\|center\|thumb\|731x731px]]
	[[File:SA 2.png\|center\|thumb\|500x500px]]		[[File:SA 2.png\|center\|thumb\|500x500px]]

	~~=== Projects ===~~
	LinkingAlps is one of the EU projects in which they develop a decentralised network of travel information services. This network will be created by interlinking existing regional or national journey planner services from all neighbour countries, with focus on multimodal transport (public transport, railways, new modes) through a standardised exchange service.

	~~Also, for LinkingAlps, they chose to introduce standards that are ready for any future architecture and can accommodate future developments on for example MaaS and ticketing.~~

	== Outcome ==		== Outcome ==
			To be completed.

Anasfou: /* Bolzano, STA (Südtiroler Transportstrukturen) */

2024-09-03T12:45:02Z

Bolzano, STA (Südtiroler Transportstrukturen)

← Older revision		Revision as of 14:45, 3 September 2024
Line 119:		Line 119:
	= Bolzano, STA (Südtiroler Transportstrukturen)=		= Bolzano, STA (Südtiroler Transportstrukturen)=

	STA (Südtiroler Transportstrukturen), the in-house company working on behalf of the Public Transport Authority in Bolzano.		STA (Südtiroler Transportstrukturen), is the in-house company working on behalf of the Public Transport Authority in Bolzano.

	STA is positioned in a unique location, is part of Italy but very close to Austria and the majority of the people speaks German. This means that the travel information STA offers (such as bus stop names) has to be multilingual. Therefore, there were needed a standard which allows then to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity.		STA is positioned in a unique location, is part of Italy but very close to Austria and the majority of the people speaks German. This means that the travel information STA offers (such as bus stop names) has to be multilingual. Therefore, there were needed a standard which allows then to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity.

Anasfou: /* Short presentation of STA */

2024-09-03T12:44:42Z

Short presentation of STA

← Older revision		Revision as of 14:44, 3 September 2024
Line 119:		Line 119:
	= Bolzano, STA (Südtiroler Transportstrukturen)=		= Bolzano, STA (Südtiroler Transportstrukturen)=

	~~=== Short presentation of STA ===~~
	STA (Südtiroler Transportstrukturen), the in-house company working on behalf of the Public Transport Authority in Bolzano.		STA (Südtiroler Transportstrukturen), the in-house company working on behalf of the Public Transport Authority in Bolzano.

	STA is positioned in a unique location, is part of Italy but very close to Austria and the majority of the people speaks German. This means that the travel information STA offers (such as bus stop names) has to be multilingual. Therefore, there were needed a standard which allows then to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity.		STA is positioned in a unique location, is part of Italy but very close to Austria and the majority of the people speaks German. This means that the travel information STA offers (such as bus stop names) has to be multilingual. Therefore, there were needed a standard which allows then to exchange this kind of information considering the multilingual data. NeTEx provided this opportunity.

	STA is in the process of innovating their IT architecture. They opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format.		STA is in the process of innovating their IT architecture. They opted to implement NeTEx and SIRI ‘natively’, meaning there is no conversion between the production of the data and NeTEx data files from another exchange data format.

	== System Architecture ==		== System Architecture ==

Anasfou: /* Overview in the National Level */

2024-09-03T12:43:44Z

Overview in the National Level

← Older revision		Revision as of 14:43, 3 September 2024
Line 12:		Line 12:


	Passenger Information Profile (Level 1)		==== Passenger Information Profile (Level 1) ====

	For the level 1 of the Italian NeTEx Profile, European Passenger Information Profile (EPIP) has been adopted as defined in the CEN Technical Specification CEN/TS 16614-4:2021.		For the level 1 of the Italian NeTEx Profile, European Passenger Information Profile (EPIP) has been adopted as defined in the CEN Technical Specification CEN/TS 16614-4:2021.