结论:型式检验由「变更」和「周期」两条线触发
轮椅企业常问:型式检验多久做一次?
这个问题的答案不是一个固定的时间,而是两条触发线:
变更触发。 产品或生产条件发生变化时。
周期触发。 即使没有变更,也需要定期验证。
两条线独立,哪条触发就做哪条。
变更触发被忽略的频率更高 ——企业往往记得周期,但换了供应商、改了工艺、调了结构,却觉得「产品还是那个产品」而不做型式检验。
触发的情形
| 触发类型 | 具体情形 | 范围 |
|---|---|---|
| 设计变更 | 结构、尺寸、材料改变 | 受影响项目或全项 |
| 工艺变更 | 焊接、热处理、表面处理改变 | 受影响项目 |
| 供应商变更 | 关键件换供应商 | 该件相关项目 |
| 材料变更 | 牌号、规格、来源改变 | 材料相关项目 |
| 软件变更 | 控制器程序改变 | 功能与安全项目 |
| 周期到期 | 按规定周期 | 通常全项 |
| 停产恢复 | 停产较长时间后 | 通常全项 |
| 标准换版 | 适用标准更新 | 变化的条款 |
「软件变更」容易被忽略 ——控制器的程序更新不改变外观和结构,但可能影响制动、速度控制、故障保护的行为。
设计变更的判断
哪些变更需要重新做型式检验?判断依据是变更是否可能影响标准要求的项目:
结构变更。 车架结构、连接方式的改变,影响强度和疲劳。
尺寸变更。 座宽、轴距、重心位置的改变,影响稳定性。
材料变更。 管材牌号、壁厚的改变,影响强度。
功能增减。 增加或去掉某个功能。
外观件变更。 通常不影响性能,但如果涉及面料则影响阻燃。
紧固件变更。 规格或强度等级改变,影响连接强度。
「重心位置的改变」值得注意 ——即使看起来只是小改动,重心的移动直接影响静态稳定性的结果。
工艺与供应商变更
焊接工艺变更。 焊接方法、参数、焊材的改变,影响焊缝强度和疲劳。
热处理变更。 影响材料的力学性能。
表面处理变更。 影响耐腐蚀和涂层性能。
供应商变更。 即使规格相同,不同供应商的实际性能可能不同。
生产场地变更。 设备、人员、环境的整体变化。
「规格相同但供应商不同」是常见的误区 ——同样标称的管材,不同供应商的实际壁厚、材质成分、加工状态可能有差异,而这些差异在疲劳试验中会体现出来。
项目范围的取舍
变更触发的型式检验不一定要做全项:
分析变更的影响面。 变更可能影响哪些项目。
做受影响的项目。 只做可能受影响的。
保留未受影响项目的原数据。 说明为什么不受影响。
论证的记录。 把影响分析的过程记录下来。
不确定时做全项。 影响面不清楚的,做全项更稳妥。
「影响分析的论证」是缩小范围的依据 ——有充分的论证,可以只做部分项目;没有论证就缩小范围,在审查时难以说明。
周期的确定
按规定的周期。 适用文件有规定的按规定。
按产品风险。 风险较高的产品周期可以短一些。
按生产稳定性。 质量波动大的产品周期短一些。
按市场要求。 某些市场或客户有额外要求。
按标准换版情况。 标准更新时同步安排。
建议把周期性型式检验纳入年度计划,避免临时发现过期而影响出货。
样品的选取
从正常生产中抽取。 不是专门制作的样品。
覆盖规格。 系列产品中选取有代表性的规格。
数量。 满足各项目的需要,破坏性项目需要额外样品。
状态。 出厂状态,含全部标准配置。
记录来源。 样品的批次和来源要记录。
「从正常生产中抽取」是要求 ——专门制作的精品样品不代表实际生产的水平,这样的型式检验失去了验证工艺能力的意义。
记录与管理
变更台账。 记录所有的设计、工艺、供应商变更。
影响评估记录。 每次变更的影响分析。
型式检验台账。 记录每次型式检验的时间、范围、结论。
报告管理。 报告的有效性和适用范围。
到期提醒。 周期型式检验的到期管理。
「变更台账」是判断是否需要型式检验的基础 ——没有台账,变更就是零散的,事后无法说明哪些变更做过评估。
常见的准备不足
信息不全。 材料、工艺、使用环境的信息缺失,导致方案设计缺乏依据。
样品不具代表性。 试制样品或挑选样品,与量产状态有差距。
条件未明确。 测试条件没说清楚,数据的适用范围就不明确。
只看初始值。 忽略了环境和时间作用后的性能变化。
项目不完整。 遗漏了必要的项目,提交时才发现。
这五项在实际委托中出现频率较高,建议在项目启动时逐项确认,因为它们造成的返工成本远高于事前确认所花的时间。
数据的组织与保存
记录的完整性。 条件、方法、设备、样品状态、实测值。
可追溯性。 数据与样品批次、生产批次的关联。
保存期限。 覆盖产品的生命周期。
检索的便利。 需要时能快速定位。
版本的管理。 数据更新时的版本控制。
建议建立统一的数据台账,记录每组数据的来源、条件、适用范围和有效期。数据积累起来之后,后续的产品开发和变更评估都能受益。
与整体工作的衔接
这部分工作不是孤立的,它与几项内容相关:
与设计的衔接。 数据是设计决策的依据,也是设计验证的证据。
与风险管理的衔接。 识别出的风险点应当有对应的验证。
与变更管理的衔接。 变更时判断是否需要重新验证。
与生产控制的衔接。 关键参数的控制限值来自验证数据。
与售后的衔接。 失效分析需要原始数据作为对照。
建议在项目规划时就把这些衔接关系理清楚,避免各环节各做各的、数据无法互相支撑。
我们的做法
企业委托型式检验时,我们会询问相对上次检验有哪些变更,因为这决定了检验的范围。
对于变更触发的检验,我们会与委托方一起分析影响面,确定哪些项目需要做、哪些可以引用原数据,并把分析的理由写清楚,便于在资料中说明。
供应商变更和软件变更我们会特别提醒 ——这两类变更在企业内部容易被当作「不影响产品」,但它们实际可能影响试验结果。
如果你不确定某次变更是否需要重新做型式检验,可以把变更内容发过来一起判断,或者直接联系:132 4819 8029。检测能力见服务介绍,产品分类见手动轮椅检测与电动轮椅检测,标准信息见标准查询。
English version
Conclusion. Wheelchair manufacturers often ask how often type testing must be done. The answer is not a fixed interval but two triggers. Change triggers it when the product or production conditions alter. Periodicity triggers it even without change, requiring verification at intervals. The two are independent and whichever fires requires action. The change trigger is overlooked more often: manufacturers remember the interval but, having changed supplier, altered a process or adjusted the structure, consider the product unchanged and skip type testing.
Triggering circumstances. Design change in structure, dimensions or material triggers affected items or the full set. Process change in welding, heat treatment or surface treatment triggers affected items. Supplier change for a key component triggers the items relating to that component. Material change in grade, specification or source triggers material-related items. Software change in the controller program triggers functional and safety items. Expiry of the interval triggers generally the full set. Resumption after a long production halt triggers generally the full set. And a change of standard edition triggers the clauses that changed. Software change is readily overlooked: a controller program update alters neither appearance nor structure while potentially affecting braking, speed control and fault protection behaviour.
Judging design change. Which changes require fresh type testing depends on whether the change may affect items the standard requires. Structural change to the frame or the method of connection affects strength and fatigue. Dimensional change to seat width, wheelbase or centre of gravity position affects stability. Material change to tubing grade or wall thickness affects strength. Adding or removing a function changes the functional set. Appearance component changes generally do not affect performance, though fabric changes affect flammability. And fastener changes in size or property class affect connection strength. Movement of the centre of gravity deserves attention: even where the change looks minor, shifting the centre of gravity bears directly on static stability results.
Process and supplier change. Welding process change in method, parameters or consumables affects weld strength and fatigue. Heat treatment change affects mechanical properties. Surface treatment change affects corrosion resistance and coating performance. Supplier change may alter actual performance even at identical specification. And change of production site alters equipment, personnel and environment together. Identical specification from a different supplier is a common misconception: nominally identical tubing may differ between suppliers in actual wall thickness, composition and processing condition, and those differences show up in fatigue testing.
Scoping the items. Type testing triggered by change need not always cover everything. Analyse what the change may affect. Test the affected items only. Retain the original data for unaffected items, explaining why they are unaffected. Record the reasoning of that impact analysis. And test everything where uncertain, since an unclear impact makes the full set the safer course. The impact analysis is the basis for narrowing scope: with sound reasoning, a subset suffices, while narrowing scope without reasoning is hard to justify in review.
Setting the interval. Follow the interval any applicable document prescribes. Shorten it for higher-risk products. Shorten it where production quality varies. Extend the requirement where particular markets or customers demand more. And align it with standard revisions. Put periodic type testing in the annual plan, to avoid discovering an expiry at short notice and disrupting shipment.
Selecting samples. Take them from normal production rather than building them specially. Cover the specifications, selecting representative variants from a product series. Provide enough units for all items, with extra for destructive testing. Present them in shipping condition with the full standard configuration. And record their batch and origin. Taking samples from normal production is a requirement: specially built show samples do not represent actual production, and type testing on them loses its purpose of verifying process capability.
Records and management. A change register records every design, process and supplier change. Impact assessment records document the analysis for each change. A type testing register records the date, scope and conclusion of each exercise. Report management covers validity and applicable scope. And expiry reminders manage the periodic requirement. The change register underpins the judgement of whether type testing is needed: without it, changes remain scattered and it becomes impossible afterwards to show which were assessed.
How we handle it. When commissioned for type testing we ask what has changed since the previous exercise, since that determines the scope. For change-triggered testing we analyse the impact with the client, establishing which items need testing and which may rely on existing data, and write out the reasoning so that it can be presented in the documentation. And we raise supplier changes and software changes particularly, since both are readily treated internally as not affecting the product while potentially affecting test results.
If you are unsure whether a change requires fresh type testing, send us the details and we will work through it. Phone or WeChat: +86 132 4819 8029.