Skip to main content

Project Intelligence

Project Intelligence is a grounded briefing across your connected portfolio.

What it produces​

A Project Intelligence briefing is composed of a few tiers:

  • Now — where the program stands today, and what's at risk.
  • History — past projects that resemble the current situation (ones that slipped), so the risk isn't judged in isolation.
  • Context — relevant recalled context (for example, what leadership has flagged as a priority).
  • So what — the takeaway you can act on.

Because InaiBridge maps every source into one canonical record, a single briefing reasons across Jira, Asana, and Azure DevOps together.

Example​

A briefing for one program looks like this:

⚠ Legacy Retooling: Munich Plant Assembly Line Conversion — AT RISK

Now: 5 of 6 initiatives at risk, epic health RED. KAN-88 (calibration and sensor integration of the automated optical inspection weld-quality cameras) is 98 days overdue.

History: resembles 3 past projects that slipped — KAN-84 (151d, awaiting delivery of specialized heavy-payload robotic arms); KAN-83 (72d, blocked removing legacy conveyor systems); KAN-117 (35d, blocked on data-schema discrepancies with the legacy system).

Context: the Munich plant retooling is the operations team's top worry this quarter; leadership has standardized on SAP S/4HANA across all verticals; the CEO's priority is the EU launch date for the connected-vehicle platform.

So what: with KAN-88 already 98 days overdue — mirroring the delays in KAN-84 and KAN-83 — and integration risk a board-level concern, the EU launch date for the connected-vehicle platform is in jeopardy.

The figures (at-risk counts, days overdue, the resembling projects) come from your connected data; only the So what line is generated, and it reasons only over those facts.

Honest confidence​

Each signal in a briefing carries its confidence. A project isn't shown as on track just because a source couldn't prove otherwise — the briefing distinguishes what's known from what's uncertain. See Grounding & memory.

Where you see it​

The briefing is not something you run by hand — it is the reasoning layer underneath the surfaces you already use.

It powers the Portfolio's risk view: the What's driving this and Signal & context panels in a program's detail are this briefing, scoped to that program. The same grounding is what Mira draws on when you ask why a program is drifting.

The Inaibridge-Lumina Risk Assessment workflow puts the same reasoning to work on a schedule: it reads what has moved, assesses it, and raises a Suggested risk for a person to confirm in the Inbox.