An Experimental Study on Three General Interface Layout Designs for Chemical Process Plants
Bibliographic record
Abstract
Abstract The human‐machine interface design is not a new problem; however, existing knowledge appears to be focused either on interface conceptual design, which determines what information at what time needs to be displayed, or on interface detailed design, which determines the form of display elements. This article presents a study on interface layout design. Three interface layout designs were proposed based on the proximity compatibility priniciple, which were on the same interface conceptual design. In particular, the first interface layout design is with the highest degree of proximity cognition and the second and third with a reduced degree of proximity cognition. They are called sophisticated, semisophisticated, and nonsophisticated interfaces, respectively. An experiment with a simple process plant was conducted to understand user behaviors on the three interfaces. It is noted that in order to provide an unbiased comparative evaluation of these interfaces the same application problem and similar look‐and‐feel forms of interfaces were designed. In the experiment, three general classes of tasks were considered, namely, normal control operation, fault detection (or monitoring), and fault diagnosis. Two categories of measures were used: the performance measure and the subjective measure. The major results obtained from the experiment are 1) the nonsophisticated interface is the best for fault detections in terms of performance measure; besides, this interface has the lowest mental workload for fault detection; 2) the sophisticated interface is the best for normal operation in terms of performance measure; 3) there appears no significant difference for fault diagnosis in terms of performance measures for all these three interfaces; 4) for normal operation and fault diagnosis, the mental workloads for the three interfaces have no significant difference. Overall, the experiment suggests that the nonsophisticated interface be used in practice with additional two reasons: 1) most of time in the chemical process plant today is the fault detection or operation monitoring task, and 2) it is relatively easier for the nonsophisticated interface to adapt to changes in the chemical process plant design, which are common in today's manufacturing environments.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".