06.01.2013 Views

Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

Unmanned Aircraft Systems Roadmap 2005-2030 - Federation of ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

UAS ROADMAP <strong>2005</strong><br />

layers (IPv6), deployment <strong>of</strong> the TCA and transformation <strong>of</strong> circuit based DISN communications links to<br />

IP based services.<br />

Although smaller, the second group provides radio telecommunications guidance that enables wireless<br />

connectivity to the GIG and is binding on all UA communications systems and waveforms. While current<br />

UA systems support the warfighter through the common data link effort, implementation <strong>of</strong> common and<br />

more flexible physical links with the JTRS program will be the next step. Guidance that implements the<br />

GIG consist <strong>of</strong>:<br />

� DoD Directive 8100.1, GIG Overarching Policy, dated September 19, 2002.<br />

� DoD Chief Information Officer (CIO) Guidance and Policy Memorandum (G&PM) No. 11-8450,<br />

DoD GIG Computing, dated April 6 2001.<br />

� DoD CIO Memorandum, Subject: Net-Centric Data Strategy: Visibility-Tagging and Advertising<br />

Data Assets with Discovery Metadata, dated October 24, 2003.<br />

� DoD Memorandum, Subject: Internet Protocol Version 6 (IPv6), dated June 9, 2004.<br />

� Chairman <strong>of</strong> the Joint Chiefs <strong>of</strong> Staff Instruction 6212.01C, Interoperability and Supportability <strong>of</strong><br />

Information Technology and National Security <strong>Systems</strong>, dated November 20, 2003.<br />

Guidance that implements radio communications:<br />

� OSD Memorandum, Subject: RF Equipment Acquisition Policy, dated June 17, 2003.<br />

� OSD Memorandum for Secretaries <strong>of</strong> the Military Departments, Subject: JTRS, dated August 12,<br />

2004.<br />

� ASD Memorandum, Subject: CDL Policy, dated June 19, 2001.<br />

� ASD Memorandum, Subject: C3I Tactical Data Link Policy, dated October 18, 1994.<br />

Standards<br />

Standards support policy by providing technical information in sufficient detail to guide system and<br />

subsystem acquisition and development. These standards are mandatory for DoD weapon systems,<br />

including UAS, and are only waived in exceptional circumstances. Table C-2 lists the key standards and<br />

sources for standards.<br />

The “source” column contains hyperlinks to the websites hosting the information. For detailed<br />

information regarding a standard or source <strong>of</strong> standards, follow the respective link. Some websites will<br />

require a user ID and password for access. Appendix E discusses standards that apply to various system<br />

implementations.<br />

ENABLING PROGRAMS<br />

Along with written guidance above, the DoD has invested in common products with the expectation that<br />

they be used to a maximum extent possible. This is to correct the weakness from past experience where<br />

each developing UA would invest in its own unique communication mechanism or design a system<br />

architecture that drove unique communication solutions. While the capabilities and schedules <strong>of</strong> these<br />

common-use programs may change, the following represents the best knowledge as <strong>of</strong> the time <strong>of</strong> this<br />

writing. UA programs should seek to synchronize their systems with the milestones <strong>of</strong> the applicable<br />

programs: CDL, JTRS, TSAT, FAB-T and HAIPE.<br />

In the area <strong>of</strong> net-centricity, GIG capabilities will not come on line simultaneously but will ramp up in a<br />

series <strong>of</strong> spirals. Once fielded, these capabilities will continue their evolution. Figure C-9 illustrates the<br />

spiral approach to achieving the net-centric force. Spiral 1, 2006, connects UA to the net and bridges<br />

gaps between legacy systems resulting from nonstandard data structures and transport mechanisms.<br />

Transition to IP based transport and metadata registration constitutes foundation elements to this strategy.<br />

Spiral 1 also introduces JTRS in a move toward a more flexible, interoperable system <strong>of</strong> s<strong>of</strong>tware defined<br />

tactical radios and dynamic wireless networks. Spiral 2, 2008, leverages advances in net-centric<br />

APPENDIX C - COMMUNICATIONS<br />

Page C-18

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

Saved successfully!

Ooh no, something went wrong!