monitoring
monitoring
monitoring
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
UNCLASSIFIED<br />
DEFENSE SCIENCE BOARD | DEPARTMENT OF DEFENSE<br />
6.2.1. Why is a National Testing Capability for Monitoring and Verification Needed?<br />
There are many inter‐related reasons. The comprehensive <strong>monitoring</strong> regime the Task Force<br />
proposes is a system of systems that must work together, and is too complicated to plan/assess<br />
on paper and/or with piecemeal testing. Furthermore, experience shows that operators<br />
typically learn to use actual <strong>monitoring</strong> systems differently and often better than system<br />
design/analysis would predict. Two examples illustrate the point:<br />
• Past experience in radiation detection operations; e.g., Operation Morning Light (the<br />
1978 deployment to search for and recover debris from a reactor‐powered Soviet<br />
RORSAT that re‐entered in northern Canada); and Navy experience in detection of<br />
shipboard nuclear weapons. In both cases, operators learned to reject clutter and<br />
spurious signals by identifying patterns inherent in their own operations and/or in the<br />
larger context. For example, in Morning Light, radiation signatures from the low‐grade<br />
uranium‐ore deposits that are ubiquitous in Northern Canada confounded the search<br />
operations in the first days. But operators identified the source of the spurious signals,<br />
and learned that the radiation signatures from these deposits rose and declined more<br />
slowly, as the search platforms flew across the terrain, than the radiation signatures of<br />
the point‐targets they were looking for, and could be sorted out on that basis;<br />
• Recent experience in the development of new‐generation tactical ISR in the Counter IED<br />
fight discussed elsewhere in this report; learning from operational experience in<br />
Iraq/Afghanistan (“on the job training”), has been coupled with iteration in experiments<br />
in various DoD testing and training facilities (e.g., the National Training Center [NTC]) to<br />
not only train deploying units but also to anticipate next steps in adversary tactics,<br />
techniques and procedures (TTPs).<br />
The need to learn from experimentation and experience is even greater in the areas addressed<br />
by this Task Force, where an adaptive adversary and/or one with sophisticated denial and<br />
deception is likely to be involved.<br />
The advantages of a testing capability are many and compelling. It would or could:<br />
• Provide a focal point for planning, iterating/adapting, and operating the system of<br />
systems;<br />
• Help integrate the technically disparate and organizationally disaggregated activities<br />
that comprise the national <strong>monitoring</strong> system;<br />
• Better couple developers and users and provide an experimental basis for net<br />
assessment and risk management;<br />
• Provide ground‐truth performance metrics for technologies and operations, in part as a<br />
basis for future spirals;<br />
• Stimulate sorely needed new ideas;<br />
• Expose “subcritical” programs because planning experiments would force development<br />
of concrete requirements and CONOPs;<br />
DSB TASK FORCE REPORT Chapter 6: Experiment to Iterate and Adapt: National Testing Capability | 66<br />
Nuclear Treaty Monitoring Verification Technologies<br />
UNCLASSIFIED