Avium Platform
Audience Leadership · Product · Eng Status Current
Avium
See the work. Plan the capacity. Catch the risk.
AI delivery intelligence + Visibility, Capacity, and Risk management across every project.
Ask anything about your work — capacity, flow, risk, and when you'll really ship. Get answers grounded in your own Jira data — or any work management tool — and act on them with one click back to your tool (write-back live for Jira today, more integrations on the way).
Version
v2.4.0
Visibility
Who's working on what — across every project
Capacity
Whether your team can take on more work
Risk
Where delivery is at risk before it happens
How Your Data Flows
From source to insight — what Avium does with the data you give it
01 Ingest
02 Process & Transform
03 Deliver
01 Ingest
📊
Excel Import
Spreadsheet ingest
  • File upload (.xlsx, .csv)
  • Column-to-field mapping wizard
  • Field alias recognition
  • Collision detection vs Jira data
  • Preview before commit
🔗
Jira Import
API-driven sync
  • OAuth + API token auth
  • Project & sprint wizard
  • Status → Phase mapping
  • Cursor-paginated JQL sync
  • Protected (erm_created skipped)
Excel · .xlsx
Jira · REST API
02 Process & Transform
Avium Platform
Unified data plane · processing engine · governance
Core
Import Mapping Layer
Ingests the full Jira field set — promotes the Agile/planning fields to typed columns, captures the long tail in rawFields (JSONB) · resolves custom-field IDs per instance · resolves phases · tags dataSource
excel_import jira_import
Work Management Core
The engine — what Avium actually does
Engine
Workload Board
Sprint Planning
Resource Capacity
Time Tracking
Phase Pipeline
Velocity & Throughput
Allocation Planning
Dashboards & KPIs
Signals Engine (Team+)
AI Layer (Business+)
Export Mapping Layer
Translates the internal schema back into Jira fields & Excel columns · write-back eligibility · plan gating
jira_modified erm_created jira_import
Excel · .xlsx
Jira · REST API
03 Deliver
📤
Excel Export
Round-trip ready
  • Combined workbook (single export)
  • Individual CSV per entity table
  • Headers match import wizard
  • Filtered scopes (project, sprint, dept)
  • Time logs · resources · allocations
↗️
Jira Write-back
Sync to source of truth
  • Field updates (summary, points, priority)
  • Status changes via Jira transitions
  • Sprint & fix version assignment
  • Batch sync of modified tickets
  • erm_created & excel_import skipped
✦
The Avium Signals Engine
The engine is Avium's proprietary core — domain-specific rules that produce every insight card. Your data, your rules, runs without an LLM API key. ~80% of the Insights page works on the engine alone. AI sits on top as a narrative layer; the engine is the moat.
Signals Engine · Layer 1
Team+
  • Sprint Risk — progress ≥12 pts behind the clock OR a blocker / over-allocation
  • Over-Allocation — anyone committed above 105% of capacity
  • Rebalance — spare capacity in the SAME department as the over-allocated person
  • Velocity Drift — last sprint < 65% of period peak (cliff) or 12% trend swing
  • Blocked / Stale — flagged tickets OR no activity for X days (per phase)
  • Data Quality — weighted penalty for missing assignee / estimate / sprint / due date
  • Lead Time Configurable — days from your chosen start phase to Done · P50/P75/P90 percentiles · any user picks the start phase
  • Time in Status Configurable — per-phase dwell (median, P75, P90) + currently-stuck list · stuck threshold configurable · bottleneck detection
  • Dwell / Stuck-in-phase — Insight card emits the moment ANY ticket dwells past the threshold · clicks open a drill-in modal listing every stuck ticket
  • Reopen Rate Configurable — % of resolved tickets that bounced back from Done · quality + acceptance-criteria signal · drives the next sprint's QA priorities
  • Sprint Scope-Change Configurable — per-sprint added / removed tickets after the sprint started · planning-discipline signal most tools don't surface
  • Sprint Creep — Insight card emits on ANY mid-sprint addition to the active sprint · drill-in lists every added ticket with author + timestamp
  • Flow Efficiency Configurable — active-phase time / total lifecycle · Lean staple · industry typical 15-25% · also a Dashboard headline KPI
  • Hand-off Cost Configurable — assignee-change count per ticket · high counts predict slower cycle time + reopens
  • Workflow Sankey Configurable — process-mining over real status transitions · backward moves tinted amber · noise floor configurable · the flagship Phase 5 visualization
  • Ping-Pong Anti-Pattern Configurable — tickets bouncing A↔B between two statuses · org's signature bottleneck pair surfaced · emits an Insight card on ANY cycle
AI Layer · Layer 2
Requires Anthropic key
  • Business+ AI Briefing — sprint narrative at top of Insights
  • Business+ Sprint Risk Forecast — likelihood + drivers + recommendations
  • Business+ Data-Quality Fixes — plain-English fix suggestions
  • Business+ Sprint Review Draft — first-draft retro from sprint data
  • Business+ Ask Avium — natural-language queries against your own data
  • Business+ Reports Narrative — AI summary on the Reports tab
  • Team+ Import Mapping — Claude proposes the field for every column (import wizard)
Layer 3 — UI Routing: the drill-in modal, panel-per-signal mapping, and "Open in full view" destinations live in the client. No external dependency; pure rendering of the engine's output.
🛡️
Data Governance
Every record carries a dataSource tag (jira_import, jira_modified, excel_import, erm_created) that governs sync behavior, write-back eligibility, and conflict resolution.
🔐
Protection Guarantees
Avium-created and Excel-imported records are never overwritten by Jira sync. Jira tickets are never silently modified without user intent.
📈
Plan Gating
Free & Team plans cover one-way import. Write-back to Jira and bulk Excel export unlock at Business tier — aligned with monetization strategy.