Skip to main content

Business Case

Print

Table of Contents

  • Investment Summary Information
  • Investment Detail
  • Investment and Contracts
  • Historic CIO Rating
  • Investment Spending
  • Projects and Activities Detail
Section A: Investment Summary Information
Investment Name
Navy Enterprise Resource Planning
Unique Investment Identifier
007-000000186

Investment Description

The Navy Enterprise Resource Planning (Navy ERP) Program was established to transform and standardize Navy business processes for key acquisition, financial, and logistics operations. Navy ERP combines business process reengineering (BPR) and industry best practices, supported by commercial off-the-shelf software, and integrates all facets of a business, using a single database to manage shared common data. Navy ERP will be a major component of the Navy's Global Combat Support System family of systems and will provide a critical link between operating forces and support activities. Navy ERP will: reduce the Navy's overall costs by applying proven industry best practices and processes and replacing legacy IT systems; facilitate an end-to-end supply chain solution; integrate financial management, workforce management, inventory management, and material operations; and, enable rapid response to operating force logistics needs.
Agency Department of Defense
Point of Contact Hon. Kirsten Davies - CIO
Investment Type Major IT Investments
Bureau Navy, Marine Corps
Mission Support Not Applicable
Shared Service Category Not Applicable
Shared Service Identifier Not Applicable
TMF Initiatives
  • Not Applicable
FY 2025 IT Spending $615.82 M
Current CIO Rating 4
Data As Of: 02/24/2026

Total Projects

7

Cost Variance

  • 7Low
  • 0Medium
  • 0High

Schedule Variance

  • 7Low
  • 0Medium
  • 0High

Cost Variance

  • Low: Projects that have <10% Cost Variance
  • Medium: Projects that have ≥10% and <30% Cost Variance
  • High: Projects that have ≥30% Cost Variance
Cost Variance: ((Planned Total Costs - Projected or Actual Total Costs) / Planned Total Cost) x 100

Schedule Variance

  • Low: Projects that have <10% Schedule Variance
  • Medium: Projects that have ≥10% and <30% Schedule Variance
  • High: Projects that have ≥30% Schedule Variance
Schedule Variance: ((Planned Completion Date - Projected or Actual Completion Date) / Project Duration) x 100
Date Investment First Submitted
11/09/2021
Date of Last Investment Detail Update
02/24/2026
Section B: Investment Detail
  1. Briefly describe the investment's return on investment, including benefits internal and external to the government and outcomes achieved or planned.
Section C: Investment and Contracts

Public URLs

  • www.secnav.navy.mil/rda/pages/programs/erp.aspx
  • www.navair.navy.mil/node/8266
  • www.erp.navy.mil

Contracts

Section D: Historic CIO Rating
Data Last Updated On: 12/23/2025
Section E: Investment Spending

Table 1: Distribution by Spending Type

Spending Type PY 2024 CY 2025 BY 2026
DME Costs 3.487 2.459 0
O&M Costs 578.959 613.36 0
Total 582.446 615.819 0

Table 2: Distribution by Cost Pools

Cost Pools PY 2024 CY 2025 BY 2026
External Labor 498.271 526.598 0
Facilities & Power 0 0 0
Hardware 0 0 0
Internal Labor 20.774 27.004 0
Internal Services 0 0 0
Other 8.965 9.153 0
Outside Services 13.528 20.419 0
Software 40.908 32.645 0
Telecom 0 0 0
Total 582.446 615.819 0
Cost PoolsCost in millions (M)

Table 3: Distribution by IT Towers

IT Tower PY 2024 CY 2025 BY 2026
Application 575.336 608.232 0
Compute 0 0 0
Data 0 0 0
Data Center 0.399 0.416 0
Delivery 0 0 0
End User 0 0 0
IT Management 6.711 7.171 0
Network 0 0 0
Output 0 0 0
Platform 0 0 0
Security & Compliance 0 0 0
Storage 0 0 0
Total 582.446 615.819 0
IT TowersCost in millions (M)
Data Last Updated On: 02/24/2026
Section F: Project Detail

Table 1: Project Details

Project Name Project UID Status Planned Total Cost ($M) Cost Variance (%) Planned Start Date Planned End Date Schedule Variance (%) Schedule Variance (Days) TMF Initiative
Mechanization of Contract Administration System (MOCAS) PA0186-115 In Progress 6739410.2 0 2025-04-23 2026-04-22 0 0 Not Applicable
PCard PA0186-116 In Progress 6739410.2 0 2025-04-23 2026-04-22 0 0 Not Applicable
ePS PA0186-118 In Progress 2660293.5 0 2025-04-23 2026-04-22 0 0 Not Applicable
APSR Dependency PA0186-119 In Progress 15961761 0 2025-04-23 2026-04-22 0 0 Not Applicable
G-Invoicing PA0186-120 In Progress 15961761 0 2025-04-23 2026-04-22 0 0 Not Applicable
Debt Management PA0186-121 In Progress 15961761 0 2025-04-23 2026-04-22 0 0 Not Applicable
Top 10 QCIs PA0186-117 In Progress 2660293.5 0 2025-04-23 2026-04-22 0 0 Not Applicable
LowMediumHigh

Table 2: Project Related Details

Mechanization of Contract Administration System (MOCAS)
  1. Are information technology investments adequately implementing incremental development methodology? (Y/N)
    Yes
  2. What is the frequency of incremental development iterations? (ex. 1 month, 3 months, 6 months, 12 months or greater)
    Months
  3. Please describe the iterative development methodology being employed. (500 characters or less)
    Create Test User IDs, enabling command POs access to functionality before formal UAT to reduce UAT defects. Complete development for reprocessing functionality and new TDO cash balance reporting, enabling error resolution at least two business days faster than the initial design and reducing reconciliation time for end users. Achieve 100% backlog story creation for PI-4, including: Design and Test Documentation review, Cutover, UM Support, Support FISCAM requirements and documents.
PCard
  1. Are information technology investments adequately implementing incremental development methodology? (Y/N)
    Yes
  2. What is the frequency of incremental development iterations? (ex. 1 month, 3 months, 6 months, 12 months or greater)
    Months
  3. Please describe the iterative development methodology being employed. (500 characters or less)
    Regression testing passed for Inbound Interface from US Bank with Card Holder Data, Outbound Interface to US Bank with Purchase Order data, FI Invoice report, PR/PO report, ZRRM0025 Report enhancements, PR Workflow, and PR and PO enhancements. Development and functional unit testing completed for PR and PO enhancements, procurement approval process and PR and PO detail report.
ePS
  1. Are information technology investments adequately implementing incremental development methodology? (Y/N)
    Yes
  2. What is the frequency of incremental development iterations? (ex. 1 month, 3 months, 6 months, 12 months or greater)
    Months
  3. Please describe the iterative development methodology being employed. (500 characters or less)
    May 2025 release QCIs, QCI 31259 (Enhancing PR status report to make it more usable Jun 2025 release QCI, QCI 32352 (Handle PR funds realignment), QCI 32496 (Correct incorrect ePS interface error message) Jul 2025 release QCI, QCI 31591 (Correct Line Of Accounting sent to ePS so that the postings can go to the correct account), QCI 32876 (Resolve interface issues so that text lines can be sent to ePS) ? Finalizing Analysis/Development/Unit testing Nov 2025 release, Prepare for unit testing
APSR Dependency
  1. Are information technology investments adequately implementing incremental development methodology? (Y/N)
    Yes
  2. What is the frequency of incremental development iterations? (ex. 1 month, 3 months, 6 months, 12 months or greater)
    Months
  3. Please describe the iterative development methodology being employed. (500 characters or less)
    APSR Dependency will resolve issues identified as dependencies to the larger APSR auditability effort and covers four BSDs: Carcass Tracking, IDocs, DLA/BLA to ERP URB, NWCF Inventory Valuation. Confirm quality of the solution for Carcass Tracking (reduce billing errors, prevent or reverse erroneous carcass bills increasing auditability, improve interface between Navy ERP and ERMS-NITA, and reduce manual workload), DLA/BLA to URB (resolve dependencies in the URB process, reducing manual workload
G-Invoicing
  1. Are information technology investments adequately implementing incremental development methodology? (Y/N)
    Yes
  2. What is the frequency of incremental development iterations? (ex. 1 month, 3 months, 6 months, 12 months or greater)
    Months
  3. Please describe the iterative development methodology being employed. (500 characters or less)
    Continued to design and build solution for Jun 2025 and Jul 2025 releases. Continued Regression Testing for May 2025 Continued to provide Production support for G-Invoicing issues and non-PROD Cutovers for SP04 (RAB, RG2/FG2) Deploy G-Invoicing Service Pack 04 and enhancements Continue to design and build solution for Jun 2025 and Jul 2025 releases for duplicates in the hub (order/performances). Continue to provide Production support for G-Invoicing and non-PROD Cutovers (D5, T4, F4)
Debt Management
  1. Are information technology investments adequately implementing incremental development methodology? (Y/N)
    Yes
  2. What is the frequency of incremental development iterations? (ex. 1 month, 3 months, 6 months, 12 months or greater)
    Months
  3. Please describe the iterative development methodology being employed. (500 characters or less)
    Refunds, Rejects, and Adjustments features are on track for Jun 2025 release, and RM/QA reviews have started. Sprint 3.6 started on 05/14/25. PI-4 Planning event occurs 05/19/25 - 05/21/25 June 15, 2025: Refund, Reject, and Adjustment functionality for CRS transactions and manual invoice controls July 20, 2025: Full visibility to track CIHO in Navy ERP October 12. 2025: PBIS budget interface and collections functionality, ebilling Output File for
Top 10 QCIs
  1. Are information technology investments adequately implementing incremental development methodology? (Y/N)
  2. What is the frequency of incremental development iterations? (ex. 1 month, 3 months, 6 months, 12 months or greater)
  3. Please describe the iterative development methodology being employed. (500 characters or less)
Section G: Performance Metrics
Metric Description Performance Measurement Category Unit of Measure Reporting Frequency Agency Baseline Capability Measurement Condition Target 2025 CY Latest Actual Result Date of Latest Actual Result Met Target
Availability (Ao) Strategic and Business Results Percentage Monthly Over target 99.5 99.82 2026-01-31 MET
Mean Time Between Mission Critical Failure (MTBMCF) Strategic and Business Results Hours Quarterly Over target 660 1853.92 2026-01-31 MET
Mean Data Assurance (MDA) Strategic and Business Results Percentage Quarterly Over target 99.98 100 2026-01-31 MET
Operation Failure Detection Rate (OFDR) Strategic and Business Results Percentage Quarterly Over target 85 88.7 2026-01-31 MET
Mean Time To Recover (MTTR) Strategic and Business Results Hours Quarterly Under target 8 0.38 2026-01-31 MET
TIER 1 CUSTOMER WAIT TIME Customer Satisfaction Seconds Monthly Under target 90 16 2026-01-31 MET
Meet OSD Obligation Annual Benchmarks (OMN) Financial Performance Percentage Annual Over target 100 100 2025-09-30 MET
Overall Key User Transaction Response Time Strategic and Business Results Seconds Quarterly Under target 10 0.93 2026-01-31 MET
Percent of Help Desk Service Level Targets (SLT) met Customer Satisfaction Percentage Quarterly Over target 90 92.67 2026-01-31 MET
Help Desk Survey Results Customer Satisfaction Points (0-5) Semi-Annual Over target 3 4.62 2026-01-31 MET