Roles and responsibilities

[Bruce Hadley]

We are preparing to start the journey through the CSDM maturity. How are other clients that have implemented this framework assigning responsibilities to keep it correct. I don't see this as an admin responsibility. Do people make this part of the ITOM department? Is it more ITBM resources and the same resources that manage APM to manage their separate portfolios?

Any insight on who other companies have assigned as operational owners will be appreciated.

[Mary Vanatta]

Bruce

When looking at the "Crawl" the Business Applications table is populated.  But would recommend only populating minimal attributes like "Name, IT Application Owner" and Architecture Type (helps with modeling the service).  

Then it is ready for the "Fly" stage when APM should be implemented. 

In the Crawl stage you would implement the "Application Services"  which is a logical CI, and here we want to capture the Name + Env (recommend sticking with Prod env's first) 
 Then make the Consumes by::Consumes relationship from the Business Application to the Application Service.  

[Chuck Huntley]

My thought is to split it up by domain.  For example, our Digital Business Office (ITBM focused) would own the Design domain and our Infrastructure team (ITOM focused) would own the Manage Technical Services domain.

[Mary Vanatta]

Chuck 

Basically the roles or "personas" are broken out by domain.  The application service owner is typically someone in the IT world (orange) vs the EA or "business" application owner in the Business world (blue).

Many organizations are now realizing the benefits to becoming more "service-centric"  this is a great way to start that journey.  

[Bruce Hadley]

Good suggestion Chuck. 

Thanks.