@Johannes,
While i agree rationalization of distinct technologies, OS, database, middleware etc are definitely important and to be considered, our other product offerings by SAM/HAM have a degree of this capability especially SAM Pro.  So, if we incorporate into EA, we have a duplication of functionality.   We have asked for an enhancement to allow "assessment" at the Technology Reference Model (TRM) level and that is where, in EA, we would do individual tech rationalization.  I've seen a few of our TRM customers create/configure the appropriate workflows for this.  A TRM Product is a declaration that a particular Product (software, hardware, coming at some point patterns) is an allowed technology standard in the organization/enterprise.   A great point of focus for periodic rationalization.

@SteveMac1 , indeed, all Business Applications must have at least one Application Service, Saas and otherwise.   I was stating that the Application Service would likely not have any infrastructure CI relationships.  

As for Technical Service and Offerings, by CSDM and Service Portfolio best practice, they must/should be created at the appropriate layers: Application Service, Infrastructure and Delivery.   While it would be excellent to have a association/reference from a TSO to the TRM Product being "delivered/supported" by the TSO, the wide varioation on how TSO are defined and the facilities to management them being outside of Enterprise Architecture's (our tool not the practice) area of concern, make it difficult to do anything with TS/TSO in EA Workspace though Modeling does indeed recognize and include them.