What does an equipment vendor's field service engineer (FSE) do?

A field service engineer, or FSE, is an equipment vendor's engineer who works inside a customer's chip fab. A chip fab buys its tools from equipment vendors, and the vendor sends engineers to the customer's fab to look after the tools it sold: installing them, checking them out, maintaining them, fixing them when they break, and teaching the customer's engineers how to maintain them and what to do first when something goes wrong. They work for the vendor, but the place they go to work every day is the customer's fab.

Think of the big copier in an office. The office manager looks after it every day and decides when it can be stopped for repair; the copier company's technician comes to service it, fix the big problems and replace the big parts. The fab's own equipment engineer is like the office manager, and the field service engineer is like the technician.

Why do the vendor's people look after the tools?

Chip fabs don't build their own tools. Etch tools, lithography scanners and thin-film tools are all bought from companies that specialize in making them (see "What does each part of the semiconductor supply chain do?"). The people who know best how a tool is designed and which revision of a part it needs are the people who made it. The vendor has the maker's design documents, service manuals and parts warehouses, and when the engineer on site can't solve something, they can bring in experts at headquarters who know the design.

So the fab's contracts with the vendor often say who installs the tool, who maintains it, and how soon someone has to arrive when it breaks.

How is the work split with the fab's own equipment engineers?

For what the fab's equipment engineers do every day, see "What does an equipment engineer do in a chip fab?". A common way to split the work:

	Fab's equipment engineer	Vendor's field service engineer
Works for	The fab	The vendor that sold the tool
Which tools	Many tools in one area, sometimes from more than one vendor	The few tools their company sold
Day to day	Scheduled maintenance, handling alarms, deciding when a tool stops	Installing, checking out, major maintenance, big repairs, key parts
What they have	This tool's maintenance schedule and history	The tool's design documents, the maker's parts and experts

When a tool stops, the lots behind it have to wait, so the fab schedules when a tool stops for maintenance (see "What is PM (preventive maintenance), and why do fab tools stop on a schedule?"). After a repair, it's also the fab's people who confirm the tool can go back to production. How the work is really split depends on the contract: some fabs do almost all the maintenance themselves and call the vendor only for big problems; others hand the whole tool's maintenance to the vendor.

A new tool, from arrival to signed acceptance

For how a whole fab is built, see "What does it take to build a chip fab?". Here we follow just one new tool, step by step.

Step 1: Move it in

• What: the crates are opened outside the cleanroom, each section of the tool is wiped clean, and it is pushed in through two doors that never open at the same time.
• Why: dust from outside would come in with the tool.
• If not: the cleanroom gets dirty, and the tools nearby are affected too.

Step 2: Hook it up

• What: once the tool is in place, Facilities connects water, power, gases and exhaust line by line from a connection list. This is the hook-up. New gas lines get a pressure test and a leak check (see "What does a fab facilities engineer do?"). The field service engineer stands by and checks every connection.
• Why: water, power and gases all come from Facilities, and the vendor knows best what each connection point on the tool needs.
• If not: one wrong line can damage the tool or let a toxic gas leak.

Step 3: Check it out: get the tool itself running

• What: power it up and check it part by part: the chambers pump down to vacuum, the fittings don't leak, the robot arm that moves wafers reaches every position, and the sensors read correctly.
• Why: the vibration of the journey, and taking it apart and putting it back together, can loosen a fitting or shift a position slightly.
• If not: problems show up only when wafers are running, and then you can't tell whether it's the tool or the settings.

Step 4: Run the tests in the contract

• What: test item by item against what was agreed in the contract beforehand, for example whether the results fall in the agreed range, whether extra particles appear, and whether the tool keeps running for a stretch without stopping. These are agreed test settings, not the customer's own process settings. Many tools have already been tested once at the vendor's own factory before shipping.
• Why: "is the tool good?" has to be defined in advance, so the two sides aren't arguing past each other.
• If not: after handover, the two sides find out they meant different things by "passed".

Step 5: Sign the acceptance

• What: when everything passes, the customer signs the final acceptance, and only then has the tool officially been handed over. In some contracts, the last payment waits for this signature.
• Why: the signature means the customer agrees the tool did what was agreed.
• If not: sign before it's been checked, and if something goes wrong later, nobody can say whose responsibility it is.

What's different about working in someone else's fab?

• Someone else opens the doors: the customer's badges come in levels, and some areas require one of the customer's people to stay with you the whole time. If they step away, you wait outside. You take a safety course before going in. Some fabs don't allow phones with cameras, and the computers used to service the tools have to be scanned for viruses first.
• You can't see the customer's settings: the settings a tool runs are its recipe, and they're often among the things a customer guards most closely. How much the vendor's people can see differs from fab to fab; some see only the alarms and the tool's own log. So you learn to tell from the log whether it's a hardware fault or something about the settings. Connecting to a tool from outside is the same: it has to go through a path the fab has opened.
• Called out at night: contracts often say how soon the vendor has to arrive when a tool stops; how soon differs from one contract to the next (for what being on call is like, see "Is working in a semiconductor fab hard?").
• Waiting for parts: a tool has so many kinds of parts that not every one can be kept near the customer's fab. When one is missing, it's moved from another warehouse, flown in, or taken from another tool for now; a part taken from another tool has to go back later, which means doing the job twice.
• Caught between fast and right: the customer wants the tool in production a day sooner, and your own company hopes the acceptance gets signed a day sooner. But research on aircraft maintenance lists rushing as one of the common causes of maintenance errors: skip one check, and the mistake often doesn't show at the time, only some while later.

So every service visit ends with a service report: what was done, how long it took, who did it, and what to watch for next. It's for the customer, and for the next person who comes to fix the tool.

In fab24hr

Tap "Clock in", choose "A day in the fab", then on the "Your role today" card tap "R&D line" and swipe to the vendor field service engineer (for what an R&D line is, see "How is an R&D line different from a production fab?"). You look after a new etch tool, ETCH-R1, on the customer's R&D line, and the time you open the game decides which shift you get:

• Morning shift "Day One": two weeks before the wafer start of Glowmere (the customer's hearing-aid chip), it's your first day at this customer's fab. The R&D line is in another building, every corridor looks the same, and for the first minute there's no "Take me there". ETCH-R1 throws an alarm while running the customer's recipe, and you can't see the recipe. Your badge can't open the air shower, so someone with access has to take you in; during the maintenance you explain while the customer's equipment engineer, Chien-Hung, does the work.
• Afternoon shift "One short": a week before wafer start, a part needed for acceptance has burned out, and the one in the spares cabinet is an old revision. You can airfreight a new one, take one from your company's demo tool, or fit the old one and retest that item later.
• Late-night shift: in the second week after wafer start, Chien-Hung calls at 02:00. ETCH-R1 has stopped in the middle of a step with Glowmere's send-ahead wafer inside. The fab hasn't opened a remote connection yet, so all you can do is ask him to read the log to you. You can come in now, or coach him over the phone to get the wafer out first.
• Evening shift "Quarter end": about five weeks after wafer start, your manager hopes the customer signs the final acceptance today, but the leak check reading sits right at the edge of the pass line. You can sign today, or ask the customer for one more day and test again. Take the extra day, and you find that when the ESC (electrostatic chuck) was changed last week, a helium fitting on its back wasn't tightened all the way; the service report gets one more line, "after an ESC swap, leak-check the fittings", and the production fab's ESC swap steps gain that line too.

About six months later, in the etch equipment engineer's morning shift at the production fab, the vendor waiting outside the air shower with a new ESC is you.

The companies, chip, people, tool IDs and times in the game are fictional. What a vendor's field service engineer does and how the work is split come from public, general sources; the real rules and contracts differ between companies. For other jargon, see Chip fab jargon in plain English.