Transcription of Joint Battle Command – Platform (JBC-P) - DOT&E
{{id}} {{{paragraph}}}
FY14 ARMY PROGRAMS. Joint Battle Command Platform (JBC-P). Executive Summary DOT&E released a November 2013 IOT&E report that assessed Joint Battle Command Platform (JBC-P) software build as operationally effective, not operationally suitable, and not survivable. This report was based upon the May 2013. JBC-P software build IOT&E. In November 2013, the Army approved a fielding decision for JBC-P software build based upon the May 2013 JBC-P. IOT&E and demonstrated corrections to discovered deficiencies. In May 2014, the Army and Marine Corps conducted a JBC-P software build Multi-Service Operational Test and Evaluation (MOT&E) to support fielding decisions in both Services. While software build delivered several enhanced capabilities, it introduced deficiencies which significantly detracted from mission capabilities and led to a change in the assessment.
FY14 armY Programs Joint Battle Command – Platform (JBC-P) JBC-P 113 - Hybrid capability to connect JBC-P across different networks through the use of its Network Services Gateway
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}
Joint Battle Command Platform, PM Mission Command, Command, Joint Battle Command – Platform, Blue Force Tracking, Battle Command, Joint Battle Command-Platform, SUBCOMMITTEE ON TACTICAL AIR AND, Joint Battle Command–Platform, Joint Battle Command - Platform, United States Court of Federal Claims, Surface Transportation Distribution of Materiel, Joint, PROGRAM EXECUTIVE OFFICE MISSILES AND SPACE