If one can fairly clearly define what it means for project to be active vs. inactive/stagnant/parked, the following ideas may offer a solution. Of course there also needs to be a way to administer whatever solution is selected. The general idea is a per-project storage space pricing structure that is tiered over time. This would be a way to address the concern that was raised about stagnant projects.
Here are two models based on the following criteria:
-members should get some project space included as a member benefit.
-space has a measurable value, especially if it is in short supply.
-project churn is desired, with 6 months as the default limit per project.
-the model should not (strongly) favor smaller, long term projects (small, slow churn) at the expense of bigger but rapid projects (big, but rapid churn). Fairness is needed between them.
-the goal is to maximize the number of completed projects per unit of space per unit of time.
This first model does encourage smaller projects, with a bit of a drag on larger projects. Any that run over time limit quickly start to become expensive.
The numbers below assign a value to square footage with a goal of encouraging project churn as well as smaller projects. The prices are simply placeholders. They aren't based on anything. (FWIW, last I looked, mini storage lockers are in $1-$2/sf/month range in the Twin Cities.)
Month, Fee per unit of storage space (e.g. square foot of floor or cubic foot)
1st month, first 10sf free, $0.10/sf above 10.
2nd month, first 10sf free, $0.10/sf above 10.
3rd month, ""
4th month, ""
5th month, ""
6th month, ""
7th month, $0.10/sf for all space.
8th month, $0.25/sf for all space.
9th month, $0.50/sf for all space.
Etc, or something similar.
Or just add $0.10/sf every additional month beyond 6 until project is completed/removed/deemed abandoned.
Second model:
This is meant to properly balance (small, slow churn) and bigger but rapid projects (big, but rapid churn) and everything in between like growing projects. This uses the concept of a Space-Month Unit, which is just a certain amount of space that is held for a month. Each member gets a certain amount of Space-Month Units (SMU) for each project they are working on.
Assuming 10 sf for an average project, with a 6 month limit, each project thus gets 10*6=60 SMU by default. (Members may also request approval for more than 60 SMU for a project if they can justify the request.)
(Note: It may or may not be necessary to define a limit on simultaneous projects. This might be a membership-level thing or a permission request/grant thing, based on current space demands.
Process:
Member starts a new project (fills out project info form).
Member is granted 60 SMU for project. This is written on project form.
Member begins project.
At end of month, amount of space (floor s.f. or volume c.f.) currently consumed by project is deducted from remaining SMU for that project. (Presumably any member can view/record this info when each recording interval comes up. Auditing is via peers as needed.) When remaining SMU balance reaches zero, project now incurs idling fees for each additional month it is present.
Example of what could be written on project sheet for a 10 sf project.
Time 0: 60 SMU allocated
End of month 1: 10 sf used, deduct 10 SMU, 50 SMU remaining
End of month 2: 10 sf used, deduct 10 SMU, 40 SMU remaining
End of month 3: 10 sf used, deduct 10 SMU, 30 SMU remaining
End of month 4: 10 sf used, deduct 10 SMU, 20 SMU remaining
End of month 5: 10 sf used, deduct 10 SMU, 10 SMU remaining
End of month 6: 10 sf used, deduct 10 SMU, 0 SMU remaining
End of month 7: 10 sf used, 0 SMU balance, apply fee of $0.10/sf
End of month 8: 10 sf used, 0 SMU balance, apply fee of $0.25/sf
End of month 9: 10 sf used, 0 SMU balance, apply fee of $0.50/sf
Example of what could be written on project sheet for a bigger 30 sf project.
Time 0: 60 SMU allocated
End of month 1: 30 sf used, deduct 30 SMU, 30 SMU remaining
End of month 2: 30 sf used, deduct 30 SMU, 0 SMU remaining
End of month 3: 30 sf used, 0 SMU balance, apply fee of $0.10/sf
End of month 4: 30 sf used, 0 SMU balance, apply fee of $0.25/sf
End of month 5: 30 sf used, 0 SMU balance, apply fee of $0.50/sf
Continue escalating until project is completed/removed/deemed abandoned.
The second model is fairer and easier to administer in that it can be handled right on a project sheet. Time extensions would be granted by issuing additional SMUs to a project. Those SMUs would come from SMUs that would have otherwise been granted to new projects.
Total SMUs possible depend on amount of space available for project storage. If there are 1000 square feet in the building for project storage, per the definition of 1 SMU per square foot per month, that is up to 1000 new SMUs that can be issued to projects each month. 1000/60=16.7 simultaneous 60 sf big quick projects done each month. Or 1000/10=100 smaller 10 sf projects done each month. Or a mix. Projects that were overtime and incurring fees or had been granted extensions would reduce the SMUs available for issuing to new projects.
To unsubscribe from this group and stop receiving emails from it, send an email to tcmaker+u...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to tcmaker+unsubscribe@googlegroups.com.
The thought of the discretion of the management is that it depends on the size of the item, if we are talking about a car, truck, camper, art-house/shanty, etc type large item, sure we will want a deposit. If it’s a medium sized item like a dresser, Tardis, cement 3d printer. That probably won’t need a deposit.
So by “Large Item” we mean something that will either occupy a parking spot, or excessive amount of ground/floor space at or in the shop.
It’s not based on the item, or the person, it would be based solely on the size. To your point, We should define in more detail what items will require a deposit, ie any item that exceeds any of the following dimensions (HxWxL) or be stored outside, will require a deposit.
The change in the rules is that space will be allocated on a first come first serve request basis. Not first come first serve as in the shelfs empty and I’m claiming it forever as I was here first.
Example: (assumes shelves are all allocated and requests are processed as received)
User A requests a space to store an item to begin oct 15th for 30 days and is granted Shelf A1.
User B requests a space on Oct 30th, to start November 16th for 30 days, and the only shelf that will be available starting then is A1, User B is granted shelf A1 for November 16th through December 16th.
User A then requests an extension of shelf on Nov 1 but is told that the shelf is not available, but shelf B5 will be available on November 27th and can have that shelf for 30 days. User A must remove his stored item on shelf A1 on Nov 15th, but can bring it back and put it on shelf B5 on November 27th.
I believe we can do this with a database fairly easily, or even with a Spreadsheet until we can come up with an app to manage it.
--
As for your projects, we didn't even get to member storage on cleanup.