What is our primary use case?
Our use case for this solution is processing inventory transactions, everything from receiving inventory to different types of costing situations, consignment inventory versus inventory held, non-netable locations, different types of costing, builds material, routing, inventory evaluation all the way up through to and including your cost of goods sold release.
How has it helped my organization?
When we were using it, we did see an immediate benefit, especially in the inventory on consignment issue. We were a biotech pre-revenue company and most of our manufacturing was outsourced. So being able to track inventory within the system without creating a financial impact was very key for us.
Our organization has also been improved by the solution's regulatory reporting, specifically lot identification for FDA regulation. For example, if you have bad batches and it results in a compromised product, you could trace that all the way back to the receipt of the vendor good. That connect capability is very key and very helpful.
What needs improvement?
There is room for improvement in the reporting capability. To use it properly, you need intensive IT support. You cannot write your own reports. You can query data from tables and you can create your own reports within an Excel environment and that's helpful. But if you have to do anything formalized in a SOCs-compliant environment, you wouldn't be allowed access to those data tables. You would have to have a support function that can help you create the reports that you need.
For how long have I used the solution?
I have been using this solution for about two years.
What do I think about the stability of the solution?
I would rate the stability of this solution a 10, on a scale from one to 10, with one being the least stable and 10 being the most stable.
What do I think about the scalability of the solution?
This is definitely a scalable solution. It's a tier-one ERP system, so you definitely get what you pay for. If you're a small company and you buy a tier-one ERP system, you're never going to be able to address the full feature and functionality of something like an SAP. But if you're a large-scale organization, multiple legal entities, inventory accounting, and things like that, you'll get far more use out of it and it'll be a far greater payback.
At the time, I would say there were about 25-30 people using this solution in our company.
How are customer service and support?
I don't have any experience with SAP's technical support in regard to Business ByDesign.
Which solution did I use previously and why did I switch?
We were on a different version of SAP. We were very limited because we had a shared environment with a sister company. It was a very complicated setup. We had to have very synchronized functionality needs. We couldn't bring in any new functionality that the sister company didn't also want or need. It was a very complicated and unique situation.
How was the initial setup?
How straightforward the initial setup will be for your organization will depend on the level of integration that you want within your organization. For example, how many users you have, how many specific requirements they have, and what your logistics function needs are versus your accounting function versus your HR function. The list goes on.
I would say that when it comes down to tier one and tier two ERPs, a lot rides on the partner you choose to help with the implementation and the requirements that you have going into it. It has to be carefully managed. You can have a very decent implementation. But if not, you're going to be stuck with horrible reporting.
I would say having a core implementation team is essential. Each function is represented by a business leader and that leader can bring the requirements to the implementation team and serve as an intermediary between the business itself and the implementation, providing the test cases, doing the pass or fails, evaluating the progress of the partner that you're using. Being able to have direct communication and having a very structured approach to implementation is key.
You cannot just install the disk and have it be ready to go. This solution requires a lot more thought and effort to be able to put into place in a large-scale company.
A lot depends on how you approach it. If you approach it badly, you're going to have a bad experience. But if you approach it in a very prudent way, you're going to have the right experience implementing this solution.
The deployment of this solution took about five months for us. We took specific steps when we deployed Business ByDesign. We chose a project manager. We chose a VAR to help with that. We set up our historical data integration, we defined our test cases, and we developed a timeline for the implementation with key points and deliverables along the way. We took a very practical view of the implementation.
What about the implementation team?
We had to hire a third party to help us implement this solution. I would say around 40 people worked on the implementation process.
What's my experience with pricing, setup cost, and licensing?
I would say that the price is quite high. SAP and Oracle are highly competitive with each other in quality and in price.
The licensing is usage-based. The price also depends on the complexity of your organization. So if you're just a software company, you don't need to put in an inventory module within SAP. But if you do, you're going to have to pay for that.
Which other solutions did I evaluate?
We looked at Oracle solutions as well, but I don't remember the reason why we chose SAP over Oracle as I was not in that decision-making process.
What other advice do I have?
Overall, I would rate the SAP solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.
Which deployment model are you using for this solution?
Private Cloud