SBS Transit's iris system
-
One thing I noticed about IRIS... For those who are using IRIS Mobile, there isn't any option to check timings at Interchanges, only bus stops.
-
quite accurate i must say
like for sv 64 just now i check for the BS @ Selegie Ctr, Next Bus Arriving in 5 mins (then Bus Arriving), Subsequent Bus Arriving in 7 mins (then in 2 mins) ... kena bunching 
after that Next Bus Arriving in Bus Arriving, Subsequent Bus Arriving in 26 mins 
-
I just check Sv 14 and... Next bus Arriving in 26 minutes
Subsequent Bus Arriving in 44 minutes -
This afternoon searched for 151, next bus 31 mins, subsequent bus 45 minsOriginally posted by SBS9806J:I just check Sv 14 and... Next bus Arriving in 26 minutes
Subsequent Bus Arriving in 44 minutes -
You guys sure the IRIS system is really excellent?
Apparently I found 4 problems with it.
1. We know 520 --> 97e. Terminating pts for 97e are given as Fullerton Road and Collyer Quay. Jurong East disappeared. Bug in direction.
2. The Interchange timetables DO NOT STATE whether a bus is WAB, but the search for buses at bus stops do show such a case.
3. Referring to Problem 1, it's always better for commuters to see service numbers as the actual service numbers. (E.G. 521 --> 174e)
4. I am puzzled over IRIS regarding shortworking trips. How would it show that a service (for example 95C) is Service 95C and NOT Service 95? Note that there is no selection whatsoever for short-working trips. If anyone can help me find out about this it'd be good. -
Quite accurate! You can actually track the bus. Like just now I tried Svc 315, then after about 20 - 30 secs, that bus pass by the street, then I keep on tracking down from that stop, I can actually know how fast the bus travels (not the speed, its the time). As the time now is midnight, the bus travels faster.
-
services originating from amk temp int keeps showing bus bunching. the first two stops keep showing "arriving".Originally posted by Donavan:You guys sure the IRIS system is really excellent?
Apparently I found 4 problems with it.
1. We know 520 --> 97e. Terminating pts for 97e are given as Fullerton Road and Collyer Quay. Jurong East disappeared. Bug in direction.
2. The Interchange timetables DO NOT STATE whether a bus is WAB, but the search for buses at bus stops do show such a case.
3. Referring to Problem 1, it's always better for commuters to see service numbers as the actual service numbers. (E.G. 521 --> 174e)
4. I am puzzled over IRIS regarding shortworking trips. How would it show that a service (for example 95C) is Service 95C and NOT Service 95? Note that there is no selection whatsoever for short-working trips. If anyone can help me find out about this it'd be good.
regarding WAB trips, the system recognises it via rego. which means if it's a cameo it will show WAB. -
i heard the OCC phone management to catch svc 28 reach interchange 10++ minute earlyOriginally posted by carbikebus:Because of this we Bus captain can't chiong anymore on certain times
poor bus captain 
sure stop work at least 5 day. suck -
Nowadays you can ask OCC permission to arrive early @ Int/Ter if the demand was low and the traffic was smooth.So not so jialat afterall.Plus minus lorOriginally posted by davidchua123:i heard the OCC phone management to catch svc 28 reach interchange 10++ minute early poor bus captain sure stop work at least 5 day. suck 
-
I tried on 74 and 112... both show the minutes... then need to add another 4-5 min to it... not so accurate... maybe plus minus 5 mins
-
which stop? the timings for the system is inaccurate for the first few stops out of some interchanges/terminals....Originally posted by medicheng:I tried on 74 and 112... both show the minutes... then need to add another 4-5 min to it... not so accurate... maybe plus minus 5 mins -
the first few stops right out of some interchanges or terminals consistently gives inaccurate readings. so far amk and bishan kena.... the bus may switch to arriving out of nowhere but it is actually still 10 mins away (listed as subsequent)... sometimes both are listed as arriving or bunching...
2 possibilities conjectured.....
1. nextbus sub-system is not "talking" properly to the nextdep sub-system at the interchanges. nextdep most likely got its info from the individual interchanges about the next departure times the computer assigns to the next bus driver, which means the info is about a trip that has yet to commence.
however, nextbus uses info based on a trip that has commenced and tracks it while it is on the road. when bunching occurs on nextbus for bus stops just after the int/ter (arriving/2mins), it is probably nextdep giving a timing for nextdep and nextbus using its own tracking, producing 2 timings, which will be rectified down the route as nextbus determines the position of the bus (and eliminates the duplicate).
2. there may be buses that end trips at the interchanges/terminals but has details of the next trip set. by right DDU/nextdep shld be smart enough to know how many minutes before the commencement of the next trip, but nextbus may start indicating 2mins or arriving on top of timings given to it by nextdep (which is more accurate here), which may appear as the subsequent bus.
if 2 buses are parking at the interchange, nextbus may start detecting it as arriving/2mins, arriving/arriving or 2mins/2mins, which pushes the timing given by nextdep out of projected timings.
for stops which are somewhere down the route, such issues do not happen, and it is very very accurate, even displaying bunching like the bus 64 incident described above.
for example, at the bus stop opposite bishan MRT, svcs 13, 88 and 156 give accurate timings while 52, 54, 55 and 58 keeps having an unknown "arriving" trip interfereing with the data from time to time.
will need more investigations, but if SBST will ever want to put up panels at popular stops for demos and awareness campaigns, Somerset MRT is a good place where it works well because the profile of the road before it is pretty straightforward (one straight road) and it does not have the problem described above associated with stops close to interchanges and terminals.
another thing is the timing of 174 (town bound) which tends to early i.e. bus arriving 2-4 mins after the arriving flag is up and over.
one more observation from bus stop after rifle range rd along dunearn rd (42059): the evening peak after NP causes buses to be stuck with Arriving for a few minutes, then it promptly jumps to the timing of the bus behind as it assumes the bus may have passed the stop without stopping, before jumping back to Arriving when the bus has finally arrived 2 to 4 mins after first instance of Arriving flag. this is alright since it is due to 'external' causes outside the system's control. -
one more thing, the ETA of the niteowl services are largely identical at every bus stops, and they correspond to the departure time from marina centre.
but they're accurate in a sense that the bus really came after travelling the time required from marina centre to your bus stop, after the arriving flag was up..... -
interchange issue rectified
-
For NP's case that tammy pointed out, what if 3 Sv 74 buses arrived together?
-
it will only show the first 2, then when first bus left, it will still show arriving/arriving.Originally posted by sbst275:For NP's case that tammy pointed out, what if 3 Sv 74 buses arrived together?
today somerset there 14 and 65 keep bunching. -
466R of 162 is not shown in iris on at least 3 seperate occasions. 3868U of 124 on 2 occasions.
-
I tried on bus 112 at 8.55pm at bus stop 63391. It shows 12 mins and seq bus at 13 min. I took the 12th min bus, alight at Hougang Festival Market. And I waited like for 10 min, never see the so called seq bus of 13 min arrive. So is it cock up again? Detecting one bus twice?
-
i think if u refresh again later, the 13th minute bus wll stay at 13 mins until it comes out of the interchange.Originally posted by medicheng:I tried on bus 112 at 8.55pm at bus stop 63391. It shows 12 mins and seq bus at 13 min. I took the 12th min bus, alight at Hougang Festival Market. And I waited like for 10 min, never see the so called seq bus of 13 min arrive. So is it cock up again? Detecting one bus twice? -
I think impossible too.
My stop is like a few stop after kovan. And if the bus need to go to kovan it needs at least 20 mins.
So if it show 12 and 13, it mean the bus 2 and bus 1 is different by 1 min right?
Then the bus 2 should be somewhere behind?
Unless I am wrong in the caculation? -
the service is quite good.. however, even on 3G GPRS can still be a bit slow sometimes...
also, on most occasions, the bus always arrives 3-5 mins later than indicated... even if its off peak hours etc..
and, this service really revealed the true frequency of the services..
example, 159 was 25minutes for next bus at 11am .. -
actually, the connection doesn't matter, use internet to access mobile iris also get the same speed.Originally posted by 105090:the service is quite good.. however, even on 3G GPRS can still be a bit slow sometimes...
the first time u load a svc and bus stop, it needs to take a slightly longer time to locate the buses and return the timings. this can take up to 30 secs at times....
also, when the next bus bus has just left the bus stop, it will take a bit longer as it needs to 'grab' the timing of the bus behind the subsequent bus. -
That's why lor, see next time if they dare to reply to commuters abt ghost buses deploymentOriginally posted by 105090:the service is quite good.. however, even on 3G GPRS can still be a bit slow sometimes...
also, on most occasions, the bus always arrives 3-5 mins later than indicated... even if its off peak hours etc..
and, this service really revealed the true frequency of the services..
example, 159 was 25minutes for next bus at 11am .. -
This system... so far so good...
1. Braddell Rd (Blk 219)
Service: 13
Response: 5 min
Actual: 6 min
Reason: There was an accident just after the bus stop I was at. Left lane blocked. Only centre and right lanes passable..
Verdict: Pass
2. Toa Payoh Lor 2 (Toa Payoh Stn)
Service: 105
Response: 11 min / 20 min
Actual: 12 min
Reason: Maybe its my watch giving problems. Always come later 1min than the actual time.
Verdict: Pass
Additional Info: That '20min' bus caught up with the '11min' bus at Napier Rd. Should have did another check just before the earlier bus came at my boarding stop.
3. Orchard Rd (Thai Embassy)
Service: 36
Response: 3 min / 17min
Actual: N.A
Reason: The response was for the bus stop at Tanglin Rd (After Tomlinson Rd) Technically speaking an addition of 4min to my current stop will do.. So take it 21min.
1648hrs - Time of Query
1709hrs - Where is the bus?
1715hrs - Run 2nd query from current bus stop (Response: 2 min / 10 min)
1717hrs - The bus is late by 8 min from my first query.
Verdict: Fail. Then again 36 is erratic anyway The bus was already behind schedule and its unusual for this bus to get packed to the brim at 1745hrs at Suntec. The crowd usually get in after 1815hrs. Poor driver. -
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.
