Systems and methods for managing computer components
First Claim
1. A computer-based method for managing a plurality of computer components in an organization, the method implemented using a Component Manager (CM) computing device, wherein the CM computing device comprises a processor in communication with a memory device, the method comprising:
- receiving, by the CM computing device, from a stakeholder computing device, component data for at least one computer component of the plurality of computer components;
storing, by the CM computing device, the component data in a memory block in the memory device;
assigning, by the CM computing device, a first lifecycle classification, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the memory device, wherein the first lifecycle classification is one of a plurality of lifestyle classifications, and wherein each lifestyle classification represents a status of the at least one computer component defined by an age of the component, a nature of usage of the component, and an availability of alternative or newer versions of the component;
automatically updating the memory block in the memory device by applying a lifecycle model stored within the memory device, the lifecycle model updating the lifestyle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification of the plurality of lifecycle classifications;
causing, by the CM computing device, the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component including the update from the first lifecycle classification to the second lifecycle classification;
prompting, by the CM computing device, the at least one stakeholder to further update the memory block for the at least one computer component, by electronically displaying the graphical representation;
determining, by the CM computing device, at least one future lifecycle transition date 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 component should be updated from the second lifecycle classification to a third lifecycle classification; and
causing, by the CM computing device, 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 method 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.
1 Assignment
0 Petitions
Accused Products
Abstract
A computer-based method for managing a plurality of computer components in an organization is provided. The method is implemented using a Component Manager (CM) computing device. The method includes receiving, from a stakeholder computing device, component data for at least one computer component of the plurality of computer components. The method also includes storing the component data in a memory block in the memory device. The method further includes assigning a first lifecycle classification, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the memory device. The method also includes causing the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component. The method further includes prompting a stakeholder to update a component utilization scheme for the computer component, by electronically displaying the graphical representation.
16 Citations
19 Claims
-
1. A computer-based method for managing a plurality of computer components in an organization, the method implemented using a Component Manager (CM) computing device, wherein the CM computing device comprises a processor in communication with a memory device, the method comprising:
-
receiving, by the CM computing device, from a stakeholder computing device, component data for at least one computer component of the plurality of computer components; storing, by the CM computing device, the component data in a memory block in the memory device; assigning, by the CM computing device, a first lifecycle classification, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the memory device, wherein the first lifecycle classification is one of a plurality of lifestyle classifications, and wherein each lifestyle classification represents a status of the at least one computer component defined by an age of the component, a nature of usage of the component, and an availability of alternative or newer versions of the component; automatically updating the memory block in the memory device by applying a lifecycle model stored within the memory device, the lifecycle model updating the lifestyle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification of the plurality of lifecycle classifications; causing, by the CM computing device, the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component including the update from the first lifecycle classification to the second lifecycle classification; prompting, by the CM computing device, the at least one stakeholder to further update the memory block for the at least one computer component, by electronically displaying the graphical representation; determining, by the CM computing device, at least one future lifecycle transition date 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 component should be updated from the second lifecycle classification to a third lifecycle classification; and causing, by the CM computing device, 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 method 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. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A system for managing a plurality of computer components in an organization, 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, from a stakeholder computing device, 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, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the database, wherein the first lifecycle classification is one of a plurality of lifestyle classifications, and wherein each lifestyle classification represents a status of the at least one computer component defined by an age of the component, a nature of usage of the component, and an availability of alternative or newer versions of the component; automatically update the memory block in database by applying a lifecycle model stored within the database, the lifecycle model updating the lifestyle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification of the plurality of lifecycle classifications; cause the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component including the update from the first lifecycle classification to the second lifecycle classification; prompt the at least one stakeholder to further update the memory block for the at least one computer component, by electronically displaying the graphical representation; determine at least one future lifecycle transition date 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 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 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. - View Dependent Claims (8, 9, 10, 11, 12, 13)
-
-
14. A non-transitory computer readable medium that includes computer executable instructions for managing a plurality of computer components in an organization, 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, from a stakeholder computing device, component data for at least one computer component of the plurality of computer components; store the component data in the memory device; assign a first lifecycle classification, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the memory device, wherein the first lifecycle classification is one of a plurality of lifestyle classifications, and wherein each lifestyle classification represents a status of the at least one computer component defined by an age of the component, a nature of usage of the component, and an availability of alternative or newer versions of the component; automatically update the memory block in the memory device by applying a lifecycle model stored within the memory device, the lifecycle model updating the lifestyle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification of the plurality of lifecycle classification; cause the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component including the update from the first lifecycle classification to the second lifecycle classification; prompt the at least one stakeholder to further update the memory block for the at least one computer component, by electronically displaying the graphical representation; determine at least one future lifecycle transition date 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 component should be undated 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. - View Dependent Claims (15, 16, 17, 18, 19)
-
Specification