DoD FM

Dormant Obligation Detection Agentic Workflow Automation

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

Description

Coordinate multistep tasks for dormant obligation detection: gather data, build an evidence package, draft analysis, route for review, and record decisions with audit logs. The MVP would connect GFEBS, Navy ERP, DEAMS, DAI, EFDSS, Advana, obligation/outlay history and produce read-only recommendations for OUSD(C), DFAS, Service Comptrollers.

AI / analytics pattern

agentic AI + workflow orchestration

Automation level / stage

supervised workflow automation

Expected benefit

End-to-end productivity gain while preserving human signoff and auditability.

Audit / financial statement impact

Statement of Budgetary Resources; obligations incurred; unobligated balance

Controls / human review

Human approval required before posting, payment, denial, personnel action, or official audit response; model validation; drift monitoring; exception sampling; full prompt/data/output logging. Agent must operate in read-only or draft mode during MVP; all postings/payments/responses require named human approval.

Data needed

GFEBS, Navy ERP, DEAMS, DAI, EFDSS, Advana, obligation/outlay history; master/reference data; audit logs; policy/control requirements; prior exceptions; relevant document evidence.

Possible metrics

cycle time reduction; workflow completion rate; human override rate; audit log completeness

MVP scope

Start with one Component/reporting entity and one subprocess (dormant obligation detection) for two close/audit cycles; read-only outputs first.

Related material weakness / control objective

High-integrity funds control environment, appropriation controls