Model Planview Business Applications

Kelli Fellows
Tera Contributor

I am looking for help modeling our Planview applications.  For our Business Applications, I am trying to decide if we should have...

 

1. Planview Platform as "Platform Host" and Planview AgilePlace, Planview ProjectPlace, Planview Portfolios, etc. as "Platform Applications". 

 

OR

 

2. Only have Planview AgilePlace, Planview ProjectPlace, Planview Portfolios as "Web-Based" Business Applications. 

 

What is your recommendation?  Attached is a model of option 1. 

3 REPLIES 3

Mathew Hillyard
Giga Sage

Hi @Kelli Fellows 

It's good to be able to pull the platforms out of your Business App inventory so I would choose option 1.

If you don't want CI relationships or the platform host/platform application functionality then you can use the Platform field and create a choice for Planview.

There is also the option of the Application Family, but that is more for an ecosystem of Business Applications.

 

I hope this helps!
Mat

Jonathan Schnei
Giga Guru

A further clarification - in the CSDM there should not be any CI relationship between business apps. The CI Relationship Depends On::Used by can be used between the appropriate App Services (Service Instances). On the Business Application, the functionality to model Platform and Platform apps is using the Architecture Type field. On the platform Business App set Architecture Type = Platform Host to flag the app as a platform. On the various apps on the platform, set Architecture Type = Platform App which will reveal the Platform Host field where you select the Business App record that is the platform. Or/And you can use the Platform field to select a generic platform (Platform field) that an app runs on in the case where the app runs on a platform, but is not a platform app on the platform.

 

I am in agreement with Mat for how to model your planview.

Uday Damaraju
Kilo Guru

@Kelli Fellows One size doesn't fit all 😉
In my opinion whether it is 1 or 2 also depends on how your organization manages these tools from a lifecycle and business capability perspective. Both can be argued with their respective rationale behind.
For most mature organizations 1 suites (Platform Host/Platform Application) is the long-term approach for the Design domain.

I try to choose by answering following questions: 
1. from maintenance & support perspective: Done by a centralized team or different teams? My answer: Off-late its mostly a central team.
2. Authentication within your Org? - SSO or not. My answer: mostly its SSO. Makes your CSDM Technical service layer definition better with 1 endpoint. 
3. GRC,SecOps lense Do you need to perform separate security audits or risk assessments for ProjectPlace vs. AgilePlace? or 1 at planview? Assuming separate audits not required (that's how my last client did it) 

If your answers are in line,  choose 1- Platform Host & Application is the way to go for your CSDM journey.
choose 2 if your Org wants value autonomy over consolidation.
 

 

"Hope that helps, if it does- please accept the solution and mark it helpful"
BR, UD