Industries
An operator’s procurement runs as separate programmes: devices, network intelligence, the enterprise messaging layer, the IT estate underneath. They are bought separately and they depend on each other. This page is written for the planning and procurement roles that have to see all of them at once.
Sector guide Published 5 min read
01The terrain
An operator procures the way its organisation is drawn. The device team runs a CPE and ONT programme against a rollout plan and a local-content requirement. The network team runs a traffic-visibility programme against capacity and policy needs. The enterprise business unit runs a messaging platform for the businesses that send OTPs and campaigns over the network. The IT estate that all three depend on is run by a fourth team, on a fourth budget.
Each programme is sensible on its own and each assumes the others are somebody else’s. The practical consequences arrive at the joins: a device programme sized without the traffic picture, a visibility platform that cannot see the devices the operator itself supplies, a messaging platform that depends on sender-ID and routing rules the network team changed last quarter. This page is about the joins, because Interkey works on more than one side of them.
02What Interkey brings
Each is a product or practice with its own page; what this page adds is how they meet inside an operator.
5G CPE, mesh routers, 5G MiFi and ONT assembled in Riyadh by Interkey Semiconductor, for operators with local-content requirements or import lead times to solve. The manufacturing page states what the facility does today.
Interkey Intelligent DPI: traffic classification for lawful network management, run on infrastructure the operator controls, with the classification figure qualified as the product’s own measurement.
Interkey Digital Connect: the platform through which businesses send OTPs, alerts and campaigns to subscribers, with sender ID registration handled as a process rather than a surprise.
03The joins
The dependencies an operator’s programmes have on each other, written so a planning role can check whether each one is owned. None of these is exotic; all of them are routinely discovered late.
| Programme | Depends on | What happens when nobody owns the join |
|---|---|---|
| Device supply | A demand forecast the network team believes; firmware and provisioning integration with the operator’s systems; a local-content assessment that is the buyer’s to make | Devices arrive on schedule and sit in a warehouse because provisioning was somebody else’s programme. The evaluation guide lists what to ask a manufacturer before the order. |
| Traffic visibility | Where the platform runs and what it may inspect, decided by the operator’s own lawful-management policy; the device estate it needs to recognise; the IT platform it reports into | A classification platform that cannot see the operator’s own CPE traffic distinctly, or that reports into a dashboard the operations team does not watch. |
| Enterprise messaging | Sender-ID rules and routing the network side controls; the enterprise customers’ integration effort; the same IT and observability estate as everything else | Enterprise customers discover a registration step at go-live. The Digital Connect questions cover what they ask. |
| The IT estate underneath | Platforms that are observed, operated and upgraded: the observability practice, the container platform, and someone who owns them after go-live | Three programmes report into three monitoring tools, and the first cross-programme incident is diagnosed by conference call. |
04Local content
Operators in the Kingdom procure against local-content expectations, and a device programme is one of the few places an operator can move that number with a single sourcing decision. What Interkey can state is the capability: a Riyadh facility assembling the four device families at the SKD stage, with the delivered count and capacity the manufacturing page publishes as Interkey’s own figures.
What Interkey does not state is the local-content position a given programme would achieve. That is an assessed figure under the buyer’s own rules, it depends on the programme’s scope and stage, and a supplier asserting it in advance is describing a number it does not control. The evaluation guide sets out how to ask the question so the answer can be checked.
05After go-live
A device programme ends when the devices ship. A visibility platform and a messaging platform do not end; they are run, upgraded and integrated with the next thing the operator buys. The question for a planning role is who operates each of them in year three, on which working week, in which language, and whether that was priced.
Interkey operates the platforms it implements, from Riyadh, on an agreed scope through its managed service, and builds the integrations between them as systems integration work. An operator that wants to run them itself receives the runbooks to do so.
No operator is named here, and none will be
This page describes capability. It names no operator as a customer, quotes no deployment figure, and implies nothing about any relationship beyond what the product and manufacturing pages state in their own words. An operator evaluating Interkey should ask for references directly, in a conversation where they can be given with the counterparty’s consent, which a web page cannot do.
Planning a device, visibility or messaging programme and want the joins owned from the start? Interkey works on all three sides of them, from Riyadh, and the first conversation is about which programme is which.
06Buyer questions
Direct answers to the questions that come up in real evaluations. Anything missing, ask us at the bottom of the page.
The facility operates as a contract assembler, open to all vendors of network devices, and the commercial model is a quote per programme and volume. What it builds today, and at which stage, is stated on the manufacturing page; what to ask before ordering is in the evaluation guide.
No. It runs on infrastructure the operator controls, and what it may inspect is decided by the operator’s own lawful network-management policy rather than by the product. The DPI questions cover deployment, scope and the qualification on the classification figure.
For the businesses that send messages over the network, and therefore of interest to the operator’s enterprise business unit. It handles sender-ID registration, OTP and campaign traffic for those customers; the product page describes the platform and the figures it publishes with their qualification.
Not on this site. References are given in conversation, with the counterparty’s consent, which is the only honest way to give one. A sector page that names customers it has not cleared is a page that will eventually be asked to take them down.
From the insights library
The questions to ask before a device order, including how to ask the local-content question so the answer can be checked.
ProductTraffic classification for lawful network management, on infrastructure the operator controls.
ProductThe enterprise messaging platform: OTP, campaigns and sender-ID registration for the businesses on the network.
Solutions for this sector
Next step
Say which of the three is being procured now, what it assumes about the other two, and who owns the IT estate they all report into.
Or directly
+966-11-2180999 info@interkey.com.saTawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia