Adjusting recorded announcements to station specifics?

[TheManOnThe172]

At 0620 this morning, a recorded announcement boomed out at Matlock station, reminding passengers to look after their bags, and to keep clear of the platform edge because fast trains might come through at speed.

With the first train just departed, it would be over an hour before the next train arrived so there was nobody on the station. And being at the end of a branch line, there are no fast trains.

How hard is it for a TOC to set up their system so that these general announcements would only be played out when people are going to be around, and only to cover imperatives that are relevant to the specific station?

 

[pokemonsuper9]

fast trains might come through at speed.

And being at the end of a branch line, there are no fast trains.

Ah yes 15mph, I'm sure a train coming at cycling speed would definitely be a surprise and not blindingly obvious, and won't have much turbulence at that speed either.

I imagine they just have it so if station has any through platforms, that announcement will play, and Matlock's Platform 1 is a through platform for trains onto the heritage line.

 

[Horizon22]

Pretty easy - software dependent. However the quiet default hours are normally only 2200-0600, unless there’s some specific resident concern noted at the station.

Most pre-recorded announcements are set at intervals across the network (every X minutes) so it doesn’t matter how often there is a train service.

Also fairly easy to remove a station from any specific announcement, if so desired. But if you’re playing it at hundreds of stations unless someone knows otherwise and is specifically aware to remove a station, it will be the default set up.

 

[CaptainHaddock]

Pretty easy - software dependent. However the quiet default hours are normally only 2200-0600, unless there’s some specific resident concern noted at the station.

Most pre-recorded announcements are set at intervals across the network (every X minutes) so it doesn’t matter how often there is a train service.

Also fairly easy to remove a station from any specific announcement, if so desired. But if you’re playing it at hundreds of stations unless someone knows otherwise and is specifically aware to remove a station, it will be the default set up.

Or just turn off the announcements altogether at small terminus stations like Matlock. What information do passengers need to know? All the trains are going the same way and to the same destinations.

 

[The exile]

How hard is it for a TOC to set up their system so that these general announcements would only be played out when people are going to be around, and only to cover imperatives that are relevant to the specific station?

We are in an age of “box ticking” compliance. Safety announcements are played “so that’s all right then”. The fact that some of those announcements are so patently drivel that those listening start being conditioned to ignore them is irrelevant. All that matters is that box 27.2.43 on page 956 of some compliance manual has been ticked.
Like the “caution, contents may be hot” printed on coffee cups.

 

[Horizon22]

Or just turn off the announcements altogether at small terminus stations like Matlock. What information do passengers need to know? All the trains are going the same way and to the same destinations.

Why are you turning off announcements? Are you turning off the PA all all termini? Sure some can be switched off specific to through stations but things like engineering works, security announcements, service disruption will all be relevant wherever you are.

I’m not here to get into the classic RailUK debate about whether there are “too many announcements”, but answering queries related to the OP’s question.

 

[Parallel]

Or just turn off the announcements altogether at small terminus stations like Matlock. What information do passengers need to know? All the trains are going the same way and to the same destinations.

They’re a legal requirement where the equipment exists or has existed.

Some TOCs (including EMR at some stations) use noise sensors, which adjusts the volume of the PA equipment subject to the ambient background noise of a station. EMR use this at Derby, Nottingham, Burton-on-Trent and probably others. Perhaps it should also be fitted to their smaller stations. However it may already be fitted, if it boomed out. The sensors may have recorded significant background noise as the train departed.

Some TOCs also configure ‘quiet hours’ when the volume is reduced or switched off from late evening to the early morning, or removing the generic announcements about safety and security at these times.

 

[Lockwood]

I've been at Guildford and heard an announcement to stand clear of platform 1, as the approaching train is not scheduled to stop at this station.

I understand the spirit of that message is more "leave that train alone, it isn't for passenger use", but the wording sounds more like it is not going to stop...

 

[Mcr Warrior]

I've been at Guildford and heard an announcement to stand clear of platform 1, as the approaching train is not scheduled to stop at this station.

Have heard similar at Manchester Victoria (platform 2). Arrival (ECS) into a dead-end bay platform before heading out in service.

 

[Lockwood]

Ah yes, that's what it was at Guildford as well. Rather than a totally non-passenger service.

 

[CaptainHaddock]

They’re a legal requirement where the equipment exists or has existed.

Well change the law then! Has there ever been an instance of a passenger being hit by a fast train passing through a terminus station?

 

[Parallel]

Well change the law then! Has there ever been an instance of a passenger being hit by a fast train passing through a terminus station?

My point was in relation to the general provision for announcements, not the specifically poorly programmed examples. I doubt anyone would argue on the latter point.