IT must manage costs, deliver the right services at the right time, secure information assets, provide dependable service and lead the business in leveraging technologies. This requires automated procedures and management tools in order to achieve this effectively and efficiently. The selection of an appropriate management architecture is key to establishing the required level of control and automation. There are two separate approaches to developing a management architecture:
The challenges for IT management are to coordinate and work in partnership with the business in the building of these management solutions, supporting the appropriate processes and providing the required measurements and metrics. This has to be achieved while reducing or optimizing the costs involved, particularly the annual, ongoing costs. The best way of minimizing costs is to design cleverly and carefully – for example, making best use of capacity so that additional capacity is not unnecessarily bought (with its associated ongoing costs), or designing a backup/recovery solution that doesn’t require a complete additional set of infrastructure. Considerable costs can be saved by intelligent and careful design, using technology that is supportable and causes few problems in the operational environment.
The main method of realizing these goals is to design solutions that give a reduction in the overall network management and support costs, while maintaining or even improving the quality of service delivered to the business.
To gain the greatest benefit from the use of the Four Ps, organizations should determine the roles of processes and people, and then implement the tools to automate the processes, facilitating people’s roles and tasks. The best way of achieving this is to develop a model or architecture based on these principles. This architecture should facilitate the implementation of a set of integrated tools and processes that support ‘end-to-end’ management of all areas of the technology used, ensuring that there are no gaps and no ‘technical silos’.
However, IT faces a big challenge in developing and maintaining the soft skills required to perform these management roles and processes effectively. In the truly efficient organizations, these roles and processes are aligned to those of the business. This ensures that the business and IT Management processes and information have similar targets and goals. However, all too often, organizations devote insufficient time and effort to the development of the soft skills (for example, interpersonal skills, communication skills, meeting skills) necessary for the processes and the business alignment to be effectively achieved.
There are five areas that need to be considered with regard to the design of a management architecture, as illustrated in Figure 3.10.
Figure 3.10 Integrated business-driven technology management
The relationships between these architectural perspectives can be seen in the above diagram. The development, documentation and maintenance of business and IT architectures will typically form part of the processes of strategic thinking and strategy development in the organization.
These five management areas to be considered can be briefly defined as:
Such an architecture can be used to design and implement efficient, effective and integrated management solutions that are aligned to the business requirements of the organization and its Business Managers. This management architecture can be applied within an organization to:
These bullet points are also illustrated in Figure 3.10.
The key to the development of a management architecture is to ensure that it is driven by business needs and not developed for IT needs in isolation:
Management architectures need to be:
‘... business aligned, NOT technology driven’.
Within this overall structure, a management architecture is needed that can be applied to all areas of IT Management and not just to individual isolated areas. This can then be implemented in a coordinated programme of inter-working, to provide overall end-to-end Enterprise Management so essential to the effective management of today’s IT infrastructure. If only individual areas buy into the architecture, then individual ‘islands of excellence’ will develop and it will be impossible to provide the complete end-to-end solutions required to support today’s e-business solutions.
As well as ensuring that all areas of the IT are integrated, it is vital that the management architecture is developed from the business and service perspective (i.e. ‘top down’). Therefore, the key elements to agree and define before developing the management architecture are:
These are the key elements that need to be determined by SLM and IT Management. They provide crucial input to the development of business-focused management architectures. All too often management tools and processes have been focused on components and component management rather than services and business processes. This needs to be changed, with emphasis clearly on the design of management systems, processes and tools that are driven by business needs and are focused on the management of business processes and IT services. If the appropriate management architecture is designed and implemented, this will allow Service Management processes to focus on managing services and service quality and operate from end-to-end across the entire IT enterprise, providing true Enterprise Service Management. This will truly facilitate the management of services to ensure that services and service quality are closely aligned to the needs of the business.
The architectures described suggest that the future of network and systems management will be less focused on the technology and become more integrated with the overall requirements of the business and IT Management. These new systems and processes are already starting to evolve as the management standards for the exchange of management information between tools become more fully defined, by organizations such as the Distributed Management Task Force (DMTF). In essence, management systems will become: