ASK A CERTIFIED PRACTITIONER

Need Advice?

Ergonomics Engineered builds software. We have never sold consulting hours, and we are not looking for any. But there is a certified practitioner behind the software. If you have a Human Factors problem in front of you, send it over and we will tell you how we would approach it.

  • Free
  • No follow-up, no pitch, no mailing list
  • A reply within five business days

Answered by a Certified Human Factors and Ergonomics Professional (CHFEP), certified by the Human Factors and Ergonomics Society of Australia.

What people bring

Three shapes, mostly. Yours will be one of them.

01

A control room or interface is changing

Consoles reconfigured, two rooms consolidated into one, a new alarm scheme, a SCADA or HMI upgrade. It arrives as a layout question on paper and it is almost always a workload question underneath.

02

You are choosing between two pieces of equipment

Two devices, two vehicle fits, two console designs, and a procurement decision that has to hold up on more than preference. There is a defensible method for this, and it is not a survey asking people which one they liked.

03

Something has handed you a Human Factors requirement

AS 7470, MIL-STD-1472, IEC 62366, a contract clause, a regulator, a design gate. You can read what the clause says. What it actually wants you to produce is the harder part.

What you get back

One problem in. One answer out.

An invented problem, in the four parts the form below asks for. Beside it, the reply it would get, in the four parts every reply takes: how we would frame it, what we would reach for, what we would look at first, where the traps are. About twenty minutes of a practitioner's attention, written down.

Re: Control room consolidation, console layout at DDR Reply, three business days later

That is how we would open it. The endorsement is yours, and the argument above is the one we would put in front of the design authority. If the project needs a formal control room verification against ISO 11064, that is scoped work with operators in a mock-up, and we can point you towards someone who does it.

Twenty minutes, roughly. The problem is invented. The method is not.

The utility, the engineer and the numbers are made up for this page. Real problems stay between us unless you tick the box in the form that says otherwise.

Two ways to ask

By email, usually. By Teams, when it needs a conversation.

The default

By email

Describe the problem in the form below. We reply within five business days, in the shape above, and usually sooner.

When it warrants one

By Teams

Thirty minutes, for a problem that genuinely needs a conversation. Send the problem first, so we have read it before we talk, then pick a time.

Both are free. There is no follow-up sequence, no pitch and no mailing list. You hear from us once, with the answer.

The limits are the offer

One problem. One answer.

What you get

  • How we would frame it.
  • Which method or standard we would reach for.
  • What we would look at first.
  • Where the usual traps are.

What we will not do

  • Write your report or assessment.
  • Sign off, endorse or certify anything.
  • Review a tender submission or a bid.
  • Act as an expert witness.
If it turns out you need a full assessment, we will say so and point you towards someone who does that work.

We do not want the work, so we have no reason to tell you otherwise.

Your turn

Describe the problem.

The same four questions the reply above answers. Write it the way you would tell a colleague in the corridor: what the thing is, what happened, what you have tried, what you have to decide. Leave out anything sensitive; the note under the form says what that means.

How should we reply?
One email back. Nothing else.

What comes back is general guidance based on what you tell us. It is not a formal Human Factors assessment.

You own the decision, and the duty of care that goes with it.

Do not send classified, export-controlled or commercially sensitive material, or anyone's personal health information. If the problem cannot be described without it, say so in the form and we will talk about how to handle it.

By Teams

Pick a time.

Thirty minutes. Send the problem through the form first, so we have read it before we talk.

Why free

Because it is the cheapest honest test there is.

A case study is a story we chose. A problem you bring is a test you set. Twenty minutes on it tells you more about what we are like to work with than anything else on this site.

It tells us something too: what practitioners are actually up against. That is where the software's roadmap comes from, and where the next Workbook example comes from, if you let it.

The software we build instead: ErgoSphere.

To Top