FIGURE 4
SoS operational issues. Figure 5 also depicts the evolving and maturing capa- bility of the MoP Framework maps, as the MoPs for the COE/security layer have yet to be developed and coordinated.
Each MoP has a unique number. Tis numbering schema allows analysts and evaluators to leverage the MoP Frame- work for MC Display Hardware and import the information to event- or sys- tem-specific data source matrices, while still maintaining the traceability and ori- gin of these MoPs.
CONCLUSION By identifying and aligning MoPs for each operational capability subcategory, the MoP Framework provides credible and traceable metrics for analysts that are reusable across Agile Process activities and between organizations in support of a particular application (i.e., event). Tis reusability is based on repeated applica- tion of operational capability and the repeated need to measure operational performance and utility.
Te standardization of a MoP Framework Armywide will promote cost avoidance by reducing the re-creation of testing objectives and streamlining instrumen- tation planning. Te implementation of a unified MoP Framework will also give greater validity to the operational rel- evance of testing. Analytic requirements exchanged between organizations using this standardized construct provide for clear cost-evaluation guidelines, prioriti- zation and traceable evaluation.
For more information, please contact Dr. Dennis Bushmitch (dennis.bushmitch.
civ@mail.mil, 410-322-2054) or Mr. Brian Hobson (
bhobson@trideum.com, 913-544-5101).
MISSION THREAD, IER, DATA TYPES
Position Location Information Thread
Mission Effectiveness Mission Threads Application
Common Operating Environment/ Security
Network Routing/Quality of Service Network Transport Waveform
Spectrum/Radio Frequency Applicable Systems:
Font color by level of
completeness/maturity for MoP/ availability of requirements
Tactical Intelligence Ground ReportingThread
File Transfer (fragmentary order)
Video (Full Motion Video) Stream
Unit’s ability to obtain an integrated common picture at the tactical edge Unit’s ability to maintain running estimates Unit’s ability to establish an integrated common operational picture Unit’s ability to interoperate with joint, interagency, intergovernmental and Unit’s ability to mitigate network operations challenges and/or complexity
Message completion rate
Client reachability success rate by data type Average E2E session delay by data type Data max client group
TBD
Session completion rate Client reachability success rate Average E2E session delay Video max client group
Other MoP Framework maps can provide detailed MoPs at these layers
N/A
1.1 - Well defined 2.1 - Partially defined 3.3 - Not developed 4.2 - TBD
FRAMEWORK
This graphic illustrates the application of the MoP Framework methodology to the MC Display Hardware operational capability subcategory, moving hierarchically through mission threads, IERs and data types. (SOURCE: MR. Brian Hobson, ASA(ALT) SoSE&I)
Fill colors by
significance for users High
Low
FIGURE 5 19-1.0 System 19-2.0 System of Systems
19-3.0 MC Tasks
19-4.0 Operational Effectiveness MoP breakdown is needed by the following
categories – individually and in combination:
Note: Additional supporting data elements are needed to interpret MOPs fully: GPS position, full packet captures, routing tables, link states.
PERFORMANCE MOPS Performance MoPs are predominantly in the area of SoS operational issues. Each MoP has a unique number. This numbering schema allows analysts and evaluators to leverage the MoP Frame- work for MC Display Hardware and import the information to event- or system-specific data source matrices, while still maintaining the traceability and origin of these MoPs. (SOURCE: Mr. Brian Hobson, ASA(ALT) SoSE&I)
ASC.ARMY.MIL
97
SCIENCE & TECHNOLOGY
LAYERS
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172 |
Page 173 |
Page 174 |
Page 175 |
Page 176 |
Page 177 |
Page 178 |
Page 179 |
Page 180 |
Page 181 |
Page 182 |
Page 183 |
Page 184 |
Page 185 |
Page 186 |
Page 187 |
Page 188 |
Page 189 |
Page 190 |
Page 191 |
Page 192 |
Page 193 |
Page 194 |
Page 195 |
Page 196
