search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
To better integrate and synchronize the development and fielding of the Army’s required capabilities, as well as to provide a more efficient and effec- tive capability management process, the U.S. Army Training and Doctrine Command (TRADOC) recently changed its strategy for TRADOC Capability Manager (TCM) alignment to include TCMs that focus on organi- zations as well as other TCMs that will continue the traditional systems-based functional focus.


From Systems to Programs In the early 1970s, TRADOC was established and assumed the training functions of the Continental Army Command and the combat devel- opments mission of the Combat Developments Command, as part of a major reorganization of the Army command structure. In assuming those responsibilities, TRADOC became the focal point for formulating the need and requirements for new weapon and materiel systems, monitoring the development of those systems, and identifying the need to adjust train- ing, personnel, and organizations to facilitate the integration of these new systems into Army units.


To fulfill its role in providing training excellence, guidance on fighting the country’s wars, and insights about the organization and materiel necessary to support the Soldier on the battlefield, TRADOC needed to take a total sys- tems approach to development. This approach spawned the establishment of the first TRADOC System Manager (TSM) offices in 1977 (see Figure 1). Each TSM consisted of a colonel with a small staff pulled from the TRADOC centers and schools.


The TSMs represented all major weapon and materiel systems in development and functioned with power and authority comparable to those of the program and project managers within the U.S. Army Materiel Command


FIGURE 1. TRADOC SYSTEM MANAGER OFFICES ARMY AL&T


FORT BENNING Black Hawk


Fighting Vehicle System Improved Tow Vehicle


FORT HUACHUCA Corps Tactical Electronic


Warfare/Intelligence System


Division Tactical Electronic Warfare/Intelligence System


FORT BLISS


Division Air Defense Gun Patriot Roland Stinger


FORT GORDON


Automatic Telephone Central Office Advanced Tactical Support System


Single Channel Ground and Airborne Radio System


Tactical Satellite Communications FORT KNOX Tank System Development


FORT RUCKER Attack Helicopter


Advanced Scout Helicopter HELLFIRE


FORT SILL


Copperhead Firefinder


General Support Rocket System


M198 Towed Howitzer and associated systems Pershing II Missile


FORT LEAVENWORTH Positioning/Navigation


Remotely Piloted Vehicle Smoke


Stand-off Target Acquisition System Tactical Operating Systems


SOURCE: March 1977 brief to TRADOC CG


Tactical Fire Direction System 8" Howitzer Systems


(AMC). They were given the job of integrating and synchronizing all the doctrine, training, leadership, organizations, and materiel activities associated with fielding weapon and materiel systems. The TSMs’ charters were to facilitate the training, logistical support, and personnel functions needed to sustain the systems during fielding and beyond. They were designed to be the “energizers” of the larger TRADOC school staffs and not necessarily the “doers.”


TSMs served as user advocates—the “voice” of the warfighter—and worked in complement with the system developers in AMC. They reported directly to their respective school commandants, and were chartered by and worked for the TRADOC Commanding General (CG) in defending the need for the systems.


The original intent was for each TSM office to be disestablished once the specific weapon or materiel system was fielded. However, the continuation of block improvements, the evolution of spiral developments, and the general requirement for continuous improve- ments to these systems required the TSMs to evolve beyond their original


purpose of addressing the life cycle of changing materiel programs and force design updates.


Recognizing the increasing linkages and interdependencies between systems and the growing number of different systems being developed and fielded, TRADOC identified the need for a similar type of office to facilitate integration across TRADOC centers and schools. Hence, TRADOC Program Integration Offices (TPIOs) were established with the mission to serve as the TRADOC integrating agency for their assigned systems. The first of these, TPIO Deep Battle, was established in April 1988. Unlike the TSMs, which managed specific systems, the TPIOs managed the commonality and interoperability aspects and provided management and development oversight for proponent system-specific components, modules, or weapon systems.


Establishment and Evolution of TCMs


Eventually, rather than concentrating on a single system, TSMs gained responsi- bility for a family of materiel systems, or a group of closely related or interdepen- dent materiel systems. TRADOC found


APRIL –JUNE 2011 67


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