Abstract: An object model comprises a plurality of event framework information objects, a shared event data store and an event managing object. Each one of the event framework information objects define event framework characteristics for a respective one of a plurality of event frameworks implemented in a server. The shared event data store includes a plurality of event information objects each defining server event information for a respective one of a plurality of unique events exhibited by the server during operation. Each one of the event information objects is at least temporarily referenced by at least one of the event framework information objects. The event managing object is configured for creating the event information objects and managing persistence of the event information objects.

Abstract: An object model comprises a data store and a plurality of event framework information objects. The data store including a plurality of event information objects each defining server event information for a respective one of a plurality of unique events exhibited by a server during operation. The plurality of event framework information objects each define event framework characteristics for a respective one of a plurality of event frameworks implemented in the server. At least one of the event framework information objects reference a common one of the event information objects for enabling server event information defined by the common one of the event information objects to be viewed using the respective one of the event frameworks corresponding thereto. Each one of the event framework information objects define event framework unification rules under which unification of event framework views provided in accordance with each one of the event framework information objects is facilitated.

Abstract: A power system, which can comprise multiple power subsystems (e.g., one or more power converters sources, etc.) delivers one or more rails of power to a system. The performance of a power system is thermally limited and depends on the different components' specifications. A power system design tool that dynamically generates constraints based on design specifications and power system configurations allows for robust and intelligent validation of a power system design. The power system design tool that allows for robust and intelligent validation of a design facilitates thorough designs that account for numerous factors that can affect a power system. Further, a power system design tool that generates a configuration file in accordance with a validated design, allows for efficient and automatic configuring of a configurable component of a power system.

Abstract: An object model comprises a plurality of event framework information objects, a shared event data store and an event managing object. Each one of the event framework information objects define event framework characteristics for a respective one of a plurality of event frameworks implemented in a server. The shared event data store includes a plurality of event information objects each defining server event information for a respective one of a plurality of unique events exhibited by the server during operation. Each one of the event information objects is at least temporarily referenced by at least one of the event framework information objects. The event managing object is configured for creating the event information objects and managing persistence of the event information objects.

Abstract: An object model comprises a data store and a plurality of event framework information objects. The data store including a plurality of event information objects each defining server event information for a respective one of a plurality of unique events exhibited by a server during operation. The plurality of event framework information objects each define event framework characteristics for a respective one of a plurality of event frameworks implemented in the server. At least one of the event framework information objects reference a common one of the event information objects for enabling server event information defined by the common one of the event information objects to be viewed using the respective one of the event frameworks corresponding thereto. Each one of the event framework information objects define event framework unification rules under which unification of event framework views provided in accordance with each one of the event framework information objects is facilitated.

Abstract: An object model comprises a plurality of event framework information objects, a shared event data store and an event managing object. Each one of the event framework information objects define event framework characteristics for a respective one of a plurality of event frameworks implemented in a server. The shared event data store includes a plurality of event information objects each defining server event information for a respective one of a plurality of unique events exhibited by the server during operation. Each one of the event information objects is at least temporarily referenced by at least one of the event framework information objects. The event managing object is configured for creating the event information objects and managing persistence of the event information objects.

Abstract: A computer system comprises a service processor, flash memory, and service processor main memory accessible by the service processor and coupled to the flash memory. The service processor is coupled to various data processing system components of the computer system. The flash memory includes protected memory space having protected system functionality components stored therein and unprotected memory space having a custom system functionality component stored therein. The protected system functionality components and the custom system functionality component are loadable into the service processor main memory from the flash memory. The custom system functionality component is stored in place of a corresponding default system functionality component that is designated as being customisable.