A capability number depends on its assumptions. Instability, skewed data or an invented lower specification can invalidate a conventional two-sided normal interpretation. Investigate special causes first and choose an appropriate model for the actual requirement. Keep unusual values unless an investigation justifies exclusion. An upper-only requirement does not imply a lower specification at zero.
You work with original records from fictional operations teams. Start by checking what each column means and which cases belong in the denominator. A precise calculation can still answer the wrong business question if the population or time boundary changes. Use the worksheet to leave an audit trail: preserve the inputs, record the intermediate outputs and check the stated exception. The transfer case uses new data so you must apply the method again.
Recognize when a conventional normal capability index is unsupported.