Automated workflow management system for application and data retirement
AssigneeDGD Systems, Inc.
InventorBryon E. Rickey
Life of this patent
Estimating the term…
Abstract
Systems and methods are provided for retiring an application and any associated data, hardware assets, and software assets. A workflow management system creates and tracks the life cycle of a project for application retirement, data retirement, purge, or performance archiving. The workflow management system evaluates the cost of the project, the availability of resources for the project, and captures information about the application and associated assets. Upon deciding to initiate the project based on the evaluations, the workflow management system captures and tracks implementation of project requirements. The workflow management system further manages retirement of hardware and software assets by cancelling, repurposing, decommissioning, or bypassing the assets.
Claims17
An automated workflow management system comprising:
- a hardware asset info database that stores information describing hardware assets and information identifying applications associated with the hardware assets, wherein the hardware assets comprise at least one of computer servers, network switches, and network firewalls;
- one or more processors, and
- memory storing computer-readable instructions that, when executed by the one or more processors, cause the automated workflow management system to:
- determine, at a mapping module, based at least in part on information stored in the hardware asset info database, a plurality of hardware assets associated with an application;
- determine, at the mapping module, a first subset of the plurality of hardware assets to be repurposed and a second subset of the plurality of hardware assets to be decommissioned;
- trigger, at the mapping module, a repurpose life cycle tracker module to address the first subset and a decommission life cycle tracker module to address the second subset;
- generate, at the repurpose life cycle tracker module, one or more repurposing work request tickets corresponding to the first subset;
- track, at the repurpose life cycle tracker module, repurposing of the first subset based at least in part on the one or more repurposing work request tickets;
- generate, at the decommission life cycle tracker module, one or more decommissioning work request tickets corresponding to the second subset;
- track, at the decommission life cycle tracker module, decommissioning of the second subset based at least in part on the one or more decommissioning work request tickets;
- update, by a get candidate applications module of a requirements capture module, a specifications database to reflect receiving a legal hold request, wherein the legal hold request includes a set of criteria;
- determining, by the get candidate applications module, a plurality of impacted applications, based, at least in part, on the set of criteria, wherein the plurality of impacted applications includes the application;
- and
- receive, from a hold sweep module of the requirements capture module, a first notification of an electronic block placed on the application, wherein the electronic block prevents the one or more repurposing work request tickets corresponding to the first subset from progressing further, and wherein the electronic block prevents the one or more decommissioning work request tickets corresponding to the second subset from progressing further.
A method comprising:
- receiving, at a decision module, an input representing a decision to initiate a project based, at least in part, on a project impact assessment, wherein the project impact assessment is received from an ROI assessor module based on a costing model and a savings model;
- determining, at a mapping module, based at least in part on information stored in a hardware asset info database, a plurality of hardware assets associated with an application associated with the project;
- determining, at the mapping module, a first subset of the plurality of hardware assets to be repurposed and a second subset of the plurality of hardware assets to be decommissioned;
- triggering, at the mapping module, a repurpose life cycle tracker module to address the first subset and a decommission life cycle tracker module to address the second subset;
- tracking, at the repurpose life cycle tracker module, repurposing of the first subset;
- tracking, at the decommission life cycle tracker module, decommissioning of the second subset;
- updating the hardware asset info database to reflect a final retired status of the first and second sub sets;
- creating, at a create program module of a planning module, a program container associated with the project, wherein the program container includes at least the application;
- generating, at an estimate costs module of the planning module, a costing model for the application based, at least in part, on the program container and a plurality of cost assumptions;
- generating, at a capture savings module of the planning module, a savings model for the application based, at least in part, on the program container, and a plurality of savings assumptions;
- and
- applying, by the ROI assessor module of the planning module, a service calculation template to the costing model and the savings model to generate a project impact assessment for the application, wherein the project impact assessment includes program level investment costs and program level investment savings.
A method comprising:
- providing, by a planning module, a project impact assessment associated with a project of retiring an application;
- capturing, by an initiation module, one or more attributes associated with the project;
- capturing, by a snapshot module, information describing one or more hardware assets and information describing one or more software assets, wherein the one or more hardware and the one or more software assets are associated with the application;
- receiving, by a decision module, an input representing a decision to initiate the project;
- determining, by a requirements capture module, a plurality of requirements for the project, wherein the plurality of requirements includes legal requirements;
- initiating, by a status tracker module, an implementation of the plurality of requirements;
- auditing, by the status tracker module, the implementation of the plurality of requirements;
- retiring, by a retirement module, one or more software assets associated with the application;
- retiring, by the retirement module, one or more hardware assets associated with the application;
- performing, by the requirements capture module, a hold query on a specifications database to identify one or more applications subject to a legal hold request received by the requirements capture module;
- receiving, by a get candidate applications module of the requirements capture module, the legal hold request, wherein the legal hold request includes a set of criteria;
- determining, by the get candidate applications module, a plurality of impacted applications based, at least in part, on the set of criteria, and place the plurality of impacted applications in a legal hold container, wherein the plurality of impacted applications includes the application;
- adding, by the get candidate applications module, the plurality of impacted applications to the legal hold request;
- receiving, by a hold sweep module of the requirements capture module, the legal hold request;
- and
- conducting, by the hold sweep module, a hold sweep of the plurality of impacted applications.
Dependencies are inferred from the claim text.