System Lifecycle Management

Each time a system is powered up, all device parameters and flow of control information captured during initial system deployment is read from the local Choreographer configuration file for this particular instance of a system and can be used to automate system configuration. The stored system configuration is compared with what is detected to be available in the current network environment. Any differences between the current state of the local system and the stored configuration are highlighted on a graphical display of the actual system. Using information stored during deployment every time the system powers up prevents many sources of operator error.

In most repair situations, Choreographer will identify the optimum course of action and propose it to the user. If a component damaged in service has been replaced with a spare unit, Choreographer will recognize that there is a role for which hardware is missing and that hardware with a new serial number is now present. If the new hardware is compatible with the unfulfilled role, Choreographer will propose using the newly installed device in place of the missing device. If the user accepts Choreographer’s proposal, all of the system start up parameters will be updated to reflect the new part, the revised parameters will be stored in an updated system configuration file, and the new information will be used for all subsequent operation of the system.