Emerson 6 3 4 Upgrade Project Kickoff Project

Emerson 6. 3. 4 Upgrade – Project Kickoff

Project Governance • Standard project governance will be utilized to manage the project, including: ▫ ▫ ▫ ▫ Project Plan Status Reporting Scope Management Cost Control Communication Management Risk Management Quality Control

Project Phases Release Review Dev Setup Upgrade Verification End-to-End Testing Test Migration UAT Migration to Prod Smoke Test Go-Live • Project team working session to review release notes (? ) • Project team to develop project schedule & implementation timeline • Dev hardware refresh • Upgrade applied to Dev environment • App lead to verify packages, agents, style sheets, screen sets and XML interface • CI lead to conduct light testing to validate functionality • Emerson to conduct heavy testing of processes (leverage scripts from previous upgrade) • Menlo CI and App leads to support and retro fit as needed • MW to migrate upgrade Test • Apply MRs for fixes from functional testing • Menlo operations to conduct additional testing related to their functions • Include Emerson Business Units? • MW to upgrade Production • Emerson to execute a few test scripts to validate basic functionality • Typical post go-live support cycle after go-live

Integration Considerations • When will we conduct integration testing? • In which environment will we conduct integration testing? • Who will need to be involved in integration testing? • What are the risks/concerns/callouts, etc for integration in the upgrade?

Impact to Pending Enhancements • November migration will be cancelled • December migration will be postponed or cancelled • Development in Dev will be on hold from 10/2711/17 • Resource availability – Put enhancements on hold so resources can focus on upgrade project

Project Governance Process Documentation ▫ SWIs may need to be updated with any UI changes ▫ Global Process Navigator http: //team/sites/Menlo. Process/OTM/default. aspx Client’s Role: 6 Continuous improvement support, kaizen participation, SWI validation, “client” stakeholder involvement at multiple levels

Project Governance Project Meeting Structure Ø Weekly team meetings Ø Held with entire project team once per week to review project schedule, open items, and next steps Ø Defect Review/Testing Status Calls Ø includes Dev, Test, and Post go-live cycles Ø Held 2 -5 times per week depending on issues found to review pending defects and test progress Ø Go/No-Go Decision Ø Held prior to each upgrade of the next environment to ensure all parties agree to move forward Ø Smoke Testing Ø Typically held the Sunday morning after the Prod upgrade is applied Ø All test participants and support team join an open phone line to review progress and issues found 7

Project Governance Weekly Project Status A 3 8

Lessons Learned from 6. 3. 2

Project Team Emerson • Don Sorg • Russ Hermes • Ken Deters • Brian Sher • Novita Gan • Nathan Menlo • Elaine Blair • Freddy Ibarra • Rajiv Jegannathan • Arun Radhakrishnan • Andrey Bondar

Tentative high-level timeline

Tentative detailed schedule

Next Steps • Build verification checklist and functional test scripts – Arun & Rajiv • Build end-to-end test scripts – Nathan • Scheduling concerns? ▫ Holidays, PTO, other Emerson initiatives? • JIRA project setup ▫ Requested & in progress • Weekly team meetings ▫ Elaine to schedule after kickoff