CONSIDERING EXPORTS
A recent JTNC white paper, “Electronic Protection (EP) of Tactical Radio Sys- tems,” highlights specific electronic protection areas the acquisition com- munity can address strategically. JTNC security analysis of waveforms includes examination of requirements for, and verification of, effective electronic pro- tection against interception, GPS denial or deception, and jamming against elec- tronic warfare capabilities of probable adversaries. Analyses to date consistently indicate
that improvements are neces-
sary in intelligence collection targeting, design and testing requirements, test exe- cution, and tactics to enhance electronic protection of radio communications when subjected to our likely adversaries’ electronic warfare capabilities.
In the white paper, JTNC recommends quantifying performance thresholds for electronic protection. Tese quanti- fied electronic protection requirements should be aimed at the threats the intelli- gence community identifies as most likely to be encountered. Tese include threats to waveform detection and identifica- tion, which allow the adversary to disrupt communication capabilities.
Associated with the development of
waveform electronic protection require- ments is the development of electronic protection test procedures and represen- tative threat electronic warfare systems to quantify waveforms.
EXPORT CONSIDERATIONS Integrating exportability considerations at
the waveform source code level is
more important than ever, given the cur- rent nondevelopmental item approach to acquisitions and the continued improve- ment of existing (and development of new) waveforms for SDR platforms. Developers obtaining waveforms from the DOD Waveform Information Repository
The JTNC Export Office provides the following practical recommendations in the two areas of requirements and docu- mentation, and training and awareness.
REQUIREMENTS AND DOCUMENTATION • DOD offices identified as waveform “sponsors” should develop waveform- specific
program protection plans
that identify any critical program information, critical technologies and known and potential vulnerabilities. Identifying critical information and vulnerabilities ahead of time will make it easier
to determine which
waveforms and pieces of source code can be exported without risk to U.S. capabilities.
• Identify exportability requirements in the formal requirements process so program management offices have the resources to determine exportabil- ity throughout product development. As mentioned in BBP 2.0, program managers (PMs) should increase the incorporation of defense exportabil- ity features in initial design. The Joint Capabilities Integration and Devel- opment System manual states that exportability should be identified in the capability development document prior to the milestone B decision, and the capability production document prior to the milestone C decision. (See Figure 2, Page 96.)
• Modify DOD issuances, including chang- ing DOD Instruction 5000.02 from “will consider” to “shall address” export.
• Review pertinent program documents to ensure that exportability is bet- ter
business case, including the acquisi- tion
baseline,
strategy, acquisition technology
assessment development
strategy, security classification guide, technology
and con-
trol plan, and data distribution list. Together these documents help enable sound and timely decisions
on export during a system’s design, development and implementation.
TRAINING AND AWARENESS • Update the Defense Acquisition Guidebook based on changes to the formal
processes
requirements and acquisition to
support including exportability
plans for PMs and acquisition pro- fessionals,
the Exportability Features Pilot Program.
• The guidebook should provide exam- ple language for typical acquisition activities, such as requests for infor- mation and requests for proposals, to help PMs and industry consider future exports in the responses and bids to DOD. This is another way to encour- age strategic acquisition planning.
• Emphasize exportability training throughout the Defense Acquisition University’s curriculum, in line with BBP 3.0.
• PMs should become familiar with the Defense Exportability Features Pilot Program, which encourages DOD acquisition programs that are nomi- nated by their component acquisition executives and selected by the Inter- national of
Cooperation Directorate the undersecretary of defense for
acquisition, technology and logistics, to assess, design and incorporate defense exportability features in their systems to facilitate foreign sales.
integrated into the overall DOD program
These practical recommendations, along with other changes across the require- ments and acquisition processes, could better institutionalize DOD planning for export. This improved planning will help support the DOD industrial base in reducing unit costs and protecting DOD systems, and will provide solutions that interoperate with our foreign partners from the early requirements and into the design phase.
—LT. COL. MATTHEW A. “MATT” JURY Defense
ASC.ARMY.MIL
95
SCIENCE & TECHNOLOGY
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
