Specify a shielded harness by its complete shield path, including both ends and every detachable interface. Identify the cable shield, its termination at each connector, the connection through mating shells, and the intended equipment reference. A drain-wire connection and a circumferential shield termination describe different physical arrangements; neither phrase alone establishes the electromagnetic performance of the finished equipment.
The buying decision is not simply whether a cable contains foil or braid. It is whether the delivered assembly reproduces the design owner's approved shielding arrangement, with evidence for the exact cable, connectors and installation boundaries. A harness can have the correct signal pinout and still differ from the intended shield topology.
This guide covers procurement of shielded control, instrumentation and communication harnesses. It does not prescribe a universal rule to ground one end or both ends, and it does not provide instructions for energized testing. Equipment design, protective bonding and EMC acceptance remain the responsibility of the qualified project team. For the entry hardware itself, use the separate EMC cable gland selection guide; the focus here is the assembled path across cables, connectors and equipment boundaries.
Separate the shield, drain wire, pigtail and connector shell
A shield is the conductive layer around a cable core or group of conductors. A drain wire is a separate conductor associated with a shield construction. A pigtail describes a short wire-like extension used to take a shield connection to another point; it may be made from a drain wire or from gathered braid. A connector shell is the connector's outer structure, which must be assessed separately from its signal contacts.
Belden's industrial cabling technical information, printed page 250 describes foil shields and drain wires used to simplify their termination, as well as woven braid constructions. The procurement implication is to identify the actual cable layer being connected. A drawing that says only “shield to terminal” leaves open whether production should use the drain, braid, an approved sleeve or another specified feature.
Do not turn these definitions into a material preference without application evidence. The useful question is whether the quoted cable construction matches the selected termination method. A connector instruction written for exposed braid does not automatically cover a cable with only foil and a drain. Similarly, finding a drain inside a cable does not authorize replacing a specified backshell clamp with that drain.
Use a cable cross-section and an end-preparation detail to remove ambiguity. Identify overall and individual pair shields separately. If a cable has more than one shielding layer, assign each layer its own identifier rather than placing all of them under a single “screen” note. This makes unintended joins visible during drawing review.
Define the performance question before comparing connection styles
“EMC compatible” is too broad to serve as a purchase acceptance criterion. Ask which equipment function must remain satisfactory, what installation is being represented, and which engineering verification document controls the result. The answer might concern a communication port, a sensor input or emissions from the equipment. Each needs a traceable configuration rather than a generic certificate for a cable family.
Analog Devices' hardware design handbook, section 8, printed page 8.84 explains that a single-wire pigtail may fail to provide low impedance at high frequency, and includes connector interfaces in the shielding system. It favors circumferential contact at the chassis interface for that context. This supports asking about geometry and connector continuity; it does not establish a universal pass limit or approve a particular harness.
Phoenix Contact's shield connection guidance for control cabinets likewise explains why ohmic contact resistance alone is insufficient: connection impedance varies with frequency and geometry. Its guidance also distinguishes directly grounded and insulated support arrangements. A continuity result should therefore be labeled as a connectivity result, while the design owner specifies any additional evidence needed for the actual interference environment.
The RFQ should name the controlling equipment requirement and ask bidders to disclose assumptions. If that requirement is not yet available, purchasing can compare documented construction and request samples, but should not describe the assembly as EMC qualified. Keep the unresolved requirement explicit until the responsible engineer supplies a disposition.
Draw the complete path and mark the delivery boundary
Create one simple interface map before issuing the RFQ. Start with the shield identifier in the cable drawing and continue through each component that the design expects to connect. For a detachable assembly, the map may include a braid capture feature, backshell, plug shell, mating receptacle shell and equipment mounting interface. Some applications intentionally use a different arrangement; the map must show the approved design rather than forcing this sequence.
The delivery boundary matters commercially. A harness supplier may deliver the cable and plug, while a cabinet builder provides the receptacle and mounting plate. If no one owns the interface between them, both suppliers can meet their separate drawings while the assembled path remains undefined. Assign a named document owner to every boundary crossing.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Map element | Record in the RFQ | Evidence to request | Decision if missing |
|---|---|---|---|
| Cable shield layer | Cable code and layer identifier | Controlled cross-section | Hold cable substitution |
| Shield to termination | Preparation and capture detail | Applicable assembly instruction | Hold first-article release |
| Termination to shell | Backshell and shell order codes | Interface drawing or manufacturer statement | Review the complete connector set |
| Plug to receptacle | Both mating part numbers | Mating-interface evidence | Do not infer from similar appearance |
| Receptacle to equipment | Mounting and surface detail | Equipment drawing reference | Assign the equipment-side owner |
| Intentional isolation | Location and rationale reference | Approved topology document | Do not add an unapproved bridge |
Add connector orientation and end labels to the map. “Left” and “right” can reverse when a cable is installed, photographed or laid on a bench. End A and End B should refer to marked equipment identities, while connector cavity views follow their own drawing convention. The harness pinout and cavity-view guide helps control those signal identities alongside the separate shield map.
Also show any intermediate adapter or extension. A quoted harness may be correct on its own but installed through an adapter that changes the shell path. Record whether such accessories are inside the validated configuration, outside the supplier's delivery scope, or prohibited without review. A photograph of a finished cable cannot resolve this installation question.
Add a shield netlist for branches and hidden interfaces
A shield netlist is a connection schedule for the shield system, separate from the signal pinout. Give every shield layer, shell and designated shield contact a unique node name. Show connections that are required and connections that are intentionally absent. This allows the inspection plan to check the design intent instead of assuming that all accessible metal should be joined.
The following entries are hypothetical documentation examples, not an approved electrical architecture. They illustrate how a buyer can turn a verbal description into an explicit question set.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Example node pair | Drawing intent | Required clarification before release |
|---|---|---|
| Overall shield S0 to plug shell A | Connected through capture set | Identify the complete capture and shell parts |
| Plug shell A to receptacle shell A | Connected when mated | Identify the matching receptacle and interface evidence |
| Pair shield S1 to overall shield S0 | Isolated in this example | Define the insulated end detail and inspection coverage |
| Branch shield S2 through junction J1 | Connection status unresolved | Obtain an engineering decision and revised netlist |
| Drain D0 to signal return R0 | No connection shown | Confirm that the absence is intentional before building |
For a branched harness, mark where the overall shield divides and which shielding continues into each leg. Ask whether a shield splice, sleeve or enclosure interface is specified at the junction. A common signal splice does not answer the shield question. Require separate identifiers for any pair shields that must remain distinguishable, and resolve how their identities are preserved after the breakout is covered.
For an overmolded junction, request evidence before encapsulation: component identities, connection schedule revision and the agreed inspection record. The outer molded shape cannot reveal the buried shield architecture. If the supplier proposes a different internal join while retaining the same outer geometry, treat that as a disclosed change requiring review, not an invisible manufacturing preference.
Also identify the fixture coverage boundary. A fixture may reach connector contacts while leaving shells or isolated shield nodes unobserved. Ask the quality plan to list what it can verify, what needs in-process evidence and what remains an equipment-level activity. This avoids accepting a complete-looking report that never addressed the interfaces unique to the shield system.
Compare termination arrangements without declaring a universal winner
The following table is a comparison of evidence requirements. It does not rank the arrangements by a universal shielding value, and it does not authorize exchanging one for another.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Arrangement offered | What the description establishes | What still needs evidence |
|---|---|---|
| Drain landed on a dedicated contact | A defined conductor reaches a contact location | Drain identity, shell relationship and approved system topology |
| Gathered braid used as a pigtail | Braid is extended to a separate point | Prepared length, routing, restraint and application approval |
| Braid captured around a backshell interface | A circumferential contact method is proposed | Cable compatibility, capture geometry and the rest of the shell path |
| Shield connected at an entry clamp | A connection is made before internal fan-out | Clamp assembly, reference structure and downstream shield treatment |
| Shield intentionally isolated at one end | An intentional topology is proposed | Approved end detail, insulation method and verification requirement |
A useful supplier response identifies the applicable row, then adds the exact parts and drawing detail. An unhelpful response repeats “360 degrees” without showing where the contact occurs. A circumferential clamp at one end also says nothing about an unshielded adapter farther along the assembly.
Treat a dedicated shield contact as its own interface. Ask whether it connects to a shell, a terminal board or another defined node after mating. Do not equate that contact with a protective earth terminal or signal return because they share a connection symbol in an informal sketch. Resolve symbols and functions in the controlled circuit documentation.
Do not make purchasing staff choose between single-ended and both-ended bonding based on internet slogans. Ask the equipment design owner to specify the intended topology, including any approved isolated or frequency-dependent arrangement. If two equipment manuals appear to conflict, obtain an integration decision before authorizing production. The cable assembler should receive an unambiguous build requirement, not an unresolved design debate.
Build a preparation detail that production can reproduce
The preparation drawing should show which layers are removed, retained, folded, captured or insulated at each end. Reference the selected connector manufacturer's instructions rather than copying a strip length from another connector family. Include the measurement datum and tolerance for every controlled dimension. A note such as “short drain” is not a measurable requirement.
Specify the treatment of unused drain wires and shield layers explicitly. An unused drain should not be left to an operator's preferred practice. The approved detail needs to define its cut or retained length, insulation, restraint and separation from other contacts. These requirements belong to the design drawing; the article does not prescribe one universal treatment.
For captured braid, request evidence of the prepared cable condition before the interface is closed. The acceptance document should identify permitted preparation features and unacceptable damage for that selected assembly. For a wire termination, require the terminal and conductor combination, tool reference and applicable assembly instruction. Do not assume that a terminal approved for a signal conductor also accepts the drain construction.
Consider repair access while the drawing is still editable. If a backshell is opened during servicing, state which components may be reused, which preparation steps must be repeated, and which inspections become necessary. A supplier should not invent a repair method after a failed inspection merely because replacement parts are inconvenient to obtain.
Route and restrain the cable according to the complete assembly requirements. The strain-relief and bend-radius guide addresses that mechanical planning. A shield contact feature should not be assumed to provide cable pull relief unless the selected assembly's instructions establish that function. Keeping the two requirements separate makes both the quotation and the inspection plan clearer.
Send the cable cross-section, connector list and proposed shield map for an RFQ.
Ask for evidence at three different levels
Organize the supplier's submittal into component, assembly and equipment evidence. A cable data sheet answers different questions from an assembled-harness inspection record. An equipment EMC report answers a different question again. Mixing these records creates apparent coverage without showing whether the offered configuration was represented.
At component level, collect cable identification, connector ordering codes, backshell instructions and any exact accessory references. Check document revisions and the conditions attached to manufacturer statements. A family brochure is useful for orientation, but the offer must identify which member of that family will be delivered.
At assembly level, request the controlled drawing, bill of materials, preparation photographs, inspection plan and traceability between the sample and those documents. If continuity or resistance is specified, the approved procedure needs to identify its endpoints, acceptance rule and record format. The buyer should be able to tell whether the record covers the drain, shell path or another circuit.
At equipment level, ask the design owner to identify which report or planned verification establishes suitability in the intended installation. Record the represented cable length, connector arrangement, routing and equipment configuration where relevant to that evidence. A report from a different harness may be informative, but its applicability needs an engineering assessment rather than a purchasing assumption.
The harness continuity, insulation resistance and dielectric testing guide explains how to keep electrical inspection purposes distinct. Here, the key buying rule is narrower: do not relabel a continuity pass as an EMC pass. No test values or live test methods are prescribed by this guide.
Use a hypothetical bid comparison to expose scope differences
The following example is hypothetical. Assembly H-042, document identifiers, offers and dispositions are invented to demonstrate purchasing decisions. They are not SINAWATTS products, customer cases, test results or recommended electrical limits.
The buyer's design package describes a shielded communication harness connecting a removable control module to an enclosure interface. Drawing H-042 revision C specifies the shield arrangement at both ends. The removable interface requires a particular circumferential capture assembly and identified mating shells. Equipment verification remains a separate release activity owned by the integrator.
Three bidders respond with similar descriptions of conductor count, overall cable length and connector contact count. Those similarities are insufficient for interchangeability. The buyer compares the response against the shield map instead of selecting the lowest cable price first.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Review field | Bid A | Bid B | Bid C |
|---|---|---|---|
| Cable identity | Matches drawing C | Alternate cable disclosed | Matches drawing C |
| End A termination | Specified capture set | Drain to spare contact | Specified capture set |
| End B detail | Complete drawing reference | “Same as sample” | Complete drawing reference |
| Mating shell evidence | Both part numbers supplied | Receptacle unspecified | Both part numbers supplied |
| Hidden preparation record | Proposed in-process images | Final external photograph only | Proposed in-process images |
| Equipment evidence scope | Integrator-owned, stated | Generic EMC claim | Integrator-owned, stated |
| Purchasing disposition | Proceed to defined sample review | Hold for design deviation review | Clarify accessory revision |
Bid B is not rejected merely because it uses a drain. It is held because it changes the approved topology, omits the mating receptacle and provides no evidence resolving the deviation. If engineering later approves a revised arrangement, the drawing and verification plan must change together. Purchasing should not approve the substitution by attaching the original drawing to the new offer.
Bid C proposes the correct functional arrangement but cites an older accessory instruction. The buyer requests confirmation that the supplied parts and current instruction are compatible with drawing C. This is a smaller documentation issue than Bid B's design change, yet it still needs closure before production release.
Bid A has the most complete initial package, but it has not thereby passed equipment EMC verification. Its disposition allows the defined sample review to proceed. Separating “documentation complete,” “sample accepted” and “equipment released” avoids turning a procurement milestone into an unsupported performance claim.
A filled clarification record
For Bid B, the buyer opens clarification Q-17 with the subject “End A shield path differs from H-042 revision C.” The requested response is a marked drawing showing the proposed drain contact, its destination after mating and the treatment of the unused capture interface. The response owner is the bidder; the approval owner is the equipment engineer.
The record states “status: open; production release: blocked for this deviation.” It requests an applicability assessment and revised sample requirements rather than specifying a desired test result. The commercial offer remains under review, with the alternate cable and added engineering work shown as separate lines. This preserves a usable negotiation trail without implying that the alternate is either technically acceptable or inherently defective.
Make first-article evidence useful after the connector is closed
Choose evidence points where the important features are visible. A finished connector photograph cannot show the shield layer captured inside a backshell. Ask the supplier's quality team to propose an in-process record that links the prepared end, installed termination and final assembly to the same sample identifier.
The first-article package should reconcile drawing requirements with actual parts. Check that cable jacket markings, connector packaging identifiers and accessory codes agree with the submitted bill of materials. Where an item lacks a visible mark, use the agreed traceability method instead of assuming that identical appearance proves identity.
Record the state of both ends. An attractive photograph of End A does not demonstrate the isolated treatment or connection at End B. Include any intermediate branch, splice or adapter covered by the delivered assembly. Identify which images are representative process examples and which belong to the actual first article.
Define how deviations are handled before samples arrive. Possible dispositions include correction, replacement, design review or a documented concession with a defined scope. A concession should identify affected serial numbers or lots and its expiration or review condition. It must not silently become a permanent alternate drawing through repeated acceptance.
Control changes that look harmless on a purchase order
A replacement connector shell, different cable source or revised backshell can change the interfaces that the original evidence represented. Ask suppliers to notify the buyer of such changes before delivery. The notification should describe the affected drawing features, not merely state that form, fit and function are unchanged.
Include preparation and assembly changes in the control plan. A new stripping method, different shielding sleeve or altered drain routing can produce a different assembly even if the top-level part number remains constant. Require the supplier to identify which existing evidence still applies and what additional review is proposed.
Separate commercial alternates from approved production alternates. A second source listed for quotation is not automatically authorized for shipment. Keep a revision-controlled list showing the approval status of each cable, connector and termination combination. Approving individual components does not necessarily approve every combination of those components.
For field replacements, preserve assembly identity on service documents. A maintenance team should be able to distinguish the approved harness from a physically connectable alternative. Request a replacement reference that includes any required mating accessories and installation instructions, while leaving equipment isolation and service procedures to the responsible technical team.
Compare total quotation scope rather than a shield label
Ask bidders to separate sample preparation, special termination accessories, agreed inspection records, traceability and any engineering work from recurring assembly cost. This helps explain price differences without assuming that the more expensive arrangement has better performance. The scope of verification may be a larger difference than the cable itself.
State forecast quantities and packaging needs as buyer inputs. Ask the supplier to quote minimum order quantity, schedule and any tooling conditions explicitly; none can be inferred from this guide. For shared or confidential equipment drawings, agree how revisions and access will be controlled before distributing the full package.
Use the OEM and ODM project page as a starting point for a project inquiry, then attach the exact technical package. A useful request includes cable construction, both mating interfaces, the shield map, applicable instructions, installation boundary and unresolved questions. It should also identify who can approve a topology change.
Buyer FAQ
Is a drain wire the same as a cable shield?
No. The drain is a conductor associated with a particular shield construction; the shield is the conductive layer around the cable core or conductors. Identify both on the cable drawing. The presence of a drain does not by itself define how either end of the assembly should be terminated.
Is a 360-degree shield connection always better than a drain-wire termination?
It is not a universal purchasing rule. Circumferential interfaces are important in many high-frequency shielding arrangements, but the acceptable construction depends on the equipment requirements and approved topology. Compare the complete assembly and its supporting evidence, rather than replacing one termination solely because another has a stronger marketing description.
Should the shield be grounded at one end or both ends?
Follow the equipment design owner's documented arrangement. The answer depends on the application, interfaces and bonding design. Purchasing should obtain that decision before release and pass it to the assembler without ambiguity. This article does not authorize disconnecting protective conductors or adding unapproved shield connections.
Does a continuity pass prove that the harness meets EMC requirements?
No. It establishes only the result covered by that particular connectivity procedure and its endpoints. EMC suitability requires the evidence specified for the equipment and represented installation. Keep component documentation, assembly inspection and equipment verification as separate approval records.
Can we substitute a shielded connector with the same contact count?
Not on contact count alone. Review the mating connector, shell path, shield capture method, cable compatibility and applicable instructions. The signal pinout may match while the shielding arrangement differs. Obtain a documented deviation decision before authorizing a changed connector combination.
What should determine the price and delivery comparison?
Compare the same drawing revision, components, inspection scope, records, quantity and packaging requirements. Ask each bidder for its actual price, minimum quantity and schedule. A lower quote that omits backshell accessories or first-article evidence is not yet an equivalent offer; clarify the missing scope before comparing totals.
What information is needed when the shield drawing is incomplete?
Send the cable cross-section, both equipment interface references, proposed connector codes and a list of unresolved decisions. Identify the engineering owner for the shield topology and acceptance requirements. Request a marked proposal with assumptions rather than allowing production to fill the gaps informally.
Prepare a shield-termination RFQ that can be released
Before issuing the final order, confirm that the quoted assembly, interface map and verification plan describe the same configuration. Close unresolved topology questions, preserve approved end details, and state the boundary between harness delivery and equipment integration. Keep the first-article records linked to the approved revision so future substitutions can be assessed against a known baseline.
Send your shield map, cable drawing and mating connector details for a harness RFQ.