Installation Management Institute January 2007

1. Installation Management InstituteJanuary 2007 PART 8- UNIT LEVEL DATA Determine/ Validate Requirements This section of the workshop addresses unit level data.This section of the workshop addresses unit level data.

2. The Master Planning Formula Implicit in the process is the Master Planning Formula, which states that the Force (populations, units and missions) is evaluated based on Criteria (policy that determines which populations or units require a particular type of facility and criteria that says how much is authorized if the policy standard is met). This results in Allowances, an objective statement of requirements based solely on automated analysis of corporate data. Allowances are then compared to Assets, which consist of the inventory plus planned construction, to provide an initial quantitative status of a particular location’s ability to support its populations, units and missions with infrastructure. This is known as a Tabulation of Existing and Allowed Facilities, or the TAB. In the absence of further effort the allowance is assumed to be an accurate statement of the requirement and corresponding assets and, at HQDA, is treated as such. The TAB is then evaluated to determine the extent to which it correctly states the requirements. If there is a valid deviation the installation is allowed to adjust the TAB by making requirements edits which, if approved by the responsible IMA region, become the basis for evaluating the installations infrastructure needs.Implicit in the process is the Master Planning Formula, which states that the Force (populations, units and missions) is evaluated based on Criteria (policy that determines which populations or units require a particular type of facility and criteria that says how much is authorized if the policy standard is met). This results in Allowances, an objective statement of requirements based solely on automated analysis of corporate data. Allowances are then compared to Assets, which consist of the inventory plus planned construction, to provide an initial quantitative status of a particular location’s ability to support its populations, units and missions with infrastructure. This is known as a Tabulation of Existing and Allowed Facilities, or the TAB. In the absence of further effort the allowance is assumed to be an accurate statement of the requirement and corresponding assets and, at HQDA, is treated as such. The TAB is then evaluated to determine the extent to which it correctly states the requirements. If there is a valid deviation the installation is allowed to adjust the TAB by making requirements edits which, if approved by the responsible IMA region, become the basis for evaluating the installations infrastructure needs.

3. The TAB Management Process Coarse Screen Verify/reconcile supporting data ASIP Assets Organize the force the way you manage it Prepare installation and unit profiles Installation profiles look at FCGs Unit profiles look at organizations Determine/Validate requirements Analyze facility status Update requirements Confirm results

4. Unit Workbooks For major TAB update efforts it may be necessary to create a parallel book to manage information about units called “Unit Workbooks” The Unit Workbook focuses information by Major Units Major Units are from TAB 16 in the Installation Workbook One Workbook tab per Major Unit Each TAB can be considered a Unit Profile Installation workbooks track data by FCG. They are designed to look at a single FCG in depth and only address the units that impact on that FCG either by having allowances, requirements and assets. Consequently it provides an installation-wide view of each FCG in breadth. The unit workbook looks at each organization that has real property assigned grouped with all activities to which it provides space. Instead of looking at the installation in breadth the unit workbook looks at each unit in depth. Because of the nature of its uses the unit workbook may not be as standard as the installation workbook, but contains as a minimum an RPLANS TAB Package for the organization and its component pieces, personnel and equipment data from FPS if available, and narrative information about the organization and its missions to include information provided by the organization and information obtained from other sources including the world wide web. The detailed discussion of the composition and preparation of the unit workbook is outside the scope of this reference and training guide.Installation workbooks track data by FCG. They are designed to look at a single FCG in depth and only address the units that impact on that FCG either by having allowances, requirements and assets. Consequently it provides an installation-wide view of each FCG in breadth. The unit workbook looks at each organization that has real property assigned grouped with all activities to which it provides space. Instead of looking at the installation in breadth the unit workbook looks at each unit in depth. Because of the nature of its uses the unit workbook may not be as standard as the installation workbook, but contains as a minimum an RPLANS TAB Package for the organization and its component pieces, personnel and equipment data from FPS if available, and narrative information about the organization and its missions to include information provided by the organization and information obtained from other sources including the world wide web. The detailed discussion of the composition and preparation of the unit workbook is outside the scope of this reference and training guide.

5. TAB 16 Extract – Major Unit Lash Ups

6. Unit Profiles RPLANS TAB Package Summary TAB ASIP data UIC Profile Detailed TABs FPS Personnel and Major Equipment List FPS Allowances Summary WEB information Unit provided information

7. Prepare Unit ProfilesTAB Packages Select UICs from TAB 16 Create UIC Package Run TAB Package: Reports/ Tabulation of Facilities/TAB Package (not RC TAB Package) Caution: Facilities on Unrecognized UICs report will not appear in a TAB package

8. Create TAB Package STEPS to CREATE a TAB Package: Utilities/ UIC Packages/ Create new UIC Package/ Select UICs/ Choose UICs and ADD/ OK/ Name the Package/ Save NOTE: After doing this, the report will NOT show up in the report status windowSTEPS to CREATE a TAB Package: Utilities/ UIC Packages/ Create new UIC Package/ Select UICs/ Choose UICs and ADD/ OK/ Name the Package/ Save NOTE: After doing this, the report will NOT show up in the report status window

9. Run a TAB Package STEPS to RUN a TAB Package: Reports/ Tabulation of Facilities/ TAB Package/ Select from UIC Tab Packages (the one you created should be in here) and double click/ OK/ Choose Year (farthest out)/ RunSTEPS to RUN a TAB Package: Reports/ Tabulation of Facilities/ TAB Package/ Select from UIC Tab Packages (the one you created should be in here) and double click/ OK/ Choose Year (farthest out)/ Run

10. AMSAA TAB TABs can be prepared at either installation level by FCG or at unit level by UIC or groups of UICs. In reality, the installation TAB for a particular FCG should be the sum of the unit TABs for that same facility category. This slide shows the TAB for facilities in GSF that RPLANS produces using a feature called the TAB package. The TAB package allows users to associate related UICs and prepare a TAB for them as a group. This is addressed further in Section 8 of this workshop workbook.TABs can be prepared at either installation level by FCG or at unit level by UIC or groups of UICs. In reality, the installation TAB for a particular FCG should be the sum of the unit TABs for that same facility category. This slide shows the TAB for facilities in GSF that RPLANS produces using a feature called the TAB package. The TAB package allows users to associate related UICs and prepare a TAB for them as a group. This is addressed further in Section 8 of this workshop workbook.

11. ProcessDetermine/Validate Requirements Focus on FCG but don’t ignore relationships Battalion HQ/Admin/Aviation Unit Ops Organizational Storage/Inst Enclosed Storage Barracks, AT/MOB Barracks, Student UPH Focus on unit but don’t ignore installation-wide implications (if one is excess, is another short?) Requirements are based on what you need, not what you have Mission Equipment Personnel

12. Requirements By default requirements = allowances Allowances adjusted to reflect personnel, equipment, mission or other conditions not fully addressed in the allowance generation process MTOE vs. OTOE Contracted activities Contingency missions Capacity issues Requirements should be based on the same factors that generate an allowance (force, policy and criteria)

13. ProcessDetermine/Validate Requirements Start with the allowance and… Evaluate factors that trigger allowances Link requirements to policy and criteria in ACTS Requirements can be lower than allowances Try FPS requirements for Unit Level FCGs Consider all unit requirements, not just target FCGs

14. Requirements Worksheet

15. Requirements Sequence Installation RPLANS users with privileges edit requirements RPLANS Site administrator submits as desired or in accordance with Region directives Region approves, modifies or disapproves edits and moves to approved HQRPLANS updates requirements from Region approved set in June and December based on mid-May and mid – November status Region RPLANS feeds requirements to ISR

16. Other Thoughts on Requirements Determining requirements is the meat of the process Proper identification of requirements essential to effective space management Effective space management saves resources Get the commander involved Possession does not equal requirements What was required before isn’t always required now