What Key Terms Should I Specify in a Multi Cable Transit Purchase Contract?

A vague [multi cable transit purchase contract](https://dewinmct.com/?p=528) nearly cost one of our EPC customers a commissioning date. Our engineers rewrote the scope with them. Here is what we specify now.

A multi cable transit purchase contract should specify scope of supply, fire and IP ratings with test documents, frame and module dimensions for drop-in fit, delivery dates with transit risk allocation, warranty start point, acceptance criteria, spare module lead times, and free validation samples plus CAD files.

Below, I break each of these terms into contract language you can copy, adjust, and hand to your legal team. I focus on four areas where I see the most disputes.

What Certification and Test Documentation Should I Require Before Signing?

Last quarter a sourcing manager in Germany asked us for our BV factory approval before he would open our price sheet. I respected that. Documents first is the right order.

Require fire test reports for the stated rating such as A-0 or A-60, IP68 ingress test records, watertight and gas-tight pressure test data, EN 10204 3.1 material test certificates for frames, a Certificate of Conformance per batch, and ISO 9001 or IATF 16949 quality system certificates before signing.

The most common mistake I see is a contract that says "supplier shall be certified" and nothing more. That sentence is not enforceable. It does not say certified for what, by whom, or to which test condition. Your contract needs to name the document, the standard, and the rating that your barrier actually needs.

Match the rating to the barrier, not the brochure

Fire resistance ratings for a BESS container wall are not the same as ratings for an offshore bulkhead ¹. A-0 or A-60 covers most enclosure and container work. H-120 and jet fire ratings belong to hydrocarbon process areas. If you write H-120 into a data center contract, you pay for testing you will never use. If you leave the rating out, you accept whatever the supplier ships. On our side, we test to A-0 and A-60, so I always ask the buyer which one their fire plan calls for.

IP rating requirements follow the same logic. IP67 covers temporary immersion. IP68 covers continuous immersion ² at a defined depth and time. Our modules carry IP68, and I recommend you write the test depth and duration into the annex rather than the IP code alone. Water and gas tightness should also be stated as a pressure range. Our sealing systems are tested from 0.01 to 0.4 MPa. Write your working pressure and your test pressure as two separate numbers.

The document table I put in every quotation

Two more items deserve a line in the annex. First, ask for halogen-free material declarations for the EPDM. Our modules are halogen-free, and buyers in Europe usually need that on paper for smoke toxicity reasons. Second, if the penetration sits in an EMC enclosure, ask whether electromagnetic shielding is part of the module design, because standard rubber modules do not provide it.

One buyer objection I hear often: "The supplier's general certificate covers all their products, so we do not need project-specific documents." That is a real risk. A quality system certificate proves a process exists. It does not prove your frame size at your pressure passed a test. Ask for the report that matches your configuration. We keep ours ready and send them on request.

How Do I Specify Dimensional Compatibility for Drop-In Replacement in the Contract?

On our Shaanxi line, every TSC module batch gets a gauge check against the 120-frame cutout drawing before packing. That habit came from a mismatch we caught years ago.

Specify the reference frame standard, frame internal opening dimensions with tolerances, module heights and widths per size, stay plate and compression unit dimensions, cable diameter range per module, and attach a model cross-reference table listing the existing model number against the replacement DEWIN model.

Drop-in replacement is the whole point of second sourcing. If the module does not fit the existing frame cutout, the 40–60% cost saving disappears in rework. So the contract must describe fit in numbers, not in the word "compatible."

A five-step process for writing the compatibility clause

1. Name the reference standard. Write "dimensionally compatible with the 120-frame system" and attach the frame drawing you already use. Do not rely on a brand name alone.
2. State the frame opening. Give the internal width and height with a tolerance band. Our TSC square modules and TSR round assemblies are made to drop into common 120-frame cutouts, but I still want your drawing on file.
3. Define the module stack. List each module size, its nominal height and width, and how many fit per row. Include stay plate thickness. The compression unit height matters most, because it sets the final stack-up.
4. Attach the cross-reference table. This is the document that lets your quality team approve us as a second source without opening every box. It maps existing model → DEWIN model, size by size.
5. Define the cable range per module. Our step-core EPDM modules accept a range of cable diameters within one module size. Write the minimum and maximum diameter per module into the annex so the installer knows which layer to peel.

What the contract table should contain

That last row is easy to forget. Ask for a guaranteed spare space ratio inside each frame, filled with blank modular sealing blocks. When the cable schedule grows, and it always grows, the installer swaps a blank for a cored module instead of cutting a new opening.

A buyer once told me, "Same nominal size means it fits." Not always. Two modules can share a nominal size and still differ in compressed height by a millimeter or two. Over a stack of ten modules, that error stops the compression unit from seating. That is why I insist on the full stack drawing, and why we ship free validation samples before any production order.

What Lead Time and Delivery Terms Should I Lock In for Spare Modules?

Keeping finished spare modules in stock costs us warehouse space. Making every one to order costs the customer weeks. We chose stock for common sizes.

Lock in a firm lead time per module size in working days, an Incoterm that names who carries transit risk, a delivery date stated as of the essence, a minimum spare module ratio, a defined remedy for late delivery, and export documentation as a supplier obligation.

A late spare module can block a cable pull, a firestop sign-off, or a container hand-over. So delivery is not a commercial detail in a multi cable transit purchase contract. It is a performance term.

Write time as an essential term

Public procurement templates often state that delivery time is "of the essence" and that the schedule cannot change without written approval. I recommend the same wording for private buyers. It gives you leverage if the supplier slips. Pair it with a remedy. Liquidated damages per week of delay, a right to source replacement modules elsewhere at the supplier's cost, or termination for default are all common. The termination clause should define default clearly: failure to deliver on time, or failure to make progress that endangers performance.

Allocate transit risk in writing

Bulky frames and rubber modules can be damaged in transit. Some contracts put transit risk ⁴ on the supplier. Others place transit insurance under the buyer's policy but still require the supplier to send dispatch details. Both work. What fails is silence. Use the Incoterm and then say who insures.

Warranty should start when the seal starts working

Here is a common objection from supplier side: "Warranty runs from the ship date." I understand why suppliers want that. But an MCT can only be proven under installed compression. So I advise buyers to tie warranty and performance guarantees to commissioning or handover, with a cap on how long the start can be delayed. Spell out duration, response time, and whether replacement modules ship free. On our side, fast spare module delivery is part of the offer, so a clear warranty trigger costs us little and gives you real protection.

Finally, include a changes clause. Cable counts change after design freeze. A clause that allows scope changes within the contract, with an equitable price and schedule adjustment, prevents every added penetration from turning into a dispute.

Should I Request Free Validation Samples and CAD Files Before Finalizing the Order?

We learned the hard way that a STEP file ⁵ answers more questions than a 20-page spec sheet. Now we send both before quoting on any second-source project.

Yes. Request free validation samples of each module size plus native CAD or STEP files before finalizing the order, and write into the contract that production parts must match the approved sample and drawing, with sample approval recorded as a formal acceptance milestone.

Samples and files are not a favor. They are the cheapest form of risk control available to a purchasing engineer. A sample lets you test fit in your own frame. A STEP file lets you check the stack-up in your CAD model before a single bolt is turned.

What to check on the sample

Put the sample into a frame you already own. Peel the step-core layers to your smallest and largest cable diameter. Compress the stack with your existing compression unit. Then answer three questions. Does the compression unit seat fully? Does the rubber show any gap at the cable surface? Does the blank module sit flush with the cored ones? If any answer is no, you have saved yourself a production order.

Make the sample a contract document

Write "production parts shall conform to approved sample no. X and drawing revision Y." Then acceptance has an objective reference. Public procurement guidance separates award, inspection, and final acceptance into distinct events, and I think private buyers should copy that discipline. Sample approval is the first event. Delivery inspection against the Certificate of Conformance is the second. Installed test is the third.

Ask for the digital deliverables too

Modern buyers ask for more than a STEP file. BIM metadata and asset data for facility management software are now common handover items on data center and infrastructure projects. A transit register listing each penetration, its location, cable type, and inspection history should be a required deliverable, and the CAD data feeds it. If the MCT carries integrated sensors for monitoring, the contract should also state data protocol and encryption requirements. For most container and switchgear work, that is not needed, but the clause costs nothing to include.

One more line worth adding: installation supervision or installer training from the supplier. Our engineers provide English technical support and drawings for exactly this reason. A correctly specified module still fails if it is compressed wrong on site.

Conclusion

Vague contracts create late seals, failed audits, and cost overruns. Specify documents, dimensions, delivery, and samples in numbers. Then your second source becomes a real one.

Footnotes

1. IMO safety page covering fire protection standards like A-60 for marine vessels. ↩︎

2. Authoritative IEC explanation of IP ratings for ingress protection standards. ↩︎

3. ISO standard for supplier declarations of conformity and quality documentation. ↩︎

4. Official ICC resource defining Incoterms for international trade and risk allocation. ↩︎

5. ISO standard page for the STEP file format (ISO 10303) used in CAD. ↩︎