Looks good on paper. Reality was not consulted.
Customers are strangely obsessed with our technical datasheets. They read the output, capacity, efficiency, temperature range, weight and dimensions and then make the unreasonable assumption that the machine they receive should somehow correspond to those numbers.
We prefer a more flexible relationship between documentation and equipment. The datasheet tells you what the product is capable of being. The actual machine tells you what we managed to build.
Sometimes the numbers match beautifully. Sometimes they require context. Temperature. Configuration. Peak load. Tolerance. Firmware. Measurement method. Lunar phase. We have explanations.
The important thing is that the brochure remains consistent.
THE MACHINE IS OUR DISCLAIMER. Actual performance becomes clearer after delivery.
We publish the best number we can find
Engineering loves conditions. Continuous output. Peak output. Ambient temperature. Duty cycle. Test duration. Configuration. Engineers keep adding these words because apparently numbers need context.
Marketing has a cleaner approach. We find the largest defensible number, remove the parts that make it look smaller and put it in the brochure. If the machine reaches the figure for a few seconds under ideal conditions, then technically the figure has been introduced to reality.
We are not lying. We are simply giving the number room to express its full commercial potential.
Continuous output?
Customers mostly notice the output.
Everything becomes a tolerance eventually
We understand that manufacturing tolerances are supposed to describe small variations between real products. We simply believe the concept deserves more ambition.
If a customer measures slightly less than the brochure, that is tolerance. If they measure noticeably less, that is extended tolerance. If they measure something completely different, we start discussing configuration, environmental conditions and whether their measuring equipment has been calibrated recently.
This is one of the advantages of engineering language: almost every bad number has a longer phrase available.
WITH THE DATASHEET,
REALITY NEEDS CONTEXT.
Our equipment passes the test eventually
Factory Acceptance Testing is awkward because somebody connects instruments to the machine and numbers start appearing independently of our PowerPoint presentation.
Sometimes those numbers agree with the datasheet. Excellent. Sometimes they do not. Also excellent, because now we have useful information for refining the acceptance criteria.
We believe testing should be collaborative. Why decide what constitutes a pass before seeing what the equipment can actually achieve?
to accept the product we already built.
If the customer finds it, they helped develop it
The customer receives the machine, connects it to real infrastructure and begins using it under actual operating conditions. This is where certain technical details occasionally become visible for the first time.
Maybe the output behaves differently. Maybe the temperature limit develops nuance. Maybe a protection function works in a way the manual had not anticipated. Traditional manufacturers might call these validation gaps.
We call them field discovery.
The customer sends logs, measurements and photographs. Our engineers study them. Eventually we understand the product better than we did before selling it. Everybody wins, especially R&D, which receives free operating data.
CUSTOMER JOINED R&D. Thank you for your contribution to product development.
Why fix the machine when we can fix the PDF?
Once a discrepancy is confirmed, there are technically two options. We can modify the equipment until it meets the specification, or modify the specification until it meets the equipment.
One option requires components, engineering hours, testing and possibly redesign. The other requires Microsoft Word.
We believe in efficient corrective action.
So a guaranteed value may become typical. Continuous may become maximum. A temperature range gains a footnote. A number receives the words “up to”. And suddenly product and documentation are aligned again.
is a revised datasheet.
Frequently
Measured Questions
Does our equipment match the datasheet?
Yes, within the appropriate combination of tolerance, configuration, interpretation and optimism.
Please specify which revision of reality you are using.
Why did the customer measure a different value?
Our first assumption is measurement error. Our second assumption is environmental conditions. Our third assumption is configuration.
The product becomes our assumption only later.
What happens if the product clearly misses the agreed specification?
We begin a comprehensive technical investigation into whether the customer really needs the specification they purchased.
If necessary, a new PDF can normally be issued much faster than a new machine.
We understand why customers expect equipment to match technical documentation. We even agree with the principle. It is just considerably easier to agree with it before somebody starts measuring.
Our process is simple: publish the attractive number, build the product, test what we have, explain the difference and update whichever side of the equation is cheaper.
Could we validate every important specification properly before selling the machine? Of course.
But then the datasheet might contain smaller numbers.
And smaller numbers are terrible for Sales.
FAIL THE SPECIFICATION.
THE SPECIFICATION FAILS
TO UNDERSTAND OUR EQUIPMENT.