How to relate Technical Service to another Technical Service?

[mejasonroar]

In the CSDM, I can envision 3 Technical Services with corresponding tech service offerings.

• Server Hosting
  • Windows Server Hosting
  • Linux Server Hosting
• Network Services
  • Wired Networking
  • Wireless Networking
• Data Center Power Services
  • Battery Backup Power Services
  • Utility Power Services

That makes sense to me, however, ultimately, those 3 don't exist at the same level in a dependency tree, they're related and dependent upon each other. If I don't have power, I don't have network or hosting. If I don't have network, I don't have hosting.

I looked in the Tech Services page in platform and see no field for defining a relationship to another Tech Service. Is there such a thing or is there a better way to do this such that the outage of Power clearly shows all these other things being affected?

[mejasonroar]

I did not see that! I will poke around there and see if that provides what I'm looking for!

[Mark Bodman]

You wouldn't relate them directly, as this is where the ownership is established and bypasses the offering, where the commitments are defined. 

Backup Services should be pointed to the Backup Apps on the servers, they don't actually manage the servers.  Likewise the power, they provide power to the racks the servers are in, their location.  And so on.  

If you do want to relate them, you would through the offering lever of detail. The Service Builder will lead you through this in the Offering / Operational / Dependancies step of setting up Offerings.

 

[Chuck Sellers1]

I think Stig (above) is probably right about your manually assigning "depends on" (dependencies).

What you're asking is reasonable. There could be a technical service owned by a Service Owner for providing power and cooling in a building for the IT infrastructure. In fact, you could take it a step backwards and have different Buildings on the campus with different Facilities Owners for each building that offer all of those service offerings e.g. ....you are okay with how you defined it in my opinion. Services and their Offerings can be sliced and diced so may ways....SLA, geo location, QA, Dev, Production etc. etc. etc.

• Building 234 Data Center Services
  • Battery Backup Power Services (UPS and generator)
  • Utility Power Services
  • Air conditioning
  • Rack/Stack infrastructure
  • (and on and on and on)
• Building 123 Data Center Power Services
  • Battery Backup Power Services (UPS and generator)
  • Utility Power Services
  • Air conditioning
  • Rack/Stack infrastructure
  • (and on and on and on)

Each of those might have its own Service Owner, Managed by, Owned by, etc. I think you have a very realistic TECHNICAL service example if that is what works for your company. Maik (above) says you have the concept of a technical service wrong but I disagree. A technical service is offered to technical/IT staff and not to "offering to a consumer/customer". That is why there are at least TWO service catalogs usually... a business/user catalog and a technical catalog for requesting databases, VM's, backups, etc. 

Chuck