Evidence Sufficiency Scoring Anomaly Detection
Description
Detect unusual patterns in evidence sufficiency scoring using transaction features, user behavior, timing, amount, fund/account, and historical peer benchmarks. The MVP would connect Advana, audit management tools, NFR repositories, CAP trackers, IPA requests, evidence stores and produce read-only recommendations for OUSD(C), DoD OIG, Service audit remediation offices, DFAS.
AI / analytics pattern
ML anomaly detection
Automation level / stage
human-in-the-loop alert triage
Expected benefit
Higher detection coverage, fewer missed exceptions, better prioritization of high-risk items.
Audit / financial statement impact
Audit opinion; audit support; control testing; evidence sufficiency
Controls / human review
Human review for exceptions and recommendations; maintain evidence packages, lineage, source citations, model cards, data-quality checks, and periodic QA sampling. Do not use alerts as sole basis for adverse action; require sampled validation and feedback loop.
Data needed
Advana, audit management tools, NFR repositories, CAP trackers, IPA requests, evidence stores; master/reference data; audit logs; policy/control requirements; prior exceptions; relevant document evidence.
Possible metrics
precision/recall of alerts; dollars reviewed; false-positive rate; high-risk exception closure time
MVP scope
Start with one Component/reporting entity and one subprocess (evidence sufficiency scoring) for two close/audit cycles; read-only outputs first.
Related material weakness / control objective
NFR remediation and auditability