| |
| |
List of Figures | |
| |
| |
List of Tables | |
| |
| |
List of Acronyms | |
| |
| |
Acknowledgments | |
| |
| |
About the Author | |
| |
| |
| |
Setting the Stage | |
| |
| |
| |
Introduction | |
| |
| |
| |
The Trend toward Large-Scale, Richly Interconnected Systems | |
| |
| |
| |
Why This Book? | |
| |
| |
| |
Organization of the Book | |
| |
| |
Endnote | |
| |
| |
| |
Context and Trends | |
| |
| |
| |
Changing the Strategic Environment in the U.S. Department of Defense | |
| |
| |
| |
The Imperative to Share Information across Agencies | |
| |
| |
| |
Information Sharing to Counter Terrorism | |
| |
| |
| |
Other Examples of Information Sharing across Organizational Boundaries | |
| |
| |
| |
Enabling Conditions | |
| |
| |
| |
Information Technologies Environment | |
| |
| |
| |
Improved Performance and Reduced Costs Drive Information Technologies | |
| |
| |
| |
Global Information Infrastructure | |
| |
| |
| |
Mobile Society, Wireless Lifestyle | |
| |
| |
| |
Increased Reliance, Increased Risk | |
| |
| |
| |
Institutional Trends: Enterprisewide, Top-Down Perspective | |
| |
| |
| |
Clinger-Cohen Act of 1996 | |
| |
| |
| |
Enterprise Architectures | |
| |
| |
| |
Changes to the DoD Requirements Process | |
| |
| |
| |
Implications for Systems and Programs | |
| |
| |
| |
A Look Ahead | |
| |
| |
Endnotes | |
| |
| |
| |
Concepts and Frameworks | |
| |
| |
| |
Mega-System Concepts | |
| |
| |
| |
What Is a System? | |
| |
| |
| |
Systems as Components of Larger Systems | |
| |
| |
| |
What Is a �System-of-Systems?� | |
| |
| |
| |
What Differentiates �System-of-Systems� from Similar Terms? | |
| |
| |
| |
Mega-Systems | |
| |
| |
| |
What Are Mega-Systems? | |
| |
| |
| |
Emergence of Mega-Systems | |
| |
| |
| |
�Composed� Mega-Systems | |
| |
| |
| |
�Designed� Mega-Systems | |
| |
| |
| |
�Dynamically Assembled� Mega-Systems | |
| |
| |
| |
Summary | |
| |
| |
Endnotes | |
| |
| |
| |
A Framework for Exploring Mega-Systems | |
| |
| |
| |
Basis for the Framework | |
| |
| |
| |
Elements of the Basic Framework | |
| |
| |
| |
The System Behavior Vector | |
| |
| |
| |
The Decision-Making Vector | |
| |
| |
| |
The Context or Environment Vector | |
| |
| |
| |
Region of Well-Bounded Systems | |
| |
| |
| |
Region of Mega-Systems | |
| |
| |
| |
Tame versus Wicked Problems | |
| |
| |
Endnotes | |
| |
| |
| |
Engineering and Acquiring Mega-Systems | |
| |
| |
| |
What Is Systems Engineering? | |
| |
| |
| |
Systems Engineering Process | |
| |
| |
| |
Software Engineering Processes | |
| |
| |
| |
Emergence of System-of-Systems Engineering | |
| |
| |
| |
Mega-System Challenges for Systems Engineers | |
| |
| |
| |
Increasing Scope and Complexity | |
| |
| |
| |
More Diverse Stakeholders | |
| |
| |
| |
Multiple, Often Conflicting, Objectives and Constraints | |
| |
| |
| |
Dissimilar Time Scales | |
| |
| |
| |
Test and Evaluation Challenges and Constraints | |
| |
| |
| |
Vulnerabilities: Expected and Unexpected Negative Effects | |
| |
| |
| |
Troubled Large-Scale Systems | |
| |
| |
| |
Levels of Systems Engineering | |
| |
| |
| |
Enterprise Systems Engineering Profiler | |
| |
| |
| |
Quadrants and Dimensions | |
| |
| |
| |
Concentric Rings | |
| |
| |
| |
Using the Enterprise Systems Engineering Profiler | |
| |
| |
| |
Summary | |
| |
| |
Endnotes | |
| |
| |
| |
Case Studies in Engineering Mega-systems | |
| |
| |
| |
Introduction to Mega-System Case Studies | |
| |
| |
| |
A Note about Case Studies | |
| |
| |
| |
Approach to Mega-System Case Studies | |
| |
| |
Endnotes | |
| |
| |
| |
Single Integrated Air Picture | |
| |
| |
| |
Motivation: Moving from Independent Systems to a Theater-Wide Integrated Capability | |
| |
| |
| |
Standing up a System Engineering Organization | |
| |
| |
| |
SIAP System Engineering Process | |
| |
| |
| |
Initial Strategy: Incremental Blocks | |
| |
| |
| |
Block 0: Demonstration of SIAP System Engineering Process | |
| |
| |
| |
Block 1: Taking on Additional Technical Issues for Resolution | |
| |
| |
| |
Strategy Shift: From Developing Solutions to Building a Model-Driven Architecture | |
| |
| |
| |
Model-Driven Architecture (MDA)� | |
| |
| |
| |
Integration into Warfighting Platforms | |
| |
| |
| |
Distributed Test Environment: Joint Distributed Engineering Plant (JDEP) | |
| |
| |
| |
Organizational Changes | |
| |
| |
| |
Building the IABM | |
| |
| |
| |
Incremental Configurations | |
| |
| |
| |
Demonstration and Test | |
| |
| |
| |
Challenges of Weapon System Integration and Synchronization | |
| |
| |
| |
Formalizing the SIAP | |
| |
| |
| |
Summary | |
| |
| |
| |
SIAP Mapping to the Systems Engineering Profiler | |
| |
| |
| |
Insights for Engineering Mega-Systems | |
| |
| |
Endnotes | |
| |
| |
| |
Developing the Electronic Product Code Network | |
| |
| |
| |
Background | |
| |
| |
| |
The Auto-ID Center | |
| |
| |
| |
The Vision: An Internet of Things | |
| |
| |
| |
Concept and Technologies | |
| |
| |
| |
Data Capture Portion | |
| |
| |
| |
Intelligent Infrastructure | |
| |
| |
| |
RFID Design Process and Implementation | |
| |
| |
| |
Architecture and Design | |
| |
| |
| |
Business Case Research | |
| |
| |
| |
Early Field Tests | |
| |
| |
| |
Privacy Pushback | |
| |
| |
| |
Release of First EPC Standards | |
| |
| |
| |
Transition from Research to Commercialization | |
| |
| |
| |
Early Pilots | |
| |
| |
| |
Maturation of the EPC Standards | |
| |
| |
| |
EPC Adoption | |
| |
| |
| |
Summary | |
| |
| |
| |
EPCglobal Network Mapping to the Extended Framework | |
| |
| |
| |
Insights for Engineering Mega-Systems | |
| |
| |
Endnotes | |
| |
| |
| |
Observations from the Case Studies | |
| |
| |
| |
Case Study Recap | |
| |
| |
| |
Observations | |
| |
| |
| |
Greater Diversity of Stakeholders and Interests | |
| |
| |
| |
Broader Set of Considerations | |
| |
| |
| |
Convergence on Critical Infrastructure Standards and Design Tenets | |
| |
| |
| |
Requirements | |
| |
| |
| |
Discovery Engineering | |
| |
| |
| |
Role of Grand Design | |
| |
| |
| |
Managing Risk and Uncertainty | |
| |
| |
| |
Leadership | |
| |
| |
Endnotes | |
| |
| |
| |
The Way Ahead | |
| |
| |
| |
The Way Ahead | |
| |
| |
| |
Emerging Tenets | |
| |
| |
| |
Strategic Context: Iterative and Incremental Strategy | |
| |
| |
| |
Implementation Context: Agreement on Infrastructure and Design Tenets | |
| |
| |
| |
Stakeholder Context: Working to Identify Intersecting Interests | |
| |
| |
| |
System Context: Value of Discovery Engineering | |
| |
| |
| |
Extensions to Current Practice: Managing Uncertainty | |
| |
| |
| |
Matching Practice to Circumstances | |
| |
| |
| |
An Emerging View of Systems Engineering as a Continuum of Practice | |
| |
| |
| |
Refining the Engineering Tenets: A Way Ahead | |
| |
| |
| |
An Emerging View of Next-Generation Practice | |
| |
| |
| |
Concluding Thoughts | |
| |
| |
| |
Postscript: Profiling a Complex Acquisition Program | |
| |
| |
| |
Multiple Purposes of the Study | |
| |
| |
| |
Approach | |
| |
| |
| |
Tailor the Profiler | |
| |
| |
| |
Clarify Sponsor Goals and Objectives | |
| |
| |
| |
Develop Interview Protocol | |
| |
| |
| |
Conduct the Interviews and Synthesize the Responses | |
| |
| |
| |
Conduct Workshops with Key Agency Staff and Leadership | |
| |
| |
| |
Review and Assess Agency Business Practices | |
| |
| |
| |
Findings | |
| |
| |
| |
Role-Specific Profiles | |
| |
| |
| |
Site Manager Profile | |
| |
| |
| |
Project Manager Profile | |
| |
| |
| |
Agency-Wide Profile | |
| |
| |
| |
External Stakeholder Profile | |
| |
| |
| |
Similarities and Differences in the Agency Profiles | |
| |
| |
| |
The Profile as an �Uncertainty Map� | |
| |
| |
| |
Recommended Practices for Dealing with Uncertainty | |
| |
| |
| |
Characterizing Uncertainty | |
| |
| |
| |
Techniques to Deal with Uncertainty | |
| |
| |
| |
Environmental Scanning | |
| |
| |
| |
Stakeholder Analysis and Management | |
| |
| |
| |
Risk Management and Uncertainty Management | |
| |
| |
| |
Putting Ideas into Practice | |
| |
| |
| |
Conclusion | |
| |
| |
Endnotes | |
| |
| |
References | |
| |
| |
Index | |