SSR Correction Service Deck
Tec Solution Pro
Act I · The opportunity
GEOSA RFI · SSR GNSS Correction Solutions
Response to request for informationState Space Representation GNSS correction solutions

From national observations to device-scale positioning

Tec Solution Pro proposes to establish, operate and commercialise a Saudi correction service built on KSA-CORS, as the Authority's prime partner and accountable integrator-operator in the Kingdom. The reference frame, datum, observations, data policy, service classes and tariffs remain under GEOSA's authority.

The opportunity is a national capability, not an SSR server.

Tec Solution Pro · Riyadh Companion to the written response Non-binding · Confidential
The propositionWritten response, opening summary

The proposition on one page

The foundation

GEOSA already owns it

A nationwide GNSS observation network, which GEOSA reports as 209 operational reference stations, and the national reference frame, KSA-GRF17.

Where the value is

Built around the corrections

We do not claim to own the best correction engine. We propose to integrate proven correction technology, connect it to KSA-CORS, and build the products, OEM integrations and channels around it.

Sovereignty

An architectural outcome

Regional corrections generated in the Kingdom from KSA-CORS, combined where required with global orbit and clock products, under GEOSA's frame policy, on infrastructure the Authority approves.

Complement

SSR does not replace network RTK

Existing KSA-CORS services remain the right tools for professional survey work. SSR extends precise positioning to device scale.

Technology route

Proven technology, operated in the Kingdom

Rather than developing a national PPP-RTK engine from zero as the first step, with capability transferred progressively.

Evidence first

Prove it before anyone commits

Two validation stages, each ending in a GEOSA decision gate. Results become the inputs to service levels, investment and partnership terms.

Why SSRSections 2.2 and 3.3

From sessions to streams

Existing KSA-CORS real-time services are primarily session-based observation-space (OSR) services: correction delivery is established per rover or user connection, usually over a two-way link. They serve professional surveyors well, and they will continue to.

State space representation describes the error sources themselves, satellite orbit and clock, signal biases, ionosphere and troposphere, so one correction stream can serve very large numbers of receivers without per-user correction generation.

PPP-RTK

Augments precise point positioning with regional atmospheric corrections derived from a ground network, enabling substantially faster convergence than conventional PPP and potentially centimetre-level positioning under suitable network, receiver and environmental conditions.

NRTK One session per rover SSR One stream, many receivers
Practical limits still apply
  • Distribution capacity, entitlement and authentication load
  • Licensing terms, bandwidth and GEOSA policy
  • Receiver compatibility: not every receiver in service can use SSR
The strategic caseSection 3.1

Why a national service

International correction services are technically mature and will remain available to Saudi users. The case for a national service rests on structural advantages it is best placed to offer, and international providers can take part in it as technology, delivery or OEM partners.

ConsiderationInternational service, as published todayNational service on KSA-CORS
Reference frameGlobal frame; transformation typically handled by the user, application or provider optionsAligned to KSA-GRF17 under GEOSA's datum, epoch and transformation policy
Ground observationsProvider's global and regional networksKSA-CORS; real-time suitability to be validated
Fastest convergence tiersPublished for other regions, including North America, Europe, East Asia and AustraliaRegional atmosphere from KSA-CORS, subject to validation by zone
Data and governanceProvider's infrastructure and service termsIn the Kingdom; GEOSA-approved classes, standards and audit
RolePotential partner: engine, orbit and clock, satellite delivery, OEM reachNational platform that partners plug into
What the public record shows

Among the services reviewed from public sources, we did not identify a provider explicitly advertising a regional PPP-RTK tier for Saudi Arabia.

An established model

National PPP-RTK services generated from national CORS networks already operate in Japan and are planned in Germany from 2027.

ArchitectureSections 2.3, 2.4 and 11

The architecture

GNSS satellites
GPS, Galileo, BeiDou and GLONASS initially prioritised, subject to KSA-CORS and receiver support
Space segment
KSA-CORS real-time observations
Interface defined with the network operator
Owned by GEOSA
Quality control and station monitoring
In the Kingdom
SSR / PPP-RTK correction generation
Orbit, clock, biases, ionosphere, troposphere
At least two availability domains
Independent integrity and quality monitoring
Separate from generation
Encoding and distribution
Standards-based formats · IP, cellular, NTRIP, API, satellite option
Multi-channel
Commercial platform
Provisioning, entitlements, usage, billing, GEOSA reporting
Apart from the core
OEM receivers and devices compute the position
User segment
GEOSA owns and governs
  • National reference frame, datum and epoch policy
  • KSA-CORS observations and archive
  • Correction-service policy and service classes
  • Tariff approval where applicable
  • Data classification, hosting and security requirements
  • Standards and formats; audit and step-in rights
Tec Solution Pro proposes to
  • Integrate a correction engine into a GEOSA-governed in-Kingdom architecture
  • Operate generation, integrity monitoring and delivery to measured service levels
  • Build the commercial platform, SDK, APIs and OEM programme
  • Build Saudi operating capability and transfer it
Vendor neutralitySections 10.3 and 10.7

Three layers, separable suppliers

The service has three technology layers. Each can come from a different party and be changed on its own, which keeps the national service open.

A

Correction engine

Estimates orbit, clock, biases and regional atmosphere from KSA-CORS and global data, with integrity and quality outputs.

Specialist engine provider, selected competitively and approved by GEOSA. We integrate, host and operate it in the Kingdom.

B

Distribution platform

Encodes, authenticates and delivers corrections over IP, cellular, NTRIP, API and optional satellite channels.

Tec Solution Pro, telecom operators and, if adopted, a satellite operator. We design, build and operate it.

C

Commercial platform

Provisioning, entitlements, keys, subscriptions, metering, billing, revenue sharing, fleet management, customer support and GEOSA reporting.

Built and operated by Tec Solution Pro under GEOSA-approved terms.

Where we add value

Integration, distribution, the commercial platform, applications, the OEM ecosystem, product development and market creation. Not the correction algorithm.

How suppliers would be chosen

No engine, receiver brand, format or delivery operator is pre-selected. Specialists would be selected competitively against capability, interoperability, in-Kingdom deployment, sovereignty and data terms, service levels and commercial terms, all subject to the Authority's approval.

International landscapeSection 10.4 and Annex F

What exists today

Our written response reviews 14 services and products from their operators' public material, each claim cited. The review shows a mature, diverse market. It is a landscape, not a selection: inclusion does not represent nomination, preference, exclusivity or commitment.

6National and public programmes

Galileo HAS (EU), QZSS CLAS and MADOCA-PPP (Japan), BeiDou PPP-B2b (China), SouthPAN (Australia and New Zealand) and GEPOS (Germany, planned).

7Commercial correction services

Global and regional PPP and PPP-RTK services for survey, agriculture, marine, autonomy and automotive markets, delivered by internet, L-band or LEO satellite.

1Licensed engine software

Network software that an operator runs on its own servers to generate observation-space and state-space corrections from its own stations.

What the landscape shows
  • Among the services reviewed, we did not identify an advertised regional PPP-RTK tier for Saudi Arabia.
  • National PPP-RTK from national CORS is an established model in Japan, and planned in Germany.
  • Formats are diverse, which supports a multi-format output layer driven by receiver support.
  • Public evidence of licensable, operator-hosted engines is limited; in-Kingdom licensing terms are tested in Stage 1.
  • User numbers and uptime history are mostly not publicly disclosed; detailed references come from shortlisted providers under NDA.
Build, licence or managedSection 10.6

The technology route

CriterionA · Fully managedB · Licence, sovereign deploymentC · Licence plus escrow or transferD · New Saudi engineE · Hybrid
Speed to serviceFastestModerateModerateSlowestFast for pilots; moderate for the national service
Technical riskLowLow to moderateLow to moderateHighLow to moderate
SovereigntyLow to moderateHighHighest of the licensed routesHighestHigh from establishment
Vendor dependencyHighModerateLow to moderateLow once matureModerate, reducing
Exit flexibilityWeakModerate to strongStrongStrongStrong with open formats, escrow and step-in

Route E combines B with an optional short-term managed stream for early pilots, and negotiates the escrow and transfer terms of C progressively. The full twelve-criterion comparison is in Section 10.6.

Use proven correction technology initially, deploy and operate it sovereignly in Saudi Arabia, and progressively transfer operating and engineering capability rather than attempting to develop a national PPP-RTK engine from zero as the first step.

Recommendation, subject to GEOSA's preference and validation

Coverage and deliverySection 13

Coverage and delivery

One national service with tiered performance zones. Generation quality follows KSA-CORS density; delivery follows the channel. Zones are defined from validation results, and densification needs can feed the KSA-CORS enhancement programme, whoever operates it.

A

Dense network

Major cities, industrial and project corridors. Full PPP-RTK service classes.

B

Standard network

Within general KSA-CORS spacing. PPP-RTK with longer convergence.

C

Sparse or remote

Deserts, borders, offshore. PPP-level service, indicated by zone; candidates for densification.

ChannelDirectionBest suited to
IP / internetOne- or two-wayOEM, IoT, mobility, enterprise
CellularTwo-wayVehicles, drones, agriculture
NTRIPTwo-waySurvey, machine control, SSR-to-OSR bridge
API / SDKTwo-wayFleet and government platforms
Satellite / L-band (option)One-wayMining, maritime, remote agriculture, if justified by demand and receiver support

Satellite broadcast, if adopted, can be designed to provide Kingdom-wide coverage, subject to the selected satellite footprint, licensing and receiver capability. It is assessed in validation as a premium class, not adopted by default.

Receiver and OEM compatibilitySections 10.2 and 14

Receivers decide the scale

The commercial scale of SSR depends on real receiver and chipset support, not on the correction engine alone. We do not assume that every existing RTK receiver can consume SSR directly.

What determines compatibility
  • Dual- or multi-frequency tracking; single-frequency devices may converge materially more slowly
  • Multi-constellation support matching the service
  • A chipset or firmware PPP-RTK engine
  • Correction-format decoding, often enabled by firmware or licence
  • A security client for authenticated streams
The installed base

Many survey and machine receivers support RTK (OSR) only. SSR-to-OSR conversion over NTRIP keeps them served while new devices adopt native SSR. It is a bridge with its own limits, not the long-term path for the device market.

A technically elegant format has limited commercial value if the priority OEM devices cannot decode it.

OEM onboarding, in order
1Compatibility review
2Lab validation
3Field validation across zones
4Integration documents
5Pilot
6Validated status
7Commercial agreement
8Provisioning
9Scale and lifecycle
Product factorySections 15 and 21.4

One core, many products

KSA-CORS, the correction layer and the commercial platform together can launch several products on the same core, each with its own service class, price and channel.

Professional

Precise positioning for survey, GIS and construction, including the SSR-to-OSR bridge.

Machines

Construction, agriculture, mining and robotics fleets.

Devices and mobility

Drones, telematics and vehicle OEMs through SDKs and volume licences.

Platforms and assurance

Enterprise APIs, high-availability positioning and integrity services.

Service classes (illustrative)
S

Standard

Device market, agriculture, general machines. IP and cellular.

P

Professional

Survey, construction, UAS. IP, NTRIP and SSR-to-OSR.

H

High availability

Mining, logistics, critical fleets. Redundant delivery.

A

Assured

Safety-relevant uses. Integrity concept still to be developed with OEMs and regulators.

G

Government

GEOSA-approved public programmes, on agreed terms.

Commercial and financial frameworkSections 5 and 6

The commercial model

We do not propose to charge for the free KSA-CORS services

The commercial proposition is not to charge for what GEOSA provides free. Commercial classes reach users and devices the present service does not, and add device-scale delivery, fleet management, programmatic provisioning, integration support and assured availability. Whether a free public tier is offered is a GEOSA policy decision.

Revenue mechanisms
  • Per-device annual or monthly licences, and volume OEM licensing
  • Enterprise fleet and government enterprise agreements
  • Platform and API subscriptions; integration and setup fees
  • Managed service, premium SLA and satellite-delivery uplifts
  • Pilot arrangements for early adopters
Technology-provider economics

The selected technology-provider model must preserve sufficient economics for GEOSA and the prime operator to support national operations, commercialisation and reinvestment.

Ten provider models are compared, from perpetual licence to revenue share. We avoid stacked charges on the same unit, seek caps or tiers on volume-linked fees, and compare quotations on a common ten-year basis.

No prices at RFI stage

We provide the structure of a ten-year model and the data needed to populate it, in conservative, base and upside scenarios. No financial values are stated before validation; the model would be shared open-book with the Authority's PPP and finance teams.

Partnership structureSections 3.2, 4 and 17

The partnership we recommend

Six structures are compared in Section 17. Recommended path: D, then E once evidence supports investment terms, with F as a later option.

A

Technology supply only

Highest GEOSA control. GEOSA keeps all revenue but bears all cost, demand risk and technical risk.

B

Managed correction service

Fast, with technical risk on the provider; low localisation, GEOSA revenue and exit flexibility.

C

Sovereign platform operated by Tec Solution Pro

High control and sovereignty; demand risk stays mainly with GEOSA.

DRecommended

Commercial partnership with revenue share

On a hybrid, Saudi-hosted platform after joint validation. Limits GEOSA's financial exposure and shares demand risk; Tec Solution Pro would invest in the commercial layer under the agreed structure.

EWhen evidence supports it

PPP investor-operator

Once validation evidence supports investment terms.

FOptional, later

National vehicle

If the Authority later wants one. No forced joint venture and no single-award requirement.

GEOSA retains, throughout

KSA-CORS and its observations, the reference frame, correction-service policy, tariff approval, data and security requirements, standards approval, audit and step-in rights, and all regulatory authority. No regulatory authority transfers to the operator.

Network and correction services

The two are technically linked and may be procured separately. Whether the Authority awards them together or separately, the arrangements should interlock, through a defined observation-service interface and joint technical governance under GEOSA.

Roadmap and transitionSections 7, 19 and 20

Roadmap and the path to national control

6–10 weeksPhase 0a

Rapid technical feasibility

Ends in an initial go/no-go gate.

+3–6 monthsPhase 0b

Extended national validation

Ends in the GEOSA establishment decision.

Months 9–18Phase 1

Establishment

In-Kingdom build, security accreditation, first OEM onboarding, service acceptance.

From month 18Phase 2

Commercial launch

Standard and professional classes; dealer, enterprise and government channels.

Years 2–3Phase 3

Scale

OEM volume programmes; Saudi-led operations.

Year 3 onwardPhase 4

Maturity

Product expansion and national-control options.

National control options

From Year 3, GEOSA may take direct operation, appoint another operator, or continue the partnership. Open formats, documented interfaces, full data export, escrow or licence continuity, and step-in rights protect continuity of service.

Localisation by competence

Saudi engineers progress from observing, to working alongside, to leading, to operating independently, measured by competency assessments, incident records and independent review reported to GEOSA. All timings are indicative.

Validation programmeSection 18

Prove it before anyone commits

A jointly governed programme in two stages, before any final financial commitment by either party, expected to take up to about nine months including gate decisions, subject to data access.

1Stage 1 · About 6–10 weeks

Rapid technical feasibility

KSA-CORS input audit; correction generation with one or more candidate engines; a correction stream to selected receivers; first latency, convergence and accuracy measurements; provider shortlisting, including in-Kingdom licensing; hosting options.

Gate 1

SSR Feasibility Report and initial go/no-go

2Stage 2 · A further 3–6 months

Extended national validation

Engine comparison; receiver performance across zones, environments and ionospheric conditions; delivery channels; platform prototype; OEM and commercial pilots; provider economics.

Gate 2

National Validation Report and final establishment business case

What validation sets

The architecture, service levels, product claims, provider selection, receiver compatibility, market parameters, investment, financial model and partnership terms. We do not quote a single nationwide accuracy or convergence figure: values are set by zone, receiver class and service class after validation on KSA-CORS data.

Next stepsAnnexes A and B; Section 18

What we ask of the Authority

1

Real-time KSA-CORS streams for validation, through an agreed interface

2

Station metadata, coordinates and GEOSA's frame and epoch policy for real-time services

3

The hosting and data-classification requirements that apply

4

Priority segments, tariff policy and public-service direction

5

A joint steering committee to govern validation

209

KSA-CORS operational stations, as published by GEOSA

14

International services and products reviewed, each claim cited

2

Validation stages, each ending in a GEOSA decision gate

≥2

Independent in-Kingdom availability domains proposed

A national correction capability on GEOSA's own infrastructure, proven before anyone commits.

Tec Solution Pro · Non-binding response at RFI stage · All structures, timings and commercial terms are indicative and subject to validation and GEOSA approval