Semi E58

SEMI E58 defines ARAMS (Automated Reliability, Availability, and Maintainability Standard), the SECS/GEM messaging layer that automates the data collection Equipment Reliability/Availability/Maintainability (SEMI E10) and Equipment Performance Tracking (SEMI E116) depend on — specifically for maintenance-event data, not just the state-time accounting E116 already automates. Where E116 streams E10's state-category transitions (productive, standby, downtime) to the host in real time, ARAMS extends that automation specifically into maintenance event detail — what failed, what was repaired, how long the repair took, and what parts were consumed — the richer information a reliability engineer actually needs to compute meaningful Mean Time Between Failures (MTBF) and Mean Time To Repair (MTTR) figures, rather than just raw downtime duration.

Equipment enters Unscheduled Downtime (E10 state)
E116 already reports this transition and timestamp
SEMI E58 ARAMS maintenance-event detailRicher data than E116's state-time accounting alone
Failure classification reported
What subsystem failed, failure mode
Repair action + parts consumed reported
What was done, what components were replaced
Host computes real MTBF/MTTR from automated data
Not just raw downtime duration from E116 alone

Without ARAMS, a reliability engineer trying to compute MTBF or MTTR from E116's data alone only has downtime duration and timing, which can tell you how often a tool went down and for how long, but not why — two tools with identical E10 availability numbers can have completely different underlying reliability pictures if one is failing for the same root cause repeatedly while the other fails for a different reason each time, a distinction that matters enormously for maintenance planning but is invisible in raw state-time data alone. ARAMS exists to automate the collection of exactly the maintenance detail that turns availability numbers into an actionable reliability engineering picture, rather than leaving that richer data to be manually logged by technicians after the fact, which is slower, less consistent, and far more prone to gaps than equipment reporting it directly through SECS/GEM.

SEMI E58 (ARAMS) — Beyond Raw Downtime Duration same downtime number, very different reliability stories Tool A (E116 data only) 90% availability same root cause, every time (only visible via ARAMS detail) Tool B (E116 data only) 90% availability different cause, every failure (only visible via ARAMS detail) Identical availability, very different maintenance needs Tool A: fix the recurring root cause once Tool B: broader reliability investigation across many failure modes ARAMS's automated failure/repair detail is what reveals this difference

SEMI E58 completes the metrics-automation family alongside Equipment Performance Tracking (SEMI E116) — E116 automates the state-time data behind E10's availability and utilization figures, while ARAMS automates the richer maintenance-event detail that turns those same figures into genuine MTBF/MTTR reliability engineering, both existing so a fab's reliability analytics run on consistent, automatically-collected equipment data rather than manually logged maintenance records.

Take SEMI E58 further

Ask the copilot about this term, or have our engineers assess it against your process.

Ask CFSGPT about this → Request a technical assessment → Open the CFS app