Downloaded from https://www.everyspec.com (1) Identified by standard numbering patterns. (2) Approved by a designated official. (3) Reviewed periodically by initiating, monitoring, and prepar- ing agencies. (4) Revised or rescinded when management needs change. b. Periodic reviews must be made of each management informa- tion requirement and data product at least once every 3 years. c. Each directive that initiates a management information require- ment will cite the title and requirement control symbol (RCS) in the table of contents and text. Each subsequent action that affects the information requirement will also state the title and the RCS. d.
Requirements not specifically exempt under chapter 5, which have not been approved, assigned an RCS, or in other ways do not conform to this AR, are unauthorized. Notice of an unauthorized information requirement will be made. (See 1–7 d (19).) Chapter 2 Initiating Management Information Requirements and Data Products Section I Requesting Approval of Management Information Requirements 2–1. Scope This section— a. States the purpose of the requirement proposal. b. Prescribes procedures for requesting approvals of Army-initi- ated management information requirements to be prepared by Army and/or other DOD agencies. c. Gives the media for directives on management information requirements. 1–10.
Management information control jurisdiction Management information control jurisdiction is as follows: a. Headquarters, Department of Army. Management Information Control Officer (MICO), Architecture Design and Control Division, Architecture Design and Control Directorate, Office of the Assistant C h i e f o f S t a f f f o r I n f o r m a t i o n M a n a g e m e n t ( H Q D A (DAIM–ADI–M)), has jurisdiction over— (1) Requests for management data prepared by the public for all Army agencies. (2) Management information requirements between the Army and the central or national office of a non-Army agency.
(3) Management information requirements initiated by HQDA or a subordinate command or agency, and prepared outside the com- mand jurisdiction by a command or agency (Army or non-Army), e x c e p t a s n o t e d i n p a r a g r a p h b b e l o w u n d e r H Q m a j o r A r m y commands. b. HQ, Major Army Commands. Management Information Con- trol Officer (MICO) has jurisdiction over— (1) Internal management information requirements initiated by the command headquarters and prepared by subordinate organiza- tions outside the headquarters.
(2) External management information requirements initiated by the command headquarters or a field element to that command and prepared by not more than one external command or agency pro- vided that the MICO of the external command concurs. In the case o f n o n c o n c u r r e n c e , r e f e r t o H Q D A ( D A I M – A D I – M ) W A S H D C 20310–0700. (3) Data requests initiated by a field or local office of a non- Army agency and prepared by elements of that command. (4) Data requests developed for command-unique standard ADP systems. c . H Q , S u b o r d i n a t e C o m m a n d s , I n s t a l l a t i o n s , a n d A g e n c i e s .
Management Information Control Officer (MICO) has jurisdiction over— (1) Internal management information requirements initiated by the command, installation, or agency headquarters and prepared by subordinate organizations outside the headquarters. ( 2 ) D a t a c o l l e c t i o n r e q u e s t s d e v e l o p e d f o r l o c a l u n i q u e A D P systems. d. HQDA Agencies/Macom Elements. Management Information Control Liaison Officer (MICLO) has jurisdiction over— ( 1 ) M a n a g e m e n t i n f o r m a t i o n r e q u i r e m e n t s i n i t i a t e d b y t h e HQDA agency/MACOM element and prepared by a subordinate element or another part of the HQDA agency/MACOM element.
(2) Internal management information requirements when the initi- ator or proponent and the preparer are subordinate activities. ( 3 ) D a t a c o l l e c t i o n r e q u e s t s f o r A D P s y s t e m s u n i q u e t o t h e HQDA agency/MACOM element. 2–2. Purpose of the requirement proposal The requirement proposal provides information, to the MICO with jurisdiction (para 1–10), which is used to— a. Determine that the provisions of this and other Army regula- tions are met. b. Evaluate a new or revised information requirement. c. Approve an information requirement or to cite an exemption from control. 2–3. Procedures a. Contents and submission of the requirement proposal.
The initiating or monitoring agency will prepare a management informa- tion requirement proposal that contains— (1) DA Form 335–R (Application for Approval of Management Information Requirement). DA Form 335–R will be reproduced locally on 8 1 2 - by 11-inch paper. A copy of the form for local reproduction is located at the back of this regulation. Submission will be as follows: (a) Information requirements within an agency. Send two com- pleted copies of form to the agency MILCLO/MICO. (b) Information requirements outside the initiator’s agency. Send three completed copies through the agency’s MICLO to the MICO with jurisdiction (paragraph 1–10).
(2) DA Form 1167 (Request for Approval of Form). Staff with MICLO/MICO for each DA form to be used in the collection of data. (3) DA Form 260 (Request for Printing of a Publication). When the management information requirement is proposed in an Army regulation, staff the draft of regulation with the MICO with jurisdic- tion before publication. (4) Other preparer guidance. b. Coordination. The initiating or monitoring agency staff officer will— (1) Obtain coordination on all management information require- ments before the project is implemented. (2) Insure that the requested data satisfies as many requirements as possible on the subject matter.
(3) Coordinate proposed information requirements, new or re- vised, in advance with— (a) The MICO with jurisdiction. (b) A representative group of preparing agencies. ( c ) A g e n c i e s t h a t c o n t r o l r e s o u r c e s , s u c h a s A D P s u p p o r t elements. c. Distribution of directive on information requirements. Copies of the published directive containing approved and exempt informa- tion requirements will be provided the MICO with jurisdiction. 2–4. Data element standardization Standard data elements must be used. Refer to AR 310–25 and AR 18–12 series for standard data elements to be used in completing data requests. 3 AR 335–15 • 28 October 1986