The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jul. 15, 2014
Filed:
Oct. 28, 2005
Aaron D. Kephart, Charlotte, NC (US);
Brian R. Kilpatrick, Walnut Creek, CA (US);
Wallace A. Kirkland, Aiken, SC (US);
William N. Waldron, Allen, TX (US);
Michael L. Ritchie, Charlotte, NC (US);
Robert J. Maloney, Weddington, NC (US);
Atilio A. Deambrosi, Greenville, SC (US);
Philip H. Howard-knight, Purley, GB;
Carol Gatrell, Duncanville, TX (US);
Aaron D. Kephart, Charlotte, NC (US);
Brian R. Kilpatrick, Walnut Creek, CA (US);
Wallace A. Kirkland, Aiken, SC (US);
William N. Waldron, Allen, TX (US);
Michael L. Ritchie, Charlotte, NC (US);
Robert J. Maloney, Weddington, NC (US);
Atilio A. Deambrosi, Greenville, SC (US);
Philip H. Howard-Knight, Purley, GB;
Carol Gatrell, Duncanville, TX (US);
Bank of America Corporation, Charlotte, NC (US);
Abstract
System and method for managing the configuration of resources in an enterprise. Embodiments of the present invention gather, store, and maintain institutional knowledge of configurations of IT resources of an enterprise. A configuration database serves as a temporal record of the configurations of the resources. The configuration database can reflect a dimensional model of the enterprise configuration where various configuration items are linked together. A configuration change can be analyzed and approved, and then reflected in a change to a configuration item (CI) which imposes an appropriate change to other configuration items based on upstream, downstream, peer relationships and/or views. A system according to an embodiment of the invention can also include a change database, an inventory database, a problem database, and/or a service level management subsystem to ensure changes to an enterprise's configuration are consistent with service level agreements and/or operating level agreements.