- Stage
- SKD
semi-knocked-down - What arrives
- Major sub-assemblies, already largely built
- What happens locally
- Final assembly, testing, firmware load, packaging
- What it does not change
- Component sourcing and board-level manufacture stay offshore
Manufacturing
How to evaluate a Saudi network equipment manufacturer
If you have to shortlist local network-equipment suppliers and defend the choice, this guide sets out what each localisation stage really means, what to ask about test and capacity, who owns the design in an OEM programme — and where local production genuinely does not help.
Buyer’s guide Published 12 min read
01The short answer
What is being evaluated?
Not a building. What you are evaluating is a programme: a specific device family, built at a specific localisation stage, on a line with a specific test regime, under a contract that puts the design on one side of the table or the other. Two suppliers with identical floor space and identical photographs can offer completely different programmes.
Ask three questions and most of the shortlist resolves itself. Which localisation stage does the line actually run for the product you are buying — SKD, CKD, or full manufacture? What is tested, and against whose specification, before a unit ships? Who owns the design, and therefore who can second-source it later? Everything else — floor space, photographs, headline capacity — describes a building rather than the programme you are about to depend on.
Read more
Interkey Semiconductor assembles network equipment in Riyadh, and this guide is built to be used against any supplier, Interkey Semiconductor included: the checklist below applies to every local line, and it says plainly where local assembly does not help.
One thing to be unambiguous about before anything else. An assembly line does not make semiconductors. A facility can be a serious, working network-equipment operation and still buy every chip in the device. If a supplier lets “semiconductor” in a company name imply fabrication, that is the moment to ask the direct question. Interkey Semiconductor assembles and tests devices; it does not fabricate chips.
02Fit
Device and deployment fit
Before anything about a factory matters, two things have to line up: the device category the supplier actually runs, and the shape of the deployment it has to feed. Establish both in the first conversation.
- Establish
- What a straight answer looks like
- Device category
- The named family — 5G CPE, mesh router, 5G MiFi, ONT, something else — and whether the supplier has run that family on a line, not merely a similar one. Fixtures and test rigs are per-family.
- Target market
- Where the devices are sold or deployed, because that decides which approvals the finished unit needs and who has to hold them.
- Deployment shape
- Consumer rollout, enterprise refresh, operator CPE programme. A rollout consuming a steady monthly volume and a one-shot refresh of a whole estate load a line very differently.
- Volume and cadence
- Units per month, over how many months, with what seasonality. A single annual number hides the peak that actually has to be built.
- Configuration spread
- How many variants: bands, firmware builds, languages, packaging, branding. Variants cost more line time than volume does.
- Design maturity
- Whether the design is frozen. A design still moving re-qualifies the line at every revision, and no supplier can quote that reliably.
03Localisation stages
Manufacturing and assembly scope
“Manufactured in Saudi Arabia” covers three very different amounts of work. The distinction is not pedantry: it drives local-content assessment, lead time, and how much of the supply chain actually moves.
- Stage
- CKD
complete-knocked-down - What arrives
- Components and parts, not sub-assemblies
- What happens locally
- Board-level assembly as well as final build and test
- What it does not change
- Chips, and usually the design, are still someone else’s
- Stage
- Full manufacture
- What arrives
- Raw inputs
- What happens locally
- Fabrication through to finished device
- What it does not change
- Nothing about fabrication is implied by an assembly line
04Local content
Do not let anyone assess local content for you
Local-content percentage is an assessed figure with a defined methodology, not a property a supplier can assert about itself. A supplier can tell you which stage it runs and what work happens in the Kingdom; converting that into a number that survives scrutiny is the assessing body’s job, and the answer depends on the specific bill of materials for the specific product.
The practical consequence for an RFP: ask for the stage and the scope of local work as facts, and treat any volunteered percentage as a claim to verify rather than an input to score.
05OEM and ODM
Who owns the design decides who has the leverage
In an OEM programme you bring the design and specification and the line builds to it. The design stays yours, which means you can move it, dual-source it, or bring it back in-house. In an ODM programme the supplier’s design is the product; you get to market faster and you own less at the end of it.
Neither is wrong. But they produce very different positions in year three, and the difference is rarely visible in a pilot. Settle ownership of the design, the firmware and the test fixtures in the contract, not in the retrospective.
06Acceptance
Firmware, acceptance and validation
A device is not finished when it is assembled. It is finished when it boots the right software, passes the tests you specified, and carries the approvals its market requires — each with a named owner.
- Establish
- Why it matters
- Whose firmware, and which build
- Who supplies the image loaded on the line, how a build is versioned, and how a change reaches production. An untracked firmware change is a field failure that nobody can reproduce.
- Provisioning and keys
- What is written into each unit at build time — identifiers, certificates, configuration — and who holds anything secret involved. Settle this before the first unit, not after.
- Test coverage per unit
- What is tested on every unit against what is sampled, and against whose written specification. “Fully tested” without a document behind it is not an answer.
- Acceptance criteria
- The written definition of a unit you will accept, agreed before the build. Without it, a dispute has no reference point and the party with the schedule pressure loses.
- Failure handling
- What happens to a unit that fails: rework, scrap, disposition record. Ask how a failure is recorded, not just what the rate is.
- Approvals and type tests
- Which certifications and type approvals the finished device needs for its market, who is responsible for obtaining each, who holds it afterwards, and at which point in the schedule each must be complete.
- Change control
- How a component substitution or a design revision is proposed, approved and re-validated. This is the mechanism that decides whether year two resembles year one.
- Traceability
- Every unit should carry a serial that resolves to its lot, its firmware build, the fixture and test record it passed on, and the date. Ask how long test records are kept and in what form you receive them; a field failure with no trail is a warranty argument, not a root cause.
07The long view
Supply chain, lifecycle and support
Assembly is a few weeks of a programme that runs for years. What decides how those years go is upstream of the line and downstream of the shipment.
- Establish
- Why it matters
- Who procures components
- You, the supplier, or a third party — and who carries the risk when a part moves in price or on to allocation. Line time is rarely the constraint; procurement usually is.
- Lead time, with assumptions
- A range with the component assumptions stated. A single confident number with no assumptions behind it has not costed the risk you will end up carrying.
- Buffer and stock
- What safety stock exists, of what, held by whom, and where. This is what a rollout leans on when a shipment slips.
- End-of-life on components
- What happens when a part in the design stops being made: who detects it, who redesigns around it, and who pays for the re-validation.
- Production lifespan
- How long the product is expected to be built, and what a mid-life revision would involve. Programmes are usually scoped for launch and then run for years.
- Field support and spares
- Who supports units after they ship, for how long after the final shipment, and where spares come from once the line has moved on.
- Exit
- What ending the programme takes: notice, tooling, fixtures, remaining stock, and whether the design can be built elsewhere. Agree it while everyone is still pleased with each other.
- Capacity versus delivered output
- A capacity figure is a ceiling: what the lines could absorb in a year if everything upstream held. Delivered output is what actually left. Ask for both, by family and by period, and treat the gap between them as the question, not the answer.
- Scale-up assumptions
- A pilot volume proves the process, not the ramp. Ask what moving from pilot to programme volume assumes — a second shift, more fixtures, component allocation — and how long each takes to arrange. A ramp plan with no dated assumptions is a hope.
08The RFP block
Questions to ask before programme commitment
Written to be answerable, and to be pasted straight into an RFP. A supplier who cannot answer these in writing is telling you something. Print this page to keep the list: the print layout drops the navigation, the contents band and the forms, and keeps the twelve questions on one sheet.
- Which localisation stage runs today for this product family, not for the facility in general?
- What is tested on every unit, what is sampled, and against whose specification?
- What is the yield and rework rate, and how is a failed unit dispositioned?
- What is the realistic lead time at our volume, including component procurement, not just line time?
- What happens to the schedule if a component goes on allocation?
- Who owns the design, the firmware and the test fixtures at the end of the programme?
- Can we second-source the same design elsewhere, and what would that take?
- What local-content position does this stage actually support, and who has assessed it?
- What certification and type approval does the finished device carry, and who holds it?
- Who supports the units in the field, and for how long after the last shipment?
- How is a component substitution or design revision proposed, approved and re-validated?
- What does ending the programme involve — notice, tooling, fixtures, remaining stock?
09The same questions, answered
How Interkey answers the checklist
The twelve questions above, put to Interkey Semiconductor. Where a value depends on the programme, it is set in the programme rather than on a web page, and the row says so.
- Question
- How Interkey answers today
- Localisation stage today
- SKD, on four lines in Riyadh, for the four current families: 5G CPE, mesh routers, 5G MiFi and ONT. CKD and ODM are roadmap phases, not current scope.
- Per-unit versus sampled tests
- Set in the programme’s test plan against your specification. The split between what every unit sees and what is sampled is agreed before the first build, not assumed.
- Yield, rework and disposition
- Not published as a site figure. Ask for them against the programme’s agreed acceptance criteria; a number with no criteria attached tells you nothing.
- Lead time at your volume
- Quoted per programme, with component procurement stated separately from line time. No standing lead time is published, because one that ignored your components would be wrong.
- Components on allocation
- Buffer stock, approved alternates and who carries the allocation risk are contract terms, agreed before volume.
- Ownership at the end
- In an OEM programme the design and the firmware are yours. Who owns fixtures built for the programme is written into the contract; ask for it explicitly.
- Second-sourcing
- An OEM programme leaves you free to. What it takes depends on how much of the test and fixture set is yours — the row above.
- Local content
- SKD assembly, firmware loading, test and packaging are performed in Riyadh. The facility’s official property presents Saudi Made positioning and Interkey’s publications state inclusion in the mandatory local-content list; confirm the scope that applies to your programme with the assessing authority.
- Certification and type approval
- Who holds type approval for the finished device is set per programme and per market. The facility operates certified quality, environmental and occupational health and safety management systems (the certifications are listed in the footer of every page); confirm that each certificate’s current scope covers the activities relevant to your programme.
- Field support
- Scope and duration are contract terms set per programme. There is no standing site-wide warranty to quote.
- Change control
- Proposal, approval and re-validation against the acceptance criteria belong in the programme contract. Ask for the process in writing before the first build.
- Ending the programme
- Notice, tooling, fixtures and remaining stock are contract terms. Settle them at signature; they are cheapest to agree before anyone depends on them.
When local assembly is the wrong answer
Be clear about the cases where it does not help: a one-off order of a few hundred units, where programme setup dominates unit economics; a design still actively changing, where every revision re-qualifies the line; a requirement that genuinely needs component-level fabrication; or a timeline shorter than the qualification cycle. In those cases importing a finished, already-certified device is the better decision, and a supplier worth working with will say so.
10Where to go next
Related manufacturing resources
Interkey Semiconductor is the company — who it is, what it is and is not, and how it relates to Interkey. Its official manufacturing website is interkey-sc.com.sa.
Network equipment manufacturing in Saudi Arabia is the capability: the Riyadh facility, the localisation stage it runs today, the four device families, and what to establish before committing a programme to it.
Read more
For the two device families with pages of their own, the questions specific to each are set out on 5G CPE manufacturing in Saudi Arabia and ONT manufacturing for Saudi fibre networks.
When the checklist above has produced a specification rather than a question, talk to the Interkey team in Riyadh.
Relatedinterkey-sc.com.saNetwork equipment manufacturing in Saudi Arabia5G CPE manufacturing in Saudi ArabiaONT manufacturing for Saudi fibre networkstalk to the Interkey team in Riyadh
11Buyer questions
What buyers ask us
Direct answers to the questions that come up in real evaluations. Anything missing, ask us at the bottom of the page.
Does SKD assembly count as “made in Saudi Arabia”?
It depends entirely on the methodology being applied, and it is not the supplier’s call. SKD means final assembly, test and packaging happen in the Kingdom while sub-assemblies arrive largely built. Ask which stage runs for your specific product, what work is performed locally, and who assessed any local-content figure you are given.
What is the difference between SKD and CKD?
SKD receives major sub-assemblies and completes, tests and packages them. CKD receives components and performs board-level assembly as well. CKD moves more of the supply chain into the country and takes materially longer to stand up. Neither implies chip fabrication.
Who owns the design in an OEM programme?
You do, in a properly written OEM contract — along with the firmware and ideally the test fixtures. That is the practical difference from an ODM arrangement, and it is what determines whether you can second-source the product later. Put it in the contract explicitly rather than assuming it.
What lead time is realistic?
Ask for it as a range with the assumptions stated, because line time is rarely the constraint — component procurement usually is. A supplier quoting a single confident number without naming its component assumptions has not costed the risk you will end up carrying.
Who holds the certifications for the finished device?
Establish it explicitly, per approval, in the contract — which approvals the device needs for its market, who obtains each, who holds it afterwards, and by when each must be complete. It varies by device and by market, so treat any general answer as an answer about a different programme than yours.
How small is too small for a local assembly programme?
There is no universal number, but the shape of the answer is consistent: programme setup — fixtures, test rig, first-article qualification — is largely fixed, so it dominates the unit cost of a small one-off order and disappears into a recurring one. If you are buying a few hundred units once, importing a finished, already-approved device is usually the better decision.
From the insights library
Continue exploring manufacturing
Manufacturing
Network equipment manufacturing in Saudi Arabia
The Riyadh facility, the four device families it assembles, and the commercial model.
Device family5G CPE manufacturing in Saudi Arabia
What a local 5G CPE programme involves, and the questions specific to that device family.
Device familyONT manufacturing for Saudi fibre networks
Optical network terminals: where an FTTH rollout actually consumes local assembly capacity.
Continue exploring
Next step
Discuss your manufacturing programme specifications
If you are writing the RFP now, describe the device family, the volumes and the timeline — the useful first answer is usually which parts of the programme local assembly can absorb and which it cannot.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia