Downloaded from https://www.everyspec.com (4) Office of the DCS, G–3. (5) Office of the DCS, G–8. (6) Office of the DCS, G–1. (7) DCS, G–4. (8) DCS, G–2. (9) U.S. Army Training and Doctrine Command (USATRADOC). (10) U.S. Army Forces Command (USAFORSCOM). (11) U.S. Army Materiel Command (USAMC). (12) U.S. Army Europe. (13) U.S. Army Intelligence and Security Command (USAINSCOM). (14) U.S. Army Pacific (USARPAC). (15) U.S. Army Special Operations Command. (16) National Guard Bureau, Army National Guard. (17) Office of the Chief Army Reserve. (18) Office of The Surgeon General through U.S Army Medical Command (USAMEDCOM)). (19) Office of the Chief of Engineers. (20) IMA. (21) U.S.
Army Special Operations Command (USASOC). c. Representatives of other Army Staff agencies or commands may be invited to participate in the TSARC process, as necessary, and especially when test programs fall in their functional area of responsibility or involve their resources. d. The chairperson may request other Army Staff agencies and Army commands to attend when tests fall within their functional area of responsibility or involve their resources. 9–4. TSARC working group A working group (WG) will support the TSARC. Each Army element represented on the TSARC will appoint a working representative (grade of major or equivalent DA civilian) and alternate.
In addition, the TSARC WG will include representatives from appropriate Army elements who can assist in identifying matters of interest to their respective agencies. 9–5. Direction, control, and administration a. The TSARC is a semi-annual process, with fall and spring cycles. Each cycle consists of one general officer and two Working Group reviews: (1) IWG meetings are held in February and August. All new and revised OTPs to be presented will be coordinated with the system program managers prior to submission. The working group members will— (a) Review new OTPs and those revised since the previous FYTP. (b) Identify potential resource conflicts for resolution prior to the MWG.
(c) Identify potential issues for the general officer TSARC. (2) Mid Cycle Working Group (MWG) meetings are held in April and October. New and revised OTPs (since the IWG) to be presented will be coordinated with the system program managers prior to submission. The working group members will— (a) Review OTPs that are new or revised since the IWG meeting. (b) Review and resolve resource conflicts identified during the IWG meeting and the staffing of the draft FYTP. (c) Review resource allocation priorities for tests having execution and budget year requirements. (d) Review proposed test priorities. (e) Identify potential issues for the general officer TSARC.
(f) Verify the need for the tests and satisfaction of a 2-year resource notification requirement. (3) GO TSARC meets in June and December. b. General officers will resolve test requirement conflicts, recommend test priorities, and recommend OTPs for inclusion in the FYTP. The FYTP will be published after HQDA DCS, G–3 approval and signature. A paper GO TSARC may occur when there are no issues requiring GO TSARC resolution. TSARC working group members will ensure that all potential GO level test requirement conflicts are resolved and that their GO TSARC representative concurs with the OTPs recommended for inclusion in the FYTP.
The TSARC working group members will also ensure that their GO TSARC representative concurs with the recommended test priorities. The GO TSARC member concur- rence will be provided to the GO TSARC chair. c. The TSARC chair may also call special meetings to address critical problems that cannot wait for a regularly scheduled meeting. d. Out-of-cycle TSARC staffing is required for new or significantly changed OTPs requiring resources within 1 year of date of submission to the TSARC. The following procedures apply: 30 AR 73–1 • 1 August 2006