1st May 2005, 01:18 AM
A better implementation will be different deadlines according to the 1st letter of the family name. This will prevent huge overloading near , and at the deadline.
1st May 2005, 01:21 AM
agreed, but what about the T, C and L, many surnames begin with these letters
1st May 2005, 01:27 AM
By splitting into 2 dates, u can effectively 1/2 the load already.
Originally Posted by ortega
1st May 2005, 09:26 AM
i am no expert in this area. IRAS's system capacity is 20,000 taxpayers a day, after the initial hiccups. does it looks like a 'probably a cheap skate IT architecture implementation'?
Originally Posted by espn
Last edited by reachme2003; 1st May 2005 at 10:58 AM.
1st May 2005, 12:11 PM
The number one problem are taxpayers themselves and this happens everywhere and evertytime : procrastination
I'd prefer the paper route too... since it creates job.
1st May 2005, 12:35 PM
1st May 2005, 01:32 PM
SLA? Interesting question. If you are a vendor building the solution, as $X and the customer tells you: "We expect peak of 20,000 users." Would you max out your budget to cater for more, say 40k? Or would you max you profit and design a solution for 20,000 users (say with 10% slack) knowing that the customer would sign off for the 20k users?
BTW, I filed about 21 hours ago. Pretty smooth sailing.
1st May 2005, 01:34 PM
Watcher, the problem is SLA is never considered AFTER signing, clients want to see the system running, the solutionists wants to get the final payment. Simple as that.
For me, definitely will provide a solution for 20K peak. The earnings come when the client instructs the developers to now up it to 50K, which should be scalable and NOT development anymore. heehee.
2nd May 2005, 01:32 AM
Tried several times since 2 weeks ago... with 4 different kinds of errors at different stages.. finally managed to do it 24 hours & 15 mins late..