Downloaded from https://www.everyspec.com Whether or not a request is “ unreasonable” is a matter of judgment. It involves consider- ation of the mission and the resources of the preparer and not simply the absolute work- load. The factors below bear on whether a request is unreasonable— ( 1 ) P r e p a r a t i o n w o u l d r e q u i r e e x t e n s i v e overtime or keep other important work from being completed on time. (2) The existing operating records and in- formation systems do not provide the data required or such data cannot be readily pro- duced from the system; for example, retroac- tive data requests that would need extensive research of records or files.
(3) The purpose of the request might be s e r v e d b y d a t a a l r e a d y a v a i l a b l e t o t h e requester. b. An exemption that certifies the request does not require “ extensive compilation or research over and above normal operations” p e r m i t s t h e f l o w o f d a t a a m o n g a g e n c i e s whose staff and operating relationships re- quire a day-to-day exchange of spot data. Al- though in the main, these exemptions cover nonrecurring data exchanges that arise out of oral discussions, they are not limited to such exchanges and include written requests for one-time data requests. be an oral statement, a manual report, or an automatic data processing (ADP) product. b.
An ADP product is one which leaves the physical confines of the ADP operations element and is sent to another element either inside or outside the DPA unit. f r o m o n e o r m o r e o t h e r F e d e r a l a g e n c i e s , with the initiating agency exceptions below: (a) Legislative Branch. (b) Judicial Branch. (c) Presidential requirements. (d) OMB budgetary requirement. ( e ) I n d e p e n d e n t r e g u l a t o r y a g e n c i e s e x - cepted by PL 96–511 or OMB. (4) Non-Federal agency management in- formation requirements. A requirement from a State or local government, a private organi- zation, or an individual. (5) Public management information re- quirement.
A Federal agency request from 10 o r m o r e n o n - F e d e r a l g o v e r n m e n t s , businesses, institutions, groups or individuals, as further explained in chapter 4. Management information requirement A requirement for management information to be collected, processed, and transmitted on a periodic, as required, or one-time basis. A request may be transmitted orally or in writ- i n g a n d m a y r e q u i r e s e v e r a l i n f o r m a t i o n products, data inputs and data outputs, proc- essed either manually or by ADPE.
An ap- p r o v e d c o n t r o l l e d 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 i s a s s i g n e d a s R C S f o l l o w i n g procedures in appendix C. a. Control Status. ( 1 ) C o n t r o l l e d m a n a g e m e n t i n f o r m a t i o n requirement. An approved request that is as- signed an RCS under this AR. (2) Exempt management information re- quirement. Requests listed in chapter 5 do not require an RCS. ( 3 ) U n a u t h o r i z e d m a n a g e m e n t i n f o r m a - tion requirement. A nonexempt request that has not been assigned an RCS before the requiring directive is published. b. Frequency.
( 1 ) R e c u r r i n g m a n a g e m e n t i n f o r m a t i o n requirement. A request that is levied for sub- m i s s i o n a t p r e s c r i b e d t i m e s ( e . g . , d a i l y , weekly, monthly, annually) or upon each oc- currence of an event or situation (e.g., occur- rence of an accident). Standard frequencies are specified in the DOD Standard “ Occur- rence Frequency” in AR 18–12–1 and AR 335–11. ( 2 ) O n e – t i m e m a n a g e m e n t i n f o r m a t i o n requirement. A request levied for one-time only submission. c. Source. (1) DA management information require- ments. Data required, collected and processed wholly within DA. (a) Internal data requests.
Request by an Army agency of agencies under its command. (b) External data requests. Requests by Army agencies outside the command of the initiating agency. (2) DOD agency management informa- tion requirements. A request levied on the Army by DOD components (i.e., Office, Sec- r e t a r y o f D e f e n s e , D e p a r t m e n t o f t h e A i r F o r c e o r N a v y ; U S M a r i n e C o r p s ; J o i n t C h i e f s o f S t a f f ( J C S ) ; D e f e n s e L o g i s t i c s A g e n c y ( D L A ) ; D e f e n s e C o m m u n i c a t i o n s Agency (DCA); Defense Intelligence Agency (DIA); or National Security Agency (NSA)). (3) Interagency management information requirement.
Any request that involves pro- viding data to one or more Federal agencies Management Information System An assemblage of resources and procedures organized to collect, process, and issue data. These data can then be used to decide how to plan, organize, staff, direct, coordinate, and control the use of resources to accomplish missions and tasks. Management information requirement workload The total workload (and costs) at all levels that would end if the request were discontin- ued. Cost estimates for management informa- tion requirement workloads will be computed using guidance in appendix B.
Management information Information required in planning, organizing, directing, coordinating, and controlling an or- ganization and its assigned mission tasks. Product control number (PCN) A s y m b o l a s s i g n e d t o i d e n t i f y e a c h A D P final product by the functional proponent or the DPA. See TB 18–103 for minimal re- quirements for PCN compositions. Management information control office (MICO) A person assigned authority to— a . A p p r o v e , d i s a p p r o v e , o r r e v i s e p r o - posed management information requirements within an agency, based on this regulation. b. Assign control symbols to needed man- agement information requirements within an agency. c .
R e v i e w c o n t r o l l e d 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 a n d d a t a p r o d u c t s a s outlined in this regulation. d . P r o v i d e t h e j u r i s d i c t i o n a l c o n t r o l o f 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 a n d data products in paragraph 1–10. Requirement control symbol (RCS) A symbol assigned to a management infor- mation requirement by the MICO with juris- diction to show it has been approved under this AR. (See app C for the composition of RCSs.) System control products ADP products required to monitor and main- tain system integrity.
These include products produced by operating systems, executive or supervisor programs; compilers, assemblers, or translators; input/output control systems; g e n e r a l i z e d u t i l i t y r o u t i n e s ; a n d h a r d w a r e monitors. Management information control liaison officer (MICLO) A person assigned authority by a principal staff agency of a command or activity to— a. Coordinate information control matters within the staff agency. b. Assist in review of ADP products for which the agency is the system proponent. c . P r o v i d e t e c h n i c a l a s s i s t a n c e t o t h e MICO as needed in the control of manage- ment information.
Section III Special Abbreviations and Terms There are no special terms. Management information product P r o d u c t s g e n e r a t e d i n r e s p o n s e t o a n a p - proved requirement for information. a. The information product may be in nar- rative, tabular, or graphic form. A product can be transmitted in different ways. It may 17 AR 335–15 • 28 October 1986