SBS Transit's iris system
-
IRIS cannot accurately predict what time Stadium Direct Bus will arrive. It always give. No Operation Error.
-
review of IRIS
verdict: no verdict
reason:
no GPRS phone. cannot use IRIS>phone a
t home cannot use IRIS, because i check already switch off computer, go downstairs is a diff of 10 mins. so the timing i check must be above 13 mins.
doing
also tried it on s147 one fine day. the thing show bus arriving, bus arriving, madness
improvement suggested: free//...hopefully.... sms system neh? (forced to use bus stop number then)
suggest show real time map of bus route with where the buses are along route at current time. suggest show rego on map also.
suggest use of next bus stop alert to commuters while travelling on bus
new verdict after uselessness
USELESS
ZYX -
read the IRIS website and you will see that SBST has explicitly stated that IRIS works for all services EXCEPT stadium directOriginally posted by SBS1985C:IRIS cannot accurately predict what time Stadium Direct Bus will arrive. It always give. No Operation Error. -
Is it after last bus?Originally posted by TIB1062Y:I noticed some errors for Service 70 and 162 (via Suntec) night bus after 11 plus in the late night. I have attached with the screenshots below:
http://i6.photobucket.com/albums/y242/tib967t/70_IRIS_prob.jpg
http://i6.photobucket.com/albums/y242/tib967t/162_IRIS_prob.jpg
http://i6.photobucket.com/albums/y242/tib967t/162_IRIS_prob_2.jpg
Take note of the exact timings that i checked. -
maybe all were 70A or 162A terminating tripsOriginally posted by stooper:Is it after last bus? -
how much is it [er iris request anyone knows:
say i use GPRS www.sbstransit.com.sg/mobileiris
then theres the space for bus service and bus stop..
the data log on the phone says data sent is 4kb, received is 8kb for the request.
so if 1kb cost 1 cent, one request cost 12 cents? -
May not be accurate sometimes
Tested(using GPRS) on sv143 @ 4+pm at People's Park Complex. It show that the next bus will arrive at 41 min and sub. at 50 min
.But it arrive 5 min later after i tested. -
I tried.. same thing happen to 76... stated 21 mins but came 5 mins after...Originally posted by choww:May not be accurate sometimes
Tested(using GPRS) on sv143 @ 4+pm at People's Park Complex. It show that the next bus will arrive at 41 min and sub. at 50 min .But it arrive 5 min later after i tested. -
services were majorly disrupted this morning and slowly resuming. many services had "no current prediction" or gave timings above 30 mins. looks like maintenance....
-
i actually had 50mins/15mins when testing the system at Central. somemore i'm testing every service and half of them had this error. dunno which line of the code broken giving such results sia.Originally posted by choww:May not be accurate sometimes
Tested(using GPRS) on sv143 @ 4+pm at People's Park Complex. It show that the next bus will arrive at 41 min and sub. at 50 min .But it arrive 5 min later after i tested.
interestingly, somerset mrt bus stop has been working fine all the while though. maybe it is not easily affected by traffic conditions given that it is a straight road for most services coming in from SMU (except 123 and 143). -
bunching. quite common, and most of time when arriving/arriving is shown, 2 buses turned up together.Originally posted by ZYX2005:review of IRIS
also tried it on s147 one fine day. the thing show bus arriving, bus arriving, madness
the worst is having the next bus behind the subsequent bus. -
the system is totally down liao. only nextdep is working....
-
did they under estimate the number of ppl wanting to use this service since sbs service is so erratic...Originally posted by ^tamago^:the system is totally down liao. only nextdep is working.... -
Actually the system can't show SWT trips...
-
dunno, but i think is maintenace bah...Originally posted by ignoramus2006:did they under estimate the number of ppl wanting to use this service since sbs service is so erratic...
they just patched it. now, when the bus takes too long to reach from the stop before (like CK Tang -> Heeren & Lucky Plaza -> Orchard Emerald), it will hold on to Arriving or revert back to 2 mins from Arriving previously, but now it jumps to the next bus and ignores the trip.
When the bus finally broke thru the traffic to rush to the next stop, it will start showing a trip 30 to 60 minutes later as the next bus when it is supposed to show Arriving, or simply show "no current prediction" until the bus has left the stop, instead of just sticking to "Arriving". -
Has anyone tried for Sv 39 & 85?
At Yishun, whole day put "No Current Prediction" -
sometimes it happens. anyway they made some modifications to the system, cannot auto-refresh. have to debug again.
-
So far now, can try Sv 191
These 2 svs confirm can show you "No Current Prediction" once it hits abv 60 mins...
At night can try 90...
For this, it's normal -
Maybe due to the fact that Yishun are not SBST area?Originally posted by sbst275:Has anyone tried for Sv 39 & 85?
At Yishun, whole day put "No Current Prediction" -
It was predicting fine when I tried last week. No such message. Dont know about accuracy though.Originally posted by carbikebus:Maybe due to the fact that Yishun are not SBST area? -
Should be the same what... Use GPRS...Originally posted by ignoramus2006:It was predicting fine when I tried last week. No such message. Dont know about accuracy though. -
same here. trying for 2 weeks since the day it came out. 39 and 85 was working well.Originally posted by ignoramus2006:It was predicting fine when I tried last week. No such message. Dont know about accuracy though. -
tested it on kent ridge terminal for 151
bus late by ard 5 min
n tt was at the terminal... prob the driver dilly dally b4 setting off -
i tested at central library before, show arriving until become no current prediction, then the bus comes. i think got something to do with the fact that sbst drivers like to leave a few mins late.Originally posted by khk:tested it on kent ridge terminal for 151
bus late by ard 5 min
n tt was at the terminal... prob the driver dilly dally b4 setting off -
but i tink the syst is gd... useful for those with super long waiting times like 151 etc. at least got some idea when the bus will come... better than waiting like 15-20 min for a bloody bus. a few min of delay is still fine w me
