Built something you're proud of? Tell the story. A quick G2 review of App Engine or Build Agent helps other developers see what's possible on ServiceNow. Share your experience.

SPW: Can a planning item sit in more than one portfolio plan?

Baldeepbhambra
Tera Contributor

We are configuring SPW with two portfolio plans (Capex and Opex). Some of our planning items span both.

 

Can a planning item belong to more than one portfolio plan, or is it limited to one? If limited, how have others handled this?

1 ACCEPTED SOLUTION

phil_bool_unifi
Kilo Sage

Hi @Baldeepbhambra. I think it interesting that you choose to separate your Portfolio Plans by the cost type (Capex vs Opex).  Whilst this isn't the first time I've heard of this type of alignment, a much more typical use case would be grouping your work by their cost centers, business units, departments, products or strategic objective.  

The purpose of the Portfolio Plans is to have a single place where you can see all the work happening in your part of the business - whether it's a demand you're considering or a project that's already in flight.

This way, projects and demands can have both Capital and Operating costs recorded side-by-side, and so long as these are set correctly in the Project (you don't have to use Cost Plans to achieve this BTW), then the financials will be recorded separately. 

That'll mean you can see the Capex and Opex spend of a Portfolio Plan side-by-side from the planning view in the totals at the bottom, and a detailed period-by-period breakdown in the Finance view if you're using Cost/Benefit plans.

When Capex and Opex costs are recorded in separate records, you can quickly lose sight of the capital savings of changes to primarily operational projects, or vice versa.  

If your requirement is really to track approval of capex and opex costs separately, it may be that the features you need are already available in the investment funding plugin.

View solution in original post

2 REPLIES 2

phil_bool_unifi
Kilo Sage

Hi @Baldeepbhambra. I think it interesting that you choose to separate your Portfolio Plans by the cost type (Capex vs Opex).  Whilst this isn't the first time I've heard of this type of alignment, a much more typical use case would be grouping your work by their cost centers, business units, departments, products or strategic objective.  

The purpose of the Portfolio Plans is to have a single place where you can see all the work happening in your part of the business - whether it's a demand you're considering or a project that's already in flight.

This way, projects and demands can have both Capital and Operating costs recorded side-by-side, and so long as these are set correctly in the Project (you don't have to use Cost Plans to achieve this BTW), then the financials will be recorded separately. 

That'll mean you can see the Capex and Opex spend of a Portfolio Plan side-by-side from the planning view in the totals at the bottom, and a detailed period-by-period breakdown in the Finance view if you're using Cost/Benefit plans.

When Capex and Opex costs are recorded in separate records, you can quickly lose sight of the capital savings of changes to primarily operational projects, or vice versa.  

If your requirement is really to track approval of capex and opex costs separately, it may be that the features you need are already available in the investment funding plugin.

Tanushree Maiti
Kilo Patron

Hi @Baldeepbhambra 

 

Refer this community post : 

Can projects belong to multiple portfolios? 

SPM Nested Portfolios 

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin: