Systems and methods for capturing data within an intelligent electronic device

• US 20070112446A1
• Filed: 11/14/2005
• Published: 05/17/2007
• Est. Priority Date: 11/14/2005
• Status: Active Grant

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Cargnelli, Claudio, Deveaux, Robert, Johnson, Raymond
• Granted Patent: US 7,734,359 B2
• Time in Patent Office: Days
• US Class Current: 700/83
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A method for capturing data includes recording, within an intelligent electronic device (IED), information regarding an initial change to one of a firmware within the IED, a hardware within the IED, and a configuration within the IED.

Claims

1. A method for capturing data comprises recording, within an intelligent electronic device (IED), information regarding an initial change to one of a firmware within the IED, a hardware within the IED, and a configuration within the IED.

2. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, wherein said recording information comprises recording, by the processor, the information during the session.

3. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed;

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed; and

extending the session for the pre-determined period of time upon determining that an additional change is to be made to one of the firmware, the hardware, and the configuration.

4. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed; and

ending, by the processor, the session upon determining that the pre-determined period of time has elapsed.

5. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, wherein said recording information comprises storing, during the session, in a memory within the IED, at least one of a date of start of the session, a time of start of the session, a number of a version of the firmware, and a status of operation of the processor.

6. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, wherein said recording information comprises storing, during the session, in a memory within the IED, at least one of an event type that is to be changed, wherein the event type includes one of the firmware, the hardware, and the configuration.

7. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, wherein said recording information comprises storing, during the session, in a memory within the IED, a method of making the initial change, wherein the method includes one of making the initial change via a keypad of the IED and making the initial change via a port of the IED.

8. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, wherein said recording information comprises storing, during the session, in a memory within the IED, at least one of an address of a device requesting the initial change and a status of entry of a password used to make the initial change, and a number of changes made during the session.

9. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, wherein said recording information comprises storing, during the session, in a memory within the IED, at least one of a name of a file uploaded to the processor and a username received from a computing unit that transmits the file that is uploaded.

10. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, wherein said recording information comprises storing, during the session, in a memory within the IED, at least one of a date of ending of the session and a time of ending of the session.

11. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether a passcode to access a memory within the IED is received; and

providing, by the processor, an option to a user to erase the information recorded within the memory upon determining that the passcode is valid.

12. A method in accordance with claim 1 further comprising:

generating, by a processor within the IED, an incremented number of a version of the configuration by incrementing a number of a version of the configuration each time a change is made is made to the configuration; and

generating a field on an interface to provide access to the incremented number.

13. A method in accordance with claim 1 further comprising:

generating an event record by counting a plurality of sessions, wherein the plurality of sessions are generated from a plurality of changes made to one of the firmware, hardware, and configuration; and

providing access to the event record to a user.

14. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed; and

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed; and

providing access to a status of the session to a user, wherein the status includes one of an active status when the access is provided and an inactive status when the access is provided.

15. A method in accordance with claim 1 wherein said recording information comprises recording the information within a nonvolatile memory of the IED.

16. A method in accordance with claim 1 further comprising:

determining, by a processor within the IED, whether one of the firmware, the hardware, and the configuration is to be changed;

initiating, by the processor, a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed; and

terminating, by the processor, a connection within a computing unit from which a portion of the information is obtained upon determining that the session has expired.

17. An intelligent end device (IED) comprising:

a memory; and

a processor configured to record, within said IED, information regarding an initial change made to one of a firmware within the IED, a hardware within the IED, and a configuration within said IED.

18. An IED in accordance with claim 17 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, and said processor configured to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed.

19. An IED in accordance with claim 17 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to extend the session for the pre-determined period of time upon determining that an additional change is to be made to one of the firmware, the hardware, and the configuration.

20. An IED in accordance with claim 17 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to end the session upon determining that the pre-determined period of time has elapsed.

21. An IED in accordance with claim 17 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to store, during the session, in a memory within said IED, at least one of a date of start of the session, a time of start of the session, a number of a version of the firmware, and a status of operation of said processor.

22. An IED in accordance with claim 17 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to store, during the session, in a memory within said IED, at least one of an event type that is to be changed, wherein the event type includes one of the firmware, the hardware, and the configuration.

23. A power management control system (PMCS) comprising:

a computing unit;

an interface coupled to said computing unit; and

an intelligent electronic device (IED) coupled to said computing unit via said interface, wherein said IED separate from said computing unit, and said IED comprising a processor configured to record, within said IED, information regarding an initial change made to one of a firmware within said IED, a hardware within said IED, and a configuration within said IED.

24. A PMCS in accordance with claim 23 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, and said processor configured to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed.

25. A PMCS in accordance with claim 23 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to extend the session for the pre-determined period of time upon determining that an additional change is to be made to one of the firmware, the hardware, and the configuration.

26. A PMCS in accordance with claim 23 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to end the session upon determining that the pre-determined period of time has elapsed.

27. A PMCS in accordance with claim 23 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to store, during the session, in a memory within said IED, at least one of a date of start of the session, a time of start of the session, a number of a version of the firmware, and a status of operation of said processor.

28. A PMCS in accordance with claim 23 wherein said processor configured to determine whether one of the firmware, the hardware, and the configuration is to be changed, to initiate a session of a pre-determined period of time upon determining that one of the configuration, the firmware, and the hardware is to be changed, and to store, during the session, in a memory within said IED, at least one of an event type that is to be changed, wherein the event type includes one of the firmware, the hardware, and the configuration.