Downloaded from https://www.everyspec.com existing controllable data requests. Supporting information will be limited to the content and frequency of the basic data request. C–3. Other agency RCSs RCSs assigned by other agencies and used by the Army under chapters 3 and 4 may be composed differently from Army RCSs. The MICO will answer questions about these symbols. C–4. Use of other agency control symbols a. Controlled data request prepared by an Army agency for a non-Army agency will cite the symbol, if any, assigned by that non- Army agency. b.
Approvals are granted by ADS (Comptroller) for Defense data requests levied on the Military Departments, and by GSA for other Federal agency requests. However, Army implementation is not authorized before coordination with the HQDA MICO to permit a thorough check of existing Army data requests that could partly or totally fulfill the requirement. Copies of all prescribing directives will be given the HQDA MICO to assist in this determination. c. Compliance with this regulation is required when responding to non-Army management information requirements. C–5.
Composition of RCSs for management information requirements initiated by Army An example and explanation of the elements of an RCS is given below: AG–(OT)–729(R3)(a) Major changes. Assign revision suffix to major changes. (Recurring data requests only.) AG–(OT)–729(R3)(b) Number. Use one sequence of numbers for both one-time and recurring data requests in each ini- tiating agency. AG–(OT)–729(R3)(c) One–time requests only. Use the letters “ OT.” AG–(OT)–729(R3)(d) Agency code. Use an acronym or alpha code that denotes the initiating agency. This code is used for both recurring and one-time data collections (e.g., ; MED for OTSG; AG for Adjutant Gener- al).
Do not duplicate codes used by other agen- cies. 15 AR 335–15 • 28 October 1986