In the last issue of Call Sign, Sid Nathan (K88) raised some points,
which the Editor said that I would answer in this issue and as I dare not
upset either, here is my response to Sid's points - softly spoken, I
should add...! They are in fact as much of an update as anything, as some
of the points have been raised and answered before.
Pick-Up Positions
1... Limited space on the trip offer is the only reason why the door
number is not shown. If we were to carry out Sid's request and show the
door number as well, then we would have to withhold the attribute of the
job. This is another one of those decisions that the Board are required to
make that will not please everyone. Sid wants the door number while others
want to see the trip attribute. I am pleased to report that the new
terminal will allow both fields to be shown, but the enhancement cannot be
made until all of the fleet are fitted with the new terminal. This will
happen, Sid, please be patient...
Voice Requests
2... Sid Nathan is not the only person who has asked the question about
the length of time it takes to deal with a voice request. The main reason
is that we only have one voice channel. All the other channels are used
solely for transmitting the Data backwards and forwards. If we were to
allocate another channel for voice, it would seriously damage what we call
the 'accuracy of the messaging.' What is meant by 'accuracy of the
messaging' is the two-way communication between host computer and cab.
Even without touching your terminal, it is still in communication with the
host computer. For every piece of information that is sent to the cab, a
reply comes back. For instance, when the computer sends you a trip, before
you press the 'accept' or 'reject' button, your terminal
|
has responded with a message which acknowledges that the trip has in
fact reached your terminal.
As with all types of communication, there are times when
there are breakdowns. We have all experienced our mobile phone cutting out
or the satellite television sometimes losing its signal. Well, the same
happens with our data despatch system and that lost signal is a situation
we monitor very closely. We have found that the more mobiles that lock on
to a specific channel, the more the accuracy of the signals slightly
drops. With fewer channels available, it means you would experience those
frustrating situations far more. You would see more 'booked off zone'
messages after accepting a trip and after pressing the 'send' button, the
'transmit busy' message would also be seen more frequently.
Over the past three to four years, we have made substantial
enhancements to our despatching system and the time has now come to do the
same with the communication side of the business. We are at present in
discussions with suppliers and with modern technology as it is, it may be
possible to simultaneously run voice and data along the same lines. If
this can be done, then Sid's frustrations would finally disappear. Again,
testing is a vital part of implementing new systems. Manufacturers were
ready to do this a couple of months before Christmas, but it was a
decision I and the Board would not take because had anything gone wrong,
it would have had a profound affect on the business at such a busy period.
Now the
|
festive season is over, we will be getting this project up and running
again. Until completed, your assistance would be appreciated by using your
terminal to its full functionality. By this, I mean DA's, AAR's and
Address Queries should not be done on voice. Voice requests and mobile
telephone calls to the voice controller must be for very urgent enquiries
only.
And Everything Else...!
3 / 4... I'm will answer Sid's points three and four together
because of the similarity between the two.
There are changes that need to be made to the new terminals.
The queue position display is one that has already been noted and I accept
should be displayed for a longer period of time. However, to have the
queue position constantly updating would have an opposite effect to what
Sid says. It is better that the QP button is pressed as and when required
because the lower in the queue you are, the more frequently your queue
position changes. If this were to be constantly transmitted, there would
be a considerable increase in the messaging being sent. Programming is
required to enhance these issues and it was decided that we should not
alter the despatching system until after the New Year, which is what will
happen.
Hopefully Sid I have answered your 'last moan of the year', but if I
know you, we will still see you coming to the office and you will still
keep asking the questions! The answers will not change but I will, if the
nickname you have given me of 'Killer Kong Cain' is used too frequently!
I hope you had a Happy Chanukah Sid and to you and everyone else, may I
wish you all the happiest of New Years and I hope to see many of you at
the AGM...
Keith Cain
|