COMPUTER SYSTEM MANAGEMENT CENTRAL SCHEDULE FOR BUSINESS DOWNTIMES

• US 20090144112A1
• Filed: 11/28/2008
• Published: 06/04/2009
• Est. Priority Date: 11/29/2007
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: ESCHENROEDER, KLAUS
• Application Number:
  US12/324,928
• Publication Number:
  US 20090144112A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group

Abstract

A method and a system are described that involve a schedule for central downtime planning. In one embodiment, the method includes creating a plurality of entries in a downtime schedule, wherein the downtime schedule can be a central downtime schedule, residing on a managing system, or a local downtime schedule, residing on a managed system. The method further includes synchronizing the central downtime schedule with the local downtime schedule. Finally, the method includes querying the downtime schedule to retrieve downtimes of the managed system.

In one embodiment, the system includes a central managing system and a set of managed systems that are connected with the central managing system via a Web service. The system also includes a central downtime schedule that stores a plurality of entries, wherein the central downtime schedule resides on the central managing system. The system further includes a synchronization service that synchronizes the plurality of entries stored in the central downtime schedule with a local downtime schedule residing on each of the set of the managed systems.

Claims

1. A computerized method comprising:

storing a plurality of entries in a downtime schedule, wherein the downtime schedule can be a central downtime schedule, residing on a managing system, or a local downtime schedule, residing on a managed system;

synchronizing the central downtime schedule with the local downtime schedule; and

querying the downtime schedule to retrieve downtimes of the managed system.

2. The method of claim 1, wherein each entry of the plurality of entries is stored with a plurality of properties.

3. The method of claim 2, wherein the plurality of properties comprises any of the following:

a system identifier for the managed system, a rule for recurrence of an entry, a category of the entry, a monitoring status, a reason, and a logical port to be used for forwarding information from the managing system to the managed system, wherein the information regards the plurality of entries.

4. The method of claim 3, wherein the category of the entry defines the entry selected from the group consisting of a planned downtime, an unplanned downtime, and a planned availability period for the managed system.

5. The method of claim 3, wherein the monitoring status has a value selected from the group consisting of suppress incidents, suppress monitoring, and full monitoring.

6. The method of claim 3 further comprising:

modifying a subset of the plurality of properties of a subset of the plurality of entries; and

synchronizing the central downtime schedule with the local downtime schedule in response to editing the subset of the plurality of properties.

7. The method of claim 1 further comprising:

querying the local downtime schedule to retrieve all downtimes of the managed system; and

notifying users of the managed system about an upcoming downtime.

8. The method of claim 6 further comprising:

deleting any number of entries from the plurality of entries from the downtime schedule; and

refreshing any number of entries from the plurality of entries from the downtime schedule.

9. The method of claim 6, wherein editing the subset of the plurality of properties comprises:

changing any of the following;

the rule for recurrence, if the recurrence happens in the future, the logical port, the monitoring status, and the reason; and

adding a new rule for recurrence.

10. The method of claim 1, wherein querying the downtime schedule comprises:

retrieving all planned downtimes within a given time period;

retrieving a next planned downtime; and

retrieving the plurality of entries in the downtime schedule.

11. The method of claim 10 further comprising:

generating a set of unavailability reports in response to retrieving the plurality of entries in the downtime schedule;

checking the monitoring status of the managed system; and

suppressing alerts and incidents in response to checking the monitoring status.

12. A computing system comprising:

a central managing system;

a set of managed systems that are connected with the central managing system via a Web service;

a central downtime schedule that stores a plurality of entries, the central downtime schedule residing on the central managing system; and

a synchronization service that synchronizes the plurality of entries stored in the central downtime schedule with a local downtime schedule residing on each of the set of the managed systems.

13. The computing system of claim 12 further comprising:

an application programming interface (API) unit with methods for creating, editing, deleting, and refreshing the plurality of entries; and

an API unit with methods for querying the central downtime schedule and the local downtime schedule.

14. The computing system of claim 12 further comprising:

an availability reporting unit that determines unavailability periods of a managed system;

a notification tool residing on the managed system to send notifications to users about the plurality of entries; and

an availability monitoring unit that evaluates the unavailability periods.

15. The computing system of claim 12 further comprising:

an alert engine that determines when to suppress alerts based on the plurality of entries.

16. The computing system of claim 12 further comprising:

a command line console residing on each of the set of managed systems to start and stop the managed systems locally; and

an application residing on the central managing system to start and stop the managed systems centrally.

17. The computing system of claim 12 further comprising:

an appointment rules unit that includes a set of rules for recurrences of a subset of the plurality of entries.

18. A computer-readable storage medium having instructions therein that when executed by the machine, cause the machine to:

store a plurality of entries in a downtime schedule, wherein the downtime schedule can be a central downtime schedule, residing on a managing system, or a local downtime schedule, residing on a managed system;

synchronize the central downtime schedule with the local downtime schedule; and

query the downtime schedule to retrieve downtimes of the managed system.

19. The computer-readable storage medium of claim 18 having instructions that when executed further cause the machine to:

query the local downtime schedule to retrieve all downtimes of the managed system; and

notify users of the managed system about an upcoming downtime.

20. The computer-readable storage medium of claim 18 having instructions that when executed further cause the machine to:

retrieve all planned downtimes within a given time period;

retrieve a next planned downtime;

check a monitoring status of the managed system; and

retrieve the plurality of entries in the downtime schedule.