Autospread Estimates

Autospread Estimate Data Summarization

• If there are several same WBS IDs with the same Resource Code, Resource Dept, Overtime field combinations and if the estimate type is all one type, then the lump sum value is added

• If summarization has different estimate types, then no records will be produced. It will be reported on the validation report.

• If summarization has different spread curves then the spread curve identified on the first existence is used.

• If summarization has different dates, then the earliest start date and the latest completion date from the set of tasks become the estimate start and complete.

How Supporting Autospread Estimate will impact BCWP and Milestone Import Options

Assumption

If the autospread value is at the task level then there can only be one resource.  If there is more then one resource, then everything is put onto the first resource.  This is then noted in the Validation Report.

BCWP

Scenario 1: 1 task per WBS

Task BAC field: add Autospread Value fields to the picklist

Scenario 2: Many tasks to 1 WBS

Nothing new

We suggest that you do not mix Work with Material budgets for the purpose of this calculation, i.e.: the tasks are either all Work or all Material but not a mixture of both.

Milestones

Scenario: 1 task per WBS (multiple lower level tasks that are flagged as MPM Milestones)

Milestone Weight is mapped to a Baseline field.  They want us to 'auto-weight' their Milestones.

We can only auto-weight Milestones if the budget exists at the same level as the 'Milestone' tasks.

Milestone Weight field: Add Autospread value fields to the picklist.

Scenario 2: Many tasks to 1 WBS

Nothing new