University ITSM

"Capacity management" seems to be overlooked in ITIL implementations--capacity management gets pushed way down the implementation plan, or is seen mainly as an input to event management (for alerts about disk filling up) and service level management (for making promises to users about what capacity will be available).
One of capacity planning's major outputs is a capacity plan--a document describing how capacity should change over the next time period, say over the next year.  It should predict how the infrastructure, service demand, and business change will impact capacity needs, and describe what additional capacity is needed to meet those demand.  (The plan should also address how to scale back capacity for services where demand is lacking, e.g. a server that has allocated to it more SAN disk than it needs.)
I'm writing about capacity plans now because they can become an important input for Universities' capital requests.  When the IT department is requesting money, ideally it could refer to its capacity plan for justification.  "Capacity management has anticipated 30% more users of this service in the next 12 months, meaning that we need an additional 1 TB of disk space."  "Actionable" capacity plans could help make capacity planning a lot more interesting and relevant for IT management--because here capacity management could directly inform business decisions about IT spend.