Re: The Future of Stick Enterprises
DavidWS wrote:
bizon wrote:
but even repairs
Where it's the same person doing both new builds & repairs that doesn't seem at all surprising.
If you were waiting for a new instrument would you be impressed if other jobs kept being inserted into the queue ahead of you?
Just a thought...
just thinking out loud here (I haven't done any process control stuff for abt a..eww quarter century now) but maybe single-line FIFO (aka queue) isn't the optimal strategy
perhaps allocating X time for wood, Y time for railboard, Z timefor repairs per cycle (not sure where NS fits in there, but they are poopie heads anyway!!
) and adjusting delivery estimates accordingly would be helpful.
That way expectations are clear, there is a service pathway, but jobs aren't continually being inserted ahead of order
couple of 'soft' thoughts on that
Not sure what the assembly time for railboard is...but I suspect it's significantly lower and I think the blanks are batch processed.
So we may be talking significantly higher throughput for those orders
getting more instruments into more hands
At a 24 month buy in as-is, maybe...MAYBE (unsure)...potential customers would be less sensitive to a push out on longer-production-time units (24 vs 26 or what have you)
There are certainly some social dynamics around some aspects (esp within a community as this).
Baggetthouse, for example, does have another functioning instrument, so perhaps he would be less sensitive to his time in the repair queue.
I, for example, struggle with Chapman stick for personal enrichment (and t o keep the ole noggin neuroplastic. Also find it helps with crippling depression)and have no performance aspirations. I would cede time in the queue for performing musicians and/or those without an instrument.
I suspect it would be too administratively and socially complex to add that as an order option - So I'd think you;'d want to look at the aggregate and do a static allocation).
Aside : Ah, it reminds me of CS where I had this prof who was into replacing stack and queues with sorted lists for control flow. Neat idea and it made for a default best-first instead of depth- or breadth-first scheme, but hilarity could ensue but I digress, just a thought on something that might, merely MIGHT (esp not having any numbers) improve throughput.