Best practices for using GRC: Advanced Audit and PPM Standard integration featuresUse Case: The integration of GRC: Advanced Audit with the PPM Standard plugin helps us in better managing and planning an engagement as a project in detail. This integration enhances the existing capabilities of an engagement and involves allocating budget, managing cost plans and resource plans and allocating resources to the audit tasks for the engagement. All this is achieved through the creation of an Engagement Project (sn_audit_advanced_engagement_project) record which extends the Project (pm_project) table and is the parallel object for an engagement to handle all the planning aspects. Guideline on role requirements: For a seamless way of using all features of the integration, it is advisable to assign the Engagement Project Manager (sn_audit_advanced.engagement_project_manager) role to the audit lead persona. The Engagement Project Manager role includes the sn_audit.manager, it_project_manager and resource_manager roles and it is only available when the PPM Standard plugin is installed. Note: For allocating Project Budget to an Engagement project, an additional role of it_portfolio_manager is required. Alternatively, users can directly enter the budgeted expenses on the engagement. Features available in GRC: Advanced Audit when PPM Standard plugin in installed: The ‘Plan with’ field on Plan form, shows an additional dropdown value - “Advanced planning capabilities”. When “Advanced planning capabilities” option is selected and the following prerequisites are met, an engagement project automatically gets created for the engagements associated to the plan Logged in user has sn_audit.manager + it_project_manager role (if the logged in user only has sn_audit.manager role then the engagement project would not be created even if all other conditions are met.)Engagement is in Validate or Fieldwork state.Engagement is currently in the Scope state but is later on moved to the Validate state by a user with the roles mentioned in step a. The “Enable Advanced Planning” button is visible, in the validate and fieldwork states, on the engagement, which is used for creating an engagement project manually . It is only visible to a user with sn_audit.manager + it_project_manager role, if a project doesn’t already exist.Engagement has an additional section “Project Details” which shows the Engagement Project that it refers to in the “Project” field. An engagement project can only be created for an engagement through steps 1 and 2 and can be accessed through this reference field based on security rules inherited from the Project (pm_project) table.When an engagement project is created, the following fields get copied over from the engagement to corresponding engagement project field(column names mentioned in brackets): Name(Project Name), Description(Description), Objectives(Objectives), Fieldwork planned start(Planned start date), Fieldwork planned end(Planned end date), Fieldwork planned duration(Planned duration),Parent plan(Plan).Engagement project gets closed when the state of the engagement changes to closed.An engagement project cannot be deleted if it is already tied to an engagement. It gets deleted when an engagement is deleted.Resource plans and Cost plans related lists show up on the engagement when it is associated to a project. It is suggested to have the sn_audit_advanced.engagement_project_manager role to be able to create and manage resource plans and cost plans. For a granular level detail on roles which can create/edit/read resource plans and cost plans, please refer to the product documentation. The product documentation links are also embedded in the info messages on top of the plan, engagement and engagement project forms for easy reference.The “Add Auditors” button on the Resource Plans related list allows users with sn_audit.manager role to add resources to the Auditors field on the engagement so that they can be assigned to audit tasks, when the engagement is in Validate/Fieldwork state. Planned and allocated resources in resource plans need to have pps_resource + sn_audit.user/sn_audit.external_auditor role otherwise they would not be added to the auditors field. As a prerequisite, apart from the role requirements, resource plans should exist and they must be allocated. Resources are not deleted automatically from the auditors field as a result of any action like cancellation or deletion of resource plans, change of resources etc. This has to be updated manually.When a cost plan is added, the planned expenses field on the engagements gets updated with the cost from the project and the field becomes read-only.When a resource plan is added and a cost plan is automatically created for it, the planned resources field on the engagement becomes read-only. Due to the associated cost plan, the planned expenses field also becomes read-only. The planned resources field shows the summation of the confirmed/allocated hours on the resource plans for the engagement and it gets updated whenever there are changes in the resource plans.When a project budget is entered on the engagement project, the budgeted expenses gets updated on the engagement.Any update to the planned expenses and resources and the actual expenses and resources, triggers an update to the corresponding fields on the plan if there is a plan associated to the engagement. Steps to use the advanced planning feature in GRC: Advanced Audit plugin: Login as an Engagement Project Manager.Create a plan with Advanced planning capabilities.Enter the budgeted expenses and resources(optional).Add new or existing engagements to the plan.Get an approval on the plan from the approvers.Scope entities into the engagements added to the plan, if not done already.Move the engagements, which were added to the plan, to the Validate state. This step creates an engagement project automatically.Update the budgeted, planned, and actual resources and expenses. This step is optional.Create resource plans and move them to appropriate states.Create cost plans.Add resources from the resource plans to the auditors field. Assign audit tasks to these auditors in the Validate or Fieldwork states.Create audit tasks in the validate or fieldwork states.Close the engagement once all pending items on the engagement are complete.Close the plan once all engagements associated to the plan are completed.