Onyx Ingenuity dragon logo
ONYX INGENUITY PRODUCT

NYRDAN™

Above your tools. Inside your walls.

NYRDAN is being built to turn the delivery data you already have into the executive answers you never have time to build.

Read-only by default. Customer-controlled deployment. Evidence behind every answer.

01: THE PROBLEM

The reporting hour that eats the delivery day.

Every week, program leaders rebuild the same story by hand. Status decks. RAID logs. Burn charts. Executive summaries. The data already exists across your systems. The hours to assemble it do not.

02: THE PLATFORM

An intelligence layer, not another tool.

NYRDAN is designed to sit above the systems you already run: project trackers, ticketing, ERP and EHR programs, spreadsheets. It is designed to read what they produce and return what executives actually ask for: status, risk, momentum, and the story behind them.

NYRDAN · DAILY EXECUTIVE BRIEFINGIllustrative product preview using synthetic data

What changed, and what needs me today?

Portfolio health: stable. 14 of 17 active workstreams on plan. Velocity within 4% of the 90 day baseline.

Payments modernization is trending 9 days late. Root cause: vendor API dependency slipped twice this sprint. Third consecutive occurrence this quarter.

Release readiness risk: Q3 platform upgrade. Test coverage below your 85% gate. Historical pattern suggests a two week impact if unaddressed by Friday.

DECISIONS WAITING ON YOU

Approve the added regression cycle for the Q3 upgrade. Cost: 3 days. Protects the release gate.

1-3-1 brief readyObjective, background, three options, one recommendation

Confirm escalation of the vendor dependency to steering. Comparable escalations recovered 6 schedule days on average.

1-3-1 brief ready
WorkstreamStateOwnerAgingAsk / Action
[APP] 4821 · Payments ModernizationBlockedB. Thistlewood14dConfirm vendor dependency path and unblock date.
[DATA] 4796 · Reporting PlatformTestingK. Marchetti6dConfirm stage validation and release readiness.
[APP] 4744 · Customer PortalActiveO. Lindqvist3dOn plan. No action required.
[DATA] 4699 · Claims Data MartResolvedD. Farrow16dConfirm validation and closure readiness.
1Blocked / needs action
2Aging over 10 days
2Release candidates
212Items tracked, 21 epics

Will we hit what we committed to?

PI predictability 87%Forecast confidence: medium14 of 17 on plan
ProgramHealthTrendStateNote
Payments Modernization71down 4WatchVendor dependency compressing buffer.
Customer Portal88up 2On planVelocity steady across three sprints.
Reporting Platform79steadyTestingStage validation in progress.
Claims Data Mart92up 5ClosingFinal validation before closure.
Identity Refresh64down 6At riskScope grew twice without date change.

Where do we slip next, and who owns the save?

Vendor API dependency slipping repeatedly. Third consecutive sprint. Exposure: 9 schedule days.

H. QuennevilleEscalate to steering committee this week

Test coverage below the 85% gate on the Q3 platform upgrade. Exposure: 2 week release slip.

C. AshcombeAdd a regression cycle before Friday

Single point of failure on Claims Data Mart. One engineer holds the model. Exposure: continuity risk at closure.

U. BergstromPair a second engineer this sprint

Is the delivery machine itself healthy?

Sprint 14 goals: 3 of 4 met. Two items carry into Sprint 15 with owners confirmed.

Flow: cycle time 6.2 days median, improving. WIP at 24 against a limit of 28. Throughput 31 items this sprint.

Pull requests: 23 merged. Median review time 9 hours, within your service standard.

Retro adopted: deployment checklist. Release prep reduced by one day on first use.

Standup digest: 2 blockers surfaced. Both routed to owners same day, one still open.

K. MarchettiClose the open blocker on stage access

Interface shown is illustrative and conceptual. Every view is designed to open the underlying items and queries. The design will continue to evolve through development.

03: CAPABILITIES

Six answers, by design.

Designed to deliver:

Executive Briefs

Board-ready program narratives generated from live delivery data.

Risk Signals

Early drift detection across schedule, scope, and dependencies.

Portfolio Lens

One view across programs, vendors, and teams.

Delivery Health Scores

Consistent, explainable scoring across every initiative.

Meeting-Ready Outputs

Steering-committee packets assembled from the same sourced evidence, in one place.

Ask Your Delivery

Plain-language questions. Sourced answers, with receipts.

04: DEPLOYMENT

Your data never leaves your walls.

NYRDAN is designed to deploy inside the customer's environment. Designed to support SOC 2-aligned security controls. Designed so PHI never reaches our systems.

By design, once deployed:

•

Runs in your cloud tenancy, under your controls.

•

Your identity provider. Your access policies. Your audit logs.

•

Reporting stays where the data lives. Nothing to exfiltrate.

•

One connection leaves your environment, by design: each evidence record is independently timestamped by a third party. The record itself never leaves, and the third party learns nothing about what it contains. Its independence is what makes the time evidence rather than our own word.

The records outlive us, by design. They are designed to stay checkable on their own terms rather than on ours: the evidence a customer holds is meant to remain meaningful whether or not this firm, or this product, is still here to vouch for it.

05: HOW IT WORKS

Three steps to command.

01

Connect

Read-only connections to the systems you already run.

02

Calibrate

Your portfolio structure, your terminology, your executive cadence.

03

Command

Briefs, scores, and answers on demand, inside your walls.

06: LICENSING

Sized to how you deliver.

Every tier includes the full intelligence core. Tiers scale by footprint, governance, and support, never by withholding answers.

Program

For a single program or department finding its footing in delivery intelligence.

Portfolio

For portfolios and PMOs that answer to executives every week.

Enterprise

For organizations that run on delivery, with the governance to match.

Availability is stated per row. Available now means the capability is built and verified in the product today; general availability governs deployment into your own environment. Licensed scope applies from the start of the agreement. Capabilities still being built are listed under On the roadmap below, and none of them is tier-gated.

AvailabilityProgramPortfolioEnterprise
The intelligence core, included at every tier
Signed evidence recordsAvailable nowIncludedIncludedIncluded
Independently timestamped, so the time is not our wordAvailable nowIncludedIncludedIncluded
Portable preservation bundles with detached integrity sealsAvailable nowIncludedIncludedIncluded
Provider-neutral independent verification that rejects tamperingAvailable nowIncludedIncludedIncluded
Footprint, governance, and support
Licensed organizational scopeOne programOne portfolio of programsOrganization-wide
PortfoliosAt general availability1Up to 5Contracted estate scale
Workspace editorsAt general availability315Unlimited
Executive viewersAt general availabilityUnlimitedUnlimitedUnlimited
Deployment topologyAt general availabilitySingle collectorMulti-collectorScaled or isolated
SupportAvailable nowStandard business-hours supportPriority support with documented response targetsEnterprise support plan and service commitments defined by contract

Tier boundaries are directional during Private Preview and will be finalized at general availability. Planning ranges are discussed during the assessment. Nothing on this page constitutes a binding offer.

On the roadmap

Undated by design, and not tier-gated. Every capability below ships to every tier when it ships, per the intelligence-core rule above. No date is stated because no date is committed.

Core decision intelligence. The executive answers layer the platform is being built to produce.
Cadence report templates, with custom authoring available as a service.
Framework standardization, guided or custom as a service.
Cross-business-unit aggregation.
Time and capitalization reporting.
The connector program. Azure DevOps collection is implemented today. Further connectors are in development, and no count is committed.
Your own delivery history, kept where your data already lives, and available to answer questions about it later.
Your own questions, asked of your own delivery data, with an answer you can show someone else.
The product shaped around how you actually deliver, without waiting on us to build it for you.
Work and evidence moving between the systems you already run, without hand-copying it.
Decisions asked for, recorded, and answerable later, in the place the work already happens.
What went wrong once, becoming something the next program does not repeat.
07: START HERE

Start with a Delivery Health Assessment.

A structured working session. We map your delivery landscape, score your current reporting load, and show what NYRDAN is designed to return inside your environment.