Home » railML newsgroups » railml.common » Possession Mgmt Use-Case
Re: Possession Mgmt Use-Case [message #2872 is a reply to message #2843] Fri, 14 January 2022 09:00 Go to previous messageGo to previous message
David Lichti is currently offline  David Lichti
Messages: 13
Registered: December 2020
Junior Member
We discussed this in the TT Developer group. While possession management is not a prime concern for all TT users, it is still relevant in some degree to most. For some, it is enough to have a basic object that can be referenced from train schedules. So it should be possible to include possessions without too much details about activities. Others do detailed possession management throughout their entire planning and/or implementation phase.

While it may not be reasonable to integrate all possible life cycle states of all capacity objects into one single, common enumeration, it would definitely be good to use similar wordings and definitions wherever these use cases have similar stages. It should be kept in mind, that the life cycle of a capacity object is not always a linear process. Capacity requests may be cancelled, rejected or amended, resulting in an iterative process.

for the TT Dev Group

David Lichti
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML2/3] creating a new element to describe the project metadata
Next Topic: [railML3] status and life cycle (Common)
Goto Forum:
  


Current Time: Thu Mar 28 14:04:36 CET 2024