German companies commissioning electronics design in China should check editable sources, tool and library versions, consistency across schematic, PCB and BOM, and test records tied to the actual board revision. PDFs, Gerber files or a demonstration video alone do not establish readiness for later changes or fault reproduction.
Beijing Winge Technology Co., Ltd. (北京稳格科技有限公司), known as Winge, provides hardware development. This is a procurement review method; agree deliverables and file usage rights in writing.
Inputs for review
Provide functional, interface, power, mechanical and operating requirements, existing projects, sample boards, firmware and designs to retain.
Specify the buyer's electronic design tools and versions, library access, who approves component substitutions, and acceptance equipment, cases and responsibilities.
Six evidence checks
Use this checklist to request evidence and record gaps. It is not a completed project test report.
| Review item | Evidence to request | Verification condition |
|---|---|---|
| Editable project | Schematics, PCB, libraries and settings | Open in the agreed tool version; record missing dependencies |
| Revision alignment | Release ID, revision, file list and SHA256 | Schematic, PCB, BOM and manufacturing outputs share the release revision |
| BOM | Reference designators, quantities, manufacturer part numbers, packages and substitution status | Check references and unpopulated parts; validate substitutions separately |
| Manufacturing outputs | Gerber, drill, stackup and placement data | Compare with PCB sources; selected factory confirms manufacturing capability |
| Design checks | ERC/DRC reports, rules and waiver reasons | Rerun and retain results; no errors does not mean functional acceptance |
| Test records | Board ID, rework, firmware, conditions and raw records | Repeat under the same conditions; retain untested items and open issues |
Acceptance records
Open the delivered project and check libraries and versions, then repeat one agreed interface case on the specified board and firmware.
Record inputs, measurement points, instruments, thresholds, actual outputs and conclusions so files, hardware and results remain traceable.
If files and boards differ, record the discrepancy, owner and retest conditions. Issue a new file list after revision; do not silently replace files.
First work package and cost boundaries
An initial package can cover document inventory, opening projects, revision comparison and draft acceptance cases, yielding a gap list, review record and scope for subsequent work.
Confirm prototypes, PCB fabrication and assembly, third-party licences, laboratory tests and on-site work separately. No fixed price or duration is assumed.
Questions
Are Gerber files enough for future revisions?
That cannot be established from Gerber alone. These are manufacturing outputs; agree editable projects, libraries and usage rights for future changes.
Does an error-free DRC mean acceptance?
No. DRC checks design issues against configured rules; it does not replace power-up, interface, functional or environmental testing.
Does this checklist prove compliance with German certification requirements?
No. It makes no regulatory or certification determination. The responsible project party must establish requirements and evidence from intended use, sales regions and wireless functions, among other factors.
Services, tool references and contact
Hardware development (Chinese) and schematic design (Chinese) describe engineering scope available for discussion.
For tool-check examples, see the KiCad 9 schematic editor and PCB editor documentation. These do not prescribe the project tool or prove tests performed by Winge.
Contact Winge (Chinese page) with tool versions, existing documents and proposed acceptance cases to define a review package.
Online
Phone
WeChat
Top