I would follow the Service Builder approach here. If Service Builder allows you to relate one Service Offering to another using Depends on and Used by, that is a strong indication that ServiceNow supports this model even if the CSDM documentation does not show the relationship explicitly.
For your example, I would model the Server and DB package as its own Service Offering and create Depends on relationships from that package offering to the Server Offering and the DB Offering.
The important part is to keep the underlying service model clean as well. The Server Offering and DB Offering should still be connected to the correct services and service instances, so the offering relationship does not replace the technical relationships underneath.
I would also make sure the package offering represents a real consumable offering with its own commitments, subscriptions, or support expectations. If it is only being used as a grouping mechanism, then I would first check whether a separate offering is really needed.
So in this case, I would not avoid the relationship just because it is not shown clearly in the CSDM model. Since Service Builder creates it natively, I would consider it a valid approach as long as it reflects a real dependency in your service model.
If this helped, can you mark it as a solution or helpful?
