Have an expert on hand!
Article#: 00030
Date: 2020-09-12
Author: Radim
Before you decide to use a hardware or software product in a project, you should also assess the quality and helpfulness of the supplier's technical support.
Good technical support is important.
You will need to have an expert on hand.
You'll need support to get trained on the product.
If you discuss the task with a support engineer, you may get the correct solution.
Technical support team can resolve any issues that may arise with the product.
Since software can contain bugs, the technical support should be connected to the developers of the software product to get the fixes faster.
The technical support team can assist you with the project and so you can learn under expert supervision.
A bad support team can leave you hanging, which costs time and money.
Working together with good technical support is very valuable and save you time.
© 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:
- 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"
- Don't make it worse!
- Do the right things and do them right!
- 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!
- Are the people planned for this task really available?
- Appoint a representative!
- Who knows it?
- Functional and intuitive HMI
- Who will operate?
- Collect all the requirements and sort them!
- Project leader
- Learn from your journey!
- Think critically!
- Are there also any disadvantages?
- A good concept = Complete set of suitable solutions
- Hardware concept
- Choice of programming language
- Safety relays versus safety PLC
- Software update
- Design considerations for effective HMIS
- It doesn't work without sensors
- Event logger as the very first function implemented in the program
- Diagnostic tools
- My boss was a hero
- PLC network diagram
- Maintain order in the program code
- Dream of a platform-independent PLC program
- Dedicated employees
- HMI - Have a consistent style
- HMI - Don't overdo it with complex design
- Hidden dangers during commissioning
- The false illusion of rapid progress
- HMI layout and correct display size
Comment#: 00001
Date: 2022-06-16
User: Radim
"Beckhoff’s free TwinCAT software engineering tools, free phone support and free online training eliminate the cost of ownership associated with other controls platforms."
- Beckhoff Automation LLC (06/2021). White paper - Machine Control Migrations Hinge on System Openness - Key aspects to consider when upgrading controllers and automation platforms include increasing flexibility and adding capabilities while being cost conscious.
Comment#: 00002
Date: 2023-04-11
User: Radim
"As an engineer, it's easy to talk about the performance, the capacity, the pros/cons of this solution versus that and just generally the numbers but what's equally important are the humans involved in helping you reaching your goal. Sometimes the resources on the infosys are not enough, and then you have to contact the local Beckhoff support office. At any time I can call or e-mail the local support office and get immediate support/help. I've always had first-class support, and they've always walked the extra mile to solve my issues. Did I also mention the support is free?"
- https://www.linkedin.com/pulse/five-best-worst-things-twincat-jakob-sagatowski/
Comment#: 00003
Date: 2023-08-18
User: Radim
"Don't dig deep into anything because it costs us money. Just pretend that we are experts and hope that the others gets the chestnuts out of the fire."
- unnamed user (own experiences leading to this ironic statement)
Comment#: 00004
Date: 2023-09-11
User: Radim
Does it make sense to think about digitalization if we don't see any use case?
"If you don't see any practical use case or clear benefit for digitalization in your specific situation, it may not make sense to pursue it blindly. Digitalization should always align with your organization's goals and needs. Here are some considerations:
1. Assess Business Objectives: Start by identifying your organization's objectives and challenges. Digitalization should align with your strategic goals, whether it's improving efficiency, reaching new markets, enhancing customer experiences, or reducing costs.
2. Customer Demands: Consider whether your customers or clients expect or would benefit from digital solutions. If there's no demand for digital services, investing in them may not provide a return on investment.
3. Competitive Landscape: Analyze your competition. If your competitors are effectively utilizing digital technologies to gain a competitive advantage, it might be necessary to explore digitalization to stay relevant.
4. Cost-Benefit Analysis: Conduct a thorough cost-benefit analysis to determine if the potential benefits of digitalization outweigh the costs. If the investment doesn't offer a reasonable return, it might not be justified.
5. Resource Availability: Evaluate whether you have the necessary resources, including financial resources, technical expertise, and staff training, to implement and sustain digital solutions effectively.
6. Future Growth: Consider the scalability of your organization. Even if you don't currently see a clear use case for digitalization, it's essential to think about your organization's future growth and whether digital technologies could play a role in that growth.
7. Technology Trends: Stay informed about industry trends and emerging technologies. While there may not be an immediate use case, technological advancements could create new opportunities down the line.
8. Customer Feedback: Engage with your customers or stakeholders to gather feedback on their needs and preferences. They may provide insights that could uncover potential use cases for digitalization.
9. Pilot Projects: Instead of a full-scale digital transformation, consider starting with smaller pilot projects to test the waters and assess the feasibility and impact of digital solutions in a controlled environment.
10. Consult Experts: Seek advice from digital transformation consultants or experts in your industry. They can provide insights into potential use cases and help you determine if digitalization is appropriate for your organization.
In some cases, it may indeed be the case that digitalization doesn't make sense for your organization at a given time. However, it's essential to regularly revisit this assessment as technology and business landscapes evolve. What might not be relevant today could become essential in the future. Ultimately, the decision to pursue digitalization should be guided by a thorough understanding of your organization's unique needs and circumstances."
- https://chat.openai.com (Does it make sense to think about digitalization if we don't see any use case?)
Comment#: 00005
Date: 2023-09-13
User: Radim
Often the person who knows the answer or the right way is closer than you think. All you have to do is ask.
Comment#: 00006
Date: 2025-02-14
User: Radim
The 3 eras of programming: How we learn to code has evolved
1. Before the internet
In the pre-internet era, programmers relied on books, printed manuals, and personal experience. If they encountered a problem, they had to solve it through trial and error or by consulting colleagues. Debugging was slow, and every line of code was the result of hard-earned knowledge.
2. The internet era (pre-AI)
With the rise of the internet, everything changed. Documentation became instantly accessible, forums like Stack Overflow emerged, and learning to code became easier than ever. Programmers stopped memorizing everything and started searching for solutions instead — chances were, someone had already solved the same problem before.
3. The age of AI
And today? Programmers don’t just search for solutions — they have them generated. AI assists with writing code, debugging, and suggesting optimal approaches. Learning now involves experimenting with AI tools that don’t just provide answers but also explain them. More than knowing syntax, it’s about knowing how to ask the right questions.
How will the role of programmers evolve next?
What are your experiences with these changes?