The setup is related to the admin role. I can install the solution but not get into the admin role. However, from a technical point of view, integrating PeopleSoft is not complex, as I have been working with PeopleSoft for over fifteen years. We can integrate PeopleSoft with third-party systems.

As for the current market, most companies use the REST API in PeopleSoft, which supports all kinds of applications such as XML, Java, JSON, plain text, or HTML. It is why REST API is widely used in mapping with mobile applications and third-party systems. However, some organizations still use SOAP for security reasons, as SOAP supports SSL for secure transactions like banking.

The initial setup of PeopleSoft can vary in difficulty depending on various factors, such as the complexity of the organization's requirements, the expertise of the implementation team, and customization.

If you know PeopleSoft, then the setup is straightforward.

If you go to the PeopleSoft education sector they make it complicated and people don't understand.

It's important to provide consultants with proper training. Often the implementation is completed incorrectly and they blame the solution. It's not the solution, rather it's the people who implemented it incorrectly. If it's not set up correctly then it will take the software forever.

The initial setup is secondary. First, we need to identify the setup phase of which enterprise. The setup phase is very easy right now in today's technology. The setup can be done in a day.

The solution is deployed on the cloud.

The steps for deployment depend upon the size of the company.

For deployment and maintenance, not many staff members are needed. Whenever we require any feature, we just pick it up and drop it out. It's a very easy tool. So, there is no technical dependency on an IT team.

It's quite straightforward to implement the solution. There are a lot of configuration choices; however, it's very simple and straightforward when you understand what you're doing.

The time it takes to deploy with any of these systems is based on the client, not the software. If you have a client that knows what they want to do, it's quite easy. It's quite quick. However, it just depends on the mindset of the client. Do they work in an agile way, or are they still stuck in waterfall? A lot depends on the experience level and maturity of the customer's processes.

There's always maintenance. Oracle releases two or three service packs a year to upgrade. They went from a big release model to a small service pack-driven release model. There are now functions and new features that get dropped in every six months or every four months. You have to be aware of that if you want to take advantage of the new stuff. 

I would rate my experience with the initial setup a six out of ten, with ten being very easy because the setup is not quite easy enough.

The deployment took a few days. 

I can't comment on the initial setup of PeopleSoft since it was configured in my company's environment a long time ago.

The solution is deployed on an on-premises model.

For the deployment process, you need something like Oracle OEM that can assist you with the development, configuration, and installation. If you have enough expertise with the solution, then you can do the deployment by yourself.

The product's initial setup phase was complex and cumbersome, but I managed it ten years ago.

Installing PeopleSoft is relatively user-friendly. It is often considered a straightforward process, making it easy for users to get the software up and running. The time required for installing PeopleSoft can vary depending on the specific modules and components needed. For a basic installation, it typically takes just two to three days, but it is important to note that implementation, which involves configuring and customizing the system to meet an organization's specific requirements, is a separate and often more time-consuming process. Deployment and configuration of PeopleSoft varies significantly based on factors such as the scope of the project, the number of countries involved, and the modules being implemented. There is no standard timeframe for deployment, but it typically ranges from a few days to a few weeks, with larger and more complex projects naturally taking longer to complete. The number of people required to deploy PeopleSoft depends on various factors, such as the number of modules, employees, currencies, and countries involved in the project. It is a highly variable question and doesn't have a one-size-fits-all answer. The size and complexity of the deployment dictate the team's size and composition, so it is different for each case. In my experience, maintaining PeopleSoft is relatively easy. I haven't encountered significant difficulties, and it is not a major challenge to keep the system running smoothly.

The initial setup is straightforward.

I was typically more involved in the change management aspect, keeping leadership informed and working as a liaison between the developers and users. I'm also involved in the training aspect of implementations. 

The solution's initial setup is not straightforward. Additionally, PeopleSoft is not a cloud-based solution at present. Therefore, if Oracle focuses on converting PeopleSoft into a cloud-based solution, it would be really helpful for our company. Regarding the time required for deploying the product, if one considers PeopleTools upgrade and requirements, it usually takes around a day or two since the changes in the features of the solution can provide for the solution's upgrade. This way, one can have complete control over the solution. We used PeopleSoft Change Assistant to deploy the solution.

We have a technical team for deployments and maintenance. So, compared to other PaaS products where you don't have any control over deployment, with PeopleSoft, we have total control over the deployment process, including the timing and method of deployment and the ability to perform audits on the deployment.

The initial implementation is complex. Everything is complex when you first start using a new system. If someone tells you it is not complex, they can not be telling the truth. However, the most recent upgrade from 9.1 to 9.2 was pretty good.

Deployment takes a minimum of six months and I speak from the vantage point of someone who has a year-and-a-half of experience with my company, primarily in the area of implementation. 

The initial setup is quite complicated. It requires knowledgeable and experienced people to set it up. It took a whole day to set up and two or three days for training of end users. 

Some clients are hesitant to get rid of some of the customizations that they are used to and being able to pick up the versatility provided by Oracle to make their life easier. They are hesitant to adapt to the system and then they won't be able to pick up and go on cloud. The deployment for version 9.2 took about four to six months, depending on how large the project or the scope is. Deployment on cloud depends on if they are going by face to face, and it will take anywhere from three to four months because they give patches. These patches are pretty straightforward. 

The initial setup of PeopleSoft is easy.

I rate PeopleSoft a four out of five.

The implementation is not difficult. The full deployment takes approximately one year.

It was complex. It was done 15 years ago. I wasn't there when the installation was done, but it was quite complex.

Initial setup can be complex without training or use of consultants. However, once you have invested in training, the setup can be straightforward with the use of consultants. I definitely think you need to have a company ‘expert’ in every module who knows the policy and procedures and is able to ‘think’ in both a functional and technical mode to work with consultants.

We pledged to keep the setup “vanilla”. In what ways? Defining the Master data for each application is critical to successfully configuring the systems to operate seamlessly daily, and to manage business dynamics like M&A, international operations. Reporting was our biggest challenge that was not "delivered" by PeopleSoft.

Initially, it was complex, expensive, and it was done with the help of an external consulting company since the expertise was not there and it was a decentralized organization. They also had to implement payroll in 20 plants or so at the same time with a custom T&A application and hundreds of requirement gathering sessions and hundreds of training sessions. If we had to do the same thing, it would be a lot different; we know what is required and how it needs to be done.

The initial setup is straightforward. It is not complex.

The initial setup is straightforward. It is not complex.

Deployment depends on the size of the organization. If you are just installing it, it can take a week, but if you are installing, and doing a quality implementation it can take five to six months, which would include doing analysis, customization, and testing.

We had a large vendor team help us with the initial setup, and then I helped my team with the transition, making sure we were trained and ready to support it. But I didn't physically move code or anything like that myself.

We actually started the project for initial setup about five times because the clients wanted everything. We asked for specific functionalities because it really can do anything, but you can't just have the entire world. So the vendor came in with a solution, and we went with it. But the vendor team was huge and costly, which we can't have going forward.

We're hoping now as we're upgrading to the next version that we'll have our own in-house resources to do the work ourselves. But the PeopleSoft setup was so big with so many other pieces we needed for reporting that it took a long time to design with many parts that were extras in the downstream part of the system.

In fact, the integration with all the interfaces in our system was probably the hardest thing. We have over 80 different systems that feed our PeopleSoft application with around seven different formats of the general ledger. So from changing the old, very cryptic systems to the new layout has been a challenge. We've bit the bullet on doing that, though, and it's a lot to maintain.

The implementation of PeopleSoft is quite complex and is not as easy as other cloud products such as SuccessFactor or Workday.

I rate the ease of setup a seven or eight out of ten. It takes us weeks to get the proper structure implemented.

The initial setup is straightforward and can be completed quickly, though a totally new implementation may take a little longer.

The initial setup can be straightforward or complex. We've dealt with both types of implementations. It really depends on the client and their requirements. 

The setup was complex because we have a union and our benefits are so complex.

The initial setup is rather complex, depending on what you want. If you want to set up a RAC environment, then it's more complex and you need additional hardware. You need a skilled Oracle DBA. If you keep it to a single INSERT, it's simpler.

As I'm a user, I remember providing my input on what do I want to see in the product. That happens at the start of launching the product, as well as when the new roll out happens or the planning happens. In that sense, I'm involved in terms of the configuration, layout of the fields, providing user feedback. All of that has been taken into account.

Initial setup was complex.

The setup was easy and straightforward.

The initial setup takes a long time, as does any cloud-based solution.

This product is quite easy to install, although I'm not sure how long it takes to complete. It integrates with LDAP services and with Microsoft Exchange Services, so I think that it takes between two and three days.

From a technical perspective, it is not a problem for the end-user to deploy it.

The setup was complex, as it has multiple configuration changes.

It depends on where your customer is coming from and how willing they are to change. I've had clients that came from a PeopleSoft mixed mainframe, and they were really on board and really wanted that change. They did a lot of training and it went very well. I've also had clients who came from J.D. Edwards that was totally customized. They loved it. They didn't want to change, and it's been hard overcoming the resistance.

I wasn't part of the team that originally implemented it, but I was involved in upgrades. I think it was extremely difficult. I wasn't on the project, but I was there when they needed me, and inserted me where they needed me. We hired IBM to help us do that upgrade, and I think there were a lot of pain points. It was kind of a two- or three-year process. I think there was good and bad, but not perfect, but it was difficult.

It takes some time in order to set it up and to implement, make changes, and deploy it to our users.

The initial setup was straightforward for us.

Initial setup was complex, mainly due to the needs of our business process. We had IBM as a consulting firm joining us and helping us install it, with an army of people.

The setup was complex due to different components.

Yes. There were very important jobs and processes that need to be setup.

It was a complex setup. There were a lot of man hours involved as it was a big project.

The initial setup was straightforward and didn't give us any trouble. However, when we had to integrate many other modules, it was an extensive process.

It is complex because it needs to be properly configured to meet the needs of the organization.

The complexity of the setup and configuration depends on the business problem that we have. If you are a seasoned guy – a PeopleSoft consultant, a functional or solution architect – and you know the problem, you can fix it quickly. I think PeopleSoft is very reasonable. They have designed their system very, very well, keeping in mind the best of the best business processes all over the world, catering to verticals in all the industries. I find it reasonably good. I don't find it too complex, because you're expected to be an expert in that. Not everybody can go and do it.

Initial setup complexity depends on the user’s needs; if the requirement from the client can use the standard setup, then the implementation will be straightforward, but if there are many requirements that cannot use the standard setup, then setup and customization will be complex.

The implementation was done before I was at the company, but I haven't heard that it was particularly complex.

Initial setup is somewhat complex. You have to know what your business is and what you want to do.

Most businesses that use PeopleSoft can easily make the system suit their business, so I think it's flexible, but it adds complexity to the setup.

The initial setup has a moderate amount of difficulty. Deployment took about eight to ten months. For maintenance, we need around 25 to 30 people.

There's a moderate level of complexity in the initial setup. It's somewhere between easy and difficult.

The initial setup was done before I started, but I haven't heard about it being particularly complex.