relate multiple demands to a single project

[kunalgoel]

Hi Everyone,

ServiceNow provides OOTB functionality to create a project from a demand. And Demand appears as a related list on the project form. When a project is created from a demand any resource plans attached to the demand propagate to the project. We have also customized our ServiceNow instance so that cost plan and cost breakdown records attached to demand also move to the project level when a project is created from demand using the UI action that is available by default.

Now our requirement is to have a many to one relationship between the demands and projects so that a single project can have multiple demands linked to it. This can be done by using the Edit button on demand related list on project form. Has anyone implemented this sort of requirement? and What are the Best Practices in this case - how should the cost plans and cost breakdowns be moved from multiple demands to project level. Should these be merged somehow. Or any other alternative approach can be taken?

[Brian Gadeberg]

Hi kunalgoel

I would go for another approach - depending on the reason for adding multiple Demand to one project - so please feel free to explain what you will achieve with this functionality (one demand -> creating multiple projects)

To utilise the baseline functionality I would either split the Demands into multiple and then create one to one relations. To gain the full transparency - I would then group them in a program. If that's not possible I would still use the baseline functionality and create one project and then use subprojects.

I would look at your current process for categorising and qualifying your demands. When qualifying your demands you might find it valuable to relate Demands with Applications and/or Services. Then the Owners will be able to help to either break one demand into multiple or making one demand the Parent og one or more demands as Childs.

If I would go with your demand I would have to add an extra functionality when using the UI action to create a project. You will have to add an ekstra step - asking for the project it need to be related to, and then you have to decide what to do with the data from all fields from Demand and Related list. E.g. should description from demand number two be appended to the current project. I would not worry about the related list since e.g. the costplan will be added to the selected project and the sum will automatically be recalculated, but moving related list also requires some scripting since it needs to end up on the selected project..

The baseline functionality in London (OOTB) does move all resource plans, costplans, benefits plans and budgets from demand to project. The reason is that otherwise the resources and financial plans will count double and thereby give the wrong picture.

Hope this gives you some inspiration

Brian

[howell]

Hi kunalgoel,

How about Programs?

You can have multiple demands and the project under it.

Regards,

Howell