Model 1
Implementation, you operate
Ixia implements Ixia DQ on your estate and hands over. Your team operates it; Ixia is on call for rule changes and reviews.
Ixia DQ Platform
Optional managed service
Continuous data quality monitoring. Managed by Ixia.
The platform does the checking every night. Ixia does the scoping, the rule work, the reading and the follow-through, so the business gets a trusted number and a named person behind it.
Runs on your SQL Server, your Power BI tenant and your mail system; no data leaves your estate. Commercial terms, including any subscription, are agreed per engagement.
What the business receives
- A daily update email: position, top rules, four-week review
- An eight-page Power BI report in your tenant
- A failure file per domain, ready for the data owner
- A periodic review of trends and recurring failures
- A rule change log with the reason for every change
The operating model.
Each step says whether it is automated platform functionality or human service, so there is no ambiguity about what you are buying.
Establish the monitoring scope
Domains, sources, thresholds and exclusions, agreed with the data owners in business language. People.
Configure and agree the rules
The generic pack switched on, your conventions written in the Rule Builder, each on the data owner's confirmation. People, then platform.
Scheduled monitoring identifies failures
Rules run on a schedule against every record and write every failure to the result table. Platform.
Stakeholders receive quality reporting
The Power BI report in your tenant and the daily update email, from the same run. Platform output, checked by Ixia.
Issues and trends are reviewed
Ixia flags the rules moving the wrong way, confirms fixes held, and raises recurring failures that point to a process. People.
Rule coverage evolves
New objects, new conventions, a migration ahead: rules added, changed or retired, always on written confirmation. People, then platform.
The platform, automatically
- Runs the rules on schedule, every record
- Writes the run log, result table and failure files
- Feeds the Power BI report and the daily email
- Keeps run history and the trend per rule
- Reports disabled rules, exclusions and blocked checks
Ixia consultants
- Scope, thresholds and exclusions with the data owners
- Rule development and change control
- Reading the outputs and following up with owners
- Periodic reviews of trends and recurring failures
- Specialist support: governance, migration readiness, reconciliation
Three ways to run it.
Model 2
Ixia-managed monitoring
Ixia operates the monitoring on your estate: reads the outputs, reports to stakeholders, follows up with data owners and proposes rule changes for their confirmation.
Model 3
Hybrid
Your team operates the platform. Ixia reviews trends on an agreed cadence, develops rules and supports programmes such as migration readiness.
Every model runs on your estate. A rule changes only on the data owner’s written confirmation; the reason travels with the rule, and exclusions and disabled rules are visible in the outputs.
Discuss managed data quality.
Tell us which domains, how many sources and who owns the data. We will propose the model that fits and the scope to start with.