International Finance Faculty
On the topic:
“Enterprise Application Systems Management”
Done by: Gabrielyan Arman
Group IFF 4-4
Scientific advisor: Matrizaev Bahadir
Summary: Management of enterprise application systems is here to stay. IT teams have to quickly embrace newer techniques that will enable such systems to be managed effectively. Central to these techniques is to capture, build, and make available libraries of reusable knowledge about the systems they have to manage. The framework of knowledge areas presented in this document is a starting point for IT teams to organize these libraries. IT teams should extend this framework to include areas such as security, disaster prevention and recovery, capacity planning, and service-specific reporting. Creating a body of knowledge that can be used for both manual and automated application system management and providing the tools to allow IT teams to contribute and collaboratively enhance this body of knowledge are the keys to taming the complexity of enterprise application system management.
* Infrastructure Management vs. Service-Level Management
* Complexity of Managing Application Ecosystems
* IT’s Challenge
* Organization of the Body of Knowledge
* The Shape and Form of the Body of Knowledge
Current generation application systems are complex ecosystems—the various applications within the ecosystem have many interdependencies among them and are generally integrated at a platform level; they are not a collection of independent applications using application level integration schemes. There is a strong interdependency between business systems, IT systems, software systems, platforms, and IT infrastructure. As a result, a holistic management of the entire ecosystem is required to achieve consistently high quality of service—they cannot be managed as independent silos. The complexity of these systems implies that IT teams tasked with their management need to have specialized interdisciplinary knowledge and techniques beyond what has been traditionally used to manage individual elements of infrastructure. This paper introduces a framework to categorize the knowledge areas required to manage complex, mission critical application systems, and presents ten different areas of knowledge. The information in this article is useful to CIOs and operational managers engaged in the management of enterprise application systems. Infrastructure Management vs. Service-Level Management
As enterprises have become increasingly dependent on services provided by software applications to function, managing the quality of these services in terms of parameters such as up-time, performance, turnaround time, security, and consistency has become ever more important. The business criticality of services is such that any disruption is no longer treated as an IT problem; service disruptions are immediately brought to the attention of the CXOs of the enterprise. The CIOs mantra today is to reduce planned downtime for the business critical services to zero—unplanned downtime or service disruption is a cardinal sin. IT management today has been forced to rethink their methods of managing and operating IT infrastructure. For a long period of time, IT managers delivered against infrastructure-level SLAs, such as “if server XYZ had 99.9% availability” or “if network segment DEF had an average latency of less than 30 ms,” all was well. The standards for management, the operational processes, and the expertise built within IT management teams was geared toward the management of individual components of infrastructure. However, IT management teams today are increasingly having to deal with SLAs at the level of application services and sometimes even business...