My primary use case for Remedyforce is for clients who do not have a requirement on the CMDB (Configuration Management Database). When I'm talking about a requirement, I'm talking about things like federation and reconciliation requirements. This gap is one of the reasons I started looking at Remedyforce as a potential solution.
The second reason for choosing this is when the client size is medium to small — not truly enterprise. Medium-sized companies in my view means that the support staff is around 10 to 30 members. That is just the number of support staff, not end-users. There should also be about 50 to 100 servers.
A third component is when there are no critical integrations — we call them huge integrations. There are two kinds of integration. First, there is very straightforward integration where I need to connect to an active directory and, for example, read the people detail. The second is more complicated integrations. For example, a client might ask to do provisioning on the active directory, or they may want to do updates like bidirectional integration. Remedyforce is not built for this type of thing. The product as of yet was not built to handle complex requirements. When it comes to complex requirements, we have to be honest with the client. It is as if they buy a cheaper car and try to make it into a Ferrari. We have other remedies for this situation, Helix Remedy. It is a Ferrari. Remedyforce is not the Ferrari.
There are several excellent features that I find valuable in the product. The self-service portal, knowledge management, and the CMDB from the last version are the best of these. Previously CMDB was the worst feature. Now they improved it significantly and it is one of the best features of the product.
Other modules that older versions of the product had are not really featured but can be useful. For example incident management. I cannot tell you that incident management in Remedyforce is as good a feature as incident management in Micro Focus — which has different incident management capabilities. They are both valuable incident management products depending on needs and expectations.