Analytics Hub
One Command Center for Every Service, Change and Commitment
Give executives and managers consistent, cross-module views of performance, risk and service levels.
Analytics Hub brings Executive Command Center views, advanced reporting and process analytics together, using data from every Nexus module rather than exports.
- Module records
- Metric definitions
- Process analytics
- Command Center
- Review
- Action
The enterprise challenge
Every meeting starts by arguing about the numbers
Reports are built from exports, definitions differ by team and executives see last month's data.
An executive metric is only as trustworthy as the path back to the records beneath it. Analytics Hub draws directly on the incident, request, problem, change, release, asset, service-level, portfolio and vendor records maintained across Nexus, applies shared metric definitions so every team calculates the same thing the same way, and lets a leader drill from a Command Center view down to the individual records that produced it. The monthly review stops debating the numbers and starts deciding what to do about them.
Inconsistent metrics
Two teams report different SLA performance.
Manual reporting
Analysts spend days assembling decks.
No cross-module view
Change and incident trends are never compared.
Signature view
The Record to Insight River
Leaders review one set of numbers drawn directly from Nexus records.
The Record to Insight River: records from every Nexus module flow through governed metric definitions into decision views, and every leadership metric drills back to the records beneath it. Select a metric to see which modules feed it and how to drill down. Conceptual illustration, not a product screen.
Change success — Changes and releases compared with the incidents that followed them. Fed by: changes, releases, incidents.
- Definition
- Metric definition linking changes to subsequent incidents
- Definition owner
- Change manager
- Drill path
- Drill: trend → failed changes → linked incidents
What Analytics Hub covers
Approved baseline capabilities and the detail restored from the historical module record, labelled by provenance.
- Approved baseline
Executive views
Summarize for leadership.
- Executive Command Center
- Performance reporting
- Approved baseline
Process analytics
Measure service management.
- Incident, request and problem analytics
- Change and release analytics
- SLA analytics
- Approved baseline
Advanced reporting
Go deeper.
- Advanced reporting
- Scheduled and exported reports
- Approved baseline
Intelligence
Connect signals.
- Cross-module AI intelligence
- Restored · historical record
Operational Dashboards
Monitor the IT landscape with interactive dashboards.
- Incident and request volume tracking
- SLA performance heat maps
- Service availability monitors
- Team workload and capacity views
- Custom widget builder with drag-and-drop
- Restored · historical record
Predictive Analytics & Trend Analysis
Anticipate issues before they affect services.
- Incident volume forecasting
- Seasonal trend detection
- Capacity utilization predictions
- SLA breach probability alerts
- Anomaly detection across metrics
- Restored · historical record
Executive & Board-Level Reporting
Reports for every stakeholder level.
- Automated scheduled reports
- Drill-down from executive summary to operational detail
- Multi-format export (PDF, spreadsheet, API)
- Audit-ready report templates
- Cross-module consolidated views
- Restored · historical record
Custom KPI & Metric Builder
Define and track the metrics that matter.
- No-code KPI creation wizard
- Composite metric calculations
- Threshold-based alerting
- Benchmark comparisons
- Goal tracking with progress indicators
Detail reconciled from the approved historical Nexus module record (additive restoration; legacy performance figures excluded per the claims policy).
From operational records to an executive review
Trigger: A monthly service review is scheduled.
Collect
Records from all modules.
Measure
Shared definitions applied.
Present
Command Center views.
Review
Leadership discussion.
Act
Improvements assigned.
- Participants
- Service managers
- Executives
- Analysts
- Work items
- Dashboards
- Report packs
- Action items
- Automation
- Scheduled report generation
- Governance controls
- Shared metric definitions
- Role-based dashboard access
Outcome: Leaders review consistent, current data and assign improvement actions.
Metric governance
New or changed metric definitions are reviewed and approved by the metric owner; the definition history is retained, so a trend break can be explained by a definition change rather than guessed at.
From KPI to record
Every Command Center view drills from the executive summary to process analytics and on to the individual incidents, changes or requests beneath it — the same path for every audience.
Review cadence
Scheduled packs feed recurring service and leadership reviews; decisions from the review become owned improvement actions in Service Excellence instead of minutes in a document.
Thresholds and alerts
Threshold-based alerts and SLA breach-probability signals notify owners when a metric moves outside its defined range, prompting investigation before the next review.
Access by role
Dashboards respect role permissions, so security, people and supplier analytics are visible only to those entitled to see the underlying records.
Who decides, and what happens when the path breaks
Every decision in the lifecycle has an accountable owner; automation and AI contribute the support listed, never the decision itself.
Decision rights
Metric definitions
- Decides
- Metric owner
- Support
- Composite calculations and threshold configuration (workflow-triggered)
Focus areas for improvement
- Decides
- Service managers and executives
- Support
- Cross-module pattern highlighting (recommendation)
Report commentary
- Decides
- Analyst
- Support
- Draft narrative summaries for editing (assistance)
Improvement actions
- Decides
- Accountable process owner
- Support
- Forecasts and breach-probability signals (predictive)
Exception register
Source data is incomplete for a reporting period
- Handling
- The view flags the affected metric and period instead of presenting a partial figure as complete.
- Owner
- Metric owner
A metric definition changes
- Handling
- Change approved and recorded; trend views mark the point at which the definition changed.
- Owner
- Metric owner
A threshold is crossed
- Handling
- Alert to the accountable service or process owner with a drill path to the underlying records.
- Owner
- Service owner
A viewer lacks access to underlying records
- Handling
- Aggregates shown where permitted; record-level drill-down is withheld per role.
- Owner
- Platform administrator
Metric definitions
Calculations are shared across teams.
Access control
Dashboards respect role permissions.
Tenant isolation
Records are scoped to the organization's own environment.
Analytics Hub in practice
Representative situations drawn from common enterprise security, governance and data patterns.
Two teams, two availability figures
The service desk and the operations team present different availability results for the same service in the same review.
With Nexus: A shared, owned metric definition is applied to the same incident and service-level records, so there is one figure — and anyone can drill into the outages that produced it.
The board pack built by hand
Analysts spend the last week of every month exporting data and assembling slides for the leadership review.
With Nexus: Scheduled report packs generate from current records with the governed definitions, and narrative summaries draft the commentary for an analyst to edit and approve.
Change and incident trends never compared
Change volume and incident volume are reported separately, so nobody notices that a rise in failed changes precedes each incident spike.
With Nexus: Cross-module views place change, release and incident trends side by side, and cross-module intelligence highlights the pattern for people to investigate.
Mapped to recognized practice, capability by capability
Each mapping names the Nexus capability and the record that supports the practice. Mappings describe alignment of practice; they are not attestations.
ITIL 4
Aligned practice- Practice
- Measurement and Reporting practice
- Nexus capability
- Shared metric definitions, process analytics and operational-to-executive reporting
- Supporting record
- Metric definition records and dashboard views built on module records
ISO/IEC 20000-1:2018
Compliance-supporting capability- Practice
- Clause 9 performance evaluation — monitoring, measurement, analysis and evaluation; management review
- Nexus capability
- Service performance reporting and scheduled management-review packs
- Supporting record
- Scheduled report packs and review action items
COBIT 2019
Aligned practice- Practice
- MEA01 performance monitoring · MEA04 managed assurance
- Nexus capability
- Governance dashboards, performance-against-target tracking and drill-down to underlying records
- Supporting record
- KPI and goal-tracking records with drill paths
How AI supports Analytics Hub
Insights are surfaced for people to interpret and act on.
Assistance drafts or summarizesRecommendation proposes for a person to acceptPredictive forecasts or flagsWorkflow-triggered runs only as configured
- Recommendation
Cross-module intelligence
Patterns across incidents, changes and SLAs are highlighted for review.
- Assistance
Narrative summaries
Draft commentary on trends for editing.
- Predictive
Metric anomaly detection
Unusual movements in operational metrics are flagged for review.
- Predictive
Demand and capacity forecasting
Forecasts of incident volume and capacity demand inform planning.
- Assistance
Natural-language questions
Questions about governed data can be asked in plain language, returning views for people to review.
- Recommendation
Optimization suggestions
Suggested improvements based on operational patterns are offered for owners to assess.
- Workflow-triggered
Trend notifications
Owners are notified when a significant trend crosses a defined threshold.
- Assistance
Cause correlation
Performance anomalies are linked to candidate underlying causes for analysts to confirm.
Why enterprises choose Nexus for analytics hub
Analytics on the records, not on exports
Dashboards and report packs read the same records the modules maintain, so the analysis is current and every figure has a drill path to its source.
Definitions are governed objects
Each metric has a definition, an owner and a change history, so two teams cannot quietly calculate the same measure two different ways.
Insight surfaced, decisions owned
Cross-module intelligence highlights patterns and drafts commentary; interpreting them and assigning improvement actions stays with service managers and leaders.
How Analytics Hub connects
Part of the Data, Governance & Intelligence Function, with relationships across Nexus modules and the wider iShield portfolio.
Incident Management
Source of incident analytics.
Change Management
Source of change analytics.
Service Excellence
Provides SLA and CSAT data.
IT Financial Management
Adds financial views.
Across the portfolio
What changes for the organization
Shared truth
One set of numbers.
Less manual reporting
Reports generate from records.
Cross-process insight
Trends are compared.
Faster decisions
Data is current.
Where this module is used
IT Strategy, Portfolio & Financials
Align IT investment to business outcomes — capability maps, demand intake, TBM-grade financials.
Explore solutionSovereign Data Fabric & Master Data
Federated query, lineage, consent and golden records — without copying data across borders.
Explore solutionIntegrated GRC & Audit
One control library, one evidence ledger, continuous audit across every framework.
Explore solution
