The initial setup is pretty straightforward. Once it's installed, it is easy. However, the installation needs to be installed by a professional.

The deployment depends on the modules you are setting up. Generally, one person does the deployment, and then you create all of the subjects that need to be deployed. 

The initial setup is simple and straightforward. It's not overly complex. 

I'd rate the process a four or four and a half out of five in terms of ease of setup.

The initial setup was complex.

I find it very easy, but I've been working with it for the last 10 years. I've been working with NetSuite for the last two years, and I've worked with Oracle E-Business for at least one year or two years. In terms of setup, I find JD Edwards very flexible.

I would rate it an eight out of ten in terms of the setup. It's difficult to set up, but once you know the software, you can go through it.

The initial setup of JD Edwards EnterpriseOne is highly complex.

The solution is not complex or difficult. It's very straightforward, very simple. 

We have six or seven people on board that are able to implement and maintain the solution. 

Since the client was so aggressive on time, it was done in three to four months of time.

JD Edwards EnterpriseOne's initial setup is very easy. We have created some migration tools for master and transactional data in an automated way.

Compared to other ERPs, JD Edwards EnterpriseOne's initial setup is more easy and straightforward.

The initial setup without a lot of customization is straightforward. I rate it an eight out of ten. However, suppose there are many customizations, and you want to tweak the system to meet your particular function, depending on the complexity. In that case, it may be complex, but it is straightforward with minimal customization and more towards parameterization and customization.

The period for the initial setup could take up to a year or more, depending on the complexity and availability of resources. If you're starting from scratch and don't have a JD Edwards Enterprise One solution and want to implement it in the organization, configure it and set up the system to be functional.

The implementation process is pretty simple. I can relate it to the E-Business Suite, as I've also a long-term experience in E-Business Suite. JD Edwards is more simple than the E-Business Suite to set up and make work. On the other hand, if you have a very large operation and your operation is multi-language and multicurrency, then the E-Business Suite is better as it has more opportunities to set it up for multicurrency and multi-language. That said, in daily practice, JD Edwards is reasonably easy to set it up.

In terms of maintenance, for the application management team, for a normal instance of JD Edwards, then you could expect something like, let's say 500 users. Then there would be one or two application managers that are managing an application of that size - and perhaps one database manager.

It’s easy to initially set up. It’s not hard at all.

I’m not sure how long it takes to deploy the product.

The solution is easy to set up. It's not overly complex or difficult. 

It is not very straightforward. You need a very technical person to do that or assist you. The installation is okay, but when you're implementing, you have to do adjustments to make it work for your business. So, it does require a little bit of technical expertise. You might need help from Oracle as well. 

The installation takes a few days, but the implementation can take a few months.

In terms of maintenance, in the current team that I'm working with, there are about 25 to 30 people for IT support for 1,000 users.

The setup of JD Edwards EnterpriseOne difficulty depends on the module being installed by the client. The setup does not take much time but the implementation of the modules can take approximately 18 weeks to complete. If there are multiple modules being implemented it can take approximately six months.

The initial setup was complex. Currently, approximately 10 to 20 individuals within our company are using the solution.

It is complex. In terms of deployment, you can get it all up and running within a month, but its implementation is a long process. It depends on the size of the organization and the number of processes they're trying to implement. So, implementations can take anywhere from six months to two years, depending on how big the organization is.

The number of staff required for deployment and maintenance depends on the implementation. In terms of their roles, there are system admin and developers. Then there are application consultants or business analysts. They are the people who have expertise in a particular domain such as financials, supply chain, or manufacturing. So, it depends on the different processes that you are going to set up in JD Edwards. You could have an organization that is only implementing financials, and in that case, you only need one financial SME, but if you have an organization that is going to implement financials, manufacturing, and supply chain, you're going to need SMEs for these areas.

Since I have been working with the solution for around 15 years, I find the initial setup and configuration simple and straightforward. We need basic experience and domain knowledge to easily understand the configuration and setups. I rate the initial setup a nine out of ten.

The initial setup can be a bit tedious. If we have to set the hang-up, the process of scrubbing the tables is also tedious. Therefore, we need someone with the necessary skills and experience. However, if we have experience in JD Edwards, the initial setup should be manageable.

The deployment time depends on the organization. If the prototype and business processes have already been completed by the company, then we will only need to manage the project for them to go live. However, this is especially true for recent cases. It takes a bit of time to do an enterprise deployment, so if we only have to do financial and procurement, we can expect it to take four to six months. It also depends on the customer's readiness and we require eight consultants for a medium-sized deployment.

Regarding the initial setup of JD Edwards EnterpriseOne, its difficulty level depends on the size of the company and the business requirements. Still, JD Edwards EnterpriseOne is not a complex ERP system to set up.

My company has no complaints about the setup, so it's okay. It's a nine out of ten, setup-wise.

The initial setup of JD Edwards EnterpriseOne is straightforward. However, it could improve.

I rate the setup of JD Edwards EnterpriseOne a three out of five.

Provided you understand the framework, it is quite easy to install and set up. After this, it is easy to maintain and manage. The length of time required for deployment depends on whether you have a proper blueprint because all of the processes are embedded. With all of the blueprints available, for a new installation, it can take between six and nine months.

The deployment will also depend on the state of your data. It may already be clean, or it maybe needs to be pre-processed before migrating. I would say that every situation is unique. You can do the majority of the setup offsite, just by getting all of the business processes in advance. Then, when you start UAT and other testing, you go onsite and go live. It's not that complex. I came from a financial background and moved into the IT sphere, which was not that difficult to do.

The maintenance is done with our in-house team. Normally, you have one person for every module. However, on the technical side, you only need one person because everything has been automated and is orchestrated to do a lot of the work for you. It just pops out some reports and alerts as it monitors the system for you.

Originally, there were some complications with implementation. But now, it is very simple to set up and get everything going in a couple of months. Oracle has done tremendous work on improving the issues that we were facing on the J.D. Edwards front, and they fixed all those issues. Now we do a straight forward, simple plug-and-play installation, so there are no problems technically now.

I was not involved in the deployment process. I do work on product development. I'm the head of JDeveloper.

Deployment of the product is handled by a different department known as the CNC department. CNC consultants are more aware of it. 

We have separate teams, for the product deployment. 

There are some maintenance activities that our CNC team has been doing for a long time. I'll give you an example, of maintenance activities. The client may be using a specific product version, and there may be some ESUs or stars, which we, or a CNC consultant, may apply to that product upon function approval.

Those ESUs will sort when there is consolidation or when there is a package that includes some of the additional functionality for any particular object that is not present in the version that the client has been using. In that case, we identify the ESUs and stars to which we must apply in specific objects. Accordingly, we accept those functions and approvals. We, as technical personnel, reviewed them, the code that ESU and the stars requested, and upon function approval, the CMC consultants applied on those objects, the list of objects wherever it is required. This is the type of maintenance that CNC workers perform on a regular basis.

The initial setup is complex because you're going up on the cloud. Coming from where we were before to where we are now took us about two-and-a-half years.

The initial setup is somewhere between straightforward and complex. It was not straightforward, but it was done a while ago and would likely be simpler these days. We used a third party for our implementation 12 years ago. We now have 600 users. 

Setup is simple. For deployment, we used eight people to run the software.

It is straightforward. I learned it in a week to ten days and I am doing the purchasing orders as well.

The setup was absolutely straightforward. It was mostly on the end-user paradigm from using the Word software (green screen) to a web-based application.

There were implementation issues, which were more related to the customization and setting up the country-specific parameters. When the system was set up correctly, passed the UAT, and we were weeks in production it seems to be very stable.

The solution could be easier to implement. However, the complexity was in our internal processes meeting our country's requirements. Every country has a slightly different process, taxation, and rules. That was the difficult part, not the solution itself. I expect our experience would have been more or less the same with any ERP, such as SAP, Navision, or Dynamics.

The initial setup took about six to eight months, so it was accelerated. It was essentially all my time for about six or eight months, but it came in on time, on budget, etc., so obviously a lot of thanks to our US office for all their help in getting it done. They've used it for many, many years, so it was just adding a new branch into the software and getting us up to speed. It could have been complex, but because our US office was already using it, it was much simpler.

At the time, JD Edwards had completely rewritten their software, and I understand that now. I hadn't been exposed to it before. It was very cohesive at the time, I thought, for software. Sometimes you use software and you can almost tell, "oh, this module was bolted on and re-patched, but it clearly was written by a different group with a different focus." Whereas, JD Edwards at the time was all written fairly together with a new vision. I would say that the implementation was pretty good.

I cannot set up EnterpriseOne on my own.

JD Edwards is a configurable software solution. They provide you with the ability to be able to configure the software so that you can run your business in the manner that you choose. It could be summarized to say, "You don't have to change the way you run your business to run with the software. It's the opposite. The software wraps around your business." It's as complex or as straightforward as you make it.

We have a lot to do, and I'm new to the company as I've only been there for two months. Because it's a brand-new company and it's a robust advance in our software, we're going to stay away from customization as much as we can. We want to keep it as vanilla as we can.

But from what I've seen, it's straightforward because we're keeping it more vanilla, and that's one of the reasons that for those of us who've used JD Edwards, it gives us the opportunity to do a lot more and we don't have to customize as much. We want to stay away because when we upgrade, as we will, then you have to take your customizations with you and we want to stay away from that as much as we can.

It's relatively straightforward to configure. We only wanted core financials at the time. We've grown since then, and as we've acquired more companies. As our business has grown, we have added a lot more to the solution and a lot more complexity. And we've been able to do that quite efficiently over the years, and that's one of the good things about JD Edwards. You don't have to keep revisiting the box and  the instruction manual, because you can just add stuff as you go.

The initial setup is not complex. If you just follow the instructions then the set up is fine. You just need to grasp the terminology that they're using and the structures of the data and the cloud, and follow what they tell you to do and you'll be fine. You don't really need to be a rocket scientist, there's a logic that you need to apply.

I don't know as I wasn't involved in the setup. I haven't heard that it was particularly complex.

The installation is one of the best, it is very easy to install.

The initial setup was mostly quiet.

The setup was complex for the most part. In a few cases, it was simple.

EnterpriseOne can be multi-platform. That means you can have two servers on Linux, one on Windows and the last one could be an AS400. This complexity cannot be provided for by another product. My initial setup was complex, but the architecture was very complex, too. After that, I have had multiple easy setups. The best way to achieve this is to choose only one OS for your servers; otherwise it could be a nightmare.

Setup can be complex. I have worked with complicated products such as JD Edwards, considering their variety of options to configure and variety of providers involved. The secret is to have the proper documentation and support from the manufacturer and of course, constancy.

This product is an ERP tool. The level of complexity depends on a lot of variables. Generally, it is straightforward.

Straightforward in many ways, defining COA, master files, and setting up parameters.

The setup was very complex, since we are still using the AS400 platform with a DB2 database.

Neither the installation nor the implementation is straightforward. However, it quick and easy as compared to other ERP products, such as SAP.