We have leveraged ARS as a development platform but we were only able to so because we do run ITSM and hence this justified building the Remedy infrastructure and purchasing a large quantity of licenses in the first place.
Strategically we are using Remedy to close the loop on all of our shared service centres such as IT (of course), HR, Facilities and Marketing. We are increasingly using Remedy to develop business applications but generally restrict these to some form of 'request tracking system'. We also have a .NET development team and Remedy certainly does have advantages WHERE IT MAKES SENSE. It is easy to support since we already have a large Remedy infrastructure established, and the turnaround time for a functional application is usually less. However, for some small applications it doesn't make sense to use Remedy due to the license costs for users, or if we need more integration options such as advanced web services with other MS applications. The bottom line is that because we have an existing Remedy infrastructure it gives us the option to develop other Remedy applications if it makes sense, and we are more than happy to use Remedy in these cases. Regards, Tayler McLean _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
