Separating core technology from applied products in a Korean NET technical description

Give technology names and product names distinct roles

Official NET application guidance calls for applications under a technology name and describes eligible categories including completed technologies supported by quantitative evaluation data. A technology name is clearer when it identifies the problem and technical method; a product name identifies the commercial product implementing that technology. A brand or model name alone rarely explains the technology’s scope. Align terminology with official guidance and current forms, and separately review whether the technology is eligible.

Explain the core technology through structure and operating principles

Organize the description in this order: problem, limitations of existing approaches, new technology configuration, reason for improvement, and verified results. In a system with multiple functions, distinguish the core element submitted for evaluation from ordinary peripheral equipment. Use the same component names and symbols in photographs, diagrams and text. For jointly developed or transferred technology, connect development contributions with evidence of the right to use it. Patent ownership alone does not prove superior performance.

Check implementation in each applied product

When one technology is applied to several products, tabulate each product’s core components, process, control method and application scope. Products with the same appearance or brand may have different core configurations, so check differences between models. Do not assume a representative product’s test results apply unchanged to other models. Review current official procedures and required materials, including confirmation of applied products, and keep unclear scope issues as questions for the responsible organization.

Attach test conditions to every performance claim

When stating an improvement rate, include the comparison product, test environment, samples and measurement method. Check whether the test report’s model, test items and units match the description. Distinguish laboratory results from customer-site results by stating their respective conditions. Exclude promotional numbers unsupported by raw data and examine whether the operating principle explains the performance improvement. Clarifying technology and product scope before polishing the wording makes claims and evidence clearer.

Connect each performance claim with its comparison evidence

Record, one claim at a time, what changed and under which conditions. Connecting each claim to the comparison object, test conditions, result units and supporting materials helps identify statements that exceed the scope of the test evidence. The table below is a practical preparation template; it is neither an official NET/NEP submission form nor a universal assessment requirement.

On small screens, swipe the table horizontally to read all columns.

Do not treat a claim with missing evidence as verified performance. Even with an accredited laboratory report, check the organization’s and test item’s accreditation scope, the actual sample and applicable model. Do not extend results from tested conditions to all products or every operating environment.

For applying test evidence to several models, see Organizing test reports for a multi-model Korean NEP application for model correspondence and unverified items.

Preparation checklist

• Core technology scope and operating-principle diagram
• Technology/product/model correspondence table
• Comparison evidence for each claim and raw test data
• Evidence of development contributions and technology transfer