Formula sheet
Operations and Reliability Formula Sheet
Operations and reliability formulas for critical path timing, Little's Law, capacity, yield, inventory, RPN, MTBF, availability, Weibull models, and validation.
This formula sheet collects common first-pass relationships for operations planning, project control, capacity analysis, risk ranking, reliability engineering, and validation review. Use it for screening and consistency checks. Detailed decisions still require clear assumptions, data quality review, confidence bounds, and context-specific acceptance criteria.
State the system boundary, time basis, failure definition, resource assumptions, and data source before using any metric.
Reliability data normalization
Failure rate from observed failures and exposure:
Mean time between failures from exposure-normalized data:
Mean time to repair:
Repair rate:
Do not mix calendar time, operating time, cycles, starts, or distance without stating the exposure basis. A failure count without exposure is not a reliability metric.
Critical path timing
Activity duration:
where ES is earliest start and EF is earliest finish.
Forward pass:
Backward pass:
Total float:
Activities with zero or near-zero total float are critical under the current schedule logic.
Project duration and path length
Path duration:
Critical path duration:
Schedule variance from baseline:
The critical path is valid only if the dependency network, calendars, constraints, and resource assumptions are valid.
Little’s Law
Little’s Law:
where L is average number of items in the system, \lambda is throughput or arrival rate, and W is average time in the system.
Lead time from work-in-process:
Throughput from WIP and lead time:
Little’s Law applies to stable systems using consistent definitions of system boundary, throughput, and time.
Utilization
Single-server utilization:
For c parallel identical servers:
where \lambda is arrival rate and \mu is service rate per server.
Stable operation requires:
High utilization can cause large waiting times when variability is present.
Capacity and takt checks
Cycle time:
Takt time:
Capacity:
A process can meet demand only if effective capacity exceeds demand after downtime, yield loss, setup, rework, and variability are included.
Effective capacity and OEE
Operating availability:
Performance factor:
Overall equipment effectiveness:
Effective capacity:
Use the same boundary for planned time, downtime, speed loss, scrap, rework, and changeover before comparing OEE across lines or sites.
Yield and rework
First-pass yield:
Rolled throughput yield for sequential steps:
Scrap rate:
Rework can hide process weakness because final yield may look acceptable while time, cost, and capacity are consumed.
Inventory and reorder screening
Reorder point:
where d is average demand rate, L is replenishment lead time, and SS is safety stock.
Safety stock for normal lead-time demand:
Economic order quantity:
where D is annual demand, S is ordering cost per order, and H is annual holding cost per unit.
Inventory turns:
Inventory formulas should be checked against demand variability, supplier reliability, batch constraints, shelf life, obsolescence, and service-level targets.
Risk Priority Number
Traditional FMEA risk priority number:
where S is severity, O is occurrence, and D is detection ranking.
Residual RPN after action:
RPN uses ordinal rankings. It should guide discussion and prioritization, not be treated as a physical measure of absolute risk.
Reliability
Reliability function:
For constant failure rate:
Failure probability by time t:
Mean time between failures for a constant failure rate:
The exponential model is not appropriate for wear-out, fatigue, corrosion, infant mortality, or mixed failure populations without justification.
Availability
For a repairable system with mean time between failures and mean time to repair:
Downtime fraction:
Expected downtime over operating time T:
Availability depends on diagnostics, access, spare parts, repair skill, logistics, and restoration quality.
Mini example: availability
For:
and:
availability is:
Expected downtime in 2000 operating hours is:
For three required independent assets in series, each with availability 0.990:
This screen assumes independence, stable repair process, and representative MTBF and MTTR data.
Series and parallel reliability
Series system reliability for independent components:
Two independent parallel paths:
For identical independent parallel components:
These formulas assume independence. Common-cause failures, shared power, shared environment, shared software, and maintenance errors can invalidate simple redundancy claims.
Weibull reliability
Weibull reliability:
Failure distribution:
Failure rate:
Interpretation:
Weibull models require appropriate life data, censoring treatment, and confidence bounds.
Validation metrics
Mean error:
Mean absolute error:
Root-mean-square error:
Pass rate:
Validation metrics must be matched to intended use, risk, reference uncertainty, and acceptance criteria.
Confidence and uncertainty
Sample mean:
Sample standard deviation:
Standard error of the mean:
Combined independent uncertainty:
Do not treat systematic bias, missing data, or model-form error as random variation without justification.
Monte Carlo schedule or risk simulation
For uncertain inputs:
Sample each trial:
Estimate probability of meeting a target:
Monte Carlo results depend on input distributions, correlations, truncation limits, and model logic.
Pareto and improvement priority
Cumulative fraction for ranked causes:
Benefit-cost ratio:
Expected value:
Use these as decision aids. Safety, compliance, severity, strategic value, and uncertainty may override simple economic ranking.
Validation record
For operations and reliability calculations, record:
- boundary, time basis, exposure unit, and failure definition;
- data source, censoring rules, missing-data treatment, and confidence bounds;
- whether failures are independent, repairable, recurring, or common-cause;
- assumptions for demand, downtime, setup, rework, repair time, and supplier lead time;
- acceptance criteria for schedule, capacity, availability, reliability, or validation error;
- owner and action when a metric crosses its trigger threshold.
The metric is useful only when it changes a planning, maintenance, quality, or design decision.
Practical checklist
Use these formulas with a short review checklist:
- Define boundary, time basis, resource assumptions, and data source.
- Check schedule logic before trusting float or critical path.
- Separate average demand, peak demand, variability, downtime, and rework.
- Treat RPN as prioritization, not proof of safety.
- Match reliability model to the failure mechanism and mission time.
- Include confidence bounds and uncertainty where data are sparse.
- Validate controls with evidence tied to the actual failure mode.
The calculations support engineering judgement. They do not replace clear scope, field data, operating feedback, or cross-functional review.