In technical documentation in Vietnam, the same cold test may be recorded as “TCVN 7699-2-1” or as “IEC 60068-2-1”. These are not two different standards, but they are also not entirely identical once you compare the editions.
This article explains the relationship between the TCVN 7699 set and the IEC 60068 set, when to cite which one, and the points to check before signing off on a test result.
1. TCVN 7699 is the Vietnamese edition of IEC 60068
TCVN 7699 is Vietnam’s national standard set for environmental testing, built by adopting the IEC 60068 set. For example, TCVN 7699-1:2007 corresponds to IEC 60068-1:1988 plus Amendment 1:1992. The 2-x parts of TCVN 7699 correspond to the 2-x parts of IEC 60068 (cold, dry heat, vibration, salt mist, damp heat, and so on).
So when you read a report stating TCVN 7699-2-1, you can understand it as a cold test following the method of IEC 60068-2-1 — but you must establish which edition was adopted, because that is the single most important difference.
2. Why are there two ways of citing the standard?
| Context | Usual citation | Reason |
|---|---|---|
| Legal documentation, declarations of conformity in Vietnam | TCVN / QCVN | The national standards system is the basis cited in domestic documentation |
| Contracts with overseas customers | IEC 60068-2-x | Customers use the international IEC system, usually quoting the edition year |
| Certification requirements under a product standard | Either or both | The product standard refers to the corresponding test method set |
A point to note: the TCVN edition adopts one specific IEC edition at the time of review. If IEC has since published a newer edition, the technical content may have changed in some details (temperature ranges, functional checks, recovery times).
3. Three questions to answer before testing
- Which set applies? TCVN 7699 or IEC 60068 — decided by the applicable documentation, not by the habit of the laboratory.
- Which edition? If the contract specifies IEC 60068-2-2:2007 but the laboratory applies the older TCVN equivalent, this must be recorded and agreed in writing.
- Which severity and duration? Both sets leave the level for the requirement writer to choose. A report without a level is a report that cannot be defended.
4. Differences that can lead to disputes
- Edition mismatch: the method content of the adopted edition and the current IEC edition may differ in technical detail.
- Different interpretation of acceptance criteria: the same test with different functional criteria and check points leads to different conclusions.
- Missing supporting documentation: chamber performance confirmation and measurement uncertainty are the parts most often omitted from the file.
- Vague reporting: “passes TCVN 7699” says nothing about which test or which level — write it in detail, such as “test Ab to TCVN 7699-2-1, temperature… duration…”.
5. How to cite the standard correctly
| Element to record | Example |
|---|---|
| Standard number with year | TCVN 7699-2-1:2007 or IEC 60068-2-1:2007 |
| Test code | Ab / Ae / Bb / Bd / Nb / Db / Cab… |
| Severity level | Temperature, humidity, duration, number of cycles |
| Specimen state during test | Not energised / energised, measured during or after the test |
| Acceptance criteria | Which functional and mechanical checks, at which thresholds |
| Supporting documentation | Method used to confirm chamber performance |
6. How this affects the value of your documentation
If you export, customers will usually compare your report against the list of tests in their requirement documents. A report that states the correct test code and severity level is accepted quickly; a vague report usually triggers a request to redo the work — and the resulting cost is far higher than writing it precisely from the start.
Conversely, for domestic documentation, citing TCVN 7699 with the right part makes the file easier to accept. Where goods fall under quality management requirements, you should also check the requirements in the Ministry of Science and Technology’s list of risky goods and the corresponding technical regulations.
7. Quick cross-reference of commonly used parts
| TCVN (national set) | Corresponding IEC | Content |
|---|---|---|
| TCVN 7699-1:2007 | IEC 60068-1:1988 and Amendment 1:1992 | General provisions and guidance |
| TCVN 7699-2-x | IEC 60068-2-x | The tests: cold, dry heat, vibration, damp heat, salt mist, soldering… |
| Part 3-x of the national set (where available) | IEC 60068-3-x | Supporting documentation: chamber confirmation, test selection, uncertainty |
When working on domestic documentation, look up the specific TCVN edition currently in force rather than inferring part numbers from the IEC edition. Conversely, when working with international customers, cite the IEC number so that the recipient does not have to look up the equivalent themselves.
8. Frequently asked questions
Are TCVN 7699 and IEC 60068 the same thing?
TCVN 7699 was built by adopting IEC 60068, so the methods are equivalent, but the numbers and edition years differ.
A customer requires IEC. Can I test to TCVN instead?
Only with the customer’s written agreement. The safest approach is to issue the report under the standard number the customer requested, with a note about the equivalent edition where applicable.
Must everything be redone if there is a minor edition mismatch?
Not every difference invalidates the result. Compare the original texts of both editions on the clauses dealing with severity level and functional checks, then assess the impact.
Can I write “equivalent to IEC” in the report?
Write it out precisely: “performed to TCVN …, equivalent to IEC … edition of …” so the reader can verify it, rather than a bare word “equivalent”.
Are national standards mandatory?
National standards are generally voluntary; they become mandatory when cited in a legal instrument, a contract or a declaration file. This must be checked case by case.
What should a laboratory record in the report to avoid disputes?
At minimum: standard number and year, test code, severity level, test condition data, how the specimen was mounted, the acceptance criteria and the result against each criterion.
What if the applicable TCVN edition is older than the latest IEC edition?
Compare the relevant clauses of both editions and state in the report which edition was applied. If the difference affects the conclusion, agree with the customer on additional testing to the newer edition.
May I translate a standard for internal use?
A translation for internal reference does not replace the original text of the standard. When a citation is needed in documentation, you must refer to the official standard number and a valid published edition.
9. Conclusion
TCVN 7699 and IEC 60068 are two ways of citing the same system of methods. The issue is not which name you pick, but whether you record enough information for the result to be verified: which part, which test code, which edition, which severity level, which acceptance criteria.
Three things to do: agree in writing with the customer on the standard set and edition applied; record details in the report instead of a general citation; and keep the test condition data together with the equipment performance confirmation file.
References
- TCVN 7699-1:2007 — Environmental testing: General and guidance.
- TCVN 7699-2 (parts) — Environmental testing: Tests.
- IEC 60068-1 and IEC 60068-2 (parts) — Environmental testing.
- IEC 60068-3-5, IEC 60068-3-6 — Confirmation of the performance of temperature and temperature/humidity chambers.
Related articles
- What is IEC 60068? Structure of the standard set and how to read test codes
- What competence does a testing laboratory need? ISO/IEC 17025, VILAS and accredited scope
- Circular 36/2026/TT-BKHCN: full text of the list of medium-risk and high-risk goods
- Acceptance criteria in ISTA package testing
Discuss with us
Disclaimer
This article is interpretive content written by our team; it is not legal advice. Companies should review the original text of the applicable regulations and standards before applying them to a specific product.
See also: Copyright & Disclaimer Policy of ticforall.com.
