Abstract: A fault identification may be triggered by a component of a power generation system (PGS), such as a hardware component, a controller of a hardware component, a device of the PGS, a computer connected to the PGS, a computer configured to monitor the PGS, and/or the like. The fault identification may be the result of a failure of a component of the PGS, a future failure of a component of the PGS, a routine maintenance of the PGS, and/or the like. The fault is converted to a notification on a user interface using a mapping of faults, root-causes, notification rules, and/or the like. The conversion may use one or more lookup tables and/or formulas for determining the impact of the fault on the PGS, and/or the like.

Abstract: A fault identification may be triggered by a component of a power generation system (PGS), such as a hardware component, a controller of a hardware component, a device of the PGS, a computer connected to the PGS, a computer configured to monitor the PGS, and/or the like. The fault identification may be the result of a failure of a component of the PGS, a future failure of a component of the PGS, a routine maintenance of the PGS, and/or the like. The fault is converted to a notification on a user interface using a mapping of faults, root-causes, notification rules, and/or the like. The conversion may use one or more lookup tables and/or formulas for determining the impact of the fault on the PGS, and/or the like.

Abstract: A fault identification may be triggered by a component of a power generation system (PGS), such as a hardware component, a controller of a hardware component, a device of the PGS, a computer connected to the PGS, a computer configured to monitor the PGS, and/or the like. The fault identification may be the result of a failure of a component of the PGS, a future failure of a component of the PGS, a routine maintenance of the PGS, and/or the like. The fault is converted to a notification on a user interface using a mapping of faults, root-causes, notification rules, and/or the like. The conversion may use one or more lookup tables and/or formulas for determining the impact of the fault on the PGS, and/or the like.

Abstract: A fault identification may be triggered by a component of a power generation system (PGS), such as a hardware component, a controller of a hardware component, a device of the PGS, a computer connected to the PGS, a computer configured to monitor the PGS, and/or the like. The fault identification may be the result of a failure of a component of the PGS, a future failure of a component of the PGS, a routine maintenance of the PGS, and/or the like. The fault is converted to a notification on a user interface using a mapping of faults, root-causes, notification rules, and/or the like. The conversion may use one or more lookup tables and/or formulas for determining the impact of the fault on the PGS, and/or the like.

Abstract: A fault identification may be triggered by a component of a power generation system (PGS), such as a hardware component, a controller of a hardware component, a device of the PGS, a computer connected to the PGS, a computer configured to monitor the PGS, and/or the like. The fault identification may be the result of a failure of a component of the PGS, a future failure of a component of the PGS, a routine maintenance of the PGS, and/or the like. The fault is converted to a notification on a user interface using a mapping of faults, root-causes, notification rules, and/or the like. The conversion may use one or more lookup tables and/or formulas for determining the impact of the fault on the PGS, and/or the like.

Abstract: A fault identification may be triggered by a component of a power generation system (PGS), such as a hardware component, a controller of a hardware component, a device of the PGS, a computer connected to the PGS, a computer configured to monitor the PGS, and/or the like. The fault identification may be the result of a failure of a component of the PGS, a future failure of a component of the PGS, a routine maintenance of the PGS, and/or the like. The fault is converted to a notification on a user interface using a mapping of faults, root-causes, notification rules, and/or the like. The conversion may use one or more lookup tables and/or formulas for determining the impact of the fault on the PGS, and/or the like.

Abstract: Systems and methods for social graph based permissions, publication, and subscription for networks of associations are provided. A role object may be created by a user which can be a member of the network or a visitor who can join or browse the network of associations, defining a network of associations and at least one rule for user access control operation. The server identifies the role object and executes the rules against members belonging to the network of associations. The network of associations may be selected by the user via a social graph. The rules defined by the role object may include setting permissions, publishing, or subscription. Further, the server may automatically set and maintain permissions, publishing audience, and subscription lists in a dynamic network environment.