Looks good.
This won't be a .NET app will it? 'Cause if there ends up being choices, the non-.NET version will always win it for me.
Anyway, a suggestion on layout. Atm it's not overly clear to me what the save button refers to - just the stations? Or the events as well?
I'd apply some grouping to distinguish the different functionality, and to keep the buttons together and more structured. Here's a quick mockup using your model...
Having the "Prepare" button separated means that under normal operation, players can ignore the two groupings altogether and go straight for the Prepare button (which is unrelated to your editing functions anyway). Some tooltips would help with the buttons, but keep in mind this is just a quick mockup to demonstrate an alternate layout.
I have assumed that clicking on a station will automagically populate the events view. I have also assumed that you want to apply changes to each aspect separately.
Now, ordinarily, if you have a "Save" or "Apply" button, you should also have a "Discard" or "Cancel" button, otherwise how will users get back to what they started with without closing and reloading your app?
Sorry, but I just can't help but provide suggestions on programming when asked to do so, LOL! I won't be offended if you discard everything I've said.
