POET project setup, FEMA grant billing, multi-funded splits. What the user says, what the agent does, what Oracle executes.
▶ User:
"Create FEMA Hazard Mitigation project for Hurricane Ian recovery — TAS 070-25-0702, $15M ceiling, three task types: planning, construction, admin"
// Agent Actions
1 Creates Oracle Project with FEMA-standard POET structure: Project (Hurricane Ian) → Organization (FEMA HMGP) → Expenditure Types (Planning/Construction/Admin) → Tasks
2 Configures project budget by TAS 070-25-0702 with ADA fund control at task level — prevents over-obligation per task ceiling
3 Sets up project class codes (grant type, CFDA number, awarding agency) for federal reporting
4 Links project to Oracle Grants module for billing and draw request generation
🔗 Oracle Action:
Creates PA_PROJECTS record, POET hierarchy, budget lines by task, fund control rules, and grants linkage via Oracle SOA Gateway
✅
FEMA project live in Oracle in 30 minutes — full POET structure, $15M fund control active by task, CFDA codes set, ready for first expenditure charge.
▶ User:
Uploads FEMA Notice of Award PDF + "Create the grant award in Oracle — $8.2M BRIC grant, 36-month period, match requirement 25%"
// Agent Actions
1 Extracts grant terms from NoA PDF: award number, CFDA 97.047, period of performance, federal share, non-federal match %
2 Creates Oracle Grants Award record with sponsor (FEMA), award type (Cost Reimbursable), billing cycle (monthly)
3 Configures 25% match tracking: segregates federal vs. non-federal expenditures by expenditure type
4 Sets up automatic billing event triggers at each reporting milestone per the grant agreement
🔗 Oracle Action:
Creates GMS_AWARDS record, billing terms, match tracking rules, and milestone billing schedule from NoA data
✅
BRIC grant award in Oracle in 45 minutes — $8.2M award configured, 25% match tracking active, monthly billing cycle ready, all NoA terms captured.
▶ User:
"Run June billing for all active FEMA grants — generate SF-270 draw requests for reimbursable expenditures"
// Agent Actions
1 Queries all unbilled project expenditures charged to active FEMA grants through June 30
2 Applies billing exclusion rules: removes unallowable costs per FAR Part 31 and grant-specific restrictions
3 Generates billing invoice by grant with federal share calculation (expenditures × federal cost share %)
4 Formats SF-270 Request for Advance or Reimbursement for each grant and queues for submission to FEMA
🔗 Oracle Action:
Runs Oracle Projects Billing process, generates AR invoices per grant, produces SF-270 output via custom extract
✅
All June FEMA draw requests generated in 20 minutes — SF-270s ready for submission, unallowable costs excluded, federal share correctly calculated by grant.
▶ User:
"Set up burdening for FEMA grants — apply 28% indirect cost rate to salaries and direct costs, exclude equipment purchases per grant terms"
// Agent Actions
1 Creates Burden Schedule with 28% indirect cost rate (approved NICRA rate) effective from grant start date
2 Configures burden exclusion rules: expenditure type "Equipment" excluded from indirect cost base per grant terms
3 Maps burden cost codes to USSGL accounts: indirect costs → USSGL 6100 (Operating Expenses) with correct TAS
4 Tests burdening with sample transaction; verifies 28% indirect applied to salary, zero burden on equipment
🔗 Oracle Action:
Creates PA_BURDEN_SCHEDULES, burden cost codes, exclusion rules by expenditure type, and USSGL account mapping
✅
NICRA burdening active on all FEMA grants in 2 hours — 28% indirect auto-applied to allowable costs, equipment excluded, indirect costs flowing to correct USSGL accounts.
▶ User:
"Coastal resilience project is funded 60% FEMA (TAS 070-0702) and 40% HUD CDBG-DR (TAS 086-0181) — configure the cost split in Oracle"
// Agent Actions
1 Configures Oracle Projects funding allocation: 60% of expenditures charged to TAS 070-0702, 40% to TAS 086-0181
2 Creates separate billing terms per funding source — FEMA billed monthly, HUD CDBG-DR billed quarterly
3 Configures split cost distribution rules so individual transactions auto-split at the correct percentage at posting
4 Sets up fund control at the funding-source level — each TAS has its own ceiling and ADA check
🔗 Oracle Action:
Creates multi-funding source structure in Oracle Grants, configures AutoAccounting split rules, activates per-source fund control
✅
Dual-funded project split active in 1 hour — every expenditure auto-splits 60/40 at posting, separate billing cycles per sponsor, independent ADA fund control per TAS.
▶ User:
"Show me budget vs. actual for all active FEMA grants — flag any projects burning faster than expected and projects under 50% utilized past midpoint"
// Agent Actions
1 Queries Oracle Projects for all active FEMA grants: budget, commitments, expenditures, and remaining balance by task
2 Computes burn rate: YTD expenditures ÷ elapsed % of period of performance → flags grants burning >120% of expected rate
3 Flags under-utilized grants: <50% expended at midpoint (risk of funds lapsing or de-obligation by FEMA)
🔗 Oracle Action:
Queries PA_BUDGET_LINES and PA_EXPENDITURE_ITEMS, computes burn rate metrics, generates management report with exception flags
✅
FEMA portfolio status report in 10 minutes — over-burn and under-utilization flags surfaced, CFO can act before funds lapse or de-obligation risk triggers.
▶ User:
"FEMA HMGP grant 1234-DR-FL is complete — run closeout, generate final SF-425 Federal Financial Report, and release any unspent balance"
// Agent Actions
1 Verifies all expenditures are billed and collected — identifies any outstanding receivables or unbilled costs
2 Generates final SF-425 Federal Financial Report: total federal expenditures, recipient share, program income
3 Calculates unspent balance to be de-obligated and returned to FEMA; prepares refund transaction if applicable
4 Closes Oracle Grant Award and Projects, updates TAS 070-0702 fund balance, archives documentation
🔗 Oracle Action:
Closes GMS_AWARDS and PA_PROJECTS records, generates SF-425 extract, processes refund AR credit memo, releases fund balance
✅
Grant closeout complete with final SF-425 in 2 hours — all expenditures reconciled, SF-425 ready for FEMA submission, unspent balance de-obligated, Oracle records closed.