01.12.2014 Views

monitoring

monitoring

monitoring

SHOW MORE
SHOW LESS

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 />

As introduced earlier in this chapter, the first use of the national M&V test‐bed should be for<br />

both arms‐control and threat‐assessment <strong>monitoring</strong> of dual‐capable systems. The key is to<br />

start small in both the scope of the facilities/ranges involved and the complexity of the<br />

scenarios, and then grow in both dimensions as national <strong>monitoring</strong> capabilities grow and need<br />

to be integrated. The goal should also be to start soon––the problem space is too complex to<br />

be designed perfectly a priori.<br />

As a first step, DTRA should analyze use of wide‐area, persistent ISR/reconnaissance,<br />

surveillance, and target acquisition (RSTA) for <strong>monitoring</strong> of dual‐capable systems to support<br />

both treaty‐<strong>monitoring</strong> and threat‐assessment. Pros and cons should be developed comparing<br />

various applications of this first step, including for example, future warhead‐counting treaties,<br />

assessment of Russian dual‐capable systems in general, and assessment of China’s DC systems<br />

along the Taiwan Straits.<br />

Based on that analysis, the next step should be to plan, jointly among DoD, DOE, and the IC, a<br />

first, relatively simple experiment in detail; for example, using an ODIN‐like system to find a<br />

single dual‐capable platform operating in “move‐and‐hide” mode, at NTC and/or NNSS. (The<br />

latter would allow experimentation with real SNM signatures.) This would be a relatively low<br />

cost initial effort, but it would get started on an important problem. Even this first small step<br />

should involve red‐teaming, and should be planned by the White‐Team using the scenariogenerator<br />

described in Chapter 4. Various sensor mixes and adaptive sensor/platform CONOPs,<br />

posited by a “solutions team” also described in Chapter 4, should be explored. The product<br />

should be a well‐understood design for one component of the future nuclear <strong>monitoring</strong><br />

system of systems, along with options for operating that component.<br />

Following success with this single‐focused <strong>monitoring</strong> application, the experimentation<br />

campaign should add two, three, and more elements of the “pattern of life” for the red nuclear<br />

enterprise. The results should not only inform CONOPs development, but also identify<br />

intelligence gaps where collection assets might be focused.<br />

For all of the above, it will be important to partner with at least one geographical COCOM, and<br />

to be guided by a steering group of military and technical experts who have made such<br />

undertakings a success in the past.<br />

6.5. Recommendations: National Monitoring Testing Capability<br />

The Task Force believes that even with substantial investment in all other elements of its<br />

proposed “whats” and “hows”, the U.S. will likely see only marginal improvement in <strong>monitoring</strong><br />

capabilities without the national testing capability. While the idea of “testing capability” could<br />

suggest an expensive undertaking, the Task Force has been careful, as it has in other parts of<br />

this report, to make recommendations that build upon existing capabilities or shift investment<br />

priorities within existing portfolios. In the case of the testing capability, the communities<br />

DSB TASK FORCE REPORT Chapter 6: Experiment to Iterate and Adapt: National Testing Capability | 74<br />

Nuclear Treaty Monitoring Verification Technologies<br />

UNCLASSIFIED

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!