Seven approved projects, five scarce roles and a storm reserve are reconciled by quarter in this GM591 Unit 9 portfolio capacity review, which moves two projects and declines a request. Searches like "gm 591 unit 9 assignment example", "gm591 unit 9 sample" and "gm591 unit 9 example" land here.
What a finished GM591 Unit 9 portfolio capacity review looks like
Six pages with a demand-and-supply table by role and quarter, a heat map and one page of recommendations. Supply is counted first: [two] GIS analysts, [one] control systems engineer, [four] distribution engineers, [six] IT staff and [eleven] line crews, each reduced by work that is not a project, such as new service connections and a storm-restoration reserve of [25] percent of crew hours from [June] through [September]. Demand is summed by role from each project's plan. The heat map shows red in two rows. GIS analysts reach [190] percent in the second and third quarters, because meter replacement, the outage system and pole-loading remediation all need the same network model corrected first. The control systems engineer is assigned to four projects at once. Line crews stay under [85] percent once the pole program is phased.
How a GM591 Unit 9 example is structured
The review counts supply before demand, since most capacity problems start with an inflated count of available people. The supply section subtracts run work role by role and shows the arithmetic, so a reader can dispute a figure without disputing the method. Demand follows, taken from project plans. The heat map then locates the conflicts. At the center is an argument that the GIS overload is a sequencing failure rather than a staffing shortage: one network model cleanup serves three projects, and doing it once, first, removes most of the conflict. The control engineer's load is the same problem in another form, and the paper cites Goldratt's argument that a person split across several projects slows all of them. Recommendations follow in order of effect: resequence, contract the cleanup, defer vegetation analytics, decline a resubmitted charger request.
Supply after run work
Each role's hours are reduced by work that must happen regardless: service connections, meter maintenance, system support and the storm reserve. The subtraction is shown line by line, because the net figure is where most portfolio reviews go wrong.
Two rows in red
The heat map colors each role and quarter by load. GIS analysts and the control systems engineer turn red; distribution engineers sit near [95] percent; line crews stay comfortably below capacity once pole work is phased.
One model, three projects
Meter replacement, the outage system and pole-loading remediation all need the electrical connectivity model corrected. Each plan assumed another project would do it. The review makes the cleanup its own piece of work, scheduled first and funded once.
Four projects, one engineer
The control systems engineer is assigned to network segmentation, the meter network, outage integration and the fiber pilot. Citing Goldratt, the review shows that splitting him four ways delays every project, and it sequences his work instead.
Moved, deferred, declined
The outage system starts after the model cleanup, vegetation analytics waits [two] quarters, and a resubmitted charger proposal is declined for this cycle. Each change is dated and its effect on the heat map shown.
Where marks go in GM591 Unit 9
Capacity reviews in GM591 fall short most often by counting people instead of hours available for projects: a roster treated as fully free, with storms, service calls and support work ignored. Graders look for run work subtracted before any project demand is compared. Reviews that aggregate all roles into one total hide the bottleneck, which is almost always a scarce specialist rather than headcount overall. A finding without a recommendation, or recommendations that simply ask for more staff, miss what the unit tests: choosing what to delay or end. Many sections credit a review that finds a shared dependency across projects and resolves it once. Mandatory work left off the chart, as though obligations consumed no one's time, is a conceptual error that costs the analysis row.
Get a GM591 Unit 9 example written to your instructions
List the approved projects, the roles each one needs by quarter as far as you can estimate, and the staff actually available after routine work; add the Unit 9 prompt and rubric. The first review is free and ready in 24-48h, with run work subtracted first and every recommendation dated.
GM591 Unit 9 questions, answered
What counts as run work?
Anything the organization must do whether or not a project exists: routine maintenance, customer service, support of existing systems, compliance tasks and reserves for predictable emergencies. It usually consumes a large share of specialist time. Subtracting it first, role by role, gives a realistic picture of what projects can draw on, and graders tend to check whether a review did this.
Is hiring or contracting an acceptable recommendation?
It can be one recommendation among several, provided it is specific and costed, such as contracting a defined piece of work. A review that answers every conflict with more staff avoids the portfolio decision the unit is about. Show what can be resequenced, deferred or declined first, then use outside help for what remains.
How detailed should demand estimates be?
Quarterly by role is usually enough for a portfolio review. Monthly detail belongs in project schedules, and daily detail obscures the pattern. Where estimates are uncertain, give a range and note which conflicts survive even at the low end, since those are the ones that justify moving a project.