FAQ Transmodel - Revision history

Admin: /* Is it modeled right? */

2023-02-10T12:51:48Z

Is it modeled right?

← Older revision		Revision as of 14:51, 10 February 2023
Line 68:		Line 68:

	====Is it modeled right?====		====Is it modeled right?====
	[[File:SERVICE_PATTERN_1.png\|alt=]]		[[File:SERVICE_PATTERN_1.png\|alt=\|border]]

	====POINT IN SERVICE PATTERN can also be each intermediate point, which is not a VEHICLE MEETING POINT. It is not 2 but an infinite amount of those in the SINGLE JOURNEY according to the diagram. ====		====POINT IN SERVICE PATTERN can also be each intermediate point, which is not a VEHICLE MEETING POINT. It is not 2 but an infinite amount of those in the SINGLE JOURNEY according to the diagram. ====

Admin: /* Is it modeled right? */

2023-02-10T12:45:13Z

Is it modeled right?

← Older revision		Revision as of 14:45, 10 February 2023
Line 62:		Line 62:

	[[File:NM_Vehicle_Meeting_Point.png\|alt=\|border]]		[[File:NM_Vehicle_Meeting_Point.png\|alt=\|border]]






	The functional similarity of the VEHICLE MEETING LINK with a SERVICE LINK for a CONVENTIONAL MODE OF OPERATION means: '''it is a link along which no pick-up/drop-off operation can take place.'''		The functional similarity of the VEHICLE MEETING LINK with a SERVICE LINK for a CONVENTIONAL MODE OF OPERATION means: '''it is a link along which no pick-up/drop-off operation can take place.'''
Line 73:		Line 68:

	====Is it modeled right?====		====Is it modeled right?====
			[[File:SERVICE_PATTERN_1.png\|alt=]]

	POINT IN SERVICE PATTERN can also be each intermediate point, which is not a VEHICLE MEETING POINT. It is not 2 but an infinite amount of those in the SINGLE JOURNEY according to the diagram.		====POINT IN SERVICE PATTERN can also be each intermediate point, which is not a VEHICLE MEETING POINT. It is not 2 but an infinite amount of those in the SINGLE JOURNEY according to the diagram. ====
	~~[[File:SERVICE_PATTERN_1.png\|alt~~=]]

	SINGLE JOURNEY PATH is an ordered list of '''VEHICLE MEETING POINTs''' on a single ROUTE, describing the pattern of working for an ALTERNATIVE MODE service.		SINGLE JOURNEY PATH is an ordered list of '''VEHICLE MEETING POINTs''' on a single ROUTE, describing the pattern of working for an ALTERNATIVE MODE service.

Admin: /* Equipment */

2023-02-08T00:11:09Z

Equipment

← Older revision		Revision as of 02:11, 8 February 2023
Line 141:		Line 141:
	== Equipment ==		== Equipment ==

	==== VEHICLE CHARGING EQUIPMENT ====		=== VEHICLE CHARGING EQUIPMENT ===

	===== '''Description of FreeCharging unclear if the Equipment is free to be used or free of charge. Perhaps also an attribute for working/out of service?''' =====		==== '''Description of FreeCharging unclear if the Equipment is free to be used or free of charge. Perhaps also an attribute for working/out of service?''' ====
	FreeRecharging = free of charge.		FreeRecharging = free of charge.

	NB. For any Equipment, NeTEx provides an attribute 'OutOfService' (but which does not describe the status variations of the equipment in real time…)		NB. For any Equipment, NeTEx provides an attribute 'OutOfService' (but which does not describe the status variations of the equipment in real time…)

Admin: /* Why is INDIVIDUAL PASSENGER INFO not just a structure within INDIVIDUAL TRAVELLER? */

2023-02-08T00:09:50Z

Why is INDIVIDUAL PASSENGER INFO not just a structure within INDIVIDUAL TRAVELLER?

← Older revision		Revision as of 02:09, 8 February 2023
Line 40:		Line 40:
	Therefore we have both: INDIVIDUAL PASSENGER INFO and VEHICLE POOLING DRIVER INFO.		Therefore we have both: INDIVIDUAL PASSENGER INFO and VEHICLE POOLING DRIVER INFO.

			[[File:Individual Traveller and driver model 1.png]]

	Here, the roles of an INDIVIDUAL TRAVELLER are separated and the attributes reflect '''the main requirements/characteristics related to each role.'''		Here, the roles of an INDIVIDUAL TRAVELLER are separated and the attributes reflect '''the main requirements/characteristics related to each role.'''

Admin: /* TOUCH ON/OFF TRANSACTIONS */

2023-02-08T00:03:50Z

TOUCH ON/OFF TRANSACTIONS

← Older revision		Revision as of 02:03, 8 February 2023
Line 130:		Line 130:
	*PASSENGER CHECK OUT ENTRY (recording PASSENGER CHECK OUT EVENT).		*PASSENGER CHECK OUT ENTRY (recording PASSENGER CHECK OUT EVENT).

	[[File:~~Fare_model~~.png]]		[[File:TM3-2.png\|1080px]]

	This UML diagram is included in Transmodel Part 5 which deals with Fare management.		This UML diagram is included in Transmodel Part 5 which deals with Fare management.
Line 137:		Line 137:


	NB. for describing the technical behaviour of a relevant device (for example the needed duration of the contact between the card and the equipment, the maximum distance between them, etc.), the scope is probably related to the smart card standards.		NB. for describing the technical behaviour of a relevant device (for example the needed duration of the contact between the card and the equipment, the maximum distance between them, etc.), the scope is probably related to the smart card standards.


	== Equipment ==		== Equipment ==

Admin: /* TOUCH ON/OFF TRANSACTIONS */

2023-02-08T00:01:12Z

TOUCH ON/OFF TRANSACTIONS

← Older revision		Revision as of 02:01, 8 February 2023
Line 127:		Line 127:
	The diagram below includes, for instance,		The diagram below includes, for instance,

	~~· PASSENGER~~ CHECK IN ENTRY (recording PASSENGER CHECK IN EVENT) and		*PASSENGER CHECK IN ENTRY (recording PASSENGER CHECK IN EVENT) and
			*PASSENGER CHECK OUT ENTRY (recording PASSENGER CHECK OUT EVENT).
	~~· PASSENGER~~ CHECK OUT ENTRY (recording PASSENGER CHECK OUT EVENT).




			[[File:Fare_model.png]]

	This UML diagram is included in Transmodel Part 5 which deals with Fare management.		This UML diagram is included in Transmodel Part 5 which deals with Fare management.

Admin at 23:58, 7 February 2023

2023-02-07T23:58:15Z

← Older revision		Revision as of 01:58, 8 February 2023
Line 60:		Line 60:

	· The SERVICE LINK (link between tso SCHEDLED STOP POINTS) has to be seen at the same functional level as a VEHICLE MEETING LINK (link between two VEHICLE MEETING POINTs).		· The SERVICE LINK (link between tso SCHEDLED STOP POINTS) has to be seen at the same functional level as a VEHICLE MEETING LINK (link between two VEHICLE MEETING POINTs).
	[[File:~~NM Vehicle Meeting Point~~.png\|~~thumb~~]]
			[[File:NM_Vehicle_Meeting_Point.png\|alt=\|border]]



Line 71:		Line 73:

	====Is it modeled right?====		====Is it modeled right?====
	POINT IN SERVICE PATTERN can also be each intermediate point, which is not a VEHICLE MEETING POINT. It is not 2 but an infinite amount of those in the SINGLE JOURNEY according to the diagram.[[File:~~SERVICE PATTERN 1~~.png\|~~thumb~~]]SINGLE JOURNEY PATH is an ordered list of '''VEHICLE MEETING POINTs''' on a single ROUTE, describing the pattern of working for an ALTERNATIVE MODE service.
			POINT IN SERVICE PATTERN can also be each intermediate point, which is not a VEHICLE MEETING POINT. It is not 2 but an infinite amount of those in the SINGLE JOURNEY according to the diagram.
			[[File:SERVICE_PATTERN_1.png\|alt=]]

			SINGLE JOURNEY PATH is an ordered list of '''VEHICLE MEETING POINTs''' on a single ROUTE, describing the pattern of working for an ALTERNATIVE MODE service.

	A SINGLE JOURNEY PATH may pass through the same POINT more than once. The first point of a SINGLE JOURNEY PATH is the origin. The last point is the destination.		A SINGLE JOURNEY PATH may pass through the same POINT more than once. The first point of a SINGLE JOURNEY PATH is the origin. The last point is the destination.

Admin: /* What is it really used for and why is it modeled so complex? */

2023-02-07T23:52:30Z

What is it really used for and why is it modeled so complex?

← Older revision		Revision as of 01:52, 8 February 2023
Line 11:		Line 11:
	Transmodel provides the following types of organisations:		Transmodel provides the following types of organisations:

			[[File:TMOrgTypes.png]]


	A TRANSPORT ORGNISATION is providing transport services related to particular modes of operation.		A TRANSPORT ORGNISATION is providing transport services related to particular modes of operation.
Line 34:		Line 33:
	The additional attribute 'isServiceDay' is present in NeTEx.		The additional attribute 'isServiceDay' is present in NeTEx.

	~~[[File:Transmodel organisation types.png\|frameless]]~~
	===INDIVIDUAL PASSENGER INFO===		===INDIVIDUAL PASSENGER INFO===

Admin: /* ORGANISATION DAY TYPE */

2023-02-07T20:56:50Z

ORGANISATION DAY TYPE

← Older revision		Revision as of 22:56, 7 February 2023
Line 34:		Line 34:
	The additional attribute 'isServiceDay' is present in NeTEx.		The additional attribute 'isServiceDay' is present in NeTEx.

			[[File:Transmodel organisation types.png\|frameless]]
	===INDIVIDUAL PASSENGER INFO===		===INDIVIDUAL PASSENGER INFO===

Anasfou at 18:31, 7 February 2023

2023-02-07T18:31:34Z

@@ Line 10: / Line 10: @@
 Transmodel provides the following types of organisations:
-[[File:Organisational model Tsm pic1.png|thumb]]
@@ Line 34: / Line 34: @@
 The additional attribute 'isServiceDay' is present in NeTEx.
-==== '''Why is INDIVIDUAL PASSENGER INFO not just a structure within INDIVIDUAL TRAVELLER?''' ====
+===INDIVIDUAL PASSENGER INFO===
 An INDIVIDUAL TRAVELLER may be a driver (e.g. in car pooling) '''or''' a passenger .
@@ Line 47: / Line 48: @@
 NB: the list of attributes reflects the MAIN characteristics allowing to describe the semantics of a concept – NeTEx provides in may cases some more properties.
-=== VEHICLE MEETING LINK ===
+===VEHICLE MEETING LINK===
-==== '''Some conceptual explanation would be nice (and better description).''' ====
+===='''Some conceptual explanation would be nice (and better description).'''====
 Transmodel provides data structures for conventional modes of operation. Some basic concepts are VEHICLE JOURNEY, SERVICE PATTERN, SCHEDULED STOP POINT, SERVICE LINK, etc
@@ Line 69: / Line 70: @@
 The functional similarity of the VEHICLE MEETING LINK with a SERVICE LINK for a CONVENTIONAL MODE OF OPERATION means:  '''it is a link along which no pick-up/drop-off operation can take place.'''
-=== VEHICLE MEETING POINT IN PATH ===
+===VEHICLE MEETING POINT IN PATH===
-==== Is it modeled right? ====
+====Is it modeled right?====
 POINT IN SERVICE PATTERN can also be each intermediate point, which is not a VEHICLE MEETING POINT. It is not 2 but an infinite amount of those in the SINGLE JOURNEY according to the diagram.[[File:SERVICE PATTERN 1.png|thumb]]SINGLE JOURNEY PATH is an ordered list of '''VEHICLE MEETING POINTs''' on a single ROUTE, describing the pattern of working for an ALTERNATIVE MODE service.
@@ Line 80: / Line 81: @@
 Two or more (2..* ) '''VEHICLE MEETING POINTs describe a''' SINGLE JOURNEY PATH.
-== Modelling SITE, PARKING, their components vs. EQUIPMENT ==
+==Modelling SITE, PARKING, their components vs. EQUIPMENT==
-=== PARKING & PARKING ENTRANCE FOR VEHICLE ===
+===== '''Description of FreeCharging unclear if the Equipment is free to be used or free of charge. Perhaps also an attribute for working/out of service?''' =====
-==== '''The barrier type of a PARKING would be important as well. Also how the payment is to be done. Should this be modeled?''' ====
+NB. For any Equipment, NeTEx provides an attribute 'OutOfService' (but which does not describe the status variations of the equipment in real time…)