A JMC Digital product

Ryvato — a full project-management engine, governed by strategy.

Most organisations can write a strategy and most can run a project. The expensive gap is between them. Ryvato closes it from the engine up: CPM scheduling, Gantt and the critical path, earned-value analytics, risk and portfolio health — with objectives, key results and KPIs cascading down onto the same projects.

Ryvato’s organisation OKR flow view: an annual objective on the left cascading into three key results, each linked to the unit-level OKR that owns it, with achievement bars on every card.
Strategy, cascaded — one objective flowing into key results, each linked to the unit that owns it. Sample data.

What it is

Five functions, one integrated system

Ryvato — a JMC Digital product.

  1. 01

    Five functions, one integrated system.

    Strategy and objectives cascade down through the organisation. Beneath them, full project management: every project scheduled on the critical path, tracked on earned value, its schedule and cost performance rolling back up. Health scoring turns a portfolio into a single number a board can act on, and risk surfaces make the things going wrong visible while they are still cheap to fix.

  2. 02

    Built on nine international standards

    — including PMI's PMBOK, ANSI/EIA-748 for earned value, ISO 21500 and ISO 31000 — because governance that is not standards-based is just an opinion with a dashboard.

  3. 03

    KPIs, connected.

    Build the KPIs an organisation actually steers by, and connect each one to the projects, teams and units that move it — and upward to the organisation’s OKRs, so a number on a dashboard always traces to the work behind it.

  4. 04

    Bilingual by design.

    Arabic and English throughout, including board-ready reporting in both.

  5. 05

    Proven at scale.

    Ryvato runs in production today across the Kingdom — inside large organisations, with hundreds of projects and dozens of teams in daily use.

Ryvato’s organisation structure view: the group at the top with units, teams and projects beneath it — health scores, objective progress and flags rolling up the tree.
The organisation, unit by unit — health, objectives and flags rolling up. Sample data.

The argument

Linking strategy to its objectives and results down to projects and performance indicators, and linking project performance indicators up to the health of portfolios and departments.

Most organisations can write a strategy and most can run a project. The expensive gap is the one in between — where objectives stop being measurable on the way down, and delivery stops being explainable on the way back up. Closing it is not a reporting exercise: it means the same system has to carry the objective, the schedule and what was actually done, at every level.

Strategy cascades down; what was actually delivered rolls back up. Each row is one level of the same system.
Cascading downRolling up
ObjectivesPortfolio health
Key resultsEarned value
KPIsSchedule performance
ProjectsProgress and risk
TasksWhat was actually done

Standards and frameworks

What the engines are built to.

  • PMI PMBOK 7

    The project management body of knowledge, with PMI’s practice standards for earned value, scheduling and risk.

  • ANSI/EIA-748

    The earned value management systems standard, and what US federal programme offices are held to.

  • ISO 21500

    Guidance on project management.

  • ISO 31000

    Risk management — guidelines.

  • ISO 22400

    Key performance indicators for automation systems.

  • PRINCE2

    Projects in Controlled Environments — UK Government and AXELOS.

  • Balanced Scorecard

    Kaplan and Norton’s strategy measurement framework.

  • OKR

    Objectives and key results, from Intel and Google.

Shown running

The CPM and EVM engines, running

Ryvato calculates project performance on two engines: the critical path method, and earned value with the schedule and cost calculations that follow from it. These are screens from the running system on sample data — no client's data appears on this page.

Ryvato’s Gantt timeline for an automation project: three phases of tasks with progress percentages, dependency arrows, milestones, a critical-task count and a baseline switcher.
The CPM engine — a project against its baseline: dependencies, milestones, and the critical path called out. Sample data.
Ryvato’s earned-value analytics for one project: planned value, earned value and actual cost, the CPI and SPI indices, estimate at completion, burn rate, and an earned-value chart over time.
The EVM engine — planned, earned and actual cost, the indices behind them, and the forecast at completion. Sample data.

Where it runs

Two ways to run Ryvato

  1. 01

    On our hosting, configured for you

    Ryvato set up for your organisation — your structure, your KPIs, your workflows — run and kept current by the team that builds it.

  2. 02

    In your own data centre

    Ryvato installed and run inside your data centre or your in-Kingdom cloud account, for the data that may not leave the building — scoped and priced on its own.

Do you have processes or administrative work that should be running on a digital platform?

Tell us how the function runs today — or what your people do by hand. We will tell you honestly what it needs: advice on how it should run, a platform, both — or neither. And if it is neither, we will say so.

RYVATO® is a registered trademark, registered in class 9 in the United Arab Emirates and the Kingdom of Saudi Arabia.