IP Library Granted Patent US 9,152,413
Granted Patent B2
US 9,152,413 · App. 14/535,030 · Granted Oct 6, 2015

Bi-directional communication between change management tool and implementation tools

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,152,413
App. No.
14/535,030
Granted
Oct 6, 2015
Kind
B2
Abstract

Task implementation tools are registered to interface with a change management tool. The change management tool configures a plurality of tasks to implement a change to an information technology infrastructure's configuration, and sends a plurality of task instructions to the plurality of task implementation tools for performing the plurality of tasks. Each task instruction is directed to a targeted task implementation tool for performing a particular task and includes task-related information for the targeted implementation tool to perform the particular task. Registering the plurality of task implementation tools to interface with the change management tool includes registering each the plurality of task implementation tools to accept the task instruction for the particular task directed to it from the change management tool, to know what to do with the task instruction and to know how to respond to the task instruction.

Claims (31)

1. A method, comprising:

registering a plurality of task implementation tools to interface with a change management tool,

the change management tool configured to associate a unique change identifier (“unique Change ID”) with a change request specifying a change to an information technology infrastructure's configuration, to configure a plurality of tasks to implement the change, associate each of the plurality of tasks with an unique individual task identifier (“unique Task ID”), and send a plurality of task instructions to the plurality of task implementation tools for performing the plurality of tasks,

each task instruction being directed to a targeted task implementation tool for performing a particular task of the plurality of tasks to implement the change to the information technology infrastructure's configuration specified by the change request,

each task instruction including task-related information for the targeted implementation tool to perform the particular task, the unique Change ID associated with the change request and the unique Task ID associated with the particular task; and

wherein registering the plurality of task implementation tools to interface with the change management tool includes registering each of the plurality of task implementation tools to accept the task instruction for the particular task directed to it from the change management tool, to know what to do with the task instruction and to know how to respond to the task instruction.

2. The method of claim 1 , wherein registering each the plurality of task implementation tools includes providing a unique identifier (“unique Registry ID”) to each registered task implementation tool.

3. The method of claim 2 , further comprising, configuring each registered task implementation tool to respond to the change management a result indicating an implementation status of the particular task, the result further including a return of the unique Change ID and the unique Task ID sent by the change management tool in the task instruction for the particular task and a return of the unique Registry ID of the registered task implementation tool.

4. The method of claim 3 , further comprising, configuring a mapping of the result received by the change management tool from the registered implementation tool to a success or failure status of the change request at a change management level within the change management tool.

5. The method of claim 3 , wherein configuring the mapping of the result from the registered implementation tool to a success or failure status of the change request at a change management level within the change management tool includes configuring a mapping of the unique Change ID, the unique Task ID and the unique Registry ID in the result to the success or failure status of the change request.

6. The method of claim 3 , wherein configuring the mapping of the result from the registered implementation tool to a success or failure status of the change request at a change management level within the change management tool includes configuring the change management tool to use the unique Change ID and the unique Task IDs for the plurality of tasks and the unique Registry IDs for the registered task implementation tools in the received results to match and track implementation of the change request and each of the plurality of tasks associated with the change request across the information technology infrastructure.

7. The method of claim 1 , wherein registering the plurality of task implementation tools to interface with the change management tool includes establishing bi-directional communication between each of the plurality of task implementation tools and the change management tool.

8. The method of claim 1 , wherein registering the plurality of task implementation tools to interface with the change management tool includes using a registry form on a graphical user interface of the change management tool for each of the plurality of task implementation tools.

9. The method of claim 8 wherein registering the plurality of task implementation tools to interface with the change management tool includes entering a name, a description, and an active status or inactive status of the implementation tool in the registry form.

10. The method of claim 8 wherein registering the plurality of task implementation tools to interface with the change management tool further includes defining template, interface and instance forms associated with the implementation tool, and defining connection information for communicating with the implementation tool, in the registry form.

11. A non-transitory storage device, readable by a programmable control device, comprising instructions stored on the non-transitory storage device for causing the programmable control device to perform the method according to claim 1 .

12. A system, comprising:

a processor coupled to a computer memory, the processor configured to execute instructions to implement a change management tool coupled to an information technology infrastructure, the change management tool configured to:

register a plurality of task implementation tools to interface with the change management tool,

the change management tool configured to associate a unique change identifier (“unique Change ID”) with a change request specifying a change to an information technology infrastructure's configuration, to configure a plurality of tasks to implement the change, associate each of the plurality of tasks with an unique individual task identifier (“unique Task ID”), and send a plurality of task instructions to the plurality of task implementation tools for performing the plurality of tasks,

each task instruction being directed to a targeted task implementation tool for performing a particular task of the plurality of tasks to implement the change to the information technology infrastructure's configuration specified by the change request,

each task instruction including task-related information for the targeted implementation tool to perform the particular task, the unique Change ID associated with the change request and the unique Task ID associated with the particular task; and

wherein registering the plurality of task implementation tools to interface with the change management tool includes registering each of the plurality of task implementation tools to accept the task instruction for the particular task directed to it from the change management tool, to know what to do with the task instruction and to know how to respond to the task instruction.

13. The system of claim 12 , wherein the change management tool is further configured to provide a unique identifier (“unique Registry ID”) to each registered task implementation tool.

14. The system of claim 13 , wherein each registered task implementation tool is configured to return to the change management a result indicating an implementation status of the particular task, the result further including a return of the unique Change ID and the unique Task ID sent by the change management tool in the task instruction for the particular task and the unique Registry ID of the registered task implementation tool.

15. The system of claim 14 , wherein the change management tool is further configured to map the result received from the registered implementation tool to a success or failure status of the change request at a change management level within the change management tool.

16. The system of claim 14 , wherein the change management tool is further configured to map the unique Change ID, the unique Task ID and the unique Registry ID in the result to the success or failure status of the change request.

17. The system of claim 14 , wherein the change management tool is further configured to use the unique Change ID and the unique Task IDs for the plurality of tasks and the unique Registry IDs for the registered task implementation tools in the received results to match and track implementation of the change request and each of the plurality of tasks associated with the change request across the information technology infrastructure.

18. The system of claim 12 , wherein the change management tool configured to: establish bi-directional communication between each of the plurality of task implementation tools and the change management tool.

19. The system of claim 12 , wherein a respective registry form on a graphical user interface of the change management tool is used to register each of the plurality of task implementation tools.

20. The system of claim 19 , wherein the registry form for each registered implementation tool includes a name, a description, an active status or inactive status of the implementation tool, identifications of template, interface and instance forms associated with the implementation tool, and connection information for communicating with the implementation tool, in the registry form.

Assignments (15)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2025
From: BMC SOFTWARE, INC.
To: BMC HELIX, INC.
Reel/Frame 070442/0197 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0568 →
GRANT OF FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Nov 13, 2024
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 069352/0628 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052854/0139) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0617 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052844/0646) Recorded Aug 6, 2024
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 068339/0408 →
OMNIBUS ASSIGNMENT OF SECURITY INTERESTS IN PATENT COLLATERAL Recorded Mar 4, 2024
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS RESIGNING COLLATERAL AGENT
To: GOLDMAN SACHS BANK USA, AS SUCCESSOR COLLATERAL AGENT
Reel/Frame 066729/0889 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Feb 1, 2024
From: ALTER DOMUS (US) LLC
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.
Reel/Frame 066567/0283 →
GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Recorded Sep 30, 2021
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 057683/0582 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052844/0646 →
SECURITY INTEREST Recorded Jun 4, 2020
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052854/0139 →
RELEASE OF PATENTS Recorded Oct 5, 2018
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: BMC SOFTWARE, INC.; BLADELOGIC, INC.; BMC ACQUISITION L.L.C.
Reel/Frame 047198/0468 →
SECURITY INTEREST Recorded Oct 2, 2018
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE, AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047185/0744 →
SECURITY INTEREST Recorded Jul 27, 2017
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 043351/0189 →
SECURITY INTEREST Recorded Jul 27, 2017
From: BMC SOFTWARE, INC.; BLADELOGIC, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 043351/0231 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 17, 2015
From: BEHNIA, KIA; MUELLER, DOUGLAS
To: BMC SOFTWARE, INC.
Reel/Frame 036117/0704 →