IL:localOperationArea

Documentation

Syntax

Autoexport from the XML-Schema for element IL:localOperationArea of railML® version 3.2 UML-visualization of IL
Documentation	Area used for local shunting movements without routes. Movable elements within the area might be operated from onsite panels.
Subschema	interlocking
Parents*	localOperationAreas
Children	assetName (0..*), belongsToOperationalPoint (0..1), crossingInPosition (0..*), deactivationKey (0..*), derailerInPosition (0..*), designator (0..*), detectorInState (0..*), hasCommand (0..*), hasIndication (0..*), isLimitedBy (0..*), keyLockInState (0..*), levelCrossingInState (0..*), releasedForLocalOperation (0..*), signalWithAspect (0..*), switchInPosition (0..*), trackAssetInArea (0..*)
Attributes: belongsToParent: The reference to another RestrictedArea of the same type used as parent to group 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.

Autoexport from the XML-Schema for element IL:localOperationArea of railML® version 3.1 UML-visualization of IL
Documentation	Area used for local shunting movements without routes. Movable elements within the area might be operated from onsite panels.
Subschema	interlocking
Parents*	localOperationAreas
Children	any (0..*), crossingInPosition (0..*), deactivationKey (0..*), derailerInPosition (0..*), designator (0..1), detectorInState (0..*), isLimitedBy (1..*), keyLockInState (0..*), levelCrossingInState (0..*), releasedForLocalOperation (0..*), signalWithAspect (0..*), switchInPosition (0..*)
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.

Best Practice / Examples

The local operation area brings the assets in a special mode where they can be operated freely from on-site devices, e.g. button panel near a switch. These assets are not available for any normal operation by the interlocking operator. The activation is done from the interlocking operator giving authorisation for the mode. The return of operational control might be done by command from the interlocking operator or a device on-site (special deactivation button). Local operation areas are mainly used for shunting purpose without the use of any route. The traffic safety within this area is solely dependent on the on-site staff. The active status of a local operation area is indicated to the railway staff by special signals or special signal aspects. The area limits are defined by the end of TVD sections, i.e. by axle detection points or insulated rail joints.

• <deactivationKey> – This is the reference to a button device located outside within the area used by the shunter to return control of the area to the signalman.
• <switchInPosition>– The reference to any switch which shall be in a particular position for this local operation area together with the protection side and the level of enforcement.
• <derailerInPosition>– The reference to any derailer which shall be in a particular position for this local operation area together with the protection side and the level of enforcement.
• <crossingInPosition> - The reference to any movable crossing which shall be in a particular position for this local operation area together with the protection side and the level of enforcement.
• <detectorInState>– The reference to any detector which shall be in a particular state for this local operation area together with the protection side and the level of enforcement.
• <signalWithAspect>– The reference to any signal which shall show a particular aspect for this local operation area together with the protection side and the level of enforcement.
• <keyLockInState>– The reference to any key lock which shall be in a particular state for this local operation area together with the protection side and the level of enforcement.
• <levelCrossingInState>- The reference to any level crossing which shall be in a particular state for this local operation area together with the protection side and the level of enforcement.
  • @protectingSide – This marks whether the element is protecting the area from inside, outside or none.
• <releasedForLocalOperation> – This is the reference to any movable element within the local operation area which can be locally operated by keys/buttons located nearby.
• list of buttons/panels for local operable assets – not yet implemented
• list of signals that may be start or end of a main/shunting route despite the active area – not yet implemented

🗒️ 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.