Let me get this straight: forcasting accuracy is less accurate because there is a smaller quantity of current observations? I don't think so...
There is plenty of information regarding what is coming. The problem is that they don't know what is going to happen when it all gets here (Seattle).
As the weather moves in from the west, it bends around the Olympic mountains (both from the north and the south) and converges over Seattle. What happens next is anyone's guess.
This is what makes it a real challenge to predict the weather in the Seattle area.
An important distinction to keep in mind that the term "Remedy" is often used indiscriminately to refer to both the software development environment(Action Request System) and/or individual applications running on the ARS (Help Desk, Change Management, Asset Management, CRM, etc).
Any discussion of "Remedy" should make it clear what portion is being examined.
I've been working with both for many years and think that ARS is great - there are very few alternatives for building and customizing enterprise applications as quickly and comprehensively as this can.
On the other hand, Remedy's applications are good - and can be great in the right environment. It's takes a lot of attention to detail to make sure that the configuration matches your business workflow. But once this work is complete, you have a system that works well. If this is skipped (and not maintained), then you run into problems.
Custom applications are fun to build and can be really amazing in what they can do!
Slashdot Mirror
Let me get this straight: forcasting accuracy is less accurate because there is a smaller quantity of current observations? I don't think so... There is plenty of information regarding what is coming. The problem is that they don't know what is going to happen when it all gets here (Seattle). As the weather moves in from the west, it bends around the Olympic mountains (both from the north and the south) and converges over Seattle. What happens next is anyone's guess. This is what makes it a real challenge to predict the weather in the Seattle area.
An important distinction to keep in mind that the term "Remedy" is often used indiscriminately to refer to both the software development environment(Action Request System) and/or individual applications running on the ARS (Help Desk, Change Management, Asset Management, CRM, etc).
Any discussion of "Remedy" should make it clear what portion is being examined.
I've been working with both for many years and think that ARS is great - there are very few alternatives for building and customizing enterprise applications as quickly and comprehensively as this can.
On the other hand, Remedy's applications are good - and can be great in the right environment. It's takes a lot of attention to detail to make sure that the configuration matches your business workflow. But once this work is complete, you have a system that works well. If this is skipped (and not maintained), then you run into problems.
Custom applications are fun to build and can be really amazing in what they can do!