Navy ERP:  Roadmap to Enterprise Business Transformation Filename/RPS Number Beverly Veit  May 27, 2009
Agenda <ul><li>Enterprise Business Office Stand up </li></ul><ul><li>Program of Record Roll Out Schedule  </li></ul><ul><l...
Navy Enterprise Business Office (EBO) (Stand up) <ul><li>Chief Management Officer (CMO)/Deputy CMO(DCMO) –  created by Nat...
Navy Enterprise Business Office - Continued <ul><li>Evaluate Procure to Pay End to End process for improvement opportuniti...
Program of Record Roll Out Schedule <ul><li>Release 1.0  </li></ul><ul><ul><li>Naval Air Systems Command (NAVAIR) – Octobe...
Business Backbone Rollout Strategy <ul><li>Accelerated approach implements Navy ERP solution with minimal development / mo...
NAVAIR/NAVSUP Sustainment <ul><li>Naval Air Systems Command (NAVAIR)  (1 October 2007)   </li></ul><ul><ul><li>Transition ...
Refinement and Standardization of Operations  <ul><li>Automated Service Entry Sheets  </li></ul><ul><ul><li>Service Entry ...
‘Go Live’ Preps for SPAWAR/NAVSEA <ul><ul><li>Space and Naval Warfare Systems (SPAWAR) </li></ul></ul><ul><li>SPAWAR Statu...
Navy ERP Release 1.1 – Single Supply Solution Overview <ul><li>Sourcing </li></ul><ul><li>Req. processing </li></ul><ul><l...
Types of Testing Integrated System Test (IST) Cycle 1, 2 & 3, User Acceptance Testing (UAT), Operational Assessment (OT-C2...
Update on Implementation -  Release 1.1 Filename/RPS Number <ul><li>Release 1.1 Cycle 1 Testing Completed </li></ul><ul><u...
Summary <ul><li>Navy ERP is the  Cornerstone  of our FM framework for DON Business Transformation  </li></ul><ul><ul><li>S...
Backup
NAVY ERP CONVERGENCE DoD Business Environment Driving Navy to ERP Chief Financial Officer’s (CFO) Act 2003 ASN (RD&A) dire...
Navy Financial Management Systems Transition Summary Legacy Environment Target Environment
Current Enterprise Metrics <ul><li>Internal Entitlement </li></ul><ul><ul><li>% Acceptance, WAWF Vendor Pay </li></ul></ul...
OBJECTIVE 95% THRESHOLD 85% FUTURE: -CLIN/SLIN MISMATCH +10% -7 WYs ELIN CROSS REFERENCE TABLE + 8% (JAN 09 DELIVERY, METR...
Test Schedule – Release 1.1 Testing Events Date/Periods Test Readiness Review – Cycle 1 5 Feb 2009 <ul><ul><li>Cycle 1 Tes...
Upcoming SlideShare
Loading in...5
×

Navy ERP: Roadmap to Enterprise Business Transformation

2,850

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,850
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
76
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Navy ERP: Roadmap to Enterprise Business Transformation

  1. 1. Navy ERP: Roadmap to Enterprise Business Transformation Filename/RPS Number Beverly Veit May 27, 2009
  2. 2. Agenda <ul><li>Enterprise Business Office Stand up </li></ul><ul><li>Program of Record Roll Out Schedule </li></ul><ul><li>Business Backbone Rollout Strategy </li></ul><ul><li>NAVAIR/NAVSUP Sustainment </li></ul><ul><li>Refinement and Standardization of Operations </li></ul><ul><li>‘ Go Live’ Preps for SPAWAR/NAVSEA </li></ul><ul><li>Navy ERP Release 1.1 </li></ul><ul><li>Summary </li></ul>
  3. 3. Navy Enterprise Business Office (EBO) (Stand up) <ul><li>Chief Management Officer (CMO)/Deputy CMO(DCMO) – created by National Defense Authorization Act (2009) Sec 209 </li></ul><ul><ul><li>Directed Military Department to establish an Office of Business Transformation </li></ul></ul><ul><ul><li>DCMO issued memo 8 May 2009 – establishing the EBO as part of the Navy Office of Business Transformation </li></ul></ul><ul><li>Navy EBO Mission and Objective : </li></ul><ul><ul><li>Integrate the acquisition, finance, logistics, and supply chain management functions into defined end-to-end, compliant business processes </li></ul></ul><ul><ul><li>Define business value metrics that measure the efficiency of these business processes as implemented in operating procedures (i.e. time required to process a given contract type) </li></ul></ul><ul><ul><li>Define enterprise policies for business processes, adjudicating contradictions in acquisition and finance regulations within the Department and with OSD </li></ul></ul><ul><ul><li>Create and oversee a transparent process for program office resource allocation decisions between user change requests and deployment requirements. </li></ul></ul>Filename/RPS Number
  4. 4. Navy Enterprise Business Office - Continued <ul><li>Evaluate Procure to Pay End to End process for improvement opportunities : </li></ul><ul><ul><li>Policy/Procedure Memos issued 15 May 2009: Acquisition/Contract/Finance communities – Alignment of acquisition, contract, finance, logistics data in Procure 2 Pay process </li></ul></ul><ul><ul><li>Emphasis of policy memo to ensure coordination in the beginning of P2P process that the appropriate level of line item details is created in the Purchase Requisition and Contract to eliminate many of disconnects during pre-validation/invoice payment/receipt later in process </li></ul></ul><ul><li>Develop Business Value/Strategy </li></ul><ul><ul><li>Communicate Enterprise metrics that provide insight into the Business Health when operating within the Navy ERP solution </li></ul></ul><ul><ul><li>Standardized process for pulling metric information from the official system of record with consistent reporting across SYSCOMs </li></ul></ul><ul><ul><li>Standardized process for evaluating results from an end-to-end process </li></ul></ul><ul><ul><li>Documented processes that are stable and repeatable </li></ul></ul><ul><li>Develop Standard Business Process Documentation and Std Operating Procedures </li></ul><ul><ul><li>Evaluate work done to date by Process Owners (FM&C), NAVAIR/Contractors – leverage & edit to bring up to Enterprise level </li></ul></ul><ul><ul><li>Standardizing and consolidating end to end business processes across the Navy enterprise </li></ul></ul><ul><ul><li>Focus on completing business documentation for the Procure to Pay, Internal Entitlement process. </li></ul></ul><ul><ul><li>Prior to SPAWAR go-live goal: to develop SOPs of the internal entitlement process, i.e. electronic invoice processing, Purchase card, Pre-Purchase Requisition/Purchase Requisition, F110 Processing, creation of service entry sheet etc. </li></ul></ul>Filename/RPS Number
  5. 5. Program of Record Roll Out Schedule <ul><li>Release 1.0 </li></ul><ul><ul><li>Naval Air Systems Command (NAVAIR) – October 2007 (FY 08) </li></ul></ul><ul><ul><li>Naval Supply Systems Command (NAVSUP) HQ, FISC, ICP – October 2008 (FY 09) </li></ul></ul><ul><ul><li>Space and Naval Warfare Systems (SPAWAR) HQ, SSC – October 2009 (FY 10) </li></ul></ul><ul><ul><li>Naval Sea Systems Command (NAVSEA) HQ (GF activities) – October 2010 (FY 11) </li></ul></ul><ul><ul><li>Naval Sea Systems Command (NAVSEA) WC (NWCF activities) – October 2011 (FY 12) </li></ul></ul><ul><ul><li>Strategic Systems Programs (SSP) and Office Naval Research (ONR) – October 2012 (FY 13) </li></ul></ul><ul><li>Release 1.1 </li></ul><ul><ul><li>Naval Supply Systems Command (NAVSUP) – February 2010 </li></ul></ul>Filename/RPS Number
  6. 6. Business Backbone Rollout Strategy <ul><li>Accelerated approach implements Navy ERP solution with minimal development / modifications to accommodate SYSCOM specific desires: </li></ul><ul><ul><li>Current POC kept in tact – developing acquisition strategy to have business backbone managed as a separate program </li></ul></ul><ul><ul><li>Limited Gap Analysis (only 4 Shipyards, FRCs, and NAVFAC) </li></ul></ul><ul><ul><li>Conversion of master data only </li></ul></ul><ul><ul><li>Rollout schedule being developed </li></ul></ul><ul><ul><li>Navy ERP PMO preparing a questionnaire so they can gain an understanding of Commands’ functions </li></ul></ul><ul><ul><li>Commands responsible for organic costs (end user training, master data conversion, change management) </li></ul></ul><ul><li>Accelerated approach timeline: </li></ul><ul><ul><li>D-12, Receiving organization obtains Getting Started briefs and technical documentation from ERP website: </li></ul></ul><ul><ul><ul><li>Getting Started, 1.0 Walk-thru, ARIS Models, Role Matrix, Reports Catalogue, Business Process Overviews, Business Process Matrix </li></ul></ul></ul><ul><ul><li>D-11, Initial meeting with ERP team to obtain organization structure, define data cleanup requirements, and perform basic preparation work </li></ul></ul><ul><ul><li>D-6, ERP team uploads org. structure and starts LSO </li></ul></ul><ul><ul><li>D-5, Train-the-trainer begins </li></ul></ul><ul><ul><li>Go-Live </li></ul></ul><ul><ul><li>On Site-Support continues for 6 months after Go-Live </li></ul></ul>
  7. 7. NAVAIR/NAVSUP Sustainment <ul><li>Naval Air Systems Command (NAVAIR) (1 October 2007) </li></ul><ul><ul><li>Transition Days - 77 </li></ul></ul><ul><ul><li>Trained and Deployed to 14,265 users at 9 sites </li></ul></ul><ul><ul><li>145,858 Roles assigned </li></ul></ul><ul><ul><li>21,000 Test scripts executed </li></ul></ul><ul><ul><li>14,834,338 master and transactional data objects converted </li></ul></ul><ul><ul><li>99.8% data load success rate </li></ul></ul><ul><li>IOC - May 2008 </li></ul><ul><li>Naval Supply Systems Command (NAVSUP) (1 October 2008) </li></ul><ul><ul><li>Transition days - 25 </li></ul></ul><ul><ul><li>Trained and deployed to 6,222 users at x sites </li></ul></ul><ul><ul><li>8,427 Roles assigned </li></ul></ul><ul><ul><li>338,023 master data objects converted </li></ul></ul><ul><ul><li>99.78% data load success rate </li></ul></ul>
  8. 8. Refinement and Standardization of Operations <ul><li>Automated Service Entry Sheets </li></ul><ul><ul><li>Service Entry Sheets are being manually entered by DFAS/NAVAIR personnel for external entitled pre-validation of invoices. Navy ERP concept of operations calls for a 3-way match which is already captured in the external entitlement system. </li></ul></ul><ul><ul><li>Navy ERP recently implemented the automation of Service Entry Sheets since the receipt and invoice data is already captured in MOCAS. </li></ul></ul><ul><ul><li>The benefit of automating the SES is that it will save 12 FTE’s. </li></ul></ul><ul><li>Data Roll-up </li></ul><ul><ul><li>Early on root cause of pre-validation and disbursement mismatches was identified as a misalignment of transaction detail (contract/obligation, invoice, and receipt). </li></ul></ul><ul><ul><li>Navy ERP implemented CLIN/SLIN/ELIN rollup to enable system to automatically match at the lowest level of detail available. </li></ul></ul><ul><ul><li>Navy DCMO recently published guidance requiring a process to align pre-contract award finance, procurement, and logistics planning with post-contract award administration of finance procurement, and logistics operations. </li></ul></ul>Navy ERP continues to refine the configuration of the system to improve efficiency and reduce the level of manual intervention required. 27 ECP’s have been approved by the NESIB. 17 draft ECP’s are in various stages of requirements definition. Examples of system changes: VENDOR PAY: % ACCEPTANCE COMMERCIAL PAY (MAJOR CONTRACTS)
  9. 9. ‘Go Live’ Preps for SPAWAR/NAVSEA <ul><ul><li>Space and Naval Warfare Systems (SPAWAR) </li></ul></ul><ul><li>SPAWAR Status Update </li></ul><ul><ul><li>Mock Data Conversion : </li></ul></ul><ul><ul><ul><li>Mock 5 to be completed 27 May 09 -- reviewing the General Ledger throughout the Mock as well as the addition of Business Data Validation has provided SPAWAR/Navy ERP the ability to correct data related issues immediately upon discovery. </li></ul></ul></ul><ul><ul><ul><li>Cutover Practice to begin 1 June 09 -- this practice will include both Data Conversion and Business Data Validation as well as a Catch Up practice in which numerous catch up transactions will be tested within the Navy ERP mock client . </li></ul></ul></ul><ul><ul><li>Operations/Cutover/Transition: </li></ul></ul><ul><ul><ul><li>Workforce Management (WFM) early go-live is on schedule. Select WFM data will be loaded into Production in July to ensure that Echelon II will be ready to perform their Time and Attendance (T&A) entry in Navy ERP on 1 Oct 09. </li></ul></ul></ul><ul><ul><ul><li>Navy ERP/SPAWAR are currently reviewing the Cutover plan ensuring each task is on schedule for completion and capturing any action items/issues. </li></ul></ul></ul><ul><ul><ul><li>Navy ERP PMO has stated SPAWAR data conversion will not impact commands already operating in SPAWAR </li></ul></ul></ul><ul><ul><li>Key Near Term Tasks: </li></ul></ul><ul><ul><ul><li>Cutover Practice Workshop – 6 May 09 </li></ul></ul></ul><ul><ul><ul><li>War Room Full Operational Tempo – 15 May 09 </li></ul></ul></ul><ul><ul><ul><li>Start Cutover Practice – 1 Jun 09 </li></ul></ul></ul><ul><ul><li>Naval Sea Systems Command (NAVSEA) </li></ul></ul><ul><li>NAVSEA Status Update </li></ul><ul><ul><li>Road Map Under Development </li></ul></ul><ul><ul><li>ERP workshops held November 2009 - February 2009 to begin orientation of NAVSEA employees to ERP functionality </li></ul></ul><ul><ul><li>Data Conversion Strategy Agreed Upon </li></ul></ul><ul><ul><li>Major Change Management initiative underway associated with re-engineering Shipbuilding Contract Execution/Administration </li></ul></ul><ul><ul><li>Mock Data Conversion began in May 2009 </li></ul></ul><ul><ul><li>Sandbox has been delivered so NAVSEA can become more familiar with ERP functionality and determine impact to business processes. </li></ul></ul>
  10. 10. Navy ERP Release 1.1 – Single Supply Solution Overview <ul><li>Sourcing </li></ul><ul><li>Req. processing </li></ul><ul><li>Available to promise </li></ul><ul><li>Shipping </li></ul><ul><li>Material movements </li></ul><ul><li>Goods Receipts </li></ul><ul><li>Whse. Management </li></ul><ul><li>Physical inventories </li></ul><ul><li>Demand Capture </li></ul><ul><li>Forecasting </li></ul><ul><li>Simulations </li></ul><ul><li>Buy vs. Repair </li></ul><ul><li>Deployment </li></ul><ul><li>Inventory balancing </li></ul><ul><li>Surplus & Obsolescence </li></ul><ul><li>Terminations </li></ul><ul><li>Financial and Logistics </li></ul><ul><li>Integrated Requirements </li></ul><ul><li>Report </li></ul><ul><li>Redistributions </li></ul><ul><li>Contracts </li></ul><ul><li>Awards </li></ul><ul><li>Commercial Repair </li></ul><ul><li>Sub-contracting </li></ul><ul><li>Organic Navy Depots </li></ul><ul><li>Commercial </li></ul><ul><li>Original Equipment Manufacturer </li></ul><ul><li>Defense Logistics Agency </li></ul><ul><li>Fleet/Industrial Sites </li></ul><ul><li>Navy Working Capital </li></ul><ul><li>Fund Stock Points </li></ul><ul><li>Foreign Military Sales </li></ul><ul><li>Other Services </li></ul>Demand Planning Supply Planning Inventory Management Procurement Vendors Customers Order Fulfillment Master Data & Financials Core
  11. 11. Types of Testing Integrated System Test (IST) Cycle 1, 2 & 3, User Acceptance Testing (UAT), Operational Assessment (OT-C2A) Technical Test Data Recovery, Host Stress, Network Connectivity and Stress, Continuity of Operations / Disaster Recovery / High Availability / Failover and Application Output / Print Information Assurance / Security Roles / Authorizations, DIACAP (Security Certification) Initial Operational Test & Evaluation (IOT&E) Will consist of field-validation testing at the initial deployment sites and will resolve the remaining COIs and as well as evaluating the operational effectiveness and operational suitability of the Navy ERP system . Developmental Testing Unit Test (UTs), Business Process Procedures (BPPs) and Development Unit Test (TDS), FDS End to End Test (HLD), Functional Test Plans (FTP) and Functional Test Execution (FTEs) at transaction and Business Process level Follow-On Operational Test & Evaluation (FOT&E) Conduct if Required Post Go-Live Pre Go-Live Regression Testing Performed in each cycle as required for changes in solution and defect resolution Supplemental Testing Period for extended non-core development and testing Regression Testing Scenario testing to support new functionality and defect resolution
  12. 12. Update on Implementation - Release 1.1 Filename/RPS Number <ul><li>Release 1.1 Cycle 1 Testing Completed </li></ul><ul><ul><li>2777 Test Cases were executed </li></ul></ul><ul><ul><li>47 Defects were logged </li></ul></ul><ul><li>Release 1.1 Cycle 2 Testing Completed </li></ul><ul><ul><li>3262 Test Cases were executed </li></ul></ul><ul><ul><li>101 Defects were logged </li></ul></ul><ul><li>Release 1.1 Cycle 3Testing </li></ul><ul><ul><li>Cycle 3 began 18 May 2009 </li></ul></ul><ul><ul><li>Cycle 3 will consist of three Dry Runs each with one week of defect resolution </li></ul></ul><ul><ul><ul><li>DR1 18 May - 26 June </li></ul></ul></ul><ul><ul><ul><li>DR2 6 July - 14 Aug </li></ul></ul></ul><ul><ul><ul><li>DR3 24 Aug - 8 Oct </li></ul></ul></ul><ul><ul><li>Reports, Interfaces, Conversions and Enhancements (RICE) objects will be included </li></ul></ul><ul><li>User Acceptance Testing (UAT) Testing – November 2009 </li></ul><ul><li>NAVSUP Release 1.1 Initial GO LIVE scheduled for February 2010 </li></ul>Integrated System Test Cycles
  13. 13. Summary <ul><li>Navy ERP is the Cornerstone of our FM framework for DON Business Transformation </li></ul><ul><ul><li>Standard business processes </li></ul></ul><ul><ul><li>System of record for both General Fund and Working Capital Fund financial accounting and funds control </li></ul></ul><ul><ul><li>USSGL,SFIS, and BEA compliant </li></ul></ul><ul><ul><li>Enables significant reduction in the number of legacy systems requiring support </li></ul></ul><ul><ul><li>Enables, but does not guarantee, audit readiness </li></ul></ul><ul><li>Navy ERP will provide increased efficiency and improved quality of information to support decision making. </li></ul><ul><li>FMO is fully committed to support Navy ERP as the target solution for achieving a vision of improved, integrated, and compliant financial management. </li></ul><ul><li>We are working with DFAS, BTA, the EBO, FMB, the Navy ERP Program Office, and Commands to ensure a successful roll out. </li></ul><ul><li>For additional information, please contact: </li></ul><ul><ul><li>Beverly Veit Ph: 202-685-6703 email: beverly.veit@navy.mil </li></ul></ul><ul><ul><li>Quentin Gilmore Ph: 202-685-6736 email: quentin.gilmore@navy.mil </li></ul></ul><ul><ul><li>Sherri Jordan Ph: 202-685-6723 email: sherri.jordan@navy.mil </li></ul></ul><ul><ul><li>Carl Inman Ph: 216-571-7892 email: carl.inman@dfas.mil </li></ul></ul>
  14. 14. Backup
  15. 15. NAVY ERP CONVERGENCE DoD Business Environment Driving Navy to ERP Chief Financial Officer’s (CFO) Act 2003 ASN (RD&A) directs convergence of pilots NAVSUP Pilot SMART went “Live” (Jan 03) NAVAIR Pilot SIGMA went “Live” NAWC, WCF (Jan 03) 2007 2009 2011 SPAWAR 1.0 “Go-Live” (Oct 09) NAVSUP 1.1 Single Supply Solution (Feb 10) NAVSEA 1.0 General Fund “Go-Live” (Oct 10) NAVSEA 1.0 Working Capital Fund (Oct 11) 2005 NAVAIR 1.0 “Go-Live” (Oct 07) Cabrillo Pilot NAVSEA Pilot NEMAIS went “Live” (Jun 02) NAVAIR Pilot SIGMA went “Live” (GF, Oct 02) SPAWAR Cabrillo Pilot went “Live” (Jul 01) NEMAIS Pilot SIGMA Pilot SMART Pilot 1990 Navy Launched 4 Pilot Programs (1999) 1999 2001 Pilots Award Contracts to Integrators NAVSUP 1.0 “Go-Live” (Oct 08 ) Milestone C (May 07) Initial Operating Capability (May 08)
  16. 16. Navy Financial Management Systems Transition Summary Legacy Environment Target Environment
  17. 17. Current Enterprise Metrics <ul><li>Internal Entitlement </li></ul><ul><ul><li>% Acceptance, WAWF Vendor Pay </li></ul></ul><ul><ul><li>% Payment with Manual Invoices </li></ul></ul><ul><ul><li>Count of Invoices over 30 days old </li></ul></ul><ul><ul><li>% of Penalties vs. Total Payments </li></ul></ul><ul><ul><li>% of Invoices with Interest Penalties vs. Total Count </li></ul></ul><ul><li>External Entitlement </li></ul><ul><ul><li>% Successful Awards, SPS </li></ul></ul><ul><ul><li>% Successful Modified Awards, SPS </li></ul></ul><ul><ul><li>% Acceptance Commercial Pay </li></ul></ul><ul><ul><li>DDEF success rate (Gen Fund) </li></ul></ul><ul><ul><li>DDEF success rate (NWCF) </li></ul></ul><ul><ul><li>Outcome Metrics: </li></ul></ul><ul><ul><li># of Late Entitlement Payments/Week, </li></ul></ul><ul><ul><li>Late External Entitlements $/Week </li></ul></ul><ul><ul><li>$ Unrecorded Expenditures/Collections </li></ul></ul><ul><li>External Reporting </li></ul><ul><ul><li>% External Reports Complete </li></ul></ul><ul><li>Internal Reporting </li></ul><ul><ul><li>% Critical Internal Reports Complete </li></ul></ul>Filename/RPS Number
  18. 18. OBJECTIVE 95% THRESHOLD 85% FUTURE: -CLIN/SLIN MISMATCH +10% -7 WYs ELIN CROSS REFERENCE TABLE + 8% (JAN 09 DELIVERY, METRIC 2 MONTH LAG) -5 WYs AUTOMATED ACCOUNTS PAYABLE (JUL 08 DELIVERY, METRIC 2 MONTH LAG) -1 WY - AUTOMATED SES (MOCAS) + 5% (JUN 09 DELIVERY, METRIC 2 MONTH LAG) -12 WYs LONG TERM TARGET = MINIMUM OF OBJECTIVE LEVEL 85% 58% 73% 68% 68% 68% 75% 13% 90% 0% 25% 50% 75% 100% JAN 08 APR 08 JUL 08 AUG 08 SEP 08 JAN 09 AUG 09 TBD FIRST PASS SUCCESS RATE SUCCESS RATE THRESHOLD OBJECTIVE PROJECTION OCT NOV 08 08 MANUAL OBLIGATION POSTINGS + 4% (SEP 09 COMPLETION, METRIC 1 MONTH LAG) -4 WYs 61% 80% 75% 58% DEC 08 75% FEB MAR APR MAY JUN JUL 09 09 09 09 09 09 - NAVY ERP ACTION SCHEDULED - NAVAIR ACTION - DECISION AND SCHEDULE STILL REQUIRED 71% EXTERNAL ENTITLEMENT % Acceptance Commercial Pay (Major Contracts)
  19. 19. Test Schedule – Release 1.1 Testing Events Date/Periods Test Readiness Review – Cycle 1 5 Feb 2009 <ul><ul><li>Cycle 1 Test </li></ul></ul>9 Feb 2009 – 5 Mar 2009 Test Readiness Review – Cycle 2 26 Mar 2009 <ul><ul><li>Cycle 2 Test </li></ul></ul>30 Mar 2009 – 23 Apr 2009 Test Readiness Review – Cycle 3 14 May 2009 <ul><ul><li>Cycle 3 Test </li></ul></ul>18 May 2009 – 8 Oct 2009 Test Readiness Review – UAT 29 Oct 2009 <ul><ul><li>User Acceptance Test (UAT) </li></ul></ul>2 Nov 2009 – 25 Nov 2009 Regression Testing 9 Feb 2009 – 17 Dec 2009 Supplemental Testing Phase 2 Nov 2009 – 17 Dec 2009 Operational Assessment (OT-C2A) 9 Feb 2009 – 10 Dec 2009 OT-C2A Independent Event 7 Dec 2009 – 10 Dec 2009 Operational Test Readiness Review (OT-C2B) Apr 2010 Initial Operational Test and Evaluation (OT-C2B) Apr 2010 – May 2010
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×