Series Preface |
|
xi | |
Preface |
|
xiii | |
Acknowledgments |
|
xv | |
|
|
xvii | |
|
1 Introduction to Weapons Integration |
|
|
1 | (16) |
|
|
1 | (1) |
|
|
2 | (4) |
|
1.2.1 The Systems Integration Process |
|
|
2 | (1) |
|
1.2.2 Stores Management System Design |
|
|
2 | (1) |
|
1.2.3 The Global Positioning System |
|
|
3 | (1) |
|
1.2.4 Weapon Initialisation and Targeting |
|
|
3 | (1) |
|
1.2.5 The Role of Standardisation in Weapons Integration |
|
|
3 | (1) |
|
1.2.6 Interface Management |
|
|
4 | (1) |
|
1.2.7 A Weapons Integration Scenario |
|
|
4 | (1) |
|
1.2.8 `Plug and Play' Weapons Integration |
|
|
5 | (1) |
|
1.2.9 Weaponised Unmanned Air Systems |
|
|
5 | (1) |
|
1.2.10 Reducing the Cost of Weapons Integration |
|
|
6 | (1) |
|
|
6 | (8) |
|
|
6 | (1) |
|
|
6 | (1) |
|
1.3.3 Weapon Requirements |
|
|
7 | (1) |
|
|
7 | (1) |
|
|
8 | (2) |
|
|
10 | (1) |
|
1.3.7 Typical Weapon Configurations |
|
|
11 | (1) |
|
1.3.8 Implications for the Launch Aircraft |
|
|
11 | (3) |
|
|
14 | (3) |
|
1.4.1 Mechanical Attachments |
|
|
14 | (1) |
|
|
14 | (1) |
|
|
15 | (1) |
|
1.4.4 Multi-weapon Carriage Systems |
|
|
15 | (1) |
|
|
16 | (1) |
|
2 An Introduction to the Integration Process |
|
|
17 | (14) |
|
|
17 | (1) |
|
|
17 | (1) |
|
|
18 | (1) |
|
|
18 | (2) |
|
|
20 | (4) |
|
2.6 The Use of Requirements Management Tools in the Systems Engineering Process |
|
|
24 | (1) |
|
2.7 Weapons Integration Requirements Capture |
|
|
24 | (2) |
|
2.8 The Need for Unambiguous, Clear and Appropriate Requirements |
|
|
26 | (3) |
|
2.9 Minimising Requirements |
|
|
29 | (2) |
|
|
30 | (1) |
|
3 Requirements Analysis, Partitioning, Implementation in Aircraft Subsystems |
|
|
31 | (16) |
|
|
31 | (1) |
|
|
31 | (2) |
|
|
33 | (1) |
|
3.4 Requirements Decomposition |
|
|
34 | (1) |
|
3.5 Requirements Partitioning |
|
|
35 | (1) |
|
3.6 Subsystem Implementation |
|
|
36 | (1) |
|
|
37 | (1) |
|
3.8 Right-Hand Side of the V-Diagram |
|
|
38 | (1) |
|
|
38 | (3) |
|
|
41 | (1) |
|
|
42 | (1) |
|
|
42 | (1) |
|
3.13 The Safety Case and Certification |
|
|
42 | (5) |
|
|
45 | (2) |
|
4 Armament Control System and Global Positioning System Design Issues |
|
|
47 | (24) |
|
|
47 | (1) |
|
4.2 Stores Management System Design |
|
|
48 | (11) |
|
4.2.1 SMS Design Requirements |
|
|
48 | (2) |
|
4.2.2 Other System Components |
|
|
50 | (3) |
|
4.2.3 Typical System Architectures |
|
|
53 | (2) |
|
|
55 | (4) |
|
4.3 GPS: Aircraft System Design Issues |
|
|
59 | (12) |
|
|
59 | (5) |
|
4.3.2 Satellite Acquisition Concepts |
|
|
64 | (1) |
|
4.3.3 Acquisition Strategies |
|
|
65 | (1) |
|
4.3.4 GPS Signal Distribution |
|
|
65 | (2) |
|
4.3.5 Aircraft Requirements |
|
|
67 | (1) |
|
4.3.6 Aircraft Implementation Concepts |
|
|
68 | (2) |
|
|
70 | (1) |
|
|
70 | (1) |
|
5 Weapon Initialisation and Targeting |
|
|
71 | (10) |
|
|
71 | (1) |
|
|
71 | (1) |
|
5.3 Aiming of Ballistic Bombs |
|
|
72 | (1) |
|
5.4 Aircraft/Weapon Alignment |
|
|
73 | (1) |
|
5.5 Aiming of Smart Air-to-Ground Weapons |
|
|
74 | (2) |
|
|
76 | (5) |
|
|
76 | (1) |
|
|
77 | (1) |
|
5.6.3 Air-to-Air Weapons Training |
|
|
78 | (1) |
|
|
79 | (2) |
|
6 Weapon Interface Standards |
|
|
81 | (18) |
|
|
81 | (1) |
|
6.2 Benefits of Standardisation |
|
|
81 | (1) |
|
|
82 | (14) |
|
6.3.1 MIL-STD-1760 Interface Points |
|
|
83 | (1) |
|
|
83 | (2) |
|
|
85 | (1) |
|
6.3.4 GPS RF Signal Distribution |
|
|
85 | (5) |
|
|
90 | (4) |
|
|
94 | (1) |
|
|
94 | (1) |
|
|
95 | (1) |
|
|
96 | (1) |
|
6.4 Standardisation Conclusions |
|
|
96 | (3) |
|
|
97 | (2) |
|
7 Other Weapons Integration Standards |
|
|
99 | (12) |
|
|
99 | (1) |
|
7.2 AS5725 Miniature Mission Store Interface |
|
|
99 | (4) |
|
|
99 | (2) |
|
|
101 | (1) |
|
|
101 | (2) |
|
7.3 AS5726 Interface for Micro Munitions |
|
|
103 | (3) |
|
|
103 | (1) |
|
|
104 | (1) |
|
|
104 | (2) |
|
7.4 Other Weapons Integration Standards |
|
|
106 | (5) |
|
7.4.1 Generic Aircraft-Store Interface Framework |
|
|
106 | (2) |
|
7.4.2 Mission Data Exchange Format |
|
|
108 | (1) |
|
7.4.3 Common Launch Acceptability Region Approach |
|
|
109 | (1) |
|
|
110 | (1) |
|
|
111 | (14) |
|
|
111 | (1) |
|
|
111 | (1) |
|
8.3 Management of the Aircraft/Store Interface |
|
|
112 | (2) |
|
8.4 Approaches to Interface Documentation |
|
|
114 | (1) |
|
8.5 Interfaces Documented in the ICD |
|
|
115 | (4) |
|
8.6 Controlling the Interface of Store Variants |
|
|
119 | (1) |
|
8.7 Information Exchange between Design Organisations |
|
|
120 | (1) |
|
8.8 Process for Managing Integration Risk |
|
|
120 | (5) |
|
|
124 | (1) |
|
9 A Weapons Integration Scenario |
|
|
125 | (34) |
|
|
125 | (1) |
|
|
125 | (1) |
|
9.3 The Weapons Integration Scenario |
|
|
126 | (3) |
|
9.4 The V-Diagram Revisited |
|
|
129 | (1) |
|
9.5 Systems Integration Activities |
|
|
130 | (2) |
|
|
132 | (8) |
|
9.6.1 Aircraft/System Hazards |
|
|
136 | (3) |
|
|
139 | (1) |
|
9.7 Systems Requirements Decomposition, Design and Implementation |
|
|
140 | (3) |
|
9.7.1 Weapon System Integration Requirement |
|
|
140 | (1) |
|
9.7.2 Functional Definition and Development/Interface Definition |
|
|
140 | (1) |
|
|
141 | (2) |
|
9.7.4 Data Flows between Aircraft Subsystems |
|
|
143 | (1) |
|
9.8 Loading to Dispersion Sequence |
|
|
143 | (16) |
|
|
145 | (1) |
|
9.8.2 System Power-Up/Store Discovery |
|
|
145 | (1) |
|
|
146 | (1) |
|
9.8.4 Weapon BIT/System Power-Down |
|
|
147 | (1) |
|
9.8.5 Download Target Data/Power-Down Weapons |
|
|
148 | (1) |
|
9.8.6 Taxi/Take-Off/On-Route Phase |
|
|
149 | (1) |
|
9.8.7 Weapon Selection and Priming |
|
|
149 | (1) |
|
|
150 | (1) |
|
9.8.9 Steer to Target LAR/Confirm in LAR |
|
|
151 | (1) |
|
9.8.10 Initiate Release Sequence |
|
|
151 | (2) |
|
9.8.11 Weapon Release Phase |
|
|
153 | (1) |
|
9.8.12 Selective/Emergency Jettison |
|
|
154 | (1) |
|
9.8.13 Carriage Store Control |
|
|
155 | (1) |
|
9.8.14 Training Capability |
|
|
156 | (1) |
|
9.8.15 Implications of Aeromechanical Aspects - Weapon Physical Alignment |
|
|
156 | (2) |
|
|
158 | (1) |
|
10 A Weapons Integration Scenario: System Proving and Certification |
|
|
159 | (10) |
|
|
159 | (1) |
|
|
159 | (1) |
|
10.3 Simulators and Emulators |
|
|
160 | (1) |
|
|
160 | (1) |
|
|
160 | (1) |
|
|
161 | (1) |
|
|
162 | (1) |
|
10.8 Electromagnetic Compatibility |
|
|
162 | (1) |
|
10.9 Airworthiness and Certification |
|
|
163 | (1) |
|
10.10 Declaration of Design and Performance/Statement of Design |
|
|
164 | (1) |
|
10.11 Certificate of Design |
|
|
164 | (1) |
|
|
165 | (1) |
|
10.13 Airworthiness Flight Limitations |
|
|
165 | (1) |
|
|
165 | (1) |
|
|
165 | (1) |
|
10.16 Weapon System Evaluation |
|
|
166 | (1) |
|
|
167 | (2) |
|
|
167 | (2) |
|
11 Introduction to `Plug and Play' Weapons Integration |
|
|
169 | (20) |
|
|
169 | (1) |
|
11.2 Systems Integration Considerations |
|
|
169 | (2) |
|
11.3 The Journey to `Plug and Play' Weapons Integration |
|
|
171 | (1) |
|
11.4 `Plug and Play' Technologies |
|
|
172 | (1) |
|
11.5 Adoption of `Plug and Play' Technology |
|
|
172 | (1) |
|
11.6 Introduction to Aircraft, Launcher and Weapons Interoperability |
|
|
173 | (1) |
|
|
174 | (2) |
|
|
176 | (3) |
|
11.9 ALWI Common Interface Study |
|
|
179 | (7) |
|
11.9.1 Technical Architecture |
|
|
180 | (1) |
|
11.9.2 Greater Interoperability through a Common ICD Approach |
|
|
181 | (1) |
|
11.9.3 Common Store Control Service |
|
|
181 | (2) |
|
11.9.4 Model-Driven Architecture Approach |
|
|
183 | (2) |
|
11.9.5 Implementation Considerations |
|
|
185 | (1) |
|
|
186 | (3) |
|
|
187 | (2) |
|
|
189 | (14) |
|
|
189 | (1) |
|
|
189 | (1) |
|
12.3 The Contracting and Industry Environment |
|
|
190 | (1) |
|
|
191 | (1) |
|
12.5 A Typical Mission Systems Upgrade Programme |
|
|
192 | (1) |
|
|
193 | (2) |
|
12.7 ASAAC and `Plug and Play' |
|
|
195 | (3) |
|
12.8 Certification Issues |
|
|
198 | (2) |
|
12.9 Easing the Upgrade Programme |
|
|
200 | (3) |
|
|
201 | (2) |
|
13 The Universal Armament Interface |
|
|
203 | (16) |
|
|
203 | (1) |
|
|
203 | (1) |
|
|
204 | (3) |
|
13.4 Fundamental Principles of UAI |
|
|
207 | (2) |
|
13.5 Platform/Store Interface |
|
|
209 | (1) |
|
|
210 | (1) |
|
13.7 Launch Acceptability Region |
|
|
211 | (1) |
|
13.8 Integration Work Flow |
|
|
211 | (2) |
|
13.9 UAI Interface Management |
|
|
213 | (1) |
|
13.10 Certification Tools |
|
|
214 | (1) |
|
|
215 | (1) |
|
|
216 | (1) |
|
13.13 `Plug and Play' Conclusions |
|
|
216 | (3) |
|
|
217 | (2) |
|
14 Weaponised Unmanned Air Systems |
|
|
219 | (8) |
|
|
219 | (1) |
|
|
219 | (1) |
|
14.3 Distributed Weapon System |
|
|
220 | (2) |
|
14.4 System Architecture Partitioning |
|
|
222 | (4) |
|
|
226 | (1) |
|
|
226 | (1) |
|
15 Reducing the Cost of Weapons Integration |
|
|
227 | (12) |
|
|
227 | (1) |
|
|
227 | (2) |
|
|
229 | (2) |
|
15.4 Reducing the Cost of Weapons Integration - Other Initiatives |
|
|
231 | (3) |
|
15.4.1 Streamlined Integration Processes |
|
|
232 | (1) |
|
15.4.2 Common Goals for the ADO and WDO |
|
|
232 | (1) |
|
15.4.3 Employment of New Technology Which Eases Integration |
|
|
233 | (1) |
|
15.4.4 The Need for Exports |
|
|
233 | (1) |
|
15.4.5 Spiral Introduction of Capability |
|
|
234 | (1) |
|
15.4.6 Organisational Re-structuring |
|
|
234 | (1) |
|
15.4.7 Adoption of International Standards |
|
|
234 | (1) |
|
|
234 | (2) |
|
|
236 | (3) |
|
|
237 | (2) |
Index |
|
239 | |