• Developing and updating
- an “Enterprise Project Structure”
- the underlying “Work Breakdown Structure” (WBS). The PRIMAVERA® project WBS structure must be aligned with the project WBS structure as defined in SAP;
- the detailed activities in PRIMAVERA® for the projects within the scope
- the codes assigned to activities in PRIMAVERA®;
- the resources to the activities;
- the activity network;
- the templates supporting project reporting;
- periodic reporting in the form of quarterly reports and other ad hoc reporting.
• Developing a baseline schedule in PRIMAVERA P6® for each of the (sub)projects. The “Work Breakdown Structure” (WBS) of the baseline schedule is based on the WBS as defined in SAP. Within this WBS structure, activities must be defined to the level necessary for efficient coordination, monitoring, control, and reporting of execution;
• Developing a baseline schedule in PRIMAVERA P6®
• Providing support and assistance in monitoring the work of external employees and contractual service providers
• Critically assessing, inventorying, and updating resources. Resource data is linked to activities and entered into PRIMAVERA P6®;
• Defining, entering, and managing resource data at the activity level in PRIMAVERA P6®;
• Organizing consultation meetings with project managers to update and optimize the project schedule based on data from the preparation tables;
• Monitoring the progress of execution
• Performing “Earned Value Analyses” (EVA) at project and program levels;
• Calculating performance indicators, including “Cost Performance Indicators” (CPI) and “Schedule Performance Indicators” (SPI);
• Periodic reporting of progress in the form of updated project schedules and S-curves based on updated data from PRIMAVERA P6®;
• Analyzing realistic scheduling scenarios.
• Identifying scheduling bottlenecks (critical path), ensuring correct and timely progress reporting, and flagging deviations.
• Identifying changes in project scope and assessing direct and indirect schedule-related consequences