- 4chan hell raisers finding fame brings heat?
- The 10 dumbest mistakes network managers make
- NetApp quits bidding war in face of EMC opposition
- CompuServe closes after 30 years
- Google to launch open-source Chrome OS this year
| NETWORK MANAGEMENT ALL-STARS BNSF Railway | Evolution Benefits | PHH Mortgage | Priceline.com | Wilson & Company, Engineers and Architects |
Network Management |
|||||
|
To manage application performance, Evolution Benefits starts right at the source, the code itself. "We sell our performance and uptime," explains Sean Erwin, vice president of application development for the Avon, Conn., company.
Evolution Benefits sells a prepaid benefits card, called Benny, for employers to offer as part of their benefits programs. When employees sign up for a Flexible Spending Account or some other tax-favored benefit, they can use Benny to pay for eligible out-of-pocket and other expenses. The card payment system debits the payment from the appropriate accounts. "Employees no longer must pay for services, submit claims, and then wait for reimbursement," he describes.
As part of this process, a company's benefits administrators must be able to access at will the back-end application - a .Net/Web services-based Web portal called Benny Central. "Performance and uptime are key drivers in enabling benefits administrators to support employees," he says.
Via Benny Central, benefits administrators can use various tools to set up the prepaid cards for employees, provide customer service and automatically substantiate transactions per Internal Revenue Service guidelines, he says. Monitoring application performance at the code level was the only way to guarantee uninterrupted, real-time access to Benny Central.
The company gets our nod as a 2006 Enterprise All-Star for going above and beyond on application performance. Because this platform wrapped up in late 2005, application downtime has been eliminated while management-related costs are down by one-third. "Our app has to be up 100% of the time," Erwin says. "We needed a tool that could monitor performance and identify problems quickly - and not just the problem, but what the user was doing when it occurred. We needed to put the problem in context."
Comment