You are currently viewing a revision titled "[DB Station&Service] Platform Communication – How not to confuse our passengers?", saved on 30/08/2018 at 12:58 by Adrian Herzing | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Title | [DB Station&Service] Platform Communication – How not to confuse our passengers? |
||||||||||
Content | Session Summary
Key issues, questions, desired resultsIn Germany we are using a timetable which contains all trains at a station with the planned platform. This timetable is analog and is normally valid for 6 months. If there is a planned construction for 2 weeks then the DB hangs a small "construction timetable" next to it. --> Does this kind of timetable with platform Information still exist in your country? Why (not)? The DB app, the homepage and the display at the platform/hall however already contain the newest platform information. If the information has been provided early enough (1 week), then there is not even a notice for the passangers that the usual platform was has been changed. Only if the platform change is provided on short notice (< 3 days) then the passengers is noticed. --> In which cases do you communicate platform changes? In which digital/analog channels? In some stations two different trains share the same track (for example platform 1) at the same time. If this is planned, we communicate, which train is going to leave on which platform section (1a, 1b). If there is an unplanned platform change, the dispatcher can only communicate the whole platform (for example 2). The DB colleagues at the station have to change the platform section (for example 2a) manually based on their kowledge of the train length. --> Do trains sometimes share one track in your country? How do you communicate the sectors (planned, unplanned)?MaterialTo be addedSession Results and NotesThis section is reserved to keep notes about the session results during or after the session. so that this information is available to all participants after the BarCamp. |
||||||||||
Excerpt |