2010 Complex Systems Engineering for the Global Information Grid
1 like266 views
The document discusses complex systems engineering within the context of the global information grid, highlighting the role of the network-centric operations industry consortium (NCOIC) in promoting interoperability among defense contractors. It outlines various complex systems properties, structures, and design strategies, emphasizing the need for federated coordination approaches alongside traditional control methods. The conclusion calls for extensive research and a coordinated initiative to advance complex systems engineering in response to evolving technological requirements.
2010 Complex Systems Engineering for the Global Information Grid
- 1. Complex Systems Engineering for the Global information Grid Bob Marcus robert.marcus@sri.com Wednesday, December 23, 15
- 2. Overview of Talk • Background • NCOIC and the Global Information Grid • Complex Systems Engineering Strategies • Foundation Information Grid (NCOIC Demo) • Conclusion Wednesday, December 23, 15
- 3. My Background • Industrial system of systems architecture and implementation at Boeing and General Motors • Military systems of systems architecture and standards as an SRI consultant to the DoD • Author of “Great Global Grid: Emergency Technology Strategies” (2002) • Director of Colorado State Grid Initiative • Chair of Modeling, Simulation and Demonstration Working Group at Network Centric Operations Industry Consortium (NCOIC) – Foundation Information Grid Demonstration as a step towards the Global Information Grid Wednesday, December 23, 15
- 4. Wednesday, December 23, 15
- 5. The NCOIC and the Global Information Grid Wednesday, December 23, 15
- 6. Overview of the NCOIC • The Network-Centric Operations Industry Consortium (NCOIC.org) membership includes all of the leading defense contractors • The NCOIC’s mission is to facilitate collaboration on creating standardized interoperability frameworks • The Modeling, Simulation and Demonstration Working Group’s goal is to initiate foundation demonstrations for future system of systems architectures • One example of these future architectures is the DoD’s Global Information Grid • The initial demonstration is called the Foundation Information Grid Wednesday, December 23, 15
- 7. Information Grid Wednesday, December 23, 15
- 8. Colorado Information Grid Vision Instruments Data Visualization Large-Scale Databases Small Computers HPC Mobile Computing Sensors Wednesday, December 23, 15
- 9. Wednesday, December 23, 15
- 10. Global Information Grid (GES.DOD.MIL) Wednesday, December 23, 15
- 11. Standards Needed at Multiple Levels Virtualized Storage Applications, Data Analysis and Data Mining Interface Protocols and APIs Non-functional Capabilities e.g. IA, QoS, Policies Data, Metadata, and Semantic Representations Data Transport and Messaging Mechanisms Network and Communication Protocols Virtualized Databases Data Processing, Transformation, and Fusion Wednesday, December 23, 15
- 12. Complex Systems Engineering Strategies Wednesday, December 23, 15
- 13. Complex Systems Properties • Emergent- Macroscopic dynamics and variables occur in the system, which is not easily predictable from local dynamics • Multiscale Interactive - The macroscopic and component-level behavior interact in a measurable way • Non-equilibrium Metastable – Short term stability with large state changes possible under small perturbations • Evolutionary Adaption- The system exhibits altered behavior in response to environmental changes • Self Organizing - Coordinated behavior can take place among components without centralized guidance Wednesday, December 23, 15
- 14. Structures in Complex Systems • Component = Basic element of functionality in the system. Intrinsic behavior under environment influences. • Collaboration = Interactions without macroscopic coordinators. Behavior influenced by peer-to-peer interactions. • Coordination = Interaction possibly managed by coordinators to support group goals. Behavior influenced by group dynamics. • Control = Interactions directed hierarchically to foster global goals. Behavior constrained by controller. • • All of these structures can be present in a system of systems and can be mixed and combined recursively Wednesday, December 23, 15
- 15. Component Complex System Structures Controller Component Collaboration Component Coordination Coordinator Controller Coordinator Controller ControllerCoordinator Wednesday, December 23, 15
- 16. Structures in Complex Systems Components Collaboration Coordination Control Have dynamics and/or goals Individual dynamics and/ or goals Shared dynamics and/or goals Global dynamics and/or goals Capable of adaptable behavior Individuals adapt Individuals and coordinators adapt Controllers adapt Individuals Interaction Communities of Interest Enterprise Molecules in Chemistry Gas Liquid Solid No coupling Loose coupling Cooperative processes Tight coupled Citizens in Government Town Meetings Representatives Authoritarian Computers in network Internet Extranet Intranet Neurons in Neurodynamics Nervous System Brain Cerebellum Cognitive system Wednesday, December 23, 15
- 17. Complex Systems Design Strategies • Bottom up – Self-organizing, Emergent collaboration and coordination from interactions. • Top down - Traditional systems engineering, Pre- defined coordination and interactions • Matchmaking – Coordination is based on matching and combining existing components to meet requirements • Middle Out – Coordination combines existing components and collaborations but also drives new requirements, collaborations and components Wednesday, December 23, 15
- 18. Top Down Design (Control-based) Existing, Enhanced, Composite and possible new services and/or systems USERS Capability specifications (with priorities) Capability description Set of Services Needed Set of Requirements Requirements Analysis User Requirements and Derived Requirements Wednesday, December 23, 15
- 19. Bottom Up Design (Collaboration-based) Existing, Enhanced, Composite and possible new services and/or systems USERS Capability specifications and possible new capabilities Capability description (with cost of implementation) and possible new capabilities Capabilities available Set of Services Available Advertising User Interfaces Wednesday, December 23, 15
- 20. Matchmaking ( SOA Orchestration) Existing, Enhanced, Composite and possible new services and/or systems USERS Capability specifications (with priorities) Capability description (with cost of implementation) Set of Services Set of Requirements Matchmaking User Requirements and Derived Requirements Wednesday, December 23, 15
- 21. Middle Out Design (Coordination-based) Existing, Enhanced, Composite and possible new services and/or systems USERS Capability specifications (with priorities) and possible new capabilities Capability description (with cost of implementation) and possible new capabilities New capabilities available New capabilities needed Set of Services Set of Requirements Mediating User Requirements and Derived Requirements Wednesday, December 23, 15
- 22. Shared Resource Integration Process Reusable Resource Repository Program 1 (Component) Commercially Available Tools and Services Centralized Standards and Reuse Organization (Control) Program 2 (Component) Program 3 (Component) Shared Resources Integration Team (Coordination) Wednesday, December 23, 15
- 23. Foundation Information Grid (NCOIC Demo) Wednesday, December 23, 15
- 24. Foundation Information Grid • Components – Diverse data bases and physical storage with application program interfaces. • Control – Components under a single organization. Data access controlled by management. Can be viewed as a high level component. • Coordination – Components under diverse management use shared metadata and data access through a Coordinator. (Storage Resource Broker (SRB) from UCSD). • Collaboration – Data sharing across coordination zones using metadata mappings and middleware. Cooperation across communities based on need to share. Wednesday, December 23, 15
- 25. Foundation Information Grid Data Data DataData Data Data Controller Coordinator Coordinator Data Peer-to-peer Collaboration Direct Control Support for Coordination Peer-to-peer Collaboration Wednesday, December 23, 15
- 26. Foundation Information Grid Strategy • A Community of Interest (COI) is a group of users who have agreed to collaborate and have a centralized process for defining shared capabilities • COIs define an architectural framework for their components • The components are placed in the framework to implement a COI coordination for users • Multiple COIs can voluntarily collaborate to share a subset of their coordinated components • Communities of Interest must agree on interoperability standards for the shared collaborative capabilities Wednesday, December 23, 15
- 27. Application -> SRB -> Data Storage System Databases Application Interfaces Metadata-based Access Data Grid Database Interfaces The SRB (Storage Resource Broker) is middleware that supports multiple application interfaces to diverse databases and storage systems Next four slides produced by collaborators at UCSD SRB Group Wednesday, December 23, 15
- 28. Distributed SRB Agents Archives HPSS, ADSM, UniTree, DMF Databases DB2, Oracle, Sybase File Systems Unix, NT, Mac OSX Application C, C++, Linux I/O Unix Shell Dublin Core Resource, User User Defined Application Meta-data Remote Proxies DataCutter Third-party copy Java, NT Browsers WebProlog Predicate MCAT HRM Storage Resource Broker Wednesday, December 23, 15
- 29. SRB Data Integration Zone (Coordination) SRB MCAT DB SRB SRB SRB SRB SRB Wednesday, December 23, 15
- 30. SRB Data Integration Zone (Coordination) SRB MCAT DB SRB SRB SRB SRB SRB •Data Grid has arbitrary number of servers •Metadata Catalog (MCAT) used for access Wednesday, December 23, 15
- 31. Collaboration Across Zones MCAT1 MCAT2 MCAT3 Server1.1 Server1.2 Server2.1 Server2.2 Server3.1 Wednesday, December 23, 15
- 32. Next Steps • Determine user requirements for the Global Information Grid • Work with groups responsible for standards and implementation of core services for Global Information Grid • Develop a coordination strategy matching Foundation Information Grid capabilities and end-user requirements Wednesday, December 23, 15
- 34. Questions from 1995 • What are the basic laws of the scientific discipline of complex systems? • What are the generic principles for complex systems engineering? • Is it possible to build customizable generic tools for the modeling, simulation, and analysis of complex systems? • How can we maintain systems with constantly changing requirements? • Is there a management strategy for dealing with systems that are too complex for individuals or small groups to understand? • Are there unique characteristics of complex systems that are composed primarily of multiple intelligent entities, both human and non-human? • How can non-adaptable system elements be reengineered, and can adaptability be 'designed into' complex systems in the first place? Wednesday, December 23, 15
- 35. Final Thoughts • The fundamental change that complex systems bring to systems engineering is the need to create federated coordination strategies in addition to control algorithms. • Implementing this new paradigm will require extensive research in many disciplines during the next decade. • Due to the broad fundamental impact of complex systems engineering, there should be a coordinated initiative to support research projects in this domain. Wednesday, December 23, 15