The Slip process in Deltek Cobra allows the user to move either a project or one or more Control Accounts either forward or backward. There are various cases where this process would be potentially useful, but in general it can be assumed that its likely use would be prior to development of a project schedule. This is due to the fact that the schedule typically drives all baseline and forecast dates once a project goes live.
A likely scenario would occur during the proposal phase, where planning is occurring directly in Cobra. While many organizations utilize specialized costing software for this purpose, Cobra does an acceptable job in this realm and is used successfully by many organizations.
That said, even during the proposal phase, it is strongly recommended by the Cobra Guy that a schedule be utilized, as the logic (Predecessor/Successor relationships) is critical to the time-phasing resources. In the end, the Cobra user can decide when the Slip process might be useful.
The Slip process will not slip dates prior to the Status date. Additionally, Cobra will only Slip Planned (Not yet Started) Control Accounts or Work packages within a Control Account. In other words, the user can select a Control Account that has an Actual start date, but Cobra will only Slip the Work Packages within that Control Account that are Planned.
The same rule applies where the Slip process is applied to the total project. The process will only slip the dates and resource assignments for those work packages that are planned and ignore those work packages that are in-progress or complete.
The following are the general rules that should be understood prior to performing the Slip process:
- All dates associated with the Slip are to be after the status date. In other words, if the existing work package dates or the dates the user wishes to move a work package to are prior to the status date, Cobra will not process that change.
- Cobra will only Slip work packages with a status of Planned.
- Work Packages within a Control Account that have an Actual Start Date can be Slipped if its status is Planned.
- An entire project can be Slipped. Any Work Packages that are either Complete or In-Progress will be ignored.
- More than one Control Account can be Slipped at one time.
- The process will slip only Budget and Forecast Cost Classes.
- If the “Days” option is selected as to how many days to slip, Cobra will calculate calendar days, not working days.
- The Slip process can move data either forward or backward in time, although nothing can be moved on or before the project’s status date.
The Slip Process
Important Reminder! Whenever executing a process that will change the project data, generate a project Backup first. Cobra does not have a reverse gear.
In this example, the total project will be Slipped. The first Control Account dates can be seen for Budget and Forecast prior to the change.
Under Processes, launch the Slip process by double-clicking on the icon.
Select the appropriate project, then “Next”.
In this example, the total project option has been selected. Optionally, one or more Control Accounts can be selected. “Next”.
A slip of 15 days has been selected. This will move the budget and forecast dates for all Control Accounts and Work Packages 15 days to the right. “Next”.
No other selections are required. “Finish”.
Once the user has received the coveted green check-mark, the results can be reviewed.
The budget and forecast dates have both moved out 15 calendar days. The resource assignments have also been adjusted accordingly.
After completing the Slip process, it is recommended to review the time-phasing of both the budget and Forecast cost classes to assure the spread aligns with the start and finish dates. This may be an issue with the first and last periods for short duration slips.
Also consider that moving resource assignments will likely have a cost impact, as rate escalation is commonly utilized for labor rates and burden rates often are forecast to change over time as well.
The Slip process is useful in certain circumstances, but is not likely to be of much use on a live project, where time-phasing is best updated via the project schedule.
Always review the data after executing this process. Never trust your software to do what it says. Check the results to assure the intended result has been achieved.