Demand 'tasks'?

[kellykaufmann]

Our core need: To collect estimated costs across multiple teams (our 'field' person will have already checked boxes identifying which teams are impacted) for a Demand, track where we stand on each of those teams completing that activity, have these #s rolled up into an overall estimated cost across teams on the Demand form.

Our long-term desire: To have tasks/surveys (something!) auto-sent out at Screening Demand state to the rep (pre-identified rep which is standard) for each of those teams checked, and on the form are a bunch of cost fields (high/low contractor costs, high/low purchases, high/low internal hours * standard rate, etc) that will have a calculation which will then roll up to the overall estimated cost across teams on the Demand form. Have ability to track progress of each team.

Our temporary compromise: Implementing this full functionality is lower on our list until we climb out of our abyss of higher priority planned configuration changes. So we're hoping perhaps our field person can manually create tasks against this Demand for each impacted team for that Demand. But it seems OOTB, Demand 'tasks' don't exist. Correct? Is this an option? It looks like we could have PTASKS created from the Demand by the field person, and assign the PTASKS to the appropriate teams. But I don't know if I want to get into that habit

Any feedback/suggestions appreciated!

[Sangita Swamina]

Erin,

What we have done is created a new custom table called "Demand Costing" that extends task. Also we have custom fields on demand form for each team that will get impacted. Anytime when a "field" person checks one of these custom field, new demand costing record will get created and email the appropriate team's manager to estimate. Demand costing information does get rolled up back to the demand main form for the costs fields.

Thanks

Sangita

[kellykaufmann]

Thank you Sangita!

I would also like to point out the cost planning features built into Helsinki, which are described here: Combining PPM and Financial Capability to Provide a suite for Service Strategy . The features in Helsinki cover the functionality that we built at Bunzl.

[edavidso]

Thanks, Sangita (and Kelly!).   This sounds like exactly what I'm trying to do.   The only thing I think I would need to add is a way to track an SLA on gathering the estimates from the impacted teams.   I need to have the impacted team's manager complete the estimate within 5 days of receiving a request.   To Kelly's question earlier, I was thinking tasks might more easily accommodate that need but maybe there's a better approach.  

Kelly - I appreciate the links to both the white papers.   I will definitely check those out!

Thanks to both of you,

Erin

[Namita Mishra]

Hi Kelly,

This is an old post still I would like to update you that demand tasks will be available (OOTB) in New York release.

These demand tasks are mainly used to assign the task to different resources to get the resource estimate/ cost estimate, review completion etc.

Since these tasks are used to carry the work within the demand (planned for the demand), they won't be transferred to project on creating the project from the demand.

Note: These tasks are not the planned tasks hence they will not be exactly same as project task.

Thanks,

Namita