Skip to main content
Question

Capacity/bandwidth planning?

  • October 14, 2020
  • 0 replies
  • 91 views

Hi all,

Just wondering whether anyone has used their Quickbase apps for team bandwidth/capacity planning? I just can't picture how I need to build this despite knowing what I need.

The use case
We have a team of 3 roles, each role has a slightly different capacity in points, and each project has a number of points classification.


Has anyone done anything like this before or used any sample apps which approach this process well?

Thanks
Michael
edit - added screenshot of table as previously added copy and paste from Google Sheets and it didn't show up!
This topic has been closed for replies.

Michael -

Are you looking to do something that is very broad and just really looks at a Person's standard bandwidth allocation vs their current workload assignment? (Ex: Joan can handle 6 Projects and she's currently working on 4, so she's at 67% of her Capacity)
OR
Do you need to get much more in depth where you might take into consideration that person's actual daily schedule, PTO, Holidays, etc? (Ex: Joan works 10 hrs/day, 4 days a week, but is on vacation the 3rd - 10th....etc., etc., etc.)


------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
Forum|alt.badge.img+1

I have something like this in my main app, a summary report predominantly displayed on the homepage so managers and people on the same team have basic visibility to each other's workload.

First I made a table called "User Details" to store our team member data. Which team they are on, work location, role, capacities, and of course a "User" field where I select the appropriate Quickbase user. (Notes field is also handy, I log why obscure users have access to our app.)

When I make a user drop down in another table (like the Projects table), I make a relationship to the User Details table and use it to select the project member instead of just adding a basic "User" field type. This way I can pull over other data about the project member and can also get fancy, like filtering the list so that the field only shows certain types of users. (I also went and added this to existing tables, used import/export to copy over the username data from the old basic User field.)

Then back at the User Details table I add a summary field that counts their number of active items in each relationship (such as projects.)

You could setup this basic relationship counting projects, then add project levels with a points system to your Projects table and bring it over to the User Details table as an additional summary field. Finally, make a formula field to compare it to capacity and a summary report to display this data.



------------------------------
Jen Hamilton
------------------------------
Terms & ConditionsAccessibility statement