![Odin Service Automation [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_100/iec8pwn6qk6vore8l450kf2gm351.jpg?_a=BACAGSGT)
- Application Packaging Standard compatibility: Because we distribute our services via this standard, this was a key criterion.
- The ability to scale from 10s to 1000s of users was also critical.
- The ability for the users on the system to self-serve.
It is compatible with the Application Packaging Standard.
What is most valuable?
How has it helped my organization?
We can provision and bill customers in one place. Previously, this was done with different systems. This allowed us to scale massively without a massive increase in resources.
What needs improvement?
We have a multi-tier subscription selling solution. Some of the billing functionality could be better enhanced.
I would add more granular billing with more complex rules. For example, the average storage used in a month, or the minimum amount, whichever one is greater.
For more detail:
Existing APS realization supports monthly average billing.
E.g. if we sell storage to the customer, OSA will calculate how much space was used in average during e.g. calendar month and charge customer for it. It does create a bunch of complications as showing for the customer an evidence that confirms the average number is typically complicated.
Our customers base prefers to deal with end-of-the month values. In example with storage, it would imply billing customer for the usage based on usage at the last day of the month.
Why is it better?
1) Much easy to explain to customers how it works
2) Much easy to show in our application that usage is in our application is equal to the usage customer was billed for. Implementing in our application “proof” of average billing is much more complicated
3) Finally – much faster adoption and much faster go-to-market for customers like Acronis
For how long have I used the solution?
We have used the solution for six months with the latest version, and we have used it for 18 months total.
What do I think about the stability of the solution?
We need to plan sufficient time for major updates to stabilize the update.
What do I think about the scalability of the solution?
It has been scaling without issue.
How are customer service and technical support?
Support is customer facing, but we had some lack of technical expertise for the more difficult questions.
Which solution did I use previously and why did I switch?
We did not evaluate solutions of such class before. All the work was manual before.
How was the initial setup?
Initial setup was easy, but we already had expertise with this product. The design phase is critical. If you know what you want the product to do ahead of time, then there is no issue.
What's my experience with pricing, setup cost, and licensing?
Licensing is transparent. Pricing for the product is reasonable. Pricing for support is high. Negotiate a better price for a long-term commitment.
What other advice do I have?
Allocate at least six months for the implementation of, and learning about, the product before the production launch.
Think of having them manage the solution for you for a period of time while you learn.
