State Models#
Administration.StateModels
State models provide access to all the system state models and are accessible in the State Models page of the Administration menu.
Browsing State Models#
State Models are associated and organized by Entity Type and the list can be filtered using the appropriate dropdown selection.
The default page in the Administration menu lists all the available State Models:
Select any of the entries to open the details of the state model, together with information on the states, transitions and attributes associated to each of the objects within the selected state model.
Creating a State Model#
StateModel.Create
To create a new State Model, select Create and then follow the Wizard as described below.
- Provide a Name.
- Optionally, provide a Description.
- Select the Entity Type.
- Optionally, provide the Code State Mapping - refers to a Smart Table that contains the code/reason translations.
- Select Create and the system will open the visual editor in the Flowchart view.
Flowchart view#
When the visual editor in the Flowchart view is opened, you can see details for every state and transition in the State Model:
In the right panel, there are three main sub-panels, each of them containing pertinent information for easier understanding and editing of the State Model.
Info#
This panel displays general information on the selected object in the State Model:
Navigator#
A scaled view of the canvas can be useful to narrow down on small details while editing big State Models:
View#
You can filter which information to display in the State Model to make it more or less outright informative:
Editing a State Model#
StateModel.Edit
You can edit the State Model states and transitions by selecting Edit on the top ribbon.
Info
If the State Model has been used by a Protocol Instance or as an Approval Workflow, it cannot be modified because of system integrity and traceability purposes. In this case a warning icon will appear. In the case of Protocols it is possible - but not recommended - to use State Models for Protocol Instances with roles associated to either the State or the State transition, because once used, the State Model cannot be modified. We recommend that you use the Protocol State role instead.
In the main window it is possible to:
-
Add a new state by dragging the State icon from the right-side panel button. By double-clicking on the state you can change the name and description of a state, and specify whether the state is an Initial or Final state. You can also define a security role for the state. If defined, it indicates that only users belonging to that role can transition the object from that state.
Info
A State Model must have one initial state defined.
-
Add a transition to connect two states. This can be done by selecting the triangle pointing away from the (source) state and dragging it into another state (target). There is also the possibility of creating self-transitions by carrying out the same procedure but ensuring that the state area is left before entering it again. To edit a transition name and description, you should double-click on the object or right-click on it and select Settings. You can also define a lookup table with the transition reasons to be used (in the case that a reasons lookup table is defined, it is also necessary to define a default reason). In addition, if a role is defined for the transition, only users that belong to that role will be allowed to perform that transition.
-
Remove an existing state or transition by right-clicking on the object and selecting Delete from the context menu.
-
It is possible to add specific Attributes to States with a wide range of possible types. To edit the State or to add an attribute to it, you can double-click the State box or select the menu dots at the top right corner of the State box that can be selected, and selecting Settings will open a configuration wizard.
Select Save to make the changes effective.
Cloning a State Model#
StateModel.Clone
To clone a new State Model, select Clone and then follow the Wizard as described below.
- Provide a Name.
- Select Clone to complete the operation.
Info
For more information, see Clone. All states and transitions will be cloned along with the new object.
Standards#
Critical Manufacturing provides out-of-the-box State Model standards, namely, SEMI E10 and SEMI E58 (includes reason text). These standards are intended to be used with Resources, and when creating a new State Model for a Resource it is mandatory to have the Basic and SEMI E10 attributes:
Both SEMI E10 and SEMI E58 refer to specific standards published by the Semiconductor Equipment and Materials International (SEMI) organization that define state models used to represent the various states equipment can be in during operation and to describe the transitions between these states.
SEMI E10 defines various terms and equipment states but was not written specifically for application by automated equipment. SEMI E58 was created to provide a consistent interpretation of these equipment states through formal state model methodology.
Each state is associated with a set of attributes which are used to determine the Resource System State: the attribute Basic specifies wether the Resource should be Up or Down. This attribute is important because there is a DEE rule that synchronizes the Resource System State with the value stored in this attribute.
graph TD
subgraph SEMI E10 and SEMI E58
A1[NonScheduled] -->|NonScheduled to Standby| A2[Standby]
A2 --->|Standby to Productive| A3[Productive]
A2 --->|Standby to UnscheduledDown| A4[Unscheduled Down]
A2 --->|Standby to ScheduledDown| A5[Scheduled Down]
A2 -->|Standby to Engineering| A6[Engineering]
A2 --->|Standby to NonScheduled| A1
A3 --->|Productive to Standby| A2
A4 --->|UnscheduledDown to Standby| A2
A5 --->|ScheduledDown to Standby| A2
A3 --->|Productive to UnscheduledDown| A4
A4 --->|UnscheduledDown to Productive| A3
A6 --->|Engineering to Standby| A2
A6 --->|Engineering to UnscheduledDown| A4
A4 --->|UnscheduledDown to Engineering| A6
end
class A1,A2,A3,A6 mermaid_state
class A4,A5 mermaid_entitylinked
class N1,N2 mermaid_businessdata SEMI E10#
**Specification for Definition and Measurement of Equipment Reliability, Availability, and Maintainability (RAM) **
SEMI E10 provides a framework for measuring and reporting the reliability, availability, and maintainability (RAM) of semiconductor manufacturing equipment. It is widely used in the semiconductor industry to establish consistent and comparable metrics for assessing the performance of equipment over time.
States#
SEMI E10 defines a set of equipment operational states to categorize the time and activities of semiconductor manufacturing equipment. These states provide a standardized way to measure and report equipment performance, including availability, utilization, and downtime. The major states as defined by SEMI E10 are:
Productive States
These states indicate that the equipment is operational and contributing to production:
-
Production:
- The equipment is actively processing material (e.g., wafers) and performing its intended function.
- This is the primary productive state, where the equipment is producing output.
-
Engineering:
- The equipment is being used for activities such as testing, qualification, or engineering work, which may not directly contribute to production but is still an intended use of the equipment.
Non-Productive (Idle) States
In these states, the equipment is operational but not actively producing:
-
Standby:
- The equipment is powered on and ready to process material but is temporarily idle. This could happen while waiting for material, operator input, or other resources.
-
Scheduled Downtime:
- The equipment is non-operational due to planned activities, such as preventive maintenance, calibration, or other scheduled interventions.
- This downtime is anticipated and part of regular equipment usage.
Unscheduled Downtime States
These states indicate that the equipment is unavailable for production due to unexpected issues:
-
Unscheduled Downtime (Equipment-Related):
- The equipment is inoperable due to unforeseen equipment failures or malfunctions that require repair or intervention to restore operation.
- This includes hardware or software failures that stop the equipment from functioning.
-
Unscheduled Downtime (Non-Equipment-Related):
- The equipment is unavailable due to external issues not related to the equipment itself, such as power outages, utility failures, or facility issues.
Non-Scheduled States
These are times when the equipment is not scheduled to be used:
- Non-Scheduled Time:
- The equipment is not expected to be in use because it is outside of the scheduled operating hours (e.g., during company holidays or non-operating shifts).
- This state reflects times when the equipment is deliberately not used but could be operational if needed.
Other States
- Preventive Maintenance (PM):
- This is a subcategory of Scheduled Downtime, and refers to planned maintenance activities meant to prevent equipment failures. This includes cleaning, part replacements, and routine servicing.
These standardized states help semiconductor manufacturers and equipment providers measure performance, reliability, and availability in a consistent and comparable way. The following Equipment States Stack Chart reflects the SEMI E10 states:
Benefits of SEMI E10:
-
Consistency - It provides a standardized method to evaluate and compare the performance of different equipment models.
-
Decision-making - It aids in understanding whether equipment failures are occurring due to reliability, maintenance, or operational issues.
-
Improvement - By measuring performance over time, manufacturers can identify areas for improvement, increase uptime, and optimize maintenance schedules.
In sum, SEMI E10 is crucial for ensuring that semiconductor manufacturing equipment meets the high standards of reliability required for large-scale production processes.
For more information, see SEMI E10 ⧉.
SEMI E58#
Automated Reliability, Availability, and Maintainability Standard (ARAMS)
SEMI E58, also known as the Equipment Data Acquisition (EDA) standard, defines a framework for standardizing communication between semiconductor manufacturing equipment and factory control systems. It focuses on how data is collected, formatted, and transmitted to improve equipment monitoring, performance analysis, and automation. The primary goal of SEMI E58 is to establish a reliable and consistent method for gathering real-time data from semiconductor tools, which can be used for productivity monitoring, fault detection, and process optimization.
To resolve state and reason based on code and structure, Critical Manufacturing MES comes with a Smart Table called E58Mapping which contains the code/reason translations with the following columns: Code, Resource, Model, Vendor, Reason, and State.
This table provides more information on the mentioned columns:
| Property Name | Description | Note(s) |
|---|---|---|
| Code | The code from which to resolve a state and reason | Key, Mandatory, String |
| Resource | A Resource | Key, Optional, Reference to a Resource |
| ResourceType | The Resource Type of the Resource | Key, Optional, Reference to a value from the lookup table ResourceResourceType |
| Model | The Resource Model | Key, Optional, Reference to a value from the lookup table ResourceModel |
| Vendor | The Resource Vendor | Key, Optional, Reference to a value from the lookup table ResourceVendor |
| State | The name of the state | Value, Mandatory, String Name of the state, e.g.: Standby |
| Reason | The name of the state reason | Value, Mandatory String Name of the state reason, e.g.: PRD/Regular production |
States and Reasons#
The following tables list the code values and their corresponding reason texts:
PRODUCTIVE
| Code | Reason Text |
|---|---|
| 1000 | PRD (default productive code) |
| 1100 | PRD/Regular production |
| 1200 | PRD/Work for third parties |
| 1300 | PRD/Rework |
| 1400 | PRD/Engineering runs |
STANDBY
| Code | Reason Text |
|---|---|
| 2000 | SBY (default standby code) |
| 2100 | SBY/No operator |
| 2200 | SBY/No product |
| 2201 | SBY/No product/Blocked (Source: IPC CFX) |
| 2202 | SBY/No product/Starved (Source: IPC CFX) |
| 2300 | SBY/No support too! |
| 2400 | SBY/Associated cluster module down |
| 2500 | SBY/No host |
| 2600 | SBY/Reserved |
| 2700 | SBY/Reserved |
| 2800 | SBY/Reserved |
| 2900 | SBY/Reserved |
ENGINEERING
| Code | Reason Text |
|---|---|
| 3000 | ENG (default engineering code) |
| 3100 | ENG/Process experiments |
| 3200 | ENG/Equipment experiments |
| 3300 | ENG/Reserved |
| 3400 | ENG/Reserved |
| 3500 | ENG/Reserved |
| 3600 | ENG/Reserved |
| 3700 | ENG/Reserved |
| 3800 | ENG/Reserved |
| 3900 | ENG/Reserved |
SCHEDULED DOWNTIME
| Code | Reason Text |
|---|---|
| 4000 | SDT (default scheduled downtime code) |
| 4100 | SDT/User maintenance delay |
| 4200 | SDT/Supplier maintenance delay |
| 4300 | SDT/Preventive maintenance |
| 4400 | SDT/Change of consumables |
| 4500 | SDT/Setup |
| 4600 | SDT/Production test |
| 4700 | SDT/Facilities-related |
| 4800 | SDT/Reserved |
| 4900 | SDT/Reserved |
UNSCHEDULED DOWNTIME
| Code | Reason Text |
|---|---|
| 5000 | UDT (default unscheduled downtime code) |
| 5100 | UDT/User maintenance delay |
| 5200 | UDT/Supplier maintenance delay |
| 5300 | UDT/Repair |
| 5400 | UDT/Out-of-spec input material |
| 5500 | UDT/Change of consumables |
| 5600 | UDT/Facilities-related |
| 5700 | UDT/Reserved |
| 5800 | UDT/Reserved |
| 5900 | UDT/Reserved |
NON-SCHEDULED TIME
| Code | Reason Text |
|---|---|
| 6000 | NST (default non-scheduled downtime code) |
| 6100 | NST/Unworked shifts |
| 6200 | NST/Equipment installation |
| 6300 | NST/Equipment modifications (modify, rebuild, upgrade) |
| 6400 | NST/Off-line training |
| 6500 | NST/Shutdown/startup |
| 6600 | NST/Reserved |
| 6700 | NST/Reserved |
| 6800 | NST/Reserved |
| 6900 | NST/Reserved |
Transitions#
The transitions in SEMI E58 refer to the changes or events in equipment states that are communicated between semiconductor manufacturing equipment and factory control systems. These transitions occur when a piece of equipment changes from one operational state to another, and they are critical for tracking equipment performance, downtime, and productivity. The following table shows the transitions for ARAMS State Model:
| # | Current State | Trigger | New State | Action(s) | Comment |
|---|---|---|---|---|---|
| 1 | (Either undeterminable or any state except PRODUCTIVE or STANDBY) | Powerup/reset. | Depends upon the state in which Transition 11 occurred. | None | Entry state is dependent upon previous state where this can be determined. May not generate an event report. |
| 2 | any state | User selects a manufacturing state. | PRODUCTIVE or STANDBY, depending upon the status of the equipment. | Determine the new ARAMS state/substate. | Equipment determines if production criteria are satisfied. If not, it transitions to STANDBY. No event report is generated. |
| 3 | STANDBY | Equipment detects that all its production criteria are satisfied. | PRODUCTIVE | Set ARAMS State to value in PrdState. | May begin or resume processing. |
| 4 | PRODUCTIVE | Equipment detects a standby condition. | STANDBY | Monitor all production criteria. | Equipment may detect a standby condition at any time. |
| 5 | PRODUCTIVE | Equipment detects an exception. | UNSCHEDULED DOWNTIME | Increment InterruptionPrd. | Alarm or exception report generated by same trigger. |
| 6 | UNSCHEDULED DOWNTIME | All fault conditions have been cleared. | PRODUCTIVE | Resume processing. | Transition 6 can only follow Transition 5. Automatic recovery without operator direction may be disabled by the user. May resume processing. Process should be recoverable without degradation. |
| 7 | STANDBY | Equipment detects fault condition. | UNSCHEDULED DOWNTIME | None | Alarm or exception report generated by same trigger. |
| 8 | UNSCHEDULED DOWNTIME | All fault conditions have been cleared. | STANDBY | Monitor all production criteria. | Transition 8 can only follow Transition 7 and may be disabled by the user. |
| 9 | STANDBY | A monitored parameter has reached a pre-defined limit. | SCHEDULED DOWNTIME | None | Preventive maintenance may require reset of the monitored parameter. |
| 10 | (Any ARAMS state/substate) | User selects a new ARAMS Substate Code. | (Based on state/substate selected by user) | Depends upon state/substate selected. | The user may select a new ARAMS state or substate at any time. |
| 11 | (Any of the six basic states) | Powerdown | UNSCHEDULED DOWNTIME, SCHEDULED DOWNTIME, or NON-SCHEDULED TIME. | None | On powerup, the equipment assumes this transition has occurred. This state transition does not represent a collection event. |
| 12 | STANDBY | Equipment detects a change in standby conditions. | STANDBY | None | Transitions 12 and 13 are optional and may be disabled by the user. |
| 13 | PRODUCTIVE | Equipment detects a change in productive conditions. | PRODUCTIVE | None | Transitions 12 and 13 are optional and may be disabled by the user. |
| 14 | ENGINEERING | Equipment detects a fault condition. | UNSCHEDULED DOWNTIME | None | Transitions 14 and 15 may be disabled by the user. |
| 15 | UNSCHEDULED DOWNTIME | All fault conditions have been cleared. | ENGINEERING | None | Transition 14 shall only follow Transition 15. |
Benefits of SEMI E58:
-
Improved Equipment Utilization - By enabling real-time monitoring and data acquisition, SEMI E58 helps fabrication facilities better understand how equipment is being used, which can improve Overall Equipment Efficiency (OEE) and reduce downtime.
-
Enhanced Fault Detection - The standardized communication protocols enable rapid detection of equipment faults or process deviations, thus allowing fabrication facilities to respond to issues before they escalate.
-
Data Consistency - Since SEMI E58 provides standardized data formats, it ensures that data from different equipment models and vendors can be integrated into a common platform, and this improves interoperability and reduces complexities in data analysis.
-
Process Optimization - The continuous flow of equipment data supports process optimization efforts, which helps fabrication facilities adjust processes in real-time to improve yields and productivity.
-
Scalability - As fabrication facilities become more automated and data-driven, the framework of SEMI E58 can be scaled to support complex equipment configurations and large data streams, thus making it critical for modern manufacturing environments.
In sum, these benefits highlight how SEMI E58 plays a key role in enhancing efficiency, reliability, and scalability in semiconductor manufacturing operations.
For more information, see SEMI ⧉.









