Raqib · PROGRAM ROADMAP

A phased, fully-funded program from core platform to a multi-site fleet capability

Raqib is scoped as a multi-phase national-scale program, not a single build. Each phase below carries its own investment, team, budget breakdown, and exit-criteria milestones, sequenced so that later phases draw directly on the platform and accreditation work completed earlier — no phase starts until its dependencies are met.

SAR 20,000,000
Total program investment
21 months
Total program duration
3
Sequenced phases

Core fusion platform

Planned

Phase 1 — core platform buildout

6 monthsSAR 6,500,000

Resources

Sensor integration engineers3 FTE

Build and validate protocol adapters for CCTV, radar, RF, and EO/IR feeds.

Fusion & computer-vision engineers3 FTE

Track fusion, classification models, and the countermeasure hand-off API.

Compliance lead1 FTE, part-time

Drives the NDMO Classification and NCA ECC-2 accreditation package.

Program manager1 FTE

Owns cross-workstream sequencing, reporting, and design-partner readiness.

Budget breakdown

Engineering & platform development

Sensor adapters, fusion engine, classification models, and the operator console.

SAR 4,200,000
Compliance & accreditation

NDMO Classification and NCA ECC-2 submission, documentation, and audit preparation.

SAR 900,000
Design-partner pilot readiness

Site assessments, integration test rigs, and loaner sensor hardware for validation.

SAR 900,000
Contingency

Reserve against integration and accreditation-timeline risk.

SAR 500,000

Plan of action

  1. 1
    Finalize adapter spec for top 3 sensor vendor familiesIntegration engineering · 3 weeks

    Lock the protocol adapter contract so CCTV, radar, and RF integrations can proceed in parallel.

  2. 2
    Build and validate the countermeasure hand-off APIFusion engineering · 6 weeks

    Confirm a reference C2/jamming system can receive and act on a confirmed-threat hand-off.

  3. 3
    Submit NDMO Classification & NCA ECC-2 packageCompliance lead · 8 weeks

    File the accreditation submission covering the fusion platform architecture.

  4. 4
    Sign first 1-2 design-partner site letters of intentProgram manager · 10 weeks

    Confirm the sites and sensor inventories that the first live pilots will run against.

Activities

Hardware-agnostic sensor ingestion

Planned

Connects to existing CCTV, radar, RF detectors, and EO/IR cameras from any vendor, over their native protocols.

Owner Integration engineering

Multi-sensor track fusion

Planned

Correlates detections across every connected source into one fused track per object.

Owner Fusion engineering

Depends on Hardware-agnostic sensor ingestion

Bird, drone, and threat classification

Planned

Scores every track as bird, commercial drone, friendly, suspicious, or hostile, with a confidence score.

Owner Fusion engineering

Depends on Multi-sensor track fusion

Operator command console

Planned

Fused airspace picture, alert triage board, and per-track case file for the operator.

Owner Product engineering

Depends on Bird, drone, and threat classification

Countermeasure hand-off integration

Planned

Routing confirmed threats into a site’s existing jamming, interception, or C2 systems.

Owner Fusion engineering

Depends on Operator command console

NDMO Classification & NCA ECC-2 alignment

Planned

Compliance and accreditation work ahead of first live-site deployments.

Owner Compliance lead

Exit-criteria milestones

  • ✓Reference architecture and sensor-adapter specification approved
  • ✓Countermeasure hand-off validated against a reference C2 system
  • ✓NDMO Classification and NCA ECC-2 submission filed
  • ✓1-2 design-partner site letters of intent signed

Pilot deployment & hardening

Planned

Phase 2 — pilot deployment & hardening

6 monthsSAR 6,000,000

Depends on Core fusion platform

Resources

Field deployment engineers3 FTE

On-site installation, adapter validation, and operator onboarding at each pilot site.

ML engineers2 FTE

Tune classification models against live site data and observed evasion patterns.

Customer success / pilot lead1 FTE

Owns the pilot success criteria and site relationship end to end.

Program manager1 FTE

Continues cross-workstream sequencing and pilot reporting.

Budget breakdown

Field deployment & integration

On-site installation, sensor connection, and adapter validation across pilot sites.

SAR 3,000,000
ML model tuning & data engineering

Classification model retraining against real site telemetry.

SAR 1,200,000
Pilot operations & customer success

On-site support, spare adapter hardware, and pilot-cohort account management.

SAR 1,000,000
Contingency

Reserve against site-readiness and integration risk across the pilot cohort.

SAR 800,000

Plan of action

  1. 1
    Deploy to first design-partner siteField deployment · 4 weeks

    Install, connect existing sensors, and go live with the fused picture at the first site.

  2. 2
    Deploy to second design-partner siteField deployment · 4 weeks

    Repeat deployment at the second site, reusing adapters validated at the first where possible.

  3. 3
    Run a structured pilot review cyclePilot lead · 16 weeks

    Track classification accuracy, time-to-decision, and hand-off reliability against baseline.

  4. 4
    Harden after-action review workflow from pilot feedbackProduct engineering · 6 weeks

    Fold real operator feedback on evidence review into the case-file and replay tooling.

Activities

First live site deployments

Planned

Roll Raqib out to 1-2 design-partner critical-infrastructure sites on their existing sensors.

Owner Field deployment

Depends on Countermeasure hand-off integration, NDMO Classification & NCA ECC-2 alignment

Expanded sensor-vendor adapter library

Planned

Additional radar, RF, and EO/IR vendor integrations validated against real pilot-site hardware.

Owner Integration engineering

Depends on Hardware-agnostic sensor ingestion

Classification model tuning on live data

Planned

Refine bird/drone/threat classification against real site traffic and observed evasion patterns.

Owner ML engineering

Depends on Bird, drone, and threat classification, First live site deployments

After-action review tooling

Planned

Harden the evidence trail and replay workflow for post-incident review and compliance reporting.

Owner Product engineering

Depends on Operator command console

Exit-criteria milestones

  • ✓First live site operational on its existing sensor estate
  • ✓Second live site operational
  • ✓Pilot performance report validated against baseline
  • ✓After-action review workflow hardened from field feedback

Fleet-wide expansion

Planned

Phase 3 — fleet-wide expansion

9 monthsSAR 7,500,000

Depends on Pilot deployment & hardening

Resources

Platform engineers3 FTE

Build the multi-site fleet console and cross-site data model.

Fusion engineers2 FTE

Build ranked countermeasure recommendation logic on top of the existing hand-off integration.

Defence account lead1 FTE

Opens and manages defence/military site pilot relationships.

Program manager1 FTE

Owns fleet-expansion sequencing and certification tracking.

Budget breakdown

Platform engineering (fleet console)

Multi-site command view, cross-site data model, and scale-out infrastructure.

SAR 3,200,000
Fusion & recommendation engineering

Ranked countermeasure recommendation logic across connected sites.

SAR 1,300,000
Defence market development

First defence and military site pilot acquisition and relationship management.

SAR 1,500,000
Certification & scale infrastructure

ISO 27001 certification audit and infrastructure scaling for a multi-site fleet.

SAR 900,000
Contingency

Reserve against certification-timeline and defence-procurement risk.

SAR 600,000

Plan of action

  1. 1
    Design and deliver the multi-site fleet consolePlatform engineering · 14 weeks

    One command view across every connected site, for operators running more than one facility.

  2. 2
    Deliver ranked countermeasure recommendationsFusion engineering · 10 weeks

    Rank available countermeasure options per confirmed threat instead of a single hand-off target.

  3. 3
    Open first defence/military site pilotDefence account lead · 16 weeks

    Extend the design-partner model from commercial critical infrastructure into a defence site.

  4. 4
    Complete ISO 27001 certification auditCompliance lead · 12 weeks

    Close out formal certification building on the architecture pre-aligned during phase 1.

Activities

Multi-site fleet console

Planned

A fleet-wide command view for operators running more than one facility.

Owner Platform engineering

Depends on First live site deployments

Ranked countermeasure recommendations

Planned

Surface a ranked recommendation across available countermeasure options, not just a single hand-off.

Owner Fusion engineering

Depends on Countermeasure hand-off integration, Classification model tuning on live data

Defence & military site pilots

Planned

Extend from commercial critical infrastructure into defence and military deployments.

Owner Defence account lead

Depends on First live site deployments

ISO 27001 certification

Planned

Complete formal certification building on the pre-aligned architecture.

Owner Compliance lead

Depends on NDMO Classification & NCA ECC-2 alignment

Exit-criteria milestones

  • ✓Fleet console live across every pilot site
  • ✓Ranked countermeasure recommendation engine validated in production
  • ✓First defence/military site pilot underway
  • ✓ISO 27001 certification achieved

Fuse your existing sensors into one counter-drone picture

We're selecting design-partner critical-infrastructure sites for the first counter-UAS fusion pilot cohort. Book a briefing to review your current sensor inventory and integration path.