Complete AI Training

AI agent for it managers

Network Capacity Planning Agent

No network resource hits capacity unplanned

Network Capacity Planning Agent: what goes in, what the agent does and what you get

What it does

Network traffic grows, and without planning a link or device saturates at the worst time. Each week this agent collects utilization for links, device interfaces, wireless access points and firewalls. It separates steady growth from scheduled spikes, such as a nightly backup window, so forecasts are not skewed. It then forecasts when each resource will reach its capacity threshold. Where one is forecast to saturate inside the planning window, it checks whether the load is scheduled work that could move. If so, it proposes rescheduling. If not, it proposes options such as a link upgrade, traffic balancing or an extra access point, with lead times. It flags wireless areas where client counts regularly exceed what the access points handle well. You approve capacity changes and purchases.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueYes, continueApprovedNoNo 1 STARTS WHEN Weekly capacity check 2 USES A TOOL Collect utilization across links, devices andwireless 3 DOES Separate steady growth from scheduled spikes 4 DOES Forecast time to threshold for each resource 5 CHECKS THE RESULT Is any resource forecast to saturate within thewindow? If not: log a healthy result and wait for next week'sdata. Back to step 2. 6 CHECKS THE RESULT Is the load something other than movable scheduledwork? If not: propose rescheduling the work instead of anupgrade. Back to step 3. 7 DOES Propose upgrade or balancing options with lead times 8 YOU APPROVE Network lead approves capacity changes 9 RESULT Capacity plan or healthy log
Read the steps as a list
  1. Weekly capacity check
  2. Collect utilization across links, devices and wireless
  3. Separate steady growth from scheduled spikes
  4. Forecast time to threshold for each resource
  5. Is any resource forecast to saturate within the window?If not: log a healthy result and wait for next week's data. Back to step 2.
  6. Is the load something other than movable scheduled work?If not: propose rescheduling the work instead of an upgrade. Back to step 3.
  7. Propose upgrade or balancing options with lead times
  8. Network lead approves capacity changesThe agent waits here for your OK.
  9. Capacity plan or healthy log

How it decides

It forecasts from steady growth, excluding scheduled spikes, and recommends action when saturation is forecast within the window.

  • Exclude scheduled spikes from the trend
  • Warn when saturation is within the window
  • Suggest scheduling over upgrade when load is time-bound

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Capacity thresholds
  • Planning window
  • Resources in scope
  • Event schedule to exclude

What keeps you in control

It always asks you first

  • Capacity changes and purchases

Hard limits

  • Does not make network changes itself
  • Bases forecasts on real trends

It stops when

  • Done: capacity healthy or plan approved
  • Stop: utilization history is too short to forecast

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensIn the week of March 18 at Whitfield Schools, the agent forecast the main internet link to hit 90% in 20 days, inside the 30-day window, after excluding backup spikes. The load was daytime traffic, so it proposed a bandwidth upgrade with a 15-day lead time. A branch link busy only during backups was flagged for rescheduling. The network lead approved the upgrade order.

More agents for it managers