Profiling Actual v Planned savings - 2007
-
Tuesday, April 24, 2012 9:18 PM
Dear All – any views / guidance on the following I am trying to do would be greatly appreciated.
I have a project that is expected to create savings of £620,000
It is expected that the tasks associated with the project will create a savings profile of:
Apr (£50K), May (£80K), Jun (£80K), Jul (£30K) Aug (£70K), Sep (£30K), Oct (£10K), Nov (£10K), Dec (£50K), Jan (£90K), Feb (£50K), Mar (£70K)
The finance Dept will provide me with the savings as they are ledgered each month end and so I will have as set of actual savings against the project.
I appreciate that MS Project is not a finance system. The tasks in the project are important for me to assess and manage the likelihood of savings delivery. However, is there a way of me associating the planned (and then actual) financial profile with the project?
There is a possibility of numerous savings projects like this one being created and so the firm anticipate being able to merge up the info into a cost improvement programme. Keeping this in one system / area is therefore attractive. We have access to an enterprise project environment.
The alternative is spreadsheets linked to project files and then merging the spreadsheets each month. Not very elegant.
Best wishes,
Chris.
All Replies
-
Tuesday, April 24, 2012 9:53 PMModerator
You might play around with the idea of using the fields in one of the baselines to store this Savings data.
If finance says that Task X will save you 10K in April and 15K in May you could open a Task Usage view and set the timesale to months. Then insert (for example) Baseline9Cost. Then you could enter the 10k and 11k for the correct months.
the downside to this is that you would not get a rollup to the summary task level or project level but some not very difficult VBA code could take care of that.
Mess around with that and see if comes close to what you want.
Brian Kennemer - Project MVP
DeltaBahn Senior Architect
endlessly obsessing about Project Server…so that you don’t have to.
Blog | Twitter | LinkedIn