ZERO TO FULL MANPOWER IN 8 HOURS
This approach stemmed from the need to provide flexibility for different levels of programs, identify future requirements and accommodate human resource challenges.
estimate in each program and come together in functional com- petency groups. Tey compare results to PRSM, look for trends and issues and see where they can find efficiencies across the PEO.”
You may not use the same in-depth review process as PEO GCS, but you’ll definitely be using PRSM to approve your manpower requirements on an annual basis as part of
thermore, you’ll have a chance to share your thoughts on the model and enhance its capabilities: You’ve received word from your PEO that PRSM-PM will undergo an update in 2019. Another group of subject matter experts from the PEOs will come together to ensure that the tasks and workload drivers are still representative of the community and that the model still accurately projects program workforce requirements given the current environment, and to provide recommendations on how the model can better support PMO reporting requirements.
you’ll need in your PMO as well as the functional divisions and the tasks each will need to carry out. You feel relieved. Not only have you been able to calculate your manpower require- ment, but you’re confident that you’ll be able to match the right people to the required skill sets. All that’s left to do is submit your requirements.
Your PEO provided a PowerPoint template to package your out- puts. You copy and paste a few of the output reports, provide some narrative about your program and submit your require- ments to the PEO analyst.
Over the next few months, you find that this validated require- ment has been approved by DCS G-3/5/7, used in the Army’s civilian Total Army Analysis processes, submitted to the Pro- gram Evaluation Group for resourcing, and later used to develop your program’s Table of Distribution and Allowances and matrix personnel support agreements. In roughly six months, you developed the requirement, had it approved and received resources for the upcoming POM years. Te PRSM timeline proved to be much more streamlined and efficient than that of the concept plan.
ANNUAL UPDATES Tis isn’t the last time you’ll see PRSM. Every year you’ll use it to update your requirements as your program transitions. “PEO GCS uses PRSM both in the annual forecasting process and in standing up new programs,” Gonda said. “At the beginning of the annual forecasting process, PEO GCS looks out seven years at the budget cycle and uses PRSM to anticipate fluctuations in programs. Ten, supervisors perform a detailed troop-to-task
30 Army AL&T Magazine July-September 2017
CONCLUSION Te PRSM models might look different for each functional community, but the usability and incorporation into Army pro- cesses remain the same. Tis is good news across the Army for those doing just what you’re doing. For the first time, the Army is able to develop consistent and reliable workforce requirements in a timely manner, reflecting the most current Army strategy. Te requirements can be updated at any time to support what-if drills and programmatic changes.
Tere are still many conceivable refinements to the PRSM suite to make it a more robust set of tools, and the Army needs your help in making those improvements. Te models require your subject matter expertise in Army missions, processes and com- munity operating procedures to develop successful outputs.
For more information, contact the author at
rebecca.s.meyer10.
civ@mail.mil.
MS. REBECCA MEYER is a program support specialist for the deputy assistant secretary of the Army for plans, programs and resources. She holds an M.S. in cost estimating and analysis from the Naval Postgraduate School and a B.S. in mathematics from the Richard Stockton College of New Jersey. She is Level II certified in program management and business – cost estimating.
the POM. Fur-
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148 |
Page 149 |
Page 150 |
Page 151 |
Page 152 |
Page 153 |
Page 154 |
Page 155 |
Page 156 |
Page 157 |
Page 158 |
Page 159 |
Page 160 |
Page 161 |
Page 162