Data quality check
None of the held texts sets a fixed period on this consumer; every row below reads no period set by the text. Paste one job that feeds this consumer, for example dq_freshness_check, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.
Matched on the job name or the consumer column by these words: dq check, data quality, quality check, validation run, freshness check, dq , DQ check.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| ISO/IEC 25012:2008 named reference | no clock | ISO/IEC 25012 Currentness Currentnessquoted below |
| BCBS 239 named reference | no clock | BCBS 239 Principle 7 Accuracy (Reporting)quoted below |
Named reference beside this class, ISO/IEC 25012 Currentness Currentness: The degree to which data have attributes that are of the right age in a specific context of use; the acceptable age depends on the use, from real time to historical. A data quality requirement, measure or evaluation using the model is categorised under this characteristic (inherent point of view).
Named reference beside this class, BCBS 239 Principle 7 Accuracy (Reporting): Risk management reports should accurately and precisely convey aggregated risk data and reflect risk in an exact manner. Reports should be reconciled and validated.
Questions this page answers
What does the register ask the owner of a data quality check job?
What does the check do when it fails: stop the downstream job, or write a line nobody reads?
The clauses in full
The degree to which data have attributes that are of the right age in a specific context of use; the acceptable age depends on the use, from real time to historical. A data quality requirement, measure or evaluation using the model is categorised under this characteristic (inherent point of view).
What an assessor asks to see: Timestamps and refresh cadence per data set against the use's tolerance. Where it usually falls short: Reference data refreshed yearly for a daily decision
Risk management reports should accurately and precisely convey aggregated risk data and reflect risk in an exact manner. Reports should be reconciled and validated.
What an assessor asks to see: Reconciliation and validation procedures for risk reports prior to distribution; Defined accuracy requirements and validation sign-offs for reports; Documentation of report data sources and calculation methods; Error log and correction process for risk reports. Where it usually falls short: Reports distributed without validation or reconciliation
Requirement text quoted from the standards themselves, published at compliance.theartofservice.com, the same publisher as this register, read against the held text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register