The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Introduction
Documentation
Syntax
|
|
| Documentation
|
A set of track assets inside a station which can have different operating permissions (being controlled from a different controller) as the rest of the station
|
| Subschema
|
interlocking
|
| Parents*
|
permissionZones
|
| Children
|
assetName (0..*), belongsToOperationalPoint (0..1), canBeControlledBy (1..*), controlledElement (0..*), designator (0..*), hasCommand (0..*), hasIndication (0..*)
|
Attributes:
- belongsToParent: The reference to another permissionZone used as parent for grouping them together.
- if some information exists in parent and child, then information in child overwrites it in child
-if some information exists only in parent, then child inherits this information from parent (optional; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}),
- elementNumber: element number for internal referencing in the engineering data (optional;
xs:nonNegativeInteger),
- id: unique identifier (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
|
|
| Documentation
|
A set of track assets inside a station which can have different operating permissions (being controlled from a different controller) as the rest of the station
|
| Subschema
|
interlocking
|
| Parents*
|
permissionZones
|
| Children
|
any (0..*), canBeControlledBy (1..*), controlledElement (1..*), designator (0..1)
|
Attributes:
- id: unique identifier (optional;
xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Changes 3.1→3.2
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
In order to have clear command path only one operator/controller is exclusively allowed to operate assets by the interlocking. However, the permission to operate assets can be shifted to another predefined operator/controller. Subsequently zones have to be defined, describing the set of assets for which the permission is transferred. In the simple case the permission can only be changed for the entire station or interlocking. Then no particular definition of affected assets might be necessary.
Although a permission zone might appear as another type of restrictedArea on the first glance the way of defining the zone is different.
- <canBeControlledBy> – This is the reference to any controller, i.e. operator/train dispatcher place, which can use the zone for manual commands.
- <controlledElement> - This is the reference to any element which belong to the area and will have the same operating permissions.
| 🗒️
|
- restrictedAreas
restrictedArea is an abstract class, which is instantiated for any kind of special controlled area within the network. It will be than enriched by the particular classes of the area. The elements available for each instantiation are:
- <isLimitedBy> – This is the reference to track assets forming the limits of the defined area. The references shall be made preferable to interlocking elements.
- <trackAssetInArea> - This is the reference to track assets located inside the defined area. The references shall be made preferable to interlocking elements. These elements give supplementary information for definition of the area as the pure limits might not be sufficient.
- @belongsToParent - This optional attribute contains a reference to an element of the same type which is superior to this element, i.e. this is used for aggregation of several areas of same type.
|
|
|
Additional Information
Notes
Open Issues