This topic contains 7 replies, has 2 voices, and was last updated by AG 5 years, 4 months ago.
March 12, 2010 at 6:45 pm #5602
As you know, we build a lot of sales processes, here at Ballistix. You may not know that we build almost as many customer-service teams, inside-sales
[See the full post at: A quick-and-dirty approach to sales operations process improvement]March 12, 2010 at 7:36 pm #5603
Jeff SKI Kinsey
I was preaching “data” vs. “information” earlier today on LI… don’t forget Step #0: Define the System (as in boundaries, span of control vs. span of influence type definitions).
Great insight as always, with neat graphics.
-skiMarch 13, 2010 at 10:15 am #5604
Thank you Ski. Define the system is a good one. That could subsume Step 1 also (goal and necessary conditions).March 29, 2010 at 9:46 pm #5605
Hi Justin – I'm still trying to understand how the vertical axis works – does each row represent a timeslot?
ChrisMarch 29, 2010 at 9:59 pm #5606
In the Buffer Board pictured, there is no vertical axis. The timespan was too long to fit on the one board, so it zig-zags back and forth!
The section at the top is used to categorize unreleased jobs (scheduled, but not started).
JustinApril 6, 2010 at 2:29 pm #5607
Thanks, that makes alot more sense now!
ChrisNovember 18, 2012 at 11:32 am #5608
On another topic, AG asks:
“Could you explain the buffer board for me a little more and how it works?
Thanks very much. AG”
* * *
The buffer board is a simple scheduling tool. It gets its name from the TOC approach to scheduling, where a constraint is nominated and a buffer of work-in-process is maintained upstream from that resource.
The idea is that, if you schedule the constraint, you effectively schedule the entire process.
The buffer board displays a timeline and jobs are added to the time line x number of days before promised dispatch. ‘x’ is the buffered lead time for that job.
Tickets on the board contain the information that the scheduler needs to assess the on-time performance of each job (checklists that are updated as activities are completed, stickers representing prerequisites that are removed as the prerequisites come in, and so on).
The buffer size is calculated to enable necessary maneuvering (expediting) without damaging on-time performance.
Hope that helps!
JustinNovember 20, 2012 at 1:30 pm #5651
Thank you Justin.