Unmanned Systems Integrated Roadmap FY2011-2036 - Defense ...

More documents

Recommendations

Info

4.3 Today’s State Unmanned Systems Integrated Roadmap FY2011-2036 The historical approach to software and hardware acquisition relied on dedicated design for each system to accomplish a specific mission or capability. This approach may be optimal for a single system, but it unfortunately produces a collection of discrete, disjointed solutions with significant functional overlap and no method to exploit common components of each system. Open architecture (OA) facilitates interoperability between systems by effectively leveraging the following concepts: • Common capability descriptions in system requirements • Common, open data models, standards, interfaces, and architectures in system design • Common components in system acquisition strategies OSD defines OA as a multifaceted strategy providing a framework for developing joint interoperable systems that adapt and exploit open-system design principles and architectures. This framework includes a set of principles, processes, and best practices that: • Provide more opportunities for competition and innovation • Rapidly field affordable, interoperable systems • Minimize total ownership cost • Optimize total system performance • Yield systems that are easily developed and upgradeable • Achieve component software reuse 10 These (predominantly) acquisition issues are aided by a solid framework for software, component, and systems interoperability. Traditionally, efforts have focused on system functionality descriptions, with interoperability focused at the messaging layer (e.g., the Joint Architecture for Unmanned Systems (JAUS) and STANAG 4586) to achieve standards-based interoperability. However, the tenets of common definitions and understanding listed on the left are required to achieve a true plug-and-play level of interoperability in which software capabilities from multiple vendors can be developed and integrated into a single system, supporting the exchange, interpretation, and action on data from other systems. Through implementation and program-level 10 Terms and Definitions, Defense Acquisition University, https://acc.dau.mil/CommunityBrowser.aspx?id=22108. 32
Unmanned Systems Integrated Roadmap FY2011-2036 adoption of these three tenets, DoD intends to address the issue of single proprietary vendor dependency within the acquisition system and improve conditions allowing for full competition. 4.4 Problem Statement Over the last decade, the DoD has achieved great successes from the use of unmanned systems for both peacetime and wartime operations. These successes led to a significant increase in the number of unmanned systems planned and procured, and the future looks to see an exponential increase in the quantity and diversity of unmanned systems applications. Traditionally, each unmanned system was procured as a vertically integrated, vendorproprietary solution, consisting of the vehicle system, control station, communications channels, and encryption technologies. These single-system variants were typically “closed” systems utilizing proprietary interfaces. Development of the entire system was conducted in parallel with close interdependencies between components and procured as a whole through the platform prime contractor. As the number of new unmanned systems programmed in the Service budgets increased, the magnitude of RDT&E requirements for development skyrocketed. In addition to cost, this approach resulted in a number of unfavorable acquisition and growth characteristics that impeded progress as depicted above. Further, silence about the lack of interoperability and standards failed to foster dialog on how to overcome them. Over time, this resulted in an inhibition to innovation; increased vulnerability to threats where attacks on common attributes can impact multiple systems; increased complexity to systems engineering, development, and test; increased upfront costs; increased costs to system upgrades that cannot be made without changes to the interoperable dependencies of multiple systems; and budgeting protocols that treat interservice and coalition interoperability as fiscal trade-space. These issues have significantly hampered unmanned systems acquisition activities. However, urgent wartime needs dictated that such concerns be relegated to the background, in the interest of rapid initial deployment. As the unmanned systems industry matures, however, the acquisition process must evolve in parallel. Addressing and enabling interoperability within unmanned systems will help accomplish this goal. 4.5 The Way Ahead The technical approach to achieve the interoperability vision leverages the tight connection between interoperability and OAs, and consists of several elements. Each of the following elements is required, and none is sufficient in its own right to implement an OA: 33
Page 1 and 2: 3 Unmanned Systems Integrated Roadm
Page 4 and 5: Unmanned Systems Integrated Roadmap
Page 38 and 39: 3.6.3 Airspace Integration (AI) Unm
Page 40 and 41: 4 INTEROPERABILITY 4.1 Overview Unm
Page 52 and 53: 4.6 Summary Unmanned Systems Integr
Page 68 and 69: 6.4.4 CONOPS Development Unmanned S
Page 70 and 71: 7 COMMUNICATIONS 7.1 Functional Des
Page 82 and 83: 8 TRAINING 8.1 Functional Descripti
Page 84 and 85: 8.3 Problem Statement Unmanned Syst
Page 86 and 87: 9 PROPULSION AND POWER 9.1 Function
Page 90 and 91: 9.4.2 Power Unmanned Systems Integr
Page 92 and 93:
Unmanned Systems Integrated Roadmap
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
11 SUMMARY Unmanned Systems Integra
Page 100 and 101:
APPENDIX A: REFERENCES Unmanned Sys
Page 102 and 103:
Page 104 and 105:
APPENDIX C: GLOSSARY Unmanned Syste
Page 106 and 107:
Page 108:
show all

Unmanned Systems Integrated Roadmap FY2011-2036 - Defense ...

Create successful ePaper yourself

Delete template?

Save as template?