For variable data — delayed by $N minutes — sure, building that from pieces of audio makes sense.
For the name of a service though — “The service from $start_station to $end_station” — it’s not necessary to go all in on O(n) vs O(n^2) and record individual station names and put the word “to” in between. While a computer scientist will baulk at the inefficiency, a designer will optimise for the end result and record every route pair because (i) it sound much better and (ii) the problem scales quadratically where n is the number of railway stations you have built, a number which is bounded and grows extremely slowly. You could record every route name in a day, guarantee it.
This example is a bit contrived because most announcement only say the name of the destination station but it applies to a lot of other audio announcement systems where “clever programming” and “cheap out on recording studio fees” were optimised over “make it sound good”.