1 / 12

ConOps Development in a Highly Networked System

ConOps Development in a Highly Networked System. Tom Herald Senior Staff Systems Engineer Lockheed Martin Maritime Systems & Sensors 9500 Godwin Drive 105/013 Manassas, VA 20110-4157 tom.herald@lmco.com (703) 367-2973 FAX: (703) 367-3942. Dinesh Verma, Ph.D.

koconnell
Télécharger la présentation

ConOps Development in a Highly Networked System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ConOps Development in a Highly Networked System Tom Herald Senior Staff Systems Engineer Lockheed Martin Maritime Systems & Sensors 9500 Godwin Drive 105/013 Manassas, VA 20110-4157 tom.herald@lmco.com (703) 367-2973 FAX: (703) 367-3942 Dinesh Verma, Ph.D. Professor and Director, SDOE Program Stevens Institute of Technology Castle Point on Hudson dverma@stevens-tech.edu Hoboken, NJ 07030 (201) 216-8645 (or 8334) FAX: (201) 216-5080

  2. NCS ConOps Development Agenda • Current Tops-down ConOps Development • Network Centric Warfare • Bottoms-up Performance Capability Assessment • Research Considerations • Performance Assessment • Summary

  3. Others . . . Non-War Operations Planning Needs Supportability Political Inputs Training & Doctrine Financial Control Coalition Forces Multitude of Stakeholder Needs Program Control Domestic Forces Program & Financial Operations System-Level Concept of Operations Document Contents Systems Engineer Responsible Focal Point . . . Sub-System Solution Elements New Element 1 New Element 2 New Element M . . . Element 1 Element 2 Element 3 Element 4 Element 5 Element N Military ConOps Development and System Requirements Generalized Methodology Today:

  4. Platform Information Sensor Raw Data To Information Control Information Command & Control Information Control Decision Maker Sensor Grid Shooter Information Control/Comm Grid Information Grid Network Centric Warfare Source: Vision of NCW provided in a Department of Defense Report to Congress – September 2001 – http://www.c3i.osd.mil/NCW/

  5. Multitude of Stakeholder Needs Others . . . Non-War Operations Planning Needs Supportability • Performance Capability-to-Stakeholder Mapping • Affordability, Schedule and Value Trade Optimizations • Identification of New-Development System Needs Political Inputs Training & Doctrine Financial Control Coalition Forces Network-Centric Concept of Operations Document Content Program Control Domestic Forces Program & Financial Operations Research Area #2: Operational Mapping & Optimizations NCS Systems Engineer - Program Focal Point New Systems ConOps • Benefit of Network Connectivity • System Redundancy • Develop a Total Capability Listing • Dynamic vs. Static Stakeholder Requirements • New System Operational ConOps Input • Technology Evolution Guidance • Supportability Balance Research Area #3: New Development ConOps & Supportability Research Area #1: Performance Capability Assessment ... Legacy Systems Network New System M New System 1 Existing and Legacy Systems . . . System 1 System 2 System 3 System 4 System 5 System N Research Opportunity in Support of NCS Systems Engineer

  6. Multitude of Stakeholder Needs Others . . . Non-War Operations Planning Needs Supportability • Performance Capability-to-Stakeholder Mapping • Affordability, Schedule and Value Trade Optimizations • Identification of New-Development System Needs Political Inputs Training & Doctrine Financial Control Coalition Forces Network-Centric Concept of Operations Document Content Program Control Domestic Forces Program & Financial Operations Research Area #2: Operational Mapping & Optimizations NCS Systems Engineer - Program Focal Point New Systems ConOps • Benefit of Network Connectivity • System Redundancy • Develop a Total Capability Listing • Dynamic vs. Static Stakeholder Requirements • New System Operational ConOps Input • Technology Evolution Guidance • Supportability Balance Research Area #3: New Development ConOps & Supportability Research Area #1: Performance Capability Assessment ... Legacy Systems Network New System M New System 1 Existing and Legacy Systems . . . System 1 System 2 System 3 System 4 System 5 System N Research Opportunity in Support of NCS Systems Engineer

  7. Total Performance of a Network-Centric System ≈ • N N M • PNCS=Pi +((Pi ∩Pj) k ); For all i ≠ j AND • i = 1i = 1k = 1where k > 0 (i.e. the system • j = 1 pairing has connectivity) • PNCS= The total performance of the Network-Centric System • Pi = The performance capability of a Stand Alone System (no network connection) • Pj = The performance capability of a Stand Alone System (no network connection) • N = The number of Independent Systems (Network Nodes) • M = The number of independent functional connection paths for a Pi and Pj pairing • Pi ∩Pj = This intersection represents the resultant performance from the system connectivity, which could be Zero if there is no system advantage or detractor, Positive if the connectivity advantages the ConOps (Mission Needs) or Negative if the connectivity is not required by the ConOps (i.e. outside of the mission performance boundaries) NOTE: System Triples, Quadruples, etc. can also be considered as necessary.

  8. Measuring the Performance of the NCS? • Individual System Contribution (as understood by it’s own ConOps document) • Networking of the systems results in potentially positive or negative Performance Benefit. • The linkage of systems offers new direct functionality • The linkage of systems offers an indirect functionality benefit (i.e., multiple path redundancy, degraded modes of operability) • Negative linkage impacts such as Bandwidth overload, un-needed system-to-system connectivity leading lower system availability with no new performance benefit. • Changing Program Needs Drives Varying NCS Solutions

  9. Direct Connectivity in NCS • Intentional Connectivity • Mission Performance requires linkage (Secure Wire, Microwave) • Connect of System pairs yields summation of the separate functionality of the 2 systems PLUS New capabilities that the linkage allows • Possible Redundancy or Conflicts due to identical input types yielding different results (i.e. meteorological reports) that will require arbitration • Example: Connecting an Army Company information to a Theater Battle Command center. Direct Connectivity to provide better decisions.

  10. Indirect Connectivity in NCS • Unintentional Connectivity • Result of WAN connections • No Direct ConOps Requirement fulfilled by the connectivity • Multi-path connectivity - Could be an advantage • Example: Weather Radar Connectivity in a NCS. Valuable to those systems that use weather in decisions, and useless to all other LAN systems. Thus connectivity is available indirectly, but potentially not valuable.

  11. N Systems Network Interactions (if any at all) MMetrics System Unique Common Metrics N Systems X Ci Capabilities General Metrics Structure for NCS Systems Metrics Categories: • System Architecture • Data/Information & Networking • Supportability • Logistics • Technology Evolution 6. Cost Metrics Axis Y = Capabilities per System, N. Axis X = Metrics, M, for each capability (as appropriate) Axis Z = Networking Advantages (or Disadvantages)

  12. Conclusions • NCS Complexity drives the need to provide the NCS Engineer (or team) with more insight for mapping out a NCS ConOps. • Must Support NCS Engineer with: • Bottoms-up Performance Capability Assessment Method • Providing Mapping from Possible to Stakeholder Needs • Prioritizing of System Deployment • Optimizing Solution Recommendation • Facilitate variable solution sets within ConOps Development • Identify Gaps and Drive New System ConOps Development

More Related