Category: Case Studies

Let’s talk about actual experiences.

  • Case Study: Does an LTE Device Need a TKDN Certificate in Indonesia?

    Our Case: An LTE Product and the TKDN Question

    One of our clients has a product with LTE/4G capability. Since Indonesia’s TKDN regulation applies to LTE/4G devices, they believed a TKDN certificate was required before the product could enter the Indonesian market. Is that really the case?

    Permenperin No. 35 of 2025: The TKDN Rulebook

    Indonesia’s Ministry of Industry signed Regulation No. 35 of 2025 on the Provisions and Procedures for TKDN and BMP Certification on 11 September 2025. It took effect on 11 December 2025, three months after promulgation (Article 75). It replaced the 14-year-old Permenperin 16/M-IND/PER/2/2011 and three related procurement guidelines (Article 74).

    Our Short Answer for the Client

    No. Their product did not need TKDN at all. To see why, we need to look at what TKDN measures, who is actually obliged to have it, and which products cannot even apply.

    What Is TKDN?

    TKDN stands for Tingkat Komponen Dalam Negeri, or local content level. It is defined as the amount of domestic content in goods, services, or a combination of goods and services. Under the regulation, the value can be calculated for three objects:

    1. Goods (Barang)
    2. Industrial services (Jasa Industri)
    3. A combination of goods and services

    A TKDN certificate is the official proof of a product’s local content value and/or BMP value. It is issued after calculation and verification by an Independent Verification Body (LVI) appointed by the Minister of Industry. BMP (Bobot Manfaat Perusahaan) is a separate credit awarded to companies that invest and produce in Indonesia.

    How TKDN for Goods Is Calculated Under Permenperin 35/2025

    The new regulation no longer calculates TKDN on total cost. Article 4 fixes three production factors with set weights.

    Production factorWeightWhen it counts in full
    Direct materials75%Main components hold certified TKDN values above 80%, or are made in Indonesia from fully domestic raw materials (Article 5)
    Direct labour10%At least 50% of direct workers are Indonesian citizens and production runs in the company’s own factory in Indonesia (Article 6)
    Factory overhead15%The company has invested in Indonesia and produces in its own factory there (Article 7)

    A main component that is not produced by an industrial company in Indonesia counts as 0% for the materials factor. Companies with active research and development can also earn an additional 20% brainware value (Article 10).

    Who Is Obliged to Comply With TKDN?

    Government Procurement Is the Main Trigger

    Permenperin 35/2025 is a calculation and certification procedure. It does not, by itself, make TKDN a condition for importing or selling a product. The obligation comes from procurement policy. Minister Agus Gumiwang Kartasasmita explained that TKDN applies to all industrial products purchased by the government, BUMN and BUMD through public procurement (PBJ). When a domestic product with a TKDN value above 40% is available, government buyers must choose it over imports. For consumer products outside procurement, displaying a TKDN value is encouraged but voluntary.

    Can a Product Be Excluded From TKDN Assessment?

    Yes. Article 9(2) lists goods for which TKDN cannot be calculated at all:

    1. Goods whose raw materials and/or components all come from imports. This is simply because there is nothing domestic to measure.
    2. Goods produced only through packing or packaging
    3. Goods produced only through painting, colouring, cutting, slicing or diluting that does not change the HS code
    4. Goods produced by disassembling components
    5. Natural goods that undergo no production process

    So, What Did We Tell the Client?

    No, they did not need a TKDN certificate, for three reasons.

    1. Not a government procurement product. The device is sold through commercial channels, not to ministries, BUMN or BUMD, so the procurement obligation does not apply.
    2. Fully manufactured abroad. Every material is produced, and the product is assembled, outside Indonesia. Under Article 9(2)(a), it could not apply for TKDN even if it wanted to.

    What the client does need is DJID certification for the LTE and other radio functions.

    Key Takeaways

    • Ask who the buyer is. Under Permenperin 35/2025, TKDN matters mainly when the product is bought through government, BUMN or BUMD procurement. Commercial retail products have no TKDN obligation.
    • Imported goods cannot be assessed. A product made entirely from imported materials and assembled abroad falls under Article 9(2)(a) and cannot receive a TKDN value.

  • Case Study | Does Your Server’s KC RRA Still Apply After a Hardware Change?

    Does a New Server Configuration Means a New KC RRA Assessment?

    With the rapid global growth of AI applications, large computing equipment such as AI servers, GPU servers, IT racks and liquid-cooled servers is becoming an important product category in the data center market.

    In our Korean KC RRA projects over the past two years, we have clearly seen a steady rise in EMC certification demand for large servers and rack systems.

    However, the nature of AI servers also brings new challenges to certification work.

    The equipment keeps getting bigger and heavier, which raises the logistics cost and transport risk of shipping a complete system to an overseas lab for testing. So a very common question from server manufacturers is:

    “The whole server already has KC RRA. If we later just swap the SSD, NIC, add-on card or FPGA card, do we need to test again?”

    The answer can’t be decided simply by asking whether the part’s model number has changed.

    The client’s intuition: same model, same ID, so it should carry over?

    We recently handled a real case like this.

    One of the client’s FPGA add-on cards had already completed Korean KC RRA EMC assessment as part of an air-cooled L10 server system.

    As liquid cooling becomes one of the mainstream designs for AI servers, the client wanted to offer the exact same FPGA card model as an optional part in a new liquid-cooled server system.

    For the FPGA card itself:

    • The model name had not changed
    • The PCB design had not changed
    • The function had not changed
    • It had already appeared in an approved server configuration

    So the client asked a very reasonable question:

    “Since it’s the same card, and it has already been used in another KC RRA server system, we shouldn’t need to retest, right?”

    This is also one of the most common certification misconceptions among server manufacturers.

    Same Part ≠ Same EMC Configuration

    Korea’s RRA conformity assessment is not just a check of a card’s part number.

    What actually has to be confirmed is this: when the part is used in the configuration of the product as actually sold, does the equipment as a whole still meet Korea’s EMC technical requirements?

    Even when an air-cooled server and a liquid-cooled server use the same FPGA card, their actual EMC environments can be completely different. For example:

    Assessment itemAir-cooled systemLiquid-cooled system
    Chassis designAirflow-oriented chassisChassis optimized for liquid cooling
    Cooling componentsFans / fan controllerPump / CDU / liquid cooling controller
    Power configurationOriginal air-cooling PSU loadDifferent power loading conditions
    Cable routingOriginal cable layoutCooling pipes and cables rearranged
    Grounding / bondingOriginal mechanical grounding layoutMechanical structure may differ
    FPGA installation positionOriginal slot / positionSlot, riser or mounting position may change
    System loadingOriginal server configurationGPU / accelerator density may be higher
    EMI environmentOriginal EMC configurationNew internal noise environment

    So even if the FPGA card itself is identical, once it is installed in a different server architecture, the original test results do not automatically extend to the new configuration.

    Korea’s RRA Focuses on Configuration Changes

    RRA has clear management requirements for changes to products that have already completed conformity assessment.

    Changes involving, for example:

    • Circuit changes
    • Component replacement
    • Component addition
    • Parts addition
    • Optional configurations

    may all be treated as changes related to the conformity assessment technical requirements, so it has to be confirmed whether they affect the original test results.

    Therefore:

    • Same model name ≠ automatically covered
    • Same KC ID ≠ all future configurations automatically covered

    Whether additional testing is needed still comes back to the actual hardware configuration and the coverage of the original KC RRA test report.

    Does that mean the whole server must be retested every time an SSD, NIC or add-on card changes?

    No. This is exactly where AI server KC RRA projects need the most professional judgment. RRA itself allows some changes to skip a full retest when specific conditions are met.

    For example, the RRA FAQ states that in certain computer component replacement scenarios, if the replacement is a component that has already completed conformity assessment and has equivalent function, it may be handled through the change procedure instead of a full new certification.

    RRA’s 2026 regulatory revision simplifies this further in the same direction, allowing qualifying components with the same function that have already completed conformity assessment to be handled as a change in some cases, without additional testing.

    So the real question is not: “Did this card have KC before?”. It should be: “In the new server configuration, does this card still fall within the technical coverage of the original KC RRA assessment?”

    What happened in our case?

    Back to our FPGA card case. The card model stayed exactly the same, but the server changed from air cooling to liquid cooling. That switch brings a different system configuration and different operating conditions from the air-cooled L10 system that was originally assessed.

    So we could not decide, based only on “the FPGA card model is the same,” that the air-cooled server’s KC RRA assessment results could be used directly.

    We needed to re-examine:

    • The configuration in the original KC RRA test report
    • The FPGA card’s original installation position
    • The hardware architecture of the liquid-cooled system
    • The PSU, GPU, accelerators and other high-speed components
    • Cable routing and grounding
    • The new electronics added by the cooling system, such as the pump and controller
    • The worst-case EMC operating mode
    • Whether the original test configuration is enough to represent the new liquid-cooled system

    After the configuration assessment, if the new liquid-cooled configuration goes beyond the representative / worst-case coverage of the original report, the affected KC RRA EMC items need additional testing or re-assessment. You can’t simply rely on the existing KC ID.

    A Configuration Change Doesn’t Always Require a Full Retest

    This is also the most important cost-control concept for large AI server projects. When a configuration changes, the first step should be a Regulatory Impact Assessment, not immediately scheduling a full retest. By comparing the original certified configuration with the new shipping configuration, you can first determine which outcome applies:

    • No impact: The change is already covered by the original test report, so the existing certification still applies.
    • Minor change: The change needs to be reported to RRA, and the documents or registration are updated, but no new testing is required.
    • Major configuration change: The change goes beyond the original report’s coverage, so additional testing or a new conformity assessment is needed.

    That way you meet Korea’s RRA requirements while cutting the cost of repeatedly shipping and testing large servers.

  • Case Study|Declined Twice? What Your DJID Inquiry Might Be Missing

    The Overlooked Documentation Gap

    A DJID inquiry getting declined once is frustrating. Getting declined back to back, on the same product, is usually a sign that something structural is being missed. It’s typically not a technical failure, but a documentation gap nobody flagged before submission. DJID type approval inquiries can be more complex than they appear when this requirement isn’t known upfront.

    Recently, The One-GDC encountered this exact issue while handling a DJID inquiry for a product using multiple frequency ranges, WLAN and Bluetooth, simultaneously. The inquiry was declined repeatedly, and the cause wasn’t the product’s compliance itself, but a missing document that most applicants don’t anticipate.

    It’s Not Just About Passing the Test

    Products with WLAN capability require the local importer to submit an additional declaration letter, a sealed statement confirming which specific frequency range the product will use once it enters the Indonesian market.

    Without this letter, the inquiry stalls, even if the technical test results themselves are fully compliant.

    This isn’t the only reason inquiries get declined. In other cases we’ve handled, submissions were rejected due to a mismatch between the technical codes written in the RF summary statement, a separate issue worth covering in its own case study.

    For products combining WLAN and Bluetooth or other capabilities, the missing declaration letter was the deciding factor between a smooth approval and a repeated back and forth cycle.

    Our Approach|Anticipating the Paperwork Before It Becomes a Problem

    Once we identified that the product’s frequency profile triggered the WLAN declaration letter requirement, the rest of the process became about coordination rather than technical troubleshooting.

    Our filing sequence for this case:

    Technical Report Review
    → Frequency Range Identification (WLAN / Bluetooth/Wifi)
    → Additional Documentation Mapping (Declaration Letter Requirement)
    → Local Importer Coordination
    → DJID Submission
    → Approval

    This meant the declaration letter was prepared and ready before submission, instead of being requested (and delaying the process) after an initial decline.

    What Our Experts Have Done When It Comes to DJID

    In practice, DJID inquiries often take longer than expected because of this exact back and forth over missing documents. From more than 40+ DJID cases that we have done in 2026, our technical team has learned to anticipate these moments in advance, reading through the reports upfront to confirm every required document is already in place.

    Because we operate through our own Indonesian branch, we communicate directly with the local importer to make sure they’re informed of any additional documents required from their end, before submission rather than after a decline.

    For us, the value of Global Market Access isn’t just knowing that a declaration letter is needed. It’s knowing which perks and technical codes apply to your specific product, and making sure the right party has the right document at the right stage of the process.

    Key Takeaway

    For products that has WLAN, the deciding factor in a clean DJID approval is often not just the test results. It’s whether the local importer has submitted the additional declaration letter confirming the product’s frequency range use in Indonesia.

    Rather than treating DJID as a single technical checkpoint, the real path is:

    1. Frequency Range Identification
    2. Additional Declaration Letter
    3. Local Importer Coordination

    Through direct coordination with our Indonesian branch and experience across 40+ DJID cases, The One-GDC helps manufacturers avoid the repeated decline cycle and move straight to approval.