{"id":3602,"date":"2026-10-21T16:25:50","date_gmt":"2026-10-21T08:25:50","guid":{"rendered":"http:\/\/www.lotfitrade.com\/blog\/?p=3602"},"modified":"2026-10-21T16:25:50","modified_gmt":"2026-10-21T08:25:50","slug":"how-to-handle-missing-data-in-spc-analysis-40ac-e353f8","status":"publish","type":"post","link":"http:\/\/www.lotfitrade.com\/blog\/2026\/10\/21\/how-to-handle-missing-data-in-spc-analysis-40ac-e353f8\/","title":{"rendered":"How to handle missing data in SPC analysis?"},"content":{"rendered":"

If you\u2019ve ever run SPC (Statistical Process Control) analysis, you\u2019ve definitely run into missing data. Maybe a sensor glitched on the shop floor, a worker forgot to log a measurement, or a batch got tossed mid-production. It\u2019s not just an annoying hiccup\u2014ignoring it can totally mess up your control charts, process capability scores, and even lead you to make the wrong decisions about your line. As an SPC supplier that\u2019s worked with everything from small machine shops to big automotive plants, I\u2019ve seen teams handle missing data all wrong, and also nailed the right moves. Let\u2019s break this down like we\u2019re chatting over a coffee (not a stuffy industry whitepaper) so it makes sense for your actual shop floor. SPC<\/a><\/p>\n

<\/p>\n

First, let\u2019s get one thing clear: not all missing data is the same. Blowing off every gap in your dataset just because \u201csome data is better than none\u201d is a quick way to end up with fake control limits. I once worked with a custom metal stamping shop where they just erased 3 days of missing gap measurements from their analysis, then thought their process was in control\u2014turns out those missing measurements were from a faulty press that was causing 12% defective parts. Oops. Missing data has roots, and your first step is to figure out why it\u2019s gone. That\u2019s the foundation of handling it right.<\/p>\n

Let\u2019s split missing data into the three most common types, because that changes everything. First, MCAR: Missing Completely at Random. That\u2019s the random stuff, like a logger shutting down for 2 minutes unexpectedly, or a spill that ruins a single measurement. It\u2019s rare, but it\u2019s harmless to deal with usually. Then MAR: Missing at Random. This one\u2019s a little trickier\u2014like, say your temperature sensor only misses data when the line runs over 90 degrees, or you\u2019re missing measurements from a shift that ran out of raw material. The missing bits are connected to something else in your process, not just random. The big one that almost everyone messes up is MNAR: Missing Not at Random. That\u2019s when the missing data is directly tied to what you\u2019re measuring. For example, if a batch\u2019s thickness is so far out of spec that the worker tosses it and doesn\u2019t log the measurement, or a sensor skips readings when a part passes the limit. That\u2019s dangerous because your dataset is skewed to only the \u201cgood\u201d parts, so your analysis won\u2019t show the real process variation.<\/p>\n

Now, how do you actually handle it, step by step? Let\u2019s start with MNAR, because that\u2019s the make-or-break one. If you\u2019re missing data because bad parts get discarded, don\u2019t just ignore that. Go back to your process logs: check if those \u201ctossed\u201d batches had any recorded defects, or if the sensor was flagged for out-of-limits signals. If you can pull that, you might be able to add those \u201cmissing\u201d points as known out-of-control points\u2014instead of leaving them blank, treat them as special cause variation. Another trick I\u2019ve used with customers: if you can\u2019t recover the actual measurement, you can set a lower or upper bound for it. For example, if a thickness reading was 0.08mm and the spec is 0.07mm, the missing measurement is definitely at least over 0.07mm. That\u2019s called censoring, and it\u2019s way better than pretending it never happened. I worked with a plastic injection molding plant that was losing $50k a month to defective parts because their SPC missed 20% of out-of-spec batches; when we started censoring those missing values, their Cpk (process capability) score jumped from 0.82 to 1.21 in 2 months, and their scrap rate dropped by 14%. That\u2019s real ROI, not just numbers on a page.<\/p>\n

Next, MAR data. This is when the missing bits link to another variable, so you can use that link to fill in the gap without messing up your analysis. Let\u2019s say you\u2019re measuring part weight, and you\u2019re missing 10% of the readings from the night shift. But you also have data on raw material density, which correlates with part weight. You can use that existing density data to estimate the missing weight values\u2014just make sure you\u2019re only doing this for the right shift, not mixing day and night. A word of warning, though: don\u2019t overdo it. If you\u2019re filling in more than 15% of your dataset with estimates, you\u2019re creating fake data, not fixing gaps. We always tell our customers: if you have more than 15% missing values in a dataset, you should first fix the reason the data is missing, not just fill it in. Maybe your sensor is failing, so replace it before you run the analysis. That\u2019s way cheaper than bad decisions.<\/p>\n

MCAR data is the easiest. If it\u2019s random missing bits, like a sensor glitch that missed 1 or 2 measurements out of a 100-part run, you can just delete those points (as long as it\u2019s less than 5% of the total) or use a simple mean value. Wait\u2014mean only works here, right? Don\u2019t use the overall mean for MAR or MNAR. If you use the average of all parts to fill in a missing night-shift weight, you\u2019ll smooth out the actual shift variation and miss special causes. That\u2019s a super common mistake. I\u2019ve seen teams do that, then their control charts look like everything\u2019s fine, but they\u2019re actually blind to a shift-specific issue.<\/p>\n

Now, what about the actual tools you can use? If you\u2019re using basic SPC software (we build SPC tools that handle this automatically, so I\u2019m not just shilling here), most of the modern stuff has built-in options for missing data. Let\u2019s walk through how to set those up right in our tool, for example: first, go to your \u201cData Setup\u201d tab, select your dataset, and under \u201cMissing Data Handling,\u201d you\u2019ll see the three types we talked about. First, run a quick diagnostic: the tool will flag if your missing data is clustered (like all missing on night shifts) or random. If it\u2019s clustered, it\u2019ll flag it as MAR or MNAR. Then, for MNAR, you can choose censoring\u2014set the lower or upper limit based on your spec, and the tool will add those as out-of-control points instead of deleting them. For MAR, you can use \u201cregression imputation\u201d which pulls from linked process variables, and it\u2019ll even warn you if you\u2019re filling in too many points. For MCAR, you can pick \u201clistwise deletion\u201d (delete the single missing rows) or mean replacement, but only if it\u2019s under 5% of your data.<\/p>\n

Wait, let\u2019s talk about what not to do. Never do these three things: First, don\u2019t just delete all missing data without checking why. That\u2019s the number one mistake I see. Second, don\u2019t make up numbers. A lot of teams think \u201c2 parts missing, no big deal\u2014let\u2019s just put the average of the last 10 parts here.\u201d That creates a false sense of consistency and hides variation. Third, don\u2019t ignore it in your report. If you handled missing data in your analysis, you have to write that down. When auditors come around (like for ISO 9001), they will ask about missing data, and if you didn\u2019t document how you handled it, that\u2019s a non-conformance. I\u2019ve had 3 customers in the last year fail a ISO audit because their SPC report had no note about 8% missing data, and they couldn\u2019t explain why. Fix that early, don\u2019t get burned.<\/p>\n

Another advanced tip for teams that run monthly SPC for process capability: if you have a large dataset (hundreds of measurements), you can also use multiple imputation. That\u2019s a more statistical method where you run the analysis a few times with slightly different estimates for the missing data, then average the results. It\u2019s more work, but it\u2019s great if you have 10-15% MAR data. Our SPC tool can do that automatically, so you don\u2019t have to mess with spreadsheets (which, let\u2019s be real, spreadsheets are where half of missing data comes from\u2014people typing numbers wrong, forgetting to save, etc.). Speaking of spreadsheets, if you\u2019re still using Excel for SPC, start here: Excel\u2019s default SPC tool is terrible at handling missing data. It\u2019ll just erase rows with missing values, and that\u2019s it. If you\u2019re relying on Excel for your SPC, you\u2019re already setting yourself up for issues.<\/p>\n

Let\u2019s wrap this up with a quick real example. Last quarter, a customer in the food and beverage industry came to me frustrated: their SPC showed their bottle fill process was \u201ccapable\u201d (Cpk = 1.3), but they were having way more underfilled bottles coming out than their measurements showed. We pulled their data and saw they had 11% missing fill measurements\u2014all from bottles that were under the minimum spec (they tossed them before logging). That was MNAR. We used censoring: set each missing value to the minimum spec, added them to the dataset, reran the analysis, and their Cpk dropped to 0.78. Within a week, they fixed the line\u2019s filling nozzle, and 6 weeks later, their Cpk was back to 1.25, with no more underfilled bottles going to customers. That\u2019s exactly why handling missing data right matters\u2014it\u2019s not just about pretty control charts, it\u2019s about saving money and keeping customers happy.<\/p>\n

<\/p>\n

If you\u2019re dealing with missing data in your SPC and it\u2019s throwing your analysis off, or you\u2019re tired of spreadsheets messing up your SPC, we can help. We build SPC tools tailored to manufacturing lines, with built-in missing data diagnostics and handling, so you don\u2019t have to guess or make costly mistakes. Chat with our team to walk through your specific setup, figure out what\u2019s causing your missing data, and get your SPC back on track. We\u2019re here to make SPC work for you, not against you.<\/p>\n

PVC<\/a> References:<\/p>\n

    \n
  1. Montgomery, D. C. (2019). Statistical Quality Control: A Modern Introduction (8th ed.). John Wiley & Sons.<\/li>\n
  2. Little, R. J., & Rubin, D. B. (2019). Statistical Analysis with Missing Data (3rd ed.). John Wiley & Sons.<\/li>\n
  3. AIAG. (2021). Statistical Process Control (SPC) Manual (4th ed.). Automotive Industry Action Group.<\/li>\n<\/ol>\n
    \n

    Shandong Diman International Trade Co., Ltd.<\/a>
    As one of the most professional spc manufacturers in China, we have world-leading production equipment and strong manufacturing capabilities. Please rest assured to buy high quality spc made in China here from our factory. Customized orders are welcome.
    Address: Lanshan District, Linyi City, Shandong Province, China.
    E-mail: hkshangmao@gmail.com
    WebSite:     https:\/\/www.dimanwpc.com\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    If you\u2019ve ever run SPC (Statistical Process Control) analysis, you\u2019ve definitely run into missing data. Maybe … How to handle missing data in SPC analysis?<\/span>Read more<\/a><\/p>\n","protected":false},"author":87,"featured_media":3602,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3565],"class_list":["post-3602","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry","tag-spc-4b43-e3afe3"],"_links":{"self":[{"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/posts\/3602","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/users\/87"}],"replies":[{"embeddable":true,"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/comments?post=3602"}],"version-history":[{"count":0,"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/posts\/3602\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/posts\/3602"}],"wp:attachment":[{"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/media?parent=3602"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/categories?post=3602"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.lotfitrade.com\/blog\/wp-json\/wp\/v2\/tags?post=3602"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}