Industrial Heavy Copper PCB: Turning Operating Environment Into a Quotable RFQ Declaration | PCB168

!Operator at the articulated touchscreen of a cream-panelled V-CUT depanelling machine on a production floor, with a red-amber-green stack light overhead and a green A-frame rack of copper-clad arrayed panels separated by bright green sheets in the foreground.

"Industrial grade" is a category, not an input

Most heavy copper RFQs that mention environment do it in one line. *Industrial control application.* *Automotive, under-hood.* *Welding equipment, harsh duty.* Then the specification moves straight to copper weight and layer count, and the environment line is never referenced again.

That line is not useless, but it is not an input either. It tells us what family of decisions you are in; it does not tell us anything a quotation can consume. Two boards both labelled "industrial control" can require different base material, different finished thickness, different surface finish and different acceptance evidence — and the label does not distinguish them.

The practical problem is that operating environment arrives as a *use case* while a quotation is built from *declarations*. Somebody has to do the translation. When the RFQ does not do it, one of three things happens: the quotation silently assumes a baseline, the engineering review pushes the schedule while we ask, or the board is built to a baseline and argued about on arrival.

This article sorts operating-environment items into three buckets, because they are genuinely not the same kind of information:

• Bucket A — directly consumed at quotation. The fabricator reads it and it changes the build or the price. Declare these as values or ranges.
• Bucket B — must be translated into material and structure first. The raw environment figure is not actionable; the material grade, thickness, finish or construction it implies is. Declare the translation, or declare the environment *and* ask for the translation in writing.
• Bucket C — closeable only by a defined test or inspection requirement. No amount of environmental prose covers these. If you want evidence, you have to say what will be measured, on what, and what record you receive.

Getting an item into the wrong bucket is the most common failure. A vibration description in Bucket A does nothing, because there is no fabrication parameter it maps to. A base-material choice left in Bucket C does nothing, because no test recovers a material decision made six weeks earlier.

Bucket A: the environment items a quotation actually consumes

These are the items where a number or a range changes what gets built. If your RFQ contains nothing else from this article, contain these.

Load character: continuous, intermittent, or pulsed

Copper weight is usually settled before the RFQ is written, and this article does not re-derive it — the derivation of copper weight from current and temperature rise is handled separately in our copper weight decision guide. What matters *here* is that load character is an input you probably already know and probably have not written down.

Say which of these applies, in one line each:

• Continuous rated load, or duty-cycled with an approximate on/off pattern
• Whether inrush, short-circuit or fault current is expected to pass through the same copper
• Whether the board sees load while the enclosure is already at its upper ambient

You do not need to supply a thermal analysis. You need to state which case the copper is being sized for, because "the copper weight was chosen for continuous load" and "the copper weight was chosen for a short duty cycle" are different specifications wearing the same number.

Ambient temperature range as a declared range

Declare the operating ambient range and, separately, storage or transport range if it is materially different. A range is consumable; "high temperature" is not.

Two cautions. First, do not confuse operating ambient with the assembly thermal excursion — a board that sees reflow and possibly rework has a separate thermal history that belongs with the assembly requirement, not the operating declaration. Second, do not translate the range into a material grade yourself unless you have a reason to. Stating the range and asking for the recommended base material in the quotation keeps the reasoning visible to both sides.

Mechanical envelope, mounting and finished thickness

This is where environment stops being abstract. The board has to fit, mount and survive handling in a real enclosure.

Declare finished thickness with tolerance, outline with datum reference, mounting hole positions and whether any of them are plated or connected, keep-out zones for enclosure features, and whether the board is fitted with fasteners that clamp it against a heatsink or chassis. Our heavy copper process runs 0.8–6.0mm finished thickness at 1–16 layers with 3–20oz copper (source: /en/products/heavy-copper-pcb/); the broader shop window is 0.2–6.0mm across 1–40 layers with a maximum panel of 600×1100mm (source: /en/capabilities/). Thick-copper constructions consume thickness quickly, and the interaction between layer count and copper weight has its own limits, covered in our layer count and copper weight article.

If the board is clamped, say so. Clamping is an environmental load, and it is one a fabricator can act on, because it bears on thickness tolerance and on where you can afford to put features.

Creepage, clearance and isolation requirements

If the design carries mains or high-voltage sections, the isolation requirement is a Bucket A item, not a design detail to be discovered from the Gerbers.

Declare the working voltage between the sections that must stay isolated, the pollution degree and altitude assumption if your design was laid out against IEC 60664, and any tracking-resistance requirement for the base material. High-CTI material above 600V is on our published material list (source: /en/capabilities/), so a CTI requirement is answerable at quotation — but only if you state it. It is not inferable from a copper weight.

One more: if isolation is maintained partly by slots, routed channels or removed copper, mark those as functional features on the drawing. They look like cosmetic clearance to anyone who has not been told otherwise.

Bucket B: environment figures that need translating before they mean anything

These are the items buyers most often state *as environment* and then wonder why nothing changed in the quotation. The environment figure is real; it just is not a fabrication instruction. Somebody has to convert it into a material grade, a construction, a finish or a thickness — and that conversion is the thing that gets built.

Thermal environment to base material selection

An upper ambient figure plus a self-heating expectation does not select a laminate on its own. The selection is a judgement about how much thermal margin the construction needs across its life, and it interacts with lamination cycles, layer count and whether the board will be reworked.

What to do in the RFQ: state the operating ambient range and the load character (Bucket A), then either declare the base material you have qualified, or explicitly request the recommended grade in the quotation. Our heavy copper product page publishes FR-4 TG170/TG180 for thick-copper builds (source: /en/products/heavy-copper-pcb/); the broader material list covers FR-4 Tg135/150/170/180 along with Rogers, Taconic and Isola systems (source: /en/capabilities/). Those are two different page-level statements about two different scopes — a grade on the general list is not automatically available in a 20oz construction, and that specific combination is confirmed in engineering review.

The failure mode to avoid is declaring a temperature and assuming it selects a grade. It does not, and if you have already qualified a grade in a previous program, the RFQ should say the grade, not re-derive it from temperature.

Heat removal expectation to construction choice

If the environment includes a thermal path — a heatsink, a chassis mount, a cold plate — the relevant declaration is the *construction*, not the thermal environment.

State whether you expect a standard FR-4 build with thermal vias, a metal-core construction, or an insulated metal substrate. Aluminium-core and copper-core options plus Al₂O₃ and AlN ceramics are on our published material list (source: /en/capabilities/), and metal-backed work is covered on our aluminium PCB page. If you are still deciding, say that — "construction to be recommended, thermal path is chassis-mounted through the board" is a usable line. What is not usable is "must dissipate heat well".

Design-side methods for moving heat are a separate subject; we cover them in our thermal management article. This article stays on the declaration.

Humidity, condensation and contamination to finish and mask decisions

Humidity exposure translates into surface finish selection, solder mask coverage, and whether conformal coating is part of the assembly scope. Declare it that way.

Useful lines: whether condensation is possible in service, whether the board is in a sealed or vented enclosure, whether conductive dust or chemical contamination is expected, and whether conformal coating is required and who applies it. HASL, ENIG and OSP are published for heavy copper builds (source: /en/products/heavy-copper-pcb/), with the fuller finish list including immersion tin and immersion silver on the capabilities page (source: /en/capabilities/). Finish selection has shelf-life and assembly consequences, so it belongs in the RFQ rather than being left to default.

Cleanliness is where this bucket touches the next one. Ionic contamination testing is in our published quality item list (source: /en/capabilities/), but a humidity statement does not order that test. If you want the record, you ask for the test — which is Bucket C.

Vibration and shock to mechanical construction

This is the item most often mis-filed. A vibration or shock environment does not map onto a bare-board fabrication parameter, which is why declaring it in the fabrication RFQ alone changes nothing.

What it does map onto: finished thickness and stiffness, board outline and aspect ratio, mounting point count and distribution, whether stiffeners or metal backing are used, component retention strategy, and — on the assembly side — staking or bonding requirements for heavy parts. Declare those. If the environment is genuinely demanding and you need evidence, the closure is a defined test on an assembled unit, not a sentence in the fabrication package.

Automotive and other qualified-programme contexts

"Automotive" carries expectations well beyond the board environment: material control, change control, traceability and documentation discipline. Our heavy copper page lists automotive among the applications it serves (source: /en/products/heavy-copper-pcb/).

In RFQ terms, split the request. The environmental part belongs in the declarations described here. The programme part — change notification, traceability depth, documentation retention, first-article expectations — is a separate section, and we have written about the quality-system side in our automotive quality system article. This article does not restate those requirements; the point is only that naming a sector does not declare an environment, and an environment declaration does not cover a programme requirement. You need both, written separately.

Bucket C: what only a defined test or inspection requirement can close

The third bucket exists because of a specific disappointment: a buyer declares a demanding environment, receives boards, and discovers there is no evidence that anything was verified against it. Nothing was withheld. The environment declaration simply never asked for a measurement.

If you want a record, the RFQ has to name the requirement. Four things make a requirement executable — what is measured, on what specimen, against what criterion, and what document you receive.

Requirements that are answerable from our published quality item list (source: /en/capabilities/):

• Electrical continuity and isolation — 100% electrical test by flying probe or fixture. Relevant whenever isolation matters; ask for the pass record.
• Layer registration and internal structure — cross-section (microsection) on production or coupon material. Relevant when thick copper and many layers interact.
• Impedance where controlled — TDR measurement on coupon. Note the two published tolerances belong to different pages and scopes: ±10% on the heavy copper product page (source: /en/products/heavy-copper-pcb/) and ±5% on the capabilities page (source: /en/capabilities/). If your design has controlled-impedance signals alongside heavy copper, ask which applies to your stack-up rather than assuming the tighter figure.
• Plating and hole quality — X-ray inspection and cross-section evidence.
• Surface cleanliness — ionic contamination testing.
• Outer and inner layer conformity — AOI on every layer.

Requirements that belong to you, not to the published list: thermal cycling, humidity exposure, vibration or shock, functional test of an assembled unit, burn-in. These are customer-defined. Our assembly page is explicit that inspection plans and test requirements are confirmed in engineering review and written quotation (source: /en/products/pcb-assembly/), which is the correct place for them — but the definition has to originate with you.

Two boundaries worth stating plainly. First, we do not publish acceptance values for environmental stress conditions, so an RFQ line saying "must meet standard thermal cycling" has no counterpart to be accepted against; name the condition set or name the standard and the level. Second, a standard reference without a level is not a requirement. Citing IEC 60068, AEC-Q200, IPC-9592 or J-STD-001 tells us the framework; the level, duration and sample basis are what make it executable. Where a condition or level is outside what we publish, the answer at quotation is that it requires engineering review — which is a real answer, and better than a silent assumption.

For the broader mechanics of turning requirements into delivery evidence, our purchase specification and acceptance guide covers the document set, and the supplier process evidence article covers what to ask a supplier to demonstrate.

The translation table, in one place

If you take one artefact from this article, take this. Each row is an environment item, the bucket it belongs in, and what the RFQ line should actually contain.

The pattern across the table: Bucket A lines are values, Bucket B lines are decisions, Bucket C lines are requirements. An RFQ that only contains values gets a build with assumed decisions and no evidence. That is the whole failure mode this article exists to prevent.

A declaration block you can paste into an RFQ

This is deliberately short. It is not a questionnaire to be completed perfectly; it is the minimum that stops a heavy copper quotation from resting on assumptions. Unknown is an acceptable answer — a marked unknown gets asked about, a missing line gets assumed.

```

OPERATING ENVIRONMENT DECLARATION

1. Application and sector: ______
2. Load character: continuous / duty-cycled (pattern: ______)

Copper weight was sized for: ______

Inrush or fault current through the same copper: yes / no

1. Operating ambient range: ______ Storage/transport range: ______
2. Enclosure: sealed / vented / open Condensation possible: yes / no

Conductive dust or chemical exposure: ______

1. Base material: qualified grade ______ OR request recommendation: yes
2. Thermal path: none / thermal vias / metal core / IMS / to be recommended

Board clamped to heatsink or chassis: yes / no (locations: ______)

1. Finished thickness + tolerance: ______ Layer count: ______

Copper weight (finished/base, state which): ______

1. Isolation: working voltage between isolated sections ______

CTI requirement: ______ Functional slots/keep-outs marked on drawing: yes / no

1. Mechanical: mounting hole count/positions ______

Stiffener or metal backing: ______ Vibration/shock relevant: yes / no

1. Surface finish: ______ Conformal coating: required / not / by whom ______
2. Verification required (name level + specimen + record):

Bare-board items from published list: ______

Customer-defined environmental or functional tests: ______

1. Items we accept as "requires engineering review": ______

```

Line 7 deserves a note: state whether the copper weight is finished or base copper, because the two are not interchangeable and the distinction has its own acceptance consequences — we cover it in the finished vs base copper declaration article.

Where this leaves the quotation

A complete environment declaration does three things that a sector label cannot.

It removes assumed baselines. Every Bucket A value you state is one fewer default in the quotation. It makes the engineering review productive rather than remedial — the review discusses the two or three genuinely open items instead of reconstructing your whole application. And it makes acceptance possible, because Bucket C requirements written before the order create records that exist when the boards arrive.

It also surfaces infeasibility early, which is the cheapest time to find it. A combination of copper weight, layer count, thickness and isolation requirement that does not fit is better identified at quotation than at first article. Our published windows — 3–20oz at 1–16 layers and 0.8–6.0mm for heavy copper (source: /en/products/heavy-copper-pcb/), 1–40 layers and 0.2–6.0mm shop-wide (source: /en/capabilities/) — are the outer envelopes of each page's scope, not a guarantee that every combination inside them is available; specific combinations are confirmed in engineering review.

The companion input to this one is the connection interface: how current physically enters and leaves the board. Environment tells us what the board must survive; the interface tells us what it must connect to. Interface geometry, finish and ownership are declared against the published heavy copper window on our heavy copper PCB page. For multilayer constructions generally, see our multilayer PCB page; when you are ready with the declaration above, send it through our quote request or reach engineering via contact.

FAQ

Is "industrial grade" enough to specify a heavy copper PCB?

No. It identifies a family of expectations but contains no value a quotation can consume. Replace it with the Bucket A items — load character, ambient range, thickness and tolerance, isolation requirement — and state explicitly which decisions you want recommended.

Do I have to know the base material grade before sending the RFQ?

No, and stating a range plus requesting a recommendation is often the better route. What you should not do is state a temperature and assume it selects a grade. If you have qualified a grade in a previous programme, declare the grade rather than the temperature that led to it.

If I declare a harsh environment, does the fabricator test against it?

Not automatically. An environment declaration drives build decisions; it does not create test records. Verification requires a named requirement with a level, a specimen, a criterion and a record format. Bare-board items on our published list are answerable at quotation; environmental stress and functional testing are customer-defined and confirmed in engineering review (source: /en/products/pcb-assembly/).

Does vibration belong in a bare-board RFQ?

Not as a vibration figure. Translate it into the mechanical items a fabricator can act on: finished thickness, mounting point count and distribution, stiffener or metal backing, and component retention on the assembly side. If you need evidence of vibration survival, that is a defined test on an assembled unit.

Which impedance tolerance applies if my board has both heavy copper and controlled-impedance signals?

Ask, and get it in writing. The ±10% figure is published on the heavy copper product page and the ±5% figure on the capabilities page; they describe different scopes. Mixing thick copper with controlled-impedance routing is exactly the case where the applicable tolerance should be confirmed in engineering review rather than assumed.

Is naming "automotive" the same as declaring an environment?

No, and treating it as equivalent is a common source of scope disputes. The sector name implies programme requirements — change control, traceability, documentation — that are separate from the physical environment. Write both sections. The environment section uses the declarations in this article; the programme section states what change notification, traceability depth and documentation retention you need.

What if part of my requirement is outside what PCB168 publishes?

Then the honest answer at quotation is that it requires engineering review, and you should want that answer rather than a silent yes. Mark such items in line 12 of the declaration block so they are handled as open questions instead of assumed capability.