Keep it simple!
Article#: 00010
Date: 2020-04-25
Author: Radim
Strive for simplicity!
Of course, all requirements have to be met and the full functionality implemented.
However, if possible, do not overcomplicate the system and do not apply solutions that are too complicated.
Avoid developing of too complex systems.
If you look at all the requirements together, often you may find some simpler solutions.
Or when you demonstrate the solution, you may get an idea of a simpler one.
The user of the system has to think: "Of course. It is clear and easy. No problem."
Often it is not just a direct way to achieve the goal of simplicity.
But it is worth striving for.
Again and again you will benefit from the simplicity.
For example, in activities such as: development, training of new employees, communication with team members, communication with suppliers, communication with customers, testing, documentation, training of customers, troubleshooting, problem analysis and problem solving.
© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).
Related previous articles:
Related next articles:
- Don't disappoint your customer!
- What does the customer need?
- Industrial evolution - Listen to your customers and follow new trends!
- Realize every good idea ASAP!
- Introduce the terminology and standardize it!
- Everything is difficult until it becomes easy
- Keep the answers to the question "Why"
- Write a project diary!
- Don't make it worse!
- Define test scenarios and test cases continuously!
- Do the right things and do them right!
- Safety first!
- More than just start and stop
- I can see what you can not see
- Do you really want to start with this?
- Is the way really the goal?
- Prepare a good project plan and keep it up to date!
- HMI and PLC applications should grow together
- Write down your best practices and processes!
- Set your goals for today, tommorow, this week ...
- Who knows it?
- Write and accept only readable code!
- Use a usefull styleguide!
- Functional and intuitive HMI
- Who will operate?
- Collect all the requirements and sort them!
- Why do automation projects fail?
- Project leader
- Learn from your journey!
- Design machines with a focus on user's abilities and needs
- Think critically!
- Are there also any disadvantages?
- A good concept = Complete set of suitable solutions
- Hardware concept
- Modular software architecture
- Abbreviations
- Machine modularization
- Knowledge gained from a completed project is priceless
- Variable names
- Choice of programming language
- Visual modeling
- Documentation issues
- Safety relays versus safety PLC
- Software update
- Design considerations for effective HMIS
- Clear signals
- Talk to operators
- It doesn't work without sensors
- Event logger as the very first function implemented in the program
- Diagnostic tools
- My boss was a hero
- Version control system
- PLC network diagram
- Maintain order in the program code
- Code formatting
- Graphic designer
- Dream of a platform-independent PLC program
- High Performance HMI
- HMI - Have a consistent style
- HMI - Don't overdo it with complex design
- Hidden dangers during commissioning
- HMI is not a web page
- Choosing an HMI display
- The false illusion of rapid progress
- HMI layout design
- HMI navigation
- HMI - back and forward navigation buttons
- HMI – Don’t hide anything
- HMI - annoying pop-up windows
- HMI - colors in the visualization
- What makes an HMI intuitive?
Comment#: 00001
Date: 2020-07-22
User:
"Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity."
- Charles Mingus
Comment#: 00002
Date: 2021-05-31
User: Radim
"We invented computers to make the user's life easier, not more difficult."
- Jeff Atwood. Hyperink (2012). Effective Programming: More Than Writing Code.
Comment#: 00003
Date: 2021-09-17
User: Radim
A user does not have to think twice while using a properly designed system and therefore he often does not realize how simple and intuitive it is.
A properly designed system is usually recognized and appreciated by the user after a bad experience with another.
Comment#: 00004
Date: 2021-10-04
User: Radim
Even a simple machine or system can be designed and programmed in such a complex way that its diagnosis and expansion is only possible with extreme effort and a high risk of introducing new unwanted errors.
Do you believe?
Comment#: 00005
Date: 2022-07-01
User: Radim
Keep it simple but not stupid!
Comment#: 00006
Date: 2022-07-01
User: Radim
"Everything should be made as simple as possible, but not simpler."
- Albert Einstein
Comment#: 00007
Date: 2022-10-22
User: Radim
"We’re just as proud of what our products don’t do as we are of what they do. We design them to be simple because we believe most software is too complex: too many features, too many buttons, too much confusion. So we build software that’s the opposite of that. If what we make isn’t right for everyone, that’s OK. We’re willing to lose some customers if it means that others love our products intensely."
- Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.
Comment#: 00008
Date: 2022-10-22
User: Radim
"Whenever you're working on something, ask, "Is there an easier way?" You'll often find this easy way is more than good enough for now. Problems are usually pretty simple. We just imagine that they require hard solutions."
- Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.
Comment#: 00009
Date: 2023-01-30
User: Radim
The more people involved in the conception and development, the more complicated the result becomes. Especially when one doesn't know what and why the other is doing.
Comment#: 00010
Date: 2023-03-08
User: Radim
"Are you adding value? Adding something is easy; adding value is hard. Is this thing you're working on actually making your product more valuable for customers? Can they get more out of it than they did before? Sometimes things you think are adding value actually subtract from it. Too much ketchup can ruin the fries. Value is about balance."
- Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.
Comment#: 00011
Date: 2023-07-11
User: Radim
"New risks are also emerging in automated production, because who will restart a plant or even just a machine if the staff responsible for it at the time of shutdown are no longer working in the same plant. The transfer of knowledge, for example about the last software versions or settings, becomes indispensable. If you do not have the processes and the right solution in place, you risk everything. At this point, trends such as deploying increasing amounts of robots can only help to a limited extent, because even robots are dependent on updates and a certain level of maintenance."
- Curated by Statista, supported by octoplant by AUVESY-MDT. No Fatalism in Manufacturing. Exciting Insights from Leading Studies. (Page 5)
- https://info.auvesy-mdt.com/hubfs/Statista%20ePaper%20EN%20-%20AUVESY-MDT.pdf
Comment#: 00012
Date: 2023-07-14
User: Radim
"A good interface is easy to learn, leads to faster reaction time, safer operations and higher productivity. You deserve a system that is intuitive - one that at a glance you can see what actions need to be taken and is easy to navigate."
- General Electric (2021). Modern HMI/SCADA Guidebook for Efficient Operations.
- https://www.ge.com/digital/lp/modern-hmiscada-guidebook-efficient-operations
Comment#: 00014
Date: 2023-09-27
User: Radim
"By continuously improving the design of code, we make it easier and easier to work with.
This is in sharp contrast to what typically happens: little refactoring and a great deal of attention paid to expediently add new features.
If you get into the hygienic habit of refactoring continuously, you'll find that it is easier to extend and maintain code."
- Joshua Kerievsky. Addison-Wesley (2004). Refactoring to Patterns.
Comment#: 00016
Date: 2023-11-28
User: Radim
If you choose the path to the left at the crossroads, you will not be able to pick the fruit that grows on the path to the right.
So collect all the requirements and decide which ones you want to choose and which ones you want to eliminate by weighing up the pros and cons.
Comment#: 00017
Date: 2024-03-25
User: Radim
Remove the "ballast" from the program!
Only include things in the program that are really needed. Unnecessary parts of the code in the program become obsolete, untested, raise unnecessary questions and are a source of ambiguity.
Sometimes it is a good idea to try more than one way in practice to find out which way is the best. However, once we have decided on a particular approach, it is important to consolidate our methods and remove the outdated ones. By removing "ballast" from the program, we eliminate potential sources of confusion and improve the overall quality of the code.
Comment#: 00018
Date: 2024-07-03
User: Radim
Bear in mind that the operator sometimes operates the system in a panic and needs a short and fast route to the destination and a quick response from the system. The system must inform the operator of what has happened and what is expected of the operator.