What goes into a Resource inventory are Managed Entities. You don't need to include things you do not manage. Everything can be decomposed into constituent parts however we generally do not need every screw to be managed.
So you need to ask the question: What other systems need the information stored for this item?
A cloud native function (CNF) may be performing a role in the network, for example a 5G Core SMF. An SMF is represented as a ResourceFunction in inventory with relationships to other network functions (i.e. UPF). It is important to know the topology of the network functions in a well managed network. Assurance systems use the inventory to understand that a failure on an N4 interface effects the SMF and UPF it connects. Alarms on the SMF and UPF, and the transport used to accomplish N4, are all related.
Now we could stop there, however we can also represent the software application which provides the SMF in the inventory. A ResourceFunction may be provided by InstalledSoftware as a managed entity with information describing software aspects and related hosting platform. Now we can know more things, like the relationship between performance metrics on the UPF with the hosting platform (i.e. k8s cluster). If the hosting platform is also in inventory we could also know the hardware underlying it. And so it goes.
See TMF730 Software and Compute Entity Management API.
I wouldn't suggest that TM Forum assets replace anything in IT management, just that we want a management continuum and not a hard break between network and IT.
------------------------------
Vance Shipley
SigScale
------------------------------