What is our primary use case?
When a company procures an asset they need to use, by placing a purchase order, we do the capitalization of the assets. Once an asset has been capitalized and the company physically uses the asset, we calculate the depreciation of that particular asset on a routine basis. Until the time the asset is in use, we continue to keep depreciating it for its use.
In certain cases, it can also happen that the asset gets disposed of. For example, if you have an asset with an eight-year lifespan, the asset may get disposed of in the eighth year or earlier in the seventh year. Generally, this is one use case that typically happens with every company.
What is most valuable?
The most demonstrable feature is the asset creation form, which is quite informative. It has a provision to capture almost every bit of information pertaining to that asset.
What needs improvement?
The solution’s depreciation calculation setup needs to be improved because it is slightly disintegrated. The depreciation formulas or rules are not quite integrated well and could have been simplified. Currently, you'll have to get into multiple screens and applications to set up various rules, methods, and formulas. They could have been simplified, whereby the system prompts one after the other on its own. However, that is not the case right now.
One has to launch multiple applications and do the configuration separately, one after the other. Instead of that, it should have been more simplified so that the system, by default, takes you one after the other screen in a sequential manner since all of them are interlinked. However, the way the solution is currently designed, they have been de-linked. This is one area where the solution needs to be improved.
For how long have I used the solution?
I have worked on JD Edwards EnterpriseOne Asset Lifecycle Management for eight years or so as a partner.
What do I think about the stability of the solution?
The solution is quite stable. We do have problems, but they have nothing to do with the product as such.
I rate JD Edwards EnterpriseOne Asset Lifecycle Management an eight out of ten for stability.
What do I think about the scalability of the solution?
Our clients, by and large, belong to medium-scale businesses. From a concurrent user count and the revenue the company makes, we have clients who are medium and big, not small-scale. The solution is absolutely scalable.
I rate JD Edwards EnterpriseOne Asset Lifecycle Management an eight out of ten for scalability.
How are customer service and support?
Even the original product vendor, Oracle, does not have 100% capability. The support from Oracle has not been good, and it could be improved and made better. For example, if I have any problem with my client in a particular area and we log a case, it doesn't proceed how we want it to. Sometimes, the Oracle vendor or consultant does not have enough knowledge, and Oracle needs to improve in this area.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Tally was one software I used. There is no comparison between JD Edwards and Tally. Tally is very simple and user-friendly. You can define the formula on the run, define your ledger types very easily and quickly, and have multiple depreciation for tax and legal separately calculated. That is pretty much easier and faster.
Since JD Edwards is an integrated product, I don't see any problem with it; it is good the way it is.
How was the initial setup?
The solution’s initial setup is comfortable. It is a one time setup, which is quick and fast. It doesn't take much time. The planning exercise, which happens outside of JD, is a time-consuming activity, but within JD, it is quite easy and fast.
What about the implementation team?
The solution is deployed both on-cloud and on-premises. Currently, clients are using the solution on-cloud, but there are cases where the clients are still using the solution on-premises.
The solution's deployment doesn't take too much time, and it happens seamlessly. We advise our CNC team to do the deployment, and we get an update that the objects have been deployed. I have not faced any problems from a deployment perspective
What other advice do I have?
I would strongly be in favor of implementing the solution. The product is quite stable, and the offering is good. JD Edwards EnterpriseOne Asset Lifecycle Management is a good product, and I recommend going ahead and having this product.
Overall, I rate JD Edwards EnterpriseOne Asset Lifecycle Management an eight out of ten.
*Disclosure: My company has a business relationship with this vendor other than being a customer: partner