MCS Megawatt Charging Cable: IEC TS 63379 RFQ Checklist

Build an MCS cable RFQ suppliers can actually answer: acceptance criteria at 3,000 A class, liquid-cooling interface checks, and the evidence to demand.

The short answer: an MCS-class cable RFQ is only as good as the seven acceptance items you force the supplier to answer in writing. They are:

  1. Conductor design — copper cross-section, strand construction and current density at the 3,000 A class, not a headline amp figure.
  2. Temperature rise — the limit, where it is measured (contact, conductor, jacket), and the sensor architecture that reports it to the charger.
  3. Liquid-cooling interface — coolant type and concentration, rated flow, pressure drop, working and burst pressure, coupling specification.
  4. Mating-cycle life — the declared cycle count and the test conditions behind it.
  5. Touch safety and interlock behaviour — what happens electrically and mechanically on an incomplete mate or an interrupted disconnect.
  6. In-service inspection routine — interval, checklist, field-replaceable parts and withdrawal-from-service triggers.
  7. Documentary evidence for every line above — type-test report, routine-test record or third-party lab report, named and dated.

Everything else in this article is detail on those seven. Two caveats come first, because they change how you read every supplier claim you will receive.

Caveat one — scope. The IEC technical specification usually named for MCS coupler hardware (IEC TS 63379) is described by third-party sources as covering the vehicle connector, vehicle inlet and cable assembly, with requirements for the DC EV supply equipment set out in a separate document (IEC 61851-23-3). See the Versinetic EV charging glossary entry for IEC TS 63379. Treat that split as a question to confirm against the current published edition, not as settled fact — this article has not verified the standard text, its edition, or any clause-level limit.

Caveat two — the numbers. The figures circulating in 2026 (1 MW, 3.75 MW, 3,000 A, 1,250 V, 1,500 V) come from third-party publishers, not from verified standard text. A trade article on MCS rollout quotes up to 3.75 MW at 1,250 V and 3,000 A DC (innobu, MCS rollout 2026), while a vendor comparison table attributes a 1,500 V DC connector rating and up to 3,000 A to the IEC specification (Tridens). The two do not agree, and neither is a substitute for the published edition. That disagreement is precisely why the first RFQ question is documentary, not technical.

Step 1 — Fix the standard baseline before anyone quotes a price

Price comparisons across MCS-class assemblies are meaningless until every bidder is designing to the same document. Put three questions at the top of the RFQ and refuse to evaluate a quote that leaves them blank.

  • Which document, which edition, which part? Ask for the exact reference the assembly is designed and type-tested to, including year of edition. MCS runs on two parallel tracks — the IEC technical specification and SAE J3271 — and a supplier claiming both owes you two evidence sets, not one.
  • What is inside and outside the declaration? Connector only, inlet only, cable assembly only, or all three? Does the declaration explicitly exclude charger-side equipment? An ambiguous scope statement is the single most common way a "compliant" claim becomes unusable after commissioning.
  • Who issued the evidence? Self-declaration, an accredited test laboratory, or a notified body opinion? Accept a blog citation as a lead, never as proof.

CharIN is the industry alliance behind the MCS connector development and is the name to look for when a supplier describes its design lineage. Lineage is useful context; it is not a test report.

Step 2 — Conductor cross-section and current density at the 3,000 A class

"Rated 3,000 A" is not a specification. It is a conclusion that depends on ambient temperature, coolant inlet temperature, duty cycle and measurement point. Ask for the inputs.

  • Copper cross-section in mm², strand count and strand diameter, and the resulting current density at rated current.
  • Whether the rating is continuous at a stated ambient or short-duration, and at what coolant inlet temperature it applies.
  • A derating curve against ambient temperature and against coolant temperature, so you can test the claim against your depot's worst summer afternoon rather than a laboratory baseline.
  • The conductor insulation and jacket material, with the temperature class claimed for each.

If a supplier cannot produce a derating curve, you are not comparing cable assemblies — you are comparing marketing.

Step 3 — Temperature rise and the thermal sensing architecture

At megawatt-class current, thermal behaviour is a system property, not a cable property. The RFQ should specify four things:

  • Where temperature is measured — power contact, conductor, or jacket surface — because the same limit means different things at different points.
  • Sensor type and placement count, and whether sensing is part of the assembly architecture or added by the charger.
  • The signal path to the charger: analogue, digital, or via the communication protocol, and what the assembly does when the signal is lost.
  • The trip threshold and response time the charger will act on, agreed between cable supplier and charger supplier — this is an interface item and someone must own it in writing.

Demand the type-test record showing measured temperature rise at rated current with the specified coolant flow. A calculated estimate is a design intention; a measured record is evidence. Thermal sensing or thermal transport and sensing is described as part of the MCS system architecture in the glossary reference above — confirm how your chosen supplier implements it rather than assuming a default.

Step 4 — The liquid-cooling circuit interface (where most stranded assets originate)

This is the section that decides whether your cable works with your charger, your coolant loop and your maintenance regime. Write each line as a required answer, not a preference.

  • Coolant: chemistry and concentration (for example water-glycol ratio), permitted coolant brands or a specification the supplier will accept, and whether the assembly ships dry or pre-filled.
  • Hydraulics: rated flow, pressure drop at your target flow rate, maximum working pressure, burst pressure, and hose specification including bend radius.
  • Coupling: dripless or not, material, connect and disconnect force, thread or quick-release standard, and whether the coupling is a proprietary part or an interchangeable one.
  • Leak testing: what is tested on every unit (routine test) versus on a sample only, and the pass criterion in each case.
  • Compatibility and ageing: which elastomers against which coolant, at what temperature and for how many hours. An incompatible coolant is a warranty dispute waiting to happen, and the supplier is the only party who can close that question.

Step 5 — Mating-cycle life and mechanical endurance

A cycle count without test conditions is unverifiable. Ask for the declared rating and the rig: automated or manual, mated under load or de-energised, with coolant connected or dry. Then state your own duty cycle in the RFQ — expected mated cycles per day per cable, over the asset life you are planning — so the supplier answers your number instead of a generic one.

Alongside cycles, request insertion and extraction force, cable retention force, and any drop or crush test performed on the connector body. For a depot cable that gets dropped on concrete, that last item matters more than a headline cycle figure.

Step 6 — Inspection and maintenance once in service

Acceptance does not end at the factory gate. Require a written inspection interval and checklist covering coolant level and top-up procedure, hose and coupling condition, contact wear, connector body cleanliness, and the specific condition that withdraws a cable from service.

Also demand the field-replaceable parts list with lead times — hose sets, couplings, connector heads — and the written warranty terms including what voids coverage (third-party coolant, unauthorised hose replacement, unapproved cleaning agents). A cable out of service at a depot is a schedule problem, not a spare-parts problem.

Working table: RFQ line item, acceptance value, evidence to demand

Copy this into your tender document and complete the third column supplier by supplier. A blank evidence cell is a stop, never a "to be confirmed later".

RFQ line itemWhat you require the supplier to stateEvidence document to demand
Standard baselineExact document, edition year and part; IEC track, SAE J3271 track, or both; scope inclusion/exclusion of connector, inlet, cable assembly, charger equipmentWritten scope declaration plus type-test report reference
Conductor and rating basisCross-section (mm²), strand construction, current density at rated current, continuous vs short-duration rating, ambient and coolant-inlet conditionsDatasheet line plus derating curves vs ambient and vs coolant temperature
Temperature rise and sensingMeasurement points, sensor type and count, trip threshold, response time, behaviour on signal loss, signal interface to chargerType-test report with measured rise at rated current and stated coolant flow
Cooling circuit interfaceCoolant chemistry/concentration, approved coolant list, rated flow, pressure drop, working and burst pressure, coupling spec, dry vs pre-filled, leak-test regimeRoutine-test record, hydraulic test report, elastomer/coolant compatibility and ageing statement
Mechanical enduranceMating-cycle rating with test conditions, insertion/extraction force, cable retention, drop or crush resultsMechanical test summary from an accredited laboratory where available
Service and warrantyInspection interval and checklist, withdrawal-from-service triggers, field-replaceable parts and lead times, warranty terms and exclusionsWritten maintenance manual, spare-parts list, warranty document

Claims you cannot verify — ask for this instead

Most unverifiable RFQ answers fall into five patterns. Each has a documentary substitute you can insist on.

  • "IEC TS 63379 compliant." Ask for the exact edition and part, the scope statement, and the type-test report behind the claim. A compliance claim without an edition is not a claim.
  • "3,000 A rated" or "3.75 MW capable." Ask what ambient, coolant-inlet temperature and duration those figures assume. A rating without conditions is a marketing number.
  • "Liquid-cooled." Ask for flow rate, pressure drop and pressure rating. Cooling without hydraulics is a photograph of a hose.
  • "Tested to 10,000 mating cycles." Ask for the rig, the load condition and whether coolant was connected during the test.
  • "Proven in the field." Ask for named reference sites you may contact, or for the commissioning report from a comparable installation. If neither exists, the claim carries no weight in a shortlist decision.

Validate a sample before you commit the order

The shortlist should not become a purchase order without a physical loop on your own equipment. A workable sequence:

  1. First-article inspection against the completed table above, signed off before volume release.
  2. Sample loop on your charger, at your depot's ambient conditions, for a defined number of cycles, logging connector temperature and coolant pressure drop at each cycle.
  3. Post-loop teardown on contacts and seals, plus a coolant sample check if the supplier permits it. Interface mismatches surface here, not in the datasheet.
  4. Write the accepted numbers back into the purchase specification, so later production batches are held to the article that passed rather than the one that was quoted.

On our side, that sequence maps to a documented inspection routine: incoming conductor and hose verification against the approved drawing, in-process checks at crimp and coupling assembly, a routine leak and electrical test on every unit, and a retained record keyed to the serial number so a field query can be traced back to its build data. Ask any shortlisted supplier to describe their equivalent — and to show the record format.

FAQ

Is IEC TS 63379 the same as SAE J3271, and do I need both on my RFQ?

They are separate tracks addressing the same MCS coupler hardware from different regional standards bodies. Whether you need one or both depends on where the vehicle and the charger will be deployed and certified. Ask each supplier which track their type-test evidence actually supports, and require a second evidence set for any dual-track claim. Confirm the current status and scope of each document with the issuing body rather than from a supplier datasheet.

What coolant should we standardise on, and who owns coolant compatibility?

The supplier owns it, in writing. Require the approved coolant specification, the elastomer compatibility and ageing statement, and the warranty position on third-party coolant. Then standardise across sites so a top-up at one depot cannot void a cable accepted at another.

What mating-cycle life should we require?

There is no universal answer, and any single number quoted to you without your duty cycle attached is marketing. State plugs per day per cable and your planned asset life in the RFQ, and require the supplier to respond to that figure with test conditions attached.

How do we check a 3,000 A claim without a megawatt test bench?

You check the inputs rather than the headline: cross-section and current density, the derating curves, the ambient and coolant-inlet assumptions, and the measured type-test record at rated current with stated flow. Then you confirm behaviour at partial load in the sample loop on your own charger, which is the part of the claim your depot will actually exercise.

Get the checklist and a sample in one step

Request the MCS-class RFQ checklist plus a liquid-cooled cable sample for validation on your own charger, together with the current datasheet set for the assembly range. Tell us your charger's coolant loop, target flow, coupling type and expected duty cycle, and we will return the checklist pre-filled for that configuration so your evaluation starts from a completed baseline rather than a blank table.

Submit the request through our custom cable assembly RFQ form and we will confirm receipt, the documentation package available for your configuration, and the lead time for a validation sample.

Request a quote

Share a model or describe your application. Include a drawing link if you have one.