You present a good question. Forgive me for the long response:
Asset vs CI is pretty simple when we discuss physical products. In the past I would use the following to help differentiate Asset vs CI when discussing things we can touch:
Again, the above works well for physical items but not for logical. The financial data, assuming buy vs. build, is stored on a Hardware Asset and a Software Entitlement. Since the Software Entitlement asset record is a point-in-time purchase of COTS software instead of a singular representation of software, relating a Business Application to an Asset is not effective. There is no proper asset to relate to.
BUT...
There is a Product Model that can be relate to the Business Application. In future releases we will enable greater value to the Product Models as they reference various objects throughout the lifecycle of a Product. Assuming a product lifecycle with stages of Pipeline, Design, Operational, and End of life, the future begins to look something like this:
As you can see, the product model can be referenced to multiple objects throughout its life. Depending on buy vs build you will see a products purchase information via ITAM, you will see its planning information via APM, you will see its Build information via DevOps, you will see it's deployed details via ITOM, and management information via ITSM, CSM, SecOps, etc.
The gap today is with COTS Business Applications where the ITAM Software Entitlement is not easily associated with the Business Application. Feel free to reach out to me directly to work through your use cases. We intend to fill this and other gaps related to the overall processes that exist in the CSDM.
Hope this helps,
Scott
You present a good question. Forgive me for the long response:
Asset vs CI is pretty simple when we discuss physical products. In the past I would use the following to help differentiate Asset vs CI when discussing things we can touch:
Again, the above works well for physical items but not for logical. The financial data, assuming buy vs. build, is stored on a Hardware Asset and a Software Entitlement. Since the Software Entitlement asset record is a point-in-time purchase of COTS software instead of a singular representation of software, relating a Business Application to an Asset is not effective. There is no proper asset to relate to.
BUT...
There is a Product Model that can be relate to the Business Application. In future releases we will enable greater value to the Product Models as they reference various objects throughout the lifecycle of a Product. Assuming a product lifecycle with stages of Pipeline, Design, Operational, and End of life, the future begins to look something like this:
As you can see, the product model can be referenced to multiple objects throughout its life. Depending on buy vs build you will see a products purchase information via ITAM, you will see its planning information via APM, you will see its Build information via DevOps, you will see it's deployed details via ITOM, and management information via ITSM, CSM, SecOps, etc.
The gap today is with COTS Business Applications where the ITAM Software Entitlement is not easily associated with the Business Application. Feel free to reach out to me directly to work through your use cases. We intend to fill this and other gaps related to the overall processes that exist in the CSDM.
Hope this helps,
Scott
