Transparency and reliability

Article#: 00002

Date: 2020-04-11

Author: Radim

When working on a project and pursuing a vision of success, two fundamental qualities must always be kept in mind and applied: TRANSPARENCY and RELIABILITY.

Transparency means: easy to understand, self-explanatory, clearly defined, predictable, meaningful, ...
Reliability means: stable, safe, on time, accurate, working under all conditions and circumstances, predictable, clever, ...

Project requirements, concepts, program code and comments, interfaces, graphical user interface, project documentation etc. must be transparent.
Electrical components, software, interfaces, the entire machine and the entire system etc. must be reliable.

© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).

Related next articles:

• Don't neglect and don't skip any step!
• Development is evolution
• Success is not a matter of coincidence
• Keep it simple!
• Check the result!
• 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
• Store email messages in the project folder!
• 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!
• 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
• Erkenntnisse aus einem abgeschlossenen Projekt sind unbezahlbar
• 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
• Keep the documentation up to date throughout the project
• Maintain order in the program code
• Code formatting
• Graphic designer
• Dream of a platform-independent PLC program
• Keep everything you need together
• Dedicated employees
• 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 and correct display size
• 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-05-18

User: Radim

A happy person who can work with transparent and reliable people.

Comment#: 00002

Date: 2021-10-08

User: Radim

Do things in such a way that they need no further explanation.

Comment#: 00003

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#: 00004

Date: 2023-07-14

User: Radim

"In summary, high performance HMI is a proven way to boost efficiency and increase confidence across operator teams. 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#: 00005

Date: 2023-08-16

User: Radim

Should a PLC software developer design the graphical user interface himself?

"Whether a PLC (Programmable Logic Controller) software developer should design the graphical user interface (GUI) themselves depends on several factors, including the developer's skillset, the project's requirements, and the available resources. Here are some considerations to keep in mind:

1. Developer's Skillset: If the developer has the necessary skills and experience in GUI design, they can certainly handle the task themselves. However, if the developer lacks expertise in designing user-friendly and effective interfaces, it might be better to involve a dedicated UI/UX designer.

2. UI/UX Design Expertise: Designing a user-friendly and efficient GUI requires a good understanding of user experience (UX) principles, usability, and visual design. If the developer lacks expertise in these areas, collaborating with a skilled UI/UX designer can lead to a better user interface and overall user satisfaction.

3. Project Complexity: The complexity of the project can also play a role. If the GUI is relatively simple and straightforward, the developer may be able to handle the design aspect along with their programming responsibilities. However, for more complex applications, involving a dedicated designer can ensure a more polished and professional interface.

4. Time and Resources: Designing a GUI can be time-consuming, especially if it requires iterations and adjustments based on user feedback. If the developer's primary role is programming and they have limited time to allocate to GUI design, it might be more efficient to delegate the design to someone else.

5. Collaboration: Collaboration between the developer and a dedicated designer can lead to a more well-rounded solution. Developers can provide insights into the technical aspects and constraints of the PLC system, while designers can focus on creating a visually appealing and user-friendly interface.

6. User-Centered Design: If the PLC application will be used by non-technical users or operators, it's important to prioritize user-centered design. A dedicated UI/UX designer is more likely to have the expertise to create interfaces that are intuitive and easy for users to navigate.

In summary, while a PLC software developer can design the GUI themselves if they have the necessary skills and the project's requirements are relatively simple, involving a dedicated UI/UX designer can lead to a more effective and user-friendly interface, especially for complex projects or applications intended for non-technical users. Collaborative efforts can often result in a better overall outcome, balancing technical functionality with a well-designed user experience."

- https://chat.openai.com (Should a PLC software developer design the graphical user interface himself?)

Comment#: 00006

Date: 2023-10-05

User: Radim

After the internal tests, how much time does the project need for further software development until it is ready?

From my point of view, several pieces of information about the status of the project are needed for the most accurate estimation:

1. Who is the project leader? Is he still available?

2. What is the project plan?

3. Has the list of all requirements been summarised? How many have been fulfilled and which are still open?

4. On which platform was the software developed?

5. Who developed the software? Is he / she still available?

6. Are there dependencies on external companies?

7. How is the project documented - requirements, software concept, architecture, code, test cases, etc.?

8. How clean and modular is the software?

9. Do the electronic parts and processes of the machine remain unchanged after the internal tests?

10. How successful are the internal tests? What new findings, to-dos / pending issues result from this?

Have I forgotten anything?

Comment#: 00007

Date: 2024-02-02

User: Radim

It can happen that after the release of a new version, something in the program suddenly stops working, even though it worked before.
A version control system can help you keep track of who changed what and why. This allows you to quickly find out why the old function no longer works. And fix the problem accordingly.

Comment#: 00008

Date: 2024-03-06

User: Radim

There are some advantages of alphabetically sorting variables within a declaration block:

1. Easier searching: When variables are sorted alphabetically, it is easier to find a specific variable because you know it will be located at a certain place in alphabetical order.

2. Faster updates and modifications: When updating or modifying existing variables, it is easier to find the relevant variable if variables are sorted alphabetically.

3. Simpler creation of new variables: When creating new variables, you can more easily choose a suitable name if you have an overview of all existing variables and their alphabetical order.

4. Code clarity and maintenance: Alphabetically sorting variables contributes to the clarity of the code and facilitates its maintenance because the programmer knows where to look for a specific variable.

However, it is important to adhere to consistent rules for naming variables.

Comment#: 00009

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.