In addition to a BES are running a Sprint/Seven product known as Business Connect Server Solution which offers the same sort of middleware solution as a BES does but for a client (BizConn) that can run on PPC/PalmOS/and some Java-based handhelds. We have a saying in the office - "If RIM is down, it makes headlines. If BizConn is down, it must be Friday".
My own experience is that RIM's managed network is more reliable and better supported. Sprint's continued mismanagement of the BCSS back-end has caused us no shortage of grief. They refuse to provide an SLA for the service, which has forced our team to dial support back to 8x5, M-F for the app. They push client updates with little notice and no advance download available for testing. Their support line offers perpetual catch-22. They refuse to issue ticket numbers for incidents and then request ticket numbers on subsequent callbacks.
I can see the rational for the arguments that RIM should decentralize, but I would much rather deal with them in times such as these than the telecom proper. Then again we also run Exchange and offer ActiveSync. Don't ask why we offer 3 flavors. Please don't ask.
I do believe that software advances have left many a user out in the cold because of the inability to have their desire to learn a new tool match the speed at which the tools are revamped.
I can't help but think, however, that the level of support currently provided for users allows them to get by without putting in any real individual effort. I would argue that support people do too much for their users.
Technology may have moved too quickly for the average user, but it has provided a larger subset of support professionals who don't aren't represented by SNL-parodied stereotypes. I think all of us who do tech-support have tried to explain an underlying logic behind a process only to be told, 'just do it, I'll be getting coffee'.
Slashdot Mirror
University setting. Freedom of choice is a beautiful thing when it comes to having to support every platform under the sun.
In addition to a BES are running a Sprint/Seven product known as Business Connect Server Solution which offers the same sort of middleware solution as a BES does but for a client (BizConn) that can run on PPC/PalmOS/and some Java-based handhelds. We have a saying in the office - "If RIM is down, it makes headlines. If BizConn is down, it must be Friday". My own experience is that RIM's managed network is more reliable and better supported. Sprint's continued mismanagement of the BCSS back-end has caused us no shortage of grief. They refuse to provide an SLA for the service, which has forced our team to dial support back to 8x5, M-F for the app. They push client updates with little notice and no advance download available for testing. Their support line offers perpetual catch-22. They refuse to issue ticket numbers for incidents and then request ticket numbers on subsequent callbacks. I can see the rational for the arguments that RIM should decentralize, but I would much rather deal with them in times such as these than the telecom proper. Then again we also run Exchange and offer ActiveSync. Don't ask why we offer 3 flavors. Please don't ask.
How can the Video Game market continue to thrive in the same way the film industry has? Lowered expectations by the consumer!
I do believe that software advances have left many a user out in the cold because of the inability to have their desire to learn a new tool match the speed at which the tools are revamped. I can't help but think, however, that the level of support currently provided for users allows them to get by without putting in any real individual effort. I would argue that support people do too much for their users. Technology may have moved too quickly for the average user, but it has provided a larger subset of support professionals who don't aren't represented by SNL-parodied stereotypes. I think all of us who do tech-support have tried to explain an underlying logic behind a process only to be told, 'just do it, I'll be getting coffee'.