so that such updates can occur more quickly. (2) Requirements In improving the process under paragraph (1), the Secretary shall ensure the following: (A) That under such process, updates to the mission data files are developed, operationally tested, and loaded onto systems of advanced combat aircraft while in theaters of operation in a time-sensitive manner to allow for the distinguishing of threats, including distinguishing friends from foes, loading and delivery of weapon suites, and coordination with allied and coalition armed forces. (B) When updates are made to the mission data files, all areas of responsibility (AoRs) are included. (C) The process includes best practices relating to such mission data files that have been identified by industry and allies of the United States. (D) The process improves the exchange of information between weapons systems of the United States and weapon systems of allies and partners of the United States, with respect to such mission data files. (b) Consultation and pilot programs In carrying out subsection (a), the Secretary shall consult the innovation organizations resident in the Department of Defense and may consider carrying out a pilot program under another provision of this Act. (c) Report Not later than March 31, 2018, the Secretary shall submit to the congressional defense committees a report on the actions taken by the Secretary under subsection (a)(1) and how the process described in such subsection has been improved. C Reports and other matters 231. Competitive acquisition plan for low probability of detection data link networks (a) Plan required The Under Secretary of Defense for Acquisition, Technology, and Logistics and the Vice Chairman of the Joint Chiefs of Staff shall jointly, in consultation with the Secretary of the Navy and the Secretary of the Air Force, develop a plan to procure a secure, low probability of detection data link network capability with the ability to effectively operate in hostile jamming environments while preserving the low observable