SIDM · PART II
Chapter 5 — Good to Use: Usability and User Experience in Industrial Equipment
How industrial equipment becomes genuinely usable through function, comprehension, operation, maintenance, safety, and context of use.
Good to Use is a design philosophy and guiding principle within SIDM. It requires equipment to work effectively in real tasks. It directs teams to address six concerns throughout design: function, comprehension, operation, maintenance, safety, and context of use. These are considerations for design judgment, not a scoring system or a basis for assigning maturity levels.
Good to Use and Real User Experience
Industrial equipment must first perform a defined production task. That task may involve machining, inspection, conveying, sorting, packaging, assembly, cleaning, drying, welding, material handling, testing, or another industrial operation. Whatever the industry, the equipment's ability to fulfill its function determines its fundamental value as a product.
A machine may perform its machining task yet leave users struggling to understand the operating sequence. It may run reliably while making critical components difficult for maintenance personnel to reach. It may satisfy technical specifications while exposing personnel to hazards at the operating site. Automated functions may work correctly, yet unclear status feedback, complicated control logic, or impractical maintenance paths can impose an unnecessary burden on users.
In SIDM, Good to Use therefore means more than merely being operational. It means that, in the actual context of use, equipment can be understood clearly, operated smoothly, maintained conveniently, approached safely, and integrated reasonably into its surrounding environment.
Good to Use addresses the relationship between equipment and people.
Good to Use aims to reduce the burden of understanding, operation, and maintenance. It also gives equipment customers a basis for judging how well the manufacturer understands conditions on the shop floor. Improvements should be checked against records of actual use, not assumed on the strength of a design proposal.
User experience (UX) is formed as users complete tasks, interact physically with equipment, interpret information, and respond to feedback in real conditions. SIDM considers bodily movement, physical touchpoints, information comprehension, operating actions, task sequences, feedback, maintenance, safety, and context. UX is a cross-cutting method for understanding, designing, and verifying these relationships; UI or HMI is only the information-and-control interface component of that wider experience.
Experience research should begin with user tasks. Teams need to observe who performs which actions, under what conditions, on the basis of what information; where people wait, detour, or encounter obstacles; and how they recover from abnormal conditions. Management preferences, the fluent performance of a demonstration operator, or users' verbal assessments cannot individually replace observation of real tasks. Identifying actions and difficulties, then turning them into design requirements, makes verifiable improvement possible.
Three experiences must be distinguished. Equipment-use experience arises when users operate, observe, maintain, service, or manage a machine. Design-project collaboration experience concerns how the commissioning client engages a design-service team, communicates, approves decisions, manages changes, and receives service. Customer-contact and service experience concerns the relationship between the equipment customer and the manufacturer through sales, delivery, and after-sales service. They must be recorded separately: smooth project collaboration or satisfaction with service is not evidence that the equipment is Good to Use. Chapter 24 addresses project collaboration experience.
Function
Equipment must accomplish the production task agreed upon. Industrial design must respect the production process, operating principles, and the customer's production objectives. Appearance, quality expression, and brand design language cannot compensate for the absence of essential functionality.
For industrial equipment, machining accuracy, inspection performance, throughput, process capabilities, control algorithms, and core mechanical principles are generally determined by the manufacturer's technical, engineering, or product-development teams. Industrial design should not redefine those core technologies independently of their engineering foundations or assume direct responsibility for technical performance outside its remit.
The contribution of industrial design is to organize, communicate, and make the equipment's functional relationships usable more effectively, while respecting the underlying function.
The location of functional modules, the relationship between operating zones and task sequences, the positioning of observation windows for status checks, access from maintenance doors to critical parts, the separation of material flows, and coordination between safety guards and operating functions all influence usability. They do not change the machine's core technology, but they do affect whether its functions can be used, understood, and maintained readily.
When functional modules are arranged without order, operating and maintenance areas interfere with one another, observation points do not correspond to actual operating states, or guards obstruct necessary actions, users must expend more effort understanding and operating the machine—even if it still works. By contrast, clear functional organization helps users recognize where to operate, maintain, observe, approach, and avoid hazards.
Necessary functional relationships should be understandable, operating states perceptible, and access for operation and maintenance supported. Complex functions may be concealed when appropriate, but not at the expense of information or access points required by the task.
Comprehension
Industrial equipment is often large, modular, and structurally complex. Before interacting with it, users need to understand it: where to operate, where to observe, what may be opened, where hazards lie, where maintenance occurs, and what indicates the current operating state. Design relationships should communicate these distinctions clearly.
Design for comprehension should reduce the effort required to understand the equipment.
The overall layout should communicate functional zoning. Primary controls should be easy to locate; frequent actions should occur in sensible places; critical information should have a clear hierarchy; hazardous areas should be visibly bounded; and maintenance access should be identifiable. Users should not have to search repeatedly through a complex structure for controls or guess the machine's status.
Form, color, labels, windows, doors, and status feedback can communicate functions and the character of different areas. Whether they communicate the intended operating logic must be confirmed through task observation rather than inferred solely from the designer's intentions.
Industrial users frequently work under continuous production demands, noise, time pressure, and safety constraints. Confusing information hierarchies, ambiguous button locations, and inadequate feedback can cause incorrect judgments. Design for comprehension is not about making complex equipment merely look simple; it establishes a clear order within a complex task so that users can understand quickly, judge accurately, and operate consistently.
Operation
Equipment must ultimately be operated by people. Regardless of its degree of automation, it must be started, stopped, configured, adjusted, observed, confirmed, reset, attended to under abnormal conditions, and serviced. The coherence of these operating relationships directly affects user efficiency, workload, and confidence in safe operation.
Operating design should support the completion of tasks through sensible action sequences.
Operating zones should match user positions. Buttons, knobs, screens, emergency-stop devices, and control panels should reflect the frequency and order of actions. Frequently used controls should be within comfortable reach; critical operations should be clearly distinguished; hazardous actions should be protected against inadvertent activation; and abnormal-condition handling should provide clear feedback and necessary prompts.
Operating a machine is not confined to using its screen.
Many operations are physical. A user may need to open a door, pull out a drawer, adjust a fixture, load material, observe a process, remove a finished part, replace consumables, clean residues, or clear a fault. Handle position, door swing, maintenance clearance, observation-window height, and the relationship between platforms and guardrails all affect how smoothly these tasks can be performed.
Operating design must therefore address both interface interaction and bodily movement.
Screen information should be clear and physical touchpoints recognizable. Operating sequences should follow the workflow, with movement spaces suited to the body. Feedback should be timely and error prevention reliable. Common actions should be convenient; hazardous actions must be controlled. Only when these relationships work together does equipment feel straightforward in real use.
A single awkward operation may seem minor; a difficult action repeated over months becomes a persistent burden. Equipment users interact with machines day after day. Poor heights, distances, sequences, feedback, and movements accumulate costs over the equipment's service life. Good to Use is verified through precisely these repeated activities.
Maintenance
Industrial equipment is not a short-lived consumer good. It must be operated, maintained, repaired, and managed over a long service life. Its continued serviceability depends not only on core technology and manufacturing quality but also on accessible inspection points, practical servicing, reasonable replacement of wear components, and manageable cleaning procedures.
Many designs prioritize operation but give insufficient attention to maintenance. A machine may function adequately until it needs to be inspected, cleaned, adjusted, repaired, or restored after a fault. At that point, users discover insufficient clearance, unclear access, complicated disassembly, poor visibility, awkward tool access, or inaccessible critical components.
Maintenance design should support service, inspection, and management throughout the equipment life cycle.
Maintenance doors should provide access to the actual components that require attention, with opening directions that avoid site obstructions. Frequently serviced points should be reachable. Consumables and wear parts should be replaceable without unnecessary dismantling. Observation windows should support condition checks. Cleaning zones should accommodate residues and contaminants. Electrical, pneumatic, and hydraulic systems should have clearly defined maintenance boundaries.
Difficult maintenance can encourage delayed servicing or improvised, nonstandard interventions, increasing operational and failure risks. Clear service routes, appropriate working clearances, and practical disassembly support proper maintenance, although actual outcomes must still be evaluated against site management and service records.
Maintenance provisions influence how stable and manageable a machine remains over many years. Equipment customers can use service clearance, disassembly methods, and maintenance records to assess whether a manufacturer has considered the full product life cycle.
Safety
Industrial equipment may involve mechanical movement, electrical control, high temperatures or pressures, high speeds, cutting, welding, lasers, clamping, material handling, dust, noise, and other complex hazards. Once installed in production, it must accommodate personnel access, repetitive operations, abnormal-condition handling, servicing, and cooperation among multiple trades.
Safety design should establish clear hazard boundaries, control dangerous contact, support recognition of abnormal conditions, and reduce operating errors.
Hazardous areas must be distinguished by suitable structures, guarding, clearance, warnings, and feedback. Users should understand where access is permitted or prohibited, when shutdown is required, where protective equipment is necessary, and which areas pose motion, electrical, or thermal hazards. Safety cannot depend solely on training and warnings; the equipment's own design relationships must continuously communicate and enforce appropriate constraints.
Emergency stops, interlocks, guarded doors, warning labels, stack lights, viewing windows, maintenance modes, access permissions, anti-misoperation features, and abnormal-state feedback are all part of the experience of safety.
Safety design must establish an orderly approach to risk control across function, operation, maintenance, and site workflow. Protective measures must remain usable, accessible for authorized work, maintainable, and compliant with applicable specialist safety requirements. Convenience must never justify weakening necessary safeguards.
Safety is a non-negotiable condition of Good to Use; convenience elsewhere cannot compensate for a failure of essential safety requirements.
Safety is a design boundary. Comfortable operation is not grounds for relaxing professional safety requirements. Emergency stops, interlocks, guarding, and servicing boundaries involve industrial design, mechanical, electrical, and control specialists. The appropriate disciplines must confirm these provisions; industrial designers identify issues arising at points of human contact and ensure they are referred to accountable specialists.
Context of Use
Industrial equipment is not operated in idealized settings. It works in actual factories, production lines, workshops, staffing arrangements, and production rhythms. Site dimensions, material movement, operator positions, lighting, noise, temperature and humidity, dust, oil contamination, upstream and downstream equipment, and management practices all affect use.
A design may look convincing on paper without working well at the customer's site. Is there enough floor space? Can doors swing fully? Is the service side blocked by a wall or another machine? Can operators stand where they need to? Can materials enter and leave without obstruction? Are forklift access, lifting, transportation, and installation realistic? Each question has a direct bearing on real usability.
Design for context of use should verify that equipment fits its actual operating environment.
Equipment must be considered in relation to people, materials, production lines, space, environment, and management—not only as an isolated object. Automated machinery demands attention to upstream and downstream cycle times and material flows. Inspection equipment calls for appropriate sample handling, viewing, and data reading. Environmental equipment may require service passages, pipework coordination, and pollution control. Machine tools call for visibility, chip removal, and safety zones. Energy equipment needs consideration of installation, service access, and long-term operating conditions.
Priorities differ by task. Food and pharmaceutical equipment may require particular attention to cleanliness and hygiene boundaries. Laser and welding equipment demand verification of guarding and action paths. Testing equipment requires careful observation, reading, and precision handling. Heavy equipment calls for service clearance, structural strength, and durability. Specific requirements must be confirmed against the project setting and by the responsible disciplines.
Function, comprehension, operation, maintenance, and safety must all be tested in the actual context of use.
Integrating UX into the Project
During the input stage, the team should document user roles, key tasks, site conditions, and evidence of problems. During concept development, it should organize touchpoints, task flow, observation, and maintenance relationships. During structural development, these relationships become usable clearances, opening mechanisms, mounting interfaces, and necessary protection. When a physical machine exists, teams verify them through real tasks. Feedback from use after delivery feeds into subsequent projects. Chapters 17–20 describe the four-stage process; Chapter 13 addresses maturity assessment of interaction outcomes.
Experience verification should cover the tasks actually required: routine operation, changeovers or replenishment, cleaning and maintenance, and handling abnormal conditions. Different people may perform different tests; the most experienced operator should not be the sole test subject. Record task completion, misjudgments, unnecessary movements, waiting, accessibility, and recovery paths, then compare them with the original solution or project objectives. There is no need to compress all experience into a single satisfaction score.
KEEP READING





































