| Re: Possession Mgmt Use-Case [message #2882 is a reply to message #2872] |
Wed, 19 January 2022 11:00  |
Thomas Langkamm
Messages: 25
Registered: April 2019
|
Junior Member |
|
|
Maybe this should be done in a way that allows a generic support of workflows. I can see two different ways to categorize this:
- Ownership: We assign something to a person or a group that is responsible.
- A track plan (infrastructure) detailling changes/construction work could be assigned to a person or organization for review/corrections.
- In operations, certain regions of the network may be assigned to operators or workstations (time dependent, maybe one interlocking is operated by train controllers during the day but remotely from another interlocking during the night).
- A weekly plan for a duty roster could be assigned to the workers council for clearance.
- Planning stage: Define a level of completion. For example, in timetable planning we may have stages
- Weekly planning (long term). This is a weekly roster for all train journeys that serves as template for a timetable period (a year).
- Date based planning (a few days ahead). Timetable for one specific date including deviations, but still managed by timetable planners.
- Todays timetable (constantly changing due to external circumstances).
My suggestion would be to create some basic framework for this (both planning stages and responsibility), while the different subschemas could use different values. For example, having a "today" planning stage makes a lot of sense for timetable planning but may be less useful for infrastructure and interlocking. There are some commonalities though, for example in planning stage we have typically long term/mid term/short term. Perhaps this is enough so that we don't need to define schema specific values?
|
|
|
|
Members
Search
Help
Login
Home
