Masoud Moghaddam

What Is Boolean Logic and How It Works

If you want to understand the answer to this question down at the very core, the first thing you need to understand is something called Boolean logic. Boolean logic, originally developed by George Boole in the mid-1800s, allows quite a few unexpected things to be mapped into bits and bytes. The great thing about Boolean logic is that, once you get the hang of things, Boolean logic (or at least the parts you need in order to understand the operations of computers) is outrageously simple. In this chapter, we will first discuss simple logic “gates” and then see how to combine them into something useful. A contemporary of Charles Babbage, whom he briefly met, Boole is, these days, credited as being the “forefather of the information age.” An Englishman by birth, in 1849, he became the first professor of mathematics in Ireland new Queen’s College (now University College) Cork. He died at the age of 49 in 1846, and his work might never have had an impact on computer science without somebody like Claude Shannon, who 70 years later recognized the relevance for engineering of Boole’s symbolic logic. As a result, Boole’s thinking has become the practical foundation of digital circuit design and the theoretical grounding of the digital age.

Building Intelligent Models from Data Mining and Expert Knowledge

While the idea of a data warehouse remains the core ideal of most corporate IT shops, the concepts surrounding the organization and architecture and, especially, the delivery mechanisms have changed remarkably. In today’s rapid changing and highly competitive marketplace, the idea of physical centralization has given way to a virtual data warehouse tied together with message-oriented middleware and distributed through application servers, Web servers, and intelligent database systems. The overriding influence in the corporate response to its information assets has been, of course, the dramatic rise of the Internet as a knowledge-bearing framework. From the global reach of the Internet, corporations have carved out their own pieces of this universe—intranets to bind together the information needs of the enterprise, extranets to solidify and control supply chains, and B2B and B2C service nets to give even the smallest corporation an equal footing with corporate giants as well as an essentially low-cost worldwide online presence. The Internet has given corporate decision-makers and knowledge workers a vast (and sometimes seemingly infinite) access to raw data—in fact, to “raw” knowledge.

What Is Fuzzy Logic and How It Works

The idea of fuzzy logic was first advanced by Dr. Lotfi Zadeh of the University of California at Berkeley in the 1960s. Dr. Zadeh was working on the problem of computer understanding of natural language. Natural language (like most other activities in life and indeed the universe) is not easily translated into the absolute terms of 0 and 1. (Whether everything is ultimately describable in binary terms is a philosophical question worth pursuing, but in practice much data we might want to feed a computer is in some state in between and so, frequently, are the results of computing.) It may help to see fuzzy logic as the way reasoning really works, and binary or Boolean logic is simply a special case of it.

Resilience and Resilience System

Resilience thinking is inevitably systems thinking, at least as much as sustainable development is. In fact, “when considering systems of humans and nature (social-ecological systems) it is important to consider the system as a whole.” The term “resilience” originated in the 1970s in the field of ecology from the research of C.S. Holling, who defined resilience as “a measure of the persistence of systems and of their ability to absorb change and disturbance and still maintain the same relationships between populations or state variables.” In short, resilience is best defined as “the ability of a system to absorb disturbances and still retain its basic function and structure.”

A General Business Resilience System Infrastructure

Knowledge is power, thus learning from experience is a fundamental way that helps individuals or organizations to improve and avoid previous mistakes. Accident Investigations (AI) and Operational Safety Reviews (OSR) are valuable for evaluating technical issues, safety management systems, and human performance and environmental conditions to prevent accidents, through a process of continuous organizational learning.

A Simple Model of Business Resilience System

In this, chapter we can recommend and define the scope of a simple Business Resilience System (BRS) based on a simple infrastructure that one could design. As we said this is just a simple approach to give some ideas to the readers. For a more complex system and infrastructure, one needs more sophisticated design and approach to the appropriate and applicable BRS for their organization and enterprise.

Event Management and Best Practice

In order to set up and configure an efficient Business Resilience System (BRS), we need to have a deep and broad understanding about event and event management with a focus on best practice. Such practice allows us to examine event filtering, duplicate detection, correlation, notification, and synchronization. In addition, it discusses trouble-ticket integration and how the trouble ticket and as part of BRS workflow can set the triggering point at BRS dashboard and set the maintenance modes and automation concerning event management. This chapter explains the importance of event correlation and automation. It defines relevant terminology and introduces basic concepts and issues. It also discusses general planning considerations for developing and implementing a robust event management system.

Building Intelligent Models from Data Mining

In order for Business Resilience System to function and induced advanced warning for proper action, the BRS Risk Atom and, in particular, the fourth orbit have to stay in stable status, by assessing the risk elements and responses. Thus, looking at risk assessment and understanding it are an essential fact, and it is inevitable; therefore, we need to build an intelligent model to invoke information from variety of data available to us at more than terabyte from around the globe we are living on. These data need to be processed by Process Data Point in the core of Risk Atom, either real time or manually. The feed point for PDP is structured on fuzzy or Boolean logic as suggested by us authors in this book. This chapter under lays foundation for Risk Atom by discussing the risk assessment and goes through process of building intelligent models, along with data mining and expert knowledge and a look at some fundamental principles that can interact with the Risk Atom.

Event Management Categories and Best Practices

Event management issues need to be addressed when an organization begins monitoring an IT environment for the first time, decides to implement a new set of systems management tools, or wants to rectify problems with its current implementation. Often it is the tool implementers who decide the approach to use in handling events. Where multiple tools are implemented by different administrators, inconsistent policies and procedures arise. The purpose of this chapter is to provide best practices for both the general implementation approach an organization uses to monitor its environment and the specific event management concepts defined in Chap. 2, “Introduction to Event Management.”

Business Resilience System Topology of Hardware and Software

Engineers endow artifact with abilities to cope with expected anomalies. The ability may make the system robust. They are, however, a designed feature, which by definition cannot make the system “resilient.” Humans at the front end (e.g., operators, maintenance people) are inherently adaptive and productive that allows them to accomplish better performances and sometimes even allows them to exhibit astonishing abilities in unexpected anomalies. However, this admirable human characteristic is a double-edged sword. Normally it works well, but sometimes it may lead to a disastrous end. Hence, a system relying on such human characteristics in an uncontrolled manner should not be called “resilient.” A system should only be called “resilient” when it is tuned in such a way that it can utilize its potential abilities, whether engineered features or acquired adaptive abilities, to the utmost extent and in a controlled manner, both in expected and unexpected situations or circumstances.