THE CLAIM
Not the senior with the most years. The right one.
Years measure exposure, not judgement. You can have twenty years in the trade and have seen the same machine twenty times: that is experience, and it is a different thing from being able to decide in front of a problem you have never seen before.
What a good senior leaves you is not the answer. It is the reasoning that gets there: why the fault is here and not somewhere else, why this structure holds and that one does not, why this choice gets paid for in two years. The answer is good once. The reasoning is good for the next problem, which will be a different one, and which by then you solve yourself.
The book is written that way. Every chapter says what you do and, straight after, why - and where the why is uncomfortable it says it anyway.
THE PROBLEM IT SOLVES
Nobody hands you the map.
You learn this trade by being thrown at machines. You learn it through site trips, through faults that do not add up, and through colleagues who are in a hurry. What you end up with is a set of things that worked once, with no theory joining them.
That is fine while the machine in front of you resembles the one you learned on. The day it does not, you have nothing to start from: you have solutions, and you do not have the criteria that produced them.
It is nobody in particular’s fault. The knowledge in this trade travels badly: it sits in a few people’s heads, it is passed on out loud and on site, and it almost never reaches the person who needs it at the moment they need it. The book is the attempt to write it down.
PART BY PART
What it costs you, on the job, not to know this.
The book is four parts plus the appendices. For each one the question is the same, and it is the one that matters on site: what does it cost you not to know it.
P1PART I · THE TRADE AND ITS CONTEXT
The map nobody hands you: what this job is and what living it is really like.
It costs you not knowing where you are. Whoever builds, whoever integrates, whoever uses and whoever repairs are four different interests around the same machine: if you do not know which one is yours, you end up answering for decisions you did not make. Not knowing where you are in the life cycle - quotation, build, acceptance, service - means treating a change on a machine in production as if you were still in the office. And it costs you your own time: with no method for learning when there is nobody to teach you, you learn everything twice. The service report and honest documentation are not paperwork, they are what covers you when you were the last person with your hands in the machine.
P2PART II · THE TECHNICAL FOUNDATIONS
What you must be able to recognise even when it is not your discipline.
It costs you hours standing in front of a problem that is not yours and gets asked of you anyway. You are the last one to look at the machine before it runs, and a mechanical, electrical or pneumatic fault lands on your desk regardless. If you cannot read the cabinet drawing you are moving blind, and the cabinet lies: the symptom is almost never where the fault is. If you do not know the criterion for choosing a sensor, you do not recognise the ways a sensor lies to you, and you spend the afternoon looking in the software for a problem that is out in the field. If you do not know what moves and what can crush you, you do not know what actually has to be stopped before you put your hands in. Recognise, not design: that is what the part is for.
P3PART III · THE PLC AND PROGRAMMING
The core of the trade: making a machine decide, and writing it so it lasts.
It costs the work of everyone who comes after you, including yourself in five years. Clean architecture never starts from nothing: it starts from the last machine shipped, and along with the structure you inherit its limits, including the I/O spare somebody decided not to leave. The state machine is the right way to structure the code, and with the pressure of acceptance testing you betray it anyway: the difference is knowing you did and going back to fix it. The same holds for the panel, which is not a display case for data but an instrument for one specific role: too much information blinds, and colour put everywhere hides exactly what it was meant to show.
P4PART IV · CONNECTION, SAFETY, COMMISSIONING
Where the machine meets the network, the risk and the customer.
It costs you the handover. The network catches you out with the trivial and not with the exotic: a duplicate IP, a VPN, a badly configured network card, and you are standing still in front of the customer. The moment a machine is reachable, whoever reaches it becomes part of the project, and basic hygiene stops being optional. Safety gets bypassed, always, and pretending otherwise protects nobody: the real difference is between the deliberate, controlled bypass and the forgotten one, which kills. In diagnostics the distance between groping for hours and getting there quickly is not knowing more, it is starting from the right point. And the FAT is not "does the machine work, yes or no": it is the moment the customer decides whether to trust the people handing it over, and the work you do not do there gets paid for at the SAT, multiplied.
AXAPPENDICES
The tools to keep open beside the book.
It costs you the customer’s yard. The glossary exists because in the first months half of what you hear in a meeting is an acronym nobody stops to explain. The commented standards exist because what you need is not the text of the standard, it is knowing whether the problem in front of you is one the standard has already thought about. The laptop setup exists because the wrong moment to find out you are missing a driver is the customer’s yard, with the machine stopped and somebody waiting.
THE STATE, IN FULL
It is being written, and these are the real figures.
The book is not finished and it is not for sale. There is nothing to buy, no list to join, and no date brought forward to hurry anybody. What there is is the structure, entry by entry, with the reason for each one: an index can be judged, a promise cannot.
WORK IN PROGRESS IN WRITING EXPECTED RELEASE 06/2027 CHAPTERS WRITTEN 6 / 17
These are the same figures the index reads. They come from the same file and they change when the book changes, not when this page changes.