Hire a freelance HMI developer
Post the job and read proposals from engineers who have designed operator interfaces for machines like yours. Ingenium is the marketplace and holds the contract; the engineer you hire designs the screens.
Post an HMI jobWhat HMI design and development means
The HMI — the human-machine interface — is the screen an operator uses to run a machine. Usually a panel-mount terminal bolted into the cabinet door; sometimes a plant PC, sometimes a tablet.
It is the only part of a control system most people ever touch, and it is judged under the worst possible conditions: gloves on, mid-shift, something has stopped, and the person looking at it needs to know what and why within a few seconds. That is the brief. Screen design for an operator interface has far more in common with designing an aircraft cockpit than with designing a website, and the instinct to make it look impressive is almost always the wrong one.
The work starts with hardware and a layout. A panel-mount terminal has a fixed resolution, a fixed physical size and often a resistive touchscreen, so touch targets have to be sized for a gloved finger rather than a mouse pointer and the whole hierarchy has to fit the pixels available. Then a navigation model: a home or overview screen, one screen per machine area, detail popups or faceplates per device, a manual or maintenance screen for jogging individual outputs, and recipe or settings pages. An operator should never have to remember a path.
Alarm pages are their own discipline. A current-alarm list and an alarm history, with time, priority, text an operator can act on, and acknowledgement. A banner on every screen so a new alarm is visible without navigating. Text that says which sensor and which consequence instead of “Fault 42”. And restraint about what becomes an alarm at all — an interface that flashes red during every normal start-up has taught its operators that red means nothing.
The rest is the detail that decides whether the machine is pleasant to run: consistent colour meaning (and colour never as the only signal, because colour-blindness exists on a shop floor), live values with units, state shown by shape and text rather than hue alone, buttons that reflect whether the action is currently permitted, confirmations on anything irreversible, user levels so only maintenance can reach the manual screens, and language support where the shift changes language. Most of these decisions cost nothing to make correctly at the start and are expensive to retrofit.
What an HMI job usually covers
Screen count alone is a poor description of the job. These are the parts that actually take the time.
Hardware and layout decisions
Terminal size, resolution and mounting, touch target sizing for gloves, readability at the distance and lighting the operator actually stands in, and whether a second screen or a remote client is needed.
Navigation model
Overview, area screens, device faceplates, manual and maintenance screens, recipes and settings — arranged so an operator reacting to a stoppage gets to the cause without a map.
Screen design and templates
Reusable objects per device type rather than hand-drawn copies, so a second identical station is configuration and not redesign, and a change to the pump faceplate happens once.
Alarm pages and banner
Current alarms, alarm history, priorities, acknowledgement, and alarm text that names the device and the consequence. Plus a banner that is visible from every screen.
Tags and PLC interface
The tag list the HMI reads and writes, agreed with whoever is writing the controller program — including which side owns each interlock, so a button cannot bypass logic the PLC is responsible for.
User levels, languages and handover
Operator, maintenance and engineering access, multiple languages where the site needs them, a project backup, and documentation the plant can use to change a label without calling anyone.
Terminals and software
HMI work is tied to the hardware in the cabinet door. Name the terminal and the software version — a project file is rarely portable between them.
Allen-Bradley / Rockwell
- PanelView Plus
- PanelView 5000
- FactoryTalk View ME
- FactoryTalk View SE
- FactoryTalk Optix
- Studio 5000 View Designer
Siemens
- SIMATIC Comfort Panels
- Basic Panels
- Unified Comfort Panels
- WinCC in TIA Portal
- WinCC Unified
Other terminal families
- Beijer
- Pro-face
- Weintek
- Red Lion
- Mitsubishi GOT
- Omron NA / NB
- Delta DOP
- C-more
PC and web-based
- Ignition Perspective
- Ignition Vision
- AVEVA InTouch
- iFIX
- CODESYS Visualization
- TwinCAT HMI
Standards and references
- ISA-101 (HMI design)
- ISA-18.2 (alarm management)
- High-performance HMI practice
- IEC 61131-3
Terminal and software names are the products the work is done in. An engineer’s experience with one is a fact about their history, not a partnership with or endorsement by its manufacturer.
Hiring it, and doing it
The same page serves two readers. One is deciding who to trust with a running machine; the other is deciding whether the job is worth a proposal.
What to look for in an HMI developer
Ask to see screens they have shipped and, if you can, ask the operators who use them. This is the one part of a control system with a user.
- Experience on your terminal family and software version, named
- Screens built from templates and device faceplates rather than copied page by page
- Alarm text written for a person on shift, not for the person who wrote the program
- Attention to touch targets, contrast and glove use — the real conditions, not a desk monitor
- An opinion about what should not be on the screen
- A clear split with whoever writes the PLC code about which side owns each interlock
If you design operator interfaces
Your profile is what a client reads before they message you, and Ingenium requires it to be complete before you can send a proposal or accept an offer.
- List terminal families and software by name and version — that is how the jobs are described
- Use job history to show the machines: filling lines, presses, water treatment, kilns, test rigs
- Say whether you also write the controller logic, or work to someone else’s tag list
- Mention multi-language projects and user-level work; both are commonly asked for and rarely offered
- Skills, resume, job history, education, hourly rate and work schedule are all required before you can apply
- A client has to open the conversation — an invite to a job, a message, or an offer
How you hire an HMI developer here
Ingenium is a marketplace, not an engineering firm. It does not do the work — it is where the job is described, proposals are compared, and the contract and the money are held once terms are agreed.
Post the job
Describe the scope, the equipment involved and the site, and post it under Controls Engineering. Posting is free. You can also invite a specific engineer to the job, or message one from their profile.
Read the proposals
Engineers who do this work reply with their rate and how they would approach it. Messaging is open from the moment a client starts the conversation, so the scope can be argued out before anyone commits.
Send an offer
An offer sets the payment model and the terms. Fixed price is split into milestones; hourly is invoiced weekly from logged time. The model is chosen when the job is posted and cannot be swapped later. A saved card is needed before an offer can go out.
Run the contract
An accepted offer becomes a contract with a shared work diary, tasks, time entries, comments, invoices and expense claims. Funds are held by Stripe and released when the client accepts the work.
Which payment model fits
HMI work is one of the easier things to price fixed — the screen list and the tag list are countable, and milestones split cleanly into templates, then screens, then alarms and handover. Hourly is the better fit where the screens are being reworked on a machine already in production and every change has to be agreed with the people running it, or where the HMI job is really an audit of an existing project first. The model is set when the job is posted and cannot be changed later, so a project that needs both is two jobs.
The full flow from posting a job to getting paid covers both models and where the money sits in between. Everything a contract carries — time tracking, milestones, messaging, invoices, payouts — is listed on the features page. Or create an account and post the job.
Usually part of the same project
These jobs tend to arrive together. One engineer sometimes covers two of them; sometimes it is two contracts.
Your next engineer is one click away
Connect with the best freelance engineers and streamline your projects with our integrated management tools.
New here? Sign up for Free