Focus on target!

Article#: 00019

Date: 2020-06-27

Author: Radim

Implementation of the project requirements within given time and financial limits is the target of a project.
Make sure you understand customer needs and keep an eye on them throughout the ongoing project.

Don't underestimate the scope of the project!
Individual tasks may not have been clearly defined and distributed among the team members at the start of the project.
The time and financial limits can seem infinite.

Do not waste any time!
Work efficiently and focus on usability and comprehensibility of the result!

Each member of the team has to know what to do.
Assigned tasks have to be feasible and carried out in the correct order.
Avoid waiting times due to incorrect assignment and dependencies!

Don't do things that are not needed in the project scope!
Don't see a challenge in solving a problem if it is possible to get round the problem.

Do the work iteratively!
For the first release, start with a simpler version.
The quality of the result is more important than the extensiveness.

Use proven methods and tools!
Use tools that help you and save time!
Avoid tools that are not easy to use or are too complex to understand!

Don’t loose the focus and enjoy doing good things!

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

Related previous articles:

• Avoid overly optimistic estimates!
• Check the result!
• Success is not a matter of coincidence
• Choose the right tool!

Related next articles:

• Ask questions!
• Don't disappoint your customer!
• What does the customer need?
• Stay alert!
• Industrial evolution - Listen to your customers and follow new trends!
• Get and stay in the flow!
• 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!
• Set your goals for today, tommorow, this week ...
• Are the people planned for this task really available?
• Appoint a representative!
• 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
• 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
• PLC network diagram
• Graphic designer
• Dream of a platform-independent PLC program
• High Performance HMI
• HMI - Don't overdo it with complex design
• Hidden dangers during commissioning
• HMI is not a web page
• The false illusion of rapid progress
• HMI layout and correct display size
• HMI - colors in the visualization
• What makes an HMI intuitive?
• HMI - light versus dark design
• When a touch panel isn't enough
• Resilient machine control design
• How long will a failure keep our production down?
• Redundant PLC – Yes or No?
• Buttons: Start, Stop and one more
• Different types of machine stops
• Safety stops must have the highest priority

Comment#: 00001

Date: 2020-10-25

User: Radim

In all phases of project implementation, ensure that your results are suitable for their intended use.

Comment#: 00002

Date: 2021-02-14

User: Radim

The customer's application must be good enough, ie such that it meets the customer's requirements. Trying to make it more general, faster or nicer than required means unnecessary work and wasted money. At the beginning of the project, both parties must set precise and verifiable requirements for the application to meet and create a time and financial plan accordingly.

Comment#: 00003

Date: 2021-09-26

User: Radim

"Every team member should know exactly how much an hour of their work costs and keep this in mind when spending two days solving an interesting problem that could easily be avoided."
Translated from:
- Petr Paleta. Computer Press (2003). Co programátory ve škole neučí.

Comment#: 00004

Date: 2022-07-10

User: Radim

"We need to understand our clients' deadline expectations, but the schedule shouldn't be based solely on that. Too many planning activities are compromised from the project beginning by simply focusing too much on the expected delivery date and then planning the activity from start to finish. In contrast to this process, a great plan is based on three key elements:
1. Outputs – what our project should deliver
2. Resources – what we need to realize the project
3. Dependencies - connections between individual work items"
- Stephen Barker, Rob Cole. Grada Publishing (2009). Projektový management pro praxi.

Comment#: 00005

Date: 2022-07-12

User: Radim

The project definition includes:
1. Reason ("Why?")
2. Goals ("What?")
3. Deadline ("When?")
4. Project process ("How?")
5. Responsibilities ("Who?", "Where?")
6. Costs ("How much?")
7. Quality ("How good?")

Comment#: 00006

Date: 2022-10-22

User: Radim

"A business without a path to profit isn't a business, it's a hobby."
- Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.

Comment#: 00007

Date: 2022-10-22

User: Radim

"What's the problem? Are customers confused? Are you confused? Is something not clear enough? Was something not possible before that should be possible now? Sometimes when you ask these questions, you'll find you're solving an imaginary problem. That's when it's time to stop and reevaluate what the hell you're doing."
- Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.

Comment#: 00008

Date: 2022-12-12

User: Radim

It's easy to give advice at the beginning of a project. Everyone here knows best. But are these consultants able to bear the consequences of a failed development that lasts for years and cannot reach satisfaction?

It is usually experienced people who are not asked for their opinion when a concept is being defined, but who repeatedly have to struggle with the consequences of wrong decisions, workarounds and fixes due to the fact that conceptual decisions were not made based on experience.

⇒ Involve experienced people in conceptual decisions and thus avoid later problems.
⇒ Hold people accountable for their decisions and actions!

Comment#: 00010

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

Date: 2023-08-17

User: Radim

Why is there never enough time to do it right the first time, but always enough time to do it over?

"The saying "There's never enough time to do it right the first time, but always enough time to do it over" reflects a common observation about human behavior and project management. It suggests that people often rush through tasks or projects initially, hoping to save time and effort, but end up making mistakes or producing subpar results. As a result, they eventually need to invest more time and resources to fix those mistakes or redo the work properly.

There are several reasons why this phenomenon occurs:

1. Underestimation of Complexity: People might underestimate the complexity or difficulty of a task or project at the outset. This can lead to inadequate planning and allocation of resources, resulting in mistakes or oversights.

2. Pressure to Meet Deadlines: There is often pressure to complete tasks or projects quickly to meet deadlines. This can lead to shortcuts being taken or important steps being skipped in the interest of saving time.

3. Lack of Attention to Detail: When rushing through a task, individuals might not pay enough attention to details, leading to errors that require corrections later.

4. Overconfidence: Sometimes, people might overestimate their abilities or knowledge, leading them to believe they can complete a task quickly without proper preparation or diligence.

5. Incomplete Information: In some cases, tasks or projects might be started without having all the necessary information or requirements. This can lead to incorrect assumptions and decisions.

6. Limited Resources: Constraints on resources such as time, money, or manpower might force people to cut corners initially, with the intention of fixing things later when more resources are available.

7. Learning Curve: Sometimes, tasks involve new skills or technologies that individuals need to learn along the way. Initial attempts might be suboptimal as people are still acquiring the necessary expertise.

The saying serves as a reminder that investing the necessary time and effort upfront to do a task properly can save more time and resources in the long run. Proper planning, attention to detail, and thorough execution can help prevent mistakes and the need for redoing work.

However, it's worth noting that the saying is not universally true. In some cases, rushing through tasks might yield acceptable results, and redoing work might not be necessary. It all depends on the nature of the task, the level of expertise involved, and the specific circumstances."

- https://chat.openai.com (Why is there never enough time to do it right the first time, but always enough time to do it over?)

Comment#: 00013

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

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

Date: 2024-01-05

User: Radim

I found the solution !!!
…but unfortunately the problem didn't match my solution :(

Comment#: 00018

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.