What exactly are we building on top of Costpoint?
A reporting solution shaped around your own contract structure — not a template. We map your projects, tasks, organizations, cost pools, labor categories, and contract lines into a governed semantic model, write the measures that define burden, margin, and cost-to-complete the way your finance team defines them, then maintain that model as programs are added and closed. You review; we build and keep it running.
The gap is rarely that Costpoint lacks the data — it holds more of it than most systems. It is that answering "which programs eroded fee last quarter, and was it labor mix or an indirect rate drifting off provisional?" means running several reports and reconciling them in Excel. A semantic model collapses that into one page with drill-down to the charge. The discipline behind it — grain, dimensions, and measures that agree with each other — is the same work described on our Power BI data modeling and DAX page.
One clarification worth making early, because it decides which page you actually need: Costpoint and Vantagepoint are different Deltek products for different businesses. Costpoint is Deltek's ERP for government contracting and defense — Deltek describes it as built for government contracting organizations that need compliance controls built in (opens in new tab), aligned to FAR and DFARS. Vantagepoint serves architecture, engineering, and consulting firms, where the reporting question is utilization and backlog rather than indirect rates and contract ceiling. If your firm runs Vantagepoint instead, the equivalent build for AE professional-services metrics is on our Deltek Vantagepoint Power BI dashboard page. A third possibility is that neither Deltek product is your system of record: contractors and AE practices that consolidated projects and accounting onto Unanet report from a Data Lake replica rather than the ERP database directly, and that build is covered on our Unanet Power BI dashboard page.
Which Costpoint reports do government contractors ask for first?
Six areas cover most first engagements: project and job cost by task, indirect rates and cost pools, WIP and unbilled, funding against incurred cost, contract modifications and ceiling, and labor by contract. Each becomes a page in one model instead of a separate report someone has to run and reconcile.
Indirect rates are the one finance argues about most, because the definition matters more than the visual: which pools carry which bases, whether the view shows actual, provisional, or forward-priced rates, and how far into the fiscal year the actuals are meaningful. We pin those rules down with you before building and encode them once as measures, so every page agrees. Job cost and cost-to-complete answer the program question — is the estimate at completion still credible, and which task is drifting — and funding burn-down flags a ceiling problem while there is still time to raise it with the contracting officer, rather than at closeout.
Contractors doing federally funded construction work add a further layer: prevailing-wage labor hours and cost by project, so exposure is visible before an audit. We report that from Costpoint labor data, but we are precise about the boundary — Deltek documents certified payroll reporting under its construction accounting products (opens in new tab) rather than Costpoint, and the WH-347 filing itself belongs to your payroll system, not to a dashboard. Contractors who also run commercial job cost alongside their federal work will find the job-costing, WIP, and change-order patterns on our Power BI for construction page a close match. And if your finance team sits in the capital region, our Power BI consultant Washington DC page covers how these engagements run for DC, Maryland, and Northern Virginia contractors — Eastern-time delivery, on-site sessions arranged in advance, and how contract type changes the model before it changes the visuals.
Where Costpoint's own reporting stops and the dashboard picks up
Here is an honest view of the difference, area by area. It is the same data in both columns — the change is that it becomes cross-contract, trendable, and drillable instead of a report you run one question at a time.
Costpoint reporting areas and what the custom Power BI build adds
| Costpoint reporting area |
What Costpoint holds |
Power BI version we build |
| Project accounting & job cost |
Direct and indirect charges posted against project, task, and organization |
Job cost and cost-to-complete by task, trended, with drill from program summary to the individual charge |
| Indirect rates & cost pools |
Pool, base, and burden calculations that support any contract type |
Actual versus provisional rates by pool, trended by month, with the programs most exposed to a variance ranked |
| WIP & unbilled |
Revenue recognition and unbilled balances as of a period |
Aging buckets, movement since the last billing run, and the owners of the oldest balances |
| Contract funding & modifications |
Contract values, funding, and mods recorded in contract management |
Funding consumed against ceiling with burn-down by month, and the value added by each mod against what it actually cost |
| Labor & timekeeping |
DCAA-compliant timekeeping with labor captured against charge codes |
Labor hours and cost by contract, category, and organization, with uncharged or mischarged time surfaced early |
| Prevailing-wage labor (certified payroll) |
The labor detail behind federally funded construction work |
Hours and cost by project and labor category for management visibility — the WH-347 filing stays in your payroll system |
How do you connect Deltek Costpoint to Power BI?
Through whichever supported route your deployment allows: Costpoint's documented web services, a read-only copy of the SQL Server database behind it, a reporting data mart your IT team already stages, or scheduled extracts for small and stable pulls. We confirm the route with your Costpoint administrator in the scope estimate, before any hours are used.
Which one fits depends on where your instance runs and how much history you need. Cloud-hosted contractors usually go through the documented interfaces with a scoped, read-only service account. Organizations on their own or a hosting partner's servers often get better results from a read-only database copy, because it lets us pull years of charge and timekeeping history incrementally rather than asking a production system for it. If a data mart already exists — and many Costpoint sites have one staged for their Cognos-based Costpoint Business Intelligence reporting — we build on it, because one copy of the extract logic beats two. Whatever the route, we land the data, refresh only changed rows, and let the report query the modeled copy rather than pointing Power BI at production and hoping.
Refresh then runs inside Microsoft's documented limits: their data refresh reference (opens in new tab) sets out the cadence available on each licence, and where the source sits on your own network — common for contractors who keep the ERP inside their own boundary — an on-premises data gateway (opens in new tab) carries the connection. We configure it, document it, and fix breakages out of your banked hours — the maintenance part that connector tools leave to you. We are not affiliated with Deltek or Microsoft and never imply a partnership; we use their supported, documented interfaces to your own data.
What does a build like this cost, and how long does it take?
You buy prepaid Flex hours that never expire: Starter $2,500, Growth $4,600, or Power $8,000, with hours from $100. There is no project minimum and no retainer — you send a request, we reply with a scope and the hours it needs, and hours deduct only for work you approve.
The usual pattern for an ERP build is a Growth or Power block: the connection, the model, and the first pages are front-loaded, and the remaining hours go to extra views, measure changes, and refresh care over the following months. Most individual tasks ship in 3–5 business days once you approve the estimate; a first full contract-wide build is larger and gets a clear timeline up front. If you want the general cost picture before you talk to anyone, our guide to what a Power BI dashboard costs to build breaks down the drivers, and how prepaid Flex hours work covers the mechanics.
Who is this for, and what do you own at the end?
Government contractors and aerospace and defense firms running Costpoint — primes and subs, services and manufacturing alike — usually where a CFO, controller, or program finance lead is tired of assembling the same workbook before every review. Organizations with no in-house BI team get the most out of it, because the maintenance is included in the model rather than added to someone's job. To be clear about scope: we build management reporting, not compliance filings. Dashboards show indirect-rate drift, funding exposure, and labor by contract so leadership sees a problem early, but your accountants and your Costpoint configuration remain the system of record for anything submitted to a contracting officer or an auditor.
You own everything: the report file, the semantic model and measures, the extraction logic, the refresh schedule, and the service account all live in your tenant and your instance. There is no black box and no licence to us — if you never send another request, the dashboards keep running. Contact is form-only: send your request and we reply with a scope estimate.