3 Replies Latest reply on Oct 20, 2019 5:45 AM by Stefan Hall

    How do you treat relationships to CIs that are End of Life?

    Johan Teemant
      Share This:

      Hi Community!

      We are looking at some design principles in our CMDB. About CMDB relationships:

       

      How do you treat relationships to Assets/CIs in status End of Life?

      • Keep the relationship to the EOL object?
      • Remove the relationship and store it in an archive instead?
      • Remove the relationship as the CMDB should only care about current state.
      • Introduce an inactive status on the relationship and use it for relations to EOL objects
      • or something else
        • 1. Re: How do you treat relationships to CIs that are End of Life?
          Christian Smerz

          How are you defining end of life?

          What business needs are there for keeping the relationship information?

          Are related items likely to be related to something new?  If so, are there cardinality issues?

           

          I wouldn't suggest that there is any one, correct approach.  This should be driven by your business need.  What are you using your CMDB for and what information do you need to provide to support your IT processes.

          • 2. Re: How do you treat relationships to CIs that are End of Life?
            Johan Teemant

            Thanks

            EOL are CIs representing infrastructure etc that are no longer existing. We need to be able to track down historical data but not nessesarily in the ASSET dataset and it is not user friendly if the data looks the same when in production or discontinued.

            So the question is more technical and I am interested in different technical ways to solve this.

            • 3. Re: How do you treat relationships to CIs that are End of Life?
              Stefan Hall

              We keep our CIs in the asset, even if they have already been scrapped or sold.

              For us, the relationships to incidents and changes are important, as are the device information for evaluation and reporting to our regulatory authorities.

               

              In the asset module, we use the corresponding status values in the life cycle.

               

              Since version 1902, CIs can also be archived in the CMDB. I haven't tried it yet, but the idea corresponds to the other transaction data. Fewer entries in the productive views/tables. It is exciting to see how this new approach is compatible with asset management.