Feature Requests
Kyle Bonde - Vertical GC Production - Hard Key Field??
We are kicking around the idea that perhaps production could be placed in the takeoff tool as the source of truth. The problem is its a custom field and feel it would be best for the industry if this was a hard coded field in the tool under labor. (Kind of like how waste is there)
IDK is this is a good idea or not, but figured I'd throw it out there.
Oh dropped this post on Linkedin a couple hours ago that is worth a read. LINK
I like the idea of being able to hide hard coded fields if wanted. Our pricing structure will not work with hard coded fields, so all my pricing structure sits in custom properties. For us, it's not really a problem if its custom or not. Those production values will be set in the template and then modified from the reports. In reports, you can put it wherever you want it, regardless of if it's custom or hard coded.
I'd like to be able to hide all on the item screen except maybe material cost and production:
Our material, production (labor), sub, rent setup:
An example of a duration report driven off specific crew makeup and production rates:
I'm with ya @Kyle, but as @Kory mentioned we all have different styles/requirements to back us into a pre-defined box - even the term (property) SKU drives me nuts when I'm putting a labor type in (poor bro)...
I'm getting where I'm creating MLESO & assembly (or sub-assembly) templates that have the custom properties loaded and when I start building up items I try to make sure to start from that source.
I'm OK with the the minimizing (accordion collapse of headers) for now (snip 1), but sometimes I do wish some of the top headers had a way to minimize (snip 2).
So far, everything seems to stay minimized until I open the headers up. But yes, it would be nice to hide or turn off visibility of even the default properties (like the SKU).
This is where the assembly type is becoming fun because it's a blank slate (snip 3) every time...
Snip 1
Snip 2
Snip 3
Looking tight BTW @Kory on those properties and reporting (I'm approaching/building out a similar style) - thanks for the inspiration/guidance/reinforcement
FWIW, I do see a future of having MLESO & assembly offering to "Save as New Preset" or ""Save as Default" offered, much like QTO types, annotations, highlighters, etc. That way we could save our own styles to fit our situation or as just a default... Maybe???
Can we throw this idea out as a "Feature Request"?
Where the YELLOW =
- Material
- Labor
- Equipment
- Subcontract
- Other
- Assembly