T
lhe second quarterly Army Watercraft Systems (AWS) Board of Directors (BOD) meeting was held Jan. 18 in
Warren, MI, to chart the course of AWS, a capability like no other in the Army.
“The forum served and will continue to provide us with a path forward for key leaders to help shape common objec- tives for the Army watercraft fleet. It will enable us to share real-time informa- tion on critical issues and challenges, as well as to make key decisions to ensure timely and efficient life-cycle manage- ment of the AWS fleet,” said Kevin Fahey, Program Executive Officer Combat Support and Combat Service Support (PEO CS&CSS).
The AWS BOD consists of seven core members and nine supporting mem- ber
organizations, representing Army
leadership, integrators, program manag- ers, and developers. In December 2010, DoD Directive 5100.1, Functions of the
Department of Defense and Its Major Components, revalidated the specific mis- sion and functions of Army watercraft systems. Building on that
foundation,
an Army Watercraft Systems Life Cycle Management Strategy was developed and signed by the BOD co-chairs, Fahey and COL(P) Stephen Farmen, Army Chief of Transportation, in July 2011.
“It is vital for all of the stakeholders to be on the same page … to ensure that Army watercraft receives the proper attention and funding [and that] the fleet remains healthy across the board. This
is what makes the BOD so important,” Fahey said.
Product Director Army Watercraft Sys- tems (PD AWS), reporting to PEO CS&CSS’ Project Manager Force Pro- jection,
shared critical fleet portfolio
information with PEO CS&CSS and the Chief of Transportation, highlight- ing that many of the vessels were well beyond their estimated useful service life and were growing more costly to sustain.
PD AWS recommended several courses of action to reverse this trend.
Additionally, the Army watercraft com- munity provided information on lessons learned from current operations, future force requirements, Army Force Gen- eration equipping strategies, and impacts based on the Army’s strategic priorities. Also discussed were maintenance and sustainment opportunities, emerging and future requirements, and the prioritizing and execution of critical tasks ahead.
UNIQUE CAPABILITY
“Every top-level Army strategic document calls for an expeditionary capability, aus- tere access capability, and the ability for the joint ground force commander to overcome or bypass degraded infrastruc- ture in an AOR [area of responsibility]. This is no surprise to Army Mariners; these capabilities are what Army water- craft have always brought to the table and will continue to bring to the future Army,” said CW5 Michael Wichterman, Chief
EVERY TOP-LEVEL ARMY STRATEGIC DOCUMENT CALLS FOR AN EXPEDITIONARY CAPABILITY, AUSTERE ACCESS CAPABILITY, AND THE ABILITY FOR THE JOINT GROUND FORCE COMMANDER TO OVERCOME OR BYPASS DEGRADED INFRASTRUCTURE IN AN
AOR [AREA OF RESPONSIBILITY].”
ASC.ARMY.MIL 41
”
ACQUISITION
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 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162 |
Page 163 |
Page 164 |
Page 165 |
Page 166 |
Page 167 |
Page 168 |
Page 169 |
Page 170 |
Page 171 |
Page 172 |
Page 173 |
Page 174 |
Page 175 |
Page 176
