250/365

Another busy old day in the office, the overnight rain had done its best to destroy the network and as I walked in a tree was falling on a train outside New St station. As  Birmingham expected the massed workforce to make their way in, the railway infrastructure wasn’t there to allow them too. I did the noble thing and manned the Short term planning desk and kept my head down. Not long after, rafts of the Salop lines found themselves flooded and reaffirmed my good decision to continue training on the new schedule input system.

Planning trains isn’t an easy job, planning trains at short notice in between planned trains can be quite frustrating, the system in place to enter these very short term planned moves has been around for five decades and relies upon  programming code, knowledge of railway geography and a lot of guesswork. These days the vagaries of guesswork and poor planning are punished. Every delay is someone’s fault, every delay costs money and faults and costs need avoiding wherever possible. There are also the instances where long term planning hasn’t managed to find a valid path for requests, these requests are hidden under the table and then faxed through at the last moment in the hope that someone else gets the blame for it going wrong.

So enter an all singing and dancing system, designed by experts to take away the guesswork and geography using clever algorithms and shit like that. I tried it before my failed flying lesson on New Town Row and it was pants, pants to the point of the tutor not getting the system to load at all, another attempt saw it load then crash. So I was interested to see how it had developed over seven months.

On the whole I was pretty impressed, it looks very pretty and the page is fairly well thought out for something not designed by the people who use it. There are a number of advantages in that you can work on more than one request at a time and it isn’t as easy to delete hours of work by pressing the wrong key. It is fairly intuitive and actually works out how much time to add, which will save me a lot of paper. It seems the problem was the geography and guesswork issues, it can’t do them, take them away and it is fine. It is a lot slower than the old system on the easy requests but I think it leads to a more accurate result, as long as you can guess how much time is required and where you are. I love progress, it is great.

I will continue looking at the system tomorrow as I am covering the job on Friday, even more so after the weather forecast overnight.

Tomorrow we are off to collect a file of family history stuff to continue the research into the family tree. I am looking forward to getting a few questions answered and progressing further back, the relatively recent history is more difficult than the older stuff as it relies upon memories rather than fact, a number of which have already proven incorrect. It is actually very interesting and a whole lot less dangerous than bicycle acrobatics

Advertisements

6 thoughts on “250/365

  1. Chris Waite says:

    Gotta love Integrale, takes a little longer but you always have that conflict detection screen to print off to cover your arse. I’d stay on VSTP’s if I were you – lovely easy life especially in Brum where nothing happenss.

    • aideym says:

      Chris Waite opens a can of worms regarding my beloved VSTP comrades :). The system would be a whole lot better with computers that could handle the system requirements

      • Chris Waite says:

        Well they had to upgrade the PC’s in York as apparently Integrale is specc’ed to run with a min of 2Gig of RAM and our old ones had about 1/4 of that. Not sure the slowness is at user end or Serverside, though I suspect the issue is more at ATOS as the Integrale team are constantly trying to get more RAM on their virtual servers. Network speed probably holds it back too as that is an awful lot of information.

        I can avoid worrying about it for awhile though as I’m not back onto the VSTP desk until the new year.

  2. Chris Waite says:

    The other reason Integrale is so slow is that it was obviously specc’ed by an idiot, It’s simply moronic for it to attempt to validate the entire schedule every time, more sensibly it would be user specified how far along it validated (typically to next loop or whatever). You could then validate in sections and take a huge load off it.

  3. Chris Waite says:

    Or you could just pretend to be NR Scotland and only input schedules until they get onto someone elses region and leave it for someone else to do the job.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s