MANY EYES, SAME PICTURES
and egress. And, as the vehicle shifts away from analog sensors, the media con- verters can be removed and new digital sensors can tap directly into the server switch. Finally, this approach conforms to the Army’s move toward network con- nectedness with the introduction of the VICTORY standard for communicating between systems within a vehicle and the Integrated Sensor Architecture (ISA) for sharing information between sensors and systems in a tactical environment.
Over the course of the MVD system
development, NVESD worked closely with multiple hardware vendors to tran- sition each of the system architectural components from laboratory-grade prototypes to full military standard, conduction-cooled, production prod- ucts capable of operating in the extreme environments of the MMPV Type II at minimal cost.
DELIVERING THE SYSTEM Te evolution of the system server switch set
the stage for the entire MVD pro-
curement strategy. After completing the initial system demonstrations, it was time for the ruggedized solution. While researching similar hardware acquisitions on other government projects, NVESD found that the ruggedized servers used by the Project Manager for the Warfighter Information Network – Tactical (PM WIN-T) met the needs of MVD almost perfectly. PM WIN-T, assigned to the PEO for Command, Control and Com- munications – Tactical (PEO C3T), was purchasing its servers using the Com- mon Hardware Systems 4 contract of PEO C3T’s PM for Mission Command, a contract open to all DOD customers to procure tactical hardware and services. PdM AMS is testing this procurement mechanism, which would greatly reduce the time necessary to purchase hardware, for use with MVD.
A PATH FOR GROWTH Te MVD software is hardware-inde- pendent and operates on any of the three architectures with minor modifications. MVD design is novel in that it uses a modular
plug-in-based architecture,
which means that new enabler systems can be added without modifying or recompiling any of the existing code. Tis is a tremendous cost savings as the hybrid threat is continuously adapting to defeat- strategies, requiring new vehicle-enablers. MVD software comprises many thou- sands of lines of code that government personnel at NVESD authored quickly to meet the aggressive development sched- ule. Te code has been through multiple rounds of static analysis as well as code coverage testing to ensure that every line operates as intended without errors. In addition, a mobile platform version of the system for Android devices will allow an operator to continue using enablers while dismounted from the vehicle.
PUTTING IT TOGETHER
The system architecture used in the MVD system provides robust, distributed processing for redundancy, speed and room for future growth without the need for costly reconfigurations.
Te system uses industry standards for interfaces and data formats, including both VICTORY and ISA, enabling it to communicate with current and future systems internal and external to the vehicle platform. Along with image dis- play, the MVD system can also act as a digital video recorder, allowing for the capture and playback of video sequences and snapshots. Te MVD system cur- rently allows for the full control of several of the MMPV Type II enablers and dis- play of nine separate camera feeds. Te system has demonstrated robustness in testing with 14 full-motion video feeds captured simultaneously and displayed in real time—nearly five times more enabler feeds than any single configuration of a typical MMPV Type II platform. Tis is the key demonstration that provided the assurance PdM AMS needed to select the MVD system as the display solution for its MMPV Type II POR.
118
Army AL&T Magazine
July-September 2015
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156
