Home » railML newsgroups » railml.misc » [railML3] status and life cycle (Common) (Approaching a generic modelling of states and life cycle stages)
[railML3] status and life cycle (Common) [message #2850] Mon, 22 November 2021 12:29
christian.rahmig is currently offline  christian.rahmig
Messages: 357
Registered: January 2016
Senior Member
Dear railML community,

in recent discussions in various use case working groups we discovered a common need for modelling life cycle aspects and stages.

We started this development in the infrastructure domain: Within domain <infrastructure> you can find a view named <infrastructureStates> where all information about infrastructure states are modelled. It is possible to model the state of a whole infrastructure as well as the state of single infrastructure components. Possible values for <infrastructureState>@value are: closed, conceptual, disabled, operational, planned

The interesting question: Who / which use case needs modelling of life cycle states and what are its specific requirements? We want to use this forum thread to collect the various requirements and ideas. In the then following conclusion, we want to find out, how "generic" the topic can be solved in the Common part or whether we should implement states independently in the domains where they are needed (infrastructure, timetable? ...)

So, dear all, what do you need for modelling different states? As always, any feedback is highly appreciated.

Best regards

Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: Possession Mgmt Use-Case
Goto Forum:

Current Time: Wed Dec 01 23:24:30 CET 2021