满足 eCoC 强制要求的两种方式
从 eCoC 生效之日起，每一辆 M、N、O 类车辆在登记之前，都需要向 NAP 提交一份经过数字签名的 eCoC。实现这一点有两种方式：通过 NAP 门户手工操作，或者用CoCDesk 把整条流水线自动化。
纸面上手工路线看起来是免费的。但实际上，一旦算上配置 IVI XML 所花的工程时间、只能离线修复的拒收、单独的电子签名许可证，以及每份证书背后的电子表格数据录入，它就成了最贵的选项。本文把这两种方式并排比较。
提交流程，分步拆解
两种路线都遵循同样的六个阶段。区别在于每个阶段有多少是自动化的，又有多少落在了人身上。
准备数据
为每辆车收集型式批准、VIN 和技术数据。
构建为 XML
数据被格式化为 IVI 2.0 模式，并校验完整性。
数字签名
完成的 XML 按欧盟标准进行数字签名。
提交到 NAP
eCoC 被传输到 IVI 国家接入点（NAP 网关）。
校验
NAP 根据 IVI 2.0 模式校验提交内容并返回反馈。
登记
有效的 eCoC 在本国完成登记，车辆即可在 DVLA 登记。
CoCDesk 端到端地自动化第 1 至第 4 阶段，并用通俗易懂的语言呈现第 5 阶段的反馈。而手工操作时，每个阶段都是一个单独的工具加一次人工交接。
CoCDesk vs 手工 NAP 门户：并排对比
| Capability | Manual eCoC submission | |
|---|---|---|
| Time to file | Minutes for a whole batch: generate, validate, sign and submit in one pass. | 30 to 45 minutes per certificate, one vehicle at a time. |
| IVI XML preparation | Valid IVI 2.0 XML generated automatically with the correct EU Member State approval authority codes. | Hand-configure the XML, or run a EUCARIS conversion tool, then edit the country-specific approval authority codes by hand in hard-to-read raw files. |
| Pre-submission validation | Built-in schema validation catches errors and guides you to the correct values before anything is sent. Incorrectly completed eCoCs are never transmitted, which prevents rejections at NAP level. Every error is caught before submission, and the wrong fields are highlighted in an easy-to-read interface so they are quick to spot and fix. | No pre-check. The receiving NAP rejects on submission, the portal offers no in-place fix, and you reconfigure the file offline and resubmit. |
| Vehicle data entry | Automatic import of vehicle data from a VIN lookup. | Manual spreadsheet management: copy and paste data for every vehicle. |
| Edits and corrections | Fully editable records with a complete, timestamped audit trail. | Re-edit the raw XML by hand, with no audit trail of what changed or who changed it. |
| Digital signing | Seamless integrated XAdES signing as part of the flow. | A separate e-signing platform at additional licence cost and extra manual steps. |
| Cross-border submission | Integrated with every EU National Access Point for vehicles registered across Member States. | A separate manual process and a different portal for each country. |
| Audit trail and CoP compliance | Full traceable history for every certificate, ready for Conformity of Production checks. | Manual record-keeping in spreadsheets and shared drives. |
| Scalability | Bulk processing for high-volume production lines. | One certificate at a time; throughput is limited by people. |
| Cost of errors | Minimal. Most errors are caught before submission. | Each rejection means offline rework and a registration delay for that vehicle. |
手工路线悄悄让你付出的代价
VIN 查询 vs 电子表格
CoCDesk 通过 VIN 查询自动拉取车辆数据。手工路线则依赖从 Excel 里复制粘贴，既慢，又是数据录入错误的最大单一来源——而这些错误随后会被 NAP 拒收。
事前校验，而非事后
NAP 门户在提交时才校验，并且会整份拒收。门户内没有编辑器。CoCDesk 先针对 IVI 模式进行校验，因此你在问题变成一次拒收和延误之前就把它修好了。
你永远不必碰的 XML
手工操作时，你要么手动编辑 IVI XML，要么使用转换工具（包括 EUCARIS 引用的那些），然后再手动修正各国特定的批准机关代码。CoCDesk 生成正确、已签名的 XML，无需任何人去读一个标签。
出口到欧盟
如果你把车辆出口到欧盟，还需要向其他成员国申报。CoCDesk 已与欧盟各国家接入点集成，因此跨司法辖区提交是一条工作流，而不是每个国家一个门户。
用你自己的车辆来看效果
判断差距最快的方法，就是把你自己的几个 VIN 跑一遍 CoCDesk，亲眼看着 eCoC 在几分钟内完成生成、校验和签名。