The coating paste is mixed to a ratio that appears on no card. When the base cloth runs thin, the senior process engineer lifts the knife-over-roll gap by a hair. When pinholes show, he slows the line and raises the oven zone by a few degrees. The operators call him by first name and wait for his nod. One day he is on leave with fever, and the PU coated tarpaulin run goes out with a tacky face. That is the problem in a technical textile unit: the recipe lives in a single head.
Technical textiles include coated fabrics, geotextiles, filter media, needle punched felts and spunbond nonwovens. They share a tight tolerance and a recipe built on experience. Weight per square metre, pore size and peel strength are the numbers customers check. This dependence is the first pressure listed on the technical textile makers page. The parent hub puts it beside the other branches of the trade.
What is actually inside one engineer's head
- The paste mix of PU or PVC resin, plasticiser, calcium carbonate filler, pigment and stabiliser, and the sequence in which each goes into the dissolver.
- The viscosity window that works on a given base cloth, read by feel as much as by a flow cup.
- Knife gap, blade angle and line speed for each grams per square metre target.
- Oven zone temperatures and dwell, adjusted for humidity and cloth weight.
- The reasons behind each setting and the fixes for pinholes, delamination, tacky faces and edge curl.
Most of this is real knowledge, built over years of trial and error. Little of it is written. What is written is often a bare recipe card that lists numbers but not the reasons or the adjustments.
How the risk shows up
The first sign is a long wait. Operators stop the coating line to call the engineer, who is in the lab or at a customer. The second sign is scrap: a roll of coated cloth that fails the peel test, cut to remnants. The third is a customer complaint on a batch that was made on his day off. And the last sign is the quiet one, when a competitor offers him a role and he leaves with every recipe still in his memory.
Why recipes stay in heads
There are several reasons. Engineers who write everything down fear that they become replaceable. Owners who ask for documents do not want to pay for the time. The line never stops long enough for a trial run to be recorded. And the recipe shifts with every new base cloth lot, so a written version feels stale at once.
Turning the head into a record
- 1
Choose the three products that earn the most
Do not try to capture everything. Begin with the three coated fabrics or nonwovens that carry most of the order book.
- 2
Shadow the engineer for two full runs
A junior process technician stands beside the line with a notebook and a stopwatch. Write the settings, the reading of the paste and the reason for each change.
- 3
Write the recipe card with reasons
Each card has the target weight, the paste mix, the viscosity window, gap, speed and oven zones. Beside every number, one line says why and what to change if the cloth runs heavy or the paste thins.
- 4
Test the card with someone else
A second technician runs the product from the card while the engineer watches. Every point where he is asked a question goes back onto the card.
- 5
Store, date and review
Keep the card where the line crew can read it, with the date of the last review. Revisit after any change in resin, base cloth or oven.
The learning and development page for technical textile makers describes how to turn that shadowing into a repeatable training path. The role design page helps set out what a process technician, coating operator and lab assistant should each be able to do.
Where the line crew fits in
Coating operators, oven attendants, the paste mixer and the roll inspector see things the engineer misses. The inspector notices a faint edge curl before the roll leaves the winder. The oven attendant feels a draught from a bad damper. The mixer knows when a drum of resin is a degree colder. Let each of them add a line to the card in their own words. Cards written by the whole crew get used. Cards written by one man gather dust.
Lab hands matter as well. The lab assistant runs the peel strength tester, the hydrostatic head rig and the Martindale style abrasion wheel. Those numbers show whether a recipe is holding. Give that role a seat at the review. Let the lab keep retained swatches from each run. Label them with roll number, paste batch and oven log, so any complaint traces back to a card.
Making the engineer a willing teacher
An engineer will teach if he feels safer for it. Name him as lead of the recipe library. Give him a role title that says so, and tie a part of his reward to the number of recipes recorded and tested. The compensation page for technical textile makers discusses pay that recognises such work. Add a second tier of growth for the juniors he trains, so the unit has a bench of at least two people on every key product.
Signs the unit is moving the right way
- Two hands can start up each of the top three products.
- Recipe cards carry reasons and a review date.
- A coating run does not stop when the engineer is absent.
- Customer complaints on first-time batches fall, as the unit sees them.
- The engineer asks to teach.
To turn one engineer's knowledge into a recipe library and a training path, describe your unit in the requirement form.
