The Enablers

Authoritarian regimes in many countries, and the men that lead them, depend on the international management of licit and illicit funds under their control. Frank Vogl shows that curbing their activities for their kleptocratic clients is critical to secure democracy, enhance national security, and ensure international financial stability.

This is a story about complicity - about Trump's supporters being equally responsible for his tragic mismanagement of the pandemic.

"This book focuses on cases of sexual assault at Michigan State University (MSU), The Ohio State University (OSU), USA Gymnastics (USAG), the Catholic Church, and Pennsylvania State University (PSU) exploring the role that enablers have in sexual assault cases"--

Adopting the latest agile tools and practices won't be enough to respond to rapid market change. Leaders must first lay the groundwork by creating the right environment for these tools to work. Many managers struggle to install the underlying organizational operating system for business agility. High-performing agile organizations depend on the strength of six key enabling factors: leadership, culture, structure, people, governance, and ways of working. This book explains why these factors are important and how they work together to increase organizational agility. Real-world examples, stories, and tools will help leaders get realistic about the scope of changes needed in their organizations and show them how to get started. Karim Harbott does not offer a book of recipes. Instead, he focuses on mindset, principles, and general patterns. This book summarizes of the most important factors in increasing organizational agility and why they work, which leaders will need to consider in a so-called agile transformation. Because every organization is different, each will have its own route to agility and high performance. Managers will need to tackle all the areas that are crucial to creating an environment in which any chosen approach can work.

"Bohdan W. Oppenheim has pulled together experience-based insights of experts across industry, government, and academia into a comprehensive sourcebook for lean systems engineering principles and practices. This book can educate those new to lean engineering, as well as provide new insights and enablers that best-in-class organizations will want to adopt." —Dr. Donna H. Rhodes, Principal Research Scientist, SEAri and LAI, Massachusetts Institute of Technology "Lean for Systems Engineering is targeted at the practitioner who is trying to make systems engineering more effective in her or his organization or program, yet its scholarly underpinnings make the text very suitable for teachers. Educators and trainers who wish to weave lean thinking into their systems engineering curriculum will find this an invaluable text." —Earll M. Murman, Ford Professor of Engineering Emeritus, Massachusetts Institute of Technology "At last, a book that distills years of research and scholarly inquiry into a concise and coherent form for both the student and practitioner. This book will become the favored guide and 'must read' for any engineer and manager trying to establish and maintain lean practices and principles in their systems engineering/product development processes. —J. Robert Wirthlin, PhD, Lt. Col., USAF, Program Director of the Graduate Research and Development Management Program, Air Force Institute of Technology Visiting Faculty, U.S. Air Force Center for Systems Engineering "A vital contribution to linking lean practices to systems engineering. I will definitely use it as a reference for my course and writings on a value approach to product and system development." —Dr. Stanley I. Weiss, Consulting Professor, Dept. of Aeronautics and Astronautics, Stanford University "Taking the opportunity to develop and refine the Lean Enablers for Systems Engineering provided clear direction for Lean Engineering Accelerated Planning at Rockwell Collins. The Lean Enablers form a solid basis for Lean Product Development. Following this checklist and methodology promotes Lean value and waste elimination—and commonsense best practices." —Deborah A. Secor, Principal Project Manager and Lean Master, Rockwell Collins "Bo Oppenheim has been at the forefront of lean systems engineering for the better part of the last decade...An ardent advocate of lean systems engineering, the author has offered an honest appraisal of where lean systems engineering stands today. Practitioners interested in lean systems engineering will find the Lean Enablers especially useful."— Azad M. Madni, PhD, Professor and Director, SAE Program, Viterbi School of Engineering; Professor, Keck School of Medicine, University of Southern California

Co-dependency—of which enabling is a major element—can and does exist in families where there is no chemical dependency. Angelyn Miller’s own experience is a dramatic example: neither she nor her husband drank, yet her family was floundering in that same dynamic. In spite of her best efforts to fix everything (and everyone), the turmoil continued until she discovered that helping wasn’t helping. Miller recounts how she learned to alter the way she responded to family crises and general neediness, forever breaking the cycle of co-dependency. Offering insights, practical techniques, and hope, she shows us how we can transform enabling relationships into healthy ones.

This book provides full scope of automotive ECU development activities including cybersecurity and safety plus SOTIF. Every computing system has two, and only two attributes: Data Value and Data timing, which represent fully the system functionalities from the system external behavior point of view. The data driven system engineering is the approach to develop the system by focusing on the two attributes mentioned above, in which, the data values are derived by the system operation concept design, and the data timing is derived by the system latency design. Based on which, this book provides a full range of system and software engineering development activities: Requirement Elicitation Requirement Engineering System and Software Architecture Design System Operation Concept Design System and Software Structure Design Electronic Architect Design Functionality Allocation Failure Mode and Effect Analysis (FMEA) Safety including SOTIF Cybersecurity (full compliant with UN ECE 155/156) System and software Verification System and Software Integration and Verification System and Software Black Box Verification each of which has its own clearly defined scope and approach, which is different from the conventional development, in some cases even different from some ISO standards, for example: Safety Development: the safety requirements for every part in a vehicle are cascaded from the vehicle safety requirements, which is different from the Concept Phase in the Part 3 of ISO 26262, and the functional safety development will be fully covered by (1) Reliability (2) Availability (3) Quality. Error Detection and Protection: there are only two types of errors to be detected in a computing system: Data Value error and Data Timing error, to detect which, there are only two aspects to be considered: (1) input data (2) middle data and output data in addition to the platform error detection. The approaches of detection and protection include (1) data transfer protocol check, (2) data range and reasonable value check, (3) execution time check and control. FMEA: this book provides the optimized approach by following the data relationships between the input data, middle data and output data, which will be both inductive and deductive, and re-use the system operation concept that is built at the system development first phase, to make the development efficient. Cybersecurity: this book provides the full solution to cover the UN ECE 155 by implementing three aspects: (1) Trusted contents in the ECU (2) Authenticated access to the ECU (3) Authenticated communication with the ECU. Requirement Engineering: This book makes the goal and scope of requirement engineering in the computing system development specific, accurate and measurable by defining the scope as: the requirement engineering is to use the computer executable information to describe the system under development which consists only two types of information: Signal and Test Case, and defining the requirement quality measurement as: (1) Signals, either input or output signals, shall be computer readable. (2) Test cases shall be executable in the system. System Architecture Design: The goal of system architecture design is to provide the platform that transfers and transforms the input signal to become the required output signal via some middle data. This book introduces the following system functional modulizations based on the AUTOSAR that satisfies a generic automotive ECU structure: (1) Feature Function (2) Diagnostic Service (3) Cybersecurity Function (4) Serial Signal Manager (5) Application Mode Manager (6) AUTOSAR, and based on the characteristics of those functions, the book provides the approach to design the electronic architecture and allocate the functions to the architecture.

Transforming Culture offers a discussion and exploration of American work culture that can serve as a guide for organizational-culture change through the description and explanation of a model for change used at GM. The book describes the model, discusses culture-change tools that were derived from it and descriptions of how the tools work.