Using Graded Approach for Schedule Adherence
Graded approach to schedule adherence is a method for tracking adherence using four distinct levels of work scheduling (A, B, C, and D).
The levels of work scheduling are:
- A (Hourly): Used when you require the most control, adherence, and management oversight. Reasons include risk (probability safety analysis/risk assessment), personnel safety, or other significant concerns. Users must finish Level A activities within one hour of the target planned finish date.
- B (Daily): Used for work requiring multi-discipline coordination, significant tagouts, or risk significant work. Users must finish Level B activities on the same day as the target planned finish date.
- C (Weekly): Used for non-risk significant and routine work that does not require support from other work groups. Users must finish Level C activities within the week of the target planned finish date.
- D (No Tracking): Used for housekeeping, shop work, and other types of work that have no impact to the plant. Level D activities are considered “fill-in" work and are not tracked for schedule adherence.
For graded schedule adherence, ensure history exists for the project as of the scheduled freeze date and T-0 baseline date for the week the STARETL process will run.
During T-0 for a given week when you run the STARETL process, the Baseline Planned Finish Date (as of T-0) and the Schedule Freeze Planned Finish Date (as of schedule freeze UDF) for the activities will be captured. You can use these dates along with the assigned adherence grade to calculate the graded schedule adherence in CIC Analytics.
To configure graded schedule adherence:
- Ensure you have enabled a project for Work Process.
The sys_workprocess=WORKWEEK, sys_scope_freeze, and sys_schedule_freeze UDFs are populated and History Level is set to Activity.
- Ensure history exists for the project as of the scheduled freeze date and T-0 baseline date for the week the STARETL process will run in CIC Analytics.
- Code activities using an Activity Code or UDF to identify the adherence grade (A, B, C, D).
For example, in the sample data, Activity Code 11 (Schedule Adherence Priority) is used.
Related Topics
Configuring P6 EPPM Projects for CIC
Configuring User Access for P6 Analytics Module
Selecting P6 Projects for CIC for the First Time
Enabling History and Publication Services Settings for P6 Projects
Enabling Slowly Changing Dimensions for P6 Projects
Adding Additional Financial Periods
Configuring P6 EPPM Projects for Burn Down Calculations
Configuring Projects for Work Planning Calculations and Metrics
Enabling P6 Location Data for Mapping
Last Published Friday, December 8, 2023