1.There is no official communication from Pega for withdrawal of AES. PDC is hosted by PEga on the Pega Cloud and cloud being future we expect our customer to utilise the full benefit of Pega Cloud and reducing their maintenance overhead. If you opt for Cloud, you do not have to provision and maintain the application. ga handles installation and upgrades, as well as fixing any bugs and maintaining the environment. This can lead to significant cost savings for customers. Pega PDC also gets frequent updates, whereas AES is only released once a year.
2 and 3. PDC is only for Cloud environment as per my knowledge.
PDC is available for on-premise/in-house as well as PegaCloud customers. There has been a recent change to the PDC service fee to promote adoption by on-premise customers. Details and public announcement will be coming soon.
PDC is a Pega hosted service. It is not a shippable product. On premise / in-house / private cloud systems can send data to the PDC service, but PDC is not available for installation on-premise. AES remains is available for on-premise / private cloud deployment.
PDC technically could provide governance and monitoring for Pega platform starting with PRPC 5.5, however older versions of Pega platform might send PDC sensitive data and are thus discouraged.
Monitored systems send ALERTS to PDC. An alert message includes the data on the PARAM page at time of Alert. Depending on application design, there might be private or sensitive data on the PARAM page. Starting with Pega 71 (and available by hotfix to 6*), Pega platform implements a "whitelist" to prevent platform from sending sensitive data to PDC. In the engine, there is an extensible list of core-pega parameter names (pyReportname, pyReportClass, etc) that are considered "always safe" and may be sent to PDC. All other parameters have value replaced by the literal [removed]. An investigator looking into details of a specific alert / exception in PDC will know that the parameter exists but will not see the value.
To achieve full value a monitored system must send PDC usage summary data, guardrail scores and database schema information. AES can gather that data by "pulling" it from monitored nodes (sending SOAP request to run PegaAESRemote services). As a cloud service, PDC can not connect to monitored systems, so monitored systems must "push" data to PDC. Pega7 ships with PegaAESRemote agents to push data to PDC.
AES may be customized - it includes a developer account out of the box. PDC is a service - no customization is available.
AES is scheduled for annual release / upgrade. PDC service is incrementally enhanced every two to four weeks.
Feel free to contact me directly with specific questions about PDC onboarding and setup.
The PDC service is now free for all customers. AES is licensed software though the license cost is nominal and the AES license is often included with the Pega platform or strategic application license. Contact your account executive to to see if you already have AES license and to give a price to obtain AES license if needed. Contact me directly if you want to get started with PDC