ARMY AL&T
Historically, the Army has made one modernization decision and then applied it across the force, often taking two decades or longer to implement it. In part, the FCS program followed this model, but incorporated systems engin- eering, initiated total system integration to ensure functionality across the BCT, and ensured that Soldiers were included in the test process. Today, the BCT Modernization Plan recognizes that decisions must be made incrementally to stay ahead of the demands of the security environment and meet war- fighters’ needs.
The Army’s new plan allows flexibility to adapt while embracing lessons learned from the FCS program, including con- tinuing the role of battle-tested Soldiers in the development of new equipment, and retaining systems engineering and integration as key components to ensure systems’ interoperability. The strategy also will incorporate Mine Resistant Ambush Protected vehicles into BCT formations, accelerate the fielding of new Capability Packages across all BCTs, and initiate a combat vehicle modernization strategy with the Ground Combat Vehicle as a key element.
Incremental Capability Packages, devel- oped and fielded on a 2-year cycle, are at the core of modernizing BCTs. The packages will support incremen- tal fielding of the best technology available from the research and devel- opment base to meet the challenges of the current fight, while reflecting the continually evolving combat environ- ment and leveraging knowledge gained during 9 years of war to develop future capabilities. Capability Packages will include doctrine, organization, and training in conjunction with materiel to fill the highest-priority shortfalls and mitigate risk for Soldiers. The incre- mental deliveries will build upon one another as the Army continually adapts and modernizes.
Emerging from systems engineering, test integration, and product develop- ment during more than a decade of FCS program management, Program Executive Office (PEO) Integration is now a key BCT Modernization organi- zation charged with ensuring integration across the PEOs and their associated portfolios that support the Capability Package materiel solutions. System- of-systems engineering, integration,
and testing will remain the responsi- bility of PEO Integration to support the Capability Package construct. As requirements are formulated, PEO Integration will fully integrate and test Capability Packages composed of vehicles, equipment, network elements, and supporting infrastructure to mod- ernize BCTs in conjunction with the ARFORGEN model.
Capabilities for Infantry First Increment 1, managed by PEO Integration’s Project Manager Infantry BCT (PM IBCT), will form the back- bone of the first Capability Package, significantly improving the IBCT Soldier’s knowledge of the battlefield and ability to communicate key situ- ational awareness data across the BCT echelon. Increment 1 consists of the Small Unmanned Ground Vehicle, Class 1 Block 0 Unmanned Air Vehicle, Tactical and Urban Unattended Ground Sensors, and the Network Integration Kit (NIK), which receives and passes sensor data from the unmanned systems to the Soldier and provides a common operating picture of the battlefield.
“All the Increment 1 systems are net- worked to support sharing of detailed tactical and visual data across the entire IBCT,” said COL John Wendel, PM IBCT, during recent Increment 1 test exercises. “They are able to leverage and improve existing current force networks.”
A Soldier equipped with a Common Controller conducts a pre-launch check of a Class 1 Unmanned Aerial Vehicle (UAV). The Common Controller consolidates control of numerous sensor nodes and unmanned sys- tems, including the Class 1 UAV and the Small Unmanned Ground Vehicle, into a single integrated networked controller. (U.S. Army photo.)
The Army is in Year 3 of a 4-year test and evaluation process for Increment 1. This increment has successfully passed Preliminary Design Review and Critical Design Review. The current technologies have been certified as mature enough to begin low rate initial production (LRIP). The Increment 1 program is executing a robust Reliability Growth Program of the systems being tested. The rigorous testing focuses on evaluating hardware and software updates to the production representative systems; evaluating secure aspects of the network and connectivity in operationally relevant environments;
OCTOBER –DECEMBER 2010 4
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
