This paper introduces, at a high level, the key topics relevant to continuous availability of IBM systems infrastructures. After defining terms and identifying what is encompassed in the scope of continuous availability of IBM system infrastructures, we explain the IT (information technology) life cycle of planning and execution through which an IT organization and its infrastructure pass to create and continuously improve the IT infrastructure. Throughout, we show how each of the subsequent papers in this issue, drawing on real-life deployments, technology developments, and research efforts, expands on important aspects of this introductory discussion.
{"title":"Achieving continuous availability of IBM systems infrastructures","authors":"H. Morrill;M. Beard;D. Clitherow","doi":"10.1147/SJ.2008.5386519","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386519","url":null,"abstract":"This paper introduces, at a high level, the key topics relevant to continuous availability of IBM systems infrastructures. After defining terms and identifying what is encompassed in the scope of continuous availability of IBM system infrastructures, we explain the IT (information technology) life cycle of planning and execution through which an IT organization and its infrastructure pass to create and continuously improve the IT infrastructure. Throughout, we show how each of the subsequent papers in this issue, drawing on real-life deployments, technology developments, and research efforts, expands on important aspects of this introductory discussion.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"493-503"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386519","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68033285","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
High-availability service management (HASM) is defined as information technology (IT) service management that is designed to meet the business demand for availability of critical IT and IT-enabled business services. HASM requires the use of the Six Sigma method and analytical tools applied to key service management processes and services; event and incident monitoring and management design; high end and high-quality infrastructure and application configuration; high-availability (HA) architecture and design; and special solutions that implement HA patterns and associated technologies. In this paper, we examine HASM and discuss the process flow for designing and implementing HA technologies.
{"title":"IT service management for high availability","authors":"R. Radhakrishnan;K. Mark;B. Powell","doi":"10.1147/SJ.2008.5386521","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386521","url":null,"abstract":"High-availability service management (HASM) is defined as information technology (IT) service management that is designed to meet the business demand for availability of critical IT and IT-enabled business services. HASM requires the use of the Six Sigma method and analytical tools applied to key service management processes and services; event and incident monitoring and management design; high end and high-quality infrastructure and application configuration; high-availability (HA) architecture and design; and special solutions that implement HA patterns and associated technologies. In this paper, we examine HASM and discuss the process flow for designing and implementing HA technologies.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"549-561"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386521","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68034514","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
D. Bailey;E. Frank-Schultz;P. Lindeque;J. L. Temple, III
We present a brief introduction to three reliability engineering techniques: failure mode, effects, and criticality analysis; reliability block diagrams; and fault tree analysis. We demonstrate the use of one of these techniques, reliability block diagrams, in evaluating the availability of information technology (IT) systems through a case study involving an IT system supported by a three-tier Web-server configuration.
{"title":"Three reliability engineering techniques and their application to evaluating the availability of IT systems: An introduction","authors":"D. Bailey;E. Frank-Schultz;P. Lindeque;J. L. Temple, III","doi":"10.1147/SJ.2008.5386507","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386507","url":null,"abstract":"We present a brief introduction to three reliability engineering techniques: failure mode, effects, and criticality analysis; reliability block diagrams; and fault tree analysis. We demonstrate the use of one of these techniques, reliability block diagrams, in evaluating the availability of information technology (IT) systems through a case study involving an IT system supported by a three-tier Web-server configuration.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"577-589"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386507","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68034517","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
A common problem observed on mainframe installations, and one which presents a significant challenge for resiliency and high availability, involves soft failure incidents. n contrast to catastrophic failures, soft failures involve some degree of system shutdown without an obvious cause. This has been described with the phrase: “Systems don't break; they just stop running, and we don't know why.” Extending a medical paradigm, this paper proposes a new method for solutions deployed on IBM z/OS™ systems to respond when either the system or the application stops running. The current approach is to treat the “disease,” by determining the cause of he problem and taking action to prevent its recurrence. The new approach is to determine whether the system or application is behaving abnormally, identify the cause of this abnormal behavior, and take action to treat the “symptom.” This new approach uses machine learning and mathematical modeling to identify normal behavior, enabling the detection of abnormal behavior before it impacts the customer. Based on an analysis of critical problems and preliminary modeling work, the types of abnormal behavior identified are assigned to broad categories. In this paper, we describe the progress being made to address the challenge of soft failures by implementing this new paradigm.
{"title":"The resiliency challenge presented by soft failure incidents","authors":"J. M. Caffrey","doi":"10.1147/SJ.2008.5386508","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386508","url":null,"abstract":"A common problem observed on mainframe installations, and one which presents a significant challenge for resiliency and high availability, involves soft failure incidents. n contrast to catastrophic failures, soft failures involve some degree of system shutdown without an obvious cause. This has been described with the phrase: “Systems don't break; they just stop running, and we don't know why.” Extending a medical paradigm, this paper proposes a new method for solutions deployed on IBM z/OS™ systems to respond when either the system or the application stops running. The current approach is to treat the “disease,” by determining the cause of he problem and taking action to prevent its recurrence. The new approach is to determine whether the system or application is behaving abnormally, identify the cause of this abnormal behavior, and take action to treat the “symptom.” This new approach uses machine learning and mathematical modeling to identify normal behavior, enabling the detection of abnormal behavior before it impacts the customer. Based on an analysis of critical problems and preliminary modeling work, the types of abnormal behavior identified are assigned to broad categories. In this paper, we describe the progress being made to address the challenge of soft failures by implementing this new paradigm.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"641-652"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386508","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68034521","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
In this paper we examine the ways in which data center topology choices affect mission-critical business system availability and we propose a methodology for ensuring business resilience by assessing the risks to the mission-critical business systems and then designing a data center topology to mitigate these risks. This methodology is based on the IBM Business Resilience Framework, a framework that accounts for a wide range of concerns, from data center facilities to the business strategy and vision.
{"title":"Data center topologies for mission-critical business systems","authors":"R. Cocchiara;H. Davis;D. Kinnaird","doi":"10.1147/SJ.2008.5386510","DOIUrl":"https://doi.org/10.1147/SJ.2008.5386510","url":null,"abstract":"In this paper we examine the ways in which data center topology choices affect mission-critical business system availability and we propose a methodology for ensuring business resilience by assessing the risks to the mission-critical business systems and then designing a data center topology to mitigate these risks. This methodology is based on the IBM Business Resilience Framework, a framework that accounts for a wide range of concerns, from data center facilities to the business strategy and vision.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"47 4","pages":"695-706"},"PeriodicalIF":0.0,"publicationDate":"2008-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.2008.5386510","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68036046","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
J. Vayghan, Steve M. Garfinkle, Christian Walenta, D. C. Healy, Zulma Valentin
The ability to utilize data as an enterprise asset is central to every enterprise transformation initiative. This ability is critical for reusing data consistently throughout the enterprise and deriving actionable knowledge from it. Accurate and high-quality data must consistently propagate meaning and value throughout the enterprise and comply with the policies and processes of the enterprise. For a variety of reasons, large enterprises manage data at a local level (e.g., for each department and location), resulting in information "silos" where data is redundantly stored, managed, and processed, each with its own policies and processes, leading to inconsistency. IBM has begun a transformation process to establish a program for the management of its critical data, beginning with the creation of an enterprise data strategy that is aligned with IBM business strategy. In this paper, we describe the progress, to date, of the IBM transformation process. We focus on the activities of the IBM Enterprise Business Information Center of Excellence (EBI CoE), which is responsible for establishing, implementing, and deploying the enterprise data architecture program. The EBI CoE uses leading-edge information management technology and services from IBM and its partners to address enterprise data challenges. We present lessons learned and best practices derived from this ongoing internal transformation process that can be useful for enterprises facing similar data challenges as they transform their operations and business models.
{"title":"The internal information of IBM","authors":"J. Vayghan, Steve M. Garfinkle, Christian Walenta, D. C. Healy, Zulma Valentin","doi":"10.1147/SJ.464.0669","DOIUrl":"https://doi.org/10.1147/SJ.464.0669","url":null,"abstract":"The ability to utilize data as an enterprise asset is central to every enterprise transformation initiative. This ability is critical for reusing data consistently throughout the enterprise and deriving actionable knowledge from it. Accurate and high-quality data must consistently propagate meaning and value throughout the enterprise and comply with the policies and processes of the enterprise. For a variety of reasons, large enterprises manage data at a local level (e.g., for each department and location), resulting in information \"silos\" where data is redundantly stored, managed, and processed, each with its own policies and processes, leading to inconsistency. IBM has begun a transformation process to establish a program for the management of its critical data, beginning with the creation of an enterprise data strategy that is aligned with IBM business strategy. In this paper, we describe the progress, to date, of the IBM transformation process. We focus on the activities of the IBM Enterprise Business Information Center of Excellence (EBI CoE), which is responsible for establishing, implementing, and deploying the enterprise data architecture program. The EBI CoE uses leading-edge information management technology and services from IBM and its partners to address enterprise data challenges. We present lessons learned and best practices derived from this ongoing internal transformation process that can be useful for enterprises facing similar data challenges as they transform their operations and business models.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"46 1","pages":"669-683"},"PeriodicalIF":0.0,"publicationDate":"2007-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/SJ.464.0669","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"63995580","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
J. Black, C. Draper, T. Lococo, F. Matar, Christopher Ward
To develop an architecture for information technology service management (ITSM) and design integrated solutions, it is necessary to establish a common understanding of the key conceptual domains involved in delivering IT services-organization, process, tools, and technology-and how they interrelate. This paper presents an integration model for ITSM practitioners. The model is a framework for organizing the assets that constitute an ITSM design. Using this framework, an organization can document the available set of IT services offered and understand how they are composed from finer-grained services delivered by internal or external providers. Different service designs are supported, depending on the service requirements and organizational context. This integration model is applicable to both in-house IT organizations and IT service providers, regardless of industry or size of enterprise. It may be used by management software vendors to describe the capabilities of their ITSM offerings and to align those with the needs of different customers, by consultants and integrators to develop engagement materials and solution offerings, and by IT service delivery organizations to document their service designs.
{"title":"An integration model for organizing IT service management","authors":"J. Black, C. Draper, T. Lococo, F. Matar, Christopher Ward","doi":"10.1147/sj.463.405","DOIUrl":"https://doi.org/10.1147/sj.463.405","url":null,"abstract":"To develop an architecture for information technology service management (ITSM) and design integrated solutions, it is necessary to establish a common understanding of the key conceptual domains involved in delivering IT services-organization, process, tools, and technology-and how they interrelate. This paper presents an integration model for ITSM practitioners. The model is a framework for organizing the assets that constitute an ITSM design. Using this framework, an organization can document the available set of IT services offered and understand how they are composed from finer-grained services delivered by internal or external providers. Different service designs are supported, depending on the service requirements and organizational context. This integration model is applicable to both in-house IT organizations and IT service providers, regardless of industry or size of enterprise. It may be used by management software vendors to describe the capabilities of their ITSM offerings and to align those with the needs of different customers, by consultants and integrators to develop engagement materials and solution offerings, and by IT service delivery organizations to document their service designs.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"9 1","pages":"405-422"},"PeriodicalIF":0.0,"publicationDate":"2007-07-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"88883829","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
To develop an architecture for information technology service management (ITSM) and design integrated solutions, it is necessary to establish a common understanding of the key conceptual domains involved in delivering IT services—organization, process, tools, and technology—and how they interrelate. This paper presents an integration model for ITSM practitioners. The model is a framework for organizing the assets that constitute an ITSM design. Using this framework, an organization can document the available set of IT services offered and understand how they are composed from finer-grained services delivered by internal or external providers. Different service designs are supported, depending on the service requirements and organizational context. This integration model is applicable to both in-house IT organizations and IT service providers, regardless of industry or size of enterprise. It may be used by management software vendors to describe the capabilities of their ITSM offerings and to align those with the needs of different customers, by consultants and integrators to develop engagement materials and solution offerings, and by IT service delivery organizations to document their service designs.
{"title":"An integration model for organizing IT service management","authors":"J. Black;C. Draper;T. Lococo;F. Matar;C. Ward","doi":"10.1147/sj.463.0405","DOIUrl":"https://doi.org/10.1147/sj.463.0405","url":null,"abstract":"To develop an architecture for information technology service management (ITSM) and design integrated solutions, it is necessary to establish a common understanding of the key conceptual domains involved in delivering IT services—organization, process, tools, and technology—and how they interrelate. This paper presents an integration model for ITSM practitioners. The model is a framework for organizing the assets that constitute an ITSM design. Using this framework, an organization can document the available set of IT services offered and understand how they are composed from finer-grained services delivered by internal or external providers. Different service designs are supported, depending on the service requirements and organizational context. This integration model is applicable to both in-house IT organizations and IT service providers, regardless of industry or size of enterprise. It may be used by management software vendors to describe the capabilities of their ITSM offerings and to align those with the needs of different customers, by consultants and integrators to develop engagement materials and solution offerings, and by IT service delivery organizations to document their service designs.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"46 3","pages":"405-422"},"PeriodicalIF":0.0,"publicationDate":"2007-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.463.0405","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68066254","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
H. Madduri;S. S. B. Shi;R. Baker;N. Ayachitula;L. Shwartz;M. Surendra;C. Corley;M. Benantar;S. Patel
In this paper, we present the architecture of the IBM Tivoli® Change and Configuration Management Database. Its main features include a rich data model, automatic discovery of data for configuration items, visualization of application dependencies on configuration items, and multicustomer support. We discuss implementation topics, such as relationship management, composite configuration items, data federation, reconciliation of data from different sources, a security model for multicustomer support, and integration of change-management and configuration-management processes.
{"title":"A configuration management database architecture in support of IBM Service Management","authors":"H. Madduri;S. S. B. Shi;R. Baker;N. Ayachitula;L. Shwartz;M. Surendra;C. Corley;M. Benantar;S. Patel","doi":"10.1147/sj.463.0441","DOIUrl":"https://doi.org/10.1147/sj.463.0441","url":null,"abstract":"In this paper, we present the architecture of the IBM Tivoli® Change and Configuration Management Database. Its main features include a rich data model, automatic discovery of data for configuration items, visualization of application dependencies on configuration items, and multicustomer support. We discuss implementation topics, such as relationship management, composite configuration items, data federation, reconciliation of data from different sources, a security model for multicustomer support, and integration of change-management and configuration-management processes.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"46 3","pages":"441-457"},"PeriodicalIF":0.0,"publicationDate":"2007-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.463.0441","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68066256","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
C. Ward;V. Aggarwal;M. Buco;E. Olsson;S. Weinberger
This paper provides a summary of the best-practice change-management and configuration-management processes that express a core which conforms to ITIL® and discusses how they are extended for the service provider domain. These customizable processes, coupled with an execution platform and a configuration-management database, form the essence of the IBM Tivoli® Change and Configuration Management Database (CCMDB)—the heart of the IBM strategy for information technology service management (ITSM). We provide an overview of ITSM best practices and present details of the best-practice processes developed by IBM for the CCMDB product. We also describe a number of insights gained from implementing these processes and discuss issues that are key to implementing them in a service provider environment.
{"title":"Integrated change and configuration management","authors":"C. Ward;V. Aggarwal;M. Buco;E. Olsson;S. Weinberger","doi":"10.1147/sj.463.0459","DOIUrl":"https://doi.org/10.1147/sj.463.0459","url":null,"abstract":"This paper provides a summary of the best-practice change-management and configuration-management processes that express a core which conforms to ITIL® and discusses how they are extended for the service provider domain. These customizable processes, coupled with an execution platform and a configuration-management database, form the essence of the IBM Tivoli® Change and Configuration Management Database (CCMDB)—the heart of the IBM strategy for information technology service management (ITSM). We provide an overview of ITSM best practices and present details of the best-practice processes developed by IBM for the CCMDB product. We also describe a number of insights gained from implementing these processes and discuss issues that are key to implementing them in a service provider environment.","PeriodicalId":55035,"journal":{"name":"IBM systems journal","volume":"46 3","pages":"459-478"},"PeriodicalIF":0.0,"publicationDate":"2007-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"https://sci-hub-pdf.com/10.1147/sj.463.0459","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"68066259","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}