- CMDB is very useful and it is used to manage client and non-client CI
- Freedom to use your ow way to integrate other systems with BMC Remedy
- Not too difficult to customize workflows
Using Service Request Management creates a Change Request and then sends, via a web service, a request to start a job on VMware to automatically create a server. When the job is finished and server is created it send back the name of the server back to remedy and automatically creates the CI in CMDB and create relationships. In this way we created an automatically way of requesting a server.
In 8.1.02 the Atrium core in the Midtier should be improved. It is using flex technology which is not so reliable. I think in v9 it was changed the technology.
I have been using this product for almost eight years.
There were no major issues with the deployment.
There have been no major issues with the stability.
There have been no issues with the scalability.
The first level is not so skilled . If you manage to go to second level they are good.
There was no previous solution in place.
It was a complex one, because our company was bought by another one and both companies had different versions of remedy installed which needed to be unified. The complexity was from the level of customizations each instance of Remedy needed.
We did it via a vendor. It would be good to create a knowledge in hour which knowledge should be transferred from the vendor side.
I'm not involved in this area.
The BMC Remedy products are reliable and cover all the ITIL processes. An advice would be to try to keep as low as possible the level of customizations.