Downloaded from https://www.everyspec.com f. Item 11—Submission date. Enter date(s) responses are due at requesting office. Use DOD standard format of YY MM DD. g. Item 13—Minimize. If requirement to be transmitted electrical- ly, enter “ MIN” to indicate continued electric submission under MINIMIZE conditions or “ NON–MIN” to indicate submission by other than electrical means during MINIMIZE condition. If not transmitted electrically, enter “ NA.” h. Item 14—Mobilization status. Indicate status of the require- ment under conditions of mobilization or national emergency in the following way: No change (NC), Modify (M), Rescission (R), or if prepared only in case of mobilization (MOB). i.
Item 15—Security classification. Enter standard data element (DE) name specified in DOD standard, “ Security Classification,” in AR 181210. j. Item 17—Approval requested by. Show signature and title of a responsible person of the requesting agency. Normally, this will be a division chief or equivalent. k. Item 22—Cost estimate. Enter cost estimates developed in ac- cordance with appendix B. l. Item 23—Conformance with data elements and codes standard- ization program. This refers to the use of existing interim data elements (IDEs) or standard data elements (SDEs) published in the AR 18 series.
If the information proposal involves use of interim or standard data elements listed in the AR 18 series, record the IDE or SDE identification number. If the proposal involves use of elements not listed in the AR 1812 series, or proposes changes or additions thereto, explain and indicate that approval for the changes/additions has been obtained from the designated assigned responsible agency (ARA). m. Item 24—Preparing agencies. (1) Column a. List each agency or group of agencies involved in preparing data for the requirement. Typical illustrations of preparing agencies are as follows: (a) HQDA agencies.
OSA, each staff agency (Deputy Chief of Staff for Personnel (DCSPER), Deputy Chief of Staff for Logistics (DCSLOG), Comptroller of the Army (COA), etc.). (b) CONUS agencies. 1 . M A C O M s ( U S A r m y T r a i n i n g a n d D o c t r i n e C o m m a n d (TRADOC), US Army Forces Command (FORSCOM), US Army Materiel Command (AMC), etc.). 2. Each installation 3. Each national inventory control point (NICP) 4. Each civilian personnel office (CPO) 5. Each finance and accounting office (F&AO) (Fort Riley, Fort Belvoir, Fort Hood; Each DPA) (c) Overseas agencies. 1. MACOMS (US Army, Europe (USAREUR); US Army, Japan (USARJ), etc.). 2. Each installation 3. Each CPO (2) Column b.
Enter number of elements corresponding to each line in column a . (3) Column c. Enter total submissions per year by all elements on each line of column a . n. Item 25. For approved requests, the signature of the Manage- ment Information Control Officer, date of approval, and assigned RCS will be entered where indicated. requirements be submitted to the General Services Administration (GSA) for approval before implementation. 3–2. Procedures a. Requirement initiators within DA will— (1) Complete DA Form 335–R.
(2) As early as possible, agencies will discuss new or revised data requests with the MICO, HQDA (DAIM–ADI–M) for coor- d i n a t i o n w i t h O f f i c e , A s s i s t a n t S e c r e t a r y o f D e f e n s e ( O A S D ) (Comptroller)) and GSA. This action is to determine possible dupli- cate data sources, potential availability of data, cost estimating tech- niques to be used, impact on preparers, and management’s need for the information. (3) Obtain SF 360 (Request for Clearance of an Interagency Reporting Requirement) from HQDA (DAIM–ADI–M).
(4) Submit three completed copies of SF 360 through the agency MICLO/MICO to HQDA (DAIM–ADI–M) for transmittal to OASD (Comptroller) and GSA for review and approval action. Include the purpose of the data request and estimated costs. Also include three c o p i e s o f t h e p r o p o s e d d i r e c t i v e , f o r m s , a n d a n y o t h e r r e l a t e d papers. If not approved, GSA will return request for rejustification or denial. If approved, an interagency report control number (IRCN) will be assigned.
(5) After assignment of an IRCN by GSA, prepare a formal d i r e c t i v e ( w h i c h i n c l u d e s c i t a t i o n o f t h e I R C N ) , r e q u e s t i n g t h e needed data; submit three copies through agency MICLO/MICO to HQDA (DAIM–ADI–M). This office will forward the directive to GSA. (6) When the data are no longer required, advise all preparers and GSA through HQDA (DAIM–ADI–M). b. Implementing agencies within DA will— (1) Report interagency data requests received without GSA ap- proval or an IRCN to HQDA (DAIM–ADI–M). (2) Respond to approved requests. (3) Submit cost estimates as shown in appendix B or in OASD (Comptroller) instructions.
(4) Prepare formal directives to levy data requests or other Army agencies if necessary, including the IRCN cited by GSA. (5) Submit two copies of the requiring directive and Army direc- tive through agency MICLO/MICO to HQDA (DAIM–ADI–M). 3–3. Exemptions a. Title 41 CFR 201–45.6 exempts the types of data requests below from formal GSA review and approval procedures: (1) Presidential. (2) Legislative branch. (3) Judicial branch. (4) OMB budgetary. (5) One-time data collections of minor respondent burden. (6) Selected independent regulatory agency data requests. b.
Army agencies receiving a data request for implementation t h a t i s e x e m p t f r o m G S A r e v i e w w i l l a d v i s e H Q D A (DAIM–ADI–M). If Army control action is needed, the implement- ing agency will submit DA Form 335–R and process the data re- quest under this AR. HQDA (DAIM–ADI–M) will assign an RCS to such requests after review and approval. Note. Some management information requirements in the exempt group are assigned control symbols by OASD (Comptroller) before being forwarded to an Army agency. In such cases that symbol a p p l i e s , b u t a D A F o r m 3 3 5 – R w i l l b e p r o v i d e d t o H Q D A (DAIM–ADI–M) for record purposes.
Chapter 3 Army Interagency Management Information Program Chapter 4 Requests for Management Data From the Public 3–1. Scope This chapter prescribes policies and guidance for the Army Inter- agency Management Information Program. Title 41 Public Contracts and Property Management, Code of Federal Regulations (CFR) Sec- tion 201–45.6 requires that interagency management information 4–1. Scope a. This chapter prescribes procedures for requesting Office of Management and Budget (OMB) approval of certain data collection requests from the public and states policies extracted from the 5 AR 335–15 • 28 October 1986