Systems and methods for managing computer components

A system for managing a plurality of computer components, the system comprising:

• a database configured to store component data;
• and
• a component manager (CM) computing device configured to be coupled to the database and comprising a processor, the CM computing device further configured to:
• receive component data for at least one computer component of the plurality of computer components;
• store the component data in a memory block in the database;
• assign a first lifecycle classification to the at least one computer component by updating the memory block in the database, wherein the first lifecycle classification represents a status of the at least one computer component;
• store one or more lifecycle models within the database;
• use the one or more lifecycle models to update the lifecycle classification assigned to the at least one computer component when certain attributes of the at least one computer component satisfy one of the one or more lifecycle models;
• upon determining that the certain attributes of the at least one computer component satisfy the one of the one or more lifecycle models, automatically update the memory block in the database by applying the lifecycle model stored within the database, the CM computing device updating the lifecycle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification;
• determine at least one future lifecycle transition date specified by an organization rule for the at least one computer component, wherein the at least one future lifecycle transition date includes at least a first future lifecycle transition date when the at least one computer component should be updated from the second lifecycle classification to a third lifecycle classification;
• and
• cause a lifecycle report to be displayed, wherein the lifecycle report includes a lifecycle status for the at least one computer component over a specified future period of time, the lifecycle status including the at least one future lifecycle transition date, wherein the system facilitates one or more of i) centrally controlling the plurality of computer components, ii) coordinating between disparate computer systems to direct updates and fixes, iii) resolving data redundancy issues caused by multiple copies of software being in use, and iv) decreasing risk of security breaches.

A non-transitory computer readable medium that includes computer executable instructions for managing a plurality of computer components, wherein when executed by a Component Manager (CM) computing device comprising a processor in communication with a memory device, the computer-executable instructions cause the CM computing device to:

• receive component data for at least one computer component of the plurality of computer components;
• store the component data in a memory block in the memory device;
• assign a first lifecycle classification to the at least one computer component by updating the memory block in the memory device, wherein the first lifecycle classification represents a status of the at least one computer component;
• store one or more lifecycle models within the memory device, the CM computing device configured to use the one or more lifecycle models to update the lifecycle classification assigned to the at least one computer component when certain attributes of the at least one computer component satisfy one of the one or more lifecycle models;
• upon determining that the certain attributes of the at least one computer component satisfy one of the one or more the lifecycle models, automatically update the memory block in the memory device by applying the lifecycle model stored within the memory device, the CM computing device updating the lifecycle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification;
• determine at least one future lifecycle transition date specified by an organization rule for the at least one computer component, wherein the at least one future lifecycle transition date includes at least a first future lifecycle transition date when the at least one computer component should be updated from the second lifecycle classification to a third lifecycle classification;
• and
• cause a lifecycle report to be displayed, wherein the lifecycle report includes a lifecycle status for the at least one component over a specified future period of time, the lifecycle status including the at least one future lifecycle transition date, wherein the non-transitory computer readable medium facilitates one or more of i) centrally controlling the plurality of computer components, ii) coordinating between disparate computer systems to direct updates and fixes, iii) resolving data redundancy issues caused by multiple copies of software being in use, and iv) decreasing risk of security breaches.