DoD FM

Pbc Request Routing Policy-Aware Copilot

High priorityLow-Medium riskDerived/normalized from public DoD FM source and established financial-sector AI patternTier 0 — Audit data foundationLow-Medium complexity

Description

Answer policy, FMR, FIAR, and local SOP questions for PBC request routing using approved sources; provide citations and draft compliant next steps. 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

LLM + retrieval-augmented generation

Automation level / stage

human-facing assistant

Expected benefit

Improved policy consistency, shorter research time, better training and compliance support.

Audit / financial statement impact

Audit opinion; audit support; control testing; evidence sufficiency

Controls / human review

Source-grounded answers only; disclaimer for policy/decision support; user feedback loop; content QA and access controls. RAG answers must cite approved sources; no free-form legal/financial determinations without policy owner review.

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

citation accuracy; first-contact resolution; user satisfaction; policy answer QA pass rate

MVP scope

Start with one Component/reporting entity and one subprocess (PBC request routing) for two close/audit cycles; read-only outputs first.

Related material weakness / control objective

NFR remediation and auditability