NDIA Status Update Navy ERP

1
NDIA Status UpdateNavy ERP

• Presented by Angel L. Maldonado
• Faye Esaias
• Date April 28, 2009

SSC Pacific on Point and at the Center of C4ISR
2
Navy ERP Benefits

• Navy ERP is an integrated business management
  system that modernizes
• and standardizes Navy business operations,
  provides unprecedented
• management visibility across the enterprise, and
  increases effectiveness
• and efficiency.
• Modernizes, standardizes business processes
• SAP software establishes best commercial
  practices
• Common data supports real time information
  exchange
• Provides platform for enterprise-wide
  transformation (Lean/Six Sigma, Activity Based
  Costing, etc.)
• Simplifies operations, enhances visibility into
  the enterprise
• Single entry, single source data, single view of
  organizational status
• Asset visibility allows better management of
  inventories
• End-to-end connectivity, visibility, improves
  reporting and decision-making capabilities
• Increases efficiency, saves money, returns equity
  for other uses
• Retires legacy systems, reduces number of
  applications
• Facilitates federal financial, security standards
  compliance
• Retraining requirements reduced, transportable
  skills increase flexibility

3
Navy ERP Evolution
Initial Operating Capability (May 08)
2011
Milestone C (May 07)
2009
2007
2005
ASN (RDA) directs convergence of pilots
2003
NAVSUP 1.0 Go-Live (Oct 08)
NAVSEA 1.0 Working Capital Fund (Oct 11)
2001
Chief Financial Officers (CFO) Act
NAVAIR 1.0 Go-Live (Oct 07)
NAVSUP 1.1 Single Supply Solution (Feb 10)
Cabrillo Pilot
NAVAIR Pilot SIGMA went Live NAWC, WCF (Jan 03)
1999
NEMAIS Pilot
SIGMA Pilot
NAVSEA 1.0 General FundGo-Live (Oct 10)
SMART Pilot
1990
NAVAIR Pilot SIGMA went Live (GF, Oct 02)
SPAWAR 1.0 Go-Live (Oct 09)
NAVSUP Pilot SMART went Live (Jan 03)
SPAWAR Cabrillo Pilot wentLive (Jul 01)
Pilots Award Contracts toIntegrators
Go Live IOC
NAVSEA Pilot NEMAIS went Live (Jun 02)
Navy Launched 4 Pilot Programs (1999)
DoD Business Environment Driving Navy to ERP
4
Solutions, Applications, and Products (SAP)
Overview
Comprehensive functionality
Business process solutions
SD Sales Distribution
FI Financial Accounting
MM Materials Mgmt.
CO Controlling
Designed for all types of business
Open systems
PP Production Planning
AM Fixed Assets Mgmt.
R/3
Client / Server ABAP/4
QM Quality Manage-ment
PS Project System
Client / server architecture
Multinational
PM Plant Main-tenance
WF Workflow
HR Human Resources
IS Industry Solutions
Over 28,000 installations around the world
Comprehensive implementation supportBusiness
Engineering Workbench
SAP R3 is Unique Because
3
5
Why Navy ERP at SPAWAR?

• Compliance with CFO Act
• Clean-audit financial statement
• Standardization of Team SPAWAR business processes
• Gain and maintain leading competitive edge
• Legacy systems/apps reduction
• A common enterprise business picture
• Consistent and timely information for decision
  making and performance measurement
• Single data entry point
• Seamless integration of shared information
• Production and access to information in near,
  real-time environment

6
Transition Readiness

• Stability of the solution
• Two years of maturity
• Cross-DoD Teams addressing issues and gaps
• Execution of 6 Mocks prior to conversion
  (Load/Validate/Load)
• Pre-validation
• Technical and Business Data Validation
• Full cutover practice
• Availability of sandbox
• Training localization (SPAWAR examples and demos)
• Automated catch-up tools

7
Navy ERP Transition Period

• Notional transition period (1 October 15
  December)
• Some business management activities will rely on
  manual processes to record transactions.
• As a result, only emergent (mission critical)
  contract requirements will be handled during the
  transition phase.
• The theme of SPAWAR preparations for Navy ERP in
  the July through September 2009 timeframe is to
  do things early.
• During this timeframe you may expect to see an
  increase in contract-related activities as our
  project managers and engineers prepare for
  transition to Navy ERP.
• We intend to be proactive in timely execution of
  contract transactions to ensure continuity of
  support throughout the transition period.
• Most large contract actions not expected to be
  impacted during Transition (those not expected to
  be awarded before FOT).

Draft 2009-03-18
8
Navy ERP Transition Period (Continued)

• You are critical to our ability to continue to
  deliver products
• and services to the Warfighter. To facilitate
  our preparations, we
• request you perform the following actions
• Review completion dates of your current vehicles
  with a performance end date during the transition
  period.
• Review your current task orders and contracts
  that are incrementally funded where additional
  funds may be required during the transition
  period.
• Please notify the Contracting Officers
  Representative of that contract or task order to
  initiate the appropriate action in order for
  contract modifications to be executed prior to 1
  October 2009.

Draft 2009-03-18
9
Navy ERP Transition (Continued)

• Material/supplies Ship as much as practicable to
  be received by SPAWAR not later than 30 August
  2009 in order to facilitate receipt and invoicing
  prior to our transition to Navy ERP.
• Service providers Submit timely invoices for
  those services. Invoices received after 1 October
  2009, may experience a delay in processing.
• By taking the aforementioned actions, funding can
  be obligated and you should expect to be paid for
  materials and services in a timely manner.
  Through these planning efforts, we hope to
  minimize the number of manual transactions that
  will be processed during our transition phase of
  implementation.
• As additional information becomes available with
  respect to our implementing Navy ERP, please
  refer to the SPAWAR E-Commerce Central website
  at Https//e-Commerce.sscno.nmci.navy.mil to
  obtain the latest information.

Draft 2009-03-18