Our Current Workforce
This is the number of employees currently in the Application Development Division.
What is 141 (according to Jay)?
This is the approximate annual overhead-funded budget for the division.
What is $28.7 million?
These two OMB A-11 categories classify federal IT spending as operations vs modernization.
What are O&M and DME?
This is the approximate number of business applications currently in our portfolio.
What is 213?
This activity consumes the most leadership time during budget season.
What is manual reconciliation and explanation?
This is the number of FTE visible in our overhead (X90) financial reporting.
What is approximately 92 FTE?
This system is our authoritative financial source for WBS and labor charges.
What is SAP?
This federal framework maps IT cost pools to IT services and business units.
What is Technology Business Management (TBM)?
This role is accountable for business outcomes of an application.
What is a Business Owner?
This is the question Jay gets asked that is hardest to answer quickly.
What is “Where does our capacity actually go?”
This number tells us how many non-AppDev employees are charging time to our WBS codes.
What is… we don’t have a single report for that?
This number represents the total cost of an individual application including labor, subcontract, and shared services.
What is… not something we can pull with one query?
This is the percentage of our division’s spending currently categorized as O&M vs DME.
What is… not something we can state confidently division-wide?
This number represents how many applications currently lack a clearly documented business owner.
What is… not something we can verify in one report?
This tension arises when direct-funded work increases but overhead capacity stays fixed.
What is resource contention?
This percentage tells us how much of total division effort goes to direct-funded (sold services) work.
What is… not something we can answer quickly?
This percentage represents how much of our subcontract budget is concentrated in S/4HANA-related efforts.
What is approximately 39%?
This number tells us how much of our cost is “run the business” vs “transform the business.”
What is… not reconciled across all funding streams?
This number tells us the full lifecycle cost of keeping an application alive each year.
What is… not something we can produce cleanly?
This is what happens when cross-divisional labor charges are not explicitly planned.
What is cost opacity?
This is the reconciled total FTE across overhead, direct-funded, subcontract, and cross-divisional labor.
What is… we cannot produce that in one place?
This metric tells us whether sold services are subsidized by overhead-funded capacity.
What is… not something we explicitly measure?
If DOE asked for cost per IT service aligned to TBM layers, this is the dataset we would use.
What is… multiple spreadsheets and partial exports?
This metric would show which applications consume the most sustainment effort.
What is… not visible division-wide without manual reconciliation?
This capability would make planning predictable instead of reactive.
What is unified capacity visibility?
If Lab leadership asked for our total ecosystem capacity including shared dependencies, this is where we would go.
What is… there isn’t one authoritative source?
This view would reconcile budget, labor source, funding type, and product cost in a single report.
What is… something we do not currently have?
This gap prevents us from cleanly aligning to federal reporting expectations.
What is lack of unified cost-to-service visibility?
This question should be easy: “What does this application cost us annually?”
What is… harder to answer than it should be?
If we had one place that reconciled headcount, FTE allocation, funding source, and application cost, this is what we would gain.
What is clarity and control over a $28.7M portfolio?