Flow metrics: Difference between revisions
No edit summary |
No edit summary |
||
| Line 53: | Line 53: | ||
* Improved throughput often requires balancing effectiveness and reliability | * Improved throughput often requires balancing effectiveness and reliability | ||
= See Also = | |||
Other related terms that might be of interest: | Other related terms that might be of interest: | ||
* Theory of Constraints | * Theory of Constraints | ||
| Line 59: | Line 59: | ||
* Performance Measurement Systems | * Performance Measurement Systems | ||
= Further reading = | |||
* [https://flowchainsensei.wordpress.com/2018/03/06/reliability-and-effectiveness/ Effectiveness Framework, Bob Marshall] | |||
* [https://www.amazon.nl/-/en/Eliyahu-M-Goldratt/dp/0884271951 The Goal, Eliyahu M Goldratt] | * [https://www.amazon.nl/-/en/Eliyahu-M-Goldratt/dp/0884271951 The Goal, Eliyahu M Goldratt] | ||
* [https://www.amazon.nl/-/en/Eliyahu-M-Goldratt/dp/0884271668 Theory of Constraint, Eliyahu M Goldratt] | * [https://www.amazon.nl/-/en/Eliyahu-M-Goldratt/dp/0884271668 Theory of Constraint, Eliyahu M Goldratt] | ||
* Beyond the Goal | * [https://www.amazon.com/Beyond-Goal-Eliyahu-M-Goldratt-audiobook/dp/B000ELJ9NO Beyond the Goal, Eliyahu M Goldratt] | ||
Revision as of 06:13, 3 February 2025
Key Performance Metrics at Delft Solutions
Delft Solutions utilizes three fundamental metrics to measure and improve business performance: Effectiveness, Reliability, and Throughput. These metrics work in concert to provide a comprehensive view of operational excellence.
Effectiveness
Effectiveness measures actions that should not have been done but were nevertheless performed. That can be a little hard to grasp because "should not have been done" usually means "should not have been done YET". Essentially, it's work we could have done later but didn't.
Effectiveness doesn't measure overpolishing (work that is being done too well, compared to what we or the customers need), but WIP: work in progress. Work that has been completed; is ready to be delivered to the customer, but it hasn't been delivered yet.
Inventory-Dollar-Days (IDD) Effectiveness is calculated in Inventory Dollar-Days.
- Calculated as: Dollar value of inventory × Number of days held
- Example: If $100,000 worth of products sits in warehouse for 30 days, this creates 3,000,000 inventory-dollar-days
- Lower IDD indicates higher effectiveness. The ultimate goal would be 0.
Quality Impact
We don't measure quality separately from Effectiveness. Quality is inherently integrated into effectiveness measurements:
- Sales are only recognized after customer acceptance.
- Inventory reductions are only counted once items are deployed to production.
Reliability
Reliability measures commitments fulfilled to the external world, particularly focusing on timely delivery.
Throughput-Dollar-Days (TDD)
- Calculated as: Value of late orders × Number of days late
- Example: A $50,000 order delivered 5 days late results in 250,000 throughput-dollar-days
- Lower TDD indicates higher reliability
Key Characteristics
- Incorporates both time and monetary value
- Provides more meaningful insights than simple percentage-based metrics
- Encourages focus on high-value customer commitments
Throughput
Throughput represents the rate at which the system generates goal units (typically money) through sales.
Key Components
- Revenue from sales
- Variable costs directly associated with production
- Rate of conversion from input to output
Measurement Examples
- Units produced per time period
- Revenue generated per day
- Orders completed per week
Relationship Between Metrics
These three metrics are interconnected:
- High effectiveness (low IDD) supports better throughput by reducing waste
- Strong reliability (low TDD) enables consistent throughput
- Improved throughput often requires balancing effectiveness and reliability
See Also
Other related terms that might be of interest:
- Theory of Constraints
- Operational Excellence
- Performance Measurement Systems