2018 PHM Data Challenge

A dataset shared by Kai Goebel, updated on Dec 10, 2018

Summary

resource_image

This data set examines the fault behavior of an ion mill etch tool used in a wafer manufacturing process (see references at the end of this document). The process of ion mill etching typically consists of the following steps:

  1. Inserting a wafer into the mill
  2. Configure wafer settings (rotation speed, angles, beam current / voltages, etc.)
  3. Processing the wafer for a set amount of time
  4. Repeat 2 or 3 for different steps of recipe
  5. Remove wafer from mill

An ion source generates ions that are accelerated through an electric field using a series of grids set at specific voltages. This creates an ion beam that travels and eventually strikes the wafer surface. Material is removed from the wafer when ions hit the wafer surface. The wafer is placed on a rotating fixture that can be tilted at different angles facing the incoming ion beam. The wafer can be shielded from the ion beam until ready for milling operation to commence using a shutter mechanism as shown in Figure 2. A Particle Beam Neutralizer (PBN) control system influences the ion beam shape / ion distribution as it travels to the wafer surface.

The wafer is cooled by a helium / water system called flowcool. The cooling system passes helium gas behind the wafer at a specified flow rate. The helium gas is indirectly cooled by a water system. The wafer and fixture o-ring separates the flowcool gas from the ion mill vacuum chamber.

Many different failure mechanisms can be present in this system including leaks between flowcool and ion mill chambers, electric grid wear, ion chamber wear, etc. It would be beneficial to predict where and when these failures occur and schedule downtime of these ion mills for maintenance operations.

The objective of this data challenge is to build a model from time series sensor data collected from various ion mill etching tools operating under various conditions and settings.

  1. Diagnose failures (i.e. detect and identify)
  2. Determine time remaining until next failure (i.e. predict remaining useful life)

Predictions of time-to-failure at a specific time should only use time-series data from current and past times. In other words, do not try to predict the point of failure first and then backtrack through time to determine time-to-failure predictions.

show more info
Operating System
N/A (edit)
License
N/A (edit)
Programming Language
N/A (edit)
Version
N/A (edit)

Source Files

01_M02_DC_test.csv
testdata1
40.9 MB 0 downloads
02_M02_DC_test.csv
testdata2
42.0 MB 0 downloads
03_M01_DC_test.csv
testdata3
33.5 MB 0 downloads
04_M01_DC_test.csv
testdata4
21.1 MB 0 downloads
06_M01_DC_test.csv
testdata5
26.0 MB 0 downloads
06_M01_DC_score.csv
validationdata5
430.7 MB 0 downloads
03_M01_DC_score.csv
validationdata3
385.1 MB 0 downloads
02_M02_DC_score.csv
validationdata2
473.7 MB 0 downloads
01_M02_DC_groundtruth.csv
groundtruth1
31.6 MB 0 downloads
02_M02_DC_groundtruth.csv
groundtruth2
22.0 MB 0 downloads
03_M01_DC_groundtruth.csv
groundtruth3
33.2 MB 0 downloads
04_M01_DC_groundtruth.csv
groundtruth4
19.4 MB 0 downloads
06_M01_DC_groundtruth.csv
groundtruth5
19.5 MB 0 downloads
test_website_code.zip
test_website_code
24.8 MB 0 downloads
validation_website_code.zip
validation_website_code
18.8 MB 0 downloads
04_M01_DC_score.csv
validationdata4
573.5 MB 0 downloads
01_M02_DC_score.csv
validationdata1
585.0 MB 0 downloads

Support/Documentation

For any questions, contact this resource's administrator: NDC-kgoebel

Discussions

Add New Comment