What is CUE Frame Work & What it is not
CUE stands for Capacity Utilization Efficiency. CUE Framework is to measure operational efficiency. of any deployed system. The framework is similar to the "ROI" ( Return On Investment ) concept used in business process. However, CUE framework does not include business aspect ( financial value or viability ) by design. The reasoning behind is that the framework assumes that the operation it is being used to measure is already business viable. Thus CUE is not a business validation tool.
The framework does not cover the remedy part as well. The scope of the framework encompasses only monitoring and measuring operational efficiency. Plan of action to be derived based on the measurement is subject to the context and left to the users.
Fundamentals of CUE Framework
Example for CUE measurement
In this case, the utilization efficiency factor for book-shelf is 150/1000 = 0.15 or 15%
( In a conventional method, utilization factor will be considered to be 80% based on the number of books placed in the shelf. However, given that only 150 books are used by readers, 650 books are not being utilized. So these books will not be considered for service utilization. )
Postulates :
1. CUE Framework is generic to any kind of operation. The application of the framework is the choice of the user in given context and chosen KPI.5. One important factor that influences "CUE" externally is "service availability".
Service Availability = Actual availability of services provided by Deployed Capacity / Required availability of services provided
6. Though "CUE" framework atomically represents a snapshot of given instance, for effective use of the framework, the values should be captured continually on stipulated time intervals. Thus time becomes an important factor.
This is applicable when the system is in the "launch" phase. The service utilization is expected to increase gradually though the initial capacity deployed remains unchanged. ( eg. a metro rail segment is newly launched )
Implication => The capacity deployed should be modularized in a way that the deployment of additional capacity can be as minimum incremental as possible so that the curve for Ut to reach its maximum for the given capacity is minimal.
Scenario 2: If Ut is constant during the given time interval, CUE is inversely proportional to Ct.
This is applicable when the system is in a "stable" state with the level of service utilization reaching its maximum value. ( eg. a metro rail segment is reasonably stabilized )
Implication => This stage demands further optimization resulting in a change (reduction) in deployed capacity for further improvement of CUE.
Scenario 3: If both Ut and Ct are varying continually, then CUE is dependent on both Ut and Ct.
This is applicable when the system is in a dynamic state continually. ( eg. peak and off-peak hours of metro rail segments )
Implication => To achieve the higher CUE , it requires
a) the predictability of Utilization variation
7. While addressing the above scenarios, an important parameter to be taken into consideration is the Service Availability. Service Utilization for minor intervals within given interval period should be observed and analyzed. Below measures will be of interest in respective aspects.
a) Minimum Service Utilization -> Guarantees Service Availability
b) Maximum Service Utilization -> Risk to service availability
c) Mode of Service Utilization -> Most likely scenario for service availability
d) Mean of Service Utilization -> Serves as a directional measure for CUE within the minor interval. ( if the difference between Minimum and Mean is very high, CUE will become low.