F-35 Joint Strike Fighter (JSF)

More documents

Recommendations

Info

Activity Ml DS-LVT (B-1 B Integration) • Detachment 5, Air Force Operational Test and Evaluation Center (AFOTEC) conducted an Operational Assessment of the integration of the MIDS-LVT into the B-I B Bomber aircraft at Edwards AFB, California, from February to June 2010- The Common Link Information Processor (CLIP) facilitated the integration of MIDS-LVT into the B-1B aircraft- The Operational Assessment included three operational test flight sorties by the B-I B aircraft. MIDS-JTRS • The Naval Air Warfare Center completed the ground and flight Developmental Test and Evaluation of the MIDS-JTRS as integratcd on the FIA-18E/F operating from the Naval Air Station (NAS) Patuxent River, Maryland. and NAS China Lake, California. • The Naval Air Warfare Center, with participation by the Air Test and Evaluation Squadron Nine, conducted integrated aircraft carrier suitability flight testing of the F/A- 1 8E/F with the integrated MIDS-JTRS core terminal. • cuff, started the F/A-18E/F MIDS-JTRS IOT&E in July 2010 at NAS China Lake, California, and participated in a large joint force training exercise conducted at Nellis AFB- Nevada to collect Link 16 interoperability test data. • All testing was conducted in accordance with a DOT&E-approved Test and Evaluation Master Plan (TEMP) and operational test plans. Assessment M (B-1B Integration) • Results from the B-1B MIDS-LVT and CLJP integration Operational Assessment indicate that the transfer of MIDS-LVT Link 16 data via CLIP to the B-1 B host computer was problematic- Specifically, inaccurate information transferred for some of the Link 16 message types, and CLIP could not completely and accurately process information from near simultaneous beyond-line-of-sight and line-of-sight transmissions of Link 16 messages. CLIP software was riot yet mature, as indicated by the quantity of unresolved software discrepancies and a constant (not yet decreasing) rate of discovery of software discrepancies- MIDS-JTRS • The aircraft carrier suitability integrated test results indicate compatible operation of the F/A-18E/F M IDS-JTRS during approach, take-off, and landing on the aircraft carrier. 34 MIDS • The MIDS-JTRS lOT&E data collection and analysis effort is ongoing. There are emerging concerns related to MI DS-JTRS TACAN air-to-air range errors- There are emerging concerns regarding the ability to achieve the reliability requirement of 220 hours for the MIDS-JTRS terminal, as evidenced by ten MIDS-JTRS terminal (hardware) failures during IOT&E, • Data show the BIT Use alarm rate associated with the integration of the MIDS-JTRS into the F/A-18E/F is excessive, potentially affecting maintainability ratings for the system. • The operational test squadron, Air Test and Evaluation Squadron Nine, based at NAS China Lake. California, identified aircraft integration discrepancies during the Ni MIDS-JTRS installation and pre-operational flight checks conducted prior to the start of the IOT&E. Aircraft maintenance personnel resolved the issues by conducting significant levels of minor maintenance to correct aircraft electronic systems discrepancies or developing workarounds to permit IOT&E to begin as scheduled. Recommendations • The Air Force and Navy made satisfactory progress on the previous MiDS-LVE recommendations primarily related to the fielded • FY I0 Recommendations- I. The Air Force B-1 B and CLIP program offices should review the findings from the CLIP (B-I B/MIDS-LVT) integration Developmental Test and Operational Assessment and correct all major deficiencies prior to entry into the B-1 B CLIP integration OT&E, 2. The MIDS-JTRS and FA-IS program offices should continue to characterize the TACAN discrepancies and develop a solution for test prior to fielding. 3. The Navy should modify the MIDS-JTRS F 1A-18 installation checklist for fielding to ensure appropriate maintenance personnel adequately prepare all antenna and 4- cabling connections for installation of the terminal. The MIDS program office should focus industry efforts on achieving improved terminal manu facturing processes in order to elevate the overall reliability of the MIDS-JTRS system, 5, The Navy. [AIDS program office and industry should develop a solution to the excessive BIT false alarm rate for the MIDS-JTRS system as integrated into the F/A-I8 FIR
Network Centric Enterprise Services (NCES) Executive Summary • The Operational Test Team conducted a series of FOT&E II events on a subset of Increment 1 Net-Centric Enterprise Services (NCES) from November 2009 through July 2010. The FOT&E 11 was conducted in accordance with the DOT&E-approved test plan. However, testing of some services (Enterprise Service Management (ESM) and Machine-to-Machine Messaging) relied heavily on pilot programs and demonstrations providing less confidence in the results- • The Milestone Decision Authority authorized full deployment for Service Discovery on February 12, 2010, and made a fielding decision for Enterprise File Delivery, Enterprise Search, ESM. Machine-to-Machine Messaging, and People Discovery on September 20. 2010. • Penetration testing during the FOT&E, revealed Information Assurance (IA) shortfalls at the Defense Enterprise Computing Centers (DECCs) housing NCES capabilities. The Defense Information Systems Agency (DISA) addressed these shortfalls and conducted a Verification of Corrections assessment from May to June 2010. Further incident response recommendations for the DECCs are being incorporated in plans, processes, and procedures to be released in late FY I0. • Machine-to-Machine Messaging is rated as operationally effective and operationally suitable with limitalions. With the suspension of key pilot programs and demonstrations, no new programs have committed to use Machine-to-Machine Messaging. Users report a preference for another DISA service, the <strong>Joint</strong> User Messaging Service. • DOME is unable to determine the operational effectiveness of Service Discovery and ESM based on FOT&Es I and II. Service Discovery requires additional testing incorporating an expanded data base of registered services and a larger user base- The DoD Chief Information Officer (CIO) memorandum "Net-Centric Enterprise Services (NCES) Service Discovery Governance" (August 3, 2010) outlines a plan of action to improve the governance process and encourage the use of Service Discovery. ESM testing also had a limited set of users who only used a portion ofdie capabilities provided. More guidance from DoD CIO and Under Secretary of Defense for Acquisition, Technology, and Logistics (USD (AT&L)) to the DoD Services, Agencies, and Commands is needed to help software service integrators select and configure appropriate ESM capabilities, System • NCES is a suite of individual capabilities that support automated information exchange across the DoD on both classified and unclassified networks- These capabilities include collaboration, discovery, and mediation and user Service Mediation &lune OW unintinIP•tid were Aiamau Oecete spe:elffe Infafrestism for people Metadata ViscPve!Y .44e.a.n Aeries, to netweer. develop to rest d semantics CantEnt. , • DiScOrry. .. ••••• • ••fr'.', Aarne impravid Cement • awareness access through the Defense Knowledge Online pertal- Each service is unique and has its own IOT &E and acquisition fielding decision. • NCES collaboration tools enable users to hold meetings and exchange information by text, audio, and video- • The discovery capabilities (content, people, services, metadata, publish/subscribe) allow data producers to post information, alert others to the presence of new information, and evaluate the relevance Of the data to their current roles and activities. • NCES includes security and management capabilities that integrate with and rely upon: capabilities providing data on performance, operational status, and usage of web services that enhance network situational awareness t6 the Global Jnfrastructure Services Management Center - 1A/computer network defense • The software for all the NCES services is comprised of commercial off-the-shell- and government off-the-shelf products- The concept is to provide commercially available products managed under a contract that specifies maintenance, support, and performance levels :for each Service, commonly known as Service-Level Agreements (SLAB). • The warfighting, intelligence, and business communities (i.e-, finance, medical, and logistics) will access NCES capabilities either directly or through a portal that controls access by the use of Public Key Infrastructure profiles. • NCES services are available to all operational and tactical users who connect to a Defense Information System Network point-of-presence- • NCES is a collection of services from which users can select those that best fit their needs. Users can be syStem or software developers, system or network administrators, communities of interest, programs of record, or personnel executing warfighting, business, and intelligence missions. NCES <strong>35</strong>
Page 1 and 2: F-35 Joint Strike Fighter (JSF) Exe
Page 3 and 4: • The government-contractor test
Page 5 and 6: Air System-Ship Integration and Shi
Page 7 and 8: Global Combat Support System — o
Page 9 and 10: Joint Chemical Agent De ector Execu
Page 11 and 12: Joint Tactical Radio System (JTRS)
Page 13 and 14: Joint Tactical Radio System (JTRS)
Page 15: Joint Warning and Reporting Network
Page 18 and 19: BAE RG-33L CAT Ii and Ambulance var
Page 20 and 21: Assessment • The M-ATV is operati
Page 24 and 25: Mission Joint Force Commandersill w
Page 27 and 28: Public Key Infrastructure (PKI) Inc
Page 29 and 30: Suite of Integrated Radio Frequency
Page 31 and 32: Executive Summary • A November 20

F-35 Joint Strike Fighter (JSF)

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

Delete template?

Save as template?