Moving Past ETC?

[Legacy User]

Problem statement - Manual removal of past ETCs from the system

 

Process:
1. On every Friday, time sheets submitted in PPM. Time sheet submission updates the Actuals and reduces the ETCs accordingly.

 

2. On Monday, Project Managers need to check on the past ETCs (ETCs left in the previous week).
a. In case Actuals were charged then ETC was consumed.
b. If Actuals were not charged then ETC was not cosumed for that week and that shows as past ETC in the system on Monday.

 

3. The above activity involves, checking ETC for each resource on the team and moving it to the future weeks.

 

Impact of Past ETC:
1. Impact on Financials as Planned cost doest not reflect the correct figures
2. Financial Planning and Forecasting
3. Resource allocation for deployment

Is there any possibility to move Past ETC automatically to future weeks by writing down a particular logic?

[Legacy User]

Project manager can update schedule using OWB, CA PPM Gantt or MS Project - any remaining work (ETC) in past will be moved to future.

 

Expect updating the schedule can't be automated, if using OWB or MS Project - CA would have to replicate the scheduling algorithms used by each app.

 

There is an 'Autoschedule Project' job that can be set to run an individual project or a selection based on OBS unit.  Expect that this uses the same scheduling algorithm used by the CA PPM Gantt.

 

We've not used this, as we are still using (struggling) with MS Project....   So, give it a try and report back!

[mike2.2]

What's your MSP issue?

[Legacy User]

Big projects, in hierarchies, with large assignments on few (many times one) tasks.  The import to MSP process just chokes on this.  Better than in the past, but still so slow that it makes gaining adoption difficult.  The new XML version on 15.2 will work fine on small projects, but locks up on our mess.  Classic still works, but slow.

 

We did have one group officially switch to OWB.  Will see if it lasts as we are losing two key proponents, there.

 

Keep asking CA to test their MSP Interface updates on our stuff - if it works fast here, expect it will work anywhere fast.  No luck, so far.

[Jerin Sebastian]

Hi Divyanshu,

Automating the past ETC to future is not something I have done before but you can try a little bit with the fixed loading pattern. This will not help in moving the past remaining ETC to future but it will wipe out all the ETC in the past irrespective of whether the resource has entered actuals or not.

For example, the resource has 40 hours ETC for the present week and 40 hours for the next week. The resources enters only 20 hours as actuals so ideally there should be 20 hours remaining ETC for the present week. But when using Fixed Loading pattern, the complete 40 hours for the present week will be wiped out once the week is completed. 

 

Check this tec doc for more info on how the fixed loading pattern works. 

 

Logic for Calculating ETC for Timesheets and Posting 

 

Thanks,

Jerin

[Deactivated User]

Another work around is to post all timesheets. If the user has not created timesheet create one with zero hours and submit. Approve all and post.

That way the ETC is pushed ahead and not left behind. It does not fix the schedule though.

Another con is that somebody has to do that if it involves creating new timesheets and that it usually the PMO.