Shaman-X methodology drives infrastructure modelling from user requirement standpoint and results in logical equation sets which caracterize infrastructure situation
Shaman-X methodology aims at taking every precaution regarding pertinence of high availability mechanisms and planned failovers, when infrastructure complexity, threats diversity, and system evolution over time to not allow a single personne to keep a global view of the whole.
Shaman-X results in an unified design framework to cover a larger range of solutions and reduce intersect and deadlock risks. An enforced control of safety mechanims provides existing solutions improvement opportunities and avoids, with perfect understanding, a lot of limited and uncompatible products which cost a fortune in licenses and updates with no predictable final result.
The study group is ideally led by the operations manager and the maintenance manager. Someone from engineering studies should be involved. Beginning and ending of each phase is the opportunity to associate other functions which are also affected by the information system, in particular marketing management, ERP users and top management.
Shaman-X method is based on a deep familiarity with the information system. First step outcome is a comprehensive list of :
This phase ends on the definition of the perimeter of the studied system and a technical form for every component.
After the classification of users, system missions and components in consistent categories, this phase describes, by a succession of interdependency matrixes, the relations between users and missions, missions and components and the consequences of their respective failover capabilities.
The modelling phase results in an infrastructure model definition which represents in equations, the behaviour of the information system when confronted to different scenarios.
Application domains of Shaman-X method are the following ones :
High Availability : Failover of complex architectures which need to preserve functional links between several subsets of heterogeneous systems. It is the case, for example, of ERP kind of applications, which are built on multi-tiered architectures, and which require to maintain precise rules for functioning and security between client stations, application servers, database servers, backup servers an so on...
Disaster tolerance : Failover of architectures which contain several intricated failover levels. For example, the orderly failover between two clusters located in two separate rooms. One must differentiate cases when failover must tale place between the members of the active cluster in the primary room, from the case when the decision to abandon the primary room for the backup room must be made.
Computer aided crisis management and state based procedures : Permanent calculation of the model and component technical forms are combined to build an application targetted to crisis management taskforce of large organisations which heaviliy depend on IT infrastructures. When run in a simulation environment, the model can be used to train people about critical situations, or verify performance and ability to survive of the existing infrastructure as well as the one planned in futur investments.
© 2003-2005, by , all rights reserved
Shaman-X.com and Shaman-X.org sites are sponsored and hosted by SISalp