Understanding TSO - Technical Services and Deliverables

[ivaroen]

Hi all 🙂 

I am trying to get my head around the Technical Services and TSO - and TSO deliverables to an order. 

Example. I am ordering a server of type Linux/Unix - I have a technical service of type infrastructure Linux Management that is the owner of the technical service and they have a technical service offering - Linux Servers that is available for the technical consumer.

Given that "EVERY operational CI should be associated to ONE and only ONE owning Technical Service" the additional requirements to a server must be set up as either commitments to a TSO or as Technical Services set up as deliverables connected to the order. Say that not only Linux Management deliver infrastructure - they also deliver other things like patch frequencies - health monitoring etc. Other Technical Service Offerings from other Technical Services e.g. Disaster Recovery, Failover options and more can be applied in the same order. But they will only be options to an CI created. 

What is the best way to handle these extra elements/offerings that apply to the CI eventually created? 

As a technical consumer I want to be able to order exactly the type of needs I have for my System. I want 24/7 monitoring, I want hot standby and also backup of all servers. So these should be defined as deliverables - and how do I then relate all these to the CI itself? Tag-based, attributes?  

Hope the question is not to unclear 🙂 

Thanks!  

BR Ivar

[ivaroen]

My point exactly! 🙂 

It should be a possibility to reflect different technical service and offerings that are related to a CI without having the consequence of ruining synchronization logic. 

A lot of customers have different approaches and some a lot more complex than others. 

/Ivar