Services
- Last UpdatedApr 10, 2025
- 2 minute read
The AVEVA™ Production Management environment uses three different Windows services for communication between components.
-
AVEVA™ Production Management Service
-
IIS service
-
Workflow service
AVEVA Production Management Service
The service is a Windows service. This is the primary service for most AVEVA™ Production Management communications. You can stop and start the service with the Service Manager. You can also manage the service through the Windows Service Manager.
IIS Service
The IIS service is an integrated feature of the Windows operating system. This service needs to be enabled.
AVEVA™ Production Management uses the IIS service for web-based communications, such as to the web-based client and web-based diagnostic tools.
Workflow Service
The Workflow service executes the Plant2Business integration scenarios that are configured in a project. For more information about Plant2Business, see Plant2Business.
Because integration scenarios can involve large volumes of data, these integrations run in a separate Windows Service to reduce the memory pressure on the primary AVEVA™ Production Management service. The Workflow Service automatically starts and stops along with the service.
The Workflow service uses integrated security that is mapped back to a valid AVEVA™ Production Management user.
Service account for Workflow service
AVEVA™ Production Management provides the Windows credentials to the Workflow service that were entered on the Service Account screen of the AVEVA™ Production Management installer.
Both AVEVA™ Production Management service and Workflow service use these same credentials. Specifically, for Plant2Business functions to communicate with AVEVA™ Production Management, the value of the Identity property on the AVEVA™ Production Management user, must be the same as the Windows identity.
