Operational Intelligence Review / sample dossiers
Choose the dossier that matches your environment.
Findings explain the research problem. Dossiers show what a customer-facing Operational Intelligence Review can look like: problem, evidence, limits, decision exposure and a safe path to pilot. Each public-safe example keeps the approved report structure while replacing the customer name with an operator class.
Format public-safe demo
Purpose customer report preview
Boundary no operator named
Access no live data required
Regional ISP dossier
For whomOwners, managers, NOC leads and field operations teams where customer trust depends on response quality.
Core questionDoes delay between an early signal and a decision create cost, stress or avoidable customer impact before a visible incident?
Reference shape83 days, 6,552,194 observations, 193 candidate decision windows and an observed candidate decision window of about 49 minutes.
LanguageEnglish public preview. Localized print variants are prepared only after language QA and approved release.
Large telco dossier
For whomNational or multi-region operators where the problem is coordination, escalation, approval, vendor handoff and governance.
Core questionIf visibility already exists, what is the cost of delayed action across the decision chain?
Reference shapeAnonymized reference observations: 67 days, more than 6.4 million observations and 579 candidate windows.
LanguageEnglish public preview. Localized print variants are prepared only after language QA and approved release.
What these demos are not
Not a network-quality judgementThe examples do not assess any named operator and do not claim a confirmed incident where evidence does not support it.
Not a sales brochureThe purpose is to show the report class: evidence, decision exposure, unknowns, management questions and a controlled next step.
Not method disclosureThe examples explain what is observed and why it matters without exposing Raven's internal method or customer-sensitive detail.
Not automatic activationA real dossier requires approved scope, data boundary, retention rule and human approval before any customer-specific work starts.