Every analytical layer SigmaSX runs on, laid out in detail
From raw data ingestion to structured risk output, SigmaSX is built as a set of distinct modules. Below is a breakdown of what each one does and why it matters for your workflow.
Four layers, one pipeline
Each module operates independently but feeds the next, so data moves from raw input to structured output without manual handoffs.
Data Intake
Consolidates multiple data streams into a single normalized format, reducing time spent reconciling inconsistent sources.
Pattern Scanning
Applies rule-based logic to flag recurring structures in historical series, surfacing patterns that merit closer review.
Scenario Mapping
Organizes flagged patterns into labeled scenarios, giving each one context before it reaches a report or dashboard.
Report Generation
Compiles findings into a structured, exportable format designed for quick reading and internal distribution.
Modular by design, not by accident
Keeping each function separate means updates to one module don't disrupt the others. It also means you can adjust how much weight any single layer carries in your overall workflow.
SigmaSX was built around the idea that structured data shouldn't require a specialist to interpret it. Every module outputs something readable on its own, and more useful when combined with the rest.
- Configurable thresholds per module
- Independent logs for each processing stage
- Exportable output at every step, not just the final one
How the modules connect in practice
A typical session moves through these stages in sequence, though each can also be run in isolation.
-
01
Connect & Normalize
Data sources are linked and converted into a shared format so comparisons across time periods stay consistent.
-
02
Configure Scan Parameters
Set the sensitivity and scope of the pattern scan to match the timeframe and dataset you're working with.
-
03
Review Flagged Scenarios
Scenario mapping groups results by type, letting you scan summaries before drilling into any single flagged item.
-
04
Export Structured Report
Generate a document that compiles the session's findings in a layout built for internal sharing or archiving.
Two ways teams typically configure it
The same modules can be tuned for very different rhythms depending on how often you need fresh output.
Tight Scan Intervals
Ingestion and pattern scanning are configured to refresh frequently, keeping scenario maps current with short-term data shifts. This setup favors teams that check output multiple times within a single period.
- Narrow scan windows
- Faster refresh on ingestion
- Compact report format for quick scanning
Wider Scan Windows
Pattern scanning and scenario mapping are tuned for broader timeframes, better suited to periodic reviews rather than constant monitoring. Reports are generated less often but cover more ground.
- Extended scan windows
- Fewer, denser reports
- Scenario mapping weighted toward longer trends
Explore the modules yourself
Access the platform to see how ingestion, scanning, mapping, and reporting work together on your own data.
Access Data