Whether PegaRULES is implemented by a vendor team or an in-house team depends on the project. In some projects, in-house developers working on the application development can do it easily using the Deployment Manager, which is the more modern way to do it through CI/CD. That process doesn't need any input from the vendor or third party.

Another way to implement PegaRULES is by taking the Java files and the Java archival files directly from one system and then putting it on the other system, which is the traditional way to do it.

Sometimes, the client wants only Pegasystems to access the production environment; in that case, the Pegasystems team will handle the deployment of PegaRULES in the production environment. However, before production till pre-production, anybody can do it, particularly anybody working on the application, so there's no need for a third party. Technically, a software developer with two to three years of experience can easily do that till production.

The solution's overall deployment plan was for around a couple of weeks.

We handled the implementation ourselves.

We have a complete in-house team that performs the implementation and deployment for our customers. This includes creating new rules and definitions, determining which policies are required, managing the system, giving support, and release management.