Home » railML newsgroups » railML.infrastructure » infrastructure "state"
Re: infrastructure "state" [message #1937 is a reply to message #1933] Thu, 30 August 2018 16:49 Go to previous messageGo to previous message
Tobias Bregulla is currently offline  Tobias Bregulla
Messages: 20
Registered: June 2017
Junior Member
Dear all!

Am 30.08.2018 um 08:50 schrieb Christian Rahmig:
> OCP status is modelled:
>
> <ocp ...>
>   <propOther @status="planned">
> </ocp>
>
> Further enumeration values are:
> * operational
> * disabled
> * closed

We would suggest to add a fifth status for infrastructure, which is
intended to build but not in a real planning status. This would help to
exchange also future plannings e.g. for timetable simulation of long
term planning or for conceptual sketches/drawings.

In this context we suggest to add the following definitions to the
descriptions at https://wiki.railml.org/index.php?title=IS:propOther:

*Completed status value*: The construction or commissioning of the
element is planned for the medium or long term. However, there are still
no concrete (planning) activities for the construction of the element
beyond the preliminary planning and cost estimation.

PLANNED: The construction or commissioning of the element is planned
concretely and at short notice or concrete planning activities for the
construction take place, e.g. design, approval or implementation
planning, cost calculation, award of contracts. It is not normally
possible to use the element.

OPERATIONAL: The element is operational and can be used regularly.

DISABLED: The element is currently not usable, switched off or
deactivated and therefore cannot be used regularly. However, it can be
put back into operation at short notice without further construction,
acceptance or approval activities.

CLOSED: The element is no longer available, removed, dismantled, or no
longer exists. Planning, construction or commissioning activities are
absolutely necessary for recommissioning.

A German description with reference to the HOAI planning stages commonly
used in Germany can be provided.
For railML 3 we suggest a more intuitive naming of the enumeration values.

What does the community think about it?

Best regards,

Tobias and the Bahnkonzept team
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Use of <bufferStop>
Next Topic: <track>@mainDir
Goto Forum:
  


Current Time: Mon May 06 16:25:02 CEST 2024