| infrastructure "state" [message #1858] |
Thu, 28 June 2018 08:46  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
the state of infrastructure becomes more and more important for several
use cases and therefore requires an appropriate model implementation in
railML, too.
I would like to ask for your feedback on the following ideas related
with the infrastructure state:
1) operational view:
Infrastructure can be "available" or "not available" for operation.
Instead of "available" one could also use the term "valid". In any case,
the time reference (when is the infrastructure not available?) important.
2) asset life-cycle view
An infrastructure component is being "planned", then "manufactured" or
"constructed", then being put "in operation", after some years
"disabled", in between maybe several times "under construction", and
finally some day "removed" or "dismantled".
Despite the time, also the place is relevant here, because an
infrastructure component (e.g. switch) can be installed at different
locations in a track network during its lifetime.
3) funtional view
In railML 3.1 we define "functional infrastructure". Based on what I
wrote in 1) and 2) I consider the operational view to be identical with
the functional view. Do you agree?
Are there further views that I forgot to introduce?
Are there further states in these views that I forgot to mention?
Any comments are highly appreciated with regards to bringing them into
railML 3.1 beta2.
Thank you very much and best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
